Re: [openstack-dev] [neutron][kilo] - vxlan's max bandwidth

Sławek Kapłoński wrote: Hello, What MTU have You got configured on VMs? I had issue with performance on vxlan network with standard MTU (1500) but when I configured Jumbo frames on vms and on hosts then it was much better. Right. Note that custom MTU works out of the box only starting from M

Re: [openstack-dev] [ironic][nova][horizon] Serial console support for ironic instances

Thanks Yuiko for doing this, but I'm sorry that I can't go to Austin, so I would like to add more details about my proposal here, hope someone can bring it to the session. Add a custom HTTP proxy for web based consoles to Nova https://review.openstack.org/#/c/300582/ * Pros: - for Ironic -

Re: [openstack-dev] [Cinder] API features discoverability

Hi Michal, This seemed like a good idea when I first read it. What more, the server code for extension listing [1] does not do any authorization, so it can be used for any logged in user. However, I don't know if requiring the admin to manually disable an extension is practical. First, admins

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Monty Taylor wrote: On 04/17/2016 10:13 AM, Doug Hellmann wrote: I am organizing a summit session for the cross-project track to (re)consider how we manage our list of global dependencies [1]. Some of the changes I propose would have a big impact, and so I want to ensure everyone doing packaging

Re: [openstack-dev] [all] Openstack rpm build

On Mon, Apr 18, 2016 at 06:05:41AM +0200, Andreas Jaeger wrote: > On 04/18/2016 05:30 AM, Kenny Ji-work wrote: > > Hi all, > > > > In our developing environment, we want to create openstack's rpms by > > ourselves. By typing 'python setup.py bdist_rpm', there would be some > > files not packaged i

Re: [openstack-dev] [all] Removal of in progress console log access

On 04/15/2016 07:23 PM, Monty Taylor wrote: > tl;dr Effective immediately we've put firewalls in front of the Jenkins > servers removing in-progress console log streaming access > > Longer version > > > Recently some potential security issues have come to our attention with > Jenkins [1] and the

Re: [openstack-dev] [TripleO] Backport exception request // discussion: setting the default root device

On Wed, Apr 06, 2016 at 10:28:44AM +0200, Dmitry Tantsur wrote: > Hi OOO'ers! > > I'd like to get your permission to backport > https://review.openstack.org/#/c/288417/ to stable/{liberty,mitaka} or seek > alternative suggestions on how to make life easier for folks upgrading for > Kilo. > > The

Re: [openstack-dev] [neutron][kilo] - vxlan's max bandwidth

2016-04-18 15:58 GMT+09:00 Ihar Hrachyshka : > Sławek Kapłoński wrote: > >> Hello, >> >> What MTU have You got configured on VMs? I had issue with performance on >> vxlan network with standard MTU (1500) but when I configured Jumbo >> frames on vms and on hosts then it was much better. > > > Right

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

Colleagues, Whether we are going to continue using Shotgun or substitute it with something else, we still need to decouple it from Fuel because Shotgun is a generic tool. Please review these [1], [2]. [1] https://review.openstack.org/#/c/298603 [2] https://review.openstack.org/#/c/298615 Btw, o

Re: [openstack-dev] [neutron][kilo] - vxlan's max bandwidth

Akihiro Motoki wrote: 2016-04-18 15:58 GMT+09:00 Ihar Hrachyshka : Sławek Kapłoński wrote: Hello, What MTU have You got configured on VMs? I had issue with performance on vxlan network with standard MTU (1500) but when I configured Jumbo frames on vms and on hosts then it was much better.

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On 04/17/2016 11:34 AM, Monty Taylor wrote: > On 04/17/2016 10:13 AM, Doug Hellmann wrote: >> I am organizing a summit session for the cross-project track to >> (re)consider how we manage our list of global dependencies [1]. >> Some of the changes I propose would have a big impact, and so I >> want

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On Mon, 18 Apr 2016, Sean Dague wrote: So if you have strong feelings and ideas, why not get them out in email now? That will help in the framing of the conversation. I won't be at summit and I feel pretty strongly about this topic, so I'll throw out my comments: I agree with the basic premis

Re: [openstack-dev] [Tricircle] Error runnig py27

Sorry, email went to spam. Just saw it. Following is link http://paste.openstack.org/show/494403/ On Mon, Apr 18, 2016 at 8:41 AM, joehuang wrote: > Hi, Khayam, > > > > Could you paste your whole file for test cases and the source code to be > tested in the http://paste.openstack.org/ seperatly.

Re: [openstack-dev] [TripleO][CI] Tempest sources for testing tripleo in CI environment

For making clear all advantages and disadvantages, I've created a doc: https://docs.google.com/document/d/1HmY-I8OzoJt0SzLzs79hCa1smKGltb-byrJOkKKGXII/edit?usp=sharing Please comment. On Sun, Apr 17, 2016 at 12:14 PM, Sagi Shnaidman wrote: > > Hi, > > John raised up the issue - where should we

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On 04/18/2016 08:22 AM, Chris Dent wrote: > On Mon, 18 Apr 2016, Sean Dague wrote: > >> So if you have strong feelings and ideas, why not get them out in email >> now? That will help in the framing of the conversation. > > I won't be at summit and I feel pretty strongly about this topic, so > I'l

Re: [openstack-dev] [TripleO][CI] Tempest sources for testing tripleo in CI environment

On Mon, Apr 18, 2016 at 8:36 AM, Sagi Shnaidman wrote: > For making clear all advantages and disadvantages, I've created a doc: > > https://docs.google.com/document/d/1HmY-I8OzoJt0SzLzs79hCa1smKGltb-byrJOkKKGXII/edit?usp=sharing > > Please comment. > > On Sun, Apr 17, 2016 at 12:14 PM, Sagi Shnai

[openstack-dev] [puppet] weekly meeting #79

Hi, We'll have our weekly meeting tomorrow at 3pm UTC on #openstack-meeting4. https://wiki.openstack.org/wiki/Meetings/PuppetOpenStack As usual, free free to bring topics in this etherpad: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160419 We'll also have open discussion

Re: [openstack-dev] [all] Openstack rpm build

On 2016-04-18 12:01, Qiming Teng wrote: > On Mon, Apr 18, 2016 at 06:05:41AM +0200, Andreas Jaeger wrote: >> On 04/18/2016 05:30 AM, Kenny Ji-work wrote: >>> Hi all, >>> >>> In our developing environment, we want to create openstack's rpms by >>> ourselves. By typing 'python setup.py bdist_rpm', th

[openstack-dev] [devstack] openstack client slowness / client-as-a-service

There have been threads in the past about the slowness of the "openstack" client tool such as this one by Sean last year: http://lists.openstack.org/pipermail/openstack-dev/2015-April/061317.html Sean mentioned a 1.5s fixed overhead on openstack client, and mentions it is significantly slower t

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On 18/04/2016 13:51, Sean Dague wrote: > On 04/18/2016 08:22 AM, Chris Dent wrote: >> On Mon, 18 Apr 2016, Sean Dague wrote: >> >>> So if you have strong feelings and ideas, why not get them out in email >>> now? That will help in the framing of the conversation. >> >> I won't be at summit and I fe

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

>> Btw, one of the ideas was to use Fuel task capabilities to gather diagnostic snapshot. I think such kind of tools should use as less as possible existing infrastructure, because in case if something went wrong, you should be able to easily get diagnostic information, even with broken RabbitMQ,

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

Evgeniy L. wrote: > I think such kind of tools should use as less as possible existing > infrastructure, because in case if something went wrong, you should > be able to easily get diagnostic information, even with broken RabbitMQ, > Astute and MCollective. It's a good point indeed! Moreover, trou

[openstack-dev] [all] removal of "Using keystoneauth correctly in projects" from cross project schedule

After chatting with Monty and Thierry this morning, and trying to figure out the right way to ensure that enough voices are in the requirements x-p session, we've decided to do the following: * remove "Using keystoneauth correctly in projects" from cross project schedule * Do a special edition Ope

Re: [openstack-dev] [all] removal of "Using keystoneauth correctly in projects" from cross project schedule

On Mon, Apr 18, 2016 at 6:50 AM, Sean Dague wrote: > After chatting with Monty and Thierry this morning, and trying to figure > out the right way to ensure that enough voices are in the requirements > x-p session, we've decided to do the following: > > * remove "Using keystoneauth correctly in pr

Re: [openstack-dev] [watcher] Api and Decision Engine integration - design question

Hi Tomasz, Overall, I don't really have any strong opinion on this. I just think that if we do it with option 1, it may become quite hard to make Watcher more scalable in the long run if we need to. That's why I would tend to choose option 2. Also, it's not so easy for me to evaluate how much work

Re: [openstack-dev] [nova] Launchpad bug spring cleaning day Monday 4/18

In case the dashboard is not loading, you can use * query_inconsistent.py * query_stale_incomplete.py from https://github.com/markuszoeller/openstack/tree/master/scripts/launchpad Regards, Markus Zoeller (markus_z) > From: Matt Riedemann > To: "OpenStack Development Mailing Lis

[openstack-dev] [Neutron] L3 HA testing on scale

Hi guys! As a developer I use Devstack or multinode OpenStack installation (4-5 nodes) for work, but these are "abstract" environments, where you are not able to perform some scenarios as your machine is not powerful enough. But it is really important to understand the issues that real deployments

Re: [openstack-dev] [Keystone] State of Fernet Token deployment

On Fri, Apr 15, 2016 at 9:04 PM, Adam Young wrote: > We all want Fernet to be a reality. We ain't there yet (Except for mfish > who has no patience) but we are getting closer. The goal is to get Fernet > as the default token provider as soon as possible. The review to do this > has uncovered a

Re: [openstack-dev] [trove] Adding release notes to changes

Right, we are still waiting on the final +2/+1 for that ;) See https://review.openstack.org/#/c/306018/ Thanks! Peter -Original Message- From: Andreas Jaeger [mailto:[email protected]] Sent: April-18-16 2:32 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [

[openstack-dev] [Nova] SR-IOV IRC meeting and sub-team - passing the torch

Hi team, As I'll be focusing on different things going forward, I was wondering if someone from the group of people who were normally working in this area would want to step up and take over the sub-team IRC meeting. It is normally not a massive overhead, mostly tracking ongoing efforts and patch

Re: [openstack-dev] [all] Removal of in progress console log access

Sean Dague writes: > Bummer. This gets used a to figure out the state of things given that > zuul links to the console even after the job is complete. Changing that > to the log server link would mitigate the blind spot. Yeah, we know it's important, which is why we're working on getting it back

Re: [openstack-dev] [Keystone] State of Fernet Token deployment

On Mon, Apr 18, 2016 at 8:29 AM, Brant Knudson wrote: > > > On Fri, Apr 15, 2016 at 9:04 PM, Adam Young wrote: > >> We all want Fernet to be a reality. We ain't there yet (Except for mfish >> who has no patience) but we are getting closer. The goal is to get Fernet >> as the default token prov

Re: [openstack-dev] [all] Removal of in progress console log access

On 04/18/2016 11:22 AM, James E. Blair wrote: > Sean Dague writes: > >> Bummer. This gets used a to figure out the state of things given that >> zuul links to the console even after the job is complete. Changing that >> to the log server link would mitigate the blind spot. > > Yeah, we know it's

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On 04/18/2016 08:24 AM, Hayes, Graham wrote: > On 18/04/2016 13:51, Sean Dague wrote: >> On 04/18/2016 08:22 AM, Chris Dent wrote: >>> On Mon, 18 Apr 2016, Sean Dague wrote: >>> So if you have strong feelings and ideas, why not get them out in email now? That will help in the framing of t

Re: [openstack-dev] [Keystone] State of Fernet Token deployment

It looks like it does [0]. [0] https://github.com/openstack-dev/devstack/blob/4e7804431ada7e2cc0db63bd4c52b17782d33b5b/lib/keystone#L494-L497 On Mon, Apr 18, 2016 at 10:20 AM, Matt Fischer wrote: > On Mon, Apr 18, 2016 at 8:29 AM, Brant Knudson wrote: > >> >> >> On Fri, Apr 15, 2016 at 9:04 P

[openstack-dev] [infra][manila] manila/glusterfs gateway jobs are UNSTABLE due to perm isssue

Hi, The gate-manila-tempest-dsvm-glusterfs and gate-manila-tempest-dsvm-glusterfs-native gateway jobs end up UNSTABLE since a while, as one can observe at any recent change in https://review.openstack.org/#/q/project:openstack/manila eg. https://review.openstack.org/302801 . The issue is tha

[openstack-dev] [puppet] Stepping down from puppet-openstack-core

Hello here, I would like to ask to be removed from the core reviewers team on the Puppet for OpenStack project. I lack dedicated time to contribute on my spare time to the project. And I don't work anymore on OpenStack deployments. In the past months, I stopped reviewing and submitting changes o

Re: [openstack-dev] [Keystone] State of Fernet Token deployment

On Mon, Apr 18, 2016 at 10:20 AM, Matt Fischer wrote: > On Mon, Apr 18, 2016 at 8:29 AM, Brant Knudson wrote: > >> >> >> On Fri, Apr 15, 2016 at 9:04 PM, Adam Young wrote: >> >>> We all want Fernet to be a reality. We ain't there yet (Except for >>> mfish who has no patience) but we are gettin

Re: [openstack-dev] [kolla][infra] Gate bused until Sunday April 17th

On 2016-04-17 03:38:28 + (+), Steven Dake (stdake) wrote: > Hey folks. A shade + nodepool change has broken our gating > functionality on the OVH cloud provider and probably some others. > The net result is we can't actually gate our changes. [...] A change[*] to record the public address

Re: [openstack-dev] [puppet] Stepping down from puppet-openstack-core

On Mon, Apr 18, 2016 at 11:37 AM, Sebastien Badia wrote: > Hello here, > > I would like to ask to be removed from the core reviewers team on the > Puppet for OpenStack project. > > I lack dedicated time to contribute on my spare time to the project. And I > don't work anymore on OpenStack deployme

Re: [openstack-dev] [Neutron] L3 HA testing on scale

This is some awesome work, Ann. It's very neat to see that all the races we've struggled with w.r.t. the l3 scheduler has paid off. I would definitely like to see how these results are effected by https://review.openstack.org/#/c/305774/ but understandably 49 physical nodes are hard to come by. Al

Re: [openstack-dev] Fwd: [kolla][security][infra][ops] Kolla Design Summit Agenda Published

Hi All - Just a quick note to let you konw that you do not need to re-download the app in order to get Schedule updates. We do have a cached API, so it might take a few minutes for it to update. We also limit the # of updates to 30 at a time so your app doesn't crash in the event of a slow ne

Re: [openstack-dev] [trove] review dashboard, review priorities for Newton

Thanks Amrith, this looks great! Just added the new dashboard to my Gerrit dashboard. Cannot think on anything else we could need. 2016-04-16 10:45 GMT-03:00 Amrith Kumar : > At the Trove meeting last week, I agreed to send out a simple way in > which we can all view the patches that are in nee

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

So I also want to stress out that shared libraries are huge pain during upgrades. While I'm not in favor of packages with embedded virtualenvs (as Matt pointed out, this has a lot of issues), having shared dependency pool pretty much means that you need to upgrade *everything* that is openstack at

Re: [openstack-dev] [oslo][keystone][documentation][gate] Babel dependency for oslo.log

On 2016-04-17 15:15:49 -0400 (-0400), Davanum Srinivas wrote: [...] > Is there anyone working to fix all tox CI jobs to honor upper > constraints? [...] The present implementation relies on zuul-cloner, which doesn't (yet) do what we'd need in the post and release pipelines. Sachi is working on po

Re: [openstack-dev] [all] Removal of in progress console log access

Sean Dague writes: > On 04/18/2016 11:22 AM, James E. Blair wrote: >> Sean Dague writes: >> >>> Bummer. This gets used a to figure out the state of things given that >>> zuul links to the console even after the job is complete. Changing that >>> to the log server link would mitigate the blind s

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On 04/18/2016 10:57 AM, Michał Jastrzębski wrote: > So I also want to stress out that shared libraries are huge pain > during upgrades. While I'm not in favor of packages with embedded > virtualenvs (as Matt pointed out, this has a lot of issues), having > shared dependency pool pretty much means t

[openstack-dev] [horizon][keystone] Getting Auth Token from Horizon when using Federation

Hi, we're deploying Liberty (soon Mitaka) with heavy reliance on the SAML2 Federation system by Keystone where we're a Service Provider (SP). The problem in this situation is getting a token for direct API access.(*) There are conceptually two methods to use the CLI: 1) Modify ones (each custom

Re: [openstack-dev] [nova] [glance] Getting the ball rolling on glance v2 in nova in newton cycle

On 15/04/16 11:42 -0400, Nikhil Komawar wrote: comment inline On 4/15/16 11:08 AM, Sean Dague wrote: On 04/15/2016 10:42 AM, Jay Pipes wrote: On 04/01/2016 06:45 AM, Sean Dague wrote: #2 - move discover major version back to glanceclient - https://github.com/openstack/nova/blob/3cdaa30566c17a

Re: [openstack-dev] [all] removal of "Using keystoneauth correctly in projects" from cross project schedule

Hi Sean/Morgan, I think there is room for the proper use of keystoneauth sessions in the Keystone v3 only cross-project session too: https://etherpad.openstack.org/p/newton-keystone-v3-devstack Feel free to add anything related to ksa sessions. Henrique Em seg, 18 de abr de 2016 às 11:06, Morga

Re: [openstack-dev] [kolla][ssecurity] Threat Analysis Design Session

On 04/16/2016 02:19 PM, Steven Dake (stdake) wrote: If the security team has a conflict with this slot that I didn't see or am unaware of, please speak up so I can have it corrected in the main schedule. Our schedule is here: sadly, i will miss the beginning of this as i have a conflicting p

Re: [openstack-dev] [nova] [glance] Getting the ball rolling on glance v2 in nova in newton cycle

On 4/16/16 1:33 PM, Flavio Percoco wrote: > On 15/04/16 11:42 -0400, Nikhil Komawar wrote: >> comment inline >> >> On 4/15/16 11:08 AM, Sean Dague wrote: >>> On 04/15/2016 10:42 AM, Jay Pipes wrote: On 04/01/2016 06:45 AM, Sean Dague wrote: > #2 - move discover major version back to glan

Re: [openstack-dev] [all] Removal of in progress console log access

On 04/18/2016 12:18 PM, James E. Blair wrote: > Sean Dague writes: > >> On 04/18/2016 11:22 AM, James E. Blair wrote: >>> Sean Dague writes: >>> Bummer. This gets used a to figure out the state of things given that zuul links to the console even after the job is complete. Changing that

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

What I meant is if you have liberty Nova and liberty Cinder, and you want to upgrade Nova to Mitaka, you also upgrade Oslo to Mitaka and Cinder which was liberty either needs to be upgraded or is broken, therefore during upgrade you need to do cinder and nova at the same time. DB can be snapshotted

[openstack-dev] [searchlight] [ceilometer] [fuel] [freezer] [monasca] Elasticsearch 2.x gate support

Hi, I'm looking into supporting and testing Elasticsearch 2.x in Searchlight's test jobs. Currently I don't know of any other projects that run tests against Elasticsearch in the gate (since we had to add it to Jenkins [1]). Several projects install the python elasticsearch client in requiremen

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Excerpts from Matthew Thode's message of 2016-04-18 10:23:37 -0500: > On 04/18/2016 08:24 AM, Hayes, Graham wrote: > > On 18/04/2016 13:51, Sean Dague wrote: > >> On 04/18/2016 08:22 AM, Chris Dent wrote: > >>> On Mon, 18 Apr 2016, Sean Dague wrote: > >>> > So if you have strong feelings and i

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Excerpts from Hayes, Graham's message of 2016-04-18 13:24:40 +: > On 18/04/2016 13:51, Sean Dague wrote: > > On 04/18/2016 08:22 AM, Chris Dent wrote: > >> On Mon, 18 Apr 2016, Sean Dague wrote: > >> > >>> So if you have strong feelings and ideas, why not get them out in email > >>> now? That w

Re: [openstack-dev] [oslo][keystone][documentation][gate] Babel dependency for oslo.log

Andreas Jaeger wrote: On 04/17/2016 09:15 PM, Davanum Srinivas wrote: Hi Oslo folks, Andreas and others, Over the weekend oslo.log 3.4.0 was released. This broke keystone CI jobs [2], even though the 3.4.0 was not specified in upper-constraints as keystone jobs were not honoring the upper-const

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On 04/18/2016 01:33 PM, Doug Hellmann wrote: > Excerpts from Matthew Thode's message of 2016-04-18 10:23:37 -0500: >> To add to this, I'd also note that I as a packager would likely stop >> packaging Openstack at whatever release this goes into. While the >> option to package and ship a virtualen

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On Mon, 18 Apr 2016, Sean Dague wrote: Many (most?) people won't be doing those kinds of installations. If all-in- one installations are important to the rpm- and deb- based distributions then _they_ should be resolving the dependency issues local to their own infrastruc

Re: [openstack-dev] [cinder] [nova] Cinder-Nova API meeting

Hi All, We are having the last Cinder-Nova API interactions meeting before the Summit this Wednesday __20th April 2100UTC__, on the #openstack-meeting-cp channel. You can find the information about the recent discussions here: https://etherpad.openstack.org/p/cinder-nova-api-changes This week

[openstack-dev] [nova] Question on removal of 'arbitrary' pluggable interfaces

Hi nova folks, I was reading over the following: http://lists.openstack.org/pipermail/openstack-operators/2016-April/010186.html And I am wondering if there is a list of all the plugin points and there schedule for being deprecated and then removed (or am I misreading that mail/thread?). I

Re: [openstack-dev] [Keystone] State of Fernet Token deployment

Thanks Brant, I will missing that distinction. On Mon, Apr 18, 2016 at 9:43 AM, Brant Knudson wrote: > > > On Mon, Apr 18, 2016 at 10:20 AM, Matt Fischer > wrote: > >> On Mon, Apr 18, 2016 at 8:29 AM, Brant Knudson wrote: >> >>> >>> >>> On Fri, Apr 15, 2016 at 9:04 PM, Adam Young wrote: >>>

Re: [openstack-dev] [nova] Question on removal of 'arbitrary' pluggable interfaces

Each configuration option's deprecation is indicated in the Nova source code in the configuration option's declaration. For instance: https://github.com/openstack/nova/blob/master/nova/conf/compute.py#L86-L91 grep for deprecated_for_removal=True Best, -jay On 04/18/2016 02:08 PM, Joshua Harlo

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On 04/18/2016 12:33 PM, Doug Hellmann wrote: > Excerpts from Matthew Thode's message of 2016-04-18 10:23:37 -0500: >> On 04/18/2016 08:24 AM, Hayes, Graham wrote: >>> On 18/04/2016 13:51, Sean Dague wrote: On 04/18/2016 08:22 AM, Chris Dent wrote: > On Mon, 18 Apr 2016, Sean Dague wrote: >

Re: [openstack-dev] [oslo][keystone][documentation][gate] Babel dependency for oslo.log

Josh, So Andreas and i talked a bit, it seems like NONE of the oslo.* libs except oslo.i18n needs a direct dependency on Babel. So we should yank them all out and bump major versions http://eavesdrop.openstack.org/irclogs/%23openstack-infra/latest.log.html#t2016-04-18T11:58:10 Thanks, Dims On Mo

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Excerpts from Sean Dague's message of 2016-04-18 13:49:31 -0400: > On 04/18/2016 01:33 PM, Doug Hellmann wrote: > > Excerpts from Matthew Thode's message of 2016-04-18 10:23:37 -0500: > > >> To add to this, I'd also note that I as a packager would likely stop > >> packaging Openstack at whatever r

Re: [openstack-dev] [puppet] Stepping down from puppet-openstack-core

On Mon, Apr 18, 2016 at 9:37 AM, Sebastien Badia wrote: > Hello here, > > I would like to ask to be removed from the core reviewers team on the > Puppet for OpenStack project. > > I lack dedicated time to contribute on my spare time to the project. And I > don't work anymore on OpenStack deployme

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Excerpts from Matthew Thode's message of 2016-04-18 13:22:38 -0500: > On 04/18/2016 12:33 PM, Doug Hellmann wrote: > > Excerpts from Matthew Thode's message of 2016-04-18 10:23:37 -0500: > >> On 04/18/2016 08:24 AM, Hayes, Graham wrote: > >>> On 18/04/2016 13:51, Sean Dague wrote: > On 04/18/2

Re: [openstack-dev] [oslo][keystone][documentation][gate] Babel dependency for oslo.log

Excerpts from Davanum Srinivas (dims)'s message of 2016-04-18 14:27:48 -0400: > Josh, > > So Andreas and i talked a bit, it seems like NONE of the oslo.* libs > except oslo.i18n needs a direct dependency on Babel. So we should yank > them all out and bump major versions > http://eavesdrop.openstac

Re: [openstack-dev] [Keystone] State of Fernet Token deployment

On Mon, Apr 18, 2016 at 7:29 AM, Brant Knudson wrote: > > > On Fri, Apr 15, 2016 at 9:04 PM, Adam Young wrote: > >> We all want Fernet to be a reality. We ain't there yet (Except for mfish >> who has no patience) but we are getting closer. The goal is to get Fernet >> as the default token prov

Re: [openstack-dev] More on the topic of DELIMITER, the Quota Management Library proposal

On 04/16/2016 05:51 PM, Amrith Kumar wrote: If we therefore assume that this will be a Quota Management Library, it is safe to assume that quotas are going to be managed on a per-project basis, where participating projects will use this library. I believe that it stands to reason that any data p

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On 04/18/2016 01:40 PM, Doug Hellmann wrote: > Excerpts from Matthew Thode's message of 2016-04-18 13:22:38 -0500: >> On 04/18/2016 12:33 PM, Doug Hellmann wrote: >>> Excerpts from Matthew Thode's message of 2016-04-18 10:23:37 -0500: On 04/18/2016 08:24 AM, Hayes, Graham wrote: > On 18/04

[openstack-dev] [ironic] Meetings cancelled April 25 and May 2

Hi friends, We won't have our weekly meeting on April 25 (because most of us will be at the summit) or May 2 (because people will still be recovering from summit travel). See you all there on May 9. // jim __ OpenStack Deve

Re: [openstack-dev] [all] [devstack] Adding example "local.conf" files for testing?

Markus Zoeller wrote: > I guess having an IF-ELSE block in a "local.conf" is > crazy talk? Yes, I think it is. local.conf is already a pretty big complex thing for someone starting out, as it is. -- Sean M. Collins __ Ope

Re: [openstack-dev] [Neutron] L3 HA testing on scale

Great work Ann. About testing on scale it’s not so problematic because of the Cloud For All project. Here [1] you can request for a multi node cluster which you can use to perform tests. Exact requirements are specified on that website. [1] http://osic.org Regards, Lubosz “diltram” Kosnik On Ap

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On 2016-04-18 13:58:03 -0500 (-0500), Matthew Thode wrote: > Ya, I'd be happy to work more with upstream. I already review the > stable-reqs updates and watch them for the stable branches I package > for. Not sure what else is needed. Reviewing the master branch openstack/requirements repository

Re: [openstack-dev] [all] [devstack] Adding example "local.conf" files for testing?

On Thu, Apr 14, 2016 at 1:31 AM, Markus Zoeller wrote: > Sometimes (especially when I try to reproduce bugs) I have the need > to set up a local environment with devstack. Everytime I have to look > at my notes to check which option in the "local.conf" have to be set > for my needs. I'd like to a

[openstack-dev] [ironic] weekly subteam status report

Hi, We are overjoyed to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff with 11.04.2016): - Ironic: 203 bugs (+3) + 166 wishlist items (+3). 30 new (+5), 134 in progress (-2

Re: [openstack-dev] [Neutron] L3 HA testing on scale

Great work Ann. About testing on scale it’s not so problematic because of the Cloud For All project. Here [1] you can request for a multi node cluster which you can use to perform tests. Exact requirements are specified on that website. [1] http://osic.org Regards, Lubosz “diltram” Kosnik On Ap

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Excerpts from Jeremy Stanley's message of 2016-04-18 19:10:52 +: > On 2016-04-18 13:58:03 -0500 (-0500), Matthew Thode wrote: > > Ya, I'd be happy to work more with upstream. I already review the > > stable-reqs updates and watch them for the stable branches I package > > for. Not sure what e

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On 04/18/2016 02:10 PM, Jeremy Stanley wrote: > On 2016-04-18 13:58:03 -0500 (-0500), Matthew Thode wrote: >> Ya, I'd be happy to work more with upstream. I already review the >> stable-reqs updates and watch them for the stable branches I package >> for. Not sure what else is needed. > > Review

[openstack-dev] [keystone][barbican][designate][murano][fuel][ironic][cue][ceilometer][astara][gce-api][kiloeyes] keystoneclient 3.0.0 release - no more CLI!

Everyone, I sent out a note about this on Friday [1], but I'll repeat it here and tag individual projects. The keystone team *will* be releasing a new version of keystoneclient on *Thursday* that will not include a CLI. A quick codesearch showed that a few projects are still using the old `keys

Re: [openstack-dev] [oslo][keystone][documentation][gate] Babel dependency for oslo.log

Okie, the following reviews are up: https://review.openstack.org/307461 (oslo.concurrency) https://review.openstack.org/307463 (oslo.cache) https://review.openstack.org/307464 (oslo.privsep) https://review.openstack.org/307466 (oslo.middleware) https://review.openstack.org/307467 (oslo.log) https

Re: [openstack-dev] [oslo][keystone][documentation][gate] Babel dependency for oslo.log

On Mon, Apr 18, 2016 at 4:28 PM, Joshua Harlow wrote: > Okie, the following reviews are up: > > https://review.openstack.org/307461 (oslo.concurrency) > https://review.openstack.org/307463 (oslo.cache) > https://review.openstack.org/307464 (oslo.privsep) > https://review.openstack.org/307466 (oslo

[openstack-dev] [nova] [neutron] the nova network facade that isn't

When doing bug triage this morning a few bugs popped up: - https://bugs.launchpad.net/nova/+bug/1456899 - nova absolute-limits Security groups count incorrect when using Neutron - https://bugs.launchpad.net/nova/+bug/1376316 - nova absolute-limits floating ip count is incorrect in a neutron based

Re: [openstack-dev] [oslo][keystone][documentation][gate] Babel dependency for oslo.log

Davanum Srinivas wrote: On Mon, Apr 18, 2016 at 4:28 PM, Joshua Harlow wrote: Okie, the following reviews are up: https://review.openstack.org/307461 (oslo.concurrency) https://review.openstack.org/307463 (oslo.cache) https://review.openstack.org/307464 (oslo.privsep) https://review.openstack.

Re: [openstack-dev] [nova] [neutron] the nova network facade that isn't

On 4/18/2016 3:33 PM, Sean Dague wrote: When doing bug triage this morning a few bugs popped up: - https://bugs.launchpad.net/nova/+bug/1456899 - nova absolute-limits Security groups count incorrect when using Neutron - https://bugs.launchpad.net/nova/+bug/1376316 - nova absolute-limits floati

Re: [openstack-dev] [oslo][keystone][documentation][gate] Babel dependency for oslo.log

Please check whether translation of these is setup in project-config, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21

Re: [openstack-dev] [OpenStack Foundation] [board][tc][all] One Platform – Containers/Bare Metal? (Re: Board of Directors Meeting)

Hi all, Magnum will have a fishbowl session to discuss if it makes sense to build a common abstraction layer for all COEs (kubernetes, docker swarm and mesos): https://www.openstack.org/summit/austin-2016/summit-schedule/events/9102 Frankly, this is a controversial topic since I heard agreement

Re: [openstack-dev] [magnum][kuryr] Shared session in design summit

Hi all, The Magnum-Kuryr joined session was scheduled to Thursday 11:50 – 12:30: https://www.openstack.org/summit/austin-2016/summit-schedule/events/9099 . I am looking forward to seeing you all there. In addition, Magnum will have another session for container storage: https://www.openstack.o

Re: [openstack-dev] [ironic] weekly subteam status report

On Mon, Apr 18, 2016 at 3:10 PM, Ruby Loo wrote: > ... > Network isolation (Neutron/Ironic work) (jroll) > === > - Still needs review > - cross-project session tuesday on the future of bare metal networking: > https://wiki.openstack.org/wiki/Meetings/Ir

Re: [openstack-dev] [nova] Question on removal of 'arbitrary' pluggable interfaces

On 04/18/2016 01:14 PM, Jay Pipes wrote: > Each configuration option's deprecation is indicated in the Nova source > code in the configuration option's declaration. For instance: > > https://github.com/openstack/nova/blob/master/nova/conf/compute.py#L86-L91 > > grep for deprecated_for_removal=Tr

Re: [openstack-dev] [nova] Launchpad bug spring cleaning day Monday 4/18

On 4/18/2016 9:00 AM, Markus Zoeller wrote: In case the dashboard is not loading, you can use * query_inconsistent.py * query_stale_incomplete.py from https://github.com/markuszoeller/openstack/tree/master/scripts/launchpad Regards, Markus Zoeller (markus_z) From: Matt Riedem

Re: [openstack-dev] [OpenStack Foundation] [board][tc][all] One Platform – Containers/Bare Metal? (Re: Board of Directors Meeting)

I'd love to attend, but this is right on top of the app catalog meeting. I think the app catalog might be one of the primary users of a cross COE api. At minimum we'd like to be able to be able to store url's for Kubernetes/Swarm/Mesos templates and have an api to kick off a workflow in Horizon

Re: [openstack-dev] [Keystone] State of Fernet Token deployment

On 04/18/2016 02:10 PM, Matt Fischer wrote: Thanks Brant, I will missing that distinction. On Mon, Apr 18, 2016 at 9:43 AM, Brant Knudson > wrote: On Mon, Apr 18, 2016 at 10:20 AM, Matt Fischer mailto:[email protected]>> wrote: On Mon, Apr 18, 2016 a

Re: [openstack-dev] [Keystone] State of Fernet Token deployment

On 04/18/2016 10:29 AM, Brant Knudson wrote: On Fri, Apr 15, 2016 at 9:04 PM, Adam Young > wrote: We all want Fernet to be a reality. We ain't there yet (Except for mfish who has no patience) but we are getting closer. The goal is to get Fernet as the d

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Hi Doug, I very much welcome opening such a thread before the discussion at the summit, as often, sessions are too short. Taking the time to write things down first also helps having a more constructive discussion. Before I reply to each individual message below, let me attempt to reply to the bi

Re: [openstack-dev] [Keystone] State of Fernet Token deployment

Its also could be more difficult for ops to debug if it autocreates it on a cluster when config management is broken and you don't realize it, and you see keys that were created, but totally wrong for the cluster. Though maybe there should be a generic ha=True option in keystone to override tha

Re: [openstack-dev] [Keystone] State of Fernet Token deployment

On Mon, Apr 18, 2016 at 5:14 PM, Adam Young wrote: > On 04/18/2016 10:29 AM, Brant Knudson wrote: > > > > On Fri, Apr 15, 2016 at 9:04 PM, Adam Young wrote: > >> We all want Fernet to be a reality. We ain't there yet (Except for mfish >> who has no patience) but we are getting closer. The goal

  1   2   >