Private Cloud. Technical Overview. Revision Date: 10 August 2015

Transcription

1 Private Cloud Technical Overview Revision Date: 10 August 2015 ISL Online, ISL Light, ISL AlwaysOn, ISL Pronto, and ISL Groop are registered trademarks of XLAB d.o.o. Copyright XLAB d.o.o. Ljubljana. All rights reserved.

2 Document Objective This document provides basic information about ISL Online Private Cloud as well as prerequisites for setting it up, general guidelines and initial test procedures. It contains general information and examples for a Private Cloud with two servers. Please modify the examples accordingly so that they match your desired setup. Platform Overview Cloud computing benefits combined in the ISL Online Private Cloud bring you the best remote desktop access and support, live chat and web conferencing services. Particularly larger organizations using the Server License might consider setting up several servers and connecting them into a corporate Internet communications network, a Private Cloud. Corporate Private Cloud Network includes at least two ISL Conference Proxy (ICP) installations and is fully scalable. Each ICP requires one Corporate Server License (CSL). More ICP servers can be added to the Private Cloud network anytime in order to expand the capacity of the system (double, triple, etc.). Private Cloud Network provides all benefits of cloud computing technologies: Load Balancing Fault Tolerance GeoDNS Active-Active Backup Distributed Database ICP servers may be installed in a single data center or several company's data centers across the country or worldwide.

3 Supported Operating Systems ICP can be installed on the following operating systems: Microsoft Windows Server 2003 Microsoft Windows Server 2008 Microsoft Windows Server 2012 Microsoft Windows Vista Microsoft Windows 7 Microsoft Windows 8 Microsoft Windows 10 Linux Kernel 2.6 or higher and glibc or higher Please note that we also support virtualization environments (such as Hyper-V, Xen, VMware) with one of the supported operating systems installed. Firewall requirements Each ICP server must have a static public IP address (current ICP server is marked with current_server, all the other ICP servers are marked with other_servers, we will use a.b.c.d for the public IP address of the 1st ICP server and e.f.g.h for the 2nd ICP server) and the following ports accessible (make sure appropriate rules are set in the firewall, ICP does NOT support HTTP proxies, SSL filters or other content filtering software - please open ports directly): TCP: current_server:7615 <-- * (primary ISL Online port) TCP: current_server:80 <-- * (secondary ISL Online port) TCP: current_server:443 <-- * (secondary ISL Online port) TCP: current_server:7616 <-- other_servers (ICP to ICP private cloud communication) TCP: current_server --> other_servers:7616 (ICP to ICP private cloud communication) UDP: current_server:53 <-- *:* (DNS port) UDP: current_server:* --> *:123 (and reply back with connection tracking: UDP: current_server:* <-- *:123) (NTP ports)* * ICP NTP client implementation requires both rules. If you decide to use system NTP client instead, modify accordingly. Please keep in mind that if the time is off by 20 seconds or more, ICP to ICP connection is terminated until this is fixed.

4 DNS requirements A wildcard domain name must be assigned to your Private Cloud, we will use *.isl.company.com as an example. Once the domain is known, licenses are created and uploaded to each ICP server that will be added to your Private Cloud. Glue subdomain records need to be added on the DNS server(s) for the top domain (in our example for company.com). It should look like this (BIND zone file format, example for a Private Cloud with two ICP servers): isl.company.com IN NS ns1.isl.company.com isl.company.com IN NS ns2.isl.company.com ns1.isl.company.com IN A a.b.c.d ns2.isl.company.com IN A e.f.g.h (where a.b.c.d is the public IP address of the 1st ICP server and e.f.g.h the public address of the 2nd ICP server) Private Cloud Setup Once all the requirements above have been met, you have n (in your case two) ICP servers that are properly configured, fully updated, online and ready to be connected into a Private Cloud. DNS zone You will use the DNS section in the administration (DNS server --> Zones) to create a new zone (isl.company.com) with the following: NS ns1 NS ns2 ns1 A {server_address 1} ns2 A {server_address 2} Connecting into a Private Cloud You will use the GRID section in the administration of the 1st ICP to create a new Private Cloud (Configuration --> GRID --> Create), then add the 2nd ICP server to that Private Cloud. Once the procedure is complete, you can check in ICP administration (Activity monitor --> Servers) if the servers are successfully connected.

5 Testing the Installation DNS tests We recommend the following sequence of DNS tests to make sure everything is ok (samples below use the dig network utility): dig NS dig NS dig NS dig NS dig dig dig dig dig islpronto-sdfhwgs.isl.company.com General tests Now you can proceed with normal testing (e.g. create an ISL Light session) to make sure everything is working properly. You may wish to test fault tolerance by having the ISL Light session run on the 2nd ICP and then temporarily disabling ISL Light service on the 2nd ICP server (Configuration --> GRID --> Load balancing). The session should automatically switch to the 1st ICP server, successfully reconnect and continue.

6 Server Load Monitoring It is possible to use the network status page on any of the ICP servers within your Private Cloud to check current network status, CPU load, number of currently running sessions etc.: Apart from the network status link, server status is accessible in ICP administration (Activity monitor --> System statistics --> Current usage). Additional Info, Problems, Questions If you encounter any problems or have any additional questions, you can contact us via or through our live chat at