- openstack-discuss - lists.openstack.org

[first contact] Cancelling Next Meeting
by Kendall Nelson 19 Dec '18

19 Dec '18

Hello! During the meeting yesterday, we voted to cancel our next meeting which would have been January 1 st. After that we will resume our regularly scheduled programming :) Have a good rest of the year everyone! -Kendall (diablo_rojo)

1 0

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

19 Dec '18

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 Hope to see a lot of you there for the last meeting during 2018! 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

Failed live migration and duplicate attachments
by Torin Woltjer 19 Dec '18

19 Dec '18

After doing live migrations for some instances, and those migrations failing, the attached volumes show duplicates of the same attachment. This is the error message I get when the migration fails: https://pastebin.com/raw/3mxSVnRR openstack volume list shows the volume is attached to the instance twice. | a424fd41-a72f-4099-9c1a-47114d43c1dc | zktech-wpdb1 | in-use | 50 | Attached to ead8ecc3-f473-4672-a67b-c44534c6042d on /dev/vda Attached to ead8ecc3-f473-4672-a67b-c44534c6042d on /dev/vda How do I remove the duplicate attachment, and why could the live migration be failing in the first place? Not all migrations fail, but sometimes they do and I have multiple volumes with duplicate attachments. Torin Woltjer Grand Dial Communications - A ZK Tech Inc. Company 616.776.1066 ext. 2006 www.granddial.com

2 2

[swift]Putting Swift storage disks to sleep
by Vedartham Bharath 19 Dec '18

19 Dec '18

Hi all, I am an undergraduate currently working on a research project which involves OpenStack Swift. In my project, I have set up Swift to run on 4 disks. I want to put down one of the hard disks to sleep i.e reduce the spin. I am using the hdparm tool in Linux to do this. The problem is that the disk automatically wakes back up after being put to sleep. I have found out that this is due to the fact that all the storage disks of Swift have to be mounted with XFS and the sync processes of XFS require the disk to wake up. I was wondering if there is a way to use a disk without a filesystem in Swift and if not, are there any other ways of putting storage disks in Swift to sleep? I have made sure the object replicator and object auditor do not wake the disk up. My goal is to be able to control putting the disk to sleep and waking it up when I need. Details of set up: Software: OpenStack Swift Newton with Keystone OS: Ubuntu 16.04 Thanks!

2 2

[nova] When can/should we remove old nova-status upgrade checks?
by Matt Riedemann 19 Dec '18

19 Dec '18

Questions came up in review [1] about dropping an old "nova-status upgrade check" which relies on using the in-tree placement database models for testing the check. The check in question, "Resource Providers", compares the number of compute node resource providers in the nova_api DB against the number of compute nodes in all cells. When the check was originally written in Ocata [2] it was meant to help ease the upgrade where nova-compute needed to be configured to report compute node resource provider inventory to placement so the scheduler could use placement. It looks for things like >0 compute nodes but 0 resource providers indicating the computes aren't reporting into placement like they should be. In Ocata, if that happened, and there were older compute nodes (from Newton), then the scheduler would fallback to not use placement. That fallback code has been removed. Also in Ocata, nova-compute would fail to start if nova.conf wasn't configured for placement [3] but that has also been removed. Now if nova.conf isn't configured for placement, I think we'll just log an exception traceback but not actually fail the service startup, and the node's resources wouldn't be available to the scheduler, so you could get NoValidHost failures during scheduling and need to dig into why a given compute node isn't being used during scheduling. The question is, given this was added in Ocata to ease with the upgrade to require placement, and we're long past that now, is the check still useful? The check still has lots of newton/ocata/pike comments in it, so it's showing its age. However, one could argue it is still useful for base install verification, or for someone doing FFU. If we keep this check, the related tests will need to be re-written to use the placement REST API fixture since the in-tree nova_api db tables will eventually go away because of extracted placement. The bigger question is, what sort of criteria do we have for dropping old checks like this besides when the related code, for which the check was added, is removed? FFU kind of throws a wrench in everything, but at the same time, I believe the prescribed FFU steps are that online data migrations (and upgrade checks) are meant to be run per-release you're fast-forward upgrading through. [1] https://review.openstack.org/#/c/617941/26/nova/tests/unit/cmd/test_status.… [2] https://review.openstack.org/#/c/413250/ [3] https://github.com/openstack/nova/blob/stable/ocata/nova/compute/manager.py… -- Thanks, Matt

5 5

Devstack failure “Oslo.concurrency”
by d.lake＠surrey.ac.uk 19 Dec '18

19 Dec '18

Hello I’m trying to rebuild a Devstack system on an identical machine to a working system from August. Same base OS (Centos 7.5), same simple local.conf. But this system is failing with Oslo.concurrency not at 2.26. This is bizarre because when I update Oslo.concurrency using pip, I’m given 2.29. Yet something in Devstack insists on going back to 2.25.1 despite knowing that I need 2.26. What is most annoying is that I thought that by keeping all the basic build identical I would save myself the pain that is OpenStack installation. How do I work around this please? If I clear out /usr/lib/python2.7/site-packages, this doesn’t seem to help at all. Thanks David Sent from my iPhone

3 3

[tripleo][openstack-ansible] collaboration on os_tempest role update IV - Dec 19, 2018
by Chandan kumar 19 Dec '18

19 Dec '18

Hello, As 2018 is about to end, Here is the last updates on collaboration on os_tempest[1] role between TripleO and OpenStack-Ansible projects. Things got merged: os_tempest: [1.] Create basic doc structure - https://review.openstack.org/623512 [2.] Added support for installing tempestconf from distro - https://review.openstack.org/622999 [3.] Revert "Use tempest run for generating subunit results" - https://review.openstack.org/625070 Revert reason: when --subunit flag is used with tempest run, either the tests passes or fails, It was always returning success. We are investigating and working on the same to fix it. python-tempestconf: [4.] Handle Forbidden exception when creating role - https://review.openstack.org/#/c/624411/ [5.] Adapt python-tempestconf to python3 - https://review.openstack.org/#/c/622343/ [6.] Add argument which allows users to add extensions - https://review.openstack.org/620379 Works still in progress: os_tempest: [1.] Better tempest black and whitelist management - https://review.openstack.org/621605 [2.] Update all plugin urls to use https rather than git - https://review.openstack.org/625670 [3.] Remove octavia in favor of octavia-tempest-plugin - https://review.openstack.org/625828 [4.] Use tempest_tempestconf_profile for handling named args - https://review.openstack.org/623187 [5.] Add tempestconf_git_url var for tempestconf testing - https://review.openstack.org/626092 [6.] Added support for installing python-tempestconf from git - https://review.openstack.org/625904 python-tempestconf: [7.] Add profile argument - https://review.openstack.org/621567 Summary: While working on adding support of python-tempestconf profile feature support in os_tempest, we found that we cannot test tempestconf patches with os_tempest as tempestconf is getting installed by pip, that's why we were working on adding support for the same to install it from git. Thanks to evrardjp, odyssey4me, jrosser, arxcruz, mnaser, kopecmartin for helping us on our silly queries. Upcoming two weeks: * Complete existing work in progress patches. Note: We are sending next update on 09th Jan, 2019 as Holidays started. Here is the third 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/2018-December/000831… Thanks, Chandan Kumar

2 1

[requirements] adding pre-commit to requirements blacklist (skip check)
by Sorin Sbarnea 19 Dec '18

19 Dec '18

It seems that the list of linters from the the blacklist.txt file is a bit outdated and missing things like: pre-commit bashate ansilbe-lint ansible-review I discovered that while trying to enable pre-commit on tripleo-upgrades and discovered that check-requirements jobs was failing. If someone can help me merge that it would be great https://review.openstack.org/#/c/626000/ <https://review.openstack.org/#/c/626000/> My review contains only pre-commit because that was the one I really needed but looking at the file it seems it may be useful to add all known https://github.com/openstack/requirements/blob/master/blacklist.txt <https://github.com/openstack/requirements/blob/master/blacklist.txt> Thanks Sorin

1 0

[dev][ops][monasca] Additional meeting time
by Bedyk, Witold 19 Dec '18

19 Dec '18

Hello everyone, Monasca team has decided to hold additional team meetings on Thursdays, 7am UTC [1]. This way we would like to offer more suitable meeting time for developers and operators from Asia/Australia. We would like to try this new format of `double meetings` for some time and we'll keep it if there is demand. Everyone interested is warmly invited to join. If you have any topics you would like to discuss, please add them to the agenda [2]. The next meetings are planned today 1500 UTC and tomorrow 0700 UTC. See you there Witek [1] http://eavesdrop.openstack.org/#Monasca_Team_Meeting [2] https://etherpad.openstack.org/p/monasca-team-meeting-agenda

1 0

openstack magnum on queens kubectl errors
by Ignazio Cassano 19 Dec '18

19 Dec '18

Hello I've just installe openstack magnum on queens and I deployed a kubernets cluster. Heat stack terminated successfully but running kubectl describe node, at the end it reports: Allocated resources: (Total limits may be over 100 percent, i.e., overcommitted.) Resource Requests Limits -------- -------- ------ cpu 0 (0%) 0 (0%) memory 0 (0%) 0 (0%) ephemeral-storage 0 (0%) 0 (0%) Events: Type Reason Age >From Message ---- ------ ---- ---- ------- Warning FailedNodeAllocatableEnforcement 4s (x71 over 70m) kubelet, kubecerts-pvfagyxq6gf6-minion-0 Failed to update Node Allocatable Limits "": failed to set supported cgroup subsystems for cgroup : Failed to set config for supported subsystems : failed to write 2089619456 to memory.limit_in_bytes: write /rootfs/var/lib/containers/atomic/kubelet.0/rootfs/sys/fs/cgroup/memory/memory.limit_in_bytes: invalid argument Anyone can help me ? I read some patches has been applyed on queens for this issue: https://bugs.launchpad.net/magnum/+bug/1763405 but , anycase, I am facing the issue. Regards Ignazio

1 0

[scientific-sig] IRC meeting today, 1100UTC: 2018 retrospective, 2019 conferences, etc
by Stig Telfer 19 Dec '18

19 Dec '18

Hi All - We have an IRC meeting today in #openstack-meeting at 1100UTC - about 90 minutes time. Everyone is welcome. The agenda is here: https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_December_19th_20… Today we’d like to cover the activities of the SIG in 2018, and what we would like to do in 2019. I thought it would also be useful to gather together CFPs and announcements for relevant conferences for the year to come. Cheers, Stig

1 0

Watcher team meeting
by Чадин Александр Сергеев ич 19 Dec '18

19 Dec '18

Watcher team, I propose to shift today’s meeting from 08:00 UTC to 08:45 UTC. Alex

1 0

[dev] [tc][all] TC office hours is started now on #openstack-tc
by Ghanshyam Mann 19 Dec '18

19 Dec '18

Hello everyone, TC office hour is started on #openstack-tc channel. Feel free to reach to us for anything you want discuss/input/feedback/help from TC. - gmann & TC

1 0

[octavia][lbaas] Octavia v1 API will be retired along with neutron-lbaas in 2019.
by Michael Johnson 18 Dec '18

18 Dec '18

Hi Octavia folks, I wanted to send a reminder e-mail out that we are planning to retire both neutron-lbaas and the Octavia v1 API in September 2019 or the OpenStack "U" release, whichever comes first. The Octavia v1 API was used by the neutron-lbaas Octavia provider driver and was not an end-user API. The Octavia v1 API is a proprietary API and is not compatible with the LBaaS v2 API specification or any other LBaaS API specification. If you have questions about this deprecation cycle please see the FAQ wiki: https://wiki.openstack.org/wiki/Neutron/LBaaS/Deprecation If you have questions or concerns not covered by the FAQ, please reach out to the Octavia team either by using the "[octavia]" subject prefix on this mailing list or in our IRC channel #openstack-lbaas. Have a great rest of 2018 and we look forward to working with you in the new year! Michael

1 0

[octavia] Octavia weekly IRC meeting is cancelled December 26th.
by Michael Johnson 18 Dec '18

18 Dec '18

Hello OpenStack folks! Due to the number of folks taking vacation time next week, we are cancelling the December 26th Octavia IRC meeting. We will resume our regular schedule starting January 2nd, 2019. I look forward to working with you all in the new year! Michael

1 0

[neutron] CI meetings cancelled
by Slawomir Kaplonski 18 Dec '18

18 Dec '18

Hi, Due to Christmas and New Year, next 2 Neutron CI meetings are cancelled. Next CI meeting will be on 8.01.2019. — Slawek Kaplonski Senior software engineer Red Hat

1 0

[openstack-dev] [keystone] Keystone support of Multi-Factor Authentication ?
by Waines, Greg 18 Dec '18

18 Dec '18

Keystone guys, What is the current status of Keystone supporting Multi-Factor Authentication ? https://specs.openstack.org/openstack/keystone-specs/specs/keystone/rocky/m… * Does this work provide true MFA ? * Is this work still active ? Are there other solutions for MFA for OpenStack Keystone ? Greg.

3 2

Re: [openstack-dev] [nova] Metadata API cross joining "instance_metadata" and "instance_system_metadata"
by Matt Riedemann 18 Dec '18

18 Dec '18

On 10/22/2018 11:25 AM, Sergio A. de Carvalho Jr. wrote: > While troubleshooting a production issue we identified that the Nova > metadata API is fetching a lot more raw data from the database than > seems necessary. The problem appears to be caused by the SQL query used > to fetch instance data that joins the "instance" table with, among > others, two metadata tables: "instance_metadata" and > "instance_system_metadata". Below is a simplified version of this query > (I've added the full query at the end of this message for reference): Coming back on this thread [1], I've got a partial fix up which I'm hoping will help: https://review.openstack.org/#/c/624778/ That will avoid joining on some other tables depending on your configuration. It would be great if you could see if that helps resolve your issue. I think you just reverted https://review.openstack.org/#/c/276861/ as a workaround but it would be good to know if a more permanent fix (mine) gets you similar, or at least satisfactory, results. [1] http://lists.openstack.org/pipermail/openstack-dev/2018-October/thread.html… -- Thanks, Matt

2 3

[kuryr] Meetings canceled due to holidays, we'll be back on Jan 7th
by Daniel Mellado 18 Dec '18

18 Dec '18

Hi kuryrs! We'll be having a break from our weekly meetings due to Christmas' holidays! First weekly meeting will be Monday January 7th. If there are any questions, please feel free to reach out to me or post to the mailing list, as well as pinging us on #openstack-kuryr. Best! Daniel

1 0

Openstack Magnum
by Alfredo De Luca 18 Dec '18

18 Dec '18

Hi all. Just installed *openstack* and *magnum* with *ansible-openstack AIO.* All works well except magnum itself. When I click on the dashboard on* Container Infra *then C*lusters or clusters templates *I get the following errors: *Error: *Unable to retrieve the clusters. *Error: *Unable to retrieve the stats. - Not sure why. Any clue? Cheers -- *Alfredo*

3 8

[publiccloud]Choice of deployment tools
by Cody 18 Dec '18

18 Dec '18

Hello stackers, What deployment tools would be of your choice for deploying a public IaaS with an initial size of 200~300 nodes? Would TripleO be suitable for this cluster size? Thank you very much. Wish you all a happy holiday season! Best regards, Cody

5 7

[neutron][qos] IRC meeting Jan 1, 2019
by Rodolfo Alonso 18 Dec '18

18 Dec '18

Hello: Next meeting on January 1, 2019, is canceled. The next meeting of the Neutron QoS subteam will be on January 15, 2019. Regards.

1 0

Denver Open Infrastructure Summit CFP Open
by Ashlee Ferguson 18 Dec '18

18 Dec '18

Hi everyone, The OpenStack Summit has a new name! To reflect our evolving community, the first Open Infrastructure Summit <https://www.openstack.org/summit/denver-2019/> will be held in Denver, Colorado April 29 - May 1, 2019. The Call for Presentations (CFP) is now open, and the deadline to submit your presentations, panels, and workshops <https://www.openstack.org/summit/denver-2019/call-for-presentations> is Wednesday, January 23 at 11:59pm PT (January 24 at 7:59am UTC). Here are the Summit Tracks <https://www.openstack.org/summit/denver-2019/summit-categories> as well as the Programming Committee nomination form <https://openstackfoundation.formstack.com/forms/openstackdenver2019_program…> if you are interested in helping shape the content of the Summit. The content submission process for the Forum and Project Teams Gathering will be managed separately in the upcoming months. SUBMIT YOUR PRESENTATION <https://www.openstack.org/summit/denver-2019/call-for-presentations> New for the Denver Summit: Based on previous track chair and attendee feedback, we have added / updated three Tracks: Security, Getting Started, Open Development. You can find the Track descriptions here <https://www.openstack.org/summit/denver-2019/summit-categories>. In addition to OpenStack, you’ll see the OSF pilot projects —Airship, Kata Containers, StarlingX and Zuul —front and center alongside Ansible, Cloud Foundry, Docker, Kubernetes, and many more. The Open Infrastructure Summit, has evolved to recognize our diverse audience, and to signal to the market that the event is relevant for all IT infrastructure decision makers. We are working with the Programming Committee members to share the topics they’re looking for within each Track. Stay tuned on Superuser as we post these recommendations. If you’re interested in influencing the Summit content, apply to be a Programming Committee member <https://openstackfoundation.formstack.com/forms/openstackdenver2019_program…>*, where you can also find a full list of time requirements and expectations. Nominations will close on January 4, 2019. *OSF Staff will serve as the Programming Committee for the Getting Started Track. Denver Summit registration and sponsor sales are currently open. Learn more <https://www.openstack.org/summit/denver-2019> Please email speakersupport(a)openstack.org <mailto:speakersupport@openstack.org> with any questions or feedback. Cheers, Ashlee Ashlee Ferguson OpenStack Foundation ashlee(a)openstack.org

1 0

Firefox context search text across openstack related websites like codesearch, logstash, launchpad
by Sorin Sbarnea 18 Dec '18

18 Dec '18

As many of us have to search for pieces of text on many places, like codesearch, logstash,.... I invested some time in making this possible with a right-click. Warning: requires Firefox extension. Details https://github.com/openstack/coats#context-search-for-firefox <https://github.com/openstack/coats#context-search-for-firefox> I hope it would make your life easier. PS. Improvements on the search engines definition files are welcomed, on Gerrit :) Cheers, Sorin Sbarnea

1 0

[TripleO] flattening tripleo-heat-templates: what about pacemaker?
by Cédric Jeanneret 18 Dec '18

18 Dec '18

Hello folks, While working on the service flattening in t-h-t, I have some question regarding the pacemaker things. If we take rabbitmq: - we have rabbitmq things in docker/services - we have rabbitmq things in puppet/services - we have rabbitmq things in docker/services/pacemaker - we have rabbitmq things in puppet/services/pacemaker If the plain services are easy to flatten, the pacemaker part is more annoying, at least on the naming/location. I see the following possibilities: - create a deployment/pacemaker and move all pacemaker-related things in there - name files something like rabbitmq-pacemaker-foo.yaml and push them in deployment/rabbitmq Both look valid. And both might have their downsides. Any advice, idea, feeling on that? Also, regarding the workflow: do we do that flattening in one, or two passes? i.e. we can move all rabbitmq related code at once, or only the plain service, and do a second patch for the pacemaker things. Here again, both look valid, but I'm more in the "2 passes" idea. So... yeah, I'd like to get some feedback on that in order to do things right, and avoid monkey-patching because paths/naming aren't good ;). Thanks! Cheers, C. -- Cédric Jeanneret Software Engineer DFG:DF

2 1