jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-1025) Add support for user data in DigitalOcean
Date Sun, 25 Oct 2015 23:14:27 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973484#comment-14973484
] 

ASF subversion and git services commented on JCLOUDS-1025:
----------------------------------------------------------

Commit aeee5911e393268c8d85dc6e564a66b70e904cc6 in jclouds-labs's branch refs/heads/master
from [~nacx]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-labs.git;h=aeee591 ]

JCLOUDS-1025: Add support for metadata and tags in the ComputeService


> Add support for user data in DigitalOcean
> -----------------------------------------
>
>                 Key: JCLOUDS-1025
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1025
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-labs
>    Affects Versions: 1.9.1
>            Reporter: Ignasi Barrera
>            Assignee: Ignasi Barrera
>              Labels: digitalocean
>             Fix For: 2.0.0
>
>
> DigitalOcean now supports setting the {{user_data}} string when creating a droplet. That
is made available from inside the droplet via the metadata api:
> https://developers.digitalocean.com/documentation/metadata/#user-data
> jclouds should take into account the user data provided in the template options and create
the droplets accordingly.
> Note that this is not supported in all regions: jclouds should only set the user data
when deploying droplets in a region that supports the metadata.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message