Wednesday, 2 August 2017

Microsoft Azure Stack - Deployment Architecture with VM Roles - Part 2

Hello Everyone,

This post is to explain single node deployment architecture for Azure Stack Development Kit & default VM Roles which are created during ASDK Deployment.




Let's start with Azure Stack HLD Architecture for Single Node deployment...

ASDK ARCHITECTURE - HLD:


Azure Stack Development Kit Architecture shown below is High Level Design (HLD) where I have shown how ASDK & all VM Roles will be deployed on Physical Host.

Detailed Low Level Design (LLD) will be explained in next post where I will explain detailed requirements for deploying ASDK.

ASDK HLD Architecture:


As shown in above diagram, I have shown a Physical Host where You will deploy Windows Server 2016 OS & later You will download ASDK File on the server. 

Once Download is completed, You need to prepare Azure Stack OS named as "Cloudbuilder.vhdx" using ASDK Installer file. During ASDK OS preparation, You have to provide some required information & later need to reboot the server.

Now, once reboot is started, Your server will have dual booted means it will run with 2 Operating Systems - Windows Server 2016 OS (which is installed first on physical host) & Azure Stack OS (Cloudbuilder.vhdx file is attached to Physical Host).

Now, Boot Order will by default change to Azure Stack OS (Cloudbuilder.vhdx) which is also running with Windows Server 2016 OS.

This Azure Stack OS has required roles & features installed like Hyper-V, ADDS, DNS etc

Once You login in Azure Stack OS, You need to install ASDK again using ASDK Installer which will later deploy all VM Roles & configure networking roles.

In my upcoming posts, I will explain about installation process step by step with screenshots. 😉😉  

NOTE: 

ASDK is deployed only on single physical node. This can be used only for testing or development environment (NOT FOR PRODUCTION ENVIRONMENT) where You can create, deploy & evaluate Azure Stack services & have self-service portal experience. 


AZURE STACK INFRASTRUCTURE ROLES:


Azure Stack ASDK provide services with certain pre-defined Virtual Machine Roles which cannot be modified & cannot not be connected through RDP or console. These are also known as Management VMs where You cannot configure or do any changes.

You have to use only Azure Stack Admin Portal where You can create & manage Your services which You want to evaluate. Tenants will use offered services through Tenant Portal.

NOTE: These all VM Roles are already described on Microsoft Azure Stack Document Site as well.

Below are the default Azure Stack Management VM Roles which control all management services:


This is all about Azure Stack Development Kit HLD Architecture with default VM Roles.

In my next post, I will explain ASDK Prerequisites with LLD Architecture in details.


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:

10 comments:

  1. A simple bookmarking tool that makes it easy to save, organize and share your favorite web pages. Access your bookmarks from any computer, phone or tablet. Listango works on all modern web browsers… Seamless gutters

    ReplyDelete
  2. You completed some great factors there. I did a seek nearly the problem and determined re all folks will post when your blog. error 0x80d02002

    ReplyDelete
  3. By application, the market has been arranged into profound learning, shrewd robots, picture acknowledgment, advanced individual right hand, questioning strategy, language handling, signal control, video investigation, discourse acknowledgment, setting mindful preparing, and digital security. artificial intelligence training in pune

    ReplyDelete
  4. Hi there, I found your blog via Google while searching for such kinda informative post and your post looks very interesting for me. Hack APP Data APK

    ReplyDelete
  5. I have been following your post for a long time. I always found it very interesting and valuable. keep posting it is really helpful.

    Cloud Migration services

    Aws Cloud Migration services

    Azure Cloud Migration services

    ReplyDelete
  6. We are a part of the success story for many of our customer's successful cloud Migrations.
    Vmware Cloud Migration services

    Database Migration services

    ReplyDelete
  7. Thank you for the informative post about Security challenges in AWS , Found it useful . cloud migration services have now become secured and with no-risk
    Lia Infraservices

    ReplyDelete
  8. I am really impressed with the way of writing of this blog. The author has shared the info in a crisp and short way.

    Best Cloud Migration Tools


    Best Cloud Migration services

    ReplyDelete