To provision an application, define the boundary parameters that are specific to an instance of the application. These parameters are in three groups, with different sources:
|
Type of Parameter |
Description |
Examples |
Source |
|---|---|---|---|
|
General |
Names and descriptions |
Template application name, instance name, customer details |
Template application name in applications catalog, all others based on your company procedures |
|
Instance Resources |
System resources allocated to instance |
CPU, volume size, memory |
Defaults set when template application created. Override if and only if customer requirements exceed defaults. |
|
Properties |
Application-specific settings that specialize the application instance for its role. |
IP addresses, gateway, administrator email address and password |
Grid properties in Dashboard tab or from running grid info. Other details in application data sheet. |
General parameters consist of names and descriptive information.
When you run the application provision command, include the name of the template application. You can use any application on the grid as a template on two conditions. First, the application must have the template attribute set. Second, the application must not be running. To view the list of application templates, use the application list command or view the system dashboard Applications tab. Template applications are shown first in the list.
Note: The provisioning wizard opens from the context menu of the template application being provisioned. Therefore if you use the wizard, you do not need to specify the template application name.
Note: Provisioning copies the entire template, including data. Therefore do not specify any application as a template if the application contains user data.
Give a name to the application instance that you create through provisioning. The name is alphanumeric and must start with a letter. Underscores are the only special characters allowed.
Example: The following names are valid.
Example: The following names are not valid.
Note: Include the template name and the customer name in the instance name as best practice. For example, if you have an application template named cPanel_b32 and a customer named customer8, name the instance cPanel_b32_customer8. Applications are always displayed sorted. Therefore, applications starting with the same name are together in the list.
Customer billing information. For example, put the customer ID in user1 and the billing code in user2. The commands app info myapp and app config myapp display these fields. The metering information records also include these fields.
Arbitrary, human-readable description of the purpose of the application instance. The application list command app list --verbose and the system dashboard display this description.
The resource parameters specify the system resources that are available to the instance after provisioning. Default values are provided. Application developers set default resource parameters when they design the template application. Change these values from the default only if there is a customer need.
For preconfigured template applications included with this product, resource ranges are listed in the application data sheet. Data sheets are in the Application Catalog Resource Guide. Alternatively, to find the memory and CPU ranges for any template application, run the app config command with the template name. To find the assigned disk volumes and their size ranges for a template application, run the vol list command with the template name.
The system dashboard also displays template application resource ranges, in the provisioning wizard and in the application configuration details.
An instance uses the following resources:
The minimum amount of CPU that is available to the application instance. CPU is defined in fractions for a single appliance application. CPU is defined as a fixed decimal for multiple appliance applications.
Example: cpu.dflt=0.10 is 10 percent of the CPU. cpu.dflt=1.00 is a full CPU. cpu.dflt=0.25 is 25 percent of the CPU.
Note: The CPU parameter is the minimum amount of CPU that is ever available to the application instance. Regardless of any other load on the grid or the physical server, the application always has at least this much CPU. The application may get more CPU, up to the full CPU of the server, whenever no other applications need CPU on that server.
The amount of memory that is available to the application instance. The memory is defined in megabytes.
Example: mem.dflt=128M allocates 128 MB to the application instance. mem.dflt=1024M allocates 1 GB to the application instance.
Note: The memory parameter defines the exact amount of memory that is available to the application instance. This parameter is enforced exactly, minus a few megabytes for system records.
The size of disk volumes that are assigned to the application instance. Disk volumes are assigned to the template application. Disk volumes are defined in megabytes or higher. The range of disk volume sizes are set in the template application. You can override the default disk volume but you cannot set a new disk volume outside of the template application range.
Example: The following command defines the size of the grid server boot disk VPS64_CENTOS52 as 2.2 GB.
VPS64_CENTOS52.boot.size=2.2G
Note: You can view disk volumes and their ranges for a template application by running the command vol list with the template name. You can also see this information in the provisioning wizard. For preconfigured template applications included with this product, this information is included in the application data sheet, which is in the Application Catalog Reference Guide.
This parameter limits virtual system throughput.
Important: Do not change this parameter from default values except in extraordinary circumstances.
Properties are application-specific settings that specialize the application instance for its role. While the template provides most of the system and application configuration necessary for the application to run, some settings differ from instance to instance. Those typically include IP addresses, passwords, and tuning parameters.
Some properties are mandatory and must be specified when you provision the application. Other properties are optional. Specify optional properties only when you want to change the default values. The provisioning wizard highlights mandatory properties in red.
For preconfigured template applications included with this product, the set of properties and their allowed values are described in the application data sheet. Data sheets are in the Application Catalog Resource Guide. If the application is provided separately and the data sheet is missing, ask Technical Support for the data sheet. Alternatively, run the following command:
app config template_name --boundary
IP and IP-owned properties (gateway, DNS, netmask, all other IPs) are specific to the grid that hosts the template application. These values are visible in the system dashboard Dashboard tab, or by running the grid info command.
Note: Gateway, netmask, and DNS server addresses are the same for every instance that you create on the same grid. For efficiency, set these properties on the template application instead of when you provision the application. Provisioned instances inherit all properties that you set on the template application.
The following examples describe typical application provisioning commands:
app provision VPS_CentOS50_r1 gs_cust12 \ hostname=gs_cust12 primary_ip=209.100.100.12 \ netmask=255.255.255.0 gateway=209.100.100.1 \ dns1=209.101.1.2 dns=209.102.1.2 \ user=user12 user_pw=K2RX9Jx5 root_pw=17bWvuMG \ cpu.dflt=0.10 mem.dflt=256M GSC.boot.size=20G \ .user1=Customer12 .user2=RatePlan2 \ .description="grid server for customer #12"
app provision SugarCRM? _r1 sugar_1 user_ip=209.100.100.11 admin_ip=209.100.100.12 \ netmask=255.255.255.0 gateway=209.100.100.1 \ dns1=209.101.1.2 dns=209.102.1.2 \ mail_server=mail@mycompany.com \ cpu.dflt=4.0 mem.dflt=1G code.size=512M data.size=1G \ config.size=256M logs.size=64M \ .user1=Customer1 .user2=RatePlan5 \ .description="SugarCRM hosing for customer #1"
app provision TWiki_r1 twiki_1 user_ip=209.100.100.11 admin_ip=209.100.100.12 \ netmask=255.255.255.0 gateway=209.100.100.1 \ dns1=209.101.1.2 dns=209.102.1.2 \ mail_server=mail@mycompany.com \ cpu.dflt=1.0 mem.dflt=256M data.size=512M twiki.size=512M \ .user1=Customer1 .user2=RatePlan5 \ .description="TWiki hosing for customer #1"
Note: The app provision command starts the application. If you want to provision the application without starting it (for example, to prepare ready instances but not start them), add the --skipstart option at the end of the app provision command line. See the Command Line Shell Reference guide for all options of this command.
|
Copyright © 2012 CA.
All rights reserved.
|
|