Difference between revisions of "StarlingX"
(→StarlingX supporting projects) |
(→StarlingX cross-project initiatives) |
||
Line 148: | Line 148: | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
− | | [[StarlingX/Pyton2|Python2 to Python3 Transition | + | | [[StarlingX/Pyton2|Python2 to Python3 Transition]]|| [[StarlingX/Zull|Zuul Enablement and Coverage]]|| [[StarlingX/Devstack|Devstack Integration]] |
|} | |} | ||
ToDo: | ToDo: | ||
− | * Add cross project initiative (or new project) for Multi-OS support | + | * Add a cross project initiative (or new project) for Multi-OS support |
* Create a Project Map graphic that captures all of this in a graphical way, similar to (or an extension of) the OpenStack project map. | * Create a Project Map graphic that captures all of this in a graphical way, similar to (or an extension of) the OpenStack project map. | ||
Revision as of 18:18, 13 August 2018
Welcome to the StarlingX Project
StarlingX is a fully featured and high performance Edge Cloud software stack that is based on the 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.
DocumentationThese three documents will help get you started building, installing, and validating your installation of StarlingX: CodeThe StarlingX project uses Gerrit as its web-based code change management and review tool.
Story and Bug TrackingWe 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 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 here. Sample queries:
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.
References
OpenStack DocumentationThese are references to general OpenStack material:
GovernanceA very preliminary Governance document can be found here. |
CultureWe are proud to be an OpenStack Foundation project!
MeetingsWeekly calls
Call details
Agenda and meeting minutesThe agenda and notes for each call are kept in Etherpads: Please feel free to add items to the agendas for these meetings. PTG MeetingsWe are preparing for the Denver OpenStack PTG meeting. Draft agenda items can be found here: Status and PlanningThis section is under construction. Overall project planning pages
StarlingX ProjectsStarlingX 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 here StarlingX main projectsInformation on the main StarlingX development projects can be found on the wiki pages below:
StarlingX supporting projectsIn 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.
StarlingX cross-project initiativesThere are several initiatives we are implementing that cross project boundaries:
ToDo:
Upstream StatusThe 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 |