<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<!DOCTYPE assembly

[

<!ENTITY % entities SYSTEM "../common/generic-entities.ent">

%entities;

]>

<assembly version="5.2" xml:lang="en"

xmlns:xlink="http://www.w3.org/1999/xlink"

xmlns:trans="http://docbook.org/ns/transclusion"

xmlns:its="http://www.w3.org/2005/11/its"

xmlns="http://docbook.org/ns/docbook">

<!-- resources section references all topic chunks used in the final article

-->

<!-- R E S O U R C E S -->

<!-- Glue files -->

<resources>

<resource href="../concepts/vxlan-introduction.xml" xml:id="_vxlan-introduction">

<description>Introduction to VXLAN</description>

</resource>

<resource href="../tasks/vxlan-configure-bridge.xml" xml:id="_vxlan-configure-bridge">

<description>Creating a network bridge with a VXLAN</description>

</resource>

<resource href="../tasks/vxlan-create-vlan.xml" xml:id="_vxlan-create-vlan">

<description>Creating a virtual network with an existing bridge</description>

</resource>

<resource href="../tasks/vxlan-configure-vm.xml" xml:id="_vxlan-configure-vm">

<description>Configuring virtual machines to use VXLAN</description>

</resource>

<resource href="../common/legal.xml" xml:id="_legal">

<description>Legal Notice</description>

</resource>

<resource href="../common/license_gfdl1.2.xml" xml:id="_gfdl">

<description>GNU Free Documentation License</description>

</resource>

</resources>

<!-- S T R U C T U R E -->

<structure renderas="article" xml:id="vxlan" xml:lang="en">

<merge>

<title>Connecting Virtual Machines to a VXLAN</title>

<revhistory xml:id="rh-vxlan">

<revision><date>2024-02-23</date>

<revdescription>

<para>

Initial version

</para>

</revdescription>

</revision>

</revhistory>

<!-- TODO: provide a listing of possible and validatable meta entry values. Maybe in our geekodoc repo? -->

<!-- add author's e-mail -->

<meta name="maintainer" content="[email protected]" its:translate="no"/>

<!-- ISO date of last update as YYYY-MM-DD -->

<meta name="updated" content="2024-02-23" its:translate="no"/>

<!-- this does not work yet. Use the dm tags listed below for now

<meta name="bugtracker" its:translate="no">

<phrase role="url">https://bugzilla.suse.com/enter_bug.cgi</phrase>

<phrase role="component">Non-product-specific documentation</phrase>

<phrase role="product">Smart Docs</phrase>

<phrase role="assignee">[email protected]</phrase>

</meta>

-->

<!-- not supported, yet. Use dm: tag for now

<meta name="translation" its:translate="no">

<phrase role="trans">yes</phrase>

<phrase role="language">de-de,cs-cz</phrase>

</meta>

-->

<!-- enter the platform identifier or a list of

identifiers, separated by ; -->

<!-- For a full list of meta tags and their values,

see https://confluence.suse.com/x/aQDWNg

-->

<meta name="architecture" its:translate="no">

<phrase>&x86-64;</phrase>

<phrase>&power;</phrase>

</meta>

<meta name="productname" its:translate="no">

<productname version="15 SP6">&sles;</productname>

</meta>

<meta name="title" its:translate="yes">Connecting VMs to a VXLAN</meta>

<meta name="description" its:translate="yes">The VXLAN protocol offers more than four thousand separate virtual networks where VMs can communicate</meta>

<meta name="social-descr" its:translate="yes">Networking for large cloud computing deployments</meta>

<!-- suitable category, comma-separated list of categories -->

<meta name="task">

<phrase>Virtualization</phrase>

<phrase>Configuration</phrase>

</meta>

<meta name="series">Smart Docs</meta>

<dm:docmanager xmlns:dm="urn:x-suse:ns:docmanager">

<dm:bugtracker>

<dm:url>https://bugzilla.suse.com/enter_bug.cgi</dm:url>

<dm:component>Documentation</dm:component>

<dm:product>SUSE Linux Enterprise Server 16.0</dm:product>

<!-- provide your BUGZILLA e-mail address, otherwise this does not work correctly-->

<dm:assignee>[email protected]</dm:assignee>

</dm:bugtracker>

<dm:translation>yes</dm:translation>

</dm:docmanager>

<abstract>

<variablelist>

<varlistentry>

<term>WHAT?</term>

<listitem>

<para>

The VXLAN protocol can address more isolated virtual networks

than the traditional VLAN. Within these networks, groups of

virtual machines (VMs) can safely communicate even across regions.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>WHY?</term>

<listitem>

<para>

You want to connect virtual machines to VXLAN networks in a

large data center and configure them to communicate with other

VMs in a dedicated network space.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>EFFORT</term>

<listitem>

<para>

30 minutes is enough to learn and configure a VXLAN to enable

communication between VMs.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>REQUIREMENTS</term>

<listitem>

<itemizedlist>

<listitem>

<para>

A &productnameshort; &libvirt;-based &vmhost; with an

Ethernet network connection configured by &nm;.

</para>

</listitem>

</itemizedlist>

</listitem>

</varlistentry>

</variablelist>

</abstract>

</merge>

<module resourceref="_vxlan-introduction" renderas="section">

<merge>

<title>Introduction</title>

</merge>

</module>

<module resourceref="_vxlan-configure-bridge" renderas="section">

<merge>

<title>Creating a network bridge with a VXLAN attached</title>

<abstract>

<para></para>

</abstract>

</merge>

</module>

<module renderas="section" resourceref="_vxlan-create-vlan">

<merge>

<title>Creating a virtual network</title>

<abstract>

<para></para>

</abstract>

</merge>

</module>

<module renderas="section" resourceref="_vxlan-configure-vm">

<merge>

<title>Configuring virtual machines</title>

<abstract>

<para></para>

</abstract>

</merge>

</module>

<module resourceref="_legal"/>

<module resourceref="_gfdl">

<output renderas="appendix"/>

</module>

</structure>

</assembly>