April 2019 - openstack-discuss - lists.openstack.org

[telemetry][panko][ceilometer][aodh][zuul] Replace telemetry-tox-py37 with openstack-python37-jobs
by Trinh Nguyen 15 Apr '19

15 Apr '19

Hi team, I would love to replace telemetry-tox-py37 with openstack-python37-jobs since the only main difference is the nodeset [1]. If you know any reason to keep it that way, please let me know. Yours, [1] https://github.com/openstack/ceilometer/blob/master/.zuul.yaml#L47 -- *Trinh Nguyen* *www.edlab.xyz <https://www.edlab.xyz>*

1 2

Re: [placement][nova][ptg] resource provider affinity
by Alex Xu 15 Apr '19

15 Apr '19

we miss the maillist address, sorry I start that one....add it back. Alex Xu <soulxu(a)gmail.com> 于2019年4月16日周二上午7:16写道： > > > Sean Mooney <smooney(a)redhat.com> 于2019年4月16日周二上午2:27写道： > >> On Mon, 2019-04-15 at 23:16 +0800, Alex Xu wrote: >> > >> > > >> > > ?resources=DISK_GB& >> > > resources1=VCPU:2,MEMORY_MB:128& >> > > resources1.1=VF:1& >> > > resources2=VCPU:2,MEMORY_MB:128& >> > > resources2.1=VF:1& >> > > group_policy=isolate >> > > >> > > Is it the case you talking about? Sorry, I probably didn't get what >> you >> > > mean about changing grouping and group policies. Is there any >> conflict case >> > > from you vision? >> > > >> > >> > Sorry, I miss read your case. It should be >> > >> > ?resources=DISK_GB:10,VF:1& >> > resources1=VCPU:2,MEMORY_MB:128& >> > resources2=VCPU:2,MEMORY_MB:128& >> > group_policy=isolate >> > >> > VF may get from any RP in the whole tree. >> no that wont work because it would require the disk_GB and the VF to come >> form the same resouce provideer. >> so you would have to do >> > > No, that isn't un-numbered resources meaning. DISK_GB and VF are in > un-numbered request group. It may get from any RP in the whole tree, and > needn't to be same resource provider. > > > http://specs.openstack.org/openstack/nova-specs/specs/rocky/implemented/gra… > "The semantic for the (single) un-numbered grouping is unchanged. That is, > it may still return results from different RPs in the same tree (or, when > “shared” is fully implemented, the same aggregate)." > > >> ?resources=DISK_GB:10& >> resources1=VCPU:2,MEMORY_MB:128& >> resources2=VCPU:2,MEMORY_MB:128& >> resoucees3=VF:1 >> group_policy=isolate >> >> the issue aries if i want 2 VF >> >> do you do >> ?resources=DISK_GB:10& >> resources1=VCPU:2,MEMORY_MB:128& >> resources2=VCPU:2,MEMORY_MB:128& >> resoucees3=VF:1 >> resoucees4=VF:1 >> group_policy=isolate >> >> or >> ?resources=DISK_GB:10& >> resources1=VCPU:2,MEMORY_MB:128& >> resources2=VCPU:2,MEMORY_MB:128& >> resoucees3=VF:2 >> group_policy=isolate >> >> or >> ?resources=DISK_GB:10& >> resources1=VCPU:2,MEMORY_MB:128& >> resources2=VCPU:2,MEMORY_MB:128& >> resoucees3=VF:1 >> resoucees4=VF:1 >> grou >> p_policy=None >> >> i woudl say the last one is the most correct from the neutorn point of >> view >> however we lose guarentee teh cpu and ram come form different numa node >> the first option forces the vif to be form different RP and the second >> requires them to >> be form the same RPs >> >> what you really want is >> ?resources=DISK_GB:10& >> resources1=VCPU:2,MEMORY_MB:128& >> resources2=VCPU:2,MEMORY_MB:128& >> resoucees3=VF:1 >> resoucees4=VF:1 >> grou >> p_policy=isolate;none:3,4 >> >> i.e. the vfs can come form any RP in the tree but resouce group 1 an 2 >> need to be isolated. >> or said another way by default each resouce group is isolated but resouce >> groups 3 and 4 have policy none. >> >> > >> > >> > >> >>

1 0

[cinder][emc-unisphere]Need help: Some exception raise when using IPV6 to connect the EMC unisphere.
by hao wang 15 Apr '19

15 Apr '19

hi guys: Now I was using unisphere 4.4 as cinder's backend with ipv6 address. But there is an exception when I try to start the cinder volume: 2019-04-15 17:14:25.832 25795 DEBUG storops.connection.client [req-b86ea626-dcd5-4d76-9186-4f2dc902f244 - - - - -] REQ URL: [GET] https://[2019:c:0:0:0:0:0:220]:443/api/types/basicSystemInfo?compact=True&f…, TIME: 0.019809961319, RESP CODE: 400 log_response /usr/local/lib/python2.7/site-packages/storops/connection/client.py:186 2019-04-15 17:14:25.833 25795 DEBUG storops.connection.client [req-b86ea626-dcd5-4d76-9186-4f2dc902f244 - - - - -] RESP BODY: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>400 Bad Request</title> </head><body> <h1>Bad Request</h1> <p>Your browser sent a request that this server could not understand.<br /> </p> </body></html> _debug_print_json /usr/local/lib/python2.7/site-packages/storops/connection/client.py:179 I have configured the ipv6 and ipv4 address in unisphere and it connected well with my cinder volume node. When I switched the unify driver to ipv4 san ip in cinder.conf, it worked well.... So I really didn't get where is wrong. Could guys help me out here? thanks.

2 1

Disabling SSLv3, TLSv1.0 and TLSv1.1 in nova-novncproxy?
by Ricardo J. Barberis 15 Apr '19

15 Apr '19

Hello list, I've been tasked with disabling SSLv3, TLSv1.0 and TLSv1.1 in all of our public endpoints (not only OpenStack) and I'm having trouble finding where does nova-novncproxy sets which protocols to use. I have nova-novncproxy installed in 2 servers, one CentOS 6.10 (python 2.6) tied to an IceHouse installation, the other a CentOS 7 (python 2.7) tied to a Queens installation. Software versions: [root@vnc01 ~] # rpm -qa \*nova\* \*vnc\* | sort novnc-0.4-8.el6.noarch openstack-nova-common-2014.1.5-1.el6.noarch openstack-nova-novncproxy-2014.1.5-1.el6.noarch python-nova-2014.1.5-1.el6.noarch python-novaclient-2.17.0-2.el6.noarch [root@vnc02 ~] # rpm -qa \*nova\* \*vnc\* | sort novnc-0.5.1-2.el7.noarch openstack-nova-common-17.0.9-1.el7.noarch openstack-nova-novncproxy-17.0.9-1.el7.noarch python-nova-17.0.9-1.el7.noarch python2-novaclient-10.1.0-1.el7.noarch Any pointers will be appreciated. BTW, I also tried proxying them with nginx but in that case the vnc console doesn't work. I didn't try too hard to debug it, though. Thanks, -- Ricardo J. Barberis Usuario Linux Nº 250625: http://counter.li.org/ Usuario LFS Nº 5121: http://www.linuxfromscratch.org/ Senior SysAdmin / IT Architect - www.DonWeb.com

2 2

[neutron] Bug deputy report - week 8.04 - 15.04
by Slawomir Kaplonski 15 Apr '19

15 Apr '19

Hi, I was on bug deputy last week. Below is summary of bugs reported this week. There is couple of bugs which require help from the team: High: https://bugs.launchpad.net/neutron/+bug/1824299 - Race condition during init may lead to neutron server malfunction - marked as High, there is no volunteer for this one, someone needs to take a look into it. https://bugs.launchpad.net/neutron/+bug/1824571 - l3agent can't create router if there are multiple external networks - I confirmed it today, it looks that when there is more than one network marked as „external” than router can’t be created properly. It looks that it is quite serious one and someone from L3 sub team should take a look into it Medium: https://bugs.launchpad.net/neutron/+bug/1824799 - neutron dhcp agent looks for external pid unexpectedly - volunteer for this one is needed, if there will be no any I will take a look for this bug, Low: https://bugs.launchpad.net/neutron/+bug/1824788 - [DOCS] installed neutron, but no provider network exists - volunteer needed, Also I would like to ask team about this one: https://bugs.launchpad.net/neutron/+bug/1818682 - issue in keepalived 1.2.24 - user asked about list of software (and versions) compatible with neutron. Do we have anything like that? And now list of all other bugs from this week: Critical https://bugs.launchpad.net/neutron/+bug/1823865 - [neutron][networking-ovn] The function provider_network_attribute_updates_supported is breaking networking-ovn gate - marked as critical because it broke gate for stadium project - fix already released, thx Rodolfo. High https://bugs.launchpad.net/kolla/+bug/1823818 - Memory leak in some neutron agents - set to high but in fact this issue is in openvswitch, not in neutron agents directly, I marked it as invalid in neutron as fix is in openvswitch already, https://bugs.launchpad.net/neutron/+bug/1824095 - Fullstack job broken in stable/stein branch - I set to High and not to urgent because fullstack job is non-voting in stein currently so it’s not blocking gate completely - fix already merged (https://review.openstack.org/#/c/651458/) - thx again Rodolfo :) https://bugs.launchpad.net/neutron/+bug/1824138 - Fullstack QoS tests should not handle other tests port events - marked as High because it’s causing gate failures - fix already proposed by Rodolfo (again): https://review.openstack.org/#/c/651523/ - please review it, Medium https://bugs.launchpad.net/neutron/+bug/1823798 - rfp and fpr interfaces not updated after changing network MTU - fixed by Brian already - thx Brian, https://bugs.launchpad.net/neutron/+bug/1824178 - SQLAlchemy broke association proxy into a descriptor + per-class accessor - fix proposed by Rodolfo (is anyone else except Rodolfo working in Neutron now? :P) - https://review.openstack.org/#/c/651584/ https://bugs.launchpad.net/neutron/+bug/1824346 - Check in "_update_segmentation_id" that the mech_driver has an agent - fix proposed by (what a surprise) … Rodolfo - https://review.openstack.org/#/c/651878/ https://bugs.launchpad.net/neutron/+bug/1824504 - arp responder will be created for a vlan port when port ip changed - fix proposed already https://review.openstack.org/652043 https://bugs.launchpad.net/neutron/+bug/1824566 - DVR-Nexthop static routes are not getting configured in FIP Namespace when disassociating and reassociating a FloatingIP in Ocata - only for Ocata, looks that it don’t affects newer releases, fix proposed https://review.openstack.org/652122 Low https://bugs.launchpad.net/neutron/+bug/1823716 - (DOCS) url --> endpoint_template in Install and configure controller node in neutron section of nova.conf - there is volunteer for this one already assigned RFE * https://bugs.launchpad.net/neutron/+bug/1823633 - [RFE] L3 - netfilter Contrack Helper Support - already approved by drivers team (that was fast) Others https://bugs.launchpad.net/neutron/+bug/1824107 - marked as duplicate of https://bugs.launchpad.net/neutron/+bug/1808112 So the winner of "bug fixer of the week” title is definitely Rodolfo :) — Slawek Kaplonski Senior software engineer Red Hat

1 1

[kolla] No IRC meeting on 17th April
by Mark Goddard 15 Apr '19

15 Apr '19

Hi, I'm cancelling this weeks IRC meeting because I'm on vacation from tomorrow until 24th April and nobody offered to chair. Please continue to coordinate in #openstack-kolla. Focus should be on testing the upcoming Stein release and fixing bugs. Thanks, Mark

1 0

[kayobe] No IRC meeting on 29th April
by Mark Goddard 15 Apr '19

15 Apr '19

Hi, We'll cancel the next IRC meeting due to the OpenStack summit. Please bring up any items in #openstack-kayobe on an ad-hoc basis. Thanks, Mark

1 0

Re: [Release-job-failures] release-post job for openstack/releases failed
by Thierry Carrez 15 Apr '19

15 Apr '19

zuul(a)openstack.org wrote: > Build failed. > > - tag-releases http://logs.openstack.org/80/804d609460e6b165e0549e6759b1d0ee277a970a/relea… : TIMED_OUT in 31m 08s > - publish-tox-docs-static publish-tox-docs-static : SKIPPED During release-post processing of the ocata-em tagging change [1], we hit a job timeout[2]. It went as far down as sahara.yaml, where it successfully tagged sahara, sahara-dashboard, sahara-extra, sahara-image-elements, before hitting the timeout. So it did not tackle searchlight-ui and the 28 other deliverables after that. [1] https://git.openstack.org/cgit/openstack/releases/commit/?id=804d609460e6b1… [2] http://logs.openstack.org/80/804d609460e6b165e0549e6759b1d0ee277a970a/relea… -- Thierry Carrez (ttx)

2 1

Pike: "Observer" or "read-only" admin access?
by Ken D'Ambrosio 15 Apr '19

15 Apr '19

Hi, all. Beginning to roll out a newer-than-what-we-had OpenStack release -- likely to be Pike, "For reasons." (Which is still *worlds* newer than Juno, where we are.) And I've been asked if there's such a thing as an account (or ACL) that allows a user to read everything, but write nothing. Googling, I see mention of such things -- but nothing really firm. Does it exist? Is it in Pike (or more recent releases)? If it doesn't exist, is there a graceful way to make it happen, anyway? Thanks! -Ken

3 2

[Cinder] Odd Volume and Volume Snapshot Dependencies
by Jeremy Houser 15 Apr '19

15 Apr '19

Currently running python-openstackclient functional tests against an openstack deployment. Ran into some odd functionality whilst manipulating volumes and snapshots in openstack via cli and gui. I create a volume, create a snapshot of that volume, and then create a volume from that snapshot. I can't delete the snapshot until I delete the volume that I spawned using that snapshot. I understand the dependency of "can't delete a volume while a snapshot dependent on that volume is deleted first" but why can't a volume snapshot be deleted when volumes are spawned from it? Is this intentional? I am working with Cinder 3.27. Jeremy

2 1