Hi all,

I am experiencing the problem described in
https://issues.apache.org/jira/browse/JCLOUDS-317. Basically the problem is
that jclouds does not have the status "SHUTOFF" and jclouds is mapping from
Openstack "SHUTOFF" status to jclouds "UNRECOGNIZED" status.

I understand that the solution is very easy and I am willing to contribute
a fix. However, in the project I am working on, we would need a short-term
solution. My question is: could you think of any workaround we could use
until a new version of jclouds including the fix for JCLOUDS-317 is
released?

I have already asked in the #jclouds IRC channel and I have been answered
that probably there is no workaround, but I was advised to ask further.

I hope that the question is appropriate for this mailing list.

Thanks in advance,
Jacob

Reply via email to