openstack
/
ops-tags-team
Code Issues Proposed changes

Retire ops-tags-team repo 

As discussed in TC meeting[1], TC is retiring the
ops-tags-team repo.

[1] https://meetings.opendev.org/meetings/tc/2021/tc.2021-06-17-15.00.log.html#l-98

Change-Id: I2416860cc53f39cca3379667da70208670e401ff
This commit is contained in:
Ghanshyam Mann 2021-06-17 19:16:23 -05:00 committed by Ghanshyam
parent 27d4518674
commit 48f390085a
29 changed files with 8 additions and 2120 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
README.rst
View File

@ -1,14 +1,10 @@
Ops Tags Team
=============
This project is no longer maintained.
The Ops Tags Team exists to define tags for ops, allowing users to make better
decisions by providing useful information about OpenStack software projects.
The contents of this repository are still available in the Git
source code management system. To see the contents of this
repository before it reached its end of life, please check out the
previous commit with "git checkout HEAD^1".
Further information can be found at:
https://wiki.openstack.org/wiki/Operations/Tags
The team conducts its initial development of tags
in a this repository using the OpenStack gerrit workflow
( http://docs.openstack.org/infra/manual/developers.html )
while the discussions around where they will eventually end up (both
file-wise and display-wise) are conducted.
For any further questions, please email
openstack-discuss@lists.openstack.org or join #openstack-dev on
OFTC.

13
descriptions/index.rst
View File

@ -1,13 +0,0 @@
================
Tag Descriptions
================
This directory contains descriptions of tags.
The format currently follows the template that the technical committee
uses for tags under their governance[1], but is expected to evolve over time
if any structural changes are deemed necessary for ops-specific tags.
[1] http://governance.openstack.org/reference/tag-template.html

93
descriptions/ops-docs-install-guide.rst
View File

@ -1,93 +0,0 @@
========================================================================
ops:docs:install-guide
========================================================================
Is there a guide (at docs.openstack.org) that has installation
instructions for the project?
Rationale
=========
The existence of documentation that facilitates a basic installation of
a project is an important factor considered when adopting a project.
By making a general assessment for the software project's state of install
documentation based on distributions supported by the documentation team,
this tag provides the potential for at-a-glance information, especially
when used in conjunction with other tags, to determine a project's maturity.
Requirements
============
- Available - Guide exists, for all doc-team supported distributions for the
release, can be used to perform a basic installation and does not suffer
from major bugs.
- Not Available - No documentation exists for all supported distributions, or
it suffers from major bugs that prevent it from being used to perform a
basic installation.
Tag application process
=======================
- applied per major release by the ops tags team by checking
docs.openstack.org, or through collaboration with the documentation team
- the docs team has a set of supported releases that should all have the same
level. If there is a distro that is not at the same level (eg has a major
bug), this should be noted in a caveat.
- where the status is not 'good', links to bugs must be provided.
- documentation typically lags the release, and major bugs are sometimes
present for some time afterward. Reasonable efforts should be made to
take this into account, with the focus always on providing the most
information to the operator
- the application of this tag follows the distro classifications used by the
documentation team (SUSE, RHEL/CentOS, Ubuntu) for their
supported releases: the aim is a general guide to the existence of
documentation - not an exhaustive distro-by-distro breakdown. Where there
are differences between distributions or versions significant enough they
would normally warrant a change in tag level, this should be noted in a caveat.
Tag updates and timing
======================
Ops Tags are typically made on a per-release basis. At around the end of a
release cycle, a new directory to contain the JSON files for the release is
created, and tags are re-assessed, copying or not using information from
the previous release as appropriate.
In the case of this tag, though it can be updated at any time, there are
four potential update times that would be more common, mostly surrounding
the release process and how documentation has traditionally been produced
and tested slightly lagging the release.
<-- potential for tag update here
1) OpenStack is released
<-- potential for tag update here
2) Docs are released
<-- potential for tag update here
3) Mass bug reports come in and docs are fixed.
<-- potential for tag update here
This will quite likely result in some period of time post-release where
documentation that will later be available is not. This is deemed useful
information to operators.
Attributes
==========
- status - the tag application status
- bug_link - URL(s) to major bugs afflicting a project's install
- description - optional details regarding the tag application
- caveats - Any exceptions to the general status. Follows the same
attributes as the general status, in addition to a 'label'
attribute, which can be used as a title during display

92
descriptions/ops-packaged.rst
View File

@ -1,92 +0,0 @@
========================================================================
ops:packaged
========================================================================
Provides information to operators regarding the existence and quality of
packages for the project in distributions like Red Hat/CentOS, Ubuntu
and openSUSE/SLES.
Rationale
=========
The vast majority of ops use packages for deployment, so the existence of high
quality, bug free packages is an important factor considered when adopting a
project.
By making a general assessment for the software project's state of packaging
based on distributions officially supporting OpenStack, this tag provides
information that was previously difficult to determine, substantially improving
the decision making process.
Requirements
============
- good = Packages without major bugs exist for at least three distribution families
- beginning = Packages without major bugs exist for at least one distribution family
- warning = Packages exist, but have major bugs for more than one distribution family
- no = no packages exist in official distribution repositories for this project
Tag application process
=======================
- applied per major release by the ops tags team
- information is gathered from operator experiences using the packages, in
addition to anything discovered by the documentation team when writing the
new release's install guide
- in the case of 'new' projects, a simple check for the package in each
distribution's package management should suffice to select the level between
'no' and 'beginning'
- where the status is not 'good', links to bugs must be provided.
- the default assumption is that packages are bug-free unless a major bug link
can be provided.
- the application of this tag follows the three-package-management-system
classification used by the documentation team (apt, yum, zypper): the
aim is a general guide to the existence of packages - not an exhaustive
distro-by-distro breakdown. Where there are differences between
distributions or versions significant enough they would normally warrant
a change in tag level, this should be noted in a caveat.
Tag updates and timing
======================
Ops Tags are typically made on a per-release basis. At around the end of a
release cycle, a new directory to contain the JSON files for the release is
created, and tags are re-assessed, copying or not using information from
the previous release as appropriate.
In the case of this tag, though it can be updated at any time, there are
four potential update times that would be more common, mostly surrounding
the release process and how packages have traditionally been produced
and tested slightly lagging the release.
<-- potential for tag update here, based on RC efforts by packagers
1) OpenStack is released
<-- potential for tag update here, based on what's there on release day
2) Packages are formally announced
<-- potential for tag update here, based on the package cut
3) Mass bug reports come in and packages are fixed.
<-- potential for tag update here
This will quite likely result in some period of time post-release where
packages that will later be available are not yet ready, or bug-ridden.
This is deemed useful information to operators.
Attributes
==========
- status - the tag application status
- bug_link - URL(s) to major bugs afflicting a project's packages
- description - optional details regarding the tag application
- caveats - Any exceptions to the general 'status'. Follows the same
attributes as the general status: 'status', 'bug_link',
'description'. In addition a 'label' attribute could be defined
to be used as a title during display.

74
descriptions/ops-production-use.rst
View File

@ -1,74 +0,0 @@
========================================================================
ops:production-use
========================================================================
Provides general information to operators regarding the number of
deployments who are using a particular project in production.
Rationale
=========
This data allows operators to understand the level to which which projects
are generally/popularly adopted, and therefore which projects are likely
to have desirable or undesirable maturity characteristics for common cases.
Though this information is available in the user survey, placing a snapshot
of this information into the tag system allows it to be more easily
combined with other tags. The user survey data should still be published
and made widely available as normal.
Requirements
============
Status is a percentage, derived from the user survey's "What projects does
this deployment use?" question (format: ###%)
Tag application process
=======================
- start by aquiring the percentages of production deployments for each
project from the "What project does this deployment use?" question of the
latest user survey
- The user survey is currently released within a month or so of the software
release. Given this is the best current state of understanding at around
this post-release time, survey data should be paired with the tags for
the new release.
- applied per major release by the ops tags team
- in the case of 'new' projects not covered by the survey, the value should
remain blank rather than '0' until that information can be extrapolated
from the user survey
Tag updates and timing
======================
Ops Tags are typically made on a per-release basis. At around the end of a
release cycle, a new directory to contain the JSON files for the release is
created, and tags are re-assessed, copying or not using information from
the previous release as appropriate.
In the case of this tag, though it could be updated at any time, the user
survey comes out normally one month after release. As such, the following
two update times are probable:
<-- potential for tag update here, using previous survey data, so it's ready
for release with the best information we have
1) OpenStack is released
2) User Survey results released
<-- potential for tag update here, to update to the latest survey data
This will result in some period of time post-release where the user survey
data is 6 months old. However, given the choice between providing this aged
data and providing none at all, it is kinder to provide some data.
Attributes
==========
- status - the percentage of production deployments
- caveats - Any exceptions to the general status. Follows the same
attributes as the general status, in addition to an optional
'label' attribute, which can be used as a title during display

63
descriptions/ops-sdk-support.rst
View File

@ -1,63 +0,0 @@
========================================================================
ops:sdk-support
========================================================================
Provides general information to users regarding the number of
software development kits (SDKs) which support a particular service project.
Rationale
=========
This data allows users to understand the level to which which projects
are generally/popularly supported in SDKs, and therefore which projects are
likely to be able to be relied on for application development.
This information is available from the individual SDK information pages,
though it is often difficult to extract, and nowhere is it provided in
aggregate level. Placing a snapshot of this information into the tag system
allows it to be more easily combined with other tags to provide high-level
overviews of maturity for projects.
Requirements
============
Status is an integer - the number of SDKs updated within the release cycle
that support the service project - derived from a survey of all SDKs,
listed at https://wiki.openstack.org/wiki/SDKs .
Tag application process
=======================
- For each SDK listed at https://wiki.openstack.org/wiki/SDKs, determine
whether the SDK has been updated within the release cycle. Only SDKs
updated within the release cycle are counted toward this tag.
- For the recently updated SDKs, determine the status of their support for
each service project.
- For each service, count the number of those SDKs that support it and
enter that number in as the 'status'.
- in the case of 'new' projects, the value should start at '0' until SDK
support has been seen
Tag updates and timing
======================
Ops Tags are typically made on a per-release basis. At around the end of a
release cycle, a new directory to contain the JSON files for the release is
created, and tags are re-assessed, copying or not using information from
the previous release as appropriate.
In the case of this tag, though it could be updated at any time, adding
support for a new project in an SDK is a significant endeavour. As such
it is reasonable to update the tag only in conjunction with the release,
with exceptional updates on request.
Attributes
==========
- status - the number of recently updated SDKs supporting the project
- caveats - Any exceptions to the general status. Follows the same
attributes as the general status, in addition to an optional
'label' attribute, which can be used as a title during display

85
descriptions/template.rst
View File

@ -1,85 +0,0 @@
# This is a template that can be used for creating new tags. At a minimum
# the following information should be submitted when creating a tag.
#
# Each tag should have a the following structure:
# - descriptions/<tag_name>.rst - Description of the tag
# - <release_name>/<tag_name>.json - Tag definition
#
# All comment lines (marked with a '#') should be removed before submission.
========================================================================
ops:<tag_name>
========================================================================
# Introductory paragraph
# Provide a short summary of what this tag will mean
Rationale
=========
# Provide a detailed explanation of why the OpenStack ecosystem benefits
# from having this tag defined.
Requirements
============
# Provide a list of requirements for granting the tag to an existing
# project.
# All the criteria should be objective and predictable.
# If a tag requires another tag, this should be mentioned here.
#
# - Requirement 1
# - Requirement 2
Tag application process
=======================
# Details of the process to follow to maintain the tag. Are additions/
# removals regularly reviewed, or are they considered only upon request?
# Which group is involved, and at which frequency ?
#
# The process may include requiring feedback from specific groups,
# delegation of tag maintenance from the UC, minimum delays between
# application and tag grant, timeframes where granting or removing the
# tag is appropriate, etc.
#
# If the grant process is different from the removal process, this should
# also be mentioned here.
#
# By default, you can use the following process:
#
# Anyone may propose adding or removing this tag to a set of projects by
# proposing a change to the openstack/ops-tags-team repository. The change is
# reviewed by the Ops Tags Group and approved using standard resolution
# approval rules.
#
# - Step 1
# - Step 2
# - Step 3
Tag updates and timing
======================
# Ops Tags are typically made on a per-release basis. Near the end
# of a release cycle, a new directory to contain the JSON files for
# the release is created, and tags are re-assessed. Information is
# either removed or copied from the previous release as appropriate.
#
# Some tags may have a deprecation period (where a project retains the
# tag but only until a certain announced date). If the proposed tag has
# a deprecation period, its duration (and any other specific rules) should
# be listed here.
#
# - There is no deprecation period required for this tag.
# - It can be added or removed at any time.
Attributes
==========
# Tags may have attributes which provide extra information. Those attributes
# (and their values) should be described in this section
#
# - attribute1 - attribute1 description
# - attribute2 - attribute2 description
# - attribute3 - attribute3 description

67
juno/ops-docs-install-guide.json
View File

@ -1,67 +0,0 @@
{
"Compute service (Nova)":
{
"status": "available"
},
"Object Storage service (Swift)":
{
"status": "available"
},
"Image service (Glance)":
{
"status": "available"
},
"Identity service (Keystone)":
{
"status": "available"
},
"Dashboard (Horizon)":
{
"status": "available"
},
"Networking service (Neutron)":
{
"status": "available"
},
"Block Storage service (Cinder)":
{
"status": "available"
},
"Telemetry service (Ceilometer)":
{
"status": "available"
},
"Orchestration service (Heat)":
{
"status": "available"
},
"Database service (Trove)":
{
"status": "not available",
"description": "The installation guide previously available was removed this release by the documentation team, and will likely stay that way until it can be improved to the level of the other projects."
},
"Data Processing service (Sahara)":
{
"status": "not available"
},
"Bare Metal service (Ironic)":
{
"status": "not available"
},
"Messaging service (Zaqar)":
{
"status": "not available"
},
"Key Management service (Barbican)":
{
"status": "not available"
},
"DNS service (Designate)":
{
"status": "not available"
},
"Deployment service (TripleO)":
{
"status": "not available"
}
}

62
juno/ops-production-use.json
View File

@ -1,62 +0,0 @@
{
"Compute service (Nova)":
{
"status": "93%"
},
"Object Storage service (Swift)":
{
"status": "49%"
},
"Image service (Glance)":
{
"status": "85%"
},
"Identity service (Keystone)":
{
"status": "90%"
},
"Dashboard (Horizon)":
{
"status": "81%"
},
"Networking service (Neutron)":
{
"status": "68%"
},
"Block Storage service (Cinder)":
{
"status": "73%"
},
"Telemetry service (Ceilometer)":
{
"status": "33%"
},
"Orchestration service (Heat)":
{
"status": "32%"
},
"Database service (Trove)":
{
"status": "9%"
},
"Data Processing service (Sahara)":
{
"status": "0%"
},
"Bare Metal service (Ironic)":
{
"status": "5%"
},
"Message service (Zaqar)":
{
"status": "0%"
},
"Key Management service (Barbican)":
{
"status": "0%"
},
"DNS service (Designate)":
{
"status": "0%"
}
}

61
juno/ops-sdk-support.json
View File

@ -1,61 +0,0 @@
{
"Compute service (Nova)":
{
"status": "11"
},
"Object Storage service (Swift)":
{
"status": "11"
},
"Image service (Glance)":
{
"status": "4"
},
"Identity service (Keystone)":
{
"status": "11"
},
"Dashboard (Horizon)":
{
},
"Networking service (Neutron)":
{
"status": "6"
},
"Block Storage service (Cinder)":
{
"status": "7"
},
"Telemetry service (Ceilometer)":
{
"status": "2"
},
"Orchestration service (Heat)":
{
"status": "2"
},
"Database service (Trove)":
{
"status": "4"
},
"Data Processing service (Sahara)":
{
"status": "0"
},
"Bare Metal service (Ironic)":
{
"status": "0"
},
"Message service (Zaqar)":
{
"status": "0"
},
"Key Management service (Barbican)":
{
"status": "0"
},
"DNS service (Designate)":
{
"status": "0"
}
}

9
kilo/index.rst
View File

@ -1,9 +0,0 @@
=========
Kilo Tags
=========
This directory contains application information of tags as at the
Kilo release.
The format herein is designed to be consumed by one or more presentation
layers, such as the openstack.org website.

68
kilo/ops-docs-install-guide.json
View File

@ -1,68 +0,0 @@
{
"Compute service (Nova)":
{
"status": "available"
},
"Object Storage service (Swift)":
{
"status": "available"
},
"Image service (Glance)":
{
"status": "available"
},
"Identity service (Keystone)":
{
"status": "available"
},
"Dashboard (Horizon)":
{
"status": "available"
},
"Networking service (Neutron)":
{
"status": "available"
},
"Block Storage service (Cinder)":
{
"status": "available"
},
"Telemetry service (Ceilometer)":
{
"status": "available"
},
"Orchestration service (Heat)":
{
"status": "available"
},
"Database service (Trove)":
{
"status": "not available",
"description": "The installation guide previously available was removed this release by the documentation team, and will likely stay that way until it can be improved to the level of the other projects."
},
"Data Processing service (Sahara)":
{
"status": "not available",
"description": "The installation guide previously available was removed this release by the documentation team, and will likely stay that way until it can be improved to the level of the other projects."
},
"Bare Metal service (Ironic)":
{
"status": "not available"
},
"Messaging service (Zaqar)":
{
"status": "not available"
},
"Key Management service (Barbican)":
{
"status": "not available"
},
"DNS service (Designate)":
{
"status": "not available"
},
"Deployment service (TripleO)":
{
"status": "not available"
}
}

83
kilo/ops-packaged.json
View File

@ -1,83 +0,0 @@
{
"Compute service (Nova)":
{
"status": "good"
},
"Object Storage service (Swift)":
{
"status": "good"
},
"Image service (Glance)":
{
"status": "good"
},
"Identity service (Keystone)":
{
"status": "good"
},
"Dashboard (Horizon)":
{
"status": "good"
},
"Networking service (Neutron)":
{
"status": "good",
"caveats":
[{
"status": "no",
"label": "Vendor drivers not packaged",
"description": "From this release, most network drivers (particularly non-open-source) are no longer packaged. Instead, they must be found from their repository on https://github.com/stackforge or https://github.com/openstack ."
}]
},
"Block Storage service (Cinder)":
{
"status": "good"
},
"Telemetry service (Ceilometer)":
{
"status": "warning",
"description": "Red Hat's packages for Ceilometer are not usable with swift",
"bug_link": "https://bugzilla.redhat.com/show_bug.cgi?id=1214928"
},
"Orchestration service (Heat)":
{
"status": "good"
},
"Database service (Trove)":
{
"status": "warning",
"description": "On Ubuntu, /var/cache/trove is not created.",
"bug_link": "https://bugs.launchpad.net/ubuntu/+source/trove/+bug/1459961"
},
"Data Processing service (Sahara)":
{
"status": "warning",
"description": "Ubuntu packages run db-manage on install even when no database is configured.",
"bug_link": "https://bugs.launchpad.net/ubuntu/+source/sahara/+bug/1452698"
},
"Bare Metal service (Ironic)":
{
"status": "good"
},
"Message service (Zaqar)":
{
"status": "no"
},
"Key Management service (Barbican)":
{
"status": "no"
},
"DNS services (Designate)":
{
"status": "good"
},
"Deployment service (TripleO)":
{
"status": "no"
},
"Shared File Systems service (Manila)":
{
"status": "beginning"
}
}

62
kilo/ops-production-use.json
View File

@ -1,62 +0,0 @@
{
"Compute service (Nova)":
{
"status": "98%"
},
"Object Storage service (Swift)":
{
"status": "58%"
},
"Image service (Glance)":
{
"status": "92%"
},
"Identity service (Keystone)":
{
"status": "95%"
},
"Dashboard (Horizon)":
{
"status": "90%"
},
"Networking service (Neutron)":
{
"status": "79%"
},
"Block Storage service (Cinder)":
{
"status": "83%"
},
"Telemetry service (Ceilometer)":
{
"status": "43%"
},
"Orchestration service (Heat)":
{
"status": "47%"
},
"Database service (Trove)":
{
"status": "12%"
},
"Data Processing service (Sahara)":
{
"status": "7%"
},
"Bare Metal service (Ironic)":
{
"status": "9%"
},
"Message service (Zaqar)":
{
"status": "1%"
},
"Key Management service (Barbican)":
{
"status": "9%"
},
"DNS service (Designate)":
{
"status": "9%"
}
}

61
kilo/ops-sdk-support.json
View File

@ -1,61 +0,0 @@
{
"Compute service (Nova)":
{
"status": "15"
},
"Object Storage service (Swift)":
{
"status": "15"
},
"Image service (Glance)":
{
"status": "7"
},
"Identity service (Keystone)":
{
"status": "14"
},
"Dashboard (Horizon)":
{
},
"Networking service (Neutron)":
{
"status": "12"
},
"Block Storage service (Cinder)":
{
"status": "11"
},
"Telemetry service (Ceilometer)":
{
"status": "3"
},
"Orchestration service (Heat)":
{
"status": "8"
},
"Database service (Trove)":
{
"status": "5"
},
"Data Processing service (Sahara)":
{
"status": "2"
},
"Bare Metal service (Ironic)":
{
"status": "2"
},
"Message service (Zaqar)":
{
"status": "3"
},
"Key Management service (Barbican)":
{
"status": "2"
},
"DNS service (Designate)":
{
"status": "2"
}
}

14
kilo/template.json
View File

@ -1,14 +0,0 @@
# This is a template that can be used for creating definitions for new tags.
# The attributes and the values defined here will match those defined in the
# corresponding descriptions/<tag_name>.rst file.
#
# Each tag should have a the following structure
# {
# "<Product_Name>":
# {
# "attribute1": "value1",
# "attribute2": ["value2", "value3", "value4"]
# },
# }
#
# All comment lines (marked with a '#') should be removed before submission.

66
liberty/ops-docs-install-guide.json
View File

@ -1,66 +0,0 @@
{
"Compute service (Nova)":
{
"status": "available"
},
"Object Storage service (Swift)":
{
"status": "available"
},
"Image service (Glance)":
{
"status": "available"
},
"Identity service (Keystone)":
{
"status": "available"
},
"Dashboard (Horizon)":
{
"status": "available"
},
"Networking service (Neutron)":
{
"status": "available"
},
"Block Storage service (Cinder)":
{
"status": "available"
},
"Telemetry service (Ceilometer)":
{
"status": "available"
},
"Orchestration service (Heat)":
{
"status": "available"
},
"Database service (Trove)":
{
"status": "not available"
},
"Data Processing service (Sahara)":
{
"status": "not available"
},
"Bare Metal service (Ironic)":
{
"status": "not available"
},
"Messaging service (Zaqar)":
{
"status": "not available"
},
"Key Management service (Barbican)":
{
"status": "not available"
},
"DNS service (Designate)":
{
"status": "not available"
},
"Deployment service (TripleO)":
{
"status": "not available"
}
}

76
liberty/ops-packaged.json
View File

@ -1,76 +0,0 @@
{
"Compute service (Nova)":
{
"status": "good"
},
"Object Storage service (Swift)":
{
"status": "good"
},
"Image service (Glance)":
{
"status": "good"
},
"Identity service (Keystone)":
{
"status": "good"
},
"Dashboard (Horizon)":
{
"status": "good"
},
"Networking service (Neutron)":
{
"status": "good",
"caveats":
[{
"status": "no",
"label": "Vendor drivers not packaged",
"description": "From this release, most network drivers (particularly non-open-source) are no longer packaged. Instead, they must be found from their repository on https://github.com/stackforge or https://github.com/openstack ."
}]
},
"Block Storage service (Cinder)":
{
"status": "good"
},
"Telemetry service (Ceilometer)":
{
"status": "good"
},
"Orchestration service (Heat)":
{
"status": "good"
},
"Database service (Trove)":
{
"status": "good"
},
"Data Processing service (Sahara)":
{
"status": "good"
},
"Bare Metal service (Ironic)":
{
"status": "good"
},
"Message service (Zaqar)":
{
"status": "good"
},
"Key Management service (Barbican)":
{
"status": "beginning"
},
"DNS services (Designate)":
{
"status": "good"
},
"Deployment service (TripleO)":
{
"status": "no"
},
"Shared File Systems service (Manila)":
{
"status": "good"
}
}

90
liberty/ops-production-use.json
View File

@ -1,90 +0,0 @@
{
"Compute service (Nova)":
{
"status": "96%"
},
"Object Storage service (Swift)":
{
"status": "62%"
},
"Image service (Glance)":
{
"status": "94%"
},
"Identity service (Keystone)":
{
"status": "96%"
},
"Dashboard (Horizon)":
{
"status": "95%"
},
"Networking service (Neutron)":
{
"status": "89%"
},
"Block Storage service (Cinder)":
{
"status": "86%"
},
"Telemetry service (Ceilometer)":
{
"status": "61%"
},
"Orchestration service (Heat)":
{
"status": "68%"
},
"Database service (Trove)":
{
"status": "27%"
},
"Data Processing service (Sahara)":
{
"status": "20%"
},
"Bare Metal service (Ironic)":
{
"status": "17%"
},
"Message service (Zaqar)":
{
"status": "1%"
},
"Key Management service (Barbican)":
{
"status": "4%"
},
"DNS service (Designate)":
{
"status": "25%"
},
"Shared File Systems service (Manila)":
{
"status": "8%"
},
"Benchmark service (Rally)":
{
"status": "17%"
},
"Containers service (Magnum)":
{
"status": "7%"
},
"Application Catalog service (Murano)":
{
"status": "7%"
},
"Deployment service (TripleO)":
{
"status": "4%"
},
"Governance service (Congress)":
{
"status": "1%"
},
"Container-based deployment tools (Kolla)":
{
"status": "2%"
}
}

61
liberty/ops-sdk-support.json
View File

@ -1,61 +0,0 @@
{
"Compute service (Nova)":
{
"status": "15"
},
"Object Storage service (Swift)":
{
"status": "15"
},
"Image service (Glance)":
{
"status": "7"
},
"Identity service (Keystone)":
{
"status": "14"
},
"Dashboard (Horizon)":
{
},
"Networking service (Neutron)":
{
"status": "12"
},
"Block Storage service (Cinder)":
{
"status": "11"
},
"Telemetry service (Ceilometer)":
{
"status": "3"
},
"Orchestration service (Heat)":
{
"status": "8"
},
"Database service (Trove)":
{
"status": "5"
},
"Data Processing service (Sahara)":
{
"status": "2"
},
"Bare Metal service (Ironic)":
{
"status": "2"
},
"Message service (Zaqar)":
{
"status": "3"
},
"Key Management service (Barbican)":
{
"status": "2"
},
"DNS service (Designate)":
{
"status": "2"
}
}

74
mitaka/ops-docs-install-guide.json
View File

@ -1,74 +0,0 @@
{
"Compute service (Nova)":
{
"status": "available"
},
"Object Storage service (Swift)":
{
"status": "available"
},
"Image service (Glance)":
{
"status": "available"
},
"Identity service (Keystone)":
{
"status": "available"
},
"Dashboard (Horizon)":
{
"status": "available"
},
"Networking service (Neutron)":
{
"status": "available"
},
"Block Storage service (Cinder)":
{
"status": "available"
},
"Telemetry service (Ceilometer)":
{
"status": "available"
},
"Orchestration service (Heat)":
{
"status": "available"
},
"Database service (Trove)":
{
"status": "available"
},
"Data Processing service (Sahara)":
{
"status": "available"
},
"Bare Metal service (Ironic)":
{
"status": "available"
},
"Messaging service (Zaqar)":
{
"status": "not available"
},
"Key Management service (Barbican)":
{
"status": "not available"
},
"DNS service (Designate)":
{
"status": "not available"
},
"Deployment service (TripleO)":
{
"status": "not available"
},
"Shared File Systems service (Manila)":
{
"status": "available"
},
"Application Catalog (Murano)":
{
"status": "available"
}
}

94
mitaka/ops-production-use.json
View File

@ -1,94 +0,0 @@
{
"Compute service (Nova)":
{
"status": "93%"
},
"Object Storage service (Swift)":
{
"status": "52%"
},
"Image service (Glance)":
{
"status": "87%"
},
"Identity service (Keystone)":
{
"status": "88%"
},
"Dashboard (Horizon)":
{
"status": "86%"
},
"Networking service (Neutron)":
{
"status": "84%"
},
"Block Storage service (Cinder)":
{
"status": "81%"
},
"Telemetry service (Ceilometer)":
{
"status": "59%"
},
"Orchestration service (Heat)":
{
"status": "64%"
},
"Database service (Trove)":
{
"status": "17%"
},
"Data Processing service (Sahara)":
{
"status": "11%"
},
"Bare Metal service (Ironic)":
{
"status": "20%"
},
"Message service (Zaqar)":
{
"status": "2%"
},
"Key Management service (Barbican)":
{
"status": "2%"
},
"DNS service (Designate)":
{
"status": "17%"
},
"Shared File Systems service (Manila)":
{
"status": "11%"
},
"Benchmark service (Rally)":
{
"status": "25%"
},
"Containers service (Magnum)":
{
"status": "11%"
},
"Application Catalog service (Murano)":
{
"status": "15%"
},
"Deployment service (TripleO)":
{
"status": "6%"
},
"Governance service (Congress)":
{
"status": "1%"
},
"Container-based deployment tools (Kolla)":
{
"status": "3%"
},
"Workflow service (Mistral)":
{
"status": "2%"
}
}

61
mitaka/ops-sdk-support.json
View File

@ -1,61 +0,0 @@
{
"Compute service (Nova)":
{
"status": "16"
},
"Object Storage service (Swift)":
{
"status": "17"
},
"Image service (Glance)":
{
"status": "8"
},
"Identity service (Keystone)":
{
"status": "20"
},
"Dashboard (Horizon)":
{
},
"Networking service (Neutron)":
{
"status": "10"
},
"Block Storage service (Cinder)":
{
"status": "11"
},
"Telemetry service (Ceilometer)":
{
"status": "5"
},
"Orchestration service (Heat)":
{
"status": "7"
},
"Database service (Trove)":
{
"status": "4"
},
"Data Processing service (Sahara)":
{
"status": "2"
},
"Bare Metal service (Ironic)":
{
"status": "2"
},
"Message service (Zaqar)":
{
"status": "2"
},
"Key Management service (Barbican)":
{
"status": "2"
},
"DNS service (Designate)":
{
"status": "1"
}
}

143
newton/ops-docs-install-guide.json
View File

@ -1,143 +0,0 @@
{
"Key Management service (Barbican)":
{
"status": "available"
},
"Telemetry service (Ceilometer)":
{
"status": "available"
},
"Block Storage service (Cinder)":
{
"status": "available"
},
"Rating service (CloudKitty)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Governance service (Congress)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"DNS service (Designate)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Backup, Restore and Disaster Recovery service (Freezer)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Image service (Glance)":
{
"status": "available"
},
"Orchestration service (Heat)":
{
"status": "available"
},
"Dashboard (Horizon)":
{
"status": "available"
},
"Bare Metal service (Ironic)":
{
"status": "available"
},
"Identity service (Keystone)":
{
"status": "available"
},
"Data Protection Orchestration service (Karbor)":
{
"status": "not available",
"description": "No installation documentation available."
},
"Shared File Systems service (Manila)":
{
"status": "available"
},
"Container Infrastructure Management service (Magnum)":
{
"status": "available"
},
"Workflow service (Mistral)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Monitoring (Monasca)":
{
"status": "not available",
"description": "No installation documentation available."
},
"Application Catalog (Murano)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Networking service (Neutron)":
{
"status": "available"
},
"Compute service (Nova)":
{
"status": "available"
},
"Data Processing service (Sahara)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Clustering service (Senlin)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Search service (Searchlight)":
{
"status": "not available",
"description": "No installation documentation available."
},
"Software Development Lifecycle Automation service (Solum)":
{
"status": "not available",
"description": "No installation documentation available."
},
"Object Storage service (Swift)":
{
"status": "available"
},
"NFV Orchestration service (Tacker)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Deployment service (TripleO)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Database service (Trove)":
{
"status": "available"
},
"RCA (Root Cause Analysis) service (Vitrage)":
{
"status": "not available",
"description": "No installation documentation available."
},
"Infrastructure Optimization service (Watcher)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Messaging service (Zaqar)":
{
"status": "available"
}
}

102
newton/ops-production-use.json
View File

@ -1,102 +0,0 @@
{
"Compute service (Nova)":
{
"status": "98%"
},
"Object Storage service (Swift)":
{
"status": "47%"
},
"Image service (Glance)":
{
"status": "92%"
},
"Identity service (Keystone)":
{
"status": "92%"
},
"Dashboard (Horizon)":
{
"status": "92%"
},
"Networking service (Neutron)":
{
"status": "93%"
},
"Block Storage service (Cinder)":
{
"status": "88%"
},
"Telemetry service (Ceilometer)":
{
"status": "62%"
},
"Orchestration service (Heat)":
{
"status": "66%"
},
"Database service (Trove)":
{
"status": "17%"
},
"Data Processing service (Sahara)":
{
"status": "11%"
},
"Bare Metal service (Ironic)":
{
"status": "25%"
},
"Message service (Zaqar)":
{
"status": "2%"
},
"Key Management service (Barbican)":
{
"status": "5%"
},
"DNS service (Designate)":
{
"status": "19%"
},
"Shared File Systems service (Manila)":
{
"status": "11%"
},
"Benchmark service (Rally)":
{
"status": "23%"
},
"Containers service (Magnum)":
{
"status": "13%"
},
"Application Catalog service (Murano)":
{
"status": "12%"
},
"Deployment service (TripleO)":
{
"status": "7%"
},
"Governance service (Congress)":
{
"status": "2%"
},
"Container-based deployment tools (Kolla)":
{
"status": "7%"
},
"Workflow service (Mistral)":
{
"status": "2%"
},
"Message Broker service (Cue)":
{
"status": "2%"
},
"Software Dev Lifecycle Management service (Solum)":
{
"status": "1%"
}
}

70
newton/ops-sdk-support.json
View File

@ -1,70 +0,0 @@
{
"Compute service (Nova)":
{
"status": "17"
},
"Object Storage service (Swift)":
{
"status": "19"
},
"Image service (Glance)":
{
"status": "11"
},
"Identity service (Keystone)":
{
"status": "20"
},
"Dashboard (Horizon)":
{
},
"Networking service (Neutron)":
{
"status": "12"
},
"Block Storage service (Cinder)":
{
"status": "13"
},
"Telemetry service (Ceilometer)":
{
"status": "5"
},
"Orchestration service (Heat)":
{
"status": "9"
},
"Database service (Trove)":
{
"status": "6"
},
"Data Processing service (Sahara)":
{
"status": "1"
},
"Bare Metal service (Ironic)":
{
"status": "2"
},
"Message service (Zaqar)":
{
"status": "4"
},
"Key Management service (Barbican)":
{
"status": "2"
},
"DNS service (Designate)":
{
"status": "2"
},
"Application Catalog (Murano)":
{
"status": "1"
},
"Container Infrastructure Management service (Magnum)":
{
"status": "1"
}
}

188
ocata/ops-docs-install-guide.json
View File

@ -1,188 +0,0 @@
{
"Key Management service (Barbican)":
{
"status": "available"
},
"Telemetry service (Ceilometer)":
{
"status": "available"
},
"Block Storage service (Cinder)":
{
"status": "available"
},
"Rating service (CloudKitty)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Governance service (Congress)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"DNS service (Designate)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Backup, Restore and Disaster Recovery service (Freezer)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Image service (Glance)":
{
"status": "available"
},
"Orchestration service (Heat)":
{
"status": "available"
},
"Dashboard (Horizon)":
{
"status": "available"
},
"Bare Metal service (Ironic)":
{
"status": "available"
},
"Identity service (Keystone)":
{
"status": "available"
},
"Data Protection Orchestration service (Karbor)":
{
"status": "not available",
"description": "No installation documentation available."
},
"Shared File Systems service (Manila)":
{
"status": "available"
},
"Container Infrastructure Management service (Magnum)":
{
"status": "available"
},
"Workflow service (Mistral)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Monitoring (Monasca)":
{
"status": "not available",
"description": "No installation documentation available."
},
"Application Catalog (Murano)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Networking service (Neutron)":
{
"status": "available"
},
"Compute service (Nova)":
{
"status": "available"
},
"Data Processing service (Sahara)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Clustering service (Senlin)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Search service (Searchlight)":
{
"status": "not available",
"description": "No installation documentation available."
},
"Software Development Lifecycle Automation service (Solum)":
{
"status": "not available",
"description": "No installation documentation available."
},
"Object Storage service (Swift)":
{
"status": "available"
},
"NFV Orchestration service (Tacker)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Deployment service (TripleO)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Database service (Trove)":
{
"status": "available"
},
"RCA (Root Cause Analysis) service (Vitrage)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Infrastructure Optimization service (Watcher)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Messaging service (Zaqar)":
{
"status": "available"
},
"(Dragonflow)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"(Kuryr)":
{
"status": "not available",
"description": "No installation documentation available."
},
"Load-balancing service (Octavia)":
{
"status": "not available",
"description": "No installation documentation available."
},
"Command-line client (OpenStackClient)":
{
"status": "not available",
"description": "No installation documentation available."
},
"Benchmark service (Rally)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Interoperability Test Report (RefStack)":
{
"status": "not available",
"description": "No installation documentation available."
},
"Compute inside Object Store service (Storlets)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Networking automation across Neutron service (Tricircle)":
{
"status": "not available",
"description": "Guides are only available for older releases and/or certain distributions."
},
"Containers service (Zun)":
{
"status": "not available",
"description": "No installation documentation available."
}
}

106
ocata/ops-production-use.json
View File

@ -1,106 +0,0 @@
{
"Compute service (Nova)":
{
"status": "95%"
},
"Object Storage service (Swift)":
{
"status": "52%"
},
"Image service (Glance)":
{
"status": "95%"
},
"Identity service (Keystone)":
{
"status": "96%"
},
"Dashboard (Horizon)":
{
"status": "87%"
},
"Networking service (Neutron)":
{
"status": "93%"
},
"Block Storage service (Cinder)":
{
"status": "88%"
},
"Telemetry service (Ceilometer)":
{
"status": "55%"
},
"Orchestration service (Heat)":
{
"status": "67%"
},
"Database service (Trove)":
{
"status": "13%"
},
"Data Processing service (Sahara)":
{
"status": "10%"
},
"Bare Metal service (Ironic)":
{
"status": "21%"
},
"Message service (Zaqar)":
{
"status": "4%"
},
"Key Management service (Barbican)":
{
"status": "9%"
},
"DNS service (Designate)":
{
"status": "16%"
},
"Shared File Systems service (Manila)":
{
"status": "14%"
},
"Benchmark service (Rally)":
{
"status": "23%"
},
"Containers service (Magnum)":
{
"status": "11%"
},
"Application Catalog service (Murano)":
{
"status": "11%"
},
"Deployment service (TripleO)":
{
"status": "9%"
},
"Governance service (Congress)":
{
"status": "2%"
},
"Container-based deployment tools (Kolla)":
{
"status": "12%"
},
"Workflow service (Mistral)":
{
"status": "5%"
},
"Message Broker service (Cue)":
{
"status": "2%"
},
"Software Dev Lifecycle Management service (Solum)":
{
"status": "2%"
},
"Key-Value Store as a Service (Magnetodb)":
{
"status": "2%"
}
}

70
ocata/ops-sdk-support.json
View File

@ -1,70 +0,0 @@
{
"Compute service (Nova)":
{
"status": "17"
},
"Object Storage service (Swift)":
{
"status": "19"
},
"Image service (Glance)":
{
"status": "11"
},
"Identity service (Keystone)":
{
"status": "20"
},
"Dashboard (Horizon)":
{
},
"Networking service (Neutron)":
{
"status": "12"
},
"Block Storage service (Cinder)":
{
"status": "13"
},
"Telemetry service (Ceilometer)":
{
"status": "5"
},
"Orchestration service (Heat)":
{
"status": "9"
},
"Database service (Trove)":
{
"status": "6"
},
"Data Processing service (Sahara)":
{
"status": "1"
},
"Bare Metal service (Ironic)":
{
"status": "2"
},
"Message service (Zaqar)":
{
"status": "4"
},
"Key Management service (Barbican)":
{
"status": "2"
},
"DNS service (Designate)":
{
"status": "2"
},
"Application Catalog (Murano)":
{
"status": "1"
},
"Container Infrastructure Management service (Magnum)":
{
"status": "1"
}
}