In #203 we found out that orchestration state/status which is returned
by opera info could be improved. This has been done now and xOpera now
provides the following orchestration states (the are also CLI commands
that trigger changing the state in the brackets):
initialized (opera init)
deploying (opera deploy)
deployed (opera deploy)
undeploying (opera undeploy)
undeployed (opera undeploy)
error (opera deploy/undeploy/update/notify)
unknown (for special cases which might happen)
These state are changed during the execution of TOSCA interface
operations (e.g. Ansible playbooks). We had to modify our CLI commands
a little and also our integration tests.
In #203 we found out that orchestration state/status which is returned by opera info could be improved. This has been done now and xOpera now provides the following orchestration states (the are also CLI commands that trigger changing the state in the brackets):
initialized(opera init)deploying(opera deploy)deployed(opera deploy)undeploying(opera undeploy)undeployed(opera undeploy)error(opera deploy/undeploy/update/notify)unknown(for special cases which might happen)These state are changed during the execution of TOSCA interface operations (e.g. Ansible playbooks). We had to modify our CLI commands a little and also our integration tests.