September 2020 - openstack-discuss

[nova][dev] Revisiting qemu emulation where guest arch != host arch
by Apsey, Christopher 05 Jan '22

05 Jan '22

All, A few years ago I asked a question[1] about why nova, when given a hw_architecture property from glance for an image, would not end up using the correct qemu-system-xx binary when starting the guest process on a compute node if that compute nodes architecture did not match the proposed guest architecture. As an example, if we had all x86 hosts, but wanted to run an emulated ppc guest, we should be able to do that given that at least one compute node had qemu-system-ppc already installed and libvirt was successfully reporting that as a supported architecture to nova. It seemed like a heavy lift at the time, so it was put on the back burner. I am now in a position to fund a contract developer to make this happen, so the question is: would this be a useful blueprint that would potentially be accepted? Most of the time when people want to run an emulated guest they would just nest it inside of an already running guest of the native architecture, but that severely limits observability and the task of managing any more than a handful of instances in this manner quickly becomes a tangled nightmare of networking, etc. I see real benefit in allowing this scenario to run natively so all of the tooling that exists for fleet management 'just works'. This would also be a significant differentiator for OpenStack as a whole. Thoughts? [1] http://lists.openstack.org/pipermail/openstack-operators/2018-August/015653… Chris Apsey Director | Georgia Cyber Range GEORGIA CYBER CENTER 100 Grace Hopper Lane | Augusta, Georgia | 30901 https://www.gacybercenter.org

2 2

Help with eventlet 0.26.1 and dnspython >= 2
by Thomas Goirand 04 Oct '21

04 Oct '21

Hi, As you may know, eventlet is incompatible with dnspython >= 2.0.0.0rc1. See [1] for the details. However, Debian unstable has 2.0.0. Would there be some good soul willing to help me fix this situation? I would need a patch to fix this, but I'm really not sure how to start. Cheers, Thomas Goirand (zigo)

8 15

[simplification] Making ask.openstack.org read-only
by Thierry Carrez 27 May '21

27 May '21

Hi everyone, This has been discussed several times on this mailing list in the past, but we never got to actually pull the plug. Ask.openstack.org was launched in 2013. The reason for hosting our own setup was to be able to support multiple languages, while StackOverflow rejected our proposal to have our own openstack-branded StackExchange site. The Chinese ask.o.o side never really took off. The English side also never really worked perfectly (like email alerts are hopelessly broken), but we figured it would get better with time if a big community formed around it. Fast-forward to 2020 and the instance is lacking volunteers to help run it, while the code (and our customization of it) has become more complicated to maintain. It regularly fails one way or another, and questions there often go unanswered, making us look bad. Of the top 30 users, most have abandoned the platform since 2017, leaving only Bernd Bausch actively engaging and helping moderate questions lately. We have called for volunteers several times, but the offers for help never really materialized. At the same time, people are asking OpenStack questions on StackOverflow, and sometimes getting answers there[1]. The fragmentation of the "questions" space is not helping users getting good answers. I think it's time to pull the plug, make ask.openstack.org read-only (so that links to old answers are not lost) and redirect users to the mailing-list and the "OpenStack" tag on StackOverflow. I picked StackOverflow since it seems to have the most openstack questions (2,574 on SO, 76 on SuperUser and 430 on ServerFault). We discussed that option several times, but I now proposed a change to actually make it happen: https://review.opendev.org/#/c/746497/ It's always a difficult decision to make to kill a resource, but I feel like in this case, consolidation and simplification would help. Thoughts, comments? [1] https://stackoverflow.com/questions/tagged/openstack -- Thierry

10 18

[stein][neutron] gratuitous arp
by Ignazio Cassano 13 May '21

13 May '21

Hello, I have a problem on stein neutron. When a vm migrate from one node to another I cannot ping it for several minutes. If in the vm I put a script that ping the gateway continously, the live migration works fine and I can ping it. Why this happens ? I read something about gratuitous arp. Please, help me ? Any workaround , please ? Best Regards Ignazio

3 33

[ironic] Announcing deprecation of the iSCSI deploy interface
by Dmitry Tantsur 04 May '21

04 May '21

Hi all, Following up to the previous mailing list [1] and virtual meetup [2] discussions, I would like to announce the plans to deprecate the 'iscsi' deploy interface. This is the updated plan discussed on the virtual meetup: 1) In the Victoria cycle (i.e. right now): - Fill in the detected feature gaps [3]. - Switch off the iscsi deploy interface by default. - Change [agent]image_dowload_source to HTTP by default. - Give the direct deploy a higher priority, so that it's used by default unless disabled. - Mark it as deprecated in the code (causing warnings when enabled). - Release a major version of ironic to highlight the defaults changes. 2) In the W cycle: - Keep the iscsi deploy deprecated. - Listen to operators' feedback. 3) In the X cycle - Remove the iscsi deploy completely from ironic and IPA. - Remove support code from ironic-lib with a major version bump. Please let us know if you have any questions or concerns. Dmitry [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016681.h… [2] https://etherpad.opendev.org/p/Ironic-Victoria-midcycle [3] https://storyboard.openstack.org/#!/story/2008075 -- Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill

1 1

Re: [openstack-dev] Are we ready to put stable/ocata into extended maintenance mode?
by Alex Schultz 03 Mar '21

03 Mar '21

On Tue, Sep 18, 2018 at 1:30 PM Alex Schultz <aschultz(a)redhat.com> wrote: > > On Tue, Sep 18, 2018 at 1:27 PM, Matt Riedemann <mriedemos(a)gmail.com> wrote: > > The release page says Ocata is planned to go into extended maintenance mode > > on Aug 27 [1]. There really isn't much to this except it means we don't do > > releases for Ocata anymore [2]. There is a caveat that project teams that do > > not wish to maintain stable/ocata after this point can immediately end of > > life the branch for their project [3]. We can still run CI using tags, e.g. > > if keystone goes ocata-eol, devstack on stable/ocata can still continue to > > install from stable/ocata for nova and the ocata-eol tag for keystone. > > Having said that, if there is no undue burden on the project team keeping > > the lights on for stable/ocata, I would recommend not tagging the > > stable/ocata branch end of life at this point. > > > > So, questions that need answering are: > > > > 1. Should we cut a final release for projects with stable/ocata branches > > before going into extended maintenance mode? I tend to think "yes" to flush > > the queue of backports. In fact, [3] doesn't mention it, but the resolution > > said we'd tag the branch [4] to indicate it has entered the EM phase. > > > > 2. Are there any projects that would want to skip EM and go directly to EOL > > (yes this feels like a Monopoly question)? > > > > I believe TripleO would like to EOL instead of EM for Ocata as > indicated by the thead > http://lists.openstack.org/pipermail/openstack-dev/2018-September/134671.ht… > Bringing this backup to see what we need to do to get the stable/ocata branches ended for the TripleO projects. I'm bringing this up because we have https://review.openstack.org/#/c/647009/ which is for the upcoming rename but CI is broken and we have no interest in continue to keep the stable/ocata branches alive (or fix ci for them). Thanks, -Alex > Thanks, > -Alex > > > [1] https://releases.openstack.org/ > > [2] > > https://docs.openstack.org/project-team-guide/stable-branches.html#maintena… > > [3] > > https://docs.openstack.org/project-team-guide/stable-branches.html#extended… > > [4] > > https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.… > > > > -- > > > > Thanks, > > > > Matt > > > > __________________________________________________________________________ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

5 11

[largescale-sig] OpenStack DB Archiver
by Arnaud Morin 10 Feb '21

10 Feb '21

Hello large-scalers! TLDR: we opensource a tool to help reducing size of databases. See https://github.com/ovh/osarchiver/ Few months ago, we released a tool, name osarchiver, which we are using on our production environment (at OVH) to help reduce the size of our tables in mariadb (or mysql) In fact, some tables are well know to grow very quickly. We use it, for example, to clean the OpenStack mistral database from old tasks, actions and executions which are older than a year. Another use case could be to archive some data in another table (e.g. with _archived as suffix) if they are 6 months old, and delete this data after 1 year. The source code of this tool is available here: https://github.com/ovh/osarchiver/ We were wondering if some other users would be interested in using the tool, and maybe move it under the opendev governance? Feel free to contact us and/or answer this thread. Cheers, -- Arnaud, Pierre-Samuel and OVH team

12 18

[qa][tempest] Update language in tempest code base
by Arx Cruz 05 Jan '21

05 Jan '21

Hello, I would like to start a discussion regarding the topic. At this moment in time we have an opportunity to be a more open and inclusive project by eliminating outdated naming conventions from tempest codebase, such as blacklist, whitelist. We should take the opportunity and do our best to replace outdated terms with their more inclusive alternatives. As you can see in [1] the TripleO project is already working on this initiative, and I would like to work on this as well on the tempest side. Any thoughts? Shall I start with a sepc, adding deprecation warnings? [1] https://review.opendev.org/#/c/740013/1/specs/victoria/renaming_rules.rst Kind regards, -- Arx Cruz Software Engineer Red Hat EMEA <https://www.redhat.com> arxcruz(a)redhat.com @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

6 9

[placement][nova][cinder][neutron][blazar] Placement governance switch(back)
by Stephen Finucane 03 Nov '20

03 Nov '20

Placement has been a separate project with its own governance since Stein [1]. Since then, the main drivers behind the separation have moved onto pastures new and with Tetsuro sadly declaring his non- candidacy for the PTL position for Wallaby [2], we're left in the unenviable position of potentially not having a PTL for the Wallaby cycle. As such, it's probably time to discuss the future of Placement governance. Assuming no one steps forward for the Placement PTL role, it would appear to me that we have two options. Either we look at transitioning Placement to a PTL-less project, or we move it back under nova governance. To be honest, given how important placement is to nova and other projects now, I'm uncomfortable with the idea of not having a point person who is ultimately responsible for things like cutting a release (yes, delegation is encouraged but someone needs to herd the cats). At the same time, I do realize that placement is used by more that nova now so nova cores and what's left of the separate placement core team shouldn't be the only ones making this decision. So, assuming the worst happens and placement is left without a PTL for Victoria, what do we want to do? Stephen PS: Apologies if I missed other projects with an interest in placement. I did try to catch them all /o\ [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002575… [2] http://lists.openstack.org/pipermail/openstack-discuss/2020-September/01749…

8 10

Fwd: [MURANO] DevStack Murano "yaql_function" Error
by İzzettin Erdem 01 Nov '20

01 Nov '20

Thanks Andy. Regards. Forwarded Conversation Subject: [MURANO] DevStack Murano "yaql_function" Error ------------------------ Gönderen: Andy Botting <andy(a)andybotting.com> Date: 30 Nis 2020 Per, 14:13 To: İzzettin Erdem <root.mch(a)gmail.com> Cc: Rong Zhu <aaronzhu1121(a)gmail.com>, < openstack-discuss(a)lists.openstack.org> Hi İzzettin, Thanks for your interest. Complete log link is at below. It is happening > when i try to deploy or update an environment. > > http://paste.openstack.org/show/792444/ > I've encountered the error AttributeError: 'method' object has no attribute '__yaql_function__' in our environment recently. I believe it started after we upgraded to the Stein release. I haven't tracked it down yet, but calls to the YAQL function: std:Project.getEnvironmentOwner() in a Murano app seem to generate it. It's good to know that at least someone else has reproduced this. cheers, Andy ---------- Gönderen: İzzettin Erdem <root.mch(a)gmail.com> Date: 2 May 2020 Cmt, 16:08 To: Andy Botting <andy(a)andybotting.com> Hi Andy, I solved this problem, it is happening when you try to create or update an environment on existing network. If you change the network with "create new" parameter, it stuck on "creating -or updating- environment" state and after that throws connection error. So i searched Murano network errors and i found this: https://docs.oracle.com/cd/E73172_01/E73173/html/issue-21976631.html. I applied these steps and i created successfully an environment just only with "create new" network parameter. After all these, i realized my devstack environment has no internet connection and because of this murano-agent could not install. So i tried to install Murano on my OSA stable/train test environment and i came with success until last step. Murano-agent installed but this time agent could not connect to rabbitmq instance. I discussed this with OSA IRC channel and i think i have to struggle with this for a long time. Apologize for this long mail but i wanted to inform you. Thanks. Regards. ---------- Gönderen: Andy Botting <andy(a)andybotting.com> Date: 3 May 2020 Paz, 14:24 To: İzzettin Erdem <root.mch(a)gmail.com> Hi İzzettin, Glad you got it sorted. I think you've probably just worked around the issue. Using your new method, you're probably just avoiding the std:Project.getEnvironmentOwner YAQL call now. I've also worked around it in our environment, but I'd like to solve it properly. When I get some time to look into it properly, I'll let you know. cheers, Andy

3 3

[Neutron] no L3 meeting this week (2020-June-01)
by LIU Yulong 28 Oct '20

28 Oct '20

Hi there, Due to the PTG meetings this week, we will cancel the L3 meeting this week. See you guys online next week. Regards, LIU Yulong

1 2

[tc][all] Wallaby Cycle Community Goals
by Graham Hayes 27 Oct '20

27 Oct '20

Hi All It is that time of year / release again - and we need to choose the community goals for Wallaby. Myself and Nate looked over the list of goals [1][2][3], and we are suggesting one of the following: - Finish moving legacy python-*client CLIs to python-openstackclient - Move from oslo.rootwrap to oslo.privsep - Implement the API reference guide changes - All API to provide a /healthcheck URL like Keystone (and others) provide Some of these goals have champions signed up already, but we need to make sure they are still available to do them. If you are interested in helping drive any of the goals, please speak up! We need to select goals in time for the new release cycle - so please reply if there is goals you think should be included in this list, or not included. Next steps after this will be helping people write a proposed goal and then the TC selecting the ones we will pursue during Wallaby. Additionally, we have traditionally selected 2 goals per cycle - however with the people available to do the work across projects Nate and I briefly discussed reducing that to one for this cycle. What does the community think about this? Thanks, Graham 1 - https://etherpad.opendev.org/p/community-goals 2 - https://governance.openstack.org/tc/goals/proposed/index.html 3 - https://etherpad.opendev.org/p/community-w-series-goals 4 - https://governance.openstack.org/tc/goals/index.html#goal-selection-schedule

7 16

[keystone][ptg] Keystone vPTG Planning
by Kristi Nikolla 26 Oct '20

26 Oct '20

Hi all, I have started a doodle poll for scheduling our sessions during the vPTG. Please fill it out by September 10. [0] The etherpad that we are using for brainstorming the topics is [1]. Please fill it out with anything you would like us to schedule time for. More information on the vPTG and links to register can be found at [2]. [0]. https://doodle.com/poll/czgyuwepxk348vqq [1]. https://etherpad.opendev.org/p/keystone-wallaby-ptg [2]. https://www.openstack.org/ptg/

2 1

OpenStack user survey data available?
by Bernd Bausch 23 Oct '20

23 Oct '20

Is there a way to get access to raw user survey data? Some of the graphical data on the analytics page <https://www.openstack.org/analytics> is unreadable, in particular information about Neutron's drivers: The analytics FAQ tells me to contact heidijoy(a)openstack.org <mailto:heidijoy@openstack.org> for questions, but email to this address bounces back. 550 5.1.1 <heidijoy(a)openstack.org>: Email address could not be found, or was misspelled (G8) Thanks much, Bernd

5 9

[tripleo][ironic] fails to introspect: my fsm encountered an exception
by Ruslanas Gžibovskis 19 Oct '20

19 Oct '20

Hi all, I have a clean undercloud deployment. but when I add a node, it fails to introspect. in ironic logs I see interesting lines about FSM (what is it?) [1] and in the same paste, I have provided/pasted, how openstack overcloud node import instack.json looks like. [1] http://paste.openstack.org/show/uPwWVYlO3UQbrF0WzDFH/ -- Ruslanas Gžibovskis +370 6030 7030

3 14

[Keystone] 'list' object has no attribute 'get'
by Tony Liu 15 Oct '20

15 Oct '20

Is this known issue with openstack-keystone-17.0.0-1.el8.noarch? 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context [req-3bcdd315-1975-4d8a-969d-166dd3e8a3b6 113ee63a9ed0466794e24d069efc302c 4c142a681d884010ab36a7ac687d910c - default default] 'list' object has no attribute 'get': AttributeError: 'list' object has no attribute 'get' 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context Traceback (most recent call last): 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/keystone/server/flask/request_processing/middleware/auth_context.py", line 103, in _inner 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context return method(self, request) 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/keystone/server/flask/request_processing/middleware/auth_context.py", line 353, in process_request 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context resp = super(AuthContextMiddleware, self).process_request(request) 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/keystonemiddleware/auth_token/__init__.py", line 411, in process_request 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context allow_expired=allow_expired) 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/keystonemiddleware/auth_token/__init__.py", line 445, in _do_fetch_token 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context data = self.fetch_token(token, **kwargs) 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/keystone/server/flask/request_processing/middleware/auth_context.py", line 248, in fetch_token 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context token, access_rules_support=ACCESS_RULES_MIN_VERSION) 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/keystone/common/manager.py", line 115, in wrapped 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context __ret_val = __f(*args, **kwargs) 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/keystone/token/provider.py", line 145, in validate_token 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context token = self._validate_token(token_id) 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "</usr/lib/python3.6/site-packages/decorator.py:decorator-gen-26>", line 2, in _validate_token 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/dogpile/cache/region.py", line 1360, in get_or_create_for_user_func 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context key, user_func, timeout, should_cache_fn, (arg, kw) 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/dogpile/cache/region.py", line 962, in get_or_create 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context async_creator, 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/dogpile/lock.py", line 187, in __enter__ 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context return self._enter() 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/dogpile/lock.py", line 94, in _enter 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context generated = self._enter_create(value, createdtime) 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/dogpile/lock.py", line 180, in _enter_create 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context return self.creator() 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/dogpile/cache/region.py", line 916, in gen_value 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context *creator_args[0], **creator_args[1] 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/keystone/token/provider.py", line 179, in _validate_token 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context token.mint(token_id, issued_at) 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/keystone/models/token_model.py", line 579, in mint 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context self._validate_token_resources() 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/keystone/models/token_model.py", line 471, in _validate_token_resources 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context if self.project and not self.project_domain.get('enabled'): 2020-09-10 09:35:53.638 28 ERROR keystone.server.flask.request_processing.middleware.auth_context AttributeError: 'list' object has no attribute 'get' Thanks! Tony

2 1

[oslo] Project leadership
by Ben Nemec 15 Oct '20

15 Oct '20

Hi all, As you may have noticed, we had no nominees for Oslo PTL again this cycle. I said in my non-candidacy email that I don't think it would be appropriate for me to continue in the position given the lack of attention I've been paying over the past couple of cycles. My feelings on that have not changed, so we need to figure out what we're going to do from here on. The general consensus from the people I've talked to seems to be a distributed model. To kick off that discussion, here's a list of roles that I think should be filled in some form: * Release liaison * Security point-of-contact * TC liaison * Cross-project point-of-contact * PTG/Forum coordinator * Meeting chair * Community goal liaison (almost forgot this one since I haven't actually been doing it ;-). I've probably missed a few, but those are the the ones I came up with to start. Obviously there's overlap between some of them, and we don't have that many people on the team so there's going to be some combined roles. It's also possible some roles could be handled cooperatively by the team (we already have a coresec team, for example), but in general I favor explicit assignments over vague "somebody will do it" statements. That said, given my reduced role on the team I don't know how much say I get in the matter. :-) Anyway, I wanted to get this sent out because I'm going to be out on PTO next week so I won't be available for the meeting. Feel free to discuss it in my absence though. Thanks. -Ben

7 8

[Magnum][kolla-ansible][kayobe] Information gathering for 2 blocking issues
by Tony Pearce 09 Oct '20

09 Oct '20

Hi all, hope you are all keeping safe and well. I am looking for information on the following two issues that I have which surrounds Magnum project: 1. Magnum does not support Openstack API with HTTPS 2. Magnum forces compute nodes to consume disk capacity for instance data My environment: Openstack Train deployed using Kayobe (Kolla-ansible). With regards to the HTTPS issue, Magnum stops working after enabling HTTPS because the certificate / CA certificate is not trusted by Magnum. The certificate which I am using is one that was purchased from GoDaddy and is trusted in web browsers (and is valid), just not trusted by the Magnum component. Regarding compute node disk consumption issue - I'm at a loss with regards to this and so I'm looking for more information about why this is being done and is there any way that I could avoid it? I have storage provided by a Cinder integration and so the consumption of compute node disk for instance data I need to avoid. Any information the community could provide to me with regards to the above would be much appreciated. I would very much like to use the Magnum project in this deployment for Kubernetes deployment within projects. Thanks in advance, Regards, Tony

3 9

[Octavia] Please help with amphorav2 provider populate db command
by Bujack, Stefan 08 Oct '20

08 Oct '20

Hello, I think I need a little help again with the configuration of the amphora v2 provider. I get an error when I try to populate the database. It seems that the name of the localhost is used for the DB host and not what I configured in octavia.conf as DB host root@octavia04:~# octavia-db-manage --config-file /etc/octavia/octavia.conf upgrade_persistence 2020-09-29 11:45:01.911 818313 WARNING taskflow.persistence.backends.impl_sqlalchemy [-] Engine connection (validate) failed due to '(pymysql.err.OperationalError) (1045, "Access denied for user 'octavia'@'octavia04.desy.de' (using password: YES)") (Background on this error at: http://sqlalche.me/e/e3q8)' 2020-09-29 11:45:01.912 818313 CRITICAL octavia-db-manage [-] Unhandled error: sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (1045, "Access denied for user 'octavia'@'octavia04.desy.de' (using password: YES)") (Background on this error at: http://sqlalche.me/e/e3q8) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage Traceback (most recent call last): 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 2276, in _wrap_pool_connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return fn() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 303, in unique_connection 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return _ConnectionFairy._checkout(self) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 760, in _checkout 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage fairy = _ConnectionRecord.checkout(pool) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 492, in checkout 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage rec = pool._do_get() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/impl.py", line 139, in _do_get 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage self._dec_overflow() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/util/langhelpers.py", line 68, in __exit__ 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage compat.reraise(exc_type, exc_value, exc_tb) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 153, in reraise 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage raise value 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/impl.py", line 136, in _do_get 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return self._create_connection() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 308, in _create_connection 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return _ConnectionRecord(self) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 437, in __init__ 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage self.__connect(first_connect_check=True) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 639, in __connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage connection = pool._invoke_creator(self) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/strategies.py", line 114, in connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return dialect.connect(*cargs, **cparams) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 482, in connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return self.dbapi.connect(*cargs, **cparams) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/__init__.py", line 94, in Connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return Connection(*args, **kwargs) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/connections.py", line 325, in __init__ 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage self.connect() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/connections.py", line 599, in connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage self._request_authentication() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/connections.py", line 861, in _request_authentication 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage auth_packet = self._read_packet() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/connections.py", line 684, in _read_packet 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage packet.check_error() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/protocol.py", line 220, in check_error 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage err.raise_mysql_exception(self._data) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/err.py", line 109, in raise_mysql_exception 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage raise errorclass(errno, errval) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage pymysql.err.OperationalError: (1045, "Access denied for user 'octavia'@'octavia04.desy.de' (using password: YES)") 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage The above exception was the direct cause of the following exception: 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage Traceback (most recent call last): 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/local/bin/octavia-db-manage", line 8, in <module> 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage sys.exit(main()) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/local/lib/python3.8/dist-packages/octavia/db/migration/cli.py", line 156, in main 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage CONF.command.func(config, CONF.command.name) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/local/lib/python3.8/dist-packages/octavia/db/migration/cli.py", line 98, in do_persistence_upgrade 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage persistence.initialize() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/local/lib/python3.8/dist-packages/octavia/controller/worker/v2/taskflow_jobboard_driver.py", line 50, in initialize 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage with contextlib.closing(backend.get_connection()) as connection: 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/taskflow/persistence/backends/impl_sqlalchemy.py", line 335, in get_connection 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage conn.validate(max_retries=self._max_retries) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/taskflow/persistence/backends/impl_sqlalchemy.py", line 394, in validate 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage _try_connect(self._engine) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/tenacity/__init__.py", line 311, in wrapped_f 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return self.call(f, *args, **kw) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/tenacity/__init__.py", line 391, in call 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage do = self.iter(retry_state=retry_state) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/tenacity/__init__.py", line 338, in iter 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return fut.result() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3.8/concurrent/futures/_base.py", line 432, in result 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return self.__get_result() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3.8/concurrent/futures/_base.py", line 388, in __get_result 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage raise self._exception 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/tenacity/__init__.py", line 394, in call 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage result = fn(*args, **kwargs) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/taskflow/persistence/backends/impl_sqlalchemy.py", line 391, in _try_connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage with contextlib.closing(engine.connect()): 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 2209, in connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return self._connection_cls(self, **kwargs) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 103, in __init__ 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage else engine.raw_connection() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 2306, in raw_connection 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return self._wrap_pool_connect( 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 2279, in _wrap_pool_connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage Connection._handle_dbapi_exception_noconnection( 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1547, in _handle_dbapi_exception_noconnection 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage util.raise_from_cause(sqlalchemy_exception, exc_info) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 398, in raise_from_cause 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage reraise(type(exception), exception, tb=exc_tb, cause=cause) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 152, in reraise 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage raise value.with_traceback(tb) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 2276, in _wrap_pool_connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return fn() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 303, in unique_connection 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return _ConnectionFairy._checkout(self) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 760, in _checkout 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage fairy = _ConnectionRecord.checkout(pool) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 492, in checkout 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage rec = pool._do_get() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/impl.py", line 139, in _do_get 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage self._dec_overflow() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/util/langhelpers.py", line 68, in __exit__ 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage compat.reraise(exc_type, exc_value, exc_tb) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 153, in reraise 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage raise value 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/impl.py", line 136, in _do_get 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return self._create_connection() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 308, in _create_connection 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return _ConnectionRecord(self) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 437, in __init__ 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage self.__connect(first_connect_check=True) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 639, in __connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage connection = pool._invoke_creator(self) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/strategies.py", line 114, in connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return dialect.connect(*cargs, **cparams) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 482, in connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return self.dbapi.connect(*cargs, **cparams) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/__init__.py", line 94, in Connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return Connection(*args, **kwargs) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/connections.py", line 325, in __init__ 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage self.connect() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/connections.py", line 599, in connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage self._request_authentication() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/connections.py", line 861, in _request_authentication 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage auth_packet = self._read_packet() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/connections.py", line 684, in _read_packet 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage packet.check_error() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/protocol.py", line 220, in check_error 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage err.raise_mysql_exception(self._data) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/err.py", line 109, in raise_mysql_exception 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage raise errorclass(errno, errval) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (1045, "Access denied for user 'octavia'@'octavia04.desy.de' (using password: YES)") 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage (Background on this error at: http://sqlalche.me/e/e3q8) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage root@octavia04:~# cat /etc/octavia/octavia.conf [DEFAULT] transport_url = rabbit://openstack:password@rabbit-intern.desy.de use_journal = True [api_settings] bind_host = 0.0.0.0 bind_port = 9876 [certificates] cert_generator = local_cert_generator ca_certificate = /etc/octavia/certs/server_ca.cert.pem ca_private_key = /etc/octavia/certs/server_ca.key.pem ca_private_key_passphrase = passphrase [controller_worker] amp_image_owner_id = f89517ee676f4618bd55849477442aca amp_image_tag = amphora amp_ssh_key_name = octaviakey amp_secgroup_list = 2236e82c-13fe-42e3-9fcf-bea43917f231 amp_boot_network_list = 9f7fefc4-f262-4d8d-9465-240f94a7e87b amp_flavor_id = 200 network_driver = allowed_address_pairs_driver compute_driver = compute_nova_driver amphora_driver = amphora_haproxy_rest_driver client_ca = /etc/octavia/certs/client_ca.cert.pem [database] connection = mysql+pymysql://octavia:password@maria-intern.desy.de/octavia [haproxy_amphora] client_cert = /etc/octavia/certs/client.cert-and-key.pem server_ca = /etc/octavia/certs/server_ca.cert.pem [health_manager] bind_port = 5555 bind_ip = 172.16.0.2 controller_ip_port_list = 172.16.0.2:5555 [keystone_authtoken] www_authenticate_uri = https://keystone-intern.desy.de:5000/v3 auth_url = https://keystone-intern.desy.de:5000/v3 memcached_servers = nova-intern.desy.de:11211 auth_type = password project_domain_name = default user_domain_name = default project_name = service username = octavia password = password service_token_roles_required = True [oslo_messaging] topic = octavia_prov [service_auth] auth_url = https://keystone-intern.desy.de:5000/v3 memcached_servers = nova-intern.desy.de:11211 auth_type = password project_domain_name = Default user_domain_name = Default project_name = service username = octavia password = password [task_flow] persistence_connection = mysql+pymysql://octavia:woxSGH45cdZL1Sa4@maria-intern.desy.de/octavia_persistence jobboard_backend_driver = 'redis_taskflow_driver' jobboard_backend_hosts = 10.254.28.113 jobboard_backend_port = 6379 jobboard_backend_password = password jobboard_backend_namespace = 'octavia_jobboard' root@octavia04:~# octavia-db-manage current 2020-09-29 12:02:23.159 819432 INFO alembic.runtime.migration [-] Context impl MySQLImpl. 2020-09-29 12:02:23.160 819432 INFO alembic.runtime.migration [-] Will assume non-transactional DDL. fbd705961c3a (head) We have an Openstack Ussuri deployment on Ubuntu 20.04. Thanks in advance, Stefan Bujack

3 4

[oslo] Proposing Lance Bragstad as oslo.cache core
by Moises Guimaraes de Medeiros 07 Oct '20

07 Oct '20

Hello everybody, It is my pleasure to propose Lance Bragstad (lbragstad) as a new member of the oslo.core core team. Lance has been a big contributor to the project and is known as a walking version of the Keystone documentation, which happens to be one of the biggest consumers of oslo.cache. Obviously we think he'd make a good addition to the core team. If there are no objections, I'll make that happen in a week. Thanks. -- Moisés Guimarães Software Engineer Red Hat <https://www.redhat.com> <https://red.ht/sig>

7 7

Ussuri Octavia load balancer on OVS
by pwm 04 Oct '20

04 Oct '20

Hi, I using the following setup for Octavia load balancer on OVS Ansible openstack_user_config.yml - network: container_bridge: "br-lbaas" container_type: "veth" container_interface: "eth14" host_bind_override: "eth14" ip_from_q: "octavia" type: "flat" net_name: "octavia" group_binds: - neutron_openvswitch_agent - octavia-worker - octavia-housekeeping - octavia-health-manager user_variables.yml octavia_provider_network_name: "octavia" octavia_provider_network_type: flat octavia_neutron_management_network_name: lbaas-mgmt /etc/netplan/50-cloud-init.yaml br-lbaas: dhcp4: no interfaces: [ bond10 ] addresses: [] parameters: stp: false forward-delay: 0 bond10: dhcp4: no addresses: [] interfaces: [ens16] parameters: mode: balance-tlb brctl show bridge name bridge id STP enabled interfaces br-lbaas 8000.d60e4e80f672 no 2ea34552_eth14 bond10 However, I am getting the following error when creating the load balance octavia.amphorae.drivers.haproxy.rest_api_driver [-] Could not connect to instance. Retrying.: requests.exceptions.ConnectionError: HTTPSConnectionPool(host='172.29.233.47', port=9443 The Octavia api container unable to connect to the amphora instance. Any missing configuration, cause I need to manually add in the eth14 interface to the br-lbaas bridge in order to fix the connection issue brctl addif br-lbaas eth14 Thanks

2 9

[election][plt] Hervé Beraud candidacy for Release Management PTL
by Herve Beraud 02 Oct '20

02 Oct '20

Hello everyone, I am submitting my candidacy for Release Management team PTL in the Wallaby cycle. Indeed, I am a core Release Management team member for a few cycles now and I want to involve myself more in this team by proposing me as PTL. During this cycle the main efforts will be around the team building. Indeed, we now have a lot of great tools and automations but we need to recruit new members and mentor them to keep a strong and resilient core team. By recruiting more people we could easily spread the workload on more core members. I plan to dedicate myself on this topic during this cycle. Thanks for your consideration! Hervé -- Hervé Beraud Senior Software Engineer Red Hat - Openstack Oslo irc: hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

2 3

user read-only role not working
by its-openstack＠zohocorp.com 01 Oct '20

01 Oct '20

Dear Openstack, We have deployed openstack train branch. This mail is in regards to the default role in openstack. we are trying to create a read-only user i.e, the said user can only view in the web portal(horizon)/using cli commands. the user cannot create an instance or delete an instance , the same with any resource. we created a user in a project test with reader role, but in horizon/cli able to create and delete instance and similar to other access also if you so kindly help us fix this issue would be grateful. the commands used for creation $ openstack user create --domain default --password-prompt mailto:test-reader@test.com $ openstack role add --project test --user mailto:gowtham.sankar@zohocorp.com reader Thanks and Regards sysadmin

3 2

[cloudkitty][election][ptl] PTL non-candidacy
by Pierre Riteau 01 Oct '20

01 Oct '20

Hello, Late in the Victoria cycle, I volunteered to help with the then inactive CloudKitty project, which resulted in becoming its PTL. While I plan to continue contributing to CloudKitty, I will have very limited availability during the beginning of the Wallaby cycle. In particular, I may not even be able to join the PTG. Thus it would be best if someone else ran for CloudKitty PTL this cycle. If you are interested in nominating yourself but aren't sure what is involved, don't hesitate to reach out to me by email or IRC. Thanks, Pierre Riteau (priteau)

3 4

Should ports created by ironic have PXE parameters after deployment?
by Tyler Bishop 01 Oct '20

01 Oct '20

Hi, My issue is i have a neutron network (not discovery or cleaning) that is adding the PXE entries for the ironic pxe server and my baremetal host are rebooting into discovery upon successful deployment. I am curious how the driver implementation works for adding the PXE options to neutron-dhcp-agent configuration and if that is being done to help non flat networks where no SDN is being used? I have several environments using Kolla-Ansible and this one seems to be the only behaving like this. My neutron-dhcp-agent dnsmasq opt file looks like this after a host is deployed. dhcp/7d0b7e78-6506-4f4a-b524-d5c03e4ca4a8/opts cat /var/lib/neutron/dhcp/ffdf5f9b-b4ad-4a53-b154-69eb3b4a81c5/opts tag:subnet-57b772c1-7878-4458-8c60-cf21eac99ac2,option:dns-server,10.60.3.240,10.60.10.240,10.60.1.240 tag:subnet-57b772c1-7878-4458-8c60-cf21eac99ac2,option:classless-static-route,169.254.169.254/32,10.60.66.2,0.0.0.0/0,10.60.66.1 tag:subnet-57b772c1-7878-4458-8c60-cf21eac99ac2,249,169.254.169.254/32,10.60.66.2,0.0.0.0/0,10.60.66.1 tag:subnet-57b772c1-7878-4458-8c60-cf21eac99ac2,option:router,10.60.66.1 tag:port-08908db1-360b-4973-87c7-15049a484ac6,150,10.60.66.11 tag:port-08908db1-360b-4973-87c7-15049a484ac6,210,/tftpboot/ tag:port-08908db1-360b-4973-87c7-15049a484ac6,66,10.60.66.11 tag:port-08908db1-360b-4973-87c7-15049a484ac6,67,pxelinux.0 tag:port-08908db1-360b-4973-87c7-15049a484ac6,option:server-ip-address,10.60.66.11

7 16

[tc] monthly meeting
by Mohammed Naser 30 Sep '20

30 Sep '20

Hi everyone, Here’s the agenda for our monthly TC meeting. It will happen tomorrow (Thursday the 1st) at 1400 UTC in #openstack-tc and I will be your chair. If you can’t attend, please put your name in the “Apologies for Absence” section. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting * ACTIVE INITIATIVES - Follow up on past action items - OpenStack User-facing APIs and CLIs (belmoreira) - W cycle goal selection start - Completion of retirement cleanup (gmann) https://etherpad.opendev.org/p/tc-retirement-cleanup - Audit and clean-up tags (gmann) - Remove tc:approved-release tag https://review.opendev.org/#/c/749363/ Thanks, Mohammed -- Mohammed Naser VEXXHOST, Inc.

1 0

[election][horizon] PTL candidacy for Wallaby
by Ivan Kolodyazhny 30 Sep '20

30 Sep '20

Hi team, I would like to announce my candidacy for Horizon PTL for the Wallaby cycle. During Victoria cycle we did a good job with stability improvements and feature development but there are still some areas we need to pay attention during Wallaby development cycle: * More cross-project testing. * Find a solution on how to improve UX and make feature gap smaller. * Involve more contributors into the community. Thanks for reading this and helping me making Horizon better during each release, Ivan Kolodyazhny (e0ne)

1 0

[manila] GHC / Canceling the IRC Meeting this week (1st Oct 2020)
by Goutham Pacha Ravi 30 Sep '20

30 Sep '20

Hello Zorillas, A number of us are mentoring attendees of the "Open Source Day" at the Grace Hopper Celebration tomorrow (1st Oct 2020). Since the agenda [1] had no new items, we'll forego the meeting slot and convene next week instead. If there's anything urgent that needs to be discussed, please share your thoughts on #openstack-manila, or as an email here. If you're available tomorrow, and would like to help with GHC as a mentor, please see Amy's email to the list. [2] Thanks, Goutham [1] https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting [2] http://lists.openstack.org/pipermail/openstack-discuss/2020-September/01768…

1 0

[election][charms] PTL candidacy for Wallaby
by Frode Nordahl 30 Sep '20

30 Sep '20

Hello all, I hereby announce my candidacy for PTL for the Charms project. There is a lot of good movement in the community and I'm really excited about what the next cycle might bring. Apologies for missing the nomination deadline. -- Frode Nordahl

1 0

Mentors needed Tomorrow!!!!
by Amy Marrich 30 Sep '20

30 Sep '20

Hey all, Found out over night the OpenStack session at Grace Hopper Conference's Open Source Day has 78 mentees registered and we have 6-8 stackers mentoring through the day. If you've ever wanted to help mentor the next hopeful generation of Stackers please let me know. We are working to adapt our plans for the day and do have the option of sending some to another track but that's not the OpenStack way! Thanks, Amy (spotz)

2 3

[election][telemetry] PTL candidacy for Wallaby
by Matthias Runge 30 Sep '20

30 Sep '20

Hi there, I'd like to announce my candidacy to become the next PTL for OpenStack Telemetry for the Wallaby cycle. In the past cycles, we have seen a decrease in contribution for Telemetry related projects. We have also seen the lengthy discussion around gnocchi or the lack of a TSDB in OpenStack. A few months ago, I joined the project and helped with reviews and bug fixes. For the next cycle, I would like to address the a few short term but also some longer term issues such as: - finish cleaning up the python2 to python3 migration. - get a better understanding (and a solution) for the various telemetry gates being blocked - recently, heat stopped testing auto-scaling via aodh and gnocchi, because it was too unstable. I'd like to address that as well. - We haven't had a planning or a roadmap for about the last 1.5 cycles. That is something to do in the future. Thank you for your support and your consideration. Matthias Runge

1 1

Make Full Disks read-only in swift object storage
by Hamidreza Hosseini 30 Sep '20

30 Sep '20

Hi, I've some disks on my swift object storage that they filled and I made them read only by /etc/fstab I think this isn't true adjustment, Anyway, can I solve this problem (I mean full disks ) without changing the ring and just by configuring the proxy to send put /get requests to empty disks but just Get requests to empty disk? Best regards.

1 0

[ironic] Proposing returning Jay Faulkner to ironic-core
by Julia Kreger 30 Sep '20

30 Sep '20

Greetings ironic contributors, I'm sure many of you have noticed JayF has been more active on IRC over the past year. Recently he started reviewing and providing feedback on changes in ironic-python-agent as well as some work to add new features and fix some very not fun bugs. Given that he was ironic-core when he departed the community, I believe it is only fair that we return those rights to him. Any objections? -Julia

6 5

Question about faafo
by Jesus Aransay 30 Sep '20

30 Sep '20

Dear all, I know that faafo ( https://opendev.org/openstack/faafo ) is no longer being maintained, but I still use it to present some service deployment in my teaching about cloud systems. The application still runs nicely in Ubuntu1804, but I tried to configure the RabbitMQ queue to be created in the publisher (Service API), instead of in the consumers (Service Worker), but I failed. My intention was to show that messages could be published in the queue without any workers having been deployed yet. I thought adding a "maybe_declare" statement in the publisher "would do the trick": https://github.com/jmaransay/faafo/blob/478428f11d92cc22d1be396afec3c787136… But still the message queue is only created when the first worker machine is deployed. Does anybody still have some clue about why the application was configured like that, or how the queue could be created in the publisher? Any hints would be highly appreciated, thank you very much in advance, Jesús -- Jesús María Aransay Azofra Universidad de La Rioja Dpto. de Matemáticas y Computación tlf.: (+34) 941299438 fax: (+34) 941299460 mail: jesus-maria.aransay(a)unirioja.es web: http://www.unirioja.es/cu/jearansa Edificio Científico Tecnológico-CCT, c/ Madre de Dios, 53 26006, Logroño, España

1 0

[masakari][tc][elections] yoctozepto mode on
by Radosław Piliszek 29 Sep '20

29 Sep '20

Hello, Folks! Letting you know I have proposed myself for TC member [1] and Masakari PTL positions [2]. Please find the relevant letters in references. Thank you for your time. [1] https://opendev.org/openstack/election/raw/branch/master/candidates/wallaby… [2] https://opendev.org/openstack/election/raw/branch/master/candidates/wallaby… -yoctozepto

4 3

[all][elections][ptl][tc] Combined PTL/TC Nominations End
by Jeremy Stanley 29 Sep '20

29 Sep '20

The PTL and TC Nomination period is now over. The official candidate list for PTLs is available on the election website[0] as is the candidate list for TC seats[1]. There are 10 projects without candidates, so according to this resolution[2], the TC will have to decide how the following projects will proceed: Cloudkitty, Karbor, Octavia, OpenStack_Charms, Oslo, Packaging_Rpm, Placement, Qinling, Searchlight, Senlin. There is 1 project which will have elections: Telemetry. Now begins the campaigning period where candidates and electorate may debate their statements. Polling will start Oct 06, 2020 23:45 UTC. Thank you, [0] https://governance.openstack.org/election/#wallaby-ptl-candidates [1] https://governance.openstack.org/election/#wallaby-tc-candidates [2] https://governance.openstack.org/resolutions/20141128-elections-process-for… -- Jeremy Stanley

1 0

[Diversity] Community feedback on Divisive Language stance
by Amy Marrich 29 Sep '20

29 Sep '20

The OSF Diversity & Inclusion WG has been working on creating the OSF's stance concerning divisive language. We will be holding one more meeting before sending the stance to the OSF Board for any changes before bringing it back to the Community. Our goal however is to get your input now to reduce any concerns in the future! Please check out Draft 4 on the etherpad[0] and place your comments there and join us on October 5th (meeting information will be sent out closer to the meeting) Thanks, Amy (spotz) 0 - https://etherpad.opendev.org/p/divisivelanguage

2 2

Ussuri CentOS 8 add mptsas driver to introspection initramfs
by Oliver Weinmann 29 Sep '20

29 Sep '20

Hi, I already asked this question on serverfault. But I guess here is a better place. I have a very ancient hardware with a MPTSAS controller. I use this for TripleO deployment testing. With the release of Ussuri which is running CentOS8, I can no longer provision my overcloud nodes as the MPTSAS driver has been removed in CentOS8: https://www.reddit.com/r/CentOS/comments/d93unk/centos8_and_removal_mpt2sas… I managed to include the driver provided from ELrepo in the introspection image but It is not loaded automatically: All commands are run as user "stack". Extract the introspection image: cd ~ mkdir imagesnew cd imagesnew tar xvf ../ironic-python-agent.tar mkdir ~/ipa-tmp cd ~/ipa-tmp /usr/lib/dracut/skipcpio ~/imagesnew/ironic-python-agent.initramfs | zcat | cpio -ivd | pax -r Extract the contents of the mptsas driver rpm: rpm2cpio ~/kmod-mptsas-3.04.20-3.el8_2.elrepo.x86_64.rpm | pax -r Put the kernel module in the right places. To figure out where the module has to reside I installed the rpm on a already deployed node and used find to locate it. xz -c ./usr/lib/modules/4.18.0-193.el8.x86_64/extra/mptsas/mptsas.ko > ./usr/lib/modules/4.18.0-193.6.3.el8_2.x86_64/kernel/drivers/message/fusion/mptsas.ko.xz mkdir ./usr/lib/modules/4.18.0-193.6.3.el8_2.x86_64/weak-updates/mptsas sudo ln -sf /lib/modules/4.18.0-193.el8.x86_64/extra/mptsas/mptsas.ko lib/modules/4.18.0-193.6.3.el8_2.x86_64/weak-updates/mptsas.ko sudo chown root . -R find . 2>/dev/null | sudo cpio --quiet -c -o | gzip -8 > ~/images/ironic-python-agent.initramfs Upload the new image cd ~/images openstack overcloud image upload --update-existing --image-path /home/stack/images/ Now when I start the introspection and ssh into the host I see no disks: [root@localhost ~]# fdisk -l [root@localhost ~]# lsmod | grep mptsas Once i manually load the driver, I can see the disks: [root@localhost ~]# modprobe mptsas [root@localhost ~]# lsmod | grep mptsas mptsas 69632 0 mptscsih 45056 1 mptsas mptbase 98304 2 mptsas,mptscsih scsi_transport_sas 45056 1 mptsas [root@localhost ~]# fdisk -l Disk /dev/sda: 67.1 GiB, 71999422464 bytes, 140623872 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes But how can I make it so that it will automatically load on boot? Best Regards, Oliver

3 4

[election][manila] PTL candidacy for Wallaby
by Goutham Pacha Ravi 29 Sep '20

29 Sep '20

Hello Zorillas and all interested stackers, I'd like to submit my candidacy to be the PTL for the OpenStack Manila team through the Wallaby cycle. I am no longer a stranger to this role, and I've had an excellent team to work with during the past two cycles that serving as PTL has become an absolute pleasure besides being an honor. I've learned by experience that a successful project leader is one that has a great team. I seek to lead an aspirational team that goes all distances to grow, as is evidenced by every member spending a substantial amount of their time mentoring new contributors, and providing an on-boarding ramp to OpenStack - whether this is through informal introductions along the sidelines of conferences, or stray explorers finding us on IRC/email, or engaging with invaluable supporters of diversity and curiosity in the likes of Outreachy, Google Summer of Code, and the Grace Hopper Celebration. I seek to lead a committed team that wants to learn and better itself continuously. We've adopted a proactive policy to bug triage that has kept us rooted to users and their pain points; These bug triages have led to effective (and fun) community "doc-a-thon" and "bug-a-thon" events. Many a times, great effort does not result in great glory. I am proud of the work we do to enhance e2e testing. There are no press releases that reflect this, but I assure you that this work matters a lot to our users. I seek to lead an informed team. Innovation arrives here often by standing on the shoulders of the giants. The team works with technology that's been perfected over decades, as well as with novel breakthroughs of the recent years. We participate in adjacent communities, and adapt while also advocating the lessons we learned in this one. So, if you will have me, I wish to serve you through Wallaby and get things done. Apart from our commitment to OpenStack-wide goals, and the improvements we've charted out, I wish to prioritize a few more work items: - Improve fault tolerance - we've identified some gaps in resource health when certain kinds of service disruptions occur, we'll fix these up. - Achieve OpenStackCLI/SDK/UI parity - there's a lot left to do in this space, and we've actively been chipping away at this for the past two cycles. - API policy improvements - work on the "admin-everywhere" problem with the pop-up team and support fine grained policies in tune with the model of multi-tenancy we cater to. Thank you for your support, Goutham Pacha Ravi <gouthampravi(a)gmail.com> IRC: gouthamr

1 0

[baremetal-sig][ironic] Redfish interoperability profiles: status meeting
by Arne Wiebalck 29 Sep '20

29 Sep '20

Dear all, This cycle, the Ironic community has started to work on Redfish interoperability profiles [0]. These profiles allow to describe requirements for a Redfish endpoint and to automatically verify them via tools like [1]. The aim of this activity is to have an easy way for both vendors and operators to validate that specific hardware is compatible with the Redfish support in Ironic. We will be meeting next week to discuss the current status of this activity. A representative from the DMTF (as the defining body for the Redfish standard) has kindly agreed to join us. Everybody interested is welcome, of course: Thu Sep 24 at 12pm UTC https://cern.zoom.us/j/94808950339 Any question, let us know! Cheers, Richard & Arne [0] https://www.dmtf.org/sites/default/files/standards/documents/DSP0272_1.0.0_… [1] https://github.com/DMTF/Redfish-Interop-Validator

1 1

[tripleo][validations] new Validation Framework demos
by Mathieu Bultel 29 Sep '20

29 Sep '20

Hey TripleO, I have recorded three demos with the new Validation Framework (VF): 1st demo is similar to what Gael did few months ago but with the new code refactored (validations-libs/validations-common projects): https://asciinema.org/a/NRLULghjJa87qxRD9Nfq0FYoa 2nd demo is a use of the VF without any openstack/TripleO prerequisite, on a fresh and empty Ubuntu docker container, with only validations-libs and validations-common projects. It shows that only with a apt-get install git and python3-pip and with a basic python project installation we can run validations and use the framework: https://asciinema.org/a/2Jp9LZbN0xhJAR09zIpI6OpuB So it can answer a few demands such as: How to run validations as prep undercloud installation ? How to run validations on a non-openstack project ? What are the bare minimum requirements for being able to run Validations on a system ? May I run Validation remotely from my machine ? etc... The third one is mainly related to the deployment itself of TripleO. By using a simple PoC (https://review.opendev.org/#/c/724289/) I was able to make TripleO consuming the validations-libs framework and validation logging callback plugin. So it shows in this demo how the deploy steps playbook can be logged, parsed and shown with the VF CLI. This can be improve, modify & so on of course... it's basic usage. https://asciinema.org/a/344484 https://asciinema.org/a/344509 Mathieu.

4 5

[all] Switch to python3-pycryptodome
by Thomas Goirand 29 Sep '20

29 Sep '20

Hi, A number of bug reports have been filled against the Debian OpenStack packages in Sid: - keystone - python-openstackclient - python-manilaclient - python-ironic-lib - python-oauth2client - python-pysaml2 The content of the bugs is: > Source: python-pysaml2 > Version: 4.5.0-8 > Severity: important > Tags: sid bullseye > Usertags: pycrypto > > Dear maintainer, > > python-pysaml2 currently Build-Depends or Depends on python3-crypto > from PyCrypto. This project is no longer maintained and PyCryptodome > (https://www.pycryptodome.org/en/latest/) provides a drop in > replacement. Please switch to python3-pycryptodome. I'd like to > remove python-crypto before the release of bullseye. > > Cheers So my question is: - Is it really a drop-in replacement, and can it be replaced in the packages (maybe, delta the imports?)? - If not, how much work is this? - Can the OpenStack project also move to pycryptodome? Cheers, Thomas Goirand (zigo)

2 1

[horizon][dev] Horizon.next
by Apsey, Christopher 29 Sep '20

29 Sep '20

Horizon team, I recently picked up a few talented dev interns, and one of them is very interested in webdev and quite skilled. He will have up to 25 hours/week to devote to development tasks of my choosing over the 8 months or so, and I'd like to offer him up as someone who can spend all of his time working with the horizon team on horizon.next (npm-based). We rely on horizon heavily internally, and a better experience for the end-user is pretty high on our list (particularly performance-wise). He has no experience developing in the OpenStack ecosystem, but is otherwise ready to 'get to work' after process/code familiarization. Can anyone on the horizon team offer up some cycles to help get him spun up/integrated? Or is the best bet just pointing him at the IRC channel? Thanks Chris Apsey GEORGIA CYBER CENTER

3 2

Re: [tripleo]] tripleo victoria rc1
by Marios Andreou 28 Sep '20

28 Sep '20

On Mon, Sep 28, 2020 at 10:16 AM Yatin Karel <ykarel(a)redhat.com> wrote: > Hi Marios, > > << we don't normally/aren't expected to cut release candidates. > However after discussion with and guidance from Wes I decided to > propose an rc1 as practice since I << haven't used the new releases > tool before [4]. > << The proposal is up at [1] but I've set -1 there on request from > reviewers; we can't merge that until [2] merges first. > > Is this just about releasing RC Tags or changing the release-model > that tripleo used to follow:- cycle-with-intermediary(cycle-trailing > earlier) vs cycle-with-rc. Maybe you can share more context with the > this is just about bumping the git tags on the projects and not about changing the release model. > discussion points as to what's different this time and reasoning for > the same to have a clear picture. > nothing different wrt the release model - see the diff it is just bumping the hash and version https://review.opendev.org/gitweb?p=openstack%2Freleases.git;a=commitdiff;h… . We are just making a release to coincide with the wider openstack Victoria RC1 even though we aren't expected to follow the rc model with our 'cycle with intermediary' on these projects. > And if possible can you also share what's the plan for GA release for > TripleO like how it will be this time. > So weshay is still PTL, and we haven't discussed this in any great detail, except that we may have to delay a little bit cutting branch and releasing victoria final. Generally with rc tags stable branch is also cut but i don't see that > in https://review.opendev.org/#/c/754346/. And i hope this will not be > right I guess the confusion is that this isn't a proper RC since we don't have those 'officially' .It is just a version bump that coincides with the victoria rc1 milestone end of last week. hope it helps, also, did you forget to reply-all? should i send to the list (just confirmed with ykarel and re-adding list to addresses) thanks, marios > merged until victoria tripleo jobs are ready if cutting > stable/victoria branch. > > On Fri, Sep 25, 2020 at 10:05 PM Marios Andreou <marios(a)redhat.com> wrote: > > > > hello TripleO folks o/ > > > > we don't normally/aren't expected to cut release candidates. However > after discussion with and guidance from Wes I decided to propose an rc1 as > practice since I haven't used the new releases tool before [4]. > > > > The proposal is up at [1] but I've set -1 there on request from > reviewers; we can't merge that until [2] merges first. > > > > If you are interested please check [1] and add any comments. In > particular let me know if you want to include a release for one of the > independent repos [3] (though for validations-common/libs we need to reach > out to the validations team they are managing those AFAIK). > > > > thanks, hope you enjoy your weekend! > > > > [1] https://review.opendev.org/#/c/754346/ > > [2] https://review.opendev.org/754347 > > [3] https://releases.openstack.org/teams/tripleo.html#independent > > [4] > https://releases.openstack.org/reference/using.html#using-new-release-comma… > > Thanks and Regards > Yatin Karel > >

2 2

Re: [all][elections][ptl][tc] Combined PTL/TC Nominations ending in less than 24 hours
by Jeremy Stanley 28 Sep '20

28 Sep '20

Another reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Sep 29, 2020 23:45 UTC. If you want to stand for election, don't delay, follow the instructions at [1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. Election statistics[2]: Nominations started @ 2020-09-22 23:45:00 UTC Nominations end @ 2020-09-29 23:45:00 UTC Nominations duration : 7 days, 0:00:00 Nominations remaining : 23:38:26 Nominations progress : 85.93% --------------------------------------------------- Projects[1] : 55 Projects with candidates : 25 ( 45.45%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 30 (Barbican* Blazar* Cinder* Cloudkitty Cyborg Designate* Ec2_Api Freezer Horizon Ironic* Karbor Magnum* Manila Masakari Monasca Murano Octavia OpenStack_Charms Oslo Packaging_Rpm Placement Qinling Quality_Assurance* Requirements* Searchlight Senlin Solum Storlets* Telemetry Watcher) =================================================== Stats gathered @ 2020-09-29 00:06:34 UTC (* indicates teams with pending nominations which haven't been confirmed by more than one election official yet) This means that with approximately 2 days left, 30 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. There are also currently 2 confirmed candidates and 3 additional pending nominations for the 4 open Technical Committee seats, indicating it's likely there will be a runoff poll for the TC election. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.openstack.org/#/q/is:open+project:openstack/election have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for… -- Jeremy Stanley on behalf of the OpenStack Technical Election Officials

1 0

[election][storlets] PTL candidacy for Wallaby
by Takashi Kajinami 28 Sep '20

28 Sep '20

Hi All, I'd like to announce my candidacy to run PTL role for Storlets project in the next Wallaby cycles, to continue PTL role from the previous Victoria cycle. In this cycle, I'll focus on the existing proposals to improve stability and operability of Storlets. Since we have discussion slots in coming PTG, I'll moderate the discussion there and will try to make these proposals land during this cycle. Thank you for your consideration ! Thank you, Takashi Kajinami

1 0

[election][qa] PTL candidacy for Wallaby
by Masayuki Igawa 28 Sep '20

28 Sep '20

Hi everyone, I want to propose my candidacy and continue serving as Quality Assurance PTL for the Wallaby cycle. First off, I would like to thank you all the contributors, core reviewers, and anyone involved and makes the OpenStack better. In Victoria cycle, we've added a job for generating doc from docstrings and added many docstrings for that already. We can see the outcomes here[2]. And we've also made a workflow[3][4] to get along with the upper-constraints in tox.ini. We still have some more planned work pending for Victoria, such as making tempest scenario manager a stable interface, improving tempest cleanup, etc. I think we will accomplish them in Victoria or Wallaby cycle. Along with daily QA activities, my priorities for QA for the next cycle will be: * Guiding and motivating more contributors to QA projects, improving documentation and advertising OpenStack QA projects. * Stability of Tempest scenario manager. * Completing Victoria priority items if it's still remaining. It's hard to accomplish without our collaboration. So, let's do it together! [1] http://stackalytics.com/?user_id=igawa [2] https://docs.openstack.org/tempest/latest/tests/modules.html [3] https://docs.openstack.org/tempest/latest/requirement_upper_constraint_for_… [4] https://wiki.openstack.org/wiki/QA/releases#Project_with_release_mode:_cycl… Thanks for your consideration! -- Masayuki Igawa (masayukig)

1 0

Swift Installation Error
by WALSH CHANG 28 Sep '20

28 Sep '20

To whom it may concern, I am very new to OpenStack. I had an error when I install the Swift service. Error trying to load config from /etc/swift/proxy-server.conf: Entry point 'proxy\naccount_autocreate = True' not found in egg 'swift' (dir: /usr/lib/python2.7/dist-packages; protocols: paste.app_factory, paste.composite_factory, paste.composit_factory; entry_points: ) Just wondering if it's ok to have storage node and controller node on the same device. I use the controller node as the storage node, and use the flash drive as the storage space. Not sure if this is the reason for the error. It will be very appreciated if someone can provide some suggestions. Kind regards, Walsh

2 1

[election][cinder] PTL candidacy for Wallaby
by Brian Rosmaita 28 Sep '20

28 Sep '20

Hello everyone, I hereby announce my candidacy for Cinder PTL for the Wallaby cycle. I've been PTL for two cycles, so you have a pretty good idea by now of what it's like to work on the Cinder project with me in that role, and whether or not it would be a good idea for me to continue. There are a few things I'd like to see the project emphasize during the Wallaby development cycle; hopefully the team will self-organize around these themes. * Continued development of the cinder-tempest-plugin. We need more automated tests for more complicated scenarios, partly to prevent regressions for fixed bugs, but also to detect some problems before they are reported by users. * Better understanding of why some of the gate jobs are intermittently failing, particularly the backup-related tests in the tempest-storage suite. * Better review bandwidth. The core team we carried over from Ussuri to Victoria is still active, but as their careers have progressed, they have taken on more responsibilities in their day jobs, and their review counts have declined a bit. We added Lucio as a new core during Victoria; it would be good to add another person or two during the Wallaby cycle. Anyone working on the cinder project who's interested in working to get themselves into a position where they could be nominated as a cinder core, please contact me (or any of the current cores) to discuss what the expectations are. Those are what's been on my mind lately. As far as specific features, etc., those will emerge from our PTG discussions, to which I encourage you to contribute: https://etherpad.opendev.org/p/wallaby-ptg-cinder-planning We've had productive virtual mid-cycle meetings for two cycles now, and the cinder-weekly-meeting-once-a-month-in-videoconference seems to help keep the team connected, so I'd like to continue that. The team adapted well to the virtual PTG format for Victoria, so I'm confident we'll have a productive virtual Wallaby PTG, though I sincerely hope we'll once again have the opportunity to meet face-to-face for the 'X' PTG. As far as external interest in the Cinder project goes, we've added some new drivers in Victoria and already have one new driver proposed for Wallaby, with at least one more on the way, which is nice. Thanks for reading this far, and thank you for your consideration. Brian Rosmaita (rosmaita)

1 0

[all][election][tc] Candidacy
by Jay Bryant 28 Sep '20

28 Sep '20

Dear OpenStack Community, This note is to officially announce my intention to be re-elected to the OpenStack TC in the Wallaby cycle. At this point, I think that many of you know me, but for those who don't I will briefly introduce myself. I have been a part of the OpenStack Community since early in 2013. At that time I was working for IBM and acted as the liaison between the storage teams developing Cinder drivers for IBM's storage solutions and the Community. I am currently working at Lenovo as the Principal Cloud Architect, leading a team that is developing automated infrastructure deployment and cloud deploy solutions for several different cloud platforms. During my time in the OpenStack Community I have been a Cinder core team member and served as PTL for Cinder for two years. I have been an active part of on-boarding for new Community members, helping and supporting the Upstream Institute sessions since the 2016 session in Barcelona. I also have been active in projects outside of Cinder, acting as Oslo liaison for Cinder and helping the documentation team back in the days that that was a thing. Most recently, I have served a year on the OpenStack TC. I will admit that the experience has come with a learning curve. My time has also been during a time of change for the TC and for OpenStack in general. During my time on the TC I was proud to organize the first review of Technical Committee questions in the annual user survey. The exercise was interesting and I feel it brought good information to the TC with regards to what the community needs to be doing to best serve our users. I also have been active in the discussions around how to handle leaderless projects. I feel that my experience as a PTL for a notable period of time and core team member for over 6 years gives me perspective to talk about how we continue to develop OpenStack project structure. During my last year, my focus at work has changed from pure development to being more of a designer/consumer of cloud solutions. The solutions are not exclusively OpenStack, but now include OpenShift and VMware based clouds. The change in focus has given me new perspective on how OpenStack fits into the cloud ecosystem and I think it is perspective that will be helpful in the coming year as we now have a combined Technical Committee and User Committee. If re-elected I will support getting the OpenStack community connected with other cloud communities, especially the k8s community. I will continue to support efforts to adapt OpenStack's processes and projects to make things easier for projects both large and small. I also hope to help to set goals for the community that will help it continue to be a vibrant and relevant cloud solution for years to come! Working with the OpenStack Community has always been something that I have been very proud to do in my career. I thank you all for the opportunity to serve as a TC member the last year and hope that I can continue to serve the community in this capacity. Sincerely, Jay Bryant IRC (Freenode): jungleboyj

1 0

[cinder] this week's meeting in video+IRC
by Brian Rosmaita 28 Sep '20

28 Sep '20

I forgot to mention at last week's Cinder meeting that the meeting for Wednesday 30 September, being the last meeting of the month, will be held in both videoconference and IRC at the regularly scheduled time of 1400 UTC. Here's a quick reminder of the video meeting rules we've agreed to: * Everyone will keep IRC open during the meeting. * We'll take notes in IRC to leave a record similar to what we have for our regular IRC meetings. * Some people are more comfortable communicating in written English. So at any point, any attendee may request that the discussion of the current topic be conducted entirely in IRC. connection info: https://bluejeans.com/3228528973 cheers, brian

1 0

[election][designate] PTL candidacy for Wallaby
by Michael Johnson 28 Sep '20

28 Sep '20

My fellow OpenStack community, I would like to announce my candidacy for PTL of Designate for the Wallaby cycle. As you probably know I have been the Octavia PTL five times since the Pike release. I will continue to be involved in the Octavia project, but it is time for a change! I feel that allowing for leadership change on projects is healthy and gives others the opportunity to lead. In my downstream day job I am becoming more involved in supporting Designate as part of our OpenStack offering. This means I will be contributing more to Designate and supporting the Designate community. One of my Designate goals for the Wallaby release will be expanding the documentation available. For example, I would like to create some user cookbooks, similar to those in the Octavia documentation, that would guide users through scenarios using Designate. I am also excited to see a proposed patch for DNS “views” in Designate, so I will be supporting that development effort in any way I can help. Thank you for your support and your consideration for Wallaby, Michael Johnson (johnsom)

1 0

[tc] weekly update
by Mohammed Naser 28 Sep '20

28 Sep '20

Hi everyone,Here's an update for what happened in the OpenStack TC this week. You can get more information by checking for changes in openstack/governance repository. We've also included a few references to some important mailing list threads that you should check out. # Patches ## Open Reviews - Add assert:supports-standalone https://review.opendev.org/722399 - Add election schedule exceptions in charter https://review.opendev.org/751941 - Remove tc:approved-release tag https://review.opendev.org/749363 - Clarify impact on releases for SIGs https://review.opendev.org/752699 - Migrate rpm-packaging to a SIG https://review.opendev.org/752661 - Retire openstack/os-loganalyze https://review.opendev.org/753834 - Retire devstack-plugin-pika project https://review.opendev.org/748730 - Reorder repos alphabetically https://review.opendev.org/754097 - Add Ironic charms to OpenStack charms https://review.opendev.org/754099 - Define TC-approved release in a resolution https://review.opendev.org/752256 # Other Reminders - PTG Brainstorming: https://etherpad.opendev.org/p/tc-wallaby-ptg - PTG Registration: https://october2020ptg.eventbrite.com Thanks for reading! Mohammed & Kendall -- Mohammed Naser VEXXHOST, Inc.

1 0

TC Candidacy for Wallaby
by Amy Marrich 28 Sep '20

28 Sep '20

Hey all, I am declaring my candidacy for the Technical Committee. I have served in various leadership positions within the community over the years and feel I have developed a well rounded view of what goes on within OpenStack from the project level up to the OSF Board level. I feel I can represent all members of the community from the folks running small private clouds to the teams running large public clouds. I also feel my experiences helping with OpenStack Upstream Institute, the OpenStack mentoring program, and the Git and Gerrit workshops help me to connect with contributers from those just starting out to those who have been here from the beginning. While I'm admittedly not a developer by profession, I have code and documentation contributions in multiple projects which I think is important in seeing the big picture as to how pieces fit together in the larger OpenStack codebase. Thanks, Amy Marrich (spotz)

1 0

[neutron] Bug deputy report for week of September 21st
by Brian Haley 28 Sep '20

28 Sep '20

Hi, I was Neutron bug deputy last week. Below is a short summary about the 21 (!) reported bugs. -Brian Critical bugs ------------- * https://bugs.launchpad.net/neutron/+bug/1896603 - ovn-octavia-provider: Cannot create listener due to alowed_cidrs validation - https://review.opendev.org/#/c/753302/ * https://bugs.launchpad.net/bugs/1896678 - [OVN Octavia Provider] test_port_forwarding failing in gate - https://review.opendev.org/#/c/753419/ * https://bugs.launchpad.net/neutron/+bug/1896766 - OVN jobs failing due to failed OVS compilation - https://review.opendev.org/#/c/751882/ * https://bugs.launchpad.net/neutron/+bug/1897326 - scenario test test_floating_ip_update is failing often on Ubuntu 20.04 - Possibly related to https://bugs.launchpad.net/neutron/+bug/1896735 - Slawek took ownership High bugs --------- * https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1896506 - keepalived_use_no_track default=True breaks bionic deploys - Needs owner * https://bugs.launchpad.net/neutron/+bug/1896677 - [OVN Octavia Provider] OVN provider fails creating pool without subnet ID - Assigned to haleyb * https://bugs.launchpad.net/neutron/+bug/1896735 - Scenario tests from neutron_tempest_plugin.scenario.test_port_forwardings.PortForwardingTestJSON failing due to ssh failure - https://review.opendev.org/#/c/753552/ proposed * https://bugs.launchpad.net/neutron/+bug/1896827 - port update api should not lose foreign external_ids - https://review.opendev.org/#/c/753833/ proposed * https://bugs.launchpad.net/neutron/+bug/1896945 - dnsmasq >= 2.81 not responding to DHCP requests with current q-dhcp configs - Looks similar to https://bugs.launchpad.net/neutron/+bug/1876094 but that fix is merged - Needs owner * https://bugs.launchpad.net/neutron/+bug/1897095 - [OVN] ARP/MAC handling for routers connected to external network is scaling poorly - https://review.opendev.org/#/c/752678/ proposed Medium bugs ----------- * https://bugs.launchpad.net/neutron/+bug/1896470 - OVN migration infrared plugin does not remove ML2OVS-specific templates - https://review.opendev.org/#/c/752918/ proposed * https://bugs.launchpad.net/neutron/+bug/1896587 - iptables firewall driver don't drops invalid packets which match some SG rule - Fix for https://bugs.launchpad.net/neutron/+bug/1460741 moved this iptables chain lower, so more investigation required. * https://bugs.launchpad.net/tempest/+bug/1896592 - [neutron-tempest-plugin] test_dhcpv6_stateless_* clashing when creating a IPv6 subnet - Actually a bug in the tempest repo, added component - Fixed in neutron-tempest-plugin with https://review.opendev.org/#/c/560465/ - Marked Incomplete by Rodolfo as he noticed server issues (500's) in the logs * https://bugs.launchpad.net/neutron/+bug/1896733 - [FT] Error while executing "remove_nodes_from_host" method - Needs owner * https://bugs.launchpad.net/neutron/+bug/1896850 - dhcp release fails when client_id is specified - https://review.opendev.org/#/c/753865/ proposed * https://bugs.launchpad.net/neutron/+bug/1896933 - Exception when plugin creates a network without specifying the MTU - https://review.opendev.org/#/c/753717/ proposed Low bugs -------- * https://bugs.launchpad.net/neutron/+bug/1896588 - [Security Groups] When using neutron CLI, if non-existing project is given when listing the SGs, a default SG is created - Rodolfo working on it * https://bugs.launchpad.net/neutron/+bug/1897100 - Improve port listing command - https://review.opendev.org/#/c/754117/ proposed * https://bugs.launchpad.net/neutron/+bug/1897423 - [L3] Let agent extension do delete router first - https://review.opendev.org/#/c/736258/ proposed * https://bugs.launchpad.net/neutron/+bug/1895876 - When accounts.yaml is used neutron_tempest_plugin fails with "Invalid input for tenant_id. Reason: 'None' is not a valid string." - https://review.opendev.org/754782 proposed Wishlist bugs ------------- * https://bugs.launchpad.net/neutron/+bug/1896920 - Unnecessary error log when checking if a device is ready - https://review.opendev.org/#/c/754005/ proposed Further triage required ----------------------- * None

1 0

[requirements][election] PTL candidacy for Wallaby
by Matthew Thode 28 Sep '20

28 Sep '20

I would like to announce my candidacy for PTL of the Requirements project for the Wallaby cycle. The following will be my goals for the cycle, in order of importance: 1. The primary goal is to keep a tight rein on global-requirements and upper-constraints updates. (Keep things working well) 2. Un-cap requirements where possible (stuff like botocore). 3. Audit global-requirements and upper-constraints for redundancies. One of the rules we have for new entrants to global-requirements and/or upper-constraints is that they be non-redundant. Keeping that rule in mind, audit the list of requirements for possible redundancies and if possible, reduce the number of requirements we manage. Json libs are on the short list this go around. I look forward to continue working with you in this cycle, as your PTL or not. Thanks for your time, -- Matthew Thode

1 0

[blazar][election] PTL candidacy for Wallaby
by Pierre Riteau 28 Sep '20

28 Sep '20

Hi, I would like to self-nominate for the role of PTL of Blazar for the Wallaby release cycle. I have been PTL since the Stein cycle and I am willing to continue. Unfortunately, Blazar has been suffering from low participation in the project. I will keep engaging with current users and potential new ones, in order to get more contributors involved in the project. Thank you for your support, Pierre Riteau (priteau)

1 0

[election][barbican] Add Douglas Mendizábal candidacy for Barbican PTL
by Douglas Mendizabal 28 Sep '20

28 Sep '20

Hello OpenStack, I would like to nominate myself for Barbican PTL. [1] My focus for the new cycle will be to continue the maintenance and development of the project. We will continue to improve usability as well as continue to enable cross-project encryption features. We hope to deliver our first microversion revision early in the Wallaby cycle, so tha we can finally release the Secret Consumers feature. Thanks, Douglas Mendizábal [1] https://review.opendev.org/#/c/754735/

1 0

[election][magnum] Add strigazi candidancy for magnum
by Spyros Trigazis 28 Sep '20

28 Sep '20

Hello stackers, I would like to nominate [0] myself for Magnum PTL. In the recent releases the focus of the team was around our kubernetes driver. I would like to continue that direction for wallaby while trying to improve cloud administrators' management. More specifically: * simplifying addon deployment for our kubernetes driver (the current proposal relies on helm3) * allow control plane resizing * optionally run the clusters' control plane on the cloud operators' tenant * investigate addon upgrades The goal of the project is clearly to be very lean and rely as much as possible on the dependent communities like: kubernetes, containerd, calico, helm and so on. Thank you for considering me, Spyros Trigazis [0] https://review.opendev.org/754727

1 0

[release] Release countdown for week R-2 Sept 28 - Oct 2
by Sean McGinnis 28 Sep '20

28 Sep '20

Development Focus ----------------- At this point we should have release candidates (RC1 or recent intermediary release) for all the victoria deliverables. Teams should be working on any release-critical bugs that would require another RC or intermediary release before the final release. Actions ------- If you have deliverables on a cycle-with-rc model but haven't had a RC1 released yet, please check the proposed RC1 releases at [1]. Without a clear answer, the release management team will be approving those on Monday morning! [1] https://review.opendev.org/#/q/topic:victoria-rc1+status:open Early in the week, the release team will be proposing stable/victoria branch creation for all deliverables that have not branched yet, using the latest available victoria release as the branch point. If your team is ready to go for creating that branch, please let us know by leaving a +1 on these patches. If you would like to wait for another release before branching, you can -1 the patch and update it later in the week with the new release you would like to use. By the end of the week the release team will merge those patches though, unless an exception is granted. Once stable/victoria branches are created, if a release-critical bug is detected, you will need to fix the issue in the master branch first, then backport the fix to the stable/victoria branch before releasing out of the stable/victoria branch. After all of the cycle-with-rc projects have branched we will branch devstack, grenade, and the requirements repos. This will effectively open them up for wallaby development, though the focus should still be on finishing up victoria until the final release. For projects with translations, watch for any translation patches coming through and merge them quickly. A new release should be produced so that translations are included in the final victoria release. Finally, now is a good time to finalize release notes. In particular, consider adding any relevant "prelude" content. Release notes are targetted for the downstream consumers of your project, so it would be great to include any useful information for those that are going to pick up and use or deploy the victoria version of your project. Upcoming Deadlines & Dates -------------------------- Final Victoria release: October 14 Open Infra Summit: October 19-23 Wallaby PTG: October 26-30

1 0

[elections][placement][blazar] Placement PTL Non-candidacy: Stepping down
by Tetsuro Nakamura 28 Sep '20

28 Sep '20

Hello everyone, Due to my current responsibilities, I'm not able to keep up with my duties either as a Placement PTL, core reviewer, or as a Blazar core reviewer in Wallaby cycle. Thank you so much to everyone that has supported. I won't be able to checking ML or IRC, but I'll still be checking my emails. Please ping me via email if you need help. Thanks. - Tetsuro -- Tetsuro Nakamura <tetsuro.nakamura.bc(a)hco.ntt.co.jp> NTT Network Service Systems Laboratories TEL:0422 59 6914(National)/+81 422 59 6914(International) 3-9-11, Midori-Cho Musashino-Shi, Tokyo 180-8585 Japan

4 3

[Kuryr] Proposing Roman Dobosz for kuryr-kubernetes core
by Michał Dulko 28 Sep '20

28 Sep '20

Hello, I'd like to propose Roman for the core reviewer role in kuryr- kubernetes. Roman was leading several successful development activities during Train and Ussuri cycles: * Switch to use openstacksdk as our OpenStack API client. * Support for IPv6. * Moving VIF data from pod annotations to a KuryrPort CR. He also demonstrated code reviewing skills of an experienced Python developer. In the absence of objections, I'll proceed with adding Roman to the core team next week. Thanks, Michał

5 5

Re: [openstack-ansible] OpenStack Ansible deployment fails, due to lxc containers not having network connection
by Oliver Wenz 28 Sep '20

28 Sep '20

> I would recommend always building an All-In-One deployment in a virtual > machine > so that you have a reference to compare against when moving away from > the 'stock config'. > Documentation for the AIO can be found here > https://docs.openstack.org/openstack-ansible/ussuri/user/aio/quickstart.html I gradually decreased the complexity of my test system towards the 'stock config' to find out what caused the error but it kept showing up. Finally, it vanished when I rebooted the server and my original configuration also completed successfully afterwards. 🤦‍♂️ Thank you for your help and the insights to OSA! Kind regards, Oliver

1 0

[ptl][election][mistral] PTL candidacy
by Renat Akhmerov 28 Sep '20

28 Sep '20

Hi, I'm Renat Akhmerov. I'd like to announce my PTL candidacy for Mistral in Wallaby cycle. In Victoria, we made a huge change related to how we manage actions in Mistral. Previously, all actions were stored in the database and when any Mistral subsystem needed to get info about an action (action definition) it sent a query to DB. So, there wasn't any abstraction responsible for action management. This approach is not flexible and makes refactoring incredibly hard. It also means that it's nearly impossible to deliver actions to the system or alter them in runtime w/o having to reboot a cluster node. In Victoria we introduced the new abstraction called Action Provider. Action providers are fully responsible for delivering actions to Mistral. It is possible to. register many providers in the entry point "mistral.action.providers" in setup.cfg of any Python project (installed within the same Python env as Mistral) and Mistral will be using them all to find actions. So action management is now decoupled from the rest of the system and it's now possible to move away from storing action definitions only in the DB. It's fully up to a particular action provider implentation. Actions can even be dynamically generated, for example, as wrappers around a subset of operating system commands. Another option is. requesting info about actions via some communication protocols like HTTP, AMQP etc. There's still work to polish this all and document properly but the main infrastructure is already available and everyone can implement their own action providers. For W cycle I'd like to proceed with improving Mistral usability (toolset for developing Mistral actions, docs etc.) and address several known scalability issues. As always, anyone is very welcome to join our project. It's a lot of fun to work on it. The best way to get in touch with us is IRC channel #openstack-mistral or the openstack-discuss mailing list (with [mistral] tag in email subject). [1] https://review.opendev.org/#/c/754646/ Cheers Renat Akhmerov @Nokia

1 0

[tripleo][ci] proposing Yatin as tripleo-ci core
by Wesley Hayutin 28 Sep '20

28 Sep '20

Greetings, I really thought someone else had already sent this out. However I don't see it so here we go. I'd like to propose Yatin Karel as tripleo-ci core. You know you want to say +2 :)

19 18

[adjutant][election] PTL candidacy for Wallaby
by Adrian Turjak 27 Sep '20

27 Sep '20

Hello All, I'm submitting myself as the PTL for Adjutant during the W cycle. The focus is as always to continue maintaining the project to ensure it is operating as expected and as bug free as possible. Wallaby will mostly be about cleaning up some internal systems, and minor features to help with custom plugin support. The hope is to also clean up policy/role in this release, and include some elements of that into the plugin layer, and to start working on more useful user management features. Depending on time and resources, we may start work on async worker support to allow some parts of tasks to be processed asynchronously. Cheers, Adrian Turjak

1 0

[all][elections][ptl][tc] Combined PTL/TC Nominations ending soon
by Jeremy Stanley 27 Sep '20

27 Sep '20

A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Sep 29, 2020 23:45 UTC. If you want to stand for election, don't delay, follow the instructions at [1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. Election statistics[2]: Nominations started @ 2020-09-22 23:45:00 UTC Nominations end @ 2020-09-29 23:45:00 UTC Nominations duration : 7 days, 0:00:00 Nominations remaining : 1 day, 23:12:19 Nominations progress : 71.90% --------------------------------------------------- Projects[1] : 55 Projects with candidates : 18 ( 32.73%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 37 (Adjutant Barbican Blazar Cinder Cloudkitty Cyborg Designate Ec2_Api Freezer Horizon Ironic Karbor Magnum Manila Masakari Mistral Monasca Murano Octavia OpenStack_Charms OpenStack_Helm Oslo Packaging_Rpm Placement Qinling Quality_Assurance Rally Requirements Searchlight Senlin Solum Storlets Tacker Telemetry Trove Watcher Zun) =================================================== Stats gathered @ 2020-09-28 00:32:41 UTC This means that with approximately 2 days left, 37 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.openstack.org/#/q/is:open+project:openstack/election have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for… -- Jeremy Stanley on behalf of the OpenStack Technical Election Officials

1 1

[election][tacker] PTL candidacy for Wallaby
by Yasufumi Ogawa 27 Sep '20

27 Sep '20

Hi, I'd like to propose my candidacy for Tacker PTL in Wallaby cycle. In Victoria release, we have released great features required for the latest ETSI NFV standard and made several improvements for Tacker as and as planed in the last vPTG. We also fix issues for migrating to python3 and Ubuntu focal. As a PTL, I've led the team by proposing not only new features, but also things for driving the team such as documentation or bug tracking. It was something hard, but is running well. In Wallaby cycle, I would like to continue to make Tacker be more useful product from not only telco, but also all users interested in NFV. I believe Tacker will be a good reference implementation for NFV standard. We have planed to make Tacker more feasible not only for VM environment, but also container to meet requirements from industries. - Introduce the latest container technology with ETSI NFV standard. - Reinforce test environment for keeping the quality of the product, not only unit tests and functional tests, but also introduce more sophisticated scheme such as robot framework. - Revise wiki and documentation for covering users more. Regards, Yasufumi Ogawa

1 0

[election][heat] PTL candidacy for Wallaby
by Rico Lin 26 Sep '20

26 Sep '20

Hi all, I would like to announce my candidacy for Heat PTL for Wallaby cycle. Over the past couple of cycles, we running Heat dynamically according to requirements. We never stop encouraging people to join us and provide consistent reviews or fixes as much as we can based on priorities. And if those priorities not working for you, that means you must join the community to help. I believe the goals for the next cycle should be community CI stability, cross-project/community scenario tests to ensure what we deliver to users will get higher quality, also to get rid of legacy mode and move everything to convergence mode, and finally container-native support to make sure we provide usable Orchestration services for the container environment. I believe in new features, so we will try to encourage more features and review them as many as possible, but will not plan for team feature goals unless we can trigger more discussion and hands-on.Thank you for taking my self-nomination into consideration. -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

1 0

API short reponse time between the S version and the U version
by Zhi CZ Chang 26 Sep '20

26 Sep '20

1 0

[election][swift] PTL candidacy for Wallaby
by Tim Burke 26 Sep '20

26 Sep '20

I'd like to announce my candidacy for Swift PTL for the Wallaby cycle. This past year, Swift celebrated ten years running in production. Much has changed in that time: new features have been developed and polished, versions of Python have come and gone, and clusters have grown to staggering capacities. However, our commitment to operational excellence remains the same. Recently (particularly in the last several months), I've noticed our contributors increasingly have an operator's mindset. We look for more and better ways to measure Swift. We seek to reduce client impacts from config reloads and upgrades. We take greater ownership over the health and performance of our clusters. To a large extent, we're all operators now. The benefits have been enormous. We've improved performance; we've upgraded without disrupting any client requests; we've migrated clusters to Python 3 to position them well for the next ten years. Through it all, clients put ever more data into Swift. The increases in demand bring almost incomprehensible scales. We now see individual clusters sustaining tens of thousands of requests every second. We see containers with a billion objects. We see expansions that are as large as many whole clusters were just a few years ago. This is our next great challenge: how do we move away from a world where expansions are a rarity that may require a bit of a scramble and into a world of constant expansion? How can we effectively manage clusters with thousands of nodes? How do we shift from thinking in terms of petabytes to exabytes? I can't wait to see how we rise to meet this challenge. Tim Burke

1 0

The question about OpenStack instance fail to boot after unexpected compute node shutdown
by Yule Sun 26 Sep '20

26 Sep '20

I saw your message on the website http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005635.ht… . And i have been troubled by the same problem for a long time . I tried to change the parameters resume_guests_state_on_host_boot=True and instance_usage_audit=True in the nova.conf ,but it didn't work . I wonder if you have solved this problem, looking forward your reply, Thank you and best regards. And my instance error looks like this . [cid:e8770762-d2b2-4630-9ce6-4d357dc92cee]

2 1

[election][zaqar] PTL candidacy for Wallaby
by hao wang 26 Sep '20

26 Sep '20

Hi, I want to propose my candidacy and continue serving as Zaqar PTL in the Wallaby cycle. For the Victoria release, the Zaqar team continues to keep the Zaqar stable and reliable, and also some great works have been done. We designed and implemented the Encrypted message in the queue to enhance the security of Zaqar. We also fixed some bugs to meet the python3 requirements. In the Wallaby cycle, I would like to continue serving this project and bring more contributors and the user requires. There are some major works I want to do in W cycle: 1.Finish the Topic resource work, to support all backends. 2.Consider to support more backends that have widely used. 3.Continue to support more security algorithms for encrypted messages. 4.Implement some new requirements from users. 5.keep Zaqar more reliable as usual. Thanks to everyone to support my work and keep contributing to Zaqar. I will do my best in the new cycle.

1 0

[openstack-ansible][election] Candidacy
by Dmitriy Rabotyagov 25 Sep '20

25 Sep '20

Hey everyone! This cycle I've decided to take part in elections and run for PTL of the OpenStack-Ansible project. I feel that OSA nowadays is a solid and stable project, and we're doing a great job to get all features in time and deploy only modern software with our deployments, as well as providing deployers with a high range of different supported options and flexibility. It's rather important to keep up with the progress. And there are main things I'd love to focus on during the upcoming release: # Integration tests coverage for all roles Despite migrating tests for most of the projects to the integrated repo, we still have several projects not covered with proper testing (like Zun). I also would love to pay attention to passing appropriate tempest scenarios for all projects instead of running some default ones. # Cleaning up bugtracker I think one of our highest priorities should be project stability. And taking care of bugs might help us heavily with that. We haven't been paying enough attention to our Launchpad for a while and I think we should change that by cleaning up stale bugs, so we could focus on real ones. Returning bug triage to the meeting might be also an efficient way to handle them. # Roles cleanup We have a lot of things left in code, like workarounds for upgrades, upstream bugs, support for obsolete operating systems, etc. Removal/replacement of deprecated OpenStack options should be also included. # Usage of the new pip resolver Our venv build process relies on provided constraints heavily, which isn't valid in case of the new pip resolver usage, so we will need to make appropriate adjustments into the process to keep the ability to define specific package requirements and use modern pip. Thank you for taking into consideration my nomination.

1 0

Re: [magnum][infra] Can We Delete the OpenDev Fedora Atomic Images Mirror
by feilong＠catalyst.net.nz 25 Sep '20

25 Sep '20

1 0

OpenstackSwift - rclone Copy/Sync Large Objects set (150Mil objects - 80TB) from Tenant PROD1 to PROD2
by prem shivakumar 25 Sep '20

25 Sep '20

Hi Open-stack users, Our current setup: PROD1 Container1 Dir1/Dir2/YYYYMMDD.tar Want to move to: PROD2 Container2_YYYYMM Dir1/Dir2/YYYYMMDD.tar I got all the objects metadata(Object names) using “swift list Container1” I am currently using rclone where I am passing metadata(Object names) info of “Container1”. All the Auth variables exist in rclone.conf. Example command: rclone copy PROD1: Dir1/Dir2/YYYYMMDD.tar PROD2:Container2_YYYYMM/Dir1/Dir2/ YYYYMMDD.tar Currently, I am facing slowness in copying files from PROD1 to PROD2. On an average, It takes about 5s to copy the object from PROD1 to PROD2. If I count the time against 150M its more than 10000Days. I have also tried “rclone sync with —fast-list” it is failing as it is unable to keep the listing in the memory. In this case, is there any easier and faster solution to copy data from Container1 to Container2? Thank you.

1 0

[magnum][infra] Can We Delete the OpenDev Fedora Atomic Images Mirror
by Clark Boylan 25 Sep '20

25 Sep '20

I'm in the process of removing our fedora-30 images and noticed that we are still mirroring Fedora Atomic 28 and 29 images here: https://mirror.dfw.rax.opendev.org/fedora/atomic/stable/. Are these images in use anywhere? I would like to clean them up as they are even more stale than the fedora-30 nodepool images. Using http://codesearch.openstack.org I don't see anything using them but that only searches the master branches of our git repos. Clark

3 3

[election][kolla] PTL candidacy for Wallaby
by Mark Goddard 25 Sep '20

25 Sep '20

Hi, I'd like to nominate myself to serve as the Kolla PTL for the Wallaby cycle. I have been PTL for the last 3 cycles, and would like the opportunity to continue to lead the team. I am pleased with the current state of the project. We have an active community, produce interesting and useful features, and regularly receive positive feedback. As with many contributors in a less certain world, I have felt the squeeze on upstream this cycle. I'd like to thank those who have stepped up to help when downstream (or holiday) means I'm unavailable, and those who generally help out with project admin tasks. This cycle we added two new meetings to the calendar. Kolla Klub started well, with fantastic attendance and some great discussions. Over time engagement has been more variable. I think we need to assess whether to continue regular meetings, and if so, how to keep it interesting. The Kolla Kall is more development oriented, and has been useful for focussing on some specific issues. For this meeting I think we need to be sure that it is the best use of people's time, and be a bit more dynamic about content and attendance. One area where I feel we could improve as a project is in integrating contributors in non-EU/US time zones. Language, culture and time zones can make this a challenge, but everyone benefits from a connected global community. We made a start on improving our documentation this cycle, let's keep pushing on that. Thanks for reading, Mark Goddard (mgoddard)

1 0

[InteropWG] Looking for k8s Ready OpenStack / Open Infra and BMaaS Add-on Conformance Candidates
by prakash RAMCHANDRAN 25 Sep '20

25 Sep '20

Hi all, Here is summary of Friday alternate week calls of Interop(next Oct 9th) join us on meetpad - refer https://etherpad.opendev.org/p/interop We are looking forward to prep work for PTG on October23 Monday & October 30 Friday Interop slots ( https://ethercalc.openstack.org/7xp2pcbh1ncb ) 1. Seeking Candidate for "Kubernetes Ready OpenStack" Branding - need Ideation from different Project teams with variations you seek (see eg.) eg. Distros RHSOP with Cinder CSIVIO with Swift CSI eg. Hosted version Canonical OpenStack Distro with Manila CSISUSE OpenStack with Octavia Load Balances Ingress Controller Add your ideas to - https://etherpad.opendev.org/p/2020-Wallaby-interop-brainstorming 2. Seeking Candidates for OpenStack ready Bare Metal as a Service Add-ons IronicMaaS Add your ideas to - https://etherpad.opendev.org/p/2020-Wallaby-interop-brainstorming All Vendors and PTLs interested in pursuing ideas for their next releases OpenStack or Open Infra release please add your ideas to etherpads above.Reply to this chain and we will try consolidate Interop in Bare metal & K8s era. ThanksPrakash / MarkFor InteropWG

1 0

[tripleo]] tripleo victoria rc1
by Marios Andreou 25 Sep '20

25 Sep '20

hello TripleO folks o/ we don't normally/aren't expected to cut release candidates. However after discussion with and guidance from Wes I decided to propose an rc1 as practice since I haven't used the new releases tool before [4]. The proposal is up at [1] but I've set -1 there on request from reviewers; we can't merge that until [2] merges first. If you are interested please check [1] and add any comments. In particular let me know if you want to include a release for one of the independent repos [3] (though for validations-common/libs we need to reach out to the validations team they are managing those AFAIK). thanks, hope you enjoy your weekend! [1] https://review.opendev.org/#/c/754346/ [2] https://review.opendev.org/754347 [3] https://releases.openstack.org/teams/tripleo.html#independent [4] https://releases.openstack.org/reference/using.html#using-new-release-comma…

1 0

[openstack][manila] GenericShareDriver on stein
by Ignazio Cassano 25 Sep '20

25 Sep '20

Hello Stackers, I am testing manila manila.share.drivers.generic.GenericShareDriver with manila.share.drivers.generic.GenericShareDriver. I created in my project an instance with nfs server and it is up and running. In my manila.conf I have specified the instance id, use and password: [locale] share_driver = manila.share.drivers.generic.GenericShareDriver driver_handles_share_servers = false share_backend_name= locale service_instance_user = manila service_instance_passwod = manila service_instance_name_or_id = 5b0fa246-e94b-4a84-b730-7066dfb31fb0 path_to_private_key=~/.ssh/id_rsa path_to_public_key=~/.ssh/id_rsa.pub I have also other backend with netapp drivers and they works fine. The generic drivers reports: 2020-09-25 13:56:13.955 4097174 WARNING manila.share.drivers.generic [req-f0a5294a-3ef2-4226-9fc9-f3b4f35c53f5 - - - - -] Waiting for the common service VM to become available. Driver is currently uninitialized. Share server: None Retry interval: 5 2020-09-25 13:56:14.143 4097174 ERROR manila.share.drivers.generic [req-f0a5294a-3ef2-4226-9fc9-f3b4f35c53f5 - - - - -] string indices must be integers 2020-09-25 13:56:19.144 4097174 WARNING manila.share.drivers.generic [req-f0a5294a-3ef2-4226-9fc9-f3b4f35c53f5 - - - - -] Waiting for the common service VM to become available. Driver is currently uninitialized. Share server: None Retry interval: 5 2020-09-25 13:56:19.340 4097174 ERROR manila.share.drivers.generic [req-f0a5294a-3ef2-4226-9fc9-f3b4f35c53f5 - - - - -] string indices must be integers Seems the instance I created is not available. Please, any help? Ignazio

2 2

[election][Kuryr] PTL candidacy for Wallaby
by Maysa De Macedo Souza 25 Sep '20

25 Sep '20

Hello, I would like to propose my candidacy to be the PTL of Kuryr for the Wallaby cycle. I have been a contributor to Kuryr since the Queens release and was appointed to the Kuryr core team in the Ussuri cycle. I see the following goals for the Kuryr project during the Wallaby cycle: * Improve stability and extend CI: we already included great improvements in our CI, but I believe we must continuously work on it to provide better and quicker feedback when developing new features. As part of that, we should start graduating experimental jobs like the ones using OVN-Octavia driver and Network Policy, and handle issues with jobs requiring more swap. * Address testing gaps for new and existing features: this would avoid regressions and find bugs. Also, improves stability. * Continue extending and improving Kuryr functionalities, such as dual stack, SCTP support and CRDs usage. * Grow the contributor base. I would like to contribute back to the community as a PTL while following great examples of previous PTLs. Thank you, Maysa.

1 0

[rpm-packaging] Proposing Hervé Beraud as new core reviewer
by Javier Pena 25 Sep '20

25 Sep '20

Hi, I would like to propose Hervé Beraud as a new core reviewer for the rpm-packaging project. Hervé has been providing consistently good reviews over the last few months, and I think he would be a great addition to the core reviewer team. Existing cores, please vote on the thread! Regards, Javier Peña

3 3

[tc] monthly meeting
by Mohammed Naser 25 Sep '20

25 Sep '20

Hi everyone, Our monthly TC meeting is scheduled for next Thursday, October 1st, at 1400 UTC. If you would like to add topics for discussion, please go to https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting and fill out your suggestions by Wednesday, September 30th, at 1900 UTC. Thank you, Regards, Mohammed -- Mohammed Naser VEXXHOST, Inc.

1 0

[tripleo] PTL candidacy for Wallaby
by Marios Andreou 25 Sep '20

25 Sep '20

I would like to nominate myself for the TripleO PTL role for the Wallaby cycle. I think it is obvious that the role of the PTL has changed significantly compared to the early days of TripleO. Most importantly we are (and have been for a while) now organised into self-contained topic squads (deployment, validations, upgrades, networking, storage, ci, etc). Typically technical decisions are driven exclusively within those squads (even if they are done 'in the open' on gerrit and launchpad and opendev-discuss). The role of the PTL then is more about coordination across the squads, ensuring we deliver release targets, keeping bug backlogs in order and facilitating the resolution of any conflicts that arise. I have worked on TripleO since before the Kilo release and have collaborated with many current and past members of the community including engineers and also users/operators. My contributions thus far have been in code/docs/bugs, originally working on upgrades and more recently working on CI. I haven't had the opportunity to work on the 'admin' side of TripleO (besides in the past cutting the occasional release). I am thus especially excited by the prospect of contributing in this new way as PTL, if TripleO will have me! I sincerely promise to give it my best and I am sure that together with the kind help of the current PTL Wes Hayutin we will have a smooth Wallaby cycle, meeting our responsibilities to the foundation and the community. There is (as ever!) a lot of exciting work coming in the Victoria release and continuing in Wallaby including the continued exploration of the removal of Heat as our configuration engine, the new validations repos and framework, the new container builds process, Fast Forward Upgrades II (back with a vengeance), ci component and dependency pipelines, ci parent/child jobs, and I'm sure many more that we will discuss at the coming Wallaby PTG. Two areas I would like to focus on as PTL should you give me the opportunity are: - improve our current documentation/deployment guides - at minimum they must be updated to recent releases and there are many items missing. I am hoping to rally support from the various squads for this. - improve visibility into the various TripleO squads - this may mean re-instating a 'new' weekly/bi-weekly (or other frequency) tripleo meeting or by some new way of collaborating. Again this is really dependent on support from the tripleo community. thank you for your consideration!

1 0

[Neutron] Not create .2 port
by Tony Liu 24 Sep '20

24 Sep '20

Hi, When create a subnet, by default, the first address is the gateway and Neutron also allocates an address for serving DHCP and DNS. Is there any way to NOT create such port when creating subnet? Thanks! Tony

3 4

[election][neutron] PTL candidacy for Wallaby
by Slawek Kaplonski 24 Sep '20

24 Sep '20

Hi, I want to propose my candidacy and continue serving as Neutron PTL in the Wallaby cycle. In the Victoria cycle I proposed a couple of major goals. We achieved most of them, like for example: * add support for metadata over IPv6 in Neutron, * continue adoption of the OVN driver as one of the in-tree Neutron drivers. * find new maintainers for the networking-midonet project so we keep it the * Neutron stadium. In the upcoming cycle I would like to continue work which we started already and focus mostly on: * implement old, unfinished Blueprints like adoption of new engine facade, * continue adoption of the OVN backend in Neutron, closing more feature parity * gaps * switch the OVN driver to be the default backend in Devstack, In addition to the goals mentioned above mentioned, I want to continue work to improve our CI stability and coverage. It is my continuing desire to do my best to help our outstanding team to deliver better software and to grow. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[neutron] Drivers meeting agenda - 25.09.2020
by Slawek Kaplonski 24 Sep '20

24 Sep '20

Hi, For tomorrows drivers meeting we again don't have any new RFEs to discuss but I wanted to use this meeting to quickly discuss about 1 bug: https://bugs.launchpad.net/neutron/+bug/1895933 So see You on tomorrows meeting :) -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[all][election][TC] Candidacy
by Kendall Nelson 24 Sep '20

24 Sep '20

Hello Everyone! I am once again declaring my candidacy for the Technical Committee. This last year I have learned so much about OpenStack and our amazing community. There is never a shortage of work to be done and I feel there is still a lot I can do to help the community as a part of the TC. I served as TC Vice Chair during the second half of my term and I felt like I was able to do a lot to help support Mohammed, the chair and other members of the TC. My work in coordinating the new office hours and our time at the upcoming PTG will enable the future TC to be more accessible and productive. I also lead the community goal to improve the onboarding documentation, further lowering the barrier for new contributors. If elected, I will continue bridging our community with the kubernetes community. I am actively facilitating the conversations between the TC and the k8s Technical Steering Committee at the upcoming PTG meetings to share insight between both of our communities and generally share knowledge about keeping open source communities healthy. I would also like to take a more active role in pushing the unification of the community around a single CLI to simplify openstack operations to better support our users and lessen the load on developers. I think a good first step would be to work with the CLI/SDK team to build a list of items that are blocking project teams from fully implementing all their features in the openstack client. From there we can figure out what is missing from the list, which teams are affected by which blocking items and prioritize what needs to be worked on first. Thank you for your time and consideration. As I said in my platform last year, I love this community and all the awesome people in it, serving on the TC is a great experience and an honor. -Kendall Nelson (diablo_rojo)

1 0

[ironic] Recovering IPMI-type baremetal nodes in 'error' state
by Paul Browne 24 Sep '20

24 Sep '20

Hello all, I have a handful of baremetal nodes enrolled in Ironic that use the IPMI hardware type, whose motherboards were recently replaced in a hardware recall by the vendor. After the replacement, the BMC IPMI-over-LAN feature was accidentally left disabled on the nodes, and future attempts to control them with Ironic has put these nodes into the ERROR provisioning state. The IPMI-over-LAN feature on the boards has been enabled again as expected, but is there now any easy way to get the BM nodes back out of that ERROR state, without first deleting and re-enrolling them? -- ******************* Paul Browne Research Computing Platforms University Information Services Roger Needham Building JJ Thompson Avenue University of Cambridge Cambridge United Kingdom E-Mail: pfb29(a)cam.ac.uk Tel: 0044-1223-746548 *******************

2 3

LVM misconfiguration after openstack stackpack server hang and reboot
by Alan Davis 24 Sep '20

24 Sep '20

This morning my CentOS 7.7 RDO packstack installation of Rocky hung. On reboot some of the VMs won't start. This is a primary system and I need to find the most expedient way to recover without losing data. I'm not using LVM thin volumes. Any help is appreciated. Looking at nova-compute.log I see errors trying to find LUN 0 during the sysfs stage. Several machines won't boot because their root disk entries in LVM are seen as PV and booting them doesn't see them in the DM subsystem. Other machines boot but there attached disks throw LVM errors about duplicate PV and preferring the cinder-volumes VG version. LVM is showing LVs that have both "bare" entries as well as entries in cinder-volumes and it's complaining about duplicate PVs, not using lvmetad and preferring some entries because they are in the dm subsystem. I've verified that, so far, I haven't lost any data. The "bare" LV not being used as part of the DM subsystem because it's server won't boot can be mounted on the openstack host and all data on it is accessible. This host has rebooted cleanly multiple times in the past. This is the first time it's shown any problems. Am I missing an LVM filter? (unlikely since it wasn't neede before) How can I reset the LVM configuration and convince it that it's not seeing duplicate PV? How do I ensure that openstack sees the right UUID and volume ID? Excerpts from error log and output of lvs : --- nova-compute.log --- during VM start 2020-09-24 11:15:27.091 13953 INFO os_brick.initiator.connectors.iscsi [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d1c8 - default default] Trying to connect to iSCSI portal 172.10.0.40:3260 2020-09-24 11:15:29.721 13953 WARNING nova.compute.manager [req-fd32e16f-c879-402f-a32c-6be45a943c34 48af9a366301467d9fec912fd1c072c6 f9fc7b412a8446d083da1356aa370eb4 - default d efault] [instance: de7d740c-786a-4aa2-aa09-d447ae7e14b6] Received unexpected event network-vif-unplugged-79aff403-d2e4-4266-bd88-d7bd19d501a9 for instance with vm_state stopped a nd task_state powering-on. 2020-09-24 11:16:21.361 13953 WARNING os_brick.initiator.connectors.iscsi [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d 1c8 - default default] LUN 0 on iSCSI portal 172.10.0.40:3260 not found on sysfs after logging in. 2020-09-24 11:16:23.482 13953 INFO os_brick.initiator.connectors.iscsi [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d1c8 - default default] Trying to connect to iSCSI portal 172.10.0.40:3260 2020-09-24 11:17:17.741 13953 WARNING os_brick.initiator.connectors.iscsi [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d 1c8 - default default] LUN 0 on iSCSI portal 172.10.0.40:3260 not found on sysfs after logging in.: VolumeDeviceNotFound: Volume device not found at . 2020-09-24 11:17:21.864 13953 INFO os_brick.initiator.connectors.iscsi [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d1c8 - default default] Trying to connect to iSCSI portal 172.10.0.40:3260 2020-09-24 11:18:16.113 13953 WARNING os_brick.initiator.connectors.iscsi [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d 1c8 - default default] LUN 0 on iSCSI portal 172.10.0.40:3260 not found on sysfs after logging in.: VolumeDeviceNotFound: Volume device not found at . 2020-09-24 11:18:17.252 13953 INFO nova.compute.manager [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d1c8 - default defa ult] [instance: de7d740c-786a-4aa2-aa09-d447ae7e14b6] Successfully reverted task state from powering-on on failure for instance. 2020-09-24 11:18:17.279 13953 ERROR oslo_messaging.rpc.server [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d1c8 - defaul t default] Exception during message handling: VolumeDeviceNotFound: Volume device not found at . 2020-09-24 11:18:17.279 13953 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2020-09-24 11:18:17.279 13953 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 163, in _process_incoming 2020-09-24 11:18:17.279 13953 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) --- lvs output --- I've annotated 1 machine's disks to illustrate the relationship between the volume-*** cinder-volumes vg entries and the "bare" lv seen as directly accessible from the host. There are 3 servers that won't boot, they are the one's who's home/vg_home and encrypted_home/encrypted_vg entries are shown. WARNING: Not using lvmetad because duplicate PVs were found. WARNING: Use multipath or vgimportclone to resolve duplicate PVs? WARNING: After duplicates are resolved, run "pvscan --cache" to enable lvmetad. WARNING: Not using device /dev/sdu for PV yZy8Xk-foKT-ovjV-0EZv-VxEM-GqiP-WH7k53. == backup_lv/encrypted_vg WARNING: Not using device /dev/sdv for PV tHA9ui-eSIO-MDmI-RM3u-3Bf4-Dznb-Ha3XfP. == varoptgitlab/encrypted_vg WARNING: Not using device /dev/sdm for PV 5eoyCa-sMO4-b7O4-jIfh-byZE-L5pS-3lOu0D. WARNING: Not using device /dev/sdp for PV 3BI0nV-TP0k-rgPC-PrjH-FT7z-reMe-ec1spj. WARNING: Not using device /dev/sdt for PV ILdbcY-VFCm-fnH6-Y3jc-pdWZ-fnl8-PH3TPe. == storage_lv/encrypted_vg WARNING: Not using device /dev/sdr for PV zowU2N-oaBh-r4cO-cxgX-YYiq-Kf3q-mqlHfK. WARNING: PV yZy8Xk-foKT-ovjV-0EZv-VxEM-GqiP-WH7k53 prefers device /dev/cinder-volumes/volume-c8da1abf-7143-422c-9ee5-b2724a71c8ff because device is in dm subsystem. WARNING: PV tHA9ui-eSIO-MDmI-RM3u-3Bf4-Dznb-Ha3XfP prefers device /dev/cinder-volumes/volume-0a12012f-8c2e-41fb-aa0c-a7ae99c62487 because device is in dm subsystem. WARNING: PV 5eoyCa-sMO4-b7O4-jIfh-byZE-L5pS-3lOu0D prefers device /dev/cinder-volumes/volume-990a057c-46cc-4a81-ba02-28b72c34791d because device is in dm subsystem. WARNING: PV 3BI0nV-TP0k-rgPC-PrjH-FT7z-reMe-ec1spj prefers device /dev/cinder-volumes/volume-b6a9da6e-1958-46ea-90b4-ac1aebed8c04 because device is in dm subsystem. WARNING: PV ILdbcY-VFCm-fnH6-Y3jc-pdWZ-fnl8-PH3TPe prefers device /dev/cinder-volumes/volume-302dd53b-7d05-4f6d-9ada-8f2ed6e1d4c6 because device is in dm subsystem. WARNING: PV zowU2N-oaBh-r4cO-cxgX-YYiq-Kf3q-mqlHfK prefers device /dev/cinder-volumes/volume-df006472-be7a-4957-972a-1db4463f5d67 because device is in dm subsystem. LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert home centos_stack3 -wi-ao---- 4.00g root centos_stack3 -wi-ao---- 50.00g swap centos_stack3 -wi-ao---- 4.00g _snapshot-05b1e46b-1ae3-4cd0-9117-3fb53a6d94b0 cinder-volumes swi-a-s--- 20.00g volume-1d0ff5d5-93a3-44e8-8bfa-a9290765c8c6 0.00 lv_filestore cinder-volumes -wi-ao---- 1.00t ... volume-c8da1abf-7143-422c-9ee5-b2724a71c8ff cinder-volumes -wi-ao---- 100.00g volume-0a12012f-8c2e-41fb-aa0c-a7ae99c62487 cinder-volumes -wi-ao---- 60.00g volume-990a057c-46cc-4a81-ba02-28b72c34791d cinder-volumes -wi-ao---- 200.00g volume-b6a9da6e-1958-46ea-90b4-ac1aebed8c04 cinder-volumes -wi-ao---- 30.00g volume-302dd53b-7d05-4f6d-9ada-8f2ed6e1d4c6 cinder-volumes -wi-ao---- 60.00g volume-df006472-be7a-4957-972a-1db4463f5d67 cinder-volumes -wi-ao---- 250.00g ... volume-f3250e15-bb9c-43d1-989d-8a8f6635a416 cinder-volumes -wi-ao---- 20.00g volume-fc1d5fcb-fda1-456b-a89d-582b7f94fb04 cinder-volumes -wi-ao---- 300.00g volume-fc50a717-0857-4da3-93cb-a55292f7ed6d cinder-volumes -wi-ao---- 20.00g volume-ff94e2d6-449b-495d-82e6-0debd694c1dd cinder-volumes -wi-ao---- 20.00g data2 data2_vg -wi-a----- <300.00g data data_vg -wi-a----- 1.79t backup_lv encrypted_vg -wi------- <100.00g == ...WH7k53 storage_lv encrypted_vg -wi------- <60.00g == ...PH3TPe varoptgitlab_lv encrypted_vg -wi------- <200.00g varoptgitlab_lv encrypted_vg -wi------- <30.00g varoptgitlab_lv encrypted_vg -wi------- <60.00g == ...Ha3XfP encrypted_home home_vg -wi-a----- <40.00g encrypted_home home_vg -wi------- <60.00g pub pub_vg -wi-a----- <40.00g pub_lv pub_vg -wi------- <250.00g rpms repo -wi-a----- 499.99g home vg_home -wi-a----- <40.00g gtri_pub vg_pub -wi-a----- 20.00g pub vg_pub -wi-a----- <40.00g -- Alan Davis Principal System Administrator Apogee Research LLC

1 1

[Glance] PTL on Vacation
by Abhishek Kekane 24 Sep '20

24 Sep '20

Hi All, I'm starting my vacations from 28th September and will be back on October 5th. Please direct any issues to the rest of the core team. Also there will be no glance weekly meeting on 01 October [1]. [1] https://etherpad.opendev.org/p/glance-team-meeting-agenda Thanks, Abhishek

1 0

[all][tc][goals] Migrate CI/CD jobs to new Ubuntu LTS Focal: Week R-4 Update
by Ghanshyam Mann 24 Sep '20

24 Sep '20

Hello Everyone, Please find the week R-4 updates on 'Ubuntu Focal migration' community goal. Its time to force the base jobs migration which can break the projects gate if not yet taken care of. Read below for the plan. Tracking: https://storyboard.openstack.org/#!/story/2007865 Progress: ======= * We are close to V-3 release and this is time we have to complete this migration otherwise doing it in RC period can add unnecessary and last min delay. I am going to plan this migration in two-part. This will surely break some projects gate which is not yet finished the migration but we have to do at some time. Please let me know if any objection to the below plan. * Part1: Migrating tox base job tomorrow (8th Sept): ** I am going to open tox base jobs migration (doc, unit, functional, lower-constraints etc) to merge by tomorrow. which is this series (all base patches of this): https://review.opendev.org/#/c/738328/ . **There are few repos still failing on requirements lower-constraints job specifically which I tried my best to fix as many as possible. Many are ready to merge also. Please merge or work on your projects repo testing before that or fix on priority if failing. * Part2: Migrating devstack/tempest base job on 10th sept: * We have few open bugs for this which are not yet resolved, we will see how it goes but the current plan is to migrate by 10th Sept. ** Bug#1882521 ** DB migration issues, *** alembic and few on telemetry/gnocchi side https://github.com/sqlalchemy/alembic/issues/699, https://storyboard.openstack.org/#!/story/2008003 Testing Till now: ============ * ~200 repos gate have been tested or fixed till now. ** https://review.opendev.org/#/q/topic:migrate-to-focal+(status:abandoned+OR+… * ~100 repos are under test and failing. Debugging and fixing are in progress (If you would like to help, please check your project repos if I am late to fix them): ** https://review.opendev.org/#/q/topic:migrate-to-focal+status:open * ~30repos fixes ready to merge: ** https://review.opendev.org/#/q/topic:migrate-to-focal+status:open+label%3AV… Bugs Report: ========== 1. Bug#1882521. (IN-PROGRESS) There is open bug for nova/cinder where three tempest tests are failing for volume detach operation. There is no clear root cause found yet -https://bugs.launchpad.net/cinder/+bug/1882521 We have skipped the tests in tempest base patch to proceed with the other projects testing but this is blocking things for the migration. 2. DB migration issues (IN-PROGRESS) * alembic and few on telemetry/gnocchi side https://github.com/sqlalchemy/alembic/issues/699, https://storyboard.openstack.org/#!/story/2008003 3. We encountered the nodeset name conflict with x/tobiko. (FIXED) nodeset conflict is resolved now and devstack provides all focal nodes now. 4. Bug#1886296. (IN-PROGRESS) pyflakes till 2.1.0 is not compatible with python 3.8 which is the default python version on ubuntu focal[1]. With pep8 job running on focal faces the issue and fail. We need to bump the pyflakes to 2.1.1 as min version to run pep8 jobs on py3.8. As of now, many projects are using old hacking version so I am explicitly adding pyflakes>=2.1.1 on the project side[2] but for the long term easy maintenance, I am doing it in 'hacking' requirements.txt[3] nd will release a new hacking version. After that project can move to new hacking and do not need to maintain pyflakes version compatibility. 5. Bug#1886298. (IN-PROGRESS) 'Markupsafe' 1.0 is not compatible with the latest version of setuptools[4], We need to bump the lower-constraint for Markupsafe to 1.1.1 to make it work. There are a few more issues[5] with lower-constraint jobs which I am debugging. What work to be done on the project side: ================================ This goal is more of testing the jobs on focal and fixing bugs if any otherwise migrate jobs by switching the nodeset to focal node sets defined in devstack. 1. Start a patch in your repo by making depends-on on either of below: devstack base patch if you are using only devstack base jobs not tempest: Depends-on: https://review.opendev.org/#/c/731207/ OR tempest base patch if you are using the tempest base job (like devstack-tempest): Depends-on: https://review.opendev.org/#/c/734700/ Both have depends-on on the series where I am moving unit/functional/doc/cover/nodejs tox jobs to focal. So you can test the complete gate jobs(unit/functional/doc/integration) together. This and its base patches - https://review.opendev.org/#/c/738328/ Example: https://review.opendev.org/#/c/738126/ 2. If none of your project jobs override the nodeset then above patch will be testing patch(do not merge) otherwise change the nodeset to focal. Example: https://review.opendev.org/#/c/737370/ 3. If the jobs are defined in branchless repo and override the nodeset then you need to override the branches variant to adjust the nodeset so that those jobs run on Focal on victoria onwards only. If no nodeset is overridden then devstack being branched and stable base job using bionic/xenial will take care of this. Example: https://review.opendev.org/#/c/744056/2 4. If no updates need you can abandon the testing patch (https://review.opendev.org/#/c/744341/) If it need updates then modify the same patch with proper commit msg, once it pass the gate then remove the Depends-On so that you can merge your patch before base jobs are switched to focal. This way we make sure no gate downtime in this migration. Example: https://review.opendev.org/#/c/744056/1..2//COMMIT_MSG Once we finish the testing on projects side and no failure then we will merge the devstack and tempest base patches. Important things to note: =================== * Do not forgot to add the story and task link to your patch so that we can track it smoothly. * Use gerrit topic 'migrate-to-focal' * Do not backport any of the patches. References: ========= Goal doc: https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-j… Storyboard tracking: https://storyboard.openstack.org/#!/story/2007865 [1] https://github.com/PyCQA/pyflakes/issues/367 [2] https://review.opendev.org/#/c/739315/ [3] https://review.opendev.org/#/c/739334/ [4] https://github.com/pallets/markupsafe/issues/116 [5] https://zuul.opendev.org/t/openstack/build/7ecd9cf100194bc99b3b70fa1e6de032 -gmann

7 17

[tripleo] rdo infrastructure maintenance
by Wesley Hayutin 24 Sep '20

24 Sep '20

Greetings, There is some maintenance on the rdo infra that is causing check and gate jobs to fail upstream. The situation is actively being worked on at this time. You may find errors in your check / gate jobs.. like the following. TASK [oooci-build-images : Download TripleO source image] 2020-09-24 10:26:35.615996 | primary | ERROR 2020-09-24 10:26:35.617685 | primary | { 2020-09-24 10:26:35.617774 | primary | "attempts": 60, 2020-09-24 10:26:35.617850 | primary | "msg": "Failed to connect to images.rdoproject.org at port 443: [Errno 113] No route to host", 2020-09-24 10:26:35.617929 | primary | "status": -1, 2020-09-24 10:26:35.618001 | primary | "url": "https://images.rdoproject.org/CentOS-8-x86_64-GenericCloud.qcow2" 2020-09-24 10:26:35.618072 | primary | } https://5134c188955ee39fd51b-cd04c057bb6c1703504e41a1dbc31642.ssl.cf5.rackc… Sorry for the trouble, we'll update this email when we're clear. 0/

1 1

[manila] Doc-a-thon event coming up next Thursday (Aug 6th)
by Victoria Martínez de la Cruz 24 Sep '20

24 Sep '20

Hi folks, We will be organizing a doc-a-thon next Thursday, August 6th, with the main goal of improving our docs for the next release. We will be gathering on our Freenode channel #openstack-manila after our weekly meeting (3pm UTC) and also using a videoconference tool (exact details TBC) to go over a curated list of opened doc bugs we have here [0]. *Your* participation is truly valued, being you an already Manila contributor or if you are interested in contributing and you didn't know how, so looking forward to seeing you there :) Cheers, Victoria [0] https://ethercalc.openstack.org/ur17jprbprxx

2 3

[oslo] PTL Non-candidacy: I mean it this time :-P
by Ben Nemec 24 Sep '20

24 Sep '20

I'm eminently familiar with midwest goodbyes, but an entire cycle to actually leave is taking it a bit far, don't you think? :-) Seriously though, this is two cycles in a row that we've had to scramble late in a cycle to finish basic community goals, mostly because of my lack of attention. Now that we've all sort of adapted to the whole global pandemic thing I'm hoping my abdication will stick this time. I'll still be around and try to help out when I can, but it's past time for me to turn the leadership of Oslo over to someone else. We've got a great team and I'm sure any one of them will do a great job! Thanks. -Ben

5 4

[all][elections][tc] Stepping down from the TC
by Jean-Philippe Evrard 24 Sep '20

24 Sep '20

Hello everyone, This is probably not a surprise for most of you, but I think it's worth writing it down: I won't be a candidate for another term at the TC. It was a pleasure to work with all of you. I am not leaving because I don't find the TC interesting anymore, quite the opposite. I will probably still lurk and follow the channels and ML. I just have switched to (yet) another duty at my employer, keeping me away from OpenStack. Next to this, I believe it's good to have some fresh members in the TC, it's been a while I am part of this family now :) For those interested by running the TC: Don't hesitate to run! We need fresh ideas and motivated people. It's not by having always the same people at the helm that OpenStack will naturally or drastically evolve. If you want to change OpenStack, be the change! Thanks to all of you. It was nice. Regards, Jean-Philippe Evrard (evrardjp)

11 11

RE: [tacker] Propose Toshiaki Takahashi for tacker core
by TAKAHASHI TOSHIAKI(高橋　敏明) 24 Sep '20

24 Sep '20

Hi Yasufumi and Team, Thank you so much! I'm glad to join core team. I'll continue to contribute for Tacker community activation! Toshiaki > -----Original Message----- > From: Yasufumi Ogawa <yasufum.o(a)gmail.com> > Sent: Thursday, September 24, 2020 6:43 PM > To: openstack-discuss(a)lists.openstack.org; TAKAHASHI TOSHIAKI(高橋　敏明) > <ts-takahashi(a)nec.com> > Subject: ##freemail## Re: [tacker] Propose Toshiaki Takahashi for tacker core > > On 2020/09/17 4:06, yasufum wrote: > > Toshiaki Takahashi (takahashi-tsc) has been so active for reviewing, > > fixing bugs and answering questions in the recent releases [1][2] and > > had several sessions on summits for Tacker. In addition, he is now > > well distinguished as one of the responsibility from ETSI-NFV standard > > community as a contributor between the standard and implementation for > > the recent contributions for both of OpenStack and ETSI. > > > > I'd appreciate if we add Toshiaki to the core team. > > > > [1] https://www.stackalytics.com/?company=nec&module=tacker > > [2] > > https://www.stackalytics.com/?user_id=t-takahashi%40ig.jp.nec.com&metr > > ic=marks > > Thank you everyone! I've seen only positive responses, so I've added Toshiaki as a > new core of tacker team. > > Congratulations, Toshiaki! > > > > > > > Regards, > > Yasufumi > >

1 0

[tacker] Propose Toshiaki Takahashi for tacker core
by yasufum 24 Sep '20

24 Sep '20

Toshiaki Takahashi (takahashi-tsc) has been so active for reviewing, fixing bugs and answering questions in the recent releases [1][2] and had several sessions on summits for Tacker. In addition, he is now well distinguished as one of the responsibility from ETSI-NFV standard community as a contributor between the standard and implementation for the recent contributions for both of OpenStack and ETSI. I'd appreciate if we add Toshiaki to the core team. [1] https://www.stackalytics.com/?company=nec&module=tacker [2] https://www.stackalytics.com/?user_id=t-takahashi%40ig.jp.nec.com&metric=ma… Regards, Yasufumi

10 9

Error log
by Issac Chan 24 Sep '20

24 Sep '20

Hi all, May you have a look on this log file? I cannot start trove guest instance database normally. Best wishes, Issac

1 0