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

[all] Is the Denver Summit save?
by Frank Kloeker 29 Jan '19

29 Jan '19

Good morning, just a question, out of curiosity: Is the Denver Summit save? I mean, we received a lot of breaking news in the morning, that Huawei is charged in court and is doing a lot of bad things (i.e. stolen a robotics arm). I don't want to bring in any political discussions. But surely as you know, Huawei is one of the top contributor to our Open Source project. They work hard and do not need to steal things. Is there any chance that one of our friends will be caught next? At the summit between political fronts? I feel a little uncomfortable with it. We are an open community and should clarify this inconsistency. kind regards Frank

6 8

[kayobe] Proposing Pierre Riteau for core
by Mark Goddard 29 Jan '19

29 Jan '19

Hi, I'd like to propose Pierre Riteau (priteau) for core. He has contributed a number of good patches and provided some thoughtful and useful reviews. Cores, please respond +1 or -1. Mark

3 3

openstack-summit-Denver-2019
by Najeh Nafti 29 Jan '19

29 Jan '19

Dear OpenStack Project team, My name is Najeh Nafti. I am a master degree student from Tunisia North Africa. I'm currently working for a thesis project based on OpenStack, but i didn't find the need resources that can help me to realize my project. I would like to request your approval to attend OpenStack-summit-Denver-2019 with your financial support. This event is a unique opportunity for me to gain knowledge and insight I need to solve daily challenges and to help me contribute to the overall goals of my study. Although I understand there might be financial constraints in sending me to this event, I believe it will be an investment that results in immediate and longer term benefits. My objectives in attending this event are: - To increase knowledge in my discipline area. - To network with my peers from all over the world to share information, learn how they are solving similar problems, and collaborate to find innovative approaches. OpenStack-summit-Denver-2019 would be a valuable experience for me and one that would benefit my thesis. Thank you for your consideration. Looking forward to hearing from you. Najeh.

2 2

[ops] ops meetups team meeting 2019-1-22 minutes
by Chris Morgan 29 Jan '19

29 Jan '19

Meeting ended Tue Jan 22 15:48:39 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 10:48 AM Minutes: http://eavesdrop.openstack.org/meetings/ops_meetup_team/2019/ops_meetup_tea… 10:48 AM Minutes (text): http://eavesdrop.openstack.org/meetings/ops_meetup_team/2019/ops_meetup_tea… 10:48 AM Log: http://eavesdrop.openstack.org/meetings/ops_meetup_team/2019/ops_meetup_tea… Next meeting in 40 minutes on #openstack-operators see you there! Chris -- Chris Morgan <mihalis68(a)gmail.com>

1 0

[placement] update 19-03
by Chris Dent 29 Jan '19

29 Jan '19

HTML: https://anticdent.org/placement-update-19-03.html Hello, here's a quick placement update. This will be just a brief summary rather than usual tome. I'm in the midst of some other work. # Most Important Work to complete and review changes to deployment to support extracted placement is the main thing that matters. The next placement extraction status checkin will be 17.00 UTC, February 6th. # What's Changed * Changes to allow database status checks in `placement-status upgrade check` have either merged or will soon. These combine with online data migrations to ensure that the state of an upgraded installations has healthy consumers and resource providers. * libvirt vgpu reshaper [code](https://review.openstack.org/#/c/599208/) is ready for review and has an associated functional test. When that stuff merges the main remaining extraction-related tasks are in the deployment tools. * [os-resource-classes](https://pypi.org/p/os-resource-classes) `0.2.0` was released, adding the `PCPU` class. # Bugs * Placement related [bugs not yet in progress](https://goo.gl/TgiPXb): 14. -1. * [In progress placement bugs](https://goo.gl/vzGGDQ) 16. Stable. # Main Themes ## Nested * <https://review.openstack.org/#/q/topic:bp/reshape-provider-tree+status:open> * <https://review.openstack.org/#/q/topic:bp/bandwidth-resource-provider> * <https://review.openstack.org/615695> ## Extraction * [etherpad](https://etherpad.openstack.org/p/placement-extract-stein-5) Deployment related changes: * [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) and [kolla upgrade](https://review.openstack.org/#/q/topic:upgrade-placement) [Delete placement from nova](https://review.openstack.org/618215). # Other Please refer to [last week](https://anticdent.org/placement-update-19-02.html) for lots of pending changes. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

3 2

[openstack-helm] Support for Docker Registry with authentication turned on ?
by Waines, Greg 29 Jan '19

29 Jan '19

Hey ... We’re relatively new to openstack-helm. We are trying to use the openstack-helm charts with a Docker Registry that has token authentication turned on. With the current charts, there does not seem to be a way to do this. I.e. there is not an ‘imagePullSecrets’ in the defined pods/containers or in the defined serviceAccounts . Our thinking would be to add a default imagePullSecret to all of the serviceAccounts defined in the openstack-helm serviceaccount template. OR is there another way to use openstack-helm charts with a Docker Registry with authentication turned on ? Any info is appreciated, Greg / Angie / Jerry.

2 2

[tripleo][openstack-ansible] collaboration on os_tempest role update VIII - Jan 29, 2019
by Chandan kumar 28 Jan '19

28 Jan '19

Hello, Here is the 8 th update (Jan 22 to Jan 29, 2019) on collaboration on os_tempest[1] role between TripleO and OpenStack-Ansible projects. Things got merged: openstack-ansible-tests: * Setup clouds.yaml on tempest node - https://review.openstack.org/631794 * Gather all facts while preparing hosts - https://review.openstack.org/632609 * Gather different port status on different hosts - https://review.openstack.org/633179 TripleO: * Added requirements for integrating os_tempest role - https://review.openstack.org/628421 * Use os_tempest for running tempest on standalone - https://review.openstack.org/628415 Summary: We have almost completed the work of integrating os_tempest with tripleo-ci, The final patch is about to land by EOD or by tomorrow and here is the latest result: http://logs.openstack.org/00/627500/76/check/tripleo-ci-centos-7-standalone… Things In-Progress: os_tempest: * Added tempest.conf for heat_plugin - https://review.openstack.org/632021 * Use tempest_cloud_name in tempestconf - https://review.openstack.org/631708 * Always generate stackviz irrespective of tests pass or fail - https://review.openstack.org/631967 * Update cirros image from 3.5 to 3.6 - https://review.openstack.org/633208 * Added dependencies of os_tempest role - https://review.openstack.org/632726 * Only init a workspace if doesn't exists - https://review.openstack.org/633549 * Add support for aarch64 images - https://review.openstack.org/620032 * Adds tempest run command with --test-list option - https://review.openstack.org/631351 * Add telemetry distro plugin install for aodh - https://review.openstack.org/632125 TripleO: * Set keystone specific vars for os_tempest from clouds.yaml - https://review.openstack.org/633185 * Run tempest using os_tempest role in standalone job - https://review.openstack.org/627500 Summary: Currently, os_tempest tempest.scenario.test_server_basic_ops.TestServerBasicOps.test_server_basic_ops tests are failing while ssh into cirros image with ssh timeout only on CentOS7. It might be a floating Ip/networking issue. Any help on this appreciated. Failure: http://logs.openstack.org/08/633208/8/check/openstack-ansible-functional-ce… We also find other issues on centOS 7 jobs, work in progress to fix it * Use venv_packages_to_symlink to symlink to import libvirt-python - https://review.openstack.org/633474 * Ensure selinux bindings are linked into the venv - https://review.openstack.org/#/c/633513/ Goal of this week: We will be working on fixing the os_tempest gate and get above patches merged. We are working on fixing it. Thanks to jrosser and odyssey4me for helping us in debugging centOS7 issues while trying to reproduce the issue locally. Here is the 7th 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/001946.… Thanks, Chandan Kumar

1 0

[Cyborg] No IRC meeting on Jan 29 and Feb 05
by Li Liu 28 Jan '19

28 Jan '19

Hi Team, The IRC meetings for the next couple weeks will be canceled due to Chinese New Year and resumed on the week of Feb 12th. Happy Chinese New Year! 新年快乐！ -- Thank you Regards Li Liu

1 0

[Zun] No team meeting at Jan 29 and Feb 05
by Hongbin Lu 28 Jan '19

28 Jan '19

FYI ---------- Forwarded message --------- From: Ji.Wei <17366060309(a)163.com> Date: Mon, Jan 28, 2019 at 9:18 PM Subject: Zun irc meeting suspension notice To: hongbin <hongbin034(a)gmail.com> Hello everyone: Zun's irc meeting will be suspended during the Chinese traditional festival, Chinese New Year (29 January 2019 and 05 February 2019). If you have any questions, please contact me (17366060309(a)163.com). Thank you for your contribution to Zun in the past year :) -- This message was sent from Launchpad by Ji.Wei (https://launchpad.net/~jiwei) to each member of the zun-drivers team using the "Contact this team" link on the zun-drivers team page (https://launchpad.net/~zun-drivers). For more information see https://help.launchpad.net/YourAccount/ContactingPeople

1 0

[tc] Technical Committee status update
by Doug Hellmann 28 Jan '19

28 Jan '19

This is a summary of work being done by the Technical Committee members. The full list of active items is managed in the wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker We also track TC objectives for the cycle using StoryBoard at: https://storyboard.openstack.org/#!/project/923 == Recent Activity == Project updates: * Renat Akhmerov has replaced Dougal Matthews as Mistral PTL ** https://review.openstack.org/#/c/625537/ * The Sahara team added repositories for extracting their plugins ** https://review.openstack.org/#/c/628210/ * The murano-deployment repository was retired ** https://review.openstack.org/#/c/628860/ * The assert:supports-upgrade tag was added to watcher ** https://review.openstack.org/#/c/619470/ * The openstack-virtual-baremetal repository was added to the TripleO team ** https://review.openstack.org/#/c/631028/ * The charm-interface-cinder-backend repository was added to the OpenStack Charms project ** https://review.openstack.org/#/c/631251/ * The puppet-stackalytics repository has been retired ** https://review.openstack.org/#/c/631820/ Other updates: * Zane drafted a resolution about how we should choose which Python versions to track ** https://review.openstack.org/#/c/613145/ * Sean updated the PTI to reflect the runtimes supported for Stein ** https://review.openstack.org/#/c/611080/ * Thierry and Chris drafted a description of the role of the TC ** https://review.openstack.org/#/c/622400/ * I added a "house rule" for approving simple documentation changes without requiring a full TC vote ** https://review.openstack.org/#/c/625005/ * Jeremy updated the technical vision to cover hiding implementation details ** https://review.openstack.org/#/c/628181/ == TC Meetings == The most recent TC meeting was on 3 January. Logs were sent to the mailing list after the meeting. * http://lists.openstack.org/pipermail/openstack-discuss/2019-January/001376.… The next TC meeting will be 7 February @ 1400 UTC in #openstack-tc. See http://eavesdrop.openstack.org/#Technical_Committee_Meeting for details == Ongoing Discussions == Frank has proposed a list of translators as ATCs for the i18n team. * https://review.openstack.org/#/c/633398/ Ganshyam is working on updating the technical vision to cover feature discovery. * https://review.openstack.org/#/c/621516/ Jean-Philippe has proposed adding openSUSE to the list of supported platforms in the PTI. * https://review.openstack.org/#/c/633460/ == Contacting the TC == The Technical Committee uses a series of weekly "office hour" time slots for synchronous communication. We hope that by having several such times scheduled, we will have more opportunities to engage with members of the community from different timezones. Office hour times in #openstack-tc: - 09:00 UTC on Tuesdays - 01:00 UTC on Wednesdays - 15:00 UTC on Thursdays If you have something you would like the TC to discuss, you can add it to our office hour conversation starter etherpad at: https://etherpad.openstack.org/p/tc-office-hour-conversation-starters Many of us also run IRC bouncers which stay in #openstack-tc most of the time, so please do not feel that you need to wait for an office hour time to pose a question or offer a suggestion. You can use the string "tc-members" to alert the members to your question. You will find channel logs with past conversations at http://eavesdrop.openstack.org/irclogs/%23openstack-tc/ If you expect your topic to require significant discussion or to need input from members of the community other than the TC, please start a mailing list discussion on openstack-discuss at lists.openstack.org and use the subject tag "[tc]" to bring it to the attention of TC members. -- Doug

1 0