Deploying virtual application patterns

After you create a virtual application, you can provision and deploy it to the cloud. You can deploy a virtual application multiple times and each deployment is a running virtual application instance on the cloud infrastructure.

1. Click Patterns > Virtual Application Patterns.
2. Click Deploy in the Actions column for the pattern that you want to deploy, or select the pattern that you want to deploy and click Deploy near the top of the details page.

On the Configure pane of the Deploy Pattern page:

3. Edit the name for the deployment, if needed.
4. Select the environment profile that you want to use for the deployment.
   • If the Deployment type for the selected environment profile is set to Single cloud:
     • Select a Cloud Group and an IP Group.
       Note: You can also set the IP group for each virtual machine on the Distribute pane. You cannot change the Cloud Group for the deployment after you configure it on this pane.
     • The deployment is limited to a single cloud group.
   • If the Deployment type for the selected environment profile is set to Multi cloud, you select the cloud group and IP group for the deployment later, on the Distribute pane.
5. Set the priority for the deployment.
   Note: For more information about deployment priorities, see the Related tasks.
6. If more than one operating system is supported for the pattern, select the Operating system family.
   If you chose a Windows image, enter the product key and password for the operating system. Specifying an invalid product key will result in errors with the deployment.

   Important: You must use a product key from a volume license.
7. Select the Base image to use for the deployment.
   Note: Only images with an operating system that is supported by the pattern are displayed in the list.
8. Optional: To set up SSH access, use one of the following options in the SSH Key section to set the public key:
   • To generate a key automatically, click Generate. Click Download to save the private key file to a secure location. The default name is id_rsa.txt.

     The system does not keep a copy of the private key. If you do not download the private key, you cannot access the virtual machine, unless you generate a new key pair. You can also copy and paste the public key into a text file to save the key. Then, you can reuse the same key pair for another deployment. When you have the private key, make sure that it has the correct permissions (chmod 0400 id_rsa.txt). By default, the SSH client does not use a private key file that provides open permission for all users.

   • To use an existing SSH public key, open the public key file in a text editor and copy and paste it into the SSH Key field.
     Important: Do not use cat, less, or more to copy and paste from a command shell. The copy and paste operation adds spaces to the key that prevent you from accessing the virtual machine.

   The SSH key provides access to the virtual machines in the cloud group for troubleshooting and maintenance purposes. For more information, see Related tasks.

9. Modify the deployment schedule as needed:
   • Choose Start now, or choose Start later and select a date and time for the deployment to start.
   • Choose Run indefinitely, or choose Run until and select a date and time for the deployment to end.
10. Modify the component attributes as needed.

    The attributes that display in the pattern configuration column are attributes from the components in the pattern that are not locked from editing. You can modify existing values or set values that were not specified during pattern creation. Be sure that all required fields have values. Components that have a blue dot next to the name contain required attributes that must be set before the pattern is deployed.

11. When you are finished configuring all of the fields on the Configure tab:
    • If you chose an environment profile that does not have the IP addresses provided by field set to Pattern Deployer and you do not want to modify the placement, click Quick Deploy. If you choose this option, the deployment process starts. You do not need to complete any of the subsequent steps.
    • If you chose an environment profile that has the IP addresses provided by field set to Pattern Deployer, or you want to modify the placement, click Prepare to Deploy.

On the Distribute pane:

The virtual machines in the deployment are placed in cloud groups by the system.

12. Optional: To modify the placement of the virtual machines, drag the virtual machines to different cloud groups.
    • If you drag a virtual machine cell that contains more than one virtual machine, you are prompted to select the number of virtual machines that you want to move. You must select the number from the list in the dialog. After you move a virtual machine to a different cell, the IP group assignments are set to default values. If needed, you can edit the virtual machine network settings in the next step to modify the IP group.
    • If you modify the placement of the virtual machines, the new placement is validated to ensure that the necessary resources and artifacts are available in the selected cloud group.
    • If there is a problem with the placement, a message is displayed. Resolve the issue with the placement before you continue.

      For example, if this message displays when you modify the placement: CWZKS7002E Insufficient memory to place the pattern, move the virtual machine to a different cloud group with sufficient memory resources for the pattern.

      If you see the error: Unable to assign to cloud group, there is an error with the location, cloud group, NIC or IP groups for the cell where the error is displayed. If this error message occurs, you must resolve the issue with that cell before you are allowed to drag a virtual machine to that cell for placement there. Move the mouse pointer over the error to display more details about the problem in a window.

13. Optional: To edit the network or volume settings for a virtual machine, move your mouse pointer over the virtual machine icon and click the pencil icon.
    1. On the IP Groups tab, you can modify the IP group for each of the NICs in the virtual machine. The IP groups that are listed are the IP groups that are associated with the environment profile that you chose for the deployment.
    2. If you are deploying the IBM General Parallel File System (IBM Spectrum Scale) Pattern, you can modify the volumes for the virtual machine on the Volumes tab.
    3. Click OK when you are finished updating the settings.
14. When you are finished modifying the settings, click Deploy.
15. View the details of the deployed virtual application in the Virtual Application Instances pane.
    The details include a list of virtual machines that are provisioned on the cloud infrastructure for that deployment, the IP address, virtual machine status, and role status. Role is a unit of function that is performed by the virtual application middleware on a virtual machine.

    The resources that are allocated to a virtual application instance are listed in deployment.json, and are also displayed in the Virtual machine perspective > Name > Hardware and network section of the instance details page. Sometimes the memory that is allocated to a virtual image in a virtual application instance might be higher than the minimum memory requirement that is specified in topology.json because the value for the memory must be an integral multiple of 128. In this case, the system will increase the memory that is allocated to the instance to the next multiple of 128.

    The status values are listed in the following table:

    Table 1. Possible status values for a deployment

    Status	Deployment description	Virtual machine description
    Error	An error occurred during deployment. Check the logs and determine the cause of the error before you redeploy the virtual application.	The virtual machine status.
    Failed	The deployment process could not be started because of either the application configuration or a failure that is occurring in the infrastructure cloud.	The virtual machine did not start successfully.
    Installing	Not applicable	The components of the virtual application are being provisioned on the virtual machine.
    Launching	The virtual application is being deployed.	The virtual machine is being provisioned on the infrastructure cloud.
    Not_Ready	The virtual application instance is in maintenance mode.	The Not_Ready status does not apply to virtual machines.
    Queuing	The deployment is scheduled for a date and time in the future.
    Registering	Start deploying the virtual machine by registering it with hypervisor.
    Running	Resources are actively running in the infrastructure cloud.	The components of the virtual application are running on the virtual machine and can be accessed.
    Saferunning	For more information, see Agent is running in safe mode.
    Starting	Starting the virtual machine.
    Stopped	The virtual application instance is stopped. The virtual application can be made available again by starting the instance.	The virtual machine is stopped and it can be restarted.
    Stopping	The virtual application instance is stopping.	The virtual machine is being stopped.
    Stored	The virtual application instance is stored. No processor, memory, network, or data resources are reserved for stored instances. The virtual application can be started only if resources are available.	The virtual machine is stored. It can be started only if resources are available.
    Storing	The virtual application instance is storing.	The virtual machine is being stored.
    Terminated	The virtual application instance resources are deleted. History files are retained.	The virtual machine is deleted and resources were released.
    Terminating	The virtual application instance resources are being deleted.	The virtual machine is being deleted and its resources are released.
    Transferring	Transferring the image to hypervisor.
    Unknown	The status cannot be determined.
    Unknown status	The status cannot be determined.

    You can also view the virtual machine role health status information. For example, a red check mark is displayed when the amount of processor becomes critical on the virtual machine.

    If deployment fails with an error: Virtual application initialization failed on virtual machine <Virtual machine name>, you can try to log on to the virtual machine and look for the cause of the error in the configuration logs, which are in /0config/0config.log.

    Click Endpoint to view the endpoint information for a role. For a DB2® deployment, you can have more than one endpoint. For example, an endpoint for the application developer and one for the database administrator. If the elastic load balancer shared service is used by the virtual application instance, the endpoint URL is based on the virtual host name for the elastic load balancer instance. Otherwise, the endpoint URL is based on the IP address of the virtual machine that is associated with the role. For more information, see the Related concepts section.

http://IP_address:9080/tradelite/