Managing VMs in extra networks - Revision history

Tiziano at 13:11, 13 February 2014

2014-02-13T13:11:12Z

← Older revision		Revision as of 15:11, 13 February 2014
Line 13:		Line 13:
	# Open the settings for this VM-Template in the VM-Manager and hit <code>Save</code> to make sure the on-disk XML contains the changes.		# Open the settings for this VM-Template in the VM-Manager and hit <code>Save</code> to make sure the on-disk XML contains the changes.
	# When cloning VMs from this VM-Template, make sure you select the VM-Pool created for this network. This way the VM-Manager will automatically assign IP addresses matching the network attached to the respective bridge.		# When cloning VMs from this VM-Template, make sure you select the VM-Pool created for this network. This way the VM-Manager will automatically assign IP addresses matching the network attached to the respective bridge.

			[[Category:Workarounds]]

Tiziano at 13:10, 13 February 2014

2014-02-13T13:10:28Z

← Older revision		Revision as of 15:10, 13 February 2014
Line 11:		Line 11:
	#* make sure you select the newly created VM-Template pool		#* make sure you select the newly created VM-Template pool
	# via phpLdapAdmin: change the attribute <code>sstSourceBridge</code> of the subentry <code>sstInterface=net0,ou=devices</code> of this VM-Template to match the newly created bridge for the new network		# via phpLdapAdmin: change the attribute <code>sstSourceBridge</code> of the subentry <code>sstInterface=net0,ou=devices</code> of this VM-Template to match the newly created bridge for the new network
	# Open the settings for this VM-Template in the VM-Manager and hit <code>Save</code>		# Open the settings for this VM-Template in the VM-Manager and hit <code>Save</code> to make sure the on-disk XML contains the changes.
	# When cloning VMs from this VM-Template, make sure you select the VM-Pool created for this network. This way the VM-Manager will automatically assign IP addresses matching the network attached to the respective bridge.		# When cloning VMs from this VM-Template, make sure you select the VM-Pool created for this network. This way the VM-Manager will automatically assign IP addresses matching the network attached to the respective bridge.

Tiziano at 10:28, 13 February 2014

2014-02-13T10:28:42Z

← Older revision		Revision as of 12:28, 13 February 2014
Line 11:		Line 11:
	#* make sure you select the newly created VM-Template pool		#* make sure you select the newly created VM-Template pool
	# via phpLdapAdmin: change the attribute <code>sstSourceBridge</code> of the subentry <code>sstInterface=net0,ou=devices</code> of this VM-Template to match the newly created bridge for the new network		# via phpLdapAdmin: change the attribute <code>sstSourceBridge</code> of the subentry <code>sstInterface=net0,ou=devices</code> of this VM-Template to match the newly created bridge for the new network
			# Open the settings for this VM-Template in the VM-Manager and hit <code>Save</code>
	# When cloning VMs from this VM-Template, make sure you select the VM-Pool created for this network. This way the VM-Manager will automatically assign IP addresses matching the network attached to the respective bridge.		# When cloning VMs from this VM-Template, make sure you select the VM-Pool created for this network. This way the VM-Manager will automatically assign IP addresses matching the network attached to the respective bridge.

Tiziano at 10:05, 13 February 2014

2014-02-13T10:05:39Z

← Older revision		Revision as of 12:05, 13 February 2014
Line 10:		Line 10:
	# create a VM-Template for the network you want to be able to create new VMs in		# create a VM-Template for the network you want to be able to create new VMs in
	#* make sure you select the newly created VM-Template pool		#* make sure you select the newly created VM-Template pool
	# via phpLdapAdmin: change the attribute <code>sstSourceBridge</code> of the subentry <code>sstInterface=net0,ou=devices</code> of this VM-Template to match the newly created bridge for ~~that~~ network		# via phpLdapAdmin: change the attribute <code>sstSourceBridge</code> of the subentry <code>sstInterface=net0,ou=devices</code> of this VM-Template to match the newly created bridge for the new network
	# When cloning VMs from this VM-Template, make sure you select the VM-Pool created for this network. This way the VM-Manager will automatically assign IP addresses matching the network attached to the respective bridge.		# When cloning VMs from this VM-Template, make sure you select the VM-Pool created for this network. This way the VM-Manager will automatically assign IP addresses matching the network attached to the respective bridge.

Tiziano at 10:05, 13 February 2014

2014-02-13T10:05:28Z

← Older revision		Revision as of 12:05, 13 February 2014
Line 10:		Line 10:
	# create a VM-Template for the network you want to be able to create new VMs in		# create a VM-Template for the network you want to be able to create new VMs in
	#* make sure you select the newly created VM-Template pool		#* make sure you select the newly created VM-Template pool
	# via phpLdapAdmin: change the attribute <code>sstSourceBridge</code> of the subentry <code>sstInterface=net0,ou=devices</code> of ~~the dummy~~ VM-Template to match the newly created bridge for that network		# via phpLdapAdmin: change the attribute <code>sstSourceBridge</code> of the subentry <code>sstInterface=net0,ou=devices</code> of this VM-Template to match the newly created bridge for that network
	# When cloning VMs from this VM-Template, make sure you select the VM-Pool created for this network. This way the VM-Manager will automatically assign IP addresses matching the network attached to the respective bridge.		# When cloning VMs from this VM-Template, make sure you select the VM-Pool created for this network. This way the VM-Manager will automatically assign IP addresses matching the network attached to the respective bridge.

Tiziano: Created page with "The VM-Manager currently provides only partial support for additional networks: While it is possible to define additional networks and partition them into ranges, the corresp..."

2014-02-13T10:05:04Z

Created page with "The VM-Manager currently provides only partial support for additional networks: While it is possible to define additional networks and partition them into ranges, the corresp..."

New page

The VM-Manager currently provides only partial support for additional networks:

While it is possible to define additional networks and partition them into ranges, the corresponding bridge will not be selected automatically.

The easiest way is therefore as follows:

# create a new network plus ranges in vm-manager
# create a new VM and VM-Template pool and select the newly created network ranges
# [[Manually_adding_a_new_bridge|Create an additional bridge for this network]]
# create a VM-Template for the network you want to be able to create new VMs in
#* make sure you select the newly created VM-Template pool
# via phpLdapAdmin: change the attribute <code>sstSourceBridge</code> of the subentry <code>sstInterface=net0,ou=devices</code> of the dummy VM-Template to match the newly created bridge for that network
# When cloning VMs from this VM-Template, make sure you select the VM-Pool created for this network. This way the VM-Manager will automatically assign IP addresses matching the network attached to the respective bridge.