Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2FFF118AAF for ; Fri, 24 Apr 2015 09:01:43 +0000 (UTC) Received: (qmail 38346 invoked by uid 500); 24 Apr 2015 09:01:42 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 38295 invoked by uid 500); 24 Apr 2015 09:01:42 -0000 Mailing-List: contact dev-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 dev@cloudstack.apache.org Received: (qmail 38284 invoked by uid 99); 24 Apr 2015 09:01:42 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Apr 2015 09:01:42 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 3266CE0385; Fri, 24 Apr 2015 09:01:42 +0000 (UTC) From: agneya2001 To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: tool to aid db comaprision for upgrade te... Content-Type: text/plain Message-Id: <20150424090142.3266CE0385@git1-us-west.apache.org> Date: Fri, 24 Apr 2015 09:01:42 +0000 (UTC) Github user agneya2001 commented on the pull request: https://github.com/apache/cloudstack/pull/188#issuecomment-95858828 Was thinking of more of a script with a wizard interface, instead of bunch of scripts, that guides the user during upgrade. Some suggestions: A way to fix mismatched configuration like prompt user with missing config and accept values ? On another side, if this kind of functionality is integrated with upgrade itself, that warns user about changed configs after upgrades etc. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---