July 2019 - Starlingx-discuss - lists.starlingx.io

Re: [Starlingx-discuss] Community Call (July 17, 2019)
by Zvonar, Bill 18 Jul '19

18 Jul '19

>From today's call... - sanity - any red sanities since last Community meeting? - nothing this week - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.sanity - reviews in need of attention - nothing this week - documentation update (Mike Tullis) - wiki cleanup, doc updates, 2.0 plan - mega spec - there are stories for all the 2.0 gating work - many are closed, some left to do - doc team committing to get those done - <link goes here> - wiki updates - removing conflicts - see https://docs.google.com/spreadsheets/d/1UJjUttsWQRyauATrip0wKGIxSO7DvyetDKm… - focus is now on rows 57-59 in this sheet - Not Planned == Not Applicable (nothing to move from Wiki to Docs) - once they've completed moving wiki content to docs, they plan to delete the wiki page and leave a pointer to the doc - how to track per-build doc changes (say, for installation) - Action: Scott to summarize his view on using the manifest file for this ; Mike to discuss in today's doc meeting - defect trend / gating launchpads - severity vs. importance - severity - Critical (not usable), Major (usable w/ reduced functionality), Minor (usable w/ minor issues) - not query-able in Launchpad, it doesn't have a field - it's a 'suggestion' from the Launchpad creator - gating-ness - based on judgement of the TL/PL for the Launchpad - each sub-team should have the authority to use their judgement to set the gating-ness of their Launchpads - logistics - how frequently do the sub-teams 'gate' their Launchpads - at least once a week - sub-team leaders need to scrub their Mediums and fixing the ones that are truly gating - the part of how we tag issues still needs a bit of alignment, but let's focus on getting stuff fixed - stx.3.0 Milestone-1 - Milestone Criteria: - Release priorities and major features defined. - High level resourcing secured - Candidate list (based on TSC and Project Lead reviews) is available at: - https://docs.google.com/spreadsheets/d/1ZFR-9-riwhIwiBYBmWmi1qOVyHtgJ8Xk_Fa… - Additional features/specs can still be proposed/reviewed/added to the release. - The next milestone is spec freeze which is currently scheduled for the week of August 12. At that point, no new specs will be considered for stx.3.0. - Yong to add some additional items to the list - we agreed to wait til after these have been presented at tomorrow's TSC before declaring Milestone-1 - didn't get to these... next time - bitergia update: see https://etherpad.openstack.org/p/stx-bitergia - first contact update - mailing list responsiveness - see https://etherpad.openstack.org/p/stx-first-contact (at the bottom) - open actions from previous meetings - updates pending: - ACTION: Cindy to send her perspective on "severity" to the mailing list, let the discussion ensue - ACTION: Yong to propose how we could formalize the process of assessing the impact of a bug from different perspectives - ACTION: doc team to do an audit of the wikis to find pages that have stale data and/or isn't properly pointing to the docs site - ACTION: release team make the recommendation re: Blueprints for Backlog in the next TSC meeting - pending - ACTION: Bill start checking if any 'new' people emails are going unresponded - see update here (at bottom): https://etherpad.openstack.org/p/stx-first-contact - ACTION: Dean find out what our options for increasing per mail size limit - ACTION: Bill follow up on status of bitergia changes - see Thierry's updates here: https://etherpad.openstack.org/p/stx-bitergia - for later: - ACTION: Frank update on the forecast for the Docker image list - see https://bugs.launchpad.net/starlingx/+bug/1834504, with build team now - ACTION: Frank to talk to CENGN about getting sufficient space (pending any other parameters from Scott) - ACTION: Scott & Dean to talk about the mechanics for big files - pending Frank's discussions with CENGN - ACTION: Numan & Ada to sort out how aggregate regression reporting will be done (manual & automated) - they have booked a meeting to discuss - ACTION: Numan/Yang arrange an automation framweork info session for the Community (in a few weeks after Yang's vacation - ACTION: Bill check with Ian about the logistics/timing of a mid-cycle meeting -----Original Message----- From: Zvonar, Bill Sent: Tuesday, July 16, 2019 8:40 AM To: starlingx-discuss(a)lists.starlingx.io Subject: Community Call (July 17, 2019) Hi everyone, reminder of the Community Call tomorrow. Topics on the agenda include... - sanity - any red sanities since last Community meeting? - reviews in need of attention - defect trend / gating launchpads - bitergia update: see https://etherpad.openstack.org/p/stx-bitergia - first contact update - mailing list responsiveness - see https://etherpad.openstack.org/p/stx-first-contact (at the bottom) - open actions from previous meetings Please feel free to add topics on the etherpad [0]. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_C… [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190717T1400

3 2

[Starlingx-discuss] proposal for Intel GPU K8s device plugin support in StarlingX
by An, Ran1 18 Jul '19

18 Jul '19

Hi All here is the proposal for enabling intel-gpu-plugin on StarlingX , welcome suggestion and advise. The background: As a part of resource management, kubernetes provides a device plugin framework [2] for vendors to advertise their resources to the kubelet since version 1.8. StarlingX has already supported SR-IOV CNI plugins now [3]. Intel-gpu-plugins is a device plugin implementation [4] for intel GPU (with driver i915). Users could deploy their pods with Intel GPU resource requests or limits, if intel-gpu-plugins was integrated into StarlingX. proposal: Deploy intel-gpu-plugins as a daemon set with node selector "intelgpu: enabled". Kubernetes label "intelgpu: enabled" will be set automatically once the node detected supported GPU device. Details are shown as follows: 1. Build StarlingX plugin docker image based on [5], the implement in starlingx are [6] and [7] 2. Deploy Intel-gpu-plugins daemon set in tasks "bringup_kubemaster" after kubernetes master has been initialized during ansible bootstrap process. Add value "import_plugins" and value list "kube_plugins" as condition of deploying Intel-gpu-plugins daemon set, so user could determine whether Intel-gpu-plugins would be enabled. Create file "/etc/platform/enabled_kube_plugins" and write list "kube_plugins" into the file after active Intel-gpu-plugin daemon if "import_plugins" is true. Partical Implement is [8] 3. Detect supported GPU device with the help of sysinv agent and request to set kubernetes label "intelgpu: enabled" for specific node by calling sysinv conductor rpcapi. Sysinv conductor will check file "/etc/platform/enabled_kube_plugins", and set kubernetes label if the file is exist and intel-gpu-plugins is in list. Partial implement is [9] [1] https://storyboard.openstack.org/#!/story/2005937 [2] https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/d… https://github.com/kubernetes/community/blob/master/contributors/design-pro… [3] https://review.opendev.org/#/c/655495/ [4] https://github.com/intel/intel-device-plugins-for-kubernetes [5] https://github.com/intel/intel-device-plugins-for-kubernetes/blob/master/cm… [6] https://review.opendev.org/668803 [7] https://review.opendev.org/668808 [8] https://review.opendev.org/666510 [9] https://review.opendev.org/666511 Thanks Ran

3 3

[Starlingx-discuss] Proposal for Ceph containerization for StarlingX
by Chen, Tingjie 18 Jul '19

18 Jul '19

Hi, There is proposal for Ceph containerization for StarlingX, welcome review and comments. The background: Ceph is the standard persistent storage backend for starlingx, this story is to implement ceph containerization. In the proposal, we discuss the benefit of containerized Ceph, also give solution and edit design document for the implementation. BP: https://review.opendev.org/#/c/656371 Design doc: https://docs.google.com/document/d/1lnAZSu4vAD4EB62Mk18mCgM7aAItl26sJa1GBf9… SB: https://storyboard.openstack.org/#!/story/2005527 Thanks, Tingjie

1 1

[Starlingx-discuss] How to update StarlingX?
by Marcel Schaible 18 Jul '19

18 Jul '19

Hi, at the moment are running our system with a StarlingX version from around mid June. What is the recommended way to update our installation for e.g adding the StarlingX repository to our installation? In the past we where reinstalling everything, which is a real pain. Thanks Marcel

1 0

[Starlingx-discuss] controller-1 failed after unlock
by Yang, Bin 17 Jul '19

17 Jul '19

Dear StarlingX experts, I am exercising installing starlingx (with latest milestone3 image) with virtualbox following the wiki: https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnStandard I am able to install/provision controller-0, compute-0, but failed to unlock controller-1, the issue seems to be kubelet.service cannot start due to missing of config file at /var/lib/kubelet/config.yaml : controller-1:~# ls /var/lib/kubelet/ -al total 8 drwxr-xr-x. 2 root root 4096 Jun 21 02:27 . drwxr-xr-x. 60 root root 4096 Jul 16 10:43 .. Could anyone who have insight of this issue shed some lights on this issue ? Thanks in advance Below is the daemon log: 2019-07-17T02:06:13.623 controller-1 systemd[1]: info kubelet.service holdoff time over, scheduling restart. 2019-07-17T02:06:13.623 controller-1 systemd[1]: warning Cannot add dependency job for unit dev-hugepages.mount, ignoring: Unit is masked. 2019-07-17T02:06:13.641 controller-1 systemd[1]: info Stopped Kubernetes Kubelet Server. 2019-07-17T02:06:13.647 controller-1 systemd[1]: info Starting Kubernetes Kubelet Server... 2019-07-17T02:06:13.000 controller-1 root: info /usr/bin/kubelet-cgroup-setup.sh(481470): Nothing to do, already configured: /sys/fs/cgroup/cpuset/k8s-infra. 2019-07-17T02:06:13.664 controller-1 systemd[1]: info Started Kubernetes Kubelet Server. 2019-07-17T02:06:13.832 controller-1 kubelet[481475]: info Flag --feature-gates has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information. 2019-07-17T02:06:13.832 controller-1 kubelet[481475]: info Flag --cpu-manager-policy has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information. 2019-07-17T02:06:13.832 controller-1 kubelet[481475]: info F0717 02:06:13.831961 481475 server.go:189] failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "/var/lib/kubelet/config.yaml", error: open /var/lib/kubelet/config.yaml: no such file or directory 2019-07-17T02:06:13.837 controller-1 systemd[1]: notice kubelet.service: main process exited, code=exited, status=255/n/a 2019-07-17T02:06:13.847 controller-1 systemd[1]: notice Unit kubelet.service entered failed state. 2019-07-17T02:06:13.847 controller-1 systemd[1]: warning kubelet.service failed. Best Regards, Bin Yang

2 3

[Starlingx-discuss] Story for adjust timeout value in chart
by Lin, Shuicheng 17 Jul '19

17 Jul '19

Hi Bob, I have created a story [0] to track the task that adjust timeout value of armada's wait in openstack-helm chart. I will do it after stx 2.0 release. Thanks. [0]: https://storyboard.openstack.org/#!/story/2006244 Best Regards Shuicheng

1 0

[Starlingx-discuss] [Containers] Sanity Test - ISO 20190717
by Perez Ibarra, Maria G 17 Jul '19

17 Jul '19

Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Jul-17 (link<http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190717T01…>) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs PASS ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs PASS ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs PASS ] Standard - External Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs PASS ] =========================================== Regards Maria G.

1 0

[Starlingx-discuss] [docs][meetings] docs team meeting minutes 7/17/2019
by Tullis, Michael L 17 Jul '19

17 Jul '19

For notes and new action items from our docs team meeting today, see our etherpad: https://etherpad.openstack.org/p/stx-documentation Join us if you have interest in StarlingX docs! We meet Wednesdays, and call logistics are here: https://wiki.openstack.org/wiki/Starlingx/Meetings. -- Mike

1 0

[Starlingx-discuss] Build Layering and refactoring of repos
by Saul Wold 17 Jul '19

17 Jul '19

Hi Scott, I was reviewing the google spreadsheet [0] you shared during the Build Sub-team [1] meeting last week. I think this is a good direction and I am beginning to understand your logic and urgency around making the changes. I have some comments some of the moves. 1) Did you factor in any of Dean's thoughts about reorgs? email [2] / ethercalc [3] 2) can we remove the stx- prefix from the new repos to start with instead of propagating that given we are inside the starlingx/ namespace alread? 3) not sure if "compile" is right name the layer of packages (go, python, rpm, and bash), does bash really belong here, I don't think we depend on it for the build, do we ? Is there a specific modification to bash that build specific? 4) openstack-helm* I believe is used by stx-platform-helm, at least we saw that dependency with the MultiOS/openSUSE specfiles. 5) Maybe a future move is getting integ/puppet into the toplevel puppet repo and ultimately part of ansible-playbooks if the plan is to convert to ansible. Thanks Sau! [0] https://docs.google.com/spreadsheets/d/1zURL1UlDST8lnvw3dMlNWN6pkLX6EVF6TDB… [1] https://etherpad.openstack.org/p/stx-build [2] http://lists.starlingx.io/pipermail/starlingx-discuss/2019-May/004597.html [3] https://ethercalc.openstack.org/stx-repo-org

2 3

[Starlingx-discuss] July 21 Deadline: Join OSF to Vote in the 2020 Foundation Board Elections
by Ildiko Vancsa 17 Jul '19

17 Jul '19

Hi StarlingX Community, As contributors to StarlingX, a pilot project supported by the OpenStack Foundation (OSF), we want to remind everyone of a benefit of joining the Foundation as an individual member: participating in the annual Foundation Board of Directors election. The OSF board represents all of the projects[1], not just OpenStack, and so it’s important for every community to actively participate, as both voters and candidates, in this election process. If you are not already an OpenStack Foundation member, please consider joining __by July 21__ to have a voice in the 2020 election. It’s free to join and only takes a few minutes to complete the form. Join here: https://www.openstack.org/join/register/?membership-type=foundation Time sensitive! In order to be eligible to vote in the January 2020 Individual Board of Directors election[2] you must join as an Individual Foundation Member no later than __this Sunday, July 21, 2019 at 11:59pm PT__. The OpenStack Foundation Board of Directors provides strategic and financial oversight of Foundation resources and staff. The 24 person Board is composed of directors elected by the Individual Foundation Members (8), directors elected by the Gold Members (8) and directors appointed by the Platinum Members (8). Individual Member Directors are there to represent the Individual Members of the Foundation. These Directors act as the link between the thousands of members of the Foundation and the Board, and are not representing the companies for which they work. Meet the current Board of Directors[3], and learn more here[4]. For further OpenStack Foundation updates and news, please sign up for the Foundation mailing list[5]. You can also select the type of content you receive from the OpenStack Foundation here[6]. Best Regards, Ildikó [1] We’re aware that some of the language about the election on openstack.org is still “openstack project” specific, and we’ll be updating that prior to the 2020 elections to more accurately reflect that the OSF Board represents all OSF projects. Please don’t let this dissuade you from joining, if you’re interested in voting! [2] https://www.openstack.org/election/2020-individual-director-election/ [3] https://www.openstack.org/foundation/board-of-directors/ [4] https://www.openstack.org/foundation/ [5] http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation [6] https://www.openstack.org/community/email-signup

1 0