This is an old revision of the document!
Table of Contents
Azure
Login on Console
To execute console commands do
# login az login az account set --subscription a1a96cc4-4aa4-4c58-a53d-808b88bb4fb4 az account tenant list az account show # logout az account clear
Azure function
Azure functions in Azure Portal
The trigger and code.
Only available after uploading the code into the function, via
az functionapp deployment source config-zip -g $resourceg -n $functionname –src app.zip
Limitations of Azure functions
- Azure functions - are NOT only serverless.
- You can choose a premium subscription and deploy your Azure function as an always running instance into your network
- You CAN'T use a serverless function - in a private network
- You CAN'T have multiple triggers for a function. ONly one of
- http_trigger
- Blob trigger
- CosmosDB trigger
- EventHub trigger
- Queue trigger
- ServiceBus Queue trigger
- ServiceBus Topic trigger
- Timer Trigger
Azure physical infrastructure
Availability Zones
Region pairs
- Planned Azure updates are rolled out to paired regions one region at a time to minimize downtime and risk of application outage.
Azure management infrastructure
Azure resources and resource groups
- Resource groups are simply groupings of resources.
- When you create a resource, you’re required to place it into a resource group.
- There aren’t hard rules about how you use resource groups, so consider how to set up your resource groups to maximize their usefulness for you
Azure subscriptions
- Billing boundary: This subscription type determines how an Azure account is billed for using Azure. You can create multiple subscriptions for different types of billing requirements. Azure generates separate billing reports and invoices for each subscription so that you can organize and manage costs.
- Access control boundary: Azure applies access-management policies at the subscription level, and you can create separate subscriptions to reflect different organizational structures. An example is that within a business, you have different departments to which you apply distinct Azure subscription policies. This billing model allows you to manage and control access to the resources that users provision with specific subscriptions.
Azure management groups
- You organize subscriptions into containers called management groups and apply governance conditions to the management groups.
- All subscriptions within a management group automatically inherit the conditions applied to the management group,
- the same way that resource groups inherit settings from subscriptions and
- resources inherit from resource groups.
- E.g. You could limit VM locations to the US West Region in a group called Production.
ESXi
Virtual SAN (vSAN)
VMware vSAN ist eine Storage-Virtualisierungssoftware für Unternehmen, die Hyper-Converged Infrastructure (HCI) unterstützt.
VMware vSAN fasst lokale und direkt angeschlossene Datenspeichergeräte in einem VMware vSphere-Cluster zusammen, um einen einzigen Datenspeicher zu erstellen, den alle Hosts in einem vSAN-Cluster gemeinsam nutzen. VMware vSAN ist in den VMware-Hypervisor, ESXi, integriert.
vSphere
Der vCenter Server dient der Verwaltung einer vSphere-Infrastruktur. Er umfasst Funktionen zum Erzeugen, Löschen oder Ändern von virtuellen Data Centern
Network
public / private subnets
Comparison of AWS public / private subnets with Azure: https://devblogs.microsoft.com/premier-developer/differentiating-between-azure-virtual-network-vnet-and-aws-virtual-private-cloud-vpc/
see Default outbound access in Azure https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/default-outbound-access
https://learn.microsoft.com/en-us/azure/load-balancer/load-balancer-overview