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

Announcing Gertty 1.6.0
by corvus＠inaugust.com 24 Apr '19

24 Apr '19

Announcing Gertty 1.6.0 ======================= Gertty is a console-based interface to the Gerrit Code Review system. Gertty is designed to support a workflow similar to reading network news or mail. It syncs information from Gerrit to local storage to support disconnected operation and easy manipulation of local git repos. It is fast and efficient at dealing with large numbers of changes and projects. The full README may be found here: https://opendev.org/ttygroup/gertty/src/branch/master/README.rst Changes since 1.5.0: ==================== * The default config file location is now ~/.config/gertty/gertty.yaml (but Gertty will fall back on the previous default of ~/.gertty.yaml if it is not found) * The source code is now hosted in OpenDev (https://opendev.org) * Gertty supports (and should be run with) python3 * Added tab display support * Reviewkeys are enabled in diffs * Added a new option (off by default) to close the change after reviewing * Added inline comments to the change overview screen * The size column graph is more configurable * Reviewkeys now support sending a message * Added more example configurations As well as several bug fixes and stability improvements. Thanks to the following people whose changes are included in this release: Clint Byrum Dominique Martinet Doug Wiegley Emilien Macchi Ian Wienand John L. Villalovos Logan V Major Hayden Masayuki Igawa Matthias Runge Natal Ngétal Nate Johnston Nguyen Hung Phuong Robert Collins Tobias Henkel Tristan Cacqueray

1 0

[First Contact] [SIG] [PTL] Project Liaisons Update
by Matthew Oliver 24 Apr '19

24 Apr '19

Hey PTLs, Now that the new PTL election season is over and you all should be coming to grips with your life choices. It's time to update the First contact project liaison list[0]. What are first contact liaisons do I hear you ask? We at the first contact SIG strive to be a point of call for new contributors. When they do contact or we find a new contributors first patch, we try and connect them with the project. This could be as simple a adding the liaison to the review or providing and introduction. Anyone can be a liaison for a project, so you're welcome to delegate, however we do default to PTLs. Further given that we live on a globe, tracking and having multiple liaisons on each project from different timezones would also be a big win. For those of you who have already delegated previously and/or are continuing to PTL, you don't get off too easily. The world has finished it's summertime/daylight saving dance, so is time to update your timezone's too. I know the summit/PTG is just around the corner, so while your updating your etherpad and wiki's what's one more ;) Regards, Matt [0] https://wiki.openstack.org/wiki/First_Contact_SIG#Project_Liaisons

1 0

The python black project.
by Natal Ngétal 24 Apr '19

24 Apr '19

Hi everyone, Black is project to format Python code. It's more and more used by the python community. That can save time and harmonize the code. For example, simple quote versus double quote, that was not checked by pep8.i It's just an example of what make black With a pre-hook commit hook this will be also avoid to lose time with pep8 errors. Two links to see more: https://github.com/ambv/black https://www.mattlayman.com/blog/2018/python-code-black/ I think it can be very interesting to start to use Black on OpenStack. What do you thinks about that? For example, we can introduce it on some projects, I would volunteer to try on TripleO. My best regards

21 46

[openstack-dev] [neutron] Cancelling the L3 meeting on April 24
by Miguel Lavalle 24 Apr '19

24 Apr '19

Hi Neutrinos, Since we are meeting next week in Denver to discuss, among other things, L3 topics, we are cancelling this week's meeting. Safe travels to everybody! Miguel

1 0

[nova][ptg] Draft Agenda
by Eric Fried 24 Apr '19

24 Apr '19

Nova PTGers- I have drafted an agenda at the bottom of the main etherpad [1]. It is subject to change for the next week for various reasons, but I expect mainly a) for scheduling conflicts and the like (see below) and b) things falling off because resolved (e.g. I expect the SEV spec to merge in the next couple of days). Please review the agenda, **especially if your schedule isn't "I'm present all three days, and glued to the nova team"** and contact me [2] if you: - have a scheduling conflict for a topic you own **or** a topic you care about and want to be present for. - feel I've prioritized your topic unjustly. - feel I've allocated too little or too much time [3] to your topic. - think I've committed some other glaring error or omission. Because we're short on time, I'll be strict about sticking to the schedule in whatever form it solidifies into. I've allocated some time at the end [4] to resume discussions that have to be chopped off early as a result. Thanks, efried P.S. Please be gentle with me. I've tried to be fair, accommodate scheduling issues I know about, and allocate reasonable chunks of time for topics even when I barely understand them. If I've made a mistake, assume it's out of ignorance, not malice or prejudice. [1] https://etherpad.openstack.org/p/nova-ptg-train [2] via email or IRC. Please do not edit the agenda on the etherpad. [3] seriously, including "we don't actually need to talk about this at the PTG". [4] I know it sucks that it's on Saturday afternoon; my working theory is that that's better than some topics not getting any floor time at all.

1 0

Openstack LXC
by Alejandro Ruiz Bermejo 24 Apr '19

24 Apr '19

Hi everyone, I have a fresh Openstack installation and i need to use LXC to launch instances I made the deployment manually, currently i have one controller node, one compute node, one block storage node and one object storage node. I already made the necessary configurations in the nova.conf file as appears on the official documentation site compute_driver = libvirt.LibvirtDriver [libvirt]virt_type = lxc and i have installed the nova-compute-lxc package and the nbd-server package. i created a new ubuntu 18 image for the container with the following command: openstack image create --public --container-format=bare --disk-format=raw --file bionic-server-cloudimg-amd64.tar.gz ubuntu18 and the flavor: openstack flavor create --ram 2048 --vcpus 1 --disk 5 lxc.test then when i try to launch an instance: openstack server create --flavor lxc.test --image ubuntu18 --nic net-id=d0f6cc99-565b-484f-a5ab-fcb1c3af456d --security-group 1160755e-1312-43c6-8ebb-b12b92d35e51 --key-name mykey lxc6 I get the following Error cat /var/log/nova/nova-*.log | grep 269d2480-4477-4382-b09c-9c686ab7a17c 2019-04-23 17:59:26.846 3949 INFO nova.osapi_compute.wsgi.server [req-1dbeb432-67f0-4305-b91c-6548dde49bee a16c6ef0319b4643a4ec8e56a1d025cb 59065d8f970b467aa94ef7b35f1edab5 - default default] 10.8.9.54 "GET /v2.1/servers/269d2480-4477-4382-b09c-9c686ab7a17c HTTP/1.1" status: 200 len: 1737 time: 0.6656921 2019-04-23 17:59:33.076 3944 INFO nova.api.openstack.compute.server_external_events [req-206e8ace-90e3-4a95-8274-4a9091c174c0 c2657fa5083f4d5c932d53d6bf094604 18337c70d397424f8895cd4f1ae7450e - default default] Creating event network-changed:818d6adc-252e-4d47-9275-009cff55c716 for instance 269d2480-4477-4382-b09c-9c686ab7a17c on compute 2019-04-23 17:59:37.663 3926 *ERROR* nova.scheduler.utils [req-abd32ef2-3a19-4154-a7da-893f3d2b2aef a16c6ef0319b4643a4ec8e56a1d025cb 59065d8f970b467aa94ef7b35f1edab5 - default default] [instance: 269d2480-4477-4382-b09c-9c686ab7a17c] Error from last host: compute (node compute.cujae.edu.cu): [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1841, in _do_build_and_run_instance\n filter_properties, request_spec)\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2121, in _build_and_run_instance\n instance_uuid=instance.uuid, reason=six.text_type(e))\n', u'RescheduledException: Build of instance 269d2480-4477-4382-b09c-9c686ab7a17c was re-scheduled: mount() takes exactly 4 arguments (3 given)\n'] Is this error a bug or something fixable?? Has anyone accomplished this kind of environment or used lxc without problems?

3 4

[keystone] No meeting next two weeks
by Colleen Murphy 23 Apr '19

23 Apr '19

As discussed in today's meeting[1], we'll be cancelling next week's meeting (30 April) due to the summit, as well as the following week's meeting (7 May) for recovery. Colleen [1] http://eavesdrop.openstack.org/meetings/keystone/2019/keystone.2019-04-23-1…

1 0

[Security][Security SIG] Weekly Meeting Schedule
by Gage Hugo 23 Apr '19

23 Apr '19

With the Summit/PTG next week, the Security SIG meeting for May 2nd will be cancelled due to people attending the Summit/PTG. The following week I will not be available to chair, so the meeting for May 9th will be preemptively canceled, however if there is a need for discussion, please feel free to host at the usual time. We will be back to regularly scheduled meetings again on the 16th, Safe travels everyone attending the Summit/PTG!

1 0

[Security][Security SIG] Weekly Meeting Schedule
by Gage Hugo 23 Apr '19

23 Apr '19

With the Summit/PTG next week, the Security SIG meeting for May 2nd will be cancelled due to people attending the Summit/PTG. The following week I will not be available to chair, so the meeting for May 9th will be preemptively canceled, however if there is a need for discussion, please feel free to host at the usual time. We will be back to regularly scheduled meetings again on the 16th, Safe travels everyone attending the Summit/PTG! - Gage

1 0

[dev] oslosphinx Sphinx theme is EOL
by Stephen Finucane 23 Apr '19

23 Apr '19

Just a quick pointer that the oslosphinx theme does not work with Sphinx 2.0, which was released yesterday, failing with the following error: Exception occurred: File "/home/zuul/src/git.openstack.org/openstack/nova-specs/.tox/docs/lib/python3.6/site-packages/oslosphinx/__init__.py", line 76, in builder_inited app.info('Using openstack theme from %s' % theme_dir) AttributeError: 'Sphinx' object has no attribute 'info' The oslo team have decided not to fix these issues, given that oslosphinx is EOL since Pike, and we suggest that people instead migrate to openstackdocstheme [1] (for projects that are able to use the OpenStack brand [2]) or something else (for projects that are not). For the former, I suggest follow the openstackdocstheme [1] or look at what we've done in nova-specs [3] for an existing example. If you have issues, please reach out on #openstack-doc and one of us will try our best to help you migrate. I'll work with infra to get the repo shuttered and avoid any further confusion with this theme going forward. Stephen [1] https://docs.openstack.org/openstackdocstheme/latest/ [2] https://www.openstack.org/brand [3] https://review.openstack.org/#/c/648670/

1 1

[FYI][all] PySnooper, a poor man's debugger
by Artom Lifshitz 23 Apr '19

23 Apr '19

tl;dr Instead of debugging with LOG.debug and/or print() statements all over the place, use the pysnooper decorator [1]. I came across this on Hacker News this morning - if you're like me and are too lazy to invest in learning a real debugger, and instead do it with LOG.debug/print()s all over the place, pysnooper might be useful to you. This line from the README feels particularly relevant to me ;) > What makes PySnooper stand out from all other code intelligence tools? > You can use it in your sh***y, sprawling enterprise codebase without having > to do any setup. I tried it out with a random Nova unit test by decorating the function being tested, and it gave me the expected analysis of how the function executed. Just sharing this, I hope it might be useful to someone :) [1] https://github.com/cool-RR/pysnooper

5 4

[api-sig][neutron] Question on oslo policy assertion when supplied attribute equals the default
by Nate Johnston 23 Apr '19

23 Apr '19

API SIG and Neutron communities, TL;DR ----------------------- For API requests that specify boolean attributes to the request, we check "are you allowed to specify this attribute" before we check "would specifying this argument make any difference". I am proposing to change that so users can specify things forbidden by policy as long as the attribute specified equals the default and therefore the result would be the same as if it had not been specified. Are there any security problems with that? Long-winded explanation ----------------------- I would like your opinion on the potential security impact of a change I am proposing to the Neutron mechanism for assertion of oslo.policy. In response to an operator concern I proposed a change [1] that would exempt oslo.policy checks under one specific condition: if the request specifies a boolean attribute that matches a configured default. The way Neutron is currently coded, API requests have the oslo.policy check - "are you allowed to ask for X" before anything else about the request is processed. For those not familiar with it, oslo.polcy additionally provides the ability to control arguments within that request, so that you can permit only some users to use those arguments. For example, usually permissions to create a network are pretty broad but you must me admin to create a network and specify if it will be shared. The feedback that I got was that this was frustrating for users and some operators. The distinction that we make as programmers - asserting the policy check before the processing of the request - is counterintuitive from a user perspective. The preferred behavior is to say "if supplying the argument results in the same end condition as not supplying any argument (because the argument supplied is the default anyway) then allow it". Proposed change ----------------------- The proposed change I submitted to neutron is to bypass oslo.policy checks for method arguments when all boolean method arguments equal the configured default. If any boolean arguments differ from the default, or if there are any other arguments specified that are controlled by policy, then execute the oslo.policy checks as normal. Here are a few examples: - Regular project user creates a network specifying shared=false. - Current behavior: regular user cannot specify the shared attribute, denied. - Proposed behavior: "shared=false" is the default when creating networks, so allow it. - Regular project user creates a router specifying that it be non-HA. - Current behavior: regular user cannot specify the "ha" attribute, denied. - Proposed behavior: "ha=false" is the default when creating routers, so allow it. In neutron the oslo.policy check is done in the API base [2] almost immediately upon receipt of an API request, not as a decorator in the keystone style. So comparison of supplied boolean attributes against defaults could be done at that point centrally. The Concern ----------------------- The concern raised - and what I hope to get the API SIG's guidance on - is whether this raises any kind of security concern. I don't think it will. Since we are comparing equivalence of the user supplied attribute to the default, the end result of a request permitted by this proposal should always be the same as a request where the user did not supply that argument. But your wisdom would be appreciated in validating that assumption. Thanks for your feedback, Nate [1] https://bugs.launchpad.net/neutron/+bug/1821208 [2] https://opendev.org/openstack/neutron/src/branch/master/neutron/api/v2/base…

6 9

[nova] Running multinode resize tests in the gate
by Artom Lifshitz 23 Apr '19

23 Apr '19

Yo Novans, In trying to understand why my partial fix to bug 1813789 [1] - specifically the part where reverting a resize fails because we get the network-vif-plugged event from Neutron before we start listening for it - I noticed that we don't test multinode resize (and revert) in the gate. As far as I can tell, the only place where the revert tests are run are in tempest-full-py3, and that's on an allinone single node. In order to test a theory of mine about revert resize on the same node vs source to dest and back again, I do have a DNM patch up [2] to run the resize tests in the nova-live-migration job - I think that's the only multinode tempest job we have, right? I think that job also runs evacuation tests [3], correct? So, should we just rename it nova-multinode and add resize to the list of tests it runs? [1] https://bugs.launchpad.net/nova/+bug/1813789 [2] https://review.openstack.org/#/c/653498/ [3] https://github.com/openstack/nova/blob/54d8b40471e6f7b36dbe45966c1c605f94d4…

2 2

[nova][cinder] An API to replace volume-update (aka swap-volume)
by Matthew Booth 23 Apr '19

23 Apr '19

Consider this a straw-man proposal for the upcoming cross-project discussion at PTG. I'm not (currently, at any rate) proposing to do this work myself, which is also why I haven't put this in a spec. Volume-update is a problematic interface. There are likely many more than this, but problems which come to mind are: * It shares state between cinder and nova while running. A failure of either leaves an inconsistent state which is not easily recoverable. * It is fragile: it requires an instance is running. Stopping an instance while it is in progress is undefined at best. It will fail if an instance is not running. * It is mis-used by end-users to copy data between different volumes, which results in an unsupportable strange instance state. * It is slow. * It results in data corruption for multiattached volumes I'd like to propose the following api as a replacement. I'll describe the contract up top and put some example implementations below. This new flow for volume migration would be driven entirely by cinder, with no callbacks from nova, so all of the following are new nova apis. * volume-migration-start(src_attachment_id) After returning, nova will not write any data to src until completion or cancelled. Nova will return an error if it is not able to suspend writes to src. Start is a synchronous operation. Nova will not return until it can guarantee that there will be no further writes to src. * volume-migration-cancel(src_attachment_id) Nova will resume writing to src. A subsequent complete call will return an error. cancel is an asynchronous operation. Nova assumes it can resume writing to src immediately, but does not guarantee when it will finish the cancel operation. This has no impact on cinder, but nova instance operations may continue to be restricted until the cancel completes. * volume-migration-complete(src_attachment_id, dst_attachment_id) Nova expects that dst is a copy of src at the time that volume-migration-start() was called. Nova will detach from src and attach dst in its place. Nova will resume reading and writing to dst immediately. Nova will not return until it is safe for cinder to remove src, but the complete operation is not guaranteed to have finished at this time. This has no impact on cinder, but nova instance operations may continue to be restricted until it completes asynchronously. The implementation on the cinder side would be: volume-migration-start(src_attachment_id) copy(src, dst) volume-migration-complete(src, dst) Cinder doesn't need to be concerned with whether the instance or running or not, and it always does the copy itself. Using driver-specific optimisations this has the potential to be very fast, but even the fallback implementation of a full copy between 2 arrays should be substantially faster than a qemu block job on the compute host. It is entirely up to cinder to ensure this operation is safe wrt multiattach. I expect 'safe' here to mean it will refuse to do the operation. There may also be details to be worked out wrt who creates the dst attachment. If at all possible, I don't want to expose to nova the quirk that under cinder's covers a new volume is created which temporarily has the wrong volume id. I'd prefer that, from nova's POV, the operation is just a managed switch between 2 attachments to apparently the same volume. 2 possible implementations on the Nova side: 1. Hypervisor does not support live storage migration Summary: instance must be shutdown. volume-migration-start() returns success iff the instance is shutdown. Nova will set a task state such that instance cannot be started until cancel or complete. volume-migration-complete() reconfigures the specific volume attachment and unsets the task state so the instance can be started. 2. libvirt driver Summary: libvirt allows writes to continue during the copy by sending them to a local snapshot, which it commits to dst on complete(). volume-migration-start() sets task state such that instance cannot be started or stopped until cancel or completion. If instance is not running, does nothing else. If instance is running, creates local writeable qcow2 backed by read-only src volume. Swaps volume to local qcow2. volume-migration-cancel() does nothing if instance is not running except unset task state. If instance is running returns success to cinder immediately before commiting qcow2 to src volume and then unsetting task state. volume-migration-complete() updates instance to dst if it's not running, unsets task state and returns immediately. If instance is running, rebases local qcow2 from src to dst (cinder guarantees us that these are identical), then returns success to cinder because src can now be released. Nova starts a job to commit qcow2 to dst. On completion it updates instance to use dst and unsets task state. This API does not handle the case where the hypervisor is only capable of live storage migration where it manages the entire copy itself. If we had a requirement to support this we might change volume-migration-start() to return something indicating that nova will do the copy, or perhaps indicating that cinder should try again with a different entry point. However, I believe this approach will always be slower than a cinder-native copy, and I can't see any way around it requiring a callback to cinder on completion of the copy. I'd very much like some feedback from non-libvirt hypervisor folks around whether they're interested in this functionality at all, and if so what their capabilities are. Matt -- Matthew Booth Red Hat OpenStack Engineer, Compute DFG Phone: +442070094448 (UK)

2 3

Scuba Diving at the Denver Summit
by Monty Taylor 23 Apr '19

23 Apr '19

Hey everybody! tl;dr - Let me know if you'd like to go diving in the Rocky Mountains. Of all of the places we've had a Summit where one might reasonably expect there to be a possibility of Scuba Diving, the Denver Summit is probably REALLY low on the list. But it turns out that there is a Dive Shop that does dives at the Denver Aquarium [0] (with all the fish and sharks and whatnot) The Denver Aquarium is also very close to the Convention Center. I'm going to see about putting together a private group dive event for those of us who think that sounds like a fun idea. Due to cross-contamination concerns for the health and safety of the fish, the dive shop provides all equipment - so you don't have to bring gear. They will allow bringing your own mask - and I'm assuming if a well-scrubbed mask is ok then a well-scrubbed dive computer would be ok - but I'll be checking with them when I call to arrange things. If you are Open Water certified and would like to join, please send me a response back (reply directly to me rather than the list is fine) so I can judge general interest level when talking to the lovely humans. If you are **NOT** Open Water certified but are thinking to yourself "wow, that sounds like fun" - the dive shop does certification dives at the aquarium on the weekends. That's a bit out of scope for me to arrange, but if you want to show up in Denver early and do an Open Water class then join us, that's awesome. You can also get certified at home before coming ... but you'll need an Open Water certification to join us. BUT WAIT - THERE'S MORE! There is another interesting diving opportunity in the general Mountain West area - although not immediately **close** to Denver - that Sandy and I are going to be going to before the Summit - Homestead Crater. We're arranging to meet a Scuba instructor there to do our second Altitude cert dive, and also to do a 2-dive "Hot Springs Diver" specialty. We'd be happy to have folks join us. Homestead Crater [1] is outside of Salt Lake City. It's a hot spring - the water is 96F/35.5C and it's also an altitude dive. If people are interested, we can meet at the crater on Thursday morning pre-summit, dive the crater, then drive to Denver on Friday/Saturday. ** If only a small number of people are interested in any of this - we'll likely just do the Denver dives the weekend before during one of the normally scheduled dive times instead of arranging a group outing, and shift Homestead, if anyone is interested, a few days earlier ** I will not have space enough in my car to get you from the crater to Denver, so if you want to fly in to SLC ahead of time and meet there, awesome. Unlike Denver, the crater will require you have equipment, including scuba tanks. For anyone interested in coming, there are dive shops in Salt Lake where you can rent gear. There is a dive shop at the crater to do air fills. Anyway - if anyone is interested in some or all of these things, let me know this week so I can get a headcount and then we can talk more off-list about logistics and figure out how to deal with things for people coming from far off (carpools, equipment, etc) Monty PS. If any of you aren't already using Subsurface for dive logging, I'll be happy to help you get set up. [0] https://divedowntown.com/ [1] https://homesteadresort.com/utah-resort-things-to-do/homestead-crater/

4 5

[magnum] kubernests cinder deploying wordpress
by Ionut Biru 23 Apr '19

23 Apr '19

Hello, I'm trying to deploy a simple wordpress installation following the documentation from kubernets. https://kubernetes.io/docs/tutorials/stateful-application/mysql-wordpress-p… kubernets was deployed using magnum on openstack rocky using the following template: https://paste.xinu.at/sRk/ Then i'm using the cinder storage class that is described in kubernets documentation: https://kubernetes.io/docs/concepts/storage/storage-classes/#openstack-cind… and I also made it default. I did the following test: cinder volume created before hand and used in pod directly with the id, the volume is attached and mounted correctly like is described here: https://docs.openstack.org/magnum/latest/user/#storage Now if I try to deploy wordpress using the first link or other helms that use volume claim, the volume is created automatically by kubernets but they are never attached or mounted to the instances. On master I see the following error: pv_protection_controller.go:116] PV pvc-48fed935-5b61-11e9-9901-fa163e5ebeae failed with : Operation cannot be fulfilled on persistentvolumes "pvc-48fed935-5b61-11e9-9901-fa163e5ebea> the object has been modified; please apply your changes to the latest version and try again Is there something I miss? I'm using the wrong version of fedora-atomic? It's the latest version available for download. I did find that someone else had this error but not with cinder: https://github.com/kubernetes/kubernetes/issues/72905

1 1

[octavia][openstack-ansible] network layout example
by Ionut Biru 23 Apr '19

23 Apr '19

Hello guys, I have hard time understanding how to create the right layout infrastructure of octavia. Does anyone have octavia running in production with OSA? For now I have created a new tagged interface. Is this the right approach? auto bond0.40 iface bond0.40 inet manual vlan-raw-device bond0 auto br-lbaas iface br-lbaas inet manual bridge_stp off bridge_waitport 0 bridge_fd 0 pre-up ip link add br-lbaas-veth type veth peer name eth14 || true pre-up ip link set br-lbaas-veth up pre-up ip link set eth14 up post-down ip link del br-lbaas-veth || true bridge_ports bond0.40 br-lbaas-veth

1 0

[Third Party CI][Cinder] Changes from review.openstack.org to review.opedev.org
by Sean McGinnis 23 Apr '19

23 Apr '19

Attention operators of third party CI. It may have been easy to miss some of the changes that have been done last week to migrate from our Gerrit instance from review.openstack.org to review.opendev.org. For a lot of things, this should be seamless as there are pretty robust HHTP(s) redirects in place, making it easy to not even notice right away that things have changed. One thing that may impact third party CI operators though, is there is no way to automatically redirect SSH traffic. http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005423.ht… I think many CI systems SSH in and watch the event stream with something like: >> ssh -p 24198 review.openstack.org gerrit stream-events That will now fail with the move to opendev.org. Please make sure your CI configuration is updated to change that to review.opendev.org to continue to capture the event stream for triggering job execution. Thanks! Sean

3 3

[Glance] Weekly meetings
by Erno Kuvaja 23 Apr '19

23 Apr '19

Hi all, It's the Summit/PTG disruptions again. So This week Glance will be having weekly meeting normally at Thu (25th) 14:00, next week we will be having our meeting face to face in Denver so IRC will be quiet, the week after Summit, I might not be available to chair meeting if one is needed but I'll see if Abhishek or Brian can cover me. From Thu 16th of May you can again expect business as usual from us. Best, Erno

1 0

[Watcher] tomorrows meeting and agenda
by info＠dantalion.nl 23 Apr '19

23 Apr '19

Hello everyone, Tomorrow Watcher will have a meeting again at 08:00 UTC in the #openstack-meeting-alt channel. This is a reminder since we only recently started to have meetings again. The agenda is available on https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda feel free to add any additional items. Kind Regards, Corne Lukken (Dantali0n)

1 0

Re: [Release-job-failures] Release of openstack/solum failed
by Thierry Carrez 23 Apr '19

23 Apr '19

zuul(a)openstack.org wrote: > Build failed. > > - release-openstack-python http://logs.openstack.org/19/19a7574237f44807b16c37e0983223ff57340ba3/relea… : POST_FAILURE in 4m 40s > - announce-release announce-release : SKIPPED > - propose-update-constraints propose-update-constraints : SKIPPED Solum release post-job (triggered by stable/pike 5.4.1 tagging) failed with the following error: Ensure twine is installed: [ "python3", "-m", "pip", "install", "twine!=1.12.0", "readme_renderer[md]!=23.0", "requests-toolbelt!=0.9.0", "--user" ] Can not perform a '--user' install. User site-packages are not visible in this virtualenv. http://logs.openstack.org/19/19a7574237f44807b16c37e0983223ff57340ba3/relea… This seems to be a new error hitting us recently (also happened for networking-arista, which the release management team does not directly handle). It is weird since the job (exact same command) worked in subsequent runs: http://logs.openstack.org/d0/d0d2089455efb6d01a1158bad597f42cf2306c30/relea… -- Thierry Carrez (ttx)

1 1

[release-openstack-python][release pipeline] POST_FAILURE since last couple of hours, already known and being fixed?
by Yatin Karel 23 Apr '19

23 Apr '19

Hi all, release-openstack-python[1] job is failing since last couple of hours, is this already known and worked upon? If it's not being fixed yet good to hold other releases until it's fixed. The job failing at ansible task: ensure-twine : Ensure twine is installed with Error:- Can not perform a '--user' install. User site-packages are not visible in this virtualenv. Example log:- http://logs.openstack.org/c0/c09c5676b549b6705e7286ee6d1d7e000b9e756f/relea… Actually i tried to reach via IRC at #openstack-release but seems release team in other time zone, posting on mailing list so it can be followed up. Noticed the issue when found tarballs missing when building the released projects in RDO [2]. [1] http://zuul.openstack.org/builds?job_name=release-openstack-python [2] https://logs.rdoproject.org/97/20397/1/check/distgit-cbs-validate/7bd5d70/j… Thanks and Regards Yatin Karel

2 1

[Neutron][TripleO] Avoid dangling sidecars containers - add hook support
by Cédric Jeanneret 23 Apr '19

23 Apr '19

Dear List, While doing some validations on an "in-use" node, we detected a container being Exited with status 137. After some researches and discussions, it appears this container is launched from a Neutron container, as a sidecar, and then the service is killed: https://github.com/openstack/neutron/blob/master/neutron/agent/linux/extern… While the "kill" is fine outside of a container, it leads to some issues in a containerized world: - dangling container is here, with a failed state - validating container state is therefore complicated - might lead to false assumption if we don't know that "kill" process - might lead to disk space issues In order to sort that bad situation out, and prevent disk space issues and the like, I propose to discuss about some "hook" addition in that "external_process.py" (or wherever is more suited for that usage) There is apparently something like that for the service launch, since there are wrapper scripts in /var/lib/neutron. In my idea, that wrapper script could generate a new wrapper used in order to actually delete the container (instead of kill -9 <pid>). The neutron code could be modified in a simple way, something like: ############### if os.path.exists(<wrapper-file>): utils.execute(['bash', <wrapper-file>]) else: # current way to handle things ############### The <wrapper-file> might have "something" in its name in order to ensure we're actually killing the right process/container. self.pid, or maybe some specific string that neutron is aware of... you get the idea. Even outside of a container, that might be used in order to clean temporary configurations/files, and ensure we're actually facing a clean environment. It's really something more like "hooks" than "container-centric thingy" Would you consider that kind of new feature? Thank you for your time and consideration! Cheers, C. -- Cédric Jeanneret Software Engineer DFG:DF

2 2

vm missing psi-passthrough device if cpu pinning is in place
by Manuel Sopena Ballesteros 23 Apr '19

23 Apr '19

Dear Openstack community, I am trying to setup a vm with bith pci-passthrough and cpu pinning. This is my flavor: [root@openstack-deployment ~]# openstack flavor show kudu.test.dedicated.tiny +----------------------------+--------------------------------------------------------------+ | Field | Value | +----------------------------+--------------------------------------------------------------+ | OS-FLV-DISABLED:disabled | False | | OS-FLV-EXT-DATA:ephemeral | 0 | | access_project_ids | None | | disk | 10 | | id | 7e241e94-1c50-4a92-9ce6-8abb272d79d8 | | name | kudu.test.dedicated.tiny | | os-flavor-access:is_public | True | | properties | hw:cpu_policy='dedicated', hw:pci_passthrough:alias='nvme:1' | | ram | 4096 | | rxtx_factor | 1.0 | | swap | | | vcpus | 2 | +----------------------------+--------------------------------------------------------------+ And this is how I create the vm: [root@openstack-deployment ~]# openstack server create --flavor kudu.test.dedicated.tiny --image centos7.5-image --nic net-id=hpc --security-group admin --key-name mykey --availability-zone nova:zeus-53.localdomain kudu-test-3-1 The problem is that the vm does not have the nvme pci device attached to it. [root@zeus-53 test]# docker exec -it nova_libvirt virsh dumpxml instance-000000ad <domain type='kvm' id='9'> <name>instance-000000ad</name> <uuid>5d8f6cc1-e716-4f4d-ac55-df24d4cffd38</uuid> <metadata> <nova:instance xmlns:nova="http://openstack.org/xmlns/libvirt/nova/1.0"> <nova:package version="18.2.0-1.el7"/> <nova:name>kudu-test-3-1</nova:name> <nova:creationTime>2019-04-17 05:17:02</nova:creationTime> <nova:flavor name="kudu.test.dedicated.tiny"> <nova:memory>4096</nova:memory> <nova:disk>10</nova:disk> <nova:swap>0</nova:swap> <nova:ephemeral>0</nova:ephemeral> <nova:vcpus>2</nova:vcpus> </nova:flavor> <nova:owner> <nova:user uuid="91e83343e9834c8ba0172ff369c8acac">admin</nova:user> <nova:project uuid="b91520cff5bd45c59a8de07c38641582">admin</nova:project> </nova:owner> <nova:root type="image" uuid="5ec18792-05f2-4bce-b5d8-cb3480cbb35a"/> </nova:instance> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <vcpu placement='static'>2</vcpu> <cputune> <shares>2048</shares> <vcpupin vcpu='0' cpuset='9'/> <vcpupin vcpu='1' cpuset='37'/> <emulatorpin cpuset='9,37'/> </cputune> <numatune> <memory mode='strict' nodeset='0'/> <memnode cellid='0' mode='strict' nodeset='0'/> </numatune> <resource> <partition>/machine</partition> </resource> <sysinfo type='smbios'> <system> <entry name='manufacturer'>RDO</entry> <entry name='product'>OpenStack Compute</entry> <entry name='version'>18.2.0-1.el7</entry> <entry name='serial'>00000000-0000-0000-0000-0cc47aa482cc</entry> <entry name='uuid'>5d8f6cc1-e716-4f4d-ac55-df24d4cffd38</entry> <entry name='family'>Virtual Machine</entry> </system> </sysinfo> <os> <type arch='x86_64' machine='pc-i440fx-rhel7.6.0'>hvm</type> <boot dev='hd'/> <smbios mode='sysinfo'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>Skylake-Client-IBRS</model> <vendor>Intel</vendor> <topology sockets='1' cores='1' threads='2'/> <feature policy='require' name='ss'/> <feature policy='require' name='hypervisor'/> <feature policy='require' name='tsc_adjust'/> <feature policy='require' name='stibp'/> <feature policy='require' name='ssbd'/> <feature policy='require' name='pdpe1gb'/> <feature policy='disable' name='mpx'/> <feature policy='disable' name='xsavec'/> <feature policy='disable' name='xgetbv1'/> <numa> <cell id='0' cpus='0-1' memory='4194304' unit='KiB'/> </numa> </cpu> <clock offset='utc'> <timer name='pit' tickpolicy='delay'/> <timer name='rtc' tickpolicy='catchup'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/libexec/qemu-kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none'/> <source file='/var/lib/nova/instances/5d8f6cc1-e716-4f4d-ac55-df24d4cffd38/disk'/> <backingStore type='file' index='1'> <format type='raw'/> <source file='/var/lib/nova/instances/_base/4cc6eebe175e35178cb81853818a1eb103cea937'/> <backingStore/> </backingStore> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <controller type='usb' index='0' model='piix3-uhci'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <interface type='bridge'> <mac address='fa:16:3e:45:ba:a1'/> <source bridge='qbr2a0abb35-29'/> <target dev='tap2a0abb35-29'/> <model type='virtio'/> <mtu size='1500'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/14'/> <log file='/var/lib/nova/instances/5d8f6cc1-e716-4f4d-ac55-df24d4cffd38/console.log' append='off'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/14'> <source path='/dev/pts/14'/> <log file='/var/lib/nova/instances/5d8f6cc1-e716-4f4d-ac55-df24d4cffd38/console.log' append='off'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <graphics type='vnc' port='5901' autoport='yes' listen='192.168.1.53'> <listen type='address' address='192.168.1.53'/> </graphics> <video> <model type='cirrus' vram='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <stats period='10'/> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+42436:+42436</label> <imagelabel>+42436:+42436</imagelabel> </seclabel> </domain> However I do can see the nvme if I use a flavor without cpu pinning. Has anyone seen this before? Thank you NOTICE Please consider the environment before printing this email. This message and any attachments are intended for the addressee named and may contain legally privileged/confidential/copyright information. If you are not the intended recipient, you should not read, use, disclose, copy or distribute this communication. If you have received this message in error please notify us at once by return email and then delete both messages. We accept no liability for the distribution of viruses or similar in electronic communications. This notice should not be removed.

1 0

[Tripleo][Octavia][OVN] Overcloud deployment Issues with Octavia
by Rabi Mishra 23 Apr '19

23 Apr '19

Hi All, For some Octavia testing with heat, I tried deploying 3+1 node overcloud with Octavia environment and THT master. As expected, deployment finished successfully. However, when trying to do some Octavia API calls (ex. list laodbalancers etc), it was returning (503) Service Unavailable error. Checking the logs of octavia_api container (though the container was running), it was in a continous loop. I have captured some of these issues (as described below) in https://bugs.launchpad.net/tripleo/+bug/1825146 too. The intent of this mail is to bring it to the notice of the respective teams and understand the best possible way to fix these. 1. Incorrect config setting for provider_drivers. As of https://github.com/openstack/puppet-tripleo/commit/97c46ca76803fb238279d245…, we added OVN provider driver support for Octavia. However, the config option seems to be set incorrectly which resulted in octavia-api failing to start. 2. ovn_nb_connection not in octavia config It seems ovn provider driver (part of networking-ovn) connects to ovn nb database as part of initialization. However, we don't seem to configure connection string in octavia.conf and it tries to connect to 127.0.0.1 and fails. I've already proposed a few patches[1] to fix the above two issues. 3. Missing Octavia Driver Agent Octavia had added a driver-agent controller process in Stein (for provider drivers to communicate with the octavia for status and stats update). This process is expected to be collocated with octavia-api and creates a pair of unix domain sockets for communication that the drivers use. We don't seem to have this implemented in THT yet. Is this something planned and someone working on it? AFAICT, we can't enable/use the OVN provider driver without adding this service/container? Adding support for this in THT also seems little complex and probably can be done in few different ways. Is there a standard design pattern we use for these kind of requirements in Tripleo? If we already have an agreed plan on how to do it, please ignore below. I can only think of the few options below. Probably there are better ones too:) a. New OctivaDriverAgent Service. As the process is expected to be co-llocated with octavia-api to share the domain sockets (we can share /var/run/octavia from host on both containers), I'm not sure if this would be a good design though. b. As a sidecar of octavia_api Not a new service, but as a sidecar container for octavia-api (started when api starts, do we've something like this already there for other services?). Ideas/comments welcome:) [1] https://review.opendev.org/#/q/status:open+branch:master+topic:bug/1825146 -- Regards, Rabi Mishra

2 1

[Tacker] Weekly meeting and vPTG
by Dharmendra Kushwaha 23 Apr '19

23 Apr '19

Hi Team, Due to the summit, most of members busy in travel things, so canceling today's and next week IRC meeting. We will resume Tacker weekly meeting on 7th May. Due to U.S. visa issue, I am not able to travel this time, so as we agreed to cancel physical PTG, and will finalize vPTG schedule in weekly meeting of 7th May. I Will be available on Tacker channel, feel free to ping me for any discussion. Thanks & Regards Dharmendra Kushwaha

1 0

[oslo] No meeting next two weeks
by Ben Nemec 22 Apr '19

22 Apr '19

God dag, Norsk. As discussed in the meeting this morning, there will be no Oslo meeting for the next two weeks (Apr. 29 and May 6). The former is during Summit, and the latter will be the first work day after the PTG. As always, if anything comes up during that time you don't have to wait for a meeting to bring it to our attention. The mailing list is always open. -Ben

1 0

OpenStack Hound code search with OpenDev repos
by Boden Russell 22 Apr '19

22 Apr '19

Maybe I missed this, but are there some changes necessary for the OpenStack Hound (code search) service [1] to work with OpenDev git repos? As of right now Hound [1] doesn't seem to be finding any repos; click the "Advanced" option and see the empty list of repos. Thanks [1] http://codesearch.openstack.org/

3 2

[tripleo] Summit / PTG link
by Emilien Macchi 22 Apr '19

22 Apr '19

All (or almost) what you need to know about TripleO at Open Infra summit & PTG: I created a Google Calendar for TripleO related sessions (including PTG): web format: https://calendar.google.com/calendar/embed?src=es78vnjv5galctjgo1vsi3d7bo%4… ical format: https://calendar.google.com/calendar/ical/es78vnjv5galctjgo1vsi3d7bo%40grou… Our PTG etherpads are here (topics + agenda) https://etherpad.openstack.org/p/tripleo-train-topics https://etherpad.openstack.org/p/tripleo-ptg-train Don't miss the team picture on Thursday, 11am. Safe travels, and see you next week! -- Emilien Macchi

1 0

[placement][nova][ptg] Resourceless trait filters
by Chris Dent 22 Apr '19

22 Apr '19

>From the etherpad [1] (the cross project one): * This came up with the effort to add a multiattach capability filter, at https://review.openstack.org/#/c/645316/1/nova/compute/api.py@1098 * The problem: we want to be able to request allocation candidates filtered by a trait that exists on the root provider; but * (a) the root provider may provide no resources (eventually - e.g. CPU/mem in NUMA providers, shared disk); and/or * (My brain hurts from the concept for a provider that provides nothing. Perhaps it provides something we aren't remembering to count?) * (b) we are using only numbered groups and would have to guess where to stuff the `required` - again probably based on looking for the VCPU/mem resources, which, as above, may wind up not on the root provider. This, basically, is how/when do we deal with resource providers that have traits but have no classes of inventory of their own (all of it is on their descendants). The "My brain hurts" comment above is mine. The discussion on the review above (good backgrounder for this thread) had little to do with the immediate need of the proposed feature. It was a concern about how things will work in the future. So there are two salient questions (and presumably plenty of other sidebars): * How should it work? * What is the timeline for when it needs to work? [1] https://etherpad.openstack.org/p/ptg-train-xproj-nova-placement -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

6 19

Diversity Events
by Amy Marrich 22 Apr '19

22 Apr '19

Summit is a week away and I wanted to point out a few Diversity related sessions and events taking place. Thanks, Amy (spotz) 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: 12:20-1:40 - Diversity Networking Lunch sponsored by IBM - RSVP required https://www.openstack.org/summit/denver-2019/summit-schedule/events/23756/r… 1:40-2:20 - The Results are in for the D&I Survey. This is a first review of the data collected. https://www.openstack.org/summit/denver-2019/summit-schedule/events/23692/t… 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… 11:40-12:20 - Diversity and Inclusion WG https://www.openstack.org/summit/denver-2019/summit-schedule/events/23746/d…

1 1

Call for help! 'U' Release name Mandarin speakers
by Tony Breeds 22 Apr '19

22 Apr '19

Hello folks, Now that we know when and where the 'U' summit will be[1] we can pick the name for the U release. I'm happy to act as coordinator but given the location I'd really like a native speaker (or 2) to help with assessing the names against the criteria, defining the geographic region and translating the civs POLL when we get there. Yours Tony. [1] https://www.openstack.org/summit/shanghai-2019

9 13

[cinder] Proposing Brian Rosmaita for Core ...
by Jay Bryant 22 Apr '19

22 Apr '19

Team, I would like to propose Brian Rosmaita for Cinder core. His participation in Cinder has been steadily increasing during the Stein release. He attended the mid-cycle meeting in Raleigh and was able to provide great insight and input using his experience from Glance. His review activity has been consistent during Stein. He has helped get backports to our stable branches and subsequently has ensured that we do timely releases of Cinder's components. Considering the broad range of activity Brian has demonstrated and his years of experience in OpenStack I think he will serve as an excellent addition to our core team. If I do not hear any concerns with this nomination I will make Brian core on 4/24. Thank you! Jay

9 9

[dev][cinder][stable-maint] python-cinderclient
by Brian Rosmaita 22 Apr '19

22 Apr '19

At last week's Cinder weekly meeting, we discussed 3 patches to master that should be merged and then backported to stable/stein and stable/rocky (fixes for the "cinderclient can communicate with higher microversions than it thinks it can" bug). These patches still require approval (can be approved by any cinder core): * https://review.opendev.org/#/c/653473/ * https://review.opendev.org/#/c/653472/ * https://review.opendev.org/#/c/653471/ After those are approved, all 3 will need to be backported to stable/stein, and then the stein backport of https://review.opendev.org/#/c/653471/ will need to be backported to stable/rocky. cheers, brian

1 0

[neutron] Bug deputy report - April 15 - 21
by Hongbin Lu 22 Apr '19

22 Apr '19

Hi, I was on bug deputy last week. Below is my bug deputy report: Confirmed bugs: * https://bugs.launchpad.net/neutron/+bug/1824788 installed neutron, but no provider network exists * https://bugs.launchpad.net/neutron/+bug/1824799 neutron dhcp agent looks for external pid unexpectedly * https://bugs.launchpad.net/neutron/+bug/1824802 dhcp agent dnsmasq process mgmt race condition between launch and operations (Important: HIGH) * https://bugs.launchpad.net/neutron/+bug/1824911 [scale issue] the bottleneck lock will multiply increase processing time of agent resources * https://bugs.launchpad.net/neutron/+bug/1825088 [port forwarding] should not process port forwarding if snat node only run DHCP * https://bugs.launchpad.net/neutron/+bug/1825152 [scale issue] the root rootwrap deamon causes l3 agent router procssing very very slow * https://bugs.launchpad.net/neutron/+bug/1825205 when the last vm of a network in a compute is live-migrated with DVR enable, the qrouter namespace is not deleted * https://bugs.launchpad.net/neutron/+bug/1825291 TypeError: unhashable type: 'dict' in neutron-vpnaas while deleting routers * https://bugs.launchpad.net/neutron/+bug/1825456 [VPNaaS] Add missing unit test for vpn agent RFEs: * https://bugs.launchpad.net/neutron/+bug/1824856 [RFE] Add new state "ERROR" for HA routers * https://bugs.launchpad.net/neutron/+bug/1825336 [RFE] Tag based policy * https://bugs.launchpad.net/neutron/+bug/1825345 [RFE] admin-state-down doesn't evacuate bindings in the dhcp_agent_id column Invalid: * https://bugs.launchpad.net/neutron/+bug/1824988 updating multisegment network segmentation id does not raise error and although the update succeeds it doesn't work * https://bugs.launchpad.net/neutron/+bug/1825295 The openflow won't be deleted when we reboot and migrate the instance Duplicated: * https://bugs.launchpad.net/neutron/+bug/1825147 ovs flooding packets, not learning MAC addresses Best regards, Hongbin

1 0

[kuryr] No meetings today nor next week
by Daniel Mellado 22 Apr '19

22 Apr '19

Hi Kuryrs, We're canceling today's meeting due to Easter and next one due to the Open Infrastructure Summit being held. Should you need anything feel free to reach out to us at #openstack-kuryr. Happy Easter! Daniel

1 0

Re: [Release-job-failures] Release of openstack/puppet-tripleo failed
by Emilien Macchi 22 Apr '19

22 Apr '19

fixed by https://review.openstack.org/#/c/653796/ and https://review.openstack.org/#/c/653795/ On Thu, Apr 18, 2019 at 11:04 AM <zuul(a)openstack.org> wrote: > Build failed. > > - release-openstack-puppet > http://logs.openstack.org/75/75c09955854b142fd08c843bebcb8ee90d951b4d/relea… > : POST_FAILURE in 3m 18s > - announce-release announce-release : SKIPPED > > _______________________________________________ > Release-job-failures mailing list > Release-job-failures(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures > -- Emilien Macchi

2 2

[searchlight] Next 2 meetings cancelled
by Trinh Nguyen 22 Apr '19

22 Apr '19

Hi team, We will cancel the next 2 meetings (today and 6 May) to prepare for Denver summit and vacation after that. I'll be on IRC most of the time so please ping me there. Yours, -- *Trinh Nguyen* *www.edlab.xyz <https://www.edlab.xyz>*

1 0

[vitrage] The next two IRC meetings are canceled
by Ifat Afek 22 Apr '19

22 Apr '19

Hi, The next two IRC meetings are canceled. This week most of Vitrage contributors are on vacation, and next week we have the summit. We will meet again on Wednesday, May 8th. Br, Ifat

1 0

[neutron] Cancelling performance sub-team meeting
by Miguel Lavalle 22 Apr '19

22 Apr '19

Hi Neutrinos, Some members of this sub-team are on vacation / holiday on the 22nd. Besides, we are going to discuss Neutron performance and scalability in Denver. As a consequence, we will cancel the meeting. Best regards Miguel

1 0

Post OpenDev Repo Migration Issues
by Clark Boylan 21 Apr '19

21 Apr '19

Hello, There are two quick things we want to point out that we've noticed after the OpenDev Gerrit manuevers. First, any commit Depends-On footers for unmerged changes will need to use https://review.opendev.org urls instead of https://review.openstack.org urls. This is due to a limitation in Zuul and how it sees the Gerrit server. Any Depends-On footers that use https://review.openstack.org are currently non-functional and they will not enforce the dependency relationship. Second, while we have fairly robust http(s) redirects in place for old urls (including those from cgit to gitea) any ssh repo urls will need to be updated to use the new canonical paths if a repo has moved. We are unable to redirect incoming ssh requests against Gerrit. If you need to know what the canonical path is go to the corresponding https repo url and the resulting destination is the canonical location. Again thank you for your patience, Clark

3 3

[placement][nova][ptg] Shared resource providers for shared disk on compute hosts
by Chris Dent 21 Apr '19

21 Apr '19

This topic is from the cross project etherpad [1] There's a spec in progress for this: https://review.openstack.org/#/c/650188/ It does a pretty good job of explaining some of the corner cases. We need to make sure we have a good awareness of all the corners because when we try to do (or even think about) this feature we discover a problem that derails the work. Which is unfortunate because supporting shared disk is one of the principles on which placement was sold. All the necessary functionality is already there in placement, so making it work is mostly on the nova side, a lot of it in nova-compute. Much of the challenge is associated with dealing with move operations. A question I posed on the spec is whether it is possible to make this happen without having to rely on additional config. It seems like something where it would be super nice (but perhaps not possible) for a virtdriver to be able to turn on and manage itself. So the discussion surrounding this topic is perhaps around: * teasing out the dark corners as much as possible so we don't stumble again * nailing the issues with moves * exploring the options for making it as hands-free as possible [1] https://etherpad.openstack.org/p/ptg-train-xproj-nova-placement -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

2 1

[dev] Queries regarding migration through Openstack
by Priyanka Sangtani 21 Apr '19

21 Apr '19

Hi All, I'm currently working on a project which requires me to understand the live migration and cold migration process in Openstack. I have the following questions: 1. In case of live migration with shared storage, how is the current downtime set through update_downtime used? Like when does it know that it needs to pause the VM on the source and perform the stop and copy phase? It would be great if you could point me to the code base where this is happening. Is this handled by QEMU? 2. In case of cold migrate, how does it select the destination host? As per the code, I saw that it generates a sorted list of hosts based on filtering and weighing but then we also perform randomization. I'm confused as to how this works. Thank you so much for your time. Regards, Priyanka

1 0

[nova] - Stack VMs based on RAM
by Georgios Dimitrakakis 21 Apr '19

21 Apr '19

All, in the past I used to stack VMs based on RAM on hosts by putting the following settings in my nova.conf file: ->ram_weight_multiplier=-1.0 ->available_filters=nova.scheduler.filters.all_filters ->enabled_filters=RetryFilter,AvailabilityZoneFilter,CoreFilter,RamFilter,ComputeFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter,ServerGroupAntiAffinityFilter,ServerGroupAffinityFilter I have now a Rocky installation and although I have set the above on my controller node and restarted corresponding services the result when spawning two VMs (one after another) is still to be distributed on two different hosts. Seems that the something is missing in order to override the default behavior. Any suggestions please? Best regards, G.

4 26

[tc] project-update exception for 654057
by Mohammed Naser 21 Apr '19

21 Apr '19

Hi everyone: As chair, I'm making an exception to the usual timeline for the project-update housekeeping rules for change #654057 based on the following reasons: - This has no governing change, the only change is pointing to the correct deliverable repository as part of this. - The reasonable possible objection is the prefix/rename of a repository, however, this is already done. If there is any concerns about any specific renames, we can work with infra. to rename them and update the projects.yaml afterwards. - This helps unblock the (hard working) infrastructure team at cleaning up their work. It is impacting our openstack/openstack submodules repo. If anyone has any objects, you're free to propose a full (or partial) revert with your concerns. Have a good weekend! Regards, Mohammed -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

1 0

[qa][zun][kuryr][k8s]
by Hongbin Lu 20 Apr '19

20 Apr '19

Hi all, Right now, we have a devstack plugin [1] to install container engine (i.e. docker, cri-o). The plugin is currently used by Zun and Kuryr and under the governance of QA team. I am working on a patch [2] to enable k8s installation via devstack. Zun needs this feature to setup the CI for the virtual kubelet provider, and I heard Kuryr also interest to leverage it. The original idea is to incorporate k8s installation into devstack-plugin-container, so that we can avoid the overhead to bootstrap and maintain a separated plugin. However, the feedback I received so far gave preference to a separated plugin for k8s, so I sent out this email to collect more opinions. Do you prefer a dedicated devstack plugin for k8s, or is fine to reuse the existing container plugin for this purpose? [1] https://github.com/openstack/devstack-plugin-container [2] https://review.openstack.org/#/c/646018/ Best regards, Hongbin

3 3

https://review.openstack.org is down?
by Arkady.Kanevsky＠dell.com 20 Apr '19

20 Apr '19

5 5

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

20 Apr '19

# Keystone Team Update - Week of 15 April 2019 ## News This week has been mostly about Forum and PTG preparation. Please review the PTG agenda[1] and come prepared to discuss the proposed topics. According to the team dinner poll[2] it looks like Wednesday is the best day for us to go out as a team, so I will find somewhere to make a reservation for the ~8 of us. [1] https://etherpad.openstack.org/p/keystone-train-ptg [2] https://framadate.org/BHNNU9S3f9N3lasH ## Open Specs Train specs: https://bit.ly/2uZ2tRl Ongoing specs: https://bit.ly/2OyDLTh I would like to start prioritizing and committing to these specs soon after the PTG so please review the proposals and/or prepare and update your own proposals for this cycle. If a spec is proposed under ongoing/ but it should be completed this cycle, please repropose it under train/. ## Recently Merged Changes Search query: https://bit.ly/2pquOwT Gerrit is under maintenance right now so I don't have stats at the moment ;) ## Changes that need Attention Search query: https://bit.ly/2tymTje Same here. ## Bugs This week we opened 2 new bugs and closed none. At first glance the two new bugs appear to be issues with the new Stein packages on Ubuntu. Bug #1825111 (keystone:Undecided) opened by Robert Holling https://bugs.launchpad.net/keystone/+bug/1825111 Bug #1825214 (keystone:Undecided) opened by Joseph Beale https://bugs.launchpad.net/keystone/+bug/1825214 ## Milestone Outlook https://releases.openstack.org/train/schedule.html ## Help with this newsletter Help contribute to this newsletter by editing the etherpad: https://etherpad.openstack.org/p/keystone-team-newsletter

1 0

[stackalytics] Moving stackalytics configuration file to github repo
by Sergey Nikitin 20 Apr '19

20 Apr '19

Hello everyone, Every day Stackalytics team works on new features. One of these features is a statistics collecting for non OpenStack projects. For example Kubernetes [1]. Stackalytics project has configuration file (default_data.json), which contains a lot of data, including user properties. Such as name, launchpad ID, github ID, email and companies. It's a usual situation when a contributor change his/her email or find a better job in new company. To do not loose stats which were pinned with old email or to point that he/she now work in new company contributor must add/modify his/her record in default_data.json config file. This config file was in `etc` directory in stackalytics repo [2]. But we moved this file to new github repository [3]. It was made to do not force non OpenStack contributors use OpenStack Gerrit to update their stackalytics profiles. >From this moment if you want to update your stackalytics profile you must create a pull request to the new github repo [3]. The new data will be applied within 12 hours after pull request merge. All current patches with user data changes from stackalytics gerrit [4] are still valid and will be applied and moved to [3] after approve. So do not worry about them. More information about user data updating you can find in Stackalytics Wiki page [5]. If you have any questions we will be glad to answer. Stackalytics team. [1] https://www.stackalytics.com/cncf?project_type=kubernetes [2] https://github.com/openstack/stackalytics/blob/master/etc/default_data.json [3] https://github.com/stackalytics/default_data [4] https://review.openstack.org/#/q/project:openstack/stackalytics+status:open [5] https://wiki.openstack.org/wiki/Stackalytics#Company_affiliation -- Best Regards, Sergey Nikitin

3 2

[qa] [ptg] QA Stein Retrospective Etherpad
by Ghanshyam Mann 20 Apr '19

20 Apr '19

Hi All, I have started an etherpad for Stein cycle QA retrospective - https://etherpad.openstack.org/p/qa-stein-retrospective This will be discussed in PTG on Thursday 9.00-09.30 AM, so please add your feedback/comment before that. -gmann

1 0

[docs] Documenting CLI references (openstack-auto-commands)
by Sean McGinnis 19 Apr '19

19 Apr '19

Hey everyone, Hoping someone has discussed this and has a recommended course of action. Back when we had the awesome support of the openstack-docs team, there was a command called openstack-auto-commands that would load up client commands and generate help output for all commands. With the resource constraints that hit the team, there were less folks to support tools like this. Docs moved into each team's repos and, for the most part, I think that has worked out well. Some of the automatic syncing stopped happening with this move to in-repo docs. One of them was CLI docs. But it would appear there are at least a few teams that now have not updated these docs since that move happened several releases ago: http://codesearch.openstack.org/?q=This%20file%20is%20tool-generated&i=nope… There are others that appear to have used the last automatically generated version and have been (varying degrees of) successful at just manually updating the doc as things change. When the tool was removed (https://review.openstack.org/#/c/509402/) it was stated that it wasn't needed because cliff has sphinx integration to do the equivalent automatically. That's all well and good... if you are using cliff. But I think many of our legacy clients are not. So looking for recommendations on ways to best keep these docs up to date now. Migrate to cliff? Other in-repo automation tools? (and yeah, I know, "drop the CLI and move to openstackclient) Thanks for any suggestions! Sean

2 2

shelve server taking too long
by Manuel Sopena Ballesteros 19 Apr '19

19 Apr '19

Dear Openstack community, I am trying to shelve a server but the process seems to be stuck in shelving_image_pending_upload state. is it normal for the shelve process to take several hours? thank you NOTICE Please consider the environment before printing this email. This message and any attachments are intended for the addressee named and may contain legally privileged/confidential/copyright information. If you are not the intended recipient, you should not read, use, disclose, copy or distribute this communication. If you have received this message in error please notify us at once by return email and then delete both messages. We accept no liability for the distribution of viruses or similar in electronic communications. This notice should not be removed.

2 1

[searchlight] Searchlight planning for Train
by Trinh Nguyen 19 Apr '19

19 Apr '19

Hi team, We just released Searchlight for Stein last week successfully. Congratulations to all of you who have contributed to the project. We did it!!!! So now the Train cycle started [1]. I would like to plan for the things that we would want to accomplish in this new cycle. Please have a look at the etherpad [2] and put your ideas or comment on existing ones. [1] https://releases.openstack.org/train/schedule.html [2] https://etherpad.openstack.org/p/searchlight-train Yours, -- *Trinh Nguyen* *www.edlab.xyz <https://www.edlab.xyz>*

1 0

[tripleo] Scale up/down Ansible tasks
by Emilien Macchi 19 Apr '19

19 Apr '19

Hi folks, Today I spent a bit of time on: https://blueprints.launchpad.net/tripleo/+spec/scale-down-tasks Which is basically adding the capability of running Ansible tasks before a node is removed during a scale down or after a scale-up. I'm focusing on the scale-down right now, as I know it's something people have been waiting for (e.g. RHSM unsubscribe, Ceph OSD tear down, Nova Compute, etc). I need inputs from folks now, on what kind of tasks would be needed, I will test them and make sure the interface we provide is enough. John, Olie, and Martin in copy have maybe some ideas, please let me know some examples of Ansible tasks that you folks want to run before a node is deleted in Ironic. Prototype: https://review.openstack.org/#/q/topic:bp/scale-down-tasks+(status:open+OR+… Thanks a lot, -- Emilien Macchi

4 7

[ops] offer to host next OpenStack Ops meetup 2019-9-3, 2019-9-4 NYC
by Chris Morgan 19 Apr '19

19 Apr '19

Hello All, My employer Bloomberg LP would like to offer to host the next OpenStack Ops meetup here in NYC in early September this year. Please see https://etherpad.openstack.org/p/ops-meetup-2nd-2019 for some early details on this. All hosting offers are subject to scrutiny by the ops meetups team and the overal community for content, location, timing etc and then approved via a mix of consensus gathering and (if there are multiple offers) voting, see https://wiki.openstack.org/wiki/Ops_Meetups_Team and https://wiki.openstack.org/wiki/Operations/Meetups Thanks, Chris -- Chris Morgan <mihalis68(a)gmail.com>

7 6

[nova][ptg] Stein retrospective
by Eric Fried 19 Apr '19

19 Apr '19

All- I have seeded an etherpad for Nova Stein nostalgia [1]. Please populate it. Following tradition, I'm putting this first on the schedule. Unless this etherpad gets just huge, I'm going to time box the discussion to 30 minutes. Make it count. Thanks, efried [1] https://etherpad.openstack.org/p/nova-ptg-train-retrospective

1 0

Re: [openstack-dev] [nova][xenapi][ptg] can we deprecate the xenapi-specific 'nova-console' service?
by Eric Fried 19 Apr '19

19 Apr '19

Scrubbing the Nova PTG agenda (hence addition of [ptg] subject tag), and this is on it: ================ Can we remove the nova-console service? (mriedem) The nova-console service is xenapi-specific and was deprecated in stein: https://review.openstack.org/#/c/610075/ There are, however, REST APIs for it: https://developer.openstack.org/api-ref/compute/#server-consoles-servers-os… So if we drop the nova-console service, the APIs would no longer work. It seems our options are: Delete the nova-console service and obsolete the REST APIs (410 response on all microversions like what we're doingwith nova-cells and nova-network APIs) Deprecate the REST APIs on a new microversion but continue to support older microversions - this means the nova-console service would live forever. Are people still using the nova-console service? Are there alternatives/replacements for xen users? BobBall seemed to suggest there was http://lists.openstack.org/pipermail/openstack-dev/2018-October/135422.html but it's not clear to me. ================ I'm looking for any excuse to remove things from the agenda, and this seems like a good candidate, because we don't really stand to gain anything by bringing it up at the PTG. Does anyone a) object to removing the nova-console service; or b) think we need to discuss it at the PTG? Thanks, efried .

2 1

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

19 Apr '19

Dear Neutrinos, We don't have RFEs lined up for discussion for tomorrow's meeting. So we are cancelling it this week Best regards Miguel

1 0

[nova] Privsep is not giving us any security
by Matthew Booth 18 Apr '19

18 Apr '19

Privsep is intended to provide some security in depth. The idea is based on the principal of least privilege. We assume that an attacker has exploited some bug in Nova and is able to execute arbitrary code. If privsep is doing its job, the attacker should at least not be able to perform any privileged operations which Nova does not normally perform. For developers, from the spec[1]: "The intention is to allow slightly more code into the privileged portion - enough that we now have sufficient “context” to make better security decisions. For example move from “run chown” to “take ownership of VM output file”." Unfortunately, I suspect out of expediency in the initial forklift from rootwrap, we've lost this critical principal of moving security-critical logic into privsep itself. Consequently, a brief and non-exhaustive audit reveals we have privsep functions to do the following: fs.py: * mount anything of any type, including remote storage, anywhere. * unmount anything * shred any file or block device, without restriction path.py: * read any file or block device, without restriction * overwrite any existing file or block device utils.py: * send any signal to any process Just the existence of these methods in nova's privsep module essentially gives the unprivileged nova process unfettered root access, which entirely defeats the purpose of privsep. As it stands today, privsep gives us literally nothing. I suspect that it's worse than rootwrap, in fact. If privsep protection is something we want, we need to do 2 things: 1. Immediately stop adding or using generic privsep functions. 2. Audit privsep properly for problematic methods, and remove them. For example, in libvirt.driver.get_console_output() we do nova.privsep.path.writefile(console_log, 'a+', data). Instead, we should have, eg, nova.privsep.libvirt.ensure_console_log_for_instance(instance). This would determine the instance path from its own secure config (see [1] again), and touch that file. We should probably also compile a list of privsep anti-patterns if there isn't one already to make life simpler for reviewers. For example, I suggest that no privsep function should take as an argument a path, or any other reference to a system resource; it should determine these itself. I view this as essentially a continuation of the privsep forklift. As with all such large mechanical changes I expect this to be disruptive and unloved by reviewers. Is it something we'd be prepared to prioritise? Matt [1] https://specs.openstack.org/openstack/oslo-specs/specs/liberty/privsep.html -- Matthew Booth Red Hat OpenStack Engineer, Compute DFG Phone: +442070094448 (UK)

6 14

[OpenStack-sigs][publiccloud-wg][Action Required] help most needed for SIGs and WGs
by Rico Lin 18 Apr '19

18 Apr '19

Dear all SIG and WG members I would like to ask for three favors from each group. Thank you for your kindly help. tl;dr: 1. As an action from [3], we will have a forum `Help most needed for SIGs and WGs` [4]. And would like to ask each group kindly provide me the following help most needed information, including - What's your team's name - Who's leading or active in this team - What's this team recently plan or doing - How people can join this team? - What's your most needed help interns of actions or technical features? - Which team (or who) you think that have a part in above help request (high potentially is fine)? - Anything else you wish to share to attendees? 2. update help most needed section in [1]. So anyone can understand what help your group needs. Also, TCs and UCs will have a better view of how group effort been working in the community and how community priority should be if regarding SIGs and WGs. 3. Also, consider your needs as a community goal? Add it in [2] now. -------------------------------------------longer version--------------------------------------------------- ( don't worry, not like I can do a super long readable article, but under the power of line-counting this is longer and still readable for sure!) 1. Back in the last summit, we have a forum [3] to talk about how can we help to expose SIGs and WGs. As an action, We will host a forum in coming Denver summit, to talk about `Help most needed for SIGs and WGs` [4]. This forum will present the most needed help from SIGs and WGs. By plan to also invite everyone (will try to invite people from each team and group) in the community to join this forum. We might get attention from people and potentially helpers:). Therefore, I do wish to have participants from every group. Please kindly provide me the following help most needed information, including - What's your team's name - Who's leading or active in this team - What's this team recently plan or doing - How people can join this team? - What's your most needed help interns of actions or technical features? - Which team (or who) you think that have a part in above help request (high potentially is fine)? - Anything else you wish to share to attendees? I will try to reach out to each team too, but if you already have answers to the above questions, that will be super! Since we might get around 16 groups, will try to get to the ` most needed help` part for everyone. But hopefully, we can still give some time if any attendee is really interested in helping. We gonna get more focus on what's the needs and how we can help to make progress of it, so it won't be like another BoF or Project update for you. Also, it's a forum so I won't give my hope to have a video recorder, which makes the second part more essential. 2. Update help most needed section in [1]. So anyone can understand what help you need. Also, TCs and UCs will have a better view of how group effort been working in the community and how community priority should be. Possibly and hopefully organizations/users/people might find matching their inner plan and sending people to help. Now if your group are willing to help with the forum, this action should be easy. And as I mention we're going to have a forum [4], It will be benefit to have such a document ready for anyone who's not coming to summit. 3. Is this needed suitable as a community goal [2]? Since we're also discussing community goal in #openstack-tc and ML, I think this might be a good chance to raise your needs into suggestion as our goal [2] if you find it fit with community goal definition. As one of the Meta SIG chairs, I will try hard to make all SIG's life easier. So let me know if above action doesn't fit with your group or if you find it hard with making progress with your SIG mission. [1] https://github.com/openstack/governance/blob/master/reference/help-most-nee… [2] https://etherpad.openstack.org/p/community-goals [3] https://etherpad.openstack.org/p/expose-sigs-and-wgs [4] https://www.openstack.org/summit/denver-2019/summit-schedule/events/23612/h… -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

3 2

[tripleo] Stein RC1 is out (with stable/stein branch)
by Emilien Macchi 18 Apr '19

18 Apr '19

We decided to branch stable/stein and release our first Stein release candidate this week. The main action that is being asked to our dear community is to think about backporting patches landing in master that you want to see in Stein. As usual some of us will watch things which land on master but really any help on that is very welcome. Also I've produced some stats about the evolution of TripleO since Newton. https://docs.google.com/presentation/d/1RV30OVxmXv1y_z33LuXMVB56TA54Urp7oHI… A few highlights: - Bug fixing is pretty consistent since Pike, no major change - Stein is the release with the less implemented blueprints since before Newton - Our core contributors number keep growing - Number of LOC & reviews keep growing since Queens Thanks everyone for your hard work during this cycle, I'm looking forward to seeing you in Denver and work on "Train". -- Emilien Macchi

1 0

[Neutron][QoS] No meeting on April 23
by Rodolfo Alonso 18 Apr '19

18 Apr '19

Hello folks: Because of an agenda problem, I won't chair the QoS meeting on April 23. I talked to Miguel and there is no problem to postpone this meeting until May 7, after the PTG. Regards.

1 0

[tripleo] [Release-job-failures] Release of openstack/puppet-tripleo failed
by Sean McGinnis 18 Apr '19

18 Apr '19

There was a failure in the post-release job for puppet-tripleo that I think we will need someone from TripleO and or someone with Puppet knowledge to address. The error received was: Forge API failed to upload tarball with code: 400 errors: The dependency 'sensu/sensu' in metadata.json is empty. All dependencies must have a 'version_requirement'.,The dependency 'yelp/uchiwa' in metadata.json is empty. All dependencies must have a 'version_requirement'. http://logs.openstack.org/75/75c09955854b142fd08c843bebcb8ee90d951b4d/relea… I'm guessing that's something in the puppet-tripleo repo, but really have no idea how this part works. If someone from the team could look into this, we can then do a follow up release if needed to correct any issues. ----- Forwarded message from zuul(a)openstack.org ----- Date: Thu, 18 Apr 2019 15:04:39 +0000 From: zuul(a)openstack.org To: release-job-failures(a)lists.openstack.org Subject: [Release-job-failures] Release of openstack/puppet-tripleo failed Reply-To: openstack-discuss(a)lists.openstack.org Build failed. - release-openstack-puppet http://logs.openstack.org/75/75c09955854b142fd08c843bebcb8ee90d951b4d/relea… : POST_FAILURE in 3m 18s - announce-release announce-release : SKIPPED _______________________________________________ Release-job-failures mailing list Release-job-failures(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures ----- End forwarded message -----

2 1

[neutron] RFE Decouple placement reporting service plugin from ML2
by Bence Romsics 18 Apr '19

18 Apr '19

Hi Neutrinos, I'm wondering if we have a use case for the following RFE: https://bugs.launchpad.net/neutron/+bug/1818479 Decouple placement reporting service plugin from ML2 Very close to the Stein rc1 deadline we merged a change with a review comment we agreed to tackle in a followup RFE - the one above. Here's the original comment from Slawek: https://review.openstack.org/#/c/580672/30/neutron/services/placement_repor… I see why Slawek left the comment, the placement reporter service plugin's dependency on ML2 does hurt my aestethic sense too. But now starting to work out the details of the followup work I'm not sure if we have a use case here. I would like to understand if we have a use case or not, because the change we talked about would increase code complexity. So it needs justification. If we don't have a use case we better do nothing and leave the complexity as it is. But if we do have a use case I'm still happy to work on that. In short: What concrete problems does it mean if the placement reporter service plugin depends on the ML2 core plugin? When eliminating that dependency what use case(s) are we generalizing the code for? I see the following options: 1) There may be an agent reporting its resource information in a different format - unlike ovs-agent and sriov-agent. 2) There may be an agentless mechanism driver needing to sync to Placement. 3) There may be a non-ML2 core plugin needing to sync to Placement. For (1) we standardized the format included in the agent's configurations attribute. An agent newly implementing support for reporting resource information should only deviate from that format if that format cannot express the resource information. Do we have an agent like that? The format is basically a 2-layer mapping from physnets to the list of their backing physical devices (whatever that is for an agent: bridges, sriov PFs, etc) and further mapping to the backing devices' inventory numbers. For the exact format please see this piece of the docs: https://docs.openstack.org/neutron/stein/admin/config-qos-min-bw.html#neutr… Case (2) may be a realistic use case, but I'm not much familiar with agentless mechanism drivers. IIUC some agentless mechanism drivers actually maintain fake agent entries in the neutron db. Those drivers can utilize the current service plugin via the fake agent entries as if they were real. For really agentless mechanism drivers (not even fake agent records) and for (3) I'm inclined to say: Don't load this placement reporter service plugin but write your own. To summarize on a high level: Slawek's original comment on the implicit dependency detects a real design smell, but I don't see how refactoring the service plugin to a driver architecture would improve the situation. What could nicely make this plugin more generic is subscribing to another interface: create/update_host_resources() instead of create/update_agent() because agents today are an implementation detail of the ML2 drivers. But the host (instead of an agent) is an abstraction we never had in neutron. What do you think? Sorry for the long mail, Bence irc: rubasov

1 0

[ironic] Stepping down from core
by shiina.hironori＠fujitsu.com 18 Apr '19

18 Apr '19

Hi ironic folks, I'm sorry for my long absence. My job responsibility changed last November. Since it, I have been trying to spend some time on the core activity. But, I couldn't. So, I'm stepping down from the ironic core team. Thank you for accepting me to the team even though I didn't often appear in IRC due to the time difference. I hope I will work with you again someday. Best regards, Hironori

4 3

[placement][ptg] pre-ptg checkpoint
by Chris Dent 18 Apr '19

18 Apr '19

Since I'm going to be out of touch next week, I thought it best to provide a checkpoint summarizing where things are with the virtual pre-PTG process so that we go into the PTG in reasonable shape. For reference, the pre-PTG has been a series of email threads discussion topics raised in the two placement-related PTG etherpads: * https://etherpad.openstack.org/p/placement-ptg-train * https://etherpad.openstack.org/p/ptg-train-xproj-nova-placement Each thread is linked from its topic in the etherpad. Any thread which reached some resolution is marked with a boldface "ACTION", often with a link to a story or review associated with the next step. Overall I think the process has been useful. We've figured out some plans of action for resource provider partitioning and consumer types, worked out better testing for osc-placement, and have some ideas on better container manager and performance testing. These things are reflected in worklists on storyboard [1, 2]. We've also managed to uncover some more ideas, challenges, and benefits with nested resource providers. We have a planned Saturday morning session at the PTG with Ironic, Blazar and anyone else who is thinking about using placement outside of nova. Where we've made less progress is getting owners on the new features [3] and reaching some resolution or plan with the several nested provider related threads (aggregate spanning, subtree "affinity", json body, NUMA in placement, request group mapping, resource trait filters). We've shared some ideas and managed to dismiss some things that won't work, but at least so far a solid plan is yet to emerge. Part of the latter may be my fault. I'm compelled to fully understand what's going on and for things to make as much sense to as many people as possible and I believed we had the time and space to have a wide-open discussion in that direction in the weeks prior to the PTG. There's still next week, so perhaps that's still the case, but maybe a different approach is required. If you've got ideas, please share. Please carry on with the threads if there's more to add. I'll incorporate them early in the week before the PTG and extract some kind of schedule for our time at the PTG. As I've said before there may not be much opportunity, we've only got Friday and Saturday and it is mostly consumed. Friday will mostly be taken up with Nova, Saturday morning will be talking with Ironic and Blazar. By Saturday afternoon we will probably be exhausted and I suspect the best use of our time will be talking without agenda about making sure working on Placement is pleasant and useful for everyone [4]. We don't need to actively seek more work: We've already defined got a lot, especially when we account for work in other projects. Thanks. [1] Cleanups: https://storyboard.openstack.org/#!/worklist/575 [2] Features: https://storyboard.openstack.org/#!/worklist/594 [3] However, thanks very much to Surya for stepping up to make a spec for the consumer type feature: https://storyboard.openstack.org/#!/story/2005473 [4] To that end, please make sure you have added your thoughts to the retrospective etherpad: https://etherpad.openstack.org/p/placement-ptg-train-retrospective -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

1 0

[neutron] neutron-metering-agent track router and floating IP traffic
by Florian Engelmann 18 Apr '19

18 Apr '19

Hi, I configured our neutron meters like: labels: openstack network meter create --description "shared bandwidth-public-out" --share bandwidth-public-out openstack network meter create --description "shared bandwidth-public-in" --share bandwidth-public-in rules: openstack network meter rule create --egress --remote-ip-prefix 0.0.0.0/0 bandwidth-public-out openstack network meter rule create --ingress --remote-ip-prefix 0.0.0.0/0 bandwidth-public-in This created the iptables rules in all namespaces and collects data: openstack metric measures show bc6c670f-cbb5-4fe1-974c-10455448fa27 +---------------------------+-------------+---------------+ | timestamp | granularity | value | +---------------------------+-------------+---------------+ | 2019-04-15T16:00:00+02:00 | 3600.0 | 581854.954545 | | 2019-04-15T17:00:00+02:00 | 3600.0 | 23169398.5625 | | 2019-04-15T18:00:00+02:00 | 3600.0 | 586508.9 | | 2019-04-15T19:00:00+02:00 | 3600.0 | 1276372.84375 | | 2019-04-15T20:00:00+02:00 | 3600.0 | 507482.911765 | [...] But how to know which project caused which amount of traffic? It looks like only one metric is created for each label? openstack metric list | grep bandwidth | 0f9f20a4-1c60-442f-81cb-48285e3f70da | ceilometer-ew-low | bandwidth | B | efae8040-85d7-455a-958d-213a81ef98ef | | 1a058a79-965f-4a0a-a9ee-d482f57892ab | ceilometer-ew-low | bandwidth | B | 837ed34a-65d2-42ef-924e-fd3c7e5aaed6 | What does "shared" mean? I was not able to find any relevant documentation. Do I have to create a meter for each project or a rule or both? Is it possible to define a "default" meter and rule for every existing project and all future projects? All the best, Flo

1 1

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

18 Apr '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

2 1

[sahara] Sahara meeting April 18 - volunteer chair? (or cancel?)
by Jeremy Freudberg 18 Apr '19

18 Apr '19

I have a personal conflict and will not be around to run the Sahara meeting on April 18 (tomorrow). There isn't too much to discuss, so I'm comfortable letting it be cancelled. But if there is any volunteer chair, the meeting can still run. Thanks, Jeremy

2 1

[murano] Galera Table package_to_tag has no PRIMARY_KEY
by Marc Vorwerk 18 Apr '19

18 Apr '19

Hello, uploading an application to Murano fails after upgrading "percona-xtradb-cluster-common-5.6" to "percona-xtradb-cluster-common-5.7": Importing package io.murano Error {"explanation": "The server has either erred or is incapable of performing the requested operation.", "code": 500, "error": {"message": "(pymysql.err.InternalError) (1105, u'Percona-XtraDB-Cluster prohibits use of DML command on a table (murano.package_to_tag) without an explicit primary key with pxc_strict_mode = ENFORCING or MASTER') [SQL: u'INSERT INTO package_to_tag (package_id, tag_id) VALUES (%(package_id)s, %(tag_id)s)'] [parameters: {'package_id': 'a345ab1fe4924aaf8ed32f954a6fe32d', 'tag_id': '0cb3765d7fe1486ba9741f4eb9b2a437'}]", "traceback": null, "type": "DBError"}, "title": "Internal Server Error"} (HTTP 500) occurred while installing package io.murano If i looks on the galera table, i get the following information: $ mysql -u murano -p mysql> Use murano; mysql> INSERT INTO package_to_tag (package_id, tag_id) VALUES (a345ab1fe4924aaf8ed32f954a6fe32d, 0cb3765d7fe1486ba9741f4eb9b2a437); ERROR 1105 (HY000): Percona-XtraDB-Cluster prohibits use of DML command on a table (murano.package_to_tag) without an explicit primary key with pxc_strict_mode = ENFORCING or MASTER mysql> SHOW KEYS FROM package_to_tag WHERE Key_name = 'PRIMARY'; Empty set (0.00 sec) My package list: $pkg -l | grep -e mysql -e percona root@control02ve:~# dpkg -l | grep -e mysql -e percona ii libdbd-mysql-perl 4.033-1ubuntu0.1 amd64 Perl5 database interface to the MySQL database ii libmysqlclient20:amd64 5.7.25-0ubuntu0.16.04.2 amd64 MySQL database client library ii mysql-common 5.7.25-0ubuntu0.16.04.2 all MySQL database common files, e.g. /etc/mysql/my.cnf ii percona-release 1.0-11.generic all Package to install Percona gpg key and APT repos ii percona-xtrabackup-24 2.4.13-1.xenial amd64 Open source backup tool for InnoDB and XtraDB ii percona-xtradb-cluster-client-5.7 5.7.25-31.35-1.xenial amd64 Percona XtraDB Cluster database client binaries ii percona-xtradb-cluster-common-5.7 5.7.25-31.35-1.xenial amd64 Percona XtraDB Cluster database common files (e.g. /etc/mysql/my.cnf) ii percona-xtradb-cluster-galera-3.x 3.32-1.xenial amd64 Galera components of Percona XtraDB Cluster ii percona-xtradb-cluster-server-5.7 5.7.25-31.35-1.xenial amd64 Percona XtraDB Cluster database server binaries ii python-mysqldb 1.3.7-1build2 amd64 Python interface to MySQL ii python-pymysql 0.7.11-1~cloud0 all Pure-Python MySQL driver - Python 2.x Murano is installed in the latest version of queens (https://github.com/openstack/murano/tree/stable/queens) Has anyone an idea? Best Regards, Marc

2 2

[fenix][forum][ptg]
by Juvonen, Tomi (Nokia - FI/Espoo) 18 Apr '19

18 Apr '19

Hi, If you did not yet know Fenix: Fenix - rolling infrastructure maintenance and upgrade with VNF interaction to guarantee zero impact. https://wiki.openstack.org/wiki/Fenix Now there has been the rolling OpenStack upgrade with zero impact to VNF showcased in ONS America two weeks ago and it is time to look the Train and the way forward. Most importantly to harmonize with ETSI NFV and prioritize the work to have a solid base after this cycle. Here is etherpad for the forum: Fenix project update, future, discuss Tue 30th April, 9:00am - 9:40am The Colorado Convention Center - Ballroom Level - 4B https://etherpad.openstack.org/p/DEN-fenix-forum-brainstorming Here are etherpads for the PTG: Fenix and ETSI NFV synch: Sat 4th May, 10:00am - 11:00am https://etherpad.openstack.org/p/DEN2019-fenix-ETSI-NFV-PTG Fenix Train PTG, What to do next, prioritizing Sat 4th May, 11:10am - 12:10am https://etherpad.openstack.org/p/DEN2019-fenix-PTG br, Tomi

1 0

[telemetry] Nominating Rong Zhu for Telemetry core
by Trinh Nguyen 18 Apr '19

18 Apr '19

Hi team, I'd like to nominate Rong Zhu (zhurong) to become a Telemetry core. Rong Zhu has been contributing to OpenStack for a while now [1] and sometimes jump in to help Telemetry projects fix bugs. While being the PTL of Murano and Solum projects [2], his experience and network of developers working on ceilometer/aodh projects would be a huge benefit for the team. [1] https://review.openstack.org/#/q/owner:%22zhurong+%253Caaronzhu1121%2540gma… [2] https://governance.openstack.org/election/results/train/ptl.html Let give +1 for your agreement. Yours, -- *Trinh Nguyen* *www.edlab.xyz <https://www.edlab.xyz>*

3 3

[telemetry] Update cores team and team lead recruitment
by Trinh Nguyen 18 Apr '19

18 Apr '19

Hi team, As you may know, existing core members of Telemetry cannot work on the projects anymore. So, I would like to set up a new core team for Telemetry projects in the Train cycle. At the moment, only Lixian Kong and I have the core privileges over Ceilometer, AODH, and Panko projects. I expect to have 1 more core reviewer to help maintain Telemetry. So *please send us your proposal if you're interested*. This is the current structure of Telemetry: - AODH: Lixian Kong is the team lead - Ceilometer and Panko: myself. This is just tempory until we can find someone that has enough experience and willing to take the role. As discussed in yesterday meeting [1], you may argue that having experience does not necessarily qualify for code contributions but with the current situation, I would propose "*the willing to help*" as the number 1 criteria. We will move forward with it and fix processes when we see issues. Thank all the people that want to keep Telemetry alive. Yours, [1] https://etherpad.openstack.org/p/telemetry-train -- *Trinh Nguyen* *www.edlab.xyz <https://www.edlab.xyz>*

4 8

[charms] OpenStack Charms 19.04 release is available with Stein enablement
by David Ames 18 Apr '19

18 Apr '19

The OpenStack Charms development team is happy to announce the 19.04 charms release, introducing support for OpenStack Stein with Ceph Mimic on Ubuntu 18.04 (LTS) and Ubuntu 19.04. This charm release also brings several new and valuable features to the existing OpenStack Charms deployments for Queens, Rocky, Stein, and many other stable combinations of Ubuntu + OpenStack. For the full release notes, please reference: https://docs.openstack.org/charm-guide/latest/1904.html Some highlights: * Masakari instance high-availability * Keystone SSO/SAML integration * Nova GPU and general device pass-through * Multi-site replication between Ceph RADOS Gateways * Mirroring of RBD images across Ceph Clusters The charms dev team is available on Freenode #openstack-charms, and will be at the Open Infrastructure Summit and PTG events in Denver, CO (May 2019). Huge thanks to the 71 charm contributors who worked together to squash 247 bugs, to enable an entirely new charmed version of OpenStack, and to move the line forward on several key features! Ryan Beisner Frode Nordahl Liam Young James Page Doug Hellmann David Ames Corey Bryant Chris MacNaughton Paul Goins Pete Vander Giessen Alex Kavanagh Edward Hope-Morley melissaml Chris MacNaughton Sahid Orentino Ferdjaoui zhouxinyong Andreas Jaeger lijunjie Felipe Reyes caoyuan zhulingjie Vladimir Grevtsev Dmitrii Shcherbakov inspurericzhang Andrew McLeod Syed Mohammad Adnan Karim Andre Ruiz Tiago Pasqualini Billy Olsen Drew Freiberger Seyeong Kim Hua Zhang Vu Cong Tuan wanghui Trent Lloyd Przemyslaw Hausman xulei Andrea Ieri Xav Paice Alvaro Uria Tytus Kurek Nikolay Vinogradov lvxianguo Nobuto Murata Nicolas Pochet Aymen Frikha Marian Gasparovic lei zhang Niels van Adrichem andy wang Shane Peters Jonathan Herlin Andrey Grebennikov wangyayan zhangbailin Diko Parvanov Dimos Alevizos Mike Wilson David Coronel Tilman Baumann MaoyangLiu gaobin Jesper M Gábor Mészáros Junien Fridrick Pedro Guimarães Wouter van Bommel Abhijeet Patra Peter Zhang Barry Price Dongdong Tao -- OpenStack Charm Team

1 0

[cinder][dev] support-revert-to-any-snapshot
by Walsh, Helen 18 Apr '19

18 Apr '19

To cinder driver developers: * https://blueprints.launchpad.net/cinder/+spec/support-revert-to-any-snapshot In relation to the blueprint above. I am wondering if there are any drivers that whose later snapshots will not be valid after a revert to an snapshot that is NOT the last in the series Vol1 \ ----------------------------------------------------- Mon Tue Wed Thu Fri \ \ \ \ \ S1 -------- S2 ---------S3 -------- S4 ---------S5 If on Fri, I was to revert back to Tuesday's Snapshot S2, would S3, S4 and S5 still be usable Snapshots? Vol1 \ ----------------------------------------------------- Mon Tue Wed Thu Fri \ \ \ \ \ S1 -------- S2 ---------S3 -------- S4 ---------S5 Thank you, Helen

2 1

[PTG] FINAL SCHEDULE..NO SERIOUSLY.
by Kendall Nelson 17 Apr '19

17 Apr '19

Since I published the first 'Final Schedule' we have had a number of small changes that we've had to make so I wanted to update everyone to make sure we are all on the same page. Seriously though, this is the last round of changes as this version of the schedule has already gone to the design team and is going to print sometime tomorrow/Friday. To textually summarize the changes: - Tacker will no longer be meeting - Converted the Interop WG into a dynamically scheduled team - Horizon will be all day Thursday instead of a half day See you all soon! -Kendall (diablo_rojo)

1 0

Does anyone care about reviewstats?
by Matt Riedemann 17 Apr '19

17 Apr '19

There are open reviewstats changes [1] but the non-infra core team is entirely made up of people that no longer work on openstack [2]. I had a change that was open so long some of the projects are now owned by placement [3] so I just abandoned it. So the question is, does anyone use reviewstats anymore? If so, we should probably just start adding new people to the core team that actually use it. Otherwise we should probably just put it in the attic and rely on stackalytics (which is probably what most people are already doing). [1] https://review.openstack.org/#/q/project:openstack-infra/reviewstats+status… [2] https://review.openstack.org/#/admin/groups/893,members [3] https://review.openstack.org/#/c/499197/ -- Thanks, Matt

11 15

[all] Gerrit will be offline April 19, 2019
by Anita Kuno 17 Apr '19

17 Apr '19

Pursuant to this email thread: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.ht… , which discusses the rationale for moving git repo namespaces, Gerrit will be offline on April 19, 2019. Specific start time for the outage will be posted to this thread when it is decided next week. Outage may be sporadic as needed by the infra team, you can follow the progress in the #openstack-infra irc channel on freenode. Please review the above linked email and all the subsequent posts, and please post any concerns about the rationale or details to the above thread. If you have concerns about the Gerrit outage scheduled to begin April 19, 2019, please reply to this thread and/or join us in #openstack-infra on freenode to share your questions or concerns. Thank you, Anita

1 2

[placement][ptg] JSON payload for GET /a_c
by Chris Dent 17 Apr '19

17 Apr '19

>From the etherpad [1] * would make things like "resource provider affinity" above easier. much easier. and let us express granular-ness less awkwardly, and let us add new and richer group_policy concepts (which is basically the affinity thing). * Brought up briefly in the above spec at https://review.openstack.org/#/c/650476/1/doc/source/specs/train/approved/2… As clients making GET /allocation_candidates queries desire to express more and more complexity [2], query parameters start to feel cumbersome. At various times people have suggest that a JSON body might be easier to manage. The first time was during the discussion that resulted in the creation of the allocation_candidates resource. My personal feeling on this is that if we have a way to satisfy a use case without changing the API, even if it is cumbersome, we should write in that mode first and then decide if adding the other way is appropriate. This isn't simply because of some over-adherence to YAGNI, but because we need to deliver on some of placement's promise sooner than later and there don't seem to be a lot of people around. There may, however, be plenty of reasons that not everyone knows for why this needs to happen. If so, please share them. Only once we know those reasons should we start considering formats. What do we need to express (and why do we need to express it) that we can't express now? [1] https://etherpad.openstack.org/p/placement-ptg-train [2] https://review.openstack.org/#/c/555081/22/specs/train/approved/cpu-resourc… -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

4 4

[placement][ptg] Resource Provider Partitioning
by Chris Dent 17 Apr '19

17 Apr '19

>From the etherpad [1]: * do we need this? * what is it? * who is going to drive it? As as I recall, resource provider partitioning (distinct from allocation partitioning) is a way of declaring that a set of resource providers are in a thing. This would allow, for example, one placement to service multiple OpenStack clouds or for a placement to be a part of a single pane of glass system in a FOG or edge setup. This was mentioned during Stein nova discussions [2] but since then I've not personally heard a lot of discussion on this topic so it's unclear if it is a pressing issue. Do we want to be build it so they come, or wait until they come and then build it? The discussion at [2] mentions the possibility of an 'openstack-shard' header (instead of query parameter) that would be sent with any request to placement. There is, however, no substantive discussion on the internal implementation. Options: * Do nothing (see above) * Internally manipulate aggregates (all these resource providers below to shard X). * Add a 1:1 or 1:N relation between an RP and a shard uuid in the DB. * Use a trait! [3] But before we get into implementation details we should discuss the use cases for this (if any), the need to do it (if any), and the people who will do it (if any). All three of those are thin at this point. [1] https://etherpad.openstack.org/p/placement-ptg-train [2] around lines 243 on https://etherpad.openstack.org/p/nova-ptg-stein where both types (allocation/rp) of partitioning are discussed. [3] Not for the trait strict constructionists. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

4 13

[placement][ptg] Allocation Partitioning
by Chris Dent 17 Apr '19

17 Apr '19

>From the etherpad [1]: * do we need this? * what is it? * who is going to drive it? As as I recall, allocation partitioning (distinct from resource provider partitioning) is a way of declaring that a set of allocations below to a specific service. This is useful as a way, for example, of counting instances spawned via nova. Right now it is possible to count vcpus, ram and disk but if something besides nova is making allocations using those resource classes how do we distinguish? Of course it's important to also ask "should we distinguish?". If there's a concept of unified limits does it matter whether a VCPU is consume by _this_ nova or something else if they are consumed by the same user? This functionality is closely tied to resource provider partitioning. In a complex placement scenario, where placement is managing multiple instance spawning tools, in multiple cloud-like things, it seems like both would be needed. The ongoing work to implement quota counting in placement [2] has a workaround for instances not being counted in placement, but the "more than one nova per placement" limitation has to be documented. How urgent is this? Is there anyone available to do the work this cycle? How damaging is it to punt to U? What details are missing in the above description? [1] https://etherpad.openstack.org/p/placement-ptg-train [2] https://review.openstack.org/#/q/topic:bp/count-quota-usage-from-placement -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

7 26

[tripleo][openstack-ansible] collaboration on os_tempest role update XIX - Apr 16, 2019
by Chandan kumar 17 Apr '19

17 Apr '19

Hello, Here is the 19th update (Apr 10 to Apr 06, 2019) on collaboration on os_tempest[1] role between TripleO and OpenStack-Ansible projects. Highlights of the week: * os_tempest user guide is now published here: https://docs.openstack.org/openstack-ansible-os_tempest/stein/user/index.ht… * os_tempest role now have debian support. * In tripleo side, all standalone and standalone scenario [1-4] periodics jobs are consuming os_tempest to run tempest in CI Thanks to mnaser for debian support, mkopec, noonedeadpunk for user guide & Arx for porting all standalone periodic jobs to os_tempest Things got merged: os_tempest: * os_tempest user guide: https://review.openstack.org/644570 * debian: add ci and update meta : https://review.openstack.org/652346 tripleo: * Port base standalone job to os_tempest - https://review.rdoproject.org/r/20061 * Port standalone scenario01 to os_tempest - https://review.rdoproject.org/r/19916 * Port scenario002-standalone-master to os_tempest - https://review.rdoproject.org/r/20059 * Port scenario003-standalone-master to os_tempest - https://review.rdoproject.org/r/20037 * Port scenario004-standalone-master to os_tempest - https://review.rdoproject.org/r/20140 * Port standalone full tempest job to os_tempest - https://review.rdoproject.org/r/20203 Things in Progress: os_tempest: * Make smoke tests as a default whitelist tests - https://review.openstack.org/652060 * Enable support for novajoin tempest plugin - https://review.openstack.org/652986 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 What's coming? Once we have tripleo master promotion, we will update the tripleo ci upstream job config to os_tempest We will be continue working on current os_tempest patches. Here is the 18th 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/004878.ht… Thanks, Chandan Kumar

1 1

[vitrage][ptg] Vitrage PTG etherpad
by Ifat Afek 17 Apr '19

17 Apr '19

Hi, I created an etherpad for discussion topics for the Vitrage PTG, which will be held on Friday morning, May 3rd. Feel free to comment or add other topics. https://etherpad.openstack.org/p/vitrage-train-ptg Thanks, Ifat

1 0

Routed networks and FIP gateway assignments
by Syd Logan 17 Apr '19

17 Apr '19

I'm currently learning about routed networks and have a lab that is implementing a 3 tier leaf spine and have a question. I know that I can create a subnet from which FIP gateway IP addresses are consumed, e.g., openstack subnet create demo-floating-ip-agent-gateway-subnet \ --subnet-range 198.51.100.0/24 --no-dhcp \ --service-type 'network:floatingip_agent_gateway' \ --network demo-ext-net In videos from past OpenStack summits such as this https://youtu.be/XnXSwCSHc4U drawings show that the subnet is used within a single segment's compute nodes, and I can believe that would work. What isn't clear is whether the same subnet should be used across multiple segments, or the intent is for each segment defined in the routed network to have a unique subnet from which these FIP gateway IPs are assigned, e.g., some other segment would be using, say 198.52.100.0/24. In the non-routed network setup where I leanred about DVR it was pretty clear only one subnet was allowed, but what is the best practice/intent for routed nets? Thanks. syd

1 0

[Zun] Openstack Rocky Appcontainer start error
by Navdeep Uniyal 17 Apr '19

17 Apr '19

Dear All, I am getting following error while trying to start the ubuntu container Command: openstack appcontainer run --name containerA --net network=5guknet ubuntu ping 8.8.8.8 Error: status_reason | Docker internal error: 500 Server Error: Internal Server Error ("legacy plugin: Post http://127.0.0.1:23750/Plugin.Activate: dial tcp 127.0.0.1:23750: connect: connection refused"). Secondly, with Heat Template: heat_template_version: 2015-04-30 resources: the_resource: type: OS::Zun::Container properties: cpu: 4 image: ubuntu image_pull_policy: "ifnotpresent" interactive: true memory: 2048 name: "ubuntu16" command: "ping 8.8.8.8" networks: [{"network": 5guknet}] restart_policy: "no" The command I can see on the appcontainer show is : command | [u'p', u'i', u'n', u'g', u' ', u'8', u'.', u'8', u'.', u'8', u'.', u'8'] Please advise how to resolve the two issues. Kind Regards, Navdeep

2 1

[neutron] Cleaning in Neutron
by Slawomir Kaplonski 17 Apr '19

17 Apr '19

Hi, I just run abandon_old_reviews.sh [1] script again for neutron, neutron-lib and neutron-tempest-plugin repositories. So if You have Your patch abandoned but You want to continue to work on it, please simple restore it or if You can’t restore it by self, please ping me on irc (slaweq) and I will restore it for You. [1] https://github.com/openstack/neutron/blob/master/tools/abandon_old_reviews.… — Slawek Kaplonski Senior software engineer Red Hat

3 3

[stackalytics] Reported numbers seem inaccurate
by Sergey Nikitin 17 Apr '19

17 Apr '19

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

2 1

[gentoo] Looking for members to help maintain OpenStack packages on Gentoo
by Matthew Thode 16 Apr '19

16 Apr '19

I'm considering disbanding the Gentoo OpenStack project and switching to sole maintainership of the project. So far I'm the only active maintianer in the project that I can see. I'm looking for others that are interested in helping maintain the openstack ebuilds. It's fairly easy as an ongoing thing with two major releases a year (which starts an update of 160 or so packages). It's python based and I've found maintaining the ebuilds to be very easy individually if that helps. There are other actions that'd be helpful as well. Some arm64 stage work (catalyst builds these) to then do some arm64 diskimage-builder work to work on building VM images for other arches (openstack or 'vanilla'). Please respond if you are intrested in joining. I've also emailed the Gentoo developer list separately with the same request. Thanks, -- Matthew Thode

1 0

[tripleo][ptg] Initial PTG schedule
by Alex Schultz 16 Apr '19

16 Apr '19

Hey folks, I've taken the topics from the previously announced etherpad[0] and put together a basic schedule for Thursday-Saturday. Please take a moment to review https://etherpad.openstack.org/p/tripleo-ptg-train and let me know if there are any issues with the timing. We have some extra time most days if we need to shift things around. Thanks, -Alex [0] https://etherpad.openstack.org/p/tripleo-train-topics

2 2

[placement][ptg] Keeping osc-placement healthy
by Chris Dent 16 Apr '19

16 Apr '19

>From the etherpad [1]: * It is behind (in microversions) and sometimes hard to remember * It's functional tests require a working devstack, which is a bit meh * Maybe something like https://vcrpy.readthedocs.io/en/latest/ could help (reasonable given microversions) * (edleafe) It might be useful to have an osc-placement lead (czar? princess? mayor?) who can devote some of their time to this and help coordinate others. I might be able to rustle up some cycles. Not much to add to the above. What additional ideas to people have. Who (in addition to Ed) has some time to care about osc-placement? What do people think of vcrpy? What else? [1] https://etherpad.openstack.org/p/placement-ptg-train -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

3 8

[tripleo] Canceling IRC meeting on April 30, 2019
by Alex Schultz 16 Apr '19

16 Apr '19

Due to the summit and PTG, most folks won't be around so we'll cancel the meeting for that week. We will resume the weekly IRC meeting on May 7, 2019. Thanks, -Alex

1 0

[ironic] Cancelling meetings April 22nd through May 6th, resuming May 13th
by Julia Kreger 16 Apr '19

16 Apr '19

Greeting fellow practitioners of irony! I meant to raise this question during our weekly meeting yesterday, but simply forgot. Some discussion on irc[0] today has reached a consensus that we should just cancel the next few meetings. * This next week, April 22nd, out meeting conflicts with holidays for a number of contributors. * The week after, April 29th, will be during the Open Infrastructure Summit. Historically we cancel the meeting on the week following such a gathering to give contributors time to re-group. We will be resuming meetings on May 13th. As always you can find ironic contributors in #openstack-ironic. Review priorities should be sourced from the whiteboard[1] using the "This Week's Priorities" section.. Thanks everyone! -Julia [0]: http://eavesdrop.openstack.org/irclogs/%23openstack-ironic/%23openstack-iro… [1]: https://etherpad.openstack.org/p/IronicWhiteBoard

1 0

Re: [stackalytics] Reported numbers seem inaccurate
by Jeremy Stanley 16 Apr '19

16 Apr '19

On 2019-04-11 18:21:13 UTC (+0000), Mark Goddard wrote: > 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'm not going to attempt to debate the value of the Stackalytics site, but given the maintainers seem to have set their sights beyond OpenStack lately they're probably not following discussions on the openstack-discuss mailing list (their lack of replies here after nearly a week would indicate this as well). According to the readme[*] for the project, they seem to prefer bug reports via Launchpad so that may be a more effective place to follow up on this concern if there is a desire for continued use of Stackalytics by the OpenStack community. That said, someone already seems to have reported[**] the problem back in January and the bug hasn't been triaged yet, but maybe additional mee-toos will up their urgency? [*] https://opendev.org/openstack/stackalytics/src/branch/master/README.rst#pro… [**] https://launchpad.net/bugs/1811028 -- Jeremy Stanley

1 0

[nova][scheduler] scheduler spawns to the same compute node only
by Nicolas Ghirlanda 16 Apr '19

16 Apr '19

Hi all, we have a kolla-ansible deployed "Queens" Release of openstack with 8 compute nodes and an external Percona XtraDB Cluster (with read-write split with haproxy). New VMs are just currently always scheduled to the same compute node, even though a manual live-migration is working fine to other compute nodes. We're not sure, what the issue is, but perhaps someone may spot it from our config: # nova.conf scheduler config default_availability_zone = az1 ... [filter_scheduler] available_filters = nova.scheduler.filters.all_filters enabled_filters = RetryFilter, AvailabilityZoneFilter, ComputeCapabilitiesFilter, ImagePropertiesFilter, ServerGroupAntiAffinityFilter, ServerGroupAffinityFilter, AggregateInstanceExtraSpecsFilter, AggregateMultiTenancyIsolation, DifferentHostFilter, RamFilter, SameHostFilter, NUMATopologyFilter Database is an external Percona XtraDB Cluster (Version 5.7.24) with haproxy for read-write-splitting (currently only one write node). We do see mysql errors in the nova-scheduler.log on the write DB node when an instance is created. 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db [-] Unexpected error while reporting service status: OperationalError: (pymysql.err.OperationalError) (1213, u'WSREP detected deadlock/conflict and aborted the transaction. Try restarting the transaction') (Background on this error at: http://sqlalche.me/e/e3q8) 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db Traceback (most recent call last): 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/nova/servicegroup/drivers/db.py", line 91, in _report_state 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db service.service_ref.save() 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_versionedobjects/base.py", line 226, in wrapper 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db return fn(self, *args, **kwargs) 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/nova/objects/service.py", line 397, in save 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db db_service = db.service_update(self._context, self.id, updates) 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/nova/db/api.py", line 183, in service_update 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db return IMPL.service_update(context, service_id, values) 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_db/api.py", line 154, in wrapper 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db ectxt.value = e.inner_exc 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db self.force_reraise() 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db six.reraise(self.type_, self.value, self.tb) 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_db/api.py", line 142, in wrapper 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db return f(*args, **kwargs) 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/nova/db/sqlalchemy/api.py", line 227, in wrapped 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db return f(context, *args, **kwargs) 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/usr/lib/python2.7/contextlib.py", line 24, in __exit__ 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db self.gen.next() 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginefacade.py", line 1043, in _transaction_scope 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db yield resource 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/usr/lib/python2.7/contextlib.py", line 24, in __exit__ 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db self.gen.next() 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginefacade.py", line 653, in _session 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db self.session.rollback() 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db self.force_reraise() 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db six.reraise(self.type_, self.value, self.tb) 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginefacade.py", line 650, in _session 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db self._end_session_transaction(self.session) 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginefacade.py", line 678, in _end_session_transaction 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db session.commit() 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/sqlalchemy/orm/session.py", line 943, in commit 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db self.transaction.commit() 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/sqlalchemy/orm/session.py", line 471, in commit 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db t[1].commit() 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1643, in commit 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db self._do_commit() 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1674, in _do_commit 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db self.connection._commit_impl() 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 726, in _commit_impl 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db self._handle_dbapi_exception(e, None, None, None, None) 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1409, in _handle_dbapi_exception 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db util.raise_from_cause(newraise, exc_info) 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/sqlalchemy/util/compat.py", line 265, in raise_from_cause 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db reraise(type(exception), exception, tb=exc_tb, cause=cause) 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 724, in _commit_impl 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db self.engine.dialect.do_commit(self.connection) 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/sqlalchemy/dialects/mysql/base.py", line 1765, in do_commit 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db dbapi_connection.commit() 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/pymysql/connections.py", line 422, in commit 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db self._read_ok_packet() 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/pymysql/connections.py", line 396, in _read_ok_packet 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db pkt = self._read_packet() 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/pymysql/connections.py", line 683, in _read_packet 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db packet.check_error() 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/pymysql/protocol.py", line 220, in check_error 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db err.raise_mysql_exception(self._data) 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/pymysql/err.py", line 109, in raise_mysql_exception 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db raise errorclass(errno, errval) 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db OperationalError: (pymysql.err.OperationalError) (1213, u'WSREP detected deadlock/conflict and aborted the transaction. Try restarting the transaction') (Background on this error at: http://sqlalche.me/e/e3q8) 2019-04-15 16:52:10.016 24 ERROR nova.servicegroup.drivers.db 2019-04-15 16:52:20.020 24 INFO nova.servicegroup.drivers.db [-] Recovered from being unable to report status. The deadlock message is quite strange, as we have haproxy configured so all write requests are handled by one node. There are NO errors in the mysqld.log WHILE creating an instance, but we see from time to time aborted connections from nova. 2019-04-15T14:22:36.232108Z 30616972 [Note] Aborted connection 30616972 to db: 'nova' user: 'nova' host: '10.x.y.z' (Got an error reading communication packets) As I said, all instances are allocated to the same compute node. nova-compute.log doesn't show an error while creating the instance. Beside that, we also see messages from nova.scheduler.host_manager on all other nodes like (but those messages are _not_ triggered, when an instance is spawned.!) 2019-04-15 16:28:47.771 22 INFO nova.scheduler.host_manager [req-f92e340e-a88a-44a0-8cad-588390c25bc2 - - - - -] The instance sync for host 'xxx' did not match. Re-created its InstanceList. Don't know if that may be relevant, but somehow our (currently single) AZ is listed several times. # openstack availability zone list +------------+-------------+ | Zone Name | Zone Status | +------------+-------------+ | internal | available | | az1 | available | | az1 | available | | az1 | available | | az1 | available | +------------+-------------+ May that be related somehow? Thanks for any consideration and support! kind regards Nicolas --

4 7

[taas] stein
by Takashi Yamamoto 16 Apr '19

16 Apr '19

hi, i'll branch and release it sooner or later. probably in this week, or maybe the next one. wrt dashboard, i'm not sure if the repo is in a ready-to-release state. have anyone tested it recently?

1 1

[ceilometer] Missing some notifications
by Florian Engelmann 16 Apr '19

16 Apr '19

Hi, I am not sure if this problem is related to ceilometer or rabbitmq but it looks like our ceilometer notification agent is missing some notifications. Creating, eg. 10 cinder volumes in a row results in some of those volumes are not stored in gnocchi. "openstack metric resource show <ID>" results in a 404 error. Attaching the volume and detaching it again sometimes helps to "create" it in gnocchi. We do use gnocchi for billing. So missing volumes is very bad. Any recommendation on how to debug this problem? Thank you very much, flo

1 0

[scientific-sig] Meeting tonight: Ironic and Data Center Inventory, Denver Summit
by Stig Telfer 16 Apr '19

16 Apr '19

Hi All - We have a Scientific SIG IRC meeting today at 2100 UTC in channel #openstack-meeting. Everyone is welcome. Today's agenda is here: https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_April_16th_2019 <https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_April_16th_2019> We’d like to continue the discussion started last week (in the other timezone) on surveying data center inventory management systems used in research computing, and how those might be better integrated with Ironic. We also have preparations for the Denver summit to discuss. Cheers, Stig

1 0

[tc][all] Dropping py35 testing
by Ghanshyam Mann 16 Apr '19

16 Apr '19

Hello Everyone, All the integration testing has been moved to Bionic[1] now and as discussed in the TC meeting[2], we are good to drop the py35 testing. Train: Good to drop. I am going to push the patches to remove the py35 jobs from the master (which is Train now). Stable/Stein: Ok to drop if the project wants. Stable/Stein gate is also moved to Bionic so we are good to drop py35 from stable/stein too. But backporting all the patches will be too many patches for projects to merge on stable/stein so we discussed not to propose all of them to stable/stein. If the project really wants to drop it from stable/stein then, they can backport. NOTE: Till stable/rocky, we should keep testing py35. If your project is branchless like Tempest and gate the same jobs for stable/rocky or older then, you should keep testing the py35 until stable/rocky EOL. [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004647.ht… [2] http://eavesdrop.openstack.org/meetings/tc_python3/2019/tc_python3.2019-03-… http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003610.ht… -gmann

7 12

[telemetry] Vote for team meeting datetime
by Trinh Nguyen 16 Apr '19

16 Apr '19

Hi team, There're many things we need to discuss for the Train cycle so I propose we have a bi-weekly meeting and the first one would be on May 2 (next two weeks will be the vacation of most of the people). Please cast your vote for an appropriate time: https://doodle.com/poll/8akawam8yk38q2hh Yours, -- *Trinh Nguyen* *www.edlab.xyz <https://www.edlab.xyz>*

2 6

[kuryr] [kuryr-kubernetes] Unable to use kubernetes-related things after rebooting host
by Jaewook Oh 16 Apr '19

16 Apr '19

Hello kuryr-kubernetes team, currently, I deployed openstack with devstack, and I added "kuryr-kubernetes" to use kubernetes vim. At first it worked fine and no error was occurred, so I made some c-vnfs with kuryr-kubernetes. But after rebooting the host, the systems that worked well before are not working normally at all. First, I deployed an example one ('redis') with kubectl command, (Not using Tacker, but only using kubectl cli) it showed below error, Events: │obeTime":null,"lastTransitionTime":"2019-04-15T02:28:31Z"}],"hostIP":"192.168.1.20","startTime":"2019-04-15T02:28:31Z" Type Reason Age From Message │,"containerStatuses":[{"name":"web-server","state":{"waiting":{"reason":"ContainerCreating"}},"lastState":{},"ready":f ---- ------ ---- ---- ------- │alse,"restartCount":0,"image":"kyleoh95/iistrc-k8s-demo2:0.4","imageID":""}],"qosClass":"Guaranteed"}}]} Normal Scheduled 2m25s default-scheduler Successfully assigned default/redis-master-6fbbc44567-ms8n│Apr 15 11:36:52 master tacker-server[1881]: from (pid=1881) request /usr/local/lib/python2.7/dist-packages/kubernetes k to master │/client/rest.py:219 Warning MissingClusterDNS 2m25s kubelet, master pod: "redis-master-6fbbc44567-ms8nk_default(8a6f9079-5f27-│Apr 15 11:36:52 master tacker-server[1881]: 2019-04-15 11:36:52.633 DEBUG tacker.vnfm.infra_drivers.kubernetes.kuberne 11e9-9b42-a4bf01550f1a)". kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" pol│tes_driver [-] status: Pending from (pid=1881) create_wait /opt/stack/tacker/tacker/vnfm/infra_drivers/kubernetes/kube icy. Falling back to "Default" policy. │rnetes_driver.py:137 Warning FailedCreatePodSandBox 19s kubelet, master Failed create pod sandbox: rpc error: code = Unknown desc │Apr 15 11:36:52 master tacker-server[1881]: 2019-04-15 11:36:52.634 DEBUG tacker.vnfm.infra_drivers.kubernetes.kuberne = failed to set up sandbox container "310e18b859e118ad6abcaa60d29a9e332da516ce57b8cdf47456ea4882ca66f5" network for pod│tes_driver [-] VNF initializing status: ['default', 'svc-vdu1-b9e851'] Pending from (pid=1881) create_wait /opt/stack/ "redis-master-6fbbc44567-ms8nk": NetworkPlugin cni failed to set up pod "redis-master-6fbbc44567-ms8nk_default" networ│tacker/tacker/vnfm/infra_drivers/kubernetes/kubernetes_driver.py:141 k: Got invalid status code from CNI daemon.; Traceback (most recent call last): │Apr 15 11:36:52 master tacker-server[1881]: 2019-04-15 11:36:52.634 WARNING tacker.vnfm.infra_drivers.kubernetes.kuber File "/opt/stack/kuryr-kubernetes/kuryr_kubernetes/cni/api.py", line 80, in run │netes_driver [-] VNF Creation failed: Resource creation is not completed within 500 seconds as creation of stack defau vif = self._add(params) Are there any reason for this error? And how can I resolve this problem? Best Regards, Jaewook. ================================================ *Jaewook Oh* (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea Tel : +82-2-820-0841 | Mobile : +82-10-9924-2618 E-mail : jwoh95(a)dcn.ssu.ac.kr ================================================

5 6