user-data on OpenNebula restricted to shell sourceable content
Bug #1300941 reported by
Scott Moser
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Fix Released
|
Medium
|
Unassigned | ||
cloud-init (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
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:/
Related branches
lp:~enolfc/cloud-init/opennebula-b64-userdata
- cloud-init Commiters: Pending requested
-
Diff: 88 lines (+37/-4)2 files modifiedcloudinit/sources/DataSourceOpenNebula.py (+12/-0)
tests/unittests/test_datasource/test_opennebula.py (+25/-4)
To post a comment you must log in.
fix-released in 0.7.5.