pushing to fedorahosted repos

[Michael Neale]

Hey all - on the deltacloud website it wants patches to be emailed
around (recently I had a ticket closed to import my rackspace driver -
so it looks like that was a one off).

Is that still the case? I am referring to framework, docs and drivers
(not portal).

[jason.guiditta]

Michael, yes, it would be good to send patches to this list, though I
don't know how much we have formalized the ack process at this point.
I know for portal we are not pushing a patch w/o an ack, and I would
advocate doing that for the framework side as well, now that it is
available to the public.  Of course, as a committer, this is somewhat
up to your discretion, afaik.

-j

On Wed, Oct 7, 2009 at 9:42 PM, Michael Neale  wrote:
> Hey all - on the deltacloud website it wants patches to be emailed
> around (recently I had a ticket closed to import my rackspace driver -
> so it looks like that was a one off).
>
> Is that still the case? I am referring to framework, docs and drivers
> (not portal).
>
> --
> Michael D Neale
> home: www.michaelneale.net
> blog: michaelneale.blogspot.com
> _______________________________________________
> deltacloud-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/deltacloud-devel

[Michael Neale]

I didn't realise I had commit rights? (I guess that was the bob
sponsoring thing? !).
I am more then happy to pass around patches and wait for ack's,
especially if I am tweaking error handling or sensitive things like
that.

I am just not sure if I (if I have access) or someone else is meant to
do the push, just don't want to forget about something ;)

On Thu, Oct 8, 2009 at 1:00 PM, Jason Guiditta  wrote:
> Michael, yes, it would be good to send patches to this list, though I
> don't know how much we have formalized the ack process at this point.
> I know for portal we are not pushing a patch w/o an ack, and I would
> advocate doing that for the framework side as well, now that it is
> available to the public.  Of course, as a committer, this is somewhat
> up to your discretion, afaik.
>
> -j
>
> On Wed, Oct 7, 2009 at 9:42 PM, Michael Neale  wrote:
> > Hey all - on the deltacloud website it wants patches to be emailed
> > around (recently I had a ticket closed to import my rackspace driver -
> > so it looks like that was a one off).
> >
> > Is that still the case? I am referring to framework, docs and drivers
> > (not portal).
> >
> > --
> > Michael D Neale
> > home: www.michaelneale.net
> > blog: michaelneale.blogspot.com
> > _______________________________________________
> > deltacloud-devel mailing list
> > [e-mail]
> > https://fedorahosted.org/mailman/listinfo/deltacloud-devel

[Hugh O. Brock]

On Thu, Oct 08, 2009 at 01:32:29PM +1100, Michael Neale wrote:
> I didn't realise I had commit rights? (I guess that was the bob
> sponsoring thing? !).
> I am more then happy to pass around patches and wait for ack's,
> especially if I am tweaking error handling or sensitive things like
> that.
>
> I am just not sure if I (if I have access) or someone else is meant to
> do the push, just don't want to forget about something ;)
>
> On Thu, Oct 8, 2009 at 1:00 PM, Jason Guiditta  wrote:
> > Michael, yes, it would be good to send patches to this list, though I
> > don't know how much we have formalized the ack process at this point.
> > I know for portal we are not pushing a patch w/o an ack, and I would
> > advocate doing that for the framework side as well, now that it is
> > available to the public.  Of course, as a committer, this is somewhat
> > up to your discretion, afaik.
> >
> > -j

Yeah standard procedure is to post patches and get somebody to ack them,
then commit. We have not been enforcing that strictly thus far in the
interest of getting things up and running, but it's more important
now. Great to see the rackspace driver in though! Anyone test it yet?

--Hugh
> > On Wed, Oct 7, 2009 at 9:42 PM, Michael Neale  wrote:
> > > Hey all - on the deltacloud website it wants patches to be emailed
> > > around (recently I had a ticket closed to import my rackspace driver -
> > > so it looks like that was a one off).
> > >
> > > Is that still the case? I am referring to framework, docs and drivers
> > > (not portal).
> > >
> > > --
> > > Michael D Neale
> > > home: www.michaelneale.net
> > > blog: michaelneale.blogspot.com
> > > _______________________________________________
> > > deltacloud-devel mailing list
> > > [e-mail]
> > > https://fedorahosted.org/mailman/listinfo/deltacloud-devel
>
> -- 
> Michael D Neale
> home: www.michaelneale.net
> blog: michaelneale.blogspot.com
> _______________________________________________
> deltacloud-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/deltacloud-devel

[Michael Neale]

On Thu, Oct 8, 2009 at 9:13 PM, Hugh O. Brock  wrote:
> Yeah standard procedure is to post patches and get somebody to ack them,
> then commit. We have not been enforcing that strictly thus far in the
> interest of getting things up and running, but it's more important
> now. Great to see the rackspace driver in though! Anyone test it yet?
>
> --Hugh

Only me ;) I didn't send around a patch for rackspace support as each
driver is (currently) its own repo.

Pretty simple as they had a REST styled API, which supported
application/json content type, which made reading it into Ruby just a
doddle (which means easy, I think...).

Just wanted to update the docs to reflect it.

I do need to tweak the framework to have some standard error we can
throw to percolate up to the user that something is badly wrong
(probably programmer error !).

[Hugh O. Brock]

On Thu, Oct 08, 2009 at 09:22:20PM +1100, Michael Neale wrote:
> On Thu, Oct 8, 2009 at 9:13 PM, Hugh O. Brock  wrote:
> > Yeah standard procedure is to post patches and get somebody to ack them,
> > then commit. We have not been enforcing that strictly thus far in the
> > interest of getting things up and running, but it's more important
> > now. Great to see the rackspace driver in though! Anyone test it yet?
> >
> > --Hugh
>
> Only me ;) I didn't send around a patch for rackspace support as each
> driver is (currently) its own repo.
>
> Pretty simple as they had a REST styled API, which supported
> application/json content type, which made reading it into Ruby just a
> doddle (which means easy, I think...).
>
> Just wanted to update the docs to reflect it.
>
> I do need to tweak the framework to have some standard error we can
> throw to percolate up to the user that something is badly wrong
> (probably programmer error !).

Hmm, yes, I'm not sure how far we've gotten with error handling and
reporting in general. We need some well defined error handling paths...

Jeremy Perry should be able to take care of updating the docs -- they're
generated from some stuff in the source repo. At the very least he can
let you know what to change.

--Hugh

[Michael Neale]

> Hmm, yes, I'm not sure how far we've gotten with error handling and
> reporting in general. We need some well defined error handling paths...

Yes, not a big deal, most of my errors were my fat fingering of
digging out items from json responses, or typos in URIs. But still, as
rackspace returns errors as response bodies (json or XML) probably
should have a way to fling it back out to the caller, as no doubt the
specific error probably makes sense to them (eg "insert more coins you
cheapskate !" etc).
> Jeremy Perry should be able to take care of updating the docs -- they're
> generated from some stuff in the source repo. At the very least he can
> let you know what to change.

Thanks !

Jeremy - you around on this list?
> --Hugh

[Jeremy Perry]

Hi Michael - let me know when you've updated the docs (in the -docs  
repo) and i'll get the updates pushed to the site. If you want advice  
about what sections to update, Bob McWhirter could advise.

Jeremy

On Oct 8, 2009, at 7:01 AM, Michael Neale wrote:
> > Hmm, yes, I'm not sure how far we've gotten with error handling and
> > reporting in general. We need some well defined error handling  
> > paths...
>
> Yes, not a big deal, most of my errors were my fat fingering of
> digging out items from json responses, or typos in URIs. But still, as
> rackspace returns errors as response bodies (json or XML) probably
> should have a way to fling it back out to the caller, as no doubt the
> specific error probably makes sense to them (eg "insert more coins you
> cheapskate !" etc).
> > Jeremy Perry should be able to take care of updating the docs --  
> > they're
> > generated from some stuff in the source repo. At the very least he  
> > can
> > let you know what to change.
>
> Thanks !
>
> Jeremy - you around on this list?
> > --Hugh
>
> -- 
> Michael D Neale
> home: www.michaelneale.net
> blog: michaelneale.blogspot.com
> _______________________________________________
> deltacloud-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/deltacloud-devel

[Michael Neale]

Thanks Jeremy (fyi I am @redhat as well, just using gmail for non
business due to my tendency to lock my VPN token in my office when I
head home).

OK find attached a patch for /docs,

and in terms of website content: could you update:
1) http://deltacloud.org/index.html - to mention rackspace as an
available driver?
2) http://deltacloud.org/contribute.html - to have a link to
git clone git://git.fedorahosted.org/git/deltacloud/driver-rackspace.git/

Thanks !

On Fri, Oct 9, 2009 at 1:03 AM, Jeremy Perry  wrote:
> Hi Michael - let me know when you've updated the docs (in the -docs repo)
> and i'll get the updates pushed to the site. If you want advice about what
> sections to update, Bob McWhirter could advise.
>
> Jeremy
>
> On Oct 8, 2009, at 7:01 AM, Michael Neale wrote:
> > > Hmm, yes, I'm not sure how far we've gotten with error handling and
> > > reporting in general. We need some well defined error handling paths...
> >
> > Yes, not a big deal, most of my errors were my fat fingering of
> > digging out items from json responses, or typos in URIs. But still, as
> > rackspace returns errors as response bodies (json or XML) probably
> > should have a way to fling it back out to the caller, as no doubt the
> > specific error probably makes sense to them (eg "insert more coins you
> > cheapskate !" etc).
> > > Jeremy Perry should be able to take care of updating the docs -- they're
> > > generated from some stuff in the source repo. At the very least he can
> > > let you know what to change.
> >
> > Thanks !
> >
> > Jeremy - you around on this list?
> > > --Hugh
> >
> > --
> > Michael D Neale
> > home: www.michaelneale.net
> > blog: michaelneale.blogspot.com
> > _______________________________________________
> > deltacloud-devel mailing list
> > [e-mail]
> > https://fedorahosted.org/mailman/listinfo/deltacloud-devel

[Michael Neale]

Jeremy - for the docs update I just went and pushed it anyway. So its
just the web site + syncing the /docs to the website I guess?

(if there is a way I can get access to do that, just let me know
if/how and I will try to not completely pants the website up).

On Fri, Oct 9, 2009 at 11:34 AM, Michael Neale  wrote:
> Thanks Jeremy (fyi I am @redhat as well, just using gmail for non
> business due to my tendency to lock my VPN token in my office when I
> head home).
>
> OK find attached a patch for /docs,
>
> and in terms of website content: could you update:
> http://deltacloud.org/index.html - to mention rackspace as an
>
> available driver?
> 2) http://deltacloud.org/contribute.html - to have a link to
> git clone git://git.fedorahosted.org/git/deltacloud/driver-rackspace.git/
>
> Thanks !
>
> On Fri, Oct 9, 2009 at 1:03 AM, Jeremy Perry  wrote:
> > Hi Michael - let me know when you've updated the docs (in the -docs repo)
> > and i'll get the updates pushed to the site. If you want advice about what
> > sections to update, Bob McWhirter could advise.
> >
> > Jeremy
> >
> > On Oct 8, 2009, at 7:01 AM, Michael Neale wrote:
> > > > Hmm, yes, I'm not sure how far we've gotten with error handling and
> > > > reporting in general. We need some well defined error handling paths...
> > >
> > > Yes, not a big deal, most of my errors were my fat fingering of
> > > digging out items from json responses, or typos in URIs. But still, as
> > > rackspace returns errors as response bodies (json or XML) probably
> > > should have a way to fling it back out to the caller, as no doubt the
> > > specific error probably makes sense to them (eg "insert more coins you
> > > cheapskate !" etc).
> > > > Jeremy Perry should be able to take care of updating the docs -- they're
> > > > generated from some stuff in the source repo. At the very least he can
> > > > let you know what to change.
> > >
> > > Thanks !
> > >
> > > Jeremy - you around on this list?
> > > > --Hugh
> > >
> > > --
> > > Michael D Neale
> > > home: www.michaelneale.net
> > > blog: michaelneale.blogspot.com
> > > _______________________________________________
> > > deltacloud-devel mailing list
> > > [e-mail]
> > > https://fedorahosted.org/mailman/listinfo/deltacloud-devel
>
> --
> Michael D Neale
> home: www.michaelneale.net
> blog: michaelneale.blogspot.com