Windows Azure Pack - what kind of animal and what is it with?
All warm greetings from the Lord of Fire!
In this wonderful, sunny and frosty (ooh! - fret-cool!) Day, I really want to tell about something cloudy (trite, isn't it? - smile).
That's just on the topic of cloudiness, I think it's time to talk about such an interesting thing as Windows Azure Pack! It's like WIndows Azure, just like “in your pocket”! Interesting? Then you are welcome to continue reading!
')
Well, let's see, what is it - Windows Azure Pack? Well, firstly, it is completely free and available for download in the open. Secondly, in essence, this is a set of similar technologies of the mechanisms of its older and full-fledged brother - Windows Azure, which is a public cloud from Microsoft. That's just the Azure Pack is built on a private cloud tandem - Windows Server 2012 R2 and System Center 2012 R2 . The add-in allows you to get an interface that looks virtually no different from Windows Azure, realizing the possibilities of self-service, multi-tenancy (or multi-visibility, if you please) at different levels of service provision - both at the IaaS level and at the PaaS level.
If you go into the details, then this is essentially a set of web portals that use the REST API and the SPF (Service Provider Foundation) layer as its implements to manage various infrastructure elements: System Center components, in particular VMM, SQL or MySQL databases, web -IIS sites (essentially at the PaaS level) - this is an example. If you fully list the functionality, you get the following picture, described below.
Here is the complete list of services provided through Windows Azure Pack today.
1) Management portal for administrators - in fact, the interface through which all the configuration of services that can be provided through Windows Azure Pack is made. In particular, this portal creates and manages private resources from VMM (or public cloud - depending on who the end user is), user accounts - in essence, the role of Tenant Administrator is created in the same VMM, service plans (a plan is a set of services that You can build and present to the user through creating a subscription), set quotas for consumed resources, and also establish billing mechanisms for consumed resources at the expense of third-party components, such as Cloud Cruiser.
This is what a created user and a subscription to Windows Azure Pack associated with it from the point of view of VMM looks like.
2) A management portal for users is essentially an interface for end-user consumption of services — for example, the task of deploying, monitoring, and managing web sites, virtual machines, or service buses can be implemented through this portal.
3) Service management API is essentially a REST API that allows you to integrate Windows Azure portals with third-party solutions, such as billing systems. Also, this mechanism allows you to transfer the functionality of Windows Azure to customized, own web portals (read - interfaces). Here the main thing to understand is that you can fully realize all the functionality of Windows Azure Pack on the portal that apparently has nothing in common with it even without it - long live freedom of choice and competitive advantage!
4) Virtual machines - in fact, this is the IaaS level in the provision of virtual machines for both Windows and Linux. This portal includes the possibility of creating a gallery of images of VM, similar to its adult brother, as well as the settings of virtual networks and the scaling area of the deployed components.
5) Service Bus (Service Bus) - a service that provides a reliable messaging and data system between distributed applications. This mechanism operates on a subscription to messages based on requests or topics of publications or subscriptions.
6) SQL and MySQL - in fact, it is a service at the PaaS level to provide database instances on the specified platforms, used in conjunction with websites, as a rule. Here it is important to understand that SQL can be deployed at the IaaS level, i.e. get a virtual machine with a DBMS, but in this case it is fashionable to say that access is given to a specific database instance with a quota for its size, in other words, a VM with SQL can have many different isolated users at the PaaS level, which do not have access to the VM itself , only to the DBMS, and even then - only to its own instance of the database.
An example of connecting SQL DBMS at the PaaS level in Windows Azure Pack.
7) Automation and advanced features - in fact, the portal for creating custom, individual services and their inclusion in the user. You can, for example, create runbooks to automate workflows and business processes, as well as execute them.
Probably one of the easiest to install products of all, with whom I had to work.
You need to run our Web Installer on the machine where you plan to deploy the Azure Pack. First I recommend using the express method - this is when all the roles and components of the Azure Pack are deployed on a single server based on Windows Server 2012/2012 R2.
That's actually a link to the installer . Then simply select all the components and click on Next-> Next-> Next>))))).
This is what the Windows Azure Pack installer looks like.
Just in case - a list of prerequisites for installation:
• Windows Server 2012 or Windows Server 2012 R2
• Microsoft Web Platform Installer 4.6
• Microsoft .NET Framework 3.5 Service Pack (SP) 1
• Internet Information Services (IIS) 8 or IIS 8.5
• .NET Framework 4.5 Extended, with ASP.NET Windows 8
In terms of equipment requirements, the picture is as follows:
• 8 GB of RAM. If you are running inside the VM, it is strongly recommended NOT to use dynamic memory.
• 40 GB of storage space.
Since Windows Azure Pack is a web portal, some ports will need access by default, and you will need to open them on your firewall:
Admin API (Admin Functions API)
30004
Management portal for administrators (Management portal for administrators)
30091
Authentication site
30071
Configuraton site (Site configuration and configuration)
30101 - Local Subnet
Monitoring
30020
MySQL resource provider (MySQL DBMS connection provider)
30012
SQL Server or MySQL resource provider (SQL or MySQL DBMS connection provider)
30010
Tenant API (API for working with user functions - internal)
30005
Tenant public API (API for working with user-defined functions - public)
30006
Management portal for tenants (Management Portal for users)
30081
Usage (Service Portal)
30022
WebAppGallery (Web Application Gallery)
30018
Windows authentication site
30072
Something like this is a common story with WAP (Windows Azure Pack) - I naturally urge to try it yourself, deploy and configure it yourself - and then play with the services and its functions - an extremely interesting activity is coming out in practice! Successful to you experiments!
Ever-inexorable and hot pepper,
Fireman
George A. Gadzhiev.
In this wonderful, sunny and frosty (ooh! - fret-cool!) Day, I really want to tell about something cloudy (trite, isn't it? - smile).
That's just on the topic of cloudiness, I think it's time to talk about such an interesting thing as Windows Azure Pack! It's like WIndows Azure, just like “in your pocket”! Interesting? Then you are welcome to continue reading!
')
What a miracle, what a wonderful beast?
Well, let's see, what is it - Windows Azure Pack? Well, firstly, it is completely free and available for download in the open. Secondly, in essence, this is a set of similar technologies of the mechanisms of its older and full-fledged brother - Windows Azure, which is a public cloud from Microsoft. That's just the Azure Pack is built on a private cloud tandem - Windows Server 2012 R2 and System Center 2012 R2 . The add-in allows you to get an interface that looks virtually no different from Windows Azure, realizing the possibilities of self-service, multi-tenancy (or multi-visibility, if you please) at different levels of service provision - both at the IaaS level and at the PaaS level.
If you go into the details, then this is essentially a set of web portals that use the REST API and the SPF (Service Provider Foundation) layer as its implements to manage various infrastructure elements: System Center components, in particular VMM, SQL or MySQL databases, web -IIS sites (essentially at the PaaS level) - this is an example. If you fully list the functionality, you get the following picture, described below.
Here is the complete list of services provided through Windows Azure Pack today.
1) Management portal for administrators - in fact, the interface through which all the configuration of services that can be provided through Windows Azure Pack is made. In particular, this portal creates and manages private resources from VMM (or public cloud - depending on who the end user is), user accounts - in essence, the role of Tenant Administrator is created in the same VMM, service plans (a plan is a set of services that You can build and present to the user through creating a subscription), set quotas for consumed resources, and also establish billing mechanisms for consumed resources at the expense of third-party components, such as Cloud Cruiser.
This is what a created user and a subscription to Windows Azure Pack associated with it from the point of view of VMM looks like.
2) A management portal for users is essentially an interface for end-user consumption of services — for example, the task of deploying, monitoring, and managing web sites, virtual machines, or service buses can be implemented through this portal.
3) Service management API is essentially a REST API that allows you to integrate Windows Azure portals with third-party solutions, such as billing systems. Also, this mechanism allows you to transfer the functionality of Windows Azure to customized, own web portals (read - interfaces). Here the main thing to understand is that you can fully realize all the functionality of Windows Azure Pack on the portal that apparently has nothing in common with it even without it - long live freedom of choice and competitive advantage!
4) Virtual machines - in fact, this is the IaaS level in the provision of virtual machines for both Windows and Linux. This portal includes the possibility of creating a gallery of images of VM, similar to its adult brother, as well as the settings of virtual networks and the scaling area of the deployed components.
5) Service Bus (Service Bus) - a service that provides a reliable messaging and data system between distributed applications. This mechanism operates on a subscription to messages based on requests or topics of publications or subscriptions.
6) SQL and MySQL - in fact, it is a service at the PaaS level to provide database instances on the specified platforms, used in conjunction with websites, as a rule. Here it is important to understand that SQL can be deployed at the IaaS level, i.e. get a virtual machine with a DBMS, but in this case it is fashionable to say that access is given to a specific database instance with a quota for its size, in other words, a VM with SQL can have many different isolated users at the PaaS level, which do not have access to the VM itself , only to the DBMS, and even then - only to its own instance of the database.
An example of connecting SQL DBMS at the PaaS level in Windows Azure Pack.
7) Automation and advanced features - in fact, the portal for creating custom, individual services and their inclusion in the user. You can, for example, create runbooks to automate workflows and business processes, as well as execute them.
Where to get and how to deliver?
Probably one of the easiest to install products of all, with whom I had to work.
You need to run our Web Installer on the machine where you plan to deploy the Azure Pack. First I recommend using the express method - this is when all the roles and components of the Azure Pack are deployed on a single server based on Windows Server 2012/2012 R2.
That's actually a link to the installer . Then simply select all the components and click on Next-> Next-> Next>))))).
This is what the Windows Azure Pack installer looks like.
Just in case - a list of prerequisites for installation:
• Windows Server 2012 or Windows Server 2012 R2
• Microsoft Web Platform Installer 4.6
• Microsoft .NET Framework 3.5 Service Pack (SP) 1
• Internet Information Services (IIS) 8 or IIS 8.5
• .NET Framework 4.5 Extended, with ASP.NET Windows 8
In terms of equipment requirements, the picture is as follows:
• 8 GB of RAM. If you are running inside the VM, it is strongly recommended NOT to use dynamic memory.
• 40 GB of storage space.
Since Windows Azure Pack is a web portal, some ports will need access by default, and you will need to open them on your firewall:
Admin API (Admin Functions API)
30004
Management portal for administrators (Management portal for administrators)
30091
Authentication site
30071
Configuraton site (Site configuration and configuration)
30101 - Local Subnet
Monitoring
30020
MySQL resource provider (MySQL DBMS connection provider)
30012
SQL Server or MySQL resource provider (SQL or MySQL DBMS connection provider)
30010
Tenant API (API for working with user functions - internal)
30005
Tenant public API (API for working with user-defined functions - public)
30006
Management portal for tenants (Management Portal for users)
30081
Usage (Service Portal)
30022
WebAppGallery (Web Application Gallery)
30018
Windows authentication site
30072
Something like this is a common story with WAP (Windows Azure Pack) - I naturally urge to try it yourself, deploy and configure it yourself - and then play with the services and its functions - an extremely interesting activity is coming out in practice! Successful to you experiments!
Ever-inexorable and hot pepper,
Fireman
George A. Gadzhiev.
Source: https://habr.com/ru/post/209918/
All Articles