<div dir="ltr"><div><div><div>Hi! <br><br>Michaël,<br><br></div>As I understand, it is required to make a simple Fuel plugin to override standard physnet list.<br></div>Please look at <a href="https://github.com/openstack/fuel-specs/blob/master/specs/8.0/dyn-gen-physnet-set.rst">https://github.com/openstack/fuel-specs/blob/master/specs/8.0/dyn-gen-physnet-set.rst</a> for more details.<br><br></div>Sergey, <br><div><br></div><div>Could you provide more information on this?<br><br></div><div>Thanks,<br><br></div><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">Aleksey Kasatkin
<br><br></div></div></div>
<br><div class="gmail_quote">On Wed, Apr 27, 2016 at 2:36 PM, Michaël Van de Borne <span dir="ltr"><<a href="mailto:michael.van.de.borne@gmail.com" target="_blank">michael.van.de.borne@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  

    
  
  <div bgcolor="#FFFFFF" text="#000000">
    Hi all,<br>
    <br>
    According to this <a href="https://bugs.launchpad.net/fuel/+bug/1513887" target="_blank">bug</a> and
    this <a href="https://blueprints.launchpad.net/fuel/+spec/dyn-gen-physnet-set" target="_blank">blueprint</a>
    it should be possible to create multiple external networks.<br>
    I currently have the default public network with a configured range
    and am trying to add a second tagged VLAN external network to have 2
    different floating IP pools (reason: we need 1 range for external
    users and 1 range for internal users with more access to other
    services)<br>
    What I have done currently is added a new network:<br>
    <small><tt>fuel network-group --create --node-group 6 --name
        "public2" --release 1 --vlan 215 --cidr <a href="http://192.168.208.0/22" target="_blank">192.168.208.0/22</a></tt></small><br>
    and then downloading the network.yaml file to change the range from
    cidr to ip_ranges and reuploading it afterwards.<br>
    <br>
    I also have a <small><tt>network-template</tt></small> which
    creates a <tt><small>public2</small></tt> network that is added to
    the controller and compute roles. (see below, I copied only the
    public and public2 network_schemes).<br>
    <br>
    The problem here is that the network roles <small><tt>neutron/floating</tt></small>
    and <tt><small>ex </small></tt>are already configured in the
    default public network role.<br>
    <br>
    Can this be done using network templates and network groups or can
    this only be done by downloading the deployment.yaml files of each
    node and changing them manually (which can become a big chore when
    deploying ~15 nodes with multiple roles)?<br>
    <br>
    <small><tt>network_scheme:</tt><tt><br>
      </tt><tt>    public:</tt><tt><br>
      </tt><tt>        transformations:</tt><tt><br>
      </tt><tt>          - action: add-br</tt><tt><br>
      </tt><tt>            name: br-ex</tt><tt><br>
      </tt><tt>          - action: add-br</tt><tt><br>
      </tt><tt>            name: br-floating</tt><tt><br>
      </tt><tt>            provider: ovs</tt><tt><br>
      </tt><tt>          - action: add-patch</tt><tt><br>
      </tt><tt>            bridges:</tt><tt><br>
      </tt><tt>            - br-floating</tt><tt><br>
      </tt><tt>            - br-ex</tt><tt><br>
      </tt><tt>            provider: ovs</tt><tt><br>
      </tt><tt>            mtu: 65000</tt><tt><br>
      </tt><tt>          - action: add-port</tt><tt><br>
      </tt><tt>            bridge: br-ex</tt><tt><br>
      </tt><tt>            name: <% if2 %></tt><tt><br>
      </tt><tt>        endpoints:</tt><tt><br>
      </tt><tt>          - br-ex</tt><tt><br>
      </tt><tt>        roles:</tt><tt><br>
      </tt><tt>          public/vip: br-ex</tt><tt><br>
      </tt><font color="#000066"><tt>          <b>neutron/floating:
            br-floating</b></tt><b><tt><br>
          </tt></b><b><tt>          ex: br-ex</tt></b></font><tt><br>
      </tt><tt>    public2:</tt><tt><br>
      </tt><tt>        transformations:</tt><tt><br>
      </tt><tt>          - action: add-br</tt><tt><br>
      </tt><tt>            name: br-ex2</tt><tt><br>
      </tt><tt>          - action: add-br</tt><tt><br>
      </tt><tt>            name: br-floating2</tt><tt><br>
      </tt><tt>            provider: ovs</tt><tt><br>
      </tt><tt>          - action: add-patch</tt><tt><br>
      </tt><tt>            bridges:</tt><tt><br>
      </tt><tt>            - br-floating2</tt><tt><br>
      </tt><tt>            - br-ex2</tt><tt><br>
      </tt><tt>            provider: ovs</tt><tt><br>
      </tt><tt>            mtu: 65000</tt><tt><br>
      </tt><tt>          - action: add-port</tt><tt><br>
      </tt><tt>            bridge: br-ex2</tt><tt><br>
      </tt><tt>            name: <% if2 %>.215</tt><tt><br>
      </tt><tt>        endpoints:</tt><tt><br>
      </tt><tt>          - br-ex2</tt><tt><br>
      </tt><tt>        roles:</tt><tt><br>
      </tt><font color="#000066"><b><tt>          neutron/floating:
            br-floating2  //different bridge for same role?</tt><tt><br>
          </tt><tt>          ex: br-ex2</tt></b></font></small><br>
    <br>
    Thank you<br>
    <br>
    Note: we're using fuel 8.<br>
  </div>

<br>_______________________________________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to     : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
<br></blockquote></div><br></div>