Ask Your Question
1

how to create new network in mirantis fuel?

asked 2015-04-17 04:47:57 -0500

PainInNetwork gravatar image

updated 2015-04-20 09:22:52 -0500

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/fu...
  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 ...
(more)
edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
0

answered 2015-04-20 10:32:00 -0500

PainInNetwork gravatar image

Ok, modify deployment yaml files is a correct way to go. But we need to be very careful about the bridges. the br-prv-2 bridge will be automatically created, but we need to manually add patch between br-int and br-prv-2, and restart all nova and neutron services on controller nodes after the modification. on compute node, need to restart nova compute and neutron agent.

edit flag offensive delete link more
0

answered 2015-11-10 04:30:13 -0500

mikemowgli gravatar image

Hi, in Fuel 7 is a new feature called network-template which allows to prepare such network topologies. I think what you described could be done thanks to network templates, since it has a "network_scheme" section as well. However, I'm wondering if you know how to add a new provider network in this section, in order to configure 2 external networks. How should it be created and plugged in other bridges? any help appreciated.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2015-04-17 04:47:57 -0500

Seen: 1,285 times

Last updated: Nov 10 '15