vCloud Director for the smallest (part 2): creating virtual machines
- Tutorial
UPDATE: We have automated the creation of network and NAT rules. Now, when subscribing, all this is created by itself :). All that remains for you is to deploy the virtual machine from the template or from scratch. At the same time, you still have the opportunity to change the network settings if necessary.
Just do not forget about the Firewall, which by default does not allow any traffic and requires the configuration of rules .
Part 1. Configuring the network
In vCloud Director, virtual machines live in vApp containers, so creating a VM starts with creating vApp. You can select the following options:
In this material, we consider in detail the first two cases.
Let's start with the simplest option - deploy vApp from a template. At CloudLite.ru, you don’t have to bother downloading templates, because the Public Catalog provides a fairly wide selection of ready-made templates.
1. Go to the My Cloud section and select the vApps tab and click on green + .
2. In the new window, in the Look in field, select Public Catalog.
The table below will display a list of available virtual machine templates with OS. Select the one you want.
At the bottom of the window will contain information about this template, including login to enter, the required disk space, etc. Click Next .
3. Enter the name or leave the existing one (Name), fill out the description if necessary (Description). Click Next .
4. In the Configure Resources tab, make changes, if necessary, to the Computer Name field (the name that will be displayed inside the guest OS during customization). Next button .
5. In the Network Mapping tab, set the network parameters.
6. We skip the Custom Properties step and get to the Customize Hardware tab . The parameters CPU, Memory, Hard Disk are displayed here. We recommend that you do not change them during deployment of the VM, but do it after its creation. Next button .
7. On the last tabReady to Complete, carefully check all the parameters of your virtual machine selected in the previous steps. Here you can automatically start the created virtual machine by checking the box Power on vApp after this wizard is finished . Click Finish .
If you want to deploy a VM from your own template, then this can also be done in vCloud Director. To do this, create a directory (the folder into which you will load this template), well, and import the template itself . In the Look in field, respectively, instead of the Public Catalog, select your catalog.
If you need to load your OS onto the created virtual machine, then for this we create vApp with an “empty” VM.
1. Return to the My Cloud section , in the vApps tab, click on the icon marked with a yellow marker ( Build new vApp ).
2. In the window that appears, set the name of the VM.
If necessary, in the Leases section, you can set the time after which the VMs contained in this container will be automatically turned off ( Runtime Lease ) and the period after which the virtual machines of this vApp will be “frozen” ( Storage Lease ) and displayed in the Expired tab Items . Term indicated in Storage Leasestarts counting after the expiration of the period specified in Runtime Lease.
Click the Next button .
3. In the Add Virtual Machines tab, select the New Virtual Machine option . Click Next .
4. In the New Virtual Machine window that appears, you must select the parameters of the created virtual machine:
- name (Virtual Machine Name);
- the name that will be displayed inside the guest OS during customization (Computer Name);
- its description, if necessary (Description);
- a family and a specific operating system, which we will install later. For example, choose Centos;
- the amount of RAM and disk;
- The total number of virtual cores that will be allocated to VM (Number of virtual CPUs);
- the number of cores per virtual socket.
The last two options are important for licensing some operating systems. For example, for Windows Server Standard, the number of sockets should be no more than 4. In other versions, it is better to leave 1 core per socket.
Parameters that are set automatically and which we do not recommend changing:
- version of the container of the virtual machine (Virtual hardware version);
- bus type of virtual disks (Bus type). This is not related to the type of drives (SAS, SATA, VSAN) :).
- the number of virtual network adapters (Number of NICs). If there are no specialized needs, we recommend that you leave 1.
Click OK .
5. The new virtual machine appears in the list of the created vApp. Click Next .
6. On the Configure Resources tab, just click Next .
7. If necessary, make changes to the Computer Name field, select the network to which we want to connect the created virtual machine. In this case, select the network Test_Network, which we created in the previous article . Click Next .
8. In the Configure Networking tab, you can see the network settings. You can immediately select the Fence vApp option. It allows you to assign the same IP to virtual machines in different vApps, while avoiding the conflict of IP addresses. This is convenient if there are several test or development environments with identical VMs.
9. On the last tab Ready to Complete , we carefully check all the parameters of the virtual machine again. If everything works out, then click Finish .
10. We wait some time until the VM under Centos is deployed.
Next, you need to install the appropriate OS through connecting the image of the installation disk (ISO-image) or the disk itself. Here is a detailed instruction for this case.
Everything is quite simple here. The beginning is the same. as in the previous case. The only thing - this time we do not click on Add New Virtual Machine . Instead, click Next to victory. In this “empty” vApp, then similarly deploy the VM from the template or from scratch (without the OS) in the same way as we already did today.
Customization
When you turn on the VM for the first time, the so-called customization occurs, when all the specified settings are applied to the virtual machine:
• name of the virtual machine;
• network settings;
• SID;
• administrator password.
If customization is not available, then the VM settings can be configured manually through the console.
Password from the guest OS
On where to see the password for the guest OS, read here
Actually, that's all for today.
You can go train on cats in Cloudlite.ru :) Please
leave comments on this material and suggestions on future tutorial topics in the comments.
Success in mastering vCloud Director! :)
vCloud Director for the smallest (part 1): network setup
Just do not forget about the Firewall, which by default does not allow any traffic and requires the configuration of rules .
Part 1. Configuring the network
In vCloud Director, virtual machines live in vApp containers, so creating a VM starts with creating vApp. You can select the following options:
- vApp from the template (with a VM with a preinstalled OS);
- vApp c "empty" VM, i.e. without OS.
- "Empty" vApp and add VM there later.
In this material, we consider in detail the first two cases.
Creating a virtual machine from a ready-made template
Let's start with the simplest option - deploy vApp from a template. At CloudLite.ru, you don’t have to bother downloading templates, because the Public Catalog provides a fairly wide selection of ready-made templates.
1. Go to the My Cloud section and select the vApps tab and click on green + .
2. In the new window, in the Look in field, select Public Catalog.
The table below will display a list of available virtual machine templates with OS. Select the one you want.
At the bottom of the window will contain information about this template, including login to enter, the required disk space, etc. Click Next .
3. Enter the name or leave the existing one (Name), fill out the description if necessary (Description). Click Next .
4. In the Configure Resources tab, make changes, if necessary, to the Computer Name field (the name that will be displayed inside the guest OS during customization). Next button .
5. In the Network Mapping tab, set the network parameters.
6. We skip the Custom Properties step and get to the Customize Hardware tab . The parameters CPU, Memory, Hard Disk are displayed here. We recommend that you do not change them during deployment of the VM, but do it after its creation. Next button .
7. On the last tabReady to Complete, carefully check all the parameters of your virtual machine selected in the previous steps. Here you can automatically start the created virtual machine by checking the box Power on vApp after this wizard is finished . Click Finish .
If you want to deploy a VM from your own template, then this can also be done in vCloud Director. To do this, create a directory (the folder into which you will load this template), well, and import the template itself . In the Look in field, respectively, instead of the Public Catalog, select your catalog.
Creating a virtual machine from scratch (without a pre-installed OS)
If you need to load your OS onto the created virtual machine, then for this we create vApp with an “empty” VM.
1. Return to the My Cloud section , in the vApps tab, click on the icon marked with a yellow marker ( Build new vApp ).
2. In the window that appears, set the name of the VM.
If necessary, in the Leases section, you can set the time after which the VMs contained in this container will be automatically turned off ( Runtime Lease ) and the period after which the virtual machines of this vApp will be “frozen” ( Storage Lease ) and displayed in the Expired tab Items . Term indicated in Storage Leasestarts counting after the expiration of the period specified in Runtime Lease.
Click the Next button .
3. In the Add Virtual Machines tab, select the New Virtual Machine option . Click Next .
4. In the New Virtual Machine window that appears, you must select the parameters of the created virtual machine:
- name (Virtual Machine Name);
- the name that will be displayed inside the guest OS during customization (Computer Name);
- its description, if necessary (Description);
- a family and a specific operating system, which we will install later. For example, choose Centos;
- the amount of RAM and disk;
- The total number of virtual cores that will be allocated to VM (Number of virtual CPUs);
- the number of cores per virtual socket.
The last two options are important for licensing some operating systems. For example, for Windows Server Standard, the number of sockets should be no more than 4. In other versions, it is better to leave 1 core per socket.
Parameters that are set automatically and which we do not recommend changing:
- version of the container of the virtual machine (Virtual hardware version);
- bus type of virtual disks (Bus type). This is not related to the type of drives (SAS, SATA, VSAN) :).
- the number of virtual network adapters (Number of NICs). If there are no specialized needs, we recommend that you leave 1.
Click OK .
5. The new virtual machine appears in the list of the created vApp. Click Next .
6. On the Configure Resources tab, just click Next .
7. If necessary, make changes to the Computer Name field, select the network to which we want to connect the created virtual machine. In this case, select the network Test_Network, which we created in the previous article . Click Next .
8. In the Configure Networking tab, you can see the network settings. You can immediately select the Fence vApp option. It allows you to assign the same IP to virtual machines in different vApps, while avoiding the conflict of IP addresses. This is convenient if there are several test or development environments with identical VMs.
9. On the last tab Ready to Complete , we carefully check all the parameters of the virtual machine again. If everything works out, then click Finish .
10. We wait some time until the VM under Centos is deployed.
Next, you need to install the appropriate OS through connecting the image of the installation disk (ISO-image) or the disk itself. Here is a detailed instruction for this case.
Creating an “Empty vApp”
Everything is quite simple here. The beginning is the same. as in the previous case. The only thing - this time we do not click on Add New Virtual Machine . Instead, click Next to victory. In this “empty” vApp, then similarly deploy the VM from the template or from scratch (without the OS) in the same way as we already did today.
Of the important
Customization
When you turn on the VM for the first time, the so-called customization occurs, when all the specified settings are applied to the virtual machine:
• name of the virtual machine;
• network settings;
• SID;
• administrator password.
If customization is not available, then the VM settings can be configured manually through the console.
Password from the guest OS
On where to see the password for the guest OS, read here
Actually, that's all for today.
You can go train on cats in Cloudlite.ru :) Please
leave comments on this material and suggestions on future tutorial topics in the comments.
Success in mastering vCloud Director! :)
vCloud Director for the smallest (part 1): network setup