CAPÍTULO II: REVISIÓN DE LA LITERATURA
2.4. MÉTODOS DE MICROENCAPSULACIÓN DE LOS COMPUESTOS
2.4.1. Agentes de encapsulantes
With the physical computer profile defined, the VHDX ready in the System Center Virtual Machine Manager library, and the Windows Deployment Server (WDS) integrated, you can use System Center Virtual Machine Manager to deploy the Hyper-V nodes. When you create new Hyper-V hosts from bare-metal computers, at a high level, the Add Resources Wizard does the following:
Discovers the physical computer through out-of-band management
Deploys an operating system image on the computer through the host profile or the physical computer profile
Enables the Hyper-V role on the computers
Brings the computer under System Center Virtual Machine Manager management as a managed Hyper-V hostIn the following procedure, you deploy Hyper-V to your bare-metal machines.
1. Log on to VMM01 using contoso\administrator credentials.
2. Open the System Center Virtual Machine Manager console, and then click Fabric.
3. In the Fabric pane, click Servers.
4. On the Home tab, in the Add group, click Add Resources, and then click Hyper-V Hosts And Clusters. The Add Resource Wizard opens.
5. On the Resource Location page, click Physical Computers To Be Provisioned As Virtual Machine Hosts, and then click Next.
6. On the Credentials And Protocol page, next to the Run As account box, click Browse, select your BMC Administrator account, and then click OK.
7. In the Protocol list, click IPMI On Port 623 For Discovery, and then click Next. This selection might vary depending on your hardware.
8. On the Discovery Scope page, depending on how your BMCs were configured, select either the IP subnet or, more specifically, the IP range. Whichever you choose, System Center Virtual Machine Manager scans the infrastructure and returns a list of
discovered hosts. Hosts do not have to be powered on to be discovered. Click Next to start discovery.
9. When discovery is completed, on the Target Resources page, select the boxes next to the four servers that you want to deploy Hyper-V onto, and then click Next.
10. On the Provisioning Options page, in the Host Group list, select COMPUTE as the target location for the new Hyper-V hosts, and from the drop-down list, select your Hyper-V physical computer profile. Click Next.
11. The Deployment Customization page shows that deep discovery is running. This means that System Center Virtual Machine Manager used the BMC to wake the servers and is capturing details about their configuration, settings, and more. This will take a few minutes. When this is completed, the servers are returned to a powered-off state. With the process complete, you must address several warnings before proceeding. Select one of the servers in the list by selecting the BMC IP address with the warning triangle.
12. In the Computer Name text box, type HV01, as shown in Figure 5-15, and then click Network Adapters.
FIGURE 5-15 Entering the computer name
13. You should see six network adapters listed, as shown in Figure 5-16. If the window is cramped with information, stretch it to the right by dragging the right edge of the window.
FIGURE 5-16 Six network adapters listed
In this configuration, two of the network adapters are 10 Gbps and will be placed onto the DatacenterNetwork. The remaining four will be aggregated into a team and have a logical switch deployed, allowing future VMs to communicate out onto the network.
14. Ensure that one of your 10-Gbps network adapters under Management NIC has Yes selected. Also ensure that both of the 10-Gbps adapters have Static IP selected under IP Assignment.
15. For the first of your 10-Gbps adapters, click the ellipses (…) button to further
customize the NIC settings. This opens the Network Adapter IP Configuration window.
16. In the Network Adapter IP Configuration window, click Specify Static IP Settings For This Network Adapter.
17. For logical network, from the drop-down list, select Datacenter_LN.
18. For IP subnet, from the drop-down list, select 10.10.1.0/24, and then click the Obtain An IP Address Corresponding To The Selected Subnet check box. As part of the deployment process, System Center Virtual Machine Manager assigns a static IP address from the pool you created in Chapter 3. Click OK.
19. Repeat steps 15 through 18 of this procedure, but this time, select the 10.10.2.0/24 subnet.
20. The four remaining 1-Gbps adapters in this configuration will be used exclusively by VMs. Therefore, as part of the deployment, specify that these network adapters should have a logical switch assigned to them. For each of the 1-Gbps network adapters, in the Logical Switch column, ensure they all have the Tenant_LN_LS selected.
21. For the first of your 1-Gbps adapters, click the ellipses (…) button. This opens the Network Adapter IP Configuration window.
22. In the Network Adapter IP Configuration window, click the Connect This Physical NIC To The Following Logical Switch check box. From the drop-down list, select
Tenant_LN_LS if necessary. This is the logical switch that you constructed in Chapter 3.
23. Under Apply The Following Uplink Port Profile To This Physical NIC, from the drop- down list, select the uplink port profile, as shown in Figure 5-17. You created only a single profile in Chapter 3, so this is the only one available, as shown in Figure 5-17. Click OK.
FIGURE 5-17 Selecting the uplink port profile
24. Repeat steps 21 through 23 of this procedure for the remaining 1-Gbps network adapters.
25. Click Disks. If you have more than one local disk in the target server, you can use the check box and drop-down list to select the disk you’d like to deploy Hyper-V onto.
26. Repeat steps 11 through 25 of this procedure for HV02, HV03, and HV04, and then click Next.
27. On the Summary page, review your customization settings, and then click Finish. System Center Virtual Machine Manager begins the deployment process, transferring a copy of the virtual hard disk, which is currently stored in the System Center Virtual Machine Manager library, to each of the Hyper-V hosts. The host is then configured to natively boot from the virtual hard disk. System Center Virtual Machine Manager proceeds with the automated setup of the Hyper-V host, including joining the domain, enabling the Hyper-V role, and deploying the System Center Virtual Machine Manager management agent. When this is completed, the four new Hyper-V nodes appear under System Center Virtual Machine Manager management within the COMPUTE host group.