Practice of using Windows virtual machine nova-network Flatmanager

Objective

Before the use of Flatdhcp way, and later found a headache problem, is that an environment may itself already exist a DHCP server, will cause the virtual machine occasionally assigned to the outside of the IP and can not be used, so decided to configure the flat network to see the effect

Step NIC Configuration

With Flatmanager, the bridge needs to be configured manually,
The CENTOS7 used in the Network-manager is really annoying, so I removed it, or use the network bar, configured as follows:
[[email protected] ~]# cat/etc/sysconfig/network-scripts/ifcfg-wired connection _2

HWADDR=0C:C4:7A:4B:85:24TYPE=EthernetBOOTPROTO=noneIPADDR=10.1.81.210PREFIX=22GATEWAY=10.1.80.254DNS1=211.167.230.100DEFROUTE=yesIPV4_FAILURE_FATAL=noIPV6INIT=yesIPV6_AUTOCONF=yesIPV6_DEFROUTE=yesIPV6_PEERDNS=yesIPV6_PEERROUTES=yesIPV6_FAILURE_FATAL=noNAME="有线连接 2"UUID=8ae6846b-bf2e-42a0-8791-e606fa419861ONBOOT=yes

BR100 Configuration

[[email protected] ~]# cat /etc/sysconfig/network-scripts/ifcfg-br100DEVICE="br100"BOOTPROTO="static"IPADDR="10.1.81.210"NETMASK="255.255.252.0"DNS1="211.167.230.100"HOSTNAME="host210.zero"IPV6INIT="no"NAME="br100"NM_CONTROLLED="no"ONBOOT="yes"DELAY="0"TYPE="Bridge"GATEWAY="10.1.80.254"

Modify Nova.conf

Network_manager=nova.network.manager.flatmanager
Flat_injected=true
Check data found that there are two ways to provide metadata, through drive or metadata SERVER, because the network is very annoying, so use the drive way
Force_config_drive=always
Injected_network_template=/usr/share/nova/interfaces.template

/usr/share/nova/interfaces.template content is as follows:

{% for interface in interfaces %}auto {{ interface.name }}iface {{ interface.name }} inet static  address {{ interface.address }}  netmask {{ interface.netmask }}  broadcast {{ interface.broadcast }}  gateway {{ interface.gateway }}  dns-nameservers {{ interface.dns }}{% endfor %}

Cloudbase settings:

[DEFAULT]username=Admingroups=Administratorsconfig_drive_raw_hhd=trueconfig_drive_cdrom=trueconfig_drive_vfat=truebsdtar_path=C:\Program Files\Cloudbase Solutions\Cloudbase-Init\bin\bsdtar.exemtools_path=C:\Program Files\Cloudbase Solutions\Cloudbase-Init\binverbose=truedebug=truelogdir=C:\Program Files\Cloudbase Solutions\Cloudbase-Init\loglogfile=cloudbase-init.logdefault_log_levels=comtypes=INFO,suds=INFO,iso8601=WARNlogging_serial_port_settings=COM1,115200,N,8mtu_use_dhcp_config=truentp_use_dhcp_config=truemetadata_services=cloudbaseinit.metadata.services.configdrive.ConfigDriveServiceplugins=cloudbaseinit.plugins.common.mtu.MTUPlugin,        cloudbaseinit.plugins.common.sethostname.SetHostNamePlugin,    cloudbaseinit.plugins.common.networkconfig.NetworkConfigPluginlocal_scripts_path=C:\Program Files\Cloudbase Solutions\Cloudbase-Init\LocalScripts

Effect

Re-build the virtual machine and see the drive disk

Open to see information

Open metadata Information

    "uuid": "d2970089-b06c-4382-8a83-534878e691ee", "availability_zone": "nova", "hostname": "w3.novalocal", "launch_index": 0, "network_config": {"content_path": "/content/0000", "name": "network_config"}, "name": "W3"}

Open content/0000 with network information

But also found that Cloudbase seems to be not very stable, sometimes to set the network success, sometimes unsuccessful, do not understand why, still need to continue to study

Practice of using Windows virtual machine nova-network Flatmanager