version of cloudmonkey

[Marcus Sorensen <sh...@gmail.com>]

I noticed that the documentation doesn't quite match up with cloudmonkey as
installed via tools/cli, nor does it match the tarball. It seems to be
missing 'set display', among other things, and the asyncblock never
returns, in either version, long after the job is finished.

Re: version of cloudmonkey

[Sebastien Goasguen <ru...@gmail.com>]

On 1 May 2013, at 15:47, Marcus Sorensen <sh...@gmail.com> wrote:

> I noticed that the documentation doesn't quite match up with cloudmonkey as
> installed via tools/cli, nor does it match the tarball. It seems to be
> missing 'set display', among other things, and the asyncblock never
> returns, in either version, long after the job is finished.

Marcus, i noticed the asyncblock issue the other day as well but did not have time to investigate whether it was a bug or not.

Re: version of cloudmonkey

[Chip Childers <ch...@sungard.com>]

Hey Justin,

Just checking in on this...  if you give us your pypi username I'd be
happy to give you the rights to push SNAPs to pypi for cloudmonkey.

On Sat, May 4, 2013 at 3:02 PM, Rohit Yadav <bh...@apache.org> wrote:
> On Thu, May 2, 2013 at 5:04 PM, Justin Grudzien <gr...@gmail.com> wrote:
>
>> When I become reliable I am certainly willing to learn how to do it.
>>
>
> While one can disagree with me, I feel everyone who is part of the
> community should be reliable until proven guilty or whatnot.
>
> Justin, register for an account on pypi and share with me your user id. On
> pypi try to upload a fake package just to understand how pypi works.
>
> As agreed in earlier threads, we will never publish a versioned pkg without
> community vote (there won't be any separate thing, when our release will
> ask to vote on a release, that includes all the components of that release
> i.e. cloudmonkey, awsapi, api, utils etc.). Though we will publish
> snapshots (or latest src dists) with
> cloudmonkey-<cloudstack-target-version>-snapshot<incremental nos.>, so when
> one does:
>
> pip install cloudmonkey => gets latest. (the community version)
> pip install cloudmonkey==4.1 => gets cloudmonkey 4.1 (the release version)
>
> Though the actual/official source dist. will be published on apache's infra
> (pypi is a channel outside of ASF but quite popular and works with
> pip/easy_install).
>
> Cheers.
>
>
>>
>> Justin
>>
>> Sent from my iPhone
>>
>> On May 2, 2013, at 5:50 AM, Rohit Yadav <bh...@apache.org> wrote:
>>
>>
>>
>> On Thu, May 2, 2013 at 4:30 AM, Justin Grudzien <gr...@gmail.com>wrote:
>>
>>> It is currently in master but I will see if I can get Rohit, who I think
>>> owns the process, to create a new version for pip. If that isn't
>>> immediately possible I can revert the documentation until it is done. I
>>> figured documentation is always last :)
>>>
>>
>> Hey, I don't own the process just help publish snapshots. Chip has access
>> to the pypi release channel as well, and any
>> committer/pmc/reliable-contributor can gain the access.
>> Will take a look at it and try to publish latest snapshot from master this
>> weekend (but no promises :)
>>
>> Cheers.
>>
>>
>>>
>>> Justin
>>>
>>> On May 1, 2013, at 4:06 PM, Marcus Sorensen <sh...@gmail.com> wrote:
>>>
>>> > The wiki was the one that had the 'display' parameter shown. I'm
>>> assuming
>>> > the display parameter is only in master then?
>>> >
>>> >
>>> > On Wed, May 1, 2013 at 2:56 PM, Justin Grudzien <gr...@gmail.com>
>>> wrote:
>>> >
>>> >> Which documentation are you referring to? I updated cloudmonkey to add
>>> the
>>> >> set display and I updated the wiki to include the changes. I also
>>> noticed
>>> >> the async issue but haven't gotten around to fixing it yet.
>>> >>
>>> >>
>>> >> On Wed, May 1, 2013 at 8:47 AM, Marcus Sorensen <sh...@gmail.com>
>>> >> wrote:
>>> >>
>>> >>> I noticed that the documentation doesn't quite match up with
>>> cloudmonkey
>>> >> as
>>> >>> installed via tools/cli, nor does it match the tarball. It seems to be
>>> >>> missing 'set display', among other things, and the asyncblock never
>>> >>> returns, in either version, long after the job is finished.
>>> >>
>>>
>>
>>

Re: version of cloudmonkey

[Rohit Yadav <bh...@apache.org>]

On Thu, May 2, 2013 at 5:04 PM, Justin Grudzien <gr...@gmail.com> wrote:

> When I become reliable I am certainly willing to learn how to do it.
>

While one can disagree with me, I feel everyone who is part of the
community should be reliable until proven guilty or whatnot.

Justin, register for an account on pypi and share with me your user id. On
pypi try to upload a fake package just to understand how pypi works.

As agreed in earlier threads, we will never publish a versioned pkg without
community vote (there won't be any separate thing, when our release will
ask to vote on a release, that includes all the components of that release
i.e. cloudmonkey, awsapi, api, utils etc.). Though we will publish
snapshots (or latest src dists) with
cloudmonkey-<cloudstack-target-version>-snapshot<incremental nos.>, so when
one does:

pip install cloudmonkey => gets latest. (the community version)
pip install cloudmonkey==4.1 => gets cloudmonkey 4.1 (the release version)

Though the actual/official source dist. will be published on apache's infra
(pypi is a channel outside of ASF but quite popular and works with
pip/easy_install).

Cheers.


>
> Justin
>
> Sent from my iPhone
>
> On May 2, 2013, at 5:50 AM, Rohit Yadav <bh...@apache.org> wrote:
>
>
>
> On Thu, May 2, 2013 at 4:30 AM, Justin Grudzien <gr...@gmail.com>wrote:
>
>> It is currently in master but I will see if I can get Rohit, who I think
>> owns the process, to create a new version for pip. If that isn't
>> immediately possible I can revert the documentation until it is done. I
>> figured documentation is always last :)
>>
>
> Hey, I don't own the process just help publish snapshots. Chip has access
> to the pypi release channel as well, and any
> committer/pmc/reliable-contributor can gain the access.
> Will take a look at it and try to publish latest snapshot from master this
> weekend (but no promises :)
>
> Cheers.
>
>
>>
>> Justin
>>
>> On May 1, 2013, at 4:06 PM, Marcus Sorensen <sh...@gmail.com> wrote:
>>
>> > The wiki was the one that had the 'display' parameter shown. I'm
>> assuming
>> > the display parameter is only in master then?
>> >
>> >
>> > On Wed, May 1, 2013 at 2:56 PM, Justin Grudzien <gr...@gmail.com>
>> wrote:
>> >
>> >> Which documentation are you referring to? I updated cloudmonkey to add
>> the
>> >> set display and I updated the wiki to include the changes. I also
>> noticed
>> >> the async issue but haven't gotten around to fixing it yet.
>> >>
>> >>
>> >> On Wed, May 1, 2013 at 8:47 AM, Marcus Sorensen <sh...@gmail.com>
>> >> wrote:
>> >>
>> >>> I noticed that the documentation doesn't quite match up with
>> cloudmonkey
>> >> as
>> >>> installed via tools/cli, nor does it match the tarball. It seems to be
>> >>> missing 'set display', among other things, and the asyncblock never
>> >>> returns, in either version, long after the job is finished.
>> >>
>>
>
>

Re: version of cloudmonkey

[Justin Grudzien <gr...@gmail.com>]

When I become reliable I am certainly willing to learn how to do it. 

Justin 

Sent from my iPhone

On May 2, 2013, at 5:50 AM, Rohit Yadav <bh...@apache.org> wrote:

> 
> 
> On Thu, May 2, 2013 at 4:30 AM, Justin Grudzien <gr...@gmail.com> wrote:
>> It is currently in master but I will see if I can get Rohit, who I think owns the process, to create a new version for pip. If that isn't immediately possible I can revert the documentation until it is done. I figured documentation is always last :)
> 
> Hey, I don't own the process just help publish snapshots. Chip has access to the pypi release channel as well, and any committer/pmc/reliable-contributor can gain the access.
> Will take a look at it and try to publish latest snapshot from master this weekend (but no promises :)
> 
> Cheers.
>  
>> 
>> Justin
>> 
>> On May 1, 2013, at 4:06 PM, Marcus Sorensen <sh...@gmail.com> wrote:
>> 
>> > The wiki was the one that had the 'display' parameter shown. I'm assuming
>> > the display parameter is only in master then?
>> >
>> >
>> > On Wed, May 1, 2013 at 2:56 PM, Justin Grudzien <gr...@gmail.com> wrote:
>> >
>> >> Which documentation are you referring to? I updated cloudmonkey to add the
>> >> set display and I updated the wiki to include the changes. I also noticed
>> >> the async issue but haven't gotten around to fixing it yet.
>> >>
>> >>
>> >> On Wed, May 1, 2013 at 8:47 AM, Marcus Sorensen <sh...@gmail.com>
>> >> wrote:
>> >>
>> >>> I noticed that the documentation doesn't quite match up with cloudmonkey
>> >> as
>> >>> installed via tools/cli, nor does it match the tarball. It seems to be
>> >>> missing 'set display', among other things, and the asyncblock never
>> >>> returns, in either version, long after the job is finished.
>> >>
> 

Re: version of cloudmonkey

[Rohit Yadav <bh...@apache.org>]

On Thu, May 2, 2013 at 4:30 AM, Justin Grudzien <gr...@gmail.com> wrote:

> It is currently in master but I will see if I can get Rohit, who I think
> owns the process, to create a new version for pip. If that isn't
> immediately possible I can revert the documentation until it is done. I
> figured documentation is always last :)
>

Hey, I don't own the process just help publish snapshots. Chip has access
to the pypi release channel as well, and any
committer/pmc/reliable-contributor can gain the access.
Will take a look at it and try to publish latest snapshot from master this
weekend (but no promises :)

Cheers.


>
> Justin
>
> On May 1, 2013, at 4:06 PM, Marcus Sorensen <sh...@gmail.com> wrote:
>
> > The wiki was the one that had the 'display' parameter shown. I'm assuming
> > the display parameter is only in master then?
> >
> >
> > On Wed, May 1, 2013 at 2:56 PM, Justin Grudzien <gr...@gmail.com>
> wrote:
> >
> >> Which documentation are you referring to? I updated cloudmonkey to add
> the
> >> set display and I updated the wiki to include the changes. I also
> noticed
> >> the async issue but haven't gotten around to fixing it yet.
> >>
> >>
> >> On Wed, May 1, 2013 at 8:47 AM, Marcus Sorensen <sh...@gmail.com>
> >> wrote:
> >>
> >>> I noticed that the documentation doesn't quite match up with
> cloudmonkey
> >> as
> >>> installed via tools/cli, nor does it match the tarball. It seems to be
> >>> missing 'set display', among other things, and the asyncblock never
> >>> returns, in either version, long after the job is finished.
> >>
>

Re: version of cloudmonkey

[Justin Grudzien <gr...@gmail.com>]

It is currently in master but I will see if I can get Rohit, who I think owns the process, to create a new version for pip. If that isn't immediately possible I can revert the documentation until it is done. I figured documentation is always last :)

Justin 

On May 1, 2013, at 4:06 PM, Marcus Sorensen <sh...@gmail.com> wrote:

> The wiki was the one that had the 'display' parameter shown. I'm assuming
> the display parameter is only in master then?
> 
> 
> On Wed, May 1, 2013 at 2:56 PM, Justin Grudzien <gr...@gmail.com> wrote:
> 
>> Which documentation are you referring to? I updated cloudmonkey to add the
>> set display and I updated the wiki to include the changes. I also noticed
>> the async issue but haven't gotten around to fixing it yet.
>> 
>> 
>> On Wed, May 1, 2013 at 8:47 AM, Marcus Sorensen <sh...@gmail.com>
>> wrote:
>> 
>>> I noticed that the documentation doesn't quite match up with cloudmonkey
>> as
>>> installed via tools/cli, nor does it match the tarball. It seems to be
>>> missing 'set display', among other things, and the asyncblock never
>>> returns, in either version, long after the job is finished.
>> 

Re: version of cloudmonkey

[Marcus Sorensen <sh...@gmail.com>]

The wiki was the one that had the 'display' parameter shown. I'm assuming
the display parameter is only in master then?


On Wed, May 1, 2013 at 2:56 PM, Justin Grudzien <gr...@gmail.com> wrote:

> Which documentation are you referring to? I updated cloudmonkey to add the
> set display and I updated the wiki to include the changes. I also noticed
> the async issue but haven't gotten around to fixing it yet.
>
>
> On Wed, May 1, 2013 at 8:47 AM, Marcus Sorensen <sh...@gmail.com>
> wrote:
>
> > I noticed that the documentation doesn't quite match up with cloudmonkey
> as
> > installed via tools/cli, nor does it match the tarball. It seems to be
> > missing 'set display', among other things, and the asyncblock never
> > returns, in either version, long after the job is finished.
> >
>

Re: version of cloudmonkey

[Justin Grudzien <gr...@gmail.com>]

Which documentation are you referring to? I updated cloudmonkey to add the
set display and I updated the wiki to include the changes. I also noticed
the async issue but haven't gotten around to fixing it yet.


On Wed, May 1, 2013 at 8:47 AM, Marcus Sorensen <sh...@gmail.com> wrote:

> I noticed that the documentation doesn't quite match up with cloudmonkey as
> installed via tools/cli, nor does it match the tarball. It seems to be
> missing 'set display', among other things, and the asyncblock never
> returns, in either version, long after the job is finished.
>