Tuesday, 6 December 2016

Microsoft Windows Azure Pack (PRIVATE CLOUD - WAP) - Components & Deployment Types- Part 2

Hello Everyone,

This post will help You understand WAP Components & Deployments types (In Simple terms, different ways to Deploy WAP in Your Environment).

To see Microsoft Windows Azure Pack (PRIVATE CLOUD - WAP) - INTRODUCTION - Part 1, Click Here!

Let's start understanding WAP Components first...



WAP COMPONENTS:


Basically, WAP includes multiple APIs which perform respectively back-end process (task) to integrate WAP Portals with Infrastructure (back-end servers) & give response based on request to WAP Portal. These multiple APIs are known as WAP Components (This term is defined by me based on my personal experience on Private Cloud).   

Microsoft provide options to either deploy WAP Components as a bundle or using individual components. 

Let's start understanding each components one by one in details below:


REQUIRED COMPONENTS:


Below are the required components:


ADMIN API:


This performs all administrative tasks for Administrators using Administrators Management Portal.


TENANT API:


Helps Tenants to manage cloud services based on plans which is subscribed to their account. Users can perform all tasks using self-service tenant portal.


TENANT PUBLIC API:


This API helps in providing all required services to Tenants which they subscribed for from back-end.


ADMIN AUTHENTICATION SITE:


To Login to Admin Portal, authentication is required whether login user is authorised to login or not. By default, it is windows administrator (Local Account). But You can also configure Windows Azure ADFS (Active Directory Federation Service) as well to provide user access to the Admin Portal.

TENANT AUTHENTICATION SITE:


This helps in providing authentications to management portal for tenant users. By Default, it uses ASP.Net Membership provider authentication method.


ADMINISTRATOR PORTAL:


This is a Management portal for Administrator to perform all management tasks on portal. Using this portal, Administrator manage all resources like cloud, user account, plan, quotas, prices, manage subscriptions etc. Using this portal, Administrator has to register Virtual Machine Cloud for resources availability on portal.


TENANT PORTAL:


This portal is a self-service tenant portal for all tenant users. Using this portal, all tenants deploy (provision) virtual machines, monitor & manage all services.

NOTE: Both Admin & Tenant Portals are custmizable and console looks can be changed as per Your requirement by development team.


OTHER OPTIONAL COMPONENTS:


WEB SITES:


You can enable website as a service which will help in creating shared web hosting platform for ASP.NET, PHP & NODE.js web applications.


VIRTUAL MACHINE:


This is mostly used components for providing Infrastructure As A Service (IAAS) to tenants for Windows & Linux Virtual Machines. Using this, Tenants can deploy & used Virtual Machines on portal.


SERVICE BUS:

This helps in providing messaging services between distributed applications.


AUTOMATION & EXTENSIBILITY:


This helps in automating custom services integration using scripts or runbook on portal.



SQL & MYSQL:


This is also known as DATABASE As A Service where You can deploy SQL/MYSQL Databases for Tenant Users.


Above all are the components which are available in Windows Azure Pack. You can also integration On-premises WAP with Microsoft Azure (Public Cloud).


Let's now try to understand concept for Deployment Types below....



DEPLOYMENT TYPES:


As per Microsoft, There are 2 types of deployment:



EXPRESS DEPLOYMENT:


This deployment is used to show Proof of concept (POC) for Windows Azure Pack. This deployment requires minimum resources for deployment for each components. You can use only 1 VM to deploy all WAP Components with Database as well on same machine.


Minimum Resource requirement includes (Using Virtual Machine):

  • 4 GB vRAM
  • 4 vCPU
  • C Drive: 50 GB for OS & D Drive: 100 GB for SQL WAP DB


DISTRIBUTED DEPLOYMENT:


This deployment is used in Production environment. In this method, as per Microsoft, WAP components are distributed (or installed) on multiple different Virtual Machines. This is based on categories like:


  • Public facing components (Tenant Components on 1 VM).
  • Back-end components related to management services on 2nd VM.
  • Other Service components on other VMs.

Above 2 deployments types are based on Microsoft. But, based on my experience to deploy WAP in production environment, We can deploy all components on 1 VMs itself with High Availability. HA means all components will be deployed equally on 2 VMs with NLB (Network Load Balancing) Configured. 


This is basic information explained above to understand meaning of each components & concept of deployment types. 

In my next post, I will explain different WAP Architectures based on deployment types in details which will also include capacity planning & prerequisites for WAP Deployment.

Share Your feedback or any query!!!


Happy Reading!!!

If You like my post then follow my updates:


Join my Facebook group for updates on trending technologies/technical references/issues etc:

No comments:

Post a comment