You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Rohit Yadav <ro...@citrix.com> on 2012/12/21 02:00:09 UTC
Tabularize the cloudmonkey response
If you want to have the tabularized output, upgrade using: pip install --upgrade cloudmonkey
Updated wiki, see tabular output usage on wiki:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+cloudmonkey+CLI
Regards.
On 20-Dec-2012, at 4:37 PM, "Rohit Yadav (JIRA)" <ji...@apache.org> wrote:
>
> [ https://issues.apache.org/jira/browse/CLOUDSTACK-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Rohit Yadav resolved CLOUDSTACK-545.
> ------------------------------------
>
> Resolution: Fixed
> Assignee: Rohit Yadav
>
> Fixed on master:
>
> CLOUDSTACK-545: Tabularize cloudmonkey's response using filter=<fields,> argument
>
> authorRohit Yadav <bh...@apache.org>
> Fri, 21 Dec 2012 00:28:32 +0000 (16:28 -0800)
> committerRohit Yadav <bh...@apache.org>
> Fri, 21 Dec 2012 00:33:08 +0000 (16:33 -0800)
> commit8f51c630bdb874f9522ec3873c881b1c4e7cfdf7
>
>> Tabularize the cloudmonkey response
>> -----------------------------------
>>
>> Key: CLOUDSTACK-545
>> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-545
>> Project: CloudStack
>> Issue Type: Bug
>> Security Level: Public(Anyone can view this level - this is the default.)
>> Components: Cloudmonkey, Test Tools
>> Reporter: Prasanna Santhanam
>> Assignee: Rohit Yadav
>> Attachments: 0001-cli-cloudmonkey-tabular-output-and-result-view-filte.patch
>>
>>
>> cloudmonkey responses would be more sensible and easier on the eye if they can look tabular similar to the ec2 tools. enhance cloudmonkey to support tabular formatting instead of sequential lists of the response
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Tabularize the cloudmonkey response
Posted by Rohit Yadav <ro...@citrix.com>.
On 06-Jan-2013, at 3:37 PM, David Nalley <da...@gnsa.us> wrote:
>
> So lots of places do 'unofficial' releases, but what is odd here is:
>
> 1. We (the ACS community) have no plans around releasing Cloudmonkey.
> (unless the plan is to make it a part of the CloudStack release.)
Yes, it was planned to have a CLI for CloudStack: https://issues.apache.org/jira/browse/CLOUDSTACK-132
And, yes I want to make it a part of the CloudStack release.
> 2. It has a version number - despite never being released, a version
> number exists. Typically when an individual releases development
> snapshots (as opposed to a community doing a release) it ends up being
> the version number of the last release (or 0 if there has never been a
> release - plus the release tag being incremented to annotate that it's
> either a snapshot or a pre-release package.
So, the version number refers to the fact against which CloudStack version/snapshot it was developed and yes it was released as a community release (i.e. the author or one of the members of the community released it, right now the admins for the pypi account are Chip and I).
What we want is an official release. I was not clear how to proceed, so I've a proposal in a new thread coming up.
> 3. What happens if the ACS community decides that it wants to release
> CloudMonkey version 1.0.0 at some point in the future? IMO defining a
> version number is equivalent to performing a release.
I'll propose on how we should do releases for CloudStack on ML right away.
> 4. How (in your current scheme) would you delineate between snapshot
> packaging (what you've done heretofore) and a real release?
Yes, this thing is not being followed now. But right now the pypi distribution page mentions that it's unofficial now and starting 4.1 we'll do releases after voting on it.
> 5. Follow-on question to that. How do you file bugs against it? The
> primary way folks get access to cloudmonkey is to install it from pypi
> I'd suppose. There is no revision information in the releases - there
> are 4 different releases (with the difference being the release tag,
> but presumably those are different pieces of code. How does one even
> know where in time their version is?
The version/name syntax is cloudmonkey-<CloudStack version>-<cloudmonkey revisions on that major version>.
> I am also interested in why you, the primary
> author of CloudMonkey, who sees the need to release more frequently
> hasn't proposed making a separate CloudMonkey release.
Why not separate cloudmonkey:
1. https://issues.apache.org/jira/browse/CLOUDSTACK-132
2. Dependency on apidoc and marvin target, build dependency with API discovery plugin (coming up soon) there won't be any build dependency so if that works out we can separate out the src as a separate repo.
> I don't think
> there is anything inherently that prohibits you from doing so, aside
> from having to handle release management. Yes, a separate repo might
> be cleaner, but I don't know that it means you can't generate a
> release.
Proposal coming up, looking fwd to your views on it!
Regards.
>
> Regarding #2 above, take a look at a number of examples of pre-release
> and snapshot packaging here:
> [1] http://fedoraproject.org/wiki/Packaging:NamingGuidelines#Snapshot_packages
> [2] http://fedoraproject.org/wiki/Packaging:NamingGuidelines#Pre-Release_packages
Re: Tabularize the cloudmonkey response
Posted by Rohit Yadav <ro...@citrix.com>.
On 06-Jan-2013, at 4:11 PM, Chris Sears <ch...@sungard.com> wrote:
> Is the plan is to eventually make CloudMonkey the official CLI for
> CloudStack (along the lines of the AWS API Tools)?
Yes we wanted a command line tool: https://issues.apache.org/jira/browse/CLOUDSTACK-132
This is the reason why I did not create a separate repo for it and also because it's dependent on the maven build target (apidocs/marvin which helps it generate a pre cache of all the apis, their params and docstrings).
> If so, then it would
> make sense to (eventually) use an Apache repo and synchronize the releases.
There is no such thing as an Apache repo, cheese shop or pypi.python.org is a standard place to distribute python programs, libs etc. and uses pip as its pkg manager, which is why it was published on pypi.
> If not, I don't see any reason to elevate CloudMonkey above any other third
> party tool that happens to use the CloudStack API.
No it's not, it's just another client for CloudStack, one can work on their own clients.
Regards.
>
>
> On Sun, Jan 6, 2013 at 6:37 PM, David Nalley <da...@gnsa.us> wrote:
>
>> On Sun, Jan 6, 2013 at 4:39 PM, Rohit Yadav <ro...@citrix.com>
>> wrote:
>>>
>>> On 06-Jan-2013, at 1:31 PM, Sebastien Goasguen <ru...@gmail.com> wrote:
>>>>
>>>> Can't we just consider cloudmonkey source as "stable" release within a
>> cloudstack release. and just consider the pypi as "unstable" dev..
>>>>
>>>> after all anyone can grab cloudmonkey latest from master and push it to
>> pypi ...
>>>>
>>>> IMHO it's just an issue of understanding that pypi release is not an
>> official ACS release artifact.
>>>
>>> I think for now let's keep it that way, or we can have frequent release
>> cycles of cloudmonkey that are being voted by community and released on
>> pypi?
>>>
>>
>> So lots of places do 'unofficial' releases, but what is odd here is:
>>
>> 1. We (the ACS community) have no plans around releasing Cloudmonkey.
>> (unless the plan is to make it a part of the CloudStack release.)
>> Anecdotally I hear that Apache communities in the past who have had
>> 3rd parties release 'development' snapshots and never release the
>> software themselves have had the board take issue with that behavior.
>> 2. It has a version number - despite never being released, a version
>> number exists. Typically when an individual releases development
>> snapshots (as opposed to a community doing a release) it ends up being
>> the version number of the last release (or 0 if there has never been a
>> release - plus the release tag being incremented to annotate that it's
>> either a snapshot or a pre-release package.
>> 3. What happens if the ACS community decides that it wants to release
>> CloudMonkey version 1.0.0 at some point in the future? IMO defining a
>> version number is equivalent to performing a release.
>> 4. How (in your current scheme) would you delineate between snapshot
>> packaging (what you've done heretofore) and a real release?
>> 5. Follow-on question to that. How do you file bugs against it? The
>> primary way folks get access to cloudmonkey is to install it from pypi
>> I'd suppose. There is no revision information in the releases - there
>> are 4 different releases (with the difference being the release tag,
>> but presumably those are different pieces of code. How does one even
>> know where in time their version is?
>>
>> In short I see a huge number of potential problems that may manifest
>> as we move forward. I am also interested in why you, the primary
>> author of CloudMonkey, who sees the need to release more frequently
>> hasn't proposed making a separate CloudMonkey release. I don't think
>> there is anything inherently that prohibits you from doing so, aside
>> from having to handle release management. Yes, a separate repo might
>> be cleaner, but I don't know that it means you can't generate a
>> release.
>>
>> Regarding #2 above, take a look at a number of examples of pre-release
>> and snapshot packaging here:
>> [1]
>> http://fedoraproject.org/wiki/Packaging:NamingGuidelines#Snapshot_packages
>> [2]
>> http://fedoraproject.org/wiki/Packaging:NamingGuidelines#Pre-Release_packages
>>
>>
Re: Tabularize the cloudmonkey response
Posted by Chris Sears <ch...@sungard.com>.
Is the plan is to eventually make CloudMonkey the official CLI for
CloudStack (along the lines of the AWS API Tools)? If so, then it would
make sense to (eventually) use an Apache repo and synchronize the releases.
If not, I don't see any reason to elevate CloudMonkey above any other third
party tool that happens to use the CloudStack API.
On Sun, Jan 6, 2013 at 6:37 PM, David Nalley <da...@gnsa.us> wrote:
> On Sun, Jan 6, 2013 at 4:39 PM, Rohit Yadav <ro...@citrix.com>
> wrote:
> >
> > On 06-Jan-2013, at 1:31 PM, Sebastien Goasguen <ru...@gmail.com> wrote:
> >>
> >> Can't we just consider cloudmonkey source as "stable" release within a
> cloudstack release. and just consider the pypi as "unstable" dev..
> >>
> >> after all anyone can grab cloudmonkey latest from master and push it to
> pypi ...
> >>
> >> IMHO it's just an issue of understanding that pypi release is not an
> official ACS release artifact.
> >
> > I think for now let's keep it that way, or we can have frequent release
> cycles of cloudmonkey that are being voted by community and released on
> pypi?
> >
>
> So lots of places do 'unofficial' releases, but what is odd here is:
>
> 1. We (the ACS community) have no plans around releasing Cloudmonkey.
> (unless the plan is to make it a part of the CloudStack release.)
> Anecdotally I hear that Apache communities in the past who have had
> 3rd parties release 'development' snapshots and never release the
> software themselves have had the board take issue with that behavior.
> 2. It has a version number - despite never being released, a version
> number exists. Typically when an individual releases development
> snapshots (as opposed to a community doing a release) it ends up being
> the version number of the last release (or 0 if there has never been a
> release - plus the release tag being incremented to annotate that it's
> either a snapshot or a pre-release package.
> 3. What happens if the ACS community decides that it wants to release
> CloudMonkey version 1.0.0 at some point in the future? IMO defining a
> version number is equivalent to performing a release.
> 4. How (in your current scheme) would you delineate between snapshot
> packaging (what you've done heretofore) and a real release?
> 5. Follow-on question to that. How do you file bugs against it? The
> primary way folks get access to cloudmonkey is to install it from pypi
> I'd suppose. There is no revision information in the releases - there
> are 4 different releases (with the difference being the release tag,
> but presumably those are different pieces of code. How does one even
> know where in time their version is?
>
> In short I see a huge number of potential problems that may manifest
> as we move forward. I am also interested in why you, the primary
> author of CloudMonkey, who sees the need to release more frequently
> hasn't proposed making a separate CloudMonkey release. I don't think
> there is anything inherently that prohibits you from doing so, aside
> from having to handle release management. Yes, a separate repo might
> be cleaner, but I don't know that it means you can't generate a
> release.
>
> Regarding #2 above, take a look at a number of examples of pre-release
> and snapshot packaging here:
> [1]
> http://fedoraproject.org/wiki/Packaging:NamingGuidelines#Snapshot_packages
> [2]
> http://fedoraproject.org/wiki/Packaging:NamingGuidelines#Pre-Release_packages
>
>
Re: Tabularize the cloudmonkey response
Posted by David Nalley <da...@gnsa.us>.
On Sun, Jan 6, 2013 at 4:39 PM, Rohit Yadav <ro...@citrix.com> wrote:
>
> On 06-Jan-2013, at 1:31 PM, Sebastien Goasguen <ru...@gmail.com> wrote:
>>
>> Can't we just consider cloudmonkey source as "stable" release within a cloudstack release. and just consider the pypi as "unstable" dev..
>>
>> after all anyone can grab cloudmonkey latest from master and push it to pypi ...
>>
>> IMHO it's just an issue of understanding that pypi release is not an official ACS release artifact.
>
> I think for now let's keep it that way, or we can have frequent release cycles of cloudmonkey that are being voted by community and released on pypi?
>
So lots of places do 'unofficial' releases, but what is odd here is:
1. We (the ACS community) have no plans around releasing Cloudmonkey.
(unless the plan is to make it a part of the CloudStack release.)
Anecdotally I hear that Apache communities in the past who have had
3rd parties release 'development' snapshots and never release the
software themselves have had the board take issue with that behavior.
2. It has a version number - despite never being released, a version
number exists. Typically when an individual releases development
snapshots (as opposed to a community doing a release) it ends up being
the version number of the last release (or 0 if there has never been a
release - plus the release tag being incremented to annotate that it's
either a snapshot or a pre-release package.
3. What happens if the ACS community decides that it wants to release
CloudMonkey version 1.0.0 at some point in the future? IMO defining a
version number is equivalent to performing a release.
4. How (in your current scheme) would you delineate between snapshot
packaging (what you've done heretofore) and a real release?
5. Follow-on question to that. How do you file bugs against it? The
primary way folks get access to cloudmonkey is to install it from pypi
I'd suppose. There is no revision information in the releases - there
are 4 different releases (with the difference being the release tag,
but presumably those are different pieces of code. How does one even
know where in time their version is?
In short I see a huge number of potential problems that may manifest
as we move forward. I am also interested in why you, the primary
author of CloudMonkey, who sees the need to release more frequently
hasn't proposed making a separate CloudMonkey release. I don't think
there is anything inherently that prohibits you from doing so, aside
from having to handle release management. Yes, a separate repo might
be cleaner, but I don't know that it means you can't generate a
release.
Regarding #2 above, take a look at a number of examples of pre-release
and snapshot packaging here:
[1] http://fedoraproject.org/wiki/Packaging:NamingGuidelines#Snapshot_packages
[2] http://fedoraproject.org/wiki/Packaging:NamingGuidelines#Pre-Release_packages
Re: Tabularize the cloudmonkey response
Posted by Rohit Yadav <ro...@citrix.com>.
On 06-Jan-2013, at 1:31 PM, Sebastien Goasguen <ru...@gmail.com> wrote:
>
> Can't we just consider cloudmonkey source as "stable" release within a cloudstack release. and just consider the pypi as "unstable" dev..
>
> after all anyone can grab cloudmonkey latest from master and push it to pypi ...
>
> IMHO it's just an issue of understanding that pypi release is not an official ACS release artifact.
I think for now let's keep it that way, or we can have frequent release cycles of cloudmonkey that are being voted by community and released on pypi?
>
> By the way, there is the same issue with Marvin, but marvin is less under development. I suspect that when cloud monkey will reach steady-state the push to pypi would be less frequent and could be in sync with ACS releases (as those will become more frequent :) ).
If that happens, sure we can do that.
>
>>
>> thoughts?
>>
>>> Regards.
>>>
>>>
>>> ________________________________________
>>> From: Chip Childers [chip.childers@sungard.com]
>>> Sent: Friday, January 04, 2013 8:04 PM
>>> To: cloudstack-dev@incubator.apache.org
>>> Subject: Re: Tabularize the cloudmonkey response
>>>
>>> On Thu, Jan 3, 2013 at 5:23 PM, Rohit Yadav <ro...@citrix.com> wrote:
>>>> Sure, the pypi community release 4.0.0-2 (http://pypi.python.org/packages/source/c/cloudmonkey/cloudmonkey-4.0.0-2.tar.gz#md5=6125f804bc1dec4447df1e1b48a7d85b) has the latest changes with tabular output etc. I can upload the latest tar ball that would make it 4.0.0-3?
>>>>
>>>> Or, for project releases, should we do a 4.0.1 release for cloudmonkey when CloudStack releases after voting etc. or should we go ahead with the community releases (4.0.0-x, cloudmonkey versions are like this: major cloudstack version hyphen last cloudmonkey revision+1) before the actual release?
>>>>
>>>
>>> I thought we agreed that cloudmonkey updates to pypi would be part of
>>> the overall cloudstack release process. Specifically, it's only
>>> updated when we release a new source release. This would align with
>>> the DEB and RPM package release process, and we may end up doing
>>> something similar with maven artifacts as well.
>>>
>>>> Regards.
>>>>
>>>> On 03-Jan-2013, at 12:38 PM, Chip Childers <ch...@sungard.com> wrote:
>>>>
>>>>> Hey Rohit,
>>>>>
>>>>> I think that we should probably be syncing any updates to cloudmonkey
>>>>> on pypi with project releases. What do you think?
>>>>>
>>>>> On Thu, Dec 20, 2012 at 8:00 PM, Rohit Yadav <ro...@citrix.com> wrote:
>>>>>> If you want to have the tabularized output, upgrade using: pip install --upgrade cloudmonkey
>>>>>> Updated wiki, see tabular output usage on wiki:
>>>>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+cloudmonkey+CLI
>>>>>>
>>>>>> Regards.
>>>>>>
>>>>>> On 20-Dec-2012, at 4:37 PM, "Rohit Yadav (JIRA)" <ji...@apache.org> wrote:
>>>>>>
>>>>>>>
>>>>>>> [ https://issues.apache.org/jira/browse/CLOUDSTACK-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>>>>>>
>>>>>>> Rohit Yadav resolved CLOUDSTACK-545.
>>>>>>> ------------------------------------
>>>>>>>
>>>>>>> Resolution: Fixed
>>>>>>> Assignee: Rohit Yadav
>>>>>>>
>>>>>>> Fixed on master:
>>>>>>>
>>>>>>> CLOUDSTACK-545: Tabularize cloudmonkey's response using filter=<fields,> argument
>>>>>>>
>>>>>>> authorRohit Yadav <bh...@apache.org>
>>>>>>> Fri, 21 Dec 2012 00:28:32 +0000 (16:28 -0800)
>>>>>>> committerRohit Yadav <bh...@apache.org>
>>>>>>> Fri, 21 Dec 2012 00:33:08 +0000 (16:33 -0800)
>>>>>>> commit8f51c630bdb874f9522ec3873c881b1c4e7cfdf7
>>>>>>>
>>>>>>>> Tabularize the cloudmonkey response
>>>>>>>> -----------------------------------
>>>>>>>>
>>>>>>>> Key: CLOUDSTACK-545
>>>>>>>> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-545
>>>>>>>> Project: CloudStack
>>>>>>>> Issue Type: Bug
>>>>>>>> Security Level: Public(Anyone can view this level - this is the default.)
>>>>>>>> Components: Cloudmonkey, Test Tools
>>>>>>>> Reporter: Prasanna Santhanam
>>>>>>>> Assignee: Rohit Yadav
>>>>>>>> Attachments: 0001-cli-cloudmonkey-tabular-output-and-result-view-filte.patch
>>>>>>>>
>>>>>>>>
>>>>>>>> cloudmonkey responses would be more sensible and easier on the eye if they can look tabular similar to the ec2 tools. enhance cloudmonkey to support tabular formatting instead of sequential lists of the response
>>>>>>>
>>>>>>> --
>>>>>>> This message is automatically generated by JIRA.
>>>>>>> If you think it was sent incorrectly, please contact your JIRA administrators
>>>>>>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>>>>>
>>>>>>
>>>>
>>>>
>>>
>
Re: Tabularize the cloudmonkey response
Posted by Sebastien Goasguen <ru...@gmail.com>.
On Jan 4, 2013, at 9:45 PM, Chip Childers <ch...@sungard.com> wrote:
> On Fri, Jan 4, 2013 at 12:18 PM, Rohit Yadav <ro...@citrix.com> wrote:
>> Yes we agreed to do cloudmonkey updates on pypi alongwith CloudStack releases, I don't understand what you mean by syncing any updates to pypi?
>>
>> Right now the releases I've done via pypi are not part of any acs release and I upload a new src tarball on pypi everytime there are significant changes (if you see, it would be once every 3-4 weeks). Also, these releases are not voted and I do them out of my interest and free time for community, hence mentioned as community releases.
>>
>> Pl. read my previous email following your question (syncing updates), what I asked was:
>>
>> a. We want to continue doing community releases on pypi to sync updates so the users get latest and greatest changes.
>> b. We want to stop community releases and make pypi account/releases maintained by PMC/committers so it's used to do official/voted/signed releases of cloudmonkey alongwith ACS releases.
>>
>
> IMO (and I'm really looking for others to chime in and express
> opinions here too), we should really only update pypi following an
> official CloudStack release process. To me, it's similar to the RPM /
> DEB repos that Wido maintains. Those are distribution points for the
> project, although technically not Apache CloudStack release artifacts,
> that are updated when we do a source code release.
>
> Then again, you (and me, because you're nice) are the one that
> controls that pypi project. If you completely disagree, then that's
> fine. I'm not trying to box you in or anything. I just wanted to see
> if it would make sense to help keep the users clear about where and
> what is going on with things. Make sense?
>
> Another idea: we have been discussing on other threads the idea of
> adding other git repos within Apache infra. Perhaps we should break
> Marvin and CloudMonkey out as separate repos, and allow them to follow
> a different schedule for source code releases.
Can't we just consider cloudmonkey source as "stable" release within a cloudstack release. and just consider the pypi as "unstable" dev..
after all anyone can grab cloudmonkey latest from master and push it to pypi ...
IMHO it's just an issue of understanding that pypi release is not an official ACS release artifact.
By the way, there is the same issue with Marvin, but marvin is less under development. I suspect that when cloud monkey will reach steady-state the push to pypi would be less frequent and could be in sync with ACS releases (as those will become more frequent :) ).
>
> thoughts?
>
>> Regards.
>>
>>
>> ________________________________________
>> From: Chip Childers [chip.childers@sungard.com]
>> Sent: Friday, January 04, 2013 8:04 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: Tabularize the cloudmonkey response
>>
>> On Thu, Jan 3, 2013 at 5:23 PM, Rohit Yadav <ro...@citrix.com> wrote:
>>> Sure, the pypi community release 4.0.0-2 (http://pypi.python.org/packages/source/c/cloudmonkey/cloudmonkey-4.0.0-2.tar.gz#md5=6125f804bc1dec4447df1e1b48a7d85b) has the latest changes with tabular output etc. I can upload the latest tar ball that would make it 4.0.0-3?
>>>
>>> Or, for project releases, should we do a 4.0.1 release for cloudmonkey when CloudStack releases after voting etc. or should we go ahead with the community releases (4.0.0-x, cloudmonkey versions are like this: major cloudstack version hyphen last cloudmonkey revision+1) before the actual release?
>>>
>>
>> I thought we agreed that cloudmonkey updates to pypi would be part of
>> the overall cloudstack release process. Specifically, it's only
>> updated when we release a new source release. This would align with
>> the DEB and RPM package release process, and we may end up doing
>> something similar with maven artifacts as well.
>>
>>> Regards.
>>>
>>> On 03-Jan-2013, at 12:38 PM, Chip Childers <ch...@sungard.com> wrote:
>>>
>>>> Hey Rohit,
>>>>
>>>> I think that we should probably be syncing any updates to cloudmonkey
>>>> on pypi with project releases. What do you think?
>>>>
>>>> On Thu, Dec 20, 2012 at 8:00 PM, Rohit Yadav <ro...@citrix.com> wrote:
>>>>> If you want to have the tabularized output, upgrade using: pip install --upgrade cloudmonkey
>>>>> Updated wiki, see tabular output usage on wiki:
>>>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+cloudmonkey+CLI
>>>>>
>>>>> Regards.
>>>>>
>>>>> On 20-Dec-2012, at 4:37 PM, "Rohit Yadav (JIRA)" <ji...@apache.org> wrote:
>>>>>
>>>>>>
>>>>>> [ https://issues.apache.org/jira/browse/CLOUDSTACK-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>>>>>
>>>>>> Rohit Yadav resolved CLOUDSTACK-545.
>>>>>> ------------------------------------
>>>>>>
>>>>>> Resolution: Fixed
>>>>>> Assignee: Rohit Yadav
>>>>>>
>>>>>> Fixed on master:
>>>>>>
>>>>>> CLOUDSTACK-545: Tabularize cloudmonkey's response using filter=<fields,> argument
>>>>>>
>>>>>> authorRohit Yadav <bh...@apache.org>
>>>>>> Fri, 21 Dec 2012 00:28:32 +0000 (16:28 -0800)
>>>>>> committerRohit Yadav <bh...@apache.org>
>>>>>> Fri, 21 Dec 2012 00:33:08 +0000 (16:33 -0800)
>>>>>> commit8f51c630bdb874f9522ec3873c881b1c4e7cfdf7
>>>>>>
>>>>>>> Tabularize the cloudmonkey response
>>>>>>> -----------------------------------
>>>>>>>
>>>>>>> Key: CLOUDSTACK-545
>>>>>>> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-545
>>>>>>> Project: CloudStack
>>>>>>> Issue Type: Bug
>>>>>>> Security Level: Public(Anyone can view this level - this is the default.)
>>>>>>> Components: Cloudmonkey, Test Tools
>>>>>>> Reporter: Prasanna Santhanam
>>>>>>> Assignee: Rohit Yadav
>>>>>>> Attachments: 0001-cli-cloudmonkey-tabular-output-and-result-view-filte.patch
>>>>>>>
>>>>>>>
>>>>>>> cloudmonkey responses would be more sensible and easier on the eye if they can look tabular similar to the ec2 tools. enhance cloudmonkey to support tabular formatting instead of sequential lists of the response
>>>>>>
>>>>>> --
>>>>>> This message is automatically generated by JIRA.
>>>>>> If you think it was sent incorrectly, please contact your JIRA administrators
>>>>>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>>>>
>>>>>
>>>
>>>
>>
Re: Tabularize the cloudmonkey response
Posted by Rohit Yadav <ro...@citrix.com>.
On 04-Jan-2013, at 12:45 PM, Chip Childers <ch...@sungard.com> wrote:
> On Fri, Jan 4, 2013 at 12:18 PM, Rohit Yadav <ro...@citrix.com> wrote:
>> Yes we agreed to do cloudmonkey updates on pypi alongwith CloudStack releases, I don't understand what you mean by syncing any updates to pypi?
>>
>> Right now the releases I've done via pypi are not part of any acs release and I upload a new src tarball on pypi everytime there are significant changes (if you see, it would be once every 3-4 weeks). Also, these releases are not voted and I do them out of my interest and free time for community, hence mentioned as community releases.
>>
>> Pl. read my previous email following your question (syncing updates), what I asked was:
>>
>> a. We want to continue doing community releases on pypi to sync updates so the users get latest and greatest changes.
>> b. We want to stop community releases and make pypi account/releases maintained by PMC/committers so it's used to do official/voted/signed releases of cloudmonkey alongwith ACS releases.
>>
>
> IMO (and I'm really looking for others to chime in and express
> opinions here too), we should really only update pypi following an
> official CloudStack release process. To me, it's similar to the RPM /
> DEB repos that Wido maintains. Those are distribution points for the
> project, although technically not Apache CloudStack release artifacts,
> that are updated when we do a source code release.
The only problem I see when doing cloudmonkey releases with CloudStack releases is that CloudStack release cycles will be long, pypi releases may miss some of the useful changes which may be frequent enough.
>
> Then again, you (and me, because you're nice) are the one that
> controls that pypi project. If you completely disagree, then that's
> fine. I'm not trying to box you in or anything. I just wanted to see
> if it would make sense to help keep the users clear about where and
> what is going on with things. Make sense?
Meh, I don't care about the pypi, it's just a place to distribute python packages.
Any contributor, committer or PMC member who is interested, is welcome to join the pypi project as owner or admin to maintain and release cloudmonkey via cheese shop. (unless anyone goes wild, it's all good :)
>
> Another idea: we have been discussing on other threads the idea of
> adding other git repos within Apache infra. Perhaps we should break
> Marvin and CloudMonkey out as separate repos, and allow them to follow
> a different schedule for source code releases.
I've been thinking of the same as well. With git we can have sub repos, or modules. So, you place a git repo inside others. So, we can breakout parts of source (while retaining their history/changes) to separate git repos, good candidates are docs (exclude apidocs), cloudmonkey, devcloud, systemvm builder script/code, aws-api etc. This way they can be developed separately either on asf infra or some place on github etc.
I'm inclined towards *not breaking the repo* in separate repos, but yes at least the indirect (usage or dependency wise) pieces and *new pieces* which don't really require CloudStack can broken out, cloudmonkey for sure qualifies.
This way CloudStack codebase can still have pointers [1] to other git repos. So, one can do git submodule init/update etc.
Rightnow to build marvin and cloudmonkey they are required within the src as they read commands.xml to generate cloudstackAPI python boilerplate api classes and pre cache api info for cloudmonkey.
In future after work in api_refactoring is merged, I'm planning to implement a plugin which gives an api to load available api info for a user (apiname, endpoints, descp, help docs, param info etc.) from the mgmt server on the fly (hence no preaching required). If this works, changes in apis won't affect cloudmonkey or any client which implements in a generic way (functional programming ftw!) and clients (cloudmonkey, marvin) can be extracted out of CloudStack and be developed as separate projects.
[1] http://git-scm.com/book/en/Git-Tools-Submodules
>
> thoughts?
>
>> Regards.
>>
>>
>> ________________________________________
>> From: Chip Childers [chip.childers@sungard.com]
>> Sent: Friday, January 04, 2013 8:04 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: Tabularize the cloudmonkey response
>>
>> On Thu, Jan 3, 2013 at 5:23 PM, Rohit Yadav <ro...@citrix.com> wrote:
>>> Sure, the pypi community release 4.0.0-2 (http://pypi.python.org/packages/source/c/cloudmonkey/cloudmonkey-4.0.0-2.tar.gz#md5=6125f804bc1dec4447df1e1b48a7d85b) has the latest changes with tabular output etc. I can upload the latest tar ball that would make it 4.0.0-3?
>>>
>>> Or, for project releases, should we do a 4.0.1 release for cloudmonkey when CloudStack releases after voting etc. or should we go ahead with the community releases (4.0.0-x, cloudmonkey versions are like this: major cloudstack version hyphen last cloudmonkey revision+1) before the actual release?
>>>
>>
>> I thought we agreed that cloudmonkey updates to pypi would be part of
>> the overall cloudstack release process. Specifically, it's only
>> updated when we release a new source release. This would align with
>> the DEB and RPM package release process, and we may end up doing
>> something similar with maven artifacts as well.
>>
>>> Regards.
>>>
>>> On 03-Jan-2013, at 12:38 PM, Chip Childers <ch...@sungard.com> wrote:
>>>
>>>> Hey Rohit,
>>>>
>>>> I think that we should probably be syncing any updates to cloudmonkey
>>>> on pypi with project releases. What do you think?
>>>>
>>>> On Thu, Dec 20, 2012 at 8:00 PM, Rohit Yadav <ro...@citrix.com> wrote:
>>>>> If you want to have the tabularized output, upgrade using: pip install --upgrade cloudmonkey
>>>>> Updated wiki, see tabular output usage on wiki:
>>>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+cloudmonkey+CLI
>>>>>
>>>>> Regards.
>>>>>
>>>>> On 20-Dec-2012, at 4:37 PM, "Rohit Yadav (JIRA)" <ji...@apache.org> wrote:
>>>>>
>>>>>>
>>>>>> [ https://issues.apache.org/jira/browse/CLOUDSTACK-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>>>>>
>>>>>> Rohit Yadav resolved CLOUDSTACK-545.
>>>>>> ------------------------------------
>>>>>>
>>>>>> Resolution: Fixed
>>>>>> Assignee: Rohit Yadav
>>>>>>
>>>>>> Fixed on master:
>>>>>>
>>>>>> CLOUDSTACK-545: Tabularize cloudmonkey's response using filter=<fields,> argument
>>>>>>
>>>>>> authorRohit Yadav <bh...@apache.org>
>>>>>> Fri, 21 Dec 2012 00:28:32 +0000 (16:28 -0800)
>>>>>> committerRohit Yadav <bh...@apache.org>
>>>>>> Fri, 21 Dec 2012 00:33:08 +0000 (16:33 -0800)
>>>>>> commit8f51c630bdb874f9522ec3873c881b1c4e7cfdf7
>>>>>>
>>>>>>> Tabularize the cloudmonkey response
>>>>>>> -----------------------------------
>>>>>>>
>>>>>>> Key: CLOUDSTACK-545
>>>>>>> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-545
>>>>>>> Project: CloudStack
>>>>>>> Issue Type: Bug
>>>>>>> Security Level: Public(Anyone can view this level - this is the default.)
>>>>>>> Components: Cloudmonkey, Test Tools
>>>>>>> Reporter: Prasanna Santhanam
>>>>>>> Assignee: Rohit Yadav
>>>>>>> Attachments: 0001-cli-cloudmonkey-tabular-output-and-result-view-filte.patch
>>>>>>>
>>>>>>>
>>>>>>> cloudmonkey responses would be more sensible and easier on the eye if they can look tabular similar to the ec2 tools. enhance cloudmonkey to support tabular formatting instead of sequential lists of the response
>>>>>>
>>>>>> --
>>>>>> This message is automatically generated by JIRA.
>>>>>> If you think it was sent incorrectly, please contact your JIRA administrators
>>>>>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>>>>
>>>>>
>>>
>>>
>>
Re: Tabularize the cloudmonkey response
Posted by Chip Childers <ch...@sungard.com>.
On Fri, Jan 4, 2013 at 12:18 PM, Rohit Yadav <ro...@citrix.com> wrote:
> Yes we agreed to do cloudmonkey updates on pypi alongwith CloudStack releases, I don't understand what you mean by syncing any updates to pypi?
>
> Right now the releases I've done via pypi are not part of any acs release and I upload a new src tarball on pypi everytime there are significant changes (if you see, it would be once every 3-4 weeks). Also, these releases are not voted and I do them out of my interest and free time for community, hence mentioned as community releases.
>
> Pl. read my previous email following your question (syncing updates), what I asked was:
>
> a. We want to continue doing community releases on pypi to sync updates so the users get latest and greatest changes.
> b. We want to stop community releases and make pypi account/releases maintained by PMC/committers so it's used to do official/voted/signed releases of cloudmonkey alongwith ACS releases.
>
IMO (and I'm really looking for others to chime in and express
opinions here too), we should really only update pypi following an
official CloudStack release process. To me, it's similar to the RPM /
DEB repos that Wido maintains. Those are distribution points for the
project, although technically not Apache CloudStack release artifacts,
that are updated when we do a source code release.
Then again, you (and me, because you're nice) are the one that
controls that pypi project. If you completely disagree, then that's
fine. I'm not trying to box you in or anything. I just wanted to see
if it would make sense to help keep the users clear about where and
what is going on with things. Make sense?
Another idea: we have been discussing on other threads the idea of
adding other git repos within Apache infra. Perhaps we should break
Marvin and CloudMonkey out as separate repos, and allow them to follow
a different schedule for source code releases.
thoughts?
> Regards.
>
>
> ________________________________________
> From: Chip Childers [chip.childers@sungard.com]
> Sent: Friday, January 04, 2013 8:04 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: Tabularize the cloudmonkey response
>
> On Thu, Jan 3, 2013 at 5:23 PM, Rohit Yadav <ro...@citrix.com> wrote:
>> Sure, the pypi community release 4.0.0-2 (http://pypi.python.org/packages/source/c/cloudmonkey/cloudmonkey-4.0.0-2.tar.gz#md5=6125f804bc1dec4447df1e1b48a7d85b) has the latest changes with tabular output etc. I can upload the latest tar ball that would make it 4.0.0-3?
>>
>> Or, for project releases, should we do a 4.0.1 release for cloudmonkey when CloudStack releases after voting etc. or should we go ahead with the community releases (4.0.0-x, cloudmonkey versions are like this: major cloudstack version hyphen last cloudmonkey revision+1) before the actual release?
>>
>
> I thought we agreed that cloudmonkey updates to pypi would be part of
> the overall cloudstack release process. Specifically, it's only
> updated when we release a new source release. This would align with
> the DEB and RPM package release process, and we may end up doing
> something similar with maven artifacts as well.
>
>> Regards.
>>
>> On 03-Jan-2013, at 12:38 PM, Chip Childers <ch...@sungard.com> wrote:
>>
>>> Hey Rohit,
>>>
>>> I think that we should probably be syncing any updates to cloudmonkey
>>> on pypi with project releases. What do you think?
>>>
>>> On Thu, Dec 20, 2012 at 8:00 PM, Rohit Yadav <ro...@citrix.com> wrote:
>>>> If you want to have the tabularized output, upgrade using: pip install --upgrade cloudmonkey
>>>> Updated wiki, see tabular output usage on wiki:
>>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+cloudmonkey+CLI
>>>>
>>>> Regards.
>>>>
>>>> On 20-Dec-2012, at 4:37 PM, "Rohit Yadav (JIRA)" <ji...@apache.org> wrote:
>>>>
>>>>>
>>>>> [ https://issues.apache.org/jira/browse/CLOUDSTACK-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>>>>
>>>>> Rohit Yadav resolved CLOUDSTACK-545.
>>>>> ------------------------------------
>>>>>
>>>>> Resolution: Fixed
>>>>> Assignee: Rohit Yadav
>>>>>
>>>>> Fixed on master:
>>>>>
>>>>> CLOUDSTACK-545: Tabularize cloudmonkey's response using filter=<fields,> argument
>>>>>
>>>>> authorRohit Yadav <bh...@apache.org>
>>>>> Fri, 21 Dec 2012 00:28:32 +0000 (16:28 -0800)
>>>>> committerRohit Yadav <bh...@apache.org>
>>>>> Fri, 21 Dec 2012 00:33:08 +0000 (16:33 -0800)
>>>>> commit8f51c630bdb874f9522ec3873c881b1c4e7cfdf7
>>>>>
>>>>>> Tabularize the cloudmonkey response
>>>>>> -----------------------------------
>>>>>>
>>>>>> Key: CLOUDSTACK-545
>>>>>> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-545
>>>>>> Project: CloudStack
>>>>>> Issue Type: Bug
>>>>>> Security Level: Public(Anyone can view this level - this is the default.)
>>>>>> Components: Cloudmonkey, Test Tools
>>>>>> Reporter: Prasanna Santhanam
>>>>>> Assignee: Rohit Yadav
>>>>>> Attachments: 0001-cli-cloudmonkey-tabular-output-and-result-view-filte.patch
>>>>>>
>>>>>>
>>>>>> cloudmonkey responses would be more sensible and easier on the eye if they can look tabular similar to the ec2 tools. enhance cloudmonkey to support tabular formatting instead of sequential lists of the response
>>>>>
>>>>> --
>>>>> This message is automatically generated by JIRA.
>>>>> If you think it was sent incorrectly, please contact your JIRA administrators
>>>>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>>>
>>>>
>>
>>
>
RE: Tabularize the cloudmonkey response
Posted by Rohit Yadav <ro...@citrix.com>.
Yes we agreed to do cloudmonkey updates on pypi alongwith CloudStack releases, I don't understand what you mean by syncing any updates to pypi?
Right now the releases I've done via pypi are not part of any acs release and I upload a new src tarball on pypi everytime there are significant changes (if you see, it would be once every 3-4 weeks). Also, these releases are not voted and I do them out of my interest and free time for community, hence mentioned as community releases.
Pl. read my previous email following your question (syncing updates), what I asked was:
a. We want to continue doing community releases on pypi to sync updates so the users get latest and greatest changes.
b. We want to stop community releases and make pypi account/releases maintained by PMC/committers so it's used to do official/voted/signed releases of cloudmonkey alongwith ACS releases.
Regards.
________________________________________
From: Chip Childers [chip.childers@sungard.com]
Sent: Friday, January 04, 2013 8:04 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: Tabularize the cloudmonkey response
On Thu, Jan 3, 2013 at 5:23 PM, Rohit Yadav <ro...@citrix.com> wrote:
> Sure, the pypi community release 4.0.0-2 (http://pypi.python.org/packages/source/c/cloudmonkey/cloudmonkey-4.0.0-2.tar.gz#md5=6125f804bc1dec4447df1e1b48a7d85b) has the latest changes with tabular output etc. I can upload the latest tar ball that would make it 4.0.0-3?
>
> Or, for project releases, should we do a 4.0.1 release for cloudmonkey when CloudStack releases after voting etc. or should we go ahead with the community releases (4.0.0-x, cloudmonkey versions are like this: major cloudstack version hyphen last cloudmonkey revision+1) before the actual release?
>
I thought we agreed that cloudmonkey updates to pypi would be part of
the overall cloudstack release process. Specifically, it's only
updated when we release a new source release. This would align with
the DEB and RPM package release process, and we may end up doing
something similar with maven artifacts as well.
> Regards.
>
> On 03-Jan-2013, at 12:38 PM, Chip Childers <ch...@sungard.com> wrote:
>
>> Hey Rohit,
>>
>> I think that we should probably be syncing any updates to cloudmonkey
>> on pypi with project releases. What do you think?
>>
>> On Thu, Dec 20, 2012 at 8:00 PM, Rohit Yadav <ro...@citrix.com> wrote:
>>> If you want to have the tabularized output, upgrade using: pip install --upgrade cloudmonkey
>>> Updated wiki, see tabular output usage on wiki:
>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+cloudmonkey+CLI
>>>
>>> Regards.
>>>
>>> On 20-Dec-2012, at 4:37 PM, "Rohit Yadav (JIRA)" <ji...@apache.org> wrote:
>>>
>>>>
>>>> [ https://issues.apache.org/jira/browse/CLOUDSTACK-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>>>
>>>> Rohit Yadav resolved CLOUDSTACK-545.
>>>> ------------------------------------
>>>>
>>>> Resolution: Fixed
>>>> Assignee: Rohit Yadav
>>>>
>>>> Fixed on master:
>>>>
>>>> CLOUDSTACK-545: Tabularize cloudmonkey's response using filter=<fields,> argument
>>>>
>>>> authorRohit Yadav <bh...@apache.org>
>>>> Fri, 21 Dec 2012 00:28:32 +0000 (16:28 -0800)
>>>> committerRohit Yadav <bh...@apache.org>
>>>> Fri, 21 Dec 2012 00:33:08 +0000 (16:33 -0800)
>>>> commit8f51c630bdb874f9522ec3873c881b1c4e7cfdf7
>>>>
>>>>> Tabularize the cloudmonkey response
>>>>> -----------------------------------
>>>>>
>>>>> Key: CLOUDSTACK-545
>>>>> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-545
>>>>> Project: CloudStack
>>>>> Issue Type: Bug
>>>>> Security Level: Public(Anyone can view this level - this is the default.)
>>>>> Components: Cloudmonkey, Test Tools
>>>>> Reporter: Prasanna Santhanam
>>>>> Assignee: Rohit Yadav
>>>>> Attachments: 0001-cli-cloudmonkey-tabular-output-and-result-view-filte.patch
>>>>>
>>>>>
>>>>> cloudmonkey responses would be more sensible and easier on the eye if they can look tabular similar to the ec2 tools. enhance cloudmonkey to support tabular formatting instead of sequential lists of the response
>>>>
>>>> --
>>>> This message is automatically generated by JIRA.
>>>> If you think it was sent incorrectly, please contact your JIRA administrators
>>>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>>
>>>
>
>
Re: Tabularize the cloudmonkey response
Posted by Chip Childers <ch...@sungard.com>.
On Thu, Jan 3, 2013 at 5:23 PM, Rohit Yadav <ro...@citrix.com> wrote:
> Sure, the pypi community release 4.0.0-2 (http://pypi.python.org/packages/source/c/cloudmonkey/cloudmonkey-4.0.0-2.tar.gz#md5=6125f804bc1dec4447df1e1b48a7d85b) has the latest changes with tabular output etc. I can upload the latest tar ball that would make it 4.0.0-3?
>
> Or, for project releases, should we do a 4.0.1 release for cloudmonkey when CloudStack releases after voting etc. or should we go ahead with the community releases (4.0.0-x, cloudmonkey versions are like this: major cloudstack version hyphen last cloudmonkey revision+1) before the actual release?
>
I thought we agreed that cloudmonkey updates to pypi would be part of
the overall cloudstack release process. Specifically, it's only
updated when we release a new source release. This would align with
the DEB and RPM package release process, and we may end up doing
something similar with maven artifacts as well.
> Regards.
>
> On 03-Jan-2013, at 12:38 PM, Chip Childers <ch...@sungard.com> wrote:
>
>> Hey Rohit,
>>
>> I think that we should probably be syncing any updates to cloudmonkey
>> on pypi with project releases. What do you think?
>>
>> On Thu, Dec 20, 2012 at 8:00 PM, Rohit Yadav <ro...@citrix.com> wrote:
>>> If you want to have the tabularized output, upgrade using: pip install --upgrade cloudmonkey
>>> Updated wiki, see tabular output usage on wiki:
>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+cloudmonkey+CLI
>>>
>>> Regards.
>>>
>>> On 20-Dec-2012, at 4:37 PM, "Rohit Yadav (JIRA)" <ji...@apache.org> wrote:
>>>
>>>>
>>>> [ https://issues.apache.org/jira/browse/CLOUDSTACK-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>>>
>>>> Rohit Yadav resolved CLOUDSTACK-545.
>>>> ------------------------------------
>>>>
>>>> Resolution: Fixed
>>>> Assignee: Rohit Yadav
>>>>
>>>> Fixed on master:
>>>>
>>>> CLOUDSTACK-545: Tabularize cloudmonkey's response using filter=<fields,> argument
>>>>
>>>> authorRohit Yadav <bh...@apache.org>
>>>> Fri, 21 Dec 2012 00:28:32 +0000 (16:28 -0800)
>>>> committerRohit Yadav <bh...@apache.org>
>>>> Fri, 21 Dec 2012 00:33:08 +0000 (16:33 -0800)
>>>> commit8f51c630bdb874f9522ec3873c881b1c4e7cfdf7
>>>>
>>>>> Tabularize the cloudmonkey response
>>>>> -----------------------------------
>>>>>
>>>>> Key: CLOUDSTACK-545
>>>>> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-545
>>>>> Project: CloudStack
>>>>> Issue Type: Bug
>>>>> Security Level: Public(Anyone can view this level - this is the default.)
>>>>> Components: Cloudmonkey, Test Tools
>>>>> Reporter: Prasanna Santhanam
>>>>> Assignee: Rohit Yadav
>>>>> Attachments: 0001-cli-cloudmonkey-tabular-output-and-result-view-filte.patch
>>>>>
>>>>>
>>>>> cloudmonkey responses would be more sensible and easier on the eye if they can look tabular similar to the ec2 tools. enhance cloudmonkey to support tabular formatting instead of sequential lists of the response
>>>>
>>>> --
>>>> This message is automatically generated by JIRA.
>>>> If you think it was sent incorrectly, please contact your JIRA administrators
>>>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>>
>>>
>
>
Re: Tabularize the cloudmonkey response
Posted by Rohit Yadav <ro...@citrix.com>.
Sure, the pypi community release 4.0.0-2 (http://pypi.python.org/packages/source/c/cloudmonkey/cloudmonkey-4.0.0-2.tar.gz#md5=6125f804bc1dec4447df1e1b48a7d85b) has the latest changes with tabular output etc. I can upload the latest tar ball that would make it 4.0.0-3?
Or, for project releases, should we do a 4.0.1 release for cloudmonkey when CloudStack releases after voting etc. or should we go ahead with the community releases (4.0.0-x, cloudmonkey versions are like this: major cloudstack version hyphen last cloudmonkey revision+1) before the actual release?
Regards.
On 03-Jan-2013, at 12:38 PM, Chip Childers <ch...@sungard.com> wrote:
> Hey Rohit,
>
> I think that we should probably be syncing any updates to cloudmonkey
> on pypi with project releases. What do you think?
>
> On Thu, Dec 20, 2012 at 8:00 PM, Rohit Yadav <ro...@citrix.com> wrote:
>> If you want to have the tabularized output, upgrade using: pip install --upgrade cloudmonkey
>> Updated wiki, see tabular output usage on wiki:
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+cloudmonkey+CLI
>>
>> Regards.
>>
>> On 20-Dec-2012, at 4:37 PM, "Rohit Yadav (JIRA)" <ji...@apache.org> wrote:
>>
>>>
>>> [ https://issues.apache.org/jira/browse/CLOUDSTACK-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>>
>>> Rohit Yadav resolved CLOUDSTACK-545.
>>> ------------------------------------
>>>
>>> Resolution: Fixed
>>> Assignee: Rohit Yadav
>>>
>>> Fixed on master:
>>>
>>> CLOUDSTACK-545: Tabularize cloudmonkey's response using filter=<fields,> argument
>>>
>>> authorRohit Yadav <bh...@apache.org>
>>> Fri, 21 Dec 2012 00:28:32 +0000 (16:28 -0800)
>>> committerRohit Yadav <bh...@apache.org>
>>> Fri, 21 Dec 2012 00:33:08 +0000 (16:33 -0800)
>>> commit8f51c630bdb874f9522ec3873c881b1c4e7cfdf7
>>>
>>>> Tabularize the cloudmonkey response
>>>> -----------------------------------
>>>>
>>>> Key: CLOUDSTACK-545
>>>> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-545
>>>> Project: CloudStack
>>>> Issue Type: Bug
>>>> Security Level: Public(Anyone can view this level - this is the default.)
>>>> Components: Cloudmonkey, Test Tools
>>>> Reporter: Prasanna Santhanam
>>>> Assignee: Rohit Yadav
>>>> Attachments: 0001-cli-cloudmonkey-tabular-output-and-result-view-filte.patch
>>>>
>>>>
>>>> cloudmonkey responses would be more sensible and easier on the eye if they can look tabular similar to the ec2 tools. enhance cloudmonkey to support tabular formatting instead of sequential lists of the response
>>>
>>> --
>>> This message is automatically generated by JIRA.
>>> If you think it was sent incorrectly, please contact your JIRA administrators
>>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>
>>
Re: Tabularize the cloudmonkey response
Posted by Chip Childers <ch...@sungard.com>.
Hey Rohit,
I think that we should probably be syncing any updates to cloudmonkey
on pypi with project releases. What do you think?
On Thu, Dec 20, 2012 at 8:00 PM, Rohit Yadav <ro...@citrix.com> wrote:
> If you want to have the tabularized output, upgrade using: pip install --upgrade cloudmonkey
> Updated wiki, see tabular output usage on wiki:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+cloudmonkey+CLI
>
> Regards.
>
> On 20-Dec-2012, at 4:37 PM, "Rohit Yadav (JIRA)" <ji...@apache.org> wrote:
>
>>
>> [ https://issues.apache.org/jira/browse/CLOUDSTACK-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>
>> Rohit Yadav resolved CLOUDSTACK-545.
>> ------------------------------------
>>
>> Resolution: Fixed
>> Assignee: Rohit Yadav
>>
>> Fixed on master:
>>
>> CLOUDSTACK-545: Tabularize cloudmonkey's response using filter=<fields,> argument
>>
>> authorRohit Yadav <bh...@apache.org>
>> Fri, 21 Dec 2012 00:28:32 +0000 (16:28 -0800)
>> committerRohit Yadav <bh...@apache.org>
>> Fri, 21 Dec 2012 00:33:08 +0000 (16:33 -0800)
>> commit8f51c630bdb874f9522ec3873c881b1c4e7cfdf7
>>
>>> Tabularize the cloudmonkey response
>>> -----------------------------------
>>>
>>> Key: CLOUDSTACK-545
>>> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-545
>>> Project: CloudStack
>>> Issue Type: Bug
>>> Security Level: Public(Anyone can view this level - this is the default.)
>>> Components: Cloudmonkey, Test Tools
>>> Reporter: Prasanna Santhanam
>>> Assignee: Rohit Yadav
>>> Attachments: 0001-cli-cloudmonkey-tabular-output-and-result-view-filte.patch
>>>
>>>
>>> cloudmonkey responses would be more sensible and easier on the eye if they can look tabular similar to the ec2 tools. enhance cloudmonkey to support tabular formatting instead of sequential lists of the response
>>
>> --
>> This message is automatically generated by JIRA.
>> If you think it was sent incorrectly, please contact your JIRA administrators
>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>