Slashdot Mirror
Windows Server 2019 Will Feature Linux and Kubernetes Support (venturebeat.com)
Microsoft announced this week that it will launch the next major release of Windows Server later this year with better support for hybrid workloads, Linux workloads, and hyper-converged infrastructure. From a report: This release will succeed Windows Server 2016, which was made generally available in October 2016. While Microsoft moved to twice-yearly updates for Windows Server starting last year, the company bundles those changes into a long-term servicing channel once every two or three years for administrators who prefer less frequent releases. Those companies that haven't moved over to the semi-annual channel will get their first taste of Windows Server's Linux and Kubernetes support, which are currently in beta.
Lock him up!
In before the first idiot stuck in the 90's starts shouting "Embrace, Extend, Extinguish"
The only problem is that you're still stuck running a big large huge yuuuuuge pile of crap code to support your kubernetes and linux workloads. And you get to pay for the privilege, too. I frankly don't see why I have to pay a tax to this two bit manufacturer for the privilege of less control and a larger attack surface.
Honestly, I can't imagine running a server in 2018 that's not Linux. I would've done this fine on Windows 10 years ago, but there's been so much advancement since then.
What the hell would I want this for?
All my Windows servers -- going back to still-running Windows/NT -- are hosted in a Linux-based hypervisor running as VMs. The older ones used to live on bare-metal and moved to a VM and the new ones have been VMs from the start.
So if I wanted something that Linux provides that Windows does not why wouldn't I just instantiate another Linux VM? All my LAMP, Glassfish, Wikis, mail servers, etc etc are VMs hosted on Ubuntu LTS.
(These days I never put a publicly routable IP address on a hypervisor environment.)
I just don't get why what Microsoft is doing would be useful, other than it sounds awesome to people who don't know what they are doing.
what about uses that RDP / remote apps for windows?
Having just recently installed a windows server for the first time for many years due to some crap software requiring MS SQL, I could never imagine how bad it is, the process management, the resource hogging, man why!!! Why!!!
Why not just run Linux, the better OS, in the first place and when absolutely required (although rarely needed), run Windows Server in a VM?
well then give me linux bonding and bridgeing then
Linux.
Anons need not reply. Questions end with a question mark.
It's strange how servers are getting named Server 20xx while client Windows get names like XP, Vista, 7, 8, 8.1, 10. I just hope Microsoft sees sense and drop 10 and just name it Windows Client 20xx to match the server and Office versions. Meanwhile the command line Windows Server is harder than command line Linux.
Can somebody send some English teachers up to Redmond?
Windows has been able to bond and bridge for ages(More than decade). Bridging works out of the box, bonding will depend on the NIC and whether or not you actually installed the full driver or the base driver from Windows Update.
This Linux shell is great and all but we still need this thing to run our Quake server.
Most people haven't realized how little hardware change there was up until the late Core 2 Duo era.
Basically, until then, you could run any operating system you wanted from a 486 to a late Core 2 Duo unmodified (there were exceptions and cornercases, like some of the cpu specific drivers windows included by default that lacked proper checks and attempted to run on 'newer' cpus after changes were made/bugs were fixed) but generally speaking if you programmed to the 'AT/ATX Clone' standards, your hardware was supported under some form of generic driver, even if a device specific driver wasn't available. Even SATA had IDE fallbacks by default a good decade after it became popular.
Fast forward to today, and even just running 5 year older/newer hardware on a particular iteration of an operating system may be difficult despite almost all hardware following one of the same dozen or so cpu/motherboard combos from one of only two manufacturers. And half the time they have an errata list longer than the errata for the entire 90s generation of chipset manufacturers, despite there having been ~4-6x as many of them.
End stage capitalism is upon us, and the choices are not leading us to a better tomorrow.
no way that dell / hp / others will lockout esxi / linux as the base os. Hell the new core licensing rules make it so that more people don't want to run windows at all.
Bonding depends on drivers? Still? Just works in Linux, regardless of NIC.
bonding and virtual NICs works out of box now as well. It is no longer vendor/driver dependent.
Lookup NIC Teaming. Works great. GUI is a little cumbersome but the powershell for it works great.
During a job interview: "Only morons and policy wonks run containers in Linux on Windows." Those words would leave my lips and the interview would be over. I'd probably fart on the way out the door just to express one last fleeting air of disapproval as I marched proudly out. Trust me, this would happen should I ever encounter it in the future. Embrace, Extend, Head Shot.
Windows the VM. Mozilla the Guest OS. Apps: the internet.
Wanting to âoestandardizeâ on Windows and avoid touching anything else and in that way save money in the IT department.
Worst thing: if it emulates Linux well enough they might be right!
powershell? I like to do my network config in ifcfg files none of the NetworkManager BS
I guess it's your choice to live in the dark ages, then.
All modern linux distros use network managers, it's silly to touch the config files yourself.
powershell is scriptable. much more powerful then dealing with config files that may not apply to different hardware.
Windows as a hypervisor? Maybe for small deployable systems that are all inclusive that also support some internal services.
Storage(linux/Unix) -> Linux(Hypervisor)->Guest Win2016(VMs such as Kubernetes/windows/linux)
Can we get ceph storage support in windows server?