Agenda and notes - Dec 5th call

• Please register for the January community meeting so we can get a count for logistics (meals, etc...):  https://starlingx_jan2019meetup.eventbrite.com

• Discuss planning process and preparation for the community meet-up.

o Should the agenda be focused on what the teams are doing?  On what features we want to deliver?  Or both?

§ Ian - split the agenda into:  Short term items, big long term items, CI/CD/test, Process & Governance

§ Bruce - my goal for the meeting is to finalize the release plan - content and schedule

§ Ian - another goal is for the TSC to align on the vision for the project

• How do we manage / do planning for features that span sub-project?   How do we track the progress of large complex multi-story features?

§ Adopting a higher level planning tool - e.g. Jira, Trello, etc...?

§ For now using multiple Etherpads to manage and track complex projects

o Discuss alignment with OpenStack milestones and the planning assumptions built into that model.  Release plan to be reviewed with TSC tomorrow.

• Discuss Multi-OS and Zuul project team status since we ran out of time in the Nov 28th meeting.

o Multi-OS status: (Bruce)

§ Spec review status

· Specs still pending: https://review.openstack.org/#/q/status:open+AND+project:%255Eopenstack/stx-specs

o https://review.openstack.org/#/c/619801/

o https://review.openstack.org/#/c/621033/

§ Victor to fix the tox failures (trailing white space/etc...).

§ DevStack status

· https://review.openstack.org/#/c/620988/ - needs reviewers

· https://review.openstack.org/#/c/620806/ - Has self WF-1 from Yi while he runs some last minute checks

· https://review.openstack.org/#/c/616402/ - Mingyuan to respond to Dean's feedback

§ Zuul status (Cesar)

· Has been a lower priority.  Has been some background activity.  Team is not meeting.  Cesar is looking for volunteers to join the team!

· Should this be part of the Test team?

· We should add Test Strategy to the community meeting agenda and have a comprehensive discussion.

• Question from the team working on the FlexRAN demo:  By default, Ironic services are NOT enabled in StarlingX system. What’s the reasons in the background at the first place? BTW, they were not enabled by default in Titanium R5, according to the feedback from FlexRAN team.

o This was a decision made at the seed code release to make it an optional feature to cut down on foot print.  Only useful for bare metal workloads.  This will all be changing in the next release with the new container architecture which will reduce the need for bare metal support (use containers instead).  Bruce to follow up with the team to make sure they are OK with manual steps.