8 comments

[ 2.2 ms ] story [ 25.4 ms ] thread
Wait till someone comes out with (Orchestration-as-a-Service)-as-a-Service :)
That bootstrapping is pretty sweet, was that something you guys came up with or did you borrow it from somewhere?

(I'm referring to the stuff in https://github.com/cattleio/stampede/tree/master/stampede-wr...)

> On a scale of 1 to 10, we're at 11 in terms of hacks in this file.

Dont be ashamed, it's awesome!

That's something I just came up with. How the containers are setup for the management stack is incredibly complex. The wrapper was created to manage the insanity and hacks. Born out of those hacks was https://github.com/ibuildthecloud/systemd-docker which might be useful to others. It's a wrapper to manage Docker containers under systemd, which is currently quite difficult.
Could someone (OP?) explain what this is in less buzzy terms?
From an end user perspective, you can basically look at it as OpenStack + Kubernetes.
For anyone curious who the author it, it looks like he's a Cloudstack developer at Citrix.

http://www.slideshare.net/DarrenShepherd1/ccceu13-architectu... (see slide #2)

Hi, I'm Darren Shepherd, creator of Stampede. https://www.linkedin.com/in/darrensshepherd I currently work at Citrix with my primary responsibility being an architect of Apache CloudStack. In the past I've deployed clouds based on CloudStack and OpenStack, and written two proprietary IaaS systems from scratch. Stampede is now my third IaaS system I've written from scratch and I'm quite proud that this time it's all open source. For whatever reason, I love infrastructure orchestration and writing these systems is what I've done full time for about the last 5 years.