[1] Virtual Machine or Physical Server

2. OSS Service Managers Deployment Considerations

This section describes possible deployment scenarios of Cloud OSS Service Manager components. Basically, the OSS Service Managers consist of the endpoint components of the provisioning engine, that handle the actual provisioning / de-provisioning operations. The deployment of Service Manager Components may vary, depending on the actual deployment and topology of the provisioned services. However, below you can view a brief summary of typical deployment configurations regarding popular services, such as Hosted Exchange, Hosted SharePoint, Lync Server HP, VMware, Hyper-V.

2.1. Hosted SharePoint Foundation Deployment

This deployment requires that Cloud OSS Service Managers are deployed on all web front-end servers of the SharePoint Foundation infrastructure. Due to Active Directory requirements, the Cloud OSS Service Managers must also be installed on one or more Active Directory servers (Domain controllers). If the Cloud OSS Service Manager components are deployed on more than one server (regarding the same server role) then a Load Balancer may also be utilized to provide redundancy and load distribution for the Service Manager Web services (Fig. 1).

Fig. 1

2.2. Hosted Exchange Deployment 

This deployment requires that Cloud OSS  Service Managers are deployed on all CAS servers of the Hosted Exchange infrastructure. Due to Active Directory requirements, the Cloud OSS Service Managers must also be installed on one or more Active Directory servers (Domain controllers). If the Cloud OSS  Service Manager components are deployed on more than one server (regarding the same server role) then a Load Balancer may also be utilized to provide redundancy and load distribution for the Service Manager web services (Fig. 2).

Fig. 2

2.3. Lync Server 2013 Multitenant Hosting Pack Deployment

This deployment requires that Cloud OSS Service Managers are deployed on all Front-end and Director Servers of the Lync 2013 infrastructure. Due to Active Directory requirements, the Cloud OSS  Service Managers must also be installed on one or more Active Directory servers (Domain controllers). If the Cloud OSS Service Manager components are deployed on more than one server (regarding the same server role) then a Load Balancer may also be utilized to provide redundancy and load distribution for the Service Manager Web services (Fig. 3).

Fig. 3

2.4. VMware vSphere 5.x Deployment

This deployment requires that Cloud OSS Service Managers are deployed on one or more servers that have access to vCenter Server, in order to manage and provision resources using the vCenter Server API. If the Cloud OSS Service Manager components are deployed on more than one server (regarding the same server role) then a Load Balancer may also be utilized to provide redundancy and load distribution for the Service Manager Web services (Fig. 4).

Fig. 4

2.5. Hyper-V 2012 R2 Deployment

 This deployment requires that Cloud OSS Service Managers are deployed on one or more servers that have access to System Center Virtual Machine Manager (SCVMM 2012 R2), in order to manage and provision resources. Alternatively, Cloud OSS Service Managers may be directly installed on the SCVMM administration server. If the Cloud OSS Service Manager components are deployed on more than one server (regarding the same server role) then a Load Balancer may also be utilized to provide redundancy and load distribution for the Service Manager Web services (Fig. 5).

Fig. 5

2.6. CloudWorks Deployment

CloudWorks is an advanced Service Manager currently utilizing VMware and Hyper-V environments to deliver complete Infrastructure-as-a -Service offerings to the end user. This deployment requires that Cloud OSS Service Managers are deployed on one or more servers that have access to both System Center Virtual Machine Manager (SCVMM 2012 R2) and vCenter Server, in order to manage and provision resources. Alternatively, Cloud OSS Service Managers may be directly installed on the SCVMM administration server (access to vCenter Server will still be required). If the Cloud OSS Service Manager components are deployed on more than one server (regarding the same server role) then a Load Balancer may also be utilized to provide redundancy and load distribution for the Service Manager Web services (Fig. 6).

Fig. 6

3. General Server Requirements

To install interworks.cloud OSS platform you need to obtain the following servers:

• An Active Directory server

  Note: Active Directory is only required if you will be providing any of the following applications as a hosted service

  • Exchange Server 2007/2010/2013
  • Blackberry Enterprise Server 5
  • Office Communications Server 2007 R2
  • Lync 2010/2013
  • Windows SharePoint Services 3.0
  • SharePoint Foundation 2010/2013
  • Dynamics CRM 4.0
• A Microsoft SQL server (or cluster of Microsoft SQL servers)
• Orchestration servers (one or more)
• Provisioning Portal servers (one or more)
• Service Manager servers (one or more)

Each of these servers should meet the general minimum requirements shown in the following table:

Table 1. General server requirements

Any edition of the operating systems listed above is supported. Both 32-bit and 64-bit are supported. Microsoft Internet Information Services (IIS) version 7.x/8.x or higher must be installed on every server where the Cloud OSS components will be installed. Microsoft SQL Server is required in order to host the internal Cloud OSS database.

The Cloud OSS database can be installed on any of the following versions of SQL Server:

• SQL Server 2008 Express edition or higher
• SQL Server 2008 R2 Express edition or higher
• SQL Server 2012 Express edition or higher
• SQL Server 2014 Express edition or higher

The SQL Server Express edition is free. You can download the latest version from the following link: http://www.microsoft.com/express/sql/download/ .
interworks.cloud OSS components can be installed on a dedicated physical server or on a virtual machine hosted in one of the following virtualization environments:

• Microsoft Hyper-V
• KVM
• Virtuozzo
• VMware
• XenServer

4. Network and Domain Requirements

All network parameters will have to be configured correctly prior to installing Cloud OSS components. These parameters include:

• Static IP addresses for all servers that either host applications or will be used to host Cloud OSS components.
• Network Subnet masks
• Default gateways
• DNS settings

Firewall settings must be configured to allow all the servers where the Cloud OSS components will be installed to access the following server: downloads.interworkscloud.net. The servers must be able to connect to this server through TCP ports 80 and 443.

5. Remote Access Prerequisites

This section describes the remote access prerequisites in case the Customer has prepared the required infrastructure described in the previous section. An interworks.cloud Engineer will be remotely accessing this infrastructure via Remote Desktop in order to deploy interworks.cloud OSS.

Depending on its remote access policies and procedures, a Customer may choose to provide remote access to interworks.cloud using a secure VPN connection or another Remote Session software. Alternatively, interworks.cloud may provide the means for remote access if requested by Customer.

Prior to the deployment, the following information must be provided to the authorized interworks.cloud Engineer:

1. The Remote Access credentials (VPN or Remote Session Software and RDP).
2. The required credentials and IP Addresses for accessing the, described in the previous section, server infrastructure (Standalone or Highly Available Scenario).
3. The Domain Admin Account credentials and the SQL sa account password (OSS Database Server) or an equivalent account.
4. The Load Balancer Configuration (if applicable, depending on deployment scenario).

Firewall settings or access lists should permit communication between servers that will host interworks.cloud OSS components. The following table lists the necessary access rules and port requirements for the interconnection of all interworks.cloud Platform OSS components. Please note that ports not marked in bold, denote default application ports that may actually differ, depending on the installation settings of each specific application.


 

Table 2. Access rules and Port requirements