Skip to main content

OpenStack in terms of CoreOS

CoreOS is meant to be immutable so attaching to running things from the host directly is a bit of a challenge and possibly just wrong. But as I look at OpenStack, CoreOS, Unikernels and the other moving parts I'm curious to know if there is a complete and reasonable analog to OpenStack in terms of CoreOS (other Linux variations later).
  • OpenStack Cinder - Storage. 
There are plenty of Linux storage solutions for CoreOS. If you are not mounting an NFS file system from the core then you're probably creating a DataContainer and attaching to a NAS or SAN. Additionally there are some docs suggesting that ZFS can be attached using Flocker.
  • OpenStack Nova - Command Line
Currently there is no aggregated CLI or GUI for all of the CoreOS features but the same can be said for OpenStack. Nova is but one part of the equation. CoreOS performs that function mainly with the fleet list-machines command.
  • OpenStack KeyStone - Identity Server
There are a number of identity solutions for CoreOS, however, it's not actually a CoreOS function but Docker. There are OAuth and OpenID servers that can be loaded as containers.
  • OpenStack Glance - Image Server
Docker and CoreOS provide on premise enterprise registry servers.
  • OpenStack Neutron - Networking
Docker has built-in isolation and tunneling. When you get into ambassador and sidekick helpers or into schedulers like kubernetes, Deis it's all pretty similar.
  • OpenStack Swift - Object Storage
This could be implemented in any 3rd party data or in ectd.
  • OpenStack Heat - Orchestration
CoreOS has been working on Fleet as a way to schedule containers and tasks. If that's not enough any of the scheduling frameworks are sufficient; even fig.
  • OpenStack Cellometer - Telemetry
I might have to give this one to OpenStack. CoreOS has some tools that will capture system data as part of the enterprise setup. There are even some tools that will install and monitor the system... like DataDog. But things may not be the same as DTrace on SmartOS.
  • OpenStack Trove - Database Service
This is already addressed and from the OpenStack side of things is just a database or DB proxy. It does not appear to be a level up from the existing container based DBs. A handful of Postgres DBs or Mongo DBs would get you into the same place. 
  • OpenStack Sahara - Data processing command line
Just another Hadoop.
  • OpenStack Openstack - Command Line
I'm running out of steam... between the apparent duplicate projects (database and command line) and. While CoreOS + Docker + Fleet + LockSmith + Etc + Systemd + and anything else I've forgotten OpenStack does not take me someplace special. Yes, CoreOS will run in an OpenStack or QEMU environment but (a) once you have more than one OS running on the bare metal you start to lose some scale and (b) And it will effect the density benefits of a Docker plus CoreOS on bare metal. Yes, Docker will run in OpenStack too. It might even support many of the frameworks and tools identified here... however that's just a wrapper inside a wrapper. (consider running docker on windows. There's at least one addition virtualization layer between the container and the bare metal.)

One of the missing pieces from the conversation is composition. CoreOS gets that either by implementing your own tools, scripts, sidekicks, or ambassadors or by deploying under a container framework like Kubernetes, Deis, or my favorite Apcera.

In Conclusion, CoreOS is analogous to OpenStack and although it has choices in how you achieve the integration it still has the power to compete in the same space. Because the tools are supposed to be containerized you're going to get some scale and loose coupling that you're not going to get from OpenStack. If it were my money I'd be spending it on CoreOS.

Comments

Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: http://www.eeti.com.tw/drivers_Linux.html (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the setup.sh answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…