Microsoft announces Hyper-V Containers
51–60 of 148 posts
Re: Microsoft announces Hyper-V Containers
#52This will be what takes containers into the mainstream businesses. Companies may adopt docker or other instead of this, but Microsoft creating their own version of it means its a viable technology. Im more interested in the new frameworks and technologies that get adopted because of this than the fact that its in use. Traditional Java web projects that are hosted on Tomcat/JBoss don't run well inside containers but t…
Microsoft creating their own version means the technology is viable? I think people have been using 'the technology' for years, without any input from Microsoft. It doesn't need to be anointed by Microsoft to be 'viable'.
Re: Microsoft announces Hyper-V Containers
#53Top it off with SSH access to PowerShell and we're all set? (Something something something dark side)
Re: Microsoft announces Hyper-V Containers
#54Looking forward to hearing more detail about how this works in the near future. I am curious though what are the plans to orchestrate and pull together multiple containers into an application, like Kubernetes, Mesos, CoreOS, etc? Is that coming in the Win 10 timeframe?
Yes, via the Docker-native orchestration tools: Swarm [1] and Compose [2]. [1] https://docs.docker.com/swarm/ [2] https://docs.docker.com/compose/
Re: Microsoft announces Hyper-V Containers
#55Pardon the skepticism, but do "Hyper-V Containers" with "enhanced isolation powered by Hyper-V virtualization" sound suspiciously like, err, Hyper-V virtual machines? And "Server Nano" has a description rather reminiscent of 2008's "Server Core". Is this just about management tools? Because that's cool, too, but why the spin?
It makes sense for their container solution to make use of existing Hyper-V components like the virtual switch etc.
But for that to be possible it's likely they needed to make use of VT-x and VT-d (if using stuff like hardware accelerated network device isolation like SRIOV).
If anything this is closer to Bromium [1] than anything else.
Will be interesting to see if this requires Hyper-V to be running in Type-1 mode (or if this will be the default in upcoming Windows versions) or if they are able to make use of the virtualisation extensions without actually running the host as a Hyper-V partition.
So much cool stuff to hear about at BUILD.
Re: Microsoft announces Hyper-V Containers
#56This will be what takes containers into the mainstream businesses. Companies may adopt docker or other instead of this, but Microsoft creating their own version of it means its a viable technology. Im more interested in the new frameworks and technologies that get adopted because of this than the fact that its in use. Traditional Java web projects that are hosted on Tomcat/JBoss don't run well inside containers but t…
Microsoft creating their own version means the technology is viable? I think people have been using 'the technology' for years, without any input from Microsoft. It doesn't need to be anointed by Microsoft to be 'viable'.
Re: Microsoft announces Hyper-V Containers
#57Earlier quoted context omitted.
Since this is all remote powershell, it would be nice if MS/Windows introduced a native SSH server. That would probably help drive some conversion for people used to the posix world.
While they are at it, they could create a posix compatible layer for Windows. That would really drive some conversion. edit: after rereading my comment and seeing the downvotes, just to clarify, it was a serious, not negative suggestion. :)
Re: Microsoft announces Hyper-V Containers
#58Earlier quoted context omitted.
Thanks for the clarification. I at first assumed they'd bring OS level virtualization, apparently I'm not the only one. But it's basically just minimal images of windows in regular VMs then... A step in the right direction but still disappointing imo. Linux and BSD are still miles ahead.
Microsoft is doing OS-level containers and they are also going to allow running containers in VMs.
edit: http://research.microsoft.com/en-us/projects/drawbridge/ ?
Re: Microsoft announces Hyper-V Containers
#59This will be what takes containers into the mainstream businesses. Companies may adopt docker or other instead of this, but Microsoft creating their own version of it means its a viable technology. Im more interested in the new frameworks and technologies that get adopted because of this than the fact that its in use. Traditional Java web projects that are hosted on Tomcat/JBoss don't run well inside containers but t…
Microsoft creating their own version means the technology is viable? I think people have been using 'the technology' for years, without any input from Microsoft. It doesn't need to be anointed by Microsoft to be 'viable'.
Keep in mind nearly all technologies are used mostly at non-tech companies (e.g. far more software is written by developers not working for a software company) and the software/IT teams at these companies usually prefer solutions from the large/major tech names they know/trust. Microsoft having their own version of something means a lot more businesses will consider using it.
Re: Microsoft announces Hyper-V Containers
#60REALLY looking forward to this. We've needed container style deployments on Windows forever. This is actually going to make my life better...at least this part, anyway.
Imagine what switching to linux could do for you.
> In particular, if the solution begins with "First, install..." you've pretty much lost out of the gate. Solving a five-minute problem by taking a half hour to download and install a program is a net loss. In a corporate environment, adding a program to a deployment is extraordinarily expensive. You have to work with your company's legal team to make sure the licensing terms for the new program are acceptable and do not create undue risk from a legal standpoint. What is your plan of action if the new program stops working, and your company starts losing tens of thousands of dollars a day? You have to do interoperability testing to make sure the new program doesn't conflict with the other programs in the deployment. (In the non-corporate case, you still run the risk that the new program will conflict with one of your existing programs.)
> Second, many of these "solutions" require that you abandon your partial solution so far and rewrite it in the new model. If you've invested years in tweaking a batch file and you just need one more thing to get that new feature working, and somebody says, "Oh, what you need to do is throw away you batch file and start over in this new language," you're unlikely to take up that suggestion.