Return-Path: X-Original-To: apmail-libcloud-commits-archive@www.apache.org Delivered-To: apmail-libcloud-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 84717109C4 for ; Tue, 22 Oct 2013 08:51:50 +0000 (UTC) Received: (qmail 53202 invoked by uid 500); 22 Oct 2013 08:51:44 -0000 Delivered-To: apmail-libcloud-commits-archive@libcloud.apache.org Received: (qmail 53115 invoked by uid 500); 22 Oct 2013 08:51:43 -0000 Mailing-List: contact commits-help@libcloud.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@libcloud.apache.org Delivered-To: mailing list commits@libcloud.apache.org Received: (qmail 53095 invoked by uid 99); 22 Oct 2013 08:51:42 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Oct 2013 08:51:42 +0000 Date: Tue, 22 Oct 2013 08:51:41 +0000 (UTC) From: "Tomaz Muraus (JIRA)" To: commits@libcloud.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (LIBCLOUD-296) Proposal to add a node state - STOPPED - to the standard list of states. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/LIBCLOUD-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomaz Muraus resolved LIBCLOUD-296. ----------------------------------- Resolution: Fixed Merged into trunk, thanks! > 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: Jayy Vis > 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': , 'state': 4, 'public_ips': [], 'size': None, 'id': 'i-f9654189', 'name': 'i-f9654189'} > Thanks, > Jayyy V -- This message was sent by Atlassian JIRA (v6.1#6144)