New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
one_vm: moved to pyone added Persisten Deployment #57393
Conversation
Moved from python-oca to pyone. Added Persistent deployment of VMs.
The test
The test
The test
The test
The test
The test
The test
The test
The test
The test
The test
The test
The test
The test
The test
The test
The test
|
The test
The test
The test
|
The test
The test
The test
|
LGTM |
Poking @ilicmilan @kustodian @rsmontero @xorel i would like to maintain more of the Opennebula Modules any idea where to address this? |
Thanks, @meerkampdvv for the interest! I just opened #62281 So let's wait for the ansible bots and Rubens approval. |
@xorel could you take a look test on your side ? |
I found some issues but they are not related to the oca -> pyone transition, so I will try to fix them separately. |
LGTM |
SUMMARY
Moved from python-oca to pyone which is the current python module shipped with Opennebula
Added Persistent deployment of VMs. #49550
ISSUE TYPE
ADDITIONAL INFORMATION
In the latest official documentation [1] is said that pyone is the current python module to be installed with OpenNebula, so if it is not compatible with python-oca, the ansible module should use pyone instead of python-oca.
[1] http://docs.opennebula.org/5.8/deployment/opennebula_installation/frontend_installation.html