The Application Provisioning wizard allows you to provision and configure an application using an application template.
The General screen contains the following fields:
Unique name of the provisioned application on this grid.
Human-readable description of the application.
Free-form user-defined text intended for specifying billing code.
Free-form user-defined text intended for specifying billing code.
URL where the documentation for the application can be found. The URL may be opened by clicking on the Open URL text to the right of the field.
The Configure Resources screen contain the two sections: Constrain by Resources and Volumes.
Constrain by Resources
Accept the default or specify the amount of CPU, memory, and bandwidth resource by moving the slide bar or entering the value. The following resource types can be specified:
Portion of CPU or number of CPUs to be allocated for the application. Fractional amounts can be specified as a decimal number, such as 0.5 or 3.5. Whole CPU is specified simply as an integer, such as 12.
Amount of memory allocated for the application. The amount is specified as an integer value in megabytes, such as 512M or gigabytes, such as 9G.
Amount of network bandwidth allocated for this application. The amount is specified as an integer value in megabits/sec, such as 10M or gigabits/sec, such as 1G.
To restore the default value for a resource, click the restore icon.
Volumes
Specify the volume size by clicking the Size field for the App Volume you want to change. The default size of the volumes are shown in normal font weight. Volume sizes explicitly configured for this application are in bold.
Application storage location, such as code and mon.
Volume size specified as an integer value in megabytes, such as 50M or gigabytes, such as 2G.
Storage location
If the grid is configured in the Backbone Fabric Controller to use a SAN, the following displays:
Local: Stores the volumes locally, such as a hard drive on a server, on the grid
SAN: Stores the volumes on the SAN. You may specify the default location of the volume store in the BFC.
For additional information about configuring a grid to use a SAN, refer to the BFC User Guide.
Interfaces provide the means for an application to communicate with appliances and the outside world. Raw interfaces are very similar to virtual network interfaces in virtual machines and to NICS (network interface cards) in traditional servers.
The Interface Name and Network fields display. You can specify the IP address or range of IP addresses for the interface by clicking the IP Address field and entering the IP address or displaying the selection list.
In addition, you can configure multiple IP addresses for a single interface. For example, you can run two identical applications on the same grid, but on separate servers, or on different grids, if the IP address is accessible from both grids. To specify multiple IP addresses click the + icon and enter or select the IP address or IP address range. To remove the additional rows, click the - icon.
The Info icon displays the Name Servers and IP Ranges.
The Configuration Properties dialog of the wizard allows you to set values for properties of the application which specializes this instance of the application. This is useful for configuring location-specific parameters, such as IP addresses, and for configuring tuning parameters, such as cache sizes.
The default values of the properties are shown in normal font weight. Property values explicitly configured for this application are in bold. Mandatory property volumes that have not yet been configured are highlighted in red.
For information about the property, its type and allowed values, click Info.
To restore the default value of a property, click Restore.
To reset the values of all properties to their defaults, click Reset All.
The Finalizing screen contains the following fields:
Select this if you want the application to be started after the provisioning. If left unselected, the provisioned application is not started.
Select this if you want the application volumes copied using filesystem-level copy rather than block-level copy. This is useful if the application has very large volumes that have little data on them.
Select this if you want the volumes prefilled or all blocks allocated. This could greatly increase the amount of time it takes to provision the application depending on the size of the application volumes being created.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|