September 2018 - Starlingx-discuss

[Starlingx-discuss] Bug Handling Process >> Proposal for notgating tag
by Khalil, Ghada 20 Sep '18

20 Sep '18

Hello all, In StarlingX, we currently use labels for target releases for Features/Enhancements as well as bugs [0]: Example: stx.2018.10 (October Release), stx.2019.03 (March Release). For low priority bugs or enhancements which may not have a target release, I was thinking to use a specific tag to indicate that they do not gate any release - stx.ng or stx.notgating. This would help with the screening/prioritization process. Right now, we leave them blank (w/o a release tag), but it's harder to tell if they have been reviewed or not. I like the idea of having an explicit release better. Any thoughts or concerns? [0] https://wiki.openstack.org/wiki/StarlingX/Tags_and_Prefixes Thanks, Ghada From: Khalil, Ghada Sent: Monday, September 17, 2018 6:23 PM To: 'starlingx-discuss(a)lists.starlingx.io' Subject: Bug Handling Process / Useful Launchpad Bugs / Focus on stx.2018.10 Bugs Hello all, I've documented details of the StarlingX Bug Handling process on the wiki: https://wiki.openstack.org/wiki/StarlingX/Defect_Handling_Process Please review and let me know if you have any feedback. All feedback is welcome. In the above wiki, I have included links to useful Launchpad bugs: https://wiki.openstack.org/wiki/StarlingX/Defect_Handling_Process#Key_Starl… With the team's focus on stx.2018.10, I have created specific queries for the release. Project Leads, Please have a look at the unassigned stx.2018.10 bugs and assign to the team accordingly. Please also track all stx.2018.10 bugs to resolution as part of your regular team meetings/communication. Thanks, Ghada Ghada Khalil, Manager, Titanium Cloud, Wind River direct 613.270.2273 skype ghada.khalil.ottawa 350 Terry Fox Drive, Suite 200, Kanata, ON K2K 2W5

4 3

[Starlingx-discuss] [Docs] Publish StarlingX governance from an access controlled git repo
by Jones, Bruce E 20 Sep '18

20 Sep '18

I've just created a new story for this work [0]. Docs team, please review the story and tasks, and update as needed. And feel free to sign up for the tasks :). Brucej [0] https://storyboard.openstack.org/#!/story/2003821

1 0

[Starlingx-discuss] Minutes: StarlingX Networking meeting - 9/20
by Khalil, Ghada 20 Sep '18

20 Sep '18

The StarlingX networking team had their first meeting on 8/30. Weekly meetings are scheduled for Thursday at 9am Eastern. Meeting Details are available on the wiki: https://wiki.openstack.org/wiki/StarlingX/Networking Meeting agenda/notes are captured at: https://etherpad.openstack.org/p/stx-networking Team Meeting Agenda/Notes - Sept 20/2018 * Neutron Blueprint Status / Next Steps * Provider Network Management -- Highest priority ? Merge the Segment Range Management in this spec: https://review.openstack.org/579411 ? Also include the current API (w/o the Host Management piece) ? Rename to Provider Segment Range Configuration ? Action: Ruijing<?> to add a note to the current spec review saying we will re-work the spec based on the feedback from PTG and re-publish it. Fcst: Sept 21 ? Next Step: Ruijing<?> to re-work the spec. Time-Line: 1-2wks to have the updated spec. Fcst: Sept 28-Oct5 * Action: Forrest to confirm the resourcing for this work * System Host Management ? neutron community did not agree to move forward with this spec. The neutron spec will not be pursued any further. ? Action: Ruijing<?> to add a note to the gerrit review and mark the review as Abandoned. Fcst: Sept 21 ? Plan is to move this functionality to the stx-nfv project * Use the neutron APIs from stx-nfv. Need to prototype the use of admin_state_up / admin_state_down o This may drive an Enhancement Request into neutron. Neutron team was open to this. ? Next Step: Matt to write story in SB describing the requirements. * After consultation with the Technical Lead for stx-nfv, he advised us to defer this work for a while as the code is undergoing churn due to containerization support. * We will revisit this again in a few weeks - October 18 * Rescheduling of DHCP Servers and Routers ? neutron community did not agree to move forward with this spec. The neutron spec will not be pursued any further. ? Action: Ruijing<?> to add a note to the gerrit review and mark the review as Abandoned. Fcst: Sept 21 ? Plan is to move this functionality to the stx-nfv project * Implement a plugin in the stx-nfv vim to do the re-scheduling ? Next Step: Matt to capture requirements in SB. Note: This will be included in the same story as the "System Host Management" since they are closely related * Fault Management ? Plan is to not pursue this spec with neutron. The corresponding gerrit review will be abandoned. ? Action: Ruijing<?> to add a note to the review and mark the review as Abandoned. Fcst: Sept 21 ? For now, leave the patch in stx-neutron as is. This is broader than just neutron, same hooks exist in glance/cinder/etc. Need a larger discussion/decision. ? Put on hold for now. * ML2 Connection Auditing and Monitoring ? Plan is to review the current neutron logging capabilities to see if it is sufficient to diagnose issues * Neutron team is open to receiving Enhancement Requests if needed. ? Action: Forrest to confirm the resourcing for this work * Other Neutron Upstreaming Patches - Bugs * Not reviewed in the meeting * stx.2018.10 Status * 2 features planned and on track * 6 bugs: 2 well understood, 2 need more info, 2 need further investigation ? Kailun to follow up on https://bugs.launchpad.net/starlingx/+bug/1790252 * ovs-dpdk Enhancements - stx.2019.03 * Kailun working on OVS-DPDK Firewall Driver Enhancements. ? Facing some issues <Kailun to update with details>. Steve to send output from his system. Regards, Ghada

1 0

[Starlingx-discuss] [Build] [meetings] September 17 - meeting minutes
by Lara, Cesar 20 Sep '18

20 Sep '18

Attendees Mario, Memo, Hayde, Erich, Jason, Scott, Bruce, Saul,Chuy Agenda -Scoping and planning for first release of sxtb tool (all) -Installer consolidation for starling X https://bugs.launchpad.net/starlingx/+bug/1790213 Installer consolidation - We are seeing differences in the packages contained in the installer for StarlingX once the ISO is being built, apparently we have two different approaches on generating the installer files, we need to consolidate and adopt a single set of instructions to generate installer files. More information on this topic for consolidation of files and instructions - Ken Stxb tool - not ready for release yet as we are missing a few scenarios to standardize on a single tool, on initial scope, stxb tool was set as a "getting started" kind of thing, not meant to go after developers use case. A lot of comments on the code and the implementation of the logic behind the toll were raised, we will still discussing around the first scope and if this meets the criteria to be released in the next few weeks. November release out of scope for stxb tool. Regards Cesar Lara Software Engineering Manager OpenSource Technology Center

2 1

[Starlingx-discuss] RFC: Updated governance doc on the wiki
by Jones, Bruce E 20 Sep '18

20 Sep '18

I have updated our draft Governance document based on feedback from the PTG. Please review and send me any feedback you have. https://wiki.openstack.org/wiki/Starlingx/Initial_Governance Thank you! brucej

3 4

[Starlingx-discuss] Analysis of patch 170f4be for StartlingX upstreaming
by Xu, Chenjie 20 Sep '18

20 Sep '18

Hi Matt, We are analyzing the patch 170f4be. This patch add an "audit" flag into fdb but I find that ovs agent don't process this flag. Wondering if this flag is processed by avs agent? Best Regards, Xu, Chenjie

1 0

[Starlingx-discuss] Merge f/centos75 feature branch into master
by Dean Troyer 20 Sep '18

20 Sep '18

I have proposed the 4 reviews to merge the f/centos75 feature branch into master[0]. When approved we should consider the feature branch closed. Please let me know if you see anything odd about this as it is the first re-merge of a feature branch for us... Thanks dt [0] https://review.openstack.org/#/q/topic:merge-f/centos75+(status:open+OR+sta… -- Dean Troyer dtroyer(a)gmail.com

2 1

[Starlingx-discuss] ceph upgrading PR and summary.
by Shang, Dehao 19 Sep '18

19 Sep '18

Hi: This is just draft PR for ceph upgrading. Please feel free to give your advices. PR 1: change cephfs1 into cephfs2 https://github.com/shangdehao1/stx-upstream/commit/d612093fab072afb4fb9d054… PR 2 : ceph13.2.0 need to download new packages : PR: https://github.com/shangdehao1/stx-tools/commit/09abdefc37ba70f452c5998390c… PR 3: don't ignore files at compress process. ( TODO : better method to replace it) PR: https://github.com/shangdehao1/stx-root/commit/1bedca4609fbca06746f7bbfda27… PR4: ceph 13.2.0 commit id. https://github.com/shangdehao1/stx-integ/commit/1ab1d71591faa7ddf83b2cd7d53… How to create ceph13.2.0 repo 1: wget http://cbs.centos.org/kojifiles/packages/ceph/13.2.0/0.el7/src/ceph-13.2.0-… 2: rpm2cpio ceph-13.2.0-0.el7.src.rpm | cpio -div 3: tar -xvjf ceph-13.2.0.tar.bz2 4:modify ceph.spce 1: disable python3 2: apply the patch<https://github.com/ceph/ceph/commit/6af10cae66bfd2fd31ead1ad5ef187a6a4d25ac…> to solve the conflict between openstack-keystone and ceph 13.2.0 3: modify ceph version: namely 0.el7%{?_tis_dist}.%{tis_patch_ver} 4: modify compress format into tar.gz 5: disbale some useless package. Ceph debug info package Ceph dashboard TODO: refer to stx-ceph, to disable more package. Next step: 1: for PR 3, at compress process, still ignore this useless files, but for ceph, need to include these files. 2: in order to speed up building, need to disable useless packages. 2: integrate stx-ceph patch into ceph13.2.0 3: testing at runtime. Thanks Dehao

1 0

[Starlingx-discuss] Analysis of patch 4ae5a58 for StartlingX upstreaming
by Xu, Chenjie 19 Sep '18

19 Sep '18

Hi Matt, We analyze the patch 4ae5a58 related to l2pop. An RFE has been written(You can find it in the attachment). Could you please help to review and comment? Thanks very much! Best Regards, Xu, Chenjie

3 7

[Starlingx-discuss] Weekly project team call notes
by Jones, Bruce E 19 Sep '18

19 Sep '18

Here are the notes from today's call, which can also be found on https://etherpad.openstack.org/p/stx-status brucej Agenda and Notes for the Sep 19th call * PTG Update o Review comments on the draft Feature Dev process (Bruce) ? Ian to take the first shot at a Spec template (in the spec repo) o Review comments on the Governance draft (Bruce) ? Bruce (and team) to review Dean's comments o New Multi-OS sub-project (Bruce) ? Bruce to start up wiki page, arrange call with Ildiko. Brent, Saul, Cesar, Yong, Scott, Abraham, Victor all possible team members. o Containerized Services update (Brent) ? Brent to update the team at next week's call - needs 60 minutes o Project de-coupling update (Brent) ? Next step is to split/decouple sys inventory, break down into inventory and config mangement. Spec to come shortly. o Investing in StoryBoard development (Bruce) ? Looking for volunteers to help with the SB Web UI and add content. o Edge WG Update / slides (Greg) o Update from discussion with the OpenStack User Committee (Ian) ? How do we want to work with the broader OpenStack community? Beginning of the dialog. * Update from the OpenStack BoD meeting - Dean o No big surprises. Proposal made for how to manage strategic initiaitives and pilot projects. Focus areas and pilot projects are not strongly connected, no focus area governance model (yet). We are a pilot progress and within 18 months will be reviewed by the BoD who will decide if our project is viable/active/open. o Proposal made to add a new "Silver" Foundation membership level. * Release status (Ghada) o We reviewed status of features and bugs. Bug count is 15 for the release. Teams have queries for their bugs on each wiki page. Features are mostly on track, but we're going to delay the qemu upgrade to 3.0. o We need to help Ghada with bug triage. Ada can help. Other volunteers for the virtual team welcome! Brent to help. Another volunteer whose name I missed. * Forum session proposals (ildikov/gwaines) o https://etherpad.openstack.org/p/StarlingXBerlinForumBrainstorming * CentOS 7.5 update - ready to merge? Yes - approved to merge. Dean to rebase one last time from master. * stxb tool - feedback, concerns, status... (Cesar) o To be discussed in more depth at the Cores call tomorrow. * Status from other teams / issues * Help needed?

1 0