Re: [openstack-dev] [stable/havana] gate broken

Thanks for dealing with this! On 11/17/13 10:45 PM, "Sean Dague" wrote: >Clark, > >Thanks for tracking that down, just pushed those changes to the gate. > >On Sun, Nov 17, 2013 at 3:03 PM, Clark Boylan >wrote: >> On Sun, Nov 17, 2013 at 7:53 AM, Gary Kotton wrote: >>> Thanks. Looks like somet

Re: [openstack-dev] Openstack + OpenContrail

On Nov 16, 2013, at 9:43 AM, Dean Troyer wrote: > On Sat, Nov 16, 2013 at 11:15 AM, Harshad Nakil > wrote: > Sean, > We have diff in three repositories. > Nova, Neutron and devstack. Each review is requiring other to happen first. > Do you have recommendation how do we deal with these dependen

Re: [openstack-dev] Split of the openstack-dev list (summary so far)

A couple of quick points. 1) I think that splitting the list is the wrong approach. 2) Perhaps we need to look at adding a mechanism that enforces the use of tags in the subject line (send a nice "sorry, but you need to indicate the topic(s) you are mailing about" error back if it doesn't exist, ke

Re: [openstack-dev] [nova][cinder][oslo][scheduler] How to leverage oslo schduler/filters for nova and cinder

Khanh-Toan, >> There is a need for a scheduler that can scheduling a group of resources as a whole, which is difficult to realize due to the separation of Nova, Cinder –scheduler. Thus I’m in favor of a dedicated scheduler component. What we need is to have one scheduler that is able effectively

[openstack-dev] [nova] Blueprint - Disable child cell support

Hello, folks, I proposed a blueprint https://blueprints.launchpad.net/nova/+spec/disable-child-cell-support , but have not received any feedback yet. Anyone interested in this please have a look at, any feedback would be appreciated ! Thanks, Yingjun___

[openstack-dev] [Ironic][Ceilometer] get IPMI data for ceilometer

Hi stackers, During the summit session Expose hardware sensor (IPMI) data https://etherpad.openstack.org/p/icehouse-summit-ceilometer-hardware-sensors, it was proposed to deploy a ceilometer agent next to the ironic conductor to the get the ipmi data. Here I'd like to ask some questions to figu

[openstack-dev] [Neutron][Tempest] Tempest API test for Neutron LBaaS

Hi folks, I'm working on major change to Neutron LBaaS API, obviously it will break existing tempest API tests for LBaaS. What would be the right process to deal with this? I guess I can't just push fixed tests to tempest because they will not pass against existing neutron code, and vice versa. T

Re: [openstack-dev] [Neutron] Plugin and Driver Inclusion Requirements

For third party testing, I am afraid these tests will make the patch merge process much longer since each patch, which even has nothing to do with the specific plugins, will triggers the unwanted third party testing jobs. On Fri, Nov 15, 2013 at 4:20 AM, Mark McClain wrote: > tl;dr > - > The

Re: [openstack-dev] [Neutron][LBaaS] Loadbalancer instance design.

> How do you plan to handle API compatibility? The new API is not compatible and i think there was a consensus that such change is needed and incompatibility is justified. > Is an extension for each (eg. add router_id to a loadblancer resource) necessary ? Basically, yes, there should be an extens

[openstack-dev] [Mistral] Agenda for IRC community meeting - 11/18/2013

Hi, Here’s the agenda for today’s IRC community meeting on #openstack-meeting at 16.00 UTC: Review last week's action items Discuss PoC scope Discuss Roadmap Discuss Blueprints Discuss and update https://etherpad.openstack.org/p/MistralDesignAndDependencies Open discussion You can also find it

Re: [openstack-dev] [Neutron][LBaaS] Loadbalancer instance design.

Hi, > 2. Loadbalancer can be used to bind configuration to a provider, device, > agent (host), router What's the plan about this ? Is an extension for each (eg. add router_id to a loadblancer resource) necessary ? Thanks. Itsuro Oda On Fri, 15 Nov 2013 17:14:47 +0400 Eugene Nikanorov wrote:

Re: [openstack-dev] [Nova] New API requirements, review of GCE

On Sat, Nov 16, 2013 at 4:02 AM, Mark McLoughlin wrote: > > If so, do we apply the same standards to the EC2 API? > > How much time do we give EC2 to get up to this standard before we rip > > it out? > > I hadn't understood the EC2 API to be in such a woeful state. Are we > saying the implementat

Re: [openstack-dev] [Nova] New API requirements, review of GCE

On Sat, Nov 16, 2013 at 6:01 AM, Joe Gordon wrote: > > On Fri, Nov 15, 2013 at 9:01 AM, Mark McLoughlin wrote: > >> On Fri, 2013-11-15 at 11:28 -0500, Russell Bryant wrote: >> > Greetings, >> > >> > We've talked a lot about requirements for new compute drivers [1]. I >> > think the same sort of

Re: [openstack-dev] [Neutron][LBaaS] Loadbalancer instance design.

At Fri, 15 Nov 2013 17:14:47 +0400, Eugene Nikanorov wrote: > Hi folks, > > I've created a brief description of this feature. > You can find it here: > https://wiki.openstack.org/wiki/Neutron/LBaaS/LoadbalancerInstance > > I w

Re: [openstack-dev] [nova] [api] How to handle bug 1249526?

Hi Matt, On Mon, Nov 18, 2013 at 8:35 AM, Matt Riedemann wrote: > This is mainly just a newbie question but looks like it could be an easy > fix. The bug report is just asking for the nova os-fixed-ips API extension > to return the 'reserved' status for the fixed IP. I don't see that in the > v3

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On Sun, Nov 17, 2013 at 2:57 PM, Steve Baker wrote: > On 11/15/2013 05:19 AM, Christopher Armstrong wrote: > > http://docs.heatautoscale.apiary.io/ > > > > I've thrown together a rough sketch of the proposed API for > > autoscaling. It's written in API-Blueprint format (which is a simple > > subs

[openstack-dev] [nova] [api] How to handle bug 1249526?

This is mainly just a newbie question but looks like it could be an easy fix. The bug report is just asking for the nova os-fixed-ips API extension to return the 'reserved' status for the fixed IP. I don't see that in the v3 API list though, was that dropped in V3? If it's not being ported to V

Re: [openstack-dev] sqlalchemy-migrate needs a new release

On 11/17/2013 03:56 PM, Sean Dague wrote: > Given that sqla-migration is now in stackforge, it would be a really > good idea to go down the path that wsme and pecan are going and run a > devstack job to make sure they don't break the rest of OpenStack. It > will definitely help on feeling confide

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 11/15/2013 05:19 AM, Christopher Armstrong wrote: > http://docs.heatautoscale.apiary.io/ > > I've thrown together a rough sketch of the proposed API for > autoscaling. It's written in API-Blueprint format (which is a simple > subset of Markdown) and provides schemas for inputs and outputs using

Re: [openstack-dev] sqlalchemy-migrate needs a new release

Given that sqla-migration is now in stackforge, it would be a really good idea to go down the path that wsme and pecan are going and run a devstack job to make sure they don't break the rest of OpenStack. It will definitely help on feeling confident for releases. On Fri, Nov 15, 2013 at 4:13 PM, B

Re: [openstack-dev] [stable/havana] gate broken

Clark, Thanks for tracking that down, just pushed those changes to the gate. On Sun, Nov 17, 2013 at 3:03 PM, Clark Boylan wrote: > On Sun, Nov 17, 2013 at 7:53 AM, Gary Kotton wrote: >> Thanks. Looks like something fishy with tempest. When I just run neutron >> everything is well and fine. >>

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 11/15/2013 05:19 AM, Christopher Armstrong wrote: > http://docs.heatautoscale.apiary.io/ > > I've thrown together a rough sketch of the proposed API for > autoscaling. It's written in API-Blueprint format (which is a simple > subset of Markdown) and provides schemas for inputs and outputs using

Re: [openstack-dev] [stable/havana] gate broken

On Sun, Nov 17, 2013 at 7:53 AM, Gary Kotton wrote: > Thanks. Looks like something fishy with tempest. When I just run neutron > everything is well and fine. > > On 11/17/13 5:50 PM, "Matt Riedemann" wrote: > >> >> >>On Sunday, November 17, 2013 7:46:39 AM, Gary Kotton wrote: >>> Hi, >>> The gati

Re: [openstack-dev] [nova][cinder][oslo][scheduler] How to leverage oslo schduler/filters for nova and cinder

Boris Pavlovic wrote on 15/11/2013 05:57:20 PM: > >> How do you envision the life cycle of such a scheduler in terms > of code repository, build, test, etc? > > As a first step we could just make it inside nova, when we finish > and prove that this approach works well we could split it out th

Re: [openstack-dev] [stable/havana] gate broken

Thanks. Looks like something fishy with tempest. When I just run neutron everything is well and fine. On 11/17/13 5:50 PM, "Matt Riedemann" wrote: > > >On Sunday, November 17, 2013 7:46:39 AM, Gary Kotton wrote: >> Hi, >> The gating for the stable version is broken when the running the >> neutro

Re: [openstack-dev] [stable/havana] gate broken

On Sunday, November 17, 2013 7:46:39 AM, Gary Kotton wrote: Hi, The gating for the stable version is broken when the running the neutron gate. Locally this works but the gate has problem. All of the services are up and running correctly. There are some exceptions with the ceilometer service but

Re: [openstack-dev] [qa] Proposals for Tempest core

On 11/16/2013 11:26 PM, Matthew Treinish wrote: > I think responding to this is worth breaking my vacation email embargo. > Although I seem to remember a certain PTL whose vacation we waited for the > last time we did core proposals... I think we need to put "post summit vacation week" on ttx

Re: [openstack-dev] [stable/havana] gate broken

On 11/17/2013 08:46 AM, Gary Kotton wrote: > Hi, > The gating for the stable version is broken when the running the neutron > gate. Locally this works but the gate has problem. All of the services > are up and running correctly. There are some exceptions with the > ceilometer service but that is no

[openstack-dev] [stable/havana] gate broken

Hi, The gating for the stable version is broken when the running the neutron gate. Locally this works but the gate has problem. All of the services are up and running correctly. There are some exceptions with the ceilometer service but that is not related to the neutron gating. The error messag

Re: [openstack-dev] [qa] Proposals for Tempest core

+1 for both! From: Sean Dague [s...@dague.net] Sent: Friday, November 15, 2013 2:38 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [qa] Proposals for Tempest core It's post summit time, so time to evaluate our c