om vol restart¶
Chain a local service instance stop and start
--color=<string>¶
Colorize output. Possible values are:
- auto: guess based on tty presence
- always|yes: always colorize
- never|no: never colorize
--daemon¶
A flag inhibiting the command daemonization. Set by the daemonization routine.
--debug¶
Increase stream and file log verbosity up to the debug level.
--disable-rollback¶
If set, don't try to rollback resources activated before a start action interrupts on error.
--dry-run¶
Show the action execution plan.
--env¶
Export the uppercased variable in the os environment.
With the create action only, set a env section parameter in the service configuration file. Multiple
--env <key>=<val>
can be specified. For all other actions.
--local¶
Execute the service action on the local service instances only, ignoring cluster-wide considerations.
--master¶
Limit the action scope to the master service resources.
--namespace=<string>¶
The namespace to switch to for the action. Namespaces are cluster partitions. A default namespace can be set for the session setting the OSVC_NAMESPACE environment variable.
--node=<string>¶
The node to send a request to. If not specified the local node is targeted.
--nolock¶
Don't acquire the action lock. Dangerous, but can be useful to set parameters from an action trigger.
--rid=<string>¶
A resource specifier expression like
<spec>[,<spec>]
, where<spec>
can be:
- A resource id
- A driver group name (app, fs, disk, ...)
Examples:
app
all app resourcescontainer#1,ip#1
only container#1 and ip#1
--slave=<string>¶
Limit the action to the service resources in the specified, comma-separated, slaves.
--slaves¶
Limit the action scope to service resources in all slaves.
--status=<string>¶
Operate only on service with a local instance in the specified availability status (up, down, warn, ...).
--subsets=<string>¶
Limit the action to the resources in the specified, comma-separated, list of subsets.
--tags=<string>¶
A comma-separated list of resource tags to limit action to. The+
separator can be used to impose multiple tag conditions. For example,tag1+tag2,tag3
limits the action to resources with both tag1 and tag2, or tag3.
--waitlock=<string>¶
A duration expression like5s
. The maximum wait time when acquiring the service action lock.
-f, --force¶
Force action, ignore sanity checks.
-h, --help¶
Show this help message and exit.
-p, --parallel¶
Start actions on specified services in parallel. max_parallel in node.conf limits the number of parallel running subprocesses.
-s, VAL, --service=<string>¶
A service selector expression
[!]<expr>[<sep>[!]<expr>]
where:
!
is the expression negation operator<sep>
can be:
,
OR expressions+
AND expressions<expr>
can be:
- a shell glob on service names
<param><op><value>
where:
<param>
can be:
<rid>:
<group>:
<rid>.<key>
<group>.<key>
<single value jsonpath expression on the $.monitor.services.<path> dictionary extended under the 'nodes' key by each instance 'status' and 'config' data>
<op>
can be:
<
>
<=
>=
=
~
with regexp valueExamples:
*dns,ha*+app.timeout>1
ip:+task:
!*excluded
$.avail=warn
$.nodes.*.status.avail=warn
Note:
!
usage requires single quoting the expression to prevent shell history expansion