The key first step to setting up your CloudOS tenant is to configure the networks you want to build your services on. There are essentially 5 different networking scenarios that CloudOS customers generally use when deploying the service. More complex configurations can be deployed depending on your specific needs. If you have a complex network scenario or want to look at dedicated connectivity to CloudOS, contact our friendly Account Management team. Access to your servers is managed through the CloudOS Console Session Gateways separate to the networks you deploy. From the CloudOS Tenant Portal, you always have console access to all your servers no matter how the networking is configured. This console access is secured using SSL.
1. No Network
There is essentially nothing to configure. You can stand up Virtual Machines in your CloudOS tenant, but they will be isolated from each other and have no internet connectivity.
2. Private Network
This is a simple network for your new CloudOS servers to communicate with each other on. You define your IP Address Space and DNS Settings and the CloudOS network management system handles addressing the new servers you turn on. The servers can talk to each other but not to the internet or any other service. This scenario is used when you just want to stand up a server or group of servers and test communication between them.
Example scenarios:
- Standing up a single server or desktop image to test a concept
- Standing up a group of servers that communicate over a Local Area Network with each other
3. Private Network + Internet Gateway (NAT)
This is an extension of the Private Network above. On top of the IP Address and DNS Management, you are also provided a Public IP Address and a basic NAT firewall where you can open your virtual servers up to the internet on specific ports and services.This option also enables an Internet Gateway so your servers can access the internet behind your Public IP Address. This essentially adds a ‘virtual router’ that operates very similar to your internet gateway at work or at home.
Example scenarios:
- Standing up a Software as a Service Application or Web Service
- Building a new server platform for a potential customer to replace an on premise system
4. Private Network + VPN
This is an extension of the Private Network above. On top of the basic services, you are provided with a VPN Gateway Address, Public IP Address and a VPN Configuration ready to connect your existing Office network to. This option allows you to create a permanent network connection between your current platform and the CloudOS platform. The ‘virtual router’ handles the routing between hosts on your network and hosts on the CloudOS Network seemlessly. This scenario is used when you want to Connect and Extend your network in to CloudOS so you can stand up new infrastructure ‘beside’ your current infrastructure, or you want to set up Disaster Recovery scenarios.
Example scenarios:
- Extending your existing on premise network in to your own Private Cloud for platform expansion and Disaster Recovery
- Standing up new Servers and Services on CloudOS that can communicate with all the hosts/domain on your existing network
5. Private Network + VPN + Internet Gateway (NAT)
This is an extension of the Private Network + VPN option, but it also allows you to have another Public IP and NAT firewall routable by the virtual machines your run on CloudOS. This scenario is used when you want to Connect and Extend your network to CloudOS and you also want to publish new Applications on the internet. This allows new services you deploy on CloudOS that need to be accessed over the internet can run through the CloudOS Internet Gateway and the services can still talk back to devices on your existing network.
Example scenarios:
- Extending your existing on premise network in to your own Private Cloud for platform expansion and Disaster Recovery
- Standing up new internet facing Servers and Services on CloudOS that can communicate with all the hosts/domain on your existing network
- Deploying Software as a Service solutions out to staff or customers from your new CloudOS servers
What scenario is right for me?
If you just want a private cloud space to stand up new servers and you are not concerned with connecting your new CloudOS network to your existing business network, then you probably want to use a Private Network + Internet Gateway (NAT) setup. This solution also provides your Private Cloud access to the internet and a basic NAT firewall to publish services as needed.
If you want to specifically Connect and Extend your network to CloudOS, then you want to deploy a Private Network + VPN. This solution establishes the permanent link between your on premise network and your CloudOS Private Cloud.
If you want to connect your network and publish Software as a Service solutions out to the internet directly (as opposed to back through your local internet gateway), then deploy Private Network + VPN + Internet Gateway (NAT). This solution provides you access to your network, as well as providing a dedicated Internet Gateway directly from Lucidity to publish your SaaS solutions.
Buddy Davies
