MasterScope Virtual DataCenter Automation Standard ... · • OpenStack Orchestration(heat-api) - Component for accepting a stack creation or deletion request from the management

MasterScope Virtual DataCenterAutomation Standard Edition

Topology TemplateOrchestrator Option

User's Guide

1 EditionMarch, 2018

NEC Corporation

DisclaimerThe copyrighted information noted in this document shall belong to NEC Corporation.

Copying or revising this document, in whole or in part, is strictly prohibited without thepermission of NEC Corporation.

This document may be changed without prior notice.

NEC Corporation shall not be liable for any technical or editing errors or omissions in thisdocument.

NEC Corporation shall not be liable for the accuracy, usability, or certainty of information notedin this document.

Copyright information• SigmaSystemCenter and MasterScope are registered trademarks of NEC Corporation.

• Microsoft, Windows, Windows logo, Windows Server, Internet Explorer, and SQL Server aretrademarks or registered trademarks of Microsoft Corporation in the United States of Americaand other countries.

• Linux is a trademark or registered trademark of Linus Torvalds in the United States of Americaand other countries.

• Red Hat is a trademark or registered trademark of Red Hat, Inc. in the United States and othercountries.

• Intel and Itanium are trademarks or registered trademarks of Intel Corporation in the UnitedStates of America and other countries.

• Apache, Apache Tomcat, and Tomcat are trademarks or registered trademarks of ApacheSoftware Foundation.

• Firefox is a registered trademark or trademark of Mozilla Foundation.

• Google Chrome is a registered trademark or trademark of Google Inc.

• The OpenStack Word Mark and the OpenStack logos are registered trademarks or trademarks ofthe OpenStack Foundation in the United States of America and other countries.

• MySQL is a registered trademark of Oracle Corporation and/or its affiliates in the United Statesof Amerida and other countries.

Other system names, company names, and product names in this document are trademarks orregistered trademarks of their respective companies.

Note that ® mark and the ™ mark are not indicated in this document.

Notes on exporting this productIf this product (including its software) is subject to regulation under the Foreign Exchange andForeign Trade Law, it will be necessary to follow the procedures required by this law when exportingthis product, such as obtaining an export license from the Japanese Government. If you requiredocuments from NEC in order to obtain an export license, please contact the dealer where youpurchased your MasterScope product, or your local NEC sales office.

i

PrefaceTarget readers and purpose

This document is intended for system administrators who install the stack management server,configure the settings, and operate and maintain the system and describes each method.

Overview of the documentThis document describes the procedure for installing the stack management server, the procedure formaking the settings to make after the installation, the uninstallation procedure, the method of addingand changing settings during operation, and the method of writing a topology template.

• For how to check the system requirements for the stack management server, see "Chapter1. Operating Environments (page 1)".

• For how to install the stack management server, see "Chapter 2. Installation (page 6)".

• For how to make the settings to make after the installation and before starting to operate thestack management server, see "Chapter 3. Before Starting Operation (page 28)".

Before making the settings for "Chapter 3. Before Starting Operation (page 28)", you must setthe Virtual DataCenter Automation Standard Edition Portal (referred to as the vDCA SE Portalin the remainder of this document).

For an explanation of the procedure for setting the vDCA SE Portal, see Part 3, Before StartingOperation in Virtual DataCenter Automation Standard Edition Portal User Manual (ResourceManagement) Topology Template Orchestrator Option.

• For how to check the backup policy and procedure of the stack management server, see"Chapter 4. Backing up and Restoring a Database (page 38)".

• For how to uninstall the stack management server, see "Chapter 5. Uninstallation (page 40)".

• For how to write a topology template, which is supplied to tenants by the system administrator,see "Appendix B. Topology Template Format (page 58)".

Notation rules of this documentThis document describes precautions, important items, and related information as follows.

NoteIndicates precautions, warnings, and supplementary notes for the function, operation, and setting.

Notation rulesIn addition, the following notation rules are applied in this document.

Notation How to use Example

Arial bold Indicates the items to be displayed on thescreens (text boxes, check boxes, etc.)

Enter the machine name in theMachine name text box.All check box

" " Doublequotation marks

Indicates a window name or referencemanual

"Setting" window"Installation Guide"

ii

Notation How to use Example

[ ] in a commandline

Indicates that the specification of thevalue in [ ] can be omitted.

add [/a] Gr1

Monospace font(courier new)

Indicates the outputs from the commandline or system (messages, prompts, andothers)

Run the following command:replace Gr1

Italicizedmonospace font(courier new)

Indicates the items to be replaced with avalid value and input by users.When a space is included in the value,enclose the value in " ".

add GroupNameInstallPath="Install Path"

iii

ContentsChapter 1. Operating Environments.......................................................................................... 1

1.1 Component configuration......................................................................................................1

1.2 Hardware requirements .........................................................................................................3

1.3 Software requirements ..........................................................................................................4

Chapter 2. Installation................................................................................................................. 62.1 Installing the software to be prepared in advance ..................................................................9

2.1.1 Enabling the OpenStack repository ...........................................................................102.1.2 Installing and initializing MySQL .............................................................................10

2.1.2.1 Installing MySQL............................................................................................102.1.2.2 Initializing MySQL .........................................................................................112.1.2.3 Creating databases...........................................................................................11

2.1.3 Installing OpenStack and RabbitMQ .........................................................................132.1.4 Installing OpenStack and RabbitMQ by using the assisting script .............................14

2.1.4.1 Setting the parameter file.................................................................................142.1.4.2 Executing the assisting script...........................................................................17

2.2 Installing SSC Resource Plug-in .........................................................................................192.2.1 Installing dependent libraries.....................................................................................192.2.2 Installing SSC Resource Plug-in ...............................................................................202.2.3 Creating and placing a message catalog file ..............................................................202.2.4 Creating the directories for configuration files ..........................................................21

2.3 Settings required for SSL communication ...........................................................................212.3.1 Preparation................................................................................................................222.3.2 Setting the SSL of OpenStack Identity(keystone)......................................................222.3.3 Setting the SSL of OpenStack Orchestration(heat-api) ..............................................26

Chapter 3. Before Starting Operation...................................................................................... 283.1 Deploying the configuration files for SSC Resource Plug-in ...............................................28

3.2 Setting the resource management function ..........................................................................293.2.1 Settings for connecting to SigmaSystemCenter .........................................................293.2.2 Management network settings ...................................................................................303.2.3 Network setting method ............................................................................................31

3.3 Settings to use the monitoring function ...............................................................................323.3.1 Settings for connecting to MasterScope SystemManager G.......................................323.3.2 Setting the path of the executable file of the monitoring agent ..................................34

3.4 OpenStack Orchestration settings........................................................................................353.4.1 Setting the upper limit on the number of stacks .........................................................353.4.2 Setting the timeout for the response time of RabbitMQ.............................................363.4.3 Setting the command for deleting stack information..................................................363.4.4 Setting a validity period for the authentication token of OpenStack Identity(keystone) .

.....................................................................................................................................37

Chapter 4. Backing up and Restoring a Database .................................................................. 38

iv

4.1 Backing up a database .........................................................................................................384.1.1 Backing up a database using MySQL........................................................................38

4.2 Restoring a database............................................................................................................394.2.1 Restoring a database using MySQL...........................................................................39

Chapter 5. Uninstallation .......................................................................................................... 405.1 Uninstalling SSC Resource Plug-in.....................................................................................40

5.2 Uninstalling the dependent libraries ....................................................................................40

5.3 Uninstalling OpenStack and RabbitMQ ..............................................................................41

5.4 Uninstalling MySQL...........................................................................................................41

Chapter 6. Notes and Restrictions ............................................................................................ 426.1 Notes...................................................................................................................................42

6.1.1 Notes on the operation of the stack management server ............................................426.1.2 Notes on recovery measures ......................................................................................426.1.3 Notes on vDCA SE Portal .........................................................................................426.1.4 Notes on the SSC Resource Plug-in configuration file ..............................................426.1.5 Notes on the resource management function .............................................................436.1.6 Notes on the monitoring settings ...............................................................................436.1.7 Notes on using network resources .............................................................................43

6.2 Restrictions .........................................................................................................................446.2.1 Restrictions on the SSC Resource Plug-in configuration file .....................................446.2.2 Restrictions on using network resources....................................................................446.2.3 Restrictions on using server resources .......................................................................446.2.4 Restrictions on vDCA SE Portal................................................................................44

Appendix A. SSC Resource Plug-In Configuration File......................................................... 46A.1 Operation configuration file ...............................................................................................46

A.1.1 Settings for connecting to SigmaSystemCenter and MasterScope SystemManager G........................................................................................................................................47

A.1.2 Network settings.......................................................................................................48A.1.2.1 Management network settings ........................................................................48A.1.2.2 IP range settings of the network......................................................................49A.1.2.3 Port group settings of the network ..................................................................49

A.1.3 Monitoring linkage settings ......................................................................................50A.1.4 Default value settings ...............................................................................................51

A.1.4.1 Default values of the flavor (ssc.flavor.<flavor ID>) .....................................51A.1.4.2 Default values of the system disk profile (ssc.diskProfile.system.<disk profile

ID>) .....................................................................................................................52A.1.4.3 Default values of the disk profile (ssc.diskProfile.ext.<disk profile ID>) .......52A.1.4.4 Default values of the host profile....................................................................53A.1.4.5 Default values of the machine profile .............................................................54

A.1.5 Setting the interval to check whether resource creation or deletion is complete ........54

A.2 Parameter configuration file ...............................................................................................54A.2.1 Flavors .....................................................................................................................55A.2.2 Images......................................................................................................................56A.2.3 Disk profiles.............................................................................................................56

v

A.2.3.1 System disk profile.........................................................................................56A.2.3.2 Extended disk profile......................................................................................57

Appendix B. Topology Template Format ................................................................................. 58B.1 What is a topology template?..............................................................................................58

B.2 Topology template example................................................................................................58

B.3 Topology template structure ...............................................................................................60B.3.1 parameters section ....................................................................................................61

B.3.1.1 Data structure of the parameters section..........................................................61B.3.1.2 Parameter constraints......................................................................................62

B.3.2 resource section ........................................................................................................64B.3.2.1 Data structure of the resource section .............................................................64B.3.2.2 Resource types................................................................................................65

B.3.3 outputs section..........................................................................................................74B.3.3.1 Data structure of the outputs section ...............................................................74

B.4 Intrinsic functions...............................................................................................................74B.4.1 get_attr .....................................................................................................................75B.4.2 get_param.................................................................................................................76B.4.3 get_resource .............................................................................................................76B.4.4 list_join ....................................................................................................................77B.4.5 str_replace ................................................................................................................77B.4.6 repeat........................................................................................................................77B.4.7 digest ........................................................................................................................78B.4.8 str_split.....................................................................................................................78B.4.9 map_merge...............................................................................................................79B.4.10 Ref..........................................................................................................................79B.4.11 Fn::Base64..............................................................................................................79B.4.12 Fn::Join ..................................................................................................................80B.4.13 Fn::Select ...............................................................................................................80B.4.14 Fn::Split..................................................................................................................80B.4.15 Fn::Replace ............................................................................................................81B.4.16 Fn::MemberListToMap...........................................................................................81

Appendix C. Dependent Libraries............................................................................................ 82C.1 Dependent libraries.............................................................................................................82

Glossary........................................................................................................................................ 96

vi

Chapter 1. Operating EnvironmentsThe operating environments of Virtual DataCenter Automation Standard Edition Topology TemplateOrchestrator Option are described below. Topology Template Orchestrator Option consists of thefollowing server groups.

• Management server

• Stack management server

For an overall picture of the Virtual DataCenter Automation Standard Edition, see 2.1.1 ServerConfiguration Diagram of Virtual DataCenter Automation Standard Edition in Virtual DataCenterAutomation Standard Edition Setup Guide.

1.1 Component configurationThis section shows the components installed on the management server and the stack managementserver and their relationships.

Figure 1-1 Component diagram

Each component to be installed on a stack management server is overviewed below.

• OpenStack Identity(keystone)

- Component for performing user authentication and issuing and authenticating tokens.

Chapter 1. Operating Environments

1

- Accepts a user authentication request from the management server (vDCA SE Portal), andissues a token and an endpoint (URL for accepting the request) for performing stackcreation and deletion.

- Stores information about the user and the endpoint to MySQL.

• OpenStack Orchestration(heat-api)

- Component for accepting a stack creation or deletion request from the management server(vDCA SE Portal).

- Performs a check with OpenStack Identity(keystone) to determine whether the tokenattached to the accepted stack creation or deletion request has been authenticated.

- Stores the accepted stack creation or deletion request to RabbitMQ to pass it to OpenStackOrchestration(heat-engine) that performs the requested operation.

• OpenStack Orchestration(heat-engine)

- Component that acquires the stack creation or deletion request stored to RabbitMQ toperform actual stack creation or deletion.

- Performs a check with OpenStack Identity(keystone) to determine whether the tokenattached to the acquired stack creation or deletion request has been authenticated.

- Performs stack creation or deletion in accordance with the acquired request and stores theresult to MySQL.

• SSC Resource Plug-in

- Component implemented as a plug-in for OpenStack Orchestration(heat-engine).

- Creation and deletion processing of an SSC server or network contained in a stack istransferred from OpenStack Orchestration(heat-engine).

- Performs Restful API for the management servers (SigmaSystemCenter and MasterScopeSystemManager G) to make the creation, deletion, or monitoring settings for a server or anetwork.

• RabbitMQ

- Component for mediating a stack creation or deletion request between OpenStackOrchestration(heat-api) and OpenStack Orchestration(heat-engine).

• MySQL

- Component for managing information about OpenStack Identity(keystone) and OpenStackOrchestration(heat-engine).

This document mainly describes the procedures for installing and uninstalling a stack managementserver in an all-in-one configuration, in which all the components are installed on a single server. Insome cases, however, DBMS (MySQL) and application (OpenStack and RabbitMQ) components areinstalled separately on different servers in a load distribution configuration to achieve scale-up of theapplication servers. Taking the possibility of such situations into account, the document also providessupplementary descriptions for specifying servers that require specific procedures to be performeddue to the components to be installed (or the components installed) on those servers. The followingshows a component configuration in a load distribution configuration.


2

Figure 1-2 Component diagram

The procedure for installing MySQL on a stack management server (DBMS server when a loaddistribution configuration is used) is described in "2.1.2 Installing and initializing MySQL (page10)".

The procedure for installing OpenStack Identity(keystone), OpenStack Orchestration(heat-api),OpenStack Orchestration(heat-engine), and RabbitMQ on a stack management server (applicationserver when a load distribution configuration is used) is described in "2.1.3 Installing OpenStackand RabbitMQ (page 13)".

The procedure for installing SSC Resource Plug-in on a stack management server (application serverwhen a load distribution configuration is used) is described in "2.2 Installing SSC Resource Plug-in(page 19)".

For a description of the procedure for installing the components to be placed on the managementserver, see Virtual DataCenter Automation Standard Edition Setup Guide.

1.2 Hardware requirementsThis section describes the hardware requirements for the stack management servers. For the hardwarerequirements for the management serve, see Virtual DataCenter Automation Standard Edition SetupGuide

The following table shows the hardware requirements (minimum requirements) for the stackmanagement server having an all-in-one configuration.

Table 1-1 Hardware requirements for the stack management server in an all-in-one configuration(Minimum)

Hardware name Spec

CPU x86-64 processor

Memory At least 1.5 GB

Hard disk At least 16 GB


3

The hardware requirements (minimum requirements) for installation on each server in a loaddistribution configuration are as follows.

Table 1-2 Hardware requirements for a DBMS server to which to install MySQL (Minimum)

Hardware name Spec


Memory At least 256 MB


Table 1-3 Hardware requirements for an application server to which to install OpenStack andRabbitMQ (Minimum)

Hardware name Spec


Memory At least 1280 MB


1.3 Software requirementsThis section describes the software requirements for the stack management server. For the softwarerequirements for the management server, see Virtual DataCenter Automation Standard Edition SetupGuide

The following table shows the software requirements for the stack management server having an all-in-one configuration.

Table 1-4 Software requirements for the stack management server in an all-in-one configuration(Minimum)

Component Software name

OS Red Hat Enterprise Linux 7.3

DBMS MySQL Standard Edition 5.6MySQL Standard Edition 5.7MySQL Enterprise Edition 5.6MySQL Enterprise Edition 5.7

Other software OpenStack Identity(keystone) 9.0.2

OpenStack Orchestration(heat-api) 6.0.0

OpenStack Orchestration(heat-engine) 6.0.0

RabbitMQ 3.6.2

The software requirements for installation on each server in a load distribution configuration are asfollows:

Table 1-5 Software requirements for a DBMS server to which to install MySQL (Minimum)



DBMS MySQL Standard Edition 5.6MySQL Standard Edition 5.7MySQL Enterprise Edition 5.6


4

Component Software nameMySQL Enterprise Edition 5.7

Table 1-6 Software requirements for an application server to which to install OpenStack andRabbitMQ (Minimum)



Other software OpenStack Identity(keystone) 9.0.2

OpenStack Orchestration(heat-api) 6.0.0

OpenStack Orchestration(heat-engine) 6.0.0

RabbitMQ 3.6.2


5

Chapter 2. InstallationThis chapter describes how to install the stack management server.

Before the installation of the stack management server, design the values required for the followingparameters.

The parameter setting values listed below are those for an all-in-one configuration. Change the valuesaccording to your environment. When a load distribution configuration is used, design the values inaccordance with "1.1 Component configuration (page 1)", bearing in mind that the components areto be installed on the server.

Table 2-1 Installation parameters for a stack management server

Parametername

Description Usage Setting value

IDENTITY_DBMS_HOST

Host name or IP address of the serveron which MySQL is to be installed

• Used as information whenOpenStack Identity(keystone)establishes a connection withMySQL.

192.168.1.1

IDENTITY_DBMS_PORT

Port number used by MySQL • Used as information whenOpenStack Identity(keystone)establishes a connection withMySQL.

3306

IDENTITY_DBMS_USER

User name of the user permitted toaccess the keystone databasemanaged by MySQL


keystone

IDENTITY_DBMS_PASS

Password of the user permitted toaccess the keystone databasemanaged by MySQL


keystone(For MySQL5.7.8 or later, it isnecessary to set acomplexpasswordcontainingalphanumericcharacters andsymbols.)

IDENTITY_HOST

Host name or IP address of the serveron which OpenStackIdentity(keystone) is to be installed

• Used as information when themanagement server (vDCA SEPortal) establishes a connectionwith OpenStackIdentity(keystone).

• Used as information whenOpenStack Orchestration(heat-api) and OpenStackOrchestration(heat-engine)establish a connection withOpenStack Identity(keystone).

192.168.1.1

IDENTITY_ADMIN_PORT

Management port number used byOpenStack Identity(keystone)

• Used as information when themanagement server (vDCA SEPortal) establishes a connection

35357

Chapter 2. Installation

6

Parametername


with OpenStackIdentity(keystone).


IDENTITY_PUBLIC_PORT

Public port number used byOpenStack Identity(keystone)



5000

PORTAL_PROJECT_USER

User name of the user to beregistered in OpenStackIdentity(keystone)


portal

PORTAL_PROJECT_PASS

Password of the user to be registeredin OpenStack Identity(keystone)


portal

ORCHESTRATION_DBMS_HOST

Host name or IP address of the serveron which MySQL is to be installed

• Used as information whenOpenStack Orchestration(heat-engine)establishes a connectionwith MySQL.

192.168.1.1

ORCHESTRATION_DBMS_PORT

Port number used by MySQL • Used as information whenOpenStack Orchestration(heat-engine) establishes aconnection with MySQL.

3306

ORCHESTRATION_DBMS_USER

User name of the user permitted toaccess the heat database managed byMySQL

• Used as information whenOpenStack Orchestration(heat-engine) establishes aconnection with MySQL.

heat

ORCHESTRATION_DBMS_PASS

Password of the user permitted toaccess the heat database managed byMySQL


heat(For MySQL5.7.8 or later, it isnecessary to set acomplexpasswordcontainingalphanumericcharacters andsymbols.)

ORCHESTRATION_HOST

Host name or IP address of the serveron which OpenStack

• Used as information when themanagement server (vDCA SE

192.168.1.1


7

Parametername


Orchestration(heat-api) is to beinstalled

Portal) establishes a connectionwith OpenStackOrchestration(heat-api).

ORCHESTRATION_PORT

Port number used by OpenStackOrchestration(heat-api)

• Used as information when themanagement server (vDCA SEPortal) establishes a connectionwith OpenStackOrchestration(heat-api).

35357

MESSAGE_QUEUE_HOSTS

Host name or IP address of the serveron which RabbitMQ is to be installed

• Used as information whenOpenStack Orchestration(heat-api) establishes a connectionwith RabbitMQ.

• Used as information whenOpenStack Orchestration(heat-engine) establishes aconnection with RabbitMQ.

192.168.1.1

MESSAGE_QUEUE_PORT

Port number used by RabbitMQ • Used as information whenOpenStack Orchestration(heat-api) establishes a connectionwith RabbitMQ.


5672

MESSAGE_QUEUE_USER

User name of the user to beregistered in RabbitMQ



tto

MESSAGE_QUEUE_PASS

Password of the user to be registeredin RabbitMQ



tto

The installation procedure is as follows:

1. Install the software to be prepared in advance.

a. Enable the OpenStack repository.

b. Install and initialize MySQL.

c. Install OpenStack and RabbitMQ.

2. Install SSC Resource Plug-in.

When an all-in-one configuration is used, each of the above procedures is performed on the singleserver. When a load distribution configuration is used, in contrast, it is necessary to perform theprocedures while considering which server is subject to each of the procedures.


8

Before starting the work, see the following for details about the procedures to be performed on eachserver.

Table 2-2 Procedures to be performed when components are installed separately on differentservers

Procedure Implementation on the DBMSserver on which the MySQL

component is installed

Implementation on theapplication server on whichOpenStack and RabbitMQcomponents are installed

Enabling the OpenStack repository × ○

Installing and initializing MySQL ○ ×

Installing OpenStack and RabbitMQ × ○

Installing SSC Resource Plug-in × ○

Legend: ○: Necessary to perform; ×: Unnecessary to perform

NoteAll the work described in this chapter must be done under the account with Administrator authority. Executethe commands as the root user or by using the sudo command.

2.1 Installing the software to be prepared inadvance

Installing SSC Resource Plug-in requires that the following software be installed in advance.

• MySQL




• RabbitMQ

Referring to the following OpenStack document, install the software of the version mentioned in"Software requirements".

https://docs.openstack.org/mitaka/ja/install-guide-rdo/

This product offers a script for assisting in installing OpenStack and RabbitMQ.

This section describes the procedure for installation using the assisting script. To perform installationby using the assisting script, check the software licenses of OpenStack and RabbitMQ first and thenexecute the assisting script.

However, the information on the software installation procedure using the assisting script was thelatest at the time of product release, but may be out of date. If the construction cannot be achieved inaccordance with the procedure, see the above-mentioned OpenStack document, and install thesoftware of the version described in "Software requirements".

Before performing the procedure in this section, you must subscribe to Red Hat Enterprise Linux. Ifyou have not subscribed, subscribe to Red Hat Enterprise Linux, referring to the Red Hat EnterpriseLinux manual before performing the procedures in the subsequent sections.


9

2.1.1 Enabling the OpenStack repositoryOn a stack management server, enable the OpenStack repository and update the package. When aload distribution configuration is used, perform the procedure on the application server on which theOpenStack and RabbitMQ components are to be installed.

• Execute the following command to enable the OpenStack repository.

$ yum install https://repos.fedorapeople.org/repos/openstack/EOL/openstack-mitaka/rdo-release-mitaka-6.noarch.rpm

• Change the referent of the repository to the Vault repository. Open /etc/yum.repos.d/rdo-release.repo and change the setting as follows:

- Before change

[openstack-mitaka]name=OpenStack Mitaka Repositorybaseurl=http://mirror.centos.org/centos/7/cloud/$basearch/openstack-mitaka/gpgcheck=1enabled=1gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Cloud

- After change

[openstack-mitaka]name=OpenStack Mitaka Repositorybaseurl=http://vault.centos.org/7.3.1611/cloud/$basearch/openstack-mitaka/gpgcheck=1enabled=1gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Cloud

• Execute the following command to enable the option repository.

$ yum install yum-utils$ yum-config-manager --enable rhel-7-server-optional-rpms

• Execute the following command to update the installation information.

$ yum upgrade

NoteTo use the yum-config-manager command, you must install the yum management tool (yum-utils).

2.1.2 Installing and initializing MySQLInstall and initialize MySQL. When a load distribution configuration is used, perform this procedureon the DBMS server on which the MySQL component is to be installed.

2.1.2.1 Installing MySQLInstall MySQL. After purchasing MySQL, perform installation by referring to the manual providedby Oracle Corporation.

Depending on the version of the OS on which to perform installation, MariaDB and MariaDB-relatedpackages may have been installed as standard. Before installation, check whether MariaDB andMariaDB-related packages are installed and delete these packages by running the followingcommands.

• Command for checking whether MariaDB and the related packages are installed


10

yum list installed | grep mariadb

• Command for deleting the MariaDB-related packages

yum remove mariadb*

• If you deleted MariaDB and MariaDB-related packages, run the following command to deletethe data directory.

rm -rf /var/lib/mysql/

2.1.2.2 Initializing MySQLCreate the configuration file for MySQL (/etc/my.cnf.d/openstack.cnf) and describe the followingitems.

[mysqld]bind-address = IDENTITY_DBMS_HOSTdefault-storage-engine = innodbinnodb_file_per_tablemax_connections = 4096collation-server = utf8_general_cicharacter-set-server = utf8

For bind-address in the [mysqld] section, set the host name or IP address of the server on whichMySQL is installed.

Setting example

[mysqld]bind-address = 192.168.1.1default-storage-engine = innodbinnodb_file_per_tablemax_connections = 4096collation-server = utf8_general_cicharacter-set-server = utf8

Execute the following command to check that the MySQL service has started.

$ systemctl status mysqld.service

If the MySQL service is not enabled or has not started, execute the following command.

$ systemctl enable mysqld.service$ systemctl start mysqld.service

Execute the mysql_secure_installation script and set a password appropriate for the root account ofthe database.

* Not required if you have already performed this.

$ mysql_secure_installation

2.1.2.3 Creating databasesCreate the databases for use with OpenStack Identity(keystone) and OpenStack Orchestration(heat-engine), and register their users.


11

Perform this procedure according to the following parameters of "Table 2-1 Installation parametersfor a stack management server (page 6)".

Table 2-3 Installation parameters for a stack management server (only necessary parameters)

Parametername


IDENTITY_DBMS_USER

User name of the user permitted toaccess the keystone databasemanaged by MySQL


keystone

IDENTITY_DBMS_PASS

Password of the user permitted toaccess the keystone databasemanaged by MySQL


keystone

ORCHESTRATION_DBMS_USER

User name of the user permitted toaccess the heat database managed byMySQL


heat

ORCHESTRATION_DBMS_PASS

Password of the user permitted toaccess the heat database managed byMySQL


heat

Log in to the server and establish a connection with MySQL.

$ mysql -u root -p

OpenStack Identity(keystone) database

• Create a database for OpenStack Identity(keystone). Create the database with the namekeystone.

mysql> CREATE DATABASE keystone;

• Register the user permitted to access the keystone database.

mysql> GRANT ALL PRIVILEGES ON IDENTITY_DBMS_USER.* TO 'keystone'@'localhost' IDENTIFIED BY 'IDENTITY_DBMS_PASS';mysql> GRANT ALL PRIVILEGES ON IDENTITY_DBMS_USER.* TO 'keystone'@'%' IDENTIFIED BY 'IDENTITY_DBMS_PASS';

OpenStack Orchestration(heat-engine) database

• Create a database for OpenStack Orchestration(heat-engine). Create the database with the nameheat.

mysql> CREATE DATABASE heat;

• Register the user permitted to access the heat database.

mysql> GRANT ALL PRIVILEGES ON ORCHESTRATION_DBMS_USER.* TO 'heat'@'localhost' IDENTIFIED BY 'ORCHESTRATION_DBMS_PASS';mysql> GRANT ALL PRIVILEGES ON ORCHESTRATION_DBMS_USER.* TO 'heat'@'%' IDENTIFIED BY 'ORCHESTRATION_DBMS_PASS';

Close the connection with MySQL.


12

mysql> exit

Tip• When it is necessary to check whether the databases have been registered correctly, execute the

following command.

show databases;

The following shows an example of the execution result.

mysql> show databases;+--------------------+| Database |+--------------------+| information_schema || heat || keystone || mysql || performance_schema || sys |+--------------------+6 rows in set (0.00 sec)

When they are registered correctly, "keystone" and "heat" are indicated on the database list.• When it is necessary to check whether the users have been registered correctly, execute the following

command.

SELECT Host, User FROM mysql.user;

The following shows an example of the execution result.

mysql> SELECT Host, User FROM mysql.user;+-----------------+-----------+| Host | User |+-----------------+-----------+| % | heat || % | keystone || localhost | heat || localhost | keystone || localhost | mysql.sys || localhost | root |+-----------------+-----------+8 rows in set (0.00 sec)

When they are registered correctly, "IDENTITY_DBMS_USER" and"ORCHESTRATION_DBMS_USER" are indicated on the user list.

• If they are not registered correctly, delete the databases and the users and perform the procedure again.

delete from mysql.user where User = 'IDENTITY_DBMS_USER';delete from mysql.user where User = 'ORCHESTRATION_DBMS_USER';drop database keystone;drop database heat;

2.1.3 Installing OpenStack and RabbitMQOn the stack management server, install the following three components, contained in OpenStack, aswell as RabbitMQ. When a load distribution configuration is used, perform the procedure on theapplication server on which the OpenStack and RabbitMQ components are to be installed.


13




2.1.4 Installing OpenStack and RabbitMQ by using theassisting script

This section describes how to install the components contained in OpenStack and RabbitMQ on astack management server by using the assisting script. When a load distribution configuration is used,perform the procedure on the application server on which the OpenStack and RabbitMQ componentsare to be installed.

In the assisting script, the components contained in the OpenStack software and RabbitMQ areindicated as follows:

Table 2-4 Indications of software on the assisting script

Software name Indication on the assisting script

OpenStack Identity(keystone) Identity API Service

OpenStack Orchestration(heat-api) Orchestration API Service

OpenStack Orchestration(heat-engine) Orchestration Engine Service

RabbitMQ Message Queue

2.1.4.1 Setting the parameter fileBefore installing OpenStack and RabbitMQ by using the assisting script, include the parameters inthe parameter file such that they are passed to the script. The parameter file is a file used to definewhether OpenStack and RabbitMQ, to be installed by the assisting script, can be installed, as well astheir settings.

Copy the <Installation DVD>\vDCA_TTO_option\conf\parameter file to any directory on the stackmanagement server and change the values of the following setting items.

In the parameter file, include one definition on one line, in the format of "keyword=value". You caninsert a comment in the middle, as needed. In this case, include a # at the beginning of the line. Theline feed code must be LF and the character code must be UTF-8.

The setting items to be edited are listed below.

Table 2-5 Setting items in the parameter file

Setting item Description Setting value

IDENTITY_DBMS_HOST Host name or IP address of the serveron which MySQL is installed

Include the setting value ofIDENTITY_DBMS_HOST shownin "Table 2-1 Installationparameters for a stack managementserver (page 6)".

IDENTITY_DBMS_PORT Port number used by MySQL Include the setting value ofIDENTITY_DBMS_PORT shown in"Table 2-1 Installation parametersfor a stack management server (page6)".

IDENTITY_DBMS_USER User name of the user allowed toaccess the keystone database createdby MySQL

Include the setting value ofIDENTITY_DBMS_USER shown in"Table 2-1 Installation parameters


14

Setting item Description Setting valuefor a stack management server (page6)".

IDENTITY_DBMS_PASS Password of the user allowed toaccess the keystone database createdby MySQL

Include the setting value ofIDENTITY_DBMS_PASS shown in"Table 2-1 Installation parametersfor a stack management server (page6)".

IDENTITY_HOST Host name or IP address of the serveron which OpenStackIdentity(keystone) is to be installed

Include the setting value ofIDENTITY_HOST shown in "Table2-1 Installation parameters for astack management server (page 6)".

IDENTITY_ADMIN_PORT Management port number used byOpenStack Identity(keystone)

Include the setting value ofIDENTITY_ADMIN_PORT shownin "Table 2-1 Installationparameters for a stack managementserver (page 6)".

IDENTITY_PUBLIC_PORT Public port number used byOpenStack Identity(keystone)

Include the setting value ofIDENTITY_PUBLIC_PORT shownin "Table 2-1 Installationparameters for a stack managementserver (page 6)".

PORTAL_PROJECT_USER User name of the user to beregistered in OpenStackIdentity(keystone)

Include the setting value ofPORTAL_PROJECT_USER shownin "Table 2-1 Installationparameters for a stack managementserver (page 6)".

PORTAL_PROJECT_PASS Password of the user to be registeredin OpenStack Identity(keystone)

Include the setting value ofPORTAL_PROJECT_PASS shownin "Table 2-1 Installationparameters for a stack managementserver (page 6)".

MESSAGE_QUEUE_HOSTS Host name or IP address of the serveron which RabbitMQ is to be installed

Include the setting value ofMESSAGE_QUEUE_HOSTSshown in "Table 2-1 Installationparameters for a stack managementserver (page 6)".

MESSAGE_QUEUE_PORT Port number used by RabbitMQ Include the setting value ofMESSAGE_QUEUE_PORT shownin "Table 2-1 Installationparameters for a stack managementserver (page 6)".

MESSAGE_QUEUE_USER User name of the user to beregistered in RabbitMQ

Include the setting value ofMESSAGE_QUEUE_USER shownin "Table 2-1 Installationparameters for a stack managementserver (page 6)".

MESSAGE_QUEUE_PASS Password of the user to be registeredin RabbitMQ

Include the setting value ofMESSAGE_QUEUE_PASS shownin "Table 2-1 Installationparameters for a stack managementserver (page 6)".

ORCHESTRATION_HOST Host name or IP address of the serveron which OpenStack

Include the setting value ofORCHESTRATION_HOST shown


15

Setting item Description Setting valueOrchestration(heat-api) is to beinstalled

in "Table 2-1 Installationparameters for a stack managementserver (page 6)".

ORCHESTRATION_PORT Port number used by OpenStackOrchestration(heat-api)

Include the setting value ofORCHESTRATION_PORT shownin "Table 2-1 Installationparameters for a stack managementserver (page 6)".

ORCHESTRATION_DBMS_HOST Host name or IP address of the serveron which MySQL is installed

Include the setting value ofORCHESTRATION_DBMS_HOSTshown in "Table 2-1 Installationparameters for a stack managementserver (page 6)".

ORCHESTRATION_DBMS_PORT Port number used by MySQL Include the setting value ofORCHESTRATION_DBMS_PORTshown in "Table 2-1 Installationparameters for a stack managementserver (page 6)".

ORCHESTRATION_DBMS_USER User name of the user allowed toaccess the heat database created byMySQL

Include the setting value ofORCHESTRATION_DBMS_USERshown in "Table 2-1 Installationparameters for a stack managementserver (page 6)".

ORCHESTRATION_DBMS_PASS Password of the user allowed toaccess the heat database created byMySQL

Include the setting value ofORCHESTRATION_DBMS_PASSshown in "Table 2-1 Installationparameters for a stack managementserver (page 6)".

Setting example

# Identity APIIDENTITY_DBMS_HOST=192.168.1.1IDENTITY_DBMS_PORT=3306IDENTITY_DBMS_USER=keystoneIDENTITY_DBMS_PASS=keystoneIDENTITY_HOST=192.168.1.1IDENTITY_ADMIN_PORT=35357IDENTITY_PUBLIC_PORT=5000

... (Omitted) ...

PORTAL_PROJECT_USER=portalPORTAL_PROJECT_PASS=portal

# Message QueueMESSAGE_QUEUE_HOSTS=192.168.1.1MESSAGE_QUEUE_PORT=5672MESSAGE_QUEUE_USER=ttoMESSAGE_QUEUE_PASS=tto

# Orchestration APIORCHESTRATION_HOST=192.168.1.1ORCHESTRATION_PORT=8004


16

# Orchestration EngineORCHESTRATION_DBMS_HOST=192.168.1.1ORCHESTRATION_DBMS_PORT=3306ORCHESTRATION_DBMS_USER=heatORCHESTRATION_DBMS_PASS=heat

• Change the IP address or host name to a setting that can be accessed from the outside.

• For the IP address, you cannot set a loopback address.

• Set a host name that enables name resolution.

2.1.4.2 Executing the assisting scriptExecute the assisting script to install OpenStack and RabbitMQ.

The assisting script execution command is described below.

$ sh pre_install.sh [-f <parameter-file-path>] [-p]

Table 2-6 Arguments of the assisting script execution command

Argument Description

-f <parameter-file-path> Specify the path of the parameter file.* If no parameter file is specified, installation is performed with the defaultvalue of each parameter.[Optional]

-p Preview option* If the argument is specified, the software to install and parameters are sentto the standard output. Installation work is not executed.[Optional]

1. Before executing the assisting script, check the settings of the parameters by using the "-p"option (preview option).

$ sh <installation DVD>/vDCA_TTO_option/pre_install/pre_install.sh -f parameter-file-path -p

The settings of the parameters are sent to the standard output. Check that the items specified inthe parameter file are applied correctly.

Execution result examples

-------------Setup preview-------------

____________________________________________________________|1 [*] Identity API Service 1.0 ||2 [*] Message queue 1.0 ||3 [*] Orchestration API Service 1.0 ||4 [*] Orchestration Engine Service 1.0 || || || ||____________________________________________________________|

Identity API Service setup parameter


17

------------------------------------Identity DBMS host: 192.168.0.1Identity DBMS port: 3306Identity DBMS user name: keystoneIdentity DBMS user's password: ********Identity host: 192.168.0.1Identity admin port number: 35357Identity public port number: 5000Orchestration host: 192.168.0.1Orchestration port number: 8004Domain name: defaultService project user name: heatService project user's password: ********Admin project name: adminAdmin project user name: adminAdmin project user's password: ********Portal project name: portalPortal project user name: portalPortal project user's password: ********Heat domain user name: heat_domain_userHeat domain user's password: ********

Message Queue setup parameter-----------------------------Message queue port number: 5672Message queue user name: ttoMessage queue user's password: ********

Orchestration API Service setup parameter-----------------------------------------Identity host name: 192.168.0.1Identity admin port number: 35357Message queue hosts: 192.168.0.1Message queue port number: 5672Message queue user name: ttoMessage queue user's password: ********Domain name: defaultService project user name: heatService project user's password: ********

Orchestration Engine Service setup parameter--------------------------------------------Orchestration DBMS host: 192.168.0.1Orchestration DBMS port: 3306Orchestration DBMS user name: heatOrchestration DBMS user's password: ********Identity host name: 192.168.0.1Identity admin port number: 35357Message queue hosts: 192.168.0.1Message queue port number: 5672Message queue user name: ttoMessage queue user's password: ********Domain name: defaultService project user name: heatService project user's password: ********Heat domain user name: heat_domain_userHeat domain user's password: ********


18

2. Check that the settings of the parameters are free from problems, and execute the assistingscript with the following command.

$ sh <installation DVD>/vDCA_TTO_option/pre_install/pre_install.sh -f parameter-file-path

When the installation is complete, "Setup has been completed." is displayed.

If a message other than "Setup has been completed." is displayed, refer to the following tableto check the action to take for the displayed message. If message 5 or later is displayed, checkthe contents of the message output from the corresponding software and take action.

Table 2-7 Assisting script execution command output results

No. Message Description

1 Setup has been completed. Normal end

2 [parameter-file-path] is notfound.

The parameter file cannot be found. Check that the file specifiedwith the command exists.

3 At least select one component. No software component is selected. Check the settings in theparameter file.

4 [parameter-in-the-parameter-file] is invalid.

The parameter in the parameter file is a value outside the limits.Check the settings in the parameter file.

5 PreInstaller is aborted. The assisting script is interrupted. Check the contents of thestandard output.

6 [package-name-or-configuration file-name]installation or configuration isaborted.

Installing or setting the package failed. Check the contents ofthe standard output.

7 Failed to start [service-name]. Starting the service failed. Check the contents of the standardoutput.

8 Failed to start [host-name-or-IP-address-of-DBMS].

Logging in to the database failed. Check the contents of thestandard output.

9 Failed to regist [software-name] schema or regist initialdata.

Registering a database schema or registering initial data failed.Check the contents of the standard output.

2.2 Installing SSC Resource Plug-inInstall SSC Resource Plug-in on the stack management server. When a load distributionconfiguration is used, perform the procedure on the application server on which the OpenStack andRabbitMQ components are to be installed.

2.2.1 Installing dependent librariesInstall the libraries on which SSC Resource Plug-in depends. Dependent libraries are listed below.

Table 2-8 Dependent libraries to install

Dependent library Version

OpenStack Orchestration 6.0.0

dpath 1.4.0

eventlet 0.18.2 or later (excluding 0.18.3)


19

Dependent library Version

netaddr 0.7.12 or later (excluding 0.7.16)

oslo.concurrency 3.7.1 or later

oslo.log 1.14.0 or later

oslo.utils 3.5.0 or later

pytz 2013.6 or later

requestss 2.8.1 or later (excluding 2.9.0)

six 1.9.0 or later

For how to install OpenStack Orchestration, see "2.1.3 Installing OpenStack and RabbitMQ (page13)".

For the following libraries, this section does not contain the installation procedures because they arealso the dependent libraries of OpenStack Orchestration and are installed at the same time asinstalling OpenStack Orchestration.

• eventlet

• netaddr

• oslo.concurrency

• oslo.log

• oslo.utils

• pytz

• requests

• six

This section contains the procedure for installing the dpath library. Check the software license fordpath first and then install it with the following command.

$pip install dpath==1.4.0

2.2.2 Installing SSC Resource Plug-inRun the following command to install SSC Resource Plug-in.

$ pip install <under the installation DVD>vDCA_TTO_option/pkg/heat_masterscope_ssc-1.0.0-py2-none-any.whl

When the installation is complete, "Successfully installed" is displayed.

2.2.3 Creating and placing a message catalog fileCreate a message catalog file and place it in the prescribed directory. Before creating a messagecatalog file, run the following command to install the gettext package.

yum install gettext

1. Preparing the source code for a message catalog file

Create a message catalog file by merging together the source code installed on the stackmanagement server and the source code stored on the installation DVD. The directory in whichthe source code is placed is as follows.


20

• Path of the source code installed on the stack management server

/usr/lib/python2.7/site-packages/heat/locale/ja/LC_MESSAGES/heat.po

• Path of the TTO difference translation source file

<under the installation DVD>vDCA_TTO_option\conf\heat_ssc.po

2. Creating a message catalog file

Run the following command to create a message catalog file.

msgfmt -o heat.mo <path to the source code installed in the stack management server> <path to the TTO difference translation source file>

The heat.mo file is created in the command execution directory.

3. Placing the translation file

Move the translation file (heat.mo) to the following directory. If you already use heat in theJapanese environment, the file may already exist in the directory. In this case, it isrecommended to back up the original file.

• Directory

/usr/share/locale/ja/LC_MESSAGES/heat.mo

2.2.4 Creating the directories for configuration filesCreate the directories in which to place the operation configuration file (ssc_plugin.conf) and theparameter configuration file (ssc_parameter.conf) for the SSC Resource Plug-in.

Place the configuration files, with "3.1 Deploying the configuration files for SSC Resource Plug-in(page 28)".

1. Under the /usr/lib directory, create the heat directory. At the same time, change the owner.

$ mkdir /usr/lib/heat/$ chown heat:heat /usr/lib/heat/

2. Create the symbolic link to the plug-in directory for Heat.

$ cd /usr/lib/heat$ ln -s /usr/lib/python2.7/site-packages/heat_ssc .

3. Under <heat user's home directory>, create the .heat-ssc directory.

• Make sure that the owner of the directory is the heat user.

• By default, <heat user's home directory> is /var/lib/heat/.

$ mkdir /var/lib/heat/.heat-ssc$ chown heat:heat /var/lib/heat/.heat-ssc

2.3 Settings required for SSL communicationChange the protocol from http to https for the connection that is to be established from themanagement server (vDCA SE Portal) to a stack management server. When a load distribution


21

configuration is used, perform the procedure on the application server on which the OpenStackandRabbitMQ components are to be installed.

2.3.1 PreparationThe following files are necessary when the protocol of the communication from the managementserver (vDCA SE Portal) to OpenStack Identity(keystone) and OpenStack Orchestration(heat-api) isto be changed from http to https. Store the files in any folder on the server, and perform the proceduredescribed below.

• Certificate authority server certificate (referred to as cacert.pem in this section)

• Server certificate signed by a certificate authority (referred to as cert.pem in this section)

• Secret key for the decrypted server certificate (referred to as key.pem in this section)

2.3.2 Setting the SSL of OpenStack Identity(keystone)This section describes who to set the SSL of OpenStack Identity(keystone).



Parametername


IDENTITY_HOST

Host name or IP address of the serveron which OpenStackIdentity(keystone) is to be installed



192.168.1.1

IDENTITY_ADMIN_PORT

Management port number used byOpenStack Identity(keystone)



35357

IDENTITY_PUBLIC_PORT

Public port number used byOpenStack Identity(keystone)


• Used as information whenOpenStack Orchestration(heat-api) and OpenStackOrchestration(heat-engine)

5000


22

Parametername


establish a connection withOpenStack Identity(keystone).

1. Import the certificate authority server certificate.

a. Install a library for performing reliability verification on the server certificates.

$ pip install certifi

b. Acquire the path to the location of the import destination file of the certificate authorityserver certificate.

$ pythonPython 2.7.5 (default, Aug 2 2016, 04:20:16)[GCC 4.8.5 20150623 (Red Hat 4.8.5-4)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> import certifi>>> certifi.where()'/usr/lib/python2.7/site-packages/certifi/cacert.pem'>>> quit()

c. Import the certificate authority server certificate into the import destination file of thecertificate authority server certificate.

$ cat cacert.pem >> /usr/lib/python2.7/site-packages/certifi/cacert.pem

2. Copy the certificate authority server certificate, the server certificate signed by the certificateauthority, and the secret key for the decrypted server certificate to the configuration filedirectory of OpenStack Identity(keystone).

$ mkdir -p /etc/keystone/ssl/certs$ cp cacert.pem /etc/keystone/ssl/certs/$ cp cert.pem /etc/keystone/ssl/certs/signing_cert.pem$ cp key.pem /etc/keystone/ssl/certs/signing_key.pem$ chmod -R 700 /etc/keystone/ssl/certs

3. Change the protocol from http to https for the connection destination of OpenStackIdentity(keystone) registered in the database.

a. Assign an authentication token and the endpoint URL to the relevant environmentvariables.

• Execute the following command and make a note of the admin_token value.

$ cat /etc/keystone/keystone.conf | grep admin_token

• Assign the noted admin_token value to the OS_TOKEN environment variable.

$ export OS_TOKEN=admin_token value$ export OS_IDENTITY_API_VERSION=3$ export OS_URL=http://IP address of active stack management server:35357/v3

• A command execution example is shown below.


23

$ cat /etc/keystone/keystone.conf | grep admin_tokenadmin_token = 3b53d3bd3ce8942c878c# `None`, the value is ignored and the `admin_token` log in mechanism is# effectively disabled. To completely disable `admin_token` in production#admin_token = <None<$ export OS_TOKEN=3b53d3bd3ce8942c878c$ export OS_IDENTITY_API_VERSION=3$ export OS_URL=http://192.168.1.1:35357/v3

b. Check the endpoints that have been set.

• Execute the following command and make a note of the endpoint list.

$ openstack endpoint list


$ openstack endpoint list+----------------------------------+-----------+--------------+---------------+---------+-----------+------------------------------------------+| ID | Region | Service Name | Service Type | Enabled | Interface | URL |+----------------------------------+-----------+--------------+---------------+---------+-----------+------------------------------------------+| 5e46a7174be848febfbec947fe8eb8f4 | RegionOne | keystone | identity | True | public | http://192.168.1.1:5000/v3 || b72b4c4724034b6ca7c29075cdd884f1 | RegionOne | keystone | identity | True | internal | http://192.168.1.1:5000/v3 || cde0c8d8193e4c3e9a2e26cf8607075b | RegionOne | heat | orchestration | True | public | http://192.168.1.1:8004/v1/%(tenant_id)s || e70a450332634811938ddf378cf4a16d | RegionOne | keystone | identity | True | admin | http://192.168.1.1:35357/v3 |+----------------------------------+-----------+--------------+---------------+---------+-----------+------------------------------------------+

c. Change the protocol from http to https for the URL of the endpoint with a Service Namevalue of keystone. Execute the following command.

• Execute the following commands to make the change.

$ openstack endpoint set --url "https://IDENTITY_HOST:IDENTITY_PUBLIC_PORT/v3" public-endpoint-ID$ openstack endpoint set --url "https://IDENTITY_HOST:IDENTITY_PUBLIC_PORT/v3" internal-endpoint-ID$ openstack endpoint set --url "https://IDENTITY_HOST:IDENTITY_ADMIN_PORT/v3" admin-endpoint-D


$ openstack endpoint set --url "https://192.168.1.1:5000/v3" 5e46a7174be848febfbec947fe8eb8f4$ openstack endpoint set --url "https://192.168.1.1:5000/v3" b72b4c4724034b6ca7c29075cdd884f1$ openstack endpoint set --url "https://192.168.1.1:35357/v3" e70a450332634811938ddf378cf4a16d

4. Perform the setup needed to enable OpenStack Identity(keystone) to perform SSLcommunication.

a. Install the SSL communication module of Apache.

$ yum install mod_ssl

b. Open /etc/httpd/conf.d/wsgi-keystone.conf, and add the following to the next line of"WSGIPassAuthorization On".


24

SSLEngine onSSLCertificateFile /etc/keystone/ssl/certs/signing_cert.pemSSLCertificateKeyFile /etc/keystone/ssl/certs/signing_key.pem

This addition must be made in two locations. The following shows an example ofmaking this setting.

Listen 5000Listen 35357

<VirtualHost *:5000> WSGIDaemonProcess keystone-public processes=5 threads=1 user=keystone group=keystone display-name=%{GROUP} WSGIProcessGroup keystone-public WSGIScriptAlias / /usr/bin/keystone-wsgi-public WSGIApplicationGroup %{GLOBAL} WSGIPassAuthorization On SSLEngine on SSLCertificateFile /etc/keystone/ssl/certs/signing_cert.pem SSLCertificateKeyFile /etc/keystone/ssl/certs/signing_key.pem <IfVersion >= 2.4> ErrorLogFormat "%{cu}t %M" </IfVersion>

<Directory /usr/bin> Require all granted </Directory></VirtualHost>

<VirtualHost *:35357> WSGIDaemonProcess keystone-admin processes=5 threads=1 user=keystone group=keystone display-name=%{GROUP} WSGIProcessGroup keystone-admin WSGIScriptAlias / /usr/bin/keystone-wsgi-admin WSGIApplicationGroup %{GLOBAL} WSGIPassAuthorization On SSLEngine on SSLCertificateFile /etc/keystone/ssl/certs/signing_cert.pem SSLCertificateKeyFile /etc/keystone/ssl/certs/signing_key.pem <IfVersion >= 2.4> ErrorLogFormat "%{cu}t %M" </IfVersion>

<Directory /usr/bin> Require all granted </Directory></VirtualHost>

5. Change the protocol from http to https for the connection destination of OpenStackIdentity(keystone) described in /root/admin-openrc and /root/portal-openrc.

• Before change

$ export OS_AUTH_URL=http://IDENTITY_HOST:IDENTITY_ADMIN_PORT/v3


25

• After change

$ export OS_AUTH_URL=https://IDENTITY_HOST:IDENTITY_ADMIN_PORT/v3

6. Change the protocol from http to https for the endpoint for establishing a connection fromOpenStack Orchestration(heat-api) and OpenStack Orchestration(heat-engine) to OpenStackIdentity(keystone). Change the setting values described in /etc/heat/heat.conf.

$ openstack-config --set /etc/heat/heat.conf keystone_authtoken auth_uri https://IDENTITY_HOST:IDENTITY_PUBLIC_PORT$ openstack-config --set /etc/heat/heat.conf keystone_authtoken auth_url https://IDENTITY_HOST:IDENTITY_ADMIN_PORT$ openstack-config --set /etc/heat/heat.conf trustee auth_url https://IDENTITY_HOST:IDENTITY_ADMIN_PORT$ openstack-config --set /etc/heat/heat.conf ec2authtoken auth_uri https://IDENTITY_HOST:IDENTITY_PUBLIC_PORT$ openstack-config --set /etc/heat/heat.conf clients_keystone auth_uri https://IDENTITY_HOST:IDENTITY_ADMIN_PORT

The setting values described in the configuration file are changed in response to the executionof the commands. The following shows an example of the execution result.

[keystone_authtoken]auth_uri = https://192.168.1.1:5000auth_url = https://192.168.1.1:35357[trustee]auth_url = https://192.168.1.1:35357[ec2authtoken]auth_uri = https://192.168.1.1:5000[clients_keystone]auth_uri = https://192.168.1.1:35357

7. Restart the httpd service.

systemctl restart httpd

2.3.3 Setting the SSL of OpenStack Orchestration(heat-api)This section describes how to set the SSL of OpenStack Orchestration(heat-api).



Parametername


ORCHESTRATION_HOST

Host name or IP address of the serveron which OpenStackOrchestration(heat-api) is to beinstalled


192.168.1.1

ORCHESTRATION_PORT

Port number used by OpenStackOrchestration(heat-api)


35357

1. Copy the server certificate signed by a certificate authority and the secret key for the decryptedserver certificate to the configuration file directory of OpenStack Orchestration(heat-api).


26

# mkdir /etc/heat/ssl$ mkdir /etc/heat/ssl/certs$ cp –p cert.pem /etc/heat/ssl/certs/heatapi_cert.pem$ cp –p key.pem /etc/heat/ssl/certs/heatapi_key.pem

2. Include the file path to the server certificate signed by a certificate authority and that to thesecret key for the decrypted server certificate in the configuration file for OpenStackOrchestration(heat-api).

$ openstack-config --set /etc/heat/heat.conf heat_api cert_file /etc/heat/ssl/certs/heatapi_cert.pem$ openstack-config --set /etc/heat/heat.conf heat_api key_file /etc/heat/ssl/certs/heatapi_key.pem

3. Assign an authentication token and the endpoint URL to the relevant environment variables.Assign them according to step "a. (page 23)" of "2.3.2 Setting the SSL of OpenStackIdentity(keystone) (page 22)".

4. Check the endpoints that have been set. Execute the following command.

$ openstack endpoint list+----------------------------------+-----------+--------------+---------------+---------+-----------+------------------------------------------+| ID | Region | Service Name | Service Type | Enabled | Interface | URL |+----------------------------------+-----------+--------------+---------------+---------+-----------+------------------------------------------+| 5e46a7174be848febfbec947fe8eb8f4 | RegionOne | keystone | identity | True | public | https://192.168.1.1:5000/v3 || b72b4c4724034b6ca7c29075cdd884f1 | RegionOne | keystone | identity | True | internal | https://192.168.1.1:5000/v3 || cde0c8d8193e4c3e9a2e26cf8607075b | RegionOne | heat | orchestration | True | public | http://192.168.1.1:8004/v1/%(tenant_id)s || e70a450332634811938ddf378cf4a16d | RegionOne | keystone | identity | True | admin | https://192.168.1.1:35357/v3 |+----------------------------------+-----------+--------------+---------------+---------+-----------+------------------------------------------+

5. Change the protocol from http to https for the URL of the endpoint with a Service Name valueof heat. Execute the following command.

$ openstack endpoint set --url "https://ORCHESTRATION_HOST:ORCHESTRATION_PORT/v1/%(tenant_id)s" endpoint-ID


27

Chapter 3. Before Starting OperationThis chapter describes the settings that the system administrator must make before starting to operatethe stack management server. When a load distribution configuration is used, make the settings onthe application server on which the OpenStack and RabbitMQ components are to be installed.

Before performing this procedure, the administrator must perform Part 3 Before Starting Operationin Virtual DataCenter Automation Standard Edition Portal User Manual (Resource Management)Topology Template Orchestrator Option.

3.1 Deploying the configuration files for SSCResource Plug-in

Copy the vDCA SE Portal server operation configuration file (ssc_plugin.conf) and parameterconfiguration file (ssc_parameter.conf) to the stack management server.

The source files on the vDCA SE Portal server are given below.

Table 3-1 List of the configuration files for SSC Resource Plug-in

File name Description

C:\Program Files (x86)\NEC\vDCA\Tomcat\conf\NEC\TTO\ssc_plugin.conf

Operation configuration file for SSC Resource Plug-inDescribe the settings related to the operation of the SSC ResourcePlug-in function.The character code must be UTF-8 (without BOM).

C:\Program Files (x86)\NEC\vDCA\Tomcat\conf\NEC\TTO\ssc_parameter.conf

Parameter configuration file for SSC Resource Plug-inDescribe the parameter settings for the plug-in.The character code must be UTF-8 (without BOM).

Copy the ssc_plugin.conf and ssc_parameter.conf files deployed when setting up vDCA SE Portalunder <home directory of the heat user on the stack management server>/.heat-ssc/.

Make sure that the owner of the files is the heat user.

The heat user is automatically created when the OpenStack Orchestration is installed.

Copy ssc_plugin.conf.

$ chown heat <home directory of the heat user on the stack management server>/.heat-ssc/ssc_plugin.conf$ chmod 644 <home directory of the heat user on the stack management server>/.heat-ssc/ssc_plugin.conf

Copy ssc_parameter.conf.

$ chown heat <home directory of the heat user on the stack management server>/.heat-ssc/ssc_parameter$ chmod 644 <home directory of the heat user on the stack management server>/.heat-ssc/ssc_parameter

Chapter 3. Before Starting Operation

28

NoteWhen transferring files from a Windows machine, make sure that the contents of the files are not changed,including the character code and the line feed code.

3.2 Setting the resource management function3.2.1 Settings for connecting to SigmaSystemCenter

Make the settings for a connection between the stack management server and SigmaSystemCenter.

Transcribe the values in the configuration file (webframework.properties), deployed on the vDCA SEPortal server set with Virtual DataCenter Automation Standard Edition Portal User Manual(Resource Management) Topology Template Orchestrator Option to the operation configuration file(ssc_plugin.conf).

• Source file: <vDCA SE Portal server installation directory>\Tomcat\conf\NEC\webframework.properties

• Destination file: <home directory of the heat user on the stack management server>/.heat-ssc/ssc_plugin.conf

The items to transcribe are given below.

Table 3-2 Settings for connecting to SigmaSystemCenter

Sourcewebframework.properties

Destinationssc_plugin.conf

Description

Value ofproduct.cloudportal.provider.base.urlExample:http\://192.168.0.2\:26105

Value of ssc.api.endpointExample:http://192.168.0.2:26105* "\" is not required.

End point of the SigmaSystemCenterAPI

Value ofproduct.cloudportal.provider.ssc.access.key.id

Value of ssc.api.access_key Access key of theSigmaSystemCenter API

Value ofproduct.cloudportal.provider.ssc.secret.access.key

Value of ssc.api.secret_access_key Secret access key of theSigmaSystemCenter API

Setting example

An example of transcribing the settings for connecting to SigmaSystemCenter is given below.

Source: webframework.properties

product.cloudportal.provider.base.url=http\://192.168.0.2\:26105

product.cloudportal.provider.ssc.access.key.id=AccessKeyIdproduct.cloudportal.provider.ssc.secret.access.key=SecretAccessKey

Destination: ssc_plugin.conf

{ "heat": { "checkCompleteInterval": 0 }, "ssc": {


29

"api": { "endpoint": "https://192.168.0.2:26105", "api_version": "2016-10-10", "access_key": AccessKeyId "secret_access_key": SecretAccessKey },

...(Omitted)...

3.2.2 Management network settingsThe management network refers to a logical network created on SigmaSystemCenter for which"Management IP address" of the address pool setting is set. For details, see SigmaSystemCentermanuals.

In this section, settings are made for a management network to which a server created with templateprovisioning is to be automatically connected. Make the settings in this section on the stackmanagement server.

Table 3-3 Management network settings

Setting item Setting Description

Value of ssc.network.management.type existing Method of specifying the targetmanagement network* For existing, the network to which theserver is to be connected is automaticallyselected from the scope specified with thevalue of ssc.network.management.scope.

Value of ssc.network.management.scope all Scope of the target management network* For all, both private and public scopesare assumed.

Setting example

The management network setting example is shown below.

ssc_plugin.conf

{ "heat": { "checkCompleteInterval": 0 }, "ssc": { ... (Omitted) ...

"network": { "management": { "type": "existing", "scope": "all" },

TipFor details of the setting items not contained in this section, see "Appendix A. SSC Resource Plug-InConfiguration File (page 46)".


30

3.2.3 Network setting method• The following setting is required to enable the user to create a network by using vDCA SE

Topology Template Orchestrator Option. The setting is not required if you do not let the usercreate a network.

Table 3-4 Network setting

Setting item Setting

ssc.network.user.portGroup.switch Name of the virtual switch for which to create a portgroup

• If a VLAN ID is to be allocated to the network to create, the following setting is required.

Table 3-5 VLAN ID setting parameter


ssc.network.user.portGroup.vlanEnabled

true To use a VLAN ID, set it to true.Otherwise, set it to false.* If you specify true, VLAN IDs areissued sequentially according to thevlanPools setting.* If you specify false, the vlanPoolssetting is ignored.

ssc.network.user.portGroup.vlanPools.start

Start VLAN ID Specify the start value of the range ofVLAN IDs to allocate. 2 to 4091 can bespecified. The default value is 2.

ssc.network.user.portGroup.vlanPools.end

End VLAN ID Specify the end value of the range ofVLAN IDs to allocate. 2 to 4091 can bespecified. The default value is 4091.

ssc.network.user.portGroup.vlanPools.exclude

List of excluded VLANIDs

Specify the VLAN IDs to makeunavailable. 2 to 4091 can be specified.

Setting example

A virtual switch and VLAN ID setting example is shown below.


...(Omitted)...

"network": { "user": { "portGroup": { "baseName": "vlan_", "switch": switch001, "switchType": "virtualswitch", "vlanEnabled": true, "vlanPools": { "start": 2, "end": 4094, "exclude": [1000 , 1001] }


31

} } },

TipFor details of the setting items not contained in this section, see "Appendix A. SSC Resource Plug-InConfiguration File (page 46)".

Note- The creation of virtual switches is not supported.- The use of distributed virtual switches is not supported.- The setting of physical switches is not supported.

* Only the creation of the port group for a VM server and the creation of a logical networkcan be performed.

* To perform communication between VM servers, set a physical switch first.- All port groups are created on the same virtual switch on the VM server.- If, after creating a network, you changed the VM server candidates for which to create a server

by, changing the resource pool configuration or changing the allocation of the resource pool totenants, add and delete the port groups for these VM servers on SigmaSystemCenter and add anddelete port groups to and from the logical network.

If you do not want to let the user to create a network, you can make the setting of not letting theuser to create a network by adding the following to the bottom line of the /etc/heat/environment.d/default.yaml file.

"NEC::SSC::Net": ""

• After the completion of the setting of the resource management function, run the followingcommand to restart the OpenStack Orchestration(heat-api) and OpenStack Orchestration(heat-engine).

$ systemctl restart openstack-heat-api.service openstack-heat-engine.service

3.3 Settings to use the monitoring function3.3.1 Settings for connecting to MasterScope SystemManagerG

Make the settings for a connection between the stack management server and MasterScopeSystemManager G.

To use the monitoring function, make the following setting. Otherwise, the setting is not required.

Enable the MasterScope SystemManager G monitoring linkage of <home directory of the heat useron the stack management server>/.heat-ssc/ssc_parameter.conf.


32

Table 3-6 Flag for enabling MasterScope SystemManager G monitoring linkage processing


ssc.monitoring.enabled true Flag for enabling MasterScopeSystemManager G monitoringlinkage processing

• true: Enables monitoringlinkage processing.

• false: Disables monitoringlinkage processing.

If you set "ssc.monitoring.enabled" to true, make the following settings. If you set it to false, thesettings are not required.

Transcribe the values in the configuration file (webframework.properties) deployed on the vDCA SEPortal server set with Virtual DataCenter Automation Standard Edition Portal User Manual(Resource Management) Topology Template Orchestrator Option to the operation configuration file(ssc_plugin.conf).


• Destination file: <home directory of the heat user on the stack management server>/.heat-ssc/ssc_plugin.conf

The items to transcribe are given below.

Table 3-7 Settings for monitoring linkage


Destinationssc_plugin.conf

Description

Value ofproduct.cloudportal.service.monitoring.provider.webapibase.base.urlExample:http\://192.168.0.2\:12080

Value of ssc.monitoring.api.endpointExamplehttp://192.168.0.2:12080* "\" is not required.

End point of the MasterScopeSystemManager G API

Value ofproduct.cloudportal.service.monitoring.provider.webapibase.access.key.id

Value ofssc.monitoring.api.access_key

Access key of the MasterScopeSystemManager G API

Value ofproduct.cloudportal.service.monitoring.provider.webapibase.secret.access.key

Value ofssc.monitoring.api.secret_access_key

Secret access key of the MasterScopeSystemManager G API

Setting example

An example of the settings for connecting to MasterScope SystemManager G is shown below.


product.cloudportal.template.display.Template-WindowsServer2012R2STD = Windows Server/2012R2/Standard Edition

product.cloudportal.service.monitoring.provider.webapibase.base.url = http\://192.168.0.2:12080

product.cloudportal.service.monitoring.provider.webapibase.access.key.id=AccessKeyId


33

product.cloudportal.service.monitoring.provider.webapibase.secret.access.key=SecretAccessKey



...(Omitted)...

"monitoring": { "enabled": true, "api": { "endpoint": "https://192.168.0.2:12080", "api_version": "1.0", "access_key": AccessKeyId "secret_access_key": SecretAccessKey },

...

3.3.2 Setting the path of the executable file of the monitoringagent

Set the path on which the executable file of the monitoring agent is stored in the parameterconfiguration file for each template.

To use the monitoring function, make the following setting. Otherwise, the setting is not required.

Transcribe the values in the configuration file (webframework.properties), placed on the vDCA SEPortal server set with Virtual DataCenter Automation Standard Edition Portal User Manual(Resource Management) Topology Template Orchestrator Option to the parameter configuration file(ssc_parameter.conf).


• Destination file: <home directory of the heat user on the stack management server>/.heat-ssc/ssc_parameter.conf

Table 3-8 Setting the path of the executable file of the monitoring agent


Destinationssc_parameter.conf

Description

Value ofproduct.cloudportal.template.monitoring.agent.setup.path.<VM templatename>

Value of ssc.image.<imageID>.monitoringAgentPath

Installation path of the MasterScopeSystemManager G agent

• Specified: Monitoring linkageis enabled.

• Not specified: Monitoringlinkage is disabled.

* Must be specified for each templatethat is set for the image property.

Setting example


34

An example of transcribing the path of the executable file of the monitoring agent is shown below.


product.cloudportal.template.monitoring.agent.setup.path.TemplateA=C\:\\Program Files (x86)¥¥NEC¥¥UMF¥¥Operations¥¥Agent¥¥bin



...(Omitted)...

"image": { "imageA": { "vmTemplate": "TemplateA", "monitoringAgentPath": "C:¥¥Program Files (x86)¥¥NEC¥¥UMF¥¥Operations¥¥Agent¥¥bin", "flavors": [ "specName001", "specName002", "specName003", "specName004" ] } }, ...

TipFor details of the parameters in the operation configuration file (ssc_plugin.conf) and the parameterconfiguration file (ssc_parameter.conf) other than those described in this chapter, see "Appendix A. SSCResource Plug-In Configuration File (page 46)".

After the completion of the setting of the monitoring function, run the following command to restartthe OpenStack Orchestration(heat-api) and OpenStack Orchestration(heat-engine).


3.4 OpenStack Orchestration settings3.4.1 Setting the upper limit on the number of stacks

Set the upper limit on the number of stacks that can be created using vDCA SE Topology TemplateOrchestrator Option.

You can set the upper limit on the number of stacks that can be created in the entire system by usingmax_stacks_per_tenant in the [DEFAULT] section in the /etc/heat/heat.conf file. By default, theupper limit on the number of stacks that can be created is 100.

To set the upper limit on the number of stacks that can be created to 1000, set it as follows:


35

[DEFAULT]max_stacks_per_tenant = 1000

After the completion of the above setting, run the following command to restart the OpenStackOrchestration(heat-api) and OpenStack Orchestration(heat-engine).


3.4.2 Setting the timeout for the response time of RabbitMQSSC Resource Plug-in checks the validity of the information in the topology template requested fromthe management server, based on the information on SigmaSystemCenter. The time required for thevalidity check increases in proportion to the number of resources contained in the topology template.Thus, set a sufficiently long timeout according to the assumed number of resources.

You can set the timeout for rpc_response_timeout in the [DEFAULT] section in the /etc/heat/heat.conf file.

By default, the timeout is 60 seconds.

To set the timeout to 120 seconds, set it as follows:

[DEFAULT]rpc_response_timeout = 120

After making the above setting, execute the following command to restart OpenStackOrchestration(heat-api) and OpenStack Orchestration(heat-engine).


3.4.3 Setting the command for deleting stack informationMake the setting for using the command for deleting stack information when canceling a stackrequest.

By setting true for enable_stack_abandon in the [DEFAULT] section in the /etc/heat/heat.conf file asshown below, you can make the stack-abandon command available.

[DEFAULT]enable_stack_abandon = true

For details of canceling a stack request and of the stack-abandon command, see 27.1.8.1 Canceling astack request in Virtual DataCenter Automation Standard Edition Portal User Manual (ResourceManagement) Topology Template Orchestrator Option.

After the completion of the above setting, run the following command to restart the OpenStackOrchestration(heat-api) and OpenStack Orchestration(heat-engine).



36

3.4.4 Setting a validity period for the authentication token ofOpenStack Identity(keystone)

OpenStack Orchestration(heat-engine) makes a periodic check on OpenStack Identity(keystone) todetermine whether the authentication token requested by the management server has expired. Thetime required for the creation increases in proportion to the number of resources contained in thetopology template. Thus, set a sufficiently long validity period according to the assumed number ofresources.

The validity period of the authentication token can be set in the expiration field of the [token] sectionof the /etc/keystone/keystone.conf file.

When no setting is made, the validity period is 3600 seconds.

A validity period of 7200 seconds is set as follows:

[token]expiration = 7200

After making the above setting, execute the following command to restart OpenStackIdentity(keystone).

$ systemctl restart httpd


37

Chapter 4. Backing up and Restoring a DatabaseThe stack management server manages the following two databases. It is recommended that eachdatabase be backed up once when created for the first time.

Table 4-1 Database names and management information

Database name Management information

keystone Database to which OpenStack Identity(keystone) is connected. Authenticationinformation used to make a connection from the management server to the stackmanagement server is registered.

heat Database to which OpenStack Orchestration(heat-engine) is connected.Information about the stack created as requested from the management server isregistered.

The guidelines for backup operation design are described below.

The keystone database, in which data does not increase or decrease after the start of operation(because it contains master data), need not be backed up periodically.

For the heat database, in which data increases and decreases after the start of operation (because itcontains transaction data), you must consider backup operation design together with the managementserver because the database must be kept consistent with the data (for vDCA SE Portal andSigmaSystemCenter) managed by the management server.

MySQL offers a variety of backup techniques according to Recovery Time Objective and RecoveryPoint Objective. For details, see the MySQL manual. This chapter describes hot backup (onlinebackup) and restoring procedures as examples.

4.1 Backing up a database4.1.1 Backing up a database using MySQL

Following describes the backup method using mysqldump.

• Backing up a keystone database

Run the following command on the database server on which MySQL is installed to create abackup file. For filename, specify a backup file name.

$ mysqldump -u root -p keystone > filename.sql

• Backing up a heat database

Run the following command on the database server on which MySQL is installed to create abackup file. For filename, specify a backup file name.

$ mysqldump -u root -p heat > filename.sql

Chapter 4. Backing up and Restoring a Database

38

4.2 Restoring a database4.2.1 Restoring a database using MySQL

Following describes how to restore backup data acquired by using mysqldump.

• Restoring a keystone database

After creating a keystone database on the database server on which MySQL is installed, run thefollowing command to restore the database from the backup file. For backup_file, specify abackup file.

$ mysql -u root -p keystone < backup_file

• Restoring a heat database

After creating a heat database on the database server on which MySQL is installed, run thefollowing command to restore the database from the backup file. For backup_file, specify abackup file.

$ mysql -u root -p heat < backup_file

Chapter 4. Backing up and Restoring a Database

39

Chapter 5. UninstallationThis chapter describes how to uninstall the stack management server.

An overview of the uninstallation procedure is described below.

• Uninstall SSC Resource Plug-in.

• Uninstall OpenStack and RabbitMQ.

• Uninstall MySQL.

When an all-in-one configuration is used, each of the above procedures is performed on the singleserver. When a load distribution configuration is used, in contrast, it is necessary to perform theprocedures while considering which server is subject to each of the procedures.

Before starting the work, see the following for details about the procedures to be performed on eachserver.

Table 5-1 Procedures to be performed when components are installed separately on differentservers

Procedure Implementation on the DBMSserver on which the MySQL

component is installed

Implementation on theapplication server on which the

OpenStack and RabbitMQcomponents are installed

Uninstalling SSC Resource Plug-in × ○

Uninstalling OpenStack　andRabbitMQ

× ○

Uninstalling MySQL ○ ×

Legend: ○: Necessary to perform; ×: Unnecessary to perform

NoteAll the work described in this chapter must be done under the account with Administrator authority. Executethe commands as the root user or by using the sudo command.

5.1 Uninstalling SSC Resource Plug-inRun the following command to uninstall SSC Resource Plug-in.

$ pip uninstall heat-masterscope-ssc

When the uninstallation is complete, "Successfully uninstalled" is displayed.

5.2 Uninstalling the dependent librariesRun the following command to unintall the dpath libraries.

$ pip uninstall dpath

When the uninstallation is complete, "Successfully uninstalled" is displayed.

Chapter 5. Uninstallation

40

5.3 Uninstalling OpenStack and RabbitMQThis section describes how to uninstall OpenStack and RabbitMQ.

• Execute the following commands to uninstall OpenStack Identity(keystone).

$ yum remove httpd-2.4.6-40.el7.x86_64$ yum remove mod_wsgi-3.4-12.el7_0.x86_64$ yum remove memcached-1.4.25-1.el7.x86_64$ yum remove python-memcached-1.54-3.el7.noarch$ yum remove python-openstackclient-2.2.0-1.el7.noarch$ yum remove openstack-selinux-0.7.2-1.el7.noarch$ yum remove openstack-keystone-9.0.2-1.el7.noarch$ yum remove openstack-utils-2015.2-1.el7.noarch

• Execute the following command to uninstall RabbitMQ.

$ yum remove rabbitmq-server-3.6.2-3.el7.noarch

• Execute the following commands to uninstall OpenStack Orchestration(heat-api).

$ yum remove openstack-selinux-0.7.2-1.el7.noarch$ yum remove openstack-heat-api-6.0.0-1.el7.noarch$ yum remove openstack-utils-2015.2-1.el7.noarch

• Execute the following commands to uninstall OpenStack Orchestration(heat-engine).

$ yum remove python-pip-8.1.2-1.el7.noarch$ yum remove openstack-selinux-0.7.2-1.el7.noarch$ yum remove openstack-heat-engine-6.0.0-1.el7.noarch$ yum remove openstack-utils-2015.2-1.el7.noarch

Note• Check the package dependencies first and then execute uninstallation.

For details of dependent libraries, see "Appendix C. Dependent Libraries (page 82)".• The configuration files and module group that are placed during the installation of the OpenStack and

RabbitMQ packages are deleted during uninstallation, so you need not delete them manually.Delete any that have been edited with the assisting script, as needed.The following lists the files that are created or edited with the assisting script.

- /etc/httpd/conf.d/wsgi-keystone.conf- /root/portal-openrc- /root/admin-openrc

5.4 Uninstalling MySQLMySQL must be uninstalled manually.

For the uninstallation procedure, see the MySQL manual.

Chapter 5. Uninstallation

41

Chapter 6. Notes and RestrictionsThis chapter describes the notes and restrictions on using Virtual DataCenter Automation StandardEdition Topology Template Orchestrator Option.

6.1 Notes6.1.1 Notes on the operation of the stack management server

• Do not use the Restful API disclosed by the OpenStack Identity(keystone) or the OpenStackOrchestration(heat-api).

• The log files output by the OpenStack Orchestration(heat-api) and OpenStackOrchestration(heat-engine) may contain secret information depending on the log level. Thus,handle the log files with great care. When requesting an external organization to investigate forfault analysis, for example, take measures to preserve secret information.

• Basically, error messages displayed by vDCA SE Portal contain information according to thelanguage locale of the user, but in some cases, they contain information according to the systemlocale of the server on which the OpenStack Orchestration(heat-engine) runs.

6.1.2 Notes on recovery measures• If no DBMS backup exists, and a fault occurs in the DBMS used by the vDCA SE Portal

management server and vDCA SE Topology Template Orchestrator Option, causing the stackinformation to be lost, you cannot restore it with the information retained bySigmaSystemCenter alone.

For this reason, restore the servers contained in the stack on vDCA SE Portal, using the existingresource import command of the vDCA SE Portal, and operate them as non-stack resourceslater.

Request the system administrator to delete the network resources contained in the stack at thetime when the tenant no longer needs them.

6.1.3 Notes on vDCA SE Portal• A server is created in an operation group under a tenant. Non-tenant operation is not supported.

• Be sure to assign a resource pool to each tenant.

• The expansion processing that is performed when a server resource or a network resource isseparately created or deleted by vDCA SE Portal is not performed upon stack creation ordeletion.

6.1.4 Notes on the SSC Resource Plug-in configuration file• The use of a sub-resource pool cut out from a sub-resource pool is not supported.

• If a combination of parameters (VM template, datastore, logical network, and port group)retained by a resource pool is not specifiable in the same way on all the servers in the resourcepool, this may not result in an error in validation.

Examples:

Chapter 6. Notes and Restrictions

42

There is a VM template that can be used only on some VM servers in the resource pool.

There is a datastore that is connected only to some VM servers in the resource pool.

• Depending on the SigmaSystemCenter configuration, virtualization infrastructure type, and OStype, an error may occur even if the property constraints are not violated.

6.1.5 Notes on the resource management function• Updating the stack is not supported.

To change the stack configuration, delete the existing stack and then create a new stack.

6.1.6 Notes on the monitoring settings• When assigning the monitoring manager to a tenant, be sure to specify the monitoring manager

port number.

For details about how to assign the monitoring manager, see 3.3 Setting of Monitoring Agent inVirtual DataCenter Automation Standard Edition Portal User Manual (Monitoring) TopologyTemplate Orchestrator Option.

6.1.7 Notes on using network resources• It is necessary to create a virtual switch with the same name for each hypervisor in advance.

In an environment without NetvisorPro, it is necessary to set a VLAN trunk for the physicalswitch in advance and allocate the VLANID to use.

• Attributes

- CIDR (Classless Inter-Domain Routing)

If, after creating a network as part of a stack, you set the allocated address of the logicalnetwork to unset directly from SigmaSystemCenter, a value different from the actual onemay be returned for the CIDR attribute of the network resource displayed by stackmanagement.

- Address pool information and address pools excluded from allocation

On SigmaSystemCenter, only one allocation IP range can be set for the address pool of alogical network. More than one exclusion IP range can be set.

If multiple allocation_pools properties are specified, this function breaks them down to oneIP range and multiple exclusion IP ranges through calculation and registers them onSigmaSystemCenter.

For attributes, the values on SigmaSystemCenter are returned. If multiple allocation_poolsproperties are specified, the properties may not match the attributes.

• During rollback in the event of a stack creation failure, it takes 30 or more seconds to delete thenetwork resources contained in the stack.

• You cannot move from the resource details on the stack management window to the networkdetails.


43

6.2 Restrictions6.2.1 Restrictions on the SSC Resource Plug-in configurationfile

• Specify the following values in the parameter configuration file (ssc_parameter.conf) by usingsingle-byte alphanumeric characters and space.

- Flavor ID

- Image ID

- Disk profile ID

• In those images that are set in the parameter configuration file (ssc_parameter.conf) as servercreation sources, the disclosure or nondisclosure restriction cannot be designated separately foreach tenant. They are disclosed to all tenants.

• Only one switch name can be set for a port group of a network described in the operationconfiguration file (ssc_plugin.conf). Multiple switch names cannot be set.

• Set the ranges of the Start VLAN ID and End VLAN ID for a port group of a network describedin the operation configuration file (ssc_plugin.conf) such that they do not overlap with theranges of the Start VLAN ID and End VLAN ID managed by SigmaSystemCenter.

6.2.2 Restrictions on using network resources• In response to the creation of a network resource, a port group is created on all the virtual

machine servers that constitute the resource pool assigned to the tenant owning the networkresource. Port group creation cannot be limited to a specific virtual machine server.

6.2.3 Restrictions on using server resources• Resource pools for Amazon Elastic Compute Cloud (resource pools for which an upper resource

limits are not indicated) cannot be designated as the resource pools that will be used as serverresource creation destinations. Designate a resource pool for a private cloud (resource pool forwhich an upper resource limit is indicated).

• Operation groups for Amazon Elastic Compute Cloud (operation groups of a machine type for apublic cloud) cannot be designated as the operation groups that will be used as server resourcecreation destinations. Designate an operation group for a private cloud (operation group of amachine type for a VM, a VM server, or a physical server).

• Operation groups with a name containing a percent sign (%) or a sharp sign (#) cannot bedesignated as the operation groups that will be used as server resource creation destinations.Change the name such that it does not contain either a percent sign (%) or sharp sign (#), ordesignate an operation group with a name that does not contain either a percent sign (%) orsharp sign (#).

6.2.4 Restrictions on vDCA SE Portal• The request histories of the network resources contained in a stack are output by using either the

request history output command or the stack request history output command. Do not use theresults output by using the stack request history output command.


44

• A request history output by using the stack request history output command does not contain theapplicant of the relevant request for resource creation or deletion, the date of the application, theapprover, the date of the approval, or the date of the implementation of provisioning.

• A stack management widget cannot be set for the dashboard.


45

Appendix A. SSC Resource Plug-InConfiguration File

This chapter describes the specifications of the SSC resource plug-in configuration file. Describe theSSC Resource Plug-in configuration file in the JSON format. For this reason, if any of the followingcharacters are contained in the value of a setting item, add an escape character \ immediately beforethe characters.

• \\: Backslash

• \": Double quotation

• \b: Backspace

• \f: Form feed

• \n: Line feed

• \r: Carriage return

• \uXXXX: Unicode character

The setting items contained in this chapter must be represented in a form in which the JSON key isconcatenated with a period (.). For example, for setting items such as those below,

Table A-1 Example of setting items of the SSC Resource Plug-in configuration file

Setting item Type Required Settings:

ssc.api.endpoint string ○ End point of the SigmaSystemCenter API

Check and change the settings by changing the position on the file as below:

{ "ssc": { "api": { "endpoint": "https://192.168.0.1:26105", (Omitted) } }}

The legend of the [Required] column of the table contained in this chapter is as follows:

• ○: Required

• ×: Optional

• △: Optional depending on the conditions.

A.1 Operation configuration fileIn the operation configuration file (ssc_plugin.conf), make the following settings:

• Settings for connecting to SigmaSystemCenter and MasterScope SystemManager G

• Network settings

• Monitoring linkage settings

• Default value settings

Appendix A. SSC Resource Plug-In Configuration File

46

• Interval to check whether resource creation or deletion is complete

A.1.1 Settings for connecting to SigmaSystemCenter andMasterScope SystemManager G

This section describes the settings for connecting to SigmaSystemCenter in Topology TemplateOrchestrator Option.

Table A-2 Settings for connecting to SigmaSystemCenter

Setting item Type Required Settings

ssc.api.endpoint string ○ End point of the SigmaSystemCenter API

ssc.api.api_version string × Version of the SigmaSystemCenter API* Set "2016-10-10".

ssc.api.access_key string ○ Access key of the SigmaSystemCenter API

ssc.api.secret_access_key string ○ Secret access key of the SigmaSystemCenter API

ssc.api.verify boolean × Enable the flag of the server certificate of SSLcommunication of the SigmaSystemCenter APITo disable the verification of the server certificate, setfalse.By default, the verification of the server certificate isenabled.

The following table describes the settings for connecting to MasterScope SystemManager G inTopology Template Orchestrator Option.

Table A-3 Settings for connecting to MasterScope SystemManager G


ssc.monitoring.enabled boolean × Flag for enabling the MasterScope SystemManager Gmonitoring linkage processingTo enable monitoring linkage processing, set true.(By default, "true")

ssc.monitoring.api.endpoint

string △ End point of the MasterScope SystemManager G APIThe setting is required if ssc.monitoring.enabled is true.

ssc.monitoring.api.api_version

string × Version of the MasterScope SystemManager G API* Set "1.0".

ssc.monitoring.api.access_key

string △ Access key of the MasterScope SystemManager G APIThe setting is required if ssc.monitoring.enabled is true.

ssc.monitoring.api.secret_access_key

string △ Secret access key of the MasterScope SystemManager GAPIThe setting is required if ssc.monitoring.enabled is true.

ssc.monitoring.api.verify boolean × Enable the flag of the server certificate of SSLcommunication of the MasterScope SystemManager GAPITo disable the verification of the server certificate, setfalse.By default, the verification of the server certificate isenabled.


47

The following table describes the common settings for connecting to SigmaSystemCenter andMasterScope SystemManager G in Topology Template Orchestrator Option.

Table A-4 Settings for connecting to SigmaSystemCenter and MasterScope SystemManager G


ssc.client.timeout.connection

integer × HTTP connection timeout (seconds)By default, the timeout setting is invalid.

ssc.client.timeout.read integer × HTTP read timeout (seconds)By default, the timeout setting is invalid.

A.1.2 Network settings

A.1.2.1 Management network settingsFollowing describes the settings for the management network to which the server to be created byTopology Template Orchestrator Option is to be automatically connected.

Table A-5 Management network settings

Setting item Type Required Setting

ssc.network.management.type

string ○ Method of specifying the target management network• specified: The network to which the server is to be

connected is specified. The server is connected tothe management network specified forssc.network.management.name.

• existing: The network to which the server is to beconnected is not specified. The server is connectedto the management network decided in accordancewith the setting of ssc.network.management.scope.

ssc.network.management.scope

string × Target management network scope• private: The management network allocated to the

tenant is the target.• public: The management network that can be used

by all tenants is the target.• all: Both private and public scopes are the targets.

(The default is "all".)* The setting can be made ifssc.network.management.type is "existing".

ssc.network.management.name

string △ Logical network name of the target managementnetwork* The setting is required if ssc.network.management.typeis "specified".

ssc.network.management.dns_nameservers

string[] × DNS server IPv4 address list* You can set it if ssc.network.management.type is"specified".

ssc.network.management.ipv6_dns_nameservers

string[] × DNS server IPv6 address list* You can set it if ssc.network.management.type is"specified".


48

A.1.2.2 IP range settings of the networkFollowing describes the settings for the name of the IP range in the address pool of the network to becreated by Topology Template Orchestrator Option.

Table A-6 IP range settings of the network


ssc.network.user.rangeName

string × Name of the IP range whose classification is "allocation"(The default is "allocation_range".)

ssc.network.user.baseExcludedRangeName

string × Base name of the name of the IP range whoseclassification is "exclusion"For "base name_n", set a name (where n is a numberbetween 1 and origin).(The default is "excluded_range".)

A.1.2.3 Port group settings of the networkFollowing describes the settings of the parameters of the port group to be created simultaneouslywith the network to be created by Topology Template Orchestrator Option.

Table A-7 Port group settings of the network


ssc.network.user.portGroup.baseName

string × Base name of the port group (VLAN)• Port group name if

ssc.network.user.portGroup.vlanEnabled is true:<base name>_vlanID

• Port group name ifssc.network.user.portGroup.vlanEnabled is false:<base name>_random string (10 characters)

* Set it so that the port group name does not exceed 80characters.* The following characters cannot be used:^ \ : ; , . * ? < > | / ' "

ssc.network.user.portGroup.switch

string ○ Switch name

ssc.network.user.portGroup.switchType

string × Switch typeOnly a virtual switch can be specified.(The default is "virtualswitch".)

ssc.network.user.portGroup.vlanEnabled

boolean × Setting as to whether VLAN IDs are used• true: VLAN IDs are issued sequentially according

to the vlanPools setting.• false: The vlanPools setting is ignored, and VLAN

IDs are not used.(The default is "false".)

ssc.network.user.portGroup.vlanPools.start

integer × Start VLAN IDValid value: 2 to 4094(The default is "2".)

ssc.network.user.portGroup.vlanPools.end

integer × End VLAN IDValid value: 2 to 4094


49

Setting item Type Required Setting(The default is "4094".)

ssc.network.user.portGroup.vlanPools.exclude

integer[] × List of excluded VLAN IDsValid value: 2 to 4094

ssc.network.user.portGroup.private.type

string × Setting on the VM server on which to create a port groupof a logical network (if private)

• specified: If the VM server on which to create aport group is to be specified

• existing: If the VM server on which to create aport group is not to be specified

(The default is "existing".)If you specify "specified", the VM server specified forssc.network.user.portGroup.private.hostSystems isassumed to be the server.If you specify "existing", the VM server that can be usedin the resource pool allocated to the tenant is assumed tobe the server.

ssc.network.user.portGroup.private.hostSystems

string[] △ List of host paths or UUIDs of VM servers on which tocreate port groups* The setting is required ifssc.network.user.portGroup.private.type is "specified".* Be sure to set VM servers that exist.

ssc.network.user.portGroup.public.type

string △ Setting of the VM server on which to create a port groupof a logical network (if public)

• specified: If the VM server on which to create aport group is to be specified

• existing: If the VM server on which to create aport group is not to be specified

(The default is "existing".)If you specify "specified", the VM server specified forssc.network.user.portGroup.public.hostSystems isassumed to be the server.If you specify "existing", the VM server that can be usedin the resource pool allocated to the tenant is assumed tobe the server.

ssc.network.user.portGroup.public.hostSystems

string[] △ List of host paths or UUIDs of VM servers on which tocreate port groups* The setting is required ifssc.network.user.portGroup.public.type is "specified".* Be sure to set VM servers that exist.

A.1.3 Monitoring linkage settingsThis section describes the settings for monitoring linkage to perform during server creation if themonitoring function provided by MasterScope SystemManager G is to be used on the server to becreated by Topology Template Orchestrator Option.

Table A-8 Monitoring linkage settings


ssc.monitoring.software.linux.name

string × Name of the software to distribute when a server whoseOS type is Linux is to be created (for PVAgentSetup)


50

Setting item Type Required Settings(By default, "LinuxSetupMonitoring")Valid value: Within 58 bytesThe following cannot be used." * , . / : ; < > ? ¥ |

ssc.monitoring.software.linux.package

string × Name of the package contained in the software specifiedfor ssc.monitoring.software.linux.name (forPVAgentSetup)(By default, "Local-LinuxSetupMonitoring")Valid value: Within 63 bytes excluding the "Local-" atthe beginningSingle-byte alphanumeric characters and "- _" can beused.

ssc.monitoring.software.windows.name

string × Name of the software to distribute when a server whoseOS type is WindowsServer or WindowsClient is to becreated (for PVAgentSetup)(By default, "WindowsSetupMonitoring")Valid value: Within 58 bytesThe following cannot be used." * , . / : ; < > ? ¥ |

ssc.monitoring.software.windows.package

string × Name of the package contained in the software specifiedfor ssc.monitoring.software.windows.name (forPVAgentSetup)(By default, "Local-WindowsSetupMonitoring")Valid value: Within 63 bytes excluding the "Local-" atthe beginningSingle-byte alphanumeric characters and "- _" can beused.

A.1.4 Default value settingsFlavors, images, and disk profiles in the parameter configuration file (ssc_parameter.conf) haveoptional items. If the items are omitted, the values specified as a default value are used. If thehost_profile property and the disks[].profile property are omitted when a server is created, the valuesspecified as a default value are used.

A.1.4.1 Default values of the flavor (ssc.flavor.<flavor ID>)Following describes the settings of the values used if optional items are omitted in the settings offlavors in the parameter configuration file (ssc_parameter.conf).

Table A-9 Default values of the flavor


ssc.defaults.flavor.cpu.share

string × CPU share• lowest: Lowest• low: Low• normal: Normal• high: High• highest: Highest

(The default is "normal".)


51


ssc.defaults.flavor.cpu.reservation

integer × CPU reservation (MHz)Valid value: 0 to 99999(The default is "0".)

ssc.defaults.flavor.cpu.limit integer × CPU limitation (MHz)Valid value: 0 to 99999 (0 means no limit.)(The default is "0".)

ssc.defaults.flavor.ram.share

string × Memory share• low: Low• normal: Normal• high: High

(The default is "normal".)

ssc.defaults.flavor.ram.reservation

integer × Memory reservation (MB)Valid value: 0 to 99999999(The default is "0".)

ssc.defaults.flavor.ram.limit

integer × Memory limitation (MB)Valid value: 0 to 99999999 (0 means no limit.)(The default is "0".)

A.1.4.2 Default values of the system disk profile(ssc.diskProfile.system.<disk profile ID>)

Following describes the settings of the values used if optional items are omitted in the settings of thesystem disk profile in the parameter configuration file (ssc_parameter.conf).

Table A-10 Default values of the system disk profile


ssc.defaults.diskProfile.system.type

string × Disk type• thin: Performs thin provisioning on the virtual disk

for the system. When it is created, a minimumcapacity is secured, and is increased as needed.

• thick: Performs thick provisioning on the virtualdisk for the system. The area for the size specifiedwhen it is created is secured.

(The default is "thin".)

ssc.defaults.diskProfile.system.datastoreTags

string[] × Datastore tag list(The default is "[ ]".)

A.1.4.3 Default values of the disk profile(ssc.diskProfile.ext.<disk profile ID>)

Following describes the settings of the values used if the optional items are omitted in the settings ofthe disk profile in the parameter configuration file (ssc_parameter.conf).


52

Table A-11 Default values of the disk profile


ssc.defaults.diskProfile.ext.type


for the extended disk. When it is created, aminimum capacity is secured, and is increased asneeded.

• thick: Performs thick provisioning on the virtualdisk for the extended disk. The area for the sizespecified when it is created is secured.

(The default is "thin".)

ssc.defaults.diskProfile.ext.datastoreTags

string[] × Datastore tag list(The default is "[ ]".)

A.1.4.4 Default values of the host profileFollowing describes the settings of the values used if the host_profile property is omitted when aserver is to be created by Topology Template Orchestrator Option.

Table A-12 Default values of the host profile


ssc.defaults.hostProfile.adminAccountWindows

string × Administrator account (Windows)Fixed to "Administrator".

ssc.defaults.hostProfile.adminAccountLinux

string × Administrator account (Linux)Fixed to "root".

ssc.defaults.hostProfile.adminPassLength

integer × Length of the initial password of the administratoraccount(The default is "10".)

ssc.defaults.hostProfile.owner

string × Owner name to be set on the OS(The default is "Owner".)

ssc.defaults.hostProfile.organization

string × Organization to which the user to set on the OS belongs(The default is "Organization".)

ssc.defaults.hostProfile.timeZone

string × OS timezoneHexadecimal number defined for the Microsoft timezone index values (http://support.microsoft.com/kb/973627)(The default is "EB".)

ssc.defaults.hostProfile.domainType

string × Specify whether the setting is a workgroup or a domain.• workgroup: Workgroup• domain: Domain

(The default is "workgroup".)

ssc.defaults.hostProfile.domainName

string × Workgroup name or domain name(The default is "WORKGROUP".)

ssc.defaults.hostProfile.licenseMode

string × License mode• PerServer: Number of servers connected

simultaneously• PerSeat: Connected clients


53

Setting item Type Required Setting(The default is "PerServer".)

ssc.defaults.hostProfile.maxConnection

integer × Number of servers connected simultaneously(The default is "5".)

ssc.defaults.hostProfile.domainSuffix

string × Domain suffix(The default is "localdomain".)

A.1.4.5 Default values of the machine profileFollowing describes the settings of the values used if properties are omitted when a server is to becreated by Topology Template Orchestrator Option.

You can set the default values of the following properties.

• NEC::SSC::Server resource

- disks[].profile

Table A-13 Default values of the machine profile


ssc.defaults.machineProfile.disk.profile

string × Extended disk profile* If this is not set, the disks[ ].profile property ofNEC::SSC::Server must be specified.

A.1.5 Setting the interval to check whether resource creationor deletion is complete

This section describes the setting of the interval at which to execute the processing of sendingSigmaSystemCenter inquiries as to whether resource creation and deletion is completed withTopology Template Orchestrator Option.

Table A-14 Interval to check whether resource creation or deletion is complete


heat.checkCompleteInterval

integer × Resource creation and deletion completion checkexecution interval settingInterval at which to send an inquiry to the virtual hostabout the status of whether the executed resourcecreation and deletion processing is completed (seconds)(By default, "1")

A.2 Parameter configuration fileThe parameter configuration file (ssc_parameter.conf) sets the following:

• Flavors

• Images

• Disk profiles


54

A.2.1 FlavorsFlavors are hardware settings that can be used on a virtual server. They define the specs (such asCPU, memory size, and system disk size) of a VM template.

Settings related to flavors are listed below.

For the setting item <flavor ID>, set the ID of the flavor for specifying in the topology template.

Table A-15 Flavors


ssc.flavor.<flavorID>.cpu.count

integer ○ Number of CPUsValid value: 1 to 9999

ssc.flavor.<flavorID>.cpu.share

string × CPU share• lowest: Lowest• low: Low• normal: Normal• high: High• highest: Highest

(By default, the value that is set on "A.1.4.1 Defaultvalues of the flavor (ssc.flavor.<flavor ID>) (page 51)"is used.)

ssc.flavor.<flavorID>.cpu.reservation

integer × CPU reservation (MHz)Valid value: 0 to 99999(By default, the value that is set on "A.1.4.1 Defaultvalues of the flavor (ssc.flavor.<flavor ID>) (page 51)"is used.)

ssc.flavor.<flavorID>.cpu.limit

integer × CPU limitation (MHz)Valid value: 0 to 99999 (0 means no limit)(By default, the value that is set on "A.1.4.1 Defaultvalues of the flavor (ssc.flavor.<flavor ID>) (page 51)"is used.)

ssc.flavor.<flavorID>.ram.size

integer ○ Memory (MB)Valid value: 1 to 9999999

ssc.flavor.<flavorID>.ram.share

string × Memory share• low: Low• normal: Normal• high: High

(By default, the value that is set on "A.1.4.1 Defaultvalues of the flavor (ssc.flavor.<flavor ID>) (page 51)"is used.)

ssc.flavor.<flavorID>.ram.reservation

integer × Memory reservation (MB)Valid value: 0 to 99999999(By default, the value that is set on "A.1.4.1 Defaultvalues of the flavor (ssc.flavor.<flavor ID>) (page 51)"is used.)

ssc.flavor.<flavorID>.ram.limit

integer × Memory limitation (MB)Valid value: 0 to 99999999 (0 means no limit.)


55

Setting item Type Required Setting(By default, the value that is set on "A.1.4.1 Defaultvalues of the flavor (ssc.flavor.<flavor ID>) (page 51)"is used.)

ssc.flavor.<flavorID>.systemdisk.size

integer ○ System disk size (MB)Valid value: 10 to 99999999

ssc.flavor.<flavorID>.systemdisk.profile

string ○ System disk profilessc.diskProfile.system.<flavor ID>

A.2.2 ImagesAn image is a combination of VM template and spec. It defines the flavors that can be used in theVM template and the agent settings for monitor linkage.

For the setting item <image ID>, set the ID of the image for specifying in the topology template.

Table A-16 Images


ssc.image.<imageID>.vmTemplate

string ○ VM template nameValid number of characters: 1 to 80The following can be used.Single-byte alphanumeric characters, single-byte blank," _ - ( ) "

ssc.image.<imageID>.monitoringAgentPath

string × Installation path of the MasterScope SystemManager Gagent*1

If none is specified, monitoring linkage processing is notperformed.

ssc.image.<imageID>.flavors

string[] × List of IDs of the flavors that can use this image*2

If none is specified, it can be used by all flavors.

*1 The maximum length of the file path, as well as the available characters, differs depending on the OSand the file system.

*2 This must be set correctly because the range that can be specified with a flavor differs depending onthe VM template type and the virtualization infrastructure type. In SSC Resource Plug-in, no check isperformed for the correctness of the settings.

A.2.3 Disk profiles

A.2.3.1 System disk profileIn the system disk profile, define a combination of a datastore tag with the disk type of the systemdisk to set on a server. You can also define the flavors that can use the system disk profile.

For the setting item <disk profile ID>, set the ID of the disk profile for specifying in the flavorsetting.

Table A-17 System disk profile


ssc.diskProfile.system.<disk profile ID>.type

string × Disk type


56

Setting item Type Required Setting• thin: Performs thin provisioning on the virtual disk

for the system. When it is created, a minimumcapacity is secured, and is increased as needed.

• thick: Performs thick provisioning on the virtualdisk for the system. The area for the size specifiedwhen it is created is secured.

(By default, the value that is set on "A.1.4.2 Defaultvalues of the system disk profile(ssc.diskProfile.system.<disk profile ID>) (page 52)" isused.)

ssc.diskProfile.system.<disk profile ID>.datastoreTags

string[] × Datastore tag list(By default, the value that is set on "A.1.4.2 Defaultvalues of the system disk profile(ssc.diskProfile.system.<disk profile ID>) (page 52)" isused.)

ssc.diskProfile.system.<disk profile ID>.flavors

string[] × List of IDs of the flavors that can use this profile*1

(By default, it can be used by all flavors.)

*1 This must be set correctly because the range that can be specified with a flavor differs depending onthe VM template type and the virtualization infrastructure type. In SSC Resource Plug-in, no check isperformed for the correctness of the settings.

A.2.3.2 Extended disk profileIn the extended disk profile, define a combination of a datastore tag with the disk type of theextended disk to set on a server.

For the setting item <disk profile ID>, set the ID of the disk profile for specifying in the topologytemplate.

Table A-18 Extended disk profile


ssc.diskProfile.ext.<diskprofile ID>.type


for the extended disk. When it is created, aminimum capacity is secured, and is increased asneeded.

• thick: Performs thick provisioning on the virtualdisk for the extended disk. The area for the sizespecified when it is created is secured.

(By default, the value that is set on "A.1.4.3 Defaultvalues of the disk profile (ssc.diskProfile.ext.<diskprofile ID>) (page 52)" is used.)

ssc.diskProfile.ext.<diskprofile ID>.datastoreTags

string[] × Datastore tag list(By default, the value that is set on "A.1.4.3 Defaultvalues of the disk profile (ssc.diskProfile.ext.<diskprofile ID>) (page 52)" is used.)


57

Appendix B. Topology Template FormatThis chapter describes the topology template.

B.1 What is a topology template?A topology template is a text file that defines the resources making up a stack and their relationships.

The character code must be UTF-8 (without BOM) and the format must be YAML.

This chapter is intended for template creators and describes how to write a topology template.

TipIf you want to provide a long description that does not fit in a single line, you can write it on multiple linesin YAML format.A '>' replaces a line feed code with a single-byte space. The line feed code on the last line is, however,saved.

B.2 Topology template exampleIn the following example, a logical network is created, address pool settings are made, and a sever toconnect to the logical network is created.

1 heat_template_version: 2016-04-08 2 3 description: > 4 HOT template to create a new logical network and IP address allocation pools, 5 and for deploying a linux server into the new logical network. 6 7 parameters: 8 net_name: 9 type: string10 description: name of logical network to be created11 net_cidr:12 type: string13 description: logical network address (CIDR notation)14 net_gateway:15 type: string16 description: logical network gateway address17 net_pool_start:18 type: string19 description: start of logical network IP address allocation pool20 net_pool_end:21 type: string22 description: end of logical network IP address allocation pool23 server_group_path:24 type: string25 description: path to operation group26 server_host_name:27 type: string28 description: host name of server29 server_resource_pool:

Appendix B. Topology Template Format

58

30 type: string31 description: resource pool for server32 server_flavor:33 type: string34 description: flavor to use for server35 server_image:36 type: string37 description: image to use for server38 server_disk_size:39 type: number40 description: size of extended disk to use for server41 server_admin_pass:42 type: string43 description: administrator password of server4445 resources:46 net1:47 type: NEC::SSC::Net48 properties:49 name: { get_param: net_name }50 subnets:51 - cidr: { get_param: net_cidr }52 gateway_ip: { get_param: net_gateway }53 allocation_pools:54 - start: { get_param: net_pool_start }55 end: { get_param: net_pool_end }5657 server1:58 type: NEC::SSC::Server59 properties:60 group: { get_param: server_group_path }61 name: { get_param: server_host_name }62 resource_pool: { get_param: server_resource_pool }63 flavor: { get_param: server_flavor }64 image: { get_param: server_image }65 disks:66 - size: { get_param: server_disk_size }67 networks:68 - network: { get_resource: net1 }69 host_profile:70 admin_pass: { get_param: server_admin_pass }7172 outputs:73 server1_networks:74 description: networks of server175 value: { get_attr: [server1, networks] }

Line 1: For heat_template_version, define the version of the topology template.

Line 3: For the description section, provide a description of the template.

Line 7: In the parameters section, define, as input parameters, the items that each user can specifyduring stack creation.

When the topology template is read on the "Stack Creation (Input)" window on vDCA SE Portal, thesettings in the parameters section are displayed in [Parameters] on the window. By entering valuesfor the parameters displayed in [Parameters], you can specify property values not on the topologytemplate but during stack creation.


59

Line 45: In the resources section, define the resources making up a stack. In the example, the virtualnetwork "net1" and the virtual server "server1" are defined.

Line 49: Using the get_param function, pass the value entered on the screen to the input parameternet_name, defined on line 8.

Line 68: Using the get_resource function, reference the logical network "net1" on line 46, which isset in the template. In the example, "net1" is specified as the name of the logical network to whichserver1 is connected.

Line 72: In the outputs section, define the output parameters to return after stack creation. In theexample, the name of the logical network to which server1 is connected is returned as an outputparameter.

B.3 Topology template structureA topology template consists of multiple sections.

heat_template_version: 2016-04-08 # specify version of the template

description: # a description of the template

parameter_groups: # a declaration of input parameter groups and order

parameters: # declaration of input parameters

resources: # declaration of template resources

outputs: # declaration of output parameters

conditions: # declaration of conditions

Table B-1 Section

Section Description

heat_template_version Define the version of the topology template.The supported versions are as follows:

• 2013-05-23• 2014-10-16• 2015-04-30• 2015-10-15• 2016-04-08

[Required]

description Provide a description of the template and so on.

parameter_groups Define the grouping and input order of input parameters.


60

Section Description

parameters Define the input parameters that user can specify during stack creation.

resources Define the types and properties of the resources to create.* Specify at least one resource definition.[Required]

outputs Define output parameters.

B.3.1 parameters sectionThe parameters section is used to define the input parameters that are used to instantiate a template.

In this section, describe parameters that must be set for each user, for example, a password.

B.3.1.1 Data structure of the parameters section

parameters: <param name>: type: <string | number | json | comma_delimited_list | boolean> label: <human-readable name of the parameter> description: <description of the parameter> default: <default value for parameter> hidden: <true | false> constraints: <parameter constraints>

Table B-2 parameters section

Name Description

param name Input parameter name[Required]

type Input parameter data type• string• number• json• comma_delimited_list• boolean

[Required]

label Input parameter label* Displayed as the name of the parameter key on the "Stack Creation(Input)" window.

description Description of the input parameter

default Default value to assume if the input parameter is omitted

hidden Set it to true to mask the input parameter value on the "Stack Creation(Input)" window.Set it to false to display the input value.

• true• false

* The default is false.* Used to hide the password specified as a parameter, for example.


61

Name Description

constraints Input parameter constraintsSee "B.3.1.2 Parameter constraints (page 62)".

B.3.1.2 Parameter constraintsThe structure of the parameter constraints in the parameters section is shown below.

constraints: - <constraint type>: <constraint definition> description: <constraint description>

Table B-3 Parameter Constraints

Name Description

constraint type Constraint type• length• range• allowed_values• allowed_pattern• custom_constraint

[Required]

constraint definition Constraint value corresponding to the specified constraint type* The syntax of the individual constraints is described in the subsequentsections.[Required]

description Set the message to be displayed to the user if the constraint is violated.If none is set, the default message is displayed.

lengthThis is applied to a string type parameter and defines the minimum and maximum values of thenumber of characters.

Either or both of min and max must be specified.

length: { min: <lower limit>, max: <upper limit> }

rangeThis is applied to a numeric type parameter and defines the minimum and maximum values ofspecifiable values.

Either or both of min and max must be specified.

range: { min: <lower limit>, max: <upper limit> }

allowed_valuesThis is applied to both numeric type and string type parameters and defines a list of possible values.


62

allowed_values: [ <value>, <value>, ... ]

The following description is also available.

allowed_values: - <value> - <value> - ...

Setting example

parameters: instance_type: type: string label: Instance Type description: Instance type for compute instances constraints: - allowed_values: - m1.small - m1.medium - m1.large

allowed_patternThis is applied to a string type parameter and defines a regular expression of possible values.

allowed_pattern: <regular expression>

Setting example

parameters: user_name: type: string label: User Name description: User name to be configured for the application constraints: - allowed_pattern: "[A-Z]+[a-zA-Z0-9]*" description: User name must start with an uppercase character

custom_constraintThis is used to define a customized constraint.

custom_constraint: <name>

The SSC Resource Plug-in function provides the following custom_constraints.

Table B-4 custom_constraint

Name Description of the check

nec.ssc.ipv4_addr Must be an IPv4 address.


63

Name Description of the check

nec.ssc.ipv6_addr Must be an IPv6 address.

nec.ssc.flavor Must be the flavor ID that is set for "ssc.flavor.<flavor ID>" inssc_parameter.conf.

nec.ssc.image Must be the image ID that is set for "ssc.image.<image ID>" inssc_parameter.conf.

nec.ssc.disk_profile Must be the disk profile ID that is set for "ssc.diskProfile.ext.<disk profileID>" in ssc_parameter.conf.

nec.ssc.network Resource ID (logical network name) of NEC::SSC::Net

nec.ssc.tenant Tenant name

nec.ssc.group Group path

nec.ssc.resource_pool Resource pool name

nec.ssc.timezone Must be the timezone of the OS.The hexadecimal number defined for the Microsoft time zone index values(http://support.microsoft.com/kb/973627) is valid.

Setting example

parameters: net_gateway: type: string description: logical network gateway address constraints: - custom_constraint: nec.ssc.ipv4_addr

B.3.2 resource sectionThe resource section is used to define the resources to make up the stack created from a topologytemplate.

By using intrinsic functions (get_param, get_resource), you can reference parameters and otherresources.

B.3.2.1 Data structure of the resource section

resources: <ID in template>: type: <resource type> properties: <property name>: gt;property value> depends_on: <ID in template or list of ID>

Table B-5 resource section

Name Description

type Resource type• NEC::SSC::Net• NEC::SSC::Server


64

Name Description

properties Resource properties

depends_on Dependency with other resources

B.3.2.2 Resource typesThe resource types managed by the SSC Resource Plug-in function are as follows:

• NEC::SSC::Net

• NEC::SSC::Server

NEC::SSC::Net resource type• Topology template syntax

resources: <ID in template>: type: NEC::SSC::Net properties: name: <network name> subnets: - cidr: <cidr> gateway_ip: <default gateway ip address> allocation_pools: - start: <ip address> end: <ip address> excluded_allocation_pools - start: <ip address> end: <ip address>

• Properties

Table B-6 NEC::SSC::Net resource type

Property Type Require

d

Input constraint Initialvalue

Description

name string ○ Must be unique inSigmaSystemCenter.1 to 63 charactersAvailablecharacters: [0-9a-zA-Z][0-9a-zA-Z\-_]*

- Logical network name*2

Used as a resource ID.

subnets list × Valid range of theindex: 0 to 2

[ ] SubnetOne IPv4 address and one IPv6address can be set.

subnets[ ].cidr string ○ - - CIDR*2

subnets[ ].gateway_ip

string × Must be within theCIDR range.*1

- Default gateway IP address*2


65


d

Input constraint Initialvalue

Description

subnets[ ].allocation_pools[ ]

list ○ Valid range of theindex: 1 to 256

[ ] Address pool information array

subnets[ ].allocation_pools[ ].start

string ○ Must be within theCIDR range.*1

The start addressmust be ≤ the endaddress.

- Start IP address

subnets[ ].allocation_pools[ ].end



- End IP address

subnets[ ].excluded_allocation_pools[ ]

list × Valid range of theindex: 0 to 256

[ ] Array of address pools excludedfrom allocation

subnets[ ].excluded_allocation_pools[ ].start



- Start IP address

subnets[ ].excluded_allocation_pools[ ].end



- End IP address

*1 Indicates that the specified IP address is the IP address of the subnet specified in CIDR and thatthe IP version is the same as that of CIDR.

*2 You cannot specify functions other than get_param or dummy parameters.

• Attributes

Table B-7 NEC::SSC::Net attributes

Name Description

name Logical network name (same as the resource ID)

tenant Name of the tenant to which the network is applied

subnets Subnet

subnets[ ].cidr CIDR

subnets[ ].gateway_ip Default gateway

subnets[ ].ip_version IP version• For IPv4, 4• For IPv6, 6

subnets[ ].allocation_pools Address pool information array

subnets[ ].allocation_pools[ ].start Start address

subnets[ ].allocation_pools[ ].end End address


66

Name Description

subnets[ ].allocation_pools[ ].name IP range name

subnets[ ].excluded_allocation_pools Array of address pools excluded from allocation

subnets[ ].excluded_allocation_pools[ ].start Start address

subnets[ ].excluded_allocation_pools[ ].end End address

subnets[ ].excluded_allocation_pools[ ].name IP range name

NoteFor address pool information and address pools excluded from allocation, the values onSigmaSystemCenter are returned, and may differ from the values specified for properties.

NEC::SSC::Server resource type• Topology template syntax

resources: <ID in template>: type:NEC::SSC::Server properties: group:<group pass> name:<host name> resource_pool:<resource pool name> flavor:<flaver id> image:<image id> disks: - size:<size> profile:<profile id> networks: - network:<network resource id> fixed_ips: - <ip address> - <ip address> - ... dns_nameservers: - <ip address> - <ip address> - ... ipv6_dns_nameservers: - <ip address> - <ip address> - ... wins_servers: - <ip address> - <ip address> host_profile: admin_pass:<password> owner:<user name> organization:<organization> timezone:<timezone> product_key:<product key> domain_type:<domain type> domain_name:<domain name> domain_user:<domain account>


67

domain_pass:<domain password> license_mode:<license mode> max_connection:<maximum number of connections> domain_suffix:<domain suffix>

• Properties

Table B-8 NEC::SSC::Server resource type


d

Input constraint Defaultvalue

Description

group string ○ Must be anexisting operationgroup.1 to 1024characters

- Path of the operation group tocreate a server*1

Specify the path of the taskgroup created by the tenant towhich the user submitting astack creation request belongs.Specify the task group pathcontaining the tenant ID.

name string ○ Must be unique inthe operationgroup specified forthe group property.Availablecharacters: [a-zA-Z][a-zA-Z0-9-.]Number ofcharacters:- For Linux, 1 to24 characters- For Windows, 1to 15 characters

- Host name*1

resource_pool string ○ 1 to 63 characters - Name of the resource pool tocreate server*1

Specify the name of the resourcepool available to the tenant towhich the user submitting astack creation request belongs.Separate the resource pool pathto specify at the time of a servercreation request with a slash (/)and specify the last value(resource pool name).

flavor string ○ 1 to 64 characters - Flavor ID*1

image string △ 1 to 64 characters - Image ID*1

Specify the name of the catalogto specify at the time of a servercreation request.By default, the VM template in[Properties] - [Software] of theoperation group specified forgroup is applied.


68


d


Description

* This must be specified if noVM template is set in operationgroup properties.*3

disks list - Valid range of theindex: 0 to 6

[ ] Extended disk listBy default, the disk information(extended disk) in [Properties] -[Machine Profile] of theoperation group specified forgroup is applied.

disks[ ].size integer ○ Valid value: 10 to99999999

- Disk size (MB)*1

* Specify it in decimal notation.Even if you set a valuecontaining a decimal point, thevalue is truncated to a wholenumber.

disks[ ].profile string △ 1 to 64 characters ssc.defaults.machineProfile.disk.profile

Disk profile ID*1

Specify the name of the disk tagavailable to the catalog specifiedat the time of a server creationrequest.* This must be specified ifssc.defaults.machineProfile.disk.profile is not set up.

networks list - Valid index range:0 to (10 - Numberof managednetworks)

[ ] Setting list of networks toconnect

networks[ ].network

string ○ Must be a sharednetwork or anetwork allocatedto a tenant.Must be availableto the resourcepool.1 to 63 characters

- Logical network name*2

* If no address pool is set for thelogical network, the IP address isnot checked for availability.

networks[ ].fixed_ips

list - Valid range of theindex: 0 to 10

[ ] IP address listBy default, issued from theaddress pool that is set for thelogical network.If an address pool is not set up,an IP address is assigned byDHCP.

networks[ ].fixed_ips[ ]

string ○ Must be within therange of the subnetof the logicalnetwork (specifiedfor the networkproperty).

- IP address


69


d


Description

networks[ ].dns_nameservers

list - Valid range of theindex:- For Linux: 0 to 3- For Windows: 0to 2

- DNS server address list

networks[ ].dns_nameservers[]

string ○ - - IPv4 address of the DNS server

networks[ ].ipv6_dns_nameservers

list - Valid range of theindex:・For Linux: 0 to3・For Windows: 0to 2

[ ] DNS server address list

networks[ ].ipv6_dns_nameservers[]

string ○ - - IPv6 address of the DNS server

networks[ ].wins_servers

list - Valid range of theindex: 0 to 2

[ ] WINS server address listBy default, no settings are made.* This can be specified when theOS type is Windows Server orWindows Client.

networks[ ].wins_servers[]

string ○ - - IPv4 address of the WINS server

host_profile map △ - - Host profileBy default, [Properties] - [HostProfile] of the operation groupspecified for group is applied.* This cannot be omitted if animage whose OS type isWindows Server or WindowsClient is used and domain isspecified for the default value(ssc.defaults.hostProfile.domainType in ssc_parameter.conf).

host_profile.admin_pass

string - 1 to 256 charactersAvailablecharacters: ASCIIcharacters, single-byte blankProhibitedcharacters: "" ,"

Randomlygeneratedby the SSCResourcePlug-in.

Password for the administratoraccount* The specifiable string length islimited by the OS of the serveron which the VM template isbased.

host_profile.owner string - 1 to 100 charactersAvailablecharacters: ASCIIcharacters, single-byte blank

ssc.defaults.hostProfile.owner

User name to set on the OSThis can be specified when theOS type is Windows Server orWindows Client.

host_profile.organization

string - 1 to 100 charactersAvailablecharacters: ASCII

ssc.defaults.hostProfile.organization

Organization to which the userto set on the OS belongs


70


d


Description

characters, single-byte blank

This can be specified when theOS type is Windows Server orWindows Client.

host_profile.timezone

string - Hexadecimalnumber defined in"Microsoft TimeZone IndexValues"

ssc.defaults.hostProfile.timeZone

OS timezoneThis can be specified when theOS type is Windows Server orWindows Client.

host_profile.product_key

string - Format "xxxxx-xxxxx-xxxxx-xxxxx-xxxxx"

- OS product key* This can be specified when theOS type is Windows Server orWindows Client.

host_profile.domain_type

string - • workgroup:Workgroup

• domain:Domain

ssc.defaults.hostProfile.domainType

Workgroup or domain* This can be specified when theOS type is Windows Server orWindows Client.

host_profile.domain_name

string - Number ofcharacters:

• Workgroup:1 to 15characters

• Domain: 1 to155characters

Availablecharacters: ASCIIcharacters, single-byte blankProhibitedcharacters:

• Workgroup:"" * + , : ; <= > ? ¥ | ",

• Domain:Single-byteblank, ""* , / : ; < > ?[ ¥ ] |"

ssc.defaults.hostProfile.domainName

Workgroup name or domainnameThis can be specified when theOS type is Windows Server orWindows Client.

host_profile.domain_user

string △ 1 to 255 charactersAvailablecharacters: ASCIIcharacters, single-byte blankProhibitedcharacters: "" *+ , / : ; < = > ? [ ¥ ]|"

- Domain accountThis can be specified whendomain_type is domain.This can be specified when theOS type is Windows Server orWindows Client.* This must be specified ifdomain_type is domain.

host_profile.domain_pass

string △ 1 to 256 charactersAvailablecharacters: ASCII

- Domain passwordThis can be specified whendomain_type is domain.


71


d


Description

characters, single-byte blankProhibitedcharacters: "" ,"

This can be specified when theOS type is Windows Server orWindows Client.* This must be specified ifdomain_type is domain.

host_profile.license_mode

string - • PerServer:Number ofserversconnectedsimultaneously

• PerSeat:Connectedclients

ssc.defaults.hostProfile.licenseMode

License modeThis can be specified when theOS type is Windows Server.

host_profile.max_connection

integer - Valid range of theindex: 1 to 99999

ssc.defaults.hostProfile.maxConnection

Number of servers connectedsimultaneouslyThis can be specified when theOS type is Windows Server.This can be specified whenlicense_mode is PerServer.* Specify it in decimal notation.Even if you set a valuecontaining a decimal point, thevalue is truncated to a wholenumber.

host_profile.domain_suffix

string - 1 to 63 charactersAvailablecharacters: ASCIIcharactersProhibitedcharacters: "" # $& ' ( ) ; < > ¥ ` | "

ssc.defaults.hostProfile.domainSuffix

Domain suffix* This can be specified when theOS type is Linux.

*1 You cannot specify functions other than get_param or dummy parameters.*2 You cannot specify functions other than get_param and get_resource or dummy parameters.*3 The administrator account name of the server created with the vDCA SE Topology Template

Orchestrator Option on the OS type of the VM template specified for the image.- If the OS type is Windows Server or Windows Client, the value of the

ssc.defaults.hostProfile.adminAccountWindows key in ssc_plugin.conf (Administrator bydefault) is set.

- If the OS type is Linux, the value of the ssc.defaults.hostProfile.adminAccountLinux key inssc_plugin.conf (root by default) is set.

Note- The use of models is not supported.

If you omit the specification of a property in the topology template, the operation group settinginformation is checked, but the model information is not checked.

- The use of a root resource pool whose type is shared is not supported.


72

- The use of a VM template profile is not supported.* If the specification of the image property is omitted in the topology template and nothing is

set for the [Software] of the operation group, an error occurs.* If the specification of the host_profile property is omitted in the topology template and

nothing is set for the profile of the operation group, the value in the configuration file isreferenced.

- If a server whose OS type is Linux is to be created, only the first piece of DNS information forthe network specified for the networks[ ].network property is used.

- If the specification of the image property is omitted, an image that matches the VM templatename that is set in the operation group is found from the configuration file, and the informationfor the flavor available to the found VM template is acquired. If multiple images are registeredwith the same VM template name in the configuration file, the first image is found.

- If you want to specify a tag for a property value, specify a tag of the same type as that of theproperty.

• Attribute

Table B-9 NEC::SSC::Server attribute

Name Description

group Path of the operation group that has created a server

name Host name

resource_pool Resource pool

flavor Flavor

flavor.id Flavor ID

image Image

image.id Image ID

disks Extended disk list

disks[ ].size Disk size (MB)

disks[ ].profile Disk profile ID

networks.<network> Logical network

networks.<network>.index NIC number

networks.<network>.addresses IP address list

networks.<network>.addresses[ ].addr IP addressFor DHCP allocation, a string "DHCP"

networks.<network>.addresses[ ].version IP version• ipv4• ipv6

networks.<network>.addresses[ ].management Whether the address is a management address

host_profile Host profile

host_profile.admin_user Administrator user account

host_profile.admin_pass Password for the administrator user account

host_profile.owner User name to set on the OS

host_profile.organization Organization to which the user to set on the OSbelongs


73

Name Description

host_profile.timezone OS timezone

host_profile.product_key OS product key

host_profile.domain_type Workgroup or domain

host_profile.domain_name Workgroup name or domain name

host_profile.domain_user Domain account

host_profile.domain_pass Domain password

host_profile.license_mode License mode

host_profile.max_connection Number of servers connected simultaneously

host_profile.domain_suffix Domain suffix

host_profile.os_type OS type

NoteThe extended disk may be different from the actual one.

B.3.3 outputs sectionThe outputs section is used to define the output parameters that a user can use after creating a stack.

By using an intrinsic function such as get_attr, you can output values.

B.3.3.1 Data structure of the outputs section

outputs: <parameter name>: description: <description> value: <parameter value> condition: <condition name or expression or boolean>

Table B-10 outputs section

Name Description

parameter name Output parameter name[Required]

description Description of the output parameter

parameter value Value of the output parameter

condition Defines the output parameter conditionally.If the condition is False, no value is displayed.

B.4 Intrinsic functionsThe supported intrinsic functions differ depending on the topology template version.

The following table shows versions and the intrinsic functions supported by the versions.


74

Table B-11 Available versions

Function 2013-05-23 2014-10-16 2015-04-30 2015-10-15 2016-04-08

get_attr ○ ○ ○ ○ ○

get_param ○ ○ ○ ○ ○

get_resource ○ ○ ○ ○ ○

list_join ○ ○ ○ ○ ○

str_replace ○ ○ ○ ○ ○

Fn::Base64 ○

Fn::Join ○

Fn::MemberListToMap ○

Fn::Replace ○

Fn::Select ○ ○ ○

Fn::Split ○

Ref ○

repeat ○ ○ ○

digest ○ ○ ○

str_split ○ ○

map_merge ○

B.4.1 get_attrThe get_attr function references an attribute of an instantiated resource.

get_attr: - <resource name> - <attribute name> - <key/index 1> (optional) - <key/index 2> (optional) - ...

Table B-12 get_attr

Name Description

resource name Resource name defined in the resources section[Required]

attribute name Attribute name to reference[Required]

key/index If the attribute is a list or hash, specify the key or index for acquiring thedata.

Setting example

resources: server1: type: NEC::SSC::Server # ...

outputs:


75

server1_networks: description: networks of server1 value: { get_attr: [server1, networks] }

B.4.2 get_paramThe get_param function references the input parameter defined in the parameters section of thetemplate.

get_attr: - <parameter name> - <key/index 1> (optional) - <key/index 2> (optional) - ...

Table B-13 get_param

Name Description

parameter name Input parameter name defined in the parameters section[Required]

key/index If the input parameter defined in the parameters section is a list or hash,specify the key or index for acquiring the data.

Setting example

parameters: net_name: type: string description: name of logical network to be created

resources: net1: type: NEC::SSC::Net properties: name: { get_param: net_name } # ...

B.4.3 get_resourceThe get_resource function references the resource defined in the same template.

It returns the resource ID defined for each resource type.

get_resource: <ID in template>

Table B-14 get_resource

Name Description

ID in template Unique ID in the topology template defined in the resources section[Required]

Setting example

resources: net1: type: NEC::SSC::Net


76

properties: ...

server1: type: NEC::SSC::Server properties: ... networks: - network: { get_resource: net1 }

B.4.4 list_joinThe list_join function joins the elements of a list with the specified delimiting character and returns asingle string.

list_join:- <delimiter>- <list to join>

Table B-15 list_join

Name Description

delimiter Delimiting character[Required]

list to join List to be concatenated[Required]

Setting example

list_join: [', ', ['one', 'two', 'and three']]

Returns "one, two, and three".

B.4.5 str_replaceThe str_replace function searches for the string to replace and replaces it with the specified string.

str_replace: template: <template string> params: <parameter mappings>

Table B-16 str_replace

Name Description

template String to replace[Required]

params Replacement string mapping (key: Search string, value: Replacement string)[Required]

B.4.6 repeatThe repeat function replaces the key value defined in the template argument with the datacorresponding to the key and value (list) defined for the for_each argument.


77

repeat: template: <template> for_each: <var>: <list>

Table B-17 repeat

Name Description

template Define it by using a key that can be replaced during execution.[Required]

for_each For <var>, set a key that can be replaced in template:. For <list>, set thereplacement value (list).* If multiple key and value pairs are specified, this is executed repeatedlyfor all the values of the specified list.* You can specify the <list> value with the get_attr function, get_paramfunction, and so on.[Required]

B.4.7 digestThe digest function returns the hash value corresponding to the specified value.

digest: - <algorithm> - <value>

Table B-18 digest

Name Description

algorithm Digest algorithmA valid algorithm is an algorithm provided by hashlib (md5, sha1, sha224,sha256, sha384, sha512) or OpenSSL.[Required]

value Value[Required]

Setting example

# from a user supplied parameterpwd_hash: { digest: ['sha512', { get_param: raw_password }] }

B.4.8 str_splitThe str_split function splits a string into a list with the specified delimiting character.

str_split: [<delimiter> , <string>]

• Parameters

- delimiter: Delimiting character

- string: String

• Setting example


78

str_split: - ',' - string,to,split

OR

str_split: [',', 'string,to,split']

As with get_attr/get_param, you can specify the index for selecting a specific entry from the resultlist. Start the index with 0.

str_split: [',', 'string,to,split', 0]

B.4.9 map_mergeThe map_merge function merges maps. If there are multiple same keys, a key value is overwrittenwith a value of the latter key.

map_merge:- <map 1>- <map 2>- ...

Setting example

map_merge: [{'k1': 'v1', 'k2': 'v2'}, {'k1': 'v2'}]

Returns "{'k1': 'v2', 'k2': 'v2'}".

B.4.10 RefThe Ref function returns the value of the specified parameter or resource.

{Ref: <name>}

• Parameter

- name: Resource name or parameter

• Setting example

{Ref: my_server}

B.4.11 Fn::Base64The Fn::Base64 function converts the specified character string into Base64.

{"Fn::Base64": <value>}

• Parameter

- value: Character string to be converted

• Setting example

{"Fn::Base64": "convert this string please."}


79

B.4.12 Fn::JoinThe Fn::Join function joins the elements of a list with the specified delimiting character into a singlestring.

{Fn::Join: [<delimiter> , <list>]}

• Parameters


- list: List to be concatenated

• Setting example

{Fn::Join: [",", ["beer", "wine", "more beer"]]}

Returns "beer, wine, more beer".

B.4.13 Fn::SelectThe Fn::Select function selects an item from a list or hash.

{ "Fn::Select" : [<selector> , <collection>]}

• Parameters

- selector: List index or hash key name

- collection: List or hash for selecting an item

• Setting example

For List

{ "Fn::Select" : [ "2", [ "apples", "grapes", "mangoes" ] ] }

Returns "mangoes".

For Map

{ "Fn::Select" : [ "red", {"red": "a", "flu": "b"} ] }

Returns "a".

B.4.14 Fn::SplitThe Fn::Split function splits a string into a list with the specified delimiting character.

{ "Fn::Split" : [ <delimiter> , <string>]}

• Parameters


- string: String

• Setting example

{ "Fn::Split" : [ ",", "str1,str2,str3,str4"]}

Returns "{["str1", "str2", "str3", "str4"]}".


80

B.4.15 Fn::ReplaceThe Fn::Replace function searches for the string to replace and replaces it with the specified string.

{"Fn::Replace": [<substitutions> , <string>]}

• Parameters

- substitutions: Replacement string mapping (key: Search string, value: Replacement string)

- string: String to replace

• Setting example

{"Fn::Replace": [ {'$var1': 'foo', '%var2%': 'bar'}, '$var1 is %var2%']}

Returns ""foo is bar"".

B.4.16 Fn::MemberListToMapThe Fn::MemberListToMap function converts an AWS-style member list into a map.

{'Fn::MemberListToMap': [<key name> , <value name> , <list>]}

• Parameters

- key name: Key name

- value name: Value

- list: String list

• Setting example

{'Fn::MemberListToMap': ['Name', 'Value', ['.member.0.Name=key', '.member.0.Value=door', '.member.1.Name=colour', '.member.1.Value=green']]}

Returns "{'key': 'door', 'colour': 'green'}".


81

Appendix C. Dependent LibrariesThis chapter describes the OpenStack and RabbitMQ dependent libraries.

C.1 Dependent librariesThe following tables show the dependent libraries in Red Hat Enterprise Linux 7.3.

Table C-1 httpd

Package Dependent packages

httpd-2.4.6-40.el7.x86_64 apr-1.4.8-3.el7.x86_64.rpm

apr-util-1.5.2-6.el7.x86_64.rpm

httpd-2.4.6-40.el7.x86_64.rpm

httpd-tools-2.4.6-40.el7.x86_64.rpm

mailcap-2.1.41-2.el7.noarch.rpm

mod_wsgi-3.4-12.el7_0.x86_64.rpm

Table C-2 mod_wsgi


mod_wsgi-3.4-12.el7_0.x86_64 apr-1.4.8-3.el7.x86_64.rpm

apr-util-1.5.2-6.el7.x86_64.rpm

httpd-2.4.6-40.el7.x86_64.rpm

httpd-tools-2.4.6-40.el7.x86_64.rpm

mailcap-2.1.41-2.el7.noarch.rpm

Table C-3 memcached


memcached-1.4.25-1.el7.x86_64 libevent-2.0.21-4.el7.x86_64.rpm

memcached-1.4.25-1.el7.x86_64.rpm

perl-5.16.3-291.el7.x86_64.rpm

perl-Carp-1.26-244.el7.noarch.rpm

perl-Encode-2.51-7.el7.x86_64.rpm

perl-Exporter-5.68-3.el7.noarch.rpm

perl-File-Path-2.09-2.el7.noarch.rpm

perl-File-Temp-0.23.01-3.el7.noarch.rpm

perl-Filter-1.49-3.el7.x86_64.rpm

perl-Getopt-Long-2.40-2.el7.noarch.rpm

perl-HTTP-Tiny-0.033-3.el7.noarch.rpm

perl-PathTools-3.40-5.el7.x86_64.rpm

perl-Pod-Escapes-1.04-292.el7.noarch.rpm

perl-Pod-Perldoc-3.20-4.el7.noarch.rpm

Appendix C. Dependent Libraries

82


perl-Pod-Simple-3.28-4.el7.noarch.rpm

perl-Pod-Usage-1.63-3.el7.noarch.rpm

perl-Scalar-List-Utils-1.27-248.el7.x86_64.rpm

perl-Socket-2.010-4.el7.x86_64.rpm

perl-Storable-2.45-3.el7.x86_64.rpm

perl-Text-ParseWords-3.29-4.el7.noarch.rpm

perl-Time-HiRes-1.9725-3.el7.x86_64.rpm

perl-Time-Local-1.2300-2.el7.noarch.rpm

perl-constant-1.27-2.el7.noarch.rpm

perl-libs-5.16.3-292.el7.x86_64.rpm

perl-macros-5.16.3-292.el7.x86_64.rpm

perl-parent-0.225-244.el7.noarch.rpm

perl-podlators-2.5.1-3.el7.noarch.rpm

perl-threads-1.87-4.el7.x86_64.rpm

perl-threads-shared-1.43-6.el7.x86_64.rpm

Table C-4 python-memcached


python-memcached-1.54-3.el7.noarch python-memcached-1.54-3.el7.noarch.rpm

Table C-5 python_pip


python_pip python-pip-8.1.2-1.el7.noarch python-pip-8.1.2-1.el7.noarch.rpm

python2-setuptools-22.0.5-1.el7.noarch.rpm

Table C-6 python-openstackclient


python-openstackclient-2.2.0-1.el7.noarch PyYAML-3.10-11.el7.x86_64.rpm

libyaml-0.1.4-11.el7_0.x86_64.rpm

pyparsing-2.0.7-1.el7.noarch.rpm

python-backports-1.0-8.el7.x86_64.rpm

python-backports-ssl_match_hostname-3.4.0.2-4.el7.noarch.rpm

python-cliff-2.0.0-2.5dc9b9agit.el7.noarch.rpm

python-cliff-tablib-1.1-3.el7.noarch.rpm

python-cmd2-0.6.8-8.el7.noarch.rpm

python-crypto-2.6.1-1.el7.x86_64.rpm

python-extras-0.0.3-2.el7.noarch.rpm

python-fixtures-3.0.0-2.el7.noarch.rpm

python-jsonschema-2.3.0-1.el7.noarch.rpm


83


python-keyring-5.7.1-1.el7.noarch.rpm

python-keystoneclient-2.3.2-1.el7.noarch.rpm

python-linecache2-1.0.0-1.el7.noarch.rpm

python-mimeparse-0.1.4-1.el7.noarch.rpm

python-monotonic-0.6-1.el7.noarch.rpm

python-msgpack-0.4.6-3.el7.x86_64.rpm

python-netaddr-0.7.18-1.el7.noarch.rpm

python-netifaces-0.10.4-3.el7.x86_64.rpm

python-openstackclient-2.2.0-1.el7.noarch.rpm

python-pbr-1.8.1-2.el7.noarch.rpm

python-prettytable-0.7.2-3.el7.noarch.rpm

python2-requests-2.11.1-1.el7.noarch.rpm

python-simplejson-3.5.3-5.el7.x86_64.rpm

python-tablib-0.10.0-1.el7.noarch.rpm

python-testtools-1.8.0-2.el7.noarch.rpm

python-traceback2-1.4.0-2.el7.noarch.rpm

python-unicodecsv-0.14.1-1.el7.noarch.rpm

python-unittest2-1.0.1-1.el7.noarch.rpm

python2-urllib3-1.16-1.el7.noarch.rpm

python-warlock-1.0.1-1.el7.noarch.rpm

python-webob-1.4.1-2.el7.noarch.rpm

python-wrapt-1.10.8-2.el7.x86_64.rpm

python2-appdirs-1.4.0-4.el7.noarch.rpm

python2-babel-2.3.4-1.el7.noarch.rpm

python2-cinderclient-1.6.0-2.el7.noarch.rpm

python2-debtcollector-1.3.0-1.el7.noarch.rpm

python2-funcsigs-0.4-2.el7.noarch.rpm

python2-glanceclient-2.0.1-2.el7.noarch.rpm

python2-iso8601-0.1.11-1.el7.noarch.rpm

python2-jsonpatch-1.14-1.el7.noarch.rpm

python2-jsonpointer-1.10-4.el7.noarch.rpm

python2-keystoneauth1-2.4.3-1.el7.noarch.rpm

python2-neutronclient-4.1.2-1.el7.noarch.rpm

python2-novaclient-3.3.2-1.el7.noarch.rpm

python2-openstacksdk-0.8.3-1.el7.noarch.rpm

python2-os-client-config-1.16.0-1.el7.noarch.rpm

python2-oslo-config-3.9.0-1.el7.noarch.rpm

python2-oslo-i18n-3.5.0-1.el7.noarch.rpm


84


python2-oslo-serialization-2.4.0-2.el7.noarch.rpm

python2-oslo-utils-3.8.0-2.el7.noarch.rpm

python2-positional-1.0.1-1.el7.noarch.rpm

python2-pysocks-1.5.6-3.el7.noarch.rpm

python2-requestsexceptions-1.1.3-1.el7.noarch.rpm


python2-stevedore-1.12.0-2.el7.noarch.rpm

pytz-2016.10-2.el7.noarch.rpm

Table C-7 rabbitmq-server


rabbitmq-server-3.6.2-3.el7.noarch erlang-asn1-18.3.4.4-2.el7.x86_64.rpm

erlang-compiler-18.3.4.4-2.el7.x86_64.rpm

erlang-crypto-18.3.4.4-2.el7.x86_64.rpm

erlang-eldap-18.3.4.4-2.el7.x86_64.rpm

erlang-erts-18.3.4.4-2.el7.x86_64.rpm

erlang-hipe-18.3.4.4-2.el7.x86_64.rpm

erlang-inets-18.3.4.4-2.el7.x86_64.rpm

erlang-kernel-18.3.4.4-2.el7.x86_64.rpm

erlang-mnesia-18.3.4.4-2.el7.x86_64.rpm

erlang-os_mon-18.3.4.4-2.el7.x86_64.rpm

erlang-otp_mibs-18.3.4.4-2.el7.x86_64.rpm

erlang-public_key-18.3.4.4-2.el7.x86_64.rpm

erlang-runtime_tools-18.3.4.4-2.el7.x86_64.rpm

erlang-sasl-18.3.4.4-2.el7.x86_64.rpm

erlang-sd_notify-0.1-9.el7.x86_64.rpm

erlang-snmp-18.3.4.4-2.el7.x86_64.rpm

erlang-ssl-18.3.4.4-2.el7.x86_64.rpm

erlang-stdlib-18.3.4.4-2.el7.x86_64.rpm

erlang-syntax_tools-18.3.4.4-2.el7.x86_64.rpm

erlang-tools-18.3.4.4-2.el7.x86_64.rpm

erlang-xmerl-18.3.4.4-2.el7.x86_64.rpm

lksctp-tools-1.0.17-2.el7.x86_64.rpm

rabbitmq-server-3.6.2-3.el7.noarch.rpm

Table C-8 openstack_selinux


openstack-selinux-0.7.2-1.el7.noarch audit-libs-python-2.7.6-3.el7.x86_64.rpm

checkpolicy-2.5-4.el7.x86_64.rpm


85


libcgroup-0.41-13.el7.x86_64.rpm

libsemanage-python-2.5-8.el7.x86_64.rpm

openstack-selinux-0.7.2-1.el7.noarch.rpm

policycoreutils-python-2.5-17.1.el7.x86_64.rpm

python-IPy-0.75-6.el7.noarch.rpm

setools-libs-3.3.8-1.1.el7.x86_64.rpm

Table C-9 openstack-keystone


openstack-keystone-9.0.2-1.el7.noarch MySQL-python-1.2.5-1.el7.x86_64.rpm

PyPAM-0.5.0-19.el7.x86_64.rpm

PyYAML-3.10-11.el7.x86_64.rpm

libyaml-0.1.4-11.el7_0.x86_64.rpm

openstack-keystone-9.0.2-1.el7.noarch.rpm

python-alembic-0.8.7-1.el7.noarch.rpm

python-amqp-1.4.6-1.el7.noarch.rpm

python-anyjson-0.3.3-3.el7.noarch.rpm



python-beaker-1.5.4-10.el7.noarch.rpm

python-cachetools-1.0.3-2.el7.noarch.rpm

python-contextlib2-0.4.0-1.el7.noarch.rpm


python-dogpile-cache-0.5.7-3.el7.noarch.rpm

python-dogpile-core-0.4.1-2.el7.noarch.rpm

python-editor-0.4-4.el7.noarch.rpm



python-futures-3.0.3-1.el7.noarch.rpm

python-inotify-0.9.4-4.el7.noarch.rpm

python-jinja2-2.7.2-2.el7.noarch.rpm



python-keystone-9.0.2-1.el7.noarch.rpm


python-keystonemiddleware-4.4.1-1.el7.noarch.rpm

python-kombu-3.0.32-1.el7.noarch.rpm

python-ldap-2.4.15-2.el7.x86_64.rpm


86


python-ldappool-1.0-4.el7.noarch.rpm


python-mako-0.8.1-2.el7.noarch.rpm

python-markupsafe-0.11-10.el7.x86_64.rpm

python-memcached-1.54-3.el7.noarch.rpm

python-migrate-0.10.0-1.el7.noarch.rpm






python2-oauthlib-2.0.1-8.el7.noarch.rpm

python-paste-1.7.5.1-9.20111221hg1498.el7.noarch.rpm


python-posix_ipc-0.9.8-1.el7.x86_64.rpm


python-pycadf-common-2.2.0-1.el7.noarch.rpm

python-repoze-lru-0.4-3.el7.noarch.rpm

python-repoze-who-2.1-1.el7.noarch.rpm


python-retrying-1.2.3-4.el7.noarch.rpm

python-routes-1.13-2.el7.noarch.rpm

python-sqlalchemy-1.0.11-1.el7.x86_64.rpm

python-sqlparse-0.1.18-5.el7.noarch.rpm

python-tempita-0.5.1-8.el7.noarch.rpm







python-zope-interface-4.0.5-4.el7.x86_64.rpm

python2-PyMySQL-0.7.9-2.el7.noarch.rpm



python2-eventlet-0.17.4-4.el7.noarch.rpm

python2-fasteners-0.14.1-6.el7.noarch.rpm



87


python2-futurist-0.13.0-1.el7.noarch.rpm

python2-greenlet-0.4.9-1.el7.x86_64.rpm



python2-oslo-cache-1.6.0-1.el7.noarch.rpm

python2-oslo-concurrency-3.7.1-3.el7.noarch.rpm


python2-oslo-context-2.2.0-2.el7.noarch.rpm

python2-oslo-db-4.7.1-1.el7.noarch.rpm


python2-oslo-log-3.3.0-1.el7.noarch.rpm

python2-oslo-messaging-4.6.1-1.el7.noarch.rpm

python2-oslo-middleware-3.8.1-1.el7.noarch.rpmm

python2-oslo-policy-1.6.0-1.el7.noarch.rpm


python2-oslo-service-1.8.0-1.el7.noarch.rpm


python2-passlib-1.7.0-4.el7.noarch.rpm

python2-pika-0.10.0-3.el7.noarch.rpm

python2-pika_pool-0.1.3-3.el7.noarch.rpm


python2-pycadf-2.2.0-1.el7.noarch.rpm

python2-pysaml2-3.0.2-2.el7.noarch.rpm





Table C-10 openstack-heat-api


openstack-heat-api-6.0.0-1.el7.noarch MySQL-python-1.2.5-1.el7.x86_64.rpm


libyaml-0.1.4-11.el7_0.x86_64.rpm

openstack-heat-api-6.0.0-1.el7.noarch.rpm

openstack-heat-common-6.0.0-1.el7.noarch.rpm






88






python-ceilometerclient-2.4.0-1.el7.noarch.rpm




python-croniter-0.3.4-2.el7.noarch.rpm




python-ecdsa-0.11-3.el7.noarch.rpm





python-httplib2-0.9.2-1.el7.noarch.rpm


















python-osprofiler-1.2.0-1.el7.noarch.rpm

python-paramiko-1.15.1-1.el7.noarch.rpm



89


python-paste-deploy-1.5.2-6.el7.noarch.rpm




python2-psutil-5.0.1-2.el7.x86_64.rpm


python-qpid-0.30-1.el7.noarch.rpm

python-qpid-common-0.30-1.el7.noarch.rpm




























python2-heatclient-1.1.1-1.el7.noarch.rpm




90




python2-mock-1.3.0-2.el7.noarch.rpm














python2-oslo-reports-1.7.0-1.el7.noarch.rpm




python2-oslo-versionedobjects-1.8.0-1.el7.noarch.rpm







python2-saharaclient-0.14.1-1.el7.noarch.rpm



python2-swiftclient-3.0.0-3.el7.noarch.rpm

python2-troveclient-2.1.2-2.el7.noarch.rpm


Table C-11 openstack-heat-engine


openstack-heat-engine-6.0.0-1.el7.noarch MySQL-python-1.2.5-1.el7.x86_64.rpm


libyaml-0.1.4-11.el7_0.x86_64.rpm


91


openstack-heat-common-6.0.0-1.el7.noarch.rpm

openstack-heat-engine-6.0.0-1.el7.noarch.rpm









python-ceilometerclient-2.4.0-1.el7.noarch.rpm




python-croniter-0.3.4-2.el7.noarch.rpm




python-ecdsa-0.11-3.el7.noarch.rpm





python-httplib2-0.9.2-1.el7.noarch.rpm
















92





python-osprofiler-1.2.0-1.el7.noarch.rpm

python-paramiko-1.15.1-1.el7.noarch.rpm


python-paste-deploy-1.5.2-6.el7.noarch.rpm




python2-psutil-5.0.1-2.el7.x86_64.rpm


python-qpid-0.30-1.el7.noarch.rpm

python-qpid-common-0.30-1.el7.noarch.rpm


























93





python2-heatclient-1.1.1-1.el7.noarch.rpm





python2-mock-1.3.0-2.el7.noarch.rpm














python2-oslo-reports-1.7.0-1.el7.noarch.rpm




python2-oslo-versionedobjects-1.8.0-1.el7.noarch.rpm







python2-saharaclient-0.14.1-1.el7.noarch.rpm



python2-swiftclient-3.0.0-3.el7.noarch.rpm

python2-troveclient-2.1.2-2.el7.noarch.rpm


94



Table C-12 openstack-utils


openstack-utils-2015.2-1.el7.noarch crudini-0.7-1.el7.noarch.rpm

openstack-utils-2015.2-1.el7.noarch.rpm


95

GlossaryAlphabet

■ D

■ Disk profileCombination of a disk type and a datastore tag set to SigmaSystemCenter. In vDCA SE Portal, this iscalled a disk tag.

■ F

■ FlavorCombination of the number of CPUs, memory size, and system disk size. In vDCA SE Portal, this iscalled spec.

■ I

■ ImageCombination of a VM template name and spec. In vDCA SE Portal, this is called a catalog.

■ L

■ Logical networkLogical network to be used on a virtual machine.

■ M

■ MySQLOpen-source SQL database management system provided by Oracle Corporation. vDCA SETopology Template Orchestrator Option uses MySQL as a database to store system configurationinformation.

■ O

■ OpenStack Identity(keystone)One of the components making up vDCA SE Topology Template Orchestrator Option.

This is used to receive an authentication request from vDCA SE Portal and an OpenStackOrchestration (such as heat-api and heat-engine).

96

■ OpenStack Orchestration(heat-api)One of the components making up

vDCA SE Topology Template Orchestrator Option.

This is used to receive a stack creation or deletion request from vDCA SE Portal.

■ OpenStack Orchestration(heat-engine)One of the components making up vDCA SE Topology Template Orchestrator Option.

This is used to receive a stack creation or deletion request from an OpenStack Orchestration(heat-api)via RabbitMQ.

■ S

■ SSC resource plug-inProvides the functions to create, delete, and browse a logical network and server and monitor forresources managed by SigmaSystemCenter, which is a vDCA SE plug-in for OpenStack Heat.

■ StackIndicates a group of components (server and network) making up an IT system.

■ T

■ Topology templateIn

vDCA SE Topology Template Orchestrator Option, a topology template means a Heat Orchestrationtemplate (HOT template).This is a text file in which resources making up the stack and their relationship are defined.

■ R

■ RabbitMQOne of the components making up vDCA SE Topology Template Orchestrator Option.

This is used to manage messages from an OpenStack Orchestration(heat-api).

■ Resource poolGroup of the physical total number of storage, CPU, and memory resources on multiple managedVM servers. If necessary, the required resources can be moved from a resource pool to a sub resourcepool.

97

■ RESTful APIAPI to identify a resource by URL/URI and achieve stateless interactions with a Web server

■ V

■ Virtual machineIndicates a machine that is virtually realized on a virtual machine server. The abbreviation is VM.

■ VMStands for "virtual machine." See "Virtual machine."

■ VM templateTemplate of a virtual machine that a tenant can use from a service catalog.

98

MasterScope Virtual DataCenter Automation Standard EditionTopology TemplateOrchestrator Option

User's Guide

March, 2018 1 Edition

NEC Corporation

©NEC Corporation 2017-2018

Documents

MasterScope Virtual DataCenter Automation Standard ... · • OpenStack Orchestration(heat-api) - Component for accepting a stack creation or deletion request from the management