OpenStack - User contributions [en]

StarlingX

2019-10-23T16:44:36Z

Dtroyer: Update Gerrit Review Dashboard links

__NOTOC__
<center>

== Welcome! ==
Welcome to the StarlingX Contributor Community! We're glad you are here. Everything you need to get started with StarlingX is available below. If you have questions or need advice, please reach out to us on the mailing list or IRC - we're here to help!
</center>
----


{| style="border-collapse: separate; border-spacing: 25px;"
|style="vertical-align:top; width:25%;" |

===== Getting Started =====
----
* [[StarlingX/Releases|Releases]]
* [https://www.starlingx.io/ StarlingX web site]
* [https://docs.starlingx.io/ Documentation]
* [https://www.starlingx.io/learn/ Learn more]

|style="vertical-align:top; width:25%;" |

===== Culture =====
----
* [https://www.openstack.org/legal/community-code-of-conduct/ Code of Conduct]
* [https://governance.openstack.org/tc/reference/opens.html The Four Opens]

|style="vertical-align:top; width:25%;" |

===== Communicate =====
----
* [http://lists.starlingx.io/ Email lists]
* IRC: #starlingX@freenode
* [https://docs.openstack.org/infra/manual/developers.html IRC setup]
* [[Starlingx/Meetings|Weekly calls schedule]]
* [https://zoom.us/j/342730236 Weekly calls Zoom]
|style="vertical-align:top; width:25%;" |

===== Developer Resources =====
----
* [https://docs.openstack.org/infra/manual/developers.html Developer Guide]
* [[StarlingX/StarlingX VirtualBox Configuration Guide | VirtualBox Guide]]
* [[StarlingX/StarlingX Packet.com iPXE Installation | StarlingX Packet.com iPXE]]
* [[StarlingX/CodeSubmissionGuidelines|Code Submission Guidelines]]
* [https://docs.starlingx.io/contributor/index.html Contribution guidelines]
* [https://docs.starlingx.io/contributor/api_contribute_guide.html StarlingX API Contributor Guide]
* [https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.helpwanted "Help wanted" bugs]
|}
{| style="border-collapse: separate; border-spacing: 25px;"
|style="vertical-align:top; width:25%;" |


===== User resources =====
----
* [https://docs.starlingx.io/deploy_install_guides/index.html Installation and Deployment Guides]
* [[StarlingX/Platform Features|Hardware platform features]]
* [https://docs.openstack.org/infra/manual/developers.html OpenStack Developer's Guide]
* [https://docs.openstack.org/infra/manual/creators.html OpenStack Project Creator's Guide]
* [https://wiki.openstack.org/wiki/How_To_Contribute OpenStack Contributors Guide]
* [https://governance.openstack.org/tc/reference/project-testing-interface.html OpenStack Project Testing Interface]

|style="vertical-align:top; width:25%;" |


===== Code =====
----
* [https://opendev.org/starlingx Source code repositories]
* [https://review.opendev.org/#/q/status:open+AND+project:%255Estarlingx/%2540 Active code reviews]

|style="vertical-align:top; width:25%;" |


===== Governance =====
----
* [https://docs.starlingx.io/governance/index.html Governance documents]
* [https://docs.starlingx.io/election/ Election documents and results]
* [https://etherpad.openstack.org/p/stx-governance Archive: Draft governance etherpad]
* [[Starlingx/Initial Governance|Archive: Draft governance wiki]]
|style="vertical-align:top; width:25%;" |

===== Meetups & PTGs =====
----
* [https://etherpad.openstack.org/p/stx-PTG-agenda StarlingX Denver 2018 PTG Agenda]
* add link here to the Berlin PTG meeting minutes
* [https://etherpad.openstack.org/p/stx-chandler-meetup Jan 2019 meetup etherpad]
* [https://www.starlingx.io/blog/starlingx-meetup-january-2019.html Jan 2019 meetup blog]
* [https://etherpad.openstack.org/p/stx-ptg-agenda StarlingX Denver 2019 PTG Agenda and Notes]
|}

{| style="border-collapse: separate; border-spacing: 25px;"
|style="vertical-align:top; width:25%;" |

===== Planning & Processes =====
----
* [[StarlingX/Release_Plan|StarlingX Release Planning]]
* [[StarlingX/Feature Development Process|StarlingX Feature Development Process (needs update)]]
* [[StarlingX/Defect Handling Process|StarlingX Defect Handling Process]]
* [[StarlingX/Tags and Prefixes|Tags and Prefixes]]
* [https://storyboard.openstack.org/#!/project_group/86 Storyboard Group]
|style="vertical-align:top; width:25%;" |

===== Useful queries =====
----
* [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.new Newly created stories]
* [https://storyboard.openstack.org/#!/worklist/456 Stories with no sub-project tags]
* [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86 All active stories]
* [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.2.0 All active stories for StarlingX 2.0]
* [https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2.0 All open bugs for StarlingX 2.0].
* [https://review.opendev.org/#/dashboard/?title=StarlingX+Review+Inbox&foreach=%28%0Aproject%3Astarlingx%2Fansible%2Dplaybooks+OR%0Aproject%3Astarlingx%2Fclients+OR%0Aproject%3Astarlingx%2Fcompile+OR%0Aproject%3Astarlingx%2Fconfig+OR%0Aproject%3Astarlingx%2Fconfig%2Dfiles+OR%0Aproject%3Astarlingx%2Fcontainers+OR%0Aproject%3Astarlingx%2Fdistcloud+OR%0Aproject%3Astarlingx%2Fdistcloud%2Dclient+OR%0Aproject%3Astarlingx%2Fdocs+OR%0Aproject%3Astarlingx%2Felection+OR%0Aproject%3Astarlingx%2Ffault+OR%0Aproject%3Astarlingx%2Fgovernance+OR%0Aproject%3Astarlingx%2Fgui+OR%0Aproject%3Astarlingx%2Fha+OR%0Aproject%3Astarlingx%2Fhelm%2Dcharts+OR%0Aproject%3Astarlingx%2Finteg+OR%0Aproject%3Astarlingx%2Fmanifest+OR%0Aproject%3Astarlingx%2Fmetal+OR%0Aproject%3Astarlingx%2Fmonitor%2Darmada%2Dapp+OR%0Aproject%3Astarlingx%2Fmonitoring+OR%0Aproject%3Astarlingx%2Fnfv+OR%0Aproject%3Astarlingx%2Fopenstack%2Darmada%2Dapp+OR%0Aproject%3Astarlingx%2Fplatform%2Darmada%2Dapp+OR%0Aproject%3Astarlingx%2Froot+OR%0Aproject%3Astarlingx%2Fspecs+OR%0Aproject%3Astarlingx%2Fstx%2Dpuppet+OR%0Aproject%3Astarlingx%2Ftest+OR%0Aproject%3Astarlingx%2Ftools+OR%0Aproject%3Astarlingx%2Fupdate+OR%0Aproject%3Astarlingx%2Fupstream+OR%0Aproject%3Astarlingx%2Futilities+OR%0Aproject%3Astarlingx%2Fzuul%2Djobs%0A%29%0Astatus%3Aopen%0ANOT+owner%3Aself%0ANOT+label%3AWorkflow%3C%3D%2D1%0Alabel%3AVerified%3E%3D1%2Czuul%0ANOT+reviewedby%3Aself&Needs+final+%2B2=label%3ACode%2DReview%3E%3D2+limit%3A50+NOT+label%3ACode%2DReview%3C%3D%2D1%2Cself&Passed+Zuul%2C+No+Negative+Feedback+%28Small+Fixes%29=NOT+label%3ACode%2DReview%3E%3D2+NOT+label%3ACode%2DReview%3C%3D%2D1%2Cstarlingx%2Dcore+delta%3A%3C%3D10&Passed+Zuul%2C+No+Negative+Feedback=NOT+label%3ACode%2DReview%3E%3D2+NOT+label%3ACode%2DReview%3C%3D%2D1%2Cstarlingx%2Dcore+delta%3A%3E10&Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode%2DReview%3C%3D%2D1+NOT+label%3ACode%2DReview%3E%3D1+age%3A5d&You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=NOT+label%3ACode%2DReview%3C%3D%2D1%2Cself+NOT+label%3ACode%2DReview%3E%3D1%2Cself+reviewer%3Aself&Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+is%3Areviewed+age%3A2d Gerrit Review Dashboard]
* [https://review.opendev.org/#/dashboard/?title=StarlingX+TSC+Overview&foreach=%28%0Aproject%3Astarlingx%2Fgovernance+OR%0Aproject%3Astarlingx%2Fspecs%0A%29%0Astatus%3Aopen%0ANOT+label%3AWorkflow%3C%3D%2D1%0Alabel%3AVerified%3E%3D1%2Czuul%0ANOT+reviewedby%3Aself&Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode%2DReview%3C%3D%2D1+NOT+label%3ACode%2DReview%3E%3D1+age%3A5d+branch%3Amaster&You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=NOT+label%3ACode%2DReview%3C%3D%2D1%2Cself+NOT+label%3ACode%2DReview%3E%3D1%2Cself+reviewer%3Aself&Needs+final+%2B2=label%3ACode%2DReview%3E%3D2+limit%3A50+NOT+reviewedby%3Aself+NOT+label%3Aworkflow%3E%3D1&Passed+Zuul%2C+No+Negative+Feedback=NOT+label%3ACode%2DReview%3E%3D2+NOT+label%3ACode%2DReview%3C%3D%2D1+limit%3A50+branch%3Amaster&Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2+days%29=NOT+label%3ACode%2DReview%3C%3D%2D1+NOT+label%3ACode%2DReview%3E%3D1+age%3A2d+branch%3Amaster TSC Review Dashboard]

|style="vertical-align:top; width:25%;" |

===== StarlingX sub-projects =====
----
* [[StarlingX/Config|Config project]]
* [[StarlingX/Fault|Fault project]]
* [[StarlingX/HA|HA project]]
* [[StarlingX/GUI|GUI project]]
* [[StarlingX/Metal|Metal project]]
* [[StarlingX/NFV|NFV project]]
* [[StarlingX/Update|Update project]]
* [[StarlingX/DistCloud|Distributed Cloud project]]
* [[StarlingX/Docs_and_Infra|Docs and Infra project]]
* [[StarlingX/Build|Build project]]
* [[StarlingX/DistroOpenStack|Distro - OpenStack project]]
* [[StarlingX/Distro|Distro - Non-OpenStack project]]
* [[StarlingX/Test|Test project]]
* [[StarlingX/Security|Security project]]
* [[StarlingX/Containers|Containers project]]
* [[StarlingX/Networking|Networking project]]
* [[StarlingX/Releases|Releases project]]
* [[StarlingX/MultiOS|MultiOS project]]
* [[StarlingX/Pyton2|Python2 to Python3 Transition]]
* [[StarlingX/Zull|Zuul Enablement and Coverage]]
* [[StarlingX/Devstack|Devstack Integration]]
* [[StarlingX/stxinabox|StarlingX In-a-box]]

|style="vertical-align:top; width:25%;" |

===== Special Interest Groups (SIGs) =====
----
* [[StarlingX/Packet SIG|Packet SIG]]
* [[StarlingX/First Contact SIG|First Contact SIG]]
|}

The previous wiki home page can be found [[StarlingX/Archived wiki home page|here]]

StarlingX

2019-10-09T15:24:22Z

Dtroyer: Add Gerrit Review Dashboard

__NOTOC__
<center>

== Welcome! ==
Welcome to the StarlingX Contributor Community! We're glad you are here. Everything you need to get started with StarlingX is available below. If you have questions or need advice, please reach out to us on the mailing list or IRC - we're here to help!
</center>
----


{| style="border-collapse: separate; border-spacing: 25px;"
|style="vertical-align:top; width:25%;" |

===== Getting Started =====
----
* [[StarlingX/Releases|Releases]]
* [https://www.starlingx.io/ StarlingX web site]
* [https://docs.starlingx.io/ Documentation]
* [https://www.starlingx.io/learn/ Learn more]

|style="vertical-align:top; width:25%;" |

===== Culture =====
----
* [https://www.openstack.org/legal/community-code-of-conduct/ Code of Conduct]
* [https://governance.openstack.org/tc/reference/opens.html The Four Opens]

|style="vertical-align:top; width:25%;" |

===== Communicate =====
----
* [http://lists.starlingx.io/ Email lists]
* IRC: #starlingX@freenode
* [https://docs.openstack.org/infra/manual/developers.html IRC setup]
* [[Starlingx/Meetings|Weekly calls schedule]]
* [https://zoom.us/j/342730236 Weekly calls Zoom]
|style="vertical-align:top; width:25%;" |

===== Developer Resources =====
----
* [https://docs.openstack.org/infra/manual/developers.html Developer Guide]
* [[StarlingX/StarlingX VirtualBox Configuration Guide | VirtualBox Guide]]
* [[StarlingX/StarlingX Packet.com iPXE Installation | StarlingX Packet.com iPXE]]
* [[StarlingX/CodeSubmissionGuidelines|Code Submission Guidelines]]
* [https://docs.starlingx.io/contributor/index.html Contribution guidelines]
* [https://docs.starlingx.io/contributor/api_contribute_guide.html StarlingX API Contributor Guide]
* [https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.helpwanted "Help wanted" bugs]
|}
{| style="border-collapse: separate; border-spacing: 25px;"
|style="vertical-align:top; width:25%;" |


===== User resources =====
----
* [https://docs.starlingx.io/deploy_install_guides/index.html Installation and Deployment Guides]
* [[StarlingX/Platform Features|Hardware platform features]]
* [https://docs.openstack.org/infra/manual/developers.html OpenStack Developer's Guide]
* [https://docs.openstack.org/infra/manual/creators.html OpenStack Project Creator's Guide]
* [https://wiki.openstack.org/wiki/How_To_Contribute OpenStack Contributors Guide]
* [https://governance.openstack.org/tc/reference/project-testing-interface.html OpenStack Project Testing Interface]

|style="vertical-align:top; width:25%;" |


===== Code =====
----
* [https://opendev.org/starlingx Source code repositories]
* [https://review.opendev.org/#/q/status:open+AND+project:%255Estarlingx/%2540 Active code reviews]

|style="vertical-align:top; width:25%;" |


===== Governance =====
----
* [https://docs.starlingx.io/governance/index.html Governance documents]
* [https://docs.starlingx.io/election/ Election documents and results]
* [https://etherpad.openstack.org/p/stx-governance Archive: Draft governance etherpad]
* [[Starlingx/Initial Governance|Archive: Draft governance wiki]]
|style="vertical-align:top; width:25%;" |

===== Meetups & PTGs =====
----
* [https://etherpad.openstack.org/p/stx-PTG-agenda StarlingX Denver 2018 PTG Agenda]
* add link here to the Berlin PTG meeting minutes
* [https://etherpad.openstack.org/p/stx-chandler-meetup Jan 2019 meetup etherpad]
* [https://www.starlingx.io/blog/starlingx-meetup-january-2019.html Jan 2019 meetup blog]
* [https://etherpad.openstack.org/p/stx-ptg-agenda StarlingX Denver 2019 PTG Agenda and Notes]
|}

{| style="border-collapse: separate; border-spacing: 25px;"
|style="vertical-align:top; width:25%;" |

===== Planning & Processes =====
----
* [[StarlingX/Release_Plan|StarlingX Release Planning]]
* [[StarlingX/Feature Development Process|StarlingX Feature Development Process (needs update)]]
* [[StarlingX/Defect Handling Process|StarlingX Defect Handling Process]]
* [[StarlingX/Tags and Prefixes|Tags and Prefixes]]
* [https://storyboard.openstack.org/#!/project_group/86 Storyboard Group]
|style="vertical-align:top; width:25%;" |

===== Useful queries =====
----
* [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.new Newly created stories]
* [https://storyboard.openstack.org/#!/worklist/456 Stories with no sub-project tags]
* [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86 All active stories]
* [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.2.0 All active stories for StarlingX 2.0]
* [https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2.0 All open bugs for StarlingX 2.0].
* [https://review.opendev.org/#/dashboard/?title=StarlingX+Review+Inbox&foreach=%28%0Aproject%3Astarlingx%2Fansible%2Dplaybooks+OR%0Aproject%3Astarlingx%2Fclients+OR%0Aproject%3Astarlingx%2Fcompile+OR%0Aproject%3Astarlingx%2Fconfig+OR%0Aproject%3Astarlingx%2Fconfig%2Dfiles+OR%0Aproject%3Astarlingx%2Fcontainers+OR%0Aproject%3Astarlingx%2Fdistcloud+OR%0Aproject%3Astarlingx%2Fdistcloud%2Dclient+OR%0Aproject%3Astarlingx%2Fdocs+OR%0Aproject%3Astarlingx%2Felection+OR%0Aproject%3Astarlingx%2Ffault+OR%0Aproject%3Astarlingx%2Fgovernance+OR%0Aproject%3Astarlingx%2Fgui+OR%0Aproject%3Astarlingx%2Fha+OR%0Aproject%3Astarlingx%2Fhelm%2Dcharts+OR%0Aproject%3Astarlingx%2Finteg+OR%0Aproject%3Astarlingx%2Fmanifest+OR%0Aproject%3Astarlingx%2Fmetal+OR%0Aproject%3Astarlingx%2Fmonitor%2Darmada%2Dapp+OR%0Amonitoring+OR+project%3Astarlingx%2Fnfv+OR%0Aproject%3Astarlingx%2Fopenstack%2Darmada%2Dapp+OR%0Aproject%3Astarlingx%2Fplatform%2Darmada%2Dapp+OR%0Aproject%3Astarlingx%2Froot+OR%0Aproject%3Astarlingx%2Fspecs+OR%0Aproject%3Astarlingx%2Fstx%2Dpuppet+OR%0Aproject%3Astarlingx%2Ftest+OR%0Aproject%3Astarlingx%2Ftools+OR%0Aproject%3Astarlingx%2Fupdate+OR%0Aproject%3Astarlingx%2Fupstream+OR%0Aproject%3Astarlingx%2Futilities+OR%0Aproject%3Astarlingx%2Fzuul%2Djobs%0A%29%0Astatus%3Aopen%0ANOT+owner%3Aself%0ANOT+label%3AWorkflow%3C%3D%2D1%0Alabel%3AVerified%3E%3D1%2Czuul%0ANOT+reviewedby%3Aself&Needs+final+%2B2=label%3ACode%2DReview%3E%3D2+limit%3A50+NOT+label%3ACode%2DReview%3C%3D%2D1&Passed+Zuul%2C+No+Negative+Feedback+%28Small+Fixes%29=NOT+label%3ACode%2DReview%3E%3D2+NOT+label%3ACode%2DReview%3C%3D%2D1%2Cstarlingx%2Dcore+delta%3A%3C%3D10&Passed+Zuul%2C+No+Negative+Feedback=NOT+label%3ACode%2DReview%3E%3D2+NOT+label%3ACode%2DReview%3C%3D%2D1%2Cstarlingx%2Dcore+delta%3A%3E10&Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode%2DReview%3C%3D%2D1+NOT+label%3ACode%2DReview%3E%3D1+age%3A5d&You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=NOT+label%3ACode%2DReview%3C%3D%2D1%2Cself+NOT+label%3ACode%2DReview%3E%3D1%2Cself+reviewer%3Aself&Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+is%3Areviewed+age%3A2d Gerrit Review Dashboard]

|style="vertical-align:top; width:25%;" |

===== StarlingX sub-projects =====
----
* [[StarlingX/Config|Config project]]
* [[StarlingX/Fault|Fault project]]
* [[StarlingX/HA|HA project]]
* [[StarlingX/GUI|GUI project]]
* [[StarlingX/Metal|Metal project]]
* [[StarlingX/NFV|NFV project]]
* [[StarlingX/Update|Update project]]
* [[StarlingX/DistCloud|Distributed Cloud project]]
* [[StarlingX/Docs_and_Infra|Docs and Infra project]]
* [[StarlingX/Build|Build project]]
* [[StarlingX/DistroOpenStack|Distro - OpenStack project]]
* [[StarlingX/Distro|Distro - Non-OpenStack project]]
* [[StarlingX/Test|Test project]]
* [[StarlingX/Security|Security project]]
* [[StarlingX/Containers|Containers project]]
* [[StarlingX/Networking|Networking project]]
* [[StarlingX/Releases|Releases project]]
* [[StarlingX/MultiOS|MultiOS project]]
* [[StarlingX/Pyton2|Python2 to Python3 Transition]]
* [[StarlingX/Zull|Zuul Enablement and Coverage]]
* [[StarlingX/Devstack|Devstack Integration]]
* [[StarlingX/stxinabox|StarlingX In-a-box]]

|style="vertical-align:top; width:25%;" |

===== Special Interest Groups (SIGs) =====
----
* [[StarlingX/Packet SIG|Packet SIG]]
* [[StarlingX/First Contact SIG|First Contact SIG]]
|}

The previous wiki home page can be found [[StarlingX/Archived wiki home page|here]]

ThirdPartySystems/Intel OpenStack CI

2019-09-19T14:26:34Z

Dtroyer: Created page with "{{ThirdPartySystemInfo|name=Intel OpenStack CI |account=intel-zuul |contact=<intel-openstack-ci@intel.com>, <dean.troyer@intel.com>, <timothy.gresham@intel.com> |intent=Consol..."

{{ThirdPartySystemInfo|name=Intel OpenStack CI
|account=intel-zuul
|contact=<intel-openstack-ci@intel.com>, <dean.troyer@intel.com>, <timothy.gresham@intel.com>
|intent=Consolidate some of the older Intel third party CI systems under Zuul v3
|structure=Zuulv3, Nodepool, OpenStack Cloud, KVM/QEMU Virtual Machines
|method=Use Gerrit Trigger to trigger ZuulV3,. Deploy OpenStack on Intel hardware and run specific tests. Recheck comment: <tbd>.
|programs=Neutron, Nova, OVS-DPDK, ODL, devstack, devstack-gate, Tempest
|status=Initial testing complete, migration of existing tests has begun.}}

ThirdPartySystems

2019-09-19T14:21:07Z

Dtroyer: Add intel-openstack-ci, sort entries in the vicinity

== Third Party CI Systems ==

{| border="1" cellpadding="2" cellspacing="0" class="wikitable"
|+
!colspan="3"|3rd Party CI Systems
|-
!Name
!Link
!Comments
|-
{{ThirdPartySystemTableEntry|6WIND Networking CI}}|
{{ThirdPartySystemTableEntry|A10 Networks CI |}}|
{{ThirdPartySystemTableEntry|Arista-CI}}|
{{ThirdPartySystemTableEntry|ATT Airship-CI}}|
{{ThirdPartySystemTableEntryDown|Blockbridge EPS CI}}|
{{ThirdPartySystemTableEntry|Brocade OpenStack CI}}|
{{ThirdPartySystemTableEntry|Big Switch CI}}|
{{ThirdPartySystemTableEntry|Canonical Charm CI}}|
{{ThirdPartySystemTableEntry|Cisco Ironic CI}}|
{{ThirdPartySystemTableEntry|Cisco ml2 CI}}|
{{ThirdPartySystemTableEntry|Cisco N1kV CI}}|
{{ThirdPartySystemTableEntry|Cisco UCSm CI}}|
{{ThirdPartySystemTableEntry|cisco_pnr_ci}}|
{{ThirdPartySystemTableEntry|Cisco Tail-f CI}}|
{{ThirdPartySystemTableEntry|Cisco ZM CI}}|
{{ThirdPartySystemTableEntry|Citrix NetScaler CI}}|
{{ThirdPartySystemTableEntry|Cloudbase Cinder SMB3 CI}}|
{{ThirdPartySystemTableEntryDown|Cloudbase Compute Hyper-V CI}}|
{{ThirdPartySystemTableEntryDown|Cloudbase Manila SMB3 CI}}|
{{ThirdPartySystemTableEntry|Cloudbase Neutron Hyper-V CI}}|
{{ThirdPartySystemTableEntry|Cloudbase Nova Hyper-V CI}}|
{{ThirdPartySystemTableEntry|CloudByte CI}}|
{{ThirdPartySystemTableEntryDown|CloudFounders OpenvStorage CI}}|
{{ThirdPartySystemTableEntry|Coho Data CI}}|
{{ThirdPartySystemTableEntry|Coraid CI}}|
{{ThirdPartySystemTableEntry|DataCore CI}}|
{{ThirdPartySystemTableEntry|datera-ci}}|
{{ThirdPartySystemTableEntry|DB Datasets CI}}|
{{ThirdPartySystemTableEntryDown|Designate CI}}|
{{ThirdPartySystemTableEntry|DellEMC Ironic CI}}|
{{ThirdPartySystemTableEntry|DellEMC SC CI}}|
{{ThirdPartySystemTableEntry|DellEMC PowerMAX CI}}|
{{ThirdPartySystemTableEntry|DellEMC VNX CI}}|
{{ThirdPartySystemTableEntry|DellEMC XtremIO CI}}|
{{ThirdPartySystemTableEntry|DellEMC VxFlexOS CI}}|
{{ThirdPartySystemTableEntry|DellEMC Unity CI}}|
{{ThirdPartySystemTableEntry|DellEMC Unity Manila CI}}|
{{ThirdPartySystemTableEntry|DellEMC PowerMAX Manila CI}}|
{{ThirdPartySystemTableEntry|DellEMC VNX Manila CI}}|
{{ThirdPartySystemTableEntry|FalconStor CI}}|
{{ThirdPartySystemTableEntry|Freescale CI}}|
{{ThirdPartySystemTableEntry|Fuel CI}}|
{{ThirdPartySystemTableEntry|Fuel Packaging CI}}|
{{ThirdPartySystemTableEntry|Fujitsu C-Fabric CI}}|
{{ThirdPartySystemTableEntry|Fujitsu ETERNUS CI}}|
{{ThirdPartySystemTableEntry|Fujitsu iRMC CI}}|
{{ThirdPartySystemTableEntry|Fujitsu ISM CI}}|
{{ThirdPartySystemTableEntry|Hedvig CI}}|
{{ThirdPartySystemTableEntry|HGST Solutions CI}}|
{{ThirdPartySystemTableEntry|Hitachi HBSD CI}}|
{{ThirdPartySystemTableEntry|Hitachi HBSD2 CI}}|
{{ThirdPartySystemTableEntry|Hitachi HNAS CI}}|
{{ThirdPartySystemTableEntry|Hitachi Manila HNAS CI}}|
{{ThirdPartySystemTableEntry|Hitachi Manila HSP CI}}|
{{ThirdPartySystemTableEntry|HP Octavia Sonar CI}}|
{{ThirdPartySystemTableEntry|HPE Storage CI}}|
{{ThirdPartySystemTableEntry|HP Networking CI}}|
{{ThirdPartySystemTableEntry|HPE Proliant iLO drivers CI}}|
{{ThirdPartySystemTableEntry|HPMSA CI}}|
{{ThirdPartySystemTableEntry|Huawei FusionCompute CI}}|
{{ThirdPartySystemTableEntry|Huawei FusionStorage CI}}|
{{ThirdPartySystemTableEntry|Huawei Ironic CI}}|
{{ThirdPartySystemTableEntry|Huawei Manila CI}}|
{{ThirdPartySystemTableEntry|Huawei ML2 CI}}|
{{ThirdPartySystemTableEntry|Huawei volume CI}}|
{{ThirdPartySystemTableEntry|IBMPowerKVMCI}}|
{{ThirdPartySystemTableEntryDown|IBM FlashSystem CI}}| See [[ThirdPartySystems/IBM Storage CI|IBM Storage CI]]
{{ThirdPartySystemTableEntry|IBM GPFS CI}}|
{{ThirdPartySystemTableEntry|IBM GPFS REMOTE CI}}|
{{ThirdPartySystemTableEntry|IBM GPFS NFS CI}}|
{{ThirdPartySystemTableEntry|IBM PowerVM CI}}|
{{ThirdPartySystemTableEntry|IBM NAS CI}}|
{{ThirdPartySystemTableEntry|IBM SDN-VE CI}}|
{{ThirdPartySystemTableEntry|IBM Storage CI}}|
{{ThirdPartySystemTableEntryDown|IBM STORWIZE CI}}| See [[ThirdPartySystems/IBM Storage CI|IBM Storage CI]]
{{ThirdPartySystemTableEntryDown|IBM XIV-DS8K CI}}| See [[ThirdPartySystems/IBM Storage CI|IBM Storage CI]]
{{ThirdPartySystemTableEntry|IBM xCAT CI}}|
{{ThirdPartySystemTableEntryDown|IBM zKVM CI}}|
{{ThirdPartySystemTableEntryDown|IBM z/VM CI}}|
{{ThirdPartySystemTableEntry|INFINIDAT CI}}|
{{ThirdPartySystemTableEntry|Infortrend Storage CI}}|
{{ThirdPartySystemTableEntry|Inspur CI}}|
{{ThirdPartySystemTableEntry|Intel-IPMI-CI}}|
{{ThirdPartySystemTableEntry|Intel NFV CI}}|
{{ThirdPartySystemTableEntryDown|Intel_NGFW_CI}}|
{{ThirdPartySystemTableEntry|Intel OpenStack CI}}|
{{ThirdPartySystemTableEntry|Intel-PCI-CI}}|
{{ThirdPartySystemTableEntryDown|Intel-RSD-CI}}|WIP
{{ThirdPartySystemTableEntry|Intel-SRIOV-CI}}|
{{ThirdPartySystemTableEntry|Intel-SRIOV-CI-TaaS}}|
{{ThirdPartySystemTableEntryDown|ITRI DISCO CI}}|
{{ThirdPartySystemTableEntryDown|ITRI Peregrine CI}}|
{{ThirdPartySystemTableEntry|Kaminario K2 CI}}|
{{ThirdPartySystemTableEntry|KEMPtechnologies CI}}|
{{ThirdPartySystemTableEntryDown|Linaro CI}}|
{{ThirdPartySystemTableEntry|Lenovo LXCA CI}}|
{{ThirdPartySystemTableEntry|Lenovo Storage CI}}|
{{ThirdPartySystemTableEntry|Limestone Networks CI}}|
{{ThirdPartySystemTableEntry|LINBIT LINSTOR CI}}|WIP
{{ThirdPartySystemTableEntry|MacroSAN Volume CI}}|
{{ThirdPartySystemTableEntry|Maxta CI}}|
{{ThirdPartySystemTableEntry|Mellanox CI}}|
{{ThirdPartySystemTableEntry|Metaplugin CI}}|
{{ThirdPartySystemTableEntryDown|Midokura CI}}|
{{ThirdPartySystemTableEntry|MapR-FS Manila CI}}|
{{ThirdPartySystemTableEntry|Mirantis Rally CI}}|
{{ThirdPartySystemTableEntry|murano-ci}}|
{{ThirdPartySystemTableEntryDown|NEC CI}}|
{{ThirdPartySystemTableEntry|NEC Cinder CI}}|
{{ThirdPartySystemTableEntry|NetApp CI}}|
{{ThirdPartySystemTableEntry|NetApp Eseries CI}}|
{{ThirdPartySystemTableEntry|NetApp SolidFire CI}}|
{{ThirdPartySystemTableEntry|Networking-spp Integration CI}}|
{{ThirdPartySystemTableEntry|Nexenta CI}}|
{{ThirdPartySystemTableEntry|Nexenta Manila CI}}|
{{ThirdPartySystemTableEntry|Nimble Storage CI}}|
{{ThirdPartySystemTableEntry|Nokia Airframe CI}}|
{{ThirdPartySystemTableEntry|NTT SystemFault MasakariIntegration CI}}|
{{ThirdPartySystemTableEntry|Nuage CI}}|
{{ThirdPartySystemTableEntryDown|OpenDaylight CI}}|
{{ThirdPartySystemTableEntry|Open-E JovianDSS CI}}|
{{ThirdPartySystemTableEntryDown|OPNFV CI}}|
{{ThirdPartySystemTableEntry|Oracle ZFSSA CI}}|
{{ThirdPartySystemTableEntryDown|PLUMgrid CI}}|
{{ThirdPartySystemTableEntry|Pengyun Cinder CI}}|
{{ThirdPartySystemTableEntry|ProphetStor CI}}|
{{ThirdPartySystemTableEntry|PhazrIO CI}}|
{{ThirdPartySystemTableEntry|Pure Storage CI}}|
{{ThirdPartySystemTableEntry|QNAP CI}}|
{{ThirdPartySystemTableEntry|Quantastor CI}}|
{{ThirdPartySystemTableEntry|Quobyte CI}}|
{{ThirdPartySystemTableEntry|Rackspace CloudDNS CI}}|
{{ThirdPartySystemTableEntry|Rackspace GolangSwift CI}}|
{{ThirdPartySystemTableEntry|Radware CI}}|
{{ThirdPartySystemTableEntry|RDO Third Party CI}}|
{{ThirdPartySystemTableEntry|RedHat CI}}|
{{ThirdPartySystemTableEntry|RedHat GlusterFS CI}}|
{{ThirdPartySystemTableEntryDown|RedHat̞ NFVPE CI}}|
{{ThirdPartySystemTableEntry|RedHat RDO CI}}|
{{ThirdPartySystemTableEntry|Reduxio HX550 CI}}|
{{ThirdPartySystemTableEntry|SandStone Storage CI}}|
{{ThirdPartySystemTableEntry|Scality CI}}|
{{ThirdPartySystemTableEntryDown|Seagate CI}}|WIP
{{ThirdPartySystemTableEntry|Snabb-NFV CI}}|
{{ThirdPartySystemTableEntry|Software Factory CI}}|ZuulV3|
{{ThirdPartySystemTableEntry|SolidFire CI}}|
{{ThirdPartySystemTableEntry|StorPool distributed storage CI}}|
{{ThirdPartySystemTableEntry|SUSE Cloud CI}}|
{{ThirdPartySystemTableEntry|SwiftStack Cluster CI}}|
{{ThirdPartySystemTableEntry|Synology DSM CI}}|
{{ThirdPartySystemTableEntry|Tail-f NCS CI}}|
{{ThirdPartySystemTableEntry|Tegile Storage CI}}|
{{ThirdPartySystemTableEntry|Tintri CI}}|
{{ThirdPartySystemTableEntry|UFCG OneView CI}}|
{{ThirdPartySystemTableEntry|Vanilla Stack CI}}|
{{ThirdPartySystemTableEntry|vArmour CI}}|
{{ThirdPartySystemTableEntry|Vedams SCST CI}}|
{{ThirdPartySystemTableEntry|Veritas HyperScale CI}}|
{{ThirdPartySystemTableEntry|Veritas Access CI}}|
{{ThirdPartySystemTableEntry|Violin Memory CI}}|
{{ThirdPartySystemTableEntry|Virtuozzo CI}}|
{{ThirdPartySystemTableEntryDown|Virtuozzo Storage CI}}|
{{ThirdPartySystemTableEntry|VMware CI}}|
{{ThirdPartySystemTableEntry|Wherenow.org CI}}|
{{ThirdPartySystemTableEntry|XenProject CI}}|
{{ThirdPartySystemTableEntry|XenServer CI}}|
{{ThirdPartySystemTableEntry|X-IO technologies CI}}|
{{ThirdPartySystemTableEntryDown|XP Storage CI}}|
{{ThirdPartySystemTableEntry|ZadaraStorage VPSA CI}}|
{{ThirdPartySystemTableEntry|ZTE cinder2 CI}}|
{{ThirdPartySystemTableEntry|Example}}|
|-
|}

Instructions on how to add a new system to the above table:
* Add an '''alphabetical''' entry in the above table: <code><nowiki>{{ThirdPartySystemTableEntry|Example}}|Comment</nowiki></code> where Example is the name of your system and Comment (optional) is a free text comment about your system
* Save the page and click on the link to the new page
* Select the "edit the page" option and paste <code><nowiki>{{subst:ThirdPartySystemInfoSubst}}</nowiki></code> into your new page and then save it. This will expand to a table. Edit the table replacing the placeholder values with the correct values for your system
* If your system is going down or having problems, change the entry to <code><nowiki>{{ThirdPartySystemTableEntryDown|<your ci system name>}}</nowiki></code>
----

Do you have a Gerrit CI account created for you by the Infrastructure team and you want to update it? [https://wiki.openstack.org/wiki/OldtoNewGerritCIAccount Read how here].

[[Category:ThirdPartySystems]]

StarlingX/Release Plan

2019-08-02T17:17:37Z

Dtroyer: Bring information current for 2.0 release timeframe

<big><big> '''Releases''' </big></big>

StarlingX is released periodically; one beta release in 2018 and two releases/year starting in 2019. A release consists of a branch in the source code repositories that enables repeatable builds over time.
----
== Release Definition ==
A StarlingX milestone/release is a tagged branch in the source code repositories that:
* is considered stable and can be used for repeatable builds
* will have no additional features added
* will backport bug fixes for critical issues only
* will be maintained in the canonical repositories for a specified minimum period
* The list of repos included is maintained in stx-manifest/default.xml (or similar) for any given release. (Note: this file included non-StarlingX-managed repos, only repos from the "starlingx" and "stx-staging" remotes are included.)
* The actual release is a tag on the corresponding branch, i.e. r/stx.2.0 release branch will be initially tagged as v2.0.0.rc0, the actual release will be tagged as v2.0.0
* In addition to source, the corresponding binaries will be made available on the StarlingX CENGN mirror (see the [[StarlingX/Build#Starling_X_Mirror|the build team page]] for more details).

== Release Cadence and Schedule ==
'''Releases are published in a time based fashion:'''
* The initial (beta) StarlingX release was released in October 2018.
* In 2019, StarlingX releases will align with OpenStack releases. StarlingX will have two releases a year, following a cycle-trailing model relative to the OpenStack release cycle.
** The goal is to release StarlingX 4-6 weeks after the corresponding OpenStack release.
** Background: During the OpenStack Berlin Summit in Nov 2019, the StarlingX TSC discussed a proposal to have StarlingX track OpenStack master during the development cycle and align on the latest OpenStack release once available. To support this direction, the StarlingX release cadence was updated accordingly.

=== Formal Releases ===
* Released two times per year
* Branch name format r/X.0
** 'r/' is the branch name prefix (release)
** 'X' is the major release identifier
* Release Candidate is tagged as vX.Y.Z.rcN
* Release is tagged as vX.Y.Z

=== Informal Monthly Milestones ===
''[Note: StarlingX has not used milestone branches since the 1.0 release (AKA 2018.10). ]''

* Informal milestones to be created for a pre-defined sanity/regression test cycle.
* Milestone is tagged as YYYY.MM.bN, where YYYY.MM is the year/month of the milestone date, and N is >=1 and incremented should there ever need to be multiple milestones in the same month.
''NOTE: Milestones were originally branched similar to releases with a prefix of 'm/'. This is no longer done following the 2018.10 release.''

=== Branch Logistics ===
* StarlingX master builds docker images from OpenStack master during the development cycle
* Once the OpenStack release branch is created (ex: Stein), switch the builds to the release branch
* Once the StarlingX release branch is created, the master StarlingX builds will switch back to OpenStack master in the default.xml manifest
* The StarlingX release branch will continue building from the stable OpenStack release branch (ex: Stein)
* StarlingX maintenance (dot) releases will periodically pick up the latest from the stable OpenStack release branch (ex: Stein)
[[File:Stx-branch-logistics.png]]

== Release Milestones ==
StarlingX follows the OpenStack release milestones. The criteria for each milestone is defined to align more closely with the StarlingX deliverables/development cycle
* Milestone-1:
** Release priorities and major features defined.
** High level resourcing secured.
* Milestone-2:
** Spec freeze
** Feature plans defined and feature development well underway
** Release test plan defined - including test automation deliverables
** Documentation plan defined
* Milestone-3:
** Feature freeze: All feature code merged and feature testing completing within 2 weeks
** No blocking issues from Automated Sanity and Regression
** No critical issues severely impacting system stability or release test activities
** Release regression testing underway
** Preliminary documentation available (TBC by doc team)
* RC1 (aka RC period start):
** Release branch created & first release candidate tagged
** RC binaries (and supporting build artifacts) posted on the StarlingX CENGN mirror
*** RC builds will be posted daily on CENGN during the RC period.
*** The daily builds will not be explicitly tagged until the end of the RC period. ''(To be confirmed with Dean)''
** Final Release Testing Start
** Only Bug fixes are allowed in the release branch.
*** Bugs fixes must be sourced in master first before getting cherry-picked to the release branch.
* Final Release
** Release Testing Complete and Pass Rate meets project criteria (> 95% ?)
** All release gating issues are addressed or reviewed/accepted for deferral
** Release tagged on release branch
** Release binaries (and supporting build artifacts) posted on the StarlingX CENGN mirror
** Final documentation posted on docs.startlingx.io

== Release Maintenance ==
* Formal releases are maintained for a minimum of 12 months to maintain support for two previous StarlingX releases.
* During the maintenance window, the release team will evaluate monthly whether a maintenance release is required.
** The maintenance release will be tagged on the release branch.
** The maintenance release will undergo a mini regression test cycle.
** The corresponding binaries will be posted on the StarlingX CENGN mirror.
* After the 12-month maintenance window, the release will be considered End of Life.

== List of Releases ==
'''Planned'''
{| class="wikitable"
|-
! Version !! Milestone-1 !! Milestone-2 !! Milestone-3 !! RC1 !! Release Date !! End of Life Date
|-
| stx.1.0 || N/A || N/A || Sep 26 2018 || Sep 28 2018 || Oct 24 2018 || N/A
|-
| stx.2.0 || Jan 18 2019 || Apr 29 2019 || June 21 2019 || Aug 5-9 2019 || Aug 30 2019 || 2020
|-
| stx.3.0 || TBD || TBD || TBD || TBD || TBD || TBD
|}

== Release Planning References ==
* For team members and other information, visit the StarlingX Releases sub-project wiki page [https://wiki.openstack.org/wiki/StarlingX/Releases here]
* Release Planning Etherpad: https://etherpad.openstack.org/p/stx-releases
* stx.2.0 Release Plan: [https://docs.google.com/spreadsheets/d/1HUwbsaSerzFRuvXVB_qvoGdI0Chx1YiiA2WYHwvIoYI/edit?usp=sharing here]

StarlingX/Release Process

2019-08-02T16:57:47Z

Dtroyer: Add some examples

Describe the steps in creating a StarlingX Release

= Release Activity =

== Milestone ==

''[Note: StarlingX has not used milestone branches since the 1.0 release (AKA 2018.10). ]''
* Finalize any outstanding changes to master stx-manifest/default.xml, particularly for the starlingx and stx-staging remotes as those are used to create the list of repos to branch and tag.
* Create the branches and tag them by running stx-tools/release/branch-stx.sh. Set SERIES to the proper value if the current year/month is not correct: <pre>SERIES=2018.07 stx-tools/release/branch-stx.sh</pre>
* Create the branch manifest in stx-manifest/default.xml
* Review and approve the .gitreview updates in the new branch

== Release ==

* Make a cleanup pass though release notes and add missing
* Finalize any outstanding changes to master stx-manifest/default.xml, particularly for the starlingx and stx-staging remotes as those are used to create the list of repos to branch and tag.
* Create the branches and tag them by running stx-tools/release/branch-stx.sh. Set SERIES, BRANCH and TAG to the proper values and use the manifest to retrieve the repo list:
** SERIES=stx.X.0
** BRANCH=r/stx.X.0
** TAG=vX.0.0.rc0
** -m <path>/default.xml
<pre>SERIES=stx.2.0 BRANCH=r/stx.2.0 TAG=v2.0.0.rc0 ../tools/release/branch-stx.sh -m ../manifest/default.xml</pre>
* Create the branch manifest in starlingx/manifest/default.xml
<pre>SERIES=stx.2.0 BRANCH=r/stx.2.0 TAG=v2.0.0.rc0 ../tools/release/branch-stx.sh https://opendev.org/starlingx/manifest.git</pre>
* Make any branch-specific updates to the manifest and create a new review if necessary
* Review and approve the .gitreview updates in the new branch
* Look for UPPER_CONSTRAINTS_FILE values to update for stable branches (there may not be any as this is an OpenStack-ism that we would change when rebasing OpenStack projects)
* Verify release notes appear correctly and make adjustments

= Scripts =

== branch-stx.sh ==

Found in stx-tools/release, performs the following steps for each repo listed on the command line:
* if -m <manifest> is included on the command line add the repo list extracted from stx-manifest/default.xml for the starlingx and stx-staging remotes using getrepo.sh (also in stx-tools/release)
* for each repo:
** clone repo
** create the new branch
** tag branch if TAG is set
** for gerrit (starlingx) repos:
*** push to gerrit
*** update .gitreview
** for Github repos (stx-staging):
*** push to github

StarlingX/Release Process

2019-08-02T15:32:02Z

Dtroyer: Updates for 2.0

Describe the steps in creating a StarlingX Release

= Release Activity =

== Milestone ==

''[Note: StarlingX has not used milestone branches since the 1.0 release (AKA 2018.10). ]''
* Finalize any outstanding changes to master stx-manifest/default.xml, particularly for the starlingx and stx-staging remotes as those are used to create the list of repos to branch and tag.
* Create the branches and tag them by running stx-tools/release/branch-stx.sh. Set SERIES to the proper value if the current year/month is not correct: <pre>SERIES=2018.07 stx-tools/release/branch-stx.sh</pre>
* Create the branch manifest in stx-manifest/default.xml
* Review and approve the .gitreview updates in the new branch

== Release ==

* Make a cleanup pass though release notes and add missing
* Finalize any outstanding changes to master stx-manifest/default.xml, particularly for the starlingx and stx-staging remotes as those are used to create the list of repos to branch and tag.
* Create the branches and tag them by running stx-tools/release/branch-stx.sh. Set SERIES, BRANCH and TAG to the proper values:
** SERIES=stx.X.0
** BRANCH=r/stx.X.0
** TAG=vX.0.0.rc0
* Create the branch manifest in stx-manifest/default.xml
* Review and approve the .gitreview updates in the new branch
* Look for UPPER_CONSTRAINTS_FILE values to update for stable branches (there may not be any as this is an OpenStack-ism that we would change when rebasing OpenStack projects)
* Verify release notes appear correctly and make adjustments

= Scripts =

== branch-stx.sh ==

Found in stx-tools/release, performs the following steps for each repo listed on the command line:
* if -m <manifest> is included on the command line add the repo list extracted from stx-manifest/default.xml for the starlingx and stx-staging remotes using getrepo.sh (also in stx-tools/release)
* for each repo:
** clone repo
** create the new branch
** tag branch if TAG is set
** for gerrit (starlingx) repos:
*** push to gerrit
*** update .gitreview
** for Github repos (stx-staging):
*** push to github

StarlingX

2019-04-21T04:21:02Z

Dtroyer: Update some of the OpenDev links, but not the dashboards

__NOTOC__
<center>

== Welcome to the StarlingX Project ==
</center>

''See the [https://www.starlingx.io/ main StarlingX web site] for current information about the project and the [https://docs.starlingx.io/ StarlingX Documentation site] for reference documentation and guides.''

StarlingX is a fully featured and high performance Edge Cloud software stack that is based on the [https://www.windriver.com/products/titanium-cloud/ Wind River® Titanium Cloud] R5 product. Intel and Wind River have jointly open sourced this software and we invite you to download, build, install, and run it.

Wind River Titanium Cloud was originally built on open source components, that were then extended and hardened to meet critical infrastructure requirements, including: high availability, fault management, and performance management. This software provides numerous features and capabilities to enable 24/7 operation of mission critical applications.

You can find an overview of the StarlingX project's features [https://www.starlingx.io/learn/ here].

The StarlingX project opens all of these enhancements to the open source community. Please join us as we build the infrastructure stack for Edge Computing.
----

{| style="border-collapse: separate; border-spacing: 25px;"
|style="vertical-align:top; width:50%;" |


== Releases ==
The first StarlingX release is stx.1.0 (previously referred to as stx.2018.10) and it is available now!
* How to get the code (placeholder)
* You can find a pre-build image for the October 2018 release [http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/outputs/iso/ here]
* [http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ Latest builds]
* [https://docs.starlingx.io/releasenotes/index.html StarlingX Release Notes (stx.2018.10)]

== Documentation ==
These two documents will help get you started building, installing, and validating your installation of StarlingX:
* [https://docs.starlingx.io/contributor/index.html StarlingX Developer Guide]
* [https://docs.starlingx.io/installation_guide/index.html StarlingX Installation Guide]
* [[StarlingX/StarlingX VirtualBox Configuration Guide | StarlingX VirtualBox Configuration Guide]]
* [[StarlingX/StarlingX Packet.com iPXE Installation | StarlingX Packet.com iPXE Installation]]

== Contributing ==
Your contribution is welcome - check the list of [https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.helpwanted "help wanted" bugs].

== Code ==
The StarlingX project uses Gerrit as its web-based code change management and review tool.
* [https://opendev.org/starlingx Gerrit repositories] maintain the StarlingX code, build instructions are in the [https://docs.starlingx.io/developer_guide/index.html StarlingX Developer Guide]
* [https://review.opendev.org/#/admin/projects/?filter=starlingx StarlingX Gerrit Projects] and [https://review.opendev.org/#/q/status:open+AND+project:%255Estarlingx/%2540 Open StarlingX project reviews]
* [https://review.openstack.org/#/dashboard/?foreach=(project:openstack/stx-clients%20OR%20project:openstack/stx-config%20OR%20project:openstack/stx-distcloud%20OR%20project:openstack/stx-distcloud-client%20OR%20project:openstack/stx-fault%20OR%20project:openstack/stx-gui%20OR%20project:openstack/stx-ha%20OR%20project:openstack/stx-integ%20OR%20project:openstack/stx-manifest%20OR%20project:openstack/stx-metal%20OR%20project:openstack/stx-nfv%20OR%20project:openstack/stx-root%20OR%20project:openstack/stx-tools%20OR%20project:openstack/stx-update%20OR%20project:openstack/stx-upstream)%20status:open%20NOT%20owner:self%20NOT%20label:Workflow%3C=-1%20label:Verified%3E=1,zuul%20NOT%20reviewedby:self&title=StarlingX%20Review%20Inbox&Needs%20final%20%202=label:Code-Review%3E=2%20limit:50%20NOT%20label:Code-Review%3C=-1,self&Passed%20Zuul,%20No%20Negative%20Feedback%20(Small%20Fixes)=NOT%20label:Code-Review%3E=2%20NOT%20label:Code-Review%3C=-1,starlingx-core%20delta:%3C=10&Passed%20Zuul,%20No%20Negative%20Feedback=NOT%20label:Code-Review%3E=2%20NOT%20label:Code-Review%3C=-1,starlingx-core%20delta:%3E10&Needs%20Feedback%20(Changes%20older%20than%205%20days%20that%20have%20not%20been%20reviewed%20by%20anyone)=NOT%20label:Code-Review%3C=-1%20NOT%20label:Code-Review%3E=1%20age:5d&You%20are%20a%20reviewer,%20but%20haven't%20voted%20in%20the%20current%20revision=NOT%20label:Code-Review%3C=-1,self%20NOT%20label:Code-Review%3E=1,self%20reviewer:self&Wayward%20Changes%20(Changes%20with%20no%20code%20review%20in%20the%20last%202days)=NOT%20is:reviewed%20age:2d StarlingX Gerrit Review Dashboard]
* [https://review.openstack.org/#/dashboard/?foreach=%28project%3Aopenstack%2Fstx-clients+OR+project%3Aopenstack%2Fstx-config+OR+project%3Aopenstack%2Fstx-distcloud+OR+project%3Aopenstack%2Fstx-distcloud-client+OR+project%3Aopenstack%2Fstx-fault+OR+project%3Aopenstack%2Fstx-gui+OR+project%3Aopenstack%2Fstx-ha+OR+project%3Aopenstack%2Fstx-integ+OR+project%3Aopenstack%2Fstx-manifest+OR+project%3Aopenstack%2Fstx-metal+OR+project%3Aopenstack%2Fstx-nfv+OR+project%3Aopenstack%2Fstx-root+OR+project%3Aopenstack%2Fstx-tools+OR+project%3Aopenstack%2Fstx-update+OR+project%3Aopenstack%2Fstx-upstream%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D-1+label%3AVerified%3E%3D1%2Czuul+NOT+reviewedby%3Aself&title=StarlingX+Review+Inbox&Needs+final+%2B2=label%3ACode-Review%3E%3D2+limit%3A50+NOT+label%3ACode-Review%3C%3D-1%2Cself&Passed+Zuul%2C+No+Negative+Feedback+%28Small+Fixes%29=NOT+label%3ACode-Review%3E%3D2+NOT+label%3ACode-Review%3C%3D-1%2Cstarlingx-core+delta%3A%3C%3D10&Passed+Zuul%2C+No+Negative+Feedback=NOT+label%3ACode-Review%3E%3D2+NOT+label%3ACode-Review%3C%3D-1%2Cstarlingx-core+delta%3A%3E10&Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode-Review%3C%3D-1+NOT+label%3ACode-Review%3E%3D1+age%3A5d&You+are+a+reviewer%2C+but+haven't+voted+in+the+current+revision=NOT+label%3ACode-Review%3C%3D-1%2Cself+NOT+label%3ACode-Review%3E%3D1%2Cself+reviewer%3Aself&Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+is%3Areviewed+age%3A2d StarlingX Gerrit Review Dashboard by Status]

* [[StarlingX/CodeSubmissionGuidelines|Code Submission Guidelines]]
* [https://docs.starlingx.io/contributor/api_contribute_guide.html StarlingX API Contributor Guide]

== Planning & Process ==
* [[StarlingX/Release_Plan|StarlingX Release Planning]]
* [[StarlingX/Feature Development Process|StarlingX Feature Development Process (in review)]]
* [[StarlingX/Defect Handling Process|StarlingX Defect Handling Process]]

== Story and Bug Tracking ==
We are using the OpenStack Storyboard tool for tracking feature development activities. Each new Story shall be marked with one or more Tags, and can optionally include one or more Prefixes in the title. See [[StarlingX/Tags and Prefixes|Tags and Prefixes]] for a description of how we use them.

The StarlingX Storyboard project group is [https://storyboard.openstack.org/#!/project_group/86 here]. '''IMPORTANT:''' If you create a new story, please mark it with the tag "stx.new" so we can find it, review it and assign it to the right team/release.

We are using [https://bugs.launchpad.net/starlingx Launchpad] for tracking bugs. '''IMPORTANT:''' If you create a new bug, please use [[StarlingX/BugTemplate|the StarlingX Bug Template]].

Sample queries:
* To find newly created stories, use: [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.new this query]
* To find stories with no sub-project tags, use [https://storyboard.openstack.org/#!/worklist/456 this worklist]
* To find all active stories, use [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86 this query]
* To find all active stories for stx.2.0, use [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.2.0 this query]
* To find all active bugs for stx.2.0 in launchpad, use [https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2018.10 this query].
* Queries for the Sub-projects are defined on each Sub-project's page

== References ==

* [https://etherpad.openstack.org/p/stx-notes The list of repos] and other things

== OpenStack Documentation ==

These are references to general OpenStack material:

* [https://docs.openstack.org/infra/manual/developers.html Developer's Guide]
* [https://docs.openstack.org/infra/manual/creators.html Project Creator's Guide]
* [https://wiki.openstack.org/wiki/How_To_Contribute The Contributors Guide] (the older wiki page)
* [https://governance.openstack.org/tc/reference/project-testing-interface.html Project Testing Interface]

== Governance ==

You can find more information about StarlingX governance and the TSC charter on the [https://docs.starlingx.io/governance/index.html governance section] of the documentation website.

For early versions and evolution of the documents see [https://etherpad.openstack.org/p/stx-governance here] and [[Starlingx/Initial Governance|on this wiki page.]]

|style="vertical-align:top; width:50%;" |


== Culture ==

We are proud to be an OpenStack Foundation project!
* We support and adhere to the [https://www.openstack.org/legal/community-code-of-conduct/ OpenStack community Code of Conduct]
* We support and fully embrace the [https://governance.openstack.org/tc/reference/opens.html Four Opens]
* [[StarlingX/Contribution Guidelines|Contribution Guidelines]]
* The mailing lists are now live at http://lists.starlingx.io/. There are two lists, starlingx-announce and starlingx-discuss. Please subscribe.
* We have the #starlingX IRC channel set up on freenode. Refer to https://docs.openstack.org/infra/manual/developers.html regarding how to have your IRC account setup.

== Meetings ==

=== Weekly calls ===

* The list of meetings and dial-in information can be found [[Starlingx/Meetings|on this page.]]
* We held a community meetup in January 2019. The agenda and meeting notes [https://etherpad.openstack.org/p/stx-chandler-meetup can be found here]. A blog with pictures and a description of the meetup [https://www.starlingx.io/blog/starlingx-meetup-january-2019.html is here].

=== PTG Meetings ===

Here are the agendas and notes for our PTG meetings:
* [https://etherpad.openstack.org/p/stx-PTG-agenda StarlingX Denver PTG Agenda]

== Status and Planning ==
This section is under construction.
=== Overall project planning pages ===
* [[StarlingX/Project Priorities|Project Priorities]]
* [[StarlingX/Release Plan|Release Plan]]
* [[StarlingX/Project Plans|Project Plans]]

=== StarlingX Projects ===
StarlingX is both a development project and an integration project that combines new services with many other open source projects into an overall Edge Cloud software stack. We've broken the overall project into a set of separate projects to help keep things manageable.
Notes from the F2F discussion on how to organize sub-teams are [https://ethercalc.openstack.org/ctjc7vlbphm1 here]
==== StarlingX main projects ====
Information on the main StarlingX development projects can be found on the wiki pages below:
{| class=wikitable
|-
| [[StarlingX/Config|Config project]]|| [[StarlingX/Fault|Fault project]]
|-
| [[StarlingX/HA|HA project]] || [[StarlingX/GUI|GUI project]]
|-
| [[StarlingX/Metal|Metal project]]|| [[StarlingX/NFV|NFV project]]
|-
| [[StarlingX/Update|Update project]]|| [[StarlingX/DistCloud|Distributed Cloud project]]
|}

==== StarlingX supporting projects ====
In addition to the main StarlingX development projects there are also additional projects to help us develop, maintain, document, build and release the overall StarlingX software stack.
{| class="wikitable"
|-
| [[StarlingX/Docs_and_Infra|Docs and Infra project]]|| [[StarlingX/Build|Build project]]
|-
| [[StarlingX/DistroOpenStack|Distro - OpenStack project]] || [[StarlingX/Distro|Distro - Non-OpenStack project]]
|-
| [[StarlingX/Test|Test project]]|| [[StarlingX/Security|Security project]]
|-
| [[StarlingX/Containers|Containers project]]|| [[StarlingX/Networking|Networking project]]
|-
| [[StarlingX/Releases|Releases project]] || [[StarlingX/MultiOS|MultiOS project]]
|}

==== StarlingX cross-project initiatives ====
There are several initiatives we are implementing that cross project boundaries:
{| class="wikitable"
|-
| [[StarlingX/Pyton2|Python2 to Python3 Transition]]|| [[StarlingX/Zull|Zuul Enablement and Coverage]]
|-
| [[StarlingX/Devstack|Devstack Integration]] || [[StarlingX/stxinabox|StarlingX In-a-box]]
|}
ToDo:
* Create a Project Map graphic that captures all of this in a graphical way, similar to (or an extension of) the OpenStack project map.

== Upstream Status ==

The StarlingX code base contains a number of out-of-tree patches against other open source components. One of our highest priorities is to contribute those changes to their upstream communities.

We are tracking the progress of resolving the OpenStack patches in an [https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit?usp=sharing shared Google document]. If you need write access to the document, please request it through the Google sheet directly.

We are tracking the Non-OpenStack patches in a [https://docs.google.com/spreadsheets/d/1nKnkweuxcqvVOoRcpnTYMVUUv1RoAugOWXMjB7VIrfc/edit?usp=sharing a different shared Google document]. Please send an email to [mailto:bruce.e.jones@intel.com BruceJ @ Intel] with your gmail.com email address for access to the document.

StarlingX/Devstack/Plugins

2019-03-25T22:32:58Z

Dtroyer: Created page with "= DevStack Plugins for StarlingX = Seven of the StarlingX repositories have DevStack plugins: stx-config, stx-fault, stx-ha, stx-integ, stx-metal, stx-nfv, stx-update. Thes..."

= DevStack Plugins for StarlingX =

Seven of the StarlingX repositories have DevStack plugins: stx-config, stx-fault, stx-ha, stx-integ, stx-metal, stx-nfv, stx-update. Thes eplugins are used to build, install and start a subset of the StarlingX services that can be operated outside of the specific environment

StarlingX/Branches

2019-01-30T15:38:00Z

Dtroyer:

= Branches =

StarlingX branching policy is largely derived from OpenStack policy with some changes to accommodate different development cycle and release priorities.

== Stable/Release Branches ==

== Feature Branches ==

Feature branches are used to develop and coordinate large numbers of changes. They should be used with care as they can also be a source of long-term debt and divergence.

Feature branches are named with the prefix 'f/' followed by a descriptive name.

=== Branch Updates ===

Feature branches should regularly be re-sync'ed with the master branch rather than wait until the feature work is done. Resolution of conflicts occurs on the feature branch side and generally falls to the developers working on the feature branch.

Merging new updates from master into the feature branch can only be performed by members of the starlingx-release group in Gerrit. The process follows the OpenStack [https://docs.openstack.org/infra/manual/drivers.html#merge-master-into-feature-branch|Project Driver's Guide].

First look at how the two branches have diverged to get an idea of the differences and look for potential conflicts:

feature_branch=<branch-name>
git remote update
git checkout master
git pull --ff-only origin master
git checkout $feature_branch
git pull --ff-only origin $feature_branch
git log --oneline --no-merges --cherry-mark --left-right --graph master...HEAD

Merge master into feature branch:

git remote update
git checkout master
git pull --ff-only origin master
git checkout $feature_branch
git pull --ff-only origin $feature_branch
git merge origin/master
# Resolve merge conflicts (git add ...; git commit)

# Avoid changing to these files
git checkout origin/master -- .gitreview

# Amend the merge commit to automatically add a Change-ID to the commit message
GIT_EDITOR=true git commit --amend
git review -R $feature_branch

The resulting review will contain the resolution of any merge conflicts that are resolved in this process, meaning that the review will only be a merge commit without any files listed if there are no conflicts.

== Tools ==

=== branch-stx.sh ===

This shell script is found in stx-tools/release/branch-stx.sh and performs the grunt work of branching the set of StarlingX repositories both in Gerrit and the staging repos in Github. It can pull the repo list from a manifest file or accept repo URLs on the command line. It is used for creating milestone, release and feature branches.

* The default action is to create a milestone branch with prefix 'm/'.
* To create a release branch set BRANCH directly using a 'r/' prefix.
BRANCH=r/2018.05 branch-stx.sh <repo-url>
* To create a feature branch set BRANCH directly using a 'f/' prefix and set TAG="" to skip tagging the branch point:
BRANCH=f/centos75 TAG="" branch-stx.sh <repo-url>

branch-stx.sh [--dry-run|-n] [-l] [-m <manifest>] [<repo-url> ...]

--dry-run|-n Do all work except pushing back to the remote repo.
Useful to validate everything locally before pushing.

-l List the repo URLS that would be processed and exit

-m <manifest> Extract the repo list from <manifest> for starlingx
and stx-staging remotes

<repo-url> Specify one or more direct repo URLs to branch (ie git remote)
These are appended to the list of repos extracted from the
manifest if one is specified.

For each repo:
* create a new branch $BRANCH
* tag the new branch with an initial release identifier if $TAG is set
* update the .gitreview file to default to the new branch (Gerrit repos only)

Environment variables are available for modifying this script's behaviour:

<code>SERIES</code> is the base of the branch and tag names, similar to how it is used in OpenStack branch names. StarlingX formats SERIES based on year and month as YYYY.MM although that is only a convention, no tooling assumes that format.

<code>BRANCH</code> is the actual branch name, derived by adding 'm/' (for milestones) or 'r/' (for periodic releases) to SERIES.

<code>TAG</code> is the release tag that represents the actual release. If TAG is unset no tag is created.

== References ==

'''OpenStack Documentation'''

* [https://docs.openstack.org/project-team-guide/other-branches.html#feature-branches Feature Branches]

Starlingx

2019-01-16T17:20:51Z

Dtroyer: Redirected page to StarlingX

#REDIRECT [[StarlingX]]

Here's the [[StarlingX|StarlingX Wiki Page]]

Starlingx

2019-01-16T17:20:20Z

Dtroyer:

#REDIRECT [[StarlingX]

Here's the [[StarlingX|StarlingX Wiki Page]]

StarlingX

2019-01-16T16:21:34Z

Dtroyer: Add links to starlingx.io

__NOTOC__
<center>

== Welcome to the StarlingX Project ==
</center>

''See the [https://www.starlingx.io/ main StarlingX web site] for current information about the project and the [https://docs.starlingx.io/ StarlingX Documentation site] for reference documentation and guides.''

StarlingX is a fully featured and high performance Edge Cloud software stack that is based on the [https://www.windriver.com/products/titanium-cloud/ Wind River® Titanium Cloud] R5 product. Intel and Wind River have jointly open sourced this software and we invite you to download, build, install, and run it.

Wind River Titanium Cloud was originally built on open source components, that were then extended and hardened to meet critical infrastructure requirements, including: high availability, fault management, and performance management. This software provides numerous features and capabilities to enable 24/7 operation of mission critical applications.

You can find an overview of the StarlingX project's features [https://www.starlingx.io/learn/ here].

The StarlingX project opens all of these enhancements to the open source community. Please join us as we build the infrastructure stack for Edge Computing.
----

{| style="border-collapse: separate; border-spacing: 25px;"
|style="vertical-align:top; width:50%;" |


== Releases ==
The first StarlingX release is stx.2018.10 and it is available now!
* How to get the code (placeholder)
* You can find a pre-build image for the October 2018 release [http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/outputs/iso/ here]
* [http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ Latest builds]
* [https://docs.starlingx.io/releasenotes/index.html StarlingX Release Notes (stx.2018.10)]

== Documentation ==
These two documents will help get you started building, installing, and validating your installation of StarlingX:
* [https://docs.starlingx.io/developer_guide/index.html StarlingX Developer Guide]
* [https://docs.starlingx.io/installation_guide/index.html StarlingX Installation Guide]

== Code ==
The StarlingX project uses Gerrit as its web-based code change management and review tool.
* [https://git.starlingx.io/cgit Gerrit repositories] maintain the StarlingX code, build instructions are in the [https://docs.starlingx.io/developer_guide/index.html StarlingX Developer Guide]
* [https://review.openstack.org/#/admin/projects/?filter=stx StarlingX Gerrit Projects] and [https://review.openstack.org/#/q/status:open+AND+project:%255Eopenstack/stx-%2540 Open StarlingX project reviews]
* [https://review.openstack.org/#/dashboard/?foreach=(project:openstack/stx-clients%20OR%20project:openstack/stx-config%20OR%20project:openstack/stx-distcloud%20OR%20project:openstack/stx-distcloud-client%20OR%20project:openstack/stx-fault%20OR%20project:openstack/stx-gui%20OR%20project:openstack/stx-ha%20OR%20project:openstack/stx-integ%20OR%20project:openstack/stx-manifest%20OR%20project:openstack/stx-metal%20OR%20project:openstack/stx-nfv%20OR%20project:openstack/stx-root%20OR%20project:openstack/stx-tools%20OR%20project:openstack/stx-update%20OR%20project:openstack/stx-upstream)%20status:open%20NOT%20owner:self%20NOT%20label:Workflow%3C=-1%20label:Verified%3E=1,zuul%20NOT%20reviewedby:self&title=StarlingX%20Review%20Inbox&Needs%20final%20%202=label:Code-Review%3E=2%20limit:50%20NOT%20label:Code-Review%3C=-1,self&Passed%20Zuul,%20No%20Negative%20Feedback%20(Small%20Fixes)=NOT%20label:Code-Review%3E=2%20NOT%20label:Code-Review%3C=-1,starlingx-core%20delta:%3C=10&Passed%20Zuul,%20No%20Negative%20Feedback=NOT%20label:Code-Review%3E=2%20NOT%20label:Code-Review%3C=-1,starlingx-core%20delta:%3E10&Needs%20Feedback%20(Changes%20older%20than%205%20days%20that%20have%20not%20been%20reviewed%20by%20anyone)=NOT%20label:Code-Review%3C=-1%20NOT%20label:Code-Review%3E=1%20age:5d&You%20are%20a%20reviewer,%20but%20haven't%20voted%20in%20the%20current%20revision=NOT%20label:Code-Review%3C=-1,self%20NOT%20label:Code-Review%3E=1,self%20reviewer:self&Wayward%20Changes%20(Changes%20with%20no%20code%20review%20in%20the%20last%202days)=NOT%20is:reviewed%20age:2d StarlingX Gerrit Review Dashboard]
* [https://review.openstack.org/#/dashboard/?foreach=%28project%3Aopenstack%2Fstx-clients+OR+project%3Aopenstack%2Fstx-config+OR+project%3Aopenstack%2Fstx-distcloud+OR+project%3Aopenstack%2Fstx-distcloud-client+OR+project%3Aopenstack%2Fstx-fault+OR+project%3Aopenstack%2Fstx-gui+OR+project%3Aopenstack%2Fstx-ha+OR+project%3Aopenstack%2Fstx-integ+OR+project%3Aopenstack%2Fstx-manifest+OR+project%3Aopenstack%2Fstx-metal+OR+project%3Aopenstack%2Fstx-nfv+OR+project%3Aopenstack%2Fstx-root+OR+project%3Aopenstack%2Fstx-tools+OR+project%3Aopenstack%2Fstx-update+OR+project%3Aopenstack%2Fstx-upstream%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D-1+label%3AVerified%3E%3D1%2Czuul+NOT+reviewedby%3Aself&title=StarlingX+Review+Inbox&Needs+final+%2B2=label%3ACode-Review%3E%3D2+limit%3A50+NOT+label%3ACode-Review%3C%3D-1%2Cself&Passed+Zuul%2C+No+Negative+Feedback+%28Small+Fixes%29=NOT+label%3ACode-Review%3E%3D2+NOT+label%3ACode-Review%3C%3D-1%2Cstarlingx-core+delta%3A%3C%3D10&Passed+Zuul%2C+No+Negative+Feedback=NOT+label%3ACode-Review%3E%3D2+NOT+label%3ACode-Review%3C%3D-1%2Cstarlingx-core+delta%3A%3E10&Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode-Review%3C%3D-1+NOT+label%3ACode-Review%3E%3D1+age%3A5d&You+are+a+reviewer%2C+but+haven't+voted+in+the+current+revision=NOT+label%3ACode-Review%3C%3D-1%2Cself+NOT+label%3ACode-Review%3E%3D1%2Cself+reviewer%3Aself&Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+is%3Areviewed+age%3A2d StarlingX Gerrit Review Dashboard by Status]

* [[StarlingX/CodeSubmissionGuidelines|Code Submission Guidelines]]
* [https://docs.starlingx.io/contributor/api_contribute_guide.html StarlingX API Contributor Guide]

== Planning & Process ==
* [[StarlingX/Release_Plan|StarlingX Release Planning]]
* [[StarlingX/Feature Development Process|StarlingX Feature Development Process (in review)]]
* [[StarlingX/Defect Handling Process|StarlingX Defect Handling Process]]

== Story and Bug Tracking ==
We are using the OpenStack Storyboard tool for tracking feature development activities. Each new Story shall be marked with one or more Tags, and can optionally include one or more Prefixes in the description. See [[StarlingX/Tags and Prefixes|Tags and Prefixes]] for a description of how we use them.

The StarlingX Storyboard project group is [https://storyboard.openstack.org/#!/project_group/86 here]. '''IMPORTANT:''' If you create a new story (of any kind), please mark it with the tag "stx.new" so we can find it, review it and assign it to the right team and a release.

We are using Launchpad for tracking bugs. [https://bugs.launchpad.net/starlingx Link to the StarlingX Launchpad] '''IMPORTANT:''' If you create a new bug, please use [[StarlingX/BugTemplate|the StarlingX Bug Template]].

Sample queries:
* To find newly created stories, use: [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.new this query]
* To find stories with no sub-project tags, use [https://storyboard.openstack.org/#!/worklist/456 this worklist]
* To find all active stories assigned to the stx.2018.10 release, use [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.2018.10 this query]
* To find all active bugs assigned to the stx.2018.10 release in launchpad, use [https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2018.10 this query].
* [Temporary] To find all active bugs in story board, use: [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.bug this query]
* Queries for the Sub-projects are defined on each Sub-project's page

Optional: You can also use Prefixes to search for Stories, but we consider Prefixes optional so these searches might not show the same results as searching for Tags.
* Sample Prefix queries:
** To find all Stories with the [Features] prefix use: [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Feature this query]
** To find all Stories with the [Build] prefix use: [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Build this query]

== References ==

* [https://etherpad.openstack.org/p/stx-notes The list of repos] and other things

== OpenStack Documentation ==

These are references to general OpenStack material:

* [https://docs.openstack.org/infra/manual/developers.html Developer's Guide]
* [https://docs.openstack.org/infra/manual/creators.html Project Creator's Guide]
* [https://wiki.openstack.org/wiki/How_To_Contribute The Contributors Guide] (the older wiki page)
* [https://governance.openstack.org/tc/reference/project-testing-interface.html Project Testing Interface]

== Governance ==

You can find more information about StarlingX governance and the TSC charter on the [https://docs.starlingx.io/governance/index.html governance section] of the documentation website.

For early versions and evolution of the documents see [https://etherpad.openstack.org/p/stx-governance here] and [[Starlingx/Initial Governance|on this wiki page.]]

|style="vertical-align:top; width:50%;" |


== Culture ==

We are proud to be an OpenStack Foundation project!
* We support and adhere to the [https://www.openstack.org/legal/community-code-of-conduct/ OpenStack community Code of Conduct]
* We support and fully embrace the [https://governance.openstack.org/tc/reference/opens.html Four Opens]
* [[StarlingX/Contribution Guidelines|Contribution Guidelines]]
* The mailing lists are now live at http://lists.starlingx.io/. There are two lists, starlingx-announce and starlingx-discuss. Please subscribe.
* We have the #starlingX IRC channel set up on freenode. Refer to https://docs.openstack.org/infra/manual/developers.html regarding how to have your IRC account setup.

== Meetings ==

=== Weekly calls ===

* The list of meetings and dial-in information can be found [[Starlingx/Meetings|on this page.]]
* We are holding a community meetup in January 2019. The agenda and meeting notes [https://etherpad.openstack.org/p/stx-chandler-meetup can be found here]

=== PTG Meetings ===

Here are the agendas and notes for our PTG meetings:
* [https://etherpad.openstack.org/p/stx-PTG-agenda StarlingX Denver PTG Agenda]

== Status and Planning ==
This section is under construction.
=== Overall project planning pages ===
* [[StarlingX/Project Priorities|Project Priorities]]
* [[StarlingX/Release Plan|Release Plan]]
* [[StarlingX/Project Plans|Project Plans]]

=== StarlingX Projects ===
StarlingX is both a development project and an integration project that combines new services with many other open source projects into an overall Edge Cloud software stack. We've broken the overall project into a set of separate projects to help keep things manageable.
Notes from the F2F discussion on how to organize sub-teams are [https://ethercalc.openstack.org/ctjc7vlbphm1 here]
==== StarlingX main projects ====
Information on the main StarlingX development projects can be found on the wiki pages below:
{| class=wikitable
|-
| [[StarlingX/Config|Config project]]|| [[StarlingX/Fault|Fault project]]
|-
| [[StarlingX/HA|HA project]] || [[StarlingX/GUI|GUI project]]
|-
| [[StarlingX/Metal|Metal project]]|| [[StarlingX/NFV|NFV project]]
|-
| [[StarlingX/Update|Update project]]|| [[StarlingX/DistCloud|Distributed Cloud project]]
|}

==== StarlingX supporting projects ====
In addition to the main StarlingX development projects there are also additional projects to help us develop, maintain, document, build and release the overall StarlingX software stack.
{| class="wikitable"
|-
| [[StarlingX/Docs_and_Infra|Docs and Infra project]]|| [[StarlingX/Build|Build project]]
|-
| [[StarlingX/DistroOpenStack|Distro - OpenStack project]] || [[StarlingX/Distro|Distro - Non-OpenStack project]]
|-
| [[StarlingX/Test|Test project]]|| [[StarlingX/Security|Security project]]
|-
| [[StarlingX/Containers|Containers project]]|| [[StarlingX/Networking|Networking project]]
|-
| [[StarlingX/Releases|Releases project]] || [[StarlingX/MultiOS|MultiOS project]]
|}

==== StarlingX cross-project initiatives ====
There are several initiatives we are implementing that cross project boundaries:
{| class="wikitable"
|-
| [[StarlingX/Pyton2|Python2 to Python3 Transition]]|| [[StarlingX/Zull|Zuul Enablement and Coverage]]
|-
| [[StarlingX/Devstack|Devstack Integration]] ||
|}
ToDo:
* Create a Project Map graphic that captures all of this in a graphical way, similar to (or an extension of) the OpenStack project map.

== Upstream Status ==

The StarlingX code base contains a number of out-of-tree patches against other open source components. One of our highest priorities is to contribute those changes to their upstream communities.

We are tracking the progress of resolving the OpenStack patches in an [https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit?usp=sharing shared Google document]. If you need write access to the document, please request it through the Google sheet directly.

We are tracking the Non-OpenStack patches in a [https://docs.google.com/spreadsheets/d/1nKnkweuxcqvVOoRcpnTYMVUUv1RoAugOWXMjB7VIrfc/edit?usp=sharing a different shared Google document]. Please send an email to [mailto:bruce.e.jones@intel.com BruceJ @ Intel] with your gmail.com email address for access to the document.

StarlingX/Branches

2018-12-20T16:10:11Z

Dtroyer: /* Branch Updates */

= Branches =

StarlingX branching policy is largely derived from OpenStack policy with some changes to accommodate different development cycle and release priorities.

== Stable/Release Branches ==

== Feature Branches ==

Feature branches are used to develop and coordinate large numbers of changes. They should be used with care as they can also be a source of long-term debt and divergence.

Feature branches are named with the prefix 'f/' followed by a descriptive name.

=== Branch Updates ===

Feature branches should regularly be re-sync'ed with the master branch rather than wait until the feature work is done. Resolution of conflicts occurs on the feature branch side and generally falls to the developers working on the feature branch.

Merging new updates from master into the feature branch can only be performed by members of the starlingx-release group in Gerrit. The process follows the OpenStack [https://docs.openstack.org/infra/manual/drivers.html#merge-master-into-feature-branch|Project Driver's Guide].

First look at how the two branches have diverged to get an idea of the differences and look for potential conflicts:

feature_branch=<branch-name>
git remote update
git checkout master
git pull --ff-only origin master
git checkout $feature_branch
git pull --ff-only origin $feature_branch
git log --oneline --no-merges --cherry-mark --left-right --graph master...HEAD

Merge master into feature branch:

git remote update
git checkout master
git pull --ff-only origin master
git checkout $feature_branch
git pull --ff-only origin $feature_branch
git merge origin/master
# Resolve merge conflicts (git add ...; git commit)

# Avoid changing to these files
git checkout origin/master -- .gitreview

# Amend the merge commit to automatically add a Change-ID to the commit message
GIT_EDITOR=true git commit --amend
git review -R $feature_branch

The resulting review will contain the resolution of any merge conflicts that are resolved in this process, meaning that the review will only be a merge commit without any files listed if there are no conflicts.

== Tools ==

=== branch-stx.sh ===

This shell script is found in stx-tools/release/branch-stx.sh and performs the grunt work of branching the set of StarlingX repositories both in Gerrit and the staging repos in Github. It can pull the repo list from a manifest file or accept repo URLs on the command line. It is used for creating milestone, release and feature branches.

* The default action is to create a milestone branch with prefix 'm/'.
* To create a release branch set BRANCH directly using a 'r/' prefix.
BRANCH=r/2018.05 branch-stx.sh <repo-url>
* To create a feature branch set BRANCH directly using a 'f/' prefix and set TAG="" to skip tagging the branch point:
BRANCH=f/centos75 TAG="" branch-stx.sh <repo-url>

branch-stx.sh [--dry-run|-n] [-l] [-m <manifest>] [<repo-url> ...]

--dry-run|-n Do all work except pushing back to the remote repo.
Useful to validate everything locally before pushing.

-l List the repo URLS that would be processed and exit

-m <manifest> Extract the repo list from <manifest> for starlingx
and stx-staging remotes

<repo-url> Specify one or more direct repo URLs to branch (ie git remote)
These are appended to the list of repos extracted from the
manifest if one is specified.

For each repo:
* create a new branch $BRANCH
* tag the new branch with an initial release identifier if $TAG is set
* update the .gitreview file to default to the new branch (Gerrit repos only)

Environment variables are available for modifying this script's behaviour:

<code>SERIES</code> is the base of the branch and tag names, similar to how it is used in OpenStack branch names. StarlingX formats SERIES based on year and month as YYYY.MM although that is only a convention, no tooling assumes that format.

<code>BRANCH</code> is the actual branch name, derived by adding 'm/' (for milestones) or 'r/' (for periodic releases) to SERIES.

<code>TAG</code> is the release tag that represents the actual release, derived by adding a 'patch' version to SERIES, initially '0'. If TAG is unset no tag is created.

== References ==

'''OpenStack Documentation'''

* [https://docs.openstack.org/project-team-guide/other-branches.html#feature-branches Feature Branches]

StarlingX/Branches

2018-12-13T18:22:26Z

Dtroyer:

= Branches =

StarlingX branching policy is largely derived from OpenStack policy with some changes to accommodate different development cycle and release priorities.

== Stable/Release Branches ==

== Feature Branches ==

Feature branches are used to develop and coordinate large numbers of changes. They should be used with care as they can also be a source of long-term debt and divergence.

Feature branches are named with the prefix 'f/' followed by a descriptive name.

=== Branch Updates ===

Feature branches should regularly be re-sync'ed with the master branch rather than wait until the feature work is done. Resolution of conflicts occurs on the feature branch side and generally falls to the developers working on the feature branch.

Merging new updates from master into the feature branch can only be performed by members of the starlingx-release group in Gerrit. The process follows the OpenStack [https://docs.openstack.org/infra/manual/drivers.html#merge-master-into-feature-branch|Project Driver's Guide].

First look at how the two branches have diverged to get an idea of the differences and look for potential conflicts:

feature_branch=<branch-name>
git remote update
git checkout -t origin/$feature_branch
git log --oneline --no-merges --cherry-mark --left-right --graph master...HEAD

Merge master into feature branch:

git remote update
git checkout $feature_branch
git pull --ff-only origin $feature_branch
git merge origin/master
# Resolve merge conflicts (git add ...; git commit)

# Avoid changing to these files
git checkout origin/master -- .gitreview

# Amend the merge commit to automatically add a Change-ID to the commit message
GIT_EDITOR=true git commit --amend
git review -R $feature_branch

The resulting review will contain the resolution of any merge conflicts that are resolved in this process, meaning that the review will only be a merge commit without any files listed if there are no conflicts.

== Tools ==

=== branch-stx.sh ===

This shell script is found in stx-tools/release/branch-stx.sh and performs the grunt work of branching the set of StarlingX repositories both in Gerrit and the staging repos in Github. It can pull the repo list from a manifest file or accept repo URLs on the command line. It is used for creating milestone, release and feature branches.

* The default action is to create a milestone branch with prefix 'm/'.
* To create a release branch set BRANCH directly using a 'r/' prefix.
BRANCH=r/2018.05 branch-stx.sh <repo-url>
* To create a feature branch set BRANCH directly using a 'f/' prefix and set TAG="" to skip tagging the branch point:
BRANCH=f/centos75 TAG="" branch-stx.sh <repo-url>

branch-stx.sh [--dry-run|-n] [-l] [-m <manifest>] [<repo-url> ...]

--dry-run|-n Do all work except pushing back to the remote repo.
Useful to validate everything locally before pushing.

-l List the repo URLS that would be processed and exit

-m <manifest> Extract the repo list from <manifest> for starlingx
and stx-staging remotes

<repo-url> Specify one or more direct repo URLs to branch (ie git remote)
These are appended to the list of repos extracted from the
manifest if one is specified.

For each repo:
* create a new branch $BRANCH
* tag the new branch with an initial release identifier if $TAG is set
* update the .gitreview file to default to the new branch (Gerrit repos only)

Environment variables are available for modifying this script's behaviour:

<code>SERIES</code> is the base of the branch and tag names, similar to how it is used in OpenStack branch names. StarlingX formats SERIES based on year and month as YYYY.MM although that is only a convention, no tooling assumes that format.

<code>BRANCH</code> is the actual branch name, derived by adding 'm/' (for milestones) or 'r/' (for periodic releases) to SERIES.

<code>TAG</code> is the release tag that represents the actual release, derived by adding a 'patch' version to SERIES, initially '0'. If TAG is unset no tag is created.

== References ==

'''OpenStack Documentation'''

* [https://docs.openstack.org/project-team-guide/other-branches.html#feature-branches Feature Branches]

StarlingX/Release Plan

2018-12-13T18:01:44Z

Dtroyer: /* Monthly Milestones (under review) */

<big><big> '''Releases''' </big></big>

StarlingX is released periodically; one beta release in 2018 and two releases/year starting in 2019. A release consists of a branch in the source code repositories that enables repeatable builds over time.
----
== Release Definition ==
A StarlingX milestone/release is a tagged branch in the source code repositories that:
* is considered stable and can be used for repeatable builds
* will have no additional features added
* will backport bug fixes for critical issues only
* will be maintained in the canonical repositories for a specified minimum period
* The list of repos included is maintained in stx-manifest/default.xml (or similar) for any given release. (Note: this file included non-StarlingX-managed repos, only repos from the "starlingx" and "stx-staging" remotes are included.)
* The actual release is a tag on the corresponding branch, i.e. r/2018.10 release branch will be initially tagged as 2018.10.0
* In addition to source, the corresponding binaries will be made available on the StarlingX CENGN mirror (see the [[StarlingX/Build#Starling_X_Mirror|the build team page]] for more details).

== Release Cadence and Schedule ==
'''Releases are published in a time based fashion:'''
* The initial (beta) StarlingX release was released in October 2018.
* In 2019, StarlingX releases will align with openstack releases. StarlingX will have two releases a year, following a cycle-trailing model relative to openstack core releases.
** The goal is to release the StarlingX release 6 weeks (to be confirmed based on the January StarlingX planning session in Chandler) after the corresponding openstack release.
** Background: During the Openstack Berlin Summit in Nov 2019, the StarlingX TSC discussed a proposal to have StarlingX track openstack master during the development cycle and align on the latest openstack release once available. To support this direction, the StarlingX release cadence was updated accordingly.

=== Formal Releases ===
* Released two times per year
* Branch name format r/YYYY.MM[.n]
** 'r/' is the branch name prefix (release)
** .n is a sequence number appended if more than one branch is created in a given month
r/2018.10
* Release Candidate is tagged as YYYY.MM.rcX
* Release is tagged as YYYY.MM.0

=== Monthly Milestones (under review) ===

* Informal milestones to be created for a pre-defined sanity/regression test cycle.
* Milestone is tagged as YYYY.MM.bN, where YYYY.MM is the year/month of the milestone date, and N is >=1 and incremented should there ever need to be multiple milestones in the same month.
''NOTE: Milestones were originally branched similar to releases with a prefix of 'm/'. This is no longer done following the 2018.10 release.''

=== Branch Logistics ===
* StarlingX master builds docker images from openstack master during the development cycle
* Once the openstack release branch is created (ex: Stein), switch the builds to the release branch
* Once the StarlingX release branch is created, the master StarlingX builds will switch back to openstack master.
* The StarlingX release branch will continue building from the stable openstack release branch (ex: Stein)
* StarlingX maintenance (dot) releases will periodically pick up the latest from the stable openstack release branch (ex: Stein)
[[File:Stx-branch-logistics.png]]

== Release Milestones ==
StarlingX follows the openstack release milestones. The criteria for each milestone is defined to align more closely with the StarlingX deliverables/development cycle
* Milestone-1:
** Release priorities and major features defined.
** High level resourcing secured.
* Milestone-2:
** Spec Freeze
** Feature Development underway
** TBD: others? Doc deliverables? Test Automation deliverables?
* Milestone-3:
** Feature Freeze: All Feature Code Submitted and Feature Testing Complete
** No blocking issues from Automated Sanity and Regression
** Release Test Plan Defined (any specific test automation deliverables?)
** Preliminary Documentation Available
** TBD: any criteria for # of open bugs for the milestone declaration?
* RC1 (aka RC period start):
** Release Branch Created & First Release Candidate Tagged
** RC binaries (and supporting build artifacts) posted on the StarlingX CENGN mirror
*** To be discussed: how often do we build an "RC" ISO and post during the RC period?
** Release Testing Start
** Only Bug fixes are allowed in the release branch
* Final Release
** Release Testing Complete and Pass Rate meets project criteria (> 95% ?)
** All release gating issues are addressed or reviewed/accepted for deferral
** Release tagged on release branch
** Release binaries (and supporting build artifcats) posted on the StarlingX CENGN mirror
** Final documentation posted on docs.startlingx.io

== Release Maintenance ==
* Formal releases are maintained for 12 months. This allows support for two previous StarlingX releases.
* During the maintenance window, the release team will evaluate monthly whether a maintenance release is required.
** The maintenance release will be tagged on the release branch.
** The maintenance release will undergo a mini regression test cycle.
** The corresponding binaries will be posted on the StarlingX CENGN mirror.
* After the 12-month maintenance window, the release will be considered End of Life.

== List of Releases ==
'''Planned'''
{| class="wikitable"
|-
! Version !! Milestone-1 !! Milestone-2 !! Milestone-3 !! RC1 !! Release Date !! End of Life Date
|-
| 2018.10.0 || N/A || N/A || Sep 26 2018 || Sep 28 2018 || Oct 24 2018 || N/A
|-
| 2019.05.0 || Jan 14-18 2019 || Feb 18-22 2019 || Apr 8-12 2019 || Apr 29-May 3 2019 || May 20-24 2019 || May 2020
|-
| 2019.yy.0 || TBD || TBD || TBD || TBD || TBD || TBD
|}

Note: The 2019.05.0 dates will be confirmed at milestone-1 based on the StarlingX Planning session in Chandler.

== Release Team ==
* For team members and other information, visit the StarlingX Releases sub-project wiki page [https://wiki.openstack.org/wiki/StarlingX/Releases here]

StarlingX/FeatureSpecTemplate

2018-10-09T21:31:14Z

Dtroyer: Add pointer to published stx-specs

The actual specs template and instructions on the process is now available at https://docs.starlingx.io/specs/. Please refer to that location as the authoritative source for StarlingX specs documentation.

== References ==
* Nova: https://github.com/openstack/nova-specs/blob/master/specs/rocky/implemented/add-extra-specs-to-flavor-list.rst

StarlingX

2018-10-09T15:08:58Z

Dtroyer: Updated Gerrit dashboard queries

__NOTOC__
<center>

== Welcome to the StarlingX Project ==
</center>
StarlingX is a fully featured and high performance Edge Cloud software stack that is based on the [https://www.windriver.com/products/titanium-cloud/ Wind River® Titanium Cloud] R5 product. Intel and Wind River have jointly open sourced this software and we invite you to download, build, install, and run it.

Wind River Titanium Cloud was originally built on open source components, that were then extended and hardened to meet critical infrastructure requirements, including: high availability, fault management, and performance management. This software provides numerous features and capabilities to enable 24/7 operation of mission critical applications.

You can find an overview of the StarlingX project's features <insert link here>.

The StarlingX project opens all of these enhancements to the open source community. Please join us as we build the infrastructure stack for Edge Computing.
----

{| style="border-collapse: separate; border-spacing: 25px;"
|style="vertical-align:top; width:50%;" |


== Releases ==
The first StarlingX release will be stx.2018.10 and will be available in late October.
* How to get the code (placeholder)
* [[StarlingX/stx.2018.10 Release Notes|stx.2018.10 Release Notes]]

== Documentation ==
These three documents will help get you started building, installing, and validating your installation of StarlingX:
* [[StarlingX/Developer Guide|Developer Guide]]
* [[StarlingX/Installation Guide|Installation Guide]]
* [[StarlingX/Testing Guide|Testing Guide]]

== Code ==
The StarlingX project uses Gerrit as its web-based code change management and review tool.
* [https://git.starlingx.io/cgit Gerrit repositories] maintain the StarlingX code, build instructions are in the [[StarlingX/Developer Guide]]
* [https://review.openstack.org/#/admin/projects/?filter=stx StarlingX Gerrit Projects] and [https://review.openstack.org/#/q/status:open+AND+project:%255Eopenstack/stx-%2540 Open StarlingX project reviews]
* [https://review.openstack.org/#/dashboard/?foreach=(project:openstack/stx-clients%20OR%20project:openstack/stx-config%20OR%20project:openstack/stx-distcloud%20OR%20project:openstack/stx-distcloud-client%20OR%20project:openstack/stx-fault%20OR%20project:openstack/stx-gui%20OR%20project:openstack/stx-ha%20OR%20project:openstack/stx-integ%20OR%20project:openstack/stx-manifest%20OR%20project:openstack/stx-metal%20OR%20project:openstack/stx-nfv%20OR%20project:openstack/stx-root%20OR%20project:openstack/stx-tools%20OR%20project:openstack/stx-update%20OR%20project:openstack/stx-upstream)%20status:open%20NOT%20owner:self%20NOT%20label:Workflow%3C=-1%20label:Verified%3E=1,zuul%20NOT%20reviewedby:self&title=StarlingX%20Review%20Inbox&Needs%20final%20%202=label:Code-Review%3E=2%20limit:50%20NOT%20label:Code-Review%3C=-1,self&Passed%20Zuul,%20No%20Negative%20Feedback%20(Small%20Fixes)=NOT%20label:Code-Review%3E=2%20NOT%20label:Code-Review%3C=-1,starlingx-core%20delta:%3C=10&Passed%20Zuul,%20No%20Negative%20Feedback=NOT%20label:Code-Review%3E=2%20NOT%20label:Code-Review%3C=-1,starlingx-core%20delta:%3E10&Needs%20Feedback%20(Changes%20older%20than%205%20days%20that%20have%20not%20been%20reviewed%20by%20anyone)=NOT%20label:Code-Review%3C=-1%20NOT%20label:Code-Review%3E=1%20age:5d&You%20are%20a%20reviewer,%20but%20haven't%20voted%20in%20the%20current%20revision=NOT%20label:Code-Review%3C=-1,self%20NOT%20label:Code-Review%3E=1,self%20reviewer:self&Wayward%20Changes%20(Changes%20with%20no%20code%20review%20in%20the%20last%202days)=NOT%20is:reviewed%20age:2d StarlingX Gerrit Review Dashboard]
* [https://review.openstack.org/#/dashboard/?foreach=%28project%3Aopenstack%2Fstx-clients+OR+project%3Aopenstack%2Fstx-config+OR+project%3Aopenstack%2Fstx-distcloud+OR+project%3Aopenstack%2Fstx-distcloud-client+OR+project%3Aopenstack%2Fstx-fault+OR+project%3Aopenstack%2Fstx-gui+OR+project%3Aopenstack%2Fstx-ha+OR+project%3Aopenstack%2Fstx-integ+OR+project%3Aopenstack%2Fstx-manifest+OR+project%3Aopenstack%2Fstx-metal+OR+project%3Aopenstack%2Fstx-nfv+OR+project%3Aopenstack%2Fstx-root+OR+project%3Aopenstack%2Fstx-tools+OR+project%3Aopenstack%2Fstx-update+OR+project%3Aopenstack%2Fstx-upstream%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D-1+label%3AVerified%3E%3D1%2Czuul+NOT+reviewedby%3Aself&title=StarlingX+Review+Inbox&Needs+final+%2B2=label%3ACode-Review%3E%3D2+limit%3A50+NOT+label%3ACode-Review%3C%3D-1%2Cself&Passed+Zuul%2C+No+Negative+Feedback+%28Small+Fixes%29=NOT+label%3ACode-Review%3E%3D2+NOT+label%3ACode-Review%3C%3D-1%2Cstarlingx-core+delta%3A%3C%3D10&Passed+Zuul%2C+No+Negative+Feedback=NOT+label%3ACode-Review%3E%3D2+NOT+label%3ACode-Review%3C%3D-1%2Cstarlingx-core+delta%3A%3E10&Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode-Review%3C%3D-1+NOT+label%3ACode-Review%3E%3D1+age%3A5d&You+are+a+reviewer%2C+but+haven't+voted+in+the+current+revision=NOT+label%3ACode-Review%3C%3D-1%2Cself+NOT+label%3ACode-Review%3E%3D1%2Cself+reviewer%3Aself&Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+is%3Areviewed+age%3A2d StarlingX Gerrit Review Dashboard by Status]

* [[StarlingX/CodeSubmissionGuidelines|Code Submission Guidelines]]

== Planning & Process ==
* [[StarlingX/Release_Plan|StarlingX Release Planning]]
* [[StarlingX/Feature Development Process|StarlingX Feature Development Process (in review)]]
* [[StarlingX/Defect Handling Process|StarlingX Defect Handling Process]]

== Story and Bug Tracking ==
We are using the OpenStack Storyboard tool for tracking feature development activities. Each new Story shall be marked with one or more Tags, and can optionally include one or more Prefixes in the description. See [[StarlingX/Tags and Prefixes|Tags and Prefixes]] for a description of how we use them.

The StarlingX Storyboard project group is [https://storyboard.openstack.org/#!/project_group/86 here]. '''IMPORTANT:''' If you create a new story (of any kind), please mark it with the tag "stx.new" so we can find it, review it and assign it to the right team and a release.

We are using Launchpad for tracking bugs. [https://bugs.launchpad.net/starlingx Link to the StarlingX Launchpad] '''IMPORTANT:''' If you create a new bug, please use [[StarlingX/BugTemplate|the StarlingX Bug Template]].

Sample queries:
* To find newly created stories, use: [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.new this query]
* To find stories with no sub-project tags, use [https://storyboard.openstack.org/#!/worklist/456 this worklist]
* To find all active stories assigned to the stx.2018.10 release, use [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.2018.10 this query]
* To find all active bugs assigned to the stx.2018.10 release in launchpad, use [https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2018.10 this query].
* [Temporary] To find all active bugs in story board, use: [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.bug this query]
* Queries for the Sub-projects are defined on each Sub-project's page

Optional: You can also use Prefixes to search for Stories, but we consider Prefixes optional so these searches might not show the same results as searching for Tags.
* Sample Prefix queries:
** To find all Stories with the [Features] prefix use: [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Feature this query]
** To find all Stories with the [Build] prefix use: [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Build this query]

== References ==

* [https://etherpad.openstack.org/p/stx-notes The list of repos] and other things

== OpenStack Documentation ==

These are references to general OpenStack material:

* [https://docs.openstack.org/infra/manual/developers.html Developer's Guide]
* [https://docs.openstack.org/infra/manual/creators.html Project Creator's Guide]
* [https://wiki.openstack.org/wiki/How_To_Contribute The Contributors Guide] (the older wiki page)
* [https://governance.openstack.org/tc/reference/project-testing-interface.html Project Testing Interface]

== Governance ==

A very preliminary Governance document can be found [https://etherpad.openstack.org/p/stx-governance here]. It contains lot of feedback from various reviewers of the early drafts.

A more polished version of the same document can be found [[Starlingx/Initial Governance|on this page.]]

|style="vertical-align:top; width:50%;" |


== Culture ==

We are proud to be an OpenStack Foundation project!
* We support and adhere to the [https://www.openstack.org/legal/community-code-of-conduct/ OpenStack community Code of Conduct]
* We support and fully embrace the [https://governance.openstack.org/tc/reference/opens.html Four Opens]
* [[StarlingX/Contribution Guidelines|Contribution Guidelines]]
* The mailing lists are now live at http://lists.starlingx.io/. There are two lists, starlingx-announce and starlingx-discuss. Please subscribe.
* We have the #starlingX IRC channel set up on freenode. Refer to https://docs.openstack.org/infra/manual/developers.html regarding how to have your IRC account setup.

== Meetings ==

=== Weekly calls ===

The list of meetings and dial-in information can be found [[Starlingx/Meetings|on this page.]]

=== PTG Meetings ===

We are preparing for the Denver OpenStack PTG meeting. Draft agenda items can be found here:
* [https://etherpad.openstack.org/p/stx-PTG-agenda StarlingX Denver PTG Agenda]

== Status and Planning ==
This section is under construction.
=== Overall project planning pages ===
* [[StarlingX/Project Priorities|Project Priorities]]
* [[StarlingX/Release Plan|Release Plan]]
* [[StarlingX/Project Plans|Project Plans]]

=== StarlingX Projects ===
StarlingX is both a development project and an integration project that combines new services with many other open source projects into an overall Edge Cloud software stack. We've broken the overall project into a set of separate projects to help keep things manageable.
Notes from the F2F discussion on how to organize sub-teams are [https://ethercalc.openstack.org/ctjc7vlbphm1 here]
==== StarlingX main projects ====
Information on the main StarlingX development projects can be found on the wiki pages below:
{| class=wikitable
|-
| [[StarlingX/Config|Config project]]|| [[StarlingX/Fault|Fault project]]
|-
| [[StarlingX/HA|HA project]] || [[StarlingX/GUI|GUI project]]
|-
| [[StarlingX/Metal|Metal project]]|| [[StarlingX/NFV|NFV project]]
|-
| [[StarlingX/Update|Update project]]|| [[StarlingX/DistCloud|Distributed Cloud project]]
|}

==== StarlingX supporting projects ====
In addition to the main StarlingX development projects there are also additional projects to help us develop, maintain, document, build and release the overall StarlingX software stack.
{| class="wikitable"
|-
| [[StarlingX/Docs_and_Infra|Docs and Infra project]]|| [[StarlingX/Build|Build project]]
|-
| [[StarlingX/DistroOpenStack|Distro - OpenStack project]] || [[StarlingX/Distro|Distro - Non-OpenStack project]]
|-
| [[StarlingX/Test|Test project]]|| [[StarlingX/Security|Security project]]
|-
| [[StarlingX/Containers|Containers project]]|| [[StarlingX/Networking|Networking project]]
|-
| [[StarlingX/Releases|Releases project]] || [[StarlingX/MultiOS|MultiOS project]]
|}

==== StarlingX cross-project initiatives ====
There are several initiatives we are implementing that cross project boundaries:
{| class="wikitable"
|-
| [[StarlingX/Pyton2|Python2 to Python3 Transition]]|| [[StarlingX/Zull|Zuul Enablement and Coverage]]
|-
| [[StarlingX/Devstack|Devstack Integration]] ||
|}
ToDo:
* Add a vendor project for Intel platform specific features e.g. FPGA access in guests, GPU support in guests, Intel SGX and EPID support and NEV SDK integration
* Create a Project Map graphic that captures all of this in a graphical way, similar to (or an extension of) the OpenStack project map.

== Upstream Status ==

The StarlingX code base contains a number of out-of-tree patches against other open source components. One of our highest priorities is to contribute those changes to their upstream communities.

We are tracking our progress in a [https://docs.google.com/spreadsheets/d/1nKnkweuxcqvVOoRcpnTYMVUUv1RoAugOWXMjB7VIrfc/edit?usp=sharing shared Google document]. Please send an email to [mailto:bruce.e.jones@intel.com BruceJ @ Intel] with your gmail.com email address for access to the document.

StarlingX/Release Process

2018-09-27T22:51:31Z

Dtroyer:

Describe the steps in creating a StarlingX Release

= Release Activity =

== Milestone ==

* Finalize any outstanding changes to master stx-manifest/default.xml, particularly for the starlingx and stx-staging remotes as those are used to create the list of repos to branch and tag.
* Create the branches and tag them by running stx-tools/release/branch-stx.sh. Set SERIES to the proper value if the current year/month is not correct: <pre>SERIES=2018.07 stx-tools/release/branch-stx.sh</pre>
* Create the branch manifest in stx-manifest/default.xml
* Review and approve the .gitreview updates in the new branch

== Release ==

* Make a cleanup pass though release notes and add missing
* Finalize any outstanding changes to master stx-manifest/default.xml, particularly for the starlingx and stx-staging remotes as those are used to create the list of repos to branch and tag.
* Create the branches and tag them by running stx-tools/release/branch-stx.sh. Set SERIES, BRANCH and TAG to the proper values:
** SERIES=YYYY.MM
** BRANCH=r/YYYY.MM
** TAG=YYYY.MM.rc1
* Create the branch manifest in stx-manifest/default.xml
* Review and approve the .gitreview updates in the new branch
* Look for UPPER_CONSTRAINTS_FILE values to update for stable branches (there may not be any as this is an OpenStack-ism that we would change when rebasing OpenStack projects)
* Verify release notes appear correctly and make adjustments

= Scripts =

== branch-stx.sh ==

Found in stx-tools/release, performs the following steps:
* create repo list using getrepo.sh (also in stx-tools/release) to extract from stx-manifest/default.xml for the starlingx and stx-staging remotes
* for each repo:
** clone repo
** create the new branch
** tag branch
** for gerrit (starlingx) repos:
*** push to gerrit
*** update .gitreview
** for Github repos (stx-staging):
*** push to github

StarlingX/Release Plan

2018-09-27T22:51:20Z

Dtroyer:

<big><big> '''Releases''' </big></big>

StarlingX is released periodically; one release in 2018 and three releases/year starting in 2019. A release consists of a branch in the source code repositories that enables repeatable builds over time.
----
== Release Definition ==

A StarlingX milestone/release is a tagged branch in the source code repositories that:
* is considered stable and can be used for repeatable builds
* will have no additional features added
* will backport bug fixes for critical issues only
* will be maintained in the canonical repositories for a specified minimum period
* The list of repos included is maintained in stx-manifest/default.xml (or similar) for any given release. (Note: this file included non-StarlingX-managed repos, only repos from the "starlingx" and "stx-staging" remotes are included.)
* The actual release is a tag on the corresponding branch, i.e. r/2018.10 release branch will be initially tagged as 2018.10.0

== Release Cadence and Schedule ==

'''Releases are published in a time based fashion:'''
* The initial StarlingX release is planned for October 2018
* From 2019, the regular release cadence is 3 releases/year; released in March, July, and November.

== Release Lifecycle ==
=== Release Definition Phase ===
*
*

=== Release Planning Phase ===
*
*

=== Release Execution Phase ===
*
*

=== Code Freeze and RC Phase ===
*
*

==== Formal Releases ====
* Released three times per year
* For each release, the code freeze for that release is four weeks prior to the release date.
* Branch name format r/YYYY.MM[.n]
** 'r/' is the branch name prefix (release)
** .n is a sequence number appended if more than one branch is created in a given month
r/2018.10
* Release Candidate is tagged as YYYY.MM.rcX
* Release is tagged as YYYY.MM.0

==== Monthly Milestones ====
* Informal milestones to be used by the test team for a pre-defined sanity/regression test cycle.
* Created each month in the 2nd week of the month a branch will be pulled.
* Branch name format m/YYYY.MM
** 'm/' is the branch name prefix (milestone)
** .n is a sequence number appended if more than one branch is created in a given month
m/2018.07
* Milestone is tagged as YYYY.MM.0

==== Long Term Support ====
* To be defined based on release content, not time based

=== Support Length ===
* Formal releases are supported for 8 months; support for the '''n''' and '''n-1''' releases.
* Long Term Support is ""TBD""

== List of Releases ==
'''Planned'''
{| class="wikitable"
|-
! Version !! Code Freeze !! Release Date !! End of Life Date !! Docs
|-
| 2018.10.0 || 2018/09/26 || 2018/10/24 || TBD || TBD
|-
| 2019.03.0 || 2019/02/13 || 2018/03/13 || TBD || TBD
|-
| 2019.07.0 || TBD || TBD || TBD || TBD
|-
| 2019.11.0 || TBD || TBD || TBD || TBD
|-
| ... || || ||
|}

== Release Team ==
* For team members and other information, visit the StarlingX Releases sub-project wiki page [https://wiki.openstack.org/wiki/StarlingX/Releases here]

== Release Diagram ==
'''''Diagram needs to be updated'''''
[[File:Stx Release Plan.png||]]

Starlingx/Initial Governance

2018-09-17T22:41:47Z

Dtroyer: /* Technical Steering Committee */

== StarlingX Initial Governance ==
The initial draft of this document with feedback from the reviewers [https://etherpad.openstack.org/p/stx-governance is on this Etherpad].

=== Introduction ===
The StarlingX project is governed according to the OpenStack Foundation's "[https://governance.openstack.org/tc/reference/opens.html four opens]", which are open source, open design, open development and open community. Technical decisions are made by technical contributors, technical leaders and by a representative Technical Steering Committee. Our community is committed to diversity, openness, and encouraging new contributors and leaders to rise up.

StarlingX is both a development project and an integration project. It includes new services that provide important features and combines them with components from many other Open Source projects into a complete Edge Cloud solution. To help manage the complexity of the project, we have divided the project up into several sub-projects, each with project and technical leadership, to help distribute the overall work and to acknowledge in the community that there are multiple ways to contribute to the project. The sub-project lifecycle is managed by the project's Technical Steering Committee who approve the creation of new sub-projects and the retirement of sub-projects that are no longer active.

StarlingX is a brand new project and is in an initial "bootstrapping" phase in which the leadership positions will be volunteers. All leadership positions will transition to be elected by the project's Contributors within one year.

=== Project Roles ===
StarlingX defines the following roles for the project.

==== Contributors ====
A Contributor to StarlingX is someone who has made a Contribution to the project within the last 12 months. Contributions can include merged code, test or document submissions, or serving in a leadership role as defined below. All Contributions are welcome and will be accepted based on their technical merit.

The project's Technical Steering Committee can grant Contributor status for other contributions at its discretion.

Contributors are eligible to vote in the elections for Technical Steering Committee positions and for the leadership roles described in this document. Contributors are also eligible to become members of the Technical Steering Committee and/or serve in a leadership role.

==== Core Reviewer ====
Core Reviewers are active Contributors and participants in a sub-project that have the additional responsibility to review the changes proposed to the sub-project, to ensure that approved changes are aligned with the project's design & architecture, and meet the project's quality requirements. Core Reviewers have the ability to approve code to be merged into the StarlingX repositories. Core Reviewers for a sub-project are appointed by the sub-project Technical Lead with input from other StarlingX Core Reviewers. Contributors can become Core Reviewers for multiple sub-projects.

==== Technical Lead ====
A Technical Lead in StarlingX is a Core Reviewer who has additional responsibility for guiding the overall technical direction of one or more of the sub-projects, under the overall technical guidance of the Technical Steering Committee. Technical Leads are responsible for resolving disagreements between the sub-project's Contributors and Core Reviewers. A sub-project's Technical Lead should be included as a reviewer and approver for any [https://wiki.openstack.org/wiki/StarlingX/Feature_Development_Process Feature Specification] that impacts their sub-project. The initial Technical Leads are appointed to one year terms at launch by the Technical Steering Committee but will be fully elected by the sub-project's Contributors on an annual basis. Technical Lead elections will be held in September of every year starting in 2019 and will be administered by the TSC or their delegates. Contributors can be Technical Leads for multiple sub-projects.

==== Project Lead ====
A Project Lead in StarlingX is an outside facing role for a StarlingX sub-project that is responsible for requirements gathering, tracking progress, reporting results, handling outside communication, serving as a project ambassador and facilitating the four opens within the sub-project. The Project Lead works with the Technical Lead and the sub-project team to break down large work items for the team into Stories and Tasks. The Project Lead can help guide Contributors to the work items most needed by the sub-project, as defined by the Project Priorities established by the Technical Steering Committee. The initial Project Leads are appointed to one year terms at launch by the Technical Steering Committee but will be fully elected by the sub-project's Contributors on an annual basis with the first election to be held in April 2019. Contributors can be Project Leads for multiple sub-projects.

The same person can become a Technical Lead and Project Lead for a StarlingX sub-project. That person's role would then be similar to an [https://docs.openstack.org/project-team-guide/ptl.html OpenStack PTL]. The StarlingX project has split these roles to enable Technical Leaders to focus more of their attention on technical issues and to leverage the skills and strengths of Project Leaders in the initial community.

==== Technical Steering Committee ====
The Technical Steering Committee is responsible for overall project architectural decisions, managing the sub-project life-cycle including approving new sub-projects and making final decisions if sub-project Core Reviewers, Technical Leads or Project Leads disagree. It defines the overall project architecture and sets the overall Project Priorities in collaboration with the community. It will be comprised of 7 members who will be appointed at Launch but fully elected by the Contributors within the first year.

The initial Technical Steering Committee members will be:
* Brent Rowsell (Wind River)
* Ian Jolliffe (Wind River)
* Dean Troyer (Intel)
* Saul Wold (Intel)
* TBD...
We are actively recruiting for additional Technical Steering Committee members

In September 2019, 3 of the 7 seats will be up for election by the project's Contributors. Anyone who is a Contributor to the project will be eligible to run, and anyone who is a Contributor is eligible to vote. In that election the TSC positions held by one each of the members from Wind River and Intel will be opened for election, to be determined randomly. In April 2020, the remaining 4 seats will be up for election. In that election, the other initial TSC members from Wind River and Intel will be opened for election. TSC elections will continue on this staggered cycle (3 seats and 4 seats) every six months in order to allow new leaders to rise up and ensure some consistency across the terms. TSC members will serve at least one year terms after the initial bootstrapping phase. There are no term limits, but in order to encourage diversity, no more than 2 of the 7 seats can be filled by any one organization.

The Technical Steering Committee will meet regularly in an open forum with times and locations published in community channels. The Technical Steering Committee can elect a Chair at its discretion. Meetings with be hosted and facilitated by the OpenStack Foundation.

Voting within the TSC requires a quorum of 5 members present. In the initial phase when the TSC does not have 5 members, a quorum will be 4 members. TSC members should seek consensus on most technical issues but if needed they can be resolved through a simple majority vote. Voting to create a new or archive an inactive StarlingX sub-project or to change the project's formal Governance document requires a 2/3rds super-majority.

The exact size and model for the Technical Steering Committee will evolve over time based on the needs and growth of the project, but the governing body will always be committed to openness, diversity and the principle that technical decisions are made by technical contributors.

=== Elections ===
All elections for leadership positions in StarlingX shall follow standard OpenStack procedures and methods. Ballots will be distributed to each Contributor's primary email address. Elections will be held using CIVS and a Condorcet algorithm (Schulze/Beatpath/CSSD variant). Any tie will be broken using [https://wiki.openstack.org/wiki/Governance/TieBreaking Governance_TieBreaking]. In the event that a candidate runs unopposed for a position, the TSC can waive a formal vote. Membership in the Foundation itself is not a requirement for holding an elected position though it is preferred. Elections are appointing an individual to a position in the project, not a company or organization. Individuals are expected to continue to support the project in the event of career changes unless they notify the project that they are resigning their position.

=== Governance Changes ===
The project's formal governance document shall be maintained in a git repository. Changes to the document can be proposed by any project Contributor but would need to be ratified by the TSC with a super-majority (2/3rds) vote. The TSC should strive for consensus for any change to the project's formal governance.

Installation libvirt qemu

2018-09-07T19:50:49Z

Dtroyer: Created page with "Installation for StarlingX using Libvirt/QEMU virtualization. ===Hardware Requirements=== A workstation computer with: * Processor: x86_64 only supported architecture with..."

Installation for StarlingX using Libvirt/QEMU virtualization.

===Hardware Requirements===

A workstation computer with:

* Processor: x86_64 only supported architecture with BIOS enabled hardware virtualization extensions
* Memory: At least 32GB RAM
* Hard Disk: 500GB HDD
* Network: One network adapter with active Internet connection

===Software Requirements===

A workstation computer with:

* Operating System: This process is known to work on Ubuntu 16.04 and is likely to work on other Linux OS's with some appropriate adjustments.
* Proxy settings configured (if applies)
* Git
* KVM/VirtManager
* Libvirt Library
* QEMU Full System Emulation Binaries
* <stx-deployment> project
* StarlingX ISO Image

==Deployment Environment Setup==

=== Configuration ===

These scripts are configured using environment variables that all have built-in defaults. On shared systems you probably do not want to use the defaults. The simplest way to handle this is to keep an rc file that can be sourced into an interactive shell that configures everything. Here's an example called madcloud.rc::

<pre><nowiki>
export CONTROLLER=madcloud
export COMPUTE=madnode
export BRIDGE_INTERFACE=madbr
export INTERNAL_NETWORK=172.30.20.0/24
export INTERNAL_IP=172.30.20.1/24
export EXTERNAL_NETWORK=192.168.20.0/24
export EXTERNAL_IP=192.168.20.1/24
</nowiki></pre>

This rc file shows the defaults baked into the scripts:

<pre><nowiki>
export CONTROLLER=controller
export COMPUTE=compute
export BRIDGE_INTERFACE=stxbr
export INTERNAL_NETWORK=10.10.10.0/24
export INTERNAL_IP=10.10.10.1/24
export EXTERNAL_NETWORK=192.168.204.0/24
export EXTERNAL_IP=192.168.204.1/24
</nowiki></pre>

===Install stx-tools project===

Clone the stx-tools project into a working directory.

<pre><nowiki>
git clone git://git.openstack.org/openstack/stx-tools.git
</nowiki></pre>

It will be convenient to set up a shortcut to the deployment script directory:
<pre><nowiki>
SCRIPTS=$(pwd)/stx-tools/deployment/libvirt
</nowiki></pre>

Load the configuration (if you created one) from madcloud.rc:
<pre><nowiki>
source madcloud.rc
</nowiki></pre>

===Installing Requirements and Dependencies===

Install the required packages and configure QEMU. This only needs to be done once per host. (NOTE: this script only knows about Ubuntu at this time):
<pre><nowiki>
$SCRIPTS/install_packages.sh
</nowiki></pre>

===Disabling Firewall===

Unload firewall and disable firewall on boot:

<pre><nowiki>
sudo ufw disable
sudo ufw status
</nowiki></pre>

=== Configure Networks ===

Configure the network bridges using setup_network.sh before doing anything else. It will create 4 bridges named stxbr1, stxbr2, stxbr3 and stxbr4. Set the BRIDGE_INTERFACE environment variable if you need to change stxbr to something unique.

<pre><nowiki>
$SCRIPTS/setup_network.sh
</nowiki></pre>

The destroy_network.sh script does the reverse, and should not be used lightly. It should also only be used after all of the VMs created below have been destroyed.

There is also a script cleanup_network.sh that will remove networking configuration from libvirt.

=== Configure Controllers ===

There are two scripts for creating the controllers: setup_allinone.sh and setup_standard_controller.sh. They are operated in the same manner but build different StarlingX cloud configurations. Choose wisely.

You need an ISO file for the installation, these scripts take a name with the -i option::

<pre><nowiki>
$SCRIPTS/setup_allinone.sh -i stx-2018-08-28-93.iso
</nowiki></pre>

And the setup will begin. The scripts create one or more VMs and start the boot of the first controller, named oddly enough ``controller-0``. If you have Xwindows available you will get virt-manager running. If not, Ctrl-C out of that attempt if it doesn't return to a shell prompt. Then connect to the serial console::

<pre><nowiki>
virsh console madcloud-0
</nowiki></pre>

Continue the usual StarlingX installation from this point forward.

Tear down the VMs using destroy_allinone.sh and destroy_standard_controller.sh.

== Continue ==

Pick up the installation in one of the existing guides at the 'Initializing Controller-0 step.

* Standard Controller
** [[StarlingX/Installation Guide Virtual Environment/Dedicated Storage|StarlingX Cloud with Dedicated Storage Virtual Environment]]
** [[StarlingX/Installation Guide Virtual Environment/Controller Storage|StarlingX Cloud with Controller Storage Virtual Environment]]
* All-in-one
** [[StarlingX/Installation Guide Virtual Environment/Duplex|StarlingX Cloud Duplex Virtual Environment]]
** [[StarlingX/Installation Guide Virtual Environment/Simplex|StarlingX Cloud Simplex Virtual Environment]]

StarlingX/Installation Guide

2018-09-07T19:50:44Z

Dtroyer:

== Intro ==

StarlingX may be installed in virtual environments, two options are currently known to work: [[Installation_libvirt_qemu|Libvirt/QEMU]] and VirtualBox. Virtual environments should only be used for evaluation or development purposes; real deployments of StarlingX are only supported on physical servers.

==Requirements==

Different use cases require different configurations. For the StarlingX Deployment Options described later, the recommended minimum requirements for the workstation, running the Virtual Machine(s) where StarlingX will be deployed, include:

===Hardware Requirements===

A workstation computer with:

* Processor: x86_64 only supported architecture with BIOS enabled hardware virtualization extensions
* Memory: At least 32GB RAM
* Hard Disk: 500GB HDD
* Network: Two network adapters with active Internet connection

===Software Requirements===

A workstation computer with:

* Operating System: Freshly installed Ubuntu 16.04 LTS 64-bit
* Proxy settings configured (if applies)
* Git
* KVM/VirtManager
* Libvirt Library
* QEMU Full System Emulation Binaries
* <stx-deployment> project
* StarlingX ISO Image

==Deployment Environment Setup==

This section describes how to set up a StarlingX Controller Storage system in a workstation computer. After completing these steps, you will be able to deploy and run your StarlingX system on the following Linux distribution:

* Ubuntu 16.04 LTS 64-bit

===Updating Your Operating System===

Before proceeding with the build, ensure your OS is up to date. You’ll first need to update the local database list of available packages:

<pre><nowiki>
$ sudo apt-get update
</nowiki></pre>

===Install stx-tools project===

Clone the stx-tools project. Usually you’ll want to clone it under your user’s home directory.

<pre><nowiki>
$ cd $HOME
$ git clone git://git.openstack.org/openstack/stx-tools
</nowiki></pre>

===Installing Requirements and Dependencies===

Navigate to the stx-tools installation libvirt directory:
<pre><nowiki>
$ cd $HOME/stx-tools/deployment/libvirt/
</nowiki></pre>

Install the required packages:
<pre><nowiki>
$ bash install_packages.sh
</nowiki></pre>

===Getting the StarlingX ISO Image===

Follow the instructions from [[StarlingX/Developer_Guide]] to build a StarlingX ISO image. Copy the StarlingX ISO Image to the ''<stx-deployment>'' libvirt project directory naming it as bootimage.iso:

<pre><nowiki>
$ cp <starlingx iso image> $HOME/stx-tools/deployment/libvirt/bootimage.iso
</nowiki></pre>

===Disabling Firewall===

Unload firewall and disable firewall on boot:

<pre><nowiki>
$ sudo ufw disable
Firewall stopped and disabled on system startup
$ sudo ufw status
Status: inactive
</nowiki></pre>

==Deployment Options==

* Standard Controller
** [[StarlingX/Installation Guide Virtual Environment/Dedicated Storage|StarlingX Cloud with Dedicated Storage Virtual Environment]]
** [[StarlingX/Installation Guide Virtual Environment/Controller Storage|StarlingX Cloud with Controller Storage Virtual Environment]]
* All-in-one
** [[StarlingX/Installation Guide Virtual Environment/Duplex|StarlingX Cloud Duplex Virtual Environment]]
** [[StarlingX/Installation Guide Virtual Environment/Simplex|StarlingX Cloud Simplex Virtual Environment]]

Starlingx/Initial Governance

2018-08-31T20:00:29Z

Dtroyer: Add a link to OSF's four opens page

== StarlingX Initial Governance ==
The initial draft of this document with feedback from the reviewers [https://etherpad.openstack.org/p/stx-governance is on this Etherpad].

=== Introduction ===
The StarlingX project is governed according to the OpenStack Foundation's "[https://governance.openstack.org/tc/reference/opens.html four opens]", which are open source, open design, open development and open community. Technical decisions are made by technical contributors, technical leaders and by a respresentative Technical Steering Committee. Our community is committed to diversity, openness, and encouraging new contributors and leaders to rise up.

StarlingX is both a development project and an integration project. It includes new services that provide important features and combines them with components from many other Open Source projects into a complete Edge Cloud solution. To help manage the complexity of the project, we have divided the project up into several sub-projects, each with project and technical leadership, to help distribute the overall work and to acknowledge in the community that there are multiple ways to contribute to the project. The sub-project lifecycle is managed by the project's Technical Steering Committee who approve the creation of new sub-projects and the retirement of sub-projects that are no longer active.

StarlingX is a brand new project and is in an initial "bootstrapping" phase in which the leadership positions will be appointed volunteers. All leadership positions will transition to be elected by the project's Contributors within one year.

=== Project Roles ===
StarlingX defines the following roles for the project.

==== Contributors ====
A Contributor to StarlingX is someone who has made a Contribution to the project within the last 12 months. Contributions can include merged code, test or document submissions, or serving in a leadership role as defined below. The project's Technical Steering Committee can grant Contributor status for other contributions at its discretion. Contributors are eligible to vote in Technical Steering Committee elections. All Contributions are welcome and will be accepted based on their technical merit.

==== Core Reviewer ====
A Core Reviewer for a sub-project has the responsibility to review the changes proposed to the sub-project and help ensure that approved changes are aligned with the project's design & architecture, and meet the project's quality requirements. Core Reviewers have the ability to approve code to be merged into the StarlingX repositories. Core Reviewers are active Contributors and participants in the project. Core Reviewers for a sub-project are appointed by the sub-project Technical Lead with input from other StarlingX Core Reviewers. Contributors can become Core Reviewers for multiple sub-projects.

==== Technical Lead ====
A Technical Lead in StarlingX is a Core Reviewer who has additional responsibility for guiding the overall technical direction of one or more of the sub-projects, under the overall technical guidance of the Technical Steering Committee. Technical Leads are responsible for resolving disagreements between the sub-project's Contributors and Core Reviewers. The initial Technical Leads are appointed to one year terms at launch by the Technical Steering Committee but will be fully elected by the sub-project's Contributors on an annual basis. Contributors can be Technical Leads for multiple sub-projects.

==== Project Lead ====
A Project Lead in StarlingX is responsible for the sub-project's work item list and facilitating the four opens within the sub-project. The Project Lead works with the Technical Lead to break down large work items for the team into Stories and Tasks. The Project Lead can help guide Contributors to the work items most needed by the sub-project, as defined by the Project Priorities established by the Technical Steering Committee. The initial Project Leads are appointed to one year terms at launch by the Technical Steering Committee but will be fully elected by the sub-project's Contributors on an annual basis. Contributors can be Project Leads for multiple sub-projects.

The same person can become a Technical Lead and Project Lead for a StarlingX sub-project.

==== Technical Steering Committee ====
The Technical Steering Committee is responsible for architectural decisions and making final decisions if sub-project Core Reviewers, Technical Leads or Project Leads disagree. It defines the overall project architecture and sets the overall Project Priorities. It will be comprised of 9 members who will be appointed at Launch but fully elected by the Contributors within the first year.

The initial Technical Steering Committee members will be:
* Brent Rowsell and Ian Jolliffe from Wind River
* Dean Troyer and Saul Wold from Intel
* TBD...
We are actively recruiting for additional Technical Steering Committee members

In April 2019, 4 of the 9 seats will be up for election by the project's Contributors. Anyone who is a Contributor to the project will be eligible to run, and anyone who is a Contributor is eligible to vote. In October 2019, the remaining 5 seats will be up for election. The elections will continue on this staggered cycle (4 seats and 5 seats) every six months in order to allow new leaders to rise up, but also ensure some consistency across the terms. There are no term limits, but in order to encourage diversity, no more than 2 of the 9 seats can be filled by any one organization. The Technical Steering Committee will meet regularly in an open forum with times and locations published in community channels.

The Technical Steering Committee can elect a Chair at its discretion. Meetings with be hosted and facilitated by the OpenStack Foundation.

The exact size and model for the Technical Steering Committee will evolve over time based on the needs and growth of the project, but the governing body will always be committed to openness, diversity and the principle that technical decisions are made by technical contributors.

=== Elections ===
All elections for leadership positions in StarlingX shall follow standard OpenStack procedures and methods. In the event that a candidate runs unopposed for a position, the TSC can waive a formal vote. Membership in the Foundation itself is not a requirement for holding an elected position though it is preferred. Elections are appointing an individual to a position in the project, not a company or organization. Individuals are expected to continue to support the project in the event of career changes unless they notify the project that they are resigning their position.

StarlingX/Branches

2018-08-22T21:26:47Z

Dtroyer:

StarlingX/Branches

2018-08-21T16:16:25Z

Dtroyer: Created page with "= Branches = StarlingX branching policy is largely derived from OpenStack policy with some changes to accommodate different development cycle and release priorities. == Sta..."

StarlingX/Developer Guide

2018-07-26T13:42:46Z

Dtroyer: Update stx URLs to https://git.starlingx.io/...

This section contains the steps for building a StarlingX ISO from Master branch.

== Requirements ==

The recommended minimum requiremeonts include:

=== Hardware Requirements ===

A workstation computer with:

* Processor: x86_64 only supported architecture
* Memory: At least 32GB RAM
* Hard Disk: 500GB HDD
* Network: Network adapter with active Internet connection

=== Software Requirements ===

A workstation computer with:

* Operating System: Ubuntu 16.04 LTS 64-bit
* Docker
* Android Repo Tool
* Proxy Settings Configured (If Required)
** See http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000136.html for more details
* Public SSH Key

== Development Environment Setup ==

This section describes how to set up a StarlingX development system on a workstation computer. After completing these steps, you will be able to build a StarlingX ISO image on the following Linux distribution:

* Ubuntu 16.04 LTS 64-bit

=== Update Your Operating System ===

Before proceeding with the build, ensure your OS is up to date. You’ll first need to update the local database list of available packages:

<source lang="sh">$ sudo apt-get update
</source>
=== Installation Requirements and Dependencies ===

<ol start="1">
==== Git ====
<li>Install the required packages in an Ubuntu host system with:
<source lang="sh">$ sudo apt-get install git
</source></li>
==== Docker CE ====
<li>Install the required Docker CE packages in an Ubuntu host system. See [https://docs.docker.com/install/ Get Docker] for more information.</li>
==== Android Repo Tool ====
<li>Install the required Android Repo Tool in an Ubuntu host system. Follow the 2 steps in "Installing Repo" section from [https://source.android.com/setup/build/downloading#installing-repo Installing Repo] to have Andriod Repo Tool installed.</li></ol>

=== Install Public SSH Key===

# Follow these instructions on GitHub to [https://help.github.com/articles/connecting-to-github-with-ssh Generate a Public SSH Key] and then upload your public key to your GitHub and Gerrit account profiles:
#* [https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account Upload to Github]
#* [https://review.openstack.org/#/settings/ssh-keys Upload to Gerrit]

=== Install stx-tools project ===

<ol start="1"><li>Under your $HOME directory, clone the <stx-tools> project

<source lang="sh">$ cd $HOME
$ git clone https://git.starlingx.io/stx-tools
</source></li></ol>

=== Create a Workspace Directory ===

<ol start="1"><li>Create a ''starlingx'' workspace directory on your workstation computer. Usually, you’ll want to create it somewhere under your user’s home directory.

<source lang="sh">$ mkdir -p $HOME/starlingx/
</source></li></ol>

== Build the CentOS Mirror Repository ==

This section describes how to build the CentOS Mirror Repository.

=== Setup Repository Docker Container ===

Run the following commands under a terminal identified as "one". 

<ol start="1"><li>Navigate to the ''<$HOME/stx-tools>/centos-mirror-tool'' project directory:

<source lang="sh">$ cd $HOME/stx-tools/centos-mirror-tools/
</source></li>

<li> Temporal! Only Branch Master Check if the following Gerrit Reviews are merged, if not, cherry pick them 
https://review.openstack.org/#/c/585915 
</li>

<li> Temporal! Only Branch m/2018.07 Check if the following Gerrit Reviews are merged, if not, cherry pick them 
https://review.openstack.org/#/c/585923/ 
</li>

<li>If necessary you might have to set http/https proxy in your Dockerfile before building the docker image.

<source lang="sh">ENV http_proxy "http://your.actual_http_proxy.com:your_port" && \
https_proxy "https://your.actual_https_proxy.com:your_port" && \
ftp_proxy "http://your.actual_ftp_proxy.com:your_port"
RUN echo "proxy=http://your-proxy.com:port" >> /etc/yum.conf
</source></li>
<li>Build your ''<user>:<tag>'' base container image with '''e.g.''' ''user:centos-mirror-repository''

<source lang="sh">$ docker build -t user:centos-mirror-repository -f Dockerfile .
</source></li>
<li>Launch a ''<user>'' docker container using previously created Docker base container image ''<user>:<tag>'' '''e.g.''' ''user-centos-mirror-repository''. As /localdisk is defined as the workdir of the container, the same folder name should be used to define the volume. The container will start to run and populate a logs and output folders in this directory. The container shall be run from the same directory where the other scripts are stored.

<source lang="sh">$ docker run -it --name user-centos-mirror-repository -v $(pwd):/localdisk user:centos-mirror-repository
</source></li></ol>

=== Download Packages ===

<ol start="1"><li>Enter the following command to download the required packages to populate the CentOS Mirror Repository:

<source lang="none"># bash download_mirror.sh
</source></li>
<li>Monitor the download of packages until it is complete. When download is complete, the following message is displayed:

<source lang="none">totally 17 files are downloaded!
step #3: done successfully
IMPORTANT: The following 3 files are just bootstrap versions. Based on them, the workable images
for StarlingX could be generated by running "update-pxe-network-installer" command after "build-iso"
- out/stx-r1/CentOS/pike/Binary/LiveOS/squashfs.img
- out/stx-r1/CentOS/pike/Binary/images/pxeboot/initrd.img
- out/stx-r1/CentOS/pike/Binary/images/pxeboot/vmlinuz
</source></li></ol>

=== Verify Packages ===

<ol start="1"><li>Verify there are no missing or failed packages:

<source lang="none"># cat output/3rd-centos_rpms_missing_L1.txt output/3rd_rpms_missing_L1.txt output/3rd_srpms_missing_L1.txt output/centos_rpms_missing_L1.txt output/centos_srpms_missing_L1.txt
# cat output/3rd_rpms_fail_move_L1.txt output/3rd_srpms_fail_move_L1.txt output/centos_rpms_fail_move_L1.txt output/centos_srpms_fail_move_L1.txt
</source></li>
<li>In case there are missing or failed ones due to network instability (or timeout), you should download them manually, to assure you get all RPMs listed in "rpms_from_3rd_parties.lst" and "rpms_from_centos_repo.lst".</li></ol>

=== Create CentOS Mirror Repository ===

Run the following commands under a terminal identified as "two".

<ol start="1"><li>From terminal "two", create a ''mirror/CentOS'' directory under your ''starlingx'' workspace directory:

<source lang="sh">$ mkdir -p $HOME/starlingx/mirror/CentOS/
</source></li>
<li>Copy the built CentOS Mirror Repository built under ''<stx-tools>/centos-mirror-tool'' to the ''$HOME/starlingx/mirror/CentOS'' workspace directory.

<source lang="sh">$ cp -r $HOME/stx-tools/centos-mirror-tools/output/stx-r1/ $HOME/starlingx/mirror/CentOS/
</source></li></ol>

==Create StarlingX Packages==
===Setup Building Docker Container===

<ol start="1"><li>From terminal "two", Workspace Setup

<source lang="sh">$ mkdir -p $HOME/starlingx/workspace
</source></li>

<li>Navigate to the ''<$HOME/stx-tools>'' project directory:

<source lang="sh">$ cd $HOME/stx-tools
</source></li>

<li>Copy your git options

<source lang="sh">$ cp ~/.gitconfig toCOPY
</source></li>

<li>Create a ''<localrc>'' file

<source lang="sh">$ nano localrc
</source></li>

<source lang="sh">
# tbuilder localrc
MYUNAME=user
PROJECT=starlingx
HOST_PREFIX=$HOME/starlingx/workspace
HOST_MIRROR_DIR=$HOME/starlingx/mirror
</source></li>

<li>If necessary you might have to set http/https proxy in your Dockerfile.centos73 before building the docker image.

<source lang="sh">ENV http_proxy "http://your.actual_http_proxy.com:your_port" && \
https_proxy "https://your.actual_https_proxy.com:your_port" && \
ftp_proxy "http://your.actual_ftp_proxy.com:your_port"
RUN echo "proxy=http://your-proxy.com:port" >> /etc/yum.conf
</source></li>

<li>Base container setup
If you are running in fedora system, you will see " .makeenv:88: *** missing separator. Stop. " error, to continue :

* delete the functions define in the .makeenv ( module () { ... } )
* delete the line 19 in the Makefile and ( NULL := $(shell bash -c "source buildrc ... ).

<source lang="sh">$ make base-build
</source></li>

<li>Build container setup

<source lang="sh">
$ make build
</source></li>

<li>Verify environment variables

<source lang="sh">$ bash tb.sh env
</source></li>

<li>Build container run

<source lang="sh">$ bash tb.sh run
</source></li>

<li>Execute the built container:

<source lang="sh">$ bash tb.sh exec
</source></li></ol>

===Download Source Code Repositories===

<ol start="1"><li>Internal environment

<source lang="sh">$ eval $(ssh-agent)
$ ssh-add
</source></li>

<li>Repo init

<source lang="sh">$ cd $MY_REPO_ROOT_DIR
$ repo init -u https://git.starlingx.io/stx-manifest.git -m default.xml
</source></li>

<li>Repo sync

<source lang="sh">$ repo sync
</source></li>

<li> cgcs-dl

<source lang="sh">$ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/stx/
</source></li>

Outside the container, use another terminal

<li>Mirror Binaries

<source lang="sh">$ mkdir -p $HOME/starlingx/mirror/CentOS/tis-installer
$ cp $HOME/starlingx/mirror/CentOS/stx-r1/CentOS/pike/Binary/images/pxeboot/initrd.img $HOME/starlingx/mirror/CentOS/tis-installer/initrd.img-stx-0.2
$ cp $HOME/starlingx/mirror/CentOS/stx-r1/CentOS/pike/Binary/images/pxeboot/vmlinuz $HOME/starlingx/mirror/CentOS/tis-installer/vmlinuz-stx-0.2
$ cp $HOME/starlingx/mirror/CentOS/stx-r1/CentOS/pike/Binary/LiveOS/squashfs.img $HOME/starlingx/mirror/CentOS/tis-installer/squashfs.img-stx-0.2
</source></li></ol>

===Build Packages===

<ol start="1"><li>Temporal! Build-Pkgs Errors
Be prepared to have some missing / corrupted rpm and tarball packages generated during [[StarlingX/Developer_Guide#Build_the_CentOS_Mirror_Repository]] which will make the next step to fail, if that happens please download manually those missing / corrupted packages. 
</li>

<li>Update the symbolic links
<source lang="sh">$ generate-cgcs-centos-repo.sh /import/mirrors/CentOS/stx-r1/CentOS/pike/
</source></li>

<li>Build-Pkgs --Serial

<source lang="sh">$ cd $MY_WORKSPACE
$ build-pkgs --serial
</source></li>

<li> Generate-Cgcs-Tis-Repo

The cgcs-tis-repo has the dependency information that sequences the build order; To generate or update the information the following command needs to be executed after building modified or new packages.
<source lang="sh">$ generate-cgcs-tis-repo
</source></li>

<li>Build-Srpms

<source lang="sh">$ build-srpms --installer
</source></li>

<li>Build-Rpms

<source lang="sh">$ build-rpms --installer
</source></li></ol>

==Build StarlingX ISO==

<ol start="1"><li>Build-Iso

<source lang="sh">$ build-iso
</source></li></ol>

StarlingX

2018-07-26T13:11:55Z

Dtroyer:

__NOTOC__
<center>

== Welcome to the StarlingX Project ==
</center>
StarlingX is a fully featured and high performance Edge Cloud software stack that is based on the [https://www.windriver.com/products/titanium-cloud/ Wind River® Titanium Cloud] R5 product. Intel and Wind River have jointly open sourced this software and we invite you to download, build, install, and run it.

Wind River Titanium Cloud was originally built on open source components, that were then extended and hardened to meet critical infrastructure requirements, including: high availability, fault management, and performance management. This software provides numerous features and capabilities to enable 24/7 operation of mission critical applications.

The StarlingX project opens all of these enhancements to the open source community. Please join us as we build the infrastructure stack for Edge Computing.
----

{| style="border-collapse: separate; border-spacing: 25px;"
|style="vertical-align:top; width:50%;" |

== Documentation ==

These three documents will help get you started building, installing, and validating your installation of StarlingX:
* [[StarlingX/Developer Guide|Developer Guide]]
* [[StarlingX/Installation Guide|Installation Guide]]
* [[StarlingX/Validation Guide|Validation Guide]]

== Code ==
The StarlingX project uses Gerrit as its web-based code change management and review tool.
* [https://git.starlingx.io/cgit Gerrit repositories] maintain the StarlingX code, build instructions are in the [[StarlingX/Developer Guide]]
* [https://review.openstack.org/#/admin/projects/?filter=stx StarlingX Gerrit Projects] and [https://review.openstack.org/#/q/status:open+AND+project:%255Eopenstack/stx-%2540 Open StarlingX project reviews]
* [https://review.openstack.org/#/dashboard/?foreach=(project:openstack/stx-clients%20OR%20project:openstack/stx-config%20OR%20project:openstack/stx-fault%20OR%20project:openstack/stx-gplv2%20OR%20project:openstack/stx-gplv3%20OR%20project:openstack/stx-gui%20OR%20project:openstack/stx-ha%20OR%20project:openstack/stx-integ%20OR%20project:openstack/stx-manifest%20OR%20project:openstack/stx-metal%20OR%20project:openstack/stx-nfv%20OR%20project:openstack/stx-root%20OR%20project:openstack/stx-tis-repo%20OR%20project:openstack/stx-tools%20OR%20project:openstack/stx-update%20OR%20project:openstack/stx-upstream%20OR%20project:openstack/stx-utils)%20status:open%20NOT%20owner:self%20NOT%20label:Workflow%3C=-1%20label:Verified%3E=1,zuul%20NOT%20reviewedby:self&title=StarlingX%20Review%20Inbox&Needs%20final%20%202=label:Code-Review%3E=2%20limit:50%20NOT%20label:Code-Review%3C=-1,self&Passed%20Zuul,%20No%20Negative%20Feedback%20(Small%20Fixes)=NOT%20label:Code-Review%3E=2%20NOT%20label:Code-Review%3C=-1,starlingx-core%20delta:%3C=10&Passed%20Zuul,%20No%20Negative%20Feedback=NOT%20label:Code-Review%3E=2%20NOT%20label:Code-Review%3C=-1,starlingx-core%20delta:%3E10&Needs%20Feedback%20(Changes%20older%20than%205%20days%20that%20have%20not%20been%20reviewed%20by%20anyone)=NOT%20label:Code-Review%3C=-1%20NOT%20label:Code-Review%3E=1%20age:5d&You%20are%20a%20reviewer,%20but%20haven't%20voted%20in%20the%20current%20revision=NOT%20label:Code-Review%3C=-1,self%20NOT%20label:Code-Review%3E=1,self%20reviewer:self&Wayward%20Changes%20(Changes%20with%20no%20code%20review%20in%20the%20last%202days)=NOT%20is:reviewed%20age:2d StarlingX Gerrit Review Dashboard]

== Story and Bug Tracking ==
We are using the OpenStack Storyboard tool for tracking all development activities. Each new Story shall be marked with one or more Tags, and can optionally include one or more Prefixes in the description. See [[StarlingX/Tags and Prefixes|Tags and Prefixes]] for a description of how we use them.

'''IMPORTANT:''' If you create a new Story (of any kind), please mark it with the tag "stx.new" so we can find it, review it and assign it to the right team and a release.

The StarlingX Storyboard project group is [https://storyboard.openstack.org/#!/project_group/86 here].

Sample queries:
* To find the newly created stories use: [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.new this query]
* To find all of the active bugs use: [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.bug this query]
* To find all of the active bugs assigned to the stx.2018.08 release use [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.bug&tags=stx.2018.08 this query]
* To find all of the active bugs assigned to the stx.2018.11 release use [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.bug&tags=stx.2018.11 this query]

Queries for the Sub-projects will be defined on each Sub-project's page

You can also use Prefixes to search for Stories but we consider Prefixes optional so these searches might not show the same results as searching for Tags.
* Sample Prefix queries:
** To find all Stories with the [Features] prefix use: [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Feature this query]
** To find all Stories with the [Bug] prefix use: [https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Bug this query]

== References ==

* [https://etherpad.openstack.org/p/stx-notes The list of repos] and other things

== OpenStack Documentation ==

These are references to general OpenStack material:

* [https://docs.openstack.org/infra/manual/developers.html Developer's Guide]
* [https://docs.openstack.org/infra/manual/creators.html Project Creator's Guide]
* [https://wiki.openstack.org/wiki/How_To_Contribute The Contributors Guide] (the older wiki page)
* [https://governance.openstack.org/tc/reference/project-testing-interface.html Project Testing Interface]

|style="vertical-align:top; width:50%;" |

== Culture ==

We are proud to be an OpenStack Foundation project!
* We support and adhere to the [https://www.openstack.org/legal/community-code-of-conduct/ OpenStack community Code of Conduct]
* We support and fully embrace the [https://governance.openstack.org/tc/reference/opens.html Four Opens]
* [[StarlingX/Contribution Guidelines|Contribution Guidelines]]
* The mailing lists are now live at http://lists.starlingx.io/. There are two lists, starlingx-announce and starlingx-discuss. Please subscribe.
* We have the #starlingX IRC channel set up on freenode. Refer to https://docs.openstack.org/infra/manual/developers.html regarding how to have your IRC account setup.

== Meetings ==

=== Weekly calls ===

* We host a weekly call for the project every Wednesday at 7am PDT / 1400 UTC. All are welcome.
* We also host a Core team call every Thursday at 7AM PDT / 1400 UTC. This is for the Core team but other project participants are welcome to join.

==== Call details ====

* ''' Zoom link: https://zoom.us/j/342730236 '''
* ''' Dialing in from phone: '''
** Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923
** Meeting ID: 342 730 236
** International numbers available: https://zoom.us/u/ed95sU7aQ

==== Agenda and meeting minutes ====

The agenda and notes for each call are kept in Etherpads:
* [https://etherpad.openstack.org/p/stx-status Weekly Agenda and Notes]
* [https://etherpad.openstack.org/p/stx-cores Weekly Core team Agenda and Notes]

Please feel free to add items to the agendas for these meetings.

=== PTG Meetings ===

We are preparing for the Denver OpenStack PTG meeting. Draft agenda items can be found here:
* [https://etherpad.openstack.org/p/stx-PTG-agenda StarlingX Denver PTG Agenda]
== Status and Planning ==
This section is under construction.
=== Overall project planning pages ===
* [[StarlingX/Project Priorities|Project Priorities]]
* [[StarlingX/Release Plan|Release Plan]]
* [https://etherpad.openstack.org/p/stx-planning StarlingX Planning Etherpad] (contains sub-projects and Worklists)
* [[StarlingX/Project Plans|Project Plans]]

=== Sub-projects ===
To keep things manageable, we are splitting the overall project into sub-projects. The list of sub-projects is below with links to their sub-project home pages.

* [[StarlingX/Docs_and_Infra|Documentation and Infrastructure]]
* [[StarlingX/Build|Build improvements]]
* [[StarlingX/Releases|Releases]]
* [[StarlingX/Distro|Distro support]]
** TBD: Should updating to CentOS 7.5 and updating qemy/libvirt be tracked in the Distro project or in their own projects?
* New Features (Including networking) Task & Story list is at https://ethercalc.openstack.org/sedtamo5yauh
* Upstream patch submission for other (non-Openstack) projects (ToDo: split up into sub-sub projects) https://storyboard.openstack.org/#!/worklist/358
* Validation - high level tasks https://ethercalc.openstack.org/50vke3z9qta3
* [[StarlingX/Security|Security]]
* Container support includinng OVS DPDK integration - TBD
* [[StarlingX/Pyton2|Python2 transition]]
* Zuul enablement and coverage
* Devstack integration

== Upstream Status ==

The StarlingX code base contains a number of out-of-tree patches against other open source components. One of our highest priorities is to contribute those changes to their upstream communities.

TODO: Add a link to our Dashboard showing the status of upstream submissions
|}

StarlingX/Release Plan

2018-07-20T18:48:14Z

Dtroyer:

<big><big> '''Releases''' </big></big>

StarlingX is released periodically (currently every three months) with monthly milestone releases in between. A release consists of a branch in the source code repositories that enables repeatable builds over time.
----
== List of releases ==
'''Current'''
{| class="wikitable"
|-
! Version !! Docs !! Release Date !! End of Life Date
|-
| 2018.07.0 || Release Notes link || 2018/07/20 || TBD + 6 months
|-
| ... || || ||
|}
'''Future'''
{| class="wikitable"
|-
! Version !! Docs !! Release Date !! End of Life Date
|-
| ... || || ||
|}

== Release Definition ==

A StarlingX milestone/release is a tagged branch in the source code repositories that:
* is considered stable and can be used for repeatable builds
* will have no additional features added
* will backport bug fixes for critical issues only
* will be maintained in the canonical repositories for a specified minimum period
* The list of repos included is maintained in stx-manifest/default.xml (or similar) for any given release. (Note: this file included non-StarlingX-managed repos, only repos from the "starlingx" and "stx-staging" remotes are included.)
* The actual release is a tag on the corresponding branch, ie m/2018.07 milestone branch will be initially tagged as 2018.07.0

== Management of Releases ==

=== Release Cadence and Schedule ===

'''Releases are published in a time based fashion:'''
* Every Long Term period with quarterly updates.
* Every Quarterly with monthly updates.

==== Monthly Milestone ====

* Each month in the 2nd week of the month a branch will be pulled.
* Branch name format m/YYYY.MM[.n]
** 'm/' is the branch name prefix (milestone)
** .n is a sequence number appended if more than one branch is created in a given month
m/2018.07
* Release is tagged as YYYY.MM.0

==== Quarterly Release ====

* 2nd month in the quarter.
* For each quarterly release, the code freeze for that release is the 2nd week in the 2nd month in the quarter.
* Branch name format r/YYYY.MM[.n]
** 'r/' is the branch name prefix (release)
** .n is a sequence number appended if more than one branch is created in a given month
r/2018.07
* Release is tagged as YYYY.MM.0

==== Long Term Release ====

* '''TBD'''

=== Support length ===
* Quarterly releases are supported for 6 months.
* Long Term releases are out of plan so far.

== Release team ==

* Intel CI/CD Lead - hazzim.i.anaya.casas@intel.com
* Intel Developer - mario.alfredo.c.arevalo@intel.com

[[File:Stx Release Plan.png||]]

StarlingX/Release Process

2018-07-20T16:00:26Z

Dtroyer: Created page with "Describe the steps in creating a StarlingX Release = Release Activity = == Milestone == * Finalize any outstanding changes to master stx-manifest/default.xml, particularly..."

StarlingX/Release Plan

2018-07-19T20:32:36Z

Dtroyer:

<big><big> '''Releases''' </big></big>

StarlingX is released periodically (currently every three months) with monthly milestone releases in between. A release consists of a branch in the source code repositories that enables repeatable builds over time.
----
== List of releases ==
'''Current'''
{| class="wikitable"
|-
! Version !! Docs !! Release Date !! End of Life Date
|-
| 2018.07.0 || Release Notes link || TBD || TBD + 6 months
|-
| ... || || ||
|}
'''Future'''
{| class="wikitable"
|-
! Version !! Docs !! Release Date !! End of Life Date
|-
| ... || || ||
|}

== Release Definition ==

A StarlingX milestone/release is a tagged branch in the source code repositories that:
* is considered stable and can be used for repeatable builds
* will have no additional features added
* will backport bug fixes for critical issues only
* will be maintained in the canonical repositories for a specified minimum period
* The list of repos included is maintained in stx-manifest/default.xml (or similar) for any given release. (Note: this file included non-StarlingX-managed repos, only repos from the "starlingx" and "stx-staging" remotes are included.)
* The actual release is a tag on the corresponding branch, ie m/2018.07 milestone branch will be initially tagged as 2018.07.0

== Management of Releases ==

=== Release Cadence and Schedule ===

'''Releases are published in a time based fashion:'''
* Every Long Term period with quarterly updates.
* Every Quarterly with monthly updates.

==== Monthly Milestone ====

* Each month in the 2nd week of the month a branch will be pulled.
* Branch name format m/YYYY.MM[.n]
** 'm/' is the branch name prefix (milestone)
** .n is a sequence number appended if more than one branch is created in a given month
m/2018.07
* Release is tagged as YYYY.MM.0

==== Quarterly Release ====

* 2nd month in the quarter.
* For each quarterly release, the code freeze for that release is the 2nd week in the 2nd month in the quarter.
* Branch name format r/YYYY.MM[.n]
** 'r/' is the branch name prefix (release)
** .n is a sequence number appended if more than one branch is created in a given month
m/2018.07
* Release is tagged as YYYY.MM.0

==== Long Term Release ====

* '''TBD'''

=== Support length ===
* Quarterly releases are supported for 6 months.
* Long Term releases are out of plan so far.

== Release team ==

* Intel CI/CD Lead - hazzim.i.anaya.casas@intel.com
* Intel Developer - mario.alfredo.c.arevalo@intel.com

[[File:Stx Release Plan.png||]]

StarlingX/Release Plan

2018-07-18T20:29:31Z

Dtroyer:

<big><big> '''Releases''' </big></big>

StarlingX is released periodically (currently every three months) with monthly milestone releases in between. A release consists of a branch in the source code repositories that enables repeatable builds over time.
----
== List of releases ==
'''Current'''
{| class="wikitable"
|-
! Version !! Docs !! Release Date !! End of Life Date
|-
| Stx.08.2018.0x (Quarterly) || Release Notes link || TBD || TBD + 6 months
|-
| ... || || ||
|}
'''Future'''
{| class="wikitable"
|-
! Version !! Docs !! Release Date !! End of Life Date
|-
| ... || || ||
|}

== Release Definition ==

A StarlingX milestone/release is a branch in the source code repositories that:
* is considered stable and can be used for repeatable builds
* will have no additional features added
* will backport bug fixes for critical issues only
* will be maintained in the canonical repositories for a specified minimum period
* The list of repos included is maintained in stx-manifest/default.xml (or similar) for any given release. (Note: this file included non-StarlingX-managed repos, only repos from the "starlingx" and "stx-staging" remotes are included.)

== Management of Releases ==

=== Release Cadence and Schedule ===

'''Releases are published in a time based fashion:'''
* Every Long Term period with quarterly updates.
* Every Quarterly with monthly updates.

'''Monthly Milestone Release'''
* Each month in the 2nd week of the month a branch will be pulled.
* Branch name format stx-YYYY.MM.nn
e.g. stx-2018.08.nn (where “nn” is a sequence number)

'''Quarterly Release'''
* 2nd month in the quarter.
* For each quarterly release, the code freeze for that release is the 2nd week in the 2nd month in the quarter.

'''Long Term release'''
* '''TBD'''

=== Support length ===
* Quarterly releases are supported for 6 months.
* Long Term releases are out of plan so far.

=== Release team ===
* Intel CI/CD Lead - hazzim.i.anaya.casas@intel.com
* Intel Developer - mario.alfredo.c.arevalo@intel.com

[[File:Stx Release Plan.png||]]

OpenStack health tracker

2018-06-28T18:13:14Z

Dtroyer: fixed spaces in OpenStackClient

TC members are attached as liaisons to each of the project teams, [https://governance.openstack.org/sigs/ SIGs], or [https://governance.openstack.org/uc/ UC working groups]. The idea is for these liaisons to keep up with the general health of the group, understand any issues they encounter, and help them work with the TC on solutions if necessary. Some TC members may be more active within the group than the basic liaison responsibilities imply, but that is not required.

Liaisons should monitor their groups by:
* reading meeting logs or participating in meetings
* watching summit "project update" videos
* reading relevant messages on the mailing list
* talking with the PTL, chair, and other group members
* checking contribution rates and review turnaround times

== Liaisons ==
=== SIGs ===

{| class="wikitable"
|-
! Group !! TC members
|-
| API
|| mugsie
|-
| First Contact
|| fungi
|-
| K8s
|| dims
|-
| Meta
|| dhellmann
|-
| Resource Management
|| cdent
|-
| Scientific
|| pabelanger
|-
| Security
|| fungi
|-
| Self-healing
|| zaneb
|-
| Upgrade
|| emilien
|}

=== Working Groups ===

{| class="wikitable"
|-
! Group !! TC members
|-
| App Dev Enablement
|| zaneb
|-
| [[Diversity]]
|| fungi
|-
| Enterprise
||
|-
| Fault Genes
||
|-
| [[InteropWG|Interop]]
|| dims, fungi
|-
| LCOO
||
|-
| Large Deployment
|| pabelanger
|-
| Edge/Massively Distributed Clouds
|| ttx
|-
| Operators Telecom/NFV
|| smcginnis
|-
| Ops Tags
|| smcginnis
|-
| Product
||
|-
| [[ProfessionalCertification]]
||
|-
| Public Cloud
|| ttx
|}

=== Project Teams ===

{| class="wikitable"
|-
! Group !! TC members
|-
| Barbican
|| fungi, ttx
|-
| Blazar
|| cmurphy, mnaser
|-
| Chef Openstack
|| pabelanger, mnaser
|-
| Cinder
|| smcginnis, dims
|-
| Cloudkitty
|| ttx, dims
|-
| Congress
|| cdent, fungi
|-
| Cyborg
|| ttx, TheJulia
|-
| Designate
|| cmurphy, cdent
|-
| Documentation
|| dhellmann, pabelanger
|-
| Dragonflow
|| dims, cdent
|-
| Ec2-Api
|| TheJulia, cmurphy
|-
| Freezer
|| ttx, mugsie
|-
| Glance
|| smcginnis, mugsie
|-
| Heat
|| zaneb, emilien
|-
| Horizon
|| cmurphy, smcginnis
|-
| I18n
|| emilien, cdent
|-
| Infrastructure
|| fungi, mnaser
|-
| Ironic
|| mugsie, fungi
|-
| Karbor
|| ttx, mugsie
|-
| Keystone
|| fungi,cmurphy
|-
| Kolla
|| dims, TheJulia
|-
| Kuryr
|| dims, cdent
|-
| Loci
|| pabelanger, dims
|-
| Magnum
|| mnaser, dims
|-
| Manila
|| smcginnis, pabelanger
|-
| Masakari
|| pabelanger, cdent
|-
| Mistral
|| zaneb, cmurphy
|-
| Monasca
|| zaneb, TheJulia
|-
| Murano
|| dhellmann, emilien
|-
| Neutron
|| mugsie, dims
|-
| Nova
|| mnaser, dhellmann
|-
| Octavia
|| mnaser, mugsie
|-
| Openstack Charms
|| ttx, emilien
|-
| Openstack-Helm
|| ttx, dims
|-
| Openstackansible
|| mnaser, smcginnis
|-
| OpenStackClient
|| dhellmann, cmurphy
|-
| Openstacksdk
|| pabelanger, TheJulia
|-
| Oslo
|| dhellmann, mugsie
|-
| Packaging-Rpm
|| cmurphy, zaneb
|-
| Powervmstackers
|| emilien, TheJulia
|-
| Puppet Openstack
|| cmurphy, pabelanger
|-
| Qinling
|| zaneb, TheJulia
|-
| Quality Assurance
|| cdent, fungi
|-
| Rally
|| pabelanger, mnaser
|-
| Refstack
|| fungi, TheJulia
|-
| Release Management
|| dhellmann, smcginnis
|-
| Requirements
|| fungi, dhellmann
|-
| Sahara
|| emilien, pabelanger
|-
| Searchlight
|| mugsie, mnaser
|-
| Security
|| fungi, zaneb
|-
| Senlin
|| zaneb, smcginnis
|-
| Solum
|| zaneb, mnaser
|-
| Stable Branch Maintenance
|| fungi, smcginnis
|-
| Storlets
|| ttx, dhellmann
|-
| Swift
|| smcginnis, mugsie
|-
| Tacker
|| TheJulia, emilien
|-
| Telemetry
|| cdent, dhellmann
|-
| Tricircle
|| emilien, cdent
|-
| Tripleo
|| emilien, cmurphy
|-
| Trove
|| ttx, mugsie
|-
| Vitrage
|| emilien, dhellmann
|-
| Watcher
|| smcginnis, TheJulia
|-
| Winstackers
|| pabelanger, cdent
|-
| Zaqar
|| zaneb, dims
|-
| Zun
|| zaneb, ttx
|}

== Status updates ==

=== Cinder ===
[[File:green.png]] Update: June 22, 2018, smcginnis

* Some drop off in participation by some cores, but still active enough not to raise any red flags
* Overall less community involvement
* Project may just be "stable" and doesn't need as much activity as the past
* Still a lot of bug fix work to be done, but no major new features on the roadmap

=== Freezer ===
Reported issues
* Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]
* freezer and freezer-web-ui missed the Rocky-2 milestone

=== I18n ===
Update: June 13, emilien

Reported issues: none, yet.
The team changed leadership in Queens.

Queens status:
* 87 modules touched (+87%)
* 17 languages supported (+6%)
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)
* 7 companies support (-22%)
I18n team previously had team meetings but decided to have office hours instead.
Usually tracks completion of Rocky community goals.
A lot of collaboration with Doc team.
Dedicated mailing-list: openstack-i18n - pretty busy

Rocky:
* Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.

=== Manila ===
[[File:green.png]] Update: June 22, 2018, smcginnis

* Project appears to be in good shape
* Focusing on bug fixes and stabilization rather than any big new features
* Drop of in involvement from EU, particularly from HPE and IBM
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage
** Not a lot of involvement on IRC or weekly meeting though
* Lots of good interest downstream, particularly from HPC and telco communities

=== Masakari ===
Reported issues
* Low activity in Rocky for a "new" project

=== Murano ===
* murano and murano-dashboard missed the Rocky-2 milestone

Update 13 June 2018, dhellmann

* Recent US government action against ZTE has had an impact on the team, because ZTE employees are key contributors to the project and the core team. It is unclear how much ZTE will be able to continue to contribute in the future. [https://www.nbcnews.com/politics/congress/senate-blocks-zte-deal-rebuke-trump-deal-n882196]
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.

=== Openstack Charms ===
[[File:green.png]] Update: June 20, ttx

* Currently single-vendor (all cores from Canonical), but with some external participation
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)
* Holds weekly IRC meetings with rotating chair
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])

=== OpenStackClient ===
[[File:orange.png]] Update: 28 June 2018, dhellmann, cmurphy

* uses IRC and the mailing list but no meetings
* the review team is small, but there are several active reviewers not on the core team yet who are candidates
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)

=== OpenStack-Helm ===
[[File:green.png]] Update: June 26, ttx

* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)
* Holds weekly IRC meetings, pretty active discussions
* Migrated to StoryBoard
* Limited ML engagement (mostly used for team-wide announcements)
* OpenStack-Helm is release-independent -- it aims to support Newton -> master and track latest all the time. They are waiting until they reach a certain quality level (and stable interface) before declaring a 1.0. See [https://docs.openstack.org/openstack-helm/latest/specs/osh-1.0-requirements.html requirements for 1.0]. This explains lack of releases.

=== Oslo ===
[[File:orange.png]] Reported issues

* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.
* oslo.service has some issues with the WSGI service not working under python3. The plan is to encourage all projects to stop using that feature, deprecate, then remove it.
* taskflow is one of several projects that needs to update to a newer version of networkx, but the API changes in networkx mean reworking some of taskflow. Supporting both versions of the APIs may be complicated.

Update: 12 June 2018, dhellmann

* The team is small, but active and working on recruiting.
* Team produces regular and frequent releases for the maintained libraries
* Team meets weekly using IRC
* Team had both onboarding and project update sessions in Vancouver
* The level of activity within each library varies.
* Several of the libraries are reaching a "stable" state in which they may not see many updates beyond bug fixes. This has spurred a discussion of how to treat projects like that, led by the release management team [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131341.html]

=== Rally ===
Reported issues
* Half on GitHub those days, and unwilling to drop direct branching ACLs

=== Release Management ===
[[File:green.png]]

Update: 28 June 2018, dhellmann & smcginnis

* The review work has become easier, but there are still only 3 team members. That leaves succession planning for the PTL role a bit up in the air, and also poses challenges with the members travel to conferences all at the same time.
* Working on a reviewers' guide to help with recruiting.
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.

=== Requirements Management ===
[[File:orange.png]]

* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver

Update: 14 June 2018, dhellmann

* team has recently lost several members
* most work is really down to 3 people (Matt, Dirk, Tony)
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable
* the changes this cycle to stop syncing requirements should lower the review burden somewhat, but the move to python 3 is going to take some work
* meets regularly
* accomplishments this cycle
** stopped syncing dependencies between projects
** working on networkx upgrade
** uncapped eventlet
** uncapped sphinx
** added optional lower-constraints test jobs for project teams that want them

=== Sahara ===
Update: June 13, emilien

Reported issues: none, yet.
* The team changed leadership in Queens
* Last PTG was virtual
* Most commits in Rocky are from Red Hat
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews
* Latest survey shows that Sahara is used in production by 3% of deployments and 8% in test phase. 25% of users are interested by Sahara
* Following goals and releases
* Email sent to PTL on June 13th

=== Searchlight ===
Reported issues
* searchlight and searchlight-ui missed the Rocky-1 milestone
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone

=== Telemetry ===
[[File:orange.png]] Update: June 21, cdent, WIP
* Only two active cores and contributors, despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].
* more to come

=== Tricircle ===
Reported issues
* Not set up for zuulv3 so cannot land patches that interact with other repositories? http://lists.openstack.org/pipermail/openstack-dev/2018-June/131643.html

=== TripleO ===
Update: June 13, emilien

* Mainly Red Hat. Some contributors from vendors (storage/network plugins)
* Number of contributors / core reviewers always increasing
* Quite healthy, no problem reported so far

=== Trove ===
[[File:orange.png]] Update: June 12, ttx

* The team changed leadership in Rocky
* The new team is small, but pretty alive and active. Needs more contributors to be stable.
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens
* Organizational diversity: 53% of commits are from AWCloud. Reviews are shared between 23% China Telecom, 19% China Mobile, 19% Awcloud. Last cycle with 41% IBM.
* Regular weekly meetings, well run with clear documentation of outcomes
* Tracks completion of Rocky community goals
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)
* Missed Rocky-2 milestone, but mostly due to a [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-06-06-14.00.log.html#l-95 misunderstanding of release policy].
* No project update in Vancouver, but was discussed in meeting: sadly [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-05-16-14.00.log.html#l-20 no team member was present].
* Reached out to PTL by email on June 12 for additional concerns / questions.

=== Upgrade SIG ===
WIP (emilien)

=== Zaqar ===
Reported issues
* zaqar and zaqar-ui missed the Rocky-2 milestone

StarlingX

2018-06-18T18:13:14Z

Dtroyer: New page

== Documentation ==

== Code ==

* [https://git.openstack.org/cgit/openstack/stx Gerrit repositories]
** Instructions for how to download and build the code are in progress
* [https://review.openstack.org/ Gerrit Web UI]
* [https://review.openstack.org/#/admin/projects/?filter=stx StarlingX Gerrit Projects]]
** Hint for fast review of open reviews related to STX, in search box use the regular expression "status:open AND project:^openstack/stx-@"
* [https://review.openstack.org/#/dashboard/?foreach=%28project%3Aopenstack%2Fstx%2Dclients+OR+project%3Aopenstack%2Fstx%2Dconfig+OR+project%3Aopenstack%2Fstx%2Dfault+OR+project%3Aopenstack%2Fstx%2Dgplv2+OR+project%3Aopenstack%2Fstx%2Dgplv3+OR+project%3Aopenstack%2Fstx%2Dgui+OR+project%3Aopenstack%2Fstx%2Dha+OR+project%3Aopenstack%2Fstx%2Dinteg+OR+project%3Aopenstack%2Fstx%2Dmanifest+OR+project%3Aopenstack%2Fstx%2Dmetal+OR+project%3Aopenstack%2Fstx%2Dnfv+OR+project%3Aopenstack%2Fstx%2Droot+OR+project%3Aopenstack%2Fstx%2Dtis%2Drepo+OR+project%3Aopenstack%2Fstx%2Dtools+OR+project%3Aopenstack%2Fstx%2Dupdate+OR+project%3Aopenstack%2Fstx%2Dupstream+OR+project%3Aopenstack%2Fstx%2Dutils%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D%2D1+label%3AVerified%3E%3D1%2Czuul+NOT+reviewedby%3Aself&title=StarlingX+Review+Inbox&Needs+final+%2B2=label%3ACode%2DReview%3E%3D2+limit%3A50+NOT+label%3ACode%2DReview%3C%3D%2D1%2Cself&Passed+Zuul%2C+No+Negative+Feedback+%28Small+Fixes%29=NOT+label%3ACode%2DReview%3E%3D2+NOT+label%3ACode%2DReview%3C%3D%2D1%2Cstarlingx%2Dcore+delta%3A%3C%3D10&Passed+Zuul%2C+No+Negative+Feedback=NOT+label%3ACode%2DReview%3E%3D2+NOT+label%3ACode%2DReview%3C%3D%2D1%2Cstarlingx%2Dcore+delta%3A%3E10&Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode%2DReview%3C%3D%2D1+NOT+label%3ACode%2DReview%3E%3D1+age%3A5d&You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=NOT+label%3ACode%2DReview%3C%3D%2D1%2Cself+NOT+label%3ACode%2DReview%3E%3D1%2Cself+reviewer%3Aself&Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+is%3Areviewed+age%3A2d StarlingX Gerrit Review Dashboard]
** Also in [http://paste.openstack.org/show/723397/ StarlingX Gerrit Review Dashboard] (copy the URL from there into a browser bookmark)

== Bugs ==

* [https://storyboard.openstack.org/#!/worklist/354 StarlingX Bug List]
** This list is sorted manually by drag and drop.
** Please create bugs for any issues found in Storyboard, against one of the stx-* projects. If you can't find the right project, use stx-integ
** After you create the bug, please add it to the Bug Worklist (link above)

== Status and Planning ==

* [https://etherpad.openstack.org/p/stx-status Status Meeting Notes]
* [https://storyboard.openstack.org/#!/project_group/86 StarlingX Storyboards]]
* [https://etherpad.openstack.org/p/stx-planning StarlingX Planning] (contains sub-projects and Worklists)

== References ==

* [https://etherpad.openstack.org/p/stx-notes The list of repos] and other things

=== OpenStack Documentation ===

* [https://docs.openstack.org/infra/manual/developers.html Developer's Guide]
* [https://docs.openstack.org/infra/manual/creators.htmlProject Creator's Guide]
* [https://wiki.openstack.org/wiki/How_To_Contribute The Contributors Guide] (the older wiki page)
* [https://governance.openstack.org/tc/reference/project-testing-interface.html Project Testing Interface]

Forum/Sydney2017

2017-11-06T07:50:35Z

Dtroyer: /* Tuesday, November 7 */

The grand list of all of the Sydney 2017 [[Forum]] etherpads. Please add links to etherpads below!

At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Sydney Forum is the start of the planning phase for the '''Rocky''' development cycle. Please prepare session ideas with feedback from the '''Pike''' release in mind.

See also - [https://www.openstack.org/summit/sydney-2017/summit-schedule/#tracks=157 Full Forum Schedule]

===Monday, November 6===
* [1135-1215] Forum 101 https://etherpad.openstack.org/p/SYD-forum-101
* [1135-1215] API-SIG https://etherpad.openstack.org/p/api-sig-sydney-forum
* [1135-1215] Missing Features and Making Improvements to OpenStack Health https://etherpad.openstack.org/p/SYD-forum-openstack-health-feedback
* [1135-1215] Improving Gopher Cloud and OpenStack K8s Provider https://etherpad.openstack.org/p/SYD-improving-gopher-cloud
* [1330-1410] Kolla Ops feedback session http://etherpad.openstack.org/p/kolla-sydney-ops-feedback
* [1330-1410] Glance Project Onboarding https://etherpad.openstack.org/p/SYD-forum-glance-onboarding
* [1330-1410] Ops Guide Transition and Maintenance https://etherpad.openstack.org/p/SYD-forum-ops-guide-transition
* [1420-1500] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20434/keystone-project-onboarding Keystone Project Onboarding]
https://etherpad.openstack.org/p/SYD-forum-keystone-project-onboarding
* [1420-1500] Interop Working Group Community Feedback and Work Session https://etherpad.openstack.org/p/SYD-interop-working-group
* [1420-1500] Installation Guides and Tutorials Updates and Testing https://etherpad.openstack.org/p/SYD-install-guide-testing
* [1510-1550] Fast-Forward Upgrades https://etherpad.openstack.org/p/SYD-forum-fast-forward-upgrades
* [1510-1550] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20453/application-credentials-feedback Application Credentials Feedback] https://etherpad.openstack.org/p/SYD-forum-application-credentials-feedback
*[1510-1550] Fog/Edge/Massively Distributed Clouds (FEMDC) SIG- https://etherpad.openstack.org/p/FEMDC-F2F-meeting-sydney-summit
* [1620-1700] Protecting Plaintext Passwords in Configuration Files https://etherpad.openstack.org/p/plaintext-secrets
* [1620-1700] TripleO onboarding https://etherpad.openstack.org/p/SYD-forum-tripleo-onboarding
* [1620-1700] Privsep: what is it and operational impacts https://etherpad.openstack.org/p/SYD-forum-privsep
* [1620-1700] User Survey Feedback https://etherpad.openstack.org/p/UserSurveyFeedback
* [1710-1750] What Do Operators Want from Stable Policy https://etherpad.openstack.org/p/SYD-stable-policy
* [1710-1750] Cinder/Nova Cross Project Session on Multi-Attach https://etherpad.openstack.org/p/sydney-cinder-nova-cp-multi-attach

===Tuesday, November 7===
* [0900-0940] Self-healing and optimization SIG https://etherpad.openstack.org/p/self-healing-rocky-forum
* [0900-0940] Nova project onboarding https://etherpad.openstack.org/p/SYD-forum-nova-onboarding
* [0900-0940] Interop Test Library for OpenStack SDKs https://etherpad.openstack.org/p/SYD-forum-sdk-interop-test-library
* [0950-1030] Making OpenStack more palatable to part-time contributors https://etherpad.openstack.org/p/SYD-part-time-contributors
* [0950-1030] Zuul v3 Feedback Session https://etherpad.openstack.org/p/SYD-zuul-v3-feedback
* [0950-1030] Charms User Feedback session https://etherpad.openstack.org/p/SYD-forum-charms-ops-feedback
* [1050-1130] The State of Test Runners and Moving to stestr https://etherpad.openstack.org/p/SYD-forum-test-runners
* [1050-1130] SIGs II: to infinity and beyond https://etherpad.openstack.org/p/SYD-SIGs
* [1050-1130] Edge Computing Use Cases and Architecture https://etherpad.openstack.org/p/OS_Sydney_edge_computing_use_cases
* [1140-1220] Manila project on boarding https://etherpad.openstack.org/p/SYD-forum-manila-project-onboarding
* [1140-1220] openstack-sig-k8s and k8s-sig-openstack collaborations https://etherpad.openstack.org/p/SYD-openstack-sig-k8s-collaborations
* [1350-1430] Supporting General Federation for Large-Scale Collaborations https://etherpad.openstack.org/p/Supporting-General-Federation
* [1350-1430] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20470/extremedestructive-testing Extreme/Destructive Testing] https://etherpad.openstack.org/p/SYD-extreme-testing
* [1520-16:00] Ops Meetup Team catch-up https://etherpad.openstack.org/p/SYD-Ops_Meetup_Team_catch-up
* [1520-1600] Constellation Brainstorming https://etherpad.openstack.org/p/SYD-constellations
* [1610-1650] Glance: Operators Feedback Session https://etherpad.openstack.org/p/SYD-forum-glance-feedback
* [1610-1650] OpenStackClient and Nova API microversions https://etherpad.openstack.org/p/SYD-forum-nova-osc
* [1700-1740] Ceph in OpenStack BoF https://etherpad.openstack.org/p/SYD-forum-Ceph-OpenStack-BoF
* [1750-1830] Cells v2 update and direction https://etherpad.openstack.org/p/SYD-forum-nova-cellsv2-update
* [1750-1830] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20502/keystone-operator-and-user-feedback Keystone Operator & User Feedback] https://etherpad.openstack.org/p/SYD-forum-keystone-feedback

===Wednesday, November 8===
* [0900-0940] Upstream LTS Releases https://etherpad.openstack.org/p/SYD-forum-upstream-lts-releases
* [0900-0940] Hardware in the Cloud https://etherpad.openstack.org/p/SYD-forum-hardware-clouds
* [0950-1030] ETSI NFV Specs’ Requirements vs OpenStack Reality forum https://etherpad.openstack.org/p/ptg-denver-etsi-nfv-tst003-gaps-explained
* [0950-1030] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20473/openstack-public-cloud-passport-program OpenStack Public Cloud Passport Program] https://etherpad.openstack.org/p/SYD-forum-public-cloud
* [1100-1140] Bare metal as a service: Ironic vs. Mogan vs. Nova https://etherpad.openstack.org/p/SYD-forum-baremetal-ironic-mogan-nova
* [1100-1140] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20452/rbacpolicy-roadmap-feedback RBAC/Policy Roadmap Feedback]
https://etherpad.openstack.org/p/SYD-forum-policy-roadmap-feedback
* [1150-1230] Watcher users feedback https://etherpad.openstack.org/p/watcher-sydney-forum
* [1150-1230] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/19798/features-missing-in-openstack-core-for-public-cloud-providers Features missing in OpenStack core for Public Cloud Providers] https://etherpad.openstack.org/p/SYD-forum-missing-features-pc
* [1350-1430] Placement update and direction https://etherpad.openstack.org/p/SYD-forum-nova-placement-update
* [1440-1520] Nova: Queens roadmap and checkpoint https://etherpad.openstack.org/p/SYD-forum-nova-queens-update
* [1530-1610] Refstack: OpenStack to OPNFV, Vertical, Integrated, Interop https://etherpad.openstack.org/p/SYD-refstack-nfv
* [1630-1710] OpenStack Foundation update https://etherpad.openstack.org/p/SYD-foundation-update
* [1630-1710] Heat ops and users feedback https://etherpad.openstack.org/p/Sydney-heat-ops-and-users-feedback
* [1720-1800] Technical Committee in-person office hour https://etherpad.openstack.org/p/SYD-tc-office-hour

SDKs

2017-08-25T18:40:58Z

Dtroyer: /* Go */ Remove golang-client, it is very incomplete and not usable as-is

= Software Development Kits =

SDKs are a vital part of the OpenStack ecosystem, they help developers write applications for OpenStack and other clouds. For a list of the official OpenStack Python client libraries, see [[OpenStackClients]].

__TOC__

= Definition =

# A set of language bindings that provide a language-level API for accessing OpenStack in a manner consistent with language standards.
# A Getting Started document that shows how to use the API to access OpenStack powered clouds.
# Detailed API reference documentation.
# Tested sample code that you can use as a "starter kit" for your own OpenStack applications.
# SDKs treat OpenStack as a blackbox and only interact with the REST/HTTP API.
# Must be [http://opensource.com/life/14/1/evaluate-sustainability-open-source-project sustainable].
# License must be compatible with Apache License v2.

= Additional Criteria =

What criteria is used to determine whether or not an SDK can be considered an OpenStack SDK has not been formalized. This has been initially discussed at the OpenStack Grizzly Summit ([https://etherpad.openstack.org/sdk-documentation etherpad]). Naturally the SDK will need to meet the definition above. In addition we thought the OpenStack Foundation may want to consider a compatibility test suite that will validate whether or not an SDK supports OpenStack.

These are items that could be used as criteria to define an SDK but themselves require further definition w.r.t. SDKs.

# Handle extensions in some way.
# Backwards compatibility.
# Compatibility with test suite.

= Official OpenStack Clients =

The [[OpenStackClients]] are the native Python bindings for the OpenStack APIs. They are used to implement the command-line interfaces (which ship with the library).

= Known SDKs =

What follows is a list of known SDKs that support OpenStack. This is not a list of official OpenStack SDKs. What constitutes an official OpenStack SDK has not been determined. This is an area the needs more work (see Criteria section).

To date, SDKs that support OpenStack fall into two categories. SDKs that support multiple clouds including OpenStack (aka multi-cloud toolkits) and SDKs that support OpenStack only. If you're aware of any other SDKs, please add them to the lists below.

= [[OpenStack]] Toolkits =

== Go ==
* [https://github.com/rackspace/gophercloud Gophercloud] provides a Go binding to OpenStack cloud APIs.

== Java ==
* [http://www.openstack4j.com OpenStack4j] A fluent Java OpenStack API.
* [https://github.com/woorea/openstack-java-sdk OpenStack Java SDK] is a Java binding for the OpenStack APIs.
* [http://jclouds.apache.org/ Apache jclouds] is a Multi-cloud SDK for Java with OpenStack support

== JavaScript ==
* [https://github.com/nodejitsu/pkgcloud pkgcloud] is a Multi-cloud library for Node.js that supports OpenStack
* [http://ging.github.com/jstack/ jstack] is a JavaScript client library for the OpenStack API.
* [https://github.com/gabrielhurley/js-openclient js-openclient] is a very opinionated core client which can be used in either Node.js or in the browser (browser support not yet complete) to communicate with a RESTful APIs, including but not limited to any OpenStack-compatible API. (last updated 2015)
* [https://github.com/godaddy/node-openstack-wrapper node-openstack-wrapper] is a convenience wrapper for many of Openstack's common features with a focus on projects/tenants.

== .NET ==
* [https://github.com/openstacknetsdk/openstack.net OpenStack.NET] is a .NET SDK for OpenStack.

== PHP ==
* [https://github.com/php-opencloud/openstack php-opencloud/openstack] is a PHP SDK for OpenStack. It is actively maintained and supports latest OpenStack identity api (Keystone v3).
SDK covers following api: BlockStorage v2, Compute v2, Identity Keystone v2 and v3, Images v2, Networking v2 including Layer3 extension and Security Groups extension, Object Storage v1, Gnocchi v1

== Python ==
* [https://docs.openstack.org/developer/shade/ OpenStack Shade] shade is a simple client library for operating OpenStack clouds that abstracts deployer differences
* The [[SDK-Development/PythonOpenStackSDK]] project is a proposed solution to offering an SDK that provides a single point of entry for consumers, and a base from which other tools can be built upon, such as command-line interfaces.
* The [[OpenStackClients]] are the native Python bindings for the OpenStack APIs. They are used to implement the command-line interfaces (which ship with the library).
* [http://libcloud.apache.org/ Apache libcloud] is a Python library that abstracts away differences among multiple cloud provider APIs.

== Ruby ==
* [http://fog.io/ fog] is a Multi-cloud Ruby library with support for OpenStack
* [http://aviator.github.io/www/ Aviator] An elegantly designed OpenStack SDK for Ruby (hasn't been updated since 2015)

= Toolkits targetting Specific OpenStack Projects =

== C ==
* [https://github.com/ukyg9e5r6k7gubiekd6 Keystone and Swift libraries] C library bindings to the OpenStack Keystone and Swift APIs.
* [https://github.com/RedHatEMEA/c-keystoneclient c-keystoneclient] c-keystoneclient is a C-based client library for OpenStack Keystone authentication.
== C++ ==
[https://github.com/bshafiee/Swift_CPP_SDK SWIFT_CPP_SDK] is a C++ binding for accessing the Swift REST API.
== go ==
* [https://github.com/ncw/swift swift] implements Swift client on Go. Keystone v1,v2,v3 is supported
== Java ==
* [http://joss.javaswift.org/ Java OpenStack Storage aka JOSS] is a dedicated Java binding for accessing the Swift REST API.
== Perl ==
* [https://github.com/ironcamel/Net-OpenStack-Compute Net::OpenStack::Compute] provides Perl bindings for the OpenStack Compute API. It also provides a command line tool oscompute for interacting with an OpenStack deployment. (last updated 2015)
== Ruby ==
* [https://github.com/mrkamel/swift_client swift_client] Small but powerful client to interact with OpenStack Swift
* [https://github.com/tulios/nightcrawler_swift nightcrawler_swift] Like the X-Men nightcrawler this gem teleports your assets to a OpenStack Swift bucket/container
* [https://rubygems.org/gems/swift-storage swift-storage] Simple Openstack Swift storage client.

PTG/Queens/Etherpads

2017-08-18T13:38:25Z

Dtroyer: /* Monday -> Tuesday */

__NOTOC__

This is the list of etherpads for the Projects Team Gathering in Denver. Each team can organize the content on their allocated day(s) in the way that seems to most appropriate to them. We suspect most teams will avoid strict timeboxed slots and will use etherpads to list topics to cover. This page lists those etherpads for easy reference.

For more details on the event, see the [https://www.openstack.org/ptg/ event website].

For what's happening '''right now''', see the [http://ptg.openstack.org/ptg.html ptgbot page].

=== Whole Week ===
* Infra: https://etherpad.openstack.org/p/infra-ptg-queens
* QA: https://etherpad.openstack.org/p/qa-queens-ptg

=== Monday -> Tuesday ===
* API: https://etherpad.openstack.org/p/api-ptg-queens
* Docs: https://etherpad.openstack.org/p/denver-doc-PTG
* Horizon: https://etherpad.openstack.org/p/horizon-ptg-queens
* i18n: https://etherpad.openstack.org/p/denver-i18n-PTG
* CLI (OpenStackClient, OpenStackSDK, Shade, etc): https://etherpad.openstack.org/p/osc-queens-ptg
* Oslo: https://etherpad.openstack.org/p/oslo-ptg-queens
* Refstack: https://etherpad.openstack.org/p/InteropDenver2017PTG
* Requirements: https://etherpad.openstack.org/p/queens-PTG-requirements
* Stable: https://etherpad.openstack.org/p/queens-PTG-stable
* Technical Committee / Stewardship WG: https://etherpad.openstack.org/p/queens-PTG-TC-SWG
* VM and BM SIG: https://etherpad.openstack.org/p/queens-PTG-vmbm

=== Wednesday -> Thursday ===
* Barbican: https://etherpad.openstack.org/p/barbican-ptg-queens
* Charms: https://etherpad.openstack.org/p/ptg-queens-charms
* Congress: https://etherpad.openstack.org/p/congress-ptg-queens
* Freezer: https://etherpad.openstack.org/p/freezer-ptg-queens
* Glare: https://etherpad.openstack.org/p/glare-ptg-queens
* Heat: https://etherpad.openstack.org/p/heat-queens-ptg
* Mistral: https://etherpad.openstack.org/p/mistral-ptg-queens
* Puppet: https://etherpad.openstack.org/p/puppet-queens-ptg
* Sahara: https://etherpad.openstack.org/p/sahara-queens-ptg
* Trove: https://etherpad.openstack.org/p/trove-queens-ptg

=== Wednesday -> Friday ===
* Ansible: https://etherpad.openstack.org/p/osa-denver-PTG-planning
* Cinder: https://etherpad.openstack.org/p/cinder-ptg-queens
* Glance: https://etherpad.openstack.org/p/glance-queens-ptg-planning
* Ironic: https://etherpad.openstack.org/p/ironic-queens-ptg
* Keystone: https://etherpad.openstack.org/p/keystone-queens-ptg
* Kolla: https://etherpad.openstack.org/p/kolla-queens-ptg-planning
* Neutron: https://etherpad.openstack.org/p/neutron-queens-ptg
* Nova: https://etherpad.openstack.org/p/nova-ptg-queens
* Octavia: https://etherpad.openstack.org/p/octavia-ptg-queens
* Swift: https://etherpad.openstack.org/p/swift-ptg-queens
* TripleO: https://etherpad.openstack.org/p/tripleo-ptg-queens

=== Not In Denver ===
Some teams will not be meeting in Denver but will have separate PTG events.

* Manila: https://etherpad.openstack.org/p/manila-ptg-queens

Release Naming/R Proposals

2017-03-29T18:02:49Z

Dtroyer: /* Proposed Names */

== R Release Naming ==

According to the [http://governance.openstack.org/reference/release-naming.html Release Naming Process], this page will contain a list of nominated names for the R release of OpenStack. We will accept nominations until 2017-03-29 23:59:59 UTC.

=== Release Name Criteria ===

* Each release name must start with the letter of the ISO basic Latin alphabet following the initial letter of the previous release, starting with the initial release of "Austin". After "Z", the next name should start with "A" again.
* The name must be composed only of the 26 characters of the ISO basic Latin alphabet. Names which can be transliterated into this character set are also acceptable.
* The name must refer to the physical or human geography of the region encompassing the location of the OpenStack design summit for the corresponding release. The exact boundaries of the geographic region under consideration must be declared before the opening of nominations, as part of the initiation of the selection process.
* The name must be a single word with a maximum of 10 characters. Words that describe the feature should not be included, so "Foo City" or "Foo Peak" would both be eligible as "Foo".

Names which do not meet these criteria but otherwise sound really cool
should be added to a separate section of the wiki page and the TC may
make an exception for one or more of them to be considered in the
Condorcet poll. The naming official is responsible for presenting the
list of exceptional names for consideration to the TC before the poll
opens.

=== Exact Geographic Region ===

The Geographic Region from where names for the R release will come is [https://en.wikipedia.org/wiki/British_Columbia British Columbia]

=== Proposed Names ===

* [https://en.wikipedia.org/wiki/Radium_Hot_Springs Radium]
* [https://www.lonelyplanet.com/canada/vancouver/attractions/railspur-alley/a/poi-sig/1161243/361261 Railspur] (Railspur Alley in Granville Island, Vancouver - a place to meet makers and buy their goods from wood and metals to sake and silks)
* [https://en.wikipedia.org/wiki/Rambler_Peak Rambler] (Peak)
* [https://www.ukclimbing.com/logbook/c.php?i=230240 Rambles] (A classic rock climb on the Squamish chief)
* [https://goo.gl/maps/MdJ4YehuVu42 Rampart] (Mountain)
* [https://en.wikipedia.org/wiki/Raspberry,_British_Columbia Raspberry]
* [https://en.wikipedia.org/wiki/Raush_River Raush] (a tributary of the Fraser river)
* [https://en.wikipedia.org/wiki/Ray_Lake Ray] (Lake)
* [https://en.wikipedia.org/wiki/Razorback_Mountain_(British_Columbia) Razorback] (Mountain)
* [http://www.env.gov.bc.ca/bcparks/explore/parkpgs/rebecca/ Rebecca] (Rebecca Spit Marine Provincial Park, the quintessential coastline of BC)
* [https://en.wikipedia.org/wiki/Revelstoke,_British_Columbia Revelstoke] (City - Columbia)
* [https://goo.gl/maps/sVHsDLE6N4p Rex] (Peak, north of Vancouver)
* [https://en.wikipedia.org/wiki/Richmond,_British_Columbia Richmond] (City - Vancouver)
* [https://www.tourismvancouver.com/vancouver/neighbourhoods/robson-street/ Robson] (street from BC Place Stadium to Stanley Park, a must-stroll)
* [https://en.wikipedia.org/wiki/Rock_Creek_(British_Columbia) Rock] (Creek)
* [https://en.wikipedia.org/wiki/Rocky_Mountains Rocky] (Mountains)
* [https://en.wikipedia.org/wiki/Canadian_Rockies Rockies]
* [https://en.wikipedia.org/wiki/Roderick_Island Roderick] (Island)
* [https://en.wikipedia.org/wiki/Mount_Root Root] (Mount Root)
* [https://en.wikipedia.org/wiki/Rossland,_British_Columbia Rossland] (City - Kootenay Boundary)
* [https://en.wikipedia.org/wiki/Rosswood,_British_Columbia Rosswood]
* [https://goo.gl/maps/a7sj9aw2SMH2 Rupert]
* [https://en.m.wikipedia.org/wiki/Renfrew_station Renfrew] (station)

=== Proposed Names that do not meet the criteria ===

* [https://en.wikipedia.org/wiki/Roundabout Roundabout]
* [https://en.wikipedia.org/wiki/Roustabout Roustabout]

PTG/Pike/Etherpads

2017-01-12T16:40:27Z

Dtroyer: /* Monday -> Tuesday */

__NOTOC__

This is the list of etherpads for the Projects Team Gathering in Atlanta. Each team can organize the content on their allocated day(s) in the way that seems to most appropriate to them. We suspect most teams will avoid strict timeboxed slots and will use etherpads to list topics to cover. This page lists those etherpads for easy reference.

For more details on the event, see the [https://www.openstack.org/ptg/ event website].

=== Only Monday ===

* Stewardship workgroup

=== Monday -> Tuesday ===

* Community App Catalog
* Documentation / I18n
* Horizon: https://etherpad.openstack.org/p/horizon-ptg-pike
* Infrastructure: https://etherpad.openstack.org/p/infra-ptg-pike
* Kolla
* OpenStackAnsible: https://etherpad.openstack.org/p/osa-ptg-pike
* OpenStackClient: https://etherpad.openstack.org/p/osc-ptg-pike
* OpenStack Charms
* Oslo
* Packaging RPM
* Quality Assurance: https://etherpad.openstack.org/p/qa-ptg-pike
* Rally / Performance workgroup: https://etherpad.openstack.org/p/ptg-performance-team
* RefStack / Interop workgroup
* Release Goal #1 (tbd)
* Release Goal #2 (tbd)
* Release Mgmt / Stable maint / Requirements
* Security: https://etherpad.openstack.org/p/ptg-security-team

=== Only Tuesday ===

* Architecture workgroup

=== Wednesday -> Thursday ===

* Congress
* Dragonflow
* Karbor: https://etherpad.openstack.org/p/karbor-ptg-pike
* Manila: https://etherpad.openstack.org/p/manila-pike-ptg-topics
* Sahara
* Storlets: https://etherpad.openstack.org/p/storlets-pike-design-summit
* Trove: https://etherpad.openstack.org/p/trove-pike-ptg-topics
* Watcher

=== Wednesday -> Friday ===

* Barbican: https://etherpad.openstack.org/p/ptg-barbican-pike
* Cinder: https://etherpad.openstack.org/p/ATL-cinder-ptg-planning
* Glance: https://etherpad.openstack.org/p/glance-pike-ptg-planning
* Heat: https://etherpad.openstack.org/p/heat-pike-ptg-sessions
* Ironic: https://etherpad.openstack.org/p/ironic-pike-ptg
* Keystone: https://etherpad.openstack.org/p/keystone-pike-ptg
* Magnum
* Mistral: https://etherpad.openstack.org/p/mistral-ptg-pike
* Neutron
* Nova: https://etherpad.openstack.org/p/nova-ptg-pike
* Octavia: https://etherpad.openstack.org/p/octavia-ptg-pike
* Swift
* TripleO: https://etherpad.openstack.org/p/tripleo-ptg-pike

Meetings/OpenStackClient

2017-01-12T13:02:56Z

Dtroyer: /* Weekly OpenStackClient Team Meeting */

= Weekly OpenStackClient Team Meeting =

The OpenStackClient Team holds public weekly meetings as noted on the [http://eavesdrop.openstack.org/#OpenStackClient_Team_Meeting OpenStack IRC Meeting] page, currently at 1900 UTC Thursday on odd weeks in <code><nowiki>#openstack-meeting</nowiki></code>, and 1300 UTC Thursday on even weeks in <code><nowiki>#openstack-meeting-3</nowiki></code>. 
Everyone who uses an OpenStack command-line interface is invited to attend.

The meeting minutes of can be found here: [http://eavesdrop.openstack.org/meetings/openstackclient meeting minutes on eavesdrop]

== Next Meeting Agenda ==

The meeting agenda is now kept in an [https://etherpad.openstack.org/p/osc-weekly-meeting Etherpad].

=== 7th April 2016 ===
* How to handle both Network related Compute and Neutron outputs when both are enabled:(reedip)
https://bugs.launchpad.net/python-openstackclient/+bug/1566090
* OSC Meeting Time
** Common votes seems for below time options
*** Even Weeks - E.4 - Thursday at 1600 UTC in #openstack-meeting (IRC webclient)
*** Odd Weeks - O.3 - Thursday at 1900 UTC in #openstack-meeting (IRC webclient) - our regular meeting time.
**Tang Chen was interested for O.1 for odd weeks. (Tuesday at 1400 UTC in #openstack-meeting-4 ).
***If possible for all, please consider this option.

=== 31 March 2016 ===
* Meeting time change proposal
* Cinder support in OSC (jgregor, baumann, sheel)
** Moving all commands over (filling in gaps)
*** Using the "volume" keyword before all volume commands
**** Consistency groups - naming convention
**** Snapshots are also used by manilla
** Keyword "properties" vs "metadata"
** Name is not a necessary field in cinder, but is in openstackclient
* Bugs and Reviews
* Open Discussion

=== 24 Sep 2015 ===
* Remaining Image work
* SDK Integration
** terrylhowe's series for Network: https://review.openstack.org/#/c/138745/
** dtroyer's common refactor, beginning Image: https://review.openstack.org/#/c/227037/
** Version discussion for dependency addition
*** Recent ML discussion: http://lists.openstack.org/pipermail/openstack-dev/2015-September/075107.html
* Bugs and Reviews
* Open Discussion

=== 6 August 2015 ===
* Discussed making 1.6.0 release

=== 16 July 2015 ===
* Make a consistent functional test, identity vs others, pretty table vs not

=== 04 Jun 2015 ===
* Open actions
** https://bugs.launchpad.net/python-openstackclient/+bug/1405562
*** Amey Bhide is making good progress on this
** https://bugs.launchpad.net/python-openstackclient/+bug/1459519
*** Terry has https://review.openstack.org/#/c/186394/ in cliff (now approved)
** Plugins - osc-plugin to cookiecutter
*** dtroyer: no movement
* Releases
** 1.4.0 release any minute now, was going to be a point release but the EC2 credentials fixes included adding v3 commands
** Still waiting on requirements update for KSC, in gate queue: https://review.openstack.org/#/c/188078/ (now merged)
* Blueprint Review
* Bugs/Reviews
* Open discussion

=== 28 May 2015 ===
* Open actions
* Blueprint Review
* Bugs/Reviews
* Open discussion

=== 07 May 2015 ===
* Open actions
* Summit planning
** [https://etherpad.openstack.org/p/osc-liberty-summit-planning Etherpad]
* Bugs/Reviews
* Open discussion

=== 30 Apr 2015 ===
* Open actions
* Release planning
** 1.2.0 release today - [https://launchpad.net/python-openstackclient/+milestone/m10 milestone m10]
* Summit planning
** [https://etherpad.openstack.org/p/osc-liberty-summit-planning Etherpad]
* Bugs/Reviews
* Open discussion

=== 23 Apr 2015 ===
* Open actions
* Release planning
** 1.1.0 released on 21Apr2015 - [https://launchpad.net/python-openstackclient/+milestone/m9 milestone m9]
** follow-up soon with 1.1.1 to clean up release notes and get in a few more bug fixes - [https://launchpad.net/python-openstackclient/+milestone/m10 nilestone m10]
* Summit planning
** [https://etherpad.openstack.org/p/osc-liberty-summit-planning Etherpad]
* Bugs
** [https://bugs.launchpad.net/python-openstackclient/+bug/1443089 1443089] - image list displays a maximum of 25 images
*** is this fixed by [https://review.openstack.org/#/c/173420/ review 173420]?
* Open discussion

=== 16 Apr 2015 ===
* Open actions
* Summit planning
* Reviews
** [https://review.openstack.org/#/c/164091/ 164091] - session timing
* Bugs
** [https://bugs.launchpad.net/python-openstackclient/+bug/1406470 1406470] - track backwards incompatible changes
*** Suggested to use a commit message tag
** [https://bugs.launchpad.net/python-openstackclient/+bug/1409218 1409218] - condense credentials (ec2, v3, compute)
*** still m9?
** [https://bugs.launchpad.net/python-openstackclient/+bug/1435962 1435962] - add support for keystone service providers
*** [https://review.openstack.org/#/c/165755/ review 165755]
*** has this been released in KSC yet?
** [https://bugs.launchpad.net/python-openstackclient/+bug/1443089 1443089] - image list displays a maximum of 25 images
*** recent discussion on how to handle:
**** add --limit (or other option)
**** just do the pagination to return all
**** both of the above
** [https://bugs.launchpad.net/python-openstackclient/+bug/1431649 1431649] - openstackclient is really slow
*** static import timing done with boris-42's profimp, addressed some in [https://review.openstack.org/173098 review 173098]
* Blueprints
** New: [https://blueprints.launchpad.net/python-openstackclient/+spec/waitcommand wait command]
* Open discussion

=== 09 Apr 2015 ===
* Open actions
* Open discussion

=== 02 Apr 2015 ===
* Open actions
** stevemar: BP to move fakes to fixtures for plugin testing
** dtroyer: BP to generalize JSON input
** dtroyer: add timing info to https://bugs.launchpad.net/python-openstackclient/+bug/1431649
** dtroyer: ML tag - OSC is registered
* Summit space
** what do we want/need? I asked ttx for one fishbowl and one workroom slot each, do we need them both?
*** https://wiki.openstack.org/wiki/Summit/Planning
* Review Review
** --os-cloud (https://review.openstack.org/129795)
* Bug Review
* Other repos
** os-client-config renamed last week
* Open Discussion

=== 19 Mar 2015 ===
* Open actions
** dtroyer: contributors list
* Public test interfaces
** Question about plugins using fakes from openstackclient.tests, public status undefined before now
* Bug Review
** Priorities for next release
* Other repos
** ACL changes in Gerrit made for cliff and os-client-config
* Open discussion

=== 12 Mar 2015 ===
* Open actions
** Project proposal submitted: https://review.openstack.org/#/c/161885/
* Release plans
* Bug Review
* Other repos
** cliff
** os-client-config
* Open discussion

=== 05 Mar 2015 ===
* Re-confirm meeting time from Doodle results (http://doodle.com/4uy5w2ehn8y2eayh)
* Open actions
** dhellmann set up doodle for meeting times (done)
** dtroyer to add cliff repo ownership to project proposal (done)
** dhellmann discuss cliff ownership change with oslo team (done)
* Project status
** Project requirement evaluation: [https://etherpad.openstack.org/p/osc-project etherpad]
** cliff repo ownership resolution
** Also add os-client-config repo
* Release schedule
** Possibly early next week (09 Mar 2015)
** propose 1.1.0 as new --os-cloud support adds interesting new capability
* Bug review
** Evaluate what can be completed before release and what should be deferred
* Open discussion

=== 26 Feb 2015 ===
* Confirm meeting time
* Project status
** Project requirement evaluation: [https://etherpad.openstack.org/p/osc-project etherpad]
** Should this project also own the cliff repo?
* Release schedule
* Bug review
* Open discussion

Meetings/OpenStackClient

2016-08-04T19:04:15Z

Dtroyer: /* Regular attendees */

= Weekly OpenStackClient Team Meeting =

The OpenStackClient Team holds public weekly meetings in <code><nowiki>#openstack-meeting</nowiki></code> on Thursdays at 19:00 UTC ([http://www.timeanddate.com/worldclock/fixedtime.html?hour=19&min=0&sec=0 Timezone Help]). 
Everyone who uses an OpenStack command-line interface is invited to attend.

== Regular attendees ==

Add yourself to this list to be pinged prior to each meeting:

dtroyer, dhellmann, rtheis, stevemar, dstanek, MeganR, DuncanT, sheel, jgregor, baumann

The meeting minutes of can be found here: [http://eavesdrop.openstack.org/meetings/openstackclient meeting minutes on eavesdrop]

== Next Meeting Agenda ==

''Note: Not all meetings had an advance agenda.''

=== 7th April 2016 ===
* How to handle both Network related Compute and Neutron outputs when both are enabled:(reedip)
https://bugs.launchpad.net/python-openstackclient/+bug/1566090
* OSC Meeting Time
** Common votes seems for below time options
*** Even Weeks - E.4 - Thursday at 1600 UTC in #openstack-meeting (IRC webclient)
*** Odd Weeks - O.3 - Thursday at 1900 UTC in #openstack-meeting (IRC webclient) - our regular meeting time.
**Tang Chen was interested for O.1 for odd weeks. (Tuesday at 1400 UTC in #openstack-meeting-4 ).
***If possible for all, please consider this option.

=== 31 March 2016 ===
* Meeting time change proposal
* Cinder support in OSC (jgregor, baumann, sheel)
** Moving all commands over (filling in gaps)
*** Using the "volume" keyword before all volume commands
**** Consistency groups - naming convention
**** Snapshots are also used by manilla
** Keyword "properties" vs "metadata"
** Name is not a necessary field in cinder, but is in openstackclient
* Bugs and Reviews
* Open Discussion

=== 24 Sep 2015 ===
* Remaining Image work
* SDK Integration
** terrylhowe's series for Network: https://review.openstack.org/#/c/138745/
** dtroyer's common refactor, beginning Image: https://review.openstack.org/#/c/227037/
** Version discussion for dependency addition
*** Recent ML discussion: http://lists.openstack.org/pipermail/openstack-dev/2015-September/075107.html
* Bugs and Reviews
* Open Discussion

=== 6 August 2015 ===
* Discussed making 1.6.0 release

=== 16 July 2015 ===
* Make a consistent functional test, identity vs others, pretty table vs not

=== 04 Jun 2015 ===
* Open actions
** https://bugs.launchpad.net/python-openstackclient/+bug/1405562
*** Amey Bhide is making good progress on this
** https://bugs.launchpad.net/python-openstackclient/+bug/1459519
*** Terry has https://review.openstack.org/#/c/186394/ in cliff (now approved)
** Plugins - osc-plugin to cookiecutter
*** dtroyer: no movement
* Releases
** 1.4.0 release any minute now, was going to be a point release but the EC2 credentials fixes included adding v3 commands
** Still waiting on requirements update for KSC, in gate queue: https://review.openstack.org/#/c/188078/ (now merged)
* Blueprint Review
* Bugs/Reviews
* Open discussion

=== 28 May 2015 ===
* Open actions
* Blueprint Review
* Bugs/Reviews
* Open discussion

=== 07 May 2015 ===
* Open actions
* Summit planning
** [https://etherpad.openstack.org/p/osc-liberty-summit-planning Etherpad]
* Bugs/Reviews
* Open discussion

=== 30 Apr 2015 ===
* Open actions
* Release planning
** 1.2.0 release today - [https://launchpad.net/python-openstackclient/+milestone/m10 milestone m10]
* Summit planning
** [https://etherpad.openstack.org/p/osc-liberty-summit-planning Etherpad]
* Bugs/Reviews
* Open discussion

=== 23 Apr 2015 ===
* Open actions
* Release planning
** 1.1.0 released on 21Apr2015 - [https://launchpad.net/python-openstackclient/+milestone/m9 milestone m9]
** follow-up soon with 1.1.1 to clean up release notes and get in a few more bug fixes - [https://launchpad.net/python-openstackclient/+milestone/m10 nilestone m10]
* Summit planning
** [https://etherpad.openstack.org/p/osc-liberty-summit-planning Etherpad]
* Bugs
** [https://bugs.launchpad.net/python-openstackclient/+bug/1443089 1443089] - image list displays a maximum of 25 images
*** is this fixed by [https://review.openstack.org/#/c/173420/ review 173420]?
* Open discussion

=== 16 Apr 2015 ===
* Open actions
* Summit planning
* Reviews
** [https://review.openstack.org/#/c/164091/ 164091] - session timing
* Bugs
** [https://bugs.launchpad.net/python-openstackclient/+bug/1406470 1406470] - track backwards incompatible changes
*** Suggested to use a commit message tag
** [https://bugs.launchpad.net/python-openstackclient/+bug/1409218 1409218] - condense credentials (ec2, v3, compute)
*** still m9?
** [https://bugs.launchpad.net/python-openstackclient/+bug/1435962 1435962] - add support for keystone service providers
*** [https://review.openstack.org/#/c/165755/ review 165755]
*** has this been released in KSC yet?
** [https://bugs.launchpad.net/python-openstackclient/+bug/1443089 1443089] - image list displays a maximum of 25 images
*** recent discussion on how to handle:
**** add --limit (or other option)
**** just do the pagination to return all
**** both of the above
** [https://bugs.launchpad.net/python-openstackclient/+bug/1431649 1431649] - openstackclient is really slow
*** static import timing done with boris-42's profimp, addressed some in [https://review.openstack.org/173098 review 173098]
* Blueprints
** New: [https://blueprints.launchpad.net/python-openstackclient/+spec/waitcommand wait command]
* Open discussion

=== 09 Apr 2015 ===
* Open actions
* Open discussion

=== 02 Apr 2015 ===
* Open actions
** stevemar: BP to move fakes to fixtures for plugin testing
** dtroyer: BP to generalize JSON input
** dtroyer: add timing info to https://bugs.launchpad.net/python-openstackclient/+bug/1431649
** dtroyer: ML tag - OSC is registered
* Summit space
** what do we want/need? I asked ttx for one fishbowl and one workroom slot each, do we need them both?
*** https://wiki.openstack.org/wiki/Summit/Planning
* Review Review
** --os-cloud (https://review.openstack.org/129795)
* Bug Review
* Other repos
** os-client-config renamed last week
* Open Discussion

=== 19 Mar 2015 ===
* Open actions
** dtroyer: contributors list
* Public test interfaces
** Question about plugins using fakes from openstackclient.tests, public status undefined before now
* Bug Review
** Priorities for next release
* Other repos
** ACL changes in Gerrit made for cliff and os-client-config
* Open discussion

=== 12 Mar 2015 ===
* Open actions
** Project proposal submitted: https://review.openstack.org/#/c/161885/
* Release plans
* Bug Review
* Other repos
** cliff
** os-client-config
* Open discussion

=== 05 Mar 2015 ===
* Re-confirm meeting time from Doodle results (http://doodle.com/4uy5w2ehn8y2eayh)
* Open actions
** dhellmann set up doodle for meeting times (done)
** dtroyer to add cliff repo ownership to project proposal (done)
** dhellmann discuss cliff ownership change with oslo team (done)
* Project status
** Project requirement evaluation: [https://etherpad.openstack.org/p/osc-project etherpad]
** cliff repo ownership resolution
** Also add os-client-config repo
* Release schedule
** Possibly early next week (09 Mar 2015)
** propose 1.1.0 as new --os-cloud support adds interesting new capability
* Bug review
** Evaluate what can be completed before release and what should be deferred
* Open discussion

=== 26 Feb 2015 ===
* Confirm meeting time
* Project status
** Project requirement evaluation: [https://etherpad.openstack.org/p/osc-project etherpad]
** Should this project also own the cliff repo?
* Release schedule
* Bug review
* Open discussion

Meetings/OpenStackClient

2016-06-23T19:04:27Z

Dtroyer: /* Regular attendees */

= Weekly OpenStackClient Team Meeting =

The OpenStackClient Team holds public weekly meetings in <code><nowiki>#openstack-meeting</nowiki></code> on Thursdays at 19:00 UTC ([http://www.timeanddate.com/worldclock/fixedtime.html?hour=19&min=0&sec=0 Timezone Help]). 
Everyone who uses an OpenStack command-line interface is invited to attend.

== Regular attendees ==

Add yourself to this list to be pinged prior to each meeting:

dtroyer, dhellmann, rthies, stevemar, terrylhowe, dstanek, MeganR, rtheis, DuncanT, sheel, jgregor, baumann

The meeting minutes of can be found here: [http://eavesdrop.openstack.org/meetings/openstackclient meeting minutes on eavesdrop]

== Next Meeting Agenda ==

''Note: Not all meetings had an advance agenda.''

=== 7th April 2016 ===
* How to handle both Network related Compute and Neutron outputs when both are enabled:(reedip)
https://bugs.launchpad.net/python-openstackclient/+bug/1566090
* OSC Meeting Time
** Common votes seems for below time options
*** Even Weeks - E.4 - Thursday at 1600 UTC in #openstack-meeting (IRC webclient)
*** Odd Weeks - O.3 - Thursday at 1900 UTC in #openstack-meeting (IRC webclient) - our regular meeting time.
**Tang Chen was interested for O.1 for odd weeks. (Tuesday at 1400 UTC in #openstack-meeting-4 ).
***If possible for all, please consider this option.

=== 31 March 2016 ===
* Meeting time change proposal
* Cinder support in OSC (jgregor, baumann, sheel)
** Moving all commands over (filling in gaps)
*** Using the "volume" keyword before all volume commands
**** Consistency groups - naming convention
**** Snapshots are also used by manilla
** Keyword "properties" vs "metadata"
** Name is not a necessary field in cinder, but is in openstackclient
* Bugs and Reviews
* Open Discussion

=== 24 Sep 2015 ===
* Remaining Image work
* SDK Integration
** terrylhowe's series for Network: https://review.openstack.org/#/c/138745/
** dtroyer's common refactor, beginning Image: https://review.openstack.org/#/c/227037/
** Version discussion for dependency addition
*** Recent ML discussion: http://lists.openstack.org/pipermail/openstack-dev/2015-September/075107.html
* Bugs and Reviews
* Open Discussion

=== 6 August 2015 ===
* Discussed making 1.6.0 release

=== 16 July 2015 ===
* Make a consistent functional test, identity vs others, pretty table vs not

=== 04 Jun 2015 ===
* Open actions
** https://bugs.launchpad.net/python-openstackclient/+bug/1405562
*** Amey Bhide is making good progress on this
** https://bugs.launchpad.net/python-openstackclient/+bug/1459519
*** Terry has https://review.openstack.org/#/c/186394/ in cliff (now approved)
** Plugins - osc-plugin to cookiecutter
*** dtroyer: no movement
* Releases
** 1.4.0 release any minute now, was going to be a point release but the EC2 credentials fixes included adding v3 commands
** Still waiting on requirements update for KSC, in gate queue: https://review.openstack.org/#/c/188078/ (now merged)
* Blueprint Review
* Bugs/Reviews
* Open discussion

=== 28 May 2015 ===
* Open actions
* Blueprint Review
* Bugs/Reviews
* Open discussion

=== 07 May 2015 ===
* Open actions
* Summit planning
** [https://etherpad.openstack.org/p/osc-liberty-summit-planning Etherpad]
* Bugs/Reviews
* Open discussion

=== 30 Apr 2015 ===
* Open actions
* Release planning
** 1.2.0 release today - [https://launchpad.net/python-openstackclient/+milestone/m10 milestone m10]
* Summit planning
** [https://etherpad.openstack.org/p/osc-liberty-summit-planning Etherpad]
* Bugs/Reviews
* Open discussion

=== 23 Apr 2015 ===
* Open actions
* Release planning
** 1.1.0 released on 21Apr2015 - [https://launchpad.net/python-openstackclient/+milestone/m9 milestone m9]
** follow-up soon with 1.1.1 to clean up release notes and get in a few more bug fixes - [https://launchpad.net/python-openstackclient/+milestone/m10 nilestone m10]
* Summit planning
** [https://etherpad.openstack.org/p/osc-liberty-summit-planning Etherpad]
* Bugs
** [https://bugs.launchpad.net/python-openstackclient/+bug/1443089 1443089] - image list displays a maximum of 25 images
*** is this fixed by [https://review.openstack.org/#/c/173420/ review 173420]?
* Open discussion

=== 16 Apr 2015 ===
* Open actions
* Summit planning
* Reviews
** [https://review.openstack.org/#/c/164091/ 164091] - session timing
* Bugs
** [https://bugs.launchpad.net/python-openstackclient/+bug/1406470 1406470] - track backwards incompatible changes
*** Suggested to use a commit message tag
** [https://bugs.launchpad.net/python-openstackclient/+bug/1409218 1409218] - condense credentials (ec2, v3, compute)
*** still m9?
** [https://bugs.launchpad.net/python-openstackclient/+bug/1435962 1435962] - add support for keystone service providers
*** [https://review.openstack.org/#/c/165755/ review 165755]
*** has this been released in KSC yet?
** [https://bugs.launchpad.net/python-openstackclient/+bug/1443089 1443089] - image list displays a maximum of 25 images
*** recent discussion on how to handle:
**** add --limit (or other option)
**** just do the pagination to return all
**** both of the above
** [https://bugs.launchpad.net/python-openstackclient/+bug/1431649 1431649] - openstackclient is really slow
*** static import timing done with boris-42's profimp, addressed some in [https://review.openstack.org/173098 review 173098]
* Blueprints
** New: [https://blueprints.launchpad.net/python-openstackclient/+spec/waitcommand wait command]
* Open discussion

=== 09 Apr 2015 ===
* Open actions
* Open discussion

=== 02 Apr 2015 ===
* Open actions
** stevemar: BP to move fakes to fixtures for plugin testing
** dtroyer: BP to generalize JSON input
** dtroyer: add timing info to https://bugs.launchpad.net/python-openstackclient/+bug/1431649
** dtroyer: ML tag - OSC is registered
* Summit space
** what do we want/need? I asked ttx for one fishbowl and one workroom slot each, do we need them both?
*** https://wiki.openstack.org/wiki/Summit/Planning
* Review Review
** --os-cloud (https://review.openstack.org/129795)
* Bug Review
* Other repos
** os-client-config renamed last week
* Open Discussion

=== 19 Mar 2015 ===
* Open actions
** dtroyer: contributors list
* Public test interfaces
** Question about plugins using fakes from openstackclient.tests, public status undefined before now
* Bug Review
** Priorities for next release
* Other repos
** ACL changes in Gerrit made for cliff and os-client-config
* Open discussion

=== 12 Mar 2015 ===
* Open actions
** Project proposal submitted: https://review.openstack.org/#/c/161885/
* Release plans
* Bug Review
* Other repos
** cliff
** os-client-config
* Open discussion

=== 05 Mar 2015 ===
* Re-confirm meeting time from Doodle results (http://doodle.com/4uy5w2ehn8y2eayh)
* Open actions
** dhellmann set up doodle for meeting times (done)
** dtroyer to add cliff repo ownership to project proposal (done)
** dhellmann discuss cliff ownership change with oslo team (done)
* Project status
** Project requirement evaluation: [https://etherpad.openstack.org/p/osc-project etherpad]
** cliff repo ownership resolution
** Also add os-client-config repo
* Release schedule
** Possibly early next week (09 Mar 2015)
** propose 1.1.0 as new --os-cloud support adds interesting new capability
* Bug review
** Evaluate what can be completed before release and what should be deferred
* Open discussion

=== 26 Feb 2015 ===
* Confirm meeting time
* Project status
** Project requirement evaluation: [https://etherpad.openstack.org/p/osc-project etherpad]
** Should this project also own the cliff repo?
* Release schedule
* Bug review
* Open discussion

Design Summit/Newton/Etherpads

2016-04-14T20:23:06Z

Dtroyer: /* OpenStackClient */

[[Category:Summit]]
[[Category:Newton]]
[[Category:Etherpad]]

The grand list of all the Newton Design Summit sessions. Please include Date, Time, and links to etherpads when adding new content.

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
__TOC__
</div>
== Event intro/closure ==
* Tue 11:15: Design Summit 101 - https://etherpad.openstack.org/p/newton-design-summit-101

==App Catalog==
?

== Barbican ==
?

== Cinder ==
?

== CloudKitty ==
?

== Congress ==
?

== Cross-Project workshops ==

All sessions are on Tuesday 2016-04-26

https://www.openstack.org/summit/austin-2016/summit-schedule/#day=2016-04-26&summit_types=2&tags=3601

* '''11:15 - 11:55'''
** Deployment tools discussion - https://etherpad.openstack.org/p/newton-deployment-tools-discussion
** Getting API Docs off of WADL and into RST - https://etherpad.openstack.org/p/newton-api-docs-rst
** How do we get a single CLI? - https://etherpad.openstack.org/p/newton-single-cli
* '''12:05 - 12:45'''
** Alternatives to polling - https://etherpad.openstack.org/p/newton-alternatives-to-polling
** Co-installability Requirements Are Holding Us Back - https://etherpad.openstack.org/p/newton-coinstallable-requirements
** Using keystoneauth correctly in projects - https://etherpad.openstack.org/p/newton-using-keystoneauth
* '''''Lunch'''''
* '''14:00 - 14:40'''
** Improve oslo.policy to be used more like configuration - https://etherpad.openstack.org/p/newton-policy-in-code
** Moving towards a Identity v3 API only devstack - https://etherpad.openstack.org/p/newton-keystone-v3-devstack
** Stable Branch End of Life Policy - https://etherpad.openstack.org/p/stable-branch-eol-policy-newton
* '''14:50 - 15:30'''
** Backwards compatibility for Libraries - https://etherpad.openstack.org/p/newton-backwards-compat-libs
** Common service deployment in devstack - https://etherpad.openstack.org/p/newton-devstack-wsgi-patterns
** Conventional roles for default policy files - https://etherpad.openstack.org/p/newton-default-policy-roles
* '''15:40 - 16:20'''
** Discovery: Everybody's doing it. Can we all do it the same way? - https://etherpad.openstack.org/p/newton-discovery
** Moving from oslo.rootwrap to oslo.privsep - https://etherpad.openstack.org/p/newton-privsep
** Scaling the OSSA/VMT via Threat Analysis - https://etherpad.openstack.org/p/newton-thread-analysis
* '''''Coffee Break'''''
* '''16:40 - 17:20'''
** (In)secure messaging - https://etherpad.openstack.org/p/newton-secure-messaging
** Brainstorm format for design summit split event - https://etherpad.openstack.org/p/newton-design-summit-format
** The future of baremetal networking - https://etherpad.openstack.org/p/newton-baremetal-networking
* '''17:30 - 18:10'''
** Defining scope of cross projects specs, tracking methods, and approach for providing user/operator feedback as user & design summits separate. - https://etherpad.openstack.org/p/newton-cross-project-spec-scope
** Instance Users - https://etherpad.openstack.org/p/newton-instance-users
** Quota 'delimiter' service and/or library - https://etherpad.openstack.org/p/newton-quota-library

== Ceilometer ==

?

== Cue ==

?

== Designate ==

?

== Documentation ==

?

== Glance ==

?

== Group Based Policy ==

?

== Heat ==

?

== Horizon ==

?

== I18N ==

?

== Infrastructure ==

?

== Ironic ==
?

== Kolla ==

?

== Keystone ==

* (work session) https://etherpad.openstack.org/p/newton-keystone-shadow-ldap-users

== Magnum ==
?

== Manila ==
?

==Murano==
?

== Neutron ==

Wednesday 2016-04-27

Wed 13:50 - 14:30 Development track: future of *-aas projects https://etherpad.openstack.org/p/newton-neutron-future-adv-services

Wed 14:40 - 15:20 Development track: neutron-lib next steps https://etherpad.openstack.org/p/newton-neutron-lib-next-steps

Wed 15:30 - 16:10 Development track: completing the Mitaka backlog https://etherpad.openstack.org/p/newton-neutron-core-mitaka-backlog

Wed 16:30 - 17:10 Development track: future of Neutron API https://etherpad.openstack.org/p/newton-neutron-future-neutron-api

Wed 17:20 - 18:00 Development track: future of Neutron architecture https://etherpad.openstack.org/p/newton-neutron-future-neutron-architecture

Thursday 2016-04-28

Thu 09:00 - 09:40 Development track: future of Neutron client https://etherpad.openstack.org/p/newton-neutron-future-neutron-client

Thu 09:50 - 10:30 User feedback track: health checking and troubleshooting https://etherpad.openstack.org/p/newton-neutron-troubleshooting

Thu 16:10 - 16:50 User feedback track: end user and operator pain points https://etherpad.openstack.org/p/newton-neutron-pain-points

Thu 17:00 - 17:40 Community track: stadium evolution https://etherpad.openstack.org/p/newton-neutron-community-stadium-evolution

Friday 2016-04-29

Fri 09:00 - 12:30 Neutron: Contributors meetup https://etherpad.openstack.org/p/newton-neutron-unplugged-track

Fri 14:00 - 17:30 Neutron: Contributors meetup https://etherpad.openstack.org/p/newton-neutron-unplugged-track

== Nova ==

?

== OpenStack-Ansible ==
https://etherpad.openstack.org/p/openstack-ansible-newton-summit

== OpenStack Chef ==
?

== OpenStackClient ==
28 Apr 2016 15:10 - 15:50
https://etherpad.openstack.org/p/newton-openstackclient

== Ops ==
Operators sessions are on Monday 2016-04-25

https://www.openstack.org/summit/austin-2016/summit-schedule/#day=2016-04-25&summit_types=2&tags=976,1419

== Oslo ==

?

== Packaging OpenStack ==

?

== Product Team ==

?

== Puppet OpenStack ==
?

== QA ==
?

== Release management ==
?

== Searchlight ==
?

== Sahara ==

All links to all documents are located in here:

https://etherpad.openstack.org/p/sahara-newton-summit

== Swift ==
?

== Tacker ==

Thursday 2016-04-28

Thu 14:20 - 17:40 Development track: https://etherpad.openstack.org/p/tacker-newton-summit

== Tricircle ==
?

== TripleO ==
?

== Trove ==
?

== UX ==
?

== Watcher ==
?

== Zaqar ==
?

Meetings/OpenStackClient

2016-03-31T18:22:34Z

Dtroyer: /* 31 March 2016 */

= Weekly OpenStackClient Team Meeting =

The OpenStackClient Team holds public weekly meetings in <code><nowiki>#openstack-meeting</nowiki></code> on Thursdays at 19:00 UTC ([http://www.timeanddate.com/worldclock/fixedtime.html?hour=19&min=0&sec=0 Timezone Help]). 
Everyone who uses an OpenStack command-line interface is invited to attend.

== Regular attendees ==

Add yourself to this list to be pinged prior to each meeting:

dtroyer, dhellmann, stevemar, terrylhowe, lhcheng, dstanek, MeganR, rtheis, DuncanT, sheel, jgregor, baumann

The meeting minutes of can be found here: [http://eavesdrop.openstack.org/meetings/openstackclient meeting minutes on eavesdrop]

== Next Meeting Agenda ==

''Note: Not all meetings had an advance agenda.''

=== 31 March 2016 ===
* Meeting time change proposal
* Cinder support in OSC (jgregor, baumann, sheel)
** Moving all commands over (filling in gaps)
** Name is not a necessary field in cinder, but is in openstackclient
** Keyword "properties" vs "metadata"
** Using the "volume" keyword before all volume commands
*** Consistency groups - naming convention
*** Snapshots are also used by manilla
* Bugs and Reviews
* Open Discussion

=== 24 Sep 2015 ===
* Remaining Image work
* SDK Integration
** terrylhowe's series for Network: https://review.openstack.org/#/c/138745/
** dtroyer's common refactor, beginning Image: https://review.openstack.org/#/c/227037/
** Version discussion for dependency addition
*** Recent ML discussion: http://lists.openstack.org/pipermail/openstack-dev/2015-September/075107.html
* Bugs and Reviews
* Open Discussion

=== 6 August 2015 ===
* Discussed making 1.6.0 release

=== 16 July 2015 ===
* Make a consistent functional test, identity vs others, pretty table vs not

=== 04 Jun 2015 ===
* Open actions
** https://bugs.launchpad.net/python-openstackclient/+bug/1405562
*** Amey Bhide is making good progress on this
** https://bugs.launchpad.net/python-openstackclient/+bug/1459519
*** Terry has https://review.openstack.org/#/c/186394/ in cliff (now approved)
** Plugins - osc-plugin to cookiecutter
*** dtroyer: no movement
* Releases
** 1.4.0 release any minute now, was going to be a point release but the EC2 credentials fixes included adding v3 commands
** Still waiting on requirements update for KSC, in gate queue: https://review.openstack.org/#/c/188078/ (now merged)
* Blueprint Review
* Bugs/Reviews
* Open discussion

=== 28 May 2015 ===
* Open actions
* Blueprint Review
* Bugs/Reviews
* Open discussion

=== 07 May 2015 ===
* Open actions
* Summit planning
** [https://etherpad.openstack.org/p/osc-liberty-summit-planning Etherpad]
* Bugs/Reviews
* Open discussion

=== 30 Apr 2015 ===
* Open actions
* Release planning
** 1.2.0 release today - [https://launchpad.net/python-openstackclient/+milestone/m10 milestone m10]
* Summit planning
** [https://etherpad.openstack.org/p/osc-liberty-summit-planning Etherpad]
* Bugs/Reviews
* Open discussion

=== 23 Apr 2015 ===
* Open actions
* Release planning
** 1.1.0 released on 21Apr2015 - [https://launchpad.net/python-openstackclient/+milestone/m9 milestone m9]
** follow-up soon with 1.1.1 to clean up release notes and get in a few more bug fixes - [https://launchpad.net/python-openstackclient/+milestone/m10 nilestone m10]
* Summit planning
** [https://etherpad.openstack.org/p/osc-liberty-summit-planning Etherpad]
* Bugs
** [https://bugs.launchpad.net/python-openstackclient/+bug/1443089 1443089] - image list displays a maximum of 25 images
*** is this fixed by [https://review.openstack.org/#/c/173420/ review 173420]?
* Open discussion

=== 16 Apr 2015 ===
* Open actions
* Summit planning
* Reviews
** [https://review.openstack.org/#/c/164091/ 164091] - session timing
* Bugs
** [https://bugs.launchpad.net/python-openstackclient/+bug/1406470 1406470] - track backwards incompatible changes
*** Suggested to use a commit message tag
** [https://bugs.launchpad.net/python-openstackclient/+bug/1409218 1409218] - condense credentials (ec2, v3, compute)
*** still m9?
** [https://bugs.launchpad.net/python-openstackclient/+bug/1435962 1435962] - add support for keystone service providers
*** [https://review.openstack.org/#/c/165755/ review 165755]
*** has this been released in KSC yet?
** [https://bugs.launchpad.net/python-openstackclient/+bug/1443089 1443089] - image list displays a maximum of 25 images
*** recent discussion on how to handle:
**** add --limit (or other option)
**** just do the pagination to return all
**** both of the above
** [https://bugs.launchpad.net/python-openstackclient/+bug/1431649 1431649] - openstackclient is really slow
*** static import timing done with boris-42's profimp, addressed some in [https://review.openstack.org/173098 review 173098]
* Blueprints
** New: [https://blueprints.launchpad.net/python-openstackclient/+spec/waitcommand wait command]
* Open discussion

=== 09 Apr 2015 ===
* Open actions
* Open discussion

=== 02 Apr 2015 ===
* Open actions
** stevemar: BP to move fakes to fixtures for plugin testing
** dtroyer: BP to generalize JSON input
** dtroyer: add timing info to https://bugs.launchpad.net/python-openstackclient/+bug/1431649
** dtroyer: ML tag - OSC is registered
* Summit space
** what do we want/need? I asked ttx for one fishbowl and one workroom slot each, do we need them both?
*** https://wiki.openstack.org/wiki/Summit/Planning
* Review Review
** --os-cloud (https://review.openstack.org/129795)
* Bug Review
* Other repos
** os-client-config renamed last week
* Open Discussion

=== 19 Mar 2015 ===
* Open actions
** dtroyer: contributors list
* Public test interfaces
** Question about plugins using fakes from openstackclient.tests, public status undefined before now
* Bug Review
** Priorities for next release
* Other repos
** ACL changes in Gerrit made for cliff and os-client-config
* Open discussion

=== 12 Mar 2015 ===
* Open actions
** Project proposal submitted: https://review.openstack.org/#/c/161885/
* Release plans
* Bug Review
* Other repos
** cliff
** os-client-config
* Open discussion

=== 05 Mar 2015 ===
* Re-confirm meeting time from Doodle results (http://doodle.com/4uy5w2ehn8y2eayh)
* Open actions
** dhellmann set up doodle for meeting times (done)
** dtroyer to add cliff repo ownership to project proposal (done)
** dhellmann discuss cliff ownership change with oslo team (done)
* Project status
** Project requirement evaluation: [https://etherpad.openstack.org/p/osc-project etherpad]
** cliff repo ownership resolution
** Also add os-client-config repo
* Release schedule
** Possibly early next week (09 Mar 2015)
** propose 1.1.0 as new --os-cloud support adds interesting new capability
* Bug review
** Evaluate what can be completed before release and what should be deferred
* Open discussion

=== 26 Feb 2015 ===
* Confirm meeting time
* Project status
** Project requirement evaluation: [https://etherpad.openstack.org/p/osc-project etherpad]
** Should this project also own the cliff repo?
* Release schedule
* Bug review
* Open discussion

OpenStackClient/Commands

2016-03-23T17:26:33Z

Dtroyer: Replaced content with "''[Note: The former content of this page was removed on 23Mar2016 as it was over 15 months out of date. The current information that was formerly on this page can be foun..."

''[Note: The former content of this page was removed on 23Mar2016 as it was over 15 months out of date. The current information that was formerly on this page can be found at [http://docs.openstack.org/developer/python-openstackclient/command-list.html OpenStack Documentation]'']

Design Summit/Mitaka/Etherpads

2015-10-15T21:33:13Z

Dtroyer:

[[Category:Summit]]
[[Category:Liberty]]
[[Category:Etherpad]]

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
__TOC__
</div>
== Event intro/closure ==
* Tue 11:15: Design Summit 101 [https://etherpad.openstack.org/p/mitaka-design-summit-101]
* Fri 12:30: Design Summit feedback [https://etherpad.openstack.org/p/mitaka-design-summit-feedback]

== Cinder ==
* Wed 14.00: Why fight it, Cinder could/should be the next ViPR [https://etherpad.openstack.org/p/mitaka-cinder-direction]
* Wed 14.50: Availability zones in Cinder [https://etherpad.openstack.org/p/mitaka-cinder-az]
* Thur 9.00: Experimental APIs and Microversions [https://etherpad.openstack.org/p/mitaka-cinder-experimental-apis]
* Thur 9.50: Cinder Nova Interaction [https://etherpad.openstack.org/p/mitaka-cinder-nova-interaction]
* Thur 13.50: Cinder driver interface [https://etherpad.openstack.org/p/mitaka-cinder-driver-interface]
* Thur 14.40: API Microversions [https://etherpad.openstack.org/p/mitaka-cinder-api-microversions]
* Thur 15.30: ABC work [https://etherpad.openstack.org/p/mitaka-cinder-abc-work]
* Thur 15.30: Driver deadlines [https://etherpad.openstack.org/p/mitaka-cinder-driver-deadlines]
* Thur 16.30: C-Vol Active/Active HA [https://etherpad.openstack.org/p/mitaka-cinder-cvol-aa]
* Thur 17.20: Volume manager locks [https://etherpad.openstack.org/p/mitaka-cinder-volmgr-locks]
* Fri: Contributor Meetup [https://etherpad.openstack.org/p/mitaka-cinder-contributor-meetup]

== Congress ==
* Wed 2:00: [https://etherpad.openstack.org/p/congress-mitaka-arch Distributed architecture and additional features for Mitaka]
* Wed 2:50: [https://etherpad.openstack.org/p/congress-mitaka-integrations Integration with other projects: congress gating (murano, nova, neutron, etc.), keystone]
* Wed 3:40: [https://etherpad.openstack.org/p/congress-mitaka-external Discussions with external teams: OPNFV, Monasca]

== Cross-Project workshops ==

All sessions are on Tuesday 2015-10-27

* 11:15
** Cycle themes [https://etherpad.openstack.org/p/mitaka-crossproject-themes]
* 12:05
** Supporting DefCore and Interoperability Testing [https://etherpad.openstack.org/p/mitaka-crossproject-defcore]
** Tags today and tomorrow [https://etherpad.openstack.org/p/mitaka-crossproject-next-tags]
* 14:50
** Role Assignments for Service users [https://etherpad.openstack.org/p/mitaka-cross-project-role-assignment-service-user]
* 15:40
** Documenting the OpenStack way [https://etherpad.openstack.org/p/mitaka-crossproject-doc-the-way]
* 16:40
** Troubleshooting cross-project comms [https://etherpad.openstack.org/p/mitaka-crossproject-comms]
* 17:30
** Serving extreme use cases [https://etherpad.openstack.org/p/mitaka-crossproject-extreme-usecases]

== Ceilometer ==
* Wednesday, 2015-08-28
** 11:15 - [https://etherpad.openstack.org/p/mitaka-telemetry-alarms alams]
** 12:05 - [https://etherpad.openstack.org/p/mitaka-telemetry-ui visualising data]
** 14:50 - [https://etherpad.openstack.org/p/mitaka-telemetry-upgrades rolling upgrades]
** 15:40 - [https://etherpad.openstack.org/p/mitaka-telemetry-split componentisation]

* Thursday, 2015-08-29
** 09:00 - [https://etherpad.openstack.org/p/mitaka-telemetry-testing functional and integration testing]
** 09ː50 - [https://etherpad.openstack.org/p/mitaka-telemetry-bi business intelligence]
** 11ː00 - [https://etherpad.openstack.org/p/mitaka-telemetry-polling refined polling]
** 11ː50 - [https://etherpad.openstack.org/p/mitaka-telemetry-cross-project project data ownership]
** 13ː50 - [https://etherpad.openstack.org/p/mitaka-telemetry-alarms event alarms]

* Friday, 2015-08-30
** 09:00 - [https://etherpad.openstack.org/p/mitaka-telemetry-contributors-meetup contributors meetup]

== Designate ==

* Wed 11:15: Roadmap https://etherpad.openstack.org/p/mitaka-designate-summit-roadmap
* Wed 12:05: Alias Records https://etherpad.openstack.org/p/mitaka-designate-summit-alias
* Wed 14:00: Batch API Actions https://etherpad.openstack.org/p/mitaka-designate-summit-batch-api
* Wed 14:50: Embedable Services https://etherpad.openstack.org/p/mitaka-designate-summit-embeddable-services
* Wed 16:40: Incremental Zone Transfer (IFXR) https://etherpad.openstack.org/p/mitaka-designate-summit-ifxr
* Fri 14:00: Contributors Meetup https://etherpad.openstack.org/p/mitaka-designate-summit-meetup

== Nova ==

* Wed 11:15: REST API https://etherpad.openstack.org/p/mitaka-nova-api
* Wed 12:05: Upgrade https://etherpad.openstack.org/p/mitaka-nova-upgrade

* Wed 14:00: Unconference https://etherpad.openstack.org/p/mitaka-nova-unconference
* Wed 14:50: OS VIF lib https://etherpad.openstack.org/p/mitaka-nova-os-vif-lib
* Wed 15:40: Resources and Flavors https://etherpad.openstack.org/p/mitaka-nova-resource-modeling
* Wed 16:40: Resources and Flavors (continued) https://etherpad.openstack.org/p/mitaka-nova-resource-modeling
* Wed 17:30: SR-IOV https://etherpad.openstack.org/p/mitaka-nova-sr-iov

* Thurs 09:00: Cells v2 https://etherpad.openstack.org/p/mitaka-nova-cells
* Thurs 9:50: see Cinder track
* Thurs 11:00: Scheduler https://etherpad.openstack.org/p/mitaka-nova-scheduler
* Thurs 11:50: see Ironic track

* Thurs 13:50: Unconference https://etherpad.openstack.org/p/mitaka-nova-unconference
* Thurs 14:40: Error handling https://etherpad.openstack.org/p/mitaka-nova-error-handling
* Thurs 15:30: Cross Service issues: Server locking, token refresh, Instance users https://etherpad.openstack.org/p/mitaka-nova-service-users
* Thurs 16:30: Mitaka Priorities https://etherpad.openstack.org/p/mitaka-nova-priorities
* Thurs 17:20: Unconference https://etherpad.openstack.org/p/mitaka-nova-unconference

* Fri: 09:00 and 14:00: Nova contributors meetup https://etherpad.openstack.org/p/mitaka-nova-summit-meetup

== Manila ==
* Wed 11:15 - 11:55: (WS) Migration Improvements https://etherpad.openstack.org/p/mitaka-manila-migration-improvements
* Wed 12:05 - 12:45: (WS) Access Allow/Deny Driver Interface https://etherpad.openstack.org/p/mitaka-manila-allow-deny
* Thu 11:00 - 11:40: (FB) Share Replication https://etherpad.openstack.org/p/mitaka-manila-replication
* Thu 11:50 - 12:30: (FB) Alternative Snapshot Semantics https://etherpad.openstack.org/p/mitaka-manila-snapshot-semantics
* Thu 14:40 - 15:20: (WS) Export Location Metadata https://etherpad.openstack.org/p/mitaka-manila-export-location-metadata
* Thu 15:30 - 16:10: (WS) Interactions Between New Features https://etherpad.openstack.org/p/mitaka-manila-feature-interactions
* Fri 09:00 - 12:30: (CM) Contributor Meetup https://etherpad.openstack.org/p/mitaka-manila-contributor-meetup

== Release management ==
* Thu 15:30: Mitaka process changes [https://etherpad.openstack.org/p/mitaka-relmgt-process-changes]
* Thu 16:30: Work session: the Mitaka plan [https://etherpad.openstack.org/p/mitaka-relmgt-plan]

== Puppet OpenStack ==
* General etherpadː https://etherpad.openstack.org/p/HND-puppet
* Wed 2 pm: Code design sessionː https://etherpad.openstack.org/p/HND-puppet-code
* Wed 2.50 pm: Code design sessionː https://etherpad.openstack.org/p/HND-puppet-code
* Thu 1.50 pm: Community feedbackː https://etherpad.openstack.org/p/HND-puppet-community
* Thu 2.40 pm: CI and documentationː https://etherpad.openstack.org/p/HND-puppet-ci and https://etherpad.openstack.org/p/HND-puppet-doc
* Thu 4.30 pm: Code design sessionː https://etherpad.openstack.org/p/HND-puppet-code

== Ironic ==
* The everything etherpad: https://etherpad.openstack.org/p/summit-mitaka-ironic
* Wednesday fishbowl DS3 2:00-2:40 https://etherpad.openstack.org/p/summit-mitaka-ironic-third-party-ci
* Wednesday fishbowl DS3 2:50-3:30 https://etherpad.openstack.org/p/summit-mitaka-ironic-group-management
* Thursday workroom DS10 9:00-9:40 https://etherpad.openstack.org/p/summit-mitaka-ironic-notifications-bus
* Thursday workroom DS10 9:50-10:30 https://etherpad.openstack.org/p/summit-mitaka-ironic-driver-composition
* Thursday fishbowl DS3 11:00-11:40 https://etherpad.openstack.org/p/summit-mitaka-ironic-driver-api
* Thursday fishbowl DS3 11:50-12:30 https://etherpad.openstack.org/p/summit-mitaka-ironic-nova-driver (joint session with Nova)
* Thursday workroom DS11 4:30-5:10 https://etherpad.openstack.org/p/summit-mitaka-ironic-lock-manager
* Thursday workroom DS11 5:20-6:00 https://etherpad.openstack.org/p/summit-mitaka-ironic-gate-improvements
* Friday workroom DS15 9:00-12:30 https://etherpad.openstack.org/p/summit-mitaka-ironic-contributors-meetup (shared space with Infra)

== Heat ==
* The everything etherpad: https://etherpad.openstack.org/p/mitaka-heat-sessions
'''Wed'''
* 11:15 - 11:55: [https://etherpad.openstack.org/p/mitaka-heat-documentation (W) Documentation improvements]
* 12:05 - 12:45: [https://etherpad.openstack.org/p/mitaka-heat-tests (W) Heat tests]
* 14:00 - 14:40: [https://etherpad.openstack.org/p/mitaka-heat-convergence-migration (W) Tool to migrate stacks to/from convergence]
* 14:50 - 15:30: [https://etherpad.openstack.org/p/mitaka-heat-large-stacks (F) Issues from deploying very large stacks]
* 15:40 - 16:20: [https://etherpad.openstack.org/p/mitaka-heat-user-ops (F) User/ops session for summit ]
'''Thu'''
* 09:00 - 09:40: [https://etherpad.openstack.org/p/mitaka-heat-autoscaling (W) AutoScaling/Group architecture/roadmap]
* 09:50 - 10:30: [https://etherpad.openstack.org/p/mitaka-heat-break-stack-barrier (W) Breaking the stack barrier]
* 11:00 - 11:40: [https://etherpad.openstack.org/p/mitaka-heat-composition-improvements (F) Composition improvements ]
* 11:50 - 12:30: [https://etherpad.openstack.org/p/mitaka-heat-openstackclient (F) Complete heat support in python-openstackclient ]
* 13:50 - 14:30: [https://etherpad.openstack.org/p/mitaka-heat-hooks-notifications (W) Hooks & Notifications ]
* 14:40 - 15:20: [https://etherpad.openstack.org/p/mitaka-heat-convergence-ph1 (W) Convergence Phase 1 results]
* 15:30 - 16:10: [https://etherpad.openstack.org/p/mitaka-heat-convergence-ph2 (W) Convergence Phase 2 start]
'''Fri'''
* 09:00 - 12:30: [https://etherpad.openstack.org/p/mitaka-heat-summit-meetup Contributor Meetup]

== OpenStack Chef ==
* general discussion: https://etherpad.openstack.org/p/mitaka-openstack-chef-general
* defining the refactoring process: https://etherpad.openstack.org/p/mitaka-openstack-chef-refactoring

== OpenStackClient ==
* Wed 16:40 - 17:20: [https://etherpad.openstack.org/p/tokyo-osc-session Near-term Roadmap]
* Fri 09:00 - 12:30: [https://etherpad.openstack.org/p/tokyo-osc-meetup Meetup]

Meetings/OpenStackClient

2015-09-24T14:34:56Z

Dtroyer: /* Next Meeting Agenda */

= Weekly OpenStackClient Team Meeting =

The OpenStackClient Team holds public weekly meetings in <code><nowiki>#openstack-meeting</nowiki></code> on Thursdays at 19:00 UTC ([http://www.timeanddate.com/worldclock/fixedtime.html?hour=19&min=0&sec=0 Timezone Help]). 
Everyone who uses an OpenStack command-line interface is invited to attend.

== Regular attendees ==

Add yourself to this list to be pinged prior to each meeting:

dtroyer, dhellmann, stevemar, briancurtin, terrylhowe, lhcheng, sigmavirus24

The meeting minutes of can be found here: [http://eavesdrop.openstack.org/meetings/openstackclient meeting minutes on eavesdrop]

== Next Meeting Agenda ==

''Note: Not all meetings had an advance agenda.''

=== 24 Sep 2015 ===
* Remaining Image work
* SDK Integration
** terrylhowe's series for Network: https://review.openstack.org/#/c/138745/
** dtroyer's common refactor, beginning Image: https://review.openstack.org/#/c/227037/
** Version discussion for dependency addition
*** Recent ML discussion: http://lists.openstack.org/pipermail/openstack-dev/2015-September/075107.html
* Bugs and Reviews
* Open Discussion

=== 6 August 2015 ===
* Discussed making 1.6.0 release

=== 16 July 2015 ===
* Make a consistent functional test, identity vs others, pretty table vs not

=== 04 Jun 2015 ===
* Open actions
** https://bugs.launchpad.net/python-openstackclient/+bug/1405562
*** Amey Bhide is making good progress on this
** https://bugs.launchpad.net/python-openstackclient/+bug/1459519
*** Terry has https://review.openstack.org/#/c/186394/ in cliff (now approved)
** Plugins - osc-plugin to cookiecutter
*** dtroyer: no movement
* Releases
** 1.4.0 release any minute now, was going to be a point release but the EC2 credentials fixes included adding v3 commands
** Still waiting on requirements update for KSC, in gate queue: https://review.openstack.org/#/c/188078/ (now merged)
* Blueprint Review
* Bugs/Reviews
* Open discussion

=== 28 May 2015 ===
* Open actions
* Blueprint Review
* Bugs/Reviews
* Open discussion

=== 07 May 2015 ===
* Open actions
* Summit planning
** [https://etherpad.openstack.org/p/osc-liberty-summit-planning Etherpad]
* Bugs/Reviews
* Open discussion

=== 30 Apr 2015 ===
* Open actions
* Release planning
** 1.2.0 release today - [https://launchpad.net/python-openstackclient/+milestone/m10 milestone m10]
* Summit planning
** [https://etherpad.openstack.org/p/osc-liberty-summit-planning Etherpad]
* Bugs/Reviews
* Open discussion

=== 23 Apr 2015 ===
* Open actions
* Release planning
** 1.1.0 released on 21Apr2015 - [https://launchpad.net/python-openstackclient/+milestone/m9 milestone m9]
** follow-up soon with 1.1.1 to clean up release notes and get in a few more bug fixes - [https://launchpad.net/python-openstackclient/+milestone/m10 nilestone m10]
* Summit planning
** [https://etherpad.openstack.org/p/osc-liberty-summit-planning Etherpad]
* Bugs
** [https://bugs.launchpad.net/python-openstackclient/+bug/1443089 1443089] - image list displays a maximum of 25 images
*** is this fixed by [https://review.openstack.org/#/c/173420/ review 173420]?
* Open discussion

=== 16 Apr 2015 ===
* Open actions
* Summit planning
* Reviews
** [https://review.openstack.org/#/c/164091/ 164091] - session timing
* Bugs
** [https://bugs.launchpad.net/python-openstackclient/+bug/1406470 1406470] - track backwards incompatible changes
*** Suggested to use a commit message tag
** [https://bugs.launchpad.net/python-openstackclient/+bug/1409218 1409218] - condense credentials (ec2, v3, compute)
*** still m9?
** [https://bugs.launchpad.net/python-openstackclient/+bug/1435962 1435962] - add support for keystone service providers
*** [https://review.openstack.org/#/c/165755/ review 165755]
*** has this been released in KSC yet?
** [https://bugs.launchpad.net/python-openstackclient/+bug/1443089 1443089] - image list displays a maximum of 25 images
*** recent discussion on how to handle:
**** add --limit (or other option)
**** just do the pagination to return all
**** both of the above
** [https://bugs.launchpad.net/python-openstackclient/+bug/1431649 1431649] - openstackclient is really slow
*** static import timing done with boris-42's profimp, addressed some in [https://review.openstack.org/173098 review 173098]
* Blueprints
** New: [https://blueprints.launchpad.net/python-openstackclient/+spec/waitcommand wait command]
* Open discussion

=== 09 Apr 2015 ===
* Open actions
* Open discussion

=== 02 Apr 2015 ===
* Open actions
** stevemar: BP to move fakes to fixtures for plugin testing
** dtroyer: BP to generalize JSON input
** dtroyer: add timing info to https://bugs.launchpad.net/python-openstackclient/+bug/1431649
** dtroyer: ML tag - OSC is registered
* Summit space
** what do we want/need? I asked ttx for one fishbowl and one workroom slot each, do we need them both?
*** https://wiki.openstack.org/wiki/Summit/Planning
* Review Review
** --os-cloud (https://review.openstack.org/129795)
* Bug Review
* Other repos
** os-client-config renamed last week
* Open Discussion

=== 19 Mar 2015 ===
* Open actions
** dtroyer: contributors list
* Public test interfaces
** Question about plugins using fakes from openstackclient.tests, public status undefined before now
* Bug Review
** Priorities for next release
* Other repos
** ACL changes in Gerrit made for cliff and os-client-config
* Open discussion

=== 12 Mar 2015 ===
* Open actions
** Project proposal submitted: https://review.openstack.org/#/c/161885/
* Release plans
* Bug Review
* Other repos
** cliff
** os-client-config
* Open discussion

=== 05 Mar 2015 ===
* Re-confirm meeting time from Doodle results (http://doodle.com/4uy5w2ehn8y2eayh)
* Open actions
** dhellmann set up doodle for meeting times (done)
** dtroyer to add cliff repo ownership to project proposal (done)
** dhellmann discuss cliff ownership change with oslo team (done)
* Project status
** Project requirement evaluation: [https://etherpad.openstack.org/p/osc-project etherpad]
** cliff repo ownership resolution
** Also add os-client-config repo
* Release schedule
** Possibly early next week (09 Mar 2015)
** propose 1.1.0 as new --os-cloud support adds interesting new capability
* Bug review
** Evaluate what can be completed before release and what should be deferred
* Open discussion

=== 26 Feb 2015 ===
* Confirm meeting time
* Project status
** Project requirement evaluation: [https://etherpad.openstack.org/p/osc-project etherpad]
** Should this project also own the cliff repo?
* Release schedule
* Bug review
* Open discussion

Meetings/OpenStackClient

2015-09-24T14:33:57Z

Dtroyer: /* Next Meeting Agenda */

= Weekly OpenStackClient Team Meeting =

The OpenStackClient Team holds public weekly meetings in <code><nowiki>#openstack-meeting</nowiki></code> on Thursdays at 19:00 UTC ([http://www.timeanddate.com/worldclock/fixedtime.html?hour=19&min=0&sec=0 Timezone Help]). 
Everyone who uses an OpenStack command-line interface is invited to attend.

== Regular attendees ==

Add yourself to this list to be pinged prior to each meeting:

dtroyer, dhellmann, stevemar, briancurtin, terrylhowe, lhcheng, sigmavirus24

The meeting minutes of can be found here: [http://eavesdrop.openstack.org/meetings/openstackclient meeting minutes on eavesdrop]

== Next Meeting Agenda ==

''Note: Not all meetings had an advance agenda.''

=== 24 Sep 2015 ===
* Remaining Image work
* SDK Integration
* terrylhowe's series for Network: https://review.openstack.org/#/c/138745/
* dtroyer's common refactor, beginning Image: https://review.openstack.org/#/c/227037/
* Version discussion for dependency addition
* Recent ML discussion: http://lists.openstack.org/pipermail/openstack-dev/2015-September/075107.html
* Bugs and Reviews
* Open Discussion

=== 6 August 2015 ===
* Discussed making 1.6.0 release

=== 16 July 2015 ===
* Make a consistent functional test, identity vs others, pretty table vs not

=== 04 Jun 2015 ===
* Open actions
** https://bugs.launchpad.net/python-openstackclient/+bug/1405562
*** Amey Bhide is making good progress on this
** https://bugs.launchpad.net/python-openstackclient/+bug/1459519
*** Terry has https://review.openstack.org/#/c/186394/ in cliff (now approved)
** Plugins - osc-plugin to cookiecutter
*** dtroyer: no movement
* Releases
** 1.4.0 release any minute now, was going to be a point release but the EC2 credentials fixes included adding v3 commands
** Still waiting on requirements update for KSC, in gate queue: https://review.openstack.org/#/c/188078/ (now merged)
* Blueprint Review
* Bugs/Reviews
* Open discussion

=== 28 May 2015 ===
* Open actions
* Blueprint Review
* Bugs/Reviews
* Open discussion

=== 07 May 2015 ===
* Open actions
* Summit planning
** [https://etherpad.openstack.org/p/osc-liberty-summit-planning Etherpad]
* Bugs/Reviews
* Open discussion

=== 30 Apr 2015 ===
* Open actions
* Release planning
** 1.2.0 release today - [https://launchpad.net/python-openstackclient/+milestone/m10 milestone m10]
* Summit planning
** [https://etherpad.openstack.org/p/osc-liberty-summit-planning Etherpad]
* Bugs/Reviews
* Open discussion

=== 23 Apr 2015 ===
* Open actions
* Release planning
** 1.1.0 released on 21Apr2015 - [https://launchpad.net/python-openstackclient/+milestone/m9 milestone m9]
** follow-up soon with 1.1.1 to clean up release notes and get in a few more bug fixes - [https://launchpad.net/python-openstackclient/+milestone/m10 nilestone m10]
* Summit planning
** [https://etherpad.openstack.org/p/osc-liberty-summit-planning Etherpad]
* Bugs
** [https://bugs.launchpad.net/python-openstackclient/+bug/1443089 1443089] - image list displays a maximum of 25 images
*** is this fixed by [https://review.openstack.org/#/c/173420/ review 173420]?
* Open discussion

=== 16 Apr 2015 ===
* Open actions
* Summit planning
* Reviews
** [https://review.openstack.org/#/c/164091/ 164091] - session timing
* Bugs
** [https://bugs.launchpad.net/python-openstackclient/+bug/1406470 1406470] - track backwards incompatible changes
*** Suggested to use a commit message tag
** [https://bugs.launchpad.net/python-openstackclient/+bug/1409218 1409218] - condense credentials (ec2, v3, compute)
*** still m9?
** [https://bugs.launchpad.net/python-openstackclient/+bug/1435962 1435962] - add support for keystone service providers
*** [https://review.openstack.org/#/c/165755/ review 165755]
*** has this been released in KSC yet?
** [https://bugs.launchpad.net/python-openstackclient/+bug/1443089 1443089] - image list displays a maximum of 25 images
*** recent discussion on how to handle:
**** add --limit (or other option)
**** just do the pagination to return all
**** both of the above
** [https://bugs.launchpad.net/python-openstackclient/+bug/1431649 1431649] - openstackclient is really slow
*** static import timing done with boris-42's profimp, addressed some in [https://review.openstack.org/173098 review 173098]
* Blueprints
** New: [https://blueprints.launchpad.net/python-openstackclient/+spec/waitcommand wait command]
* Open discussion

=== 09 Apr 2015 ===
* Open actions
* Open discussion

=== 02 Apr 2015 ===
* Open actions
** stevemar: BP to move fakes to fixtures for plugin testing
** dtroyer: BP to generalize JSON input
** dtroyer: add timing info to https://bugs.launchpad.net/python-openstackclient/+bug/1431649
** dtroyer: ML tag - OSC is registered
* Summit space
** what do we want/need? I asked ttx for one fishbowl and one workroom slot each, do we need them both?
*** https://wiki.openstack.org/wiki/Summit/Planning
* Review Review
** --os-cloud (https://review.openstack.org/129795)
* Bug Review
* Other repos
** os-client-config renamed last week
* Open Discussion

=== 19 Mar 2015 ===
* Open actions
** dtroyer: contributors list
* Public test interfaces
** Question about plugins using fakes from openstackclient.tests, public status undefined before now
* Bug Review
** Priorities for next release
* Other repos
** ACL changes in Gerrit made for cliff and os-client-config
* Open discussion

=== 12 Mar 2015 ===
* Open actions
** Project proposal submitted: https://review.openstack.org/#/c/161885/
* Release plans
* Bug Review
* Other repos
** cliff
** os-client-config
* Open discussion

=== 05 Mar 2015 ===
* Re-confirm meeting time from Doodle results (http://doodle.com/4uy5w2ehn8y2eayh)
* Open actions
** dhellmann set up doodle for meeting times (done)
** dtroyer to add cliff repo ownership to project proposal (done)
** dhellmann discuss cliff ownership change with oslo team (done)
* Project status
** Project requirement evaluation: [https://etherpad.openstack.org/p/osc-project etherpad]
** cliff repo ownership resolution
** Also add os-client-config repo
* Release schedule
** Possibly early next week (09 Mar 2015)
** propose 1.1.0 as new --os-cloud support adds interesting new capability
* Bug review
** Evaluate what can be completed before release and what should be deferred
* Open discussion

=== 26 Feb 2015 ===
* Confirm meeting time
* Project status
** Project requirement evaluation: [https://etherpad.openstack.org/p/osc-project etherpad]
** Should this project also own the cliff repo?
* Release schedule
* Bug review
* Open discussion

Stackforge Namespace Retirement

2015-09-22T16:10:59Z

Dtroyer: /* Active Projects to Move */

=== Background ===

The stackforge/ git namespace is being retired, and active projects are being moved to the openstack/ namespace. See this mailing list post for [http://lists.openstack.org/pipermail/openstack-dev/2015-August/071816.html full background]. These changes are scheduled to occur on October 17, 2015.

There are two lists below, one for active projects that should be moved, and a second for inactive projects that should become read-only. Please update them to add your project to the correct list.

=== Active Projects to Move ===
Active stackforge projects that wish to move into the openstack/ namespace should be added to this list. Projects in this list will be automatically moved by the Infrastructure team to openstack/ on October 17. Please note that no other renames can happen during this move -- projects will strictly be moved from stackforge/ to openstack/ with their existing names.

* ec2-api
* gce-api
* aeromancer
* cloud-init
* cloudbase-init
* python-openstacksdk
* networking-hyperv
* networking-zvm
* namos
* ceilometer-zvm
* compute-hyperv
* ospurge
* nova-zvm-virt-driver
* telcowg-usecases
* anvil
* doc8
* vmtp
* wsme
* tacker
* tacker-specs
* tacker-horizon
* puppet-autossh
* puppet-setproxy
* python-tackerclient
* third-party-ci-tools
* terracotta
* sqlalchemy-migrate
* senlin
* python-senlinclient
* senlin-dashboard
* packstack
* tricircle
* networking-ovs-dpdk
* intel-nfv-ci-tests
* fuel-octane
* fuel-plugin-ha-fencing
* python-fuelclient
* yaql
* fuel-plugin-lma-collector
* fuel-plugin-lma-infrastructure-alerting
* fuel-plugin-elasticsearch-kibana
* fuel-plugin-influxdb-grafana
* fuel-plugin-midonet
* fuel-plugin-mellanox
* fuel-plugin-ceilometer-redis
* git-upstream
* blazar
* python-blazarclient
* blazar-nova
* fuel-plugin-calico
* merlin
* fuel-plugin-swiftstack
* swift3
* fuel-plugin-vmware-dvs
* nova-docker
* stackalytics
* driverlog
* shaker
* compass-adaptors
* compass-core
* compass-specs
* compass-web
* cloudpulse
* python-cloudpulseclient
* nova-powervm
* ceilometer-powervm
* fuel-plugin-tintri-cinder
* fuel-plugin-opendaylight
* fuel-plugin-zabbix-monitoring-extreme-networks
* fuel-plugin-external-zabbix
* fuel-plugin-zabbix-monitoring-emc
* fuel-plugin-zabbix-snmptrapd
* fuel-plugin-external-emc
* cloudkitty
* python-cloudkittyclient
* cloudkitty-dashboard
* golang-client

=== Inactive Projects to Retire ===
Inactive projects that should be retired should be added to this list. These projects will have a commit merged removing their content and replacing it with a message indicating the project is no longer maintained and will become read-only in Gerrit.

* MRaaS
* openstackdroid
* rubick

Meetings/OpenStackClient

2015-06-04T18:54:07Z

Dtroyer: /* 04 Jun 2015 */

= Weekly OpenStackClient Team Meeting =

The OpenStackClient Team holds public weekly meetings in <code><nowiki>#openstack-meeting</nowiki></code> on Thursdays at 19:00 UTC ([http://www.timeanddate.com/worldclock/fixedtime.html?hour=19&min=0&sec=0 Timezone Help]). 
Everyone who uses an OpenStack command-line interface is invited to attend.

== Regular attendees ==

Add yourself to this list to be pinged prior to each meeting:

dtroyer, dhellmann, stevemar, briancurtin, terrylhowe, lhcheng, sigmavirus24

The meeting minutes of can be found here: [http://eavesdrop.openstack.org/meetings/openstackclient meeting minutes on eavesdrop]

== Next Meeting Agenda ==

''Note: No meetings scheduled for 14 May 2015 and 21 May 2015''

=== 04 Jun 2015 ===
* Open actions
** https://bugs.launchpad.net/python-openstackclient/+bug/1405562
*** Amey Bhide is making good progress on this
** https://bugs.launchpad.net/python-openstackclient/+bug/1459519
*** Terry has https://review.openstack.org/#/c/186394/ in cliff (now approved)
** Plugins - osc-plugin to cookiecutter
*** dtroyer: no movement
* Releases
** 1.4.0 release any minute now, was going to be a point release but the EC2 credentials fixes included adding v3 commands
** Still waiting on requirements update for KSC, in gate queue: https://review.openstack.org/#/c/188078/ (now merged)
* Blueprint Review
* Bugs/Reviews
* Open discussion

=== 28 May 2015 ===
* Open actions
* Blueprint Review
* Bugs/Reviews
* Open discussion

=== 07 May 2015 ===
* Open actions
* Summit planning
** [https://etherpad.openstack.org/p/osc-liberty-summit-planning Etherpad]
* Bugs/Reviews
* Open discussion

=== 30 Apr 2015 ===
* Open actions
* Release planning
** 1.2.0 release today - [https://launchpad.net/python-openstackclient/+milestone/m10 milestone m10]
* Summit planning
** [https://etherpad.openstack.org/p/osc-liberty-summit-planning Etherpad]
* Bugs/Reviews
* Open discussion

=== 23 Apr 2015 ===
* Open actions
* Release planning
** 1.1.0 released on 21Apr2015 - [https://launchpad.net/python-openstackclient/+milestone/m9 milestone m9]
** follow-up soon with 1.1.1 to clean up release notes and get in a few more bug fixes - [https://launchpad.net/python-openstackclient/+milestone/m10 nilestone m10]
* Summit planning
** [https://etherpad.openstack.org/p/osc-liberty-summit-planning Etherpad]
* Bugs
** [https://bugs.launchpad.net/python-openstackclient/+bug/1443089 1443089] - image list displays a maximum of 25 images
*** is this fixed by [https://review.openstack.org/#/c/173420/ review 173420]?
* Open discussion

=== 16 Apr 2015 ===
* Open actions
* Summit planning
* Reviews
** [https://review.openstack.org/#/c/164091/ 164091] - session timing
* Bugs
** [https://bugs.launchpad.net/python-openstackclient/+bug/1406470 1406470] - track backwards incompatible changes
*** Suggested to use a commit message tag
** [https://bugs.launchpad.net/python-openstackclient/+bug/1409218 1409218] - condense credentials (ec2, v3, compute)
*** still m9?
** [https://bugs.launchpad.net/python-openstackclient/+bug/1435962 1435962] - add support for keystone service providers
*** [https://review.openstack.org/#/c/165755/ review 165755]
*** has this been released in KSC yet?
** [https://bugs.launchpad.net/python-openstackclient/+bug/1443089 1443089] - image list displays a maximum of 25 images
*** recent discussion on how to handle:
**** add --limit (or other option)
**** just do the pagination to return all
**** both of the above
** [https://bugs.launchpad.net/python-openstackclient/+bug/1431649 1431649] - openstackclient is really slow
*** static import timing done with boris-42's profimp, addressed some in [https://review.openstack.org/173098 review 173098]
* Blueprints
** New: [https://blueprints.launchpad.net/python-openstackclient/+spec/waitcommand wait command]
* Open discussion

=== 09 Apr 2015 ===
* Open actions
* Open discussion

=== 02 Apr 2015 ===
* Open actions
** stevemar: BP to move fakes to fixtures for plugin testing
** dtroyer: BP to generalize JSON input
** dtroyer: add timing info to https://bugs.launchpad.net/python-openstackclient/+bug/1431649
** dtroyer: ML tag - OSC is registered
* Summit space
** what do we want/need? I asked ttx for one fishbowl and one workroom slot each, do we need them both?
*** https://wiki.openstack.org/wiki/Summit/Planning
* Review Review
** --os-cloud (https://review.openstack.org/129795)
* Bug Review
* Other repos
** os-client-config renamed last week
* Open Discussion

=== 19 Mar 2015 ===
* Open actions
** dtroyer: contributors list
* Public test interfaces
** Question about plugins using fakes from openstackclient.tests, public status undefined before now
* Bug Review
** Priorities for next release
* Other repos
** ACL changes in Gerrit made for cliff and os-client-config
* Open discussion

=== 12 Mar 2015 ===
* Open actions
** Project proposal submitted: https://review.openstack.org/#/c/161885/
* Release plans
* Bug Review
* Other repos
** cliff
** os-client-config
* Open discussion

=== 05 Mar 2015 ===
* Re-confirm meeting time from Doodle results (http://doodle.com/4uy5w2ehn8y2eayh)
* Open actions
** dhellmann set up doodle for meeting times (done)
** dtroyer to add cliff repo ownership to project proposal (done)
** dhellmann discuss cliff ownership change with oslo team (done)
* Project status
** Project requirement evaluation: [https://etherpad.openstack.org/p/osc-project etherpad]
** cliff repo ownership resolution
** Also add os-client-config repo
* Release schedule
** Possibly early next week (09 Mar 2015)
** propose 1.1.0 as new --os-cloud support adds interesting new capability
* Bug review
** Evaluate what can be completed before release and what should be deferred
* Open discussion

=== 26 Feb 2015 ===
* Confirm meeting time
* Project status
** Project requirement evaluation: [https://etherpad.openstack.org/p/osc-project etherpad]
** Should this project also own the cliff repo?
* Release schedule
* Bug review
* Open discussion