Return-Path: X-Original-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A98DCC283 for ; Tue, 19 Mar 2013 11:02:56 +0000 (UTC) Received: (qmail 13300 invoked by uid 500); 19 Mar 2013 11:02:54 -0000 Delivered-To: apmail-incubator-cloudstack-users-archive@incubator.apache.org Received: (qmail 12989 invoked by uid 500); 19 Mar 2013 11:02:53 -0000 Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-users@incubator.apache.org Delivered-To: mailing list cloudstack-users@incubator.apache.org Received: (qmail 12271 invoked by uid 99); 19 Mar 2013 11:02:53 -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 11:02:53 +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 74.125.83.45 as permitted sender) Received: from [74.125.83.45] (HELO mail-ee0-f45.google.com) (74.125.83.45) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Mar 2013 11:02:48 +0000 Received: by mail-ee0-f45.google.com with SMTP id b57so159639eek.4 for ; Tue, 19 Mar 2013 04:02:27 -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:cc:content-type; bh=R8hMpo+M14PRlbX2mf7ncAsRmNBvzZWnaF2vSwVWvn0=; b=XM5oOVQ6Hs5q0Hz2Io83P5EWM+KK0tLIjqKC0tj7ApbjTgziZNKZxA8ZlGl7PFrMNe JtaA64oSB9Wf5/1WuiQX6uVZ99UB1OZ3emAcmZ2AXvCj9OqbB66jcg1QZexdhkF7MFBF 024F9cFPNbzllxHoC4F49KXE2uRPDPdJ2491ZUjDYIjj11CBqvpnZnUz/WrewqNze1PW FiBfsRBCr0btRpF0o5P8UxF4daQJltfr2T48m14V4vSd+7+286iOXoDTq6jaOMKlhp/L WE2Ciq8mg3SOPYpcLOh/RJaT7SUY1bZ+XAskFsDUHwMPz2gD4/pLh163ghWT8yXS78ph 1qsw== X-Received: by 10.14.207.200 with SMTP id n48mr59603392eeo.4.1363690947233; Tue, 19 Mar 2013 04:02:27 -0700 (PDT) MIME-Version: 1.0 Sender: rohityadav89@gmail.com Received: by 10.223.157.10 with HTTP; Tue, 19 Mar 2013 04:02:06 -0700 (PDT) In-Reply-To: References:

<90166C9A-26AF-4506-ADA7-DDEC60BF7D43@gmail.com>

From: Rohit Yadav Date: Tue, 19 Mar 2013 16:32:06 +0530 X-Google-Sender-Auth: oC5pFNc3MjAtpn-67qT45xTbsRU Message-ID: Subject: Re: [DISCUSS] CloudMonkey profiles to manage multiple CS instances To: cloudstack-dev@incubator.apache.org, "Musayev, Ilya" Cc: cloudstack-users@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Hi All, In the latest cloudmonkey, one can pass a config file using -c to run cloudmonkey with a different config. profile, the default will be ~/.cloudmonkey/config. This would allow you to run multiple cloudmonkey's with different config profiles. I've uploaded the latest snapshot for everyone to install, try out and report any bugs, suggestions, features. Thanks. Usage: cloudmonkey -v cloudmonkey -h # cp ~/.cloudmonkey/config myconfig # edit my config cloudmonkey -c Cheese shop: https://pypi.python.org/pypi/cloudmonkey/4.1.0-snapshot Upgrade: sudo pip install --upgrade cloudmonkey Regards. On Tue, Mar 19, 2013 at 1:33 PM, Rohit Yadav wrote: > 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 >>>>> >> >>