<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle25
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1820346630;
mso-list-type:hybrid;
mso-list-template-ids:274755826 -1169928188 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;}
@list l0:level1
{mso-level-start-at:73;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:Calibri;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Hello OpenStack and NetVirt<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">I’d really appreciate some guidance here because I am a confused as to how I should be building this.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">To explain what I want to do:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1"><span style="mso-fareast-language:EN-US">Controller in one location with a single IP connection (1 GE)<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1"><span style="mso-fareast-language:EN-US">Compute node in a remote location with 4 10GE connections for public networking and 1GE IP connection to the Controller<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">The VMs on the Compute node will each have 2 10GE connections as they will be forwarding data.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">I have successfully deployed a Pike system with ODL with the previously attached local.conf.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">However, there seem to be a number of areas of confusion for me:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1"><span style="mso-fareast-language:EN-US">In the local.conf for the Control node, why do I need to declare ODL_PROVIDER_MAPPINGS ? There will be no connection to data-forwarding networks
at the Controller location. However, if I leave these out (I declare physnet1-physnet4 and bridge them to disconnected ports on the Control node em1-em4) when I try to build the VXLAN network with Neutron, I get a failure in that the Provider Network does
not exist.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1"><span style="mso-fareast-language:EN-US">If I declare the physnet1-physnet4 on the Compute node, whilst this works, when I try to add the local networks using Neutron, it appears to
be using information relevant to the Control node, not the Compute node.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1"><span style="mso-fareast-language:EN-US">The only way that I have found I can make any of this work is to essentially build a Layer 2 network layout on the Control node which matches
that of the Compute node and is connected to it. This is problematic in my layout because I don’t have layer 2 connectivity between the locations with the Control and the Compute nodes.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1"><span style="mso-fareast-language:EN-US">Even when that happens, the DHCP server appears to be on the Control node, not the Compute node. That should be fine if the VXLAN tunnel is
up, but I’ve found that the VXLAN flow is only built on the physical layer 2 link between the systems and I don’t have any layer 2 links on the Control node.
<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Also, in local.conf, I seem to have to declare PUBLIC_BRIDGE. I have no idea what this does or how the system would react to having four PUBLIC_BRIDGE entries:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">PUBLIC_BRIDGE=br-physnet1<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">#PUBLIC_PHYSICAL_NETWORK=physnet1,physnet2,physnet3,physnet4<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">PUBLIC_PHYSICAL_NETWORK=physnet1<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">#ML2_VLAN_RANGES=physnet1,physnet2,physnet3,physnet4<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">ML2_VLAN_RANGES=physnet1<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">#ODL_PROVIDER_MAPPINGS=physnet1:br-physnet1,physnet2:br-physnet2,physnet3:br-physnet3,physnet4:br-physnet4<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">ODL_PROVIDER_MAPPINGS=physnet1:br-physnet1<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">The commented out lines are what I eventually want but only on the Compute node. br-physnetx bridges to physical interface emx respectively. The Control node really needs no VM side networking
at all.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">I’m probably getting very confused here – what I want is the ability at the remote location to have four 10GE connections to a local Layer2 network and simply have 2 of those appear on a Virtual
Machine instantiated at that remove location. The physical network ports should be directly bridged to the VM.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">I then want the third network to boot-up as normal from OpenStack and obtain an internal IP address so that I can ssh to the machine.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">I’d really appreciate some assistance because I am at the point of not understanding the options here or how to configure them into the DevStack builder.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><br>
Thanks<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><br>
David<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></a></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Lake D Mr (PG/R - Elec Electronic Eng)
<br>
<b>Sent:</b> 19 December 2017 22:27<br>
<b>To:</b> 'Trinath Somanchi' <trinath.somanchi@nxp.com>; 'openstack@lists.openstack.org' <openstack@lists.openstack.org><br>
<b>Subject:</b> RE: Issues Understanding Neutron Networking Layout<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">I tried sending the log file to the list but it was rejected as too large.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">So I’ve zipped the log file.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">David<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Lake D Mr (PG/R - Elec Electronic Eng)
<br>
<b>Sent:</b> 19 December 2017 16:02<br>
<b>To:</b> 'Trinath Somanchi' <<a href="mailto:trinath.somanchi@nxp.com">trinath.somanchi@nxp.com</a>>;
<a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
<b>Subject:</b> RE: Issues Understanding Neutron Networking Layout<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">OK – the log file from trying to start a new instance on the Compute server (intel-test2) is attached. Control server is called “23-210”<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Line 2017 doesn’t look right to me:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Dec 19 15:26:36 23-210 neutron-server[169175]: DEBUG neutron.plugins.ml2.managers [req-e60dabcc-4c78-4ad2-8eed-11c70e5433dc req-ca0a8968-16cf-4548-9654-a248a28268ca service neutron] Attempting to
bind port f1702fcc-49e0-4b98-8304-860ee2c436aa on host intel-test2 at level 0 using segments [{'network_id': '3862495f-43d2-4dbc-a67b-ade91d97e141', 'segmentation_id': 1500, 'physical_network': None, 'id': '4d45af9a-72ee-4fef-9042-a5e7debff29b', 'network_type':
u'vxlan'}] {{(pid=169276) _bind_port_level /opt/stack/neutron/neutron/plugins/ml2/managers.py:765}}<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Segmentation ID 1500 is the VXLAN I want to use but it says “Physical Network:None”<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Is this correct?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">David<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Trinath Somanchi [<a href="mailto:trinath.somanchi@nxp.com">mailto:trinath.somanchi@nxp.com</a>]
<br>
<b>Sent:</b> 19 December 2017 10:30<br>
<b>To:</b> Lake D Mr (PG/R - Elec Electronic Eng) <<a href="mailto:d.lake@surrey.ac.uk">d.lake@surrey.ac.uk</a>>;
<a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
<b>Subject:</b> RE: Issues Understanding Neutron Networking Layout<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">Check /opt/stack/logs ?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">/<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> Trinath Somanchi | HSDC | NXP INDIA<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> <a href="mailto:d.lake@surrey.ac.uk">
d.lake@surrey.ac.uk</a> [<a href="mailto:d.lake@surrey.ac.uk">mailto:d.lake@surrey.ac.uk</a>]
<br>
<b>Sent:</b> Tuesday, December 19, 2017 3:59 PM<br>
<b>To:</b> Trinath Somanchi <<a href="mailto:trinath.somanchi@nxp.com">trinath.somanchi@nxp.com</a>>;
<a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
<b>Subject:</b> RE: Issues Understanding Neutron Networking Layout<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal">Can you tell me where to look? None of the usual “screen” logs are there with the latest DevStack and the system doesn’t seem to be populating any of the /var/log locations etiher.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">David<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Trinath Somanchi [<a href="mailto:trinath.somanchi@nxp.com">mailto:trinath.somanchi@nxp.com</a>]
<br>
<b>Sent:</b> 19 December 2017 08:51<br>
<b>To:</b> Lake D Mr (PG/R - Elec Electronic Eng) <<a href="mailto:d.lake@surrey.ac.uk">d.lake@surrey.ac.uk</a>>;
<a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
<b>Subject:</b> RE: Issues Understanding Neutron Networking Layout<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">Can you check neutron server/agent logs for exact error to debug ?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">/<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> Trinath Somanchi | HSDC | NXP INDIA<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> <a href="mailto:d.lake@surrey.ac.uk">
d.lake@surrey.ac.uk</a> [<a href="mailto:d.lake@surrey.ac.uk">mailto:d.lake@surrey.ac.uk</a>]
<br>
<b>Sent:</b> Tuesday, December 19, 2017 2:02 PM<br>
<b>To:</b> <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
<b>Subject:</b> [Openstack] Issues Understanding Neutron Networking Layout<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal">Hello<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’m trying to create a Pike system with Carbon ODL integration using a single Controller node and a single Compute node.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The Controller Node has a single 1GE NIC to the management network. It will not run any compute or network services.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The Compute Node has a single 1GE NIC to the management network and 4 x 10GE NICS for public network access. I will be creating 4 VXNets, 4 routers, 4 pools of public floating IP addresses.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have built the machines using DevStack (configs attached).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It seems that even though the Controller node will have no network/compute functions, I still need to declare the ODL and networking parts in the local.conf on the controller. But this implies that the Controller also has to have access
to the 10GE network which I don’t want or need.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have created 4 OVS bridges on both the Controller and the Compute nodes but the corresponding NICs on the Controller are not connected anywhere. The bridges are br-physnet1 to br-physnet4 and these link to em1 to em4 respectively. Only
the em1 – em4 on the Compute node are actually active.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I then create the VXLAN, router and DHCP agent. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">However, when I try to start an instance on the Compute node post DevStack installation, I hit an issue where the GUI tells me it has been “unable to allocate network.”<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I see no attempt to create a VXLAN between the Controller and the Compute node. IPTables is open and a sniff on port 4789 reveals no traffic back and forth (on either side).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Does the Controller need to be physically connected to the same public facing networks as the Compute node?
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Alternatively, how can I get all the Networking functions to run in the Compute node so that the Controller is just a controller?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">David<o:p></o:p></p>
</div>
</body>
</html>