- openstack-discuss - lists.openstack.org

[tc] TC Chair Nominations - closing soon
by Graham Hayes 12 Sep '19

12 Sep '19

Hello all new and returning TC members! Welcome (back) to the TC. We now have to do some of the standard post election paperwork / processes. One of the first things we need to do is elect a chair for this cycle! We currently have 2 nominations, and nominations will remain open until 23:59 UTC tomorrow 12-Sept-2019. At that point, we will start a CIVS election for the chair, and select them. To nominate yourself, just add a review to the governance repo like so : [1][2]. If you are interested in the chair, please do consider running - It is open to everyone, new and less new on the TC, and the job has been documented by previous chairs and TC members [3] If you have any questions - reply to this mail, ask in the #openstack-tc IRC room, reply to me and I will see who I can put you in contact with, who may know, or ping mnaser, who is the current chair. I propose the following timeline: Nominations Close: 2019-09-12 @ 23:59 UTC. Election created: Morning (EU timezone) of 13 Sept Election finish: Evening (EU timezone) of 18 Sept or when all TC members have voted. Thanks all, and please reach out with any questions! - Graham 1 - https://review.opendev.org/#/c/681285/2/reference/members.yaml 2 - https://review.opendev.org/#/c/680414/2/reference/members.yaml 3 - https://opendev.org/openstack/governance/src/branch/master/CHAIR.rst

2 1

Rabbitmq error report
by Md. Farhad Hasan Khan 12 Sep '19

12 Sep '19

Hi, I'm getting this error continuously in rabbitmq log. Though all operation going normal, but slow. Sometimes taking long time to perform operation. Please help me to solve this. rabbitmq version: rabbitmq_server-3.6.16 =ERROR REPORT==== 12-Sep-2019::13:04:55 === Channel error on connection <0.8105.3> (192.168.21.56:60116 -> 192.168.21.11:5672, vhost: '/', user: 'openstack'), channel 1: operation queue.declare caused a channel exception not_found: failed to perform operation on queue 'versioned_notifications.info' in vhost '/' due to timeout =WARNING REPORT==== 12-Sep-2019::13:04:55 === closing AMQP connection <0.8105.3> (192.168.21.56:60116 -> 192.168.21.11:5672 - nova-compute:3493037:e6757c9b-1cdc-43cd-bfd3-dcb58aa4974a, vhost: '/', user: 'openstack'): client unexpectedly closed TCP connection Thanks & B'Rgds, Rony

1 0

[ceph][nova][DR] Openstack DR Setup
by Premdeep S 12 Sep '19

12 Sep '19

Hi Team, We are looking to build a DR infrastructure. Our existing DC setup consists of multiple node Controller, Compute and Ceph nodes as the storage backend. We are using ubuntu 18.04 and Rocky version. Can someone please share any document or guide us on how we can build a DR infra for the existing DC? 1. Do we need to have the storage shared across (Ceph)? 2. What are the dependencies? 3. Is there a guide for the same Thanks Prem

1 1

[qa] forum sessions brainstorming
by Masayuki Igawa 12 Sep '19

12 Sep '19

Hi All, I have created the below etherpad[0] to collect the forum ideas related to QA for Shanghai Summit. Please write up your ideas with your IRC name on the etherpad. [0] https://etherpad.openstack.org/p/PVG-forum-qa-brainstorming -- Masayuki

1 0

[self-healing][autohealing][PTG][Forum] brainstorming etherpads for Shanghai
by Eric K 11 Sep '19

11 Sep '19

Hello healers, The brainstorming etherpads for Self-healing Forum and PTG sessions are up: https://etherpad.openstack.org/p/SHA-self-healing-SIG Please add your topics there. Looking forward to productive discussions in Shanghai!

1 0

How to boot 2 VMs in openstack on same subnet?
by Paul Belanger 11 Sep '19

11 Sep '19

Greetings, We use a few openstack public clouds for testing in the ansible project, specifically using nodepool. We have a use case, where we need to boot 2 VMs on the same public subnet for testing reasons. However, the majority of the clouds we are using, do not have a single subnet for their entire public IP range. Up until now, we boot the 2 VMs, then hope they land on the same subnet, but this isn't really efficient. Basically looking to see if there is a better way to handle this either via openstacksdk or some other configuration we need cloud side. Also note, we'd like to do this with public provider network (which we don't have control over) and avoid using private network for now. Paul

3 3

Re: [rpm-packaging] Proposing new core member
by Nicolas Bock 11 Sep '19

11 Sep '19

On 9/11/19 6:48 AM, Thomas Bechtold wrote: > Hi, > > I would like to nominate Ralf Haferkamp for rpm-packaging core. > Ralf has be active in doing very valuable reviews since some time so I > feel he would be a great addition to the team. > > Please give your +1/-1 in the next days. +1 > Cheers, > > Tom > >

1 0

[rpm-packaging] Proposing new core member
by Thomas Bechtold 11 Sep '19

11 Sep '19

Hi, I would like to nominate Ralf Haferkamp for rpm-packaging core. Ralf has be active in doing very valuable reviews since some time so I feel he would be a great addition to the team. Please give your +1/-1 in the next days. Cheers, Tom

2 1

[sahara] Cancelling Sahara meeting September 12
by Jeremy Freudberg 11 Sep '19

11 Sep '19

Hi all, There will be no Sahara meeting 2019-09-12, the reason being that Luigi is not around and there is not much to discuss anyway. Holler if you need anything. Thanks, Jeremy

1 0

Re: [Horizon] Paging and Angular...
by Marek Lyčka 11 Sep '19

11 Sep '19

Hi, > we need people familiar with Angular and Horizon's ways of using Angular (which seem to be very > non-standard) that would be willing to write and review code. Unfortunately the people who originally > introduced Angular in Horizon and designed how it is used are no longer interested in contributing, > and there don't seem to be any new people able to handle this. I've been working with Horizon's Angular for quite some time and don't mind keeping at it, but it's useless unless I can get my code merged, hence my original message. As far as attracting new developers goes, I think that removing some barriers to entry couldn't hurt - seeing commits simply lost to time being one of them. I can see it as being fairly demoralizing. > Personally, I think that a better long-time strategy would be to remove all > Angular-based views from Horizon, and focus on maintaining one language and one set of tools. Removing AngularJS wouldn't remove JavaScript from horizon. We'd still be left with a home-brewish framework (which is buggy as is). I don't think removing js completely is realistic either: we'd lose functionality and worsen user experience. I think that keeping Angular is the better alternative: 1) A lot of work has already been put into Angularization, solving many problems 2) Unlike legacy js, Angular code is covered by automated tests 3) Arguably, improvments are, on average, easier to add to Angular than pure js implementations Whatever reservations there may be about the current implementation can be identified and addressed, but all in all, I think removing it at this point would be counterproductive. M. čt 5. 9. 2019 v 14:28 odesílatel Radomir Dopieralski <openstack(a)sheep.art.pl> napsal: > Both of your questions have one answer: we need people familiar with > Angular and Horizon's ways of using Angular (which seem to be very > non-standard) that would be willing to write and review code. Unfortunately > the people who originally introduced Angular in Horizon and designed how it > is used are no longer interested in contributing, and there don't seem to > be any new people able to handle this. Personally, I think that a better > long-time strategy would be to remove all Angular-based views from Horizon, > and focus on maintaining one language and one set of tools. > > On Thu, Sep 5, 2019 at 1:52 PM Marek Lyčka <marek.lycka(a)ultimum.io> wrote: > >> Hi all, >> >> I took apart the Horizon paging mechanism while working on [1] and have a >> few of findings: >> >> - Paging is unimplemented/turned off for many (if not most) panels, not >> just Routers and Networks >> - Currently, single page data loads could potentially bump up against API >> hard limits >> - Sorting is also broken in places where paging is enabled (Old >> images...), see [2] >> - The Networks table loads data via three API calls due to neutron API >> limitations, which makes the marker based mechanism unusable >> - There is at least one more minor bug which breaks pagination, there may >> be more >> >> While some of these things may be fixable in different hacky and/or >> inefficient ways, >> we already have Angular implementations which fix many of them and make >> improving >> and fixing the rest easier. >> >> Since Angular ports would help with other unrelated issues as well and >> allow us to >> start deprecating old code, I was wondering two things: >> >> 1) What would it take to increase the priority of Angularization in >> general? >> 2) Can the Code Review process be modified/improved to increase the >> chance for >> Angularization changes to be code reviewed and merged if they do >> happen? >> My previous attempts in this area have failed because of lack of code >> reviewers... >> >> Since full Angularization is still the goal for Horizon as far as I know, >> I'd rather >> spend time doing that than hacking solutions to different problems in >> legacy code >> which is slated deprecation. >> >> Best Regards, >> Marek >> >> [1] https://bugs.launchpad.net/horizon/+bug/1746184 >> [2] https://bugs.launchpad.net/horizon/+bug/1782732 >> >> -- >> Marek Lyčka >> Linux Developer >> >> Ultimum Technologies s.r.o. >> Na Poříčí 1047/26, 11000 Praha 1 >> Czech Republic >> >> marek.lycka(a)ultimum.io <stanislav.ulrych(a)ultimum.io> >> *https://ultimum.io <https://ultimum.io/>* >> > -- Marek Lyčka Linux Developer Ultimum Technologies s.r.o. Na Poříčí 1047/26, 11000 Praha 1 Czech Republic marek.lycka(a)ultimum.io <stanislav.ulrych(a)ultimum.io> *https://ultimum.io <https://ultimum.io/>*

3 3

RE: [winstackers][powervmstackers][tc] removing winstackers and PowerVMStackers from TC governance
by Lucian Petrut 11 Sep '19

11 Sep '19

Hi, I had a chat with my team and we think it would be best if we could keep Winstackers as a separate team. This is mostly because of the associated projects, which are essential for the Windows – Openstack integration effort. Other teams may not be interested in adopting those projects, which would be required if we chose the SIG route. Despite missing this election, I can assure you that we’re quite active in this endeavor. I’m willing to take the PTL role, offloading this task from Claudiu, whose time was quite limited recently. Regards, Lucian Petrut Cloudbase Solutions ________________________________________ From: Mohammed Naser [mnaser(a)vexxhost.com] Sent: Monday, September 09, 2019 3:05 PM To: Thierry Carrez Cc: OpenStack Discuss Subject: Re: [winstackers][powervmstackers][tc] removing winstackers and PowerVMStackers from TC governance On Fri, Sep 6, 2019 at 5:10 AM Thierry Carrez <thierry(a)openstack.org> wrote: > > Divya K Konoor wrote: > > Missing the deadline for a PTL nomination cannot be the reason for > > removing governance. > > I agree with that, but missing the deadline twice in a row is certainly > a sign of some disconnect with the rest of the OpenStack community. > Project teams require a minimal amount of reactivity and presence, so it > is fair to question whether PowerVMStackers should continue as a project > team in the future. > > > PowerVMStackers continue to be an active project > > and would want to be continued to be governed under OpenStack. For PTL, > > an eligible candidate can still be appointed . > > There is another option, to stay under OpenStack governance but without > the constraints of a full project team: PowerVMStackers could be made an > OpenStack SIG. > > I already proposed that 6 months ago (last time there was no PTL nominee > for the team), on the grounds that interest in PowerVM was clearly a > special interest, and a SIG might be a better way to regroup people > interested in supporting PowerVM in OpenStack. > > The objection back then was that PowerVMStackers maintained a number of > PowerVM-related code, plugins and drivers that should ideally be adopted > by their consuming project teams (nova, neutron, ceilometer), and that > making it a SIG would endanger that adoption process. > > I still think it makes sense to consider PowerVMStackers as a Special > Interest Group. As long as the PowerVM-related code is not adopted by > the consuming projects, it is arguably a special interest, and not a > completely-integrated part of OpenStack components. > > The only difference in being a SIG (compared to being a project team) > would be to reduce the amount of mandatory tasks (like designating a PTL > every 6 months). You would still be able to own repositories, get room > at OpenStack events, vote on TC election... > > It would seem to be the best solution in your case. I echo all of this and I think at this point, it's better for the deliverables to be within a SIG. > -- > Thierry Carrez (ttx) > -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

1 0

[sigs][publiccloud][publiccloud-wg][publiccloud-sig] Bi-weekly meeting for the Public Cloud SIG tomorrow
by Tobias Rydberg 11 Sep '19

11 Sep '19

Hi all, It is time for a new meeting for the Public Cloud SIG! Would love to see as many of you there as possible! Topics for the meeting includes Shanghai Forum topics and moving forward on the billing initiative. Time and place: Tomorrow, 12th September at 1400 UTC in #openstack-publiccloud! Agenda can be found at https://etherpad.openstack.org/p/publiccloud-sig Feel free to add topics to the agenda! Cheers, Tobias -- Tobias Rydberg Senior Developer Twitter & IRC: tobberydberg www.citynetwork.eu | www.citycloud.com INNOVATION THROUGH OPEN IT INFRASTRUCTURE ISO 9001, 14001, 27001, 27015 & 27018 CERTIFIED

1 0

[masakari]
by Liam Young 11 Sep '19

11 Sep '19

Hi, I have a patch up for masakari and another for masakari-monitors: https://review.opendev.org/#/c/647756/ https://review.opendev.org/#/c/675734/ If any of the masakari devs have cycles I'd really love to get them landed. Thanks Liam

1 0

[scientific-sig] No IRC meeting today
by Stig Telfer 11 Sep '19

11 Sep '19

Hi all - Apologies, there will not be a Scientific SIG IRC meeting today, due to chair availability. Cheers, Stig

1 0

[all] [tc] [ptls] PDF Goal Update
by Alexandra Settle 11 Sep '19

11 Sep '19

Hi all, According to the Train schedule, this week is the week of "Train Community Goals completed" [1]. In the last few weeks, we've been working hard on the goal to enable PDF support in the project docs. We have successfully completed... 1. Creating a workable solution [2] 2. Communicating this solution via ML [3] As far as the success of the goal is, that has to be measured by the individual teams. But it looks like we're all going really well at implementing the new changes [4]. Thanks to everyone who has jumped in from across the board to make this a success! I wanted to touch base with the teams and gather a status update from the PTLs or project liaisons on where they are at, what questions they may have, and how we (the docs team and TC) can help. Over the next week I will reach out to each team and gather a status update of sorts. Thanks, Alex -- Alexandra Settle <a.settle(a)outlook.com> IRC: asettle [1] https://releases.openstack.org/train/schedule.html#t-goals-complete [2] https://etherpad.openstack.org/p/train-pdf-support-goal [3] http://lists.openstack.org/pipermail/openstack-discuss/2019-August/ 008503.html (amongst others) [4] https://review.opendev.org/#/q/topic:build-pdf-docs

1 0

[nova][glance][entropy][database] update glance metadata for nova instance
by Jordan Ansell 11 Sep '19

11 Sep '19

Hi Openstack Discuss, I have an issue with nova not synchronizing changes between a glance image and it's local image meta information in nova. I have updated a glance image with the property "hw_rng_model=virtio", and that successfully passes that to new instances created using the updated image. However existing instances do not receive this new property. I have located the image metadata within the nova database, in the **instance_system_metadata** table, and can see it's not updated for the existing instances, and only adding the relevant rows for instances that are created when that property is present. The key being "image_hw_rng_model" and "virtio" being the value. Is there a way to tell nova to update the table for existing instances, and synchronizing the two databases? Or is this the kind of thing that would need to be done *shudder* manually...? If so, are there any experts out there who can point me to some documentation on doing this correctly before I go butcher a couple of dummy nova database? Regards, Jordan

3 4

[Watcher] team meeting at 08:00 UTC today
by li.canwei2＠zte.com.cn 11 Sep '19

11 Sep '19

Hi team, Watcher team will have a meeting at 08:00 UTC today in the #openstack-meeting-alt channel. The agenda is available on https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda feel free to add any additional items. Thanks! Canwei Li

1 0

[nova][keystone][neutron][kuryr][requirements] breaking tests with new library versions
by Matthew Thode 11 Sep '19

11 Sep '19

NOVA: lxml===4.4.1 nova tests fail https://bugs.launchpad.net/nova/+bug/1838666 websockify===0.9.0 tempest test failing KEYSTONE: oauthlib===3.1.0 keystone https://bugs.launchpad.net/keystone/+bug/1839393 NEUTRON: tenacity===5.1.1 https://2c976b5e9e9a7bed9985-82d79a041e998664bd1d0bc4b6e78332.ssl.cf2.rackc… this could be caused by pytest===5.1.0 as well KURYR: kubernetes===10.0.1 openshift PINS this, only kuryr-tempest-plugin deps on it https://review.opendev.org/665352 MISC: tornado===5.1.1 salt is cauing this, no eta on fix (same as the last year) stestr===2.5.0 needs merged https://github.com/mtreinish/stestr/pull/265 jsonschema===3.0.2 see https://review.opendev.org/649789 I'm trying to get this in place as we are getting closer to the requirements freeze (sept 9th-13th). Any help clearing up these bugs would be appreciated. -- Matthew Thode

7 18

[tc] monthly meeting summary
by Mohammed Naser 10 Sep '19

10 Sep '19

Hi everyone, The TC held it’s monthly meeting on the 5th of September 2019 and this email provides a summary of that meeting. We contacted Alan to mention that TC will have some presence at the Shanghai leadership meeting alongside other OSF projects on November 3rd, so the day before the summit. Rico is currently working on an etherpad to update SIG guidelines to simplify the process for new SIGs. Once the draft version is done, they will ask SIG chairs to join in the editing part. We still have to contact interested parties for a new ‘large scale’ SIG so we will follow up again on that action item in the next meeting. Graham is currently in the process of testing the code in order to make the proposal bot for propose project-template patches for specific releases. We’re working on adding some forum sessions ideas for the TC and we’ve got volunteers in the forum selection committee. Thierry finished making goal selection a two-step process and it's been merged. There are a few projects that lacked a PTL elected, we’ve discussed the following points for each: - Cyborg: Sundar self-nominated but only on the mailing list, therefore we will appoint them. - Designate: The developers who have expressed interest didn’t have commits, so Graham will sync with both of them to see how if can make it work. - OpenstackSDK: Monty might have missed the notice since they were traveling so Thierry will reach out to him to see if they want to take it again or has suggestions. - I18n: Ian Y. Choi expressed interest but couldn’t run because they were an election official. - {PowerVM,Win}stackers: The code and review activity was quiet and they missed election twice in a row so we proposed to remove them from project teams list and if they want to continue they can as a SIG. - Placement: we are trying to find someone to volunteer by reaching out to Placement and Nova team. We started discussing a change in the process for release names and the rest of that discussion carried over into office hours. I hope that I covered most of what we discussed, for the full meeting logs, you can find them here: http://eavesdrop.openstack.org/meetings/tc/2019/tc.2019-09-05-14.00.log.html Thanks! Regards, Mohammed -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

1 0

Invite Oleg Ovcharuk to join the Mistral Core Team
by András Kövi 10 Sep '19

10 Sep '19

I would like to invite Oleg Ovcharuk <vgvoleg(a)gmail.com> to join the Mistral Core Team. Oleg has been a very active and enthusiastic contributor to the project. He has definitely earned his way into our community. Thank you, Andras

4 4

[tc] weekly update
by Mohammed Naser 10 Sep '19

10 Sep '19

Hi everyone, Here’s the update for what happened in the OpenStack TC this week. You can get more information by checking for changes in openstack/governance repository. # New Projects - os_murano (under openstack-ansible) # General Changes - We made a few improvements while reviewing the separation of goal definition from goal selection: https://review.opendev.org/#/c/677938/ Thanks! Regards, Mohammed -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

1 0

[charms] Retiring charm-neutron-api-genericswitch
by Corey Bryant 10 Sep '19

10 Sep '19

Hi All, I'm going to retire charm-neutron-api-genericswitch today as it is currently not maintained. I've already discussed and received approval to do so from the original author and the current charms PTL, so this serves as a more broad announcement. Thanks, Corey

1 0

[Horizon] Help making custom theme
by Amy Marrich 10 Sep '19

10 Sep '19

For the Grace Hopper Conference's Open Source Day we're doing a Horizon based workshop for OpenStack (running Devstack Pike). The end goal is to have the attendee teams create their own OpenStack theme supporting a humanitarian effort of their choice in a few hours. I've tried modifying the material theme thinking it would be the easiest route to go but that might not be the best way to go about this.:) I've been getting some assistance from e0ne in the Horizon channel and my logo now shows up on the login page, and I had already gotten the SITE_BRAND attributes and the theme itself to show up after changing the local_settings.py. If anyone has some tips or a tutorial somewhere it would be greatly appreciated and I will gladly put together a tutorial for the repo when done. Thanks! Amy (spotz)

3 6

[release][cyborg] os-acc status
by Thierry Carrez 10 Sep '19

10 Sep '19

Hi Cyborgs, One of your deliverables is the os-acc library. It has seen no change over this development cycle and therefore was not released at all in train. We have several options for this library now: 1- It's still very much alive and desired and just has exceptionally not seen much activity during this cycle. We should just cut a stable/train branch from the last release available (0.2.0) and continue in ussuri. 2- It's a valuable library, it just changes extremely rarely. We should make it independent from the release cycle and have it release at its own rhythm. 3- Development has stopped on this, and the library is not useful right now. We should retire this deliverable so that we do not build wrong expectations for our users. Please let us know which option fits the current status of os-acc. -- Thierry Carrez (ttx)

3 4

[placement][ptl][tc] Call for Placement PTL position
by Ghanshyam Mann 10 Sep '19

10 Sep '19

Hello Everyone, With Ussuri Cycle PTL election completed, we left with Placement project as leaderless[1]. In today TC meeting[2], we discussed the few possibilities and decided to reach out to the eligible candidates to serve the PTL position. We would like to know if anyone from Placement core team, Nova core team or PTL (as placement main consumer) of any other interested/related developer is interested to take the PTL position? [1] https://governance.openstack.org/election/results/ussuri/ptl.html [2] http://eavesdrop.openstack.org/meetings/tc/2019/tc.2019-09-05-14.00.log.htm… -TC (gmann)

5 8