Haylix Ops Bot instructions via Slack

Haylix have developed a function to allow our clients to manually stop/start/reboot instances or environments utilising Slack.

To access this functionality you will be required to complete a Haylix on-boarding process that will grant you access to a Haylix shared Slack channel. We use the shared Slack channel to ensure we can monitor activities and see when you have enabled or disabled environments. 

Note: Production environments can be listed but not stopped or disabled

Ops Slack Commands

In your Haylix Slack channel you can use the following commands to interact with your environment:

ops help

ops list

ops reboot instance <instance_id>

ops start instance <instance_id>

ops stop instance <instance_id>

ops start env <environment name>

ops stop env <environment name>

To Stop/Start Individual Instances

To stop/start/reboot individual instances you will need to use the <Instance ID> located in the first column of the table shown below.

Example: ops stop instance i-02367xxxxxxxxxxxx

Databases will also need to use the <Instance ID> again in the first column of the table below, however, AWS database Instance IDs are in a friendlier format than other server names.

To keep it simple; always use the Instance ID column as the identifier with the instance command. 

To stop/start Entire Environments

Use the following commands:

ops start env <environment name>

ops stop env <environment name>

You can find the environment name by listing assets using the ops list command. Assets are grouped by their respective environment name.

 Note: An error will appear if you attempt to start/stop instances or environments whilst already in another stop/start process

To List The Environments Resources

Use the ops list command

Stage

Instance ID

Status

Server name

i-02367xxxxxxxxxxxx

stopped

stage-term1

i-0a8b2xxxxxxxxxxxx

stopped

stage-proc1

i-020cd4xxxxxxxxxxxx

stopped

stage-nebu1

i-0a7911xxxxxxxxxxxx

stopped

stage-sql1

i-0998bxxxxxxxxxxxx

stopped

stage-web1

i-0cd714xxxxxxxxxxxx

stopped

stage-app1

stage--db1

available

db-XPFKxxxxxxxxxxxx

 

Prod

Instance ID

Status

Server name

i-02178exxxxxxxxxxxx

running

prod-web1

i-059a4xxxxxxxxxxxx

running

prod-app1

i-0aa52xxxxxxxxxxxx

running

prod-term1

i-03430xxxxxxxxxxxx

running

prod-proc1

i-054e9xxxxxxxxxxxx

running

prod-sql1

i-05ae1xxxxxxxxxxxx

running

prod-nebu1

prod--db1

available

db-CJEXxxxxxxxxxxxx

 

 

 

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.