Re: [one-users] Documentation
Dear Daniel, It was a minor point. If you look for the following in the document you linked: Entry Resources (ER) GET: to list the information associated with that resource PUT: to update the resource (only supported by the COMPUTE resource) DELETE: to delete the resource You can see that it calls out the COMPUTE resource. It's the same with the v3.0 OCCI API documentation. Also, thank you for taking into consideration my suggestion. -- Hutson Betts Computer Science and Engineering Texas AM University On Mon, 2011-12-05 at 18:33 +0100, Daniel Molina wrote: On 4 December 2011 23:32, Hutson Betts hut...@tamu.edu wrote: I've noticed that the documentation for OCCI could use a little updating. The OCCI User's Guide instructs users on how to update existing entity resources. However, the OCCI API Document says that only the Compute Resource can be updated. What document are you looking at?, the following page was updated days ago: http://www.opennebula.org/documentation:rel3.2:occidd Also, in the User's Guide, could Hello OCCI Cloud! be changed to something like Create resources to better fit the flow of title names. Changed, thanks for your feedback. Cheers. -- Hutson Betts Computer Science and Engineering Texas AM University ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org signature.asc Description: This is a digitally signed message part ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] Documentation
I've noticed that the documentation for OCCI could use a little updating. The OCCI User's Guide instructs users on how to update existing entity resources. However, the OCCI API Document says that only the Compute Resource can be updated. Also, in the User's Guide, could Hello OCCI Cloud! be changed to something like Create resources to better fit the flow of title names. -- Hutson Betts Computer Science and Engineering Texas AM University signature.asc Description: This is a digitally signed message part ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] Documentation
Potential Documentation Issues: There are a few documentation issues which can be found here (http://opennebula.org/documentation:rel3.0:occiug) On the Storage example there are two definitions for the Storage entity, and, for which, one is blank: $ occi-storage --url http://localhost:4567 --username oneadmin --password opennebula create image.xml STORAGE href='http://0.0.0.0:4567/storage/3' /STORAGE STORAGE href='http://localhost:4567/storage/0' ID3/ID NAMEUbuntu Desktop/NAME TYPEOS/TYPE DESCRIPTIONUbuntu 10.04 desktop for students./DESCRIPTION PUBLICNO/PUBLIC PERSISTENTNO/PERSISTENT SIZE41943040/SIZE /STORAGE On the Compute example there is an id attribute which I don't believe should be there: DISK id='0' STORAGE href='http://0.0.0.0:4567/storage/3' name='Ubuntu Desktop'/ TYPEDISK/TYPE TARGEThda/TARGET /DISK On the Using the Cloud page, each Storage Entity is name attribute. However, on the OCCI API page for the OpenNebula 3.0 documentation, each Storage Entity is only given a href attribute. Which documentation is correct? On the OpenNebula OCCI User Guide 3.0 I see the following example in which the STATE value is in all caps: $ occi-compute --url http://localhost:4567 --username oneadmin --password opennebula create vm.xml COMPUTE href='http://0.0.0.0:4567/compute/0' ID0/ID CPU1/CPU MEMORY1024/MEMORY NAMEMyCompute/NAME INSTANCE_TYPEsmall/INSTANCE_TYPE STATEPENDING/STATE DISK id='0' STORAGE href='http://0.0.0.0:4567/storage/3' name='Ubuntu Desktop'/ TYPEDISK/TYPE TARGEThda/TARGET /DISK NIC NETWORK href='http://0.0.0.0:4567/network/0' name='MyServiceNetwork'/ IP192.168.1.12/IP MAC02:00:c0:a8:01:0c/MAC /NIC CONTEXT DATADATA1/DATA HOSTNAMEMAINHOST/HOSTNAME TARGEThdb/TARGET /CONTEXT /COMPUTE However, on the OpenNebula OCCI Specification 3.0 page, the values for the state of a Compute Resource are show in lower caps. Which is it? -- Hutson Betts Computer Science and Engineering Texas AM University signature.asc Description: This is a digitally signed message part ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Documentation for imagepool.info in http://www.opennebula.org/documentation:rel2.0:api incomplete
Hi Carsten, The documentation is now updated, thanks for the feedback! Regards, Carlos. Carlos Martín, Cloud Technology Engineer/Researcher DSA Research Group: web http://dsa-research.org and blog http://blog.dsa-research.org OpenNebula Open Source Toolkit for Cloud Computing: http://www.OpenNebula.org On 28 September 2010 08:20, carsten.friedr...@csiro.au wrote: The information on http://www.opennebula.org/documentation:rel2.0:apiabout the imagepool.info call is incomplete. The call expects one more int input parameter. Carsten ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] Documentation for imagepool.info in http://www.opennebula.org/documentation:rel2.0:api incomplete
The information on http://www.opennebula.org/documentation:rel2.0:api about the imagepool.info call is incomplete. The call expects one more int input parameter. Carsten ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
