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.
Linux is Embracing, Extending, and Extinguishing Windows!
If you are going with Windows Server, chances are you need Windows Server as the primary OS, because it is primary running a Windows Service (Say SQL Server for Application compatibility). But there are some things you may need Linux for and would prefer the Linux port over the windows port, say some sort of LAMP stack... Just as a secondary low resource web front end. So why bother setting up two computers when one will be good enough.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
If you are going with Windows Server, chances are you need Windows Server as the primary OS, because it is primary running a Windows Service (Say SQL Server for Application compatibility). But there are some things you may need Linux for and would prefer the Linux port over the windows port, say some sort of LAMP stack... Just as a secondary low resource web front end. So why bother setting up two computers when one will be good enough.
If only there was some way to run multiple operating systems on the same hardware. /s
You get less overhead this way, industry is going full circle again, int he end everything will be solaris zones
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.
like some sort of virtual hardware implementation? intriguing...
what about uses that RDP / remote apps for windows?
So why bother setting up two computers when one will be good enough.
Well, if the Windows one is a VM (and mostly probably it will be) it makes much more sense to create other VM just for Linux. Plus, the concept of depending on Windows to run a Linux server just plain blows the mind of any sensible sysadmin. It makes as much sense as depending on your pre-teen boy to drive you to the hospital because you are too ill to drive.
You dont do much actual work then, more recompliing the kernel just to change directory...
Honestly, I can't imagine running a server in 2018 that's not Windows. I did this fine on Windows ten years ago, yet there's been so much advancement since then.
I can't imagine running a server, who manages at that level? Give me just let me host my containers or hell manage the container for me and just run my code. No reason to waste my time doing silly things like patching host operating systems.
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.
I don't really care about the OS these days, I use what is best for the workload at hand. Having the option of Linux can't hurt, especially how Kubernates is a "make or break" product in a lot of newer shops.
Of course, a lot of shops are best using Linux, and shoehorning Windows only adds another layer. However, there are shops that have a significant Windows investment, in both licenses and skills, where having Linux on Windows may be their best solution.
There are some things which only Windows can do, and are needed. AD for example. However, there are some applications which only run on Linux (or UNIXes like macOS) and are nice to have, like Borg Backup, which does a great job for deduplicating and encrypting content.
What you want is to run your Windows Server on a VM and use that to emulate Linux and then launch containers inside the emulated Linux. Naturally, inside the containers you run your software inside virtual machine models such as the JVM. If you don't have at least four layers of 'virtual' between you and your hardware you're not trying hard enough.
Maw! Fire up the karma burner!
If you are going with Windows Server, chances are you need Windows Server as the primary OS, because it is primary running a Windows Service (Say SQL Server for Application compatibility).
Or you can run SQL Server for Linux.
You are the idiot Monkeyshit Corp shill stuck in the 90's.
If M$ does it, it must be bad! Therefore, no one should use Linux servers.
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.
Where do you host your containers?
APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
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.
Solaris zones? Kids! IBM mainframes has an os called VM in the late 70s - guess what VM stood for?
Ken
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.
AWS fargate, lambda (if I'm not even interested in managing the container), etc.
Vaporware Machine?
Okay, so, the answer to my question is really "other peoples' servers", which makes the answer to your question "the people who run the servers you host your containers on."
Did you honestly think all of that happened without servers?
APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
Solaris zones? Kids! IBM mainframes has an os called VM in the late 70s - guess what VM stood for?
Vi iMproved? Kids these days don't even know that emacs is an OS as well;)
-- Political fascism requires a Fuhrer.
I get that, my point is given the option (unless the poster here works for a cloud provider) why the hell would you bother running and managing your own servers? Next you will tell me that serverless apps still have servers behind it.
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.
Oh, let me think...
A) Applications do exist that require performance you can only get from bare metal
B) Fields do exist that require that you don't put certain data in the hands of a 3rd party (think medical and legal, just for starters)
C) It's not uncommon for a business to wish to continue operations when their internet connection is down.
D) As your container host provider, I can see all of your dirty little secrets. That new service you're trying to bring to market with a team of 5? The one that's 50% done? The one you've handed me all of the current source code to? I've got a team of 50 working on getting it to market a year ahead of you and a big enough war chest to bankrupt you if you sue. Aren't you glad you used containers?
Need I continue?
APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
Oh and yes, since you really wanted me to say it... Serverless app do still have servers behind them.
APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
Windows the VM. Mozilla the Guest OS. Apps: the internet.
Did you honestly think all of that happened without servers?
Its containers all the way down.
Have gnu, will travel.
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!
If that is the case then you should start to use Visual Source Safe.
That's a valid exit strategy for Microsoft if they decided the OS business wasn't profitable in the future.
What if the "server" runs on a P2P network of clients?
I dunno about ad being something only windows can do... Checkout FreeIPA.. It not 100% 1to1 on features, but its close
powershell? I like to do my network config in ifcfg files none of the NetworkManager BS
Then they're lots of little servers.
"Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
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)
What the hell is a Kubernates?
Is it a modern version of a Nazi?
Thank you for that. I had never heard of FreeIPA. I will be checking it out. I have been utilizing Linux where it makes sense to in our "Windows Only" shop. From the demo it does appear to be pretty comprehensive, but simple enough for our Windows admins to understand.
Can we get ceph storage support in windows server?
SQL Server stopped being a good example last year. That's running on Linux now. :)
Federate FreeIPA it as a subdomain of AD. When you get seamless AD logins but the ability to control HBAC and sudo policies via FreeIPA. Totally amazing combo.
As a hardware vendor, I whole heartedly agree. Just make sure to buy the top of the line CPU not the one that only bursts to 98% as much performance for half the price. That's a sucker's bet.
Remember, the more expensive your hardware, the smaller the percentage of the budget your salary represents.