September 2019 - Starlingx-discuss

[Starlingx-discuss] Minutes: StarlingX Release Meeting - Sept 19/2019
by Khalil, Ghada 19 Sep '19

19 Sep '19

Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases stx.3.0 - Release Plan: https://docs.google.com/spreadsheets/d/1ZFR-9-riwhIwiBYBmWmi1qOVyHtgJ8Xk_Fa… - StoryBoard Dashboard: https://storyboard.openstack.org/#!/board/186 - Readout from review with TSC -- Bill - Reviewed stx.3.0 milestone-2 status: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/005881… - No main concerns raised by the TSC team. - Milestone-2 can be declared. - Items to keep an eye on: - Upversion openstack to train - Not making a lot of progress on securing resources; no volunteers from the community; only partially staffed - Tasks are defined - A few will be covered by 99cloud. - The main task is not covered yet - Bruce reaching out to the broader Intel community as well as Cindy; may need to shift resources from other features. - Tracking Feature Test Completion in SB - Agreed to have the test prime add a "Feature Test" to the top-level story for each feature. - Gives us a more visible way of tracking when feature test is done (story won't merge until task is marked as complete) - Example: https://storyboard.openstack.org/#!/story/2005516 - Task: [Feature Test] Time Sensitive Networking stx.2.0 - stx.2.0 branch: https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.2.0 - 7 commits merged since stx.2.0 final compile - 2 security fixes & 2 bugs - To be cherrypicked: (waiting for sanity/soak. Note added requesting the developers to cherrypick when appropriate) - https://bugs.launchpad.net/starlingx/+bug/1817936 - https://bugs.launchpad.net/starlingx/+bug/1830736 - stx.2.0 gating bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2.0 - Current count: 12 - Discuss date for an initial rc build for maintenance release - Ada confirmed that the test team can run a sanity and automated regression - Any manual regression would be focused on the bug fixes that got merged - Agreed to have an "rc" build for the maintenance release on Sept 25 with sanity/regression on Sept 26-27 - stx.2.0 Process: ** email sent to mailing list ** - Merge the fix in master first - Wait for a green sanity on master (load including the fix) - Optional: wait for soak or targeted testing on master. This is left at the discretion of the developer depending on the complexity/risk of the code change. - Cherry-pick the fix to r/stx.2.0 & work thru the merge process - Bill is suggesting we do a community retrospective for stx.2.0 - what went well? what can be done better? - To cover in one of the community calls Regards, Ghada

1 0

[Starlingx-discuss] [Release] r/stx.2.0 cherrypicking & rc build for maintenance release
by Khalil, Ghada 19 Sep '19

19 Sep '19

Hello all, The release team is looking to have a candidate build for the stx.2.0 maintenance release (stx.2.0.1) on 2019-09-25 evening ET. Sanity and automated regression are planned starting 2019-09-26. This is a reminder for developers fixing stx.2.0 gating bugs to: - Merge the fix in master first - Wait for a green sanity on master (w/ load including the fix) - Optional: wait for soak or follow-up on targeted testing on master. This is left to the discretion of the developer depending on the complexity/risk of the code change. - Cherry-pick the fix to r/stx.2.0 (manual cherry-picking may be required due to the repo restructuring in master) If you have a fix ready (or close), please plan to cherry-pick it before 2019-09-25. References: - stx.2.0 branch: https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.2.0 - stx.2.0 open gating bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2.0 - stx.2.0 fixed bugs that need to be cherry-picked: (as of 2019-09-19) https://bugs.launchpad.net/starlingx/+bug/1817936 https://bugs.launchpad.net/starlingx/+bug/1830736 Regards, Ghada On behalf of the release team

1 0

Re: [Starlingx-discuss] stx.3.0 milestone-2 -- Milestone Declared
by Khalil, Ghada 19 Sep '19

19 Sep '19

Hello all, The stx.3.0 milestone-2 status was reviewed with the TSC today. No concerns were raised. The release team is pleased to declare this milestone. Many thanks to all who contributed towards this milestone. Regards, Ghada -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil@windriver.com] Sent: Monday, September 16, 2019 4:21 PM To: starlingx-discuss(a)lists.starlingx.io Subject: [Starlingx-discuss] stx.3.0 milestone-2 status Hello TSC & community members, The stx release team would like to share with you the status of milestone-2 and the overall stx.3.0 release. Your feedback is welcome. - Features on track for stx.3.0 - Count: 9 - Fault Containerization - Upversion K8s and dependencies - Upversion Openstack to Train (Risk: yellow. Plan is still being worked) - Intel GPU support for K8s - Intel QAT support for K8s (Risk: yellow) - TSN Support in VM - Redfish Support - Infrastructure & Cluster Monitoring - Support remote auth via OIDC / OAUTH2 for K8s API - Features with partial or prep delivery in stx.3.0 - Count: 7 - Distributed Cloud (support for platform only; no openstack) - Backup & Restore with containers (support for platform only; no openstack) - Layered Build - Sysvinit >> systemd Conversion/Cleanup - Multi-OS Support - Intel FPGA support for K8s - Flock Versioning - Features proposed for deferral to stx.4.0 due to staffing constraints - Count: 4 - Containerized Openstack clients - Containerize Ceph - Containerize OVS-DPDK - Unstaffed features (no current plan for delivery) >> considered out of stx.3.0 - Count: 2 - IPv6 support for PXE boot network - R2 >> R3 Upgrades In terms of overall proposal for the release dates, the current plans show a date move of 2wks for feature test & regression and ~1wk to the overall release date. - Milestone-2 -- Plan: 9/4/2019, Forecast: 9/19/2019 - Milestone-3 -- Plan: 10/16/2019, Forecast: no change - Feature Test -- Plan: 10/16/2019, Forecast: 10/30/2019 - Regression Test -- Plan: 11/8/2019, Forecast: 11/22/2019 - RC1 (Branch Creation) -- Plan: 11/13/2019, Forecast: 11/20/2019 - Final Regression - Plan: 11/27/2019, Forecast: 12/6/2019 - Release - Plan: 12/4/2019, Forecast: 12/13/2019 At this point, the release team feels we have enough to proceed with declaring milestone-2 pending review and feedback from the TSC. Regards, Ghada PS: Finally, if there are additional community resources available to contribute to stx.3.0 deliverables, please reach out to the release team (myself, Bill Zvonar or Bruce Jones). _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss(a)lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

1 0

[Starlingx-discuss] controller-1 install/setup using ISO (not pxe)
by Pratik M. 19 Sep '19

19 Sep '19

Hi, I have installed controller-0 and my OAM_IF is eno1 and MGMT_IF is eno2. I am trying to install controller-1. However, my existing OAM lab network already runs pxe. And my server BIOS does not have an option to select one specific network interface for PXE booting. So I tried to temporarily switch the cables (connect mgmt to eno1 and disconnect oam). The pxe boot works; controller-1 gets discovered. And I can do host-update 2 personality=controller. After the install and reboot, I switch back the cables. And try to set the OAM_IF to the correct/final interface (eno1). [sysadmin@controller-0 etc(keystone_admin)]$ OAM_IF=eno1 && MGMT_IF=eno2 [sysadmin@controller-0 etc(keystone_admin)]$ system host-if-modify controller-1 $OAM_IF -c platform Interface not found: host controller-1 if eno1 I see the controller-1 does not have an IP post reboot. I tried manually setting the eno2 IP to 192.168.204.2/24 but still it shows offline. [sysadmin@controller-0 ~(keystone_admin)]$ system host-list +----+--------------+-------------+----------------+-------------+--------------+ | id | hostname | personality | administrative | operational | availability | +----+--------------+-------------+----------------+-------------+--------------+ | 1 | controller-0 | controller | unlocked | enabled | available | | 2 | controller-1 | controller | locked | disabled | offline | +----+--------------+-------------+----------------+-------------+--------------+ I cannot reverse the cabling on the NICs for a different set of reasons. Any workaround? Is there a way to install the software using iso, set some IPs manually and then enroll the controller-1 to the cluster? Thanks in advance Pratik

2 2

[Starlingx-discuss] Help creating new branch on Test repo
by Perez Carranza, Jose 19 Sep '19

19 Sep '19

Hi Dean In order to have backwards compatibility on the test suite we require a new branch on Test repo [1] called “ stx_2.0 ” based on current master, are you able to help us creating that branch. 1. https://opendev.org/starlingx/test Regards Jose --

2 2

[Starlingx-discuss] update spreadsheetcgts-client
by Dominig ar Foll (Intel Open Source) 19 Sep '19

19 Sep '19

Hello, In the new/old repo conversion spread sheet I see the following line. stx-config sysinv/cgts-client cgts-client utilities system-client system-client This relocation deferred till a future date. It seems that the move has already be done. Could some one with write access on the spreadsheet do the update. Thanks -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre

2 1

[Starlingx-discuss] Failure launching Cirros Image
by Saul Wold 19 Sep '19

19 Sep '19

Folks, I have been working on setting up a baremetal system on a NUC with dual NICs. I have been able to provision it and have the stx-openstack application manifest fully loaded. I have created a flavor, image and subnet to use for this instance, but when I try to launch it with: openstack server create --image cirros --flavor f1.small --nic net-id=3fd14704-8482-4cdd-975d-6e9e0a14e61e vm-cirros-1 I get an Error and iget the following output from openstack server show. > controller-0:~$ openstack server show vm-cirros-1 > +-------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ > | Field | Value | > +-------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ > | OS-DCF:diskConfig | MANUAL | > | OS-EXT-AZ:availability_zone | | > | OS-EXT-SRV-ATTR:host | None | > | OS-EXT-SRV-ATTR:hypervisor_hostname | None | > | OS-EXT-SRV-ATTR:instance_name | instance-00000001 | > | OS-EXT-STS:power_state | NOSTATE | > | OS-EXT-STS:task_state | None | > | OS-EXT-STS:vm_state | error | > | OS-SRV-USG:launched_at | None | > | OS-SRV-USG:terminated_at | None | > | accessIPv4 | | > | accessIPv6 | | > | addresses | | > | config_drive | | > | created | 2019-09-18T21:26:48Z | > | fault | {u'message': u'Exceeded maximum number of retries. Exhausted all hosts available for retrying build failures for instance 9525360e-6ac6-4da1-a0dd-8f5d8c82ee75.', u'code': 500, u'details': u' File "/var/lib/openstack/lib/python2.7/site-packages/nova/conductor/manager.py", line 627, in build_instances\n raise exception.MaxRetriesExceeded(reason=msg)\n', u'created': u'2019-09-18T21:27:00Z'} | > | flavor | f1.small (15efd6ca-c402-4aba-819a-8ab323d9f482) | > | hostId | | > | id | 9525360e-6ac6-4da1-a0dd-8f5d8c82ee75 | > | image | cirros (88a002f8-ba00-4aa3-9920-66f126fd2efc) | > | key_name | None | > | name | vm-cirros-1 | > | project_id | 64f69c36cfd44c96802b40a3534d8906 | > | properties | | > | status | ERROR | > | updated | 2019-09-18T21:27:00Z | > | user_id | 079d6c910606497c9e9329bb81f9afb4 | > | volumes_attached | | > +-------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ More logs needed? Where do I look? Thoughts? Sau!

1 1

[Starlingx-discuss] Community meetings and use of Zoom
by Cobbley, David A 19 Sep '19

19 Sep '19

We have had an issue arise lately when our community meetings are adjacent to each other. As you know, we use a limited version of Zoom to allow community members and sub project teams to meet and do their work. Unfortunately, the Zoom license we have for StarlingX only allows *one meeting* to occur at a time. That requires *all* participants to immediately drop at the end of each meeting, or subsequent meetings will not be able to start. Each of us should keep that in mind, and as soon as a StarlingX project or community meeting has ended, you should immediately exit that meeting on Zoom so another meeting can get started. For our Wednesday weekly community meeting, we have added a note to the end of the agenda each week to remind you of the importance of exiting the meeting as soon as Bill has declared it finished. We appreciate your efforts to close out your instances of our meetings as quickly as you can when they have ended. Thank you, -- David Cobbley

1 0

[Starlingx-discuss] system lock fail and then can't unlock
by Ezpeer Chen 19 Sep '19

19 Sep '19

Dear all, I want to use system host-lock and then system host-unlock to reboot. But is cause task always locking. It also shows that "vim_progress_status | services-disable-failed." Log: [sysadmin@controller-0 ~(keystone_admin)]$ system host-lock controller-0 +---------------------+--------------------------------------------+ | Property | Value | +---------------------+--------------------------------------------+ | action | none | | administrative | unlocked | | availability | available | | bm_ip | None | | bm_type | None | | bm_username | None | | boot_device | /dev/disk/by-path/pci-0000:00:11.5-ata-3.0 | | capabilities | {u'stor_function': u'monitor'} | | config_applied | 1a574443-db19-4338-86c6-d0b3c2afd3ce | | config_status | None | | config_target | 1a574443-db19-4338-86c6-d0b3c2afd3ce | | console | tty0 | | created_at | 2019-09-10T10:15:49.779617+00:00 | | hostname | controller-0 | | id | 1 | | install_output | text | | install_state | None | | install_state_info | None | | inv_state | inventoried | | invprovision | provisioned | | location | {} | | mgmt_ip | 192.168.204.3 | | mgmt_mac | 00:00:00:00:00:00 | | operational | enabled | | personality | controller | | reserved | False | | rootfs_device | /dev/disk/by-path/pci-0000:00:11.5-ata-3.0 | | serialid | None | | software_load | 19.08 | | subfunction_avail | available | | subfunction_oper | enabled | | subfunctions | controller,worker | | task | Locking | | tboot | false | | ttys_dcd | None | | updated_at | 2019-09-19T06:32:21.003163+00:00 | | uptime | 372 | | uuid | 86ccb737-a20b-4cea-86ae-50032383cde8 | | vim_progress_status | services-disabled | +---------------------+--------------------------------------------+ [sysadmin@controller-0 ~(keystone_admin)]$ system host-unlock controller-0 Avoiding 'unlock' action on already 'unlocked' host controller-0 [sysadmin@controller-0 ~(keystone_admin)]$ system host-unlock controller-0 Avoiding 'unlock' action on already 'unlocked' host controller-0 [sysadmin@controller-0 ~(keystone_admin)]$ system host-lock controller-0 +---------------------+--------------------------------------------+ | Property | Value | +---------------------+--------------------------------------------+ | action | none | | administrative | unlocked | | availability | available | | bm_ip | None | | bm_type | None | | bm_username | None | | boot_device | /dev/disk/by-path/pci-0000:00:11.5-ata-3.0 | | capabilities | {u'stor_function': u'monitor'} | | config_applied | 1a574443-db19-4338-86c6-d0b3c2afd3ce | | config_status | None | | config_target | 1a574443-db19-4338-86c6-d0b3c2afd3ce | | console | tty0 | | created_at | 2019-09-10T10:15:49.779617+00:00 | | hostname | controller-0 | | id | 1 | | install_output | text | | install_state | None | | install_state_info | None | | inv_state | inventoried | | invprovision | provisioned | | location | {} | | mgmt_ip | 192.168.204.3 | | mgmt_mac | 00:00:00:00:00:00 | | operational | enabled | | personality | controller | | reserved | False | | rootfs_device | /dev/disk/by-path/pci-0000:00:11.5-ata-3.0 | | serialid | None | | software_load | 19.08 | | subfunction_avail | available | | subfunction_oper | enabled | | subfunctions | controller,worker | | task | Locking | | tboot | false | | ttys_dcd | None | | updated_at | 2019-09-19T06:33:29.533163+00:00 | | uptime | 442 | | uuid | 86ccb737-a20b-4cea-86ae-50032383cde8 | | vim_progress_status | services-disabled | +---------------------+--------------------------------------------+ [sysadmin@controller-0 ~(keystone_admin)]$ system host-unlock controller-0 Avoiding 'unlock' action on already 'unlocked' host controller-0 [sysadmin@controller-0 ~(keystone_admin)]$ system host-lock controller-0 +---------------------+--------------------------------------------+ | Property | Value | +---------------------+--------------------------------------------+ | action | none | | administrative | unlocked | | availability | available | | bm_ip | None | | bm_type | None | | bm_username | None | | boot_device | /dev/disk/by-path/pci-0000:00:11.5-ata-3.0 | | capabilities | {u'stor_function': u'monitor'} | | config_applied | 1a574443-db19-4338-86c6-d0b3c2afd3ce | | config_status | None | | config_target | 1a574443-db19-4338-86c6-d0b3c2afd3ce | | console | tty0 | | created_at | 2019-09-10T10:15:49.779617+00:00 | | hostname | controller-0 | | id | 1 | | install_output | text | | install_state | None | | install_state_info | None | | inv_state | inventoried | | invprovision | provisioned | | location | {} | | mgmt_ip | 192.168.204.3 | | mgmt_mac | 00:00:00:00:00:00 | | operational | enabled | | personality | controller | | reserved | False | | rootfs_device | /dev/disk/by-path/pci-0000:00:11.5-ata-3.0 | | serialid | None | | software_load | 19.08 | | subfunction_avail | available | | subfunction_oper | enabled | | subfunctions | controller,worker | | task | Locking | | tboot | false | | ttys_dcd | None | | updated_at | 2019-09-19T06:33:37.166469+00:00 | | uptime | 442 | | uuid | 86ccb737-a20b-4cea-86ae-50032383cde8 | | vim_progress_status | services-disabled | +---------------------+--------------------------------------------+ [sysadmin@controller-0 ~(keystone_admin)]$ [sysadmin@controller-0 ~(keystone_admin)]$ system host-show controller-0 +---------------------+----------------------------------------------------------------------+ | Property | Value | +---------------------+----------------------------------------------------------------------+ | action | none | | administrative | unlocked | | availability | available | | bm_ip | None | | bm_type | None | | bm_username | None | | boot_device | /dev/disk/by-path/pci-0000:00:11.5-ata-3.0 | | capabilities | {u'stor_function': u'monitor', u'Personality': u'Controller-Active'} | | config_applied | 1a574443-db19-4338-86c6-d0b3c2afd3ce | | config_status | None | | config_target | 1a574443-db19-4338-86c6-d0b3c2afd3ce | | console | tty0 | | created_at | 2019-09-10T10:15:49.779617+00:00 | | hostname | controller-0 | | id | 1 | | install_output | text | | install_state | None | | install_state_info | None | | inv_state | inventoried | | invprovision | provisioned | | location | {} | | mgmt_ip | 192.168.204.3 | | mgmt_mac | 00:00:00:00:00:00 | | operational | enabled | | personality | controller | | reserved | False | | rootfs_device | /dev/disk/by-path/pci-0000:00:11.5-ata-3.0 | | serialid | None | | software_load | 19.08 | | subfunction_avail | available | | subfunction_oper | enabled | | subfunctions | controller,worker | | task | | | tboot | false | | ttys_dcd | None | | updated_at | 2019-09-19T06:34:33.201421+00:00 | | uptime | 507 | | uuid | 86ccb737-a20b-4cea-86ae-50032383cde8 | | vim_progress_status | services-disable-failed.. | +---------------------+----------------------------------------------------------------------+ [sysadmin@controller-0 ~(keystone_admin)]$ system host-lock controller-0 +---------------------+--------------------------------------------+ | Property | Value | +---------------------+--------------------------------------------+ | action | none | | administrative | unlocked | | availability | available | | bm_ip | None | | bm_type | None | | bm_username | None | | boot_device | /dev/disk/by-path/pci-0000:00:11.5-ata-3.0 | | capabilities | {u'stor_function': u'monitor'} | | config_applied | 1a574443-db19-4338-86c6-d0b3c2afd3ce | | config_status | None | | config_target | 1a574443-db19-4338-86c6-d0b3c2afd3ce | | console | tty0 | | created_at | 2019-09-10T10:15:49.779617+00:00 | | hostname | controller-0 | | id | 1 | | install_output | text | | install_state | None | | install_state_info | None | | inv_state | inventoried | | invprovision | provisioned | | location | {} | | mgmt_ip | 192.168.204.3 | | mgmt_mac | 00:00:00:00:00:00 | | operational | enabled | | personality | controller | | reserved | False | | rootfs_device | /dev/disk/by-path/pci-0000:00:11.5-ata-3.0 | | serialid | None | | software_load | 19.08 | | subfunction_avail | available | | subfunction_oper | enabled | | subfunctions | controller,worker | | task | Locking | | tboot | false | | ttys_dcd | None | | updated_at | 2019-09-19T06:35:21.167957+00:00 | | uptime | 507 | | uuid | 86ccb737-a20b-4cea-86ae-50032383cde8 | | vim_progress_status | | +---------------------+--------------------------------------------+ [sysadmin@controller-0 ~(keystone_admin)]$ system host-unlock controller-0 Avoiding 'unlock' action on already 'unlocked' host controller-0 [sysadmin@controller-0 ~(keystone_admin)]$ system host-lock controller-0 +---------------------+--------------------------------------------+ | Property | Value | +---------------------+--------------------------------------------+ | action | none | | administrative | unlocked | | availability | available | | bm_ip | None | | bm_type | None | | bm_username | None | | boot_device | /dev/disk/by-path/pci-0000:00:11.5-ata-3.0 | | capabilities | {u'stor_function': u'monitor'} | | config_applied | 1a574443-db19-4338-86c6-d0b3c2afd3ce | | config_status | None | | config_target | 1a574443-db19-4338-86c6-d0b3c2afd3ce | | console | tty0 | | created_at | 2019-09-10T10:15:49.779617+00:00 | | hostname | controller-0 | | id | 1 | | install_output | text | | install_state | None | | install_state_info | None | | inv_state | inventoried | | invprovision | provisioned | | location | {} | | mgmt_ip | 192.168.204.3 | | mgmt_mac | 00:00:00:00:00:00 | | operational | enabled | | personality | controller | | reserved | False | | rootfs_device | /dev/disk/by-path/pci-0000:00:11.5-ata-3.0 | | serialid | None | | software_load | 19.08 | | subfunction_avail | available | | subfunction_oper | enabled | | subfunctions | controller,worker | | task | Locking | | tboot | false | | ttys_dcd | None | | updated_at | 2019-09-19T06:36:15.197604+00:00 | | uptime | 572 | | uuid | 86ccb737-a20b-4cea-86ae-50032383cde8 | | vim_progress_status | services-disable-failed.. | +---------------------+--------------------------------------------+ [sysadmin@controller-0 ~(keystone_admin)]$

2 1

[Starlingx-discuss] Trying to set simple password for sysadmin
by Pratik M. 19 Sep '19

19 Sep '19

Hi, I can't figure out how to relax the PAM password policy for sysadmin user on private hosts. Have tried: 1. Removing enforce_root in /etc/pam.d/common-password and setting via root 2. Removing all *credit in /etc/pam.d/common-password 2. Setting all *credit to 0 in /etc/security/pwquality.conf Thanks in advance Pratik

1 0