Re: [openstack-dev] [OpenStack-Dev][Nova] - https://launchpad.net/bugs/1667794 Changing hostname not to be treated as a pattern instead exact match will be done.

Thanks Matt, Thanks for explaining this well. and bug is being taken care by chris now. Thanks Nidhi -Original Message- From: Matt Riedemann [mailto:mriede...@gmail.com] Sent: Wednesday, July 26, 2017 10:06 PM To: OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [Tacker] Proposing yanxingan for Tacker core

I am proposing we add Yan xingan as a Tacker core. Yanxingan is woking in china mobile, a telecom company which has big requirement on NFV MANO. We are proud of having him on tacker team, and promoting the usage of tacker in his company. In not long time, he has contributed lots on project,

[openstack-dev] [nova] hardware offload support for openvswitch feature exception

Hi all, In the last few week I was working on hardware offload support for openvswitch. The idea is to leverage SR-IOV technology with OVS control plane management. Just last month the ovs community merged all the required patches to enable this feature [1] should be in OVS-2.8.0. I was working

[openstack-dev] [rpm-packaging][karbor] Code review needed!

Hello packaging team and folks, We(Karbor team) need your help to review https://review.openstack.org/#/c/480806/ which adds karbor to rpm-packaging repository. But it always failed in CI tests. It's highly appreciated if anyone could help! Thanks! Jeremy

[openstack-dev] [tripleo][ci] looking for doc reviews with regards to adding ooo check gates

Greetings, I thought it may be helpful if we wrote some instructions for other OpenStack projects with how to add a TripleO job to their projects check gate in a nonvoting or voting capacity. I'm not 100% sure if I'm accurate in my steps or if I'm missing something someone may want to add.

Re: [openstack-dev] [infra] Non-candidacy for Queens cycle Infrastructure PTL

On 2017-07-26 12:55 PM, Jeremy Stanley wrote: On 2017-07-26 11:44:17 -0500 (-0500), Sean McGinnis wrote: Thank you for all your work Jeremy. The fact that most don't think about and aren't aware of all that infra does is a testament to how well things have been running. To quote Ken Keeler

Re: [openstack-dev] [srv-apl-arch:7353] Re: [nova] Discussions for ivshmem support in OpenStack Nova

On 2017/07/27 0:58, Daniel P. Berrange wrote: On Wed, Jul 26, 2017 at 11:53:06AM -0400, Jay Pipes wrote: On 07/26/2017 09:57 AM, Daniel P. Berrange wrote: On Wed, Jul 26, 2017 at 09:50:23AM -0400, Jay Pipes wrote: On 07/26/2017 03:06 AM, TETSURO NAKAMURA wrote: Hi Nova team, It has been

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

On 07/26/2017 07:58 PM, Michael Bayer wrote: On Jul 26, 2017 7:45 PM, "Jay Pipes" > wrote: On 07/26/2017 07:06 PM, Octave J. Orgeron wrote: Hi Michael, On 7/26/2017 4:28 PM, Michael Bayer wrote: it at all.

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

On Jul 26, 2017 7:45 PM, "Jay Pipes" wrote: On 07/26/2017 07:06 PM, Octave J. Orgeron wrote: > Hi Michael, > > On 7/26/2017 4:28 PM, Michael Bayer wrote: > >> >> it at all. >> thinking out loud >> >> oslo_db.sqlalchemy.types.String(255, mysql_small_rowsize=64) >>

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

On 07/26/2017 07:06 PM, Octave J. Orgeron wrote: Hi Michael, On 7/26/2017 4:28 PM, Michael Bayer wrote: it at all. thinking out loud oslo_db.sqlalchemy.types.String(255, mysql_small_rowsize=64) oslo_db.sqlalchemy.types.String(255, mysql_small_rowsize=sa.TINYTEXT)

Re: [openstack-dev] [legal-discuss] [neutron] License issue & Need help

Thank you. That's exactly what we needed. On Wed, Jul 26, 2017 at 8:57 AM, Jeremy Stanley wrote: > On 2017-07-26 03:04:42 + (+), hoan...@vn.fujitsu.com wrote: > > We are recently trying to propose a Netlink solution [1] in order > > to improve performance for

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

On 07/26/2017 07:09 PM, Octave J. Orgeron wrote: Hi Michael, That is something we are working towards having our own CI where we could catch these things. I do think that having a function in the utils module of oslo.db to test the length of a table row would be handy though for projects to

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

[snip] > > I do think a real migration that simply reduces the sizes of selected > columns is the best approach in this case, and that the types like > AutoStringXYZ should go away completely. > > To that end I've proposed reverting the one ndb patchset that has > merged which is the one in

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

On 07/26/2017 07:01 PM, Octave J. Orgeron wrote: Either way though, we'll have to ... still have to deal with any migrations that don't make proper use of oslo.db. Could you elaborate on the above? What about the Nova migrations aren't making proper use of oslo.db? Could you provide an example

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

Hi Michael, That is something we are working towards having our own CI where we could catch these things. I do think that having a function in the utils module of oslo.db to test the length of a table row would be handy though for projects to leverage as part of their unit tests. Octave On

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

Hi Michael, On 7/26/2017 4:28 PM, Michael Bayer wrote: it at all. thinking out loud oslo_db.sqlalchemy.types.String(255, mysql_small_rowsize=64) oslo_db.sqlalchemy.types.String(255, mysql_small_rowsize=sa.TINYTEXT) oslo_db.sqlalchemy.types.String(255, mysql_small_rowsize=sa.TEXT) so if you

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

Hi Michael, Yeah, the data types are the same database wise, it's just the total row size that different between InnoDB and NDB when it comes to table structure. So it's more of a decision point of: A. Change the column size or type across the database types. B. Have a mechanism to

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

On Jul 26, 2017 6:28 PM, "Michael Bayer" wrote: On Wed, Jul 26, 2017 at 6:19 PM, Michael Bayer wrote: > On Wed, Jul 26, 2017 at 5:30 PM, Michael Bayer wrote: >> >> There is a bigger problem with this entire series of changes, whether >>

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

On Wed, Jul 26, 2017 at 6:19 PM, Michael Bayer wrote: > On Wed, Jul 26, 2017 at 5:30 PM, Michael Bayer wrote: >> >> There is a bigger problem with this entire series of changes, whether >> or not the "ndb" keyword is present. Which is that projects need to

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

On Wed, Jul 26, 2017 at 5:30 PM, Michael Bayer wrote: > > There is a bigger problem with this entire series of changes, whether > or not the "ndb" keyword is present. Which is that projects need to > add new columns, tables, and make datatype changes all the time, and > they

Re: [openstack-dev] new contributor

Ha, I knew I was missing a step :) My profile account was set as a "community member" I just changed it to foundation member/level and the form works :) Thanks for the help. 2017-07-26 18:37 GMT-03:00 Jeremy Stanley : > On 2017-07-26 18:21:35 -0300 (-0300), Leonardo Rossetti

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

I realize now that we are in fact going for a total "row size", when I was under the impression that ndb had a simple limit of 64 characters for a VARCHAR. As I was going on the completely wrong assumptions, I'd like to rethink the approach of datatypes. I do think a real migration that simply

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

Hi Michael, Comments below.. On 7/26/2017 1:08 PM, Michael Bayer wrote: On Jul 25, 2017 3:38 PM, "Octave J. Orgeron" > wrote: Hi Michael, I understand that you want to abstract this completely away inside of

Re: [openstack-dev] new contributor

On 2017-07-26 18:21:35 -0300 (-0300), Leonardo Rossetti wrote: > I am trying to sign the individual contributor agreement but the web form > always returns this error message: > > -32603 Cannot store contact information > > Any ideas how should I get it working? I tried to remove all special

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

On Tue, Jul 25, 2017 at 3:27 PM, Octave J. Orgeron wrote: > 5. Evaluated against the other columns in the table, which one makes the > most sense to adjust? well, the above point is one I've been trying to get a straight answer on for a long time. "evaluated against

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

Still working through a full response but wanted to point something important out about something you say below On 07/25/2017 03:27 PM, Octave J. Orgeron wrote: If we really want to remove the complexity here, why don't we just change the sizes and types on these handful of table columns

[openstack-dev] new contributor

Hello, I am trying to sign the individual contributor agreement but the web form always returns this error message: -32603 Cannot store contact information Any ideas how should I get it working? I tried to remove all special chars from the contact field but it didn't work. Thanks.

Re: [openstack-dev] [Cinder] Proposing TommyLikeHu for Cinder core

+1 -Patrick On Tue, Jul 25, 2017 at 1:07 AM, Sean McGinnis wrote: > I am proposing we add TommyLike as a Cinder core. > > DISCLAIMER: We work for the same company. > > I have held back on proposing him for some time because of this conflict. > But > I think from his

Re: [openstack-dev] [Cinder] Requirements for re-adding Gluster support

On 07/26/2017 05:08 PM, John Griffith wrote: > On Wed, Jul 26, 2017 at 10:42 AM, Sean McGinnis > wrote: > >> On Wed, Jul 26, 2017 at 12:30:49PM +, Jeremy Stanley wrote: >>> On 2017-07-26 12:56:55 +0200 (+0200), Niels de Vos wrote: >>> [...] My current guess is

Re: [openstack-dev] [Cinder] Proposing TommyLikeHu for Cinder core

+1 On Wed, Jul 26, 2017 at 8:50 AM, yang, xing wrote: > +1! Tommy is great addition to Cinder core team. > > Thanks, > Xing > > > > > From: Sean McGinnis [sean.mcgin...@gmx.com] > Sent: Tuesday, July 25, 2017 4:07 AM > To:

Re: [openstack-dev] [Cinder] Requirements for re-adding Gluster support

On Wed, Jul 26, 2017 at 10:42 AM, Sean McGinnis wrote: > On Wed, Jul 26, 2017 at 12:30:49PM +, Jeremy Stanley wrote: > > On 2017-07-26 12:56:55 +0200 (+0200), Niels de Vos wrote: > > [...] > > > My current guess is that adding a 3rd party CI [3] for Gluster is > > >

Re: [openstack-dev] Help regarding VM Migration

I am using devstack all in one. But if these configurations are valid with pike, and leads to vm migration somehow, then I can give it a try. Thanks. On Jul 26, 2017 7:52 PM, "Chris Friesen" wrote: > On 07/25/2017 10:21 PM, Ziad Nayyer wrote: > >> Can anybody help

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

On Jul 25, 2017 3:38 PM, "Octave J. Orgeron" wrote: Hi Michael, I understand that you want to abstract this completely away inside of oslo.db. However, the reality is that making column changes based purely on the size and type of that column, without understanding

[openstack-dev] [sahara] Proposing Luigi Toscano, Evgeny Sikachev and Jeremy Freudberg for Sahara core team

Hi folks, With a lot of changes happening along OpenStack we need to update our core team. I'm proposing adding Luigi Toscano, Evgeny Sikachev and Jeremy Freudberg to Sahara core team. The first two, are already sahara-tests core and lately have been doing a lot more than test and addition to

Re: [openstack-dev] [infra] Non-candidacy for Queens cycle Infrastructure PTL

On 2017-07-26 11:44:17 -0500 (-0500), Sean McGinnis wrote: > Thank you for all your work Jeremy. The fact that most don't think > about and aren't aware of all that infra does is a testament to > how well things have been running. To quote Ken Keeler (Futurama production staff writer): When

Re: [openstack-dev] [infra] Non-candidacy for Queens cycle Infrastructure PTL

On Tue, Jul 25, 2017 at 11:37:40PM +, Jeremy Stanley wrote: > It has been a pleasure and a privilege to captain the good ship > Infrastructure for the past four cycles, but it's time to let > someone else take a turn at the wheel. Thank you for all your work Jeremy. The fact that most don't

Re: [openstack-dev] [Cinder] Requirements for re-adding Gluster support

On Wed, Jul 26, 2017 at 12:30:49PM +, Jeremy Stanley wrote: > On 2017-07-26 12:56:55 +0200 (+0200), Niels de Vos wrote: > [...] > > My current guess is that adding a 3rd party CI [3] for Gluster is > > the only missing piece? > [...] > > I thought GlusterFS was free/libre software. If so,

Re: [openstack-dev] [OpenStack-Dev][Nova] - https://launchpad.net/bugs/1667794 Changing hostname not to be treated as a pattern instead exact match will be done.

On 7/26/2017 11:34 AM, Matt Riedemann wrote: On 7/26/2017 11:23 AM, Matt Riedemann wrote: Given this, what else do you need? Please be clear about what your use case is and how it is not solved using the 2.53 microversion. There may need to be changes to the CLI but let's separate that

Re: [openstack-dev] [OpenStack-Dev][Nova] - https://launchpad.net/bugs/1667794 Changing hostname not to be treated as a pattern instead exact match will be done.

On 7/26/2017 11:23 AM, Matt Riedemann wrote: Given this, what else do you need? Please be clear about what your use case is and how it is not solved using the 2.53 microversion. There may need to be changes to the CLI but let's separate that concern from the REST API changes. I think your

Re: [openstack-dev] [OpenStack-Dev][Nova] - https://launchpad.net/bugs/1667794 Changing hostname not to be treated as a pattern instead exact match will be done.

On 7/26/2017 12:24 AM, nidhi.h...@wipro.com wrote: Hello All, This is follow up mail on my y'days mail regarding bug _https://bugs.launchpad.net/python-novaclient/+bug/1667794_ It looks like all the cli commands that are related to http://10.141.67.190:8774/v2.1/os-hypervisors/wipro/servers api

Re: [openstack-dev] [legal-discuss] [neutron] License issue & Need help

On 2017-07-26 03:04:42 + (+), hoan...@vn.fujitsu.com wrote: > We are recently trying to propose a Netlink solution [1] in order > to improve performance for Neutron's Security Group. [...] I answered in the duplicate thread on legal-discuss:

Re: [openstack-dev] [nova] Discussions for ivshmem support in OpenStack Nova

On 07/26/2017 09:57 AM, Daniel P. Berrange wrote: On Wed, Jul 26, 2017 at 09:50:23AM -0400, Jay Pipes wrote: On 07/26/2017 03:06 AM, TETSURO NAKAMURA wrote: Hi Nova team, It has been quite a long time since the last discussion, but let me make sure one thing about the thread below. IIUC,

Re: [openstack-dev] [nova] Discussions for ivshmem support in OpenStack Nova

> -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: Wednesday, July 26, 2017 2:50 PM > To: OpenStack Development Mailing List (not for usage questions) > ; TETSURO NAKAMURA > ; Daniel P. Berrange >

[openstack-dev] [openstack-ansible][security] To firewalld, or not to firewalld

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey there, I'm working through some drafts of a spec[0] (rendered[1]) that aims to deploy software firewalls within an OpenStack-Ansible deployment. The goal is to increase security by restricting lateral movement. One of the questions that was

Re: [openstack-dev] Help regarding VM Migration

On 07/25/2017 10:21 PM, Ziad Nayyer wrote: Can anybody help me out regarding VM migration between two devstacks installed on two different physical machines? Hot or cold? Are you configured as per https://docs.openstack.org/devstack/latest/guides/multinode-lab.html ? Chris

Re: [openstack-dev] [Cinder] Proposing TommyLikeHu for Cinder core

+1! Tommy is great addition to Cinder core team. Thanks, Xing From: Sean McGinnis [sean.mcgin...@gmx.com] Sent: Tuesday, July 25, 2017 4:07 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [Cinder] Proposing TommyLikeHu for Cinder

Re: [openstack-dev] [openstack-ansible] restrictive umask / file permissions in target hosts

On 07/26/2017 07:48 AM, Markus Zoeller wrote: > To close the loop, I've added a bug report to track this effort: > https://bugs.launchpad.net/openstack-ansible/+bug/1706595 > > TBH, I'm not sure when/if I can work on that. I also don't know how the > effort prioritization works within the

Re: [openstack-dev] [Cinder] Requirements for re-adding Gluster support

I believe the previous CI ran on the Openstack CI infrastructure, but was constantly broken and unmaintained (I'm working from memory here). The Cinder team have never cared /where/ the CI is run, and if infra is happy to host the Gluster CI jobs then great. What is needed is somebody to maintain

Re: [openstack-dev] [openstack-ansible] restrictive umask / file permissions in target hosts

On 25.07.2017 16:20, Major Hayden wrote: > On 07/25/2017 08:36 AM, Markus Zoeller wrote: >> A short grep in 'openstack-ansible' shows that the file permissions are >> often not set. I used these commands: >> >> $ grep -n -R "template:" --include \*.yml -A 5 >> $ grep -n -R "copy:" --include \*.yml

Re: [openstack-dev] [Cinder] Requirements for re-adding Gluster support

On 2017-07-26 12:56:55 +0200 (+0200), Niels de Vos wrote: [...] > My current guess is that adding a 3rd party CI [3] for Gluster is > the only missing piece? [...] I thought GlusterFS was free/libre software. If so, won't the Cinder team allow upstream testing in OpenStack's CI system for free

[openstack-dev] [keystone] canceling policy meeting 2017-07-26

Hey all, There isn't anything on the agenda for today's policy meeting [0] and I know several members of the team are wrapping things up for pike-3. As a result, I'm canceling the policy meeting today and we can reconvene next week after the dust settles. Thanks, Lance [0]

[openstack-dev] [QA] Meeting Thursday July 27th at 8:00 UTC

Hello everyone, Please reminder that the weekly OpenStack QA team IRC meeting will be Thursday, July 27th at 8:00 UTC in the #openstack-meeting channel. The agenda for the meeting can be found here: https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_July_27th_2017_.280800_UTC.29

Re: [openstack-dev] [nova] Discussions for ivshmem support in OpenStack Nova

On 07/26/2017 03:06 AM, TETSURO NAKAMURA wrote: Hi Nova team, It has been quite a long time since the last discussion, but let me make sure one thing about the thread below. IIUC, Nova is not welcome ivshmem support because it is no longer supported by DPDK+QEMU. But how would you say if it

Re: [openstack-dev] [infra] Non-candidacy for Queens cycle Infrastructure PTL

Excerpts from Jeremy Stanley's message of 2017-07-25 23:37:40 +: > It has been a pleasure and a privilege to captain the good ship > Infrastructure for the past four cycles, but it's time to let > someone else take a turn at the wheel. I am confident in the ability > of my shipmates to step up

Re: [openstack-dev] [release][freezer][Release-job-failures] Pre-release of openstack/freezer-web-ui failed

Excerpts from jenkins's message of 2017-07-26 13:32:20 +: > Build failed. > > - freezer-web-ui-tarball > http://logs.openstack.org/c1/c151f2ea0c2e6e22d86b38f7916eabd2ce74c5bf/pre-release/freezer-web-ui-tarball/636/ > : FAILURE in 2m 48s > - freezer-web-ui-tarball-signing

Re: [openstack-dev] [infra] Non-candidacy for Queens cycle Infrastructure PTL

On Tue, Jul 25, 2017 at 4:37 PM, Jeremy Stanley wrote: [...] > Thank you all for making it so much > easier than I ever could have anticipated. Thank *you* for your hard work, you're a great leader and excellent in OpenStack community. Thanks for all the help and always

Re: [openstack-dev] [octavia][heat] Octavia deployment with Heat

On Wed, Jul 26, 2017 at 5:34 PM, wrote: > Hello, > > > > Is Octavia (Ocata version) supposed to work with Heat (tested with Newton > version) deployment? I launch a Heat stack trying to deploy a load balancer > with a single listener/pool and two members. While the Heat

Re: [openstack-dev] [tripleo] Proposing Bogdan Dobrelya core on TripleO / Containers

On 21.7.2017 16:55, Emilien Macchi wrote: Hi, Bogdan (bogdando on IRC) has been very active in Containerization of TripleO and his quality of review has increased over time. I would like to give him core permissions on container work in TripleO. Any feedback is welcome as usual, we'll vote as a

Re: [openstack-dev] [Cinder] Requirements for re-adding Gluster support

I think the substantial part was running (and maintaining) the CI. Given the fragility of devstack and tempest, and their dependencies, this is not, unfortunately, a fire-and-forget operation but rather something that requires a fair time investment. Certainly I don't know of any reason other than

[openstack-dev] [octavia][heat] Octavia deployment with Heat

Hello, Is Octavia (Ocata version) supposed to work with Heat (tested with Newton version) deployment? I launch a Heat stack trying to deploy a load balancer with a single listener/pool and two members. While the Heat shows status COMPLETE and the Neutron shows all objects as created, Octavia

[openstack-dev] [Cinder] Requirements for re-adding Gluster support

Hello, In one of the last Cinder releases support for Gluster has been dropped. The commit message [1] mentions that the support has been marked deprecated during Newton. It seems that there are quite some users in the Gluster Community that run OpenStack with Gluster storage. These users did

Re: [openstack-dev] [TripleO][keystone] internal endpoints vs sanity

Hi, > > > > On Mon, Jul 24, 2017 at 10:53 AM, Dmitry Tantsur > wrote: > > > These questions are to the operators, and should be asked on > openstack-operators IMO (maybe with tuning the overall tone to be a bit less > aggressive). > >

Re: [openstack-dev] [TripleO][keystone] internal endpoints vs sanity

On Mon, Jul 24, 2017 at 10:53 AM, Dmitry Tantsur wrote: > These questions are to the operators, and should be asked on > openstack-operators IMO (maybe with tuning the overall tone to be a bit > less aggressive). > So the question looks like this without tuning: - Do you

Re: [openstack-dev] [Massively distributed] Massively scaling OpenStack the P2P way (tech-talk)

On 2017-07-26 10:55, Vinay Yadhav wrote: > Hi, > > We have submitted a tech-talk by the title “Massively scaling OpenStack > the P2P way” which we think is relevant to the Working Group. In the > link below you can find more details on the talk, and if you think it is > interesting, feel free to

[openstack-dev] [Massively distributed] Massively scaling OpenStack the P2P way (tech-talk)

Hi, We have submitted a tech-talk by the title “Massively scaling OpenStack the P2P way” which we think is relevant to the Working Group. In the link below you can find more details on the talk, and if you think it is interesting, feel free to vote.

[openstack-dev] [PTL] [Freezer] Ptl on leave

Hi, I will be on leave starting from this week till a couple of weeks as I need to do a surgery. Pierre-Arthur Mathieu (core developer) will be replacing me during my leave. Best Regards, Saad! __ OpenStack Development

[openstack-dev] [ironic-ui]failed to intall ironic-ui in all in one

Hi, I was failed to install ironic-ui in all-in-one environment as the steps of the [docs]( https://docs.openstack.org/ironic-ui/latest/install/installation.html) say.Some files was not found in my stack,such as ‘./env/bin/active’, ‘run_tests.sh’. I reopen the dashboard,but there

[openstack-dev] [nova] Discussions for ivshmem support in OpenStack Nova

Hi Nova team, It has been quite a long time since the last discussion, but let me make sure one thing about the thread below. IIUC, Nova is not welcome ivshmem support because it is no longer supported by DPDK+QEMU. But how would you say if it is supported out of DPDK-tree and can be used