Answering your questions below about deleted stub topics... Yes, leading up to the R2 release, some of the empty stub topics were deleted. But the plan is not forgotten or lost. We are queuing up content for a new "configuration guide" landing page that will contain refactored and optimized content that was in the old stubs. These are roughed-out sub-tasks in this story: https://storyboard.openstack.org/#!/story/2006289 For the R2 launch, temporarily removing some of the stub topics made the left pane nav much cleaner and more usable while setting the stage for our larger plan to cover a variety of topics in the new advanced configuration guide. You'll see the structure for that in the coming weeks when we add the landing page. For example, the old stubs for OpenStack and Kubernetes with "content coming soon" statements potentially confused users, taking away from the OpenStack and Kubernetes content that does exist in the basic installation and deployment at https://docs.starlingx.io/deploy_install_guides/index.html. Going forward, the optional/advanced OpenStack and Kubernetes content will be available from the configuration guide landing page along with other topics. -- Mike -----Original Message----- From: Jones, Bruce E <bruce.e.jones@intel.com> Sent: Friday, September 13, 2019 11:31 AM To: Zvonar, Bill <Bill.Zvonar@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Community Call (Sep 11, 2019) Re: my AR below - the work items in the documentation can be found here: [1]. The gaps in the documentation tree used to be self-documenting - there were many placeholder documents showing where docs are needed. While I was out, these stub documents were deleted. Why? And if they were deleted, why didn't someone create Stories for them? Now we're going to have to re-create all of that. Brucej [1] https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.docs -----Original Message----- From: Zvonar, Bill [mailto:Bill.Zvonar@windriver.com] Sent: Wednesday, September 11, 2019 8:28 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Community Call (Sep 11, 2019) Notes from today's meeting... - standing topics - any reviews that need attention? - nothing this week - sanity - any reds since last call? - nope - any unanswered calls for assistance on the mailing list? - issue with running on ansible playbook - Saichandu/Pavan from Calsoft: nothing on mailing list - Saichandu/Pavan to re-send to the mailing list, it doesn't seem to be there - offline installation for StarlingX R2.0 http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/005909.... - we don't seem to have this documented yet - raises the general issue of how we get features documented - there were relevant features in 2.0 (private docker registry, docker proxy) - there's a 3.0 task list that Mike's tracking: https://storyboard.openstack.org/#!/story/2006289 - Cindy suggested a per-story task for capturing user documentation - Don suggested adding the docs repo to the manifest for repo sync - makes it visible - AR: Don change the manifest - docs, zuul-jobs & test - AR: Bruce identify the feature documentation gaps - Ildiko suggested documenting the process of adding customer documentation to the contributor guide - AR: Ildiko will look into this - vm boot from big size image timeout: vm boot from big size image timeout http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/005910.... - he's in Forrest's team - Forrest to check if this got sorted out - 3.0 milestone-2 (Ghada) - decent progress - Code Merge Dates - A few features have merge dates beyong MS-3: Containerize Ceph, Containerize OVS-DPDK, B&R for openstack (likely won't make stx.3.0), DC for openstack (won't make stx.3.0) - Agreed that Feature Test can be lag MS-3 by two weeks (Oct 30) - Action: Ada to review and confirm that most features can come in by that date - The current exception is Containerized Ceph. Current Feature Test Date: Nov 8 - repo restructuring - http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/005938.... - all done except for the to-be-renamed system-client (nee: cgcs-client) - AR: Build Team to sort out how/when to finish this off - some options are available - project sub-team re-alignment - sgw - reviews are in progress - https://review.opendev.org/#/c/680514/ - need to close on this in the next 1-2 weeks for it to be in effect for the upcoming election - AR: something! - release notes - don't close a feature w/out doing release notes! (per release team meeting last week) - when code is changed that impacts our Documentation, should the person making the change also change the documents? - http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/005925.... - Root Ara report removed from Zuul Jobs - Clark Boylan email http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/005931.... - no comments on this - server usage audit log API in Nova - Dean's email http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/005951.... - per Dean, we're ok (based on input from Gerry Kopec) - Dean further noted that this *was* in an OpenStack patch that didn't get upstreamed to Nova - StarlingX Beijing meetup - Sep 20th - Cindy's email http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/005956.... - Open Action Required (AR) Summary - (see https://etherpad.openstack.org/p/stx-status-archive for archived actions) - <date task was assigned> -- <owner> -- <description + comments> - July 31, 2019 -- Ada/Numan -- combine sanity runs/reports - Sep 11/19: proposal was presented yesterday in the test meeting - working on getting Pytest running - Aug 14/19: they started discussing how to do this, a formal proposal is pending - Aug 7/19: Numan: will discuss w/ Ada this week, won't start until after 2.0 - Ada: Ada's team will do both, Numan will do RC1 and occasionally Master - it'll be run daily on both, for now anyways - if there are issues running on the virtualized environment, which branch should we focus on - <add here> - June 26, 2019 -- Numan/Yang -- arrange an automation framework info session for the Community - Sep 11/19: Cindy asked about the newly created stx-test repo - Al noted that Don just adding this to the manifest & anyone can contribute - Numan: it's in progress, plan to do it after 2.0 (or right near the end) - any Q&A before then will be appreciated - Ada noted that they've started to look at it a bit - June 26, 2019 -- Abraham -- provide a forecast for providing a Docker image list - Aug 21/19: Bill to ask Abraham for an update - per http://lists.starlingx.io/pipermail/starlingx-discuss/2019-June/005063.html - July 3: opened https://bugs.launchpad.net/starlingx/+bug/1834504, assigned to build team (Abraham) - June 5, 2019 --- <COMMUNITY> -- provide requirements/input on Community Activity Dashboard (see notes from June 5 meeting) - Sep 5: Thierry added "Individual Contributor" page, see his email http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/005913.... - see https://starlingx.biterg.io/ & https://etherpad.openstack.org/p/stx-bitergia - Aug 14: several updates from Thierry on the stx-bitergia etherpad - July 3: see updates on stx-bitergia etherpad - June 19: added github repos & ansible-playbooks repo; request to see which commits a contributor has done - May 8, 2019 -- <LOOKING FOR A VOLUNTEER> -- follow up with CENGN on storage for really large files for reference in Launchpads - Aug 21/19: Bill to ask the Build team to be tracking this as well, if they're not already - Aug 14: CENGN ready to do a trial - need a volunteer to work on this with CENGN (probably ~2-3 days of effort over a few weeks) - need to make sure that it's only StarlingX stuff being put there, some kind of monitoring job to do cleanup, etc. - July 31: CENGN is setting up a PoC for us, no firm date - July 24: waiting on CENGN - July 3: Frank reached out to CENGN, no response yet - June 5: team feels xv/split is cumbersome, max LP attach size is ~60M - OSF can't change LP directly ? it's owned by Canonical; maybe use http://paste.openstack.org/ ? - Frank to talk to CENGN about them providing the needed storage - May 29: Bruce followed up with the OSF team, the suggested using xv & split to permit logs to be stored within LP's size limits -----Original Message----- From: Zvonar, Bill Sent: Wednesday, September 11, 2019 7:17 AM To: starlingx-discuss@lists.starlingx.io Subject: Community Call (Sep 11, 2019) Hi folks, reminder of the Community call coming up later today. Topics on the agenda include these - feel free to add more at [0]. - 3.0 milestone-2 - repo restructuring - http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/005938.... - release notes - don't close a feature w/out doing release notes! (per release team meeting last week) - when code is changed that impacts our Documentation, should the person making the change also change the documents? - http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/005925.... - Root Ara report removed from Zuul Jobs - Clark Boylan email http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/005931.... - server usage audit log API in Nova - Dean's email http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/005951.... - StarlingX Beijing meetup - Sep 20th - Cindy's email http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/005956.... 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_-_Co... [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190911T1400 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss