May 2019 - openstack-discuss - lists.openstack.org

[watcher] Question about baremetal node support in nova CDM
by Matt Riedemann 29 May '19

29 May '19

While working on [1] I noticed that the NovaHelper.get_compute_node_by_hostname method is making 3 API calls to get the details about a hypervisor: 1. listing hypervisors and then filtering client-side by the compute service host - this fails if there is not exactly one hypervisor for the given compute service host name 2. search for the hypervisor given the hypervisor_hostname to get the id 3. get the hypervisor details using the id My patch is collapsing 2 and 3 into a single API call to nova. The question I had was if we need that first call. For all non-ironic baremetal nodes, the compute service host and node hypervisor_hostname should be identical, so technically we could just search for the hypervisor details with the compute service hostname. Only in the case of ironic would we potentially get more than one hypervisor (node) for a single compute service (host). I don't think the nova CDM code really handles baremetal instances at all because it's not handling this kind of host:node 1:M cardinality elsewhere in the code, but you also can't do most things to optimize like cold or live migrating baremetal instances. I'm not exactly sure how Watcher deals with ironic but I know there is the separate BaremetalClusterDataModelCollector so I'm assuming watcher just optimizes for baremetal outside of the nova compute API? If this is true, then we can get rid of that first API all noted above and I don't need to write a nova spec to add a host filter parameter to the GET /os-hypervisors/detail API. [1] https://review.opendev.org/#/c/661121/2/watcher/common/nova_helper.py@65 -- Thanks, Matt

3 9

[manila] Weekly Meeting on May 30th canceled
by Goutham Pacha Ravi 29 May '19

29 May '19

Hello Zorillas, We have no items on the agenda for the weekly meeting tomorrow (30th May 2019) [1] and several of the folks on the team are either out of office or traveling. So, I'd like to cancel this week's meeting. Next week (6th June 2019), we'd welcome back folks that attended Cephalocon, KubeCon+CloudNativeCon and OpenStack Days @ CERN and have them share their updates. I'm also looking forward to officially introducing our Outreachy intern and have the awesome Outreachy mentors join us in that meeting. If you have any questions or concerns, please post them here, or on freenode's #openstack-manila. Thanks, Goutham [1] https://wiki.openstack.org/wiki/Manila/Meetings

1 0

[dev][horizon][docs][i18n]Horizon Taiwanese locale issue
by Vadym Markov 29 May '19

29 May '19

Hi, There is an issue with Taiwanese locale at least in Horizon. It would be good to get a feedback from i18n team according to OpenStack docs too. Speaking about Horizon, Chinese locales were renamed in Django 1.7 [1]. Zh-cn became zh-Hans, and zh-tw became zh-Hant. Old names were marked as deprecated and finally removed in Django 1.11. Current supported Django versions are 1.11 and 2.0 [2] It is not an issue for Chinese because django locale middleware does silent fallback from zh-cn to zh-Hans. But for Taiwanese it treats zh-tw as some unknown variant of zh-* and also does fallback to default zh-cn, which is wrong. Reported bug: https://bugs.launchpad.net/horizon/+bug/1830886 Proposed solution is to migrate to new locale names everywhere in Horizon. Here are proposed steps to fix this issue: 1. Zanata jobs reconfiguration 2. Django-related backend stuff. Biggest, but easiest part because it is well documented 3. AngularJS. Quite old version is used, so we can hit some well forgotten issues. Also, testing is complicated. 4. Horizon.js components. It is the smallest part Other question will be thorougful testing of the bugfix. [1] https://docs.djangoproject.com/en/dev/releases/1.7/#language-codes-zh-cn-zh… [2] https://docs.openstack.org/horizon/latest/install/system-requirements.html

2 1

[nova] API updates week 19-22
by gmann＠ghanshyammann.com 29 May '19

29 May '19

Hi All, Please find the Nova API updates of this week. Weekly Office Hour: =============== Canceled the API office hours as no response on ML - http://lists.openstack.org/pipermail/openstack-discuss/2019-March/004336.ht… API Related BP : ============ Code Ready for Review: ------------------------------ 1. Support adding description while locking an instance: - Topic: https://review.opendev.org/#/q/topic:bp/add-locked-reason+(status:open+OR+s… - Weekly Progress: Only OSC patch is not merged (all other code is merged). waiting for python-novaclient version update after release. 2. Add host and hypervisor_hostname flag to create server - Topic: https://review.opendev.org/#/q/topic:bp/add-host-and-hypervisor-hostname-fl… - Weekly Progress: Code is up for review 3. Detach and attach boot volumes: - Topic: https://review.openstack.org/#/q/topic:bp/detach-boot-volume+(status:open+O… - Weekly Progress: Spec is merged but the code is in the merge-conflict state. need rebase and update the patch. Spec Ready for Review: ----------------------------- 1. Nova API policy improvement - Spec: https://review.openstack.org/#/c/547850/ - PoC: https://review.openstack.org/#/q/topic:bp/policy-default-refresh+(status:op… - Weekly Progress: Spec has been updated with Train PTG discussion. Ready to re-review. 2. Support for changing deleted_on_termination after boot -Spec: https://review.openstack.org/#/c/580336/ - Weekly Progress: lyarwood commented on spec about the PTG discussion and mentioned to update the spec accordingly. 3. Nova API cleanup - Spec: https://review.openstack.org/#/c/603969/ - Weekly Progress: Spec has been updated with Train PTG discussion. Alex is +2 on this, need another +2. 4. Specifying az when restore shelved server - Spec: https://review.openstack.org/#/c/624689/ - Weekly Progress: No updates on this. 5. default value of swap in the show flavor details API - Spec: https://review.openstack.org/#/c/648919/ - Weekly Progress: This has been merged in API cleanup Spec(603969) 6. Support delete_on_termination in volume attach api -Spec: https://review.openstack.org/#/c/612949/ - Weekly Progress: Ready for review. 7. Add API ref guideline for body text - ~8 api-ref are left to fix. Previously approved Spec needs to be re-proposed for Train: --------------------------------------------------------------------------- 1. Servers Ips non-unique network names : - https://blueprints.launchpad.net/nova/+spec/servers-ips-non-unique-network-… - https://review.openstack.org/#/q/topic:bp/servers-ips-non-unique-network-na… 2. Volume multiattach enhancements: - https://blueprints.launchpad.net/nova/+spec/volume-multiattach-enhancements - https://review.openstack.org/#/q/topic:bp/volume-multiattach-enhancements+(… Bugs: ==== No progress report in this week. NOTE- There might be some bug which are not tagged as 'api' or 'api-ref', those are not in above list. Tag such bugs so that we can keep our eyes. -gmann

1 0

[auto-scaling] SIG meeting in 10 mins, welcome to join us
by Rico Lin 29 May '19

29 May '19

Dear all We will have SIG meeting in 10 mins, so welcome to join us in #openstack-auto-scaling channel -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

1 0

[infra] Retire x/pbrx and openstack-infra/opendev-website-repos
by Andreas Jaeger 29 May '19

29 May '19

We will retire x/pbrx and openstack-infra/opendev-website-repos: pbrx was an attempt at container building tools which has been superceded by the zuul image building jobs and Dockerfiles. opendev-website is no longer needed since the content is directly served by gitea. First change for this: https://review.opendev.org/661910 -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

1 0

[requirements][nova][neutron] updating sqlalchemy to 1.3.4
by Matthew Thode 29 May '19

29 May '19

so, there are no requirements type reasons why we can't merge this now, but functional tests seem to be failing for nova/neutron (tempest). Would those teams be able to test? https://review.opendev.org/651591 is the test patch (now updated for 1.3.4) Some failures show up here as well. http://logs.openstack.org/39/661539/1/check/tempest-full/b127828/testr_resu… -- Matthew Thode

2 1

[ironic][inspector] Can inspector create port groups or add a port group to the baremetal ports?
by Abishek Subramanian (absubram) 29 May '19

29 May '19

Hi all, I’m looking at port-groups/ bonding options with ironic and I’ve looked at this documentation - https://docs.openstack.org/ironic/rocky/admin/portgroups.html Everything listed there checks out and works when manually attempted. The next thing I’d like to do is see if the port group creation and addition of the port group to the baremetal ports can be done via inspector. Is this feature available? If not, once I create the port group and then run inspection, will the inspector apply the port group to any baremetal ports that it creates? Appreciate any help with this regard. Thanks! Abishek

3 3

[mistral] Office hours in 1 hour at #openstack-mistral
by Renat Akhmerov 29 May '19

29 May '19

Hi, We’ll have an Office Hours session in 1 hour at #openstack-mistral. Welcome to join. Thanks Renat Akhmerov @Nokia

1 0

[barbican] dev: Using barbican in media center/box product
by Hunter Nins 28 May '19

28 May '19

1 0