Merge lp:~enolfc/cloud-init/opennebula-b64-userdata into lp:~cloud-init-dev/cloud-init/trunk
Status: | Merged |
---|---|
Merged at revision: | 971 |
Proposed branch: | lp:~enolfc/cloud-init/opennebula-b64-userdata |
Merge into: | lp:~cloud-init-dev/cloud-init/trunk |
Diff against target: |
88 lines (+37/-4) 2 files modified
cloudinit/sources/DataSourceOpenNebula.py (+12/-0) tests/unittests/test_datasource/test_opennebula.py (+25/-4) |
To merge this branch: | bzr merge lp:~enolfc/cloud-init/opennebula-b64-userdata |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
cloud-init Commiters | Pending | ||
Review via email: mp+212646@code.launchpad.net |
Description of the change
This change adds the possibility to have base64 encoded userdata in OpenNebula source.
OpenNebula uses a text file with shell variables for storing the configuration variables (including user provided data). Some user data may not be renderable into this format, so using base64 encoding alleviates the problem. This change considers that, by default, USERDATA variable contains a base64 encoded string with the user provided data. This behavior can be deactivated by defining the USERDATA_ENCODING variable to anything different to "base64" (similarly to the Azure data source).
This feature is of special interest for resource providers with rOCCI-server front-end as the ones in EGI's Federated Cloud (https:/
Unit tests for the change are included.