Hey Ilya,
Glad to know that helps you, get the latest; pip install --upgrade cloudmonkey
and report and bugs, features!
Cheers.
On Tue, Mar 19, 2013 at 8:16 PM, Musayev, Ilya <imusa...@webmd.net> wrote:
> Rohit
>
> Config files work as well and probably better than my approach if you are
> scripting and using cloudmonkey.
>
> Thank you
> -ilya
>
>
>
> -------- Original message --------
> From: Rohit Yadav <bhais...@apache.org>
> Date:
> To: cloudstack-dev@incubator.apache.org,"Musayev, Ilya" <imusa...@webmd.net>
> Subject: Re: [DISCUSS] CloudMonkey profiles to manage multiple CS instances
>
>
> On Tue, Mar 19, 2013 at 8:46 AM, Musayev, Ilya <imusa...@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 <run...@gmail.com>
>> Date:
>> To: cloudstack-dev@incubator.apache.org
>> Cc: aemne...@gmail.com
>> Subject: Re: [DISCUSS] CloudMonkey profiles to manage multiple CS instances
>>
>>
>>
>> On Mar 18, 2013, at 4:19 PM, Rohit Yadav <bhais...@apache.org> wrote:
>>
>>> On Tue, Mar 19, 2013 at 1:44 AM, Ahmad Emneina <aemne...@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 <imusa...@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
>>>>>
>>
>>
>
