[openstack-dev] [Neutron] Ryu/ofagent CI outage

hi, Ryu/ofagent CI will be offline during the next weekend for a scheduled maintenance. sorry for inconvenience. YAMAMOTO Takashi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-re

Re: [openstack-dev] [Neutron] Ryu/ofagent CI outage

Hi- Regarding the CI offline mails, I previously received an email from Anita. Please find the summary below. Please set your account listing to down on this page: https://wiki.openstack.org/wiki/ThirdPartySystems Following these instructions: If your system is going down or having problems,

[openstack-dev] Mellanox request for permission for Nova CI

Hi , I would like to ask for a CI permission to start commenting on Nova branch. Mellanox is engaged in pci pass-through features for quite some time now. We have an operating Neutron CI for ~2 years, and since the pci pass-through features are part of Nova as well, we would like to start monitor

[openstack-dev] [nova] will instance action deprecate in feature

Hi all will instance action deprecate in feature since we have notify mechanism now? Currently, nova have instance action and instance event action to record specify actions performed on a instances. For some enterprise user, they may need to compute the latency when they perform an action on an

Re: [openstack-dev] [horizon] Do No Evil

On 09/03/15 15:54, Doug Hellmann wrote: > > > Not everyone realizes that many of the distros run our tests against the > packages they build, too. So our tool choices trickle downstream beyond > our machines and our CI environment. In this case, because the tool is a > linter, it seems like the

[openstack-dev] [nova][heat] Autoscaling parameters blueprint

Hey, Can someone please share the current status of the "Autoscaling signals to allow parameter passing for UserData" blueprint - https://blueprints.launchpad.net/heat/+spec/autoscaling-parameters. We have a very concrete use case that require passing parameters on scale out. What is the best

[openstack-dev] [GBP] PTL elections

Hello OpenStackers! To meet the requirement of an officially elected PTL, we're running elections for the Group Based Policy (GBP) PTL for Kilo and Liberty cycles. Schedule and policies are fully aligned with official OpenStack PTLs elections. You can find more information in the official

Re: [openstack-dev] [Magnum][Heat] Expression of Bay Status

2015-03-10 23:21 GMT+08:00 Hongbin Lu : > Hi Adrian, > > On Mon, Mar 9, 2015 at 6:53 PM, Adrian Otto > wrote: > >> Magnum Team, >> >> In the following review, we have the start of a discussion about how to >> tackle bay status: >> >> https://review.openstack.org/159546 >> >> I think a key issue h

Re: [openstack-dev] [nova][heat] Autoscaling parameters blueprint

On Wed, Mar 11, 2015 at 7:01 PM, ELISHA, Moshe (Moshe) < [email protected]> wrote: > Hey, > > > > Can someone please share the current status of the “Autoscaling signals to > allow parameter passing for UserData” blueprint - > https://blueprints.launchpad.net/heat/+spec/autoscaling-

Re: [openstack-dev] [nova][heat] Autoscaling parameters blueprint

On Wed, Mar 11, 2015 at 09:01:04AM +, ELISHA, Moshe (Moshe) wrote: >Hey, > > > >Can someone please share the current status of the "Autoscaling signals to >allow parameter passing for UserData" blueprint - > https://blueprints.launchpad.net/heat/+spec/autoscaling-paramete

Re: [openstack-dev] [Openstack-operators] [all][qa][gabbi][rally][tempest] Extend "rally verfiy" to unify work with Gabbi, Tempest and all in-tree functional tests

The idea is great, but IMHO we can move all project-specific code out of rally, so: * rally plugin should be a part of project (for example, located in functional tests directory) * use {project url} instead of {project name} in rally verify command, example: $ rally verify https://gi

Re: [openstack-dev] [neutron] VXLAN with single-NIC compute nodes: Avoiding the MTU pitfalls

OK, I looked at the devstack patch [6] "Configure mtu for ovs with the common protocols" but no -- it doesn't do the job for the VLAN-based separation of native and encapsulated traffic, which I'm using in [1] for a clean (correct MTUs ...) VXLAN setup with single-NIC compute nodes. As shown

[openstack-dev] [stable] Icehouse 2014.1.4 freeze exceptions

Hi, next Icehouse stable point release 2014.1.4 has been slipping last few weeks due to various gate issues, see "Recently closed" section in https://etherpad.openstack.org/p/stable-tracker for details. Branch looks good enough now to push the release tomorrow (Thursdays are traditional release da

Re: [openstack-dev] [neutron] VXLAN with single-NIC compute nodes: Avoiding the MTU pitfalls

[resent with a clarification of what [6] is doing towards EoM] OK, I looked at the devstack patch [6] "Configure mtu for ovs with the common protocols" but no -- it doesn't do the job for the VLAN-based separation of native and encapsulated traffic, which I'm using in [1] for a clean (corre

Re: [openstack-dev] Driver documentation for Kilo [cinder] [neutron] [nova] [trove]

Ok, thanks Anne! On Tue, Mar 10, 2015 at 6:10 PM, Anne Gentle wrote: > > > On Tue, Mar 10, 2015 at 3:35 PM, Erlon Cruz wrote: > >> Hi Anne, >> >> Thanks for the quick answer. One thing that still not clear for me is >> about the documentation that is currently there. Will it be removed >> (conv

Re: [openstack-dev] [stable] Icehouse 2014.1.4 freeze exceptions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/11/2015 12:21 PM, Alan Pevec wrote: > Hi, > > next Icehouse stable point release 2014.1.4 has been slipping last > few weeks due to various gate issues, see "Recently closed" section > in https://etherpad.openstack.org/p/stable-tracker for detai

[openstack-dev] [stable] Freeze exception for "Correct initialization order for logging to use eventlet locks"

Hello, I would like to get a freeze exception for patch "Correct initialization order for logging to use eventlet locks", [0]. https://review.openstack.org/#/c/163387/ The bug fixed by the changeset is known to affect Keystone deployed with eventlet. I am aware of a customer who hit this bug i

Re: [openstack-dev] [stable] Freeze exception for "Correct initialization order for logging to use eventlet locks"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/11/2015 12:51 PM, Boris Bobrov wrote: > Hello, > > I would like to get a freeze exception for patch "Correct > initialization order for logging to use eventlet locks", [0]. > > https://review.openstack.org/#/c/163387/ > > The bug fixed by the

[openstack-dev] [nova] Kilo FeatureFreeze is March 19th, FeatureProposalFreeze has happened

Hi, Just a quick update on where we are at with the release: https://wiki.openstack.org/wiki/Kilo_Release_Schedule Please help review all the code we want to merge before FeatureFreeze: https://etherpad.openstack.org/p/kilo-nova-priorities-tracking https://launchpad.net/nova/+milestone/kilo-3 Pl

Re: [openstack-dev] [Fuel] Recent issues with our review workflow

I'll keep it in mind not to create unnecessary backports, although I really find it more convenient to do them once I submit changes to master for review. I apologize for [4], it indeed was wrong and it won't happen again. Regards, Bartłomiej On Wed, Mar 11, 2015 at 12:36 AM, Ryan Moe wrote: >

Re: [openstack-dev] [nova] Kilo FeatureFreeze is March 19th, FeatureProposalFreeze has happened

Hi, Not 100% sure that I understand. This is for the BP¹s and specs that were approved for Kilo. Bug fixes if I understand are going to be reviewed until the release of Kilo. Is launchpad not a sufficient source for highlighting bugs? Thanks Gary On 3/11/15, 2:13 PM, "John Garbutt" wrote: >Hi, >

[openstack-dev] [sahara] team meeting Mar 12 1400 UTC

Hi sahara folks, We'll be having the Sahara team meeting tomorrow at #openstack-meeting-3 channel. Agenda: https://wiki.openstack.org/wiki/Meetings/SaharaAgenda#Next_meetings http://www.timeanddate.com/worldclock/fixedtime.html?msg=Sahara+Meeting&iso=20150312T14 P.S. I'll be unavailable at this

Re: [openstack-dev] [all] Testtools 1.7.0 may error if you installed it before reading this email

> So, we can work around this in devstack, but it seems like there is a > more fundamental bug here that setup project isn't following dependencies. Dep chain was: testtools (from zake>=0.1->tooz<=0.12,>=0.3->ceilometer==2014.2.3.dev2) Unneeded _runtime_ dependency on testtools was removed in http

Re: [openstack-dev] [sahara] team meeting Mar 12 1400 UTC

Correction, Michael McCune (elmiko) will chair the meeting. On Wed, Mar 11, 2015 at 3:57 PM, Sergey Lukjanov wrote: > Hi sahara folks, > > We'll be having the Sahara team meeting tomorrow at #openstack-meeting-3 > channel. > > Agenda: > https://wiki.openstack.org/wiki/Meetings/SaharaAgenda#Next_

Re: [openstack-dev] [oslo.messaging] extending notification MessagingDriver

Regarding bug 1426046 (see below) -- Is this just a matter of making the classes "public" or are you thinking the driver interface needs more thought + solidifying before making something extendable? Perhaps I can donate a cycle to 2 to help get this in. > On 2/26/15 10:33 AM, Doug Hellmann wrote

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

On 3/11/2015 7:59 AM, Sean Dague wrote: The last couple of days I was at the Operators Meetup acting as Nova rep for the meeting. All the sessions were quite nicely recorded to etherpads here - https://etherpad.openstack.org/p/PHL-ops-meetup There was both a specific Nova session - https://eth

[openstack-dev] Fwd: PCI passthrough of 40G ethernet interface

-- Forwarded message -- From: jacob jacob Date: Tue, Mar 10, 2015 at 6:00 PM Subject: PCI passthrough of 40G ethernet interface To: [email protected] Hi, I'm interested in finding out if anyone has successfully tested PCI passthrough functionality for 40G interfaces

Re: [openstack-dev] [Glance] Proposal to change Glance meeting time.

I have no opinions on the matter. Either 1400 or 1500 work for me. I think there are a lot of people asking for it to be at 1500 instead though. Would anyone object to changing it to 1500 instead (as long as it is one consistent time for the meeting)? On 3/11/15, 01:53, "Inessa Vasilevskaya" wrot

Re: [openstack-dev] Avoiding regression in project governance

On 2015-03-10 23:00:16 + (+), Devananda van der Veen wrote: > Many of those requirements were subjective (well tested, well > documented, etc) and had to be evaluated by the TC. Are these the > sort of tags you're referring to? If so, and if the TC delegated > responsibility to manage the a

Re: [openstack-dev] [Glance] Proposal to change Glance meeting time.

On Wed, Mar 11, 2015 at 02:25:26PM +, Ian Cordasco wrote: > I have no opinions on the matter. Either 1400 or 1500 work for me. I think > there are a lot of people asking for it to be at 1500 instead though. > Would anyone object to changing it to 1500 instead (as long as it is one > consistent

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

On Wed, 11 Mar 2015, Matt Riedemann wrote: Thanks for writing this up. Etherpads are usually a mess for those not involved in creating them so it's always useful to have some summary and digestion after the fact. +trillion for summaries. Going to look at an etherpad is pretty much useless pre

Re: [openstack-dev] [all] Testtools 1.7.0 may error if you installed it before reading this email

On Wed, 11 Mar 2015, Alan Pevec wrote: So, we can work around this in devstack, but it seems like there is a more fundamental bug here that setup project isn't following dependencies. Dep chain was: testtools (from zake>=0.1->tooz<=0.12,>=0.3->ceilometer==2014.2.3.dev2) Unneeded _runtime_ depe

[openstack-dev] [cinder] K3 Feature Freeze Exception request for bp/nfs-backup

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I hereby solicit a feature freeze exception for the NFS backup review [1]. Although only about 140 lines of non-test code, this review completes the implementation of the NFS backup blueprint [2]. Most of the actual work for this blueprint was a refa

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

On Wed, Mar 11, 2015, at 05:59 AM, Sean Dague wrote: > Galera Upstream Testing > --- > > The majority of deploys run with Galera MySQL. There was a question > about whether or not we could get that into upstream testing pipeline > as that's the common case. > It should be poss

Re: [openstack-dev] [devstack] pip wheel' requires the 'wheel' package

I don’t have any solution just chiming in that I see the same error with devstack pulled from master on a new ubuntu trusty VM created last night. 'pip install —upgrade wheel’ indicates: Requirement already up-to-date: wheel in /usr/local/lib/python2.7/dist-packages Haven’t gotten it cleared up.

Re: [openstack-dev] [Fuel] Recent issues with our review workflow

It's really fine to create backports, even of other people's commits, as long as you don't do it too early (and thus make it possible to forget to update backports in line with newer patch sets of the master commit and land inconsistent implementations to different release series) and don't mangle

[openstack-dev] [nova] need input on possible API change for bug #1420848

Hi, I'm working on bug #1420848 which addresses the issue that doing a "service-disable" followed by a "service-enable" against a "down" compute node will result in the compute node going "up" for a while, possibly causing delays to operations that try to schedule on that compute node. The

Re: [openstack-dev] [nova] need input on possible API change for bug #1420848

I would think a on v2 extension is needed for v2.1 , mircoversion is a way but not very sure it's needed. Best Regards! Kevin (Chen) Ji 纪 晨 Engineer, zVM Development, CSTL Notes: Chen CH Ji/China/IBM@IBMCN Internet: [email protected] Phone: +86-10-82454158 Address: 3/F Ring Building, ZhongGu

Re: [openstack-dev] [nova] Shared storage support

On 03/02/2015 06:24 PM, Jay Pipes wrote: On 02/25/2015 06:41 AM, Daniel P. Berrange wrote: On Wed, Feb 25, 2015 at 02:08:32PM +, Gary Kotton wrote: I understand that this is a high or critical bug but I think that we need to discuss more on it and try have a more robust model. What I'm no

Re: [openstack-dev] [Openstack-operators] [all][qa][gabbi][rally][tempest] Extend "rally verfiy" to unify work with Gabbi, Tempest and all in-tree functional tests

> $ rally verify https://github.com/openstack/nova start As one of end-users of Rally, I dislike such construction, because I don't want to remember links to repos, they are too long for me:) On Wed, Mar 11, 2015 at 12:49 PM, Aleksandr Maretskiy < [email protected]> wrote: > The idea is gr

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

Here is a compromise option. The pluggable IPAM will be optionally enabled in Kilo. We could introduce the restriction, but only when pluggable IPAM is enabled. Support for having a tenant with overlapping IP space, along with pluggable IPAM would wait until Liberty, when we can fully implement the

Re: [openstack-dev] [cinder] K3 Feature Freeze Exception request for bp/nfs-backup

All, I will sponsor this. Patch just needs to be rebased. Jay On 03/11/2015 10:20 AM, Tom Barron wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I hereby solicit a feature freeze exception for the NFS backup review [1]. Although only about 140 lines of non-test code, this review comple

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

Thanks Sean for writing up this report, greatly appreciated. Comments inline. Le 11/03/2015 13:59, Sean Dague a écrit : The last couple of days I was at the Operators Meetup acting as Nova rep for the meeting. All the sessions were quite nicely recorded to etherpads here - https://etherpad.opens

Re: [openstack-dev] [all] Testtools 1.7.0 may error if you installed it before reading this email

I think part of the problem is that we’re still relying on distribution packaged dependencies. If you look earlier in the logs for: http://logs.openstack.org/51/146651/15/check/check-grenade-dsvm/2485c9e/log s/grenade.sh.txt.gz#_2015-03-11_00_58_45_129 you’ll see that “python-unittest2” is being in

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

On 3/12/15, 12:46 AM, "Carl Baldwin" wrote: >When talking with external IPAM to get a subnet, Neutron will pass >both the cidr as the primary identifier and the subnet_id as an >alternate identifier. External systems that do not allow overlap can > Recall that IPAM driver instances are associa

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

> -Original Message- > From: Sylvain Bauza [mailto:[email protected]] > Sent: 11 March 2015 17:53 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [nova] readout from Philly Operators Meetup > > Thanks Sean for writing up this report, greatl

Re: [openstack-dev] [cinder] K3 Feature Freeze Exception request for bp/nfs-backup

Discussed in the weekly meeting, plenty of sponsors, agreed to try to get it through today On 11 March 2015 at 18:48, Jay S. Bryant wrote: > All, > > I will sponsor this. > > Patch just needs to be rebased. > > Jay > > > On 03/11/2015 10:20 AM, Tom Barron wrote: > >> -BEGIN PGP SIGNED MESSAG

[openstack-dev] [Keystone] keystonemiddleware 1.5.0 released

The Keystone development community would like to announce the release of keystonemiddleware 1.5.0. This release can be installed from the following locations:  * http://tarballs.openstack.org/keystonemiddleware  * https://pypi.python.org/pypi/keystonemiddleware  Detailed changes in this release:

Re: [openstack-dev] Mellanox request for permission for Nova CI

On Wed, Mar 11, 2015 at 12:49 AM, Nurit Vilosny wrote: > Hi , > > I would like to ask for a CI permission to start commenting on Nova branch. > > Mellanox is engaged in pci pass-through features for quite some time now. > > We have an operating Neutron CI for ~2 years, and since the pci > pass-

Re: [openstack-dev] [swift] auth migration and user data migration

On Mon, Mar 9, 2015 at 12:27 PM, Weidong Shao wrote: > > I noticed swauth project is not actively maintained. In my local testing, > swauth did not work after I upgraded swift to latest. > > Hrm... I think gholt would be open to patches/support, I know of a number of deployers of Swauth - so mayb

Re: [openstack-dev] Avoiding regression in project governance

On Tue, 2015-03-10 at 15:23 -0700, James E. Blair wrote: > The holy grail of this system would be the "suitable for production > deployment" tag, but no one has figured out how to define it yet. Are crazy ideas welcome in this phase? I start with 2 below: Preface: an idea circulates about visua

Re: [openstack-dev] [neutron] Proposal to add Ihar Hrachyshka as a Neutron Core Reviewer

On Wed, Mar 4, 2015 at 1:42 PM, Kyle Mestery wrote: > I'd like to propose that we add Ihar Hrachyshka to the Neutron core > reviewer team. Ihar has been doing a great job reviewing in Neutron as > evidence by his stats [1]. Ihar is the Oslo liaison for Neutron, he's been > doing a great job keepi

[openstack-dev] [nova][neutron][nfv] is there any reason neutron.allow_duplicate_networks should not be True by default?

While looking at some other problems yesterday [1][2] I stumbled across this feature change in Juno [3] which adds a config option "allow_duplicate_networks" to the [neutron] group in nova. The default value is False, but according to the spec [4] neutron allows this and it's just exposing a fe

Re: [openstack-dev] [cinder] cinder is broken until someone fixes the forking code

I've also got the following up: https://review.openstack.org/#/c/162781/ Which tries the force file descriptors to be closed; although I'm unsure where the tempest results went (and am rechecking that); maybe it breaks so badly that tempest doesn't even run? -Josh Mike Bayer wrote: Hello C

Re: [openstack-dev] new failures running Barbican functional tests

On Tue, Mar 10, 2015, at 05:50 PM, Douglas Mendizabal wrote: > Thanks for the insight, other Doug. :) It appears that this is in part > due to the fact that Tempest has not yet updated to oslo_log and is still > using incubator oslo.log. Can someone from the Tempest team chime in on > what the

Re: [openstack-dev] [neutron] Proposal to add Ihar Hrachyshka as a Neutron Core Reviewer

Congratulations Ihar! Edgar From: Kyle Mestery mailto:[email protected]>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:[email protected]>> Date: Wednesday, March 11, 2015 at 1:54 PM To: "OpenStack Development Mailing List (not for usage questi

Re: [openstack-dev] Avoiding regression in project governance

On Tue, Mar 10, 2015, at 10:16 PM, Stefano Maffulli wrote: > On Tue, 2015-03-10 at 15:23 -0700, James E. Blair wrote: > > The holy grail of this system would be the "suitable for production > > deployment" tag, but no one has figured out how to define it yet. > > Are crazy ideas welcome in this

Re: [openstack-dev] [cinder] cinder is broken until someone fixes the forking code

Joshua Harlow wrote: > I've also got the following up: > > https://review.openstack.org/#/c/162781/ > > Which tries the force file descriptors to be closed; although I'm unsure > where the tempest results went (and am rechecking that); maybe it breaks so > badly that tempest doesn't even ru

Re: [openstack-dev] [neutron] VXLAN with single-NIC compute nodes: Avoiding the MTU pitfalls

On 11 March 2015 at 04:27, Fredy Neeser wrote: > 7: br-ex.1: mtu 1500 qdisc noqueue state > UNKNOWN group default > link/ether e0:3f:49:b4:7c:a7 brd ff:ff:ff:ff:ff:ff > inet 192.168.1.14/24 brd 192.168.1.255 scope global br-ex.1 >valid_lft forever preferred_lft forever > > 8: br-

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

John, I think our proposals fit together nicely. This thread is about allowing overlap within a pool. I think it is fine for an external IPAM driver to disallow such overlap for now. However, the reference implementation must support it for backward compatibility and so my proposal will account

Re: [openstack-dev] [cinder] cinder is broken until someone fixes the forking code

On Wed, Mar 11, 2015, at 01:47 PM, Mike Bayer wrote: > Hello Cinder - > > I’d like to note that for issue > https://bugs.launchpad.net/oslo.db/+bug/1417018, no solution that > actually > solves the problem for Cinder is scheduled to be committed anywhere. The > patch I proposed for oslo.db is on

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

On Wed, Mar 11, 2015 at 5:59 AM, Sean Dague wrote: > The last couple of days I was at the Operators Meetup acting as Nova > rep for the meeting. All the sessions were quite nicely recorded to > etherpads here - https://etherpad.openstack.org/p/PHL-ops-meetup > > There was both a specific Nova ses

Re: [openstack-dev] [cinder] cinder is broken until someone fixes the forking code

We have this patch in review currently. I think this one should 'fix' it no? Please review. https://review.openstack.org/#/c/163551/ Walt On 03/11/2015 10:47 AM, Mike Bayer wrote: Hello Cinder - I’d like to note that for issue https://bugs.launchpad.net/oslo.db/+bug/1417018, no solution t

Re: [openstack-dev] Avoiding regression in project governance

> -Original Message- > From: Stefano Maffulli [mailto:[email protected]] > Sent: 11 March 2015 03:16 > To: [email protected] > Subject: Re: [openstack-dev] Avoiding regression in project governance > > On Tue, 2015-03-10 at 15:23 -0700, James E. Blair wrote: > > The hol

Re: [openstack-dev] [kolla] about the image size

On 3/10/15, 12:22 AM, "Bohai (ricky)" wrote: >Hi, stackers > >I try to use the Kolla Images and pull them down from docker hub. >I found the size of the image is bigger than what I thought(for example, >the images of docker conductor service is about 1.4GB). > >Is it possible to get a more smal

Re: [openstack-dev] [cinder] K3 Feature Freeze Exception request for bp/nfs-backup

On 11:20 Wed 11 Mar , Tom Barron wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I hereby solicit a feature freeze exception for the NFS backup review [1]. This was granted by the community in the Cinder IRC meeting this morning (sorry raw log is only available due to irc bot iss

Re: [openstack-dev] [cinder] cinder is broken until someone fixes the forking code

On 11:49 Wed 11 Mar , Walter A. Boring IV wrote: > We have this patch in review currently. I think this one should > 'fix' it no? > > Please review. > > https://review.openstack.org/#/c/163551/ Looks like it to me. Would appreciate a +1 from Mike Bayer before we push this through. Thanks f

Re: [openstack-dev] Avoiding regression in project governance

On 2015-03-11 19:06:21 + (+), Tim Bell wrote: [...] > I think we can make this work. Assuming more than N (to my mind > > 5 or so) deployments report they are using project X, we can say > that this is used in production/POC/... and the number of > nodes/hypervisors/etc. > > This makes it

Re: [openstack-dev] [Neutron] Issue when upgrading from Juno to Kilo due to agent report_state RPC namespace patch

I've filed a bug here: https://bugs.launchpad.net/neutron/+bug/1430984 I've outlined the path I'd like to take in the bug description. - Original Message - > +1 on avoiding changes that break rolling upgrade. > > Rolling upgrade has been working so far (at least from my perspective), and

Re: [openstack-dev] [cinder] cinder is broken until someone fixes the forking code

On 03/11/2015 03:37 PM, Mike Bayer wrote: > > > Mike Perez wrote: > >> On 11:49 Wed 11 Mar , Walter A. Boring IV wrote: >>> We have this patch in review currently. I think this one should >>> 'fix' it no? >>> >>> Please review. >>> >>> https://review.openstack.org/#/c/163551/ >> >> Looks

[openstack-dev] [Solum] Should app names be unique?

Hi Solum team, In yesterday's team meeting the question of whether Solum should enforce unique app name constraint within a tenant came up. As a recollection, in Solum one can create an 'app' using: solum app create --plan-file --name Currently Solum does support creating multiple apps w

Re: [openstack-dev] Avoiding regression in project governance

> -Original Message- > From: Jeremy Stanley [mailto:[email protected]] > Sent: 11 March 2015 20:40 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] Avoiding regression in project governance > > On 2015-03-11 19:06:21 + (+), Tim Bel

Re: [openstack-dev] [Solum] Should app names be unique?

The only reason this came up yesterday is because we wanted Solums 'app create' behavior to be consistent with other openstack services. However, if heat has a unique stack name constraint and glance\nova don't, then the argument of consistency does not hold. I'm still of the opinion that we

[openstack-dev] [OSSN 0045] Vulnerable clients allow a TLS protocol downgrade (FREAK)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vulnerable clients allow a TLS protocol downgrade (FREAK) - --- ### Summary ### Some client-side libraries, including un-patched versions of OpenSSL, contain a vulnerability which can allow a man-in-the-middle (MITM) to force a TLS version downgrade.

Re: [openstack-dev] [Glance] Proposal to change Glance meeting time.

I'd prefer to go with 1400 UTC unless there's a majority for 1500UTC. P.S. It's my feeling that ML announcements and conversations are not effective when taking poll from wider audience so we'd discuss this a bit more in the next meeting and merge the votes. Thanks, -Nikhil ___

Re: [openstack-dev] [Solum] Should app names be unique?

Dev, thanks for bringing up the item about Heat enforcing unique stack names.. My mistake on thinking it supported non-unique stack names. I remember it working early on, but probably got changed/fixed somewhere along the way. My argument in IRC was one based on consistency with related/similar

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

On 3/12/15, 2:33 AM, "Carl Baldwin" wrote: >John, > >I think our proposals fit together nicely. This thread is about >allowing overlap within a pool. I think it is fine for an external >IPAM driver to disallow such overlap for now. However, the reference >implementation must support it for

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

On 03/11/2015 12:53 PM, Sylvain Bauza wrote: >> Reporting on Scheduler Fails >> >> >> Apparently, some time recently, we stopped logging scheduler fails >> above DEBUG, and that behavior also snuck back into Juno as well >> (https://etherpad.openstack.org/p/PHL-ops-nova

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

On 03/11/2015 01:21 PM, Tim Bell wrote: > Reporting on Scheduler Fails > > Apparently, some time recently, we stopped logging scheduler > fails above DEBUG, and that behavior also snuck back into > Juno as well > (https://etherpad.openstack.org

Re: [openstack-dev] [swift] auth migration and user data migration

On Wed, Mar 11, 2015 at 1:16 PM, Weidong Shao wrote: > > ​the url is encoded in the object hash​! This somehow entangles the data > storage/validity with its account and makes it difficult to migrate the > data. I guess it is too late to debate on the design of this. Do you know > the technical r

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

On 03/11/2015 11:26 AM, Clark Boylan wrote: > On Wed, Mar 11, 2015, at 05:59 AM, Sean Dague wrote: >> Galera Upstream Testing >> --- >> >> The majority of deploys run with Galera MySQL. There was a question >> about whether or not we could get that into upstream testing pipeline

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

On 12 March 2015 at 10:09, Sean Dague wrote: > On 03/11/2015 11:26 AM, Clark Boylan wrote: >> On Wed, Mar 11, 2015, at 05:59 AM, Sean Dague wrote: >>> Galera Upstream Testing >>> --- >>> >>> The majority of deploys run with Galera MySQL. There was a question >>> about whether o

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

On Wed, Mar 11, 2015 at 2:54 PM, John Belamaric wrote: > I was proposing that the reference driver not support it either, and we > only handle that use case via the non-pluggable implementation in Kilo, > waiting until Liberty to handle it in the pluggable implementation. > However, I don't think

Re: [openstack-dev] [Solum] Should app names be unique?

I agree that we should pursue an implementation that allows for duplicate names, as I think that use case makes sense. I manage several application deployments that run different concurrent versions of the same application during blue/green and canary deployment, and I routinely use duplicate na

Re: [openstack-dev] [Ironic] Thinking about our python client UX

On 8 March 2015 at 13:12, Devananda van der Veen wrote: > Hi folks, > > Recently, I've been thinking more of how users of our python client > will interact with the service, and in particular, how they might > expect different instances of Ironic to behave. > > We added several extensions to the A

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/10/2015 06:34 PM, Gabriel Bezerra wrote: > Em 10.03.2015 14:24, Carl Baldwin escreveu: >> Neutron currently does not enforce the uniqueness, or >> non-overlap, of subnet cidrs within the address scope for a >> single tenant. For example, if a te

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I also agree wilcards do not look solid, and without clear use cases with reasonable demand from operators, it's better to avoid putting ourselves into position of supporting the feature for eternity. We had cases of immature API design rushed into th

Re: [openstack-dev] [neutron] Proposal to add Ihar Hrachyshka as a Neutron Core Reviewer

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/11/2015 06:54 PM, Kyle Mestery wrote: > On Wed, Mar 4, 2015 at 1:42 PM, Kyle Mestery > wrote: > > I'd like to propose that we add Ihar Hrachyshka to the Neutron > core reviewer team. Ihar has been doing a great job r

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

My concern is that we are introducing new objects in Neutron that are scoped to a tenant and we don't have anything else like that right now. For example, I can create 100 3-tier topologies (router + 3 subnets/networks) with duplicated names, CIDRs, etc between all of them and it doesn't matter if

Re: [openstack-dev] [stable] Icehouse 2014.1.4 freeze exceptions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/11/2015 12:21 PM, Alan Pevec wrote: > Hi, > > next Icehouse stable point release 2014.1.4 has been slipping last > few weeks due to various gate issues, see "Recently closed" section > in https://etherpad.openstack.org/p/stable-tracker for detai

Re: [openstack-dev] [nova] need input on possible API change for bug #1420848

I can see how to do a v2 extension following the example given for extended_services.py and extended_services_delete.py. That seems to be working now. I'm not at all clear on how to go about doing the equivalent for v2.1. Does that use the api/openstack/compute/plugins/v3/ subdirectory? I

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

This has been settled and we're not moving forward with it for Kilo. I agree tenants are an administrative concept, not a networking one so using them for uniqueness doesn't really make sense. In Liberty we are proposing a new grouping mechanism, as you call it, specifically for the purpose of

[openstack-dev] [neutron] [metadata] metadata service when NOT using name space

When use_namespaces is True, there will be a namespace metadata proxy launched for either dhcp or router namespace, this proxy will accept metada service request , and then proxy the request to metadata server via metadata agent. But when use_namespaces is False, there is no namespace metadata

Re: [openstack-dev] Avoiding regression in project governance

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/11/2015 02:40 PM, Jeremy Stanley wrote: >> I think we can make this work. Assuming more than N (to my mind > >> > 5 or so) deployments report they are using project X, we can say >> > that this is used in production/POC/... and the number of >> >

Re: [openstack-dev] [Neutron] Issue when upgrading from Juno to Kilo due to agent report_state RPC namespace patch

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Should we target it for Kilo? It does not seem right to allow it slipping into the next release while we know there are operators relying on the feature. On 03/11/2015 08:42 PM, Assaf Muller wrote: > I've filed a bug here: > https://bugs.launchpad.ne

[openstack-dev] [neutron] [dhcp] dnsmasq scale problem

One of my peers mentioned that people talked about dnsmasq scale problems at paris summit. So what was the scale problems? Currently, there is one dnsmasq instance for each subnet. And pool management and allocation seemed to be done at neutron. Thus dnsmasq is light-weighted. So if dnsmasq

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/11/2015 07:48 PM, Joe Gordon wrote: > Out of sync Quotas -- > > https://etherpad.openstack.org/p/PHL-ops-nova-feedback L63 > > The quotas code is quite racey (this is kind of a known if you look > at the bug tracker). It was act

Re: [openstack-dev] [stable] Icehouse 2014.1.4 freeze exceptions

Big +2 on both those, but will leave it up to Alan make the final call Cheers On Wed, Mar 11, 2015 at 3:42 PM, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 03/11/2015 12:21 PM, Alan Pevec wrote: > > Hi, > > > > next Icehouse stable point release 2014.1.4 has be

Re: [openstack-dev] [Ironic] Thinking about our python client UX

On 11 March 2015 at 18:21, Robert Collins wrote: ... > > Since there was no debate on the compat thing, I've thrown up an > etherpad to start the discussion. > > https://etherpad.openstack.org/p/ironic-client-ux > Thanks Rob. Michael Davies has a spec [1] that discusses how a client interacts wit

Re: [openstack-dev] [all] Testtools 1.7.0 may error if you installed it before reading this email

On 03/11/2015 08:10 AM, Robert Collins wrote: > The wheel has been removed from PyPI and anyone installing testtools > 1.7.0 now will install from source which works fine. I noticed the centos7 job failed with the source version. The failing job was [1] where the back-trace looks like ~45 songs o

  1   2   >