[openstack-dev] [diskimage-builder] Restarting bi-weekly meeting

Hi, We've let this meeting [1] lapse, to our communications detriment. I will restart it, starting next week [2]. Of course agenda items are welcome, otherwise we will use it as a session to make sure patches are moving in the right direction. If the matter is urgent, and not getting

Re: [openstack-dev] [mistral][freezer] adopting oslo.context for logging debugging and tracing

Thanks Doug. We’ll look into this. @Tuan, is there any roadblocks with the patch you’re working on? [1] [1] https://review.openstack.org/#/c/455407/ Renat On 26 May 2017, 01:54 +0700, Doug Hellmann , wrote: > The new work to add the exception information and request ID

Re: [openstack-dev] [glance] nominating Mike Fedosin for glance core

Welcome back, Mike. On 26/05/17 16:21, Kekane, Abhishek wrote: +1, agree with Nikhil. Abhishek *From:*Nikhil Komawar [mailto:nik.koma...@gmail.com] *Sent:* Friday, May 26, 2017 6:04 AM *To:* OpenStack Development Mailing List (not for usage questions) *Subject:* Re: [openstack-dev] [glance]

Re: [openstack-dev] [glance] nominating Mike Fedosin for glance core

+1, agree with Nikhil. Abhishek From: Nikhil Komawar [mailto:nik.koma...@gmail.com] Sent: Friday, May 26, 2017 6:04 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [glance] nominating Mike Fedosin for glance core This is great news. Always +2 for

Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang

Hi john: I have seen your updates on the bp. I agree with your plan on how to develop the codes. However, there is one issue I have to remind you that at present, Fuxi not only can convert Cinder volume to Docker, but also Manila file. So, do you consider to involve Manila part of

Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang

On Thu, May 25, 2017 at 6:25 PM, Zhipeng Huang wrote: > Hi John and Zeng, > > The OpenSDS community already developed a golang client for the > os-brick[1], I think we could host the new golang os-brick code there as a > new repo and after things settled port the code back

Re: [openstack-dev] [OSC][ironic][mogan] Can we share the same keyword 'baremetal'?

On Thu, May 25, 2017 at 9:37 PM, Loo, Ruby wrote: > Hi Zhenguo, > > > > Thanks for bringing this up. Naming is hard :-( > > > > Maybe this is a dumb question but your phrase "We copied nova's server > resource concept here, so users may easily to accept the 'baremetal >

Re: [openstack-dev] [OSC][ironic][mogan] Can we share the same keyword 'baremetal'?

On Thu, May 25, 2017 at 9:29 PM, Mark Goddard wrote: > On 25 May 2017 at 11:03, Dmitry Tantsur wrote: > >> On 05/25/2017 11:38 AM, Zhenguo Niu wrote: >> >>> >>> On Thu, May 25, 2017 at 4:27 PM, Dmitry Tantsur >>

Re: [openstack-dev] [QA] Proposed changes to the team meeting time

+1, thanks! zhufl Original Mail Sender: ＜andrea.fritt...@gmail.com＞ To: ＜openstack-dev@lists.openstack.org＞ Date: 2017/05/25 21:19 Subject: [openstack-dev] [QA] Proposed changes to the team meeting time Hello team, our current QA team meeting schedule alternates between

Re: [openstack-dev] uWSGI help for Congress

On 5/22/17, 8:54 PM, "gordon chung" wrote: > > >On 22/05/17 05:48 PM, Eric K wrote: >> If someone out there knows uWSGI and has a couple spare cycles to help >> Congress project, we'd super appreciate it. >> >> The regular contributors to Congress don't have experience with uWSGI

[openstack-dev] [upgrades][skip-level][leapfrog] - RFC - Skipping releases when upgrading

Hello Stackers, As I'm sure many of you know there was a talk about doing "skip-level"[0] upgrades at the OpenStack Summit which quite a few folks were interested in. Today many of the interested parties got together and talked about doing more of this in a formalized capacity. Essentially we're

Re: [openstack-dev] uWSGI help for Congress

On 5/23/17, 5:37 AM, "Chris Dent" wrote: >On Mon, 22 May 2017, Eric K wrote: > >> If someone out there knows uWSGI and has a couple spare cycles to help >> Congress project, we'd super appreciate it. >> >> The regular contributors to Congress don't have experience with

Re: [openstack-dev] [QA] Proposed changes to the team meeting time

+1 -gmann On Thu, May 25, 2017 at 10:03 PM, Andrea Frittoli wrote: > Hello team, > > our current QA team meeting schedule alternates between 9:00 UTC and 17:00 > UTC. > The 9:00 meetings is a bit towards the end of the day for out contributors > in APAC, so I'm

Re: [openstack-dev] [keystone][nova][cinder][glance][neutron][horizon][policy] defining admin-ness

I think a option 2 is better. Best Regards Chaoyi Huang (joehuang) From: Lance Bragstad [lbrags...@gmail.com] Sent: 25 May 2017 3:47 To: OpenStack Development Mailing List (not for usage questions); openstack-operat...@lists.openstack.org Subject: Re:

Re: [openstack-dev] [glance] nominating Mike Fedosin for glance core

This is great news. Always +2 for Mike, he's been great (dev, glancer, stacker ..) all the years. Let's not wait so long for reinstatement if folks are on-board, as having another core will only help. On Thu, May 25, 2017 at 11:53 AM, Brian Rosmaita wrote: > As

Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang

Hi John and Zeng, The OpenSDS community already developed a golang client for the os-brick[1], I think we could host the new golang os-brick code there as a new repo and after things settled port the code back to OpenStack [1]

Re: [openstack-dev] [all] Onboarding rooms postmortem, what did you do, what worked, lessons learned

Kendall, Thanks for that pointer and to those who sent emails. I guess the pre-summit time was a bit weird this time around (for many cores/liaisons) and may be the next round we will see someone from Glance participate. Unfortunately, I can't be a Glance liaison at the moment. I hope someone

Re: [openstack-dev] Is the pendulum swinging on PaaS layers?

On 5/23/2017 10:23 AM, Zane Bitter wrote: Yes! Everything is much easier if you tell all the users to re-architect their applications from scratch :) Which, I mean, if you can... great! Meanwhile here on planet Earth, it's 2017 and 95% of payment card transactions are still processed using

Re: [openstack-dev] Is the pendulum swinging on PaaS layers?

On 5/22/2017 11:01 AM, Zane Bitter wrote: If the user does a stack update that changes the network from 'auto' to 'none', or vice-versa. OK I guess we should make this a side discussion at some point, or hit me up in IRC, but if you're requesting networks='none' with microversion >= 2.37

Re: [openstack-dev] [release] Issues with reno

On 5/24/2017 2:46 PM, Doug Hellmann wrote: Please take a look at the results and let me know if that's doing what you all expect. Tested this out locally and it fixes my issue. Thanks Doug! -- Thanks, Matt __ OpenStack

[openstack-dev] [glance] spec to fix a security issue

Hello Glancers, As discussed in today's meeting, I've put up a spec to address OSSN-0075, which is an issue I'd really like to see fixed (or at least better mitigated) in Pike. Please take a look at the patch and leave some comments: https://review.openstack.org/#/c/468179/ cheers, brian

[openstack-dev] [congress] policy library tasks

Hi all! I have organized the tasks for policy library here: https://bugs.launchpad.net/congress/+bugs?field.tag=policy-lib Please take a look and feel free to pick up, comment, modify, etc. The four non-GUI high importance items are essential for rolling out this feature. The high importance GUI

Re: [openstack-dev] Is the pendulum swinging on PaaS layers?

On 05/20/2017 10:36 AM, Monty Taylor wrote: On 05/19/2017 03:13 PM, Monty Taylor wrote: On 05/19/2017 01:53 PM, Sean Dague wrote: On 05/19/2017 02:34 PM, Dean Troyer wrote: On Fri, May 19, 2017 at 1:04 PM, Sean Dague wrote: These should be used as ways to experiment with the

Re: [openstack-dev] [Openstack-operators] [keystone][nova][cinder][glance][neutron][horizon][policy] defining admin-ness

On Thu, May 25, 2017 at 2:36 PM, Marc Heckmann wrote: > First of all @Lance, thanks for taking the time to write and summarize > this for us. It's much appreciated. > Absolutely! it helps me think about it, too. > > While I'm not aware of all the nuances, based on

Re: [openstack-dev] [ptg] ptgbot: how to make "what's currently happening" emerge

Great idea, +1 On Mon, May 22, 2017 at 10:19 AM Thierry Carrez wrote: > Thierry Carrez wrote: > > [...] > > I have POC code for this bot already. Before I publish it (and start > > work to make infra support it), I just wanted to see if this is the > > right direction and

Re: [openstack-dev] [requirements][tripleo][heat] Projects holding back requirements updates

Tagging with tripleo and heat teams for the os-*-config projects. I'm not sure which owns them now, but it sounds like we need a new release. On 05/22/2017 10:32 AM, Matthew Thode wrote: This is just a friendly reminder that without a release from master, if your project still caps a

Re: [openstack-dev] [all] Onboarding rooms postmortem, what did you do, what worked, lessons learned

Thanks Amrith! I added you to our wiki[1] feel free to make changes if any of the info is incorrect. -Kendall(diablo_rojo) [1] https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute On Thu, May 25, 2017 at 7:41 AM Amrith Kumar wrote: > Kendall, > > I would like

[openstack-dev] [mistral][freezer] adopting oslo.context for logging debugging and tracing

The new work to add the exception information and request ID tracing depends on using both oslo.context and oslo.log to have all of the relevant pieces of information available as log messages are emitted. In the course of reviewing the "done" status for those initiatives, I noticed that although

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

Greetings OpenStack community, Today was a relatively short meeting with most the time being devoted to a discussion of Monty Taylor's document chain regarding using the service catalog for version discovery[4]. The group was largely in agreement that work is proceeding well and with a few

Re: [openstack-dev] [nova][vlan trunking] Guest networking configuration for vlan trunk

I created a nova bug for this: https://bugs.launchpad.net/nova/+bug/1693535. I am currently working on a code patch for it. --Robert On 5/24/17, 3:52 PM, "Robert Li (baoli)" > wrote: Thanks for the pointer. I think your suggestion in comments #14

[openstack-dev] [Openstack-dev] [Designate]

Hi everyone, I integrated Designate in Openstack by devstack, now i'm using the new default commands like zone create/delete, etc. I got this problem: +--+---+-++++ | id | name

[openstack-dev] [glance] priorities for the coming week (05/26-06/01)

As discussed at today's Glance meeting, here are the priorities for this week: 0 Glanceclient release We plan to cut a release of the python-glanceclient on Wednesday 31 May. There are two patches outstanding that would be good to have in the release. They need to be merged by 12:00 UTC on

[openstack-dev] [glance] nominating Mike Fedosin for glance core

As you've no doubt read elsewhere on the ML, we've lost several glance cores recently due to employment changes. Luckily, Mike Fedosin informed me at today's Glance weekly meeting that he will have time for the next few months to devote some time to Glance reviewing. For those who don't know

[openstack-dev] [murano][barbican] Encrypting sensitive properties

Hi all, I've been looking at a blueprint[0] logged for Murano which involves encrypting parts of the object model stored in the database that may contain passwords or sensitive information. I wanted to see if people had any thoughts or preferences on how this should be done. On the face of

Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang

On Thu, May 25, 2017 at 5:50 AM, zengchen wrote: > Very sorry to foget attaching the link for bp of rewriting Fuxi with go > language. > https://blueprints.launchpad.net/fuxi/+spec/convert-to-golang > > > At 2017-05-25 19:46:54, "zengchen" wrote: > > Hi

Re: [openstack-dev] Update re: debian packages?

On Thu, May 25, 2017 at 08:30:46AM -0500, Andrew Bogott wrote: > I've just noticed that, as predicted, Mirantis has switched off their > Openstack package repos (e.g. http://liberty-jessie.pkgs.mirantis.com/). > Are there any updates about a replacement repo, or a newly-reconstituted >

[openstack-dev] [oslo][all][logging] logging debugging improvement work status

One outcome from the forum session about improving logging debugging was agreement that the proposal to add more details about exceptions to the logs. The spec [1] was updated and has been approved, and the patches to implement the work in oslo.log have also been approved [2]. The changes should

Re: [openstack-dev] [glance] Stepping Down

Dharini, on behalf of the Glance community, thank you for your service to the project. You were always willing to help out in any way necessary, and your good work is much appreciated. We all wish you luck in your future endeavors, and we hope you'll find some time for Glance again at some

Re: [openstack-dev] [glance] Stepping Down

Hemanth, on behalf of the Glance community, thank you for your long and very productive service to the project. We all wish you luck in your future endeavors, and we hope you'll find some time for Glance again at some point. cheers, brian On Fri, May 19, 2017 at 5:49 PM, Hemanth Makkapati

Re: [openstack-dev] [trove] Trove reboot meeting

The time has come! I have opened the hangout, You can join now! Please only join if you plan on participating in the discussion as there is a limit on these calls. Given the number of people who responded on the doodle poll we should have room for a few extras.

Re: [openstack-dev] [OSC][ironic][mogan] Can we share the same keyword 'baremetal'?

Hi Zhenguo, Thanks for bringing this up. Naming is hard :-( Maybe this is a dumb question but your phrase "We copied nova's server resource concept here, so users may easily to accept the 'baremetal server'" made me wonder. I'm not a user of Mogan so I don't know if this would work, but OSC

[openstack-dev] Update re: debian packages?

I've just noticed that, as predicted, Mirantis has switched off their Openstack package repos (e.g. http://liberty-jessie.pkgs.mirantis.com/). Are there any updates about a replacement repo, or a newly-reconstituted packaging team? I remember being convinced back in February that

Re: [openstack-dev] [OSC][ironic][mogan] Can we share the same keyword 'baremetal'?

On 25 May 2017 at 11:03, Dmitry Tantsur wrote: > On 05/25/2017 11:38 AM, Zhenguo Niu wrote: > >> >> On Thu, May 25, 2017 at 4:27 PM, Dmitry Tantsur > > wrote: >> >> On 05/25/2017 10:20 AM, Zhenguo Niu wrote: >> >>

[openstack-dev] [QA] Proposed changes to the team meeting time

Hello team, our current QA team meeting schedule alternates between 9:00 UTC and 17:00 UTC. The 9:00 meetings is a bit towards the end of the day for out contributors in APAC, so I'm proposing to move the meeting to 8:00 UTC. Please respond with +1 / -1 and/or comments, I will leave the poll

Re: [openstack-dev] [all] Onboarding rooms postmortem, what did you do, what worked, lessons learned

Kendall, I would like to be the Trove liaison, and would like to participate in Upstream University next time around. With that said, the answers to Sean's original question. I ran the room for the Trove team, I think it was a welcome addition. What went well: I think it was a good opportunity

Re: [openstack-dev] [cyborg]Nominate Rushil Chugh and Justin Kilpatrick as new core reviewers

+1 I haven't had time to actively participate these past months but have monitored and agree :) Thanks for your time Harm Sluiman harm.slui...@gmail.com > On May 25, 2017, at 10:24 AM, Zhipeng Huang wrote: > > Hi Team, > > This is an email for nomination of rushil and

Re: [openstack-dev] [ptg] Strawman Queens PTG week slicing

Thierry, Thanks for doing this. Two specific points below. 1. You can schedule Trove for Wednesday and Thursday, skip the Friday. 2. Similar to the idea of splitting the project things from the cross project/infra things, would it be possible to have projects try and keep their project specific

Re: [openstack-dev] [openstack-ansible] mount ceph block from an instance

I doubt many people have tried this, because 1) cinder/nova/glance probably do the job well in a multi-tenant fashion 2) you’re poking holes into your ceph cluster security. Anyway, if you still want it, you would need (I guess) have to create a provider network that will be allowed to access

Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang

Very sorry to foget attaching the link for bp of rewriting Fuxi with go language. https://blueprints.launchpad.net/fuxi/+spec/convert-to-golang At 2017-05-25 19:46:54, "zengchen" wrote: Hi guys: hongbin had committed a bp of rewriting Fuxi with go language[1]. My

[openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang

Hi guys: hongbin had committed a bp of rewriting Fuxi with go language[1]. My question is where to commit codes for it. We have two choice, 1. create a new repository, 2. create a new branch. IMO, the first one is much better. Because there are many differences in the layer of

Re: [openstack-dev] [nova][cinder][barbican] Why is Cinder creating symmetric keys in Barbican for use with encrypted volumes?

On 25-05-17 11:38:44, Duncan Thomas wrote: > On 25 May 2017 at 11:00, Lee Yarwood wrote: > > This has also reminded me that the plain (dm-crypt) format really needs > > to be deprecated this cycle. I posted to the dev and ops ML [2] last > > year about this but received no

Re: [openstack-dev] [nova][cinder][barbican] Why is Cinder creating symmetric keys in Barbican for use with encrypted volumes?

On Thu, May 25, 2017 at 11:38:44AM +0100, Duncan Thomas wrote: > On 25 May 2017 at 11:00, Lee Yarwood wrote: > > This has also reminded me that the plain (dm-crypt) format really needs > > to be deprecated this cycle. I posted to the dev and ops ML [2] last > > year about

Re: [openstack-dev] [nova][cinder][barbican] Why is Cinder creating symmetric keys in Barbican for use with encrypted volumes?

On 25 May 2017 at 11:00, Lee Yarwood wrote: > This has also reminded me that the plain (dm-crypt) format really needs > to be deprecated this cycle. I posted to the dev and ops ML [2] last > year about this but received no feedback. Assuming there are no last > minute

Re: [openstack-dev] [OSC][ironic][mogan] Can we share the same keyword 'baremetal'?

On 05/25/2017 11:38 AM, Zhenguo Niu wrote: On Thu, May 25, 2017 at 4:27 PM, Dmitry Tantsur > wrote: On 05/25/2017 10:20 AM, Zhenguo Niu wrote: hi all, Hi! I'm from the Mogan team, we chose the same keyward

[openstack-dev] [nova][cinder][barbican] Why is Cinder creating symmetric keys in Barbican for use with encrypted volumes?

Hello all, I'm currently working on enabling QEMU's native LUKS support within Nova [1]. While testing this work with Barbican I noticed that Cinder is creating symmetric keys for use with encrypted volumes :

[openstack-dev] [cinder] [nova] How to provide additional options to NFS backend?

Hi, it seems to me that the way of adding extra NFS options to the cinder backend is somewhat confusing. 1. There is nfs_mount_options in cinder config file [1] 2. Then I can put my options to the nfs_shares_config file - that it could contain additional options mentiones [2] or the commit

Re: [openstack-dev] [OSC][ironic][mogan] Can we share the same keyword 'baremetal'?

On Thu, May 25, 2017 at 4:27 PM, Dmitry Tantsur wrote: > On 05/25/2017 10:20 AM, Zhenguo Niu wrote: > >> hi all, >> > > Hi! > > >> I'm from the Mogan team, we chose the same keyward 'baremetal' when >> implementing a OSC plugin [1]. As we think the baremetal command is >>

Re: [openstack-dev] [TripleO] A proposal for hackathon to reduce deploy time of TripleO

On 25.05.2017 0:08, Jeremy Stanley wrote: > On 2017-05-24 16:27:18 -0500 (-0500), Ben Nemec wrote: > [...] >> I spent a _lot_ of time tracking down performance issues and >> optimizing things where I could, and in the end pretty much every >> gain I made was regressed somewhere else within a few

Re: [openstack-dev] [ironic] using keystone right - catalog, endpoints, tokens and noauth

On 05/24/2017 11:46 AM, Pavlo Shchelokovskyy wrote: Hi all, There are several problems or inefficiencies in how we are dealing with auth to other services. Although it became much better in Newton, some things are still to be improved and I like to discuss how to tackle those and my ideas for

Re: [openstack-dev] [OSC][ironic][mogan] Can we share the same keyword 'baremetal'?

On 05/25/2017 10:20 AM, Zhenguo Niu wrote: hi all, Hi! I'm from the Mogan team, we chose the same keyward 'baremetal' when implementing a OSC plugin [1]. As we think the baremetal command is representative of a baremetal resource, not a service, so it makes sense for different projects to

[openstack-dev] [OSC][ironic][mogan] Can we share the same keyword 'baremetal'?

hi all, I'm from the Mogan team, we chose the same keyward 'baremetal' when implementing a OSC plugin [1]. As we think the baremetal command is representative of a baremetal resource, not a service, so it makes sense for different projects to share the top level resource name that OpenStack can

[openstack-dev] [meteos] Meteos Weekly Meeting

Hello Meteos Team and All, Meteos IRC weekly meeting will be held at May.30 Tuesday 13:00-14:00 JST (09:30-10:30 IST). - Tensorflow implementation - Pike release schedule If you have other topics to be discussed in the weekly meeting, please let me know. Meteos is very young