<div dir="auto">Hi Dan..noted and thank you. I will proceed wth the deployment. Thank you so much for your great support. Thanks to all too..<div dir="auto">Have a nice day...</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 20 Oct 2020 23:24 Dan Sneddon, <<a href="mailto:dsneddon@redhat.com">dsneddon@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Since you don't have a dedicated provisioning port, you want the control <br>
plane address directly on the bond rather than on a separate NIC. I <br>
modified the templates in 2-linux-bonds-vlans to use the first 2 NICs <br>
for the bond with the control plane IP and VLANs, and the other bond for <br>
Tenant VLAN (tunnel traffic) and a bridge on the second bond for tenant <br>
provider networks.<br>
<br>
The only changes necessary were moving the IP/subnet/route information <br>
from the dedicated NIC to the first bond, and then renumbering the NICs <br>
in the bonds to 1/2 and 3/4 instead of 2/3 and 4/5.<br>
<br>
Note that in order for this example to work, you would need to use LACP <br>
bonds with the switch configured with LACP fallback so that the first <br>
NIC becomes a regular host port for DHCP and PXE boot prior to the host <br>
OS being installed. Once the host OS is installed and the bond is <br>
configured, the LACP bond will be negotiated and the provisioning link <br>
will become a slave in the first bond. You may want to set the switch to <br>
LACP passive so that it waits for the host to bring up the bond.<br>
<br>
I have attached the modified NIC config templates.<br>
<br>
-Dan<br>
<br>
On 10/19/20 5:54 AM, dangerzone ar wrote:<br>
> Hi Marios and team,<br>
> Thank you for pointing me out. Need further advice.<br>
> <br>
> Below is my deployment command :-<br>
> /openstack overcloud deploy --templates \<br>
> /<br>
> / -r ~/templates/roles_data.yaml \<br>
> -n ~/templates/network_data.yaml \<br>
> -e <br>
> /usr/share/openstack-tripleo-heat-templates/environments/network-environment.yaml <br>
> \<br>
> -e <br>
> /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml <br>
> \<br>
> -e <br>
> /usr/share/openstack-tripleo-heat-templates/environments/docker-ha.yaml<br>
> -e ~/templates/network.yaml \<br>
> -e ~/templates/scheduler_hints_env.yaml \<br>
> -e ~/templates/node-info.yaml/<br>
> <br>
> I have copy 2-linux-bonds-vlans to nic-configs folder below:-<br>
> /cp <br>
> ~/generated-openstack-tripleo-heat-templates/network/config/2-linux-bonds-vlans/* <br>
> ~/templates/nic-configs/<br>
> /<br>
> /<br>
> In the nic-configs folder got 3 files<br>
> i.README<br>
> ii.controller.yaml<br>
> iii.compute-dpdk.yaml<br>
> <br>
> My initial deployment only involves controllers and computes (no dpdk), <br>
> should I use 'compute-dpdk.yaml' file to configure my NIC setup, is it <br>
> the same template for non-dpdk computes?<br>
> My actual network, vlan and nic setup:-<br>
> (1)bond0 (NIC1+NIC2)<br>
> -Internal API -vlan10<br>
> -External -vlan60<br>
> -Provisioning - vlan24<br>
> *provisoning is configure on the same bond0 of NIC1 and NIC2<br>
> <br>
> (2)bond1 (NIC5+NIC6)<br>
> -Tenant -vlan20<br>
> <br>
> compute-dpdk.yaml:-<br>
> The template have nic1 as single nic, while nic2+nic3 on another bond <br>
> and nic4+nic5 as another bond. Which line should I set as bond0 and <br>
> bond1? Appreciate to confirm, I would be thankful if <br>
> someone can point which line I should edit bond0 and bond1 as per setup <br>
> above. I attached file compute-dpdk.yaml and controller.yaml.<br>
> <br>
> Thank you for your help, may god bless you all.<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> On Mon, Oct 19, 2020 at 3:08 PM Marios Andreou <<a href="mailto:marios@redhat.com" target="_blank" rel="noreferrer">marios@redhat.com</a> <br>
> <mailto:<a href="mailto:marios@redhat.com" target="_blank" rel="noreferrer">marios@redhat.com</a>>> wrote:<br>
> <br>
> <br>
> <br>
> On Mon, Oct 19, 2020 at 8:14 AM dangerzone ar <<a href="mailto:dangerzonen@gmail.com" target="_blank" rel="noreferrer">dangerzonen@gmail.com</a><br>
> <mailto:<a href="mailto:dangerzonen@gmail.com" target="_blank" rel="noreferrer">dangerzonen@gmail.com</a>>> wrote:<br>
> <br>
> Hi.. I'm looking help to deploy overcloud (openstack train) as<br>
> per initial req below:-<br>
> a) 3 controllers<br>
> b) 5 computes<br>
> c) 2 bonds (bond0 - all vlan except for tenant , bond1 - for<br>
> tenant vlan only)<br>
> *No external storage and dpdk computes for now as trying to<br>
> deploy these 3 controllers and 5 computes first.<br>
> <br>
> I have gone through openstack web, blogs and some other<br>
> resources and failed to deploy with success. One of my problems<br>
> is to identify the right templates to use for my setup and<br>
> config for 2 bonds above.<br>
> I have struggled to deploy overcloud for a month without<br>
> success...I really appreciate your help and support to guide me.<br>
> Please your help and support is much appreciated. I request help<br>
> from everybody. Thank you<br>
> <br>
> <br>
> <br>
> Hello,<br>
> <br>
> The network templates in tripleo-heat-templates are always meant as<br>
> an example which you will need to customize for your specific<br>
> deployment requirements.<br>
> <br>
> That being said, there are a number of examples there which you<br>
> should be able to adapt to your needs. For 2 bonds with vlans I<br>
> believe this [1] is the config you will need - nics 2/3 go into one<br>
> bond then nics 4/5 into another.<br>
> <br>
> Since you're looking at train one thing I can think of is to ensure<br>
> you have the docker-ha [3] environment file included (deployment was<br>
> by default non-ha [2] before ussuri).<br>
> <br>
> Hope it helps you a bit :). Hopefully others can also chime in with<br>
> more specific info about the network config (I haven't touched those<br>
> for a very long time) but I think you'll have to give more details<br>
> about the full deployment command you're currently using (i.e. what<br>
> are the -e environment_files you're now passing) and the problems<br>
> you have,<br>
> <br>
> regards, marios<br>
> <br>
> [1]<br>
> <a href="https://opendev.org/openstack/tripleo-heat-templates/src/commit/ed46b26527b5f0ac09712c98fe8560d752544f80/network/config/2-linux-bonds-vlans/role.role.j2.yaml#L169-L188" rel="noreferrer noreferrer" target="_blank">https://opendev.org/openstack/tripleo-heat-templates/src/commit/ed46b26527b5f0ac09712c98fe8560d752544f80/network/config/2-linux-bonds-vlans/role.role.j2.yaml#L169-L188</a><br>
> <<a href="https://opendev.org/openstack/tripleo-heat-templates/src/commit/ed46b26527b5f0ac09712c98fe8560d752544f80/network/config/2-linux-bonds-vlans/role.role.j2.yaml#L169-L188" rel="noreferrer noreferrer" target="_blank">https://opendev.org/openstack/tripleo-heat-templates/src/commit/ed46b26527b5f0ac09712c98fe8560d752544f80/network/config/2-linux-bonds-vlans/role.role.j2.yaml#L169-L188</a>><br>
> [2]<br>
> <a href="https://opendev.org/openstack/tripleo-heat-templates/src/commit/ed46b26527b5f0ac09712c98fe8560d752544f80/overcloud-resource-registry-puppet.j2.yaml#L172" rel="noreferrer noreferrer" target="_blank">https://opendev.org/openstack/tripleo-heat-templates/src/commit/ed46b26527b5f0ac09712c98fe8560d752544f80/overcloud-resource-registry-puppet.j2.yaml#L172</a><br>
> <<a href="https://opendev.org/openstack/tripleo-heat-templates/src/commit/ed46b26527b5f0ac09712c98fe8560d752544f80/overcloud-resource-registry-puppet.j2.yaml#L172" rel="noreferrer noreferrer" target="_blank">https://opendev.org/openstack/tripleo-heat-templates/src/commit/ed46b26527b5f0ac09712c98fe8560d752544f80/overcloud-resource-registry-puppet.j2.yaml#L172</a>><br>
> [3]<br>
> <a href="https://opendev.org/openstack/tripleo-heat-templates/src/commit/ed46b26527b5f0ac09712c98fe8560d752544f80/environments/docker-ha.yaml" rel="noreferrer noreferrer" target="_blank">https://opendev.org/openstack/tripleo-heat-templates/src/commit/ed46b26527b5f0ac09712c98fe8560d752544f80/environments/docker-ha.yaml</a><br>
> <<a href="https://opendev.org/openstack/tripleo-heat-templates/src/commit/ed46b26527b5f0ac09712c98fe8560d752544f80/environments/docker-ha.yaml" rel="noreferrer noreferrer" target="_blank">https://opendev.org/openstack/tripleo-heat-templates/src/commit/ed46b26527b5f0ac09712c98fe8560d752544f80/environments/docker-ha.yaml</a>><br>
> <br>
> <br>
<br>
-- <br>
Dan Sneddon | Senior Principal Software Engineer<br>
<a href="mailto:dsneddon@redhat.com" target="_blank" rel="noreferrer">dsneddon@redhat.com</a> | <a href="http://redhat.com/cloud" rel="noreferrer noreferrer" target="_blank">redhat.com/cloud</a><br>
dsneddon:irc | @dxs:twitter<br>
</blockquote></div>