Commands

Microservice

microservcie

Syntax: microservcie

Display the current microservice.

Examples:

admin@/jlupin/zone/zone1/node1/mic1> microservice

microservice activate

Syntax: microservice activate [<microservice>] [<node>] [<zone>]

Activate the current or given (<microservice>) microservice on all nodes that it is running or on given (<node>) node in the current or given (<zone>) zone.

Argument Information
[<microservice>] Name of microservice to activate.
[<node>] Name of node from which microservice will be taken.
[<zone>] Name of zone from which microservice will be taken.

Examples:

admin@/jlupin/zone/zone1/node1/mic1> microservice activate

microservice deactivate

Syntax: microservice deactivate [<microservice>] [<node>] [<zone>]

Deactivate the current or given (<microservice>) microservice on all nodes that it is running or on given (<node>) node in the current or given (<zone>) zone.

Argument Information
[<microservice>] Name of microservice to deactivate.
[<node>] Name of node from which microservice will be taken.
[<zone>] Name of zone from which microservice will be taken.

Examples:

admin@/jlupin/zone/zone1/node1/mic1> microservice deactivate

microservice deploy

Syntax: microservice deploy [<repo_name>:]<file_path> <strategy> [<strategy_arguments>]

Deploy microservice from file located on [<repo_name>:]<file_path> by the given <strategy>.

Argument Information
[<repo_name>:]<file_path> Path to zipped microservice.
<strategy> Name of strategy used for upload.

Examples:

admin@/jlupin/zone/zone1/node1/mic1> microservice deploy local:mic2.zip smart 1

microservice destroy

Syntax: microservice destroy [<microservice>] [<node>] [<zone>]

Destroy the current or given (<microservice>) microservice located on <node> node in the current or given (<zone>) zone..

Argument Information
[<microservice>] Name of microservice to destroy.
[<node>] Name of node from which microservice will be taken.
[<zone>] Name of zone from which microservice will be taken.

Examples:

admin@/jlupin/zone/zone1/node1/mic1> microservice destroy

microservice details

Syntax: microservice details [<microservice>] [<node>] [<zone>]

Show details of the current or given (<microservice>) microservice on all nodes or given (<node>) node in the current or given (<zone>) zone.

Argument Information
[<microservice>] Name of microservice to show details.
[<node>] Name of node from which microservice will be taken.
[<zone>] Name of zone from which microservice will be taken.

Examples:

admin@/jlupin/zone/zone1/node1/mic1> microservice details

microservice disable

Syntax: microservice disable [<microservice> <node>] [<zone>] [force]

Disable the current or given (<microservice>) microservice on the given (<node>) node in the current or given (<zone>) zone, force switch terminates microservice instead of stopping.

Argument Information
[<microservice> Name of microservice to disable.
<node>] Name of node from which microservice will be taken.
[<zone>] Name of zone from which microservice will be taken.
[force] Force switch terminates microservice instead of stopping.

Examples:

admin@/jlupin/zone/zone1/node1/mic1> microservice disable

microservice double restart

Syntax: microservice double restart [<microservice>] [<node>] [<zone>]

Restart the current or given (<microservice>) microservice twice on all nodes that it is running or on given (<node>) node in the current or given (<zone>) zone.

Argument Information
[<microservice>] Name of microservice to restart.
[<node>] Name of node from which microservice will be taken.
[<zone>] Name of zone from which microservice will be taken.

Examples:

admin@/jlupin/zone/zone1/node1/mic1> microservice double restart

microservice enable

Syntax: microservice enable [<microservice>] [<node>] [<zone>]

Enable the given (<microservice>) microservice on the current or given (<node>) node in the current or given (<zone>) zone.

Argument Information
[<microservice>] Name of microservice to enable.
[<node>] Name of node from which microservice will be taken.
[<zone>] Name of zone from which microservice will be taken.

Examples:

admin@/jlupin/zone/zone1/node1/mic1> microservice enable

microservice list

Syntax: microservice list [<zone>] [<node>]

List microservices in the current or given (<zone>) zone, optionally available on the current or given (<node>) node.

Argument Information
[<zone>] Name of zone from which microservice will be taken.
[<node>] Name of node from which microservice will be taken.

Examples:

admin@/jlupin/zone/zone1/node1/mic1> microservice list

microservice repo

Syntax: microservice repo [<microservice>] [<node>] [<zone>]

Show microservice's load balancer's service repository for the current or given (<microservice>) microservice on the current or given (<node>) node in the current or given (<zone>) zone.

Argument Information
[<microservice>] Name of microservice to show service repository.
[<node>] Name of node to show service repository.
[<zone>] Name of zone to show service repository.

Examples:

admin@/jlupin/zone/zone1/node1/mic1> microservice repo

microservice restart

Syntax: microservice restart [<microservice>] [<node>] [<zone>]

Restart the current or given (<microservice>) microservice on all nodes that it is running or on given (<node>) node in the current or given (<zone>) zone.

Argument Information
[<microservice>] Name of microservice to restart.
[<node>] Name of node from which microservice will be taken.
[<zone>] Name of zone from which microservice will be taken.

Examples:

admin@/jlupin/zone/zone1/node1/mic1> microservice restart

microservice runtime

Syntax: microservice runtime [threads|memory|cpu|stats] [<microservice>] [<node>] [<zone>]

Show runtime statistics of the current or given (<microservice>) microservice on all nodes or given (<node>) node in the current or given (<zone>) zone.

Argument Information
[threads|memory|cpu|stats] Threads, memory, cpu or general statistics.
[<microservice>] Name of microservice to restart.
[<node>] Name of node from which microservice will be taken.
[<zone>] Name of zone from which microservice will be taken.

Examples:

admin@/jlupin/zone/zone1/node1/mic1> microservice runtime

microservice start

Syntax: microservice start [<microservice>] [<node>] [<zone>] [force]

Start the current or given (<microservice>) microservice on all nodes that it is stopped or terminated or on given (<node>) node in the current or given (<zone>) zone ('force' flag indicates if also activate microservice).

Argument Information
[<microservice>] Name of microservice to start.
[<node>] Name of node from which microservice will be taken.
[<zone>] Name of zone from which microservice will be taken.
[force] Also activate microservice.

Examples:

admin@/jlupin/zone/zone1/node1/mic1> microservice start

microservice status

Syntax: microservice status [<microservice>] [<node>] [<zone>]

Show the status of the current or given (<microservice>) microservice on all or given (<node>) node that it is enabled in the current or given (<zone>) zone.

Argument Information
[<microservice>] Name of microservice to show status.
[<node>] Name of node to select microservice.
[<zone>] Name of zone to select microservice.

Examples:

admin@/jlupin/zone/zone1/node1/mic1> microservice status

microservice stop

Syntax: microservice stop [<microservice>] [<node>] [<zone>]

Stop the current or given (<microservice>) microservice on all nodes that it is running or on given (<node>) node in the current or given (<zone>) zone.

Argument Information
[<microservice>] Name of microservice to stop.
[<node>] Name of node from which microservice will be taken.
[<zone>] Name of zone from which microservice will be taken.

Examples:

admin@/jlupin/zone/zone1/node1/mic1> microservice stop

microservice tech

Syntax: microservice tech <name> <command> [<node>] [<zone>] [force]

Executes <command> on technical microservice named <name> on the current or given (<node>) node in the current or given (<zone>) zone ('force' flag indicate if check technical microservice and command both exists on server).

Argument Information
<name> Name of technical microservice.
<command> Name of command to execute.
[<node>] Name of node to execute command.
[<zone>] Name of zone to execute command.
[force] Flag to indicate if check technical microservice and command both exists on server.

Examples:

admin@/jlupin/zone/zone1/node1/mic1> microservice tech nginx status

microservice terminate

Syntax: microservice terminate [<microservice>] [<node>] [<zone>]

Stop force the current or given (<microservice>) microservice on all nodes it is running or on given (<node>) node in the current or given (<zone>) zone.

Argument Information
[<microservice>] Name of microservice to terminate.
[<node>] Name of node from which microservice will be taken.
[<zone>] Name of zone from which microservice will be taken.

Examples:

admin@/jlupin/zone/zone1/node1/mic1> microservice terminate

microservice undeploy

Syntax: microservice undeploy [<microservice>] [<node>] [<zone>] [force]

Stop or stop force (based on 'force' flag) and destroy the current or given (<microservice>) microservice on all nodes that it is stopped or terminated or on given (<node>) node in the current or given (<zone>) zone.

Argument Information
[<microservice>] Name of microservice to undeploy.
[<node>] Name of node from which microservice will be taken.
[<zone>] Name of zone from which microservice will be taken.
[force] If provided stop force is used.

Examples:

admin@/jlupin/zone/zone1/node1/mic1> microservice undeploy

microservice upload

Syntax: microservice upload [<repo_name>:]<file_path> [<node>] [<zone>]

Upload microservice from file located on [<repo_name>:]<file_path> to the current or given (<node>) node in the current or given (<zone>) zone.

Argument Information
[<repo_name>:]<file_path> Path to zipped microservice.
[<node>] Name of node to which microservice will be uploaded.
[<zone>] Name of zone to which microservice will be uploaded.

Examples:

admin@/jlupin/zone/zone1/node1/mic1> microservice upload local:mic2.zip