The Azure platform SLA applies to virtual machines running the Linux OS only when one of the endorsed distributions is used. All Linux distributions that are provided in the Azure image gallery are endorsed distributions with the required configuration
Azure MarketPlace has a collection of Published, maintained and supported Linux images produced by partners
All images provided on the Azure MarketPlace are curated & tested by Microsoft to ensure that a
Most endorsed distros maintain repos in each Azure region for fast updating
There are selection of imaged available
“Life is already really complicated, so we insist on making it even more complicated.”
The infrastructure for your application is typically made up of many components – maybe a virtual machine, storage account, and virtual network, or a web app, database, database server, and 3rd party services.
You do not see these components as separate entities, instead you see them as related and interdependent parts of a single entity. You want to deploy, manage, and monitor them as a group.
DevOps Deployment Automation - Requires a faster, more flexible deployment approach than the old ASM gateway and powershell could provide – ASM PowerShell can be very complex to define and troubleshoot. https://msdn.microsoft.com/en-us/powershell/dsc/LnxGettingStarted
An Azure Resource Manager template is a JSON formatted document that can be deployed to create a ring-fenced group of resources
Azure Resource Manager provides a new way for you to deploy and manage the services that make up your applications, most, but not all, services support Resource Manager, and some services support Resource Manager only partially. Microsoft will enable Resource Manager for every service that is important for future solutions, but until the support is consistent, you need to know the current status for each service.
•Azure Resource Manager enables you to work with the resources in your solution as a group. You can deploy, update or delete all of the resources for your solution in a single, coordinated operation.
•You can repeatedly deploy your application throughout the app lifecycle and have confidence your resources are deployed in a consistent state.
•You can use declarative templates to define your deployment and you can define the dependencies between resources so they are deployed in the correct order.
•You can apply access control to all resources in your resource group because Role-Based Access Control (RBAC) is natively integrated into the management platform.
•You can apply tags to resources to logically organize all of the resources in your subscription
•When using Resource Groups, limits that once were global become managed at a regional level with the Azure Resource Manager.
•It is important to emphasize that quotas for resources in Azure Resource Groups are per-region accessible by your subscription, and are not per-subscription, as the service management quotas are.
Written in JSON, describes entities
Template execution engine can interpret dependencies and relationships and orchestrate the deployment of the resources for you
Resources at the bottom of the stack are deployed first
Parameterized input and output – reuse template in different environments
Templates are represented in the gallery https://azure.microsoft.com/en-us/resources/templates/
Azure Role-Based Access Control (RBAC) enables fine-grained access management for Azure for example you would only give students contributor access to Azure resources whilist academics and RA would have owner rights.
Azure allows you to utilise RBAC, you can segregate duties within your students projects and teach DevOps, RBAC simply allow you to grant only the amount of access to users that they need to perform their roles and taks which are required .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.