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

Adrian Cole commented on JCLOUDS-43:
------------------------------------

created https://github.com/jclouds/jclouds/pull/9 by doing..

git revert --no-commit f88609d1dd05b88ca5124b60359613210503f506
git status
git rm 
providers/ultradns-ws/src/main/java/org/jclouds/ultradns/ws/ScopedTransaction.java
git rm 
providers/ultradns-ws/src/test/java/org/jclouds/ultradns/ws/ScopedTransactionExpectTest.java
git rm 
providers/ultradns-ws/src/test/java/org/jclouds/ultradns/ws/ScopedTransactionLiveTest.java
git revert --continue
git revert --no-commit b021d743fde13632c2da1bee8b999646a096c314
git status
git rm 
providers/ultradns-ws/src/main/java/org/jclouds/ultradns/ws/features/TransactionApi.java
git rm 
providers/ultradns-ws/src/test/java/org/jclouds/ultradns/ws/features/TransactionApiExpectTest.java
git rm 
providers/ultradns-ws/src/test/java/org/jclouds/ultradns/ws/features/TransactionApiLiveTest.java
git status
git revert --continue
mvn clean install
                
> UltraDNS Transaction support
> ----------------------------
>
>                 Key: JCLOUDS-43
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-43
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-core
>    Affects Versions: 1.6.0
>            Reporter: Adrian Cole
>            Assignee: Adrian Cole
>             Fix For: 1.7.0, 1.6.1
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> When testing the ultradns-ws provider, Netflix noticed that migrating 
> territories from one directional group to another to results in a drop of 
> traffic and slow recovery.  The root cause is how updates must occur 
> considering territory overlaps are illegal.
> Ex. first remove argentina from group a.  next add argentina to group b.
> Advice is to wrap the two commands into a transaction, which may eliminate 
> some traffic loss scenarios.
> Implementation:
> expose a TransactionApi and a corresponding scope to attribute the 
> transaction to any write commands within it.

--
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

Reply via email to