Shell Commands › Application Control › start (Application Control and Management)--Start Application

start (Application Control and Management)--Start Application

Start application

Syntax

application start name ( prop=val )* [ --debug ] [ --norestart ] [ --skipbuild ] [ --force ] [ --cap_cpu ] 

Parameters

name

Name of application.

prop=val

Parameters for scheduling. The following parameters may be specified:

cpu - (optional) CPU allocation in whole CPUs or percent (val[%])

mem - (optional) Memory allocation (val[M[B]|G[B]]). If units are not specified, memory is specified in MB.

bw - (optional) Bandwidth allocation (val[M[b]|G[b]]). If units are not specified, bandwidth is specified in Mbps.

sched - String specifying scheduling target (see below)

servers - Number of servers on which application is to be started;

--debug

Start application in debug mode.

--norestart

Do not restart application upon grid failure.

--skipbuild

Do not build application prior to start.

--force

Force releasing any volumes that are currently in use without asking for verification.

--cap_cpu

Enable the capping of CPU for all components of the application.

Examples

application start sugarcrm

Start application 'sugarcrm'

Notes: 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. CA 3Tera 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 (that is, 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 start will fail if --debug is specified and the application has field engineering code 16 set.

Starting an application resets the component flapping counters that are maintained by CA 3Tera 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 CA 3Tera AppLogic. comp start/restart or app restart may also be used to reset a component's flapping counter.