January 2023 - openstack-discuss - lists.openstack.org

[Openstack Tacker] - Issue while creating NS
by Lokendra Rathour 15 Jan '23

15 Jan '23

Hi Team, Was trying to create NS using the document : https://docs.openstack.org/tacker/yoga/user/nsd_usage_guide.html But getting an error, the bug has been opened, requesting your kind assistance. https://bugs.launchpad.net/tacker/+bug/1999502 thanks once again. -- ~ Lokendra skype: lokendrarathour

2 1

Destroy a specific service from an openstack kolla deployment
by A Monster 15 Jan '23

15 Jan '23

Is it possible to remove a specific service from openstack, using > > kolla-ansible destroy -i multinode --tag service destroys all service and doesn't take into consideration the tag parameter.

1 0

Minimum Number Of Nodes for Deployment
by Nazmul Haque (N&C, SIL) 14 Jan '23

14 Jan '23

Hi, We are exploring various open source cloud platform. We are currently running Nutanix for our private cloud infrastructure. We would like to explore Openstack. Currently we have two clusters , one with 5 nodes and another with 3 nodes. In order to deploy two Openstack clusters what is the minimum number of nodes required for a private cloud infrastructure ensuring high availability and data integrity in mind. I will pursue the COA course however I want to have some background from industry experts since I am under the impression that Openstack deployment would require a lot of nodes for initial deployment which would be very expensive. Regards, Md Nazmul Haque Disclaimer: This e-mail, including any attachment with it may contain privileged, proprietary & confidential information and is intended solely for the addressee. If you are not the intended recipient of this e-mail, please notify us immediately and destroy this email without taking any copies or showing it to anyone. Unauthorized use of this e-mail is prohibited. SQUARE will not take any responsibility for misdirection, corruption or unauthorized use of e-mail communications, or for any damage that may be caused as a result of transmitting or receiving an e-mail communication. Caution: Do not click links or open attachments unless you recognize the sender and know the content is safe.

1 0

[all][tc] What's happening in Technical Committee: summary 2023 Jan 13: Reading: 5 min
by Ghanshyam Mann 13 Jan '23

13 Jan '23

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Jan 11. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2023/tc.2023-01-11-16.00.log.html * The next TC weekly meeting will be on Jan 18 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Jan 17. 2. What we completed this week: ========================= * Nothing specific for this week. 3. Activities In progress: ================== TC Tracker for the 2023.1 cycle ------------------------------------- * Current cycle working items and their progress are present in the 2023.1 tracker etherpad[2]. Open Reviews ----------------- * Five open reviews for ongoing activities[3]. Cleanup of PyPI maintainer list for OpenStack Projects ---------------------------------------------------------------- The horizon team discussed the 'xstatic-font-awesome' repo PyPi maintainer topic[4] in the weekly meetings[5], As the next step, they will be discussing it with PyPi non-OpenStack maintainers for the possible option to do the maintenance in a single place (either in OpenStack or outside of OpenStack). TC continued the discussion for all other repo/developers' PyPi maintainer cleanup. knikolla will be automating to get the list of deliverables that need PyPi maintainer's cleanup and after that TC will reach out to the respective project PTL to do the audit if we can cleanup those directly or need some more discussion with external maintainers (like 'xstatic-font-awesome' case) if there is any. We will continue this topic discussion in TC next weekly meeting also. Project updates ------------------- * Add Cinder Huawei charm[6] * Add the woodpecker charm to Openstack charms[7] Less Active/Inactive projects: ~~~~~~~~~~~~~~~~~~~~~~ * Zaqar status Zaqar gate is broken due to the MongoDB package not being present in Ubuntu 22.04 which is used for testing in 2023.1 cycle. Zaqar's team knows about the issue and discusses the same[8]. The TC is discussing and reaching out to the PTL about it. The release team is waiting to get a clear situation on the activeness/gate fix of this project so that they can decide on its release for 2023.1 cycle. It is also proposed to be marked as Inactive[9]. TC will continue the discussion with the Zaqar team and take the next action soon. * Mistral status: The Mistral team is actively merging the gate fixes[10], python-mistralclient gate is facing more issue which is being looked at by the Mistral team. The release team is trying the beta release patches for mistral deliverables[11][12] * Adjutant Status The Adjutant gate is green and its beta release is done[13][14]. With that, Dale proposed to remove this project from the Inactive project list[15] which has a positive response from the TC review. Thanks, Dale to make this project active again. 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[16]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [17] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggesti… [2] https://etherpad.opendev.org/p/tc-2023.1-tracker [3] https://review.opendev.org/q/projects:openstack/governance+status:open [4] https://github.com/openstack/xstatic-font-awesome/pull/2 [5] https://meetings.opendev.org/meetings/horizon/2023/horizon.2023-01-11-15.00… [6] https://review.opendev.org/c/openstack/governance/+/867588 [7] https://review.opendev.org/c/openstack/governance/+/869752 [8] https://review.opendev.org/c/openstack/zaqar/+/857924/comments/a0d5d45e_300… [9] https://review.opendev.org/c/openstack/governance/+/870098 [10] https://review.opendev.org/q/project:openstack/mistral [11] https://review.opendev.org/c/openstack/releases/+/869470 [12] https://review.opendev.org/c/openstack/releases/+/869448 [13] https://review.opendev.org/c/openstack/releases/+/869449 [14] https://review.opendev.org/c/openstack/releases/+/869471 [15] https://review.opendev.org/c/openstack/governance/+/869665 [16] hhttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[neutron] Drivers meeting cancelled today
by Rodolfo Alonso Hernandez 13 Jan '23

13 Jan '23

Hello Neutrinos: Due to the lack of agenda [1], today's meeting is cancelled. Have a nice weekend! [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

[horizon]
by Nguyễn Hữu Khôi 12 Jan '23

12 Jan '23

Hello guys. I use Openstack Xena which deployed by Kolla Ansible.My problem is when I launch instance from Horizon, Port selection won't show as below pictures: [image: image.png] [image: image.png] I try to change browser but this problem still persists Any suggestions for me? Thank you. Regards. Nguyen Huu Khoi

2 2

RuntimeError: The expected HostnameMap and RoleHostnameFormat are not defined in data file: /home/stack/dcn01/dcn01_overcloud-baremetal-deployed.yaml | Openstack wallaby | tripleo | centos 8 stream
by Swogat Pradhan 12 Jan '23

12 Jan '23

Hi, INFO: Openstack wallaby on centos 8 stream I am trying to deploy a DCN and during the ceph deploy command i am getting the following error: (undercloud) [stack@hkg2director dcn01]$ openstack overcloud ceph deploy dcn01_overcloud-baremetal-deployed.yaml --stack dcn01 --config initial-ceph.conf --output deployed_ceph.yaml --container-image-prepare containers-prepare-parameter.yaml --network-data custom_network_data.yaml --cluster dcn01 --roles-data dcn01_roles.yaml -vvv The full traceback is: Traceback (most recent call last): File "/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py", line 241, in get_deployed_roles_to_hosts UnboundLocalError: local variable 'matching_hosts' referenced before assignment During handling of the above exception, another exception occurred: Traceback (most recent call last): File "<stdin>", line 102, in <module> File "<stdin>", line 94, in _ansiballz_main File "<stdin>", line 40, in invoke_module File "/usr/lib64/python3.6/runpy.py", line 205, in run_module return _run_module_code(code, init_globals, run_name, mod_spec) File "/usr/lib64/python3.6/runpy.py", line 96, in _run_module_code mod_name, mod_spec, pkg_name, script_name) File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py", line 500, in <module> File "/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py", line 471, in main File "/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py", line 246, in get_deployed_roles_to_hosts RuntimeError: The expected HostnameMap and RoleHostnameFormat are not defined in data file: /home/stack/dcn01/dcn01_overcloud-baremetal-deployed.yaml 2023-01-13 01:27:15.811878 | 48d539a1-1679-ea57-d54d-000000000013 | FATAL | Create Ceph spec based on baremetal_deployed_path and tripleo_roles | undercloud | error={ "changed": false, "module_stderr": "Traceback (most recent call last):\n File \"/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py\", line 241, in get_deployed_roles_to_hosts\nUnboundLocalError: local variable 'matching_hosts' referenced before assignment\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n File \"<stdin>\", line 102, in <module>\n File \"<stdin>\", line 94, in _ansiballz_main\n File \"<stdin>\", line 40, in invoke_module\n File \"/usr/lib64/python3.6/runpy.py\", line 205, in run_module\n return _run_module_code(code, init_globals, run_name, mod_spec)\n File \"/usr/lib64/python3.6/runpy.py\", line 96, in _run_module_code\n mod_name, mod_spec, pkg_name, script_name)\n File \"/usr/lib64/python3.6/runpy.py\", line 85, in _run_code\n exec(code, run_globals)\n File \"/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py\", line 500, in <module>\n File \"/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py\", line 471, in main\n File \"/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py\", line 246, in get_deployed_roles_to_hosts\nRuntimeError: The expected HostnameMap and RoleHostnameFormat are not defined in data file: /home/stack/dcn01/dcn01_overcloud-baremetal-deployed.yaml\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1 } (undercloud) [stack@hkg2director dcn01]$ cat /home/stack/dcn01/dcn01_overcloud-baremetal-deployed.yaml parameter_defaults: DeployedServerPortMap: dcn01-hci-0-ctlplane: fixed_ips: - ip_address: 172.25.221.96 dcn01-hci-1-ctlplane: fixed_ips: - ip_address: 172.25.221.90 dcn01-hci-2-ctlplane: fixed_ips: - ip_address: 172.25.221.106 HCICount: 3 HCIHostnameFormat: '%stackname%-hci-%index%' HostnameMap: dcn01-hci-0: dcn01-hci-0 dcn01-hci-1: dcn01-hci-1 dcn01-hci-2: dcn01-hci-2 NodePortMap: dcn01-hci-0: ctlplane: ip_address: 172.25.221.96 ...> Can someone please tell me what could be the issue here?? Am I missing something? With regards, Swogat Pradhan

1 1

[ironic] Bugfix branches being EOL'd first week of Jan, 2023
by Jay Faulkner 12 Jan '23

12 Jan '23

OpenStack Community and Operators, As documented in https://specs.openstack.org/openstack/ironic-specs/specs/approved/new-relea…, Ironic performs bugfix releases in the middle of a cycle to permit downstream packagers to more rapidly deliver features to standalone Ironic users. However, we've neglected as a project to cleanup or EOL any of these branches -- until now. Please take notice that during the first week in January, we will be EOL-ing all old, unsupported Ironic bugfix branches. This will be handled similarly to an EOL of a stable branch; we will create a tag -- e.g. for bugfix/x.y branch, we would tag bugfix-x.y-eol -- then remove the branch. These branches have been out of support for months and should not be in use in your Ironic clusters. If you are using any branches slated for retirement, please immediately upgrade to a supported Ironic version. A full listing of projects and branches impacted: ironic branches being retired bugfix/15.1 bugfix/15.2 bugfix/16.1 bugfix/16.2 bugfix/18.0 bugfix/20.0 ironic-python-agent branches being retired bugfix/6.2 bugfix/6.3 bugfix/6.5 bugfix/6.6 bugfix/8.0 bugfix/8.4 ironic-inspector branches being retired bugfix/10.2 bugfix/10.3 bugfix/10.5 bugfix/10.10 Thank you, Jay Faulkner Ironic PTL

1 4

[ironic] Moving Aija to core-emeritus
by Jay Faulkner 12 Jan '23

12 Jan '23

Hi all, As many of you may already know, Aija is no longer actively working on OpenStack. She informed many Ironic cores over email of this last week. I asked her if she expected to contribute on her own time and she said no. In order to ensure we keep core reviewer lists up to date, I suggest we move Aija to core-emeritus status, removing core permissions from gerrit. If she decides to begin working on OpenStack again in the future, we'd obviously quickly return core permissions. What do you think? -- Jay Faulkner Ironic PTL TC Member P.S. A huge thanks to Aija for her hard work on the sushy project and the Dell driver in Ironic.

6 6

Overriding tox's install_command won't work for non-service projects
by Stephen Finucane 12 Jan '23

12 Jan '23

Another tox 4 PSA. It turns out the tox 3 was not using the command in '[tox] install_command' when installing the package under test. tox 4 does, which means overriding '[tox] install_command' to include a constraints file (-c) will prevent you installing any requirement that is listed in the upper-constraints file, even if said requirement is the thing you're currently working on. This applies to all libraries (e.g. oslo.db, python-cinderclient) but not the services (cinder, nova) since those aren't included in upper-constraints. The "correct" way to respect upper-constraints is to provide them in 'deps' alongside the requirements file(s), e.g. [testenv] deps = -c{env:UPPER_CONSTRAINTS_FILE:https://releases.openstack.org/constraints/upper/master} -r{toxinidir}/requirements.txt -r{toxinidir}/test-requirements.txt This will cause tox to install all of the package's dependencies first *with* constraints before installing the package itself *without constraints*. There is a bug report open against pip to change this behaviour [1], but it's been sat there for over two years with no activity so I wouldn't rely on this. Stephen [1] https://github.com/pypa/pip/issues/7839

2 3