libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (LIBCLOUD-356) Provide user-data for Openstack driver
Date Sat, 28 Jun 2014 11:55:24 GMT


ASF GitHub Bot commented on LIBCLOUD-356:

GitHub user stickystyle opened a pull request:

    [LIBCLOUD-356] Add config_drive to support user_data


You can merge this pull request into a Git repository by running:

    $ git pull patch-1

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #330
commit 23b4f14a41a4822cea7b598d529379529300d018
Author: Ryan Parrish <>
Date:   2014-06-28T11:51:14Z

    [LIBCLOUD-356] Add config_drive to support user_data


> Provide user-data for Openstack driver
> --------------------------------------
>                 Key: LIBCLOUD-356
>                 URL:
>             Project: Libcloud
>          Issue Type: Improvement
>          Components: Compute
>    Affects Versions: 0.12.3
>         Environment: Libcloud 0.13.0 against Openstack
>            Reporter: Mattieu Puel
>              Labels: cloud-init, openstack, userdata
>             Fix For: 0.12.3
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
> libcloud openstack's driver supports parameter "user-data" (namely ex_userdata) for providing
user data to the instance. This is the equivalent to "nova boot --user-data" parameter.
> With Openstack nova command, this results in providing the content of the pointed file.
You may for instance provide a shell script, a configuration file for cloud-init...
> Once the VM startups, cloud-init retrieves the file from the metadata server and uses
it (executes it for shell scripts for instance).
> The libcloud behaviour is different: it simply passes the parameter content as is.

This message was sent by Atlassian JIRA

View raw message