From a04a460e586763cd086b9b41c486ab28a22dcb93 Mon Sep 17 00:00:00 2001 From: Ankur Gupta Date: Mon, 20 Mar 2017 15:33:34 -0400 Subject: [PATCH] Feature Classification Cleanup Fix last remaining comments for recently merged FeatCl. TrivialFix Change-Id: I80c43cd24c7d19739c23717e8ab833e87b819590 --- .../feature_classification_introduction.rst | 10 +++--- .../general_feature_support_matrix.ini | 32 +++++++++---------- 2 files changed, 21 insertions(+), 21 deletions(-) diff --git a/doc/source/feature_classification/feature_classification_introduction.rst b/doc/source/feature_classification/feature_classification_introduction.rst index 27ac7facd9b..1f92d24477c 100644 --- a/doc/source/feature_classification/feature_classification_introduction.rst +++ b/doc/source/feature_classification/feature_classification_introduction.rst @@ -9,8 +9,8 @@ Goals ~~~~~ The object of this document is to inform users whether or not -features are complete, well-documented, stable, and tested. -This approach ensures a good user-experience for those well-maintained features. +features are complete, well documented, stable, and tested. +This approach ensures good user experience for those well maintained features. .. note:: @@ -35,7 +35,7 @@ Feature status Immature -------- -Immature features do not have enough functionality to satisfy real-world +Immature features do not have enough functionality to satisfy real world use cases. An immature feature is a feature being actively developed, which is only @@ -54,14 +54,14 @@ A feature is considered mature if it satisfies the following criteria: * Complete API documentation including concept and REST call definition. * Complete Administrator documentation. * Tempest tests that define the correct functionality of the feature. -* Enough functionality and reliability to be useful in real-world scenarios. +* Enough functionality and reliability to be useful in real world scenarios. * Low probability of support for the feature being dropped. Required -------- Required features are core networking principles that have been thoroughly -tested and have been implemented in real-world use cases. +tested and have been implemented in real world use cases. In addition they satisfy the same criteria for any mature features. diff --git a/doc/source/feature_classification/general_feature_support_matrix.ini b/doc/source/feature_classification/general_feature_support_matrix.ini index b2b3dfdde7e..0546a27142e 100644 --- a/doc/source/feature_classification/general_feature_support_matrix.ini +++ b/doc/source/feature_classification/general_feature_support_matrix.ini @@ -23,8 +23,7 @@ status=required api=core cli=openstack network * notes=The ability to create, modify and delete networks. - Other OpenStack Client commands are create, delete, list, - segment list, segment show, set, show. + https://developer.openstack.org/api-ref/networking/v2/#networks networking-ovs=complete networking-linux-bridge=complete networking-odl=complete @@ -37,9 +36,7 @@ status=required api=core cli=openstack subnet * notes=The ability to create and manipulate subnets and subnet pools. - Other OpenStack Client commands are create, delete, list, - pool create, pool delete, pool list, pool set, pool show, - set, show. + https://developer.openstack.org/api-ref/networking/v2/#subnets networking-ovs=complete networking-linux-bridge=complete networking-odl=complete @@ -52,8 +49,7 @@ status=required api=core cli=openstack port * notes=The ability to create and manipulate ports. - Other OpenStack Client commands are create, delete, list, set, - show. + https://developer.openstack.org/api-ref/networking/v2/#ports networking-ovs=complete networking-linux-bridge=complete networking-odl=complete @@ -66,9 +62,7 @@ status=required api=router cli=openstack router * notes=The ability to create and manipulate routers. - Other OpenStack Client commands are create, add port, - add subnet, delete, list, remove port, remove subnet, - set, show. + https://developer.openstack.org/api-ref/networking/v2/#routers-routers networking-ovs=complete networking-linux-bridge=complete networking-odl=complete @@ -82,8 +76,7 @@ api=security-group cli=openstack security group * notes=Security groups are set by default, and can be modified to control ingress & egress traffic. - Other OpenStack Client commands are create, delete, list, rule create, - rule delete, rule list, rule show, set, show. + https://developer.openstack.org/api-ref/networking/v2/#security-groups-security-groups networking-ovs=complete networking-linux-bridge=complete networking-odl=complete @@ -107,6 +100,7 @@ title=Distributed Virtual Routers status=immature api=dvr notes=The ability to support the distributed virtual routers. + https://wiki.openstack.org/wiki/Neutron/DVR networking-ovs=complete networking-linux-bridge=incomplete networking-odl=partial @@ -130,6 +124,7 @@ title=Quality of Service status=mature api=qos notes=Support for Neutron Quality of Service policies and API. + https://developer.openstack.org/api-ref/networking/v2/#qos-policies-qos networking-ovs=complete networking-linux-bridge=partial networking-odl=partial @@ -139,6 +134,7 @@ networking-ovn=complete [operation.BGP] title=Border Gateway Protocol status=immature +notes=https://developer.openstack.org/api-ref/networking/v2/#bgp-mpls-vpn-interconnection networking-ovs=complete networking-linux-bridge=unknown networking-odl=unknown @@ -150,8 +146,7 @@ title=DNS status=mature api=dns-integration notes=The ability to integrate with an external DNS - as a Service. http://docs.openstack.org/newton/ - networking-guide/config-dns-int.html + as a Service. http://docs.openstack.org/newton/networking-guide/config-dns-int.html networking-ovs=complete networking-linux-bridge=complete networking-odl=complete @@ -162,6 +157,9 @@ networking-ovn=complete title=Trunk Ports status=mature api=trunk +notes=Neutron extension to access lots of neutron networks over + a single vNIC as tagged/encapsulated traffic. + https://developer.openstack.org/api-ref/networking/v2/#trunk-networking networking-ovs=complete networking-linux-bridge=complete networking-odl=incomplete @@ -172,6 +170,8 @@ networking-ovn=complete title=Metering status=mature api=metering +notes=Meter traffic at the L3 router levels. + https://developer.openstack.org/api-ref/networking/v2/#metering-labels-and-rules-metering-labels-metering-label-rules networking-ovs=complete networking-linux-bridge=complete networking-odl=incomplete @@ -181,8 +181,8 @@ networking-ovn=unknown [operations.Routed_Provider_Networks] title=Routed Provider Networks status=immature -notes=The ability to present a multi-segment layer-3 - network as a single entity +notes=The ability to present a multi-segment layer-3 network as a + single entity. https://docs.openstack.org/ocata/networking-guide/config-routed-networks.html networking-ovs=partial networking-linux-bridge=partial networking-odl=incomplete