Vagrant for the uninformed: Headless interface to VirtualBox and VMWare VMs on OSX. Instancing is made a breeze.
It isn't specific to osx is it?
It is not! Works on Linux, Mac and Windows.
CoreOS Vagrant Images
21–30 of 46 posts
Re: CoreOS Vagrant Images
#22I don't want to sound overly negative, but attempting to support every useful combination of hardware and drivers, particularly in any kind of supported, certified configuration, ultimately leads back to the same result: just running a real OS.
You can look at CoreOS the same way as the Xen hypervisor and VMWare ESX: the more flexible these became (new hardware drivers, supported configurations, etc. etc) the more they began to look like general purpose operating systems. At which point, why not start with one? (Kvm followed the same logic)
I'd much rather see the guts of CoreOS available as e.g. a RHEL or Debian package. As it stands, throwing away 20 years of distribution experience just to avoid installing a few files on my server seems far from worth it.
Re: CoreOS Vagrant Images
#23Ahh another Gentoo distro. Never ceases to amaze me how people troll it and yet it keeps popping out in every nook and cranny. https://github.com/coreos/coreos-overlay/ Must have been a good idea that no one got.
AFAIK CoreOS is based on ChromeOS which uses some parts from Gentoo. That doesn't mean Gentoo was ever a good idea for general-purpose PCs or servers.
Nice burn on Gentoo. I've had the job of supporting Gentoo on a PaaS and have deployed it many places happily.
Sadly one of the dumbest arguments ever that will blacken the Linux horizon for decades, big dick syndrome over what Linux distro you run.
Re: CoreOS Vagrant Images
#24Simple question, but if there is no package management, how do you install basic programs? Download binaries for everything?
Re: CoreOS Vagrant Images
#25I don't want to sound overly negative, but attempting to support every useful combination of hardware and drivers, particularly in any kind of supported, certified configuration, ultimately leads back to the same result: just running a real OS. You can look at CoreOS the same way as the Xen hypervisor and VMWare ESX: the more flexible these became (new hardware drivers, supported configurations, etc. etc) the more th…
You just described the actual draw of CoreOS. CoreOS is just Linux. Instead of going the Xen route you just described, it can capitalize on being just Linux by supporting everything Linux already supports. At this point, you can view CoreOS, which is just Linux, as the "hypervisor." Containers don't have to replicate key subsystems in every paravirtualized instance, as containers share all the same subsystems like e.g. the TCP/IP stack. You're also not throwing away any distribution experience. Want CentOS? Create a CentOS container with Docker. Want Ubuntu? Create an Ubuntu container with Docker. These are incredibly powerful ideas I'm just now being exposed to.
Re: CoreOS Vagrant Images
#26What's the idea behind CoreOS? I found the site incredibly weak in information about what it is.
Re: CoreOS Vagrant Images
#27Simple question, but if there is no package management, how do you install basic programs? Download binaries for everything?
I believe it's intended to be a minimal OS for running containers like those made by Docker (http://www.docker.io/).
Re: CoreOS Vagrant Images
#28Simple question, but if there is no package management, how do you install basic programs? Download binaries for everything?
Simple answer: you don't. Longer answer: It depends. Do you want to use yum or apt-get to install programs? If you like CentOS, create a CentOS container with Docker and begin installing programs using yum! Ubuntu? Spool up an Ubuntu container and apt-get away! CoreOS is just the cradle upon which you can run the userland of any distribution you please.
Re: CoreOS Vagrant Images
#29I don't want to sound overly negative, but attempting to support every useful combination of hardware and drivers, particularly in any kind of supported, certified configuration, ultimately leads back to the same result: just running a real OS. You can look at CoreOS the same way as the Xen hypervisor and VMWare ESX: the more flexible these became (new hardware drivers, supported configurations, etc. etc) the more th…
[deleted]
Re: CoreOS Vagrant Images
#30I don't want to sound overly negative, but attempting to support every useful combination of hardware and drivers, particularly in any kind of supported, certified configuration, ultimately leads back to the same result: just running a real OS. You can look at CoreOS the same way as the Xen hypervisor and VMWare ESX: the more flexible these became (new hardware drivers, supported configurations, etc. etc) the more th…
You just described the actual draw of CoreOS. CoreOS is just Linux . Instead of going the Xen route you just described, it can capitalize on being just Linux by supporting everything Linux already supports . At this point, you can view CoreOS, which is just Linux , as the "hypervisor." Containers don't have to replicate key subsystems in every paravirtualized instance, as containers share all the same subsystems like…
Try telling your SAN vendor that you're running "just Linux" and can you have a driver and support package for that please, and let us know how you get on.
When you're done there, now try plugging your nice new machine into the corporate DC. Oh it seems it needs to support VLAN tagging. No problem, better just write some new code for that.
Time to migrate a bunch of performance sensitive services. Uh oh, no support for FusionIO PCI SSDs! Better write some more code.
Time to migrate your remote sites, only policy dictates certain services must be physically encrypted. No problem, better just cutpaste Debian's cryptsetup scripts and be done with it.
Oops, turns out we deployed 1000 machines with a duff BIOS setting. No problem, I'm sure the server vendor has a support package for CoreOS..
We could come up with examples until we've basically reinvented a modern Redhat/Debian initramdisk and boot environment.