Published: October 2013interworks.cloud OSS VMware vSphere® Service ManagerInstallation Guide
interworks.cloud S.A.









   



























This document contains information proprietary to interworks.cloud S.A. and its receipt or possession does not convey any rights to reproduce, disclose, manufacture, or sell anything it might describe. Use without interworks.cloud' specific written authorization is strictly forbidden. interworks.cloud makes no representations or warranties with respect to the contents or use of this document, and it reserves the right to revise this document any time, without the obligation to notify any person or entity of revisions. Further, interworks.cloud assumes no responsibility or liability for any errors or inaccuracies, makes no warranty of any kind (express, implied, or statutory) with respect to the contents or use of the information, and expressly disclaims any and all warranties of merchantability, fitness for particular purposes, and non-infringement of third-party rights.

interworks.cloud, the interworks.cloud logo, the interworks.cloud Platform logo, the interworks.cloud BSS logo, the interworks.cloud Storefront logo, the interworks.cloud Marketplace and the interworks.cloud OSS logo are registered trademarks of interworks.cloud S.A. All other trademarks are the property of their respective owners.



interworks.cloud S.A.

www.interworkscloud.com
Table of Contents
Document revision history5
About this guide 6
Introduction6
Document conventions6
Support and feedback7
CHAPTER 1 8
Overview of Cloud OSS VMware vSphere Service Manager 8
Introduction8Overview of VMware vSphere 5.x8
Overview of Cloud OSS9
CHAPTER 2 10
Preparing for the installation 10
Introduction10
Deploying VMware vSphere Infrastructure10
Preparing the network11
Preparing the VM templates (Guest OS Master Images)11
CHAPTER 3 12
Installing Cloud OSS VMware vSphere Service Manager 12
Introduction12
Installing Cloud OSS VMware vSphere Service Managers12
CHAPTER 4 14
Configuring Cloud OSS VMware vSphere Service Manager 14
Introduction14
Configuring VMware vSphere module15
Configuring Network Settings17
Creating Virtual Server18
Creating Hosting Plan19
APPENDIX A 20
APPENDIX B 38
This page is intentionally left blank

Document revision history

There have been no changes to this document since its initial publication. For information about new features in this release, see the latest release notes at: *http://www.interworkscloud.com/release.en.aspx*

About this guide

Introduction

This guide provides instructions for installing and configuring interworks.cloud OSS VMware vSphere Service Manager 2.x. The following versions of VMware vSphere are currently supported in this release:

• VMware vSphere 5.1
• VMware vSphere 5.5

Document conventions

Throughout this guide, specific fonts and styles are used to identify user input, computer code, and user interface elements. The following table lists conventions used in this guide.
Table 1. Document conventions

Support and feedback

To receive support for the Cloud OSS platform use the following link:
*http://www.interworkscloud.com/downloads* to access product downloads and online help and documentation

CHAPTER 1

Overview of Cloud OSS VMware vSphere Service Manager

Introduction

This chapter provides an overview of interworks.cloud OSS platform and the VMware vSphere Service Manager.

Overview of VMware vSphere 5.x

VMware vSphere is the industry-leading virtualization platform for building cloud infrastructures. It enables IT to meet SLAs (service-level agreements) for the most demanding business critical applications, at the lowest TCO (total cost of ownership).
VMware vSphere Hypervisor Architecture provides a robust, production-proven, high-performance virtualization layer. It enables multiple virtual machines to share hardware resources with performance that can match (and in some cases exceed) native throughput.
VMware vSphere Virtual Symmetric Multiprocessing enables the use of ultra-powerful virtual machines that possess up to 64 virtual CPUs.
VMware vSphere Virtual Machine File System (VMFS) allows virtual machines to access shared storage devices (Fiber Channel, iSCSI, etc.) and is a key enabling technology for other vSphere components such as VMware vSphere Storage vMotion®.
VMware vSphere Storage APIs provide integration with supported third-party data protection, multi-pathing and disk array solutions.

Overview of Cloud OSS

The interworks.cloud OSS platform is a centralized software application that simplifies the day-to-day burden of activating, configuring and managing a service provider's unified communications and collaboration infrastructure. interworks.cloud OSS enables service providers to centrally create, control, and deliver hosted IP and application services. It addresses critical operational challenges for provisioning, monitoring, metering, self-management, authentication and further integration into other applications in the service provider's OSS/BSS systems.
interworks.cloud OSS has the following components:

• Cloud OSS Provisioning Portal

Server that host the web-based control panels. Service providers can have multiple Provisioning Portal servers to balance loads and provisioning requests. Provisioning Portal servers or control panels provide easy access to tasks. These control panels enable service providers, resellers, organization administrators, and users to manage their accounts, resources, and other system settings. Provisioning Portal servers are typically placed in the Front End (internet facing) network.

• Cloud OSS Orchestration Server

The Cloud OSS Orchestration Server coordinates the provisioning of services to customers. Service Providers can have multiple Orchestration servers to balance loads and provisioning requests. The Orchestration Server role comprises the business logic of Cloud OSS. Orchestration servers are typically placed in the Back End network.

• Cloud OSS Service Managers

The Cloud OSS Service Manager can be seen as a provisioning helper server. Service Managers expose an extensive set of web services APIs that perform the actual provisioning actions as dictated by the Orchestration Servers. Service Managers are mainly installed on servers that host specific applications or services (e.g.: IIS, SQL Server), but they can also be installed on servers that have special management tools to manage and control other applications or services (e.g.: Exchange servers, Lync servers, etc.). Cloud OSS Service Managers are typically placed in the Back End network.

CHAPTER 2

Preparing for the installation

Introduction

This chapter explains how to prepare a hosting/cloud environment for the Cloud OSS VMware vSphere Service Manager installation.

Deploying VMware vSphere Infrastructure

This guide assumes that you have deployed and configured vSphere in high availability mode. The Service Manager can only interact with the vSphere infrastructure through vCenter Server, therefore vCenter Server must be installed and properly configured to manage the entire infrastructure. At the very least two servers running ESXi hypervisors are required in order to form a vSphere cluster.
The VMware vSphere Service Manager requires that the following configuration settings are applied:

• A cluster of two or more ESXi Hosts is created and configured appropriately
• A Datastore Cluster is configured with one or more datastores
• A Datacenter object container is defined. The Cluster and Datastore Cluster must be linked under this Datacenter container
• Network and storage configuration of each ESXi Host is set up correctly

The vSphere administrator should also ensure that various other settings such as Time Configuration, DNS and Routing, Power Management, etc. are properly configured.

Preparing the Network

The current release of VMware vSphere Service Manager supports provisioning of VMs in standard VLAN based isolated networks. Each tenant (customer) is automatically assigned a VLAN and all VMs provisioned under that tenant belong to that specific VLAN. The Service Manager automatically configures the Standard vSwitch in each ESXi Host with the appropriate port group settings for each tenant VM.
The Network Administrator must prepare for and supply the following information:

• A list of VLANs that will be made available to the VMs

  Important:

  Further configuration may be required depending on the existing network infrastructure. This may include routers, firewalls, physical switches or other networking devices.

  
  

• A list of IP Addresses/Ranges (IP address, Network Subnet mask, Default Gateway) that will be assigned to VMs during provisioning
• Primary and Secondary DNS server IP addresses that the provisioned VMs will use

Preparing the VM templates (Guest OS Master Images)

The Service Manager requires the use of templates created in vCenter Server, in order for VM provisioning to function correctly. The vSphere administrator should prepare the required VM templates along with relevant Guest OS customization specification files. Further instructions on how to create the necessary customization specification files and specific guest OS images can be found in Appendix A of this guide.

CHAPTER 3

Installing Cloud OSS VMware vSphere Service Manager

Introduction

This chapter explains how to install the Cloud OSS VMware vSphere Service Manager.

Installing Cloud OSS VMware vSphere Service Managers

To integrate VMware vSphere into the Cloud OSS platform you will need to install the Cloud OSS Service Managers components on one or more mediation servers You can install interworks.cloud OSS Service Manager on more than one servers and make use of hardware or software load balancing to distribute load and maintain high availability. This server may also be referred as Mediation Server. in your environment. Installation of the components is performed by the interworks.cloud Platform Installer. For more information about installing the interworks.cloud Platform Installer and the Service Managers please consult the interworks.cloud OSS Installation Guide.
The mediation server should have the following minimum system and software specifications:
Mediation Server System Requirements

Login to every mediation server and install the Cloud OSS Service Managers components as described in the Cloud OSS Installation Guide. Keep in mind the following network port requirements, in order to maintain successful communication between the various Cloud OSS components and the vSphere infrastructure.
Network Access Rules

After installation has completed successfully, you will need to manually edit the configuration file templatesConfiguration.xml (you can use notepad or any other common text editor). This file is located at the root of the installation directory of the Cloud OSS Service Manager and contains the VM templates that the Service Manager will use to provision VMs. In this configuration file you define the names of the VM templates and the customization specification files you created earlier in vCenter Server (See previous section Preparing the VM templates). Fig. 3.1 shows an example of the contents of the configuration file.
Image Added

Fig. 3.1
According to the example above, the administrator has configured one VM template named Windows Server 2008 R2 Standard and one VM template named CentOS 6.4 (64-Bit). There are also two customization specification files. One is configured for Windows based guest OS and is named OSS Windows Customization, and the other is configured for Linux based guest OS and is named OSS Linux Customization.
Appendix A of this guide contains step by step instructions on how to create both VM templates and customization specification files in vCenter Server to support VM provisioning in Cloud OSS.

CHAPTER 4

Configuring Cloud OSS VMware vSphere Service Manager

Introduction

This section provides information about configuring the Cloud OSS VMware vSphere Service Manager. It is assumed that you have installed the Cloud OSS Service Managers components on all servers that require it, as described in the previous sections and you have verified connectivity to the Service Managers web sites. Before configuring each component, it is necessary to add each server to the Cloud OSS servers' collection. This is done by signing in to the Cloud OSS Provisioning Portal, navigating to Configuration ► Servers (Fig. 4.1) and clicking on Add Server (Fig. 4.2) button.
Image AddedImage Added Fig. 4.1 Fig. 4.2
You have to enter a server name (you may choose any name that is meaningful and/or descriptive of the server role) as well as the URL and server password that correspond to each Service Manager installation. For more information about administering and configuring Cloud OSS platform you may consult the Cloud OSS Administrator Guide.

Configuring VMware vSphere module

Sign in to Cloud OSS Provisioning Portal and navigate to Configuration ► Servers. Click on the server where the Cloud OSS VMware vSphere Service Manager was previously installed and perform the following actions:

• Under the Services section click Add next to VMware vSphere (Fig. 4.4)
• Optionally, change the Service Name label if required
• Select vSphere 5.x as Service Provider
• Image Added Click on the Add Service button

Fig. 4.4
On the service settings page (Fig. 4.5) perform the following actions:

• Under the vCenter Server Connection Options enter the IP address of the vCenter Server and the user name and password of either the root user or a user with administrative privileges configured in vCenter Server. Click on the check button next to the IP address text box. If the connection settings are correct the button image will change from red stop sign to a green check mark
• Under the Datacenter section select the desired Datacenter container object. This object should have been previously configured in vCenter Server (see Chapter 2, Preparing for the installation)
• Under the Clusters section select the desired cluster that the Service Manager will manage
• Under the External Network section select the Standard vSwitch that will be used for VM external network communication
• Click on the Update button. Upon successful operation the following message will be displayed:

VMware Custom Service has been provisioned successfully
Image Added
Fig. 4.5

Configuring Network Settings

VLAN Pool configuration

Sign in to Cloud OSS Provisioning Portal and navigate to Configuration ► Virtual LANs. Click on Add Virtual LAN button and enter a meaningful name in the Description field; then enter the range of available VLANs and finally click on the Add button to save your VLAN selection (Fig. 4.6).
Image Added





Fig. 4.6

You can repeat this process if you wish to insert additional VLAN ranges.

IP Address Pool configuration
Sign in to Cloud OSS Provisioning Portal and navigate to Configuration ► IP Addresses. Click on the Add IP Address button and enter the following information (Fig. 4.7):

• Select VMware External Network in the Pool: drop down list
• Select the server previously configured in the Server: drop down list (See section Configuring VMware vSphere module)
• Enter an appropriate IP address range
• Optionally, set the NAT Address that will apply to the selected IP Address range
• Enter the Subnet mask and the Default Gateway

Image Added

Fig. 4.7


You can repeat this process if you wish to insert additional IP Address ranges.

Creating Virtual Server

Sign in to Cloud OSS Provisioning Portal and navigate to Configuration ► Virtual Servers. Click on Add Virtual Server button and enter a meaningful name in the Server Name: field; then click on Add Server button to save the new Virtual Server.

Click on Add Services button and select VMware vSphere service on the server previously configured.
Click on the Update button.

Creating Hosting Plan

Image Added

Sign in to Cloud OSS Provisioning Portal and navigate to Account Home ► Hosting Plans ► Create Hosting Plan. Enter a meaningful plan name and an optional description and select as target server the Virtual Server you created earlier from the drop-down list. Under the Quotas section select the VMware vSphere service. Adjust the quotas and values of the service to meet your plan needs and click on the Save button to save the new Hosting Plan (Fig. 4.8).
Fig. 4.8
You are now ready to create a new customer and assign a new Hosting Space to the customer based on the Hosting Plan you just created.

APPENDIX A

Deploying Guest OS Master Images (VM Templates)

Introduction

This section provides information that can help you create Windows and Linux based guest OS templates that will be used by Cloud OSS during VM provisioning. Instructions provided herein will assist in creating customizations specification files for Windows and Linux operating systems as well as optimized images ready for provisioning. To follow these instructions you will need administrative access to vCenter Server (via vSphere Client) as well as adequate ISO images or CD/DVD discs containing the operating systems for the guest OS.

Windows Customization Specification

Launch vSphere client and connect to the vCenter Server using root credentials (or another user with administrative privileges). Navigate to Management ► Customization Specifications Manager and click New to create a new Customization Specification.
In the Properties page make the following selections:

• Select Windows as the Target Virtual Machine OS
• Do not check Use custom sysprep answer file
• Under Customization Specification Information section enter a name and optionally a description
• Click Next > to continue

In the Registration Information page provide the following information:

• Enter a desired value for the Name: field
• Enter a desired value for the Organization: field
• Click Next > to continue

In the Computer Name page make the following selections:

• Under the NetBIOS Name section select the option: Use the virtual machine name
• Click Next > to continue

In the Windows License page provide the following information:

• Enter a valid Windows Server Key in the Product Key: field
• Check the option: Include Server License Information (Required for customizing a server guest OS)
• Set the Server License Mode to: Per Server (Maximum Connections: 5)
• Click Next > to continue

In the Administrator Password page enter the following information:

• Type any password in the Password: field
• Retype the password in the Confirm Password: field
• Do not check the option: Automatically log on as the Administrator
• Click Next > to continue

In the Time Zone page make the following selection:

• Select the desired Time Zone from the drop down list
• Click Next > to continue

In the Run Once page enter the following commands (type each command at a time and click on the Add button):

• start /w slmgr.vbs -ipk <XXXXX-YYYYY-ZZZZZ-WWWWW-TTTTT> where <XXXXX-YYYYY-ZZZZZ-WWWWW-TTTTT> is a valid Windows Server Product Activation Key
• start /w slmgr.vbs -ato
• bootcfg /timeout 5
• powercfg.exe -h off
• Click Next > to continue

In the Network page make the following selections:

• Select Custom Settings and click Next > to continue

In the Custom Settings page make the following selections:

• Click the browse button next to NIC1 network interface entry to bring up the Network Properties window
• Under the General tab (IP Address section) provide the following values:
  • Check the option: Use the following IP settings:
  • Type any (arbitrary) IP address, Subnet Mask and Default Gateway in the respective fields
• Under the General tab (DNS Server section) provide the following values:
  • Check the option: Use the following DNS server addresses:
  • Enter the desired and valid Name Server IP addresses in the Preferred DNS Server: and Alternate DNS Server: fields
• Click OK
• Click Next > to continue

In the Workgroup or Domain page make the following selections:

• Select the option: Workgroup: (Leave the default value in the textbox as is: WORKGROUP)
• Click Next > to continue

In the Operating System Options page make the following selections:

• Check the option: Generate New Security ID (SID)
• Click Next > to continue

Click Finish to finalize and save the Customization Specification

Linux Customization Specification

Launch vSphere client and connect to the vCenter Server using root credentials (or another user with administrative privileges). Navigate to Management ► Customization Specifications Manager and click New to create a new Customization Specification.
In the Properties page make the following selections:

• Select Linux as the Target Virtual Machine OS
• Under Customization Specification Information section enter a name and optionally a description
• Click Next > to continue

In the Computer Name page make the following selections:

• Under the Computer Name section select the option: Enter a name and type an arbitrary name (e.g.: localhost1)
• Under the Domain Name section enter a valid domain name (e.g.: hosterdomain.com)
• Click Next > to continue

In the Time Zone page make the following selections:

• Select appropriate values for Area: and Location: from the respective drop down lists
• Set the option Hardware Clock Set To: to value: UTC
• Click Next > to continue

In the Network page make the following selections:

• Select Custom Settings and click Next > to continue

In the Custom Settings page make the following selections:

• Click the browse button next to NIC1 network interface entry to bring up the Network Properties window
• Under the General tab (IP Address section) provide the following values:
  • Check the option: Use the following IP settings:
  • Type any (arbitrary) IP address, Subnet Mask and Default Gateway in the respective fields
  • Click OK
  • Click Next > to continue

In the DNS and Domain Settings page provide the following values:

• Check the option: Use the following DNS server addresses:
• Enter the desired and valid Name Server IP addresses in the Primary DNS and Secondary DNS fields
• Enter a valid domain name (e.g.: hosterdomain.com) in the DNS Search Path field and Click Add
• Click Next > to continue

Click Finish to finalize and save the Customization Specification

Create a Windows Server 2008 R2 Standard with SP1 Guest OS Template

The following instructions aim to assist in configuring and deploying a server guest OS template based on Windows Server 2008 R2 Standard with SP1. You may choose to select different settings depending on your own experience or other requirements that may apply in your environment.
Image AddedImage Added Launch vSphere client and connect to the vCenter Server using root credentials (or another user with administrative privileges). Navigate to Inventory ► VMs and Templates, select the Datacenter container and right click New Virtual Machine… to create a new VM.
Image AddedImage Added Fig. A1: Select Custom configuration for the VM Fig. A2: Enter a meaningful name for the VM Fig. A3: Select a cluster to run the VM Fig. A4: Choose the destination storage of the VM
Fig. A5: Select the Virtual Machine version Fig. A6: Choose the guest OS and specify the version (Normally the latest version should be selected) Image Added Image Added In this example the selection is Windows and Microsoft Windows Server 2008 R2 (64-bit)
Image AddedImage Added
Fig. A7: Select 1 virtual socket and 1 CPU core Fig. A8: Select 512 MB for the memory size of the VM


Fig. A9: Configure 1 Network connection, choose the VMXNET 3 Adapter Image Added Image Added Fig. A10: Choose the LSI Logic SAS SCSI controller
Image AddedImage Added
Fig. A11: Select to create a new virtual disk Fig. A12: Set the disk size to 20GB and select Thindisk provisioning

Image AddedImage Added
Fig. A13: Keep default settings in disk advanced options Fig. A14: Click Finish to create the new VM
Image AddedImage Added
Fig. A15: Optionally uncheck the Enable logging checkbox Fig. A16: Enable memory and CPU hot add for the VM
Image AddedImage Added

Fig. A17: Insert the parameter devices.hotplug in Configuration Fig. A18: Set the value of disk.EnableUUID option in Parameters and set its value to false Configuration Parameters to false
Image Added
Fig. A19: Force the BIOS setup to launch next time the VM starts



Mount a Windows ISO image or insert a Windows DVD in the host DVD device (Make sure that the VM's DVD device status is set to Connect at power on) and power on the VM. At the BIOS setup screen disable the following devices:

• Legacy Diskette A:
• Serial port A: (Advanced ► I/O Device Configuration)
• Serial port B: (Advanced ► I/O Device Configuration)
• Parallel port: (Advanced ► I/O Device Configuration)
• Floppy disk controller: (Advanced ► I/O Device Configuration)

Press F10 to Save and Exit
The Windows setup program will launch. Proceed with installing Windows 2008 R2 Standard (Full GUI install)
Logon to Windows after installation completes. Perform the following actions:

• Uncheck the Launch on startup option in Initial Configuration Tasks and Server Manager consoles
• Unmount the Windows DVD (Set the CD/DVD drive of the VM to Client Device)
• Install VMware Tools (Choose custom installation, uncheck the Audio Driver, keep all other default values)
• Reboot the VM after installation completes
• Set initial TCP/IP settings to allow internet access
• Install the following hotfixes:
  • http://support.microsoft.com/kb/2545227
  • http://support.microsoft.com/kb/2550978
• Reboot the VM
• Install latest Windows Updates
• Reboot the VM
• Make the following changes:
  • Enable Remote Desktop
  • Edit TCP/IP settings ► Configure NIC ► Power Management and uncheck the option allow this device to turn off the computer
  • Go to Control Panel ► Power management and set sleep Display to never
  • Go to Control Panel ► Sounds and select No sound scheme. Also set the option Do not play startup sound
• Optionally, you may choose to make other changes or customizations that may be desired, such as configuration of IE ESC, Firewall rules, installation of custom applications, etc.
• Temporary disable Paging (Set no page file for all volumes) and reboot the VM
• Delete any temporary files from the VM and perform a full defragmentation of all drives
• Enable Paging again and reboot the VM
• Create the following files:
  • Unattend.xml (Copy this file to c:\windows\system32\sysprep)Fig. A.20 shows sample contents of the file
  • Setupcomplete.cmd (Copy this file to c:\windows\setup\scripts)Fig. A.21 shows sample contents of the file

You can also download these sample files at *http://downloads.gocloud360.net/files/misc/win2k8r2std-sysprep.zip*

• Launch a command prompt (cmd) and execute the following commands:
  • *cd c:\windows\system32\sysprep*
  • sysprep /generalize /unattend:unattend.xml

Select Enter System Out-of-Box Experience (OOBE) and check Generalize and Reboot in Shutdown Options

• Reboot the VM
• Release the IP address (Set TCP/IP settings to DHCP)
• Shutdown the VM
• Right click the VM and select Template ► Convert to Template

Image Added
Fig. A20: Sample content of setupcomplete.cmd file

Image Added


Fig. A21: Sample content of unattend.xml file

Create a Linux CentOS 6.4 (64-Bit) Guest OS Template

The following instructions aim to assist in configuring and deploying a server guest OS template based on CentOS 6.4 (64-bit). You may choose to select different settings depending on your own experience or other requirements that may apply in your environment.
Image AddedImage Added Launch vSphere client and connect to the vCenter Server using root credentials (or another user with administrative privileges). Navigate to Inventory ► VMs and Templates, select the Datacenter container and right click New Virtual Machine… to create a new VM.
Image AddedImage Added Fig. A22: Select Custom configuration for the VM Fig. A23: Enter a meaningful name for the VM
Fig. A24: Select a cluster to run the VM Fig. A25: Choose the destination storage of the VM
Image Added
Image Added
Fig. A26: Select the Virtual Machine version Fig. A27: Choose the guest OS and specify the version (Normally the latest version should be selected) In this example the selection is Linux and Red Hat Enterprise Linux 6 (64-bit)
Image AddedImage Added
Fig. A28: Select 1 virtual socket and 1 CPU core Fig. A29: Select 512 MB for the memory size of the VM
Image AddedImage Added
Fig. A30: Configure 1 Network connection, choose the VMXNET 3 Adapter Fig. A31: Choose the VMware Paravirtual SCSI controller
Image AddedImage Added

Fig. A32: Select to create a new virtual disk Fig. A33: Set the disk size to 20GB and select Thindisk provisioning


Image AddedImage Added
Fig. A34: Keep default settings in disk advanced options Fig. A35: Click Finish to create the new VM
Mount a CentOS ISO image or insert a CentOS DVD in the host DVD device (Make sure that the VM's DVD device status is set to Connect at power on) and power on the VM.
The CentOS installer will launch. Proceed with installing CentOS 6.4 (64-bit)
Logon to CentOS after installation completes. Perform the following actions:

• Navigate to /etc/sysconfig/network-scripts/ and edit the file ifcfg-eth0

Change the following parameters to these values:

• • ONBOOT=yes
  • NM_CONTROLLED=no
  • BOOTPROTO=static

Add the following lines:

• • IPADDR=<VM_IP_Address>
  • NETMASK=<Network_Subnet_Mask>
  • GATEWAY=<Gateway_IP_Address>
  • DNS1=<Primary_DNS_Server_IP_Address>
  • DNS2=<Secondary_DNS_Server_IPAddress>

The values you enter above should be valid IP addresses, so that the VM can temporarily have internet access, in order for further updates or packages to be installed.

• Restart the network service by executing the command:

[root@localhost]# /etc/init.d/network restart

• Install OS updates and Application packages updates by executing the command:

[root@localhost]# yum update

• Optionally, install and configure additional software packages, i.e.:

[root@localhost]# yum install bind-utils traceroute –y

• Optionally, configure security settings such as iptables, Security Enhanced Linux, etc.
• Reboot the VM
• Unmount the CentOS DVD (Set the CD/DVD drive of the VM to Client Device)
• Install VMware Tools
  • In vSphere Client, right-click on the VM and select Guest ► Install/Upgrade VMware Tools
  • Logon to VM and install prerequisite packages and software: [root@localhost]# yum install perl gcc make –y
  • Reboot the VM
  • Mount the installer image: [root@localhost]# mount -t iso9660 /dev/cdrom /mnt
  • Copy the installer files to a temporary location and run the installation script: [root@localhost]# cd /mnt [root@localhost]# cp VMwareTools-9.2.2-893683.tar.gz /tmp [root@localhost]# cd /tmp [root@localhost]# tar xzvf VMwareTools-9.2.2-893683.tar.gz [root@localhost]# cd vmware-tools-distrib/ [root@localhost]# ./vmware-install.pl Follow the instructions and provide default values unless otherwise required.
  • Unmount CD/DVD [root@localhost]# umount /mnt
• Reboot the VM
• Navigate to /etc/sysconfig/network-scripts/ and edit the file ifcfg-eth0 Remove the line that contains the following parameter:
  • HWADDR
• Remove the following files:
  • 70-persistent-net.rules [root@localhost]# rm -rf /etc/udev/rules.d/70-persistent-net.rules
  • SSH Keys [root@localhost]# rm -rf /etc/ssh/ssh_host_* http://support.microsoft.com/kb/2550978
• Shutdown the VM [root@localhost]# halt
• Right click the VM and select Template ► Convert to Template

APPENDIX B

Troubleshooting

Introduction

This section provides basic information that can help you troubleshoot issues with interworks.cloud OSS VMware vSphere Service Manager installation and configuration.

Basic troubleshooting

1. Make sure all Cloud OSS web applications (Cloud OSS Provisioning Portal, Cloud OSS Orchestration Server and Cloud OSS Service Managers) are of the same version.
2. Make sure all Cloud OSS components have been upgraded to the latest Cloud OSS release.
3. Make sure you are able to open all Cloud OSS web applications (Cloud OSS Provisioning Portal, Cloud OSS Orchestration Server and Cloud OSS Service Managers) URLs in web browser.
4. Make sure Cloud OSS Service Managers are able to manage the systems where they are deployed. Sign in to the provisioning portal, navigate to Configuration ► Servers, select a server, and then open Windows Services.
5. Those error messages can contain useful information for troubleshooting:
a. Error message (if exists) with stack trace from Cloud OSS Audit Log (Sign in to the provisioning portal, navigate to Account Home ► Audit Log).
b. Errors and warnings from Cloud OSS event log (WebSitePanel) in the Windows Event Viewer.
To increase level of the WebsitePanel event log you need to go to C:\Cloud360\Service Managers (or the directory where you installed Cloud OSS Service Manager components) end edit web.config file with notepad. Find the entry <add name="Log" value="1"/> and set the value to 3. After this change, please check that the WebsitePanel event log is set to "Override events as needed".

interworks.cloud S.A.interworks.cloud OSS VMware vSphere® Service ManagerInstallation Guide