Application Control and Management Commands

The following commands are supported:

list

Typical Output

   Name                State     Template
   -----------------------------------------
   BackupHelper_r1     stopped   yes
   LampCluster_r6      stopped   yes
   Lamp_r2             stopped   yes
   LampX4_r2           stopped   yes
   MigHelper           stopped   yes
   SugarCRM_r2         stopped   yes
   Sys_Filer_Linux     stopped   yes
   Sys_Filer_Solaris   stopped   yes
   Sys_Filer_Windows   stopped   yes
   TWiki_r2            stopped   yes
   VDS_CentOS50_r3     stopped   yes
   VDS_CentOS51_r3     stopped   yes
   VDS_Win03_r2        stopped   yes
   VDS64_CentOS50_r3   stopped   yes
   VDS64_OSOL_r2       stopped   yes

info

Typical Output

Name                    : SugarCRM_r4
Description             : Fully featured, scalable CRM Application, based on SugarCRM's Sugar Open Source 4.0.1 (v4.0.1d-11)
ID                      : 2
Documentation URL       : http://doc.3tera.net/AppLogic27/RefAppsSugarCRM.html
Template                : yes
Locked                  : no
User1                   :
User2                   :
Destroy on Stop         : no
State                   : stopped
CPU                     : 1.65
Memory                  : 2.25 GB
Bandwidth               : 2050 Mbps
Default Login Appliance :

create

destroy

rename

copy

config

Description:	Configure an application
Syntax:	application config name [--effective] [--batch]
	application config name --boundary
	application config name [--reset ] [ prop>=val]* [--d prop]* [ --partial ] [--verify ]
	application config name [ prop=val]* [--d prop]* --test_only [ --partial ] [--verify ]
	application config name --template=app [ --skip_rsc ] [ prop=val]* [--d prop]* --test_only [ --partial ] [--verify ]
	application config name --stdin [--test_only] [ --partial ] [--verify ]
Arguments:	name	Name of application to configure
	--boundary	Show application boundary (i.e., list of properties that may be configured).
	--reset	Reset all properties to default.
	--template=app	Name of application whose configuration is to be used as a base configuration before applying any configuration parameters specified on the command line.
	--skip_rsc	Do not propagate any resource settings from the template application.
	prop=val	Change a property setting.
	--d prop	Reset property to default.
	--test_only	Test provided configuration parameters, do not set. Note --test-only is provided for backward compatibility.
	--partial	Skip verification that all mandatory properties are set. As of Applogic 1.5, this option is provided for backward compatibility only (i.e., no-op).
	--effective	Display the effective configuration of an application. The output will include all configuration parameters for the application - essentially merging the default and explicitly overridden values. This option is only available if hotfix e3856 is installed on the grid.
	--batch	Display output in UDL format.
	--stdin	Read configuration parameters to be set from standard input.
	--verify	Verify that all mandatory properties are set.
Examples:	app config SugarCRM - Show current configuration for SugarCRM
	application config SugarCRM --boundary - Show configurable parameters for SugarCRM
	application config SugarCRM --reset - Reset app configurable parameters for SugarCRM to defaults
	application config SugarCRM --stdin < sugar.params - configure application using settings contained within the file sugar.params.
	application config MyApp .template=1 --partial - configure application as a template so that it may be later provisioned.
Notes:	Application configuration parameters specified by prop can be one of the following:
	* .name - attribute, attributes can be:
	.description - Free form text describing application
	.template - 0/1 - must be set in order for application to be provisioned
	.user1, .user2 - Free form text used for client billing information
	.destroy_on_stop - Destroy application after it is stopped.
	.doc_url - URL where application documentation can be found.
	* name - property
	* resource.val - resource, resource can be cpu, mem, bw val can be min, max, dflt
	* vol. name - volume
	* servers. val - set servers, val can be min, max, set.
	When configuring an application using the --stdin option, the format of the input should be similar to the output of the following command: app confiig name --batch.
	As of Applogic 1.5, this command will not validate that all mandatory properties are set by default. To enable the property validation, specify the --verify option.
	Using the --template=app option is similar to executing 'app config mytemplate --batch | app config myapp --stdin' in that the configuration from 'mytemplate' is configured on 'myapp'.
	An added benefit of using the --template=app option is that additional configuration parameters may be specified that override those of the template application.
	A specification of the output of this command can be found here.

start

stop

continue

restart

Description:	Restart application
Syntax:	application restart name ( prop=val )* [ --debug ] [ --clean ] [ --norestart ] [ --skipbuild ] [ --force ] [ --cap_cpu ]
Arguments:	name	Name of application.
	prop=val	Parameters for scheduling. The following parameters may be specified:
		cpu - (optional) CPU allocation (val[%])
		mem - (optional) Memory allocation (val[M[B]|G[B]]). If units are not specified, memory is in MB.
		bw - (optional) Bandwidth allocation (val[M[b]|G[b]]). If units are not specified, bandwidth is in Mbps.
		sched - String specifying scheduling target (see below)
		servers - Number of servers on which application is to be started;
	--debug	Restart application in debug mode. SCR 779
	--clean	Clean application prior to restart.
	--norestart	Do not restart application upon grid failure.
	--skipbuild	Do not build application prior to restart.
	--force	Force releasing any volumes that are currently in use without asking for verification. This is useful when restart is executed over an application that is not currently running. Supported in Applogic 2.8.8+.
	--cap_cpu	Enable the capping of CPU for all components of the application.
Examples:	application restart sugarcrm - Restart application 'sugarcrm'
Notes:	This command combines application stop and start commands.
	The --clean and --skipbuild options may not be specified at the same time.
	The following scheduling targets are supported:
	sched="percentile=(resource percentile)"
	sched=crunch - assign the minimum resources to all components, same as "percentile=0"
	sched=expand - assign the maximum resources to all components, same as "percentile=100"
	sched="mode=(scheduling mode)", valid values are one of the following:
	* 1 - pack servers, schedule appliances on server with least amount of available resources
	* 2 - round robin with random start, randomly schedule first appliance to a server and then assign remaining appliances to other servers using round robin
	* 3 - round robin, schedule first appliance on the first server and then assign remaining appliances to other servers using round robin
	When using the pack server scheduling mode, the servers are chosen in priority order based on their assigned role and the least amount of available resources. AppLogic will always use servers with a role of none first, secondary second and primary last; without regards to the available resources on those servers (i.e., the secondary servers won't be used until all of the none servers are used, the primary server won't be used until all secondary and none servers are used).
	The application restart will fail if --debug is specified and the application has field engineering code 16 set.
	Restarting an application resets the component flapping counters that are maintained by AppLogic. A component's flapping counter is the number of times that component has failed within the last 24 hours (each component has its own flapping counter). Once a component fails 3 times in 24 hours, the component is not restarted by AppLogic. comp start/restart or app start may also be used to reset a component's flapping counter.

build

clean

repair

login

export

import

migrate

provision

get_desc

put_desc

lock

unlock

-- BeckyH - 23 May 2006