[Docs] Replace names and images

After commit I49999d702f403d946084c5c4312d367404127b47
some names in dashboard were changed.
This patch replaces these names and related images in the docs.

Closes-Bug: #1583579

Depends-On: I8dea2cdf682ddd615a8dcc37154fc3d90df5c12b
Depends-On: I709308cf34dd8982e73422c26aad487a6068e24c

Change-Id: I3f0719e34c94594555cd5924f5ffd87692053b0a
This commit is contained in:
Tetiana Lashchova 2016-05-23 19:54:15 +03:00
parent 0355244123
commit 928ee3fcc9
38 changed files with 43 additions and 42 deletions

View File

@ -59,7 +59,7 @@ If any problems occur, first of all verify that:
* Check that MySQL or PostgreSQL (depending of what you provided in * Check that MySQL or PostgreSQL (depending of what you provided in
connection string) Python modules are installed on the system. connection string) Python modules are installed on the system.
**Murano panel is not seen in horizon** **Applications panel is not seen in horizon**
* Make sure that :file:`_50_murano.py` file is copied to * Make sure that :file:`_50_murano.py` file is copied to
``openstack-dashboard/local/enabled`` directory and there is no other file, ``openstack-dashboard/local/enabled`` directory and there is no other file,
@ -68,7 +68,7 @@ If any problems occur, first of all verify that:
* Check that murano data is not inserted twice in the settings file and as a * Check that murano data is not inserted twice in the settings file and as a
plugin. plugin.
**Murano panel can be browsed, but 'Unable to communicate to murano-api server.' appears** **Applications panel can be browsed, but 'Unable to communicate to murano-api server.' appears**
If you have murano registered in keystone, verify the endpoint URL is valid If you have murano registered in keystone, verify the endpoint URL is valid
and service has *application-catalog* name. If you don't want to register and service has *application-catalog* name. If you don't want to register

View File

@ -64,7 +64,7 @@ DevStack installation
#. Restart the ``apache2`` service. #. Restart the ``apache2`` service.
Now ``murano-dashboard`` will retrieve packages from Glare. Now ``murano-dashboard`` will retrieve packages from Glare.
#. Log in to Dashboard and navigate to :menuselection:`Murano > Manage > Packages` #. Log in to Dashboard and navigate to :menuselection:`Applications > Manage > Packages`
to view the empty list of packages. to view the empty list of packages.
Alternatively, use the :command:`murano` command. Alternatively, use the :command:`murano` command.

Binary file not shown.

Before

Width:  |  Height:  |  Size: 34 KiB

After

Width:  |  Height:  |  Size: 33 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 64 KiB

After

Width:  |  Height:  |  Size: 52 KiB

View File

@ -75,7 +75,7 @@ Application package could be composed manually. Follow the 5 steps below.
* *Step 5. Create a zip archive, containing the specified files:* ``template.yaml``, ``manifest.yaml``, ``logo.png`` * *Step 5. Create a zip archive, containing the specified files:* ``template.yaml``, ``manifest.yaml``, ``logo.png``
`Applications` page looks like: `Browse` page looks like:
.. image:: /draft/appdev-guide/hotpackages/chef_server.png .. image:: /draft/appdev-guide/hotpackages/chef_server.png

Binary file not shown.

Before

Width:  |  Height:  |  Size: 74 KiB

After

Width:  |  Height:  |  Size: 73 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 155 KiB

After

Width:  |  Height:  |  Size: 114 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 19 KiB

After

Width:  |  Height:  |  Size: 38 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 152 KiB

After

Width:  |  Height:  |  Size: 112 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 73 KiB

After

Width:  |  Height:  |  Size: 73 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 151 KiB

After

Width:  |  Height:  |  Size: 112 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 87 KiB

After

Width:  |  Height:  |  Size: 86 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 142 KiB

After

Width:  |  Height:  |  Size: 128 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 48 KiB

After

Width:  |  Height:  |  Size: 45 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 77 KiB

After

Width:  |  Height:  |  Size: 87 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 87 KiB

After

Width:  |  Height:  |  Size: 90 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 45 KiB

After

Width:  |  Height:  |  Size: 57 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 50 KiB

After

Width:  |  Height:  |  Size: 58 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 78 KiB

After

Width:  |  Height:  |  Size: 75 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 78 KiB

After

Width:  |  Height:  |  Size: 75 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 46 KiB

After

Width:  |  Height:  |  Size: 52 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 47 KiB

After

Width:  |  Height:  |  Size: 53 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 32 KiB

After

Width:  |  Height:  |  Size: 38 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 42 KiB

After

Width:  |  Height:  |  Size: 49 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 34 KiB

After

Width:  |  Height:  |  Size: 39 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 34 KiB

After

Width:  |  Height:  |  Size: 39 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 68 KiB

After

Width:  |  Height:  |  Size: 80 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 113 KiB

After

Width:  |  Height:  |  Size: 94 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 79 KiB

After

Width:  |  Height:  |  Size: 88 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 52 KiB

After

Width:  |  Height:  |  Size: 80 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 80 KiB

After

Width:  |  Height:  |  Size: 79 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 108 KiB

After

Width:  |  Height:  |  Size: 135 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 120 KiB

After

Width:  |  Height:  |  Size: 133 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 86 KiB

After

Width:  |  Height:  |  Size: 86 KiB

View File

@ -36,7 +36,7 @@ Perform the following steps to import an application package from a
.zip file: .zip file:
#. In OpenStack dashboard, navigate to #. In OpenStack dashboard, navigate to
:menuselection:`Murano > Manage > Packages`. :menuselection:`Applications > Manage > Packages`.
#. Click the :guilabel:`Import Package` button on the top right of the #. Click the :guilabel:`Import Package` button on the top right of the
page. page.
@ -88,7 +88,8 @@ murano applications repository:
package to see its full name. package to see its full name.
#. In OpenStack dashboard, navigate to #. In OpenStack dashboard, navigate to
:menuselection:`Murano > Manage > Packages`. :menuselection:`Applications > Manage > Packages`.
#. Click the :guilabel:`Import Package` button on the top right of the #. Click the :guilabel:`Import Package` button on the top right of the
page. page.
@ -129,7 +130,8 @@ Perform the following steps to import a bundle of applications:
desired bundle to see its full name. desired bundle to see its full name.
#. In OpenStack dashboard, navigate to #. In OpenStack dashboard, navigate to
:menuselection:`Murano > Manage > Packages`. :menuselection:`Applications > Manage > Packages`.
#. Click the :guilabel:`Import Bundle` button on the top right of the #. Click the :guilabel:`Import Bundle` button on the top right of the
page. page.
@ -152,8 +154,8 @@ When you have imported many applications and want to quickly find
a required one, you can filter them by category, tags and words that a required one, you can filter them by category, tags and words that
the application name or description contains: the application name or description contains:
In OpenStack dashboard, navigate to :menuselection:`Murano > Application Catalog In OpenStack dashboard, navigate to :menuselection:`Applications > Catalog
> Applications`. > Browse`.
The page is divided into two sections: The page is divided into two sections:
@ -182,7 +184,7 @@ description, use the rightmost filter:
Tags can be specified during the import of an application package. Tags can be specified during the import of an application package.
For example, there is an application that has the word For example, there is an application that has the word
*community-developed* in description. Let's find it with the filter. *document-oriented* in description. Let's find it with the filter.
The following screenshot shows you the result. The following screenshot shows you the result.
.. image:: figures/app_filter_example.png .. image:: figures/app_filter_example.png
@ -195,8 +197,7 @@ Delete an application package
To delete an application package from the catalog, please perform To delete an application package from the catalog, please perform
the following steps: the following steps:
#. In OpenStack dashboard, navigate to :menuselection:`Murano > Manage > Package #. In OpenStack dashboard, navigate to :menuselection:`Applications > Manage > Packages.
Definitions`.
#. Select a package or multiple packages you want to delete and click #. Select a package or multiple packages you want to delete and click
:guilabel:`Delete Packages`. :guilabel:`Delete Packages`.
@ -222,7 +223,7 @@ From environment details page
----------------------------- -----------------------------
#. In OpenStack dashboard, navigate to #. In OpenStack dashboard, navigate to
:menuselection:`Murano > Application catalog > Environments`. :menuselection:`Applications > Catalog > Environments`.
#. Find the environment you want to manage and click #. Find the environment you want to manage and click
:guilabel:`Manage Components`, or simply click on the environment's :guilabel:`Manage Components`, or simply click on the environment's
@ -270,9 +271,9 @@ the Environment Components page.
settings may vary from app to app and are predefined by the settings may vary from app to app and are predefined by the
application author. application author.
#. To add more applications, check :guilabel:`Add more applications #. To add more applications, check :guilabel:`Continue application adding`,
to the environment`, then click :guilabel:`Create` and repeat the then click :guilabel:`Create` and repeat the steps above. Otherwise, just
steps above. Otherwise, just click :guilabel:`Create`. click :guilabel:`Create`.
.. image:: figures/add_to_env/add_more_apps.png .. image:: figures/add_to_env/add_more_apps.png
:alt: Configure Application dialog: Add more applications :alt: Configure Application dialog: Add more applications
@ -287,7 +288,7 @@ From applications catalog page
------------------------------ ------------------------------
#. In OpenStack dashboard, navigate to #. In OpenStack dashboard, navigate to
:menuselection:`Murano > Application catalog > Applications`. :menuselection:`Applications > Catalog > Browse`.
#. On the Applications catalog page, use one of the following methods: #. On the Applications catalog page, use one of the following methods:
@ -368,8 +369,8 @@ following one of the options below:
* Deploy an environment from the Environments page * Deploy an environment from the Environments page
#. In OpenStack dashboard, navigate to :menuselection:`Murano > #. In OpenStack dashboard, navigate to :menuselection:`Applications >
Application Catalog > Environments`. Catalog > Environments`.
#. Select :guilabel:`Deploy Environment` from the Actions drop-down list #. Select :guilabel:`Deploy Environment` from the Actions drop-down list
next to the environment you want to deploy. next to the environment you want to deploy.
@ -384,8 +385,8 @@ following one of the options below:
* Deploy an environment from the Environment Components page * Deploy an environment from the Environment Components page
#. In OpenStack dashboard, navigate to :menuselection:`Murano > #. In OpenStack dashboard, navigate to :menuselection:`Applications >
Application Catalog > Environments`. Catalog > Environments`.
#. Click the name of the environment you want to deploy. #. Click the name of the environment you want to deploy.
@ -422,7 +423,7 @@ a component:
To browse a component details, perform the following steps: To browse a component details, perform the following steps:
#. In OpenStack dashboard, navigate to #. In OpenStack dashboard, navigate to
:menuselection:`Murano > Application Catalog > Environments`. :menuselection:`Applications > Catalog > Environments`.
#. Click the name of the required environment. #. Click the name of the required environment.
@ -447,7 +448,7 @@ an elastic diagram showing the relationship between a component and the
infrastructure it runs on. To view the topology: infrastructure it runs on. To view the topology:
#. In OpenStack dashboard, navigate to #. In OpenStack dashboard, navigate to
:menuselection:`Murano > Application Catalog > Environments`. :menuselection:`Applications > Catalog > Environments`.
#. Click the name of the necessary environment. #. Click the name of the necessary environment.
@ -501,8 +502,8 @@ To get detailed information on a deployment, use:
To see the log of a particular deployment, proceed with the steps To see the log of a particular deployment, proceed with the steps
below: below:
#. In OpenStack dashboard, navigate to :menuselection:`Murano > Application #. In OpenStack dashboard, navigate to :menuselection:`Applications > Catalog >
Catalog > Environments`. Environments`.
#. Click the name of the required environment. #. Click the name of the required environment.
@ -522,8 +523,8 @@ below:
To see the latest deployment log, proceed with the steps below: To see the latest deployment log, proceed with the steps below:
#. In OpenStack dashboard, navigate to :menuselection:`Murano > Application #. In OpenStack dashboard, navigate to :menuselection:`Applications > Catalog >
Catalog > Environments`. Environments`.
#. Click the name of the required environment. #. Click the name of the required environment.
@ -536,8 +537,8 @@ To see the latest deployment log, proceed with the steps below:
To see the logs of a particular component of an environment, proceed with the To see the logs of a particular component of an environment, proceed with the
steps below: steps below:
#. In OpenStack dashboard, navigate to :menuselection:`Murano > Application #. In OpenStack dashboard, navigate to :menuselection:`Applications > Catalog >
Catalog > Environments`. Environments`.
#. Click the name of the required environment. #. Click the name of the required environment.
@ -554,8 +555,8 @@ Delete an application
To delete an application that belongs to the environment: To delete an application that belongs to the environment:
#. In OpenStack dashboard, navigate to :menuselection:`Murano > #. In OpenStack dashboard, navigate to :menuselection:`Applications >
Application Catalog > Environments`. Catalog > Environments`.
#. Click on the name of the environment you want to delete an #. Click on the name of the environment you want to delete an
application from. application from.

View File

@ -24,7 +24,7 @@ Create an environment
To create an environment, perform the following steps: To create an environment, perform the following steps:
#. In OpenStack dashboard, navigate to Murano > Application Catalog > Environments. #. In OpenStack dashboard, navigate to Applications > Catalog > Environments.
#. On the :guilabel:`Environments` page, click the :guilabel:`Add New` button. #. On the :guilabel:`Environments` page, click the :guilabel:`Add New` button.
@ -51,7 +51,7 @@ Edit an environment
You can edit the name of an environment. For this, perform the following steps: You can edit the name of an environment. For this, perform the following steps:
#. In OpenStack dashboard, navigate to Murano > Application Catalog > Environments. #. In OpenStack dashboard, navigate to Applications > Catalog > Environments.
#. Position your mouse pointer over the environment name and click the #. Position your mouse pointer over the environment name and click the
appeared pencil icon. appeared pencil icon.
@ -67,7 +67,7 @@ This section provides a general overview of an environment, its structure,
possible statuses, and actions. An environment groups applications together. possible statuses, and actions. An environment groups applications together.
An application that is added to an environment is called a component. An application that is added to an environment is called a component.
To see an environment status, navigate to :menuselection:`Murano > Application Catalog > Environments`. To see an environment status, navigate to :menuselection:`Applications > Catalog > Environments`.
Environments may have one of the following statuses: Environments may have one of the following statuses:
* **Ready to configure**. When the environment is new and contains no * **Ready to configure**. When the environment is new and contains no

View File

@ -20,7 +20,7 @@ To upload an application to the catalog:
#. Log in to the OpenStack dashboard. #. Log in to the OpenStack dashboard.
#. Navigate to :menuselection:`Murano > Manage > Packages`. #. Navigate to :menuselection:`Applications > Manage > Packages`.
#. Click on the :guilabel:`Import Package` button: #. Click on the :guilabel:`Import Package` button:
@ -56,8 +56,8 @@ To upload an application to the catalog:
:width: 600 px :width: 600 px
:alt: Import Package dialog 3 :alt: Import Package dialog 3
#. Now your application is available from :menuselection:`Murano > #. Now your application is available from :menuselection:`Applications >
Application Catalog > Applications` page. Catalog > Browse` page.
Deploy an application Deploy an application
@ -68,7 +68,7 @@ and deploy the environment:
#. Log in to the OpenStack dashboard. #. Log in to the OpenStack dashboard.
#. Navigate to :menuselection:`Murano > Application Catalog > Applications`. #. Navigate to :menuselection:`Applications > Catalog > Browse`.
#. Click on the :guilabel:`Quick Deploy` button from the required application #. Click on the :guilabel:`Quick Deploy` button from the required application
from the list. Lets deploy Apache HTTP Server, for example: from the list. Lets deploy Apache HTTP Server, for example:
@ -91,7 +91,7 @@ and deploy the environment:
:alt: Configure Application dialog 2 :alt: Configure Application dialog 2
#. Now the Apache HTTP Server application is successfully added to the newly #. Now the Apache HTTP Server application is successfully added to the newly
created ``quick-env-1`` environment. created ``quick-env-4`` environment.
Click the :guilabel:`Deploy This Environment` button Click the :guilabel:`Deploy This Environment` button
to start the deployment: to start the deployment:
@ -102,7 +102,7 @@ and deploy the environment:
It may take some time for the environment to deploy. Wait until the status It may take some time for the environment to deploy. Wait until the status
is changed from ``Deploying`` to ``Ready``. is changed from ``Deploying`` to ``Ready``.
#. Navigate to `Murano > Application Catalog > Environments` to view the #. Navigate to `Applications > Catalog > Environments` to view the
details. details.
@ -113,7 +113,7 @@ To delete an application that belongs to the environment:
#. Log in to the OpenStack dashboard. #. Log in to the OpenStack dashboard.
#. Navigate to :menuselection:`Murano > Application Catalog > Environments`. #. Navigate to :menuselection:`Applications > Catalog > Environments`.
#. Click on the name of the environment to view its details, which include #. Click on the name of the environment to view its details, which include
components, topology, and deployment history. components, topology, and deployment history.

View File

@ -74,7 +74,7 @@ where:
.. note:: .. note::
Existing images could be marked in a simple way in the horizon UI with the murano dashboard installed. Existing images could be marked in a simple way in the horizon UI with the murano dashboard installed.
Navigate to *Murano -> Manage -> Images -> Mark Image* and fill up a form: Navigate to *Applications -> Manage -> Images -> Mark Image* and fill up a form:
* **Image** - ws-2012-std * **Image** - ws-2012-std
* **Title** - My Prepared Image * **Title** - My Prepared Image