New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add new command verdi process
to interact with running processes
#1855
Add new command verdi process
to interact with running processes
#1855
Conversation
All interactions with processes, now go through RabbitMQ. Historically there is a division in the calculations, where job and inline calculations are managed through `verdi calculation` and the work type calculations through `verdi work`. However, these commands should really only serve to introspect the state of a process through the node that serves as its proxy in the database. Any commands that need to affect the process that these nodes represent, have to go through RabbitMQ. To make this distinction clearer to users, the new command `verdi process` is created. Any command that interacts with the process, such as `kill`, `play` and `pause` should go through `verdi process`. All other commands that only strictly display information about the process through the calculation node proxy, should go in `verdi calculation` and `verdi work`.
cd2b8a4
to
f9fc184
Compare
Codecov Report
@@ Coverage Diff @@
## develop #1855 +/- ##
===========================================
- Coverage 66.81% 66.78% -0.03%
===========================================
Files 316 320 +4
Lines 32331 32527 +196
===========================================
+ Hits 21602 21724 +122
- Misses 10729 10803 +74
Continue to review full report at Codecov.
|
aiida/cmdline/commands/cmd_work.py
Outdated
@verdi_work.command('kill') | ||
@arguments.CALCULATIONS( | ||
type=types.CalculationParamType(sub_classes=('aiida.calculations:work', 'aiida.calculations:function'))) | ||
def work_kill(calculations): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Put back with deprecation warning.
@@ -517,14 +530,10 @@ Configure and manage users | |||
-------------- | |||
Manage work calculations. | |||
|
|||
* **kill**: kill a work calculation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Put back with deprecation
* **pause**: Pause running processes. | ||
* **play**: Play paused processes. | ||
* **watch**: Watch the state transitions for a process. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add list
Fixes #1825
All interactions with processes, now go through RabbitMQ. Historically
there is a division in the calculations, where job and inline calculations
are managed through
verdi calculation
and the work type calculationsthrough
verdi work
. However, these commands should really only serveto introspect the state of a process through the node that serves as its
proxy in the database. Any commands that need to affect the process that
these nodes represent, have to go through RabbitMQ. To make this distinction
clearer to users, the new command
verdi process
is created.Any command that interacts with the process, such as
kill
,play
andpause
should go throughverdi process
. All other commands that onlystrictly display information about the process through the calculation
node proxy, should go in
verdi calculation
andverdi work
.