- openstack-discuss - lists.openstack.org

[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 20 Feb '19

20 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 20 Feb '19

20 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 20 Feb '19

20 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 20 Feb '19

20 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 20 Feb '19

20 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

[oslo] How to properly cleanup FakeExchangeManager between test cases
by Balázs Gibizer 20 Feb '19

20 Feb '19

Hi, Nova has tests that are using the oslo.messaging FakeDriver implementation by providing the 'fake://' transport url. The FakeExchangeManager keeps a class level dict of FakeExchange objects keyed by the communication topic[1]. This can cause that an RPC message sent by a test case is received by a later test case running in the same process. I did not find any proper way to clean up the FakeExchangeManager at the end of each test case to prevent this. To fix the problem in the nova test I did a hackish cleanup by overwriting FakeExchangeManager._exchanges directly during test case cleanup [2]. Is there a better way to do this cleanup? Cheers, gibi [1] https://github.com/openstack/oslo.messaging/blob/0a784d260465bc7ba878bedeb5… [2] https://review.openstack.org/#/c/637233/1/nova/tests/fixtures.py

3 2

[cinder]queens][vmax3] FC issue
by Ignazio Cassano 20 Feb '19

20 Feb '19

Hello All. I'am trying to configure cinder driver for vmax3 fc using the rest api driver. I am facing issues creating volumes from images because masking view errors: The error message received was Bad or unexpected response from the storage volume backend API: Error retrieving masking group On unisphere (8.4) log files I found that moveVolumeToStorageGroup is not found, while the openstack dell_emc rest-py is using it in its payload. Anyone could help us with this problem ? Regards Ignazio

1 0

[all] Denver Forum Brainstorming
by Kendall Nelson 20 Feb '19

20 Feb '19

Hello Everyone! Welcome to the topic selection process for our Forum in Denver! This is not a classic conference track with speakers and presentations. OSF community members (participants in development teams, operators, working groups, SIGs, and other interested individuals) discuss the topics they want to cover and get alignment on and we welcome your participation. The Forum is your opportunity to help shape the development of future project releases. For OpenStack Denver marks the beginning of Train’s release cycle, where ideas and requirements will be gathered. We should come armed with feedback from the upcoming Stein release if at all possible. We aim to ensure the broadest coverage of topics that will allow for multiple parts of the community getting together to discuss key areas within our community/projects. For OSF Projects (StarlingX, Zuul, Airship, Kata Containers) As a refresher, the idea is to gather ideas and requirements for your project’s upcoming release. Look to https://wiki.openstack.org/wiki/Forum for an idea of how to structure fishbowls and discussions for your project. The idea is to ensure the broadest coverage of topics, while allowing for the project community to discuss critical areas of concern. To make sure we are presenting the best topics for discussion, we have asked representatives of each of your projects to help us out in the Forum selection process. There are two stages to the brainstorming: 1.If you haven’t already, its encouraged that you set up an etherpad with your team and start discussing ideas you'd like to talk about at the Forum and work out which ones to submit. 2. On the 22nd of February, we will open up a more formal web-based tool for you to submit abstracts for the most popular sessions that came out of your brainstorming. Make an etherpad and add it to the list at: https://wiki.openstack.org/wiki/Forum/Denver2018 <https://wiki.openstack.org/wiki/Forum/Berlin2018> This is your opportunity to think outside the box and talk with other projects, groups, and individuals that you might not see during Summit sessions. Look for interested parties to collaborate with and share your ideas. Examples of typical sessions that make for a great Forum: - Strategic, whole-of-community discussions, to think about the big picture, including beyond just one release cycle and new technologies - eg Making OpenStack One Platform for containers/VMs/Bare Metal (Strategic session) the entire community congregates to share opinions on how to make OpenStack achieve its integration engine goal - Cross-project sessions, in a similar vein to what has happened at past forums, but with increased emphasis on issues that are of relevant to all areas of the community - eg Rolling Upgrades at Scale (Cross-Project session) – the Large Deployments Team collaborates with Nova, Cinder and Keystone to tackle issues that come up with rolling upgrades when there’s a large number of machines. - Project-specific sessions, where community members most interested in a specific project can discuss their experience with the project over the last release and provide feedback, collaborate on priorities, and present or generate 'blue sky' ideas for the next release - eg Neutron Pain Points (Project-Specific session) – Co-organized by neutron developers and users. Neutron developers bring some specific questions about implementation and usage. Neutron users bring feedback from the latest release. All community members interested in Neutron discuss ideas about the future. Think about what kind of session ideas might end up as: Project-specific, cross-project or strategic/whole-of-community discussions. There'll be more slots for the latter two, so do try and think outside the box! This part of the process is where we gather broad community consensus - in theory the second part is just about fitting in as many of the good ideas into the schedule as we can. Further details about the forum can be found at: https://wiki.openstack.org/wiki/Forum Thanks all! Kendall Nelson, on behalf of the OpenStack Foundation, User Committee & Technical Committee

2 1