Merge "Feature Classification Cleanup"
This commit is contained in:
commit
3d5d9e8957
|
@ -9,8 +9,8 @@ Goals
|
||||||
~~~~~
|
~~~~~
|
||||||
|
|
||||||
The object of this document is to inform users whether or not
|
The object of this document is to inform users whether or not
|
||||||
features are complete, well-documented, stable, and tested.
|
features are complete, well documented, stable, and tested.
|
||||||
This approach ensures a good user-experience for those well-maintained features.
|
This approach ensures good user experience for those well maintained features.
|
||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
|
|
||||||
|
@ -35,7 +35,7 @@ Feature status
|
||||||
Immature
|
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.
|
use cases.
|
||||||
|
|
||||||
An immature feature is a feature being actively developed, which is only
|
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 API documentation including concept and REST call definition.
|
||||||
* Complete Administrator documentation.
|
* Complete Administrator documentation.
|
||||||
* Tempest tests that define the correct functionality of the feature.
|
* 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.
|
* Low probability of support for the feature being dropped.
|
||||||
|
|
||||||
Required
|
Required
|
||||||
--------
|
--------
|
||||||
|
|
||||||
Required features are core networking principles that have been thoroughly
|
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.
|
In addition they satisfy the same criteria for any mature features.
|
||||||
|
|
||||||
|
|
|
@ -23,8 +23,7 @@ status=required
|
||||||
api=core
|
api=core
|
||||||
cli=openstack network *
|
cli=openstack network *
|
||||||
notes=The ability to create, modify and delete networks.
|
notes=The ability to create, modify and delete networks.
|
||||||
Other OpenStack Client commands are create, delete, list,
|
https://developer.openstack.org/api-ref/networking/v2/#networks
|
||||||
segment list, segment show, set, show.
|
|
||||||
networking-ovs=complete
|
networking-ovs=complete
|
||||||
networking-linux-bridge=complete
|
networking-linux-bridge=complete
|
||||||
networking-odl=complete
|
networking-odl=complete
|
||||||
|
@ -37,9 +36,7 @@ status=required
|
||||||
api=core
|
api=core
|
||||||
cli=openstack subnet *
|
cli=openstack subnet *
|
||||||
notes=The ability to create and manipulate subnets and subnet pools.
|
notes=The ability to create and manipulate subnets and subnet pools.
|
||||||
Other OpenStack Client commands are create, delete, list,
|
https://developer.openstack.org/api-ref/networking/v2/#subnets
|
||||||
pool create, pool delete, pool list, pool set, pool show,
|
|
||||||
set, show.
|
|
||||||
networking-ovs=complete
|
networking-ovs=complete
|
||||||
networking-linux-bridge=complete
|
networking-linux-bridge=complete
|
||||||
networking-odl=complete
|
networking-odl=complete
|
||||||
|
@ -52,8 +49,7 @@ status=required
|
||||||
api=core
|
api=core
|
||||||
cli=openstack port *
|
cli=openstack port *
|
||||||
notes=The ability to create and manipulate ports.
|
notes=The ability to create and manipulate ports.
|
||||||
Other OpenStack Client commands are create, delete, list, set,
|
https://developer.openstack.org/api-ref/networking/v2/#ports
|
||||||
show.
|
|
||||||
networking-ovs=complete
|
networking-ovs=complete
|
||||||
networking-linux-bridge=complete
|
networking-linux-bridge=complete
|
||||||
networking-odl=complete
|
networking-odl=complete
|
||||||
|
@ -66,9 +62,7 @@ status=required
|
||||||
api=router
|
api=router
|
||||||
cli=openstack router *
|
cli=openstack router *
|
||||||
notes=The ability to create and manipulate routers.
|
notes=The ability to create and manipulate routers.
|
||||||
Other OpenStack Client commands are create, add port,
|
https://developer.openstack.org/api-ref/networking/v2/#routers-routers
|
||||||
add subnet, delete, list, remove port, remove subnet,
|
|
||||||
set, show.
|
|
||||||
networking-ovs=complete
|
networking-ovs=complete
|
||||||
networking-linux-bridge=complete
|
networking-linux-bridge=complete
|
||||||
networking-odl=complete
|
networking-odl=complete
|
||||||
|
@ -82,8 +76,7 @@ api=security-group
|
||||||
cli=openstack security group *
|
cli=openstack security group *
|
||||||
notes=Security groups are set by default, and can be modified to control
|
notes=Security groups are set by default, and can be modified to control
|
||||||
ingress & egress traffic.
|
ingress & egress traffic.
|
||||||
Other OpenStack Client commands are create, delete, list, rule create,
|
https://developer.openstack.org/api-ref/networking/v2/#security-groups-security-groups
|
||||||
rule delete, rule list, rule show, set, show.
|
|
||||||
networking-ovs=complete
|
networking-ovs=complete
|
||||||
networking-linux-bridge=complete
|
networking-linux-bridge=complete
|
||||||
networking-odl=complete
|
networking-odl=complete
|
||||||
|
@ -107,6 +100,7 @@ title=Distributed Virtual Routers
|
||||||
status=immature
|
status=immature
|
||||||
api=dvr
|
api=dvr
|
||||||
notes=The ability to support the distributed virtual routers.
|
notes=The ability to support the distributed virtual routers.
|
||||||
|
https://wiki.openstack.org/wiki/Neutron/DVR
|
||||||
networking-ovs=complete
|
networking-ovs=complete
|
||||||
networking-linux-bridge=incomplete
|
networking-linux-bridge=incomplete
|
||||||
networking-odl=partial
|
networking-odl=partial
|
||||||
|
@ -130,6 +124,7 @@ title=Quality of Service
|
||||||
status=mature
|
status=mature
|
||||||
api=qos
|
api=qos
|
||||||
notes=Support for Neutron Quality of Service policies and API.
|
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-ovs=complete
|
||||||
networking-linux-bridge=partial
|
networking-linux-bridge=partial
|
||||||
networking-odl=partial
|
networking-odl=partial
|
||||||
|
@ -139,6 +134,7 @@ networking-ovn=complete
|
||||||
[operation.BGP]
|
[operation.BGP]
|
||||||
title=Border Gateway Protocol
|
title=Border Gateway Protocol
|
||||||
status=immature
|
status=immature
|
||||||
|
notes=https://developer.openstack.org/api-ref/networking/v2/#bgp-mpls-vpn-interconnection
|
||||||
networking-ovs=complete
|
networking-ovs=complete
|
||||||
networking-linux-bridge=unknown
|
networking-linux-bridge=unknown
|
||||||
networking-odl=unknown
|
networking-odl=unknown
|
||||||
|
@ -150,8 +146,7 @@ title=DNS
|
||||||
status=mature
|
status=mature
|
||||||
api=dns-integration
|
api=dns-integration
|
||||||
notes=The ability to integrate with an external DNS
|
notes=The ability to integrate with an external DNS
|
||||||
as a Service. http://docs.openstack.org/newton/
|
as a Service. http://docs.openstack.org/newton/networking-guide/config-dns-int.html
|
||||||
networking-guide/config-dns-int.html
|
|
||||||
networking-ovs=complete
|
networking-ovs=complete
|
||||||
networking-linux-bridge=complete
|
networking-linux-bridge=complete
|
||||||
networking-odl=complete
|
networking-odl=complete
|
||||||
|
@ -162,6 +157,9 @@ networking-ovn=complete
|
||||||
title=Trunk Ports
|
title=Trunk Ports
|
||||||
status=mature
|
status=mature
|
||||||
api=trunk
|
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-ovs=complete
|
||||||
networking-linux-bridge=complete
|
networking-linux-bridge=complete
|
||||||
networking-odl=incomplete
|
networking-odl=incomplete
|
||||||
|
@ -172,6 +170,8 @@ networking-ovn=complete
|
||||||
title=Metering
|
title=Metering
|
||||||
status=mature
|
status=mature
|
||||||
api=metering
|
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-ovs=complete
|
||||||
networking-linux-bridge=complete
|
networking-linux-bridge=complete
|
||||||
networking-odl=incomplete
|
networking-odl=incomplete
|
||||||
|
@ -181,8 +181,8 @@ networking-ovn=unknown
|
||||||
[operations.Routed_Provider_Networks]
|
[operations.Routed_Provider_Networks]
|
||||||
title=Routed Provider Networks
|
title=Routed Provider Networks
|
||||||
status=immature
|
status=immature
|
||||||
notes=The ability to present a multi-segment layer-3
|
notes=The ability to present a multi-segment layer-3 network as a
|
||||||
network as a single entity
|
single entity. https://docs.openstack.org/ocata/networking-guide/config-routed-networks.html
|
||||||
networking-ovs=partial
|
networking-ovs=partial
|
||||||
networking-linux-bridge=partial
|
networking-linux-bridge=partial
|
||||||
networking-odl=incomplete
|
networking-odl=incomplete
|
||||||
|
|
Loading…
Reference in New Issue