Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ECEA6E851 for ; Tue, 19 Mar 2013 08:04:20 +0000 (UTC) Received: (qmail 25185 invoked by uid 500); 19 Mar 2013 08:04:20 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 24750 invoked by uid 500); 19 Mar 2013 08:04:20 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 24732 invoked by uid 99); 19 Mar 2013 08:04:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Mar 2013 08:04:19 +0000 X-ASF-Spam-Status: No, hits=-0.5 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rohityadav89@gmail.com designates 209.85.215.172 as permitted sender) Received: from [209.85.215.172] (HELO mail-ea0-f172.google.com) (209.85.215.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Mar 2013 08:04:15 +0000 Received: by mail-ea0-f172.google.com with SMTP id d10so79749eaj.3 for ; Tue, 19 Mar 2013 01:03:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=c8Njb3TjillvqdcDH600Hbb5wKgTEoZO8KHixIZPvrQ=; b=RCKoIBtOpslSlcefj3g3Y8cvpR4oTzDIQd/cra9s00JkLsNWzTpNcOuq5lDeftaG6O dcJLvAXC+Dp3MnOq7TxlAze3pO3Ia5F0k6ZBOK3gv1eZCxzrJJVTD/GjP+w5Px+RzQgH oXkwOY8pR7g5SSJD3WHBXjX7LxIUcXsv2jUuxQrg3wcUjezhwMfc7S1CM7rbSCCsN4Iv GwQUk+oTKWvKFkGyOGiKe9CidVa/S+3q1Ect3CJ+WBuoDNaXOBw5L6gsvtYhWo4YXi0p TpKQ0gGCAZYsc/NOU8LQ6kjjgA7ggHK0Of1sqC2+NYF/yn/OINGdv7MYjuzlAoqOsK8Q TnNw== X-Received: by 10.14.225.72 with SMTP id y48mr57854430eep.45.1363680234291; Tue, 19 Mar 2013 01:03:54 -0700 (PDT) MIME-Version: 1.0 Sender: rohityadav89@gmail.com Received: by 10.223.157.10 with HTTP; Tue, 19 Mar 2013 01:03:34 -0700 (PDT) In-Reply-To: References: <90166C9A-26AF-4506-ADA7-DDEC60BF7D43@gmail.com> From: Rohit Yadav Date: Tue, 19 Mar 2013 13:33:34 +0530 X-Google-Sender-Auth: Uw6OdtN4n_dNEp5urYDxmzCyOEg Message-ID: Subject: Re: [DISCUSS] CloudMonkey profiles to manage multiple CS instances To: cloudstack-dev@incubator.apache.org, "Musayev, Ilya" Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Mar 19, 2013 at 8:46 AM, Musayev, Ilya wrote: > Why dont we keep the same config and just have multiple servers defined in single config file. > > The shell prompt can then display the env name you are working on. > > Example of prompt: > Cloudmonkey [ACS41QA] # Hi Ilya, What you're suggesting can also work, the problem is tricky when people use cloudmonkey as shell tool. Using the interactive shell, you can fire up multiple instances and using set command you can have various profiles in memory (each cloudmonkey has different host, port, path, api, secret keys etc.), using various profiles in one cfg would mean users would use something like sql's use statement to use a profile; again becomes tricky as shell tool, so for each call you do something like cloudmonkey -P . So, I think it would be best if one keeps all their cfgs in ~/.cloudmonkey/config{0,1,2,3...} and calls cloudmonkey with default cfg in ~/.cloudmonkey/config or using: cloudmonkey -c Thoughts? Regards. > > Thanks > Ilya > > > > -------- Original message -------- > From: Sebastien Goasguen > Date: > To: cloudstack-dev@incubator.apache.org > Cc: aemneina@gmail.com > Subject: Re: [DISCUSS] CloudMonkey profiles to manage multiple CS instances > > > > On Mar 18, 2013, at 4:19 PM, Rohit Yadav wrote: > >> On Tue, Mar 19, 2013 at 1:44 AM, Ahmad Emneina wrote: >>> +1 I was actually wishing for this, this morning! >> >> Alright will push the change tomorrow, the fix is simple, we'll also >> change fixed/hard-coded caching file path and add option for people to >> configure colors (themes for cloudmonkey colored output). >> > > Could you provide default paths ( I like the way it is right now :) ) > > I don't want to provide paths of config file as param every time... > >> Cheers. >> >>> >>> >>> On Mon, Mar 18, 2013 at 12:20 PM, Musayev, Ilya wrote: >>> >>>> Would like to get the feel of what community thinks of having "profile" >>>> abilities in CloudMonkey. >>>> >>>> I have multiple CS instances at the moment and AFAIK I have to reconfigure >>>> CloudMonkey for each when I have to switch - when working on my desktop. >>>> >>>> Alternative, I could probably create multiple shell users and switch >>>> between each or do some other magic like swapping config files, but it >>>> would be nice just to switch between profiles just like we do in git >>>> between branches from within CloudMonkey shell. >>>> >>>> Your input is welcome, >>>> >>>> Thanks >>>> ilya >>>> > >