January 2019 - openstack-discuss - lists.openstack.org

[dev][puppet] Register PTG team attendance
by Tobias Urdin 16 Jan '19

16 Jan '19

Dear Puppeteers, The foundation would like all projects to report if they will be attending the PTG and I'm in charge of reporting that for the Puppet OpenStack project. I'm now reaching out to hear if you are attending and would like the Puppet OpenStack project to have an official attendance and therefore possible requirements of rooms etc? I personally is not sure that I will attend the PTG even though it's directly after the Summit which I'm hoping to be able to attend this year. Earlier years we haven't had any real reasons to have dedicated rooms or events from what I know but please let me know if you have any plans. I don't think not placing our team as attending prevents anybody from actually being at the PTG, I hope not atleast (maybe somebody can shine in on that part). I need to fill in the survey by January 20th, 2019 at 7:00 UTC so please let me know urgently, sorry for the short timespan, it's entirely my fault on that part. Please get back to me if you will be attending and need to register the Puppet OpenStack team. Best regards Tobias

1 0

[openstack-discuss] [stackalytics] Stackalytics facelift
by Boris Renski 16 Jan '19

16 Jan '19

Folks, Happy New Year! We wanted to start the year by giving a facelift to stackalytics.com (based on stackalytics openstack project). Brief summary of updates: - We have new look and feel at stackalytics.com - We did away with DriverLog <http://stackalytics.com/report/driverlog> and Member Directory <http://stackalytics.com/report/members>, which were not very actively used or maintained. Those are still available via direct links, but not in the menu on the top - BIGGEST CHANGE: You can now track some of the CNCF and Unaffiliated project commits via a separate subsection accessible via top menu. Before this was all bunched up in Project Type -> Complimentary Happy to hear comments or feedback. -Boris

9 12

[publiccloud-wg][sigs] Reminder weekly meeting Public Cloud WG
by Tobias Rydberg 16 Jan '19

16 Jan '19

Hi everyone, Time for a new meeting for Public Cloud WG - tomorrow 1400 UTC in #openstack-publiccloud! Agenda found at https://etherpad.openstack.org/p/publiccloud-wg Cheers, Tobias -- Tobias Rydberg Senior Developer Twitter & IRC: tobberydberg www.citynetwork.eu | www.citycloud.com INNOVATION THROUGH OPEN IT INFRASTRUCTURE ISO 9001, 14001, 27001, 27015 & 27018 CERTIFIED

1 0

Re: [Release-job-failures] Release of openstack/puppet-* failed
by Thierry Carrez 16 Jan '19

16 Jan '19

Puppet-OpenStack Stein M2 release job (triggered after https://review.openstack.org/#/c/629753/ merged) failed for all modules with errors similar to: zuul(a)openstack.org wrote: > Build failed. > > - release-openstack-puppet http://logs.openstack.org/b1/b1434f41935eb5c4cb50fc5aea2b6406a6d0f63d/relea… : POST_FAILURE in 2m 58s > - announce-release announce-release : SKIPPED This is due to the recent introduction of a puppetforge upload job: https://review.openstack.org/#/c/627573/5/zuul.d/jobs.yaml That job tries to install a few gems and that fails because the ruby header files are not available (missing ruby-dev / ruby-devel package). Tarball upload jobs are then skipped, as well as announcement or releases.o.o documentation. Solution is probably to add that missing package to the "build" bindep.txt profile (for every affected puppet-* repository) that is loaded in pre-run of that publication job. Currently that profile only contains "puppet" and that stops short of installing the ruby development header package (at least on Ubuntu hosts). Once that's done, I recommend pushing a new Stein release for Puppet-OpenStack (similar to https://review.openstack.org/#/c/629753/, bumping .Z for all packages) so that we can test that it properly works before end-of-release crush. -- Thierry Carrez (ttx)

2 2

[neutron]
by Masha Atakova 16 Jan '19

16 Jan '19

1 0

[neutron] Patch fails to build after rechecking.
by Ni, Qi 16 Jan '19

16 Jan '19

Hello guys, I've been working on a patch of neutron https://review.openstack.org/#/c/626109/11 and it keeps failing when building. I'm sure my code is bug free and I found Liu Yulong's patch has a similar condition like mine. https://review.openstack.org/#/c/627285/. He rechecks many times and fails every time. His code is nearly the same as previous except a line of comment. I'm not sure if there's any bug on this checking system and please take a look at our issue, thank you.

2 1

[pctavia][heat] queens loadbalancer issue
by Ignazio Cassano 16 Jan '19

16 Jan '19

Hello All, I am facing an issue with octavia loadbalancer on queens. Attached here there is the heat stack I am using for frating a loadbalancer between 2 virtual machines. I launched the stack 4 times. First, second and third work fine. The forth gives a lot of errors in octavia worker log attached here. It seems to loop . Please help me. Ignazio

1 1

[heat]meeting cancelled this week
by Rico Lin 16 Jan '19

16 Jan '19

Dear team, due to some personal stuff, I will not join meeting today. Let’s resume meeting next week. -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

1 0

[meta-sig][docs] new section for SIG documentation on docs.o.o
by Adam Spiers 16 Jan '19

16 Jan '19

For the Stein release there is now a new section for SIGs on the documentation home page: https://docs.openstack.org/stein/ Currently only the self-healing SIG has a link but if other SIGs have links to add, it won't feel so lonely ;-)

2 3

[placement] update 19-01
by Chris Dent 16 Jan '19

16 Jan '19

HTML: https://anticdent.org/placement-update-19-01.html Hello! Here's placement update 19-01. Not a ton to report this week, so this will mostly be updating the lists provided last week. # Most Important As mentioned last week, there will be a meeting next week to discuss what is left before we can pull the trigger on [deleting the placement code from nova](https://review.openstack.org/618215). Wednesday is looking like a good day, perhaps at 1700UTC, but we'll need to confirm that on Monday when more people are around. Feel free to respond on this thread if that won't work for you (and suggest an alternative). Since deleting the code is dependent on deployment tooling being able to handle extracted placement (and upgrades to it), reviewing that work is important (see below). # What's Changed * It was nova's spec freeze this week, so a lot of effort was spent getting some specs reviewed and merged. That's reflected in the shorter specs section, below. * Placement had a release and was published to [pypi](https://pypi.org/project/openstack-placement/). This was a good excuse to write (yet another) blog post on [how easy it is to play with](https://anticdent.org/placement-from-pypi.html). # Bugs * Placement related [bugs not yet in progress](https://goo.gl/TgiPXb): 14. -1. * [In progress placement bugs](https://goo.gl/vzGGDQ) 16. +1 # Specs With spec freeze this week, this will be the last time we'll see this section until near the end of this cycle. Only one of the specs listed last week merged (placement for counting quota). * <https://review.openstack.org/#/c/544683/> Account for host agg allocation ratio in placement (Still in rocky/) * <https://review.openstack.org/#/c/595236/> Add subtree filter for GET /resource_providers * <https://review.openstack.org/#/c/597601/> Resource provider - request group mapping in allocation candidate * <https://review.openstack.org/#/c/549067/> VMware: place instances on resource pool (still in rocky/) * <https://review.openstack.org/#/c/555081/> Standardize CPU resource tracking * <https://review.openstack.org/#/c/599957/> Allow overcommit of dedicated CPU (Has an alternative which changes allocations to a float) * <https://review.openstack.org/#/c/591037/> Modelling passthrough devices for report to placement * <https://review.openstack.org/#/c/603955/> Nova Cyborg interaction specification. * <https://review.openstack.org/#/c/601596/> supporting virtual NVDIMM devices * <https://review.openstack.org/#/c/552924/> Proposes NUMA topology with RPs * <https://review.openstack.org/#/c/569011/> Count quota based on resource class * <https://review.openstack.org/#/c/141219/> Adds spec for instance live resize * <https://review.openstack.org/#/c/612497/> Provider config YAML file * <https://review.openstack.org/603545> Resource modeling in cyborg. * <https://review.openstack.org/#/c/609960/> Support filtering of allocation_candidates by forbidden aggregates * <https://review.openstack.org/601596> support virtual persistent memory # Main Themes ## Making Nested Useful I've been saying for a few weeks that "progress continues on gpu-reshaping for libvirt and xen" but it looks like the work at: * <https://review.openstack.org/#/q/topic:bp/reshape-provider-tree+status:open> is actually stalled. Anyone have some insight on the status of that work? Also making use of nested is bandwidth-resource-provider: * <https://review.openstack.org/#/q/topic:bp/bandwidth-resource-provider> There's a [review guide](http://lists.openstack.org/pipermail/openstack-discuss/2018-December… for those patches. Eric's in the process of doing lots of cleanups to how often the ProviderTree in the resource tracker is checked against placement, and a variety of other "let's make this more right" changes in the same neighborhood: * Stack at: <https://review.openstack.org/#/c/615677> ## Extraction Besides the meeting mentioned above, I've refactored the extraction etherpad to make a [new version](https://etherpad.openstack.org/p/placement-extract-stein-5) that has less noise in it so the required actions are a bit more clear. The tasks remain much the same as mentioned last week: the reshaper work mentioned above and the work to get deployment tools operating with an extracted placement: * [TripleO](https://review.openstack.org/#/q/topic:tripleo-placement-extractio… * [OpenStack Ansible](https://review.openstack.org/#/q/project:openstack/openstack-ansib… * [Kolla and Kolla Ansible](https://review.openstack.org/#/q/topic:split-placement) Loci's change to have an extracted placement has merged. Kolla has a patch to [include the upgrade script](https://review.openstack.org/#/q/topic:upgrade-placement). It raises the question of how or if the `mysql-migrate-db.sh` should be distributed. Should it maybe end up in the pypi distribution? (The rest of this section is duplicated from last week.) Documentation tuneups: * Release-notes: <https://review.openstack.org/#/c/618708/> This is blocked until we refactor the release notes to reflect _now_ better. * The main remaining task here is participating in [openstack-manuals](https://docs.openstack.org/doc-contrib-guide/doc-index.h…, to that end: * <https://review.openstack.org/#/c/628183/> A stack of changes to nova to remove placement from the install docs. * <https://review.openstack.org/#/c/628220/> Install docs in placement. I wrote to the [mailing list](http://lists.openstack.org/pipermail/openstack-discuss/2019-January/0… asking for input on making sure these things are close to correct, especially with regard to distro-specific things like package names. * <https://review.openstack.org/#/c/628324> Change to openstack-manuals to assert that placement is publishing install docs. Depends on the above. * There is a patch to [delete placement](https://review.openstack.org/#/c/618215/) from nova that we've put an administrative -2 on while we determine where things are (see about the meeting above). * There's a pending patch to support [online data migrations](https://review.openstack.org/#/c/624942/). This is important to make sure that fixup commands like `create_incomplete_consumers` can be safely removed from nova and implemented in placement. # Other There are still 13 [open changes](https://review.openstack.org/#/q/project:openstack/placement+statu… in placement itself. Most of the time critical work is happening elsewhere (notably the deployment tool changes listed above). Of those placement changes, the [database-related](https://review.openstack.org/#/q/owner:nakamura.tetsuro%2… ones from Tetsuro are the most important. Outside of placement: * <https://review.openstack.org/#/q/topic:minimum-bandwidth-allocation-placeme…> Neutron minimum bandwidth implementation * <https://review.openstack.org/#/c/586960/> zun: Use placement for unified resource management * <https://review.openstack.org/#/c/621645/> WIP: add Placement aggregates tests (in tempest) * <https://review.openstack.org/627326> blazar: Consider the number of reservation inventory * <https://review.openstack.org/622316> Add placement client for basic GET operations (to tempest) # End If anyone has submitted, or is planning to, a proposal for summit that is placement-related, it would be great to hear about it. I had thought about doing a resilient placement in kubernetes with cockroachdb for the edge sort of thing, but then realized my motivations were suspect and I have enough to do otherwise. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

2 1