Re: [openstack-dev] [Ceilometer]Add hardware pollster of memory buffer and cache

Hi guys, I have submit a blueprint of adding hardware memory buffer and cache pollster.‍ Anyone interested in it, Please review https://blueprints.launchpad.net/ceilometer/+spec/hardware-memory-buffer-and-cache-metrics,‍ Thanks All. -- Luo gangyiluogan...@chinamobile.com

Re: [openstack-dev] [nova] Updating 'scheduled_at' field of nova instances in the database.

On Tue, Mar 24, 2015 at 11:57 AM, Deepak Shetty wrote: > > > On Tue, Mar 24, 2015 at 10:58 AM, Deepthi Dharwar < > deep...@linux.vnet.ibm.com> wrote: > >> On 03/23/2015 09:00 PM, Jay Pipes wrote: >> > On Mon, Mar 23, 2015 at 11:18:28AM +0530, Deepthi Dharwar wrote: >> >> All the VM information is

Re: [openstack-dev] [nova] Updating 'scheduled_at' field of nova instances in the database.

On Tue, Mar 24, 2015 at 10:58 AM, Deepthi Dharwar < deep...@linux.vnet.ibm.com> wrote: > On 03/23/2015 09:00 PM, Jay Pipes wrote: > > On Mon, Mar 23, 2015 at 11:18:28AM +0530, Deepthi Dharwar wrote: > >> All the VM information is stored in the instances table. > >> This includes all the time relat

[openstack-dev] [gantt] Scheduler sub-group meeting agenda 3/25

Meeting on #openstack-meeting at 1500 UTC (9:00AM MDT) 1) Patch status - https://etherpad.openstack.org/p/kilo-nova-priorities-tracking 2) Vancouver design summit - start thinking about what we want to discuss -- Don Dugger "Censeo Toto nos in Kansa esse decisse." - D. Gale Ph: 303

Re: [openstack-dev] [nova][api] Microversions. And why do we need API extensions for new API functionality?

On Tue, Mar 24, 2015 at 5:45 AM, Jay Pipes wrote: > On Tue, Mar 10, 2015 at 09:52:14PM +1030, Christopher Yeoh wrote: > > On Mon, 09 Mar 2015 16:14:21 -0400 > > Sean Dague wrote: > > > > > On 03/09/2015 03:37 PM, Jay Pipes wrote: > > > > On 03/08/2015 08:10 AM, Alex Xu wrote: > > > >> Thanks for

Re: [openstack-dev] [nova] Updating 'scheduled_at' field of nova instances in the database.

On 03/23/2015 09:00 PM, Jay Pipes wrote: > On Mon, Mar 23, 2015 at 11:18:28AM +0530, Deepthi Dharwar wrote: >> All the VM information is stored in the instances table. >> This includes all the time related field like scheduled_at, launched_at etc. >> >> After upgrading to Juno, I have noticed that

Re: [openstack-dev] [nova] how to handle vendor-specific API microversions?

On 03/23/2015 03:28 AM, John Garbutt wrote: We are not stopping vendor specific API endpoints, that appear separately in the keystone catalog. Certainly, thats where I hope things that would never go upstream will move to. How would that be expected to work for things where it's fundamentally

Re: [openstack-dev] [devstack] Overriding settings file for devstack plugin

On Tue, Mar 24, 2015 at 8:36 AM, Ian Wienand wrote: > On 03/23/2015 09:20 PM, Deepak Shetty wrote: > >> Hi all, >>I was wondering if there was a neat way to override the settings file >> present in the devstack plugin stackforge project. >> >> For eg: stackforge/devstack-plugin-glusterfs >> >

Re: [openstack-dev] [nova] how to handle vendor-specific API microversions?

2015-03-21 23:31 GMT+08:00 Monty Taylor : > I would vote that we not make this pleasant or easy for vendors who are > wanting to add a feature to the API. As a person who uses several clouds > daily, I can tell you that a vendor chosing to do that is VERY mean to > users, and provides absolutely n

Re: [openstack-dev] [Openstack-operators] [Neutron] Deprecating the use_namespaces option - Now's the time to speak up!

On 2015-03-21 02:57, Assaf Muller wrote: Hello everyone, The use_namespaces option in the L3 and DHCP Neutron agents controls if you can create multiple routers and DHCP networks managed by a single L3/DHCP agent, or if the agent manages only a single resource. Are the setups out there *not*

Re: [openstack-dev] [devstack] Overriding settings file for devstack plugin

On 03/23/2015 09:20 PM, Deepak Shetty wrote: Hi all, I was wondering if there was a neat way to override the settings file present in the devstack plugin stackforge project. For eg: stackforge/devstack-plugin-glusterfs I plan to use `enable_plugin glusterfs ` in my local to setup GlusterFS b

Re: [openstack-dev] About Sahara EDP New Ideas for Liberty

Hi Andrew. Thanks for response. My reply in line. From: Andrew Lazarev [mailto:alaza...@mirantis.com] Sent: Saturday, March 21, 2015 12:10 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] About Sahara EDP New Ideas for Liberty Hi Weiting, >1. Add

Re: [openstack-dev] [magnum] swagger-codegen generated code for python-k8sclient

Hi Hongbin, On Tue, Mar 24, 2015 at 12:37 AM, Hongbin Lu wrote: > Hi Madhuri, > > Amazing work! I wouldn't concern the code duplication and modularity issue > since the codes are generated. However, there is another concern here: if > we find a bug/improvement of the generated code, we probably

Re: [openstack-dev] [nova][api] Microversions. And why do we need API extensions for new API functionality?

On Mon, Mar 23, 2015 at 09:35:50PM +, Jeremy Stanley wrote: > On 2015-03-23 15:15:18 -0400 (-0400), Jay Pipes wrote: > [...] > > I don't want it suppressed. I want the use of API extensions and the > > extension framework(s) to be completely dropped for all future > > API-affecting work. > [...

Re: [openstack-dev] [magnum] swagger-codegen generated code for python-k8sclient

Hi Steven, On Mon, Mar 23, 2015 at 11:11 PM, Steven Dake (stdake) wrote: > > > From: Madhuri Rai > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Date: Monday, March 23, 2015 at 1:53 AM > To: "openstack-dev@lists.openstack.or

Re: [openstack-dev] Cinder Third-Party CI: what next? (was Re: [cinder] Request exemption for removal of NetApp FC drivers (no voting CI))

As an Engineer running the NetApp CI, I thought it would be a good time to chime in here. While I have many opinions around this whole process, I will try my best to avoid any judgement and minimize ratholes. Over the past year, we have implemented a scalable CI system that is now running tests ag

Re: [openstack-dev] [magnum] updated Fedora Atomic image available - needs testing

Note to community, The various patches needed to enable the fedora-21-atomic-2 image with k8s v0.11 are merged after multiple functional tests. You will need to rebuild your devstack environment with a fresh pull if you are developing Magnum. Enjoy :) On 3/22/15, 8:10 AM, "Adrian Otto" wrote:

Re: [openstack-dev] [api][neutron] Best API for generating subnets from pool

I just think that we might bury this discussion considering what Carl said, and that I agree with. So far we don't even know if we'll ever need this feature. When a concrete use case will come for asking things like: gimme a /22 Ipv4 network and make sure I have a pool spanning from the 1st to the

Re: [openstack-dev] [api][neutron] Best API for generating subnets from pool

I don't think they would be surprised if we call it offset or index. >To me, 0.0.0.63 didn't say that I'd get something ending in .63. Perhaps this is just a difference in backgrounds then. Even though I'm work on network stuff all of the time, when I see that it's not obvious that it will be mas

[openstack-dev] [Neutron][L3] Stop agent scheduling without stopping sevices

Neutron cores, I have submitted the change [1] which is related to the thread [2] in January. Unfortunately it did not attract the interest of many core reviewers, and only time has passed. Now it is pointed that it may need FFE/SSE, and the opinion of the core is a bit divided about implement

Re: [openstack-dev] [api][neutron] Best API for generating subnets from pool

On Mon, Mar 23, 2015 at 4:23 PM, Kevin Benton wrote: > How would you represent that you want the last address in a /26 network if > you don't know what address range you are getting? 0.0.0.63? That seems > pretty confusing when the resulting address turns out to be 192.168.10.191. > >>It isn't a n

Re: [openstack-dev] Cinder Third-Party CI: what next? (was Re: [cinder] Request exemption for removal of NetApp FC drivers (no voting CI))

On 21:51 Mon 23 Mar , Rochelle Grober wrote: > I’d like to suggest that the myriad wiki pages and spreadsheets for Third > Party CI also be consolidated to a more manageable count. Just looking for > maintainers contact, you can find information (often conflicting) in > Stackalytics, on the Th

Re: [openstack-dev] [api][neutron] Best API for generating subnets from pool

How would you represent that you want the last address in a /26 network if you don't know what address range you are getting? 0.0.0.63? That seems pretty confusing when the resulting address turns out to be 192.168.10.191. >It isn't a new concept to think about the network and host parts of an IP

Re: [openstack-dev] [OpenStack-Infra][cinder] Could you please re-consider Oracle ZFS/SA Cinder drivers (iSCSI and NFS)

Hello Cinder team, Oracle ZFSSA CI has been reporting since March 20th. Below is a link to the list of results the CI already posted: https://review.openstack.org/#/q/reviewer:%22Oracle+ZFSSA+CI%22,n,z Our CI system will be running and reporting results from now on, hence I kindly request th

Re: [openstack-dev] [nova][api] Microversions. And why do we need API extensions for new API functionality?

On Mon, Mar 23, 2015 at 2:35 PM, Jeremy Stanley wrote: > On 2015-03-23 15:15:18 -0400 (-0400), Jay Pipes wrote: > [...] > > I don't want it suppressed. I want the use of API extensions and the > > extension framework(s) to be completely dropped for all future > > API-affecting work. > [...] > > P

Re: [openstack-dev] Cinder Third-Party CI: what next? (was Re: [cinder] Request exemption for removal of NetApp FC drivers (no voting CI))

On 03/23/2015 05:51 PM, Rochelle Grober wrote: > I’d like to suggest that the myriad wiki pages and spreadsheets for Third > Party CI also be consolidated to a more manageable count. Just looking for > maintainers contact, you can find information (often conflicting) in > Stackalytics, on the T

Re: [openstack-dev] [nova] proposing feature for Liberty, would this need a spec?

I'm not 100% sure if this would be trivial or not, but the process to find out isn't scary. We should add this to a nova meeting agenda on the wiki and talk through it during a meeting. (Noting that we're not approving specs for liberty in any form until the Kilo branch is cut, so we have some tim

Re: [openstack-dev] Cinder Third-Party CI: what next? (was Re: [cinder] Request exemption for removal of NetApp FC drivers (no voting CI))

I’d like to suggest that the myriad wiki pages and spreadsheets for Third Party CI also be consolidated to a more manageable count. Just looking for maintainers contact, you can find information (often conflicting) in Stackalytics, on the ThirdPartyDrivers page, on the Cinder PTL’s google doc a

Re: [openstack-dev] Cinder Third-Party CI: what next?

On 03/23/2015 05:21 PM, Stefano Maffulli wrote: > On Mon, 2015-03-23 at 16:23 -0400, Anita Kuno wrote: >> Some folks just will not respect other people's time. To pretend >> otherwise is a huge dis-service to folks trying their hardest to >> support those worthy of the support. > > This may be tru

[openstack-dev] [Keystone][FFE] ECP wrapped assertions

I'd like to request an exemption for the following to go into the Kilo release. This work is crucial for: - Keystone to Keystone communication. An ECP wrapped SAML assertion will make it much easier for consumers and clients to use the K2K feature in Keystone. Currently, a client must take th

Re: [openstack-dev] Cinder Third-Party CI: what next? (was Re: [cinder] Request exemption for removal of NetApp FC drivers (no voting CI))

On Mon, Mar 23, 2015 at 12:59 PM, Stefano Maffulli wrote: > On Mon, 2015-03-23 at 11:43 -0700, Mike Perez wrote: > > We've been talking about CI's for a year. We started talking about CI > deadlines > > in August. If you post a driver for Kilo, it was communicated that you're > > required to have

Re: [openstack-dev] [Oslo][TaskFlow] Proposal for new core reviewer (min pae)

+1 from me. -- dims On Mon, Mar 23, 2015 at 4:58 PM, Doug Hellmann wrote: > Excerpts from Joshua Harlow's message of 2015-03-23 10:40:09 -0700: >> Greetings all stackers, >> >> I propose that we add Min Pae[1] to the taskflow-core team[2]. >> >> Min has been actively contributing to taskflow for

Re: [openstack-dev] [nova][api] Microversions. And why do we need API extensions for new API functionality?

On 2015-03-23 15:15:18 -0400 (-0400), Jay Pipes wrote: [...] > I don't want it suppressed. I want the use of API extensions and the > extension framework(s) to be completely dropped for all future > API-affecting work. [...] Perhaps controversial, but would it be worthwhile to propose to the Defco

Re: [openstack-dev] Cinder Third-Party CI: what next?

On Mon, 2015-03-23 at 16:23 -0400, Anita Kuno wrote: > Some folks just will not respect other people's time. To pretend > otherwise is a huge dis-service to folks trying their hardest to > support those worthy of the support. This may be true in general but I have yet to be convinced that this is

Re: [openstack-dev] Cinder Third-Party CI: what next? (was Re: [cinder] Request exemption for removal of NetApp FC drivers (no voting CI))

On 03/23/2015 01:50 PM, Mike Perez wrote: On 12:59 Mon 23 Mar , Stefano Maffulli wrote: On Mon, 2015-03-23 at 11:43 -0700, Mike Perez wrote: We've been talking about CI's for a year. We started talking about CI deadlines in August. If you post a driver for Kilo, it was communicated that you

Re: [openstack-dev] [Oslo][TaskFlow] Proposal for new core reviewer (min pae)

Will do, And of course, the more reviews the better (and I'm grateful for those that have put in some time; in there busy day lives to make it possible). Keep it up as it's always appreciated :) -Josh Doug Hellmann wrote: Excerpts from Joshua Harlow's message of 2015-03-23 10:40:09 -0700:

Re: [openstack-dev] [Oslo][TaskFlow] Proposal for new core reviewer (min pae)

I’ll take that as a prod to step up on my review contributions, and definitely will be doing so ;-) Thank you for the vote of confidence, I’m glad to be helping with what I think will be an essential part of the underlying software infrastructure for Openstack services. On Mon, Mar 23, 2015 at 1:

Re: [openstack-dev] [oslo][cinder][nova][neutron] going forward to oslo-config-generator ...

Excerpts from Walter A. Boring IV's message of 2015-03-23 13:49:48 -0700: > Maybe we can leverage Cinder's use of the abc in the drivers.py now. > We could create an OptionsVD that drivers would add and implement. The > config generator could inspect objects looking for OptionsVD and then > c

Re: [openstack-dev] [Oslo][TaskFlow] Proposal for new core reviewer (min pae)

Excerpts from Joshua Harlow's message of 2015-03-23 10:40:09 -0700: > Greetings all stackers, > > I propose that we add Min Pae[1] to the taskflow-core team[2]. > > Min has been actively contributing to taskflow for a while now, both in > helping prove taskflow out (by being a user via the projec

[openstack-dev] [nova] proposing feature for Liberty, would this need a spec?

Hi, I'd like to propose (and implement) a feature for Liberty that would allow configuration of the pinning of the emulator when CPU pinning is enabled. (Currently the emulator is affined to the logical OR of all pCPUs used by the instance.) The general idea is to add an optional flavor extr

Re: [openstack-dev] Cinder Third-Party CI: what next? (was Re: [cinder] Request exemption for removal of NetApp FC drivers (no voting CI))

On 12:59 Mon 23 Mar , Stefano Maffulli wrote: > On Mon, 2015-03-23 at 11:43 -0700, Mike Perez wrote: > > We've been talking about CI's for a year. We started talking about CI > > deadlines > > in August. If you post a driver for Kilo, it was communicated that you're > > required to have a CI b

Re: [openstack-dev] [oslo][cinder][nova][neutron] going forward to oslo-config-generator ...

Maybe we can leverage Cinder's use of the abc in the drivers.py now. We could create an OptionsVD that drivers would add and implement. The config generator could inspect objects looking for OptionsVD and then call list_opts() on it. That way, driver maintainers don't also have to patch th

[openstack-dev] [oslo] stable-maint for oslo.vmware

Gary pinged me on IRC earlier today and I missed him, so I’m sending this to the list in case someone else wants to volunteer. It sounds like there are some stable branch changes for oslo.vmware that need attention. Does someone on the oslo.vmware team want to volunteer to be on a stable-mainte

Re: [openstack-dev] Cinder Third-Party CI: what next? (was Re: [cinder] Request exemption for removal of NetApp FC drivers (no voting CI))

On 03/23/2015 03:59 PM, Stefano Maffulli wrote: > On Mon, 2015-03-23 at 11:43 -0700, Mike Perez wrote: >> We've been talking about CI's for a year. We started talking about CI >> deadlines >> in August. If you post a driver for Kilo, it was communicated that you're >> required to have a CI by the

[openstack-dev] Cinder Third-Party CI: what next? (was Re: [cinder] Request exemption for removal of NetApp FC drivers (no voting CI))

On Mon, 2015-03-23 at 11:43 -0700, Mike Perez wrote: > We've been talking about CI's for a year. We started talking about CI > deadlines > in August. If you post a driver for Kilo, it was communicated that you're > required to have a CI by the end of Kilo [1][2][3][4][5][6][7][8]. This > should've

Re: [openstack-dev] [Neutron][IPv6] Prefix delegation and user facing API thoughts

Following discussion on IRC, a patch is now up to add this config option. Reviews appreciated. https://review.openstack.org/#/c/166973/ Cheers, John On 23/03/2015 18:11, "Carl Baldwin" wrote: >On Mon, Mar 23, 2015 at 12:04 PM, John Davidge (jodavidg) > wrote: >> The above blueprint outlin

Re: [openstack-dev] [glance] Applying patch in bug #1414725 while string freeze in place

Please direct this query to documentation and i18n lists [1, 2, 3] and include the response (if any) as a comment on the review so that the core reviewers are aware. Thanks for bringing this up and helping in contributing to the project! [1] http://lists.openstack.org/cgi-bin/mailman/listinfo/o

Re: [openstack-dev] [nova][api] Microversions. And why do we need API extensions for new API functionality?

On Tue, Mar 10, 2015 at 09:52:14PM +1030, Christopher Yeoh wrote: > On Mon, 09 Mar 2015 16:14:21 -0400 > Sean Dague wrote: > > > On 03/09/2015 03:37 PM, Jay Pipes wrote: > > > On 03/08/2015 08:10 AM, Alex Xu wrote: > > >> Thanks for Jay point this out! If we have agreement on this and > > >> docu

Re: [openstack-dev] [nova][api] Microversions. And why do we need API extensions for new API functionality?

Sorry for the delay in responding all. Comments inline. On Mon, Mar 09, 2015 at 03:04:59PM -0700, melanie witt wrote: > On Mar 9, 2015, at 13:14, Sean Dague wrote: > > So possibly another way to think about this is our prior signaling of > > what was supported by Nova was signaled by the extensio

Re: [openstack-dev] [cinder] Request exemption for removal of NetApp FC drivers (no voting CI)

On 17:23 Mon 23 Mar , ClaytonLuce, Timothy wrote: > I disagree with your assertion that NetApp has ignored this for a year and we > are being inconsiderate of the community. The specific drivers (FC) we are > discussing were added in the Kilo-1 period, so since Dec. and are net new > drivers.

[openstack-dev] [Ironic] Weekly subteam status report

Hi, Following is the subteam report for Ironic. Note that this is pulled from the weekly meeting we just had. (Normally it comes from the Ironic whiteboard[0], but the whiteboard seems to have been whitened out.) Testing (adam_g) == working on testing the API microversioning within t

Re: [openstack-dev] [api][neutron] Best API for generating subnets from pool

On Mon, Mar 23, 2015 at 8:52 AM, John Belamaric wrote: > > On 3/21/15, 9:10 AM, "Salvatore Orlando" wrote: > > If we feel a need for specifying the relative position of gateway address > and allocation pools when creating a subnet from a pool which will pick a > CIDR from its prefixes, then the i

Re: [openstack-dev] [Fuel] [UI] New design + Bootstrap 3

There is no reason, just a markup demo. Added a sample deployment failure message to the nodes page. As for settings or networks page, they should look pretty much the same and most likely we won't create a markup demo for these pages as they are mostly built from standard controls. 2015-03-23 21:

[openstack-dev] [Neutron][IPv6] Tomorrow's IPv6 subteam meeting

Hi, My apologies for the short notice, but I will not be able to run the IPv6 subteam meeting tomorrow. If one of the attendees who has items to discuss would like to run the meeting in my absence, that would be great! -- Sean M. Collins

Re: [openstack-dev] [nova][pci-passthrough] Error: An object of type PciDevicePoolList is required here

Jay, Thanks for the response. Here is the bug https://bugs.launchpad.net/nova/+bug/1435483 -Original Message- From: Jay Pipes [mailto:jaypi...@gmail.com] Sent: Monday, March 23, 2015 5:46 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [no

Re: [openstack-dev] [api][neutron] Best API for generating subnets from pool

An integer index doesn't do it for me. Maybe I'm the only one. It is part of an IP address. It isn't a new concept to think about the network and host parts of an IP address separately. Why would we change the notation from dotted quad (ipv4) to integer just because we mask out the network part

[openstack-dev] [Infra] Meeting Tuesday March 24th at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday March 24th, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is welcome to to add agenda items) Everyone interest

Re: [openstack-dev] [Neutron] IPAM reference driver status and other stuff

On Mon, Mar 23, 2015 at 9:03 AM, Salvatore Orlando wrote: >> Actually, I don't see this as a big deal or a failure. In fact, it may be >> quite common and useful for a given driver to store some state in its own >> tables (like the reference driver is doing). The primary goal is to enable >> alter

Re: [openstack-dev] [Neutron][IPv6] Prefix delegation and user facing API thoughts

On Mon, Mar 23, 2015 at 12:04 PM, John Davidge (jodavidg) wrote: > The above blueprint outlines an admin-configurable global default pool to > be used in the case of a user calling subnet-create without specifying a > CIDR or subnet-pool ID. If the OpenStack environment has been made > PD-capable

Re: [openstack-dev] [Neutron][IPv6] Prefix delegation and user facing API thoughts

On Wed, Mar 18, 2015 at 8:15 AM, Sean M. Collins wrote: > On Wed, Mar 18, 2015 at 06:45:59AM PDT, John Davidge (jodavidg) wrote: >> In the IPv6 meeting yesterday you mentioned doing this >> with an extension rather than modifying the core API. Could you go into >> some detail about how you see thi

Re: [openstack-dev] [Neutron][IPv6] Prefix delegation and user facing API thoughts

Going forward, I think the best approach for PD would be to align with the subnet-pools being added by the subnet allocation BP work (thanks to Sean for bringing this to our attention again). http://specs.openstack.org/openstack/neutron-specs/specs/kilo/subnet-alloca tion.html#rest-api-impact Th

Re: [openstack-dev] [Fuel] [UI] New design + Bootstrap 3

Looks good, a couple of things: Is there a reason that the nodes near to top didn't render in the role group? Can you render a message like deployment failure, or deployment success? Can you render the networks or settings page? On Mon, Mar 23, 2015 at 10:36 AM, Vitaly Kramskikh wrote: > Hi, > >

Re: [openstack-dev] [Oslo][TaskFlow] Proposal for new core reviewer (min pae)

+1 Congrats Min! On Mon, Mar 23, 2015 at 10:40 AM, Joshua Harlow wrote: > Greetings all stackers, > > I propose that we add Min Pae[1] to the taskflow-core team[2]. > > Min has been actively contributing to taskflow for a while now, both in > helping prove taskflow out (by being a user via the

Re: [openstack-dev] [qa][neutron] Moving network api test development to Neutron repo

On Tue, Mar 17, 2015 at 10:22:50PM +0100, Salvatore Orlando wrote: > With the API tests being now available in the neutron repository - and > being actively developed, I would also mandate in reviews that API tests > are provided in lieu of the usual unit tests which at the end of the day do > what

[openstack-dev] [Oslo][TaskFlow] Proposal for new core reviewer (min pae)

Greetings all stackers, I propose that we add Min Pae[1] to the taskflow-core team[2]. Min has been actively contributing to taskflow for a while now, both in helping prove taskflow out (by being a user via the project that he is using it in @ https://wiki.openstack.org/wiki/Cue) and helping wit

Re: [openstack-dev] [Neutron][IPAM] Uniqueness of subnets within a tenant

On Mon, Mar 23, 2015 at 9:52 AM, Salvatore Orlando wrote: > I think the goal of subnet pools is to use these environments as "units of > isolations" and ensure no overlapping CIDRs there. However, since there is > no way to identify such environments at the API layers, API clients will > need to b

[openstack-dev] [Fuel] [UI] New design + Bootstrap 3

Hi, We're working on migrating Fuel UI from Bootstrap 2 to Bootstrap 3 and changing the design. It's mostly upgrade of styles and markup, but we also plan to implement some changes which are frequently requested (like making action buttons always available on top of the page). Here is markup for 3

Re: [openstack-dev] [cinder] Request exemption for removal of NetApp FC drivers (no voting CI)

I disagree with your assertion that NetApp has ignored this for a year and we are being inconsiderate of the community. The specific drivers (FC) we are discussing were added in the Kilo-1 period, so since Dec. and are net new drivers. All other NetApp drivers have had corresponding CI in plac

[openstack-dev] [Neutron][IPAM] Address Scopes (was: Uniqueness of subnets within a tenant)

On Mon, Mar 23, 2015 at 8:56 AM, John Belamaric wrote: > > > On 3/22/15, 8:05 PM, "Ian Wells" wrote: > > > Seems to me that an address pool corresponds to a network area that you can > route across (because routing only works over a network with unique > addresses and that's what an address pool

Re: [openstack-dev] [magnum] swagger-codegen generated code for python-k8sclient

On Mar 23, 2015, at 9:05 AM, Steven Dake (stdake) mailto:std...@cisco.com>> wrote: From: Hongbin Lu mailto:hongbin...@gmail.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Monday, March 23, 2015 at 8:37 AM To: "Op

[openstack-dev] [glance] Applying patch in bug #1414725 while string freeze in place

Hello, I have submitted a patch to address the bug(https://bugs.launchpad.net/glance/+bug/1414725). This patch updates glance-manage documentation. Currently the documentation misses details on handling the glance-manage metadata definitions. I have submitted https://review.openstack.org/#/c

Re: [openstack-dev] [cinder] Request exemption for removal of NetApp FC drivers (no voting CI)

On 13:15 Mon 23 Mar , ClaytonLuce, Timothy wrote: > Mike, > > Did not see a response to this request. Please respond, we can discuss in > the Cinder Core meeting this week. Which request? I already responded to your message: http://lists.openstack.org/pipermail/openstack-dev/2015-March/059

Re: [openstack-dev] [all] Do we need release announcements for all the things?

On Mon, Mar 23, 2015 at 9:47 AM, Thierry Carrez wrote: > One area where we could work to remove noise would be to move new core > reviewers nomination/suggestion threads out of the ML. They are mostly > useless IMHO (only +1s), and PTLs are empowered to make the call anyway. > > That's one area w

Re: [openstack-dev] [neutron][lbaas] canceling meeting

Hi all, Lbaas meetings are canceled until further notice, including tomorrow morning. Thanks, doug On Fri, Mar 20, 2015 at 9:45 AM, Brandon Logan wrote: > That is correct. > > On Fri, 2015-03-20 at 15:11 +, Vijay Venkatachalam wrote: > > > > > > +1 For on demand meeting. > > > > > > On de

Re: [openstack-dev] [neutron][lbaas] Invalid import in tempest v2 api tests

Hi Vijay, That works because we pin the version of tempest that we run against, via tox. If you're using devstack-gate in your CI, note the two hooks found here: https://github.com/openstack/neutron-lbaas/blob/master/neutron_lbaas/tests/contrib/ If not, you need to mimic the behavior of the pos

Re: [openstack-dev] [all] Do we need release announcements for all the things?

Excerpts from Russell Bryant's message of 2015-03-23 07:51:43 -0700: > On 03/23/2015 10:47 AM, Thierry Carrez wrote: > > Kuvaja, Erno wrote: > >> [...] > >> This is one of the benefits/caveats of having a single dev mailing list. > >> There is lots of noise for everyone, but this particular noise

Re: [openstack-dev] [glance] reminder to check 'Author' of patch set when reviewing

On 2015-03-23 15:52:35 + (+), stuart.mcla...@hp.com wrote: > A quick reminder for Glance cores to check if the 'Author' changes > between patch sets. [...] Also a quick reminder to all devs. If you stick to git commands for manipulating commits then it should be _very_hard_ to accidentally

Re: [openstack-dev] [magnum] swagger-codegen generated code for python-k8sclient

From: Hongbin Lu mailto:hongbin...@gmail.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Monday, March 23, 2015 at 8:37 AM To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@list

Re: [openstack-dev] [Sahara] Is it possible to do "instance scale" for a node in a living cluster ?

Hi Chen, >1. resize the master node. Using command like “nova resize”, to add more cpu & memory and other resources for this single instance. Instance reside is not supported on Sahara level. But you can always do that on nova level. Sahara doesn't use any specific information about flavor (

[openstack-dev] [glance] reminder to check 'Author' of patch set when reviewing

A quick reminder for Glance cores to check if the 'Author' changes between patch sets. When someone other than the original submitter uploads a new patch set they should, if appropriate, add themselves as a co-author rather than replace the original patch author. (It's the 'Author' rather than th

Re: [openstack-dev] [Neutron][IPAM] Uniqueness of subnets within a tenant

I think that moving the discussion in whether a pool represents a tenant's routable address space, or whether we need a new (another?!) API entity do deal with it probably does not really fall within the scope of this thread. I am pretty sure Carl will soon push a specification for address scope ma

Re: [openstack-dev] [nova][pci-passthrough] Error: An object of type PciDevicePoolList is required here

On Sun, Mar 22, 2015 at 04:58:00PM +, Moshe Levi wrote: > Hi, > > In the latest master nova code I am keep getting this error "An object of > type PciDevicePoolList is required here" > > My nova.conf contains pci_passthrough_whitelist. > > When I tried to launch vm after devstack installa

Re: [openstack-dev] [Neutron][IPAM] Uniqueness of subnets within a tenant

On Sun, Mar 22, 2015 at 05:05:17PM -0700, Ian Wells wrote: > On 22 March 2015 at 07:48, Jay Pipes wrote: > > > On 03/20/2015 05:16 PM, Kevin Benton wrote: > > > >> To clarify a bit, we obviously divide lots of things by tenant (quotas, > >> network listing, etc). The difference is that we have no

Re: [openstack-dev] [magnum] swagger-codegen generated code for python-k8sclient

Hi Madhuri, Amazing work! I wouldn't concern the code duplication and modularity issue since the codes are generated. However, there is another concern here: if we find a bug/improvement of the generated code, we probably need to modify the generator. The question is if the upstream will accept th

Re: [openstack-dev] [Neutron][IPv6] Prefix delegation and user facing API thoughts

On 3/18/15, 9:12 PM, "Sean M. Collins" wrote: > My hope is that either the new IPAM subsystem for subnet allocations >would provide this, or that a small API extension could "paper over" some >of the sharper edges. In IPAM we have added this concept of a subnet request. The built-in support w

Re: [openstack-dev] [nova] Updating 'scheduled_at' field of nova instances in the database.

On Mon, Mar 23, 2015 at 11:18:28AM +0530, Deepthi Dharwar wrote: > All the VM information is stored in the instances table. > This includes all the time related field like scheduled_at, launched_at etc. > > After upgrading to Juno, I have noticed that my 'scheduled_at' field > is not getting refl

Re: [openstack-dev] [Neutron] IPAM reference driver status and other stuff

On 3/23/15, 11:03 AM, "Salvatore Orlando" mailto:sorla...@nicira.com>> wrote: Whether is a big deal or a failure it depends on one's expectation. If the expectation is to enable external IPAM backends, then I agree that this is not a big deal. However, my expectation (and I hope I'm not the o

Re: [openstack-dev] [Neutron] IPAM reference driver status and other stuff

Comments inline. Salvatore On 23 March 2015 at 15:41, John Belamaric wrote: > > > On 3/20/15, 8:31 PM, "Salvatore Orlando" wrote: > > > As the IPAM driver is called in NeutronDbPluginV2, this call happens > while another transaction is typically in progress. Initiating a separate > session

Re: [openstack-dev] [Neutron][IPAM] Uniqueness of subnets within a tenant

On 3/22/15, 8:05 PM, "Ian Wells" mailto:ijw.ubu...@cack.org.uk>> wrote: Seems to me that an address pool corresponds to a network area that you can route across (because routing only works over a network with unique addresses and that's what an address pool does for you). We have those areas

Re: [openstack-dev] [api][neutron] Best API for generating subnets from pool

On 3/21/15, 9:10 AM, "Salvatore Orlando" mailto:sorla...@nicira.com>> wrote: If we feel a need for specifying the relative position of gateway address and allocation pools when creating a subnet from a pool which will pick a CIDR from its prefixes, then the integer value solution is probably m

Re: [openstack-dev] [all] Do we need release announcements for all the things?

On 03/23/2015 10:47 AM, Thierry Carrez wrote: > Kuvaja, Erno wrote: >> [...] >> This is one of the benefits/caveats of having a single dev mailing list. >> There is lots of noise for everyone, but this particular noise is one of >> those I think we should not get rid of. > > One area where we co

Re: [openstack-dev] [all] Do we need release announcements for all the things?

Kuvaja, Erno wrote: > [...] > This is one of the benefits/caveats of having a single dev mailing list. > There is lots of noise for everyone, but this particular noise is one of > those I think we should not get rid of. One area where we could work to remove noise would be to move new core revie

Re: [openstack-dev] [Neutron] IPAM reference driver status and other stuff

On 3/20/15, 8:31 PM, "Salvatore Orlando" mailto:sorla...@nicira.com>> wrote: As the IPAM driver is called in NeutronDbPluginV2, this call happens while another transaction is typically in progress. Initiating a separate session within the IPAM driver causes the outer transaction to fail. I d

Re: [openstack-dev] [cinder] Third Party CI

All vendors working on cinder third party ci are encouraged to attend the 3rd party ci meetings. https://wiki.openstack.org/wiki/Meetings/ThirdParty This is a great place to ask questions, report issues, and share solutions. Ramy _

Re: [openstack-dev] [nova] how to handle vendor-specific API microversions?

On 03/21/2015 12:12 PM, Joe Gordon wrote: On Sat, Mar 21, 2015 at 8:31 AM, Monty Taylor mailto:mord...@inaugust.com>> wrote: On 03/21/2015 01:21 AM, Chris Friesen wrote: > Hi, > > I've recently been playing around a bit with API microversions and I > noticed something that

Re: [openstack-dev] Multi Region Designate

Yes this sounds interesting too. In fact the geo diverse failover mentioned in the “copper” proposal can easily be considered as an extension global DNS namespace that I am talking about.  Lets see if we get any response from openstack-dev mailer. Regards,Anik From: joehuang To: Anik ; Op

Re: [openstack-dev] [magnum] swagger-codegen generated code for python-k8sclient

From: Madhuri Rai mailto:madhuri.ra...@gmail.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Monday, March 23, 2015 at 1:53 AM To: "openstack-dev@lists.openstack.org" mailt

Re: [openstack-dev] [glance][pbr][requirements] Broken requirements?

On 03/23/2015 02:12 PM, Doug Hellmann wrote: Excerpts from Andreas Jaeger's message of 2015-03-23 13:16:05 +0100: The translation jobs [1] are failing since a requirements job merged [2] with: error in setup command: 'install_requires' must be a string or list of strings containing valid p

Re: [openstack-dev] [nova] Revert "objects: introduce numa topology limits objects"

> I am really sorry it got in as I have -1ed it several times for the same > reason (I _really_ hate using the -2 hammer - we're all adults here > after all). I guess that I should take some blame as a reviewer on that patch, but only after this mail do I read some of your comments as fundamentall

Re: [openstack-dev] [cinder] Request exemption for removal of NetApp FC drivers (no voting CI)

I request the same consideration for Huawei 18000 iSCSI driver and 18000 FC driver. May I also add it to the meeting agenda? · I promise Huawei Volume CI will become stable and reporting stably before March 31. Our CI will be moved to a more better environment tomorrow or the day after

  1   2   >