[
https://issues.apache.org/jira/browse/DTACLOUD-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marios Andreou updated DTACLOUD-257:
------------------------------------
Attachment: 0001-Updates-for-Opennebula-driver-brings-compatibility-f.patch
thanks - ok try this updated patch fixes the images issue you saw
one thing I noticed from quick testing... unless I'm mistaken there is no
notion of 'restart/reboot' for a running machine anymore. Trying the 'reboot'
action gave me an error... after investigation I noticed that:
for API v 3.2 (the version driver was last updated for):
http://opennebula.org/documentation:archives:rel3.2:occiug#change_the_compute_state
for API v3.6 (current):
http://opennebula.org/documentation:archives:rel3.0:vm_guide_2#virtual_machine_life-cycle
waiting for input from Daniel
> opennebula driver stop instance request
> ---------------------------------------
>
> Key: DTACLOUD-257
> URL: https://issues.apache.org/jira/browse/DTACLOUD-257
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: ruby1.8, deltacloud-core-1.0.0, deltacloud-core-head
> Reporter: Christian Karnath
> Assignee: Marios Andreou
> Attachments:
> 0001-Updates-for-Opennebula-driver-brings-compatibility-f.patch
>
>
> When POSTing /api/instances/<inst>/stop on a running instance against the
> opennebula-driver the following error occurs:
> Deltacloud::ExceptionHandler::ProviderError - [VirtualMachineAction] Wrong
> state to perform action
> I am running ruby 1.8.7 and requesting with cURL:
> curl -H "X-Deltacloud-Driver: opennebula" -H "X-Deltacloud-Provider:
> http://occi.c12g.com"; -v -u xxx:yyy
> http://localhost:3001/api/instances/2660/stop -d" "
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
