user-data on OpenNebula restricted to shell sourceable content

Bug #1300941 reported by Scott Moser
6
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://wiki.egi.eu/wiki/Fedcloud-tf:Main)

Related branches

Revision history for this message
Scott Moser (smoser) wrote :

fix-released in 0.7.5.

Changed in cloud-init:
status: New → Fix Committed
importance: Undecided → Medium
status: Fix Committed → Fix Released
Changed in cloud-init (Ubuntu):
status: New → In Progress
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package cloud-init - 0.7.5-0ubuntu1

---------------
cloud-init (0.7.5-0ubuntu1) trusty; urgency=medium

  * New upstream release.
    * support base64 encoded user-data in OpenNebula, required
      to allow arbitrary content in user-data (LP: #1300941)
    * pep8 and pylint fixes
 -- Scott Moser <email address hidden> Tue, 01 Apr 2014 14:39:03 -0400

Changed in cloud-init (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers