We’re in the prototyping phase of a deployment of vOneCloud 1.8 and are hoping to set up some automation via the python-oca.
At this stage though I’m getting a nothing but an authentication error when I try to communicate with OpenNebula:
ian@ian-laptop:~/Desktop$ python test2.py
Traceback (most recent call last):
File “test2.py”, line 4, in
File “build/bdist.linux-x86_64/egg/oca/pool.py”, line 104, in info
File “build/bdist.linux-x86_64/egg/oca/init.py”, line 124, in call
oca.exceptions.OpenNebulaException: [HostPoolInfo] User couldn’t be authenticated, aborting call.
I’ve stripped down the script I’m running to what I can see as the bear minimum for it to attempt to communicate with the server at all:
I’ve tried several different users; CloudAdmin, oneadmin and created users.
I’ve ran this on both my ubuntu laptop communicating with vOC across the network and on the vOC server (by placing the python-oca files in place rather than a proper integration of them, then communicating with 127.0.0.1) and I get the same error across both.
I have seen that portions of this error show up elsewhere online for people who are configuring ONE and need to use the one_auth file and have tried adding this but to no change, and it doesn’t quite seem to logically fit as I’m specifying authentication through the script anyway.
Does anyone have any thoughts or suggestions about a next step? Does anyone have python-oca working for them?