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 15 Jan '19

15 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 15 Jan '19

15 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 15 Jan '19

15 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

[neutron][qos][dpdk] is QoS supported with DPDK
by cristian.calin＠orange.com 15 Jan '19

15 Jan '19

Hi all, Is QoS supported when DPDK is leveraged on the openvswitch? >From what I can tell the two are incompatible but I'm hoping someone has some information otherwise. Thanks, Cristian Calin _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

2 1

[self-healing-sig] best practices for haproxy health checking
by Dirk Müller 15 Jan '19

15 Jan '19

Hi, Does anyone have a good pointer for good healthchecks to be used by the frontend api haproxy loadbalancer? in one case that I am looking at right now, the entry haproxy loadbalancer was not able to detect a particular backend being not responding to api requests, so it flipped up and down repeatedly, causing intermittend spurious 503 errors. The backend was able to respond to connections and to basic HTTP GET requests (e.g. / or even /v3 as path), but when it got a "real" query it hung. the reason for that was, as it turned out, the configured caching backend memcached on that machine being locked up (due to some other bug). I wonder if there is a better way to check if a backend is "working" and what the best practices around this are. A potential thought I had was to do the backend check via some other healthcheck specific port that runs a custom daemon that does more sophisticated checks like checking for system wide errors (like memcache, database, rabbitmq) being unavailable on that node, and hence not accepting any api traffic until that is being resolved. Any pointers to read upon / best practices appreciated. Thanks, Dirk

3 2

Training
by Alfredo De Luca 15 Jan '19

15 Jan '19

Hi all. I am looking for openstack training both basic and advanced here in Italy or Europe. Possibly instructor led on site. Any suggestions? -- *Alfredo*

2 2

[horizon][keystone][dev] Cross-domain administrators and context-switching
by Robert Donovan 15 Jan '19

15 Jan '19

Hello, We run a cloud service with multiple domains (one per tenant) and offer services on top which can, amongst other things, involve administrators creating instances, snapshots etc. on behalf to those tenants. My understanding is that, in order to achieve this with Horizon, we currently have to create a separate admin user in each domain with a role that allows those abilities. The administrator then needs to log into that domain using the new user to perform the required actions. Firstly, is that assumption correct? Or is it possible use the same user credentials across domain boundaries? Secondly, have there ever been discussions around the “Set Domain Context” function having a wider effect to scope the whole dashboard to that particular domain, including the project panels? Are there potential issues with this as a proposal? Many thanks, Rob

2 1

[ops] last weeks meetups team minutes
by Chris Morgan 15 Jan '19

15 Jan '19

openstack ops meetups team meeting minutes from last week: Meeting ended Tue Jan 8 15:53:43 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 10:53 AM Minutes: http://eavesdrop.openstack.org/meetings/ops_meetup_team/2019/ops_meetup_tea… 10:53 AM Minutes (text): http://eavesdrop.openstack.org/meetings/ops_meetup_team/2019/ops_meetup_tea… 10:53 AM Log: http://eavesdrop.openstack.org/meetings/ops_meetup_team/2019/ops_meetup_tea… This week's meeting will be in approximately 40 minutes as I write. Our main priority now is to get the planning for the Berlin meetup underway Chris -- Chris Morgan <mihalis68(a)gmail.com>

1 0

[nova][dev] vCPU Pinning for L1/L2 cache side-channel vulnerability mitigation
by Robert Donovan 15 Jan '19

15 Jan '19

Hello Nova folks, I spoke to some of you very briefly about this in Berlin (thanks again for your time), and we were resigned to turning off SMT to fully protect against future CPU cache side-channel attacks as I know many others have done. However, we have stubbornly done a bit of last-resort research and testing into using vCPU pinning on a per-tenant basis as an alternative and I’d like to lay it out in more detail for you to make sure there are no legs in the idea before abandoning it completely. The idea is to use libvirt’s vcpupin ability to ensure that two different tenants never share the same physical CPU core, so they cannot theoretically steal each other’s data via an L1 or L2 cache side-channel. The pinning would be optimised to make use of as many logical cores as possible for any given tenant. We would also isolate other key system processes to a separate range of physical cores. After discussions in Berlin, we ran some tests with live migration, as this is key to our maintenance activities and would be a show-stopped if it didn’t work. We found that removing any pinning restrictions immediately prior to migration resulted in them being completely reset on the target host, which could then be optimised accordingly post-migration. Unfortunately, there would be a small window of time where we couldn’t prevent tenants from sharing a physical core on the target host after a migration, but we think this is an acceptable risk given the nature of these attacks. Obviously, this approach may not be appropriate in many circumstances, such as if you have many tenants who just run single VMs with one vCPU, or if over-allocation is in use. We have also only looked at KVM and libvirt. I would love to know what people think of this approach however. Are there any other clear issues that you can think of which we may not have considered? If it seems like a reasonable idea, is it something that could fit into Nova and, if so, where in the architecture is the best place for it to sit? I know you can currently specify per-instance CPU pinning via flavor parameters, so a similar approach could be taken for this strategy. Alternatively, we can look at implementing it as an external plugin of some kind for use by those with a similar setup. Many thanks, Rob

4 4

RE: [Edge-computing] Use cases mapping to MVP architectures - FEEDBACK NEEDED
by Csatari, Gergely (Nokia - HU/Budapest) 15 Jan '19

15 Jan '19

Hi, Thanks for the comment. Do you see any other use of the capability to create images on an edge site except creating snapshots? Thanks, Gerg0 From: Ildiko Vancsa <ildiko(a)openstack.org> Sent: Tuesday, January 15, 2019 2:59 AM To: Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari(a)nokia.com> Subject: Fwd: [Edge-computing] Use cases mapping to MVP architectures - FEEDBACK NEEDED Begin forwarded message: From: Bogdan Dobrelya <bdobreli(a)redhat.com<mailto:bdobreli@redhat.com>> Subject: Re: [Edge-computing] Use cases mapping to MVP architectures - FEEDBACK NEEDED Date: 2019. January 10. 8:34:45 GMT-7 To: edge-computing(a)lists.openstack.org<mailto:edge-computing@lists.openstack.org>, "openstack-discuss(a)lists.openstack.org<mailto:openstack-discuss@lists.openstack.org>" <openstack-discuss(a)lists.openstack.org<mailto:openstack-discuss@lists.openstack.org>> On 10.01.2019 14:43, Ildiko Vancsa wrote: Hi, We are reaching out to you about the use cases for edge cloud infrastructure that the Edge Computing Group is working on to collect. They are recorded in our wiki [1] and they describe high level scenarios when an edge cloud infrastructure would be needed. Hello. Verifying the mappings created for the "Elementary operations on a site" [18] feature against the distributed glance specification [19], I can see a vital feature is missing for "Advanced operations on a site", like creating an image locally, when the parent control plane is not available. And consequences coming off that, like availability of create snapshots for Nova as well. All that boils down to a) better identifying the underlying requirement/limitations for CRUD operations available for middle edge sites in the Distributed Control Plane case. And b) the requirement of data replication and conflicts resolving tooling, which comes out, if we assume we want all CRUDs being always available for middle edge sites disregard of the parent edge's control plane state. So that is the missing and important thing to have socialised and noted for the mappings. [18] https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUse… [19] https://review.openstack.org/619638 During the second Denver PTG discussions we drafted two MVP architectures what we could build from the current functionality of OpenStack with some slight modifications [2]. These are based on the work of James and his team from Oath. We differentiate between a distributed [3] and a centralized [4] control plane architecture scenarios. In one of the Berlin Forum sessions we were asked to map the MVP architecture scenarios to the use cases so I made an initial mapping and now we are looking for feedback. This mapping only means, that the listed use case can be implemented using the MVP architecture scenarios. It should be noted, that none of the MVP architecture scenarios provide solution for edge cloud infrastructure upgrade or centralized management. Please comment on the wiki or in a reply to this mail in case you have questions or disagree with the initial mapping we put together. Please let us know if you have any questions. Here is the use cases and the mapped architecture scenarios: Mobile service provider 5G/4G virtual RAN deployment and Edge Cloud B2B2X [5] Both distributed [3] and centralized [4] Universal customer premise equipment (uCPE) for Enterprise Network Services[6] Both distributed [3] and centralized [4] Unmanned Aircraft Systems (Drones) [7] None - assuming that this Use Case requires a Small Edge instance which can work in case of a network partitioning event Cloud Storage Gateway - Storage at the Edge [8] None - assuming that this Use Case requires a Small Edge instance which can work in case of a network partitioning event Open Caching - stream/store data at the edge [9] Both distributed [3] and centralized [4] Smart City as Software-Defined closed-loop system [10] The use case is not complete enough to figure out Augmented Reality -- Sony Gaming Network [11] None - assuming that this Use Case requires a Small Edge instance which can work in case of a network partitioning event Analytics/control at the edge [12] The use case is not complete enough to figure out Manage retail chains - chick-fil-a [13] The use case is not complete enough to figure out At this moment chick-fil-a uses a different Kubernetes cluster in every edge location and they manage them using Git [14] Smart Home [15] None - assuming that this Use Case requires a Small Edge instance which can work in case of a network partitioning event Data Collection - Smart cooler/cold chain tracking [16] None - assuming that this Use Case requires a Small Edge instance which can work in case of a network partitioning event VPN Gateway Service Delivery [17] The use case is not complete enough to figure out [1]: https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases [2]: https://wiki.openstack.org/wiki/Edge_Computing_Group/Edge_Reference_Archite… [3]: https://wiki.openstack.org/wiki/Edge_Computing_Group/Edge_Reference_Archite… [4]: https://wiki.openstack.org/wiki/Edge_Computing_Group/Edge_Reference_Archite… [5]: https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Mobile_servi…. [6]: https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Universal_cu… [7]: https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Unmanned_Air… [8]: https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Cloud_Storag… [9]: https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Open_Caching… [10]: https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Smart_City_a… [11]: https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Augmented_Re… [12]: https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Analytics.2F… [13]: https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Manage_retai… [14]: https://schd.ws/hosted_files/kccna18/34/GitOps.pdf [15]: https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Smart_Home [16]: https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Data_Collect… [17]: https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#VPN_Gateway_… Thanks and Best Regards, Gergely and Ildikó _______________________________________________ Edge-computing mailing list Edge-computing(a)lists.openstack.org<mailto:Edge-computing@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing -- Best regards, Bogdan Dobrelya, Irc #bogdando _______________________________________________ Edge-computing mailing list Edge-computing(a)lists.openstack.org<mailto:Edge-computing@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing

1 0

[infra] NetworkManager on infra Fedora 29 and CentOS nodes
by Ian Wienand 14 Jan '19

14 Jan '19

Hello, Just a heads-up; with Fedora 29 the legacy networking setup was moved into a separate, not-installed-by-default network-scripts package. This has prompted us to finally move to managing interfaces on our Fedora and CentOS CI hosts with NetworkManager (see [1]) Support for this is enabled with features added in glean 1.13.0 and diskimage-builder 1.19.0. The newly created Fedora 29 nodes [2] will have it enabled, and [3] will switch CentOS nodes shortly. This is tested by our nodepool jobs which build images, upload them into devstack and boot them, and then check the networking [4]. I don't really expect any problems, but be aware NetworkManager packages will appear on the CentOS 7 and Fedora base images with these changes. Thanks -i [1] https://bugzilla.redhat.com/show_bug.cgi?id=1643763#c2 [2] https://review.openstack.org/618672 [3] https://review.openstack.org/619960 [4] https://review.openstack.org/618671

2 5

Re: [congress][infra] override-checkout problem
by Eric K 14 Jan '19

14 Jan '19

Hi Ghanshyam, On 1/11/19, 4:57 AM, "Ghanshyam Mann" <gmann(a)ghanshyammann.com> wrote: >Hi Eric, > >This seems the same issue happening on congress-tempest-plugin gate where >'congress-devstack-py35-api-mysql-queens' is failing [1]. >python-congressclient was >not able to install and openstack client trow error for congress command. > >The issue is stable branch jobs on congress-tempest-plugin does checkout >the master version for all repo >instead of what mentioned in override-checkout var. > >If you see congress's rocky patch, congress is checkout out with rocky >version[2] but >congress-tempest-plugin patch's rocky job checkout the master version of >congress instead of rocky version [3]. >That is why your test expectedly fail on congress patch but pass on >congress-tempest-plugin. > >Root cause is that override-checkout var does not work on the legacy job >(it is only zuulv3 job var, if I am not wrong), >you need to use BRANCH_OVERRIDE for legacy jobs. Myself, amotoki and >akhil was trying lot other workarounds >to debug the root cause but at the end we just notice that congress jobs >are legacy jobs and using override-checkout :). Gosh thanks so much for the investigation. Yes it's a legacy-dsvm job. So sorry for the run around! I'm thinking of taking the opportunity to migrate to devstack-tempest job. I've taken a first stab here: https://review.openstack.org/#/c/630414/ > >I have submitted the testing patch with BRANCH_OVERRIDE for >congress-tempest-plugin queens job[4]. >Which seems working fine, I can make those patches more formal for merge. And thanks so much for putting together those patches using BRANCH_OVERRIDE! Merging sounds good unless we can quickly migrate To non-legacy jobs. Realistically it'll probably end up take a while to get everything migrated and working. > > >Another thing I was discussing with Akhil that new tests of builins >feature need another feature flag >(different than congressz3.enabled) as that feature of z3 is in stein >onwards only. Yup. I was going to do that but wanted to first figure out why it wasn't failing on tempest plugin. I've now submitted a patch to do that. > > >[1] https://review.openstack.org/#/c/618951/ >[2] >http://logs.openstack.org/70/629070/4/check/congress-devstack-api-mysql/87 >474d7/logs/pip2-freeze.txt.gz >[3] >http://logs.openstack.org/51/618951/3/check/congress-devstack-api-mysql-ro >cky/23c0214/logs/pip2-freeze.txt.gz >[4] >https://review.openstack.org/#/q/topic:fix-stable-branch-testing+(status:o >pen+OR+status:merged) > >-gmann > > ---- On Fri, 11 Jan 2019 10:40:39 +0900 Eric K ><ekcs.openstack(a)gmail.com> wrote ---- > > The congress-tempest-plugin zuul jobs against stable branches appear > > to be working incorrectly. Tests that should fail on stable/rocky (and > > indeed fails when triggered by congress patch [1]) are passing when > > triggered by congress-tempest-plugin patch [2]. > > > > I'd assume it's some kind of zuul misconfiguration in > > congress-tempest-plugin [3], but I've so far failed to figure out > > what's wrong. Particularly strange is that the job-output appears to > > show it checking out the right thing [4]. > > > > Any thoughts or suggestions? Thanks so much! > > > > [1] > > https://review.openstack.org/#/c/629070/ > > >http://logs.openstack.org/70/629070/4/check/congress-devstack-api-mysql/87 >474d7/logs/testr_results.html.gz > > The two failing z3 tests should indeed fail because the feature was > > not available in rocky. The tests were introduced because for some > > reason they pass in the job triggered by a patch in > > congress-tempest-plugin. > > > > [2] > > https://review.openstack.org/#/c/618951/ > > >http://logs.openstack.org/51/618951/3/check/congress-devstack-api-mysql-ro >cky/23c0214/logs/testr_results.html.gz > > > > [3] >https://github.com/openstack/congress-tempest-plugin/blob/master/.zuul.yam >l#L4 > > > > [4] >http://logs.openstack.org/51/618951/3/check/congress-devstack-api-mysql-ro >cky/23c0214/job-output.txt.gz#_2019-01-09_05_18_08_183562 > > shows congress is checked out to the correct commit at the top of the > > stable/rocky branch. > > > > > > >

2 1

[heat][octavia][barbican] TLS-terminated HTTPS load balancer
by Ignazio Cassano 14 Jan '19

14 Jan '19

Hello everyone, I found a lot of exampe for creating TLS-terminated HTTPS load balancer by command line using octavia and barbican. I did not find any example to do it with heat. Anyone could post an example, please ? Ignazio

1 0

[tripleo][openstack-ansible] collaboration on os_tempest role update VI - Jan 15, 2019
by Chandan kumar 14 Jan '19

14 Jan '19

Hello, Here is the sixth update (Jan 08 to Jan 15, 2019) on collaboration on os_tempest[1] role between TripleO and OpenStack-Ansible projects. Things got merged: os_tempest * Better tempest blacklist management - https://review.openstack.org/621605 * Move role data in share/ansible/roles - https://review.openstack.org/629127 * Use the inventory to enable/disable services by default - https://review.openstack.org/628979 * Remove tempest_image_dir_owner var - https://review.openstack.org/629419 * Automatically select the correct tempest plugins - https://review.openstack.org/629499 Tripleo * os_tempest tripleo integration blueprint created: https://blueprints.launchpad.net/tripleo/+spec/os-tempest-tripleo Summary: os_tempest role got following features: * support of handling tempest skiplist having reasons why a test added in skip list. * Handling enable/disabling of services and tempest plugins using inventory * tempest_image_dir_owner var got removed In Progress: os_tempest: * Run smoke and dashboard tests by default - https://review.openstack.org/587617 * Fix tempest workspace path - https://review.openstack.org/628182 * [WIP] let's find proper heat tests - https://review.openstack.org/630695 * Add support for aarch64 images - https://review.openstack.org/620032 * Configuration drives don't appear to work on aarch64+kvm - https://review.openstack.org/626592 python-tempestconf * Create functional-tests role - https://review.openstack.org/626539 * Enable manila plugin in devstack - https://review.openstack.org/625191 * Set refstack-client-*-tempestconf voting again - https://review.openstack.org/628919 Updates on running os_tempest in CI * Devstack - https://review.openstack.org/627482 * TripleO - https://review.openstack.org/#/q/topic:tripleoostempest+(status:open+OR+sta… Summary: Finally we are able to execute the os_tempest role but currently due to missing vars from playbook, we will be soon reaching to run tempest tests also. Tripleo os_tempest spec review: https://review.openstack.org/630654 Upcoming week, we will be working on enabling heat tempest tests in OSA jobs and trying to run tempest tests from os_tempest in Tripleo/DevStack CI. Thanks to arxcruz (for skiplist test management) and odyssey4me (enabling openstack services using inventory ). Here is the 5th 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-January/001471.… Thanks, Chandan Kumar

1 0

[Infra][Cinder]Testing Infortrend CI setup
by Kuirong.Chen(陳奎融) 14 Jan '19

14 Jan '19

Hi, I would like to ask some question. First one is about CI system setting. My CI system setup is follow on https://docs.openstack.org/infra/system-config/third_party.html. And the trigger way is follow jenkins gerrit triger like below: [cid:image001.png@01D4ACC3.C2A2B3F0] (Set the url as the guide say) And this is my test CI result on https://review.openstack.org/#/c/630871/. [cid:image002.png@01D4ACC4.77C23210] Under the History, my test project is not hyperlink text like others CI test. Why so different? The Second Question is: Does InfortrendCI account have voting permissions on cinder repo? On https://review.openstack.org/#/c/523659/ I find Infortrend CI account will show under History but workflow like below: [cid:image003.png@01D4ACC7.17F81270] That's mean I need get voting permissions? thank you. KuiRong Software Design Dept.II Ext. 7077

1 0

[Cyborg][IRC]
by Li Liu 14 Jan '19

14 Jan '19

The IRC meeting will be held Wednesday at 0300 UTC, which is 10:00 pm est(Tuesday) / 7:00 pm pst(Tuesday) /11 am Beijing time (Wednesday) This week's Agenda: 1. Track status working items here https://storyboard.openstack.org/#!/story/2004248 2. Considering merge Sundar's patches into the pilot branch. -- Thank you Regards Li

1 0

[edge] Zero Touch Provisioning
by Curtis 14 Jan '19

14 Jan '19

Hi, I've been looking through the docs I can find related to the edge working group, and I'm wondering if there has been any discussion/documentation of a Zero Touch Provisioning use case. I can't seem to find anything, but I may not be looking in the right place. Just wanted to double check and see what the current state is, if any. Thanks, Curtis

4 12

[cinder] db sync error upgrading from pike to queens
by Brandon Caulder 14 Jan '19

14 Jan '19

Hi, I am receiving the following error when performing an offline upgrade of cinder from RDO openstack-cinder-1:11.1.0-1.el7 to openstack-cinder-1:12.0.3-1.el7. # cinder-manage db version 105 # cinder-manage --debug db sync Error during database migration: (pymysql.err.OperationalError) (2013, 'Lost connection to MySQL server during query') [SQL: u'UPDATE volumes SET shared_targets=%(shared_targets)s'] [parameters: {'shared_targets': 1}] # cinder-manage db version 114 The db version does not upgrade to queens version 117. Any help would be appreciated. Thank you

5 8

Training
by Alfredo De Luca 14 Jan '19

14 Jan '19

Hi all. I am looking for openstack training both basic and advanced here in Italy or Europe. Possibly instructor led on site. Any suggestions? -- *Alfredo*

1 0

[dev][neutron] Bug summary week of Jan 7
by Boden Russell 14 Jan '19

14 Jan '19

1 0

[ironic] stepping down from core
by Vladyslav Drok 14 Jan '19

14 Jan '19

Hello folks, As you might have noticed my contribution to ironic has dropped to almost 0 during the last three months. My current job responsibilities have changed, and I can't dedicate the time needed to be a core reviewer at this time. I will still be around and at some point might get back to contributing to ironic, but for now I'd like to request to be removed from the core reviewers group. Thank you, Vlad

3 2

[nova] Retiring gantt, python-ganttclient projects
by Stephen Finucane 14 Jan '19

14 Jan '19

Hey, These projects are mega old, don't appear to have been official projects, and should have been retired a long time ago. This is serves as a heads up on the off-chance someone has managed to do something with them. Stephen

2 2

[L2-Gateway]
by Lajos Katona 14 Jan '19

14 Jan '19

Hi, I have a question regarding networking-l2gw, specifically l2gw-connection. We have an issue where the hw switch configured by networking-l2gw is slow, so when the l2gw-connection is created the API returns successfully, but the dataplane configuration is not yet ready. Do you think that adding state field to the connection is feasible somehow? By checking the vtep schema (http://www.openvswitch.org/support/dist-docs/vtep.5.html) no such information is available on vtep level. Thanks in advance for the help. Regarads Lajos

1 1

[Searchlight] Team meeting cancelled today
by Trinh Nguyen 13 Jan '19

13 Jan '19

Hi team, I will help to coordinate an upstream training webinar at 1400 today [1] so will have to cancel the team meeting. If you guys want to discuss something, please let me know, I will be on the IRC channel. [1] https://www.meetup.com/VietOpenStack/events/257860457/ Bests, -- *Trinh Nguyen* *www.edlab.xyz <https://www.edlab.xyz>*

1 0

[Searchlight] Nominating Thuy Dang for Searchlight core
by Trinh Nguyen 13 Jan '19

13 Jan '19

Hello team, I would like to nominate Thuy Dang <thuydang.de(a)gmail.com> for Searchlight core. He has been leading the effort to clarify our vision and working on some blueprints to make Searchlight a multi-cloud application. I believe Thuy will be a great resource for our team. Bests, -- *Trinh Nguyen* *www.edlab.xyz <https://www.edlab.xyz>*

2 2

[tripleo] TripleO Stein milestone 2 released !
by Emilien Macchi 13 Jan '19

13 Jan '19

We just released Stein Milestone 2 for TripleO, thanks all for your work: https://launchpad.net/tripleo/+milestone/stein-2 If your blueprint is done, please mark it as "Implemented" Or move it to stein-3. Bugs in progress will be moved to stein-3 automatically. By the end of the week, I'll move them myself otherwise but please do it if you can. I'll provide interesting stats at the end of Stein, where we compare numbers of fixed bugs and implemented blueprints over the cycles. Thanks, -- Emilien Macchi

1 0

[openstack-ZUN]
by Rania Adouni 13 Jan '19

13 Jan '19

hi everyone , I was trying to deploy wordpress -zun by using heat , this is the template I used "https://pastebin.com/0PGtWSVw" . now the stack create successfully the mysql image running but the wordpress image alwayes stopped and when I try to started and access to the container " openstack appcontainer exec --interactive rho-1-container apache2-foreground " i get this output : ********************************* connected to container "rho-1-container" type ~. to disconnect AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.16.0.3. Set the 'ServerName' directive globally to suppress this message AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.16.0.3. Set the 'ServerName' directive globally to suppress this message [Sun Jan 13 10:07:24.463058 2019] [mpm_prefork:notice] [pid 77] AH00163: Apache/2.4.25 (Debian) PHP/7.2.14 configured -- resuming normal operations [Sun Jan 13 10:07:24.463196 2019] [core:notice] [pid 77] AH00094: Command line: 'apache2 -D FOREGROUND' ***************************************************** and then the status of wordpress image back stopped !!!! the logs of wordpress image can be found here : https://pastebin.com/CitXk6zN thanks for any help !!

2 1

Review-Priority for Project Repos
by Surya Singh 11 Jan '19

11 Jan '19

Dear All, There are many occasion when we want to priorities some of the patches whether it is related to unblock the gates or blocking the non freeze patches during RC. So adding the Review-Priority will allow more precise dashboard. As Designate and Cinder projects already experiencing this[1][2] and after discussion with Jeremy brought this to ML to interact with these team before landing [3], as there is possibility that reapply the priority vote following any substantive updates to change could make it more cumbersome than it is worth. Teams please share your experience of using Review-Priority. [1] https://review.openstack.org/#/c/295253/ [2] https://review.openstack.org/#/c/620664/ [3] https://review.openstack.org/#/c/626824/ --- Best Regards Surya

12 17

[openstack-dev][tripleo] TripleO CI Summary: Sprint 24
by Rafael Folco 11 Jan '19

11 Jan '19

Greetings, The TripleO CI team has just completed Sprint 24 (Dec 20 thru Jan 09). The following is a summary of completed work during this sprint cycle: - Created Zuul configuration and changed repository scripts for the new Fedora 28 promotion pipeline, including container build jobs. - Replaced multinode scenarios(1-4) with standalone scenarios(1-4) jobs across TripleO projects. Also fixed missing services for standalone scenario jobs. A few changes are still “in-flight” and are close to merge. - Tempest is now successfully running on Fedora 28 standalone jobs. - Improved reproducer solution using upstream Zuul containers by moving code to an ansible role in rdo-infra/ansible-role-tripleo-ci-reproducer and automated the libvirt setup. - Created a new OVB workflow without te-broker, moved OVB repo from github to gerrit and did a PoC with new reproducer and OVB jobs. The tebroker is no longer part of the ovb workflow. The planned work for the next sprint [1] are: - Apply changes for Fedora 28 promotion pipeline in production environment to start collecting logs for container build job. - Complete transition from multinode scenarios (1-4) to standalone jobs across all TripleO projects. - Improve the new Zuul container reproducer by automating nodepool config for libvirt. - Enable CI on OVB under ovb’s new git repo in the openstack namespace. - Refactor the upstream zuul job configuration to consolidate file parameters into one repo openstack-infra/tripleo-ci. - Begin to move the RDO-Phase2 Baremetal jobs to upstream tripleo. The Ruck and Rover for this sprint are Arx Cruz (arxcruz) and Sorin Sbarnea (ssbarnea). Please direct questions or queries to them regarding CI status or issues in #tripleo, ideally to whomever has the ‘|ruck’ suffix on their nick. Notes are recorded on etherpad [2]. Thanks, rfolco [1] https://tree.taiga.io/project/tripleo-ci-board/taskboard/unified-sprint-4 [2] https://review.rdoproject.org/etherpad/p/ruckrover-sprint25

3 2

Re: Issues setting up a SolidFire node with Cinder
by Jay Bryant 11 Jan '19

11 Jan '19

Grant, Ah, if you are using a different VLAN for your storage traffic than that is likely the cause of the problem. Good luck getting the networking issue resolved. Jay On 1/11/2019 9:12 AM, Grant Morley wrote: > > Jay, > > Thanks for that info. It appears that the cinder-volume service can > speak to the SolidFire over the network but for some reason it can't > actually access it over iSCSI. I think it might be something to do > with how we are tagging / untagging VLANs. > > Thank you for your help, I think I am heading in the right direction now! > > Kind Regards, > > Grant > > On 11/01/2019 14:44, Jay Bryant wrote: >> >> Grant, >> >> Doing the boot from volume is actually quite different than attaching >> a volume to an instance. >> >> In the case that you are doing the boot from volume (assuming that >> your glance storage is not in the Solidfire) the volume is created >> and attached to where the cinder-volume service is running. Then the >> image is written into the volume. >> >> Have you verified that the host and container that is running >> cinder-volume is able to access the Solidfire backend? >> >> Jay >> >> On 1/11/2019 4:45 AM, Grant Morley wrote: >>> >>> Hi Jay, >>> >>> Thanks for the tip there. I am still having some trouble with it >>> which is really annoying. The strange thing is, I can launch a >>> volume and attach it to an instance absolutely fine. The only issue >>> I am having is literally creating this bootable volume. >>> >>> I assume creating a volume and attaching it to an instance is >>> exactly the same as creating a bootable volume minus the Nova part? >>> >>> I would just expect nothing to work if nothing could speak to the >>> SolidFire. >>> >>> Would it make a difference if the current image that is being copied >>> over to the bootable volume is in a ceph cluster? I know glance >>> should deal with it but I am wondering if the copy of the image is >>> the actual issue? >>> >>> Thanks again, >>> >>> On 11/01/2019 00:10, Jay S. Bryant wrote: >>>> >>>> Grant, >>>> >>>> So, the copy is failing because it can't find the volume to copy >>>> the image into. >>>> >>>> I would check the host and container for any iSCSI errors as well >>>> as the backend. It appears that something is going wrong when >>>> attempting to temporarily attach the volume to write the image into it. >>>> >>>> Jay >>>> >>>> On 1/10/2019 7:16 AM, Grant Morley wrote: >>>>> >>>>> Hi all, >>>>> >>>>> We are in the process of trying to add a SolidFire storage >>>>> solution to our existing OpenStack setup and seem to have hit a >>>>> snag with cinder / iscsi. >>>>> >>>>> We are trying to create a bootable volume to allow us to launch an >>>>> instance from it, but we are getting some errors in our >>>>> cinder-volumes containers that seem to suggest they can't connect >>>>> to iscsi although the volume seems to create fine on the SolidFire >>>>> node. >>>>> >>>>> The command we are running is: >>>>> >>>>> openstack volume create --image $image-id --size 20 --bootable >>>>> --type solidfire sf-volume-v12 >>>>> >>>>> The volume seems to create on SolidFire but I then see these >>>>> errors in the "cinder-volume.log" >>>>> >>>>> https://pastebin.com/LyjLUhfk >>>>> >>>>> The volume containers can talk to the iscsi VIP on the SolidFire >>>>> so I am a bit stuck and wondered if anyone had come across any >>>>> issues before? >>>>> >>>>> Kind Regards, >>>>> >>>>> >>>>> -- >>>>> Grant Morley >>>>> Cloud Lead >>>>> Absolute DevOps Ltd >>>>> Units H, J & K, Gateway 1000, Whittle Way, Stevenage, Herts, SG1 2FP >>>>> www.absolutedevops.io <http://www.absolutedevops.io/> >>>>> grant(a)absolutedevops.io <mailto:grant@absolutedevops.io> 0845 874 >>>>> 0580 >>> -- >>> Grant Morley >>> Cloud Lead >>> Absolute DevOps Ltd >>> Units H, J & K, Gateway 1000, Whittle Way, Stevenage, Herts, SG1 2FP >>> www.absolutedevops.io <http://www.absolutedevops.io/> >>> grant(a)absolutedevops.io <mailto:grant@absolutedevops.io> 0845 874 0580 > -- > Grant Morley > Cloud Lead > Absolute DevOps Ltd > Units H, J & K, Gateway 1000, Whittle Way, Stevenage, Herts, SG1 2FP > www.absolutedevops.io <http://www.absolutedevops.io/> > grant(a)absolutedevops.io <mailto:grant@absolutedevops.io> 0845 874 0580

1 0

[RHEL8-OSP15] Container Runtimes integration - Status report #7
by Emilien Macchi 11 Jan '19

11 Jan '19

Welcome to the seventh status report about the progress we make to Container Runtimes into Red Hat OpenStack Platform, version 15. You can read the previous report here: http://post-office.corp.redhat.com/archives/container-teams/2018-December/m… Our efforts are tracked here: https://trello.com/b/S8TmOU0u/tripleo-podman TL;DR =========================================== - Some OSP folks will meet in Brno next week, to work together on RHEL8/OSP15. See [1]. - We have replaced the Docker Healthchecks by SystemD timers when Podman is deployed. Now figuring out the next steps [2]. - Slow progress on the Python-based uploader (using tar-split + buildah), slowed by bugs. - We are waiting for podman 1.0 so we can build / test / ship it in TripleO CI. Context reminder =========================================== The OpenStack team is preparing the 15th version of Red Hat OpenStack Platform that will work on RHEL8. We are working together to support the future Container Runtimes which replace Docker. Done =========================================== - Implemented Podman healthchecks with SystemD timers: https://review.openstack.org/#/c/620372/ - Renamed SystemD services controlling Podman containers to not conflict with baremetal services https://review.openstack.org/#/c/623241/ - podman issues (reported by us) closed: - pull: error setting new rlimits: operation not permitted https://github.com/containers/libpod/issues/2123 - New podman version introduce new issue with selinux and relabelling: relabel failed "/run/netns": operation not supported https://github.com/containers/libpod/issues/2034 - container create failed: container_linux.go:336: starting container process caused "setup user: permission denied" https://github.com/containers/libpod/issues/1980 - "podman inspect --type image --format exists <image>" reports a not-friendly error when image doesn't exist in local storage https://github.com/containers/libpod/issues/1845 - container create failed: container_linux.go:336: starting container process caused "process_linux.go:293: applying cgroup configuration for process caused open /sys/fs/cgroup/cpuset/machine.slice/cpuset.cpus: no such file or directory" https://github.com/containers/libpod/issues/1841 - paunch/runner: test if image exists before running inspect https://review.openstack.org/#/c/619313/ - Fixing a bunch of issues with docker-puppet.py to reduce chances of race conditions. - A lot of SElinux work, to make everything working in Enforced mode. - tar-split packaging is done, and will be consumed in TripleO for the python image uplaoded In progress =========================================== - Still investigating standard_init_linux.go:203: exec user process caused \"no such file or directory\" [5]. This one is nasty and painful. It involves concurrency and we are evaluating solutions, but we'll probably end up reduce the default multi-processing of podman commands from 6 to 3 by default. - Investigating ways to gate new versions of Podman + dependencies: https://review.rdoproject.org/r/#/c/17960/ - Investigating how to consume systemd timers in sensu (healtchecks) [2] - Investigating and prototyping a pattern to safely spawn a container from a container with systemd https://review.openstack.org/#/c/620062 - Investigating how we can prune Docker data when upgrading from Docker to Podman https://review.openstack.org/#/c/620405/ - Using the new "podman image exist" in Paunch https://review.openstack.org/#/c/619313/ - Still implementing a Python-based container uploader (using tar-split and buildah) - this method will be the default later: https://review.openstack.org/#/c/616018/ - Testing future Podman 1.0 in TripleO [3] - Help the Skydive team to migrate to Podman [4] Blocked =========================================== Podman 1.0 contains a lot of fixes that we need (from libpod and vendored as well). Any comment or feedback is welcome, thanks for reading! [1] https://docs.google.com/document/d/18-1M1eSnlls6j2Op2TxyvyuqoOksxmwHOhqaD6B… [2] https://trello.com/c/g6bi5DQF/4-healthchecks [3] https://trello.com/c/2tXNLJUN/58-test-podman-10 [4] https://trello.com/c/tW935FGe/56-migrate-ansible-skydive-to-podman [5] https://github.com/containers/libpod/issues/1844 -- Emilien Macchi

1 1

[ops] OpenStack Operators Meetup, March 2019
by Chris Morgan 11 Jan '19

11 Jan '19

Dear All The OpenStack Ops Meetups team is pleased to announce preliminary details for the next Ops Meetup. The event will be held March 7th and 8th in Berlin, Germany and is being hosted by Deutsche Telekom(DT). We thank them for their kind offer to host this event. The exact venue has not yet been decided but DT has two similar facilities both reserved at present and they will be working out shortly which one works better for them. DT's proposal is here https://etherpad.openstack.org/p/ops-meetup-venue-discuss-1st-2019-berlin The meetups team will be sharing the planning docs for the technical agenda in the next few weeks. So far, there has been interest expressed in having a research track at this meetup alongside the general track. Please let us know ASAP if that is of interest. Looking forward to seeing operators in Berlin! Chris Morgan (on behalf of the ops meetups team) -- Chris Morgan <mihalis68(a)gmail.com>

1 0

[Openstack-discuss][Cinder] Fail to mount the volume on the target node
by Minjun Hong 11 Jan '19

11 Jan '19

Hi. After I installed Cinder, I have had a problem which I cannot make instances with volume storage. I created an instance on Horizon and it always has failed. Actually, I'm using Xen as the hypervisor and there was not any special log about Nova. But, in the Xen's log (/var/log/xen/bootloader.5.log), I saw the hypervisor cannot find the volume which is provided by Cinder: Traceback (most recent call last): > File "/usr/lib/xen/bin/pygrub", line 929, in <module> > raise RuntimeError, "Unable to find partition containing kernel" > RuntimeError: Unable to find partition containing kernel And, I also found something noticeable in the Cinder's log ('/var/log/cinder/cinder-volume.log' on the Block storage node): 2018-12-31 04:08:11.189 12380 INFO cinder.volume.manager > [req-93eb0ad3-6c6c-4842-851f-435e15d8639b bb1e571e4d64462bac80654b153a88c3 > 96ad10a59d114042b8f1ee82c438649a - default default] Attaching volume > 4c21b8f1-ff07-4916-9692-e74759635978 to instance > bea7dca6-fb04-4791-bac9-3ad560280cc3 at mountpoint /dev/xvda on host None. It seems that Cinder cannot receive information of the target node ('on host None' above) so, I think it can cause the problem that Cinder fails to provide the volume due to lack of the host information. Since I could not find any other logs except that log, I need more hints. Please give me some help Thanks! Regard,

2 1

[dev][keystone] Keystone Team Update - Week of 7 January 2019
by Colleen Murphy 11 Jan '19

11 Jan '19

# Keystone Team Update - Week of 7 January 2019 Happy new year! We are ramping back up following the holidays. ## News ### Cross-Project Limits Followup We are trying to close in on a stable API for limits and want to restart the discussion on what the other projects need from it. Please chime in on the thread or the linked reviews[1]. [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-January/001518.… ## Open Specs Stein specs: https://bit.ly/2Pi6dGj Ongoing specs: https://bit.ly/2OyDLTh Spec freeze is today but we have two open specs for still open for Stein, we will need to decide whether to push them or grant exceptions for them, keeping in mind there is not much time left for implementation at this point. ## Recently Merged Changes Search query: https://bit.ly/2pquOwT We merged 27 changes this week. ## Changes that need Attention Search query: https://bit.ly/2RLApdA There are 103 changes that are passing CI, not in merge conflict, have no negative reviews and aren't proposed by bots. Lance's patch bomb of doom still needs more review attention. ## Bugs Since the last report we opened 7 new bugs and closed 10. Bugs opened (7) Bug #1810485 (keystone:Medium) opened by Guang Yee https://bugs.launchpad.net/keystone/+bug/1810485 Bug #1810983 (keystone:Medium) opened by Guang Yee https://bugs.launchpad.net/keystone/+bug/1810983 Bug #1809779 (keystone:Undecided) opened by Yang Youseok https://bugs.launchpad.net/keystone/+bug/1809779 Bug #1810393 (keystone:Undecided) opened by wangxiyuan https://bugs.launchpad.net/keystone/+bug/1810393 Bug #1810278 (keystonemiddleware:Undecided) opened by Yang Youseok https://bugs.launchpad.net/keystonemiddleware/+bug/1810278 Bug #1810761 (keystonemiddleware:Undecided) opened by Hugo Kou https://bugs.launchpad.net/keystonemiddleware/+bug/1810761 Bug #1811351 (python-keystoneclient:Undecided) opened by Colleen Murphy https://bugs.launchpad.net/python-keystoneclient/+bug/1811351 Bugs closed (2) Bug #1809779 (keystone:Undecided) https://bugs.launchpad.net/keystone/+bug/1809779 Bug #1810761 (keystonemiddleware:Undecided) https://bugs.launchpad.net/keystonemiddleware/+bug/1810761 Bugs fixed (8) Bug #1805403 (keystone:Medium) fixed by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1805403 Bug #1810485 (keystone:Medium) fixed by Guang Yee https://bugs.launchpad.net/keystone/+bug/1810485 Bug #1810983 (keystone:Medium) fixed by no one https://bugs.launchpad.net/keystone/+bug/1810983 Bug #1786594 (keystone:Low) fixed by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1786594 Bug #1793374 (keystone:Low) fixed by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1793374 Bug #1810393 (keystone:Undecided) fixed by wangxiyuan https://bugs.launchpad.net/keystone/+bug/1810393 Bug #1809101 (keystonemiddleware:Undecided) fixed by leehom https://bugs.launchpad.net/keystonemiddleware/+bug/1809101 Bug #1807184 (oslo.policy:Medium) fixed by Brian Rosmaita https://bugs.launchpad.net/oslo.policy/+bug/1807184 ## Milestone Outlook https://releases.openstack.org/stein/schedule.html Spec freeze is today. The feature proposal freeze is at the end of this month, with feature freeze just five weeks after. ## Help with this newsletter Help contribute to this newsletter by editing the etherpad: https://etherpad.openstack.org/p/keystone-team-newsletter Dashboard generated using gerrit-dash-creator and https://gist.github.com/lbragstad/9b0477289177743d1ebfc276d1697b67

1 0

openstack stack fails
by Alfredo De Luca 11 Jan '19

11 Jan '19

Hi all. I installed magnum on openstack and now, after a few issue with cinder type list error, it passed that issue but now I have another one.... AuthorizationFailure: resources.kube_masters.resources[0].resources.master_wait_handle: Authorization failed. Not sure what to do nor check Any clue? Cheers -- *Alfredo*

3 37

Issues setting up a SolidFire node with Cinder
by Grant Morley 11 Jan '19

11 Jan '19

Hi all, We are in the process of trying to add a SolidFire storage solution to our existing OpenStack setup and seem to have hit a snag with cinder / iscsi. We are trying to create a bootable volume to allow us to launch an instance from it, but we are getting some errors in our cinder-volumes containers that seem to suggest they can't connect to iscsi although the volume seems to create fine on the SolidFire node. The command we are running is: openstack volume create --image $image-id --size 20 --bootable --type solidfire sf-volume-v12 The volume seems to create on SolidFire but I then see these errors in the "cinder-volume.log" https://pastebin.com/LyjLUhfk The volume containers can talk to the iscsi VIP on the SolidFire so I am a bit stuck and wondered if anyone had come across any issues before? Kind Regards, -- Grant Morley Cloud Lead Absolute DevOps Ltd Units H, J & K, Gateway 1000, Whittle Way, Stevenage, Herts, SG1 2FP www.absolutedevops.io <http://www.absolutedevops.io/> grant(a)absolutedevops.io <mailto:grant@absolutedevops.io> 0845 874 0580

3 2

[TripleO] flattening breakages
by Dan Prince 11 Jan '19

11 Jan '19

I noticed a few breakages [1][2] today with the flattening effort in the codebase. Specifically we are missing some of the 'monitoring_subscription' sections in the flattened files. We apparently have no CI on these ATM so please be careful in reviewing patches in this regard until (and if) we can add CI on this feature. I fear this type of restructuring is going to break subtle things and highlight what we don't have CI on. Some of the 3rd party vendor integration worries me in that we've got no upstream way of testing this stuff ATM. [1] https://review.openstack.org/#/c/630280/ (Ironic) [2] https://review.openstack.org/#/c/630281/ (Aodh)

1 0

[infra] Updating fedora-latest nodeset to Fedora 29
by Ian Wienand 11 Jan '19

11 Jan '19

Hi, Just a heads up that we're soon switching "fedora-latest" nodes from Fedora 28 to Fedora 29 [1] (setting up this switch took a bit longer than usual, see [2]). Presumably if you're using "fedora-latest" you want the latest Fedora, so this should not be unexpected :) But this is the first time we're making this transition with the "-latest" nodeset, so please report any issues. Thanks, -i [1] https://review.openstack.org/618673 [2] http://lists.openstack.org/pipermail/openstack-discuss/2019-January/001530.…

2 1

[cinder] volume encryption performance impact
by Dave Holland 11 Jan '19

11 Jan '19

Hello, I've just started investigating Cinder volume encryption using Queens (RHOSP13) with a Ceph/RBD backend and the performance overhead is... surprising. Some naive bonnie++ numbers, comparing a plain vs encrypted volume: plain: write 1400MB/s, read 390MB/s encrypted: write 81MB/s, read 83MB/s The encryption was configured with: openstack volume type create --encryption-provider nova.volume.encryptors.luks.LuksEncryptor --encryption-cipher aes-xts-plain64 --encryption-key-size 256 --encryption-control-location front-end LuksEncryptor-Template-256 Does anyone have a similar setup, and can share their performance figures, or give me an idea of what percentage performance impact I should expect? Alternatively: is AES256 overkill, or, where should I start looking for a misconfiguration or bottleneck? Thanks in advance. Dave -- ** Dave Holland ** Systems Support -- Informatics Systems Group ** ** 01223 496923 ** Wellcome Sanger Institute, Hinxton, UK ** -- The Wellcome Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.

4 4

[dev][Tacker] Implementing Multisite VNFFG
by 이호찬 11 Jan '19

11 Jan '19

Dear Tacker folks, Hello, I'm interested in implementing multisite VNFFG in Tacker project. As far as I know, current single Tacker controller can manage multiple Openstack sites (Multisite VIM), but it can create VNFFG in only singlesite, so it can't create VNFFG across multisite. I think if multisite VNFFG is possible, tacker can have more flexibility in managing VNF and VNFFG. In the current tacker, networking-sfc driver is used to support VNFFG, and networking-sfc uses port chaining to construct service chain. So, I think extending current port chaining in singleiste to multisite can be one solution. Is there development process about multisite VNFFG in tacker project? Otherwise, I wonder that tacker is interested in this feature. I want to develop this feature for Tacker project if I can. Yours sincerely, Hochan Lee.

3 2

[congress][infra] override-checkout problem
by Eric K 11 Jan '19

11 Jan '19

The congress-tempest-plugin zuul jobs against stable branches appear to be working incorrectly. Tests that should fail on stable/rocky (and indeed fails when triggered by congress patch [1]) are passing when triggered by congress-tempest-plugin patch [2]. I'd assume it's some kind of zuul misconfiguration in congress-tempest-plugin [3], but I've so far failed to figure out what's wrong. Particularly strange is that the job-output appears to show it checking out the right thing [4]. Any thoughts or suggestions? Thanks so much! [1] https://review.openstack.org/#/c/629070/ http://logs.openstack.org/70/629070/4/check/congress-devstack-api-mysql/874… The two failing z3 tests should indeed fail because the feature was not available in rocky. The tests were introduced because for some reason they pass in the job triggered by a patch in congress-tempest-plugin. [2] https://review.openstack.org/#/c/618951/ http://logs.openstack.org/51/618951/3/check/congress-devstack-api-mysql-roc… [3] https://github.com/openstack/congress-tempest-plugin/blob/master/.zuul.yaml… [4] http://logs.openstack.org/51/618951/3/check/congress-devstack-api-mysql-roc… shows congress is checked out to the correct commit at the top of the stable/rocky branch.

2 1

[senlin] Meeting today at 0530 UTC
by Duc Truong 10 Jan '19

10 Jan '19

Everyone, Our regular Senlin meetings are resuming today. This is an even week so the meeting will be happening on Friday at 530 UTC. Regards, Duc

1 0

[tripleo] OVB 2.0-dev branch merged to master
by Ben Nemec 10 Jan '19

10 Jan '19

In preparation for importing OVB to Gerrit, the 2.0-dev branch was merged back to master. If the 2.0 changes break you, please use the stable/1.0 branch instead, which was created from the last commit before 2.0-dev was merged. -Ben

1 0