- openstack-discuss - lists.openstack.org

[all] DevStack jobs broken due to setuptools not available for Python 2
by Radosław Piliszek 14 Jan '20

14 Jan '20

Hi all, I noticed DevStack jobs fail all over the place [1] due to: UnsupportedPythonVersion: Package 'setuptools' requires a different Python: 2.7.17 not in '>=3.5' Bug reported in [2]. Notice USE_PYTHON3=True does not help as stack.sh is hardcoded to versionless Python. [1] https://zuul.opendev.org/t/openstack/builds?result=RETRY_LIMIT&result=FAILU… [2] https://bugs.launchpad.net/devstack/+bug/1859350 -yoctozepto

6 8

Designate zone troubleshooting
by Albert Braden 14 Jan '20

14 Jan '20

1 0

[ops] No ops meetup team meeting tomorrow (2020/1/14) on IRC
by Chris Morgan 14 Jan '20

14 Jan '20

We had a great OpenStack Ops meetup last week in London. Those involved now need to catch up on other work, so we'll resume regular meetings on Jan 21st. Our thanks to everyone who attended and/or helped make it one of the best meetups in a while. Chris -- Chris Morgan <mihalis68(a)gmail.com>

1 0

[blazar] No IRC meeting tomorrow
by Pierre Riteau 14 Jan '20

14 Jan '20

Hello, As announced in the last meeting, due to travel the weekly Blazar IRC meeting of January 14 is cancelled. The next meeting will be held on Jan 21. Thanks, Pierre Riteau (priteau)

1 0

Re: [magnum]: K8s cluster creation times out. OpenStack Train : [ERROR]: Unable to render networking. Network config is likely broken
by feilong 14 Jan '20

14 Jan '20

Hi Bhupathi, Firstly, I would suggest setting the use_podman=False when using fedora atomic image. And it would be nice to set the "kube_tag", e.g. v1.15.6 explicitly. Then please trigger a new cluster creation. Then if you still run into error. Here is the debug steps: 1. ssh into the master node, check log /var/log/cloud-init-output.log 2. If there is no error in above log file, then run journalctl -u heat-container-agent to check the heat-container-agent log. If above step is correct, then you must be able to see something useful here. On 11/01/20 12:15 AM, Bhupathi, Ramakrishna wrote: > > Wang, > > Here it is . I added the labels subsequently. My nova and neutron are > working all right as I installed various systems there working with no > issues.. > > > > > > *From:*Feilong Wang [mailto:feilong@catalyst.net.nz] > *Sent:* Thursday, January 9, 2020 6:12 PM > *To:* openstack-discuss(a)lists.openstack.org > *Subject:* Re: [magnum]: K8s cluster creation times out. OpenStack > Train : [ERROR]: Unable to render networking. Network config is likely > broken > > > > Hi Bhupathi, > > Could you please share your cluster template? And please make sure > your Nova/Neutron works. > > > > On 10/01/20 2:45 AM, Bhupathi, Ramakrishna wrote: > > Folks, > > I am building a Kubernetes Cluster( Openstack Train) and using > fedora atomic-29 image . The nodes come up fine ( I have a simple > 1 master and 1 node) , but the cluster creation times out, and > when I access the cloud-init logs I see this error . Wondering > what I am missing as this used to work before. I wonder if this > is image related . > > > > [ERROR]: Unable to render networking. Network config is likely > broken: No available network renderers found. Searched through > list: ['eni', 'sysconfig', 'netplan'] > > > > Essentially the stack creation fails in “kube_cluster_deploy” > > > > Can somebody help me debug this ? Any help is appreciated. > > > > --RamaK > > The contents of this e-mail message and > any attachments are intended solely for the > addressee(s) and may contain confidential > and/or legally privileged information. If you > are not the intended recipient of this message > or if this message has been addressed to you > in error, please immediately alert the sender > by reply e-mail and then delete this message > and any attachments. If you are not the > intended recipient, you are notified that > any use, dissemination, distribution, copying, > or storage of this message or any attachment > is strictly prohibited. > > -- > Cheers & Best regards, > Feilong Wang (王飞龙) > Head of R&D > Catalyst Cloud - Cloud Native New Zealand > -------------------------------------------------------------------------- > Tel: +64-48032246 > Email: flwang(a)catalyst.net.nz <mailto:flwang@catalyst.net.nz> > Level 6, Catalyst House, 150 Willis Street, Wellington > -------------------------------------------------------------------------- > The contents of this e-mail message and > any attachments are intended solely for the > addressee(s) and may contain confidential > and/or legally privileged information. If you > are not the intended recipient of this message > or if this message has been addressed to you > in error, please immediately alert the sender > by reply e-mail and then delete this message > and any attachments. If you are not the > intended recipient, you are notified that > any use, dissemination, distribution, copying, > or storage of this message or any attachment > is strictly prohibited. -- Cheers & Best regards, Feilong Wang (王飞龙) ------------------------------------------------------ Senior Cloud Software Engineer Tel: +64-48032246 Email: flwang(a)catalyst.net.nz Catalyst IT Limited Level 6, Catalyst House, 150 Willis Street, Wellington ------------------------------------------------------

1 0

[cinder] ussuri virtual mid-cycle next week
by Brian Rosmaita 13 Jan '20

13 Jan '20

The poll results are in. There was only one time when everyone can meet (apologies to the "if need be" people, but the need be). Session One of the Cinder Ussuri virtual mid-cycle will be held: DATE: 21 JANUARY 2020 TIME: 1300-1500 UTC LOCATION: https://bluejeans.com/3228528973 The meeting will be recorded. Please add topics to the planning etherpad: https://etherpad.openstack.org/p/cinder-ussuri-mid-cycle-planning cheers, brian

1 0

[horizon][stein]issue:
by prashant 13 Jan '20

13 Jan '20

when i m deleting multiple instances into the stein, could not able to see all remaining instances until i refresh instances list again.

1 0

[all] Announcing OpenStack Victoria!
by Sean McGinnis 13 Jan '20

13 Jan '20

Hello everyone, The polling results are in, and the legal vetting process has now completed. We now have an official name for the "V" release. The full results of the poll can be found here: https://civs.cs.cornell.edu/cgi-bin/results.pl?num_winners=1&id=E_13ccd49b6… While Victoria and Vancouver were technically a tie, based on the Minimax rankingi, it puts Victoria slightly ahead of Vancouver based on the votes. In addition to that, we chose to have the TC do a tie breaker vote which confirmed Victoria as the winner. Victoria is the capital city of British Columbia: https://en.wikipedia.org/wiki/Victoria,_British_Columbia Thank you all for participating in the release naming! Sean

2 1

[neutron] Bug deputy report - Jan 06 to 12
by Hongbin Lu 13 Jan '20

13 Jan '20

1 0

[tripleo][ci] Proposing Sorin Barnea as TripleO-CI core
by Marios Andreou 12 Jan '20

12 Jan '20

I would like to propose Sorin Barnea (ssbarnea(a)redhat.com) as core on tripleo-ci repos (tripleo-ci, tripleo-quickstart, tripleo-quickstart-extras). Sorin has been a member of the tripleo-ci team for over one and a half years and has made many contributions across the tripleo-ci repos and beyond - highlights include helping the team to adopt molecule testing, leading linting efforts/changes/fixes and many others. Please vote by replying to this thread with +1 or -1 for any objections thanks marios

9 8

[tripleo][ci] Proposing Chandan Kumar and Arx Cruz as TripleO-CI cores
by Ronelle Landy 12 Jan '20

12 Jan '20

Hello All, I'd like to propose Arx Cruz (arxcruz(a)redhat.com) and Chandan Kumar ( chkumar(a)redhat.com) as core on tripleo-ci repos (tripleo-ci, tripleo-quickstart, tripleo-quickstart-extras). In addition to the extensive work that Arx and Chandan have done on the Tempest-related repos ( and Tempest interface/settings within the Tripleo CI repos) , they have become active contributors to the core Tripleo CI repos, in general, in the past two years. Please vote by replying to this thread with +1 or -1 for any objections. We will close the vote 7 days from now. Thank you, Ronelle

5 5

[keystone] Keystone Team Update - Week of 6 January 2020
by vishakha agarwal 11 Jan '20

11 Jan '20

# Keystone Team Update - Week of 6 January 2020 ## News ### User Support and Bug Duty The person in-charge for bug duty for current and upcoming week can be seen on the etherpad [1] [1] https://etherpad.openstack.org/p/keystone-l1-duty ## Action Items The one-fourth of the ussuri cycle is almost over. We need to find a new mechanism for the retrospective and to check our progress for this cycle which is more convenient and less time consuming for the members. ## Open Specs Ussuri specs: https://bit.ly/2XDdpkU Ongoing specs: https://bit.ly/2OyDLTh ## Recently Merged Changes Search query: https://bit.ly/2pquOwT We merged 19 changes this week. ## Changes that need Attention Search query: https://bit.ly/2tymTje There are 37 changes that are passing CI, not in merge conflict, have no negative reviews and aren't proposed by bots. ### Priority Reviews * Community Goals https://review.opendev.org/#/c/699127/ [ussuri][goal] Drop python 2.7 support and testing keystone-tempest-plugin https://review.opendev.org/#/c/699126/ [ussuri][goal] Drop python 2.7 support and testing ldappool https://review.opendev.org/#/c/699119/ [ussuri][goal] Drop python 2.7 support and testing python-keystoneclient * Special Requests https://review.opendev.org/#/c/662734/ Change the default Identity endpoint to internal https://review.opendev.org/#/c/699013/ Always have username in CADF initiator https://review.opendev.org/#/c/700826/ Fix role_assignments role.id filter ## Bugs This week we opened 3 new bugs and closed 5. Bugs opened (3) Bug #1858410 (keystone:Low): Got error 'NoneType' when executing unittest on stable/rocky - Opened by Eric Xie https://bugs.launchpad.net/keystone/+bug/1858410 Bug #1858186 (keystoneauth:Undecided): http_log_request will print debug info include pki certificate which is unsafety - Opened by kuangpeiling https://bugs.launchpad.net/keystoneauth/+bug/1858186 Bug #1858189 (keystoneauth:Undecided): http_log_request will print debug info include pki certificate which is unsafety - Opened by kuangpeiling https://bugs.launchpad.net/keystoneauth/+bug/1858189 Bugs closed (5) Bug #1858186 (keystoneauth:Undecided) https://bugs.launchpad.net/keystoneauth/+bug/1858186 Bug #1856881 (keystone:Medium): keystone-manage bootstrap fails with ambiguous role names - Fixed by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1856881 Bug #1856962 (keystone:Undecided): openid method failed when federation_group_ids is empty list - Fixed by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1856962 Bug #1857086 (keystone: Won't Fix) https://bugs.launchpad.net/keystone/+bug/1857086 Bug #1831018 (keystone: Invalid)https://bugs.launchpad.net/keystone/+bug/1831018 ## Milestone Outlook https://releases.openstack.org/ussuri/schedule.html Spec freeze is on the week of 10 February. All the specs targeted for this cycle should be ready for the review soon. ## Help with this newsletter Help contribute to this newsletter by editing the etherpad: https://etherpad.openstack.org/p/keystone-team-newsletter

1 0

[aodh][keystone] handling of webhook / alarm authentication
by info＠dantalion.nl 11 Jan '20

11 Jan '20

Hello, I was wondering how a service receiving an aodh webhook could perform authentication? The documentation describes the webhook as a simple post-request so I was wondering if a keystone token context is available when these requests are received? If not, I was wondering if anyone had any recommendation on how to perform authentication upon received post-requests? So far I have come up with limiting the functionality of these webhooks such as rate-limiting and administrators having to explicitly enable these webhooks before they work. Hope anyone else could provide further valuable information. Kind regards, Corne Lukken Watcher core-reviewer

3 4

[release] Release countdown for week R-17, January 13-17
by Sean McGinnis 11 Jan '20

11 Jan '20

Development Focus ----------------- The Ussuri-2 milestone will happen in next month, on February 13. Ussuri-related specs should now be finalized so that teams can move to implementation ASAP. Some teams observe specific deadlines on the second milestone (mostly spec freezes): please refer to https://releases.openstack.org/ussuri/schedule.html for details. General Information ------------------- Please remember that libraries need to be released at least once per milestone period. At milestone 2, the release team will propose releases for any library that has not been otherwise released since milestone 1. Other non-library deliverables that follow the cycle-with-intermediary release model should have an intermediary release before milestone-2. Those who haven't will be proposed to switch to the cycle-with-rc model, which is more suited to deliverables that are released only once per cycle. At milestone-2 we also freeze the contents of the final release. If you have a new deliverable that should be included in the final release, you should make sure it has a deliverable file in: https://opendev.org/openstack/releases/src/branch/master/deliverables/ussuri You should request a beta release (or intermediary release) for those new deliverables by milestone-2. We understand some may not be quite ready for a full release yet, but if you have something minimally viable to get released it would be good to do a 0.x release to exercise the release tooling for your deliverables. See the MembershipFreeze description for more details: https://releases.openstack.org/ussuri/schedule.html#u-mf Finally, now may be a good time for teams to check on any stable releases that need to be done for your deliverables. If you have bugfixes that have been backported, but no stable release getting those. If you are unsure what is out there committed but not released, in the openstack/releases repo, running the command "tools/list_stable_unreleased_changes.sh <cycle_name>" gives a nice report. Upcoming Deadlines & Dates -------------------------- Ussuri-2 Milestone: February 13 (R-13 week)

1 0

[tripleo] introducing zuul-runner
by Wesley Hayutin 11 Jan '20

11 Jan '20

Greetings, Hey everyone I want to highlight work that some of our good friends in zuul are working another way to try and help everyone debug their jobs. The tool is called zuul-runner and the spec is here [1], code is here [2] Please have a look through the spec and vote to show support for Tristan's work. Thanks to Arx Cruz for contributing and testing it as well w/ TripleO jobs. This will be another very nice tool in the toolbox for us if we can get it through. Thanks! [1] https://review.opendev.org/#/c/681277/ [2] https://review.opendev.org/#/c/607078/

1 0

[neutron][rabbitmq] Neutron-server service shows deprecated "AMQPDeprecationWarning"
by Amjad Kotobi 10 Jan '20

10 Jan '20

Hi, Today we are facing losing connection of neutron especially during instance creation or so as “systemctl status neutron-server” shows below message be deprecated in amqp 2.2.0. Since amqp 2.0 you have to explicitly call Connection.connect() before using the connection. W_FORCE_CONNECT.format(attr=attr))) /usr/lib/python2.7/site-packages/amqp/connection.py:304: AMQPDeprecationWarning: The .transport attribute on the connection was accessed before the connection was established. This is supported for now, but will be deprecated in amqp 2.2.0. Since amqp 2.0 you have to explicitly call Connection.connect() before using the connection. W_FORCE_CONNECT.format(attr=attr))) OpenStack release which we are running is “Pike”. Is there any way to remedy this? Thanks Amjad

3 4

Re: [charms][watcher] OpenStack Watcher Charm
by Corey Bryant 10 Jan '20

10 Jan '20

On Fri, Jan 10, 2020 at 6:12 AM James Page <james.page(a)canonical.com> wrote: > Hi Stamatis > > Thankyou for this work! > > I'll take a look at your charm over the next few days. > > On Wed, Jan 8, 2020 at 11:25 AM Stamatis Katsaounis < > skatsaounis(a)admin.grnet.gr> wrote: > >> Hi all, >> >> Purpose of this email is to let you know that we released an unofficial >> charm of OpenStack Watcher [1]. This charm gave us the opportunity to >> deploy OpenStack Watcher to our charmed OpenStack deployment. >> >> After seeing value in it, we decided to publish it through GRNET GitHub >> Organization account for several reasons. First of all, we would love to >> get feedback on it as it is our first try on creating an OpenStack reactive >> charm. Secondly, we would be glad to see other OpenStack operators deploy >> Watcher and share with us knowledge on the project and possible use cases. >> Finally, it would be ideal to come up with an official OpenStack Watcher >> charm repository under charmers umbrella. By doing this, another OpenStack >> project is going to be available not only for Train version but for any >> future version of OpenStack. Most important, the CI tests are going to >> ensure that the code is not broken and persuade other operators to use it. >> >> Before closing my email, I would like to give some insight on the >> architecture of the code base and the deployment process. To begin with, >> charm-watcher is based on other reactive OpenStack charms. During its >> deployment Barbican, Designate, Octavia and other charms' code bases were >> counseled. Furthermore, the structure is the same as any official OpenStack >> charm, of course without functional tests, which is something we cannot >> provide. >> > I'd suggest that we initiate the process to include your watcher charm as > part of the OpenStack Charmers project on opendev.org; once the initial > migration completes adding some functional tests should be fairly easy as > you'll be able to run them on the Canonical 3rd party CI infrastructure. > > This requires that a couple of reviews be raised - here are examples for > the new Manila Ganesha charms: > > https://review.opendev.org/#/c/693463/ > https://review.opendev.org/#/c/693462/ > > One is for the infrastructure setup, the other is to formally include the > repositories as part of the TC approved project. If you would like to > raise them for the watcher charm I'm happy to review with Frode (who is the > current PTL). > >> Speaking about the deployment process, apart from having a basic charmed >> OpenStack deployment, operator has to change two tiny configuration options >> on Nova cloud controller and Cinder. As explained in the Watcher >> configuration guide, special care has to be done with Oslo notifications >> for Nova and Cinder [2]. In order to achieve that in charmed OpenStack some >> issues were met and solved with the following patches [3], [4], [5], [6]. >> With these patches, operator can set the extra Oslo configuration and this >> is the only extra configuration needs to take place. Finally, with [7] >> Keystone charm can accept a relation with Watcher charm instead of ignoring >> it. >> >> To be able to deploy GRNET Watcher charm on Train, patches [3], [4], [5] >> and [7] have to be back-ported to stable/19.10 branch but that will require >> the approval of charmers team. Please let me know if such an option is >> available and in that case I am going to open the relevant patches. >> Furthermore, if you think that it could be a good option to create a spec >> and then introduce an official Watcher charm, I would love to help on that. >> > I'd rather we wait until the 20.02 charm release - dependent changes have > all landed and will be included. > > I wish all a happy new year and I am looking forward to your response and >> possible feedback. >> > > Happy new year to you as well! > > PS. If we could have an Ubuntu package for watcher-dashboard [8] like >> octavia-dashboard [9] we would release a charm for it as well. >> > > I'll chat with coreycb and see if we might be able to package that for > 20.04/Ussuri. > > Hi, I'll take a look at packaging watcher-dashboard. Corey Cheers > > James > >> >> -- Corey

1 0

[largescale-sig] Next meeting: Jan 15, 9utc
by Thierry Carrez 10 Jan '20

10 Jan '20

Hi everyone, The Large Scale SIG will have a meeting next week on Wednesday, Jan 15 at 9 UTC[1] in #openstack-meeting on IRC. I'll not be around but Belmiro Moreira volunteered to chair the meeting. [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200115T09 We had several TODOs out of our December meeting, so I invite you to review the summary of that meeting in preparation of the next: http://lists.openstack.org/pipermail/openstack-discuss/2019-December/011667… As always, the agenda for the meeting next week is available at: https://etherpad.openstack.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez (ttx)

1 0

[kolla] Kayobe 7.0.0 released for Train
by Mark Goddard 10 Jan '20

10 Jan '20

Hi, I'm pleased to announce the release of Kayobe 7.0.0 - the first release in the Train series, and the first release as a deliverable of the Kolla project. Full details are available in the release notes which are available here: https://docs.openstack.org/releasenotes/kayobe/train.html We anticipate significant changes during the Train release series to support a migration to CentOS 8. We will communicate which releases are affected. Thanks to everyone who contributed to this release, and for the Kolla project for accepting us. I look forward to the continued integration of these teams. Cheers, Mark

1 0

[release] decentralising release approvals
by Mark Goddard 10 Jan '20

10 Jan '20

Hi, If this topic has been discussed many times already then someone please say so and we can leave it alone. As kolla PTL and ironic release liaison I've proposed a number of release patches recently. Generally the release team is good at churning through these, but sometimes patches can hang around for a while. Usually a ping on IRC will get things moving again within a day or so (thanks in particular to Sean who has been very responsive). Related to the recent discussion about decentralising stable branch maintenance, should we do this for releases too? To be clear, I'm proposing giving project teams more control over their own releases. I brought this up in IRC recently and there was a brief discussion. I suggested that releases are hard to undo, and Monty corrected me by saying they are impossible to undo. Still, if teams (or a subset of their members) had more ownership of their releases, they would become more familiar with the process, and the risk would be reduced. I'm not suggesting that release team should be disbanded - there is clearly work to do to maintain the tooling, determine and communicate the schedule, and more. But there's a lot of toil involved in checking and approving patches to the releases repo, and it's done by some of our most senior, busy colleagues. There are a number of checks that are performed automatically by the tooling and used to gate merges. I have a few questions for the release team about these reviews. * What manual checks do you do beyond those that are currently automated? * Could the above checks be automated? * What issues have you caught that were not caught by CI jobs? Hopefully I haven't offended anyone here. There's often more involved with these things than you first suspect. Cheers, Mark

5 10

[ops][largescale-sig] Collecting scaling stories
by Thierry Carrez 10 Jan '20

10 Jan '20

Hi everyone, As part of its goal of further pushing back scaling limits within a given cluster, the Large Scale SIG would like to collect scaling stories from OpenStack users. There is a size/load limit for single clusters past which things in OpenStack start to break, and we need to start using multiple clusters or cells to scale out. The SIG is interested in hearing: - what broke first for you, is it RabbitMQ or something else - what were the first symptoms - at what size/load did it start to break This will be a great help to document expected limits, and identify where improvements should be focused. You can contribute your experience by replying directly to this thread, or adding to the following etherpad: https://etherpad.openstack.org/p/scaling-stories Thanks in advance for your help ! -- Thierry Carrez (ttx) on behalf of the Large Scale SIG

1 0

Re: [charms][watcher] OpenStack Watcher Charm
by James Page 10 Jan '20

10 Jan '20

Dropping direct recipients as this causes a reject from openstack-discuss! On Fri, Jan 10, 2020 at 11:12 AM James Page <james.page(a)canonical.com> wrote: > Hi Stamatis > > Thankyou for this work! > > I'll take a look at your charm over the next few days. > > On Wed, Jan 8, 2020 at 11:25 AM Stamatis Katsaounis < > skatsaounis(a)admin.grnet.gr> wrote: > >> Hi all, >> >> Purpose of this email is to let you know that we released an unofficial >> charm of OpenStack Watcher [1]. This charm gave us the opportunity to >> deploy OpenStack Watcher to our charmed OpenStack deployment. >> >> After seeing value in it, we decided to publish it through GRNET GitHub >> Organization account for several reasons. First of all, we would love to >> get feedback on it as it is our first try on creating an OpenStack reactive >> charm. Secondly, we would be glad to see other OpenStack operators deploy >> Watcher and share with us knowledge on the project and possible use cases. >> Finally, it would be ideal to come up with an official OpenStack Watcher >> charm repository under charmers umbrella. By doing this, another OpenStack >> project is going to be available not only for Train version but for any >> future version of OpenStack. Most important, the CI tests are going to >> ensure that the code is not broken and persuade other operators to use it. >> >> Before closing my email, I would like to give some insight on the >> architecture of the code base and the deployment process. To begin with, >> charm-watcher is based on other reactive OpenStack charms. During its >> deployment Barbican, Designate, Octavia and other charms' code bases were >> counseled. Furthermore, the structure is the same as any official OpenStack >> charm, of course without functional tests, which is something we cannot >> provide. >> > I'd suggest that we initiate the process to include your watcher charm as > part of the OpenStack Charmers project on opendev.org; once the initial > migration completes adding some functional tests should be fairly easy as > you'll be able to run them on the Canonical 3rd party CI infrastructure. > > This requires that a couple of reviews be raised - here are examples for > the new Manila Ganesha charms: > > https://review.opendev.org/#/c/693463/ > https://review.opendev.org/#/c/693462/ > > One is for the infrastructure setup, the other is to formally include the > repositories as part of the TC approved project. If you would like to > raise them for the watcher charm I'm happy to review with Frode (who is the > current PTL). > >> Speaking about the deployment process, apart from having a basic charmed >> OpenStack deployment, operator has to change two tiny configuration options >> on Nova cloud controller and Cinder. As explained in the Watcher >> configuration guide, special care has to be done with Oslo notifications >> for Nova and Cinder [2]. In order to achieve that in charmed OpenStack some >> issues were met and solved with the following patches [3], [4], [5], [6]. >> With these patches, operator can set the extra Oslo configuration and this >> is the only extra configuration needs to take place. Finally, with [7] >> Keystone charm can accept a relation with Watcher charm instead of ignoring >> it. >> >> To be able to deploy GRNET Watcher charm on Train, patches [3], [4], [5] >> and [7] have to be back-ported to stable/19.10 branch but that will require >> the approval of charmers team. Please let me know if such an option is >> available and in that case I am going to open the relevant patches. >> Furthermore, if you think that it could be a good option to create a spec >> and then introduce an official Watcher charm, I would love to help on that. >> > I'd rather we wait until the 20.02 charm release - dependent changes have > all landed and will be included. > > I wish all a happy new year and I am looking forward to your response and >> possible feedback. >> > > Happy new year to you as well! > > PS. If we could have an Ubuntu package for watcher-dashboard [8] like >> octavia-dashboard [9] we would release a charm for it as well. >> > > I'll chat with coreycb and see if we might be able to package that for > 20.04/Ussuri. > > Cheers > > James > >> >>

1 0

[infra][stable] python3 is used by default in older stable branches
by Akihiro Motoki 10 Jan '20

10 Jan '20

Hi, The horizon team recently noticed that python3 is used as a default python interpreter in older stable branches like pike or ocata. For example, horizon pep8 job in stable/pike and stable/ocata fails [1][2]. We also noticed that some jobs which are expected to run with python2 (using the tox default interpreter as of the release) are now run with python3 [3]. What is the recommended way to cope with this situation? Individual projects can cope with the default interpreter change repo by repo, but this potentially affects all projects with older stable branches. This is the reason I am sending this mail. Best Regards, Akihiro Motoki (amotoki) [1] https://zuul.opendev.org/t/openstack/build/daaeaedb0a184e29a03eeaae59157c78 [2] https://zuul.opendev.org/t/openstack/build/525dc7f926684e54be8b565a7bbf7193 [3] https://zuul.opendev.org/t/openstack/build/adbc53b8d1f74dac9cd606f4a796c442…

3 3

[neutron][vpnaas] New neutron-vpnaas maintainer and core reviewer
by Slawek Kaplonski 10 Jan '20

10 Jan '20

Hi, After our last call for volunteers to maintain some of the neutron stadium projects, we have new neutron-vpnaas maintainer now \o/ Dongcan Ye just stepped up to take care of this project. After discussion with other neutron-vpnaas core reviewers I added him to neutron-vpnaas core team. He works on neutron-vpnaas since some time already and in our opinion he knows this project good enough to be core reviewer there. Thank You very much Dongcan Ye for help with neutron-vpnaas project :) — Slawek Kaplonski Senior software engineer Red Hat

1 0

[magnum]: K8s cluster creation times out. OpenStack Train : [ERROR]: Unable to render networking. Network config is likely broken
by Bhupathi, Ramakrishna 10 Jan '20

10 Jan '20

Folks, I am building a Kubernetes Cluster( Openstack Train) and using fedora atomic-29 image . The nodes come up fine ( I have a simple 1 master and 1 node) , but the cluster creation times out, and when I access the cloud-init logs I see this error . Wondering what I am missing as this used to work before. I wonder if this is image related . [ERROR]: Unable to render networking. Network config is likely broken: No available network renderers found. Searched through list: ['eni', 'sysconfig', 'netplan'] Essentially the stack creation fails in "kube_cluster_deploy" Can somebody help me debug this ? Any help is appreciated. --RamaK E-MAIL CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient of this message or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, distribution, copying, or storage of this message or any attachment is strictly prohibited.

2 1