Many thanks, Antonio. I solved my minfiguration error. Ignazio Il giorno 29/ago/2015 11:24, "Antonio Messina" <antonio.s.mess...@gmail.com> ha scritto:
> I have the same configuration on both network and compute nodes. > > Tenant networks is set to gre,vxlan, but as admin you can also create vlan > networks if it's listed in type_drivers. > > .a. > Il 28/ago/2015 10:06 AM, "Ignazio Cassano" <ignaziocass...@gmail.com> ha > scritto: > >> Hi Antonio, I tried the configuration you suggested in previous emails >> without success. >> I would be gratefull if you could give me further information: >> >> 1)Did you modify the ml2_conf.ini in the computing node or also in the >> neutron network node ? >> 2) Did yoy modify tenant_network_types (ath this time we configured >> "tenant_network_types = gre" but >> we presume we must use "gre, vlan" ? >> >> Regards >> >> 2015-07-25 12:48 GMT+02:00 Antonio Messina <antonio.s.mess...@gmail.com>: >> >>> On Sat, Jul 25, 2015 at 12:38 PM, Ignazio Cassano >>> <ignaziocass...@gmail.com> wrote: >>> > You are very kind, thank you. >>> > I have only anothe doubt. >>> > When in a normal scenario you create the external net, you also create >>> an >>> > openvswtch bridge (br-ex) on the network node and add the nic >>> interface >>> > you have configuret for internet access. >>> > In our scenario we must have another interface in the intranet network >>> : >>> > must we create a bridge and add the intranet interface? >>> > Must we modify any neutron configuration file to expose the new bridge >>> ? >>> >>> The standard configuration for vlan network applies. The setup I've >>> describe does not use an external router, so you will not pass through >>> the network node and will not use br-ex bridge. >>> >>> I'm using ml2 with openvswitch, so the relevant options for ml2_conf.ini >>> are: >>> >>> [ml2] >>> type_drivers = gre,vlan,vxlan >>> mechanism_drivers = openvswitch >>> >>> [ml2_type_vlan] >>> network_vlan_ranges = vlannet:1:4000 >>> >>> [ovs] >>> bridge_mappings = vlannet:br-vlan >>> >>> br-vlan is an openvswitch bridge created on the compute node with: >>> >>> ovs-vsctl -- --may-exist add-br br-vlan >>> ovs-vsctl -- --may-exist add-port br-vlan bond0 >>> >>> in my case, bond0 is an interface on the compute node in "trunk", so >>> that packets are received with the vlan tag on the node. >>> >>> .a. >>> >>> -- >>> antonio.s.mess...@gmail.com >>> antonio.mess...@uzh.ch +41 (0)44 635 42 22 >>> S3IT: Service and Support for Science IT http://www.s3it.uzh.ch/ >>> University of Zurich >>> Winterthurerstrasse 190 >>> CH-8057 Zurich Switzerland >>> >> >>
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
