Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

how to create new network in mirantis fuel?

Hi,

I'm using Mirantis Fuel 6.0 to deploy openstack for 10 nodes, these nodes have 6 NICs each.

The name of these NICs will be eth0.. eth5 in the Ubuntu host.

Currently there're 4 default networks defined Mirantis Fuel, "Private", "Public", "Management" and "Storage". and a VM instance can use "Private" and "Public"

eth0: Private
eth1: Public
eth2: Management
eth3: Storage

eth4: currently not used
eth5: currently not used

Is it possible to add another 2 user defined network in /etc/puppet/manifests/site.pp, so that the VM instance can use them? these "user defined" networks should only be used for VM instances,

thank you for comments in advnace!

how to create new network in mirantis fuel?

Hi,

I'm using Mirantis Fuel 6.0 to deploy openstack for 10 nodes, these nodes have 6 NICs each.

The name of these NICs will be eth0.. eth5 in the Ubuntu host.

Currently there're 4 default networks defined Mirantis Fuel, "Private", "Public", "Management" and "Storage". and a VM instance can use "Private" and "Public"

eth0: Private
eth1: Public
eth2: Management
eth3: Storage

eth4: currently not used
eth5: currently not used

Is it possible to add another 2 user defined network in /etc/puppet/manifests/site.pp, so that the VM instance can use them? these "user defined" networks should only be used for VM instances,

thank you for comments in advnace!

April 20th: Since I don't know how to modify the site.pp file, tried another direction: modify the deployment yaml files. here below is what I did.

  1. download the deployment yaml files, like described in http://docs.mirantis.com/openstack/fuel/fuel-6.0/operations.html#id32
  2. modify the section "network_scheme", add endpoint, role and transformation, add new phys_nets in quantum_settings and andd new predefined_networks.

please refer to the attachment for the modifications.

After upload the modified yaml and deploy changes, I found the new bridge br-prv-2 is created

Bridge "br-prv-2"
    Port "br-prv-2"
        Interface "br-prv-2"
            type: internal
    Port "br-prv-2--br-eth1"
        Interface "br-prv-2--br-eth1"
            type: patch
            options: {peer="br-eth1--br-prv-2"}

But the /etc/neutron/plugins/ml2/ml2_conf.ini doesn't change, it still only contains one physnet (physnet2)

...............
[ml2_type_vlan]
network_vlan_ranges =physnet2:101:102
................
[ovs]
enable_tunneling=False
integration_bridge=br-int
bridge_mappings=physnet2:br-prv

If I manually change the ml2_conf.ini and restart neutron-server on all controllers, following error popped up during VM creating.

2015-04-20 14:21:50.263 29219 TRACE nova.compute.manager [instance: fc942094-db2c-442b-8183-340b5aa1e546] Traceback (most recent call last):
2015-04-20 14:21:50.263 29219 TRACE nova.compute.manager [instance: fc942094-db2c-442b-8183-340b5aa1e546]   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2231, in _build_resources
2015-04-20 14:21:50.263 29219 TRACE nova.compute.manager [instance: fc942094-db2c-442b-8183-340b5aa1e546]     yield resources
2015-04-20 14:21:50.263 29219 TRACE nova.compute.manager [instance: fc942094-db2c-442b-8183-340b5aa1e546]   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2101, in _build_and_run_instance
2015-04-20 14:21:50.263 29219 TRACE nova.compute.manager [instance: fc942094-db2c-442b-8183-340b5aa1e546]     block_device_info=block_device_info)
2015-04-20 14:21:50.263 29219 TRACE nova.compute.manager [instance: fc942094-db2c-442b-8183-340b5aa1e546]   File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2619, in spawn
2015-04-20 14:21:50.263 29219 TRACE nova.compute.manager [instance: fc942094-db2c-442b-8183-340b5aa1e546]     write_to_disk=True)
2015-04-20 14:21:50.263 29219 TRACE nova.compute.manager [instance: fc942094-db2c-442b-8183-340b5aa1e546]   File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 4158, in _get_guest_xml
2015-04-20 14:21:50.263 29219 TRACE nova.compute.manager [instance: fc942094-db2c-442b-8183-340b5aa1e546]     context)
2015-04-20 14:21:50.263 29219 TRACE nova.compute.manager [instance: fc942094-db2c-442b-8183-340b5aa1e546]   File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3936, in _get_guest_config
2015-04-20 14:21:50.263 29219 TRACE nova.compute.manager [instance: fc942094-db2c-442b-8183-340b5aa1e546]     flavor, CONF.libvirt.virt_type)
2015-04-20 14:21:50.263 29219 TRACE nova.compute.manager [instance: fc942094-db2c-442b-8183-340b5aa1e546]   File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 383, in get_config
2015-04-20 14:21:50.263 29219 TRACE nova.compute.manager [instance: fc942094-db2c-442b-8183-340b5aa1e546]     _("Unexpected vif_type=%s") % vif_type)
2015-04-20 14:21:50.263 29219 TRACE nova.compute.manager [instance: fc942094-db2c-442b-8183-340b5aa1e546] NovaException: Unexpected vif_type=binding_failed
2015-04-20 14:21:50.263 29219 TRACE nova.compute.manager [instance: fc942094-db2c-442b-8183-340b5aa1e546]
<180>Apr 20 14:21:50 node-49 nova-compute Terminating instance