Wednesday, 28 December 2016

Microsoft Windows Azure Pack (PRIVATE CLOUD - WAP) - Complete Setup Deployment Requirement - Part 3

Hello Everyone,

This post is to explain You about complete setup requirement for Private Cloud in Your environment.

There are 2 Main types for deployment - Standalone Deployment or High Availability Deployment.

Let's start understanding different architecture for deployment...

NOTE: 

Below explanation is shared based on my personal experience. For better planning, understanding & deployment, I will suggest You to get well-designed solution documents & architecture from Microsoft or Microsoft's Partner companies based on Your environment requirements. My blog post will help in learning technical background only. 


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

To see Microsoft Windows Azure Pack (PRIVATE CLOUD - WAP) - Components & Deployment Types- Part 2, Click Here!


WAP COMPONENT DEPLOYMENT REQUIREMENT: 


As explained in my previous post (Click Here to see Previous Post!), there are 2 types for WAP Components deployment types - Express or Distributed Deployment Types. 

Microsoft has explained both deployment types with detailed architecture diagram & requirements so for this, I don't need to explain here. You can see the same by clicking on below link:

CLICK HERE: WINDOWS AZURE PACK - COMPONENTS DEPLOYMENT ARCHITECTURE!!!


WAP SETUP REQUIREMENT:


Now, You might be confused here why I mentioned 2 different headings for WAP Setup. There are 2 things to understand here:

  • WAP Component Deployments - Which includes WAP IIS Components for Admin & Tenant Portals.

  • WAP Setup Deployments - which includes back-end infra setup which will be integrated with WAP Portal to provide IAAS & other services to tenants.


This explanation is given to give You more clarity between both so that You don't get confused with deployment. 

If You deploy, WAP Components only doesn't means that Your Private Cloud setup is ready to work until Your back-end infrastructure and other components not ready with integration with each other.  

WAP Component Deployment can be understand from Microsoft Link shared above but now You must understand what all other back-end infrastructure is required to make Your private cloud setup ready to use in production.


OTHER BACK-END INFRA COMPONENTS REQUIRED FOR PRIVATE CLOUD:


System Center Suite which includes 7 components and Windows Servers (either standalone or clustered) are the back-bone of private cloud setup. Not all System components are mandatory to use but few are required.

Below are details for components used in WAP Setup:

REQUIRED:




  • SPF: Service Provider Foundation (Available in Orchestrator Setup) is the inter-mediator between SCVMM & WAP which helps in performing request-response responsibility using SCVMM power-shell scripts stored in SPF machine. All request generated via tenant/admin portal are forwarded to SCVMM via SPF and vice-versa for all responses. CLICK HERE: LEARN COMPLETE SPF FROM BEGINNING!!!



OPTIONAL:




  • SCCM: This component is used for patching, generating compliance report, inventory report, application deployment etc. I haven't written any series on this component yet because already many great Bloggers have written very good posts on this component. Few reference links are mentioned below (I am following these few blogs when required on this components):



          http://gerryhampsoncm.blogspot.in/2013/02/sccm-2012-sp1-step-by-step-guide.html



  • SCO: This component is used for automating certain tasks using integration between all components and then using scripts. (Yet to start the series on this!)



  • SCSM: This is a ticketing tool for generating tickets based on certain request like IR, SR etc. Didn't worked on this tool yet 😏



Above description will clear Your concept about all components used for Private Cloud Setup.

Now, Decision required is to deploy Private Cloud Setup as STANDALONE or HIGH AVAILABILITY?

Difference between both is:


  • STANDALONE environment will be deployed on single VMs for each components. If any machine goes down, Your complete setup will be down.

  • HIGH AVAILABILITY environment will have min 2 VMs for each components with guest clustering or software NLB (Network Load Balancer) configured which will gives You 1 fail-over availability. By 1 Failover availability, I mean to say that suppose You have used 2 VMs as guest clustering then if 1 VM goes down then 2 VM will become active node and all service will start on other node automatically. 


I will explain about both scenarios with architecture diagram in my next post. This post is just to clear Your logic behind all deployments.

After explaining with architecture diagram, You will be easily able to design Your architecture based on Your environment (NOTE: Still, Communicate with Microsoft for best solution for Your environment. 😉)



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