incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sebastien Goasguen <run...@gmail.com>
Subject Re: [DISCUSS] CloudMonkey profiles to manage multiple CS instances
Date Tue, 19 Mar 2013 12:24:41 GMT


On Mar 19, 2013, at 7:02 AM, Rohit Yadav <bhaisaab@apache.org> wrote:

> Hi All,
> 
> In the latest cloudmonkey, one can pass a config file using -c <cfg
> file> 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 <myconfig> <cmds and args>
> 

the cache and the log file will be common or relative to the directory you started cloud monkey
in ?

> 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 <bhaisaab@apache.org> wrote:
>> On Tue, Mar 19, 2013 at 8:46 AM, Musayev, Ilya <imusayev@webmd.net> 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 <profile> <commands>.
>> 
>> 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 <cfg file>
>> 
>> Thoughts?
>> 
>> Regards.
>> 
>>> 
>>> Thanks
>>> Ilya
>>> 
>>> 
>>> 
>>> -------- Original message --------
>>> From: Sebastien Goasguen <runseb@gmail.com>
>>> 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 <bhaisaab@apache.org> wrote:
>>> 
>>>> On Tue, Mar 19, 2013 at 1:44 AM, Ahmad Emneina <aemneina@gmail.com>
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 <imusayev@webmd.net>
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
>>>>>> 
>>> 
>>> 


Mime
View raw message