Windows Management Framework 5 Preview Introduces Package Manager And Network Switches Cmdlets
Microsoft announced the availability of the Windows Management Framework V5 Preview (WMF), which includes Windows PowerShell OneGet, a package manager in the spirit of yum and apt-get; a set of cmdlets to manage network switches; and some polishing on Windows PowerShell Desired State Configuration (DSC).
Windows PowerShell OneGet fills a hole on the Windows platform: a package management solution. It fulfills the same purpose of yum, apt-get and others on the Linux platform. OneGet will support different package repositories, but right now it only supports Chocolatey repositories. Chocolatey is a community-based package management system, built on NuGet infrastructure. It has thousands of available packages, such as Git, NodeJS, 7-Zip and other popular software. Boe Prox authored a detailed how-to describing most of the available OneGet cmdlets.
The new cmdlets for network switches management help with the creation of software defined networks, a growing area of interest in the operations community. There are cmdlets for automating VLANs, ethernet ports, port modes and other L2 layer features. They build upon already available PowerShell CIM cmdlets. The PowerShell-based network switch management is part of a concerted effort to support software defined networks on the Windows platform. This effort is framed by the Microsoft's Datacenter Abstraction Layer (DAL) initiative, which aims to provide a "a common management abstraction for all the resources of a data center", including the definition of standards within the context of the Distributed Management Task Force (DMTF). On pratical terms, this means that only network switches that pass the Certified for Windows program, and follow these standards, can be automated through the network switches cmdlets. Microsoft is collaborating in this process with network switches providers like Arista, Cisco and Huawei.
PowerShell DSC received stability and performance improvements. These improvements complement the release of more than 50 DSC resources since December. According to Jeffrey Snove, who wrote the WMF preview announcement: "If you are considering purchasing a Configuration Management tool, make sure that tool supports DSC or you won’t be aligned with the Windows Server strategy".
Daniel Davidson voiced security concerns, as others did, on the announcement of OneGet and the use of Chocolatey repositories:
I think what bothers me about it is that it asserts a false sense of trust - "the oneget module is core to Powershell, the things I can download must be vetted and safe". Few people feel nervous pulling software from microsoft.com for that reason... Chocolatey isn't Microsoft.com (...)
Jeffrey Snover, from the Windows Server team, replied:
You are correct to be concerned about security of downloading and installing community bits. The reality is that you don't know who is vouching for the bits in the community repository and thus whether they can be trusted or not. That is why when you do a Get-PackageSource, you'll see that we let you declare whether a source is TRUSTED or not. By default, the community repository is not trusted and therefore we will ask you about this when you download software from it.
Jeffrey added that:
So yes - it is a concern and you'll see us doing a lot of work in this space but I have nothing to announce today.
Right now, it [Chocolatey] is very popular but also very informal. What you'll see is that we'll work [with the Chocolatey team] to provide a sliding scale of formality (e.g. opt-in formality) where you'll have a choice between getting very informal software (where there are very few steps required for anyone to publish software) to much more formal software.