WorkingInT2BCloud - Revision history

Olivier Devroede: /* Creation of the disk */

2015-09-01T16:35:55Z

Creation of the disk

← Older revision		Revision as of 16:35, 1 September 2015
Line 47:		Line 47:
	#Disk size in MB		#Disk size in MB
	#Enable the advanced option to go to the next screen.		#Enable the advanced option to go to the next screen.
	[[File:Advanced_disk_opennebula.jpg]]		[[File:Advanced_disk_opennebula.jpg\|1000px]]

	Set the device prefix to “vd”. This will enable the virtio driver (otherwise VM performance are very poor).		Set the device prefix to “vd”. This will enable the virtio driver (otherwise VM performance are very poor).

Olivier Devroede: /* instantiate your VM */

2015-09-01T16:35:05Z

instantiate your VM

← Older revision		Revision as of 16:35, 1 September 2015
Line 122:		Line 122:

	==== instantiate your VM ====		==== instantiate your VM ====

			[[File:Create_Instantiate_opennebula.jpg\| 1000px]]

			# Back to the table showing all the templates, select the newly created one and...
			# ...click on button “Instantiate”

Olivier Devroede: /* Creation of VMs */

2015-09-01T15:38:36Z

Creation of VMs

← Older revision		Revision as of 15:38, 1 September 2015
Line 119:		Line 119:
	** PUBLIC_NETWORK_AVAILABLE = \"new\"		** PUBLIC_NETWORK_AVAILABLE = \"new\"
	# This was the last step ! You can click on button “Create”.		# This was the last step ! You can click on button “Create”.


			==== instantiate your VM ====

Olivier Devroede: /* Creation of VMs */

2015-09-01T15:37:26Z

Creation of VMs

← Older revision		Revision as of 15:37, 1 September 2015
Line 100:		Line 100:
	===== Template: IO =====		===== Template: IO =====

	[[File:Create_template_IO_opennebula.jpg]]		[[File:Create_template_IO_opennebula.jpg\|1000px]]

	Choose “VNC” to be able to interact with your VM.		Choose “VNC” to be able to interact with your VM.
Line 106:		Line 106:
	===== Template: Context =====		===== Template: Context =====

	[[File:Create_template_Context_opennebula.jpg]]		[[File:Create_template_Context_opennebula.jpg\|1000px]]

	Unselect the contextualization check-boxes (we don't need it because Quattor will do the job).		Unselect the contextualization check-boxes (we don't need it because Quattor will do the job).
Line 113:		Line 113:
	===== Template: Context =====		===== Template: Context =====

	[[File:Create_template_Shedulling_opennebula.jpg]]		[[File:Create_template_Shedulling_opennebula.jpg\|1000px]]

	# The scheduling is the step where OpenNebula is selecting an hypervisor to host the VM. In our T2B cloud, some hypervisors are connected to the old public network, and the others are connected to the new public network. If your VM will be in the new public network, you must tell explicitely the scheduler to choose the hypervisor accordingly.		# The scheduling is the step where OpenNebula is selecting an hypervisor to host the VM. In our T2B cloud, some hypervisors are connected to the old public network, and the others are connected to the new public network. If your VM will be in the new public network, you must tell explicitely the scheduler to choose the hypervisor accordingly.

Olivier Devroede: /* Creation of the Template */

2015-09-01T15:36:20Z

Creation of the Template

← Older revision		Revision as of 15:36, 1 September 2015
Line 69:		Line 69:
	===== Template: Storage =====		===== Template: Storage =====

	[[File:Create_template_disk_opennebula.jpg]]		[[File:Create_template_disk_opennebula.jpg\|1000px]]

	# “Disk 0” is created automatically as a default, but...		# “Disk 0” is created automatically as a default, but...
Line 75:		Line 75:
	# Display the advanced options		# Display the advanced options

	[[File:Create_template_disk_2_opennebula.jpg]]		[[File:Create_template_disk_2_opennebula.jpg\|1000px]]

	# Again, set the device prefix to “vd” to enable virtio driver for better performances.		# Again, set the device prefix to “vd” to enable virtio driver for better performances.
Line 82:		Line 82:
	===== Template: Network =====		===== Template: Network =====

	[[File:Create_template_network_opennebula.jpg]]		[[File:Create_template_network_opennebula.jpg\|1000px]]

	# By default, “interface 0” is automatically created. Click on the blue button “Add another nic” if you need more network interfaces.		# By default, “interface 0” is automatically created. Click on the blue button “Add another nic” if you need more network interfaces.
	# For each nic created in the previous step, select the virtual network in the above table.		# For each nic created in the previous step, select the virtual network in the above table.
	** The usage in the T2B is to place the first nic in the public network (Public_T2B_Fullrange)		## The usage in the T2B is to place the first nic in the public network (Public_T2B_Fullrange)
	** And the second nic in the private network (Private_T2B_Fullrange).		## And the second nic in the private network (Private_T2B_Fullrange).
	# Display the advanced options (see next slide for explanations).		# Display the advanced options (see next slide for explanations).
	# Set the IP addresses of the nics (don't forget to do it for all the nics defined in the previous step !). The model should be “virtio” for better performances.		# Set the IP addresses of the nics (don't forget to do it for all the nics defined in the previous step !). The model should be “virtio” for better performances.


			===== Template: OS Booting =====

			[[File:Create_template_booting_opennebula.jpg\|1000px]]

			If you want to install the machine with Quattor, it is very important to choose the network as the first boot device, and the hard drive as the second one.

			===== Template: IO =====

			[[File:Create_template_IO_opennebula.jpg]]

			Choose “VNC” to be able to interact with your VM.

			===== Template: Context =====

			[[File:Create_template_Context_opennebula.jpg]]

			Unselect the contextualization check-boxes (we don't need it because Quattor will do the job).


			===== Template: Context =====

			[[File:Create_template_Shedulling_opennebula.jpg]]

			# The scheduling is the step where OpenNebula is selecting an hypervisor to host the VM. In our T2B cloud, some hypervisors are connected to the old public network, and the others are connected to the new public network. If your VM will be in the new public network, you must tell explicitely the scheduler to choose the hypervisor accordingly.
			* Remark : PUBLIC_NETWORK_AVAILABLE is custom attribute that we have set for each host. Possible values are : “old” and “new”.
			** PUBLIC_NETWORK_AVAILABLE = \"new\"
			# This was the last step ! You can click on button “Create”.

Olivier Devroede: /* Creation of the Template */

2015-09-01T15:26:04Z

Creation of the Template

← Older revision		Revision as of 15:26, 1 September 2015
Line 60:		Line 60:

	==== Creation of the Template ====		==== Creation of the Template ====
			===== Template: General =====

			[[File:Create_template_opennebula.jpg\|1000px]]

			#We are using KVM hypervisors.
			#VCPU should only be used if you want to “pin” some cores of the hypervisor to your VM, the result being better performances.

			===== Template: Storage =====

			[[File:Create_template_disk_opennebula.jpg]]

			# “Disk 0” is created automatically as a default, but...
			# Now, associate it with the disk image you just created (select it in the table).
			# Display the advanced options

			[[File:Create_template_disk_2_opennebula.jpg]]

			# Again, set the device prefix to “vd” to enable virtio driver for better performances.
			# Disable disk cache for better performances

			===== Template: Network =====

			[[File:Create_template_network_opennebula.jpg]]

			# By default, “interface 0” is automatically created. Click on the blue button “Add another nic” if you need more network interfaces.
			# For each nic created in the previous step, select the virtual network in the above table.
			** The usage in the T2B is to place the first nic in the public network (Public_T2B_Fullrange)
			** And the second nic in the private network (Private_T2B_Fullrange).
			# Display the advanced options (see next slide for explanations).
			# Set the IP addresses of the nics (don't forget to do it for all the nics defined in the previous step !). The model should be “virtio” for better performances.

Olivier Devroede at 15:13, 1 September 2015

2015-09-01T15:13:44Z

← Older revision		Revision as of 15:13, 1 September 2015
Line 48:		Line 48:
	#Enable the advanced option to go to the next screen.		#Enable the advanced option to go to the next screen.
	[[File:Advanced_disk_opennebula.jpg]]		[[File:Advanced_disk_opennebula.jpg]]
	Set ~~tthe~~ device prefix to “vd”. This will enable the virtio driver (otherwise VM performance are very poor).
			Set the device prefix to “vd”. This will enable the virtio driver (otherwise VM performance are very poor).
	Don't forget to change the disk name accordingly in the hardware template in the SCDB. For example :		Don't forget to change the disk name accordingly in the hardware template in the SCDB. For example :

	<pre>		<pre>
	'harddisks' = dict('vda', create('hardware/harddisk/sas_generic', 'capacity', 60*GB));		'harddisks' = dict('vda', create('hardware/harddisk/sas_generic', 'capacity', 60*GB));
	</pre>		</pre>

			Next, click Create.
			Now your disk is ready and we can apply an opennebula template on it.

			==== Creation of the Template ====

Olivier Devroede at 15:11, 1 September 2015

2015-09-01T15:11:52Z

← Older revision		Revision as of 15:11, 1 September 2015
Line 46:		Line 46:
	#You want an empty drive		#You want an empty drive
	#Disk size in MB		#Disk size in MB
	#Don't forget to ~~enable~~ the ~~advanced options~~		#Enable the advanced option to go to the next screen.
			[[File:Advanced_disk_opennebula.jpg]]
			Set tthe device prefix to “vd”. This will enable the virtio driver (otherwise VM performance are very poor).
			Don't forget to change the disk name accordingly in the hardware template in the SCDB. For example :
			<pre>
			'harddisks' = dict('vda', create('hardware/harddisk/sas_generic', 'capacity', 60*GB));
			</pre>

Olivier Devroede at 15:02, 1 September 2015

2015-09-01T15:02:43Z

← Older revision		Revision as of 15:02, 1 September 2015
Line 41:		Line 41:

	==== Creation of the disk ====		==== Creation of the disk ====
	~~Since the disk must be empty~~, ~~you must choose~~ a ~~datablock~~. ~~Choosing persistence is also important since you want to keep~~ the content of the ~~drive even if~~ the VM is ~~deleted~~.		[[File:Create_disk_opennebula.jpg]]
	~~[[File:Example.jpg]]~~		#Choose type “DATABLOCK” because you just want a drive (not a CDROM iso, neither a disk with preinstalled OS).
			#“Persistent” means the content of the disk image is preserved when the machine is shut down.
			#You want an empty drive
			#Disk size in MB
			#Don't forget to enable the advanced options

Admin: /* Creation of VMs */

2015-08-28T09:11:57Z

Creation of VMs

← Older revision		Revision as of 09:11, 28 August 2015
Line 35:		Line 35:
	=== Creation of VMs ===		=== Creation of VMs ===
	To create a VM, you have to follow the following steps :		To create a VM, you have to follow the following steps :
	- creation of a disk		#creation of a disk
	- creation of a template using the disk created previously		#creation of a template using the disk created previously
	- instantiation of template to create the ~~VMs~~		#instantiation of the template to create the VM
			In the following explanations, we will suppose that you want to create a new VM that you want to deploy with Quattor.

			==== Creation of the disk ====
			Since the disk must be empty, you must choose a datablock. Choosing persistence is also important since you want to keep the content of the drive even if the VM is deleted.
	~~{{TracNotice\|{{PAGENAME}}}}~~		[[File:Example.jpg]]