openstack-manuals/doc/arch-design/specialized/section_networking_specialized.xml
kallimachos 993ce73bf3 Remove passive voice from Chap 9 Arch guide
Change-Id: I46a72221528b656d153a630e4053fb70fe563168
Closes-Bug: #1442451
2015-04-12 16:29:16 +10:00

40 lines
1.9 KiB
XML

<?xml version="1.0" encoding="UTF-8"?>
<section xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink"
version="5.0"
xml:id="specialized-networking-example">
<?dbhtml stop-chunking?>
<title>Specialized networking example</title>
<para>Some applications that interact with a network require
specialized connectivity. Applications such as a looking glass
require the ability to connect to a BGP peer, or route
participant applications may need to join a network at a layer
2 level.</para>
<section xml:id="challenges-specialized-networking">
<title>Challenges</title>
<para>Connecting specialized network applications to their
required resources alters the design of an OpenStack
installation. Installations that rely on overlay networks are
unable to support a routing participant, and may also block
layer-2 listeners.</para>
</section>
<section xml:id="possible-solutions-specialized-networking">
<title>Possible solutions</title>
<para>Deploying an OpenStack installation using OpenStack Networking with a
provider network allows direct layer-2 connectivity to an
upstream networking device. This design provides the layer-2
connectivity required to communicate via Intermediate
System-to-Intermediate System (ISIS) protocol or to pass
packets controlled by an OpenFlow controller. Using the
multiple layer-2 plug-in with an agent such as
<glossterm>Open vSwitch</glossterm>
allows a private connection through a VLAN directly to a
specific port in a layer-3 device. This allows a BGP
point-to-point link to join the autonomous
system. Avoid using layer-3 plug-ins as they divide the
broadcast domain and prevent router adjacencies from
forming.</para>
</section>
</section>