[
https://issues.apache.org/jira/browse/DTACLOUD-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ronelle Landy closed DTACLOUD-416.
----------------------------------
Fixed in deltacloud commit version: d590860be39300a3105f2eec1c7304697dd91d65
Decoded user-data returned when creating an instance using just the Deltacloud
server + curl client - not ruby client.
> No Base64 Decoding Openstack Driver
> -----------------------------------
>
> Key: DTACLOUD-416
> URL: https://issues.apache.org/jira/browse/DTACLOUD-416
> Project: DeltaCloud
> Issue Type: Bug
> Components: Native/Frontend
> Environment: Deltacloud commit version:
> b88656bfc0390fc5f9675b800fc1039e2d51cf09
> Openstack provider (RHOS- Essex)
> Reporter: Ronelle Landy
> Assignee: Ronelle Landy
> Attachments:
> 0001-DTACLOUD-416-do-not-base64-encode-the-user-data.patch
>
>
> Using just the Deltacloud server pointing at a RHOS provider, I:
> * created an instance with user_data (Base64 encode once)
> * created and attached a floating ip (using nova)
> * ssh'ed to the instance
> * >> curl -s GET http://169.254.169.254/latest/user-data (to find the
> user_data)
> The user_data was returned (yay!) but in the same state of Base64 encoding in
> which it was passed to the instance on creation. As I understand, with other
> providers, using just the server and not any of the Ruby clients, the data is
> returned - Base64 decoded (one time).
> What is the correct situation for Openstack?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
