[LIBCLOUD-296] Proposal to add a node state - STOPPED - to the standard list of states.

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.11.2
• Fix Version/s: 0.14.0-beta3
• Component/s: Compute
• Assignee: Unassigned
• Reporter: Jay Kumar
• Created: 09/Feb/13 16:09
• Updated: 05/Aug/14 13:57
• Resolved: 22/Oct/13 08:50

Description

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