April 2019 - openstack-discuss - lists.openstack.org

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

[openstack-ansible] dropping suse support
by Mohammed Naser 05 May '20

05 May '20

Hi everyone, I've been trying to avoid writing this email for the longest time ever. It's really painful to have to reach this state, but I think we've hit a point where we can no longer maintain support for SUSE within OpenStack Ansible. Unfortunately, with the recent layoffs, the OSA team has taken a huge hit in terms of contributors which means that there is far less contributors within the project. This means that we have less resources to go around and it forces us to focus on a more functional, reliable and well tested set of scenarios. Over the past few cycles, there has been effort to add SUSE support to OpenStack Ansible, during the time that we had maintainers, it was great and SUSE issues were being fixed promptly. In addition, due to the larger team at the time, we found ourselves having some extra time where we can help unbreak other gates. Jesse used to call this a "labour of love", which I admired at the time and hoped we continue to do as much as we can of. However, the lack of a committed maintainer for OpenSUSE has resulted in constantly failing jobs[1][2] (which were moved to non-voting, wasting CI resources as no one fixed them). In addition, it's causing several gate blocks for a few times with no one really finding the time to clean them up. We are resource constrained at this point and we need the resource to go towards making the small subset of supported features functional (i.e. CentOS/Ubuntu). We struggle with that enough, and there seems to be no deployers that are running SUSE in real life at the moment based on bugs submitted. With that, I propose that we drop SUSE support this cycle. If anyone would like to volunteer to maintain it, we can review that option, but that would require a serious commitment as we've had maintainers step off and it hurts the velocity of the project as no one can merge code anymore. ..Really wish I didn't have to write this email Mohammed [1]: http://zuul.opendev.org/t/openstack/builds?job_name=openstack-ansible-funct… [2]: http://zuul.opendev.org/t/openstack/builds?job_name=openstack-ansible-funct…

6 9

[nova] critical bug around reload/upgrades
by Mohammed Naser 24 Aug '19

24 Aug '19

Hello: I've discussed this for quite sometime with Dan over IRC and a bit with Zane as well, but basically, Nova thinks that when it gets a reload (aka SIGHUP), nothing else has occurred. However, oslo.service actually calls stop(), reload() then start() again, which potentially kills all RPC. This has caused a pretty big issue in our gates and it also means that the whole idea behind 'reload nova-compute while upgrading to refresh info' concept is fundamentally broken. I tried to do some work on this here, however, I wasn't really able to get to the bottom of it. There seems to be a decision that needs to be taken in terms of .. do we change what reload() actually means in oslo_service (it actually is more like a restart, not a reload) or does Nova (and other projects) change their implementation in assuming what reload() does? https://review.openstack.org/#/c/641907/ This seems to have been floating around for a really long time, so I'd be happy to work with someone to find the fix (and we can totally test it inside OpenStack Ansible by reloading instead of restarting). Thanks! Mohammed -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

4 4

[stackalytics] Reported numbers seem inaccurate
by Mark Goddard 26 Jun '19

26 Jun '19

Hi, I've heard a couple of people say they don't feel the numbers reported by Stackalytics accurately reflect reality. I've been trying to gather a few stats for my Kolla update session in Denver, and am finding the same. I'll try to give some concrete examples. Reviews for all kolla deliverables in Stein [1]. Here the company stats don't reflect the individual stats. Also, the total reviews in the 'Kolla Official' module does not equal the sum of the reviews of its submodules (kolla, kolla-ansible, kolla-cli). If I look at the contribution summary for Kolla Official in the last 90 days [2], they are actually greater than those for the last 180 days [3]! There are also similar issues with commit metrics, and none seem to match what I see in git. Thanks, Mark [1] https://www.stackalytics.com/?metric=marks&module=kolla-group [2] https://www.stackalytics.com/report/contribution/kolla-group/90 [3] https://www.stackalytics.com/report/contribution/kolla-group/180

10 11

Re: [nova][placement] Need for a nova-manage placement audit command
by Matt Riedemann 19 Jun '19

19 Jun '19

Re-posting this since it came up again in IRC today. On 9/20/2018 6:09 PM, Matt Riedemann wrote: > mnaser wrote a simple placement audit tool today and dumped his script > into a bug report [1]. It turns out several operators have already > written a variant of this same tool. The idea is to compare what's in > placement for allocations and (compute node) resource providers against > what's in nova for instances and compute nodes, look for orphans in > placement and then report them, or maybe also clean them up. > > I think this could go into a "nova-manage placement audit" command and > should be pretty easy to write for minimum functionality (start with > just the report). > > I'm advertising the need here in case someone wants to work on this. I'd > like to myself, but just can't justify the time right now. > > [1] https://bugs.launchpad.net/nova/+bug/1793569 > -- Thanks, Matt

2 1

[kolla][magnum] Cluster creation failed due to "Waiting for Kubernetes API..."
by Giuseppe Sannino 29 May '19

29 May '19

Hi all, need an help. I deployed an AIO via Kolla on a baremetal node. Here some information about the deployment: --------------- kolla-ansible: 7.0.1 openstack_release: Rocky kolla_base_distro: centos kolla_install_type: source TLS: disabled --------------- VMs spawn without issue but I can't make the "Kubernetes cluster creation" successfully. It fails due to "Time out" I managed to log into Kuber Master and from the cloud-init-output.log I can see: + echo 'Waiting for Kubernetes API...' Waiting for Kubernetes API... ++ curl --silent http://127.0.0.1:8080/healthz + '[' ok = '' ']' + sleep 5 Checking via systemctl and journalctl I see: [fedora@kube-clsuter-qamdealetlbi-master-0 log]$ systemctl status kube-apiserver ● kube-apiserver.service - kubernetes-apiserver Loaded: loaded (/etc/systemd/system/kube-apiserver.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2019-02-19 15:31:41 UTC; 45min ago Process: 3796 ExecStart=/usr/bin/runc --systemd-cgroup run kube-apiserver (code=exited, status=1/FAILURE) Main PID: 3796 (code=exited, status=1/FAILURE) Feb 19 15:31:40 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: kube-apiserver.service: Main process exited, code=exited, status=1/FAILURE Feb 19 15:31:40 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: kube-apiserver.service: Failed with result 'exit-code'. Feb 19 15:31:41 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: kube-apiserver.service: Service RestartSec=100ms expired, scheduling restart. Feb 19 15:31:41 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: kube-apiserver.service: Scheduled restart job, restart counter is at 6. Feb 19 15:31:41 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: Stopped kubernetes-apiserver. Feb 19 15:31:41 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: kube-apiserver.service: Start request repeated too quickly. Feb 19 15:31:41 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: kube-apiserver.service: Failed with result 'exit-code'. Feb 19 15:31:41 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: Failed to start kubernetes-apiserver. [fedora@kube-clsuter-qamdealetlbi-master-0 log]$ sudo journalctl -u kube-apiserver -- Logs begin at Tue 2019-02-19 15:21:36 UTC, end at Tue 2019-02-19 16:17:00 UTC. -- Feb 19 15:31:33 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: Started kubernetes-apiserver. Feb 19 15:31:34 kube-clsuter-qamdealetlbi-master-0.novalocal runc[2794]: Flag --insecure-bind-address has been deprecated, This flag will be removed in a future version. Feb 19 15:31:34 kube-clsuter-qamdealetlbi-master-0.novalocal runc[2794]: Flag --insecure-port has been deprecated, This flag will be removed in a future version. Feb 19 15:31:35 kube-clsuter-qamdealetlbi-master-0.novalocal runc[2794]: Error: error creating self-signed certificates: open /var/run/kubernetes/apiserver.crt: permission denied : : : Feb 19 15:31:35 kube-clsuter-qamdealetlbi-master-0.novalocal runc[2794]: error: error creating self-signed certificates: open /var/run/kubernetes/apiserver.crt: permission denied Feb 19 15:31:35 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: kube-apiserver.service: Main process exited, code=exited, status=1/FAILURE Feb 19 15:31:35 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: kube-apiserver.service: Failed with result 'exit-code'. Feb 19 15:31:35 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: kube-apiserver.service: Service RestartSec=100ms expired, scheduling restart. Feb 19 15:31:35 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: kube-apiserver.service: Scheduled restart job, restart counter is at 1. May I ask for an help on this ? Many thanks /Giuseppe

5 11

Re: [stackalytics] Reported numbers seem inaccurate
by Edward Ionel 24 May '19

24 May '19

Hello All, I first want to thank each and everyone of you for reaching out and sharing the inaccuracies you all have found within Stackalytics, this has helped us tremendously with the efforts to correct these flaws. I am writing this email to directly address each individual that has reached out and shared their concerns with our Stackalytics data. Mark Goddard Michael Johnson Julia Kreger Collen Murphy Clark Boylan Sean Mooney Thierry Carrez Jermey Stanley Arkady Kanvesky (Hopefully, I did not miss anyone) I want to insure everyone that the team is working hard to fix the inaccuracies in some of our data. We are still very much involved in OpenStack and we do read each and every message regarding Stackalytics. As Boris and Sergey mentioned, we found that this occurred due to an outdated production environment. We are currently in the progress of migrating to a new environment, and the data should be corrected. The team and I are sorry for these discrepancies and appreciate you all for bringing this to our attention. Thank you all, for providing links and examples of the inaccuracies. This has helped our efforts greatly in correcting the current issues. It would be great if the community can continue reviewing Stackalytics data and help us provide a better service to all. Once again, we are all very sorry for this and will continue to fix these issues. Cheers, Edward > On Apr 16, 2019, at 4:05 PM, Edward Ionel <eionel(a)mirantis.com> wrote: > > > >> On Tue, Apr 16, 2019 at 2:56 PM Boris Renski <brenski(a)mirantis.com> wrote: >> Folks - more specifically, we plan to roll out an update by tomorrow mid-day PT which should fix all the numbers + add aggregate details on Airship project contributions. >> >> Would really appreciate the help of the community to poke around tomorrow afternoon and see if there are still discrepancies. >> >> Sorry about this and thank you for catching it and brining it to our attention. >> >> -Boris >> >>> On Tue, Apr 16, 2019 at 1:33 PM Sergey Nikitin <snikitin(a)mirantis.com> wrote: >>> Hello everyone, >>> As you mentioned there are some inaccuracies in stats on stackalytics.com. It happened because of outdated Prod env. At this moment we are in a process of migration to the new env. All data on this env is fresh and accurate. So the problem will be solved soon. >>> >>> -- >>> Best Regards, >>> Sergey Nikitin > > > -- > Edward Ionel > Marketing Operations Manager > Mirantis, Inc. > 900 E Hamilton Ave, Suite 650 > Campbell, CA 95008 > Eionel(a)mirantis.com > www.mirantis.com

4 14

[heat][neutron] improving extraroute support
by Bence Romsics 24 May '19

24 May '19

Hi Heat and Neutron folks, I'm wondering how could I improve support for extra routes for one of our users. In this email I'd like to get your input (from both Heat and Neutron folks) in which direction should I start before I sit down to write the relevant blueprints and RFEs. This will be a bit long, please bear with me. As you know a neutron router can have extra static routing table entries as the 'routes' attribute like this (please see the api-ref in [1]): $ openstack router show router1 -f value -c routes destination='10.1.0.0/24', gateway='10.0.0.11' destination='10.2.0.0/24', gateway='10.0.0.12' ... To my best knowledge the whole set of extra routes must be updated at once which easily leads to lost updates if multiple clients modify this attribute concurrently (imagine client A and B working concurrently, for example both reads routes [r1], client A writes [r1, r2], client B writes [r1, r3]; depending on timing either r2 or r3 will be lost). Heat has an unsupported resource OS::Neutron::ExtraRoute [2] to front Neutron extra routes. For example: heat_template_version: '2015-04-30' resources: Extra_route_1: type: OS::Neutron::ExtraRoute properties: destination: '10.1.0.0/24' nexthop: '10.0.0.11' router_id: 'd544b5c5-d4d2-4b52-aaa8-ef4b9fa3e154' The Heat resource represents a single extra route out of the many in the router's routes attribute. If you have multiple OS::Neutron::ExtraRoute resources Heat by default handles them concurrently leading to the lost update problem. You can easily reproduce the problem just by having 10 extra routes in a template. The stack creation will succeed, but the router in fact will have only 6-7 (the exact number changes based on timing) extra routes. AFAIU this is exactly why this was marked unsupported. (Please let me know if you know other reasons.) As a workaround I suggested our user a hack to serialize the OS::Neutron::ExtraRoute resources by 'depends_on'. But which way should I go if I want to fix this properly? way #1 - changes in Heat only: Introduce a new Heat resource OS::Neutron::ExtraRoutes (please notice the plural) which can represent the whole routes attribute of a router (i.e. multiple extra routes in a single resource). This will not solve the design shortcomings of the neutron extraroute API, but it can at least express what can be done in the Neutron API as is. Lost updates of multiple stacks editing the same router's routes are still possible. way #2 - changes in Heat and Neutron: Introduce a new Neutron extension with a better API (either extraroutes as a top level resource, each object with a router_id or an action map a'la add/remove_router_interface to edit extra routes on the server side). This new API would work on the same DB tables and backends as the old. The old API would be kept for backwards compatibility. But if a new user exclusively uses the new API it can work concurrently. Then introduce a new Heat resource (or change the existing unsupported one) to use this new Neutron API. This is obviously more work than the first option. Which one do you prefer and why? Or let me know please if I missed a better alternative. In this thread I hope to get a cross-project agreement of this between Heat and Neutron so I can go ahead and open the relevant Heat and Neutron blueprints where we can focus only on each projects' internal questions. Thanks in advance, Bence Romsics irc: rubasov [1] https://developer.openstack.org/api-ref/network/v2/?expanded=update-router-… [2] https://docs.openstack.org/heat/latest/template_guide/unsupported.html#OS::…

4 11

[all][docs] season of docs
by Mohammed Naser 23 May '19

23 May '19

Hi there: It seems like Google has come up with a new somewhat-GSoC-like idea but focused on documentation. I think it could be a good opportunity for the documentation team (or any specific team actually, coordinated with docs) to be part of this. https://opensource.googleblog.com/2019/03/introducing-season-of-docs.html I'm not sure if the team has the amount of resources, but it seems they should be able to apply to this. Does this seem like something that might help the team more (or perhaps a specific project, coordinating with the docs team) to apply for this? Thanks, Mohammed -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

7 10

[glance][interop] standardized image "name" ?
by Mohammed Naser 23 May '19

23 May '19

Hi everyone, Something that I've been dealing with is the fact that regardless of what cloud you're using, the naming structure is very much different. While we aim to be interoperable, if I want to "boot an Debian Stretch server", the image name will probably be different all over the places. Is there some sort of way we can eliminate this by implementing a standard naming convention which would allow us to use the same images across all systems? I'm just opening the idea for discussion, I'd love to hear what others think about this. Mohammed -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

15 22

[openstack-ansible] Retirement of unused OpenStack Ansible roles
by Guilherme Steinmüller 20 May '19

20 May '19

Hello all, We have been discussing about some of our roles that are not maintained for a while, some of them are not even integrated with our main repository. In order to the team to focus on performance and stability of the roles that has been actively used, we are discussing about retiring the unused ones. The roles are the following: openstack-ansible-os_monasca openstack-ansible-os_monasca-agent openstack-ansible-os_zaqar openstack-ansible-os_watcher openstack-ansible-os_almanach openstack-ansible-os_molteniron openstack-ansible-os_searchlight We would love to help if someone wants to pick one or some of them to keep our variety of roles. If we don't hear back, we'll retire those roles out of OpenStack Ansible. Thank you Guilherme Steinmüller

6 11

OpenStack User Survey 2019
by Jimmy Mcarthur 16 May '19

16 May '19

It's time for the OpenStack User Survey <https://www.openstack.org/user-survey> [1]! In an effort to create less work for our community, in 2018 we moved to an annual, rather than a bi-annual report. If you run an OpenStack deployment, now is the time to share details about how you run the software and your thoughts on ways that the community can improve the software. Your feedback matters and it's shared directly with the PTLs and community leaders that work to build OpenStack! We had some good community feedback on the last survey and ended up with only minor updates from 2018. Below you can see a list of changes that we've incorporated: * "Which new/emerging technologies are you interested in using or seeing integrated with OpenStack?" o Added options for "AI/ML" and "5G" * Deleted the question "Are you interested in helping our interoperability efforts by using RefStack to test your cloud capabilities?" * "Which tools are you using to deploy / manage this cluster?" o Added the word "manage" to the question as tools can be used for both o Add "TripleO" and "Container-based orchestration" as options o Created a new "Please specify" if "Other tools" is chosen * "Which container orchestration or Platform-as-a-Service (PaaS) tools are you using to manage applications on this OpenStack deployment?" o Added "container orchestration or " to question * "Which OpenStack Network (Neutron) drivers are you using?" o Add Calico as an answer * "Which compatibility APIs does this deployment support?" o Added the option "This deployment doesn't use compatibility APIs" * Please note: This year, we will not be including the hardware and software vendor questions in the report or analytics dashboard due to the potential for the data to be misinterpreted. * *In addition to the question modifications above, we reached out to PTLs to ask for their feedback and guidance on the project specific questions of the survey. We've modified or added those questions as noted below: *Keystone* This will be a question where respondents can rank their choices and will follow their existing question: * Which of the following initiatives would be most beneficial for your deployment? You can rank items by priority with items at the top being most important and items at the bottom being least important. o Improved performance o Better support for synchronizing multiple keystone regions o Read-only RBAC roles o More flexible federated mappings o Improved fine-grained access control o Better support for domain administrators o Improved usability of keystone outside of an OpenStack environment Glance Changed existing question to: * "Multi back-ends feature will stay Experimental in Stein release. How badly this affect your deployment plans? Any details how you’re planning to use it would be helpful.” *Ironic* Changed existing question to: * "What would you find most useful if it was part of Ironic?" *Swift* Changed existing question to: * What features of Swift are you currently using (or have plans to use in the next 12 months)? (select all that apply o S3 compatibility o Dynamic Large Objects o Static Large Objects o Temporary URLs o Data-at-rest encryption o Multiple storage policies o Multi-region clusters o Explicit data placement (composite rings) o Container sync o Static websites or CORS o Symlinks o Quotas o Object versioning If you have further questions, concerns, please let us know. Cheers, Jimmy and Allison [1] https://www.openstack.org/user-survey

7 14

[PTL][SIG][WG] PTG Team Photos
by Kendall Nelson 15 May '19

15 May '19

Hello! If your team is attending the PTG and is interested in having a team photo taken, here is the signup[1]! There are slots Thursday and Friday from 10:00 AM to 4:30 PM. The location is TBD but will likely be close to where registration will be. I'll send an email out the day before with a reminder of your time slot and an exact location. -Kendall (diablo_rojo) [1] https://docs.google.com/spreadsheets/d/1DgsRHVWW2YLv7ewfX0M21zWJRf4wUfPG4ff…

5 10

[devstack][stein][masakari]Using Masakari in multihost devstack stein setup
by Sanjay K 13 May '19

13 May '19

Hi all, I have been trying to setup Masakari in a 3 node setup - 1 controller + 2 computes with minimal openstack services installed using devstack stable/stein version. All these 3 nodes are Ubuntu 16.04 VMs. I have included Masakari plugin in controller's local.conf file and included masakari-monitor in both compute node's local.conf file. I want to test out VM/process failure in my test environment. To do so, when I kill one of the qemu process created for one instance (cirros 256 flavor VMs) on one of the compute with root user login, I did not see any notification under my horizon/instance-ha section for this (I have already created Segments, Hosts under instance-ha in horizon). Also the killed process is not restarted by Masakari. I have asked the same question in openstack forum, but not got a single response. masakari-notification-on-process-failure <https://ask.openstack.org/en/question/121490/masakari-notification-on-proce…> Whether any additional services related to Masakari need to be configured on compute hosts to detect failures since I did not find exactly the documentation related inside devstack for this. Please let me know if I am missing anything my set up. Any helps and pointers are most appreciated. thank you for your reply. best regards

2 4

[placement][nova][ptg] resource provider affinity
by Chris Dent 09 May '19

09 May '19

Spec: https://review.openstack.org/650476 >From the commit message: To support NUMA and similar concepts, this proposes the ability to request resources from different providers nested under a common subtree (below the root provider). There's much in the feature described by the spec and the surrounding context that is frequently a source of contention in the placement group, so working through this spec is probably going to require some robust discussion. Doing most of that before the PTG will help make sure we're not going in circles in person.k Some of the areas of potential contention: * Adequate for limited but maybe not all use case solutions * Strict trait constructionism * Evolving the complexity of placement solely for the satisfaction of hardware representation in Nova * Inventory-less resource providers * Developing new features in placement before existing features are fully used in client services * Others? I list this not because they are deal breakers or the only thing that matters, but because they have presented stumbling blocks in the past and we may as well work to address them (or make an agreement to punt them until later) otherwise there will be lingering dread. And, beyond all that squishy stuff, there is the necessary discussion over the solution described in the spec. There are several alternatives listed in the spec, and a few more in the comments. We'd like to figure out the best solution that can actually be done in a reasonable amount of time, not the best solution in the absolute. Discuss! -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

10 37

[nova] Stein regressions
by Matt Riedemann 08 May '19

08 May '19

Hey cool cats, I know we just released Stein last week so what better time to write an email about a bunch of Stein regressions?! I wanted to dump this in the list so (a) I don't lose track of them all and (b) other people are aware and get involved. In no particular order: 1. https://bugs.launchpad.net/nova/+bug/1822801 There is a patch being worked: https://review.openstack.org/#/c/649345/ The workaround for this would be to disable the _heal_instance_info_cache periodic in nova-compute services that manage baremetal nodes by setting the heal_instance_info_cache_interval value to 0. 2. https://bugs.launchpad.net/nova/+bug/1824435 We have a re-create scenario for this in devstack (noted in the bug report). I've been unable to recreate in a functional test, possibly because of how sqlite deals with NULL values in unique constraints differently from mysql. I would have thought this regression test [1] would have hit it but it didn't. There are some options for fixing this, some more hacky than others, e.g.: https://review.openstack.org/#/c/653065/ Need some input from others on fixing that bug in maybe a less hacky way. 3. https://bugs.launchpad.net/nova/+bug/1825034 I found this when writing [1] to try and recreate the previous bug 1824435. I have a series up for this starting with a recreate patch [1]. The fix on top is one of a few options I detailed in the bug report. It's not pretty but it works. The workaround for this would be to archive deleted records but you'd have to do that after each run of the online data migration which is not great. 4. https://bugs.launchpad.net/nova/+bug/1825020 I just triaged this a couple of hours ago. I plan on writing a functional regression recreate test since the recreate scenario seems pretty easy - try to resize a volume-backed server where the new flavor has a smaller disk than the old flavor. The fix should also be relatively straight-forward. -- Once we get fixes landed and backported to stable/stein for these bugs we should do a patch release ASAP. [1] https://review.openstack.org/#/c/653098/ -- Thanks, Matt

1 2

[oslo][oslo-messaging][nova] Stein nova-api AMQP issue running under uWSGI
by iain.macdonnell＠oracle.com 08 May '19

08 May '19

Is anyone running Stein nova-api under uWSGI? I'm trying to do this, in exactly the same way as I did with Rocky, but encountering a new problem... The symptom is intermittent failure of API operations that involve RPC calls - notably getting the noVNC console URL for an instance. The nova-api log shows RPC timeouts and "connection reset by peer" for AMQP. I've ruled out environmental issues, as a Rocky installation on the same hosts works fine. With oslo debug enabled, I see that the first API call causes a AMQP connections to be established, and the RPC call gets its reply, and all is well... but there are no heartbeats logged after that. 3 minutes later, rabbitmq-server reports that it has received no heartbeats, and drops the connection. On a subsequent API call (but not before), nova-api logging "connection reset by peer" and the RPC call times out. With the Rocky code, once the first API call causes the AMQP connections to be established, regular heartbeats start happening, the connections are maintained, and subsequent API calls work as expected. It seems like a lockup in a thread that's supposed to maintain the AMQP connection, or something. I tried to use SIGUSR2 to trigger guru meditation, but it seems that uWSGI has its own interpretation of SIGUSR2, so nova-api never sees it (anyone know a way around this?). Running nova-api as a standalone service, instead of under uWSGI, the problem does not occur (I see the heartbeats, and everything works fine). I've tried updating oslo-messaging (and python-amqp) on a Rocky installation to the Stein version, but the problem does not reproduce. Ideas? ~iain

8 18

[octavia][taskflow] Adaption of persistence/jobboard (taskflow expert review needed)
by Anna Taraday 07 May '19

07 May '19

Hello everyone! I was looking at the topic of usage taskflow persistence and jobboard in Octavia [1]. I created a simple PoC to check what should be done to enable this functionality [2] . >From what I see, taskflow expects that data, which will be stored in persitence backend/jobboard backend, is a dict or an object easily converted to dicts [3] (error [3.1]) Also functions that creates flow should be importable [4] (error [4.1]). These two points lead to refactor required for Octavia to enable taskflow persistence and jobboard: 1) Convert data which is passed between flows in dicts, at this moment it is db objects with links to other db objects. 2) Create importable flow functions. As far as I see the only OpenStack project which adapted taskflow persistence is poppy [5] I'm looking for taskflow expect to take a look at all this and give some comments - whether I am correct or missing something. Thank you for your time in advance! [1] - https://storyboard.openstack.org/#!/story/2005072 [2] - https://review.openstack.org/#/c/647406 [3] - https://github.com/openstack/taskflow/blob/master/taskflow/persistence/back… [3.1] - http://paste.openstack.org/show/749530/ [4] - https://docs.openstack.org/taskflow/latest/_modules/taskflow/engines/helper… [4.1] - http://paste.openstack.org/show/749527/ [5] - https://github.com/openstack/poppy -- Regards, Ann Taraday Mirantis, Inc

2 3

[kolla] Virtual PTG scheduling poll
by Mark Goddard 07 May '19

07 May '19

Hi, Since most of the Kolla team aren't attending the PTG, we've agreed to hold a virtual PTG. We agreed to start with two 4 hour sessions. We can finish early or schedule another session, depending on how we progress. We'll use some video conferencing software TBD. I've created a Doodle poll here [2], please fill it in if you hope to attend. Times are in UTC. Please continue to fill out the planning Etherpad [1]. Thanks, Mark [1] https://etherpad.openstack.org/p/kolla-train-ptg [2] https://doodle.com/poll/adk2smds76d8db4u

1 2

[blazar] Scheduling a new Blazar IRC meeting for the Americas
by Pierre Riteau 06 May '19

06 May '19

Hello, Contributors to the Blazar project are currently mostly from Europe or Asia. Our weekly IRC meeting at 0900 UTC is a good match for this group. To foster more contributions, I would like to schedule another IRC meeting in the morning for American timezones, probably every two weeks to start with. I am thinking of proposing 1600 UTC on either Monday, Tuesday, or Thursday, which doesn't appear to conflict with closely related projects (Nova, Placement, Ironic). If there is anyone who would like to join but cannot make this time, or has a preference on which day, please let me know. I will wait for a few days before requesting a meeting slot. Thanks, Pierre

1 1

[tripleo] Nominate Cédric Jeanneret (Tengu) for tripleo-validations core
by Gaël Chamoulaud 04 May '19

04 May '19

Hi TripleO devs, The new Validation Framework is a big step further for the tripleo-validations project. In many ways, it improves the way of detecting & reporting potential issues during a TripleO deployment. As the mastermind of this new framework, Cédric brought a new lease of life to the tripleo-validations project. That's why we would highly benefit from his addition to the core reviewer team. Assuming that there are no objections, we will add Cédric to the core team next week. Thanks, Cédric, for your excellent work! =Gaël

10 10

[Vitrage] add datasource kapacitor for vitrage
by hoanq13＠viettel.com.vn 04 May '19

04 May '19

Hi, In our system, we use monitor by TICK stack (include: Telegraf for collect metric, InfluxDB for storage metric, Chronograf for visualize and Kapacitor alarming), which is popular monitor solution. We hope can integrate vitrage in, so we decide to write kapacitor datasource contribute for vitrage. The work is almost done , you can review in: https://review.opendev.org/653416 So i send this mail hope for more review, ideal,... Appreciate it. also ask: have any step i miss in pipeline of contribute datasource vitrage? like create blueprints, vitrage-spec,vv.. Should i do it?

2 2

[keystone][heat] security_compliance options and auto-created users
by Pavlo Shchelokovskyy 03 May '19

03 May '19

Hi all, I am currently looking at options defined in [security_compliance] section of keystone.conf [0] and trying to understand how enabling those security features may affect other services. The first thing I see is that any project that auto-creates some temporary users may be affected. Of the top of my head I can recall only Heat and Tempest doing this. For Tempest situation is easier as a) tempest can use static credentials instead of dynamic ones so it is possible to craft appropriate users beforehand and b) those users are relatively short-lived (required for limited time). In case of Heat though those users are used for deferred auth (like in autoscaling) which for long lived stacks can happen at arbitrary time in future - which is a problem. Below is breakdown of options/features possible to set and what problems that may pose for Heat and ideas on how to work those around: - disable_user_account_days_inactive - this may pose a problem for deferred auth, and it seems is not possible to override it via user "options". IMO there's a need to add a new user option to Keystone to ignore this setting for given user, and then use it in Heat to create temporary users. - lockout failure options (lockout_failure_attempts, lockout_duration) - can be overridden by user option, but Heat has to set it first. Also the question remains how realistically such problem may arise for an auto-created internal user and whether Heat should set this option at all - password expiry options (password_expires_days, unique_last_password_count, minimum_password_age) - poses a problem for deferred auth, but can be overridden by user option, so Heat should definitely set it IMO for users it creates - change_password_upon_first_use - poses problem for auto-generated users, can be overridden by a user option, but Heat must set it for its generated users - password strength enforcement (password_regex, password_regex_description) - now this is an interesting one. Currently Heat creates passwords for its temporary users with this function [1] falling back to empty password if a resource is not generating one for itself. Depending on regex_password setting in keystone, it may or may not be enough to pass the password strength check. I've looked around and (as expected) generating a random string which satisfies a pre-defined arbitrary regex is quite a non-trivial task, couple of existing Python libraries that can do this note that they support only a limited subset of full regex spec. So it seems that a most simple solution would be to add yet another user option to Keystone to ignore password strength enforcement for this given user, and amend Heat to set this option as well for internal users it creates. We in Heat may also think as to whether it would have any benefit to also set the 'lock_password' user option for the auto-created users which will prohibit such users to change their passwords via API themselves. I'd very like to hear opinion from Keystone community as most solutions I named are 'add new user option to Keystone' :-) [0] https://opendev.org/openstack/keystone/src/branch/master/keystone/conf/secu… [1] https://opendev.org/openstack/heat/src/branch/master/heat/common/password_g… Cheers, - Pavlo -- Dr. Pavlo Shchelokovskyy Principal Software Engineer Mirantis Inc www.mirantis.com

4 4

[oslo] Proposing Hervé Beraud for Oslo Core
by Ben Nemec 02 May '19

02 May '19

Hi, Hervé has been working on Oslo for a while now and in that time has shown tremendous growth in his understanding of Oslo and OpenStack. I think he would make a good addition to the general Oslo core team. Existing Oslo team members (+Keystone, Castellan, and anyone else we co-own libraries with) please respond with +1/-1. If there are no objections I'll add him to the ACL next week and we can celebrate in person. :-) Thanks. -Ben

9 9

properly sizing openstack controlplane infrastructure
by Hartwig Hauschild 02 May '19

02 May '19

Hi everyone, A colleague and I have more or less recently been tasked with redesigning my employers openstack-infrastructure and it turned out that starting over will be easier than fixing the existing stack as we've managed to lock ourselves in a corner quite good. The requirements we've got are basically "here's 50 compute-nodes, make sure whatever you're building scales upwards from there". We have the existing pike-stack as a reference but we don't really know how the different services scale up with more compute-nodes to handle. The pike-stack has three servers as control-plane, each of them with 96G of RAM and they don't seem to have too much room left when coordinating 14 compute-nodes. We're thinking about splitting the control-nodes into infrastructure (db/rabbit/memcache) and API. What would I want to look for when sizing those control-nodes? I've not been able to find any references for this at all, just rather nebulous '8G RAM should do' which is around what our rabbit currently inhales. Also: We're currently running Neutron in OVS-DVR-VXLAN-Configuration. Does that properly scale up and above 50+ nodes or should we look into offloading the networking onto something else? I'm aware that the questions may sound a bit funny, but we have to spec out the controlplane-hardware before we can start testing and we'd prefer not to retrofit the servers because we goofed up. Thanks for your time, -- Cheers, Hardy

4 7

kube_cluster_deploy fails
by Pawel Konczalski 02 May '19

02 May '19

Hi, i try to deploy a kubernetes cluster on OpenStack rocky with Magnum. All Heat steps runs fine except for the last one "kube_cluster_deploy": kube_cluster_deploy c3a79e96-87d8-442e-83f1-91d7a1acd896 1 minute Create Failed CREATE aborted (Task create from SoftwareDeployment "kube_cluster_deploy" Stack "kubernetes-cluster9-l4ol4ger3key" [b17bfab3-f46a-477b-921f-4719bfd8df06] Timed out) The cluster contains three control / compute nodes, Octavia is also installed and works fine as far as I can see. Atomic Image: https://dl.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-2018041… The command was: openstack coe cluster template create kubernetes-cluster-template \ --image fedora-atomic-latest \ --external-network public \ --dns-nameserver 8.8.8.8 \ --master-flavor m1.small \ --flavor m1.large \ --coe kubernetes \ --docker-volume-size 10 \ --tls-disabled \ --floating-ip-enabled openstack coe cluster create kubernetes-cluster \ --cluster-template kubernetes-cluster-template \ --master-count 1 \ --node-count 1 \ --timeout 30 \ --keypair mykey Did someone run also into this Problem or know how to fix it? BR Pawel

3 4

[openstack-dev] [neutron] PTG agenda
by Miguel Lavalle 02 May '19

02 May '19

Hi Neutrinos,, I took your proposals for PTG topics and organized them in an agenda. Please look at https://etherpad.openstack.org/p/openstack-networking-train-ptg. Let's have a very productive meeting! Best regards Miguel

2 3

[glance] [ops] Issue sharing an image with another project (something related to get_image_location)
by Massimo Sgaravatto 02 May '19

02 May '19

I have a small Rocky installation where Glance is configured with 2 backends (old images use the 'file' backend while new ones use the rbd backend, which is the default) show_multiple_locations is true but I have these settings in policy.json: # grep _image_location /etc/glance/policy.json "delete_image_location": "role:admin", "get_image_location": "role:admin", "set_image_location": "role:admin", This was done because of: https://wiki.openstack.org/wiki/OSSN/OSSN-0065 If an unpriv user tries to share a private image: $ openstack image add project 3194a04b-ffc8-4aaf-b6c8-adc24e3d3fe6 e81df4c0b493439abb8b85bfd4cbe071 403 Forbidden: Not allowed to create members for image 3194a04b-ffc8-4aaf-b6c8-adc24e3d3fe6. (HTTP 403) In the log file it looks like that the problem is related to the get_image_location operation: /var/log/glance/api.log:2019-04-29 16:06:54.523 8220 WARNING glance.api.v2.image_members [req-dd93cdc9-767d-4c51-8e5a-edf746c02264 ab573ba3ea014b778193b6922ffffe6d ee1865a76440481cbcff08544c7d580a - default default] Not allowed to create members for image 3194a04b-ffc8-4aaf-b6c8-adc24e3d3fe6.: Forbidden: You are not authorized to complete get_image_location action. But actually the sharing operation succeeded: $ glance member-list --image-id 3194a04b-ffc8-4aaf-b6c8-adc24e3d3fe6 +--------------------------------------+----------------------------------+---------+ | Image ID | Member ID | Status | +--------------------------------------+----------------------------------+---------+ | 3194a04b-ffc8-4aaf-b6c8-adc24e3d3fe6 | e81df4c0b493439abb8b85bfd4cbe071 | pending | +--------------------------------------+----------------------------------+---------+ Cheers, Massimo

2 3

[OpenStack-Ansible][OSA] Team Dinner Denver
by Amy Marrich 01 May '19

01 May '19

We are looking at having our official team dinner Wednesday evening. Please visit this etherpad: https://etherpad.openstack.org/p/osa-team-dinner-plan To add your name and vote on restaurants so I can get a head count and make a reservation. Thanks, Amy (spotz)

2 1

[devstack] Identity URL problem
by Neil Jerram 01 May '19

01 May '19

Does anyone know what causes this problem at [1]: 2019-04-30 16:34:03.137 | +++ functions-common:oscwrap:2346 : command openstack role add admin --user neutron --project service --user-domain Default --project-domain Default 2019-04-30 16:34:03.139 | +++ functions-common:oscwrap:2346 : openstack role add admin --user neutron --project service --user-domain Default --project-domain Default 2019-04-30 16:34:04.331 | Failed to discover available identity versions when contacting http://104.239.175.234/identity. Attempting to parse version from URL. 2019-04-30 16:34:04.331 | Could not find versioned identity endpoints when attempting to authenticate. Please check that your auth_url is correct. Not Found (HTTP 404) [1] http://logs.openstack.org/79/638479/3/check/networking-calico-tempest-dsvm/… I think there are loads of uses of that URL, before where the networking-calico plugin uses it, so I can't see why the plugin's use hits that error. Thanks, Neil

2 3

[ptg][sig][upgrades] Train PTG Upgrades SIG session
by James Page 01 May '19

01 May '19

Hi All I've finally found time to create an etherpad for the Upgrades SIG session at the upcoming PTG in Denver (on the train on my way to LHR to catch my flight). https://etherpad.openstack.org/p/upgrade-sig-ptg-train I've added a few proposed topics but if you're at the PTG (or summit) and have anything upgrade related to discuss please add your topic to the etherpad over the next few days - I'll then put together a rough schedule for our half day of upgrades discussion on Thursday morning in room 201. IRC meetings never really got restarted since the last PTG but I know that the promise of getting together to discuss upgrade successes and challenges generally appeals to us all based on prior sessions! Thanks in advance and see you all in Denver! Cheers James

1 1

[Ceilometer]: cpu_util meter not being calculated as expected leading to delay in scaling
by Arvind Kumar 01 May '19

01 May '19

Hi, A design issue is observed in ceilometer service of Openstack. Setup include multiple compute nodes and 3 controller nodes. Meters from each compute node are sent to all the 3 ceilometer instances via RabbitMQ in round robin fashion at an interval of 10 min. After transformation of cumulative cpu meter data, cpu_util is generated by ceilometer instance at controller node and is published to the http address configured in ceilometer pipeline configuration. cpu_util is used by the application to take the decision if scaling of VM needs to be triggered or not. Ceilometer instance calculates cpu_util for a VM from the difference between cumulative cpu usage of VM at two timestamp divided by the timestamp difference. Let's say 1 compute node send the cumulative cpu usage of a VM (C1, C2, C3, C4) at timestamp T1, T2, T3, T4 (difference between any two timestamp is 10 min). Now (C1,T1) & (C4,T4) tuple is received by ceilometer instance 1, (C2,T2) by instance 2, (C3,T3) by instance 3. Here even if CPU usage of VM is increased between T1 & T2, cpu_util is calculated for 30 min duration (T1 & T4) rather than as expected for 10 min. This leads to scaling getting triggered after T4 that too when CPU usage is consistently above the threshold between T1 and T4. Please suggest how could this issue could be resolved. Do we have any solution to bind VM or compute node meter data to specific ceilometer instance for processing? Regards, Arvind. "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s). are confidential and may be privileged. If you are not the intended recipient. you are hereby notified that any review. re-transmission. conversion to hard copy. copying. circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient. please notify the sender immediately by return email. and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment."

2 2

[Zun] openstack appcontainer create Error
by Alejandro Ruiz Bermejo 01 May '19

01 May '19

Hi, i'm installing Zun in Openstack Queens with Ubuntu 18.04.1 LTS, i already have configured docker and kuyr-libnetwork. I'm following the guide at https://docs.openstack.org/zun/queens/install/index.html. I followed all the steps of the installation at controller node and everything resulted without problems. After finished the installation direction at compute node the *systemctl status zun-compute* have the following errors root@compute /h/team# systemctl status zun-compute ● zun-compute.service - OpenStack Container Service Compute Agent Loaded: loaded (/etc/systemd/system/zun-compute.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2019-04-30 16:46:56 UTC; 4h 26min ago Main PID: 2072 (zun-compute) Tasks: 1 (limit: 4915) CGroup: /system.slice/zun-compute.service └─2072 /usr/bin/python /usr/local/bin/zun-compute Apr 30 16:46:56 compute systemd[1]: Started OpenStack Container Service Compute Agent. Apr 30 16:46:57 compute zun-compute[2072]: 2019-04-30 16:46:57.929 2072 INFO zun.cmd.compute [-] Starting server in PID 2072 Apr 30 16:46:57 compute zun-compute[2072]: 2019-04-30 16:46:57.941 2072 INFO zun.container.driver [-] Loading container driver 'docker.driver.DockerDriver' Apr 30 16:46:58 compute zun-compute[2072]: 2019-04-30 16:46:58.028 2072 INFO zun.container.driver [-] Loading container driver 'docker.driver.DockerDriver' Apr 30 16:48:33 compute zun-compute[2072]: 2019-04-30 16:48:33.645 2072 INFO zun.image.driver [req-7e0b8325-1e09-4410-80f4-af807cbc0420 a16c6ef0319b4643a4ec8e56a1d025cb 59065d8f970b467aa94ef7b35f1edab5 default - -] Loading container image driver 'glance' Apr 30 16:48:33 compute zun-compute[2072]: 2019-04-30 16:48:33.911 2072 INFO zun.image.driver [req-7e0b8325-1e09-4410-80f4-af807cbc0420 a16c6ef0319b4643a4ec8e56a1d025cb 59065d8f970b467aa94ef7b35f1edab5 default - -] Loading container image driver 'glance' Apr 30 16:48:35 compute zun-compute[2072]: 2019-04-30 16:48:35.455 2072 INFO zun.image.driver [req-7e0b8325-1e09-4410-80f4-af807cbc0420 16c6ef0319b4643a4ec8e56a1d025cb 59065d8f970b467aa94ef7b35f1edab5 default - -] Loading container image driver 'glance' Apr 30 16:48:35 compute zun-compute[2072]: 2019-04-30 16:48:35.939 2072 ERROR zun.image.glance.driver [req-7e0b8325-1e09-4410-80f4-af807cbc0420 a16c6ef0319b4643a4ec8e56a1d025cb 59065d8f970b467aa94ef7b35f1edab5 default - -] Imae cirros was not found in glance: ImageNotFound: Image cirros could not be found. Apr 30 16:48:35 compute zun-compute[2072]: 2019-04-30 16:48:35.940 2072 INFO zun.image.driver [req-7e0b8325-1e09-4410-80f4-af807cbc0420 a16c6ef0319b4643a4ec8e56a1d025cb 59065d8f970b467aa94ef7b35f1edab5 default - -] Loading container image driver 'docker' Apr 30 16:48:55 compute zun-compute[2072]: 2019-04-30 16:48:55.011 2072 ERROR zun.compute.manager [req-7bfa764a-45b8-4e2f-ac70-84d8bb71b135 - - - - -] Error occurred while calling Docker create API: Docker internal error: 500 Server Error: Internal Server Error ("failed to update store for object typpe *libnetwork.endpointCnt: client: etcd member http://controller:2379 has no leader").: DockerError: Docker internal error: 500 Server Error: Internal Server Error ("failed to update store for object type *libnetwork.endpointtCnt: client: etcd member http://controller:2379 has no leader"). Also *systemctl status docker* show the next output root@compute /h/team# systemctl status docker ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/docker.service.d └─docker.conf, http-proxy.conf, https-proxy.conf Active: active (running) since Tue 2019-04-30 16:46:25 UTC; 4h 18min ago Docs: https://docs.docker.com Main PID: 1777 (dockerd) Tasks: 21 CGroup: /system.slice/docker.service └─1777 /usr/bin/dockerd --group zun -H tcp://compute:2375 -H unix:///var/run/docker.sock --cluster-store etcd://controller:2379 Apr 30 16:46:20 compute dockerd[1777]: time="2019-04-30T16:46:20.815305836Z" level=warning msg="Your kernel does not support cgroup rt runtime" Apr 30 16:46:20 compute dockerd[1777]: time="2019-04-30T16:46:20.815933695Z" level=info msg="Loading containers: start." Apr 30 16:46:24 compute dockerd[1777]: time="2019-04-30T16:46:24.378526837Z" level=info msg="Default bridge (docker0) is assigned with an IP address 17 Apr 30 16:46:24 compute dockerd[1777]: time="2019-04-30T16:46:24.572558877Z" level=info msg="Loading containers: done." Apr 30 16:46:25 compute dockerd[1777]: time="2019-04-30T16:46:25.198101219Z" level=info msg="Docker daemon" commit=e8ff056 graphdriver(s)=overlay2 vers Apr 30 16:46:25 compute dockerd[1777]: time="2019-04-30T16:46:25.198211373Z" level=info msg="Daemon has completed initialization" Apr 30 16:46:25 compute dockerd[1777]: time="2019-04-30T16:46:25.232286069Z" level=info msg="API listen on /var/run/docker.sock" Apr 30 16:46:25 compute dockerd[1777]: time="2019-04-30T16:46:25.232318790Z" level=info msg="API listen on 10.8.9.58:2375" Apr 30 16:46:25 compute systemd[1]: Started Docker Application Container Engine. Apr 30 16:48:55 compute dockerd[1777]: time="2019-04-30T16:48:55.009820439Z" level=error msg="Handler for POST /v1.26/networks/create returned error: failed to update store for object type *libnetwork.endpointCnt: client: etcd member http://controller:2379 has no leader" When i try to launch an app container as the guide says it shows an Error state and when i run opentack appcontainer show this is the reason of the error status_reason | Docker internal error: 500 Server Error: Internal Server Error ("failed to update store for object type *libnetwork.endpointCnt: client: etcd member http://controller:2379 has no leader") I had some troubles installing Kuryr-libnetwork besides that i didn't had any othet problem during the installation of Zun

2 1

[openstack-dev] [neutron] Neutron team dinner at Denver PTG
by Miguel Lavalle 30 Apr '19

30 Apr '19

Hi Neutrinos, After extensive consultations with the community, we decided that pizza and beer is always a crowd pleaser among a bunch of software engineers. So our team dinner will take place at Mellow Mushroom Pizza Bakers, located at 1201 16th Street, Denver, CO 80202, phone number (720) 328-9114. There is a reservation under "Miguel" at 7pm on Friday May 3rd. Here you will find walking directions from the Convention Center: https://goo.gl/maps/G63j6FmuoyBKjA7RA If you haven't done so already and are planning to attend the team dinner, please register your name at the top of this etherpad: https://etherpad.openstack.org/p/openstack-networking-train-ptg Looking forward to see you there!

1 0

["Neutron"] Create subnet gives ERROR "Body contains invalid data"
by Kelam, Koteswara Rao 30 Apr '19

30 Apr '19

Tried to create a subnet with following curl command $ curl -s $END_POINT/neutron/v2.0/subnets -X POST -H "Content-Type: application/json" -H "Accept: application/json" -H "X-Auth-Token: $AUTH_TOKEN" -d '{'subnet': {'name': '8c7993a8-905e-4ad4-be3b-11c692e38317', 'network_id': '8f5f7cff-a320-40ba-9903-0c4e6dd80c0c', 'ip_version': 4, 'cidr': '169.254.3.1/32', 'enable_dhcp': 'false'}}' And got following ERROR: {"NeutronError": {"message": "Body contains invalid data", "type": "HTTPBadRequest", "detail": ""}} But when I tried with DOUBLE quotes in the body it got succeeded. $ curl -s $END_POINT/neutron/v2.0/subnets -X POST -H "Content-Type: application/json" -H "Accept: application/json" -H "X-Auth-Token: $AUTH_TOKEN" -d '{"subnet": {"name": "8c7993a8-905e-4ad4-be3b-11c692e38317", "network_id": "8f5f7cff-a320-40ba-9903-0c4e6dd80c0c", "ip_version": 4, "cidr": "169.254.3.1/32", "enable_dhcp": 'false'}}' {"subnet":{"description":"","enable_dhcp":false,"tags":[],"network_id":"8f5f7cff-a320-40ba-9903-0c4e6dd80c0c","tenant_id":"39f81bc21a9f4eb7b87586d983b6ec3d","created_at":"2019-04-29T11:56:57Z","segment_id":null,"dns_nameservers":[],"updated_at":"2019-04-29T11:56:57Z","gateway_ip":"169.254.3.2","ipv6_ra_mode":null,"allocation_pools":[{"start":"169.254.3.1","end":"169.254.3.1"}],"host_routes":[],"revision_number":0,"ip_version":4,"ipv6_address_mode":null,"cidr":"169.254.3.1/32","project_id":"39f81bc21a9f4eb7b87586d983b6ec3d","id":"33de75fb-fa10-460a-9123-577ae62a771a","subnetpool_id":null,"name":"8c7993a8-905e-4ad4-be3b-11c692e38317"}} Single quotes not allowed in requested body? Only double quotes allowed?? Single quotes also used to work for me with older versions on neutron. -Koteswar

4 3

[ptg] [interop] [refstack] Interop Forum and PTG sessions
by Egle Sigler 30 Apr '19

30 Apr '19

Hello Everyone, If you in Denver for the summit this week, please join the interop working group team for our forum session on Tuesday, 4:20 pm – 5:00 pm meeting room 507: https://www.openstack.org/summit/denver-2019/summit-schedule/events/23657/i… PTG: Friday, 9:00 am – 10:45 am, Room 112 Thank you, Egle Sigler

1 0

[Zun] deploying zun error at kuryr installation
by Alejandro Ruiz Bermejo 30 Apr '19

30 Apr '19

Hi i've installed Openstack Queens on Ubuntu 18.04 and i'm following the Zun Installation Guide to deploy a container infrastructure. I'm following the steps to install kuryr-libnetwork (I've already installed docker on the compute node and it's working fine). The kuryr installation process had no errors but when i try to verify the operation as it's said in the guide docker network create --driver kuryr --ipam-driver kuryr \ --subnet 10.10.0.0/16 --gateway=10.10.0.1 test_net I'm Getting this error *Error* response from daemon: legacy plugin: Post http://10.8.9.54:23750/Plugin.Activate: dial tcp 10.8.9.54:23750: connect: connection refused I tryed to find the error wit **journalctl -u kuryr-libnetwork Apr 27 13:11:12 compute systemd[1]: Started Kuryr-libnetwork - Docker network plugin for Neutron. Apr 27 13:11:13 compute kuryr-server[10736]: 2019-04-27 13:11:13.273 10736 *WARNING* keystoneauth.identity.generic.base [-] Failed to discover available identity versions when contacting http://controller:35357. Attempting to parse version from URL.: ConnectFailure: Unable to establish connection to http://controller:35357: HTTPConnectionPool(host='controller', port=35357): MTTPConnectionPool(host='controller', port=35357): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fecef1a8090>: Failed to establish a new connection: [Errno 111] Connection refused',)) Apr 27 13:11:13 compute kuryr-server[10736]: 2019-04-27 13:11:13.274 10736 *CRITICAL* kuryr [-] Unhandled error: DiscoveryFailure: Could not determine a suitable URL for the plugin Apr 27 13:11:13 compute kuryr-server[10736]: 2019-04-27 13:11:13.274 10736 *ERROR* kuryr Traceback (most recent call last): This is the relevant content of my /etc/kuryr/kuryr.conf *[DEFAULT]* bindir = /usr/local/libexec/kuryr *[neutron]* www_authenticate_uri = http://controller:5000 auth_url = http://controller:35357 username = kuryr user_domain_name = default password = 123 project_name = service project_domain_name = default auth_type = password And this is the one at /usr/lib/docker/plugins/kuryr/kuryr.spec: http://conrtoller:23750 Btw compute node have connectivity with controller. I already have worked with the environment and launched kvm VMs on it Can someone help troubleshoot this error?? *UPDATE1* I checked open ports on controller node and 23750 isn't open. I followed the directions at the guide, any recommendation? Also in the compute node when i run systemctl status kuryr-libnetwork this is the output ● kuryr-libnetwork.service - Kuryr-libnetwork - Docker network plugin for Neutron Loaded: loaded (/etc/systemd/system/kuryr-libnetwork.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2019-04-27 16:06:21 UTC; 2min 39s ago Process: 17450 ExecStart=/usr/local/bin/kuryr-server --config-file /etc/kuryr/kuryr.conf (code=exited, status=1/FAILURE) Main PID: 17450 (code=exited, status=1/FAILURE) Apr 27 16:06:21 compute kuryr-server[17450]: 2019-04-27 16:06:21.497 17450 ERROR kuryr File "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/base.py", line 134, in get_access Apr 27 16:06:21 compute kuryr-server[17450]: 2019-04-27 16:06:21.497 17450 ERROR kuryr self.auth_ref = self.get_auth_ref(session) Apr 27 16:06:21 compute kuryr-server[17450]: 2019-04-27 16:06:21.497 17450 ERROR kuryr File "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/generic/base.py", line 199, in get_auth_ref Apr 27 16:06:21 compute kuryr-server[17450]: 2019-04-27 16:06:21.497 17450 ERROR kuryr self._plugin = self._do_create_plugin(session) Apr 27 16:06:21 compute kuryr-server[17450]: 2019-04-27 16:06:21.497 17450 ERROR kuryr File "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/generic/base.py", line 194, in _do_create_plugin Apr 27 16:06:21 compute kuryr-server[17450]: 2019-04-27 16:06:21.497 17450 ERROR kuryr raise exceptions.DiscoveryFailure('Could not determine a suiable URL ' Apr 27 16:06:21 compute kuryr-server[17450]: 2019-04-27 16:06:21.497 17450 ERROR kuryr DiscoveryFailure: Could not determine a suitable URL for the plugin Apr 27 16:06:21 compute kuryr-server[17450]: 2019-04-27 16:06:21.497 17450 ERROR kuryr Apr 27 16:06:21 compute systemd[1]: kuryr-libnetwork.service: Main process exited, code=exited, status=1/FAILURE Apr 27 16:06:21 compute systemd[1]: kuryr-libnetwork.service: Failed with result 'exit-code'. *UPDATE2* I tried the recommendations given by **hongbin034** and confirm that i had a problem with Keystone. when i run openstack token issue after exporting the neutron environment varibles i get the following output Failed to discover available identity versions when contacting http://controller:35357. Attempting to parse version from URL. Could not determine a suitable URL for the plugin I checked and the port 35357 isn't even open at the controller node. But at the controller node installation there isn't any step configuring such port

2 1

[scientific-sig] ROOM CHANGE - SIG session at 3:50pm moved to 4E/4F
by Stig Telfer 29 Apr '19

29 Apr '19

Hi All - To get us a projector for our SIG session, we are moving from 507 to 4E/4F Sorry for the late notice! Cheers, Stig

1 0

[sahara][all] Sahara Train Virtual PTG is SCHEDULED
by Jeremy Freudberg 29 Apr '19

29 Apr '19

Hi all, Sahara will have a virtual PTG on Monday, May 6, beginning at 15:00 UTC. Best guess is that it will run two hours. Come and go as you need to. The etherpad is here: https://etherpad.openstack.org/p/sahara-train-ptg Please take a moment to add some topics, and, if you plan to attend, your name. The session will be hosted by Bluejeans: https://bluejeans.com/6304900378 (Take a moment to make sure your browser and peripherals are configured nicely) All interested parties are welcome. Outcomes will appear on openstack-discuss and on the etherpad itself. Till then, Jeremy

1 0

Third party CI and Zuul at OpenInfra Summit
by corvus＠inaugust.com 29 Apr '19

29 Apr '19

Hi, I'd like to invite any third-party CI operators as well as anyone else running Zuul or interested in running Zuul to join us in a discussion about reusing Zuul jobs in a downstream context at the Zuul working group session on Tuesday: https://www.openstack.org/summit/denver-2019/summit-schedule/events/23736/z… -Jim

1 0

[placement][ptg] Envisioning other technologies
by Chris Dent 29 Apr '19

29 Apr '19

>From the etherpad [1]: ("My" in here is edleafe) * The more we get into the complexities of modeling nested providers, the more it seems to me that we are not using the best technology for this task. My brief experiments with graph databases last year showed a great deal of promise, but the whole extraction process pushed that to the side. * Perhaps we might try some parallel development, where resources are modeled in both relational and graph DBs. Then we might be able to compare the different solutions to complex queries on the same data sets. This is an invitation to discuss other potentially useful technologies, the relative cost of exploring them, and benefits we might get from that exploration (even if we don't end up using the other tech). And anything else anyone else wants to add. [1] https://etherpad.openstack.org/p/placement-ptg-train -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

2 1

[scientific-sig] Denver BoF lightning talks today!
by Blair Bethwaite 29 Apr '19

29 Apr '19

Hi all, There's still space available for extra lightning talks in the Scientific SIG BoF today, so if you've a quick story to tell please add your name to the etherpad here: https://etherpad.openstack.org/p/scientific-sig-denver19-bof -- Cheers, ~Blairo

1 0

[neutron] Bug deputy report April 22 - 28
by Boden Russell 29 Apr '19

29 Apr '19

Below is a summary of bugs from last week. Based on the rotation list [1], Nate is up this week. Thanks Confirmed/In-Progress: - https://bugs.launchpad.net/neutron/+bug/1826726 [L3] stale device/process remain in network node after router removed - https://bugs.launchpad.net/neutron/+bug/1826695 [L3][QoS] cache does not removed when router is down or deleted - https://bugs.launchpad.net/neutron/+bug/1826570 Error in "tc_lib._handle_from_hex_to_string" formatting - https://bugs.launchpad.net/neutron/+bug/1826565 "tc_lib.add_tc_policy_class" must always assign a default value to "min_kbps" - https://bugs.launchpad.net/neutron/+bug/1826480 High latency on delete_subnets with increasing load and concurrency - https://bugs.launchpad.net/neutron/+bug/1825787 [L3][HA] agent HA router count should not include dvr local router Under investigation: - https://bugs.launchpad.net/neutron/+bug/1826644 ha router goes to standby mode only when they are created by heat - https://bugs.launchpad.net/neutron/+bug/1826419 dhcp agent configured with mismatching domain and host entries Incomplete: - https://bugs.launchpad.net/neutron/+bug/1826066 Iptables rules for unbound ports removed during agent sync RFE: - https://bugs.launchpad.net/neutron/+bug/1826396 [RFE] Atomic Extraroute API - https://bugs.launchpad.net/neutron/+bug/1825943 [RFE] Implement "stop agent" hook script support in Neutron [1] https://wiki.openstack.org/wiki/Network/Meetings

2 1

[tripleo] default ceph migrating from luminous to nautilus
by John Fulton 29 Apr '19

29 Apr '19

We're going to be making some updates in TripleO and RDO so that the default version of Ceph in Stein is Nautilus. Part of this involves temporarily disabling the standalone 001/004 jobs. Our reviews are lined up and linked with additional details on the TripleO Integration Squad etherpad [1]. We'll be waiting until the 3rd party checks are green [2] before we start merging. John [1] https://etherpad.openstack.org/p/tripleo-integration-squad-status [2] https://etherpad.openstack.org/p/ruckroversprint9

2 2

[placement][ptg] Aggregate on root spans whole tree policy:
by Chris Dent 29 Apr '19

29 Apr '19

>From the etherpad [1]: * Last PTG for Stein, we decided the following policies and have done so in Stein A) Aggregate on root spans whole tree for ``members_of=`` requests in 'GET /allocation_candidates' B) This spanning policy doesn't apply to granular requests ``members_of<N>=`` or to requests in 'GET /resource_providers' C) This change is a bug fix without microversion However, I now feel the policy B is weird. Consider a case where only granular requests are used in the request. If operator puts aggA on root, aggA applies the child or not depends on cases how you created the request. That's very difficult for operators to debug... This is from Tetsuro, so perhaps he can add some additional info, but basically I think what's being requested here is some discussion on whether changing B is warranted. [1] https://etherpad.openstack.org/p/placement-ptg-train -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

4 7

[placement][nova][ptg] Resource provider - request group mapping
by Chris Dent 29 Apr '19

29 Apr '19

This is about this spec [1] "Resource provider - request group mapping in allocation candidate" which didn't get approved in Stein and will need to find its appropriate home (in placement) at some point. This topic is from the cross project etherpad [2]. The questions associated with this are of two forms: * How should the data be presented in the allocation candidates response? * How best to capture the pending discussion on a nova spec as is moved to becoming a placement spec. There's quite a lot of useful information on the spec, including multiple alternatives and reasons why those alternatives are good or not good. This is one those API changes where we need to be careful to be general and within the existing grammar of placement and not simply evolving reactively to increased complexity in Nova. Obviously Placement needs to be evolve in response to Nova, but carefully. What might be useful is for people who feel some ownership for the various proposed structures to discuss their merits, here. Or go the other way: If there are some structures you dislike, why? [1] https://review.openstack.org/#/c/597601/ [2] https://etherpad.openstack.org/p/ptg-train-xproj-nova-placement -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

6 10

[cinder] Team Dinner Update ...
by Jay Bryant 28 Apr '19

28 Apr '19

Team, A slight update to our team dinner plans. I could not get a reservation for 6 due to an Avalanche game happening. I was able to get a reservation for 7:15 instead. I have updated the etherpad: https://etherpad.openstack.org/p/cinder-train-dinner-plan Look forward to seeing you all there! Jay

1 0

[ops] OpenStack Operators & Beer
by David Medberry 28 Apr '19

28 Apr '19

Reminder, Monday night at Open Infra Summit, OpenStack Ops are invited to hangout at Wynkoop Brewery. Reservation under my name for 7:30pm. This is a casual, unsponsored gathering (much as we have done at prior Operator Meetups). There is dining on the first floor and there will also be a pool table reserved on the second floor. (This is all AFTER the Open Infra Marketplace kick-off.) -dave David Medberry OpenStack Guy and Frisbee Flinger

1 0

[cinder][vendors][cinderlib] Validating Cinder driver for usage with cinderlib
by Gorka Eguileor 28 Apr '19

28 Apr '19

Hi, This is a call to Storage vendors and application developers that, with the excitement of the Stein release, may have missed the first cinderlib release [1][2] under the OpenStack umbrella that happened on the 16th. Cinderlib is doing cycle trailing releases. Using Cinder drivers out of OpenStack has been a frequent request by developers wanting to leverage Cinder's storage management capabilities without all the extra features that Cinder provides, such as quotas, replication, migrations, etc. The answer from the Cinder team has been to create a Python library that provides an object oriented abstraction around Cinder’s storage drivers to allow their direct usage without running any of the Cinder services (API, Scheduler, Volume) or surrounding services (KeyStone, MySQL, RabbitMQ). Even though cinderlib has just been released as a Tech Preview, there are already 2 projects using it: - oVirt: in the Managed Block Storage functionality [3] - Ember-CSI: providing storage for Kubernetes, Mesos, Docker swarm, cloud foundry, etc. [4] This means that with a single Cinder driver vendors can support multiple platforms: - OpenStack - oVirt - Containers: Kubernetes, Mesos, Docker swarm, cloud foundry, etc. Cinderlib works around the limitations that prevented direct usage of the drivers. One of these are driver "particularities", and that's why we recommend vendors that want to ensure compatibility with the library to run the cinderlib functional tests at the gate. These tests take but a minute to run. We have some documentation under review [5] going over the process of doing manual validation of a driver, running the tests as jobs of the cinderlib project, or as an additional step of the Cinder tempest run. The cinderlib project currently has 2 backends running the functional tests, LVM and Ceph, and we have patches up to run them as part of the LVM [6] and Ceph [7] Cinder jobs as well. If you are interested in using project, validating your driver, or just have some feedback or questions feel free to drop me an email or DM me (twitter @geguileo) and I'll be more than happy help. If you are going to the Open Infrastructure Summit we can meet in person, and if you feel adventurous we can even do the manual validation. Cheers, Gorka. [1]: https://docs.openstack.org/cinderlib/latest/index.html [2]: https://pypi.org/project/cinderlib/ [3]: https://ovirt.org/develop/release-management/features/storage/cinderlib-int… [4]: https://ember-csi.io [5]: https://review.opendev.org/#/c/651880/ [6]: https://review.opendev.org/#/c/620671/ [7]: https://review.opendev.org/#/c/645182/

1 0

[dev][keystone] Keystone Team Update - Week of 22 April 2019
by Colleen Murphy 27 Apr '19

27 Apr '19

# Keystone Team Update - Week of 22 April 2019 ## News ### Keystone Ocata in Pike are in Extended Maintenance The stable/ocata and stable/stein branches went into Extended Maintenance mode this month[1][2] in accordance with the new-ish maintenance phase procedure[3]. This means that those branches won't be released any more. However, they are still open to land backports. If and when those branches become too difficult to maintain, we will discuss putting them in the Unmaintained phase. [1] https://review.opendev.org/650467 [2] https://review.opendev.org/652905 [3] https://docs.openstack.org/project-team-guide/stable-branches.html ### No meetings next two weeks We agreed to skip the next two IRC meetings[4]. [4] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005531.ht… ### Forum Sessions and Summit Presentations Forum sessions that you should be aware of if you're interested in the future of keystone: Keystone Application Credentials: Status and Planning: https://www.openstack.org/summit/denver-2019/summit-schedule/events/23643/k… Keystone Operator Feedback: https://www.openstack.org/summit/denver-2019/summit-schedule/events/23644/k… Change ownership of resources - followup: https://www.openstack.org/summit/denver-2019/summit-schedule/events/23675/c… Project Resource Cleanup - followup: https://www.openstack.org/summit/denver-2019/summit-schedule/events/23674/p… Increasing API accessibility with granular policy and default roles: https://www.openstack.org/summit/denver-2019/summit-schedule/events/23642/i… Unified limits update and migration: https://www.openstack.org/summit/denver-2019/summit-schedule/events/23641/u… Presentations related to keystone that you may be interested in: You can't make a (Denver) omelette without breaking eggs: Using OpenStack policies for great good: https://www.openstack.org/summit/denver-2019/summit-schedule/events/23535/y… Lessons learnt federating OpenStack powered Supercomputers: https://www.openstack.org/summit/denver-2019/summit-schedule/events/23106/l… Leveraging OpenStack Keystone for Multi-Tenancy Support in Kubernetes: https://www.openstack.org/summit/denver-2019/summit-schedule/events/23673/l… Keystone - Project Update: https://www.openstack.org/summit/denver-2019/summit-schedule/events/23710/k… Bridging Clouds with Keystone to Keystone Federation: https://www.openstack.org/summit/denver-2019/summit-schedule/events/23285/b… Keystone JWS Tokens: Past, Present, and Future: https://www.openstack.org/summit/denver-2019/summit-schedule/events/23585/k… Keystone - Project Onboarding: https://www.openstack.org/summit/denver-2019/summit-schedule/events/23730/k… ### PTG Agenda I rearranged the PTG agenda[5] a bit now that we have scheduled some meetings with other teams. The schedule is still fluid and subject to change. [5] https://etherpad.openstack.org/p/keystone-train-ptg ### Team Dinner We're having out team dinner on Wednesday evening[6] in Denver. If you'd like to join us and haven't yet RSVP'd, please let me know, we'd be glad to have you. [6] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005549.ht… ## Open Specs Train specs: https://bit.ly/2uZ2tRl Ongoing specs: https://bit.ly/2OyDLTh ## Recently Merged Changes Search query: https://bit.ly/2pquOwT We merged 8 changes this week. ## Changes that need Attention Search query: https://bit.ly/2tymTje There are 27 changes that are passing CI, not in merge conflict, have no negative reviews and aren't proposed by bots. ## Bugs This week we opened 2 new bugs and closed 0. Bugs opened (2) Bug #1825867 (keystone:Undecided) opened by Abhishek Sharma M https://bugs.launchpad.net/keystone/+bug/1825867 Bug #1826197 (python-keystoneclient:Undecided) opened by jacky06 https://bugs.launchpad.net/python-keystoneclient/+bug/1826197 Bugs closed (0) Bugs fixed (0) ## Milestone Outlook https://releases.openstack.org/train/schedule.html The schedule for keystone has been posted. The next deadline is the spec proposal freeze at milestone 1 which is in a few weeks. ## Shout-outs See many of you next week! ## Help with this newsletter Help contribute to this newsletter by editing the etherpad: https://etherpad.openstack.org/p/keystone-team-newsletter

1 1

[goals][upgrade-checkers] Retrospective
by Matt Riedemann 27 Apr '19

27 Apr '19

Now that Stein is GA I figured I'd write up a quick retrospective for the upgrade-checkers goal [1]. Statistics ---------- From the tasks in the story [2]: - There were 52 total tasks. - Merged: 40 - Review: 4 (still open) - Invalid: 8* (not applicable or opted out) Excluding Invalid tasks, the overall completion percentage of the goal was 91% which is pretty good. Granted, the majority of projects just added the placeholder framework for the upgrade check command which is not very useful for operators, but it's a start for those projects to build in real checks later. *5 of the Invalid tasks were for deployment projects which were not a target for the goal [3]. The others were for swift, telemetry and panko. oslo library ------------ To ease development, Ben Nemec extracted the framework of the nova check code into the oslo.upgradecheck library [4]. This made getting the framework in place for all projects much easier and ensures a high level of consistency in the command structure which is really important with this type of thing. Thanks again Ben! Not universal ------------- As mentioned above, not all projects implemented the command since it maybe didn't make sense for those projects (swift, mistral and adjutant are good examples) and other projects just aren't in a place development-wise to put much priority in the goal (telemetry and panko). Extension points ---------------- Neutron created an extension point for their upgrade checks to support stadium projects and have already been using it. This was not something I thought about when we started the goal so it was cool that the neutron team embraced this and put their own spin on it. Contributions from NEC developers --------------------------------- Akhil Jain and Rajat Dhasmana from NEC volunteered to add the framework of the command in most projects which was extremely helpful. Thank you Akhil and Rajat, and NEC for providing development resources to work on a cross-community goal like this. Next ---- While most projects have the framework in place for upgrade checks, a lot of projects released Stein with a simple placeholder check. A few projects have started adding real checks to aid in upgrades to Stein, which is great. I'm hopeful that other projects will add real checks as they encounter upgrade issues during Train development and need a way to signal those changes to operators in an automated way. Remember: if you're adding an upgrades release note, consider if you can automate that note. Another next step is to get deployment projects to build in a call to each project's upgrade check command because without deployment projects using the tool it doesn't serve much purpose. Let me note that this does not need to be driven by the deployment projects either - developers from each project can integrate their check into a deployment project of choice, like I did for OpenStack-Ansible [5]. I'm sure the deployment project dev teams would appreciate the service project teams driving this work. [1] https://governance.openstack.org/tc/goals/stein/upgrade-checkers.html [2] https://storyboard.openstack.org/#!/story/2003657 [3] See the note: https://governance.openstack.org/tc/goals/stein/upgrade-checkers.html#compl… [4] https://docs.openstack.org/oslo.upgradecheck/latest/ [5] https://review.openstack.org/#/c/575125/ -- Thanks, Matt

6 8

[PTG][Docs][I18n] Planning and time schedule
by Frank Kloeker 27 Apr '19

27 Apr '19

Dear fellow stackers, PTG for Train will held next week in Denver. I'm alredy here and I wouldn't say, I miss the train from Stapleton Station with all the noice. But I wouldn't miss the Train PTG in this lovely town in the U.S. It reminds me that diversity is still the greatest strength of our community. Well, for the different reasons I do not expect many team members to attend onsite, but some should be still there. The scheduled Docs/I18n day is regarding timetable [1] Thursday, May 02 2019. Weather forecast says sunny with 16 degrees - so no snow do expect. I've created an Etherpd and linked it on the main list [2]. Please feel free to add your name there and propose your topic. I spotted two things so far: - Documentation PDF support which is an official main goal for train - Migrate I18n translation platform back from Zanata There is no full planned timetable yet. Maybe we have during the day an onsite discussion and want to sync with remote guys at 16:00? EU is 8 hours ahead and Korea/Japan 15 hours [3]. Let me know your thoughts and ideas or write it to the Etherpad. many thanks Frank (previous PTL I18n) [1] https://www.openstack.org/ptg/#tab_schedule [2] https://wiki.openstack.org/wiki/PTG/Train/Etherpads [3] https://www.timezones.de/time_conference_planner_timeszone/v2/1850147%2C295…

1 0

[tc][all] Github mirroring (or lack thereof) for unofficial projects
by Jim Rollenhagen 27 Apr '19

27 Apr '19

Hi, Now that the great OpenDev migration is done, we have a number of projects on Github which are no longer mirroring and becoming stale. This includes: - most repositories at https://github.com/openstack-infra - any repository in https://github.com/openstack which is no longer in https://opendev.org/openstack - I think that's it, but there could be others. The OpenDev and OpenStack teams have no plans to continue mirroring these projects to Github; primarily because we don't have a corresponding Github organization to put them in. However, teams can easily set up a mirror to any location they like on Github: http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005007.ht… The remaining question is what to do with the stale repos in the OpenStack organization on Github. Right now, we plan to just archive them. This means that the repository will be read-only, with a banner at the top saying it's archived. If a project owner wants to transfer the project to another Github organization, we can unarchive the project to do so, and they can maintain the mirroring via Zuul. If there's no wild objections to this plan, we'll go ahead with it soon. Maybe the week after the Summit, unless someone in the OpenDev team has spare cycles before that. // jim

5 4

Re: [placement][nova][ptg] Protecting driver-provided traits
by Chris Dent 26 Apr '19

26 Apr '19

On Thu, 11 Apr 2019, Adam Spiers wrote: > Ed Leafe <ed(a)leafe.com> wrote: >> The concept of “owning” particular traits isn’t in Placement. Rather, it is >> in the domain of the service that is using Placement. So any enforcement >> regarding which traits are acceptable has to be on the calling end, not in >> the Placement API. > > That feels like a slight jump in logic to me: the API can enforce ownership > without being the authoritative source of truth for that ownership. For > example, as I just suggested elsewhere in this thread, (static) ownership of > driver-provided traits could be tracked in os_traits. Maybe that's a dumb > idea; I'm not sure. It's not a dumb idea, but it's not really an idea we want to pursue. We've made an effort to keep both os-traits and os-resource-classes as dumb and "symbol only" as possible, minimizing code and metadata. Indicating ownership would require metadata. Enforcing it would require some form of code. > Having said that ... >> So yeah, “do nothing”. > > I'm totally fine with this too ;-) I only raised it because when I was > developing the driver-owned capability traits code, people seemed somewhat > concerned with the possibility of admins screwing things up. If the concern > is minimal then I'm certainly not religious about adding extra safeguards. Seeing as there's no huge drive for action on this topic, I've marked this topic as decided ("do nothing") on the etherpad [1] and we can ignore this thread henceforth. If people have additional ideas and thoughts please feel free to keep it alive. [1] https://etherpad.openstack.org/p/placement-ptg-train -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

4 7

[nova][dev] Pike Extended Maintenance coming soon
by melanie witt 26 Apr '19

26 Apr '19

Hi all, As mentioned in the nova meeting today, Pike Extended Maintenance is coming soon. The date shown on the release page says 2019-03-03 but it's predicted to occur after the Stein release (2019-04-10): http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003745.ht… We are currently in the process of flushing the stable/pike review queue for a final release of stable/pike: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:… Please be sure you get your backports proposed that you'd like to land in the final Pike release. After Pike is put into extended maintenance, there will be no more releases, but patches will still be accepted to the branch: https://docs.openstack.org/project-team-guide/stable-branches.html#maintena… Cheers, -melanie

2 3

[tripleo] TripleO CI Summary: Sprint 29
by Rafael Folco 26 Apr '19

26 Apr '19

Greetings, The TripleO CI team has just completed Sprint 29 / Unified Sprint 8 (Apr 04 thru Apr 24). The following is a summary of completed work during this sprint cycle: - Bootstrapped RDO and OSP jobs in the internal Software Factory instance. - Monitored stable/stein jobs for TripleO projects and added missing branchful job for stein. - Switched to buildah on containers build jobs upstream in check pipeline. - Improved docs and code comments in emit_releases file for upgrade jobs. - Moved the periodic standalone, standalone scenario 1-4 jobs to os-tempest - Promotion status: green on all branches The planned work for the next sprint [1] are: - Continue testing and defining jobs in the internal instance of Software Factory to run RDO and OSP on RHEL as an attempt to approximate upstream and downstream config/tooling used in the promotion pipeline. - Create a separate repository for collect-logs role and move code for being reused from other projects. - Schedule a test day for the zuul reproducer to fix deployment issues, usability and upgrade use cases. - Onboarded performance baremetal hardware to the internal Software Factory in order to run jobs of the promotion pipeline. - Noting lower capacity due to Summit / PTG The Ruck and Rover for this sprint are Rafael Folco (rfolco) and Sorin Sbarnea (zbr). Please direct questions or queries to them regarding CI status or issues in #tripleo, ideally to whomever has the ‘|ruck’ suffix on their nick. Ruck/rover notes are being tracked in etherpad [2]. Thanks, rfolco [1] https://tree.taiga.io/project/tripleo-ci-board/taskboard/unified-sprint-9 [2] https://etherpad.openstack.org/p/ruckroversprint9

1 0

[qa] Canceling QA office hour for next 3 weeks
by Ghanshyam Mann 26 Apr '19

26 Apr '19

Hello Everyone, Most of us will be in Summit and PTG next week and I will be on leave after PTG for 2 weeks to visit India. Due to that, I am cancelling the QA office hour for the next 3 weeks. -gmann

1 0

[placement][ptg] Enabling other projects to continue with placement or get started
by Chris Dent 26 Apr '19

26 Apr '19

>From the etherpad [1] * blazar * cinder * cyborg * ironic * neutron Who else? This is a bit of a catch-many topic. Despite being birthed in Nova, Placement is designed to be useful to lots of different services. There's already some time defined at the PTG to talk about the interaction of Ironic, Blazar, and Placement. What are the issues with that? What are the issues other services are experiencing with Placement? Preventing people from using Placement? What services are using Placement and the team doesn't know about it? [1] https://etherpad.openstack.org/p/placement-ptg-train -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

9 19

[horizon] No meetings next two weeks
by Ivan Kolodyazhny 26 Apr '19

26 Apr '19

Hi all, During the last IRC meeting [1] we agreed to skip the next two meetings. I hope to see you in Denver next week. [1] http://eavesdrop.openstack.org/meetings/horizon/2019/horizon.2019-04-24-15.… Regards, Ivan Kolodyazhny, http://blog.e0ne.info/

1 0

[octavia] Octavia 4.x for Rocky?
by Volodymyr Litovka 26 Apr '19

26 Apr '19

Dear colleagues, whether Octavia 4.x can be used with Rocky? Whether it makes sense (I mean, whether Octavia's new features are tied to Stein's features)? Thank you. -- Volodymyr Litovka "Vision without Execution is Hallucination." -- Thomas Edison

2 1

[neutron] Cancelling drivers meeting
by Miguel Lavalle 26 Apr '19

26 Apr '19

Dear Neutron drivers, We have 4 RFEs in the pipeline, previous to their discussion in the drivers meeting: 1) On three of them, I have left clarifying questions: https://bugs.launchpad.net/neutron/+bug/1825345, https://bugs.launchpad.net/neutron/+bug/1825336 and https://bugs.launchpad.net/neutron/+bug/1825943. I encourage you to examine them over the next few days and help clarify the proposals. 2) The fourth one, https://bugs.launchpad.net/neutron/+bug/1826396, comes from Bence Romsics (rubasov). I had an email / irc exchange with him and since he will be attending the PTG, we have agreed to discuss it in Denver Given the above, we are cancelling the April 26th drivers meeting. For those of you going to Denver, safe travels Best Regards Miguel

2 1

[cyborg] No IRC or engineering meeting next week [EOM]
by Nadathur, Sundar 26 Apr '19

26 Apr '19

Regards, Sundar

1 0

OpenStack instance fail to boot after unexpected compute node shutdown
by Md. Farhad Hasan Khan 26 Apr '19

26 Apr '19

Hi, We are running Openstack Rocky version. Our instances are getting volume from CEPH (mimic version). Suddenly one of our compute node got shutdown due to RAM issue. So all instances running on that compute node (linux/windows) got effected. After starting the compute node all services up & running. But instances on that compute node fail to boot. Instances are getting volume from CEPH storage & CEPH is in Healthy state. Please see below log. Requesting if anyone can help me to solve. ```````````````````````````````````````````````````````````````````````````` ```````````````````````````````````````````````````````````````````````````` ```````````````````````````````````````````````````````` ```````````````````````````````````````````````````````````````````````````` ```````````````````````````````````````````````````````````````````````````` ```````````````````````````````````````````````````````` Welcome to [0;34mCentOS Linux 7 (Core) dracut-033-554.el7 (Initramfs)[0m! [ 2.543762] systemd[1]: Set hostname to <localhost.localdomain>. [ 2.601779] usb 1-1: new full-speed USB device number 2 using uhci_hcd [ 2.609813] random: systemd: uninitialized urandom read (16 bytes read) [ 2.616574] random: systemd: uninitialized urandom read (16 bytes read) [ 2.622966] random: systemd: uninitialized urandom read (16 bytes read) [ 2.628863] random: systemd: uninitialized urandom read (16 bytes read) [ 2.635771] random: systemd: uninitialized urandom read (16 bytes read) [ 2.641509] random: systemd: uninitialized urandom read (16 bytes read) [ 2.647362] random: systemd: uninitialized urandom read (16 bytes read) [ 2.660222] systemd[1]: Reached target Local File Systems. [[32m OK [0m] Reached target Local File Systems. [ 2.668273] systemd[1]: Created slice Root Slice. [[32m OK [0m] Created slice Root Slice. [ 2.674835] systemd[1]: Created slice System Slice. [[32m OK [0m] Created slice System Slice. [ 2.681170] systemd[1]: Listening on udev Kernel Socket. [[32m OK [0m] Listening on udev Kernel Socket. [ 2.687811] systemd[1]: Listening on Journal Socket. [[32m OK [0m] Listening on Journal Socket. [ 2.694604] systemd[1]: Starting Create list of required static device nodes for the current kernel... Starting Create list of required st... nodes for the current kernel... [ 2.705069] systemd[1]: Starting Journal Service... Starting Journal Service... [ 2.710298] systemd[1]: Listening on udev Control Socket. [[32m OK [0m] Listening on udev Control Socket. [ 2.715399] systemd[1]: Reached target Sockets. [[32m OK [0m] Reached target Sockets. [ 2.720550] systemd[1]: Starting dracut cmdline hook... Starting dracut cmdline hook... [ 2.725277] systemd[1]: Reached target Slices. [[32m OK [0m] Reached target Slices. [ 2.731319] systemd[1]: Starting Apply Kernel Variables... Starting Apply Kernel Variables... [ 2.738718] systemd[1]: Starting Setup Virtual Console... Starting Setup Virtual Console... [ 2.744446] systemd[1]: Reached target Timers. [[32m OK [0m] Reached target Timers. [ 2.749668] systemd[1]: Reached target Swap. [ 2.781213] usb 1-1: New USB device found, idVendor=0627, idProduct=0001 [ 2.781217] usb 1-1: New USB device strings: Mfr=1, Product=3, SerialNumber=5 [ 2.781220] usb 1-1: Product: QEMU USB Tablet [ 2.781222] usb 1-1: Manufacturer: QEMU [ 2.781225] usb 1-1: SerialNumber: 42 [ 2.789965] input: QEMU QEMU USB Tablet as /devices/pci0000:00/0000:00:01.2/usb1/1-1/1-1:1.0/input/input4 [ 2.790189] hid-generic 0003:0627:0001.0001: input,hidraw0: USB HID v0.01 Mouse [QEMU QEMU USB Tablet] on usb-0000:00:01.2-1/input0 [[32m OK [0m] Reached target Swap. [ 2.887336] systemd[1]: Started Journal Service. [[32m OK [0m] Started Journal Service. [[32m OK [0m] Started Create list of required sta...ce nodes for the current kernel. [[32m OK [0m] Started Apply Kernel Variables. [ 2.903653] random: fast init done Starting Create Static Device Nodes in /dev... [[32m OK [0m] Started Create Static Device Nodes in /dev. [[32m OK [0m] Started dracut cmdline hook. Starting dracut pre-udev hook... [[32m OK [0m] Started Setup Virtual Console. [ 2.962744] device-mapper: uevent: version 1.0.3 [ 2.966701] device-mapper: ioctl: 4.37.1-ioctl (2018-04-03) initialised: dm-devel(a)redhat.com <mailto:dm-devel@redhat.com> [[32m OK [0m] Started dracut pre-udev hook. Starting udev Kernel Device Manager... [[32m OK [0m] Started udev Kernel Device Manager. Starting udev Coldplug all Devices... [[32m OK [0m] Started udev Coldplug all Devices. [[32m OK [0m] Reached target System Initialization. Starting Show Plymouth Boot Screen... Starting dracut initqueue hook... [[32m OK [0m] Started Show Plymouth Boot Screen. [[32m OK [0m] Reached target Paths. [[32m OK [0m] Started Forward Password Requests to Plymouth Directory Watch. [[32m OK [0m] Reached target Basic System. Mounting Configuration File System... [[32m OK [0m] Mounted Configuration File System. [ 3.278679] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10 [ 3.284823] FDC 0 is a S82078B [ 3.346628] scsi host0: ata_piix [ 3.358340] scsi host1: ata_piix [ 3.363061] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc0c0 irq 14 [ 3.369572] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc0c8 irq 15 [ 3.413844] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10 %G[ 3.489243] virtio_blk virtio1: [vda] 629145600 512-byte logical blocks (322 GB/300 GiB) [ 3.489830] vda: vda1 vda2 vda3 [ 3.527229] ata1.00: ATAPI: QEMU DVD-ROM, 2.5+, max UDMA/100 [ 3.529577] ata1.00: configured for MWDMA2 [ 3.542907] scsi 0:0:0:0: CD-ROM QEMU QEMU DVD-ROM 2.5+ PQ: 0 ANSI: 5 [ 3.622851] sr 0:0:0:0: [sr0] scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray [ 3.626938] cdrom: Uniform CD-ROM driver Revision: 3.20 [[32m OK [0m] Found device /dev/mapper/brilliant--centos--vg-root. Starting File System Check on /dev/...er/brilliant--centos--vg-root... [[32m OK [0m] Started File System Check on /dev/mapper/brilliant--centos--vg-root. [[32m OK [0m] Started dracut initqueue hook. Mounting /sysroot... [[32m OK [0m] Reached target Remote File Systems (Pre). [[32m OK [0m] Reached target Remote File Systems. [ 4.029336] SGI XFS with ACLs, security attributes, no debug enabled [ 4.035798] XFS (dm-0): Mounting V5 Filesystem [ 5.917747] blk_update_request: I/O error, dev vda, sector 13098937 [ 5.922604] blk_update_request: I/O error, dev vda, sector 13099961 [ 5.927008] blk_update_request: I/O error, dev vda, sector 13100985 [ 5.931339] blk_update_request: I/O error, dev vda, sector 13102009 [ 5.935231] XFS (dm-0): xfs_do_force_shutdown(0x1) called from line 1266 of file fs/xfs/xfs_buf.c. Return address = 0xffffffffc02738cc [ 5.942478] XFS (dm-0): I/O Error Detected. Shutting down filesystem [ 5.946134] XFS (dm-0): Please umount the filesystem and rectify the problem(s) [ 5.952283] XFS (dm-0): metadata I/O error: block 0x782fb9 ("xlog_bwrite") error 5 numblks 8192 [ 5.959663] XFS (dm-0): failed to locate log tail [ 5.963221] XFS (dm-0): log mount/recovery failed: error -5 [ 5.967272] XFS (dm-0): log mount failed [ 5.979786] blk_update_request: I/O error, dev vda, sector 0 [ 5.992687] blk_update_request: I/O error, dev vda, sector 0 [[1;31mFAILED[0m] Failed to mount /sysroot. See 'systemctl status sysroot.mount' for details. [[1;33mDEPEND[0m] Dependency failed for Initrd Root File System. [[1;33mDEPEND[0m] Dependency failed for Reload Configuration from the Real Root. [[32m OK [0m] Stopped dracut pre-udev hook. [[32m OK [0m] Stopped dracut cmdline hook. [[32m OK [0m] Stopped target Basic System. [[32m OK [0m] Stopped target System Initialization. [[32m OK [0m] Started Emergency Shell. [[32m OK [0m] Reached target Emergency Mode. [[32m OK [0m] Stopped dracut initqueue hook. [[32m OK [0m] Reached target Initrd File Systems. Generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report. :/# [ 12.851915] random: crng init done ```````````````````````````````````````````````````````````````````````````` ```````````````````````````````````````````````````````````````````````````` ```````````````````````````````````````````````````````` ```````````````````````````````````````````````````````````````````````````` ```````````````````````````````````````````````````````````````````````````` ```````````````````````````````````````````````````````` Thanks & B'Rgds, Rony

2 2

[nova][qa] nova-multi-cell job
by Matt Riedemann 26 Apr '19

26 Apr '19

We now have a working multi-cell CI job for nova proposed [1]. I've tried to fully document it both in the job definition and the commit message. I'd like this to be voting and gating as soon as possible given we've supported multi-cells since Pike so this has been a long-needed test environment for nova. However, if we want to be conservative we could make this non-voting in the check queue for awhile and then during or after the PTG make it voting and gating if people prefer. Thoughts? [1] https://review.opendev.org/#/c/655222/ -- Thanks, Matt

1 1

[nova][dev] broken periodic task to cleanup expired console token auths
by melanie witt 26 Apr '19

26 Apr '19

Howdy all, I'm looking for more opinions about how we should approach fixing the broken periodic task for cleaning up expired console token authorizations in the database: https://bugs.launchpad.net/nova/+bug/1816399 It's broken because it filters the database token auth records for 'host' when it goes to remove expired auths, but the 'host' used by the various types of consoles is not actually the hostname of the compute host, as the current [broken] code assumes. So the periodic task finds nothing for the compute manager's self.host and cleans up no token authorizations. There's a proposed patch that begins fixing the bug: https://review.opendev.org/637716 by iterating over a list of possible 'host' values based on the various console types. Each console type may use a different style of value for the 'host' which can also be driver dependent. That means we'd have to implement and expose 'get_<console>_host' methods for drivers that use a different host format for their console token auths. When I reviewed this patch, I wondered whether we should go down that road to fix this problem, or if we should instead stop using the required 'host' filter via the console_auth_token_destroy_expired_by_host method in the database API and instead add a console_auth_token_destroy_expired_by_instance method and have the nova-compute periodic task call that method in batches, similar to how the _heal_instance_info_cache periodic task works today. Can anyone else lend their thoughts on how we should move forward here? Cheers, -melanie

1 0

[oslo] PTG Schedule
by Ben Nemec 25 Apr '19

25 Apr '19

A quick reminder that Oslo will have a room Friday afternoon and Saturday morning. I'm expecting that we'll finish up our topics on Friday at this point, but we do have the option of Saturday if we need it. I have a very tentative schedule proposed on https://etherpad.openstack.org/p/oslo-train-topics I left several topics unscheduled for various reasons which are mentioned in the etherpad. We can fit them in whenever people are available. Thanks. -Ben

1 0

[manila] no meeting next week 2 May
by Tom Barron 25 Apr '19

25 Apr '19

Because we'll be doing PTG instead. Check #openstack-manila on freenode starting at 1500 UTC on 2 May for remote attendance instructions. We'll have our regular meeting a week later on 9 May on #openstack-meeting-alt at 1500 UTC. -- Tom Barron (tbarron)

1 0

[ironic][ptg] Schedule/Team gathering
by Julia Kreger 25 Apr '19

25 Apr '19

Greetings fellow ?Ironicans? I've posted a new etherpad[0] based upon our discussion in the planning etherpad[1]. Please review and if there are any scheduling issues please let me know. Also, we need to figure out an evening for a team gathering. I've posted a doodle[3]. Please submit it with-in the next few days and I'll begin looking around for someplace that might work. Thanks everyone! -Julia [0]: https://etherpad.openstack.org/p/DEN-train-ironic-ptg [1]: https://etherpad.openstack.org/p/DEN-train-ironic-brainstorming [2]: https://doodle.com/poll/e6q5e6pm72wbiwtz

2 3

Where is rpm-packaging spec for openstack placement?
by QingFeng Hao 25 Apr '19

25 Apr '19

Hi, I am trying to build openstack placement rpms on stein, I can find its related sources in https://tarballs.openstack.org/placement/, but I can't find its spec file in https://github.com/openstack/rpm-packaging, and I can only find nova.spec.j2 includes placement-api which I think isn't the case. Wher can I find placement's spec file please as from my understanding it is a seperated service in stein? Any tip is appreciated. Thanks! -- Regards QingFeng Hao

5 9

[nova] Nasty new gate regression as of 4/15 - bug 1825435
by Matt Riedemann 25 Apr '19

25 Apr '19

I spotted this yesterday [1] and according to logstash it showed up around 4/15. It's only hitting on nova unit tests, and I think is somehow related to the TestRPC unit tests, or maybe those just stall out as a result when we hit the stack overflow. I don't think it's due to any new oslo.config or oslo.messaging versions because there haven't been any, and it hits on both the lower-constraints and py36 jobs (so different versions of those packages). I've looked through the nova changes that merged since around 4/14 but nothing is jumping out at me that might be causing this stack overflow in the oslo.config code, but the cells v1 removal patches are pretty big and I'm wondering if something snuck through there - the cells v1 unit tests were doing some RPC stuff as I recall so maybe that's related. We need all eyes on this since it's a high failure rate and we're already experiencing really slow turnaround times in the gate. [1] https://bugs.launchpad.net/nova/+bug/1825435 -- Thanks, Matt

1 1

[ceilometer] Add Ceph disk usage for images and instances
by Gilles Mocellin 25 Apr '19

25 Apr '19

Hello, I've seen that it's possible to add polsters to ceilometer to gather additional metrics. I need to measure storage usage of my users, specially image usage (instance snapshots), where we still cannot have quotas. Does someone have already done something similar, where can I start to investigate ? I've seen some documentation to add Ceph RadosGW usage to Ceilometer, but it's not adaptable to my use case.

1 0

[manila][ptg] manila retrospective
by Tom Barron 25 Apr '19

25 Apr '19

We will kick off Manila PTG session next Thursday with a retrospective on the Stein cycle -- what went well, what we should improve, etc. So I set up an etherpad [1] that we will use to organize the discussion. Please go ahead and add items to the etherpad as they occur to you. Thanks, -- Tom Barron (tbarron) [1] https://etherpad.openstack.org/p/manila-stein-retrospective

1 0

Migrating git repos to OpenDev
by corvus＠inaugust.com 25 Apr '19

25 Apr '19

Hi, As discussed in November[1], the OpenStack project infrastructure is being rebranded as "OpenDev" to better support a wider community of projects. We are nearly ready to perform the part of this transition with the largest impact: moving the authoritative git repositories for existing projects. In this email, I'd like to introduce the new hosting system we are preparing, discuss the transition, and invite projects to work with us on the logistics of the change. Gerrit ====== Gerrit is the core of our system and it will remain so in OpenDev. As part of this move, we will rename the gerrit server from review.openstack.org to review.opendev.org. As part of the transition, we will automatically merge appropriate changes to all branches of all repositories updating .gitreview and Zuul configuration files. Any further changes (README files, etc.) we expect to be made by individual project contributors. Repository Browsing =================== Currently our canonical *public* repository system is the cgit server at https://git.openstack.org/ (and git.airshipit.org, git.starlingx.io, and git.zuul-ci.org) This is a load balanced cluster of several servers which is designed to handle all the public git repository traffic, as it scales much better than Gerrit (and has a more friendly domain name). >From a technical standpoint, it's excellent, but its usability could be improved. Therefore, as part of this transition, we will replace the cgit servers with a new system based on Gitea. Gitea is a complete development collaboration system, but it's very flexible and will allow us to disable components which we aren't using. We will operate it in a read-only configuration where it will act as the public mirror for Gerrit. The advantages it has over the current system are: * Shorter domain name in project URLs: https://git.openstack.org/openstack/nova vs https://opendev.org/openstack/nova * Clone and browsing URLs are the same (with cgit, the browsing URL has an extra path component) * More visually pleasing code browsing * Integrated code searching * Ability to highlight multiple lines in links When we perform the transition we will install redirects from git.openstack.org (and the other git sites) to opendev.org, and will maintain those redirects for the foreseeable future. We will construct them so that even existing deep links to individual files in individual commits to cgit will redirect to the correct location on opendev.org. This system is up and running now with a live mirror of data from Gerrit, and you can start testing it out today at https://opendev.org/ Please let us know if you encounter any problems. If you would like to read more about the design of this system and the transition, see the infra-spec[2]. GitHub ====== Currently all OpenStack projects are replicated to GitHub. We do not plan on changing that during the transition, however, any projects outside of the openstack*/ namespaces will not automatically be replicated to GitHub, and we do not plan on adding that in the future. We do, however, support projects using Zuul to run post-merge jobs to push updates to GitHub or any other third-party mirrors with their own credentials. We will be happy to work with anyone interested in that to help set up jobs to do so. We are adopting this approach so that individual projects can have more control over how they are represented in social media, and to give us more flexibility in supporting our own organizational namespaces on OpenDev without assuming they map directly to GitHub. Eventually we plan on moving the OpenStack project to that system as well and retiring direct replication from Gerrit to GitHub completely. But we will defer that work until after this transition. Logistics ========= We can prepare much of the system in advance (as we have for the hosting system on opendev.org) but the actual transition and renaming of the Gerrit server will need to happen at once during an outage window. We need to schedule that outage and begin preparing for it. Since all of the project git URLs are going to change (to replace git.openstack.org with opendev.org and review.openstack.org with review.opendev.org) we can additionally take the opportunity to reorganize projects into different organizations. For example, during the transition we will rename Zuul, and it's associated projects, from the "openstack-infra" org to "zuul". So their new names will be "zuul/zuul", "zuul/nodepool", etc. This is an excellent time for the rest of the OpenStack Foundation pilot projects to do the same. If the OpenStack project desires this, it would also be a good time to move unofficial projects out of the openstack/ namespace. Therefore, we need your help: Action Items ============ We need each of the following projects: * OpenStack * Airship * StarlingX * Zuul To nominate a single point of contact to work with us on the transition. It would be helpful for that person to attend the next (and possibly next several) openstack infra team meetings in IRC [3]. We will work with those people on scheduling the transition, as well as finalizing the list of projects which should be renamed as part of the transition. If you manage an unofficial project and would like to take the opportunity to move or rename your project, please add it to this ethercalc[4]. [1] http://lists.openstack.org/pipermail/openstack-dev/2018-November/136403.html [2] http://specs.openstack.org/openstack-infra/infra-specs/specs/opendev-gerrit… [3] http://eavesdrop.openstack.org/#Project_Infrastructure_Team_Meeting [4] https://ethercalc.openstack.org/opendev-transition

19 39

[publiccloud]Bi-weekly Meeting Thursday Apr 25th
by Zhipeng Huang 25 Apr '19

25 Apr '19

Hi All, We will have our bi-weekly meeting today starting UTC1400, please checkout the agenda at https://etherpad.openstack.org/p/publiccloud-wg Lokk forward to your -- Zhipeng (Howard) Huang Principle Engineer OpenStack, Kubernetes, CNCF, LF Edge, ONNX, Kubeflow, OpenSDS, Open Service Broker API, OCP, Hyperledger, ETSI, SNIA, DMTF, W3C

1 0

[release] Release countdown for week R-26 and R-25, April 15-26
by Tony Breeds 25 Apr '19

25 Apr '19

Here we go again! The Train cycle will about normal at 26 weeks. Please take a couple of minutes to look over the schedule for this release: https://releases.openstack.org/train/schedule.html We also have the same data available as an ics: https://releases.openstack.org/train/schedule.ics it's a good idea for interested parties (for example PTLs and liaisons) to subscribe to it so upcoming deadlines are visible. Development Focus ----------------- Focus should be on optimizing the time at the PTG and following up after the event to jump start Train development and spec planning Action Required --------------- PTLs will receive a direct email from me establishing contact and setting communication expectations. Be on the lookout! General Information ------------------- All teams should review their release liaison information and make sure it is up to date [1]. While reviewing liaisons, this would also be a good time to make sure your declared release model matches the project's plans for Train (e.g. [2]). This should be done prior to the first milestone and can be done by proposing a change to the Stein deliverable file for the project(s) affected [3]. Now would be a good time to start brainstorming Forum topics while some of the PTG discussions are fresh. Just a couple months until the Summit and Forum in Berlin. Upcoming Deadlines & Dates -------------------------- Train-1 milestone: Jun 03 (R-19 week) Forum at OpenInfrastructure Summit in Denver: April 29 - May 1 PTG right after the OpenInfrastructure Summit in Denver: May 2 - 4 Yours Tony (tonyb). [1] https://wiki.openstack.org/wiki/CrossProjectLiaisons [2] https://opendev.org/openstack/releases/src/branch/master/deliverables/train… [3] https://opendev.org/openstack/releases/src/branch/master/deliverables/train

2 2

gitweb link broken after OpenDev migration
by Nadathur, Sundar 25 Apr '19

25 Apr '19

The gitweb link seen in the diffs in review.openstack.org is broken - it still points to git.openstack.org in all the diffs I looked at, and that returns a 404. E.g. https://drive.google.com/file/d/1XVEyLnDOeJ0UUY16EfmDmV8029Ktp6HS/view?usp=… Regards, Sundar

3 4

[cyborg] [ironic] [ptg] Cyborg-Ironic cross-project etherpad available
by Nadathur, Sundar 25 Apr '19

25 Apr '19

Please see https://etherpad.openstack.org/p/ptg-train-xproj-ironic-cyborg . It has been linked to: https://etherpad.openstack.org/p/DEN-train-ironic-brainstorming Line 162 https://etherpad.openstack.org/p/DEN-train-ironic-ptg Line 198 https://etherpad.openstack.org/p/cyborg-ptg-train Line 20 https://wiki.openstack.org/wiki/PTG/Train/Etherpads Regards, Sundar

1 0

[all][qa][ptg][forum] QA PTG Schedule and Related Forum Sessions
by Ghanshyam Mann 25 Apr '19

25 Apr '19

Hello Everyone, I have prepared the QA schedule for Denver Open Infrastructure Summit and PTG. We will be meeting for two days in PTG which is divided into two parts 1. topic discussions for one and half days 2. Code Sprint & Open Discussion. * PTG: QA 2nd May- 3rd May 2019: Room 105 PTG Scheduled is flexible and we can adjust it based on request. QA Stein PTG Schedule - https://ethercalc.openstack.org/Train-PTG-QA-Schedule Details of each session can be found in this etherpad - https://etherpad.openstack.org/p/qa-train-ptg * Summit: QA Forum sessions: Along with project updates & onboarding sessions, QA team will host QA feedback sessions . 1. OpenStack QA - Project Update: Tuesday, April 30, 2:35pm-2:55pm [1] 2. OpenStack QA - Project Onboarding : Wednesday, May 1, 9:00am-9:40am [2] 3. Users / Operators adoption of QA tools / plugins : Wednesday, May 1, 10:50am-11:30am [3] [1] https://www.openstack.org/summit/denver-2019/summit-schedule/events/23703/o… [2] https://www.openstack.org/summit/denver-2019/summit-schedule/events/23728/o… [3] https://www.openstack.org/summit/denver-2019/summit-schedule/events/23660/u… -gmann

1 0

[all][qa][forum] Etherpad for Users / Operators adoption of QA tools / plugins sessions
by Ghanshyam Mann 25 Apr '19

25 Apr '19

Hello Everyone, I've created the etherpad for the QA feedback sessions[1] which is scheduled on Wednesday, May 1, 10:50am-11:30am. I have added a few basic feedback questions there and If you have any additional items to add or modify, please feel free to do that. In case, you are not able to attend this session, you can still write your feedback with your irc/name contact. Etherpad: https://etherpad.openstack.org/p/Den-forum-qa-ops-user-feedback [1] https://www.openstack.org/summit/denver-2019/summit-schedule/events/23660/u… -gmann

1 0

[self-healing][PTG][Forum] Self-healing SIG sessions at Denver Forum and PTG
by Adam Spiers 25 Apr '19

25 Apr '19

Hi there, This is a last call for topics for discussion at either of the two self-healing SIG sessions scheduled next week in Denver. Everyone is warmly invited to add topics they are interested in to the etherpad: https://etherpad.openstack.org/p/DEN-self-healing-SIG As always, we are particularly interested to hear feedback from operators: - Are you already implementing any self-healing functionality in your OpenStack clouds? - If so, how are you doing it, and what's working and not working? - What self-healing functionality would you like to see which is currently missing? The Birds of a Feather session on Wednesday May 1, 9:50am-10:30am is the best time to provide that feedback: https://www.openstack.org/summit/denver-2019/summit-schedule/events/23743/s… However we also have a PTG session the whole afternoon of Thursday May 2nd: https://www.openstack.org/ptg#tab_schedule and while it will certainly cover developer-oriented topics, operator feedback is very welcome there too. Looking forward to seeing you all! Regards, Adam and Eric

1 0

[storyboard] sessions at the Summit/Forum + PTG
by Kendall Nelson 24 Apr '19

24 Apr '19

Hello! Interested in StoryBoard? Got questions? Want to join us in the development? Well! We have one Forum session on Monday from 3:50pm to 4:30pm [1]. The focus of the session is to gather pain points people are encountering as we've continued to move forward through our backlog. Please come and share feedback with us! We are also planning on convening in during the PTG in the infra room Thursday morning. We will focus on a complete triage and overhaul and prioritization of all the open stories in Storyboard. If you're interested in helping out, come join us! We will book/update the PTGbot accordingly next week. -Kendall (diablo_rojo) [1] https://www.openstack.org/summit/denver-2019/summit-schedule/events/23658/i…

1 0

[oslo] Project Update Slides
by Ben Nemec 24 Apr '19

24 Apr '19

First draft here: https://docs.google.com/presentation/d/1flIiDiXdE-M4kiL5QkvceqgkqarCm42yc8i… If I missed anything or anything looks wrong let me know ASAP. I'll probably be tweaking them slightly between now and the actual session, but this is pretty much what I plan to present. Thanks. -Ben

1 0

Mentoring at Summit
by Amy Marrich 24 Apr '19

24 Apr '19

For those of you going to summit next week I wanted to point out a few mentoring related sessions. Thanks, Amy (spotz) Sunday: 9:00 - 5:50 OpenStack Upstream Institute sponsored by Lenovo https://www.openstack.org/summit/denver-2019/summit-schedule/events/23607/o… Monday: 12:20-1:40 - Speed Mentoring Lunch sponsored by Intel - RSVP required https://www.openstack.org/summit/denver-2019/summit-schedule/events/23757/r… Tuesday: 4:20 - 5:00 - Welcoming New Contributors State of the Union https://www.openstack.org/summit/denver-2019/summit-schedule/events/23659/w… Wednesday: 10:50-11:30 - Diversity WG BoF - looking for help with the Mentoring Program https://www.openstack.org/summit/denver-2019/summit-schedule/events/23745/d…

1 0

[nova] No meeting the week of the PTG
by Eric Fried 24 Apr '19

24 Apr '19

The Nova meeting that would have been held on 5/2 is canceled due to the PTG. efried .

1 0

[placement][tripleo][kolla] Update on placement extraction from nova
by Matt Riedemann 24 Apr '19

24 Apr '19

I put together an etherpad [1] for a Forum session at the upcoming summit to go over what happened with placement extraction in Stein and the plan for Train. With help I was able to figure out where the extracted placement packages are so it's good to know those exist. Mohammed also gave me the status on OpenStack-Ansible but I'm less clear on TripleO and Kolla. I thought TripleO was supporting fresh installs with extracted placement but gerrit is down and Lee is out today so I'm not sure, and I'm not seeing anything about it in TripleO release notes. I did find that the Kolla release notes say they support extracted placement [2] but I'm not sure to what extent - is it just install from source (pypi?) or also some package support? How about upgrades, i.e. the data migration from placement-in-nova to extracted placement? So if people from the TripleO and Kolla teams can reply here and clarify I can get that back into the etherpad before the Forum session. [1] https://etherpad.openstack.org/p/DEN-update-on-placement-extraction-from-no… [2] https://docs.openstack.org/releasenotes/kolla/stein.html -- Thanks, Matt

4 6

[dev][tc][all] Train Goal Schedule and Update
by Lance Bragstad 24 Apr '19

24 Apr '19

Hi all, Since the community goal selection process has taken a turn, we wanted to send an update regarding the current goals. We originally wanted to have the goals for Train be merged by this point to give project teams ample time to plan for them accordingly in their PTG scheduled. Due to discussions raised in each [0][1], it doesn't sound like either will be making it into Train as a feasible community goal. Fortunately, a couple of last minute goals might be a perfect fit for Train, instead of having a release without any community goals. The first one suggested is to render documentation as PDFs [2]. The second goal, which still needs to be proposed, is for IPv6 support. The advantage is that both of these goals are much smaller in scope, but still useful. We're running up against the clock on getting goals selected for Train, but we still have an opportunity to come to agreement on the new proposals before the PTG. We'd like to ask TC and members of the community to review the proposed goals at their earliest convenience. Additionally, if someone wants help write up the IPv6 support goal [3][4], please reach out gmann and mnaser. Even though we were originally trying to make sure we had firm goals well before the PTG, the reduced scope of the new goals should make them easier to talk about in impromptu sessions or the hallway track. Thanks, JP & Lance [0] https://review.openstack.org/#/c/639376/ [1] https://review.openstack.org/#/c/639010/ [2] https://review.openstack.org/#/c/647712/ [3] http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2019… [4] Note that this goal is for testing IPv6 networking setups in all projects. We already have a tempest full ipv6 job, it would be a matter of making these jobs passing and voting in the future.

4 5

Re: [Release-job-failures] release-post job for openstack/releases failed
by Thierry Carrez 24 Apr '19

24 Apr '19

zuul(a)openstack.org wrote: > Build failed. > > - tag-releases http://logs.openstack.org/76/762e357c0d821c35b0373ac344d697807be031bf/relea… : FAILURE in 3m 35s > - publish-tox-docs-static publish-tox-docs-static : SKIPPED Error during release-post job processing https://opendev.org/openstack/releases/commit/22a2d440f0abddff4ba8d9e3cb8a1… The tags went through, but the Launchpad comment-adding script failed with: python3 -u /home/zuul/scripts/release-tools/launchpad_add_comment.py '--subject=Fix included in openstack/panko 3.1.1' '--content=This issue was fixed in the openstack/panko 3.1.1 release.' 1710812 Connecting to Launchpad at 'production' using credentials in '/home/zuul/.launchpadlib/creds'... Adding comment to #1710812... ERROR during save ! (HTTP Error 401: Unauthorized Response headers: --- content-length: 60 content-type: text/plain date: Wed, 24 Apr 2019 05:17:10 GMT server: zope.server.http (HTTP) status: 401 x-lazr-oopsid: OOPS-f5382a2ee4e917c314954fb63ea98c61 x-powered-by: Zope (www.zope.org) Python (www.python.org) --- Response body: --- b'Unknown consumer (System-wide: Ubuntu (review.opendev.org))' --- ) We might have to reestablish credentials for that to work again... Impact: Bugs were not commented on (job failed), and the release website was not refreshed (job skipped). -- Thierry Carrez (ttx)

3 4

[keystone] Team dinner in Denver
by Colleen Murphy 24 Apr '19

24 Apr '19

Berlin feels like it was ages ago, so let's organize a team dinner in Denver. Poll here: https://framadate.org/BHNNU9S3f9N3lasH If you have strong feelings or even mild inclinations about where to go, please comment on the poll or in the brainstorming etherpad[1] because otherwise I am pretty much just going to throw a dart. Colleen [1] https://etherpad.openstack.org/p/DEN-keystone-forum-sessions

5 5

[openstack-helm] Office hours - 20:00-21:00UTC Wednesdays in #openstack-helm
by Pete Birley 24 Apr '19

24 Apr '19

------------------------------ Hey! Thanks to all those who could attend the meeting we held on the 9th of April; at this meeting we decided that we would resume holding office hours weekly in IRC until the end of this development cycle at least. These will be in our standard channel #openstack-helm, from 20:00-21:00UTC on Wednesdays. During this time we will ensure that there is representation from the core reviewers, and try to help with general support: from onboarding, and deployment issues, to more interactive disucssion regarding specs and testing - please drop in and ask us anything! :) The meeting agenda for this is here: * https://etherpad.openstack.org/p/openstack-helm-meeting-2019-04-09 With minutes logged here: * http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.… The next OpenStack-Helm meeting will be held on the 16th April, at 3pm UTC in #openstack-meeting-4 in freenode IRC, with the following agenda: https://etherpad.openstack.org/p/openstack-helm-meeting-2019-04-16 Cheers Pete

2 1

[placement][ptg] Containers/dockerfiles
by Chris Dent 24 Apr '19

24 Apr '19

>From etherpad [1]: * Some talk in the past of moving https://github.com/cdent/placedock into placement but not sure * Another option is [to] trigger container build with each merge I wrote this one, so I guess I should expand on it a bit. Basically, placedock is a Dockerfile for placement that strives to be small but configurable. The same repo also contains instructions (and YAML) for using the container in kubernetes, and provides a helm chart that uses the generated image. Each of those three things is done in a way where many of the choices are made for you in favor of being light and simple. In things like Kolla, openstack-helm, and other containerizing setups some of those choices are left as options, making the build and run infrastructure more complex. The result with placedock is a tiny service that scales horizontally really well. In the past there's been talk of including some of that stuff in the placement repo itself as a sort of "hey look, here's one way to do it". If we did that, which stuff? Another suggestion has been to use a web-hook or similar from zuul to trigger an image build (either at docker hub or some other registry) post-merge. Or we can let things go as they are (I manually build new images every now and again, which triggers automatic placecat [2] testing). The reason this comes back up is because I'm somewhat concerned that the "seriously, this is really simple" aspect of Placement gets lost and there's probably plenty of useful info in this kind of stuff. If we make it owned by more than just me, that might help spread the learning. Thoughts?k [1] https://etherpad.openstack.org/p/placement-ptg-train [2] https://github.com/cdent/placecat -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

6 7

[octavia] Octavia 4.x for Rocky?
by Volodymyr Litovka 24 Apr '19

24 Apr '19

Dear colleagues, whether Octavia 4.x can be used with Rocky? Whether it makes sense (I mean, whether Octavia's new features are tied to Stein's features)? Thank you. -- Volodymyr Litovka "Vision without Execution is Hallucination." -- Thomas Edison

2 1

[ptg] ptgbot HOWTO
by Thierry Carrez 24 Apr '19

24 Apr '19

Hi everyone, In a few days, some contributor teams will meet in Denver for the 5th Project Teams Gathering. The event is organized around separate 'tracks' (generally tied to a specific team/group). Topics of discussion are loosely scheduled in those tracks, based on the needs of the attendance. This allows to maximize attendee productivity, but the downside is that it can make the event a bit confusing to navigate. To mitigate that issue, we are using an IRC bot to expose what's happening currently at the event at the following page: http://ptg.openstack.org/ptg.html It is therefore useful to have a volunteer in each room who makes use of the PTG bot to communicate what's happening. This is done by joining the #openstack-ptg IRC channel on Freenode and voicing commands to the bot. Usage of the bot is of course optional, but in past editions it was really useful to help attendees successfully navigate this dynamic event. How to keep attendees informed of what's being discussed in your room --------------------------------------------------------------------- To indicate what's currently being discussed, you will use the track name hashtag (found in the "Scheduled tracks" section on the above page), with the 'now' command: #TRACK now <what's currently being discussed> Example: #swift now brainstorming improvements to the ring You can also mention other track names to make sure to get people attention when the topic is transverse: #ops-meetup now discussing #cinder pain points There can only be one 'now' entry for a given track at a time. To indicate what will be discussed next, you can enter one or more 'next' commands: #TRACK next <what will be discussed and when> Example: #api-sig next at 2pm we'll be discussing pagination woes Note that in order to keep content current, entering a new 'now' command for a track will automatically erase any 'next' entry for that track. Finally, if you want to clear all 'now' and 'next' entries for your track, you can issue the 'clean' command: #TRACK clean Example: #ironic clean How to book reservable rooms ---------------------------- Like at every PTG, in Denver we will have additional reservable space for extra un-scheduled discussions. Two of those rooms (Ballroom 4 and Room 112) are equipped with a projector, so if your discussion would benefit from projection, you can also book time there. Finally, some of the smaller teams do not have any pre-scheduled space, and will solely be relying on this feature to book the time that makes the most sense for them. Those teams are the OpenStack release management team (#release-management) and requirements team (#requirements), the Extended Maintenance SIG (#extended-maint-sig), the Security SIG (#security-sig), the Bare Metal SIG (#baremetal-sig) and the Interoperability working group (#interop-wg). The PTG bot page shows which track is allocated to which room, as well as available reservable space, with a slot code (room name - time slot) that you can use to issue a 'book' command to the PTG bot: #TRACK book <slot code> Example: #release-management book Room 112-ThuA1 Any track can book additional space and time using this system. All slots are 1h45-long. If your topic of discussion does not fall into an existing track, it is easy to add a track on the fly. Just ask PTG bot admins (ttx, diablo_rojo...) on the channel to create a track for you (which they can do by getting op rights and issuing a ~add <TRACK> command). For more information on the bot commands, please see: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst Let me know if you have any additional questions. -- Thierry Carrez (ttx)

1 0

[scientific-sig] No IRC meeting today
by Stig Telfer 24 Apr '19

24 Apr '19

Hi All - Apologies, no Scientific SIG meeting today. We have plenty going on besides in preparation for Denver next week, and I hope to see you there. Cheers, Stig

1 0

[kolla] Instance unable to contact outside network
by vladimir franciz blando 24 Apr '19

24 Apr '19

Hi All, Deploying an OpenStack Rocky (1 controller+ceph, 1 compute+ceph) environment on Packet.net using kolla-ansible 7.1.0. Everything works except Instance connectivity going out. controller1 network http://paste.openstack.org/show/749565/ compute1 network http://paste.openstack.org/show/749566/ openvswitch show http://paste.openstack.org/show/749567/ 1. Instance to Instance PING via it's private IP = success 2. Instance to Instance PING via floating IP = success 3. Instance to gateway ping = success 4. Instance to outside world (ex. 8.8.8.8 or google.com) = failed 5. PINGing the instance from the controller node using the floating IP = failed Here is my global.yml file http://paste.openstack.org/show/lpAGgrEm8rNe43WeB8Uo/ Here is my multinode file http://paste.openstack.org/show/DL7l1WG2xotH5KziwuyL/ Here is my init-runounce file http://paste.openstack.org/show/749568/ - Vlad ᐧ

2 1

[Kolla-Ansible] Support for LXC
by Amit Kumar 24 Apr '19

24 Apr '19

Hello All, We have deployed OpenStack multinode using Kolla-Ansible. We are able to create VMs, Docker Containers (using Zun). However, we also want to launch LXCs, but we couldn't find any such option in globals.yaml to enable this support. Is there any plan to provide it out-of-box? If anybody has enabled LXC using Kolla-Ansible by themselves, then also please let us know. Thanks. Regards, Amit

2 1

[neutron] CI meeting next week
by Slawek Kaplonski 24 Apr '19

24 Apr '19

Hi, As most of us will be on summit next week, CI meeting from 30.04 is cancelled. We will have next meeting on 7.05. See You in Denver next week :) -- Slawek Kaplonski Senior software engineer Red Hat

1 0

[tripleo][openstack-ansible] collaboration on os_tempest role update XX - Apr 24, 2019
by Chandan kumar 24 Apr '19

24 Apr '19

Hello, Here is the 20th update (Apr 17 to Apr 23, 2019) on collaboration on os_tempest[1] role between TripleO and OpenStack-Ansible projects. Highlights of the week: * os_tempest got support of novajoin tempest plugin. * During stein branching on OSA side, we found that tempest_git_repo is not defined thanks to Jesse Pretorius (odyssey4me) and mnaser for fixing it. Things got merged: os_tempest: * Enable support for novajoin tempest plugin - https://review.openstack.org/652986 * Only add tempest/tempestconf git constraints *_git_repo is defined - https://review.opendev.org/653690 Things in Progress: os_tempest: * Make smoke tests as a default whitelist tests - https://review.openstack.org/652060 * Update openstack.org -> opendev.org - https://review.opendev.org/654942 tripleo: * Enable os_tempest in baremetal-full-overcloud-validate playbook - https://review.openstack.org/652983 * Run novajoin tempest tests in all TLS job using os_tempest - https://review.openstack.org/639324 * Add documentation for consuming os_tempest role - https://review.opendev.org/#/c/654406/ What is coming? On TripleO side, we will be working on porting all upstream standalone tripleo jobs to os_tempest. We will be continue working on current os_tempest patches. Here is the 19th update [2]. Have queries, Feel free to ping us on #tripleo or #openstack-ansible channel. Links: [1.] http://git.openstack.org/cgit/openstack/openstack-ansible-os_tempest [2.] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005256.ht… Thanks, Chandan Kumar

1 0

[tricircle] Bi-weekly meeting brief note (2019-04-24)
by zhangchi＠szzt.com.cn 24 Apr '19

24 Apr '19

Hi, All, Here is today bi-weekly meeting brief note. We’ve previously decided to move back the Tricircle bi-weekly meeting back to community IRC channel, and this week some of tricircle team members facing trouble of registering IRC account so that we have to use wechat group for this week meeting again. Startling from next week, we will move back the meeting to IRC, when all team members having their IRC accounts ready. Below is a brief note of what we discussed today, 1. [tricircle] This bug is now being tracked: Tricircle some unit tests can not pass since neutron Stein introduced network_segment_ranges https://bugs.launchpad.net/neutron/+bug/1821567. PR has been submitted. 2. [tricircle] tricircle unit tests development is in progress, targeting to have 80% user case coverage. 3. [tricircle] Integrate Tricircle to work with zuul v3 (this is under planning) 4. [tricircle] Deploy containers in tricircle environment (discussion started and currently team is working on writing spec) 5. [tricircle] Finish the PR "ipv6_address_mode" not found in unit test (planning) 6. [tricircle] meeting will move back to IRC (openStack-meeting channel) every two weeks starting from next Wednesday (2019-05-08) UTC 1:00 7. [tricircle] Haoyang shared 9th Open Source Hackathon summary held in Shenzhen last week to catch up latest OpenStack activity in China.

1 0

[Forum][Ops] Ops War Stories Lightning Talk session
by Shintaro Mizuno 24 Apr '19

24 Apr '19

Hi There is a Forum session for the operators [1] at the Denver Summit, which I want to shed some light on before the Summit. This session is a Lightning Talk session for the operators to share their war stories and architectures. It will be a short 5 min slot and slides are not required (you can have them if you want). If you have stories to share, please put your name and a title of your talk to the etherpad below. [1] https://etherpad.openstack.org/p/DEN-ops-war-stories-LT Hope to see you in Denver! Best regards, Shintaro -- Shintaro MIZUNO NTT Software Innovation Center TEL: 0422-59-4977 E-mail: mizuno.shintaro(a)lab.ntt.co.jp (Expires on 2019.6） New E-mail：shintaro.mizuno.gt(a)hco.ntt.co.jp

1 1

[tricircle] Today's Topics (2019-04-24)
by zhangchi＠szzt.com.cn 24 Apr '19

24 Apr '19

Today's topic is: 1. [tricircle] The bug is now being tracking: Tricircle some unit tests can not pass since neutron Stein introduced network_segment_ranges https://bugs.launchpad.net/neutron/+bug/1821567 pr have been submitted 2. [tricircle] tricircle unitests is being added aims at Use case coverage over 80% (in progress) 3. [tricircle] Make Tricircle work with zuul v3 (planned) 4. [tricircle] deploying containers in tricircle environments (started and writing sepc) 5. [tricircle] finish the pr "ipv6_address_mode" not found in unit test (planning) 6. [tricircle] meeting will move back to IRC (openStack-meeting channel) every two weeks since next Wednesday (2019-05-08) UTC 1:00 7. [tricircle] learning the 9th Open Source Cloud Hackathon

1 0