and after executing of command:
# fuel openstack-config --env 1 --execute
just file configuration "/etc/neutron/plugins/ml2/ml2_conf.ini" will be changed but will not applyed. it may be checked creating networks from user with admin role.
# neutron net-create <network_name>
Network has data. There is field "provider:segmentation_id" which must be filled from values if ml2 vlan range from file "/etc/neutron/plugins/ml2/ml2_conf.ini".
For applying this configuration we need to restart service "neutron-server" on each controller node. And I guess this action should be run on step "fuel openstack-config --env 1 --execute".
After small investigation of this issue the following behaviour was found. If we want to change ml2 vlan range, then we upload config
--- plugin_ ml2: vlan/network_ vlan_ranges: 1000:1001, physnet1"
configuration:
neutron_
ml2_type_
value: "physnet2:
and after executing of command:
# fuel openstack-config --env 1 --execute
just file configuration "/etc/neutron/ plugins/ ml2/ml2_ conf.ini" will be changed but will not applyed. it may be checked creating networks from user with admin role. segmentation_ id" which must be filled from values if ml2 vlan range from file "/etc/neutron/ plugins/ ml2/ml2_ conf.ini" .
# neutron net-create <network_name>
Network has data. There is field "provider:
For applying this configuration we need to restart service "neutron-server" on each controller node. And I guess this action should be run on step "fuel openstack-config --env 1 --execute".