Re: [openstack-dev] [tc][pbr][packaging][all] Definition of Data Files (config) in setup.cfg

2016-06-10 Thread Robert Collins
The underlying problem is as you say that distutils and setuptools and wheel are all different, and until there is a PEP addressing this *and* implemented in both wheel and setuptools, we won't get consistent behaviour. I'm pretty sure Daniel Hoth is interested in making this happen - there have

[openstack-dev] [tc][pbr][packaging][all] Definition of Data Files (config) in setup.cfg

2016-06-10 Thread Morgan Fainberg
There has been a bit of back[1] and forth[2][3][4][5] between at least one packaging group and a few folks who are trying to define data files (config) in the setup.cfg to aid/ease installation within virtual environments. >From what I can tell, there has been an issue with setuptools that makes

Re: [openstack-dev] [keystone][all] Incorporating performance feedback into the review process

2016-06-10 Thread Morgan Fainberg
On Fri, Jun 10, 2016 at 4:19 PM, Boris Pavlovic wrote: > Morgan, > > >> When there were failures, the failures were both not looked at by the >> Rally team and was not performance reasons at the time, it was rally not >> able to be setup/run at all. > > > Prove this, or it's

[openstack-dev] [ironic] IPA example hardware managers

2016-06-10 Thread Jay Faulkner
Hi all, I've been promising to do more knowledge sharing on IPA Hardware Managers, specifically in the form of a presentation. However, I wanted to go a different route that would be more likely to stand the test of time and be more self-service. To that end, I've created a couple of

Re: [openstack-dev] [qa] Tempest unstable interfaces in plugins

2016-06-10 Thread Assaf Muller
On Fri, Jun 10, 2016 at 12:02 PM, Andrea Frittoli wrote: > Dear all, > > I'm working on making the client manager in Tempest a stable interface, so > that in future it may be used safely by plugins to easily gain access > service clients [0]. > > This work inevitably

Re: [openstack-dev] [keystone][all] Incorporating performance feedback into the review process

2016-06-10 Thread Boris Pavlovic
Morgan, > When there were failures, the failures were both not looked at by the > Rally team and was not performance reasons at the time, it was rally not > able to be setup/run at all. Prove this, or it's not true. I agree there were such situations (very rarely actually) and we were fixing

Re: [openstack-dev] [keystone][all] Incorporating performance feedback into the review process

2016-06-10 Thread Boris Pavlovic
Lance, I share just how it looked from my side. I really support your idea (no matter what you pick to use your tooling/rally/jmeter) it is very valuable, especially if it will become voting job. This really should be done by someone. Best regards, Boris Pavlovic On Fri, Jun 10, 2016 at 3:26

Re: [openstack-dev] [keystone][all] Incorporating performance feedback into the review process

2016-06-10 Thread Morgan Fainberg
On Fri, Jun 10, 2016 at 3:26 PM, Lance Bragstad wrote: > >1. I care about performance. I just believe that a big hurdle has been >finding infrastructure that allows us to run performance tests in a >consistent manner. Dedicated infrastructure plays a big role in

Re: [openstack-dev] [Higgins] Call for contribution for Higgins API design

2016-06-10 Thread Hongbin Lu
Yuanying, The etherpads you pointed to were a few years ago and the information looks a bit outdated. I think we can collaborate a similar etherpad with updated information (i.e. remove container runtimes that we don’t care, add container runtimes that we care). The existing etherpad can be

Re: [openstack-dev] [javascript] Meeting time doodle

2016-06-10 Thread Michael Krotscheck
Alright, the first meeting will be on monday, 1500UTC. For the first meeting we'll just meet in #openstack-javascript, and see which of the rooms are available at that time. The agenda is here, go ahead and add anything you'd think is pertinent:

Re: [openstack-dev] [keystone][all] Incorporating performance feedback into the review process

2016-06-10 Thread Lance Bragstad
1. I care about performance. I just believe that a big hurdle has been finding infrastructure that allows us to run performance tests in a consistent manner. Dedicated infrastructure plays a big role in this, which is hard (if not impossible) to obtain in the gate - making the gate

Re: [openstack-dev] [Kuryr] [Neutron] Waiting until Neutron Port isActive

2016-06-10 Thread Kevin Benton
Polling should be fine. get_port operations a relatively cheap operation for Neutron. Maybe for the future we can have a more pluggable version of the nova callback notifier we have in Neutron like Salvatore pointed out. On Fri, Jun 10, 2016 at 7:49 AM, Mohammad Banikazemi

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

2016-06-10 Thread Carl Baldwin
Here's a link directly to the current design proposal [1] that might be of interest. [1] https://review.openstack.org/#/c/318317/4/doc/source/devref/openvswitch_agent.rst@463 On Thu, Jun 9, 2016 at 5:31 PM, Carl Baldwin wrote: > Hi, > > You may or may not be aware of the

Re: [openstack-dev] [ironic][infra][qa] Ironic grenade work nearly complete

2016-06-10 Thread Jim Rollenhagen
On Fri, Jun 10, 2016 at 12:35:43PM -0700, Devananda van der Veen wrote: > On 06/10/2016 05:48 AM, Sean Dague wrote: > > On 06/10/2016 08:41 AM, Jeremy Stanley wrote: > >> On 2016-06-10 11:49:12 +0100 (+0100), Miles Gould wrote: > >>> On 09/06/16 23:21, Jay Faulkner wrote: > There was some

Re: [openstack-dev] [Kuryr] [Neutron] Waiting until Neutron Port isActive

2016-06-10 Thread Antoni Segura Puimedon
On Fri, Jun 10, 2016 at 5:18 PM, Neil Jerram wrote: > Yes, that all makes sense - thanks for explaining. > > Neil > > > On Fri, Jun 10, 2016 at 3:50 PM Mohammad Banikazemi wrote: > >> Hi Neil, >> >> Currently, when a docker libnetwork "join" operation in

Re: [openstack-dev] [keystone][all] Incorporating performance feedback into the review process

2016-06-10 Thread Boris Pavlovic
Lance, It is amazing effort, I am wishing you good luck with Keystone team, however i faced some issues when I started similar effort about 3 years ago with Rally. Here are some points, that are going to be very useful for you: 1. I think that Keystone team doesn't care about performance &

Re: [openstack-dev] [keystone][all] Incorporating performance feedback into the review process

2016-06-10 Thread Lance Bragstad
Ok - here is what I have so far [0], and I admit there is still a bunch of work to do [1]. I encourage folks to poke through the code and suggest improvements via Github Issues. I've never really stood up third-party testing before so this is completely new to me and I'm open to feedback, and

Re: [openstack-dev] [Neutron][LBaaS][barbican]TLS container could not be found

2016-06-10 Thread Jiahao Liang
Hi guys, I was away from Barbican for a couple of month but I still come back has the same issue. As mentioned in the original email, I went through https://wiki.openstack.org/wiki/Network/LBaaS/docs/how-to-create-tls-loadbalancer with devstack. And all my branches were set to stable/mitaka. If

Re: [openstack-dev] [ironic][infra][qa] Ironic grenade work nearly complete

2016-06-10 Thread Devananda van der Veen
On 06/10/2016 05:48 AM, Sean Dague wrote: > On 06/10/2016 08:41 AM, Jeremy Stanley wrote: >> On 2016-06-10 11:49:12 +0100 (+0100), Miles Gould wrote: >>> On 09/06/16 23:21, Jay Faulkner wrote: There was some discussion about whether or not the Ironic grenade job should be in the check

[openstack-dev] [horizon] 800 UTC Meeting Cancelled on 15/06

2016-06-10 Thread Rob Cresswell
Hi all, I'm away next week so won't be able to run the 800 UTC meeting. The 2000 UTC meeting will be chaired by David Lyle. Rob __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

2016-06-10 Thread Morgan Fainberg
On Fri, Jun 10, 2016 at 6:37 AM, Henry Nash wrote: > On further reflection, it seems to me that we can never simply enable > either of these approaches in a single release. Even a v4.0 version of the > API doesn’t help - since presumably a sever supporting v4 would want to be

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

2016-06-10 Thread Clint Byrum
Excerpts from Henry Nash's message of 2016-06-10 14:37:37 +0100: > On further reflection, it seems to me that we can never simply enable either > of these approaches in a single release. Even a v4.0 version of the API > doesn’t help - since presumably a sever supporting v4 would want to be able

[openstack-dev] [swift] crypto-review review, soft-freeze on master

2016-06-10 Thread John Dickinson
As mentioned in IRC and on https://wiki.openstack.org/wiki/Swift/PriorityReviews, Swift is now under a soft freeze for master. The patches for the crypto functionality have been proposed to feature/crypto-review. The initial plan is to spend two weeks in this soft freeze (until June 24) to

Re: [openstack-dev] [charms] Re-licensing OpenStack charms under Apache 2.0

2016-06-10 Thread Bilal Baqar
Hey James No problem on my side for this change. Regards On Fri, Jun 10, 2016 at 3:25 PM, Neil Jerram wrote: > Me too. > > On Fri, Jun 10, 2016 at 10:32 AM Cory Benfield wrote: > >> >> > On 8 Jun 2016, at 11:20, James Page wrote: >>

Re: [openstack-dev] [Neutron] Random IP address allocations

2016-06-10 Thread Carl Baldwin
On Fri, Jun 10, 2016 at 2:40 AM, Gary Kotton wrote: > Hi, > The patch https://review.openstack.org/#/c/292207/ has broken decomposed > plugins. I am not sure if we can classify this as a API change – basically Can you be more specific about how it "has broken decomposed

[openstack-dev] [craton] agenda for Monday's team meeting

2016-06-10 Thread sean roberts
I'd like to resync what our teams has been working on so we can create a common agenda -- ~sean __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [qa] Tempest unstable interfaces in plugins

2016-06-10 Thread Andrea Frittoli
Dear all, I'm working on making the client manager in Tempest a stable interface, so that in future it may be used safely by plugins to easily gain access service clients [0]. This work inevitably involves changing the current client manager (unstable) interface. Several tempest plugins in

Re: [openstack-dev] [magnum-ui][magnum] Proposed Core addition, and removal notice

2016-06-10 Thread David Lyle
+1 on my account, I've not had time to contribute. David On Fri, Jun 10, 2016 at 8:12 AM, Hongbin Lu wrote: > +1 > >> -Original Message- >> From: Shuu Mutou [mailto:shu-mu...@rf.jp.nec.com] >> Sent: June-10-16 5:33 AM >> To: openstack-dev@lists.openstack.org >>

Re: [openstack-dev] [Kuryr] [Neutron] Waiting until Neutron Port isActive

2016-06-10 Thread Neil Jerram
Yes, that all makes sense - thanks for explaining. Neil On Fri, Jun 10, 2016 at 3:50 PM Mohammad Banikazemi wrote: > Hi Neil, > > Currently, when a docker libnetwork "join" operation in Kuryr is returned, > it is not guaranteed that the network connectivity has been

Re: [openstack-dev] [rally] "Failed to create the requested number of tenants" error

2016-06-10 Thread Nate Johnston
Running 'rally deployment check' appears to come up with good results: > keystone endpoints are valid and following services are available: > +-++---+ > | services| type | status| > +-++---+ > | __unknown__

[openstack-dev] [StoryBoard] StoryBoard Bug Squash!

2016-06-10 Thread Zara Zaimeche
Hi all! We're running a bugsquash for bugs in StoryBoard and the StoryBoard webclient, on the 22nd and 23rd of June. It'll start and finish around 11:00 UTC-- though of course every day is a StoryBoard bugsquash day *really*, so that's just the timeframe where StoryBoard people will

Re: [openstack-dev] [ironic][infra][qa] Ironic grenade work nearly complete

2016-06-10 Thread Dmitry Tantsur
On 06/10/2016 02:16 PM, Jim Rollenhagen wrote: On Thu, Jun 09, 2016 at 03:21:05PM -0700, Jay Faulkner wrote: A quick update: The devstack-gate patch is currently merging. There was some discussion about whether or not the Ironic grenade job should be in the check pipeline (even as -nv) for

[openstack-dev] [neutron] [classifier] Requesting feedback on typed classifications model

2016-06-10 Thread Duarte Cardoso, Igor
Hi community and common classifier team, In anticipation to the next common classifier meeting, I've added a meeting agenda item to the next meeting's agenda [1] about the proposed "typed classifications" model for the new common classifier. The typed classifications model is described in [2,

Re: [openstack-dev] [nova][glance][qa] - Nova glance v2 work complete

2016-06-10 Thread Mikhail Fedosin
Hooray :) After a long period of time it's done. Thanks all who helped us there! Best regards, Mike Fedosin On Fri, Jun 10, 2016 at 3:27 PM, Kairat Kushaev wrote: > \0/ > That's awesome. > Big thanks to mfedosin and sudipto for driving this work. > > Best regards, >

Re: [openstack-dev] [Kuryr] [Neutron] Waiting until Neutron Port isActive

2016-06-10 Thread Mohammad Banikazemi
Hi Neil, Currently, when a docker libnetwork "join" operation in Kuryr is returned, it is not guaranteed that the network connectivity has been established. There are containers that check for network connectivity as the first thing they do when they come up and under heavy load some notice

Re: [openstack-dev] [rally] "Failed to create the requested number of tenants" error

2016-06-10 Thread Aleksandr Maretskiy
Nate, please try to make this simple check to make sure that everything is set up properly: 1) command "rally deployment check" should print an ascii-table with a list of services available 2) load rally auto-generated openrc file and run some OpenStack CLI command, for example: $ .

Re: [openstack-dev] [stable][all] Tagging kilo-eol for "the world"

2016-06-10 Thread Boden Russell
On 6/2/16 4:31 AM, Tony Breeds wrote: > Any projects that will be EOL'd will need all open reviews abandoned before it > can be processed. openstack/vmware-nsx kilo patches have been abandoned in preparation for the EOL. Thanks

Re: [openstack-dev] [neutron][SFC]

2016-06-10 Thread Alioune
Hi Mohan, Even if I clone the master branch of networking-sfc project,I get the following errir when creating flow-classifier, therefore I do precise the logical-source-port. 2016-06-10 05:34:05.693 10799 ERROR neutron.api.v2.resource DBError: (pymysql.err.IntegrityError) (1048, u"Column

Re: [openstack-dev] [rally] "Failed to create the requested number of tenants" error

2016-06-10 Thread Nate Johnston
Boris, We use a common Keystone across all of our production environments; I was running this against a new deployment we are working on making production-ready, so I had specified OS_AUTH_URL to be the common keystone. There is no keystone deployed in this datacenter. Is there a specific way I

Re: [openstack-dev] [magnum-ui][magnum] Proposed Core addition, and removal notice

2016-06-10 Thread Hongbin Lu
+1 > -Original Message- > From: Shuu Mutou [mailto:shu-mu...@rf.jp.nec.com] > Sent: June-10-16 5:33 AM > To: openstack-dev@lists.openstack.org > Cc: Haruhiko Katou > Subject: [openstack-dev] [magnum-ui][magnum] Proposed Core addition, > and removal notice > > Hi team, > > I propose the

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

2016-06-10 Thread Henry Nash
On further reflection, it seems to me that we can never simply enable either of these approaches in a single release. Even a v4.0 version of the API doesn’t help - since presumably a sever supporting v4 would want to be able to support v3.x for a signification time; and, already discussed, as

Re: [openstack-dev] Quesion about Openstack Containers and Magnum

2016-06-10 Thread Spyros Trigazis
Hi Wally. You can follow these instructions [1] to install from source code (use the stable/mitaka branch when you'll clone). Although, this guide is under the developer url, it's built for operators. Keep in mind that you need Neutron/LBaaS V1. Additionally there is this [2] puppet module.

Re: [openstack-dev] [Kuryr] [Neutron] Waiting until Neutron Port is Active

2016-06-10 Thread Neil Jerram
Hi Mohammad, Why is the blocking needed? Is it to report some kind of status back to Docker/Kubernetes, or to allow some follow-on action to happen? When using networking-calico as the driver, I think that only option (1) would work, out of the options you've suggested below. (3) doesn't work,

Re: [openstack-dev] [nova] NUMA, huge pages, and scheduling

2016-06-10 Thread Paul Michali
Actually, I had menm_page_size set to "large" and not "1024". However, it seemed like it was using 1024 pages per (small VM creation). Is there possibly some issue with large not using one of the supported values? I would have guessed it would have chosen 2M or 1G for the size. Any thoughts? PCM

Re: [openstack-dev] [nova] NUMA, huge pages, and scheduling

2016-06-10 Thread Paul Michali
Thanks Daniel and Chris! I think that was the problem, I had configured Nova flavor with a mem_page_size of 1024, and it should have been one of the supported values. I'll go through and check things out one more time, but I think that is the problem. I still need to figure out what is going on

Re: [openstack-dev] [neutron][networking-ovn] OVN vs. OpenDayLight

2016-06-10 Thread Russell Bryant
On Fri, Jun 10, 2016 at 11:11 AM, Oleg Bondarev wrote: > Hi, > > [1] is a doc comparing OVN and ODL for Neutron. I wrote it in March so > some info might be stale. > Hope this can be useful, comments are welcome! > > [1] >

Re: [openstack-dev] [nova] NUMA, huge pages, and scheduling

2016-06-10 Thread Paul Michali
See PCM: Inline... On Thu, Jun 9, 2016 at 11:42 AM Steve Gordon wrote: > - Original Message - > > From: "Paul Michali" > > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > > Sent: Tuesday,

Re: [openstack-dev] [nova] NUMA, huge pages, and scheduling

2016-06-10 Thread Paul Michali
I'll try to reproduce and collect logs for a bug report. Thanks for the info. PCM On Thu, Jun 9, 2016 at 9:43 AM Matt Riedemann wrote: > On 6/9/2016 6:15 AM, Paul Michali wrote: > > > > > > On Wed, Jun 8, 2016 at 11:21 PM Chris Friesen > >

Re: [openstack-dev] [ironic][infra][qa] Ironic grenade work nearly complete

2016-06-10 Thread Sean Dague
On 06/10/2016 08:41 AM, Jeremy Stanley wrote: > On 2016-06-10 11:49:12 +0100 (+0100), Miles Gould wrote: >> On 09/06/16 23:21, Jay Faulkner wrote: >>> There was some discussion about whether or not the Ironic grenade job >>> should be in the check pipeline (even as -nv) for grenade, >> >> Not

Re: [openstack-dev] [openstack-ansible] Mid-cycle date selection (need input!)

2016-06-10 Thread Major Hayden
On 06/10/2016 03:16 AM, Jesse Pretorius wrote: > Thanks Major. I have no conflicts for any of the dates. By option 2 I'm > guessing you mean either 22-24 August (Mon-Wed) or 24-26 (Wed-Fri) rather > than the entire week? Correct. For the August 22-26 dates, we could choose anything within that

Re: [openstack-dev] [ironic][infra][qa] Ironic grenade work nearly complete

2016-06-10 Thread Jeremy Stanley
On 2016-06-10 11:49:12 +0100 (+0100), Miles Gould wrote: > On 09/06/16 23:21, Jay Faulkner wrote: > >There was some discussion about whether or not the Ironic grenade job > >should be in the check pipeline (even as -nv) for grenade, > > Not having this would mean that changes to grenade could

Re: [openstack-dev] [nova][glance][qa] - Nova glance v2 work complete

2016-06-10 Thread Kairat Kushaev
\0/ That's awesome. Big thanks to mfedosin and sudipto for driving this work. Best regards, Kairat Kushaev On Fri, Jun 10, 2016 at 2:52 PM, Monty Taylor wrote: > On 06/10/2016 01:19 PM, Sean Dague wrote: > > On 06/07/2016 04:55 PM, Matt Riedemann wrote: > >> I tested the

Re: [openstack-dev] [ironic][infra][qa] Ironic grenade work nearly complete

2016-06-10 Thread Jim Rollenhagen
On Thu, Jun 09, 2016 at 03:21:05PM -0700, Jay Faulkner wrote: > A quick update: > > The devstack-gate patch is currently merging. > > There was some discussion about whether or not the Ironic grenade job should > be in the check pipeline (even as -nv) for grenade, so I split that patch > into

Re: [openstack-dev] [nova][glance][qa] - Nova glance v2 work complete

2016-06-10 Thread Monty Taylor
On 06/10/2016 01:19 PM, Sean Dague wrote: > On 06/07/2016 04:55 PM, Matt Riedemann wrote: >> I tested the glance v2 stack (glance v1 disabled) using a devstack >> change here: >> >> https://review.openstack.org/#/c/325322/ >> >> Now that the changes are merged up through the base nova image proxy

Re: [openstack-dev] [nova][glance][qa] - Nova glance v2 work complete

2016-06-10 Thread Sean Dague
On 06/07/2016 04:55 PM, Matt Riedemann wrote: > I tested the glance v2 stack (glance v1 disabled) using a devstack > change here: > > https://review.openstack.org/#/c/325322/ > > Now that the changes are merged up through the base nova image proxy and > the libvirt driver, and we just have

Re: [openstack-dev] [ironic][infra][qa] Ironic grenade work nearly complete

2016-06-10 Thread Miles Gould
On 09/06/16 23:21, Jay Faulkner wrote: There was some discussion about whether or not the Ironic grenade job should be in the check pipeline (even as -nv) for grenade, Not having this would mean that changes to grenade could silently break Ironic's CI, right? That sounds really bad. Miles

Re: [openstack-dev] [charms] Re-licensing OpenStack charms under Apache 2.0

2016-06-10 Thread Neil Jerram
Me too. On Fri, Jun 10, 2016 at 10:32 AM Cory Benfield wrote: > > > On 8 Jun 2016, at 11:20, James Page wrote: > > > > The majority of contributors are from Canonical (from whom I have > permission to make this switch) with a further 18 contributors

Re: [openstack-dev] [neutron][networking-ovn] OVN vs. OpenDayLight

2016-06-10 Thread Oleg Bondarev
Hi, [1] is a doc comparing OVN and ODL for Neutron. I wrote it in March so some info might be stale. Hope this can be useful, comments are welcome! [1] https://docs.google.com/document/d/13K4Xpdu1IbRJDj5JTepDI4nwUkCDCu7IOnYwHkZtcMA/edit?usp=sharing Thanks, Oleg On Fri, Jun 10, 2016 at 12:28

[openstack-dev] [magnum-ui][magnum] Proposed Core addition, and removal notice

2016-06-10 Thread Shuu Mutou
Hi team, I propose the following changes to the magnum-ui core group. + Thai Tran http://stackalytics.com/report/contribution/magnum-ui/90 I'm so happy to propose Thai as a core reviewer. His reviews have been extremely valuable for us. And he is active Horizon core member. I believe

Re: [openstack-dev] [charms] Re-licensing OpenStack charms under Apache 2.0

2016-06-10 Thread Cory Benfield
> On 8 Jun 2016, at 11:20, James Page wrote: > > The majority of contributors are from Canonical (from whom I have permission > to make this switch) with a further 18 contributors from outside of Canonical > who I will be directly contacting for approval in gerrit as

Re: [openstack-dev] [nova] theoretical race between live migration and resource audit?

2016-06-10 Thread lương hữu tuấn
Hi, Yes, it is actually a race and we have already faced a negative effect when using evacuation. Some information of cpu pinning is lost. Imagine that, in some cases, we do some re-scheduling actions (evacuate, live-migration, etc.) then immediately do the next actions (delete, resize, etc.)

Re: [openstack-dev] [swift][keystone] Using JSON as future ACL format

2016-06-10 Thread Coles, Alistair
Thai, (repeating some of what we have discussed in private for others' benefit) The Swift docs state "Be sure to use Keystone UUIDs rather than names in container ACLs" [1]. The guidance is re-iterated here [2] "...names must no longer be used in cross-tenant ACLs...". They then go on to

Re: [openstack-dev] [release][reno][infra] merging tags between branches is confusing our release notes

2016-06-10 Thread Thierry Carrez
Doug Hellmann wrote: Excerpts from John Dickinson's message of 2016-06-08 11:30:03 -0700: Isn't the reason that the branch is merged back in because otherwise per can't generate a valid version number? I don't think it's related to versions being "valid," but to making things feel less

Re: [openstack-dev] [nova] NUMA, huge pages, and scheduling

2016-06-10 Thread Daniel P. Berrange
On Thu, Jun 09, 2016 at 12:35:06PM -0600, Chris Friesen wrote: > On 06/09/2016 05:15 AM, Paul Michali wrote: > > 1) On the host, I was seeing 32768 huge pages, of 2MB size. > > Please check the number of huge pages _per host numa node_. > > > 2) I changed mem_page_size from 1024 to 2048 in the

[openstack-dev] [Neutron] Random IP address allocations

2016-06-10 Thread Gary Kotton
Hi, The patch https://review.openstack.org/#/c/292207/ has broken decomposed plugins. I am not sure if we can classify this as a API change - basically the IP address allocation model has changed. So someone prior to the patch could create a network and expect addresses A, B and C to be

Re: [openstack-dev] [nova] theoretical race between live migration and resource audit?

2016-06-10 Thread Matthew Booth
Yes, this is a race. However, it's my understanding that this is 'ok'. The resource tracker doesn't claim to be 100% accurate at all times, right? Otherwise why would it update itself in a period task in the first place. It's my understanding that the resource tracker is basically a best effort

Re: [openstack-dev] [openstack-ansible] Mid-cycle date selection (need input!)

2016-06-10 Thread Jesse Pretorius
On 9 June 2016 at 19:51, Major Hayden wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hey folks, > > I've been able to secure a few dates at Rackspace's headquarters in San > Antonio, Texas: > > 1) August 10-12 > 2) August 22-26 > 3) August 29 - September 2 >