Update OCCI specification
|Assignee:||Tino Vázquez||% Done:|
|Category:||Client API & Library|
This feature aims to update the OCCI implementation and make it compliant with the last specification produced by the group (specially HTML header, HTML5 rendering...)
Also we can revise the XML render to include additional VM attributes like GRAPHICS. This must be discussed from the public Cloud point of view, i.e. does it make sense to have a VNC port open for a VM running in a public Cloud?
#1 Updated by Gyula Csom almost 11 years ago
"does it make sense to have a VNC port open for a VM running in a public Cloud" yes:) It lets users to connect to a running virtual machine in every cicumstances, eg. independent from the guest OS, even if SSH doesn't work for some reason, RDP is turned off, etc. So VNC gives a reliable terminal service, a fall back if nothing else works.
#2 Updated by Gyula Csom almost 11 years ago
Currently HTTP Header and X/HTML seems to be the only supported OCCI formats (see #243):( Since these formats contradict with our programming conventions, we do not want to live with them, if possible. Meanwhile we'd like to use the OCCI interface, or an interface that's functionally equivalent with it (eg. supports image upload, vnet creation), however there's no such alternate interface, yet (neither ec2, or deltacloud, or libcloud supports vnet creation). So:
May I kindly ask you about your plans? Is there a chance that you drop the OCCI+POX interface? or put it into maintanance mode (bugfixes only)?
Since we will start with 1.4, a possible drop might generate migration issues for us. We'd like to prepare ourselves for such a case.
#5 Updated by Ruben S. Montero about 10 years ago
- Status changed from New to Closed
- Resolution set to worksforme
The POX representation for OpenNebula has been updated to level the functionality offered by the XML-RPC interface. We will open this issue again once the OCCI specification enters a final state.