opendev
/
infra-specs
Code Issues Proposed changes

Declare victory on StoryBoard 

The original plan to migrate all OpenStack projects may have been
overly-ambitious, but more importantly it's a policy decision
outside the Infrastructure team's immediate sphere of control. Most
identified gaps in the intervening years have been addressed, with
some final ones (like attachments) under review nearing completion
or well into a planning stage (like self-service team management).
There will always be new features some teams want, and indefinitely
delaying completion of this spec for such a treadmill is
unnecessary.

Update the spec to only cover the original well-established first
phase, and remove the hand-wavy stubs for a second phase where
"everybody agrees to migrate." Also remove the dependency on central
identity management as there is no clear path forward on it
presently. Many teams are already relying on StoryBoard today, and
the handful of developers and maintainers for it hold fairly regular
meetings and can be reached readily with questions, concerns or
suggestions. Further improvement to StoryBoard remains a priority
for them, but it doesn't need to be a priority spec for the
Infrastructure team for that to be the case.

Change-Id: I5092211bfe59646f6db0adae6075b41cb312c6ad
This commit is contained in:
Jeremy Stanley 2019-12-03 23:40:13 +00:00
parent 257392cb41
commit c872f8f6a4
2 changed files with 10 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/source/index.rst
View File

@ -12,14 +12,13 @@ infrastructure developers.
.. toctree::
:maxdepth: 1
specs/task-tracker
specs/update-config-management
Gerrit query for all changes related to priority efforts::
status:open AND (topic:storyboard-migration OR topic:puppet-4 OR topic:update-cfg-mgmt)
status:open AND (topic:puppet-4 OR topic:update-cfg-mgmt)
https://review.openstack.org/#/q/(topic:storyboard-migration+OR+topic:puppet-4+OR+topic:update-cfg-mgmt)+AND+status:open
https://review.openstack.org/#/q/(topic:puppet-4+OR+topic:update-cfg-mgmt)+AND+status:open
Approved Design Specifications
==============================
@ -112,6 +111,7 @@ for historical purposes.
specs/releases-openstack-org
specs/server_base_template_refactor
specs/shade
specs/task-tracker
specs/test-metrics-db
specs/translation_setup
specs/trystack-site

28
specs/task-tracker.rst
View File

@ -178,10 +178,10 @@ Those need to be resolved before we launch the migration operation.
Implementation
==============
Phase 1: Identify and fix remaining gaps
----------------------------------------
Identify and fix remaining gaps
-------------------------------
During this phase, we'd identify all the features that need to be implemented
Identify all the features that need to be implemented
and all the bugs that need to be fixed (including UX glitches) before we can
migrate everyone to StoryBoard. The feature gap analysis should continue no
longer than the remainder of the Newton development cycle in OpenStack, with
@ -200,29 +200,19 @@ some requested features are not suitable to implement at all. Whether the plan
is sufficient for a migration of the OpenStack community should be determined
by the OpenStack Technical Committee.
While phase 1 is going, we should actively on-board new volunteer teams
While this is going, we should actively on-board new volunteer teams
(beyond Infra) which feel ready to use StoryBoard in its current state. This
will hopefully bring more people to contribute to StoryBoard as users scratch
their own itches, creating a virtuous circle.
Phase 2: General migration
--------------------------
Once phase 1 is completed, we should migrate all remaining Launchpad users in
one shot. Migration will be scheduled not less than 1 month following the
technical committee's agreement to migrate.
Assignee(s)
-----------
During phase 1, Kendall Nelson will facilitate the discussion between the
Kendall Nelson will facilitate the discussion between the
StoryBoard team and the rest of the users, and help prioritize the must-have
items. The StoryBoard team would work on implementing the missing features and
fixing the blocker issues.
Phase 2 is mostly led by the infrastructure team and will be implemented as a
separate, followup spec.
Gerrit Topic
------------
@ -235,8 +225,6 @@ Use Gerrit topic "storyboard-migration" for all patches related to this spec.
Work Items
----------
Phase 1:
1. Facilitator identifies feature stakeholders from the OpenStack community
2. Feature stakeholders identify remaining needed features
@ -267,7 +255,7 @@ No new DNS entries should need to be created.
Documentation
-------------
This will require updating a lot of documentation. One of the phase 1 items
This will require updating a lot of documentation. One of the items
would be to identify and update the developer and project creator docs where
needed.
@ -289,6 +277,4 @@ necessary in support of this spec.
Dependencies
============
Before migrating new users, StoryBoard should be plugged into an OpenStack
identity provider (OpenStackID, ipsilon...) and therefore this work should
be completed first.
None.