Page Navigation: | |
---|---|
|
Confidence Level Moderate This article includes input from several JPLers. Multiple subject matter experts can indicate that a page is more frequently reviewed and updated. |
---|
TODO: @Xing, Marjorie Lucas @alphan, Alexander Torres
Developer Considerations
The node is still subject to spot terminations, so don't depend on it staying up forever
The developer is now responsible for the life cycle of this node, to turn it off when it's not use and to terminate it when it's no longer needed
The developer should probably relabel the node, if possible, so other developers know who is responsible for that instance, if any issues crop up.
What is the impact on the operator, who may see this node in metrics and figaro?
Key Steps
(1) detach from ASG
Go to the AWS EC2 console
Click on the
Auto Scaling Groups
link on the left hand side column (usually towards the bottom)Click on the autoscaling group that your Verdi worker instance is in.
After you click on the autoscaling group, a menu should show up on the bottom of the screen.
Click on the
Instance Management
tab and locate your Verdi worker underInstances
.Right click the instance you want to detach and click
detach
.
(2) disable harikiri
run
ps -x
in the verdi worker instance and look for the PID that contains harikirikill the process with the following command:
kill <harikiri_pid>
Create a file withtouch /data/work/.harikiri
. Harikiri will not terminate the instance as long as such a file exists.
(3) docker run bash
ssh into worker node
cd into the work directory
Edit the
_run.sh
scriptEdit the block of code starting with
docker run ...
append
-it
just after “docker run”remove PGE command (
/home/ops/...
) at the end of thedocker run ...
block and add/bin/bash
Save
_run.sh
changesRun
_run.sh