1.7. Deployment Manager


1.7.1. Overview of menu (common)

1.7.1.1. Service Menu Overview

This menu enable customers to create, edit and delete the Enteprise Cloud 2.0 each resources easily.
A collection of resources to create is called the “Stack” and customers can create stack-based system.
You can defines a system configuration in order to build a stack called “Template”, which apply to the Deployment Manager to manage creating and deleting whole system at once.

1.7.1.2. Service Menu Features

Feature of this menu as follows:


1. Build system with servers, storage and network menu by using one configuration file.

Dependence relationship of Resources is able to be written in Template, configuration order is controlled like “First, boot the server and connect Volume.”
A system with a complicated configuration can also be constructed simply by executing a template.
Utilizing the stored template can reduce the operation cost in cases where there are many restructuring such as develop environment.
Customer can reduce the construction operation time which had traditionally configure each resource and input various settings via portal.

2. No Charge

Following image shows how Customers can utilize this feature.

利用イメージ

1.7.2. Available Functions

1.7.2.1. List of Functions

The functions available on Deployment Manager are follows;

Functions

Overview

Stack management

It is a function to create, edit and delete a stack which is a collection of resources to be created.

Operating resource type.

Feature to check available resource type.

Generate template

Generate template from GUI.


1.7.2.2. Description of Functions

Description of each function on Deployment Manager is below.


1.7.2.3. Stack management

Detailed Function

Description

Stack list

Display a list of Stack

Stack Detail

Display detail information of Stack.
Display configuration information of Stack as Network diagram.
Display a list of Resource in Stack.
Display a list of Event in Stack.
Display the template information Stack uses.

Create Stack

Use HOT format template and create resource in accordance with Stack and template.
Rollback function : If failed creating some resource when creating Stack, make resource back to the state before creating Stack by deleting resourse already created.

Edit Stack

Add resources, delete some resources, change Property, etc. on the created stack.

Preview Stack

Use HOT format template and create Stack in dry run.(Actual resources are not created.)

Check Stacks

Conduct a test with regard to creating Stack.
Check the Resource status in Stack.

Delete Stacks

Delete Stack and the resources inside of it.

Abandon Stack

Create only Stack compulsory and never influence inside of resource.
Use in order to dissociate Stack from Resource compulsory in case if Stack become in error status and inoperable and son on.

Resource Detail

Move from the list of resources
Display the detail information of Resource.

1.7.2.4. Status transition of Stack

The each operations to Stack are managed by following state transitions.

Operation / State transition

IN_PROGESS COMPLETE FAILED

ABANDON

ABANDON_IN_PROGRESS    
CHECK CHECK_IN_PROGRESS CHECK_COMPLETE CHECK_FAILED
CREATE CREATE_IN_PROGRESS CREATE_COMPLETE CREATE_FAILED
UPDATE UPDATE_IN_PROGRESS UPDATE_COMPLETE UPDATE_FAILED
DELETE DELETE_IN_PROGRESS   DELETE_FAILED
ROLLBACK ROLLBACK_IN_PROGRESS   ROLLBACK_FAILED

ステータス遷移

1.7.2.5. Normal status of each resource

The status that is determined to be normal by the Stack checking function indicates the status of completing resource creation.

Resource type

Normal status

Notes

ECL::Compute::Server ACTIVE  
ECL::Compute::Volume available, in-use  
ECL::Compute::VolumeAttachment N/A

The status is not displayed.

ECL::Compute::Keypair N/A

The status is not displayed but check Keypair exists or not.

ECL::Baremetal::Server ACTIVE  
ECL::Baremetal::Keypair N/A

The status is not displayed but check Keypair exists or not.

ECL::Network::LogicalNetwork ACTIVE  
ECL::Network::Subnet ACTIVE  
ECL::Network::Port ACTIVE  
ECL::Network::Firewall ACTIVE  
ECL::Network::LoadBalancer ACTIVE  
ECL::Network::GatewayInterface ACTIVE  
ECL::Network::CommonFunctionGateway ACTIVE  
ECL::Network::InternetGateway ACTIVE  
ECL::Network::StaticRoute ACTIVE  
ECL::Network:PublicIP ACTIVE  
ECL::DH::Server ACTIVE  
ECL::DH::License N/A

The status is not displayed.

ECL::Rca::User N/A

The status is not displayed but check user exists or not.

ECL::Storage::VirtualStorage available  
ECL::Storage::Volume available  
OS::Nova::Server ACTIVE  
OS::Nova::Keypair N/A

The status is not displayed but check Keypair exists or not.

OS::Cinder::Volume available, in-use  
OS::Cinder::VolumeAttachment N/A

The status is not displayed.

ECL::DNS::Zone ACTIVE  
ECL::DNS::Record ACTIVE  

1.7.2.6. Operation related to resource type.

Detailed Function

Description

The list of resource type

Display a list of Resource types available for Stack.

Resource type detail

Display a list of Detail information of Resource types available for Stack.


1.7.2.7. The list of resource type available.

Resource type

Components

Available resource

ECL::Compute::Server

Virtual Server

Instance

ECL::Compute::Keypair

Virtual Server

Keypair for the instance

ECL::Compute::Volume

Virtual Server

Volume

ECL::Compute::VolumeAttachment

Virtual Server

Connection between instance and volume

ECL::Baremetal::Server

Baremetal Server

Baremetal Server

ECL::Baremetal::Keypair

Baremetal Server

Keypair for Baremetal Server

ECL::Network::LogicalNetwork

Network

Logical Network

ECL::Network::Subnet

Network

Subnet

ECL::Network::Port

Network

Port

ECL::Network::Loadbalancer

Network

Load Balancer

ECL::Network::LoadBalancer::Syslog::Server

Network

Syslog

ECL::Network::Firewall

Network

Firewall
※End of Sales as of July 1st, 2017.
ECL::Network::CommonFunctionGateway

Network

Common Function Gateway

ECL::Network::InternetGateway

Network

Internet Gateway

ECL::Network::GatewayInterface

Network

Gateway Interface (Internet Connectivity)

ECL::Network::StaticRoute

Network

Static route (Internet Connectivity)

ECL::Network::PublicIP

Network

Global IP address (Internet connectivity)

ECL::DH::Server

Dedicated hypervisor

Server

ECL::DH::License

Dedicated hypervisor

license

ECL::Rca::User

Remote Console Access

The user in Remote Console Access (Baremetal Server and Dedicated Hyper-Visor)

ECL::Storage::VirtualStorage

Storage Plane

Storage Plane

ECL::Storage::Volume

Storage Plane

Volume

ECL::DNS::Zone DNS

Zone

ECL::DNS::Record DNS

Record

OS::Nova::Server OpenStack Nova

Instance

OS::Nova::Keypair OpenStack Nova

Keypair for the instance

OS::Cinder::Volume OpenStack Cinder

Volume

OS::Cinder::VolumeAttachment OpenStack Cinder

Connection between instance and volume


1.7.2.8. Resource type those property can be changed

Resource type

Components

Property can be changed

ECL::Compute::Server
(OS::Nova::Server)

Virtual Server

name, flavor, networks, metadata, user_data, flavor_update_policy, user_data_update_policy
ECL::Compute::Volume
(OS::Cinder::Volume)

Virtual Server

size, name, description, metadata
ECL::Compute::VolumeAttachment

Virtual Server

instance_id, volume_id, device(mountpoint)
ECL::Network::LogicalNetwork

Network

name, description, admin_state_up, tags
ECL::Network::Subnet

Network

name, description, dns_nameservers, enable_dhcp, gateway_ip, host_routes, ntp_servers, tags
ECL::Network::Port

Network

name, admin_state_up, allowed_address_pairs, description, device_id, device_owner, fixed_ips, segmentation_type, segmentation_id, tags
ECL::Network::Loadbalancer

Network

description, load_balancer_plan_id, name, interface, default_gateway
ECL::Network::LoadBalancer::Syslog::Server

Network

acl_logging, appflow_logging, date_format, description, log_facility, log_level, priority, tcp_logging, time_zone, user_configurable_log_messages
ECL::Network::CommonFunctionGateway

Network

name, description
ECL::Network::InternetGateway

Network

description, name, qos_option_id
ECL::Network::GatewayInterface

Network

description, name
ECL::Network::PublicIP

Network

description
ECL::Storage::VirtualStorage

Storage Plane

name, description, ip_addr_pool, host_routes
ECL::Storage::Volume

Storage Plane

name, description, initiator_iqns
ECL::DNS::Zone DNS description
ECL::DNS::Record DNS name, description, ttl, record

1.7.2.9. Templates

In this menu template in HOT (Heat Orchestration Template) format is available.
In this menu, template version, 2016-04-08 is supported. Any other version is not available.
Template can be generated from GUI.
As shown below, it is possible to intuitively generate templates by dragging and dropping resources on the canvas.
The resources defined on canvas will be generated as template.
Template created from canvas is able to be saved as draft and has import/export function.

テンプレート作成1

テンプレート作成2

1.7.3. Menu


1.7.3.1. Menu / Plan

There is no plan in this menu.


1.7.3.2. Subscription Methods

Customers are not required to subscribe this menu. This service is available for every Customers who subscribe Enterprise Cloud 2.0.


1.7.4. Pricing


1.7.4.1. Initial Fee

There is no initial fee.


1.7.4.2. Monthly Fees

There is no monthly charge in this menu.


1.7.5. Quality of Service


1.7.5.1. Support Coverage

All functions provided by this service are supported. Designing and configuring Customers’ system architectures utilizing this function are not supported.


1.7.5.2. Qualities of Operations

Quality of Operation of this menu has been established as a standard on Enterprise Cloud 2.0.


1.7.5.3. Points to Note

  • There is no charge in using this menu, but Resources created when creating Stack are to be charged.

    • If the creation/update of the stack fails, the created resources will be charged.

    • If the deletion of the stack fails and the resources remain, the remaining resources will be charged.

    • If the resource deletion due to the rollback function fails and the resources remain, the remaining resources will be charged.

  • Even when customer uses the rollback function, depending on the condition, not all resources may be deleted.
    In such case, customer needs to execute discard the Stack and remove each resource individually.
  • If customer can not create a particular resource described in the template, customer will not be able to be created using the Deployment Manager. In addition, the creation of the Stack that contains the resource will fail.

  • When changing the stack configuration with the stack editing function, if you specify the stack to be changed incorrectly, the existing stack is deleted and a stack with the new configuration is created. Be careful not to mistake the selection of the stack to be changed when making changes to the running system configuration.


1.7.6. Restrictions


1.7.6.1. Restrictions: Stack

The restrictions related to create Stack are as follows:

Items

Restrictions

Details

The number of Stacks

30

The maximum number of Stacks that can be stored within the tenant is 30.

Template Size

512KB

The maximum size of template is 512KB.

Stack name

Within 255 characters.

Stack name needs to be in 255 characters and has following restrictions.

  • The first character need to be a - z A - Z

  • From the second character, a - z A - Z 0 - 9. - can be used.

  • Stack names can not duplicated within one tenants.

Resource name

A unique name in the Stack

Even if the resource type is different, the same resource name can not be defined in the Stack.

The number of resource

Upper creation limit for each resources

The maximum number of resources can be created in the Stack follows to the upper creation limit for each resources.


The restrictions of resource in the Stack are as follows;

Resource type

Restrictions

Details

ECL::Compute::Server 256

The upper limit of creating in one Stack is 256.

ECL::Compute::Keypair 100

The upper limit of creating in one Stack is 100.

ECL::Compute::VolumeAttachment

No limit

There is no upper limit inside of Stack, Volume which is able to attach per Instance is 10.

ECL::Compute::Volume 512

The upper limit of creating resource in one Stack is 512.

ECL::Baremetal::Server 30

The upper limit of creating resource in one Stack is 30.

ECL::Baremetal::Keypair 100

The upper limit of creating in one Stack is 100.

ECL::Network::LogicalNetwork 64

The upper limit of creating resource in one Stack is 64.

ECL::Network::Subnet 128

The upper limit of creating resource in one Stack is 128.

ECL::Network::Port 2048

The upper limit of creating resource in one Stack is 2048.

ECL::Network::Loadbalancer 16

The upper limit of creating resource in one Stack is 16.

ECL::Network::Firewall 16
The upper limit of creating resource in one Stack is 64.
※End of Sales as of July 1st, 2017.
ECL::Network::InternetGateway 4

The upper limit of creating resource in one Stack is 4.

ECL::Network::CommonFunctionGateway 1

The upper limit of creating resource in one Stack is 1.

ECL::Network::GatewayInterface

No limit

 
ECL::Network::StaticRoute

No limit

 
ECL::Network::PublicIP 4

The upper limit of creating resource in one Stack is 4.

ECL::DH::Server 30

The upper limit of creating resource in one Stack is 30.

ECL::DH::License

No limit

 
ECL::Rca::User

No limit

 
ECL::Storage::VirtualStorage

No limit

 
ECL::Storage::Volume

No limit

 
ECL::DNS::Zone

No limit

Although there is no maximum number of creations in the stack, the maximum number of zones that can be set per tenant in the DNS service specification is 100 zones.

ECL::DNS::Record

No limit

Although there is no maximum number of creations in the stack, the maximum number of records that can be set per tenant in the DNS service specification is 1000 records.


1.7.6.2. Restrictions: API

When creating, editing or deleting a stack, Deployment Manager creates / deletes resources of various services described in the template using your own authentication information (token), but its token is valid for only one hour.
Therefore, in some cases where stack creation / deletion processing is continued for a long time, such as cases where multiple resources are described in the template, token may be expired during creation.
To avoid such cases, Deployment Manager has function that enables creation of Stack over a long time by substituting token acquisition.
By inputting the API key and API secret key on the screen of Create Stack, Deployment Manager substitutes token acquisition. From this point, the Stack itself and its resource creation / deletion processing are continued using this token.
Please refer to following URL for API key and API secret key information; https://ecl.ntt.com/en/documents/tutorials/rsts/CustomerPortal/user_parameter.html