Microsoft Azure Stack TP1
As some of you already know, a trial version of the Microsoft Azure Stack TP1 product was released on January 29th.
You can download it here , the documentation is here .
I will try to tell you more about this product.
Microsoft Azure Stack (hereinafter referred to as MAS) is a platform for creating a hybrid cloud. You can use the resources of your data center and / or - integrate MAS with Microsoft Azure services (hereinafter referred to as Azure) and \ or other Microsoft partner service providers, thus gaining access to the “unlimited” resources of public clouds and utilizing the resources of your data center.
')
You can use such services as Virtual Machines (hereinafter referred to as VM), Virtual Networks and blob / table storage and others. Provide end users with services on your terms with the familiar (well, almost) Azure interface for them.
Your apps created for Azure will work on MAS too. For development for the Azure platform and MAS, the Azure SDK is used. You get access to Azure Application Templates, Role Based Access Control, Azure Active Directory, Azure API. In addition, you can use open source solutions such as: Linux, Java, Node.js, and PHP.
I think enough water, on the Internet you can find a lot of marketing materials for this product.
The TP1 deployment architecture of MAS.
1. ADVM - VMs with Active Directory, DNS and DHCP roles for Microsoft Azure Stack.
2. ACSVM — VMs with the role of Azure Consistent Storage services. These services use Service Fabric.
3. MuxVM - VM with the role of Microsoft software load balancer and network multiplexing service.
4. NCVM — VMs with the role of the Microsoft network controller component, a key component of Microsoft software-denied networking. This services uses Service Fabric.
5. NATVM - VM with the role of Microsoft network address translation. Allows you to provide Internet components of the Azure Stack.
6. xRPVM - VMs with key roles of Microsoft Azure Stack (Compute, Network and Storage Providers).
7. SQLVM - VM with SQL role, which is used by ACS and xRP services.
8. PortalVM - VM with the role of Control Plane (Azure Resource Manager), Azure portal services and other portals.
9. ClientVM - development VM (PowerShell, Visual Studio, etc.).
Storage Subsystem:
CS Blob Service Azure Consistent Storage Blob service allows you to create blob and table data storage services.
SoFS Scale-out File Server. ReFS CSV Resilient File System Cluster Shared Volume. Virtual Disk, Storage Space and Storage Spaces Direct Windows Server Technology for Microsoft Azure Stack Core Storage. (Pts wanted to be translated as “storage core” ... did not)
Expanding on 1 node, list of requirements , possible deployment on VM (Nested Virtualization), but, of course, not supported.
Services, subscriptions, plans, offers.
1. Services - well, everything is clear, SQL, Sharepoint, VM, etc.
2. Plans - groups of services, you create plans and your tenants subscribe to plans and use the services that are located in the plans. You can set quotas for services (number of VMs, RAM, cores, etc.). Quotas may depend on the region of the tenant. There are basic plans and additional plans, basic plans are always included in the offer, additional ones can be purchased at will. For example, an additional plan may include the same as the base plan, but with a different quota.
3. Suggestions - a group of plans. Tenants "buy" offers.
4. Subscriptions - Created when a tenant purchases an offer. A subscription can contain only 1 plan. Subscription determines access to plans / services.
Azure Resource Manager
The way to work with resources by combining them into logical groups, for example, a virtual machine consists of several resources, the network \ data \ VM. To simplify the administration of resources, to simplify the management of the life cycles of resources, to distribute rights to resources, to create, etc. Resource Groups are used (hereinafter RG).
The main advantages of Azure Resource Manager:
1. You can manage all resources in the RG as a group, not individually.
2. The first, second, tenth creation of a resource from a template will lead to the same result.
3. You can specify dependencies in resource templates to create them correctly.
4. You can issue rights to the RG and they will be applied to all resources in the RG.
5. You can use tags for logical organization of resources.
6. You can view the account details by a specific RG or by tag.
Resource Group
Logical container for grouping resources. It may contain both all deployment resources and only a fraction of the resources.
1. All resources in one RG should have the same life cycle, since you will manage them as a single entity.
2. Each resource can exist only in one RG.
3. Resource can be added to RG or deleted at any time.
4. May contain resources from different regions.
5. Used to assign roles.
6. A resource can be associated with a resource from another RG (for example, a web server in one RG, a database in another)
Azure Resource Manager Templates
Templates for deploying applications \ services. Created in JSON format. They use a declarative approach, allow them to deploy resource groups, track dependencies, support parameters and variables. Templates can be used for deployments in Azure and / or MAS. Thus, by creating a template and testing it in your data center, you can transfer it to Azure without any problems (and vice versa).
All this is absolutely consistent with Microsoft Azure, i.e. This is true for both the Microsoft Azure Stack and Microsoft Azure.
Main providers:
1. Compute - needed to create a VM. Allows you to install VM extensions, to facilitate VM management
2. Storage - allows you to create blob, table and account services. Blobs are necessary for storing information, blobs are block, page and append, the first is used for files and backups, the second for vhd, the third for logging. Table services are Microsoft's NoSQL implementation, this solution has no schems. To identify each entry, use the partition key and row key, which uniquely identify the entry in the table.
3. Network - provides services of software-defined networking and Network Function Virtualization. As Microsoft promised, this provider migrated from Azure. Allows you to create load balancers, public IP addresses, network security groups, etc.
I think enough for the first time, if there is a demand, I will write more!
If you have any questions, please contact us!
You can download it here , the documentation is here .
I will try to tell you more about this product.
Microsoft Azure Stack (hereinafter referred to as MAS) is a platform for creating a hybrid cloud. You can use the resources of your data center and / or - integrate MAS with Microsoft Azure services (hereinafter referred to as Azure) and \ or other Microsoft partner service providers, thus gaining access to the “unlimited” resources of public clouds and utilizing the resources of your data center.
')
You can use such services as Virtual Machines (hereinafter referred to as VM), Virtual Networks and blob / table storage and others. Provide end users with services on your terms with the familiar (well, almost) Azure interface for them.
Your apps created for Azure will work on MAS too. For development for the Azure platform and MAS, the Azure SDK is used. You get access to Azure Application Templates, Role Based Access Control, Azure Active Directory, Azure API. In addition, you can use open source solutions such as: Linux, Java, Node.js, and PHP.
I think enough water, on the Internet you can find a lot of marketing materials for this product.
The TP1 deployment architecture of MAS.
1. ADVM - VMs with Active Directory, DNS and DHCP roles for Microsoft Azure Stack.
2. ACSVM — VMs with the role of Azure Consistent Storage services. These services use Service Fabric.
3. MuxVM - VM with the role of Microsoft software load balancer and network multiplexing service.
4. NCVM — VMs with the role of the Microsoft network controller component, a key component of Microsoft software-denied networking. This services uses Service Fabric.
5. NATVM - VM with the role of Microsoft network address translation. Allows you to provide Internet components of the Azure Stack.
6. xRPVM - VMs with key roles of Microsoft Azure Stack (Compute, Network and Storage Providers).
7. SQLVM - VM with SQL role, which is used by ACS and xRP services.
8. PortalVM - VM with the role of Control Plane (Azure Resource Manager), Azure portal services and other portals.
9. ClientVM - development VM (PowerShell, Visual Studio, etc.).
Storage Subsystem:
CS Blob Service Azure Consistent Storage Blob service allows you to create blob and table data storage services.
SoFS Scale-out File Server. ReFS CSV Resilient File System Cluster Shared Volume. Virtual Disk, Storage Space and Storage Spaces Direct Windows Server Technology for Microsoft Azure Stack Core Storage. (Pts wanted to be translated as “storage core” ... did not)
Expanding on 1 node, list of requirements , possible deployment on VM (Nested Virtualization), but, of course, not supported.
Services, subscriptions, plans, offers.
1. Services - well, everything is clear, SQL, Sharepoint, VM, etc.
2. Plans - groups of services, you create plans and your tenants subscribe to plans and use the services that are located in the plans. You can set quotas for services (number of VMs, RAM, cores, etc.). Quotas may depend on the region of the tenant. There are basic plans and additional plans, basic plans are always included in the offer, additional ones can be purchased at will. For example, an additional plan may include the same as the base plan, but with a different quota.
3. Suggestions - a group of plans. Tenants "buy" offers.
4. Subscriptions - Created when a tenant purchases an offer. A subscription can contain only 1 plan. Subscription determines access to plans / services.
Azure Resource Manager
The way to work with resources by combining them into logical groups, for example, a virtual machine consists of several resources, the network \ data \ VM. To simplify the administration of resources, to simplify the management of the life cycles of resources, to distribute rights to resources, to create, etc. Resource Groups are used (hereinafter RG).
The main advantages of Azure Resource Manager:
1. You can manage all resources in the RG as a group, not individually.
2. The first, second, tenth creation of a resource from a template will lead to the same result.
3. You can specify dependencies in resource templates to create them correctly.
4. You can issue rights to the RG and they will be applied to all resources in the RG.
5. You can use tags for logical organization of resources.
6. You can view the account details by a specific RG or by tag.
Resource Group
Logical container for grouping resources. It may contain both all deployment resources and only a fraction of the resources.
1. All resources in one RG should have the same life cycle, since you will manage them as a single entity.
2. Each resource can exist only in one RG.
3. Resource can be added to RG or deleted at any time.
4. May contain resources from different regions.
5. Used to assign roles.
6. A resource can be associated with a resource from another RG (for example, a web server in one RG, a database in another)
Azure Resource Manager Templates
Templates for deploying applications \ services. Created in JSON format. They use a declarative approach, allow them to deploy resource groups, track dependencies, support parameters and variables. Templates can be used for deployments in Azure and / or MAS. Thus, by creating a template and testing it in your data center, you can transfer it to Azure without any problems (and vice versa).
All this is absolutely consistent with Microsoft Azure, i.e. This is true for both the Microsoft Azure Stack and Microsoft Azure.
Main providers:
1. Compute - needed to create a VM. Allows you to install VM extensions, to facilitate VM management
2. Storage - allows you to create blob, table and account services. Blobs are necessary for storing information, blobs are block, page and append, the first is used for files and backups, the second for vhd, the third for logging. Table services are Microsoft's NoSQL implementation, this solution has no schems. To identify each entry, use the partition key and row key, which uniquely identify the entry in the table.
3. Network - provides services of software-defined networking and Network Function Virtualization. As Microsoft promised, this provider migrated from Azure. Allows you to create load balancers, public IP addresses, network security groups, etc.
I think enough for the first time, if there is a demand, I will write more!
If you have any questions, please contact us!
Source: https://habr.com/ru/post/276341/
All Articles