Re: [openstack-dev] Troubleshooting and ask.openstack.org

On 01/07/16 13:01, Adam Young wrote: On 06/28/2016 11:13 PM, Tom Fifield wrote: Quick answers in-line On 29/06/16 05:44, Adam Young wrote: It seems to me that keystone Core should be able to moderate Keystone questions on the site. That means that they should be able to remove old dead ones,

Re: [openstack-dev] Troubleshooting and ask.openstack.org

On 06/28/2016 08:33 PM, Steve Martinelli wrote: I'm cool with the existing keystone repo and adding to docs. If we hit a huge amount of content then we can migrate to a new repo. I think Adam's main concern with this approach is that we reduce the contributors down to folks that know the

Re: [openstack-dev] Troubleshooting and ask.openstack.org

On 06/28/2016 11:13 PM, Tom Fifield wrote: Quick answers in-line On 29/06/16 05:44, Adam Young wrote: It seems to me that keystone Core should be able to moderate Keystone questions on the site. That means that they should be able to remove old dead ones, remove things tagged as Keystone that

Re: [openstack-dev] [requirements][mistral] Library for JWT (JSON Web Token)

> On 30 Jun 2016, at 19:50, Mehdi Abaakouk wrote: > > > > Le 2016-06-30 13:07, Renat Akhmerov a écrit : >> Reason: we need it to provide support for OpenID Connect >> authentication in Mistral. > > Can't [1] do the job ? (sorry if I'm off-beat) > > [1]

Re: [openstack-dev] [Zaqar] Nominate Thomas Herve for Zaqar core

+1, Thomas did a great job on Zaqar. As we can see, many important feature are done by him. Welcome, thomas. 2016-07-01 6:33 GMT+08:00 Emilien Macchi : > I'm not core but Thomas helped Puppet OpenStack group many times to > get Zaqar working in gate and we highly appreciate

Re: [openstack-dev] [all] Proposal: Architecture Working Group

+1 -Original Message- From: Nikhil Komawar [mailto:nik.koma...@gmail.com] Sent: Monday, June 20, 2016 10:37 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [all] Proposal: Architecture Working Group +1 , great idea. if we can add a

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

There is a version of Tempest that is released as part of OpenStack release. Agree with Mark that we should stick to versions parity. -Original Message- From: Mark Voelker [mailto:mvoel...@vmware.com] Sent: Monday, June 20, 2016 8:25 AM To: OpenStack Development Mailing List (not for

Re: [openstack-dev] [kolla][vote] Apply for release:managed tag

On Fri, Jul 01, 2016 at 12:56:09AM +, Steven Dake (stdake) wrote: > Hey folks, > > I'd like the release management team to take on releases of Kolla. This > means applying for the release:managed[1] tag. Please vote +1 if you wish to > proceed, or -1 if you don't wish to proceed. The most

Re: [openstack-dev] [kolla][vote] Apply for release:managed tag

On Fri, Jul 1, 2016 at 6:26 AM, Steven Dake (stdake) wrote: > Hey folks, > > I'd like the release management team to take on releases of Kolla. This > means applying for the release:managed[1] tag. Please vote +1 if you wish > to proceed, or –1 if you don’t wish to proceed.

[openstack-dev] [neutron] ARP responder for VLAN network?

hi, all. As we all know, for vxlan networks, ovs bridge "br-tun" are treated ARP responder. L2 agent add ARP response flows into that bridge. So that we can save ARP traffic in physical network. But, what about vlan networks? I created two vms in one vlan network and the same subnet. I

Re: [openstack-dev] [kolla][vote] Apply for release:managed tag

+1 while I know that we weren't actually good at freezing features, we were young project. Right now we're more mature and I think we can deal with feature freeze. On 30 June 2016 at 19:56, Steven Dake (stdake) wrote: > Hey folks, > > I'd like the release management team to

Re: [openstack-dev] Hangzhou Bug Smash will be held from July 6 to 8

Hi Will,Happy to know that you are going to join remotely!you can add bugs you want to fix into the link [3] below, and discuss on the irc channel. RegardsFredOn Jul 1, 2016, at 02:07, Will Zhou wrote:Hello Fred,Great event! In which way can we work remotely with the team?

Re: [openstack-dev] Hangzhou Bug Smash will be held from July 6 to 8

Hi Will, Happy to know that you are going to join remotely! you can add bugs you want to fix into the link [3] below, and discuss on the irc channel. Regards Fred > On Jul 1, 2016, at 02:07, Will Zhou > wrote: > > Hello Fred, > > Great event!

Re: [openstack-dev] Hangzhou Bug Smash will be held from July 6 to 8

Hello Fred, Thanks. It is great to communicate and cooperate with openstacker. I will be there. See you guys. Best Regards, xiangxinyong > Hi OpenStackers, > > The 4th China OpenStack Bug Smash, hosted by CESI, Huawei, and intel, will be > held in Hangzhou, China from July 6 to 8

[openstack-dev] [kolla][vote] Apply for release:managed tag

Hey folks, I'd like the release management team to take on releases of Kolla. This means applying for the release:managed[1] tag. Please vote +1 if you wish to proceed, or -1 if you don't wish to proceed. The most complex part of this change will be that when feature freeze happens, we must

Re: [openstack-dev] [release] the meaning of the release:managed tag now that everything is released:managed

On 6/30/16, 10:22 AM, "Jeremy Stanley" wrote: >On 2016-06-30 14:07:53 + (+), Steven Dake (stdake) wrote: >[...] >> If it does have some special meaning or requirements beyond the >> "we will freeze on the freeze deadline" could someone enumerate >> those? >[...] >

Re: [openstack-dev] [Cinder] Nominating Scott D'Angelo to Cinder core

On 6/29/2016 10:49 AM, Rosa, Andrea (HP Cloud Services) wrote: One more vote from "not a core member" . I am not a core and I am mainly involved in the Nova project where Scott presence is always useful and valuable when we need to sort out some cinder <-> nova issue. -- Andrea Rosa +1 to

Re: [openstack-dev] [Zaqar] Nominate Thomas Herve for Zaqar core

I'm not core but Thomas helped Puppet OpenStack group many times to get Zaqar working in gate and we highly appreciate his help. Way to go! On Thu, Jun 30, 2016 at 3:18 PM, Fei Long Wang wrote: > Hi team, > > I would like to propose adding Thomas Herve(therve) for the

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Mike Perez's message of 2016-06-30 14:10:30 -0700: > On 09:02 Jun 30, Clint Byrum wrote: > > Excerpts from Mike Perez's message of 2016-06-30 07:50:42 -0700: > > > On 11:31 Jun 20, Clint Byrum wrote: > > > > Excerpts from Joshua Harlow's message of 2016-06-17 15:33:25 -0700: > > > >

Re: [openstack-dev] [mistral][osc-lib][openstackclient] is it too early for orc-lib?

The crux of this, as Dean stated, is if the library wants OSC to always be pulled in (along with its many dependencies). We've seen folks include it in requirements, test-requirements, or even not at all (just document that OSC needs to be installed). I tossed up the idea with the ironic team of

Re: [openstack-dev] [mistral][osc-lib][openstackclient] is it too early for orc-lib?

On Thu, Jun 30, 2016 at 8:38 AM, Hardik wrote: > Regarding osc-lib we have mainly two changes. > > 1) Used "utils" which is moved from openstackclient.common.utils to > osc_lib.utils > 2) We used "command" which wrapped in osc_lib from cliff. > > So I think

Re: [openstack-dev] [all] Proposal: Architecture Working Group

On 09:02 Jun 30, Clint Byrum wrote: > Excerpts from Mike Perez's message of 2016-06-30 07:50:42 -0700: > > On 11:31 Jun 20, Clint Byrum wrote: > > > Excerpts from Joshua Harlow's message of 2016-06-17 15:33:25 -0700: > > > > Thanks for getting this started Clint, > > > > > > > > I'm happy and

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

I'm a bit late to the game here, and others have summed this up excellently, but i'll add my 2c. I think option 2 is the way to go, user and project IDs will absolutely work best as they are immutable. On Fri, Jun 10, 2016 at 4:52 AM, Coles, Alistair wrote: > Thai, > > >

Re: [openstack-dev] [nova][infra][ci] bulk repeating a test job on a single review in parallel ?

On 6/30/2016 8:44 AM, Daniel P. Berrange wrote: A bunch of people in Nova and upstream QEMU teams are trying to investigate a long standing bug in live migration[1]. Unfortuntely the bug is rather non-deterministic - eg on the multinode-live-migration tempest job it has hit 4 times in 7 days,

Re: [openstack-dev] [Cinder] Nominating Scott D'Angelo to Cinder core

On 12:27 Jun 27, Sean McGinnis wrote: > I would like to nominate Scott D'Angelo to core. Scott has been very > involved in the project for a long time now and is always ready to help > folks out on IRC. His contributions [1] have been very valuable and he > is a thorough reviewer [2]. > > Please

Re: [openstack-dev] [Nova] Deprecated Configuration Option in Nova Mitaka Release

On 6/30/2016 12:55 PM, HU, BIN wrote: I see, and thank you very much Dan. Also thank you Markus for unreleased release notes. Now I understand that it is not a plugin and unstable interface. And there is a new "use_neutron" option for configuring Nova to use Neutron as its network backend.

Re: [openstack-dev] [neutron][calico] New networking-calico IRC meeting

On Mon, Jun 20, 2016 at 8:42 AM, Neil Jerram wrote: > Calling everyone interested in networking-calico ...! networking-calico has > been around in the Neutron stadium for a while now, and it's way past time > that we had a proper forum for discussing and evolving it - so I'm

Re: [openstack-dev] [kolla][ironic] My thoughts on Kolla + BiFrost integration

> -Original Message- > From: Steven Dake (stdake) [mailto:std...@cisco.com] > Sent: Monday, June 27, 2016 9:21 PM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [kolla][ironic] My thoughts on Kolla +

[openstack-dev] [Zaqar] Nominate Thomas Herve for Zaqar core

Hi team, I would like to propose adding Thomas Herve(therve) for the Zaqar core team. TBH, I have drafted this mail about 6 months ago, the reason you see this mail until now is because I'm not sure if Thomas can dedicate his time on Zaqar(He is a very busy man). But as you see, I'm wrong. He

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Okay I'll bite. I'm a working owner; Cloud/OpenStack/SDN architect slash OpenStack SI business owner working with companies trying to extract value from technology they don't understand. Or in ways they aren't familiar with. Or with code they don't have time to build/maintain themselves. This

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Mike Perez wrote: On 11:31 Jun 20, Clint Byrum wrote: Excerpts from Joshua Harlow's message of 2016-06-17 15:33:25 -0700: Thanks for getting this started Clint, I'm happy and excited to be involved in helping try to guide the whole ecosystem together (it's also why I like being in oslo) to a

Re: [openstack-dev] Hangzhou Bug Smash will be held from July 6 to 8

Hello Fred, Great event! In which way can we work remotely with the team? Thanks. On Thu, Jun 30, 2016 at 11:05 PM Liyongle (Fred) wrote: > Hi OpenStackers, > > The 4th China OpenStack Bug Smash, hosted by CESI, Huawei, and intel, will > be held in Hangzhou, China from

Re: [openstack-dev] [Nova] Deprecated Configuration Option in Nova Mitaka Release

I see, and thank you very much Dan. Also thank you Markus for unreleased release notes. Now I understand that it is not a plugin and unstable interface. And there is a new "use_neutron" option for configuring Nova to use Neutron as its network backend. When we use Neutron, there are ML2 and

Re: [openstack-dev] [Nova] Deprecated Configuration Option in Nova Mitaka Release

> Just curious - what is the motivation of removing the plug-ability > entirely? Because of significant maintenance effort? It's not a plugin interface and has never been stable. We've had a long-running goal of removing all of these plug points where we don't actually expect people to write

Re: [openstack-dev] [release] the meaning of the release:managed tag now that everything is released:managed

On 2016-06-30 14:07:53 + (+), Steven Dake (stdake) wrote: [...] > If it does have some special meaning or requirements beyond the > "we will freeze on the freeze deadline" could someone enumerate > those? [...] As far as I know it still means that release activities for the deliverable

Re: [openstack-dev] [Nova] Deprecated Configuration Option in Nova Mitaka Release

Dan, Thank you for the information. Just curious - what is the motivation of removing the plug-ability entirely? Because of significant maintenance effort? Thanks Bin -Original Message- From: Dan Smith [mailto:d...@danplanet.com] Sent: Thursday, June 30, 2016 9:52 AM To: OpenStack

Re: [openstack-dev] [octavia][upgrades] upgrade loadbalancer to new amphora image

> On Jun 30, 2016, at 7:15 AM, Ihar Hrachyshka wrote: > >> >> On 30 Jun 2016, at 01:16, Brandon Logan wrote: >> >> Hi Ihar, thanks for starting this discussion. Comments in-line. >> >> After writing my comments in line, I might now realize

Re: [openstack-dev] [lbaas][octavia] suggestion for today's meeting agenda: How to make the Amphora-agent support additional Linux flavors

> On Jun 30, 2016, at 7:01 AM, Ihar Hrachyshka wrote: > > >> On 30 Jun 2016, at 06:03, Kosnik, Lubosz wrote: >> >> Like Doug said Amphora suppose to be a black box. It suppose to get some >> data - like info in /etc/defaults and do everything

Re: [openstack-dev] [Nova] Deprecated Configuration Option in Nova Mitaka Release

> For those deprecated options, does it mean it won’t be supported in > Mitaka and future release at all? Or is there a grace period so that > we, as a user, can gradually transition from Liberty to Mitaka? The deprecation period is usually one cycle for something like this. That means people

Re: [openstack-dev] [Nova] Deprecated Configuration Option in Nova Mitaka Release

On 30.06.2016 18:35, HU, BIN wrote: > Hello Nova team, > > I am a newbie of Nova. I read your documentation > http://docs.openstack.org/mitaka/config-reference/tables/conf-changes/nova.html > regarding new, updated and deprecated options in Mitaka for Compute. I have > a few questions: > > >

[openstack-dev] [DIB][TripleO] Refreshing the DIB specs process

Hello everyone, I believe our DIB specs process is in need of a refresh. Currently, we seem to avoid specs altogether. I think this has worked while we have mostly maintained our status-quo of fixing bugs which pop up and adding fairly straightforward elements. Recently, however, we seem to be

Re: [openstack-dev] [Fuel][Ci] New 'fuel-nailgun' gate job

Hi to all, please be informed that we've enabled voting on mentioned Jenkins jobs For any additional questions please use our #fuel-infra IRC channel On Tue, Jun 7, 2016 at 3:59 PM, Dmitry Kaiharodsev < dkaiharod...@mirantis.com> wrote: > Hi to all, > > please be informed that starting from

Re: [openstack-dev] [TripleO] TripleO deep dive hour?

On Wed, Jun 29, 2016 at 1:01 PM, Jason Rist wrote: > On 06/28/2016 04:00 PM, James Slagle wrote: >> We've got some new contributors around TripleO recently, and I'd like >> to offer up a "TripleO deep dive hour". >> >> The idea is to spend 1 hour a week in a high bandwidth

[openstack-dev] [all][api] POST /api-wg/news

Greetings OpenStack community, A few interesting developments in the API WG this week. The API WG reviewed the new Glance Artifact Repository (aka Glare) API [4]. The team was already adhering to most of the API WG guidelines [3] and after some reviews they were able to get excellent coverage

[openstack-dev] [Nova] Deprecated Configuration Option in Nova Mitaka Release

Hello Nova team, I am a newbie of Nova. I read your documentation http://docs.openstack.org/mitaka/config-reference/tables/conf-changes/nova.html regarding new, updated and deprecated options in Mitaka for Compute. I have a few questions: - For those deprecated options, does it mean

Re: [openstack-dev] [charms] inclusion of charm-helpers (LGPL licensed)

I suspect that the reactive charming model wouldn't have this issue due to the ability to essentially statically link the libraries via wheels/pip packages. If that's the case, it's likely possible to follow along the same lines as the base-layer charm and bootstrap the environment using pip/wheel

Re: [openstack-dev] [Nova] Questions about instance actions' update and finish

On 06/29/2016 09:13 PM, Edward Leafe wrote: On Jun 29, 2016, at 10:05 PM, Matt Riedemann wrote: 2. The updated_at field is also empty, should we sync the updated_at time to the created_at time when we create the action and also update it whenever the action status

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Mike Perez's message of 2016-06-30 07:50:42 -0700: > On 11:31 Jun 20, Clint Byrum wrote: > > Excerpts from Joshua Harlow's message of 2016-06-17 15:33:25 -0700: > > > Thanks for getting this started Clint, > > > > > > I'm happy and excited to be involved in helping try to guide the

[openstack-dev] [neutron][stable] status update and call for action

Hi all, I want to update the community about what’s going on in Neutron stable branches. I also want to share some ideas on how to improve the process going forward, and get some feedback. First, some basic info. - the project currently maintains two stable branches (stable/liberty and

Re: [openstack-dev] Troubleshooting and ask.openstack.org

On Tue, Jun 28, 2016 at 6:49 PM, Steve Martinelli wrote: > I think we want something a bit more organized. > > Morgan tossed the idea of a keystone-docs repo, which could have: > > - The FAQ Adam is asking about > - Install guides (moved over from openstack-manuals) > - A

Re: [openstack-dev] [openstack-infra][project-config] how project config is updated

Puppet would update the repo and trigger changes off of it. Documented here: http://docs.openstack.org/infra/openstackci/third_party_ci.html#updating-your-masterless-puppet-hosts Ramy From: 王华 [mailto:wanghua.hum...@gmail.com] Sent: Thursday, June 30, 2016 9:42 AM To: OpenStack Development

Re: [openstack-dev] [octavia][upgrades] upgrade loadbalancer to new amphora image

Hi Ihar, I think the biggest issue I see with the FIP and new amphora approach is the the persistence tables would be lost. This is not an issue in the Active/Standby scenario, but would be in the failover scenario. Michael On Wed, Jun 29, 2016 at 9:14 AM, Ihar Hrachyshka

Re: [openstack-dev] [FUEL]Network verification failed.

Hello Samer Did you read this reference (https://community.mellanox.com/docs/DOC-2036) ? If you didn’t read it yet, this may be helpful to you. By the way, "Figure 1” which is attached is very cool chart. What the tool did you use to write this figure ?? Yuki Nishiwaki > 2016/06/30 21:01、Samer

[openstack-dev] [fuel] Weekly meeting 6/30 Cancled

Nothing is on the agenda this week, so I'm calling to cancel the meeting. If you have anything to discuss. Please come chat in #fuel or add it to the agenda to discuss next week. https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda -- -- Andrew Woodward Mirantis Fuel Community

[openstack-dev] Hangzhou Bug Smash will be held from July 6 to 8

Hi OpenStackers, The 4th China OpenStack Bug Smash, hosted by CESI, Huawei, and intel, will be held in Hangzhou, China from July 6 to 8 (Beijing time), from 01:00 July 6 to 6:00 July 8 UTC. And the target to get bugs fixed before the milestone newton-2 [1]. Around 50 stackers will fix the

Re: [openstack-dev] [manila] nfs-ganesha export modification issue

Hi, just to provide some context for Alexey's statement > the second one [creating multiple exports (one per client) for an exported resource > [used in current manila's ganesha helper]] ... can easily lead to confusion. Here is how it's been dealt with in the case of Manila's Ganesha helper:

Re: [openstack-dev] [all] Proposal: Architecture Working Group

On 11:31 Jun 20, Clint Byrum wrote: > Excerpts from Joshua Harlow's message of 2016-06-17 15:33:25 -0700: > > Thanks for getting this started Clint, > > > > I'm happy and excited to be involved in helping try to guide the whole > > ecosystem together (it's also why I like being in oslo) to a >

Re: [openstack-dev] [lbaas][octavia] suggestion for today's meeting agenda: How to make the Amphora-agent support additional Linux flavors

Currently agent is in next face of his life. There are some work in progress to change that code. Because of that it’s right timing to discuss about that and find some proper way how to work with this. The biggest issue with Octavia is that there is almost no documentation about what everything

[openstack-dev] [release] the meaning of the release:managed tag now that everything is released:managed

Hey folks, I am keen on tagging Kolla in the governance repository with every tag that is applicable to our project. One of these is release:managed. I've been working as PTL the last 3 cycles to get Kolla processes to the point we could apply for release:managed. Looks like Doug and

Re: [openstack-dev] [openstack-infra][project-config] how project config is updated

On 2016-06-30 21:42:20 +0800 (+0800), 王华 wrote: > After openstack-infra/project-config is updated, for example layout.yaml > for zuul is changed, how the change is applied to the CI system? Is there a > script to trigger this change? I don't find some scripts in the pipeline of > project-config in

[openstack-dev] [nova][infra][ci] bulk repeating a test job on a single review in parallel ?

A bunch of people in Nova and upstream QEMU teams are trying to investigate a long standing bug in live migration[1]. Unfortuntely the bug is rather non-deterministic - eg on the multinode-live-migration tempest job it has hit 4 times in 7 days, while on multinode-full tempest job it has hit ~70

[openstack-dev] [openstack-infra][project-config] how project config is updated

Hi all, After openstack-infra/project-config is updated, for example layout.yaml for zuul is changed, how the change is applied to the CI system? Is there a script to trigger this change? I don't find some scripts in the pipeline of project-config in the layout.yaml to do this work. Do anyone

Re: [openstack-dev] [mistral][osc-lib][openstackclient] is it too early for orc-lib?

Hi, Regarding osc-lib we have mainly two changes. 1) Used "utils" which is moved from openstackclient.common.utils to osc_lib.utils 2) We used "command" which wrapped in osc_lib from cliff. So I think there is no harm in keeping osc_lib. Also, I guess we do not need openstackclient to be

Re: [openstack-dev] [openstack-infra][nodepool] Can the nodes created by nodepool be reused by jenkins jobs?

On 2016-06-30 12:13:01 +0800 (+0800), 王华 wrote: > There is a period between a job is done in Jenkins and the node is > deleted by nodepool. Before the node is deleted, the node can be > seen on Jenkins.How can Jenkins know not to use the node which has > already run a job? Is there a mechanism to

Re: [openstack-dev] [octavia][upgrades] upgrade loadbalancer to new amphora image

> On 30 Jun 2016, at 01:16, Brandon Logan wrote: > > Hi Ihar, thanks for starting this discussion. Comments in-line. > > After writing my comments in line, I might now realize that you're just > talking about documenting a way for a user to do this, and not have

Re: [openstack-dev] [octavia][upgrades] upgrade loadbalancer to new amphora image

> On 29 Jun 2016, at 18:33, Kosnik, Lubosz wrote: > > May you specify what exact use-case you have to upload incompatible images? > In my opinion we should prepare a flow which is like you said building new > instance, configuring everything, adding that amphora into

Re: [openstack-dev] [lbaas][octavia] suggestion for today's meeting agenda: How to make the Amphora-agent support additional Linux flavors

> On 30 Jun 2016, at 06:03, Kosnik, Lubosz wrote: > > Like Doug said Amphora suppose to be a black box. It suppose to get some data > - like info in /etc/defaults and do everything inside on its own. > Everyone will be able to prepare his own implementation of this

Re: [openstack-dev] [openstack-infra] [vitrage] branch marking policy

Thanks! From a brief look, this seems exactly what we need. Elisha From: Joshua Hesketh [mailto:joshua.hesk...@gmail.com] Sent: Thursday, June 30, 2016 3:51 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [openstack-infra] [vitrage] branch marking

Re: [openstack-dev] [requirements][mistral] Library for JWT (JSON Web Token)

Le 2016-06-30 13:07, Renat Akhmerov a écrit : Reason: we need it to provide support for OpenID Connect authentication in Mistral. Can't [1] do the job ? (sorry if I'm off-beat) [1] http://docs.openstack.org/developer/keystone/federation/openidc.html -- Mehdi Abaakouk mail:

Re: [openstack-dev] [openstack-infra] [vitrage] branch marking policy

Hey Elisha, Have you looked at http://docs.openstack.org/infra/manual/drivers.html ? Cheers, Josh On Thu, Jun 30, 2016 at 9:16 PM, Rosensweig, Elisha (Nokia - IL) < elisha.rosensw...@nokia.com> wrote: > Hi, > > We've prepared a (local) branch with Vitrage that is *Liberty-compatible*, > and

[openstack-dev] [manila] nfs-ganesha export modification issue

Hello everyone, here I will briefly summarize an export update problem one will encounter when using nfs-ganesha. While working on a driver that relies on nfs-ganesha I have discovered that it is apparently impossible to provide interruption-free export updates. As of version 2.3 which I am

Re: [openstack-dev] [keystone] [stable/mitaka] Error: Discovering versions from the identity service failed when creating the password plugin....

Hi Tony, Thanks for your reply, its working now :-) Regards, Mohammad Shahid On Fri, Jun 24, 2016 at 8:44 AM, Tony Breeds wrote: > On Tue, Jun 21, 2016 at 10:27:28AM +0530, mohammad shahid wrote: > > Hi, > > > > I am getting below error while starting openstack

Re: [openstack-dev] [Nova] Questions about instance actions' update and finish

On Wed, Jun 29, 2016, at 11:11 PM, Matt Riedemann wrote: > On 6/29/2016 10:10 PM, Matt Riedemann wrote: > > On 6/29/2016 6:40 AM, Andrew Laski wrote: > >> > >> > >> > >> On Tue, Jun 28, 2016, at 09:27 PM, Zhenyu Zheng wrote: > >>> How about I sync updated_at and created_at in my patch, and leave

Re: [openstack-dev] [kolla] Continued support of Fedora as a base platform

2016-06-30 14:07 GMT+02:00 Steven Dake (stdake) : > What really cratered our implementation of fedora was the introduction of > DNF. Prior to that, we led with Fedora. I switched my focus to something > slower moving (CentOS) so I could focus on a properly working RDO rather >

Re: [openstack-dev] [kolla] Continued support of Fedora as a base platform

What really cratered our implementation of fedora was the introduction of DNF. Prior to that, we led with Fedora. I switched my focus to something slower moving (CentOS) so I could focus on a properly working RDO rather then working around the latest and greatest changes. That said, if someone

[openstack-dev] [mistral][osc-lib][openstackclient] is it too early for orc-lib?

Hi, We already let osc-lib in to Mistral but I found out that such transition was blocked in TripleO, [1]. I’d like to ask the team to read into it and discuss whether we need to revert corresponding patches in Mistral or not. [1] https://review.openstack.org/#/c/11/

[openstack-dev] [openstack-infra] [vitrage] branch marking policy

Hi, We've prepared a (local) branch with Vitrage that is *Liberty-compatible*, and would like to mark (tag?) the branch. What is the standard way to do this? Thanks, Elisha Rosensweig, Ph.D. R Director CloudBand, Nokia T: +972 9793 3159

[openstack-dev] [requirements][mistral] Library for JWT (JSON Web Token)

Hi, Does any of the existing OpenStack requirements provide support for JWT? If not, I’d like to propose a new lib into global-requirements.txt, something from: https://pypi.python.org/pypi/PyJWT/1.4.0 (seems to be the best)

Re: [openstack-dev] [kolla] Continued support of Fedora as a base platform

My opinion as one of RDO release wranglers is not to support Fedora for anything else that isn't trunk. It's proven really hard to maintain all dependencies in a good state, and when we managed to do that, an update could break things at any time (like python-pymongo update who was removed because

Re: [openstack-dev] [Fuel] Deprecation of fuel-mirror tool

Please review this patch [1]. It is to remove the code from master branch. We still need test jobs for stable branches. [1] https://review.openstack.org/#/c/335868/ Vladimir Kozhukalov On Mon, Jun 27, 2016 at 1:14 PM, Vladimir Kozhukalov < vkozhuka...@mirantis.com> wrote: > Fuel-mirror python

[openstack-dev] [horizon] The bug list - how to use it, and how to triage

Hello! I just wanted to talk through Horizons bug list ( https://bugs.launchpad.net/horizon/ ), and how to use it to find issues you can help solve or review, as well as how to help triage bugs if you have time to help out. Using the bug list: - The "Tags" section on the right hand side is

[openstack-dev] [monasca] metering interval, global/local

Hi, as far as I can tell, Monasca does not support different metering intervals for different meters. There is the check_freq value in agent.yaml, which is global. Am I right about this? Did you consider the option of specifying check_freq for specific meters? BR, Laszlo

Re: [openstack-dev] [Fuel] Deprecate fuel-upgrade repository

Yet another patch [1] that makes fuel-upgrade read only. [1] https://review.openstack.org/#/c/335841/ Vladimir Kozhukalov On Wed, Jun 29, 2016 at 6:42 PM, Vladimir Kozhukalov < vkozhuka...@mirantis.com> wrote: > This is yet another related patch [1], that removes the code from master > branch

[openstack-dev] [horizon] Keep / Remove 800 UTC Meeting time

Hi everyone, I've mentioned in the past few meetings that attendance for the 800 UTC meeting time has been dwindling. As it stands, there are really only 3 regular attendees (myself included). I think we should consider scrapping it, and just use the 2000 UTC slot each week as a combined

[openstack-dev] [QA] Meeting Thursday June 30th at 9:00 UTC

Hello everyone, Please reminder that the weekly OpenStack QA team IRC meeting will be Thursday, June 30th at 9:00 UTC in the #openstack-meeting channel. The agenda for the meeting can be found here: