Example Environment
1.0 Introduction
The intent of this portion of the reference architecture is to provide an example application that will demonstrate various elements of VM Squared. Although this is a simple example, these steps provide the foundation for creating a multi-tenancy tiered application. In all cases, open source software has been used to simplify configuration of the applications.
2.0 Architecture
Below is a diagram of the sample application:
The setup consists of three Virtual Data Centers (VDCs) named: Public, Private, and DMZ. This represents a typical, basic architecture for a cloud solution. The Public VDC will represent a standard user with access to the public internet (although internal non-routeable addresses are used). The Private VDC represents an environment that has no access to the internet. The DMZ has controlled access to both the Private VDC and the Public VDC. This allows a user to access a web-based application that connects to application servers in the Private VDC.
A server monitoring application is used as the base application, as it is very easy to implement and show the three VDCs in operation. Nagios was chosen as the monitoring application, although any other application could be used instead. This provides a web front end that can be viewed via a browser from the User Interface (UI) in the Public VDC.
A target application server, with Operating System only, is located in the Private VDC. Through the Nagios monitoring server, the Public VDC user will be able to monitor performance data from the applications server.
All of the application servers i.e. User IF, Monitoring Front End, and Application Server, are realized using Virtual Machines (VMs). Each of these will be constructed such that they are contained within their respective VDCs. Further Users and Groups will be created to instantiate, configure, and manage the virtual machines. In this manner, there will be logical separations between the VDCs.
The networking between the three VDCs will be accomplished using a Gateway Appliance. This is a virtual machine that has been specially built for the SoftIron VM Squared infrastructure. It will also show how startup scripts can be used from the GUI to configure applications servers.
3.0 Implementation
The implementation is broken down into the following sections:
Scope | Description |
---|---|
Users and Groups | Groups will be defined for each VDC. Additionally, for each VDC, a group admin and group user will be created. An admin will also be created such that it can access all VDCs (e.g. Ref_Config_Admin) |
+ | VDC |
Networking | This will be realized using the SoftIron Gateway Appliance. It is configured using a startup script to provide the networks for the VDCs. |
Templates | A template will be created for each of the application servers. This will be accomplished using the Ref_Config_Admin. Access rights will be given to the group admins and users to enable the applications servers in each VDC to be created. |
Application Servers | These will be created in each VDC by the group admin. Specific rights will also be added for the users in each VDC. |
Server Monitoring | This will be realized using the SoftIron Nagios appliance. It is configured using a startup script to provide server monitoring for virtual machines. |