February 2019 - openstack-discuss

how to find the interfaces to exclude in SR-IOV?
by Manuel Sopena Ballesteros 21 Feb '19

21 Feb '19

Hi, I would like to exclude a couple of VFs from the neutron SR-IOV configuration... According to documentation https://docs.openstack.org/neutron/latest/admin/config-sriov#enable-neutron… exclude_devices = eth1:0000:07:00.2;0000:07:00.3,eth2:0000:05:00.1;0000:05:00.2 This is my configuration [root@zeus-59 ~]# ibdev2netdev -v 0000:88:00.0 mlx5_0 (MT4117 - MT1611X10113) CX4121A - ConnectX-4 LX SFP28 fw 14.24.1000 port 1 (ACTIVE) ==> bond0 (Up) 0000:88:00.1 mlx5_1 (MT4117 - MT1611X10113) CX4121A - ConnectX-4 LX SFP28 fw 14.24.1000 port 1 (ACTIVE) ==> bond0 (Up) 0000:88:01.2 mlx5_10 (MT4118 - NA) fw 14.24.1000 port 1 (ACTIVE) ==> enp136s1f2 (Up) 0000:88:01.3 mlx5_11 (MT4118 - NA) fw 14.24.1000 port 1 (ACTIVE) ==> enp136s1f3 (Up) 0000:88:01.4 mlx5_12 (MT4118 - NA) fw 14.24.1000 port 1 (ACTIVE) ==> enp136s1f4 (Up) 0000:88:01.5 mlx5_13 (MT4118 - NA) fw 14.24.1000 port 1 (ACTIVE) ==> enp136s1f5 (Up) 0000:88:01.6 mlx5_14 (MT4118 - NA) fw 14.24.1000 port 1 (ACTIVE) ==> enp136s1f6 (Up) 0000:88:01.7 mlx5_15 (MT4118 - NA) fw 14.24.1000 port 1 (ACTIVE) ==> enp136s1f7 (Up) 0000:88:02.0 mlx5_16 (MT4118 - NA) fw 14.24.1000 port 1 (ACTIVE) ==> enp136s2 (Up) 0000:88:02.1 mlx5_17 (MT4118 - NA) fw 14.24.1000 port 1 (ACTIVE) ==> enp136s2f1 (Up) 0000:88:00.2 mlx5_2 (MT4118 - NA) fw 14.24.1000 port 1 (ACTIVE) ==> ens2f2 (Up) 0000:88:00.3 mlx5_3 (MT4118 - NA) fw 14.24.1000 port 1 (ACTIVE) ==> ens2f3 (Up) 0000:88:00.4 mlx5_4 (MT4118 - NA) fw 14.24.1000 port 1 (ACTIVE) ==> ens2f4 (Up) 0000:88:00.5 mlx5_5 (MT4118 - NA) fw 14.24.1000 port 1 (ACTIVE) ==> ens2f5 (Up) 0000:88:00.6 mlx5_6 (MT4118 - NA) fw 14.24.1000 port 1 (ACTIVE) ==> ens2f6 (Up) 0000:88:00.7 mlx5_7 (MT4118 - NA) fw 14.24.1000 port 1 (ACTIVE) ==> ens2f7 (Up) 0000:88:01.0 mlx5_8 (MT4118 - NA) fw 14.24.1000 port 1 (ACTIVE) ==> enp136s1 (Up) 0000:88:01.1 mlx5_9 (MT4118 - NA) fw 14.24.1000 port 1 (ACTIVE) ==> enp136s1f1 (Up) ens2f2 (0000:88:00.2) and ens2f3 (0000:88:00.3) are part of bond0 which I want to assign to OVS. I would like to do something like: exclude_devices = <ethX>:0000:88:00.2,<ethY>0000:88:00.3 How can I find out ethX and ethY? Are they PFs? Thank you very much NOTICE Please consider the environment before printing this email. This message and any attachments are intended for the addressee named and may contain legally privileged/confidential/copyright information. If you are not the intended recipient, you should not read, use, disclose, copy or distribute this communication. If you have received this message in error please notify us at once by return email and then delete both messages. We accept no liability for the distribution of viruses or similar in electronic communications. This notice should not be removed.

3 2

Presentation material of previous summits
by Georg Kunz 21 Feb '19

21 Feb '19

Hi all, Can somebody help me finding the presentation slides of the Berlin summit (or previous summits in general)? As far as I know, the presentation slides were linked on the summit schedule. Now, as the Denver summit schedule is online, I cannot find the slides anymore. Maybe I just missed to look in an obvious place... Thank you Georg

2 2

Invitation to post queries regarding Outreachy
by Niharika Shrivastava 21 Feb '19

21 Feb '19

email : chunnushrivastava(a)gmail.com

1 0

[neutron] [upgrade] No meeting on Feb. 21th
by Lujin Luo 21 Feb '19

21 Feb '19

Hi team, We do not have updates since our last meeting. Thus let's do the hacking this week and resume the meeting next week! Best regards, Lujin

1 0

Outreachy applicant
by Soledad Kuczala 21 Feb '19

21 Feb '19

Hi, My name is Sol and I'm participating already in Outreachy. I was working with the documentation and Sofia and I think I have succesfully set up my environment with Devstack. I join the new channel on IRC they've created (#openstack.outreachy) and I just wanted to let you know that. I'll be waiting for the next step. Meanwhile I'll be checking bugs on Cinder in the low-hanging-fruit. Also I'll be expecting to participate on next meeting. Thanks Sol

2 2

Edit of a Summit submission
by Adam Young 21 Feb '19

21 Feb '19

There is a typo on on of my summit submission abstracts. How do I go about getting it edited now?

2 1

openstack-kolla precheck failure
by vladimir franciz blando 21 Feb '19

21 Feb '19

Hi, I have a newly installed node running on CentOS 7 with 2 NICs, my precheck failed and I can't figure it out. I'm trying out multinode with 1 node for controller and the other for compute --- begin paste --- TASK [glance : Checking free port for Glance Registry] ****************************************************************************************************************************************** fatal: [10.150.7.102]: FAILED! => {"msg": "The conditional check 'inventory_hostname in groups[glance_services['glance-registry']['group']]' failed. The error was: error while evaluating conditional (inventory_hostname in groups[glance_services['glance-registry']['group']]): Unable to look up a name or access an attribute in template string ({% if inventory_hostname in groups[glance_services['glance-registry']['group']] %} True {% else %} False {% endif %}).\nMake sure your variable name does not contain invalid characters like '-': argument of type 'StrictUndefined' is not iterable\n\nThe error appears to have been in '/usr/share/kolla-ansible/ansible/roles/glance/tasks/precheck.yml': line 18, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Checking free port for Glance Registry\n ^ here\n"} to retry, use: --limit @/usr/share/kolla-ansible/ansible/site.retry PLAY RECAP ************************************************************************************************************************************************************************************** 10.150.7.102 : ok=68 changed=0 unreachable=0 failed=1 10.150.7.103 : ok=15 changed=0 unreachable=0 failed=0 localhost --- - Vlad

2 1

[openstack-dev] [neutron] Change of day and time for the L3 sub-team meeting
by Miguel Lavalle 21 Feb '19

21 Feb '19

Hi Stackers, In an effort to make the L3 sub-team meeting schedule friendlier to Far East developers, we have moved it to Wednesdays at 1400 UTC. We are also welcoming Liu Yulong as one of the co-chairs of the meeting: https://review.openstack.org/#/c/637900/. Please update your calendars accordingly. Best regards Miguel

1 0

Denver Summit Schedule Live
by Ashlee Ferguson 21 Feb '19

21 Feb '19

Hi everyone, The agenda for the Open Infrastructure Summit <https://www.openstack.org/summit/denver-2019/summit-schedule>(formerly the OpenStack Summit) is now live! If you need a reason to join the Summit in Denver, April 29-May 1, here’s what you can expect: Breakout sessions spanning 30+ open source projects from technical community leaders and organizations including ARM, AT&T, China Mobile, Baidu, Boeing, Blizzard Entertainment, Haitong Securities Company, NASA, and more. Project updates and onboarding from OSF projects: Airship, Kata Containers, OpenStack, StarlingX, and Zuul. Join collaborative sessions at the Forum <https://wiki.openstack.org/wiki/Forum>, where open infrastructure operators and upstream developers will gather to jointly chart the future of open source infrastructure, discussing topics ranging from upgrades to networking models and how to get started contributing. Get hands on training around open source technologies directly from the developers and operators building the software. Now what? Register <https://openinfrasummitandptgdenver.eventbrite.com/> before prices increase on February 27 at 11:59pm PT (February 28 at 7:59am UTC) Then, book a room <https://www.hyatt.com/en-US/group-booking/DENCC/G-FNTE> at the official Summit hotel while rooms are still available! Questions? Reach out to summit(a)openstack.org <mailto:summit@openstack.org> Cheers, Ashlee Ashlee Ferguson OpenStack Foundation ashlee(a)openstack.org

1 0

[openstack-ansible] setup-infrastructure failure
by vladimir franciz blando 20 Feb '19

20 Feb '19

Node running on CentOS 7 with 2 NICs, try to run openstack-ansible all-in-one and ran into a problem with setup-infrastructure command: openstack-ansible setup-infrastructure.yml --- TASK [Get list of repo packages] **************************************************************************************************************************************************************** fatal: [aio1_utility_container-9fa7b0be]: FAILED! => {"changed": false, "content": "", "msg": "Status code was -1 and not [200]: Request failed: <urlopen error [Errno 113] No route to host>", "redirected": false, "status": -1, "url": " http://172.29.236.100:8181/os-releases/18.1.3/centos-7.6-x86_64/requirement… "} NO MORE HOSTS LEFT ****************************************************************************************************************************************************************************** PLAY RECAP ************************************************************************************************************************************************************************************** aio1 : ok=46 changed=0 unreachable=0 failed=0 aio1_aodh_container-646c3256 : ok=6 changed=0 unreachable=0 failed=0 aio1_ceilometer_central_container-715d011d : ok=6 changed=0 unreachable=0 failed=0 aio1_cinder_api_container-3bd7a6b4 : ok=6 changed=0 unreachable=0 failed=0 aio1_galera_container-64731bca : ok=6 changed=0 unreachable=0 failed=0 aio1_glance_container-d07a3aa4 : ok=6 changed=0 unreachable=0 failed=0 aio1_gnocchi_container-4377a0b7 : ok=6 changed=0 unreachable=0 failed=0 aio1_horizon_container-edb3edf9 : ok=6 changed=0 unreachable=0 failed=0 aio1_keystone_container-e3a4bf34 : ok=6 changed=0 unreachable=0 failed=0 aio1_memcached_container-f94f23e1 : ok=6 changed=0 unreachable=0 failed=0 aio1_neutron_server_container-00f0e572 : ok=6 changed=0 unreachable=0 failed=0 aio1_nova_api_container-bf866cf2 : ok=6 changed=0 unreachable=0 failed=0 aio1_rabbit_mq_container-19320598 : ok=6 changed=0 unreachable=0 failed=0 aio1_repo_container-b335cfef : ok=83 changed=3 unreachable=0 failed=0 aio1_utility_container-9fa7b0be : ok=29 changed=2 unreachable=0 failed=1 localhost : ok=1 changed=0 unreachable=0 failed=0 EXIT NOTICE [Playbook execution failure] ************************************** =============================================================================== [root@openstack-ansible playbooks]# --- the container is running and I can see that url is working --- [root@openstack-ansible playbooks]# lxc-ls -f |grep 9fa7b0be aio1_utility_container-9fa7b0be RUNNING 1 onboot, openstack 10.255.255.176, 172.29.237.17 - [root@openstack-ansible playbooks]# --- --- [root@openstack-ansible playbooks]# curl http://172.29.236.100:8181/os-releases/18.1.3/centos-7.6-x86_64/requirement… networking_sfc==7.0.1.dev4 urllib3==1.23 alabaster==0.7.11 restructuredtext_lint==1.1.3 pylxd==2.2.7 sphinxcontrib_seqdiag==0.8.5 oslo.cache==1.30.1 tooz==1.62.0 pytz==2018.5 pysaml2==4.5.0 pathtools==0.1.2 appdirs==1.4.3 ... --- - Vlad

3 3