Introduction to Azure IaaS
Since the dawn of public clouds, vast pools of compute, storage, and networking resources are now available and at the disposal of users who want to leverage them on a pay-as-you-go basis. The ease of implementation and usage becomes one of the key differ
- PDF / 1,107,921 Bytes
- 38 Pages / 439.37 x 666.142 pts Page_size
- 18 Downloads / 224 Views
Introduction to Azure IaaS Since the dawn of public clouds, vast pools of compute, storage, and networking resources are now available and at the disposal of users who want to leverage them on a pay-as-you-go basis. The ease of implementation and usage becomes one of the key differentiators for organizations while they select their preferred cloud service provider. Built on top of reliable Microsoft server and virtualization technologies, Azure accelerates the adoption journey of enterprises, whether they are interested in purely cloud-based environments or in a hybrid setup. Infrastructure as a service (IaaS) is usually the first step for any organization planning to move from legacy on-premise systems to the cloud. Changing from traditional on-premise design standards to the more evolved and complex Microsoft Azure cloud standards can be daunting for infrastructure architects. Design practicality and adherence to stringent design guidelines should be kept in mind. Selecting the right resource types lays the foundation of an IaaS architecture. This chapter helps with building this foundation and introduces the basic components of Azure IaaS.
© Shijimol Ambi Karthikeyan 2018 S. Ambi Karthikeyan, Practical Microsoft Azure IaaS, https://doi.org/10.1007/978-1-4842-3763-2_1
1
Chapter 1
Introduction to Azure IaaS
hat’s New in Azure Resource Manager W (ARM Model) There are two deployment models available in Azure: classic and Azure Resource Manager (ARM). The first one was a monolithic deployment model with little or no flexibility to group together or manage resources in a subscription. It followed a flat structure in terms of identity and access management; the co-admin role provided at the subscription level had full access to all resources. The Azure Resource Manager model (ARM) was introduced in 2014 and brought several enhancements over the classic model. Let’s look at some of the key changes introduced with the ARM architecture.
Resource Groups Resource groups are logical containers used to group resources that share the same lifecycle. Entities that were interdependent or related are now managed as a single unit in terms of deployment, access control, and so forth.
JSON–Based ARM Templates JavaScript Object Notation (JSON)–based ARM templates brought in a new revolution in automation. Multitiered applications and their dependencies are easily deployed using ARM templates. The public ARM repository holds templates contributed by the community, as well as Microsoft product teams, which cover most of the common deployment use cases. If not, users can easily tweak the available templates to meet their requirements.
2
Chapter 1
Introduction to Azure IaaS
Role-Based Access Control Role-based access control (RBAC) replaces the flat identity structure of the classic model. RBAC provides fine-grained access control to resources deployed using ARM. The basic roles are owner, contributor, and reader. The owner role has full access to all resources in the assigned scope; for example, users that are assigned
Data Loading...
