Open Stack

Puppet is failing to build the packages - which is probably understandable given it's a refactor.

I'm not sure if this is something that points to a problem with the refactor or the packaging itself - hopefully Dan can review the logs, or if others want to see more of the details look at the logs at https://review.openstack.org/39929.

I don't see any point in triggering another Smokestack run as it's likely to fail again until the packaging issue has been resolved by Dan's team.

Bob

From: Davanum Srinivas [mailto:davanum at gmail.com]
Sent: 05 September 2013 17:04
To: Mark McLoughlin; OpenStack Development Mailing List
Subject: Re: [openstack-dev] [Nova] FFE Request: oslo-messaging

Thanks Mark. Looks like we need to get someone to manually trigger Smokestack to run against this review at least once since i don't see any +1's from Smokestack for some reason.

On Thu, Sep 5, 2013 at 11:49 AM, Mark McLoughlin <markmc at redhat.com<mailto:markmc at redhat.com>> wrote:
Hi

On Thu, 2013-09-05 at 10:43 -0400, Davanum Srinivas wrote:
> Mark,
>
> Has this changeset get through a full tempest with QPid enabled?
No, I've only done local testing with the qpid transport to date.

I think Smokestack is the only CI tool actively testing the qpid driver.
I ran out of time adding oslo.messaging to Smokestack before heading off
on vacation, but I expect I'll get to it next week.

Cheers,
Mark.


>
> thanks,
> dims
>
>
> On Thu, Sep 5, 2013 at 10:17 AM, Mark McLoughlin <markmc at redhat.com<mailto:markmc at redhat.com>> wrote:
>
> > Hi
> >
> > I'd like to request a feature freeze exception for the final (and
> > admittedly the largest) patch in the series of 40 patches to port Nova to
> > oslo.messaging:
> >
> >   https://review.openstack.org/39929
> >
> > While this change doesn't provide any immediate user-visible benefit, it
> > would be massively helpful in maintaining momentum behind the effort all
> > through the Havana cycle to move the RPC code from oslo-incubator into a
> > library.
> >
> > In terms of risk of regression, there is certainly some risk but that risk
> > is mitigated by the fact that the core code of each of the transport
> > drivers has been modified minimally. The idea was to delay re-factoring
> > these drivers until we were sure that we hadn't caused any regressions in
> > Nova. The code has been happily passing the devstack/tempest based
> > integration tests for 10 days now.
> >
> > Thanks,
> > Mark.
> >
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
>
>



_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Davanum Srinivas :: http://davanum.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130906/bff4996d/attachment.html>