Hi,
Are you using the 3.2 java OCA? The authentication changed a bit, take a
look at
http://opennebula.org/documentation:rel3.2:compatibility#developers_and_integrators
Regards.
--
Carlos Martín, MSc
Project Engineer
OpenNebula - The Open-source Solution for Data Center Virtualization
www.OpenNeb
Hi.
After upgrading to OpenNebula 3.2 we can no longer connect with Java client.
I use:
Client client = new Client("oneadmin:passwd", "http://ip_addr:2633/RPC2";);
OneResponse or = .
I get response: User couldn't be authenticated, aborting call.
It worked fine before.
Any suggestions?
___
Hi Carlos,
Thanks for your precious help, I will take a look at the sources.
Best regards,
Enrico
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Hi Enrico,
The Java API was designed as a wrapper for the XML-RPC API with some basic
helper methods, but it is not too high level oriented.
You have to know the internal xml structure of the data returned, and query
it using xpath expressions. Take a look at getName() and state() in
PoolElement.j
Hi,
I'm doing some experiments with OpenNebula 2.0 beta and the Java API. I would
like to know if there is a way (an exposed method) to know the relevant stats
about a Host (like RVM, TCPU, FCPU, FMEM etc.), because after a couple of tests
I didn't find anything. These are the stats that are a
