Base data to generate the OpenStack map and the Software section of the www.openstack.org website.

Go to file

Dmitriy Rabotyagov 5593591e06 Add coordination tag to components At the moment etcd is present for coordination. Though since tooz is being used in openstack for coordination, there're more drivers for coordination except etcd available. Change-Id: I4b7711c9f84d2b56c2a9659e9fa8d6177b3961a2		2024-11-19 18:30:16 +01:00
.gitignore	Add YAML linting in check and gate	2019-01-07 11:34:04 +01:00
.gitreview	Update repository name in .gitreview	2021-12-20 16:33:03 +01:00
.zuul.yaml	Add YAML linting in check and gate	2019-01-07 11:34:04 +01:00
deployment_tools_capabilities.yaml	Add coordination tag to components	2024-11-19 18:30:16 +01:00
deployment_tools.yaml	Add coordination tag to components	2024-11-19 18:30:16 +01:00
openstack_components.yaml	Update map for 2024.1 release	2024-04-05 09:09:34 +02:00
README.rst	Document YAML file schema in README	2018-12-20 15:07:21 +01:00
sdks.yaml	Modify OpenStackclient's Project Teams to OpenStackSDK based on OpenStack Project Teams	2023-09-14 17:52:15 +08:00
tox.ini	Add YAML linting in check and gate	2019-01-07 11:34:04 +01:00

README.rst

Using This Repository

This repository contains information about OpenStack first-order deliverables, to be used to generate the OpenStack map and "software" pages on the openstack.org website.

What should be included

The goal is to provide a user-facing view of OpenStack deliverables. As such, only first-order deliverables (components that users actually opt into installing) are presented. Libraries, pure dependencies and other second-level deliverables should not be included.

File structure

This repository contains one file for the OpenStack components themselves (openstack_components.yaml), one for tools that can be used to deploy them (deployment_tools.yaml) and one for tools that can be used client-side to interact with them (sdks.yaml).

Each file has a super-structure with tabs and categories, under which each component can be added.

Component schema

Each component is defined by a YAML dictionary with the following keys:

name

The component name (mandatory).

title

A user-friendly short description of the component role (mandatory).

docs-title

Text to use for a link to further documentation (optional).

docs-url

URL to use for a link to further documentation (optional).

desc

Long description of the component role (mandatory).

project-team

Name of the project team that produces this deliverable, as found in the openstack/governance repository in the reference/projects.yaml file (mandatory).

support-teams

List of other project teams (such as I18n, Docs...) to credit for helping in the production of that component, as found in the openstack/governance repository in the reference/projects.yaml file (optional).

since

First OpenStack release that included that component (optional).

video

Video to embed. Currently only supports linking to YouTube videos (optional).

id: YouTube ID for the video.
title: Title for the video.
desc: Description of the video.

dependencies

List of other component names that are hard dependencies for this component (can't work without them) (optional, only for openstack_components.yaml).

see-also

List of other component names that are soft dependencies for this component (benefits of the presence of them) (optional, only for openstack_components.yaml).