Windows Azure Pack (WAP): Lifecycle

In recent days there have been important updates about Windows Azure lifecycle Pack (WAP) that will surely please all those who are currently using the solution.

Let me start by saying that Windows Azure Pack is also supported on Windows Server 2016 and then for Service providers you can take advantage of all the features introduced in the new operating system to offer better services to their customers by increasing the level of security. Among the features that may affect especially Service providers are definitely the Shielded Virtual Machines and all the latest news in the field of networking. Soon to be also introduced other important innovations in the Windows Azure Pack, signal that the solution is still evolving.

In this page You can find official references Microsoft about Windows Azure lifecycle Pack, that I carry:

2016_ 11_21_wap-01

Figure 1 – Windows Azure Pack lifecycle

The dates are very different depending on whether the implementation of WAP both Windows Server 2012 R2, or Windows Server 2016. For those who currently use the solution with Windows Server 2012 R2, the advice is to assess rapidly transitioning to Windows Server 2016 and System Center 2016.

As you can see the evolution of WAP in Windows Server environment 2016 will continue to 6 years until 2022 It's going to be a supported solution yet for ben 11 years until 2027.

About this topic is worth noting that Microsoft Azure Stack (MAS) Not is the new version of Windows Azure Pack (WAP). It's completely different solutions. WAP is based on Windows Server and System Center components, While Azure has a Stack architecture inspired by Azure and Azure model Resource Manager. To date is available on the Technical Preview 2 Azure Stack and you will have to wait until next year to be able to use the final version of the solution. Anyone wanting to try out Azure Stack in lab environment can deploy the Technical Preview 2 following article Azure Stack TP2 Deployment. Another important aspect to consider is that WAP can be implemented on different hardware that supports Windows Server 2012 R22016, While Azure Stack must be necessarily implemented on specific supported hardware architectures. Service providers who intend to use hardware already in their possession must then evaluate the Windows Azure ’ adoption Pack.

Conclusions

Windows Azure Pack (WAP) and Microsoft Azure Stack (MAS) are totally different solutions that will coexist for a long time and all this will allow those who currently use Windows Azure Pack to make a smooth transition to Azure Stack. For all Service providers that can wait until next year and that they must invest on ’ purchases of new hardware is recommended to orient the solution Azure Stack.

Leave a Reply

Your email address will not be published. Required fields are marked *