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

ASF GitHub Bot commented on LIBCLOUD-930:
-----------------------------------------

GitHub user ldipenti opened a pull request:

    https://github.com/apache/libcloud/pull/1100

    Use TagSpecification parameter on EC2 create_node

    ## Take advantage of AWS EC2 tag-on-create feature
    
    ### Description
    
    This small patch changes the way EC2 compute nodes are tagged when created, 
by adding the tags on the creation call instead of doing it immediately after. 
This avoids eventual consistency issues that sometimes happen when an instance 
isn't created yet so it can't be tagged.
    
    For reference, the AWS docs are here: 
https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_RunInstances.html
    
    This PR would tackle a colleague of mine has reported some weeks ago:
    https://issues.apache.org/jira/browse/LIBCLOUD-930
    
    ### Status
    
    - done, ready for review
    
    ### Checklist (tick everything that applies)
    
    - [ ] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
    - [ ] Documentation
    - [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
    - [X] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes) (I've just submitted it.)

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

    $ git pull https://github.com/curoverse/libcloud apache-libcloud-2.2.0.dev1

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

    https://github.com/apache/libcloud/pull/1100.patch

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

    This closes #1100
    
----

----


> EC2 create_node should supply tag data to RunInstances rather than tagging 
> separately
> -------------------------------------------------------------------------------------
>
>                 Key: LIBCLOUD-930
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-930
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Compute
>            Reporter: Tom Morris
>
> While LIBCLOUD-690 is a real bug, it'd be moot if things were done correctly 
> with the tagging metadata being provided to the AWS RunInstances call where 
> it could be applied atomically with the creation of the node. The current 
> style of doing it in two separate calls allows for a window where nodes can 
> get created without their associated tags, making accounting for them much 
> more difficult.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to