2.3.1 Cloud Preparations

In order to use Cloud Services Management, preparation of the integrated cloud vendors is necessary.

When using AWS, Azure, and K5, contracts must be arranged with cloud providers. When using ROR and VMware, the setup of cloud management software must be performed.
Resources in cloud environments must also be prepared, and the deployment of virtual machines enabled, depending on the service specifications to be released as menus.

In Cloud Services Management, contracts with cloud providers and information regarding cloud management software can be managed using Contract Management. The information required to deploy virtual machines is configured in the parameters for cloud vendor information.

Information Related to Contracts

The information managed using Contract Management is as shown below. Decide the details of this information with planners, and collect it beforehand.

Information Name	Required	Information to Prepare	Usage	Remarks
Contract Number	-	The ID, etc. that can be used by the cloud provider and cloud management software to identify a contract.	Enables easier determination of which contracts are linked to the contract of this product.	-
Vendor Portal ID	-	The ID used for logging in to the cloud provider portal	Displays the ID used for logging on to the portals of the cloud provider.	For AWS, Azure, and K5 only
Maintenance Service ID	-	The ID used for contacting the cloud provider	Displays the ID used for contacting the cloud provider.	For AWS, Azure, and K5 only

Configuration Required to Deploy Virtual Machines

Perform the following configuration in the integrated cloud and collect the information required to deploy virtual machines.

For details, refer to the published documents on individual cloud products.

For AWS
1. Sign up for AWS.
2. Create an IAM user.
  The access key (access key ID and secret access key) of an IAM user is required.
3. Create a subnet.
4. Create a Virtual Private Cloud(VPC).
  Cloud Services Management uses a local IP address to access deployed virtual machines. This operation is necessary for connecting using a local IP address.
5. Create a security group.
6. Confirm the information of the items to be specified in the vendor definition file. For details on these items, refer to "2.10.2 Cloud Vendor Information".
For Azure
1. Register the subscription file for connecting with Azure.
  For the procedure for adding subscription files, refer to "Configuring Azure Connection Information (Only when Performing Azure Coordination)" in the "FUJITSU Software Cloud Services Management Installation Guide".
2. Create a virtual network, subnets, affinity groups, and a storage account.
3. Confirm the information of the items to be specified in the vendor definition file. For details on these items, refer to "2.10.2 Cloud Vendor Information".
For ROR
1. Create tenants to use in Cloud Services Management.
2. Configure resources for the tenants.
3. Confirm the information of the items to be specified in the vendor definition file. For details on these items, refer to "2.10.2 Cloud Vendor Information".
4. Add and configure tenant users and tenant administrators, and then create an L-Platform template. Cloud Services Management associates each platform with a single L-Platform for management. Create an L-Platform template under the following conditions:
  - Prepare an L-Platform template for each serviceOption specified in the cloud vendor definition file (systemDiskImageOptions).
  - Define a single virtual machine only.
  - Define a single NIC only.
  - Set the same values as the parameters specified for serviceOption(COUNT_CPU/PROCESSORSPEED/MEMORYSIZE) in the cloud vendor definition file (instanceOptions). When defining multiple entries of instanceOptions in the cloud vendor definition file, set the parameter values for the first virtual machine to be deployed on the platform.
  - Set the same values as the parameters specified for serviceOption(DISKIMG_ID/NETWORK_ID/VSERVER_TYPE) in the cloud vendor definition file (systemDiskImageOptions).
  - Set the same value as the parameter specified for serviceOption(BLOCK_DEVICE_SIZE) in the cloud vendor definition file (dataDiskImageOptions).
  - Set the same value as the parameter specified for deployParameter(VM_POOL/STRAGE_POOL) in the cloud vendor definition file (deployParameters).
  - For the parameters in the L-Platform template other than the above, set the common values for each menu.
See
When ROR is operated using SVOM 6.10 or later, it is necessary to reconfigure the TLS/SSL communication settings used by SVOM.
For details, refer to "Configuring SVOM" in the "FUJITSU Software Cloud Services Management Installation Guide".
For K5
1. Create a K5 project to use in Cloud Services Management.
  In the new K5 project, add users to be used by Cloud Services Management to access K5.
  In addition, submit a request for increasing the maximum number of virtual machines available for use in the K5 project if necessary.
2. In the created project, create the following resources:
  - A virtual router
  - A virtual network/subnet
  - A security group
  Configure the virtual network so that it allocates IP addresses to virtual machines automatically.
  In addition, configure the virtual network so that it can be directly accessed from an internal network (an access source used by the platform providers when using virtual machines) using the private IP address of a virtual machine.
  Configure the security group so that it allows platform providers to use a remote desktop and SSH when using a virtual machine.
3. When using multiple K5 projects, repeat steps 1 and 2.
4. Confirm the information of the items to be specified in the vendor definition file. For details on these items, refer to "2.10.2 Cloud Vendor Information".
Note
When using multiple K5 projects, all of the networks to be created must belong to the same availability zone.
For VMware
1. Create a vCenter Server and a data center.
  Create clusters and folders if necessary.
2. Create resource pools and a datastore.
3. Using vSphere Client, create users to be used by Cloud Services Management for connecting using vSphere API.
  Allocate the following roles to the created users:
  - Virtual Machine (all roles)
  - Resource (allocation to the resource pool for virtual machines)
  - Datastore (area allocation)
4. Create a VMware template. For the number of NICs, specify "1".
5. Prepare the DHCP server on the virtual network where virtual machines are to be deployed.
6. Confirm the information of the items to be specified in the vendor definition file. For details on these items, refer to "2.10.2 Cloud Vendor Information".