Contents

1   Introduction

This administrator guide describes the Ericsson Atlas dashboard modifications compared to the OpenStack dashboard (Horizon). It also adds examples on features not described in the community user guide. For information on the OpenStack dashboard, refer to the OpenStack End User Guide. For detailed information about the OpenStack dashboard (Horizon) from an administrator perspective, refer to the OpenStack Administrator Guide. For further information on supported options, refer to the relevant document:

• OpenStack Networking API in CEE in BSP Deployment
• OpenStack Networking API in CEE in Dell Multi-Server Deployment
• OpenStack Networking API in CEE in Single Server Deployment

The target group of the document consists of the CEE administrators using the Atlas Graphical User Interface (GUI) for their operations.

1.1   Limitations

The following limitations apply to the Atlas dashboard:

• Atlas is best viewed using Google Chrome™ version 40.0 or later, but it also supports Mozilla Firefox® 40.0+.

  Internet Explorer is not supported.

• Previous logon information in Atlas GUI is not displayed, since the logon information for Keystone users is not stored by Keystone.
• Inactivity time for user account is not allowed, as Keystone does not provide the option to disable a dormant user.
• In case of an expired certificate, update the certificate. Otherwise, proceed at your own risk.
• In the Instances panel, Firefox does not automatically update the row after Instance creation. This is due to a cache issue in Firefox: the browser caches the page, preventing the redirection of the URL.
• If using Firefox, logout is not possible by selecting Sign Out from the drop-down menu in Logged in as. This is due to a cache issue in Firefox.

  Workaround: Do the following:

  1. Log on to Atlas VM and switch to root user:

     <user@laptop>:~# ssh atlasadm@<atlas_ip_address>atlasadm@atlas:~$ sudo -i

  2. Execute the following commands:

     sed -i 's/def switch.*/@never_cache\n&/' /usr/lib/python2.7/dist-packages/openstack_auth/views.py 
     sed -i 's/def logout.*/@never_cache\n&/' /usr/lib/python2.7/dist-packages/openstack_auth/views.py 

     sed -i 's/def switch.*/@never_cache\n&/' ⇒
     /usr/lib/python2.7/dist-packages/openstack_auth/views.py 
         sed -i 's/def logout.*/@never_cache\n&/' ⇒
     /usr/lib/python2.7/dist-packages/openstack_auth/views.py 

  3. Restart Apache service by executing the following command:

         sudo service apache2 restart

  4. Clear the Firefox browser cache.
• Resource Usage category is removed from GUI element Categories, as the code is deprecated for several cycles in the OpenStack community.
• The object store, Swift, is disabled by default, since Swift is not available for non-admin tenants.

2   GUI Description

This section describes the GUI of Atlas used in CEE.

To enter Atlas, the username and password of the admin user must be typed in at the login screen shown in Figure 1.

Figure 2 shows the GUI elements used for the operations in Atlas.

The following GUI elements are available in the screen:

Options (≡)	Click on the icon to display Categories. Categories can be pinned as a sidebar by clicking the pin icon.
Categories	The individual menu items on the left are called categories in the OpenStack terminology.
Tabs	The menu items on the left are referred to as tabs in the OpenStack terminology.
Region	The name of the current region is displayed.
Project	The user must select a tenant from this drop-down menu.
Logged in as	The name of the user logged in is displayed.
Help	Click on the icon to display help for using the Atlas GUI, and for product information.

In Atlas GUI, memory and storage quantities are represented according to the JESD100B.01 standard:

• KB refers to 2¹⁰ bytes
• MB refers to 2²⁰ bytes
• GB refers to 2³⁰ bytes

There are three initial steps common to the operations described in this document:

1. Log on to the Atlas dashboard as admin user.
2. Select the appropriate project in the Project drop-down menu.
3. Click on the Options symbol to open the Categories drop-down menu.

4. Click the <Operation> category which is related to that operation.

3   Change Password

To change the user or administrator password, use Atlas web UI, as described in the OpenStack Horizon documentation, Reference [1].

Note:  

If the administrator user password is changed through the GUI, refer to section Changing Password for OpenStack Administrator in the Security User Guide.

4   Configure Session Time-out

The Atlas GUI default session time corresponds to the Keystone expiry time, which is 3600 seconds by default.

To configure the session time-out, do the following:

1. Log on to Atlas VM and switch to root user:

   <user@laptop>:~# ssh atlasadm@<atlas_ip_address>

   atlasadm@atlas:~$ sudo -i

2. Open the file: /usr/lib/python2.7/dist-packages/openstack_dashboard/settings.py
3. Change the value of the SESSION_TIMEOUT variable to the desired value (in seconds).

   SESSION_TIMEOUT supersedes the token time-out when a shorter Atlas session time-out is configured. If a token expires in 60 minutes, a value of 1800 will log users out after 30 minutes.

4. Restart the Apache service:

   sudo service apache2 restart

5   Manage Networks

This section describes how to manage networks. An overview of the Networks screen is shown in Figure 3.

For further information on CEE network interfaces, refer to the relevant document:

• OpenStack Networking API in CEE in BSP Deployment
• OpenStack Networking API in CEE in Dell Multi-Server Deployment
• OpenStack Networking API in CEE in Single Server Deployment

5.1   Create Network

To create a network, perform the following steps:

1. Log on to the Atlas dashboard, select the appropriate project with admin view, and click the Networks category.
2. Click Create Network.

   Atlas shows the network in the Networks category.

3. In the Networks window, specify the following fields:

   Name	Description or Action
   Name (Optional)	A name to identify the network
   Project	A project for the network
   Provide Network Type	Select any of the following options: Local, VLAN, GRE and VXLAN. If the network type is VLAN, select Physical Network and Segmentation ID.
   Physical Network	A name of the physical network over which the virtual network is implemented
   Segmentation ID	Segmentation ID to use
   Admin State	Set Admin State to Down.
   Shared (Optional)	Check this option to set the network as shared.
   External Network (Optional)	Check this option to set the network as external.

5.2   Create Subnet

To create a subnet, perform the following steps:

1. Log on to the Atlas dashboard, select the appropriate project with admin view, and click the Networks category.
2. Select a network for the subnet to be created.
3. Click Create Subnet.
4. In the Create Subnet window, specify the following fields:

   Name	Description or Action
   Subnet Name (Optional)	A name to identify the subnet
   Network Address	Specify the IP address of the subnet.
   IP Version	Select either IPv4 or IPv6.
   Gateway IP (Optional)	The IP address of a specific gateway
   Disable Gateway (Optional)	Check this option to disable the gateway IP address.

   Name	Description or Action
   Enable DHCP (Optional)	Check this option to enable DHCP.
   Allocation Pools (Optional)	Specify the IP address pools that can be allocated.
   DNS Name Servers (Optional)	Specify the name of the DNS servers to be allocated.
   Host Routes (Optional)	Specify the IP address of host routes.

5. Click Create.

   Atlas shows the subnet in the Subnets section of the selected networks.

5.3   Create Port

To create a port, perform the following steps:

1. Log on to the Atlas dashboard, select the appropriate project with admin view, and click the Networks category.
2. Select a network for the port to be created.
3. Click Create Port.
4. In the Create Port window, specify the following fields:

   Name	Description or Action
   Name (Optional)	A name to identify the port
   Admin State(1) (Optional)	Uncheck this option to set Admin State to Down, instead of Up. (1) Set to Up by default.
   Trunk Port	This check box denotes whether the port would be a trunk port or not. By default, the port is not a trunk port. To create a trunk port, the check box must be checked.
   Device ID (Optional)	The ID of the device to be attached
   Device Owner (Optional)	Device owner attached to the port
   Binding Host ID (Optional)	The ID of the host where the port is allocated

   (1)   Administrative state down is not allowed for trunk ports and their subports. Refer to the relevant OpenStack Networking API in CEE document.
   

   
   
5. Click Create Port.

5.4   Create Subport

To create a subport, perform the following steps:

1. Log on to the Atlas dashboard, select the appropriate project with admin view, and click the Networks category.
2. Select the network, which has the trunk port, to which the subport is to be associated.
3. Open the drop-down list of the row containing the trunk port, in column Actions.
4. Select Create Subport.
5. In the Create Subport window, specify the following fields:

   Name	Description or Action
   Network ID	The network to which the subport has to be associated
   Subport Name (Optional)	A name to identify the subport
   VLAN ID	The VLAN ID that the server VM uses to tag the traffic
   Trunk Port Name	The name of the parent trunk port

6. Click Create Subport.

   Atlas shows the created subport in the network to which it is associated.

5.5   Delete Port

This section describes how to delete a port.

Note:  

For deleting a trunk port or a subport, the same steps need to be followed. If deleting a trunk port, associated subports must be deleted first, refer to the OpenStack Networking API in CEE:

• OpenStack Networking API in CEE in BSP Deployment
• OpenStack Networking API in CEE in Dell Multi-Server Deployment
• OpenStack Networking API in CEE in Single Server Deployment

Perform the following steps:

1. Log on to the Atlas dashboard, select the appropriate project with admin view, and click the Networks category.
2. Select the network which has the port to be deleted.
3. Click the check box for the port to be deleted.
4. Click Delete Ports.

6   Compute Environment

This section describes how to view, filter and sort the physical hosts in the cloud environment, and how to check what instances are running on a selected host. The Compute Environment screen extends the functionality of the standard Horizon Hypervisors screen.

Note:  

Before initiating the tasks described in this section, make sure that the correct user is logged in and the appropriate project is selected. The Admin tab is only available to the admin user.

An overview of the Compute Environment screen is shown in Figure 4.

6.1   View Available Hosts

To view all available hosts, perform the following steps:

1. Select the Admin tab.
2. Click the Compute Environment category.

The available hosts are shown on the left side of the screen, and the Hypervisor Summary and Instances Summary are shown to the right.

6.2   Instance States

The instance states running on respective hosts are represented in the following two colors above the host names:

• Green: Instance state is Active.
• Red: Instance state is not Active.

6.3   View Host Details

To view detailed information about a host, including the contained instances, perform the following steps:

1. Select Admin tab.
2. Click the Compute Environment category.
3. Click on a host in the list to get detailed information.

   The following information is displayed:

   • Type, vCPU, RAM, and Storage usage
   • The list of Availability Zones and Host Aggregates to which the host belongs
   • The list of instances contained by the host

6.4   Filter and Sort Available Hosts

To filter and sort the available hosts, select the Sort hosts by drop down menu.

The following filter options are available:

• Grouping hosts by Availability Zone or Host Aggregate
• Hosts with Instances only
• Hosts with Alerts only, that is, usage of vCPU, RAM, or storage have exceeded the given limit.

Click the Refresh button to clear all filters.

7   Alarm Monitoring

This section describes how to display active alarms, details about the active alarms, alarm and alert history, and how to reach the operating instructions used for clearing alarms. Additionally, the section contains information about alarm notifications.

Note:  

Before initiating the tasks described in this section, make sure that the correct user is logged in and the appropriate project is selected.

7.1   View Active Alarms

The Active Alarms screen is shown in Figure 5.

To list the active alarms, perform the following steps:

1. Select the Fault Management tab.
2. Click the All Alarms category.
3. Click the Active tab.
4. Specify the time period by filling in the From and To fields. Use the following date format: yyyy-mm-dd.

5. To filter the alarms on severity, click one of the following boxes:
   Critical, Major, Minor, Warning, or Indeterminate.
6. To filter the alarm using keywords (for example, specific problem, severity, time since created), enter the keyword in the search box.

   A list of the filtered results is displayed.

   To view more results, scroll the page.

7.2   View Alarm Details

Figure 6 shows the details of an alarm at the Overview tab of the Alarm Details screen.

To view the alarm details, perform the following steps:

1. Select the Fault Management tab.
2. Click the All Alarms category.
3. Click the Active tab.

4. Select an active alarm by clicking on it.
5. Click the Overview tab for detailed information about the alarm.

7.3   View Alarm Operating Instructions

Figure 7 shows the operating instructions for an alarm at the Operating Instructions tab of the Alarm Details screen.

To display the operating instructions for an alarm, perform the following steps:

1. Select the Fault Management tab.
2. Click the All Alarms category.
3. Click the Active tab.

4. Select an active alarm by clicking on it.
5. Click the Operating Instructions tab to display the alarm operating instructions.

7.4   View Alarm and Alert History

The Alarm & Alert History screen is shown in Figure 8.

To display the alarm and alert history of a time period, perform the following steps:

1. Select the Fault Management tab.
2. Click the All Alarms category and click the History tab.
3. Specify the time period by filling in the From and To fields. Use the following date format: yyyy-mm-dd.
4. Filter the alarms using keywords (for example, specific problem, severity, time since created) using the Search Alarms field.

   A list of the filtered results is displayed.

   To view more results, scroll the page.

Reference List

[1] OpenStack Horizon documentation, https://docs.openstack.org/horizon/pike/user/log-in.html#openstack-dashboard-settings-tab.