1 Cloud Deployment Models Contents Sentinet Components Overview... 2 Cloud Deployment Models Overview... 4 Isolated Deployment Models... 5 Co-located Deployment Models... 6 Virtual Machine Co-Location... 6 Windows Azure VM Role Example... 6 Windows Azure Service Project Co-Location... 7 Deployment Models for Windows Azure AppFabric... 8 Multi-Cloud Deployment Models... 9
2 Sentinet Components Overview Nevatech Sentinet is a network of distributed components. Each component can be deployed to different computer systems, and the computer systems can be located on different networks. From the deployment perspective Sentinet consists of two parts: Sentinet Management Web Services ASP.NET Web Application connected to a SOA Repository Microsoft SQL Server database or Windows SQL Azure database. SOA Repository database stores Sentinet configuration along with all SOA solution assets, artifacts and monitoring data. ASP.NET Web Application hosts an interactive (Silverlight), Sentinet Administrative console and collection of Sentinet Management WCF SOAP services. Sentinet Nodes A Sentinet Node is an efficient network intermediary deployed as a special Microsoft WCF application hosted in an IIS/WAS environment (On-Premises or Cloud), which enables non-intrusive runtime manageability of SOA services and applications.
3 Each Sentinet component can be deployed in its own, a Cloud or On-Premises deployment environment. In a typical all-cloud deployment scenario, Sentinet Repository Web Services Application is deployed as an isolated application that runs in the Cloud hosted virtual machine. On a Windows Azure platform it can be deployed as either a Windows Azure Web Role or a Windows Azure VM Role. Sentinet Repository is typically deployed as a cloud-based SQL database. On the Windows Azure Cloud platform it would be deployed in the SQL Azure database. The difference in the Sentinet Cloud deployment models is centered around the variation of Sentinet Nodes deployments. This document discusses the variation of Sentinet Nodes deployment models.
4 Cloud Deployment Models Overview Nevatech Sentinet Nodes can be deployed in a variety of Cloud and Hybrid environments. The choice of deployment model is driven by the combination of specific requirements: Security requirements Performance requirements» Deployment processes and procedures requirements Connectivity requirements Choice of the Cloud provider Location of SOA managed services and their deployments Sentinet Nodes Cloud deployment models can also be categorized by the Nodes location relative to managed Cloud or On-Premises services: Isolated Deployment Models Sentinet is deployed as a Cloud solution isolated (de-coupled) from the SOA managed services Co-located Deployment Models Sentinet is deployed as a Cloud solution co-located with managed SOA services deployment The isolated deployment models category describes deployment models where Sentinet Nodes are deployed in its own physical or virtual isolated environment. For example, Sentinet Nodes are deployed in the Cloud hosted virtual machines that are isolated from the virtual machines that host managed SOA services. The co-located deployment models category describes multiple deployment models where managed SOA services co-location with Sentinet Nodes depends on specific Cloud provider capabilities. For example, Microsoft Windows Azure Cloud Platform is designed around the web role, worker role and VM role concepts and has specific implications on the Sentinet co-location deployment models.
5 Isolated Deployment Models An isolated deployment scenario is where Sentinet Nodes are deployed in a dedicated Cloud virtual environment isolated from the managed SOA services and applications. Most typical examples of the isolated deployment scenarios are the following: Sentinet Nodes are deployed in an isolated Virtual Machine, such as VM role in Windows Azure Sentinet Nodes are deployed as Web Roles in an isolated Windows Azure Service project The Sentinet isolated deployment model enables managed SOA services and Sentinet Nodes with loosely coupled deployments; managed SOA services and applications are deployed via processes and packages independent from Sentinet deployment processes and packages. Unlike co-located deployment scenarios, the isolated deployment model is exposed to encountering higher network latencies for messages routed via Sentinet Nodes. This is due to the unpredictable location of the managed SOA services relative to Sentinet Nodes location, even when the location is within the same Cloud provider infrastructure.
6 Co-located Deployment Models Co-located deployment models enable Sentinet Nodes and managed SOA services and applications with a higher throughput and enhanced performance because of the predictable location of SOA services relative to Sentinet Nodes. The scope of co-location can vary depending on the capabilities of a specific Cloud provider network and virtualization infrastructure. Unlike isolated deployment scenarios, co-located deployment models assume a certain level of tight coupling in managed SOA services and Sentinet Nodes deployment processes and packages. Virtual Machine Co-Location In this scenario managed SOA services and applications are deployed within the same VM image, such as the Windows Azure VM Role image. Although the VM co-location model requires Sentinet Nodes to be deployed side-by-side with managed SOA services, it enables managed Cloud SOA solutions with the highest performance and security. Managed SOA services can be excluded from the external access and made available only for local access by Sentinet Nodes. With this deployment model, Sentinet Nodes are executed as transparent networks intermediaries with no additional network hubs and SOA services security is fully delegated to Sentinet Nodes for dynamic management and access control. Windows Azure VM Role Example SOA services are deployed in a VM Role with Microsoft named pipes transport and bindings, while the Sentinet Nodes provide external access via internet transports and protocols (http, https or net.tcp). In this scenario managed SOA services are fully secured by Sentinet Nodes. Sentinet Nodes communicate locally with SOA services via highly efficient named pipes transport.
7 Windows Azure Service Project Co-Location Windows Azure Hosted Service project model can be defined as a collection of web, worker and VM roles that share a common Windows Azure subscription account, deployment package and internet address. Similarly to the VM co-location model, managed SOA services can be enabled with internal endpoints when access to them is provided only via Sentinet Nodes running on a separate Web or VM Role within the same Windows Azure Service project. In this deployment scenario managed SOA services do not share the same VM instances with Sentinet Nodes. The managed SOA services share a common Windows Azure datacenters infrastructure that includes the concept of Windows Azure Internal endpoints. Unlike the VM co-location model, the connection between Sentinet Nodes and managed SOA services is not subject to local machine communication. At the same time this deployment (unlike the isolated deployment models) is not subject to external access that always routes messages via Windows Azure external load-balancers.
8 Deployment Models for Windows Azure AppFabric In a hybrid On-Premises/Cloud environment, services can be deployed in both types of environments. They can also be deployed only On-Premises, with the exposure to specialized Cloud infrastructure such as Windows Azure AppFabric Service Bus. Nevatech Sentinet integrates with, and extends Windows Azure AppFabric Service Bus capabilities. Internal SOA services can be dynamically on-boarded to Windows Azure Cloud platform without code or configuration changes. Any service application can be dynamically connected to Windows Azure via internal On-Premises Sentinet Node regardless of the type of managed services development and hosting platform. Additionally, all services and applications enabled with Windows Azure connectivity become subject to the Sentinet dynamic management of security, access control, monitoring and service agreements.
9 Multi-Cloud Deployment Models Nevatech Sentinet Nodes can be deployed in a variety of distributed environments that cross the boundaries of multiple On-Premises and Cloud providers and consumers, thus helping organizations to manage services and applications via a unified and centralized SOA Management Infrastructure. All distributed Sentinet Nodes are subject to secure remote control with remote access to all managed services auditing and SLA monitoring information.