Contents
1 Introduction
This document describes how to manage the Atlas software.
1.1 Prerequisites
Before starting this procedure, ensure that the following conditions are met:
1.1.1 Conditions
The following is required:
- The system is ready to accept logon attempts from users.
- Root access is available for running the atlas command.
- Root access is available for running the swift command.
2 Atlas Command Overview
This section describes the atlas command syntax and the use of its command parameters.
2.1 Atlas Command and Parameters
The Atlas command suite is implemented by scripting technology. Its purpose is to support software management.
After a successful logon, the atlas command and its parameters are available, as shown in Table 1.
|
Command |
Parameter |
Description |
|---|---|---|
|
sudo atlas |
backup-create --p <password> |
Creates a backup of the key configuration files and folders
contained in the Atlas image, |
|
backup-list |
Lists the available backup files, | |
|
backup-restore --d <id> --p <password> |
Restores the key configuration files and folder from a
backup, | |
|
backup-delete --d <id> [--all] |
Deletes the Atlas backup identified by the backup ID, see Section 2.5. | |
|
cert-create(1) |
Generates self signed default certificates which are not sufficient for a secure TLS communication.(2) | |
|
endpoint-init --host <public_host_ip> <internal_host_ip> |
Creates endpoints for OVFT, MISTRAL and HEAT in Keystone, | |
|
user-init |
Creates OVFT, MISTRAL and HEAT users in Keystone, | |
|
--help |
Prints the atlas command syntax, | |
|
--version |
Prints the current version of Atlas, | |
|
update-network <args> |
Updates the interfaces of Atlas, | |
|
update-haproxy <nbi_ip> <sbi_ip> |
Updates the haproxy-config files of ovft-api, heat-api, and heat-api-cfn of Atlas, see Section 2.11. | |
|
update-cert |
Updates the expired certificates on Atlas, see Section 2.12. | |
|
disable-heat |
Disables Heat from Atlas, see Section 2.13. | |
|
periodic-backup |
Configures periodic backups, see Section 2.14. |
(1) Deprecated
(2) For more information
on the necessary TLS certificates, refer to the "Conditions" section of the documents SW Installation in Multi-Server Deployment and SW Installation in Single Server Deployment.
2.2 Create Backups
The command syntax is as follows:
sudo atlas backup-create [--name <backup_name>] --p <password>
sudo atlas backup-create [--name <backup_name>] ⇒
--p <password>
The optional parameter --name is used to set the name of the backup. The default name is AtlasBackup. The backup name can only contain letters, numbers, and underscores. No special characters are allowed.
The positional parameter --p is used to encrypt backup during backup creation.
To back up the most important files and folders to the current directory, enter the following:
atlasadm@atlas:~ $ sudo atlas backup-create --p atlas_password
atlasadm@atlas:~ $ sudo atlas backup-create ⇒
--p atlas_password
The resulting output is shown in ex-DashboardBackup Example 1.
Example 0 Atlas Backup
Tue 02 May 2017 08:48:23 INFO: Creating Backup "AtlasBackup" with ID=1493707703... Tue 02 May 2017 08:48:23 INFO: Backing up password configuration, home ⇒ directories and database... Tue 02 May 2017 08:48:58 INFO: Done. Tue 02 May 2017 08:49:05 INFO: Encrypting... Tue 02 May 2017 08:49:05 INFO: Done. Tue 02 May 2017 08:49:05 INFO: Uploading Backup "AtlasBackup" of size 654M to ⇒ Swift... Tue 02 May 2017 08:49:15 INFO: Done. Tue 02 May 2017 08:49:15 INFO: Backup Complete!
Example 1 Atlas Backup
Tue 02 May 2017 08:48:23 INFO: Creating Backup "AtlasBackup" with ID=1493707703... Tue 02 May 2017 08:48:23 INFO: Backing up password configuration, home directories and database... Tue 02 May 2017 08:48:58 INFO: Done. Tue 02 May 2017 08:49:05 INFO: Encrypting... Tue 02 May 2017 08:49:05 INFO: Done. Tue 02 May 2017 08:49:05 INFO: Uploading Backup "AtlasBackup" of size 654M to Swift... Tue 02 May 2017 08:49:15 INFO: Done. Tue 02 May 2017 08:49:15 INFO: Backup Complete!
2.3 List Backups
To view the available backup files, enter the following:
atlasadm@atlas:~ $ sudo atlas backup-list
The resulting output is shown in Example 2.
Example 2 Atlas Backup List
+-------------+----------------+-----------+--------+-------------+-----------+ | ID | Name | Storage | Size | Date | Time | +-------------+----------------+-----------+--------+-------------+-----------+ | 1493707703 | AtlasBackup | SWIFT | 654M | 2-May-2017 | 08:49:05 | +-------------+----------------+-----------+--------+-------------+-----------+
2.4 Restore Backups
To restore the most important files and folders from a backup file in the current path, enter the following:
atlasadm@atlas:~ $ sudo atlas backup-restore --d 1493707703 --p atlas_password
atlasadm@atlas:~ $ sudo atlas backup-restore --d ⇒
1493707703 --p atlas_password
The resulting output is shown in Example 3.
Example 3 Atlas Restore
Tue 02 May 2017 11:37:48 INFO: Starting Atlas restore... Tue 02 May 2017 11:37:48 INFO: Restoring database... Tue 02 May 2017 11:37:49 INFO: Done. Tue 02 May 2017 11:37:49 INFO: Restoring etc-puppet-hieradata-passwords.yaml... Tue 02 May 2017 11:37:49 INFO: Done. Tue 02 May 2017 11:37:49 INFO: Restoring home-atlasadm... Tue 02 May 2017 11:37:49 INFO: Done. Tue 02 May 2017 11:37:49 INFO: Restoring root... Tue 02 May 2017 11:37:56 INFO: Done. Tue 02 May 2017 11:37:56 INFO: Verifying users... Tue 02 May 2017 11:38:29 INFO: Applying configuration... Tue 02 May 2017 11:38:47 INFO: Restarting services... Tue 02 May 2017 11:38:50 INFO: Done. Tue 02 May 2017 11:38:50 INFO: Successfully restored from backup:1493707703
2.5 Delete Backups
To delete an Atlas backup, use the atlas backup-delete command with the following syntax:
atlas backup-delete --d <id> [--all]
The positional parameter --d is the ID of the backup.
The optional parameter --all can be used to delete the backup from both /var/archives and Swift. If this parameter is not specified, the command only deletes the backup from /var/archives.
Example 4 shows the command for deleting backup 1493707703 from both /var/archives and Swift.
The resulting output is shown in Example 5.
Example 5
Tue 02 May 2017 10:09:20 INFO: Deleting Backup 1493707703 Tue 02 May 2017 10:09:24 INFO: Backup Delete Complete! +------------+--------------+--------------+--------+--------------+----------+ | ID | Name | Storage | Size | Date | Time | +------------+--------------+--------------+--------+--------------+----------+ +------------+--------------+--------------+--------+--------------+----------+
2.6 Create OVFT, MISTRAL and HEAT Endpoints in Keystone
To create endpoints in Keystone for OVFT, MISTRAL and HEAT, enter the following:atlasadm@atlas:~ $ sudo atlas endpoint-init --host public.atlas.local public.atlas.local
atlasadm@atlas:~ $ sudo atlas endpoint-init ⇒
--host public.atlas.local public.atlas.local
The resulting output is shown in Example 6.
Example 6 Atlas Endpoint Init
+-------------+----------------------------------+ | Field | Value | +-------------+----------------------------------+ | description | OpenStack Workflow service | | enabled | True | | id | c78b349385f442ecbb77bf1292bab18d | | name | mistral | | type | workflowv2 | +-------------+----------------------------------+ Deleting existing mistral endpoint Creating mistral endpoints +--------------+------------------------------------+ | Field | Value | +--------------+------------------------------------+ | adminurl | https://public.atlas.local:8989/v2 | | id | a9ef5b440957472985ab895847e3a57d | | internalurl | https://public.atlas.local:8989/v2 | | publicurl | https://public.atlas.local:8989/v2 | | region | RegionOne | | service_id | c78b349385f442ecbb77bf1292bab18d | | service_name | mistral | | service_type | workflowv2 | +--------------+------------------------------------+ +-------------+----------------------------------+ | Field | Value | +-------------+----------------------------------+ | description | OVF Translator | | enabled | True | | id | b45768bf8cd8425fa0f9fa5f277aeff2 | | name | ovft | | type | translator | +-------------+----------------------------------+ Deleting existing oOvft endpoint Creating ovft endpoints +--------------+--------------------------------------------------+ | Field | Value | +--------------+--------------------------------------------------+ | adminurl | https://public.atlas.local:8888/v1/$(tenant_id)s | | id | 4021bc663b2c493f86d611f428d01fd0 | | internalurl | https://public.atlas.local:8888/v1/$(tenant_id)s | | publicurl | https://public.atlas.local:8888/v1/$(tenant_id)s | | region | RegionOne | | service_id | b45768bf8cd8425fa0f9fa5f277aeff2 | | service_name | ovft | | service_type | translator | +--------------+--------------------------------------------------+ +-------------+----------------------------------+ | Field | Value | +-------------+----------------------------------+ | description | Heat Orchestration | | enabled | True | | id | 6efc3f6a09bc404c84970c2bb093acd9 | | name | heat | | type | orchestration | +-------------+----------------------------------+ Deleting existing heat endpoint Creating heat endpoints +--------------+--------------------------------------------------+ | Field | Value | +--------------+--------------------------------------------------+ | adminurl | https://public.atlas.local:8004/v1/$(tenant_id)s | | id | dd828421405e417b9e39bf73964573f1 | | internalurl | https://public.atlas.local:8004/v1/$(tenant_id)s | | publicurl | https://public.atlas.local:8004/v1/$(tenant_id)s | | region | RegionOne | | service_id | 6efc3f6a09bc404c84970c2bb093acd9 | | service_name | heat | | service_type | orchestration | +--------------+--------------------------------------------------+ +-------------+----------------------------------+ | Field | Value | +-------------+----------------------------------+ | description | Heat CloudFormation | | enabled | True | | id | 7cf2431134b84c329913b74e568dc772 | | name | heat-cfn | | type | cloudformation | +-------------+----------------------------------+ Deleting existing heat-cfn endpoint Creating heat-cfn endpoints +--------------+------------------------------------+ | Field | Value | +--------------+------------------------------------+ | adminurl | https://public.atlas.local:8000/v1 | | id | fc90c2447e9649aa85472fb40b2d55c0 | | internalurl | https://public.atlas.local:8000/v1 | | publicurl | https://public.atlas.local:8000/v1 | | region | RegionOne | | service_id | 7cf2431134b84c329913b74e568dc772 | | service_name | heat-cfn | | service_type | cloudformation |
2.7 Create OVFT, MISTRAL and HEAT Users in Keystone
To create users in Keystone for OVFT, MISTRAL and HEAT, enter the following:
atlasadm@atlas:~
$ sudo atlas user-init
The resulting output is shown in Example 7.
- Note:
- Each time the command is executed, a new user is created after deleting the existing users.
Example 7 Atlas User Init
+------------+----------------------------------+ | Field | Value | +------------+----------------------------------+ | email | mistral@example.com | | enabled | True | | id | 0d3a48e1cf814e8895ffabc4bd2b3ba1 | | name | mistral | | project_id | 22fd28267ac44929ab70967d5963e1fb | | username | mistral | +------------+----------------------------------+ +------------+----------------------------------+ | Field | Value | +------------+----------------------------------+ | email | mistral@example.com | | enabled | True | | id | 233283bf2c014604972e4056f32b5bfd | | name | mistral | | project_id | 22fd28267ac44929ab70967d5963e1fb | | username | mistral | +------------+----------------------------------+ +-------+----------------------------------+ | Field | Value | +-------+----------------------------------+ | id | 5e2b5e5e9a95493080cc86affd190ad1 | | name | admin | +-------+----------------------------------+ +------------+----------------------------------+ | Field | Value | +------------+----------------------------------+ | email | ovft@example.com | | enabled | True | | id | aff611fe263447649950ef007dfb90e1 | | name | ovft | | project_id | 22fd28267ac44929ab70967d5963e1fb | | username | ovft | +------------+----------------------------------+ +------------+----------------------------------+ | Field | Value | +------------+----------------------------------+ | email | ovft@example.com | | enabled | True | | id | 57223f27ac364c429028af3f2f21f351 | | name | ovft | | project_id | 22fd28267ac44929ab70967d5963e1fb | | username | ovft | +------------+----------------------------------+ +-------+----------------------------------+ | Field | Value | +-------+----------------------------------+ | id | 5e2b5e5e9a95493080cc86affd190ad1 | | name | admin | +-------+----------------------------------+ +------------+----------------------------------+ | Field | Value | +------------+----------------------------------+ | email | heat@example.com | | enabled | True | | id | 919bca6fe9c044388c7850738084d245 | | name | heat | | project_id | 22fd28267ac44929ab70967d5963e1fb | | username | heat | +------------+----------------------------------+ +------------+----------------------------------+ | Field | Value | +------------+----------------------------------+ | email | heat@example.com | | enabled | True | | id | 5451d5cc2b5f4658a42260fe6bd1c946 | | name | heat | | project_id | 22fd28267ac44929ab70967d5963e1fb | | username | heat | +------------+----------------------------------+ +-------+----------------------------------+ | Field | Value | +-------+----------------------------------+ | id | 5e2b5e5e9a95493080cc86affd190ad1 | | name | admin | +-------+----------------------------------+ +-------+----------------------------------+ | Field | Value | +-------+----------------------------------+ | id | 7ba93109c5b74cc3b08ac7b980a03d82 | | name | heat_stack_user | +-------+----------------------------------+ +-------+----------------------------------+ | Field | Value | +-------+----------------------------------+ | id | 6c74920126324dab862849eedd170898 | | name | heat_stack_user | +-------+----------------------------------+
2.8 Help
To view the syntax of the atlas command,
enter the following:
atlasadm@atlas:~ $ sudo atlas --help
The resulting output is shown in Example 8.
Example 8 Atlas Help
Atlas Utility Functions ATLAS-CXC1737937_3-R8A06-0 f53b617-1188 usage: /opt/atlas/bin/atlas [options] <argv>... Options: --help, -h show this help message and exit. --version show program's version number and exit user-init Create ovft and heat users in keystone endpoint-init Create endpoints for ovft and heat in keystone cert-create Create initial set of self-signed certs backup-create Create new Atlas backup backup-restore Restore from existing backup backup-list List existing backups by date backup-delete Delete the backup with given ID update-network Update network interfaces of Atlas update-haproxy Configure haproxy update-cert Update certificates disable-heat Disable heat from atlas periodic-backup Configure periodic backup
2.9 Version
To view the exact version of the Atlas Virtual Machines (VMs),
enter the following:
atlasadm@atlas:~ $ sudo atlas --version
The resulting output is shown in Example 9.
2.10 Update Network
To update the interfaces of the Atlas VMs, enter the following:atlasadm@atlas:~ $ sudo atlas update-network <nbi_ip> <sbi_ip> <gateway_nbi> <gateway_sbi> <cidr_sbi> <cidr_public> <nbi_mask> <sbi_mask>
atlasadm@atlas:~ $ sudo atlas update-network ⇒
<nbi_ip> <sbi_ip> <gateway_nbi> <gateway_sbi> ⇒
<cidr_sbi> <cidr_public> <nbi_mask> <sbi_mask>
- Note:
- For <cidr_public>, use cee_om_sp, the network used for vCIC northbound communication.
The resulting output is shown in Example 10.
Example 10 Atlas Update Network
atlasadm@atlas:~ $ sudo atlas update-network 10.33.168.4 10.33.168.36 10.33.168.1 10.33.168.33 10.33.168.32/27 10.33.168.96/27 255.255.255.224 255.255.255.224 ssh stop/waiting ssh start/running, process 5831
2.11 Update HAProxy
To update the HAProxy configuration files with the Northbound Interface (NBI) and the Southbound Interface (SBI) IPs, enter the following command:
atlasadm@atlas:~ $ sudo atlas update-haproxy NBI_IP SBI_IP
2.12 Update Certificates
To update the expired certificates of Atlas VMs, enter the following command:
atlasadm@atlas:~$ sudo atlas update-cert --atlas <path_to_atlas_cert_file> --cee <path_to_nbi_cert_file>
atlasadm@atlas:~$ sudo atlas update-cert --atlas ⇒
<path_to_atlas_cert_file> --cee <path_to_nbi_cert_file>
The resulting output is shown in Example 11.
Example 11 Update Certificate - Output
atlasadm@atlas:~ $ sudo atlas update-cert --atlas /home/atlasadm/atlas.crt
New certificates are stored in the following files, in the format below:
/etc/ssl/certs/atlas.crt
--BEGIN CERTIFICATE--
<certificate>
--END CERTIFIACTE--
--BEGIN PRIVATE
KEY--
<private_key>
--END PRIVATE KEY--
/etc/ssl/certs/atlas.pem
--BEGIN CERTIFICATE--
<certificate>
--END CERTIFIACTE--
/etc/ssl/private/atlas.key
--BEGIN PRIVATE KEY--
<private_key>
--END PRIVATE KEY--
2.13 Disable Atlas Heat
To disable Heat service in Atlas, enter the following:
atlasadm@atlas:~ $ sudo atlas disable-heat true
- Note:
- The atlas disable-heat command is not recommended as an Atlas post-installation step. The variable DISABLE_ATLAS_HEAT must be set to true during Atlas installation in order to disable Heat service. Refer to the Install Atlas section in the Atlas SW Installation for more information.
2.14 Periodic Backups
To configure periodic backups in Atlas, use the atlas periodic-backup command with the following syntax:
atlasadm@atlas:~ $ sudo atlas periodic-backup [--enable <true|false>] [--time-period <cron>]
[--current-password <current_password> --new-password <new_password>]atlasadm@atlas:~ $ sudo atlas periodic-backup⇒
[--enable <true|false>] [--time-period <cron>]
[--current-password <current_password>⇒
--new-password <new_password>]
Parameter --enable is set true to create periodic backups and false to disable Atlas periodic backups.
Parameter --time-period is used to set the time period for taking backups. It is a cron expression. It is not allowed when periodic backup is disabled.
Parameters --current-password and --new-password are used together to change the periodic backup password. They are not allowed when periodic backup is disabled.
- Note:
- All the parameters are optional and can be used together or individually.
2.14.1 Enable Periodic Backups
To enable periodic backups, use the following command:
atlasadm@atlas:~ $ sudo atlas periodic-backup --enable true
atlasadm@atlas:~ $ sudo atlas periodic-backup⇒
--enable true
This command enables periodic backup for Atlas with default time interval and default password specified in localrc at the time of installation. For more information, refer to section Install Atlas in the Atlas SW Installation document.
2.14.2 Disable Periodic Backups
To disable periodic backups, use the following command:
atlasadm@atlas:~ $ sudo atlas periodic-backup --enable false
atlasadm@atlas:~ $ sudo atlas periodic-backup⇒
--enable false
This command ensures that no periodic backups are captured.
2.14.3 Configure Time Period to Take Periodic Backups
To change the time interval of periodic backups, execute the following command:
atlasadm@atlas:~ $ sudo atlas periodic-backup --time-period "0 */3 * * *"
atlasadm@atlas:~ $ sudo atlas periodic-backup⇒
--time-period "0 */3 * * *"
- Note:
- The time period value is a cron expression and needs to be given in quotes.
2.14.4 Change Periodic Backup Password
To change the periodic backup password, execute the following command:
atlasadm@atlas:~ $ sudo atlas periodic-backup --current-password <current_password> --new-password <new_password>
atlasadm@atlas:~ $ sudo atlas periodic-backup⇒
--current-password <current_password>⇒
--new-password <new_password>
Command example:
atlasadm@atlas:~ $ sudo atlas periodic-backup --current-password ‘a9a75c#e5’ --new-password ‘q2k9pDfnc’
atlasadm@atlas:~ $ sudo atlas periodic-backup⇒
--current-password ‘a9a75c#e5’ --new-password ‘q2k9pDfnc’
- Note:
- The default password is randomly generated during Atlas installation and can be changed by updating variable BACKUP_PASSWORD in localrc before Atlas installation. Single quotes are used if any special characters are present in the password.
3 Swift Command Overview
This section describes the swift command, which is used to upload and download the Atlas backup files.
- Note:
- Before the swift command can be
entered, use source openrc for OpenStack
credentials and change the user from atlasadm to root:
atlasadm@atlas:~ $ source openrc
atlasadm@atlas:~ $ sudo -i
Additionally, the AtlasBackups container must exist in Swift.
3.1 Swift Command and Parameters
The syntax of the swift command and its parameters are shown in Table 2.
|
Command |
Parameter |
Description |
|---|---|---|
|
swift |
download |
Downloads backup files from Swift, |
|
list |
Lists the available backup files in Swift, |
3.2 Download Backup Files
To download the backup directory from Swift, enter the following:
root@atlas:~# cd /var/archives
root@atlas:/var/archives/# swift download AtlasBackups -p <atlas_backupname><id>
root@atlas:/var/archives/# swift download AtlasBackups ⇒
-p <atlas_backupname><id>
where atlas_backupname is the name of the backup and ID is the ID of the backup.
The command input is shown in Example 12.
Example 12 Swift Download Backup
root@atlas:/var/archives# swift download AtlasBackups -p AtlasBackup1520490601
3.3 List Backup Files
To list the backup files in Swift, enter
the following:
root@atlas:~ # swift list
AtlasBackups
To achieve an output for a specific ID only, add the following
to the command:
| grep <id>
The command and the resulting output, using a specific ID, is shown in Example 13.
Example 13 Swift List Backup
root@atlas:~ # swift list AtlasBackups | grep 1520490601 AtlasBackup1520490601/.meta AtlasBackup1520490601/AtlasBackup.1520490601-all-mysql-databases.sql.bz2.enc AtlasBackup1520490601/AtlasBackup.1520490601-etc-puppet-hieradata-passwords.⇒ yaml.master.tar.gz.enc AtlasBackup1520490601/AtlasBackup.1520490601-home-atlasadm.master.tar.gz.enc AtlasBackup1520490601/AtlasBackup.1520490601-root.master.tar.gz.enc AtlasBackup1520490601/AtlasBackup.1520490601.sha256.enc
4 Configure Legal Warning
This section describes the procedure to configure legal warning for Atlas CLI and GUI.
To configure the legal warning for CLI, follow these steps:
- Log in as atlasadm user:
root@cic-0-1:~# ssh atlasadm@<atlas_sbi_ip>
- Switch user to root:
atlasadm@atlas:~$ sudo su
[sudo] password for atlasadm:
root@atlas:/home/atlasadm#
- Update the following text in file /etc/issue
Login to Atlas:
This system is restricted solely to Ericsson authorized users for legitimate business purposes only. The actual or attempted unauthorized access, use, or modification of this system is strictly prohibited by Ericsson. Unauthorized users are subject to Company disciplinary proceedings and/or criminal and civil penalties under state, federal, or other applicable domestic and foreign laws. The use of this system may be monitored and recorded for administrative and security reasons. Anyone accessing this system expressly consents to such monitoring and is advised that if monitoring reveals possible evidence of criminal activity, Ericsson may provide the evidence of such activity to law enforcement officials. All users must comply with Ericsson Security Policy & Requirements regarding the protection of Ericsson information assets.
To configure the legal warning for GUI, follow these steps:
- Log on as atlasadm user:
root@cic-0-1:~# ssh atlasadm@<atlas_sbi_ip>
- Switch user to root:
atlasadm@atlas:~$ sudo su
[sudo] password for atlasadm:
root@atlas:/home/atlasadm#
- Update following text in file /usr/local/lib/python2.7/dist-packages/ui_theme/templates/ui_theme/auth/_login_form.html:
Only authorized users may access the system. Unauthorized users are subject to disciplinary proceedings and/or criminal and civil penalties.
- Restart the apache2 service
by executing the following command:
root@atlas:/home/atlasadm# sudo service apache2 restart
5 Manage Atlas Users
An administrator user can create or delete Atlas users.
5.1 Create User
As an administrator user, perform following steps to create a user:
- Note:
- The password must be of 14 or more characters with at least one special, numeric, lowercase and uppercase character.
- Log on to Atlas VM:
ssh atlasadm@<atlas_ip>
atlasadm@atlas:~$ - Create a user:
atlasadm@atlas:~$ sudo adduser new_user
[sudo] password for atlasadm:
Adding user `new_user' ...
Adding new group `new_user' (1003) ...
Adding new user `new_user' (1003) with group `new_user' ...
Creating home directory `/home/new_user' ...
Copying files from `/etc/skel' ...
Enter new UNIX password:
Retype new UNIX password:
passwd: password updated successfully
Changing the user information for new_user
Enter the new value, or press ENTER for the default
Full Name []:
Room Number []:
Work Phone []:
Home Phone []:
Other []:
Is the information correct? [Y/n] - Verify the new user by logging on to Atlas with the new
user credentials:
ssh new_user@<atlas_ip>
5.2 Delete User
As an administrator user, perform following steps to delete a user:
- Log on to Atlas VM:
ssh atlasadm@<atlas_ip>
atlasadm@atlas:~$ - Delete the user:
atlasadm@atlas:~$ sudo deluser new_user
- Note:
- The details of all the user logon activities are logged in /var/log/auth.log.