Hyper-V Cloud Node Installation for Abiquo 1.6.8

Hyper-v installation steps for management through DCOM

1. Open the Registry Editor (regedit.exe) and under the HKEY_CLASSES_ROOT key use the Find method to locate a key with the name WbemScripting.SWbemLocator.

2. You will find it at other levels, but it should be located at the level directly below the HKEY_CLASSES_ROOT. After you locate the key, expand the folder for the key name and you should see a subkey named CLSID. Click that folder to see the values within that key. The key should be: {76a64158-cb41-11d1-8b02-00600806d9b6}. Make a note of this value or copy it to Notepad. Include the brackets.

3. Navigate under the HKEY_CLASSES_ROOT\CLSID key and find the subkey with this GUID number. After you highlight the HKEY_CLASSES_ROOT\CLSID key you can use the Find function in Registry Editor (under the Edit menu) and paste the GUID into the Find dialog box. Make sure that you have found the proper interface by inspecting the InprocServer32 subkey below this key, which points to the location of your COM DLL file. If there is a TypeLib key, check this GUID value

While under the GUID's InprocServer32 subkey, make sure that a ThreadingModel value exists and that it is set to either Both or Free to make sure the marshaling understands the threading model of the COM object to enable execution of COM out of SQL Server process space. If there is not a ThreadingModel value or it is set to Apartment, COM object instantiation may not be consistent.

Key privileges You may need to add privileges to this key in order to change the ThreadingModel value.

Highlight the GUID number/subkey under the HKEY_CLASSES_ROOT\CLSID key. Righ click on the key and right-click button "Permissions". Click "Advanced", Next click on the Owner tab and you'll now see that the current owner is TrustedInstaller. Now click on the Edit button and choose who you would like to change the owner to, either your account or the Administrators. If your account is an Administrator account, I would suggest just picking Administrators.

From the Edit menu, click New, and then select String Value. Under the Name column, type the following:

AppID

Press Enter and then insert the class identifier or GUID number: It should be: {76a64158-cb41-11d1-8b02-00600806d9b6} (include the brackets).

Add a new subkey under the HKEY_CLASSES_ROOT\AppID and set it's name to the same class identifier or GUID number with the brackets as inserted in the preceding step.

Key privileges You may need to add privileges to this key.

Highlight the GUID name. From the Edit menu, click New, and then select String Value. Under the Name column, type the following:

DllSurrogate

Leave the Data column blank for this value. Because the data column is blank, this informs DCOM to run the default executable file, Dllhost.exe and load the COM object within it's process space.

Networking configuration

MAC addressing configuration

The MAC interval allocation should be:

MinimumMacAddress = 00-15-5d-00-00-00
MaximumMacAddress = 00-15-5d-FF-FF-FF

VLAN Configuration

To allow Abiquo to manage VLANs in this HyperV server, we need to add a new network attached to the service network interface.
The network name should be: SERVICE_NETWORK.

External Storage configuration

WinRM service configuration

This service is used to call remote methods in object that can't be properly managed through DCOM.

1. By default, no WinRM listener is configured. Even if the WinRM service is running, WS-Management protocol messages that request data cannot be received or sent.

Use the Winrm command to locate listeners and the addresses by typing the following command at a command prompt:

winrm e winrm/config/listener

If no listener is configured, type:

winrm QuickConfig

To check the state of configuration settings, type winrm get winrm/config*

2. Allow unencrypted traffic and basic auth:

winrm set winrm/config/service @{AllowUnencrypted="true"}
winrm set winrm/config/service/auth @{Basic="true"}

3. Execute the next command to inspect the listening port:

winrm get winrm/config/Service/DefaultPorts 

Note the HTTP port since it will be used in the virtual factory configuration section.

4. (Optional) If you want to test this configuration steps from a winrm client, set the hosts that are allowed (the client IP, yours will be different):

winrm set winrm/config/client @{TrustedHosts="IP"}

To Ping WS-Man on a remote machine:

 winrm id -auth:none -remote:\<some machine\> 

iSCSI service installation

The first thing you need to do is enable iSCSI service and set it to start automatically

C:\Users\Administrator> sc config msiscsi start=auto
ChangeServiceConfig SUCCESS

C:\Users\Administrator> net start msiscsi
The Microsoft iSCSI Initiator Service service is starting.
The Microsoft iSCSI Initiator Service service was started successfully.

Once the iSCSI service is enabled, you must manually set the initiator IQN for the machine. TO so, go to Start > Administrative tools > iSCSI Initiator, and select the Configuration tab. Click the Change button. To make the following dialog appear:

You can accept the default value. Even if the value of the initiator IQn field does not change, it is important to do these steps manually. If this is not performed manually, the initiator IQN will be dynamically computed based on the host and domain name, and may change without any advice, letting the external storage volumes unaccessible.

San Policy configuration

Open a command line and run the following commands to set the appropiate San Policy:

diskpart
san policy=OfflineAll
exit

References

http://www.virtualizationadmin.com/articles-tutorials/microsoft-hyper-v-articles/networking/mac-address-pool-duplication-hyper-v.html
http://msdn.microsoft.com/en-us/library/aa384372%28VS.85%29.aspx
http://www.windowsitpro.com/article/john-savills-windows-faqs/q-how-can-i-use-the-command-line-to-configure-iscsi-connections-.aspx
http://blogs.technet.com/otto/archive/2007/02/09/sample-vista-ws-man-winrm-commands.aspx
http://helpdeskgeek.com/windows-7/windows-7-how-to-delete-files-protected-by-trustedinstaller/