deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marios Andreou (JIRA)" <>
Subject [jira] [Commented] (DTACLOUD-358) add user_data (EC2 API) for Openstack instance creation
Date Thu, 08 Nov 2012 10:17:12 GMT


Marios Andreou commented on DTACLOUD-358:

NOT A PROBLEM/CONFUSION - e-mail thread below. closing issue.

> I am not sure exactly what you mean.. the user data as implemented in
> the driver does work, it is simply passed through as a parameter of the
> request.  The request ends up looking just like the one novaclient uses.

tl;dr: thanks for persevering and apologies! I just pushed this patch
with commit id  33bb4363a3e712d2b587177131aff63b8f26c00a (more
explanation below)


longer version ("explain yourself damnit!"):

* there is no mention of 'user_data' parameter in the Compute API v2
spec @
- I filed a bug report against the docs @

* the fact that this patch works is a happy coincidence - I just checked
the 'create_server' code in the openstack gem and saw that besides
checking for some required params (like 'name', 'flavorRef' and
'imageRef') the supplied parameter hash is converted to JSON and passed
through to Openstack unchanged... including the user_data you supply here.

* confusion around the 'EC2 endpoint' due to the fact that as I couldn't
find 'user_data' parameter in the docs, I assumed it was specific to the
(Openstack exposed) EC2 API. Hence my ramble around 'working out' how to
talk to that.

*    o_o "cool story bro"

> add user_data (EC2 API) for Openstack instance creation
> -------------------------------------------------------
>                 Key: DTACLOUD-358
>                 URL:
>             Project: DeltaCloud
>          Issue Type: New Feature
>            Reporter: Marios Andreou
>            Assignee: Marios Andreou
>         Attachments: [PATCH] Add user-data support to openstack driver. - Ian Main
- 2012-11-01 2151.eml

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:

View raw message