Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C20271111F for ; Wed, 21 May 2014 12:19:38 +0000 (UTC) Received: (qmail 73502 invoked by uid 500); 21 May 2014 12:19:38 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 73420 invoked by uid 500); 21 May 2014 12:19:38 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 73324 invoked by uid 500); 21 May 2014 12:19:38 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 73290 invoked by uid 99); 21 May 2014 12:19:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 May 2014 12:19:38 +0000 Date: Wed, 21 May 2014 12:19:38 +0000 (UTC) From: "Santhosh Kumar Edukulla (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (CLOUDSTACK-6158) [Marvin]: DeployDataCenter Enhancements 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/CLOUDSTACK-6158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-6158. ------------------------------------------------- Resolution: Fixed > [Marvin]: DeployDataCenter Enhancements > --------------------------------------- > > Key: CLOUDSTACK-6158 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6158 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: Automation, marvin > Reporter: Santhosh Kumar Edukulla > Assignee: Santhosh Kumar Edukulla > > Following are the issues with deploy data center: > 1. There is no way to delete a data center created earlier. Added a new DeleteDataCenter Interface to delete the earlier created datacenter. If user wants to delete a datacenter created and recreate, deleting has to be manual earlier. With this change, he can delete a data center created earlier. It will be useful at many places for testing to destroy and recreate with new settings etc. > 2. when deploy data center runs, it does not adequately verifies whether a given entry is created or not, it just continues. Added checks to see if an entry is not successful, it reports, dumps to log and exit gracefully. > 3. DataCenter creation as Transaction : At any given point of time during deploy data center, if an issue happens half way through, earlier created entries were still available in CS, it wont clean up i.e., data center is half created, Again, if tried to recreate , the earlier existing entries wont allow to recreate. Now, data center works as transaction, either all entries are created as part of data center or none, added a clean up to delete the half created data center. > 4. Export the created Data Center so that user can use it to further delete the data center with these exported entries etc. > -- This message was sent by Atlassian JIRA (v6.2#6252)