[
https://issues.apache.org/jira/browse/LIBCLOUD-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13575339#comment-13575339
]
Jayyy V commented on LIBCLOUD-296:
----------------------------------
You are correct. It may break existing clients and I think preserving it under
a new name (like 'old_state') still breaks but just an option to fix it back.
Just tried to attempt a way we could introduce this without breaking.
#1 Instead of old_state, we shall try new_state.
It won't break existing clients. And is available for interested parties. But
again, we need efforts to migrate from new_state -> state.
#2 How about an environment variable LIBCLOUD_UPGRADE ? (like LIBCLOUD_DEBUG)
We shall apply the upcoming changes when this flag is set. Otherwise, raise a
deprecation warning.
This way, new changes will become available for those who are ready to pick it
up and a deprecation warning for others.
> Proposal to add a node state - STOPPED - to the standard list of states.
> ------------------------------------------------------------------------
>
> Key: LIBCLOUD-296
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-296
> Project: Libcloud
> Issue Type: Improvement
> Components: Compute
> Affects Versions: 0.11.2
> Reporter: Jayyy V
> Priority: Minor
>
> With providers like EC2, a node can be stopped and started again.
> STOPPED - is a reasonably useful state to determine the nodes that are just
> stopped but not terminated and initiate a start operation, if required.
> Currently a EC2 stopped node is being mapped to UNKNOWN state. Without a
> STOPPED state, we are losing an important information with all the providers
> who supports this state.
> A sample ec2 node data in stopped state
> ------------------------------------------------------------
> {'private_ips': [], 'extra': {'status': 'stopped', 'productcode': [],
> 'groups': [None], 'tags': {}, 'instanceId': 'i-f9654189', 'dns_name': '',
> 'launchdatetime': '2013-02-09T15:35:09.000Z', 'imageId': 'ami-3fec7956',
> 'kernelid': 'aki-88aa75e1', 'keyname': 'jv', 'availability': 'us-east-1c',
> 'clienttoken': 'pfoKe1360424109512', 'launchindex': '0', 'ramdiskid': None,
> 'private_dns': '', 'instancetype': 't1.micro'}, 'image': None, '_uuid': None,
> 'driver': <libcloud.compute.drivers.ec2.EC2NodeDriver object at 0x9bbbbac>,
> 'state': 4, 'public_ips': [], 'size': None, 'id': 'i-f9654189', 'name':
> 'i-f9654189'}
> Thanks,
> Jayyy V
--
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
