Looks like MS are now saying Server Core is the best option for hosting Hyper-V. So I hope engineering time has not be wasted on trying to make Nano work...
From these changes, customers will now see the Nano Server images shrink in size by more than 50 percent, further decreasing startup times and improving container density. As part of this effort to focus on containers, we will be removing the functionality for infrastructure-related roles. Instead of using Nano Server for these scenarios, we recommend deploying the Server Core installation option, which includes all the roles and features you would need.
Moving forward, Server Core will be the recommended choice for hosting your virtual machines as well as your containers – which can be running a Nano Server container image, a Server Core container image, or even Linux container images.
Server Core is also our recommended option for infrastructure workloads. Many customers don’t realize that Server Core is the base image that runs Azure and Azure Stack.
+1. Q2 is pretty much over now, and no update here for nearly 5 months. What's the deal? I think we all understand that this is a significant upgrade from Microsoft, with lots of intracacies. But at the very least, some form of communication would be nice. I'm confident I'm not the only one with major infrastrucure projects on hold until 2016 is supported by Nutanix, so any form of realistic ETA would be appreciated.
I didnt attend either.. but I have heard/seen that 2016 is all go. GA Aug/Sep. This the session it was all announced:
NUTANIX ENTERPRISE CLOUD WITH HYPER-V AND WINDOWS SERVER 2016Nutanix takes pride in being hypervisor agnostic and continues that tradition with our Windows Server 2016 support for Hyper-V. Hyper-V with Windows Server 2016 has introduced a number of new key features including discrete device assignment, change block tracking and switch embedded teaming to name a few. This session will explore Hyper-V support with Nutanix including the technical details around our integration with Windows Server 2016 and its ecosystem of products. Learn the key differences between Windows Server 2012 R2 and Windows Server 2016 on Nutanix. Obtain best practices and considerations when deploying a Windows Server 2016 based Hyper-V solution with Nutanix. Understand the integration points with the Hyper-V ecosystem of products including the System Center suite and Azure Pack.
The most recent update I got on 5.5 was that it had been delayed. Initial release was supposed to be September, however it has been pushed back. It is "expected before end of the (calendar) year".
Hey folks,
Sorry for the extreme delay. I realize its borderline silly at this point, and on behalf of everyone in engineering (including myself), I appreciate your patience.
Here's the deal. 2016 changed quite a bit for us (which is a net-good thing), and that took us quite a while to adapt in a way that we could uplift our existing 2012 customers to 2016 in an easy manner, and provide a kick butt product for net-new hyper-v installs as well.
I won't rattle off each detail, for the sake of keeping this direct and to the point, but rather simply say we've worked through all of those challenges, and are projecting to launch 2016 support with AOS 5.5.
Given we're a public company, I can't put a forward-looking date on 5.5; however, I will say from the engineering perspective, we've got all hands on deck working on closing down this release, which means final QA and launch prep. We've already got alpha and beta customers on 2016 Hyper-V in the field right now, and have molded their feedback into the product.
In general, and this goes for the *ENTIRE* customer base, if you ever feel you're in the dark on something, please feel free to email me directly jon@nutanix.com from your business emails and I'm happy to chat in detail about what we're up to. For 2016 Hyper-V specific issues, I'm happy to loop in the PM for that feature as well, and we can discuss even more. We pride ourselves on being a pretty open book here at Nutanix, so my "digital door" is always open.
My apologies again that we didn't update this thread with our progress, but I'm hoping this will suffice for the last little bit of waiting we need to do (collectively) before 5.5 launches.
Thats a good question rohanfargade. A lot of the time spent getting Hyper-V 2016 working was what I'd call "structural" work, as we had to both recode an extremely large portion of our Hyper-V support as well as extend the code to work in both directions (to support rolling upgrades and the sort). Quite a large task, and certainly larger than we thought it would be.
Now that the structural work is done, supporting those faster release candidates (knock on wood) should be a heck of a lot easier. Its all for the best though, especially with support for DDA, it greatly simplifies the way we do things, so the overall complexity under the hood has been reduced.
Anyhow, looking to the future, we're already looking at those incremental "fast train" releases. Working on the pre-release 1803 code right now