Post on 22-May-2020
AZURE
Unleash the full power of
the Azure Stack
Development Kit
Kenny Lowe
EMEA Azure Stack Lead, Dell EMC
AZURE The aspiration of hybrid cloud
AZURE
Common Identity
Integrated Management and Security
Consistent Data Platform
Unified Development and DevOps
True Hybrid – Consistent, not just Connected
AZURE
One Azure Ecosystem
AZURE Why Azure Stack?
Potential blockers for Azure Public adoption:
• Regulatory compliance
• Data sovereignty
• Data proximity/latency
• Edge and disconnected
scenarios
• No Azure!
AZURE
Edge and disconnected solutions
Cloud applications to meet varied regulations
Modernize applications on-premises
AZURE
Classic ApplicationsMonolithic apps in Virtual Machines that can take advantage of Scale-Up
Cloud-native apps and micro-servicesApplications spanning IaaS and PaaS that take advantage of Scale-Out
AZURE
Classic ApplicationsMonolithic apps in Virtual Machines that can take advantage of Scale-Up
Cloud-native apps and micro-servicesApplications spanning IaaS and PaaS that take advantage of Scale-Out
IT Investments
Focus on the application to avoid infrastructure problems
Focus on the infrastructure to avoid application problems
AZURE One hybrid cloud platform for all apps
Cloud infrastructure
Azure IaaS | Azure PaaS
Azure Resource Manager
Portal | PowerShell | DevOps tools
Microsoft Azure Public
Cloud infrastructure
Azure IaaS | Azure PaaSCompute | Network | Storage | App Service | Service Fabric*
Azure Resource Manager
Portal | PowerShell | DevOps tools
Microsoft Azure StackBehind the firewall | Hosted
Azure services in your datacenter
Unified app development
One Azure ecosystem
Developers
IT
Dell EMC Cloud for Microsoft Azure Stack
Manage with a consistent experience
AZUREAzure Services on premises with Azure Stack
Azure Event Hubs*
Azure IoT Hub*
Azure Functions
Azure App Service
Storage – Blob, Tables, Queues
Networking – VNETs, NSGs,
LBs, VPNs
Azure Marketplace
Virtual Machines (VM)
VM Scale Sets
Azure services in your datacenter
Unified app development
One Azure ecosystem
Developers
IT
Azure IaaS on-premises Azure PaaS available on-premises
Additional Azure services delivered through Azure Stack updates
AZUREMicrosoft Azure Stack Physical Components
• Top of Rack Switches
• BMC Switch
• Hardware Lifecycle Host
• Compute Nodes (4-16 nodes)
AZURE Single node dev/test for Microsoft Azure Stack
DevOps/Infrastructure-as-Code with ARM templates
Azure Stack admin & tenant experiences
Azure App Service, Functions, IoT Hub*, Event Hubs*
Visual Studio and PowerShell experience
Infrastructure-as-a-Service
Get started today with Azure Stack for PoCs and dev/test
The single-node Azure Stack is open to all customers.
It will continue to be offered through the life of the
program to provide customers a way to purchase an
Azure Stack for the purposes of development and
testing.
It is not intended for use with production workloads.
AZURERequired Specs
AZURE What scenarios can you address with the ASDK?
AZURE
ASDK Networking
ASDK Host
Azs-ACS01
AzS-ADFS01
AzS-CA01
AzS-DC01
AzS-ERCS01
AzS-GWY01
AzS-NC01
AzS-SLB01
AzS-WAS01
AzS-WASP01
AzS-XRP01
NAT
AZURE
ASDK Networking
Azs-ACS01
AzS-ADFS01
AzS-CA01
AzS-DC01
AzS-ERCS01
AzS-GWY01
AzS-NC01
AzS-SLB01
AzS-WAS01
AzS-WASP01
AzS-XRP01
NAT
NATAzS-ROUTER1
AZUREHow do we do this?
Create a new VM, and attach to SDN Switch
Attach Windows Server 2016 ISO
Configure SDN Switch Isolation
Attach Second NIC to Public Switch
Power on and Install Windows Server 2016
Configure SDN NIC with these Settings
Configure Public NIC with these settings
Change the IP/Mask to suit your CorpNet
AZURE How do we do this?
Create new NAT on AzS-ROUTER1New-NetNAT -Name "NATSwitch" -InternalIPInterfaceAddressPrefix"192.168.1.0/24"
$range = 2..48foreach ($r in $range) { route add -p "192.168.102.$($r)" mask 255.255.255.255192.168.200.64 }
$range = 1..8
foreach ($r in $range) { route add -p "192.168.105.$($r)" mask 255.255.255.255192.168.200.64 }
Add static routes pointing to AzS-SLB01
AZURE How do we do this?
Next you will need to add appropriate routing to your internal network or clients.
Each of:192.168.100.0/24
192.168.101.0/24
192.168.102.0/24
192.168.103.0/24
192.168.104.0/24
192.168.105.0/24
192.168.200.0/24
… needs to use the Public Switch IP of the new VM you deployed as their Gateway.
AZURE How do we do this?
Export Certificates from Azure Stack Host, and import them on machines you’ll
access Azure Stack from:
AZURE
ASDK Networking
Azs-ACS01
AzS-ADFS01
AzS-CA01
AzS-DC01
AzS-ERCS01
AzS-GWY01
AzS-NC01
AzS-SLB01
AzS-WAS01
AzS-WASP01
AzS-XRP01
NAT
NATAzS-ROUTER1
AZURE
Open Q&A