Microsoft is taking containerization one step further by expanding the scenarios and workloads developers can address with containers.
Microsoft will now offer containers with a new level of isolation previously reserved only for fully dedicated physical or virtual machines, while maintaining an agile and efficient experience with full Docker cross-platform integration.
Microsoft could release Windows code. So says Mark Russinovich, one of the most important developers in the company. Russinovich made these statements in ChefConf, a Conference held in Silicon Valley which is mostly attended by Linux users. There, the developer said that we are now facing “a new Microsoft, where an Open Source Windows is possible”.
Russinovich explained this would be an important step for the company evolution, since nowadays most Microsoft’s users and customers rely on Open Source. Therefore, the Redmond giant “also should bet on it”, explained. In addition, he explained that the company already allows Linux in its Azure cloud service and that, in fact, today 20% computers using this service work with the Penguin-OS.
Azure App Service is a one-of-a-kind cloud service which allows developers to easily build employee, partner and customer-facing vApp for any platform or device.
It is an integrated solution that streamlines development while enabling easy integration with on-premises and SaaS systems while providing the ability to quickly automate business processes.
In this post we are going to describe how to deploy a VDI infrastructure with Microsoft Hyper-V and our VDI connection broker for Windows and Linux UDS Enterprise. The process of integrating UDS Enterprise with Microsoft Hyper-V is a simple task since its components are offered in Virtual Appliance format. Through a simple process, the UDS Enterprise components are hosted on the Microsoft Hyper-V platform on which the virtual desktops are going to be deployed. Once the components have been stored, it is necessary to interconnect all of them between each other as well as with the Microsoft Hyper-V virtual platform.
The initial version of Hyper-V only supported one minimal feature for Linux virtual machines (VM) through the installation of an additional component called Linux Integration Services (LIS). But recently, Microsoft has been working with providers to add new features without having to install SIL in newer Linux distributions.
One of the most awaited is the Dynamic Memory. The addition and removal of memory are now fully compatible with virtual machines running on a Windows Server Linux 2012 R2 Hyper-V host. It is important to note that this function is only available for 64-bit Linux distros and in some of them it is necessary to enable support, for example in CentOS and Red Hat Linux distributions.
The information about the Remote PCs project, the differences between ESXi and Hyper-V and virtualization of graphic station environments have been the most interesting topics during the last two weeks according to our followers.
If you didn’t have the chance to read them, you can find the links to these articles below:
Remote PCs with UDS Enterprise & OpenGnSys
