Contents

1   Introduction

The Ericsson dashboard (Atlas) for the Cloud Execution Environment is based on the OpenStack dashboard (Horizon). For more information on the OpenStack dashboard, refer to the community user guide OpenStack End User Guide.

This document describes the additional functions of the Ericsson dashboard, Atlas, as compared to OpenStack Horizon. Refer to Atlas Overview for more information.

The target group of this document consists of the users operating virtual resources with the Atlas Graphical User Interface (GUI).

Note:  

The list of supported Atlas features varies depending on the specific Cloud Execution Environment (CEE) configuration that is used.

2   Terms

This section explains the expressions used with a special meaning in the Atlas context.

Application		Application refers to the OVF package, HOT template, or TOSCA template.
Catalog		Catalog is a user interface for managing the applications.
HOT		Heat Orchestration Engine (HOT) is the template format used for orchestration of stacks, that is, VMs and related support artifacts, using the OpenStack Heat service.
OVF		The Open Virtualization Format (OVF) provides a platform independent, efficient, extensible, and open packaging distribution format.
OVF package		An OVF package is a single TAR file that contains the OVF descriptor. It is also called Open Virtualization Archive (OVA) package.
Security Group		Security groups are a kind of cloud firewall that define which incoming network traffic is forwarded to the instances. For more information, refer to section Add a rule to the default security group in the OpenStack End User Guide. Note:   CEE does not support security groups. For CEE, no security groups need to be assigned. Assigned security groups have no effect on CEE operations.
Stack		Application developers are allowed to create resources of most of the OpenStack resource types by using flexible template languages. Resources include instances, floating IP addresses, volumes, security groups, and users. Once created, the resources are referred to as stacks.
TOSCA		Topology and Orchestration Specification for Cloud Applications (TOSCA) defines the interoperable description of services and applications hosted on the cloud and elsewhere, including their components, relationships, dependencies, requirements, and capabilities. It enables portability and automated management across cloud providers regardless of the underlying platform or infrastructure.

3   GUI Description

This section describes the Graphical User Interface (GUI) of Atlas used in CEE.

Note:  

Atlas is best viewed using Google Chrome™ but it also supports Mozilla Firefox® 40.0+.

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

Note:  

If the admin user password is changed via the GUI, log on to Atlas CLI and execute the following steps manually:

atlasadm@atlas:~$ source openrc
atlasadm@atlas:~$ export OS_PASSWORD=new_password

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

The following GUI elements are available in the screen:

Categories		The menu items on the left are called categories in the OpenStack terminology.
Current Project		The user must select a tenant from this drop-down menu.
Current Region		The name of the current region is displayed.
View		The user must select a view from the drop-down menu, that is, the area of operations the user wants to reach.
User		The name of the user logged in is displayed.
Sign Out		Click on the icon to sign out from Atlas.
Settings		Click on the icon to change password or other user settings.
Help		Click on the icon to display help for using the Atlas GUI, and for product information.

Note:  

In case of an expired certificate, update the certificate. Otherwise, proceed at your own risk.

4   Manage Routers

This section describes how to manage routers. The following procedures are available:

• Create a router, see Section 4.1.
• Add interface to a router, see Section 4.2.

An overview of the Routers screen is shown in Figure 3.

4.1   Create Router

Perform the below steps to create a router.

Note:  

The availability of the Manage Router actions depends on the configuration of CEE.

1. Log on to the Atlas dashboard.
2. Select the appropriate project in the Current Project field, and select Project in the View field.
3. Click the Routers category.
4. Click Create Router.
5. In the Create Router dialog box, specify a name for the router and External Network, then click Create Router.
6. Click Create Router to create a router.

   The Atlas dashboard shows the router in the Routers category.

4.2   Add Interface

To add an interface, perform the following steps:

1. Log on to the Atlas dashboard.
2. Select the appropriate project in the Current Project field, and select Project in the View field.
3. Click the Routers category.
4. Select the router to which the interface is to be added, and click on the Interfaces tab.
5. Click Add Interface.
6. In the Add Interface window, specify the following values:

   Subnet	Select a subnet to be added to the router.
   IP Address (Optional)	Enter an IP address. The default IP address of the interface created is a gateway of the selected subnet. A different IP address of the interface can be specified.

7. Click Add interface to add the selected subnet.

   Atlas dashboard shows the interface in the Interface table of the selected router.

5   Manage Applications in Catalog

This section describes how to manage applications by using the Catalog. The following procedures are available:

• Upload applications, see Section 5.1.
• Show details of applications, see Section 5.2.
• Show details of application templates, see Section 5.3.
• Show details of environment files, see Section 5.4.
• Update applications, see Section 5.5.
• Delete applications, see Section 5.6.
• Launch stacks, see Section 5.7.
• Export applications uploaded in Catalog to local file system, see Section 5.8.

An overview of the Catalog screen is shown in Figure 4.

5.1   Upload Application

This section describes how to add the OVF, HOT or TOSCA file to the Atlas catalog.

The Application Upload screen is shown in Figure 5.

To upload an application, perform the following steps:

1. Log on to the Atlas dashboard.
2. Select the appropriate project in the Current Project field, and select Project in the View field.
3. Click the Catalog category.
4. Click Upload.
5. In the Application Upload window, specify the following values:

   Application Name	A name to identify the application
   Type	The type can be one of the following: OVF package/OVA HOT TOSCA
   Application Source	A source from which the application can be uploaded. Only visible and applicable if the application type is OVF package/OVA. The source can be one of the following: An application Uniform Resource Locator (URL) An application file (OVF package, HOT or TOSCA file)
   Description (Optional)	Description for the application
   Public (Optional)	Apply the relevant setting: Tick the checkbox to set the application to public, that is, visible for all projects. Leave the checkbox empty to only make the application visible for the project that uploads it.
   Protected (Optional)	Apply the relevant setting: Tick the checkbox to make the application protected. Protected applications cannot be deleted. Leave the checkbox empty to make the application deletable.

6. Click Upload to upload an application.

   Atlas dashboard shows the uploaded application in the Catalog category.

5.2   Show Application Overview

The Application Details - Application Overview content is shown in Figure 6.

To show the application overview, perform the following steps:

1. Log on to the Atlas dashboard.
2. Select the appropriate project in the Current Project field, and select Project in the View field.
3. Click the Catalog category.
4. Click on the name of an uploaded application.
5. Click the Overview tab to display the application overview.

5.3   Show Application Template

The Application Details - Application Template content is shown in Figure 7.

To show application templates, perform the following steps:

1. Log on to the Atlas dashboard.
2. Select the appropriate project in the Current Project field, and select Project in the View field.
3. Click the Catalog category.
4. Click on the name of an uploaded application.
5. Click the Template tab to display the application template.

5.4   Show Environment Files

To show the environment files, perform the following steps:

1. Log on to the Atlas dashboard.
2. Select the appropriate project in the Current Project field, and select Project in the View field.
3. Click the Catalog category.
4. Click on the name of an uploaded application.
5. Click the Environment tab to display the present environment files.

5.5   Update Application

To update applications, perform the following steps:

1. Log on to the Atlas dashboard.
2. Select the appropriate project in the Current Project field, and select Project in the View field.
3. Click the Catalog category.
4. Click More in the row of the application to be updated.
5. Click Edit.
6. In the Edit Application window, specify the new value or values. The following can be updated:

   Application Name	The name of the application
   Description	A description for the uploaded application
   Public	Apply the relevant setting: Tick the checkbox to set the application to public, that is, visible for all projects. Leave the checkbox empty to only make the application visible for the project that uploads it.
   Protected	Apply the relevant setting: Tick the checkbox to make the application protected. Protected applications cannot be deleted. Leave the checkbox empty to make the application deletable.

7. Click Save.

5.6   Delete Application

To delete applications, perform the following steps:

1. Log on to the Atlas dashboard.
2. Select the appropriate project in the Current Project field, and select Project in the View field.
3. Click the Catalog category.
4. Click the check box next to the application that is to be deleted.
5. Click Delete Applications.

5.7   Launch Stack From Catalog Page

To launch a stack from the Catalogs page, perform the steps from Section 8.

5.8   Export Application

Applications uploaded in the Catalog can be exported to the local file system.

To export an application, perform the following steps:

1. Log on to the Atlas dashboard.
2. Select the appropriate project in the Current Project field, and select Project in the View field.
3. Click the Catalog category.
4. Click More in the row of the application that is to be exported.
5. Click on Export Application.

Figure 8 shows how to export an application in the Catalog - Applications window.

6   Manage Stacks

This section describes how to manage stacks.

The following procedures are available:

• Launch stack, see Section 6.1.
• Manually scale out resources by adding resources to a running stack, see Section 6.2.
• Manually scale in resources that have been previously scaled out by removing the previously added resources from a running stack, see Section 6.3.

An overview of the Stacks screen is shown in Figure 9.

6.1   Launch Stacks

The Launch Stack screen is shown in Figure 10.

To launch a stack, perform the following steps:

1. Log on to the Atlas dashboard.
2. Select the appropriate project in the Current Project field, and select Project in the View field.
3. Click Stacks category.
4. Click Launch Stack.
5. In the Select Template window, specify the following fields:

   Template Source	A source from which environment files can be added. The following template sources are available: URL File Direct Input
   Environment Source (Optional)	A source from which environment files can be added. The following environment sources are available: URL File Direct Input

6. Click Next.
7. In the Launch Stack window, specify the following fields:

   Stack Name	Enter a name to identify the stack
   Creation Timeout (minutes)	Specify the timeout interval for launching the stack. If the task times out, the stack is not launched
   Rollback on Failure (Optional)	Select this check box if you want the service to roll back changes in case the stack fails to launch
   Password	Specify the password to be used by the default user for creating the stack
   Additional Fields	Additional fields generated by the application template

8. Click Launch.

   Atlas dashboard shows the launched stack and its status in the Stacks category.

9. Verify that the status of the stack is CREATE COMPLETE. If the status is CREATE FAILED, check the logs in /var/log/heat in Atlas or check the stack details for debugging.

For more information on how to provide customized resources while launching a stack from a catalog application, see Section 8.

6.2   Scale out Stack

The scaling feature makes it possible to manually scale resources that belong to a running stack. Use Scale Out to add resources to a running stack.

To scale out a stack, perform the following steps:

1. Go to the Stacks page.
2. In the Actions column, select the Scale Out Stack option from the drop down menu for the stack that is to be scaled out, as shown in Figure 11.

3. Fill in all the scale out data for the new instance like Target Name, optional IP Address, and MAC Address. If there are files to inject, select them. Click on the Submit button when ready. Figure 12 shows the data fields.

4. Click on the Scale Out button as shown in Figure 13.

5. After a successful scale out, the resources scaled out are listed among the resources of the stack, as shown in Figure 14.

6.3   Scale in Stack

The scaling feature makes it possible to manually scale resources that belong to a running stack. Use Scale In to remove scaled resources from a running stack.

To scale in a scaled out stack, perform the following steps:

1. Go to the Stacks page.
2. In the Actions column, select the Scale In Stack option from the drop down menu for the scaled out stack that is to be scaled in as shown in Figure 15.

3. In the Scale In page, select the scaling group (scaled resource) you want to scale in, and click the Scale In button as shown in Figure 16.

4. After a successful scale in, the scaling group (scaled resource) is removed from the stacks resource list, as shown in Figure 17.

7   Manage Workflow in Mistral

This section describes how to manage the workflow in Mistral.

7.1   Create Workbook

To create a workbook, perform the following steps:

1. Log on to the Atlas dashboard, select the appropriate project with Workflow view as shown in Figure 18.

2. Select Workbooks category under the Workflow panel. Click Create Workbook.

3. In the Create Workbook window specify the following fields:

   Name	Action
   Definition Source	File
   Definition File	Select the required template

4. Click Next to see the template description.

5. Click Create Workbook. Workbook is created.

7.2   Create Workflow

To create a workflow, perform the following steps:

1. Log on to the Atlas dashboard, select the appropriate project with Workflows view, and click the Workflows Category.
2. Click Create Workflow.

3. In the Create Workflow window specify the following fields. Click Next:

   Name	Action
   Definition Source	File
   Definition File	Select the required template.

4. After the template description is displayed, select Create Workflow.

7.3   Start Execution

To start an execution, perform the following steps:

1. Log on to the Atlas dashboard, select the appropriate project with WorkFlow view, and click the Workflows Category.
2. Select Execute for respective workflow.
3. In the window specify the following fields:

   Name	Action
   Input	Enter the input file in json format.
   Task name	Enter a name for a specific task to executed. If not specified, the tasks are executed.

4. Click Execute
5. Execution can be seen in the execution page as shown in Figure 21.

6. Click on view in Tasks column to see result of an execution, as shown in Figure 22.

7.4   Create Cronjob

To create a Cronjob, perform the following steps:

1. Log on to the Atlas dashboard. Select the appropriate project with WorkFlow view, and select the Cron Triggers category.
2. Click Create Cron Trigger.
3. In the Create Cron Trigger window specify the following fields:

   Name	Action
   Name	A name to identify the cronjob
   Workflow ID	Workflow ID
   Input	Select any option among Direct Input or File.
   Input Data	If option selected for input is Direct Input enter the data in json format.
   File	If option selected for Input is File upload the required json file.
   Params	Select any one option among Direct Input or File.
   Params File	If option selected for Params is File upload the required json file.
   Params Direct Input	If option selected for Params is Direct Input enter the data in json format.
   First Time	Specify the first scheduling time for the cronjob.
   Count	Specify the frequency for the cronjob.
   Pattern	Specify the cronjob pattern to run periodically.

4. Click Create Cron-Trigger.

7.5   Task Result

To get the result of a particular task, perform the following steps:

1. Log on to the Atlas dashboard, select the appropriate project with WorkFlow view, and select the Tasks category.
2. Select View under Result column against specific action.

7.6   Delete Workflow

To delete a workflow, perform the following steps:

1. Log on to the Atlas dashboard, select the appropriate project with WorkFlow view, and select the Workflows Category.
2. Select the check box next to the workflow to be deleted as shown in Figure 25.
3. Select Delete Workflows.

7.7   Delete Cron Trigger

To delete a Cron Trigger, perform the following steps:

1. Log on to the Atlas dashboard, select the appropriate project with WorkFlow view, and select the Cron Triggers category.
2. Select the checkbox next to the Cron trigger to be deleted.
3. Select Delete Cron Triggers and again select Delete Cron Triggers as shown in Figure 26.

7.8   Delete Execution

To delete an execution, perform the following steps:

1. Log on to the Atlas dashboard, select the appropriate project with WorkFlow view, and click the Executions category.
2. Select the checkbox next to the execution to be deleted.
3. Select Delete Executions and again select Delete Executions as shown in Figure 27.

8   Deployment Wizard from UI

Deployment wizard allows to provide customized resources while launching a stack from a catalog application. It allows the user to provide extra properties for the resources existing in the application.

Note:  

Deployment wizard window has help content for each tab which can be viewed by clicking ?, which helps in understanding the usage.

To launch stack using deployment wizard from catalog panel, perform the following steps:

1. Log on to the Atlas dashboard.
2. Select the appropriate project in the project field and select Project in the View field.
3. Select the Catalog category.
4. Select Launch in the row of the application that is to be used for launching the stack.
5. In the Environment window, select the Load environment variables from a file button, and select the file with environment variables to upload.

6. Select Next.
7. In the Availability zone window, specify the following fields:

   Instances	Names of instances in application
   Zones (Optional)	Select zone in the row of an instance to which zone has to be changed.

8. Select Next.
9. In the Flavors window specify the following fields:

   Instances	Names of instances in application
   Extra specs (Optional)	Select Add Extra Specs. Specify the extra specs in application key=value,key=value format. Select Enter. (Or) Select flavor in the row of an instance to which flavor has to be changed.

10. Select Next.
11. In the Security Groups window, specify the following fields:

    Instances	Names of instances in application
    Security Groups (Optional)	Click on the Close X. Select Gropus in the row of an instance or ports under the instance to which Security Group has to be changed.

    Note:  

    CEE does not support security groups. For CEE, no security groups need to be assigned. Assigned security groups have no effect on CEE operations.

    
    

12. Select Next.
13. In the Configuration for Instance window, specify the following fields:

    Intances	Names of instances in application
    Files (Optional)	Click on Add file. Select the file to inject into an instance in the row of an instance to which Files have to be injected and provide target path for file to be placed (Optional). Click on Add more files to add extra files.
    User Data (Optional)	Click on Add Userdata. Select the user data file in the row of an instance to which user data has to be added.

Note:  

The maximum body size for HTTP requests is set to 112 KB in the default settings of the Nova API. Larger environment files cannot be injected, even if the injected_file_content_bytes quota value is changed for the specific tenant. To increase the default value, set quota_injected_file_content_bytes in /etc/nova/nova.conf on all controllers and restart nova-api.

14. Select Next.
15. In the Metadata window, specify the following fields:

    Instances	Names of instances in application
    Metadata (Optional)	Select Add Metadata, and specify metadata in the text area in key=value, key=value format. Select Save.

16. Select Next.
17. In the Launch Stack window, specify the following fields:

    Stack Name	Enter a name to identify the stack
    Creation Timeout (Minutes)	Specify the timeout interval for launching the stack. If the task times out, the stack is not launched.
    Rollback on Failure (Optional)	Select the check box if you want the service to roll back changes in case the stack fails to launch.
    Password	Specify the password to be used by the default user for creating the stack.
    Additional Fields	Additional fields generated by the application template.

    Note:  

    Depending on the application template, the number of additional fields vary.

    
    

18. Select Launch Stack.

Atlas dashboard shows the launched stack in the Stacks category.

9   Stack Topology

Stack topology provides an interface to look and analyze resource created and or used by stack. Figure 35 shows Stack Topology and its controls.

9.1   Navigation

1. Log on to the Atlas dashboard and select the appropriate project in the Current Project field.
2. Select project in the View field.
3. Click Stacks Category.
4. Click Stack Name in the row of the application to be used for viewing stack topology.
5. Click the Topology tab.

9.2   Icons

Table 1    Stack Topology Icons

Resource	Icon
Server
Flavor
Flavor Pinned
Network
Subnet
Router
Compute
Port
Volume
Heat Delay

9.3   Edges and Connections

Edges show the connection between nodes, the connection can be highlighted by hovering on the node as shown in Figure 36.

9.4   Hierarchy

Use Hierarchy control to switch between random and hierarchy mode as shown in Figure 37.

The reset button changes the topology from hierarchy back to random.

9.5   Labels

Use Labels control to show and hide names of resources. Click the node for a tooltip with more information on the node.

9.6   NUMA/CPU Pinning

Click NUMA to show the connection of a VM with a compute through VM and the pinning information of the flavor.

The pin symbol on Flavor indicates that its pinned and it provides pinning information in tooltip as shown in Figure 41.

By hovering the mouse on Compute, it shows the VM(s) on the compute:

Note:  

NUMA check disables Hierarchy and Reset options.

9.7   Topology Search

Search for nodes based on resource type, name and state of the nodes in the Search bar:

You can also search by using a combination of filters:

10   Stack Overview

Stack Overview displays the parameters and details of the stack. The stack resource summary contains the number of each resource type present in the stack. Each resource type is assigned a unique icon for easy identification of the resource type.

Stack overview tab is divided into seven sections:

• Stack resource summary
• Stack information
• Stack parameters
• Launch parameters
• Outputs
• Activity summary
• Most recent events

10.1   Stack Resource Summary

Only the first row of resource types is displayed initially. To view the resource types, click View all (displaying the total number of resource types available).

10.2   Stack Information

Stack information contains the following information about the stack:

• Description of the stack
• ID of the stack
• Name of the stack
• Region name

10.3   Stack Parameters

Stack parameters display the following information:

• project_id
• stack_id
• stack_name

10.4   Launch Parameters

Launch parameters specifies parameters such as timeout and rollback.

10.5   Outputs

Outputs are displayed below the Launch parameters, which typically contains the output of the stack.

10.6   Activity Summary

Activity summary summaries the total number of events and total number of error events.

10.7   Most Recent Events

This section contains a table with the most recent events. Click the link Complete event list for a complete list.

11   Stack Resources

Stack resources provide a clear view of all the resources in a stack.

To view Stack resources overview, perform the following steps:

1. Log on to the Atlas dashboard.
2. Select the appropriate project in the current project field, and select Project in the View field.
3. Click the Stacks Category.
4. Click the Stack Name of any launched stack.
5. Click the Resources tab to display the resources of the stack.

Stack resource summary gives the details of number of resources present under each resource type. The count of active and error state resources are showed using valid and invalid icons.

The following Stack resources features are available:

• Resource Search: Enter any word in search bar and then press Enter.
• Accordion: > hide extra information and shows it when clicked.
• Pagination: Select number of resources to be shown in the drop down list. Click to select: First - Go to first page and Previous - Go to previous page. Number - Go to particular page. Next - Go to next page. Last - Go to the last page.
• Pinning: The Instance (VM) which is pinned to a particular host is shown with a pin symbol, click Accordian (>) to view details.
• Resource Usage Graph: The Usage of resources is shown in the form of line graphs.
• VCPU Utilization: The VCPU Utilization of an instance is shown with respect to the time. Click > of any instance to view graph.
• Disk Operations: The Disk Operations taken place in an instance is shown with respect to the time. Click > of any instance to view graph.

12   Stack Events

A series of events is generated during the life cycle of a stack. Events can be viewed on clicking the events tab. The page is divided into two section.

• Event Summary
• Events

12.1   Event Summary

The first section of the stack events page presents the summary of the stack, displaying the total number of events and number of error events.

12.2   Events

The table with series of events contains the followings:

• Unique icon for each resource.
• Name of the stack resource, with link to the detail overview of the stack resource.
• Description
• Resource ID
• Time since the event has occurred
• Status: Active: Green. In progress: Yellow. Failed: Red.

Events can be filtered based on name of the resource, description, Resource ID, Time and status. The filter dynamically filters out the contents as the user types in the filter bar. The user can also set the number of events to be displayed (10 or 20).

13   Atlas Help Center

This section describes how to display different types of information, using the Atlas GUI.

The help center is shown in Figure 49.

13.1   Fault Management

To reach the fault management documentation, perform the following steps:

1. Log on to the Atlas dashboard.
2. Select the appropriate project in the Current Project field, and select Project in the View field.
3. Click Help in the top bar.
4. Open a specific fault management document by clicking its title under the Fault Management heading.

13.2   User Guides

To open user guides, perform the following steps:

1. Log on to the Atlas dashboard.
2. Select the appropriate project in the Current Project field, and select Project in the View field.
3. Click Help in the top bar.
4. Open a specific user guide by clicking its title under the User Guide heading.

13.3   Atlas Product Information

This section describes how to display Atlas and CEE product information from the Atlas dashboard. The content of the product information page is shown in Figure 50.

To display Atlas and CEE product information, perform the following steps:

1. Log on to the Atlas dashboard.
2. Select the appropriate project in the Current Project field, and select Project in the View field.
3. Click Help in the top bar.
4. Click About on the Help page.