Ilya, can you check/share your cloudmonkey version? Probably you can
uninstall and reinstall latest cloudmonkey (sometimes pip upgrades may not
work due to compiled pyc files in the path). `filter` was added in
cloudmonkey several months (maybe one year?) ago and should work, unless
the problem is
On Mar 28, 2014, at 6:46 PM, ilya musayev wrote:
> Hi Sebastian,
>
> I tried, does not do anything.
strange, I use it all the time.
>
> Regards
> ilya
>
> On 3/26/14, 10:13 AM, Sebastien Goasguen wrote:
>> On Mar 26, 2014, at 12:55 PM, ilya musayev
>> wrote:
>>
>>> Hi Rohit,
>>>
>>> Wha
Hi Sebastian,
I tried, does not do anything.
Regards
ilya
On 3/26/14, 10:13 AM, Sebastien Goasguen wrote:
On Mar 26, 2014, at 12:55 PM, ilya musayev wrote:
Hi Rohit,
What is your thought on tracking exit code of CloudMonkey, as it stands - even if
CloudMonkey prints "Error:" message, no e
I prefer having exit codes. Is always nicer to use that than to grep for error
messages.
--Alex
> -Original Message-
> From: ilya musayev [mailto:ilya.mailing.li...@gmail.com]
> Sent: Wednesday, March 26, 2014 9:56 AM
> To: Rohit Yadav; dev@cloudstack.apache.org
> Subject: CloudMonkey -
On Mar 26, 2014, at 12:55 PM, ilya musayev wrote:
> Hi Rohit,
>
> What is your thought on tracking exit code of CloudMonkey, as it stands -
> even if CloudMonkey prints "Error:" message, no exit code is passed back to a
> shell.
> I know this may conflict if someone is using interactive shell
CloudMonkey should obey the standard rules for exit statuses. It would help
especially with error detection from async jobs. If an error result is
returned, non-zero exit status. Better than analyzing the JSON contents
programmatically anyway.
On Wed, Mar 26, 2014 at 4:55 PM, ilya musayev
wrote:
