aceec15371
Better follow conventions, especially: * remove Latinism like via and i.e. * use variable lists * Add missing <filename> * wrap long lines Change-Id: I2a537df78ddf4fbeb127b058bf05caaf42441d5f
22 lines
1.8 KiB
XML
22 lines
1.8 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<chapter xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
xmlns:xlink="http://www.w3.org/1999/xlink"
|
|
xmlns="http://docbook.org/ns/docbook"
|
|
version="5.0"
|
|
xml:id="ch030_state-of-networking">
|
|
<?dbhtml stop-chunking?>
|
|
<title>State of networking</title>
|
|
<para>OpenStack Networking in the Grizzly release enables the end-user or tenant to define, utilize, and consume networking resources in new ways that had not been possible in previous OpenStack Networking releases. OpenStack Networking provides a tenant-facing API for defining network connectivity and IP addressing for instances in the cloud in addition to orchestrating the network configuration. With the transition to an API-centric networking service, cloud architects and administrators should take into consideration best practices to secure physical and virtual network infrastructure and services.</para>
|
|
<para>
|
|
OpenStack Networking was designed with a plug-in architecture
|
|
that provides extensibility of the API through open source
|
|
community or third-party services. As you evaluate your
|
|
architectural design requirements, it is important to determine
|
|
what features are available in OpenStack Networking core
|
|
services, any additional services that are provided by
|
|
third-party products, and what supplemental services are
|
|
required to be implemented in the physical
|
|
infrastructure.</para>
|
|
<para>This section is a high-level overview of what processes and best practices should be considered when implementing OpenStack Networking. We will talk about the current state of services that are available, what future services will be implemented, and the current limitations in this project.</para>
|
|
</chapter>
|