<story><title>It&apos;s time to reconsider going on-prem</title><url>http://gravitational.com/blog/time-to-reconsider-going-onprem/</url></story><parent_chain><item><author>chrissnell</author><text>I&amp;#x27;m a huge believer in colocation&amp;#x2F;on-prem in the post-Kubernetes era.  I manage technical operations at a SaaS company and we migrated out of public cloud and into our own private, dedicated gear almost two years ago.  Kubernetes and--especially--CoreOS has been a game changer for us.  Our Kube environment achieves a density that simply isn&amp;#x27;t possible in a public cloud environment with individual app server instances.   We&amp;#x27;re running 150+ service containers on  each 12-core, 512 GB RAM server.  Our Kubernetes farm--six servers configured like this--is barely at 10% capacity and I suspect that we will continue to grow on this gear for quite some time.&lt;p&gt;CoreOS, however, is the real game-changer for us.  The automatic updates and ease of management is what took us from a mess of 400+ ill-maintained OpenStack instances to a beautiful environment where servers automatically update themselves and everything &amp;quot;just works&amp;quot;.  We&amp;#x27;ve built automation around our CoreOS baremetal deployment, our Docker container building (Jenkins + custom Groovy), our monitoring (Datadog-based), and soon, our F5-based hardware load balancing.  I&amp;#x27;m being completely serious when I say that this software has made it fun to be a sysadmin again.  It&amp;#x27;s disposed of the rote, shitty aspects of running infrastructure and replaced it with exciting engineering projects with high ROI, huge efficiency improvements and more satisfying work for the ops engineering team.</text></item></parent_chain><comment><author>tensor</author><text>There is a huge difference between managing your own cloud infrastructure and letting clients run your big SaaS app in their own data centre. I think &amp;quot;on-prem&amp;quot; in the context of SaaS usually refers to the latter.</text></comment>
<story><title>It&apos;s time to reconsider going on-prem</title><url>http://gravitational.com/blog/time-to-reconsider-going-onprem/</url></story><parent_chain><item><author>chrissnell</author><text>I&amp;#x27;m a huge believer in colocation&amp;#x2F;on-prem in the post-Kubernetes era.  I manage technical operations at a SaaS company and we migrated out of public cloud and into our own private, dedicated gear almost two years ago.  Kubernetes and--especially--CoreOS has been a game changer for us.  Our Kube environment achieves a density that simply isn&amp;#x27;t possible in a public cloud environment with individual app server instances.   We&amp;#x27;re running 150+ service containers on  each 12-core, 512 GB RAM server.  Our Kubernetes farm--six servers configured like this--is barely at 10% capacity and I suspect that we will continue to grow on this gear for quite some time.&lt;p&gt;CoreOS, however, is the real game-changer for us.  The automatic updates and ease of management is what took us from a mess of 400+ ill-maintained OpenStack instances to a beautiful environment where servers automatically update themselves and everything &amp;quot;just works&amp;quot;.  We&amp;#x27;ve built automation around our CoreOS baremetal deployment, our Docker container building (Jenkins + custom Groovy), our monitoring (Datadog-based), and soon, our F5-based hardware load balancing.  I&amp;#x27;m being completely serious when I say that this software has made it fun to be a sysadmin again.  It&amp;#x27;s disposed of the rote, shitty aspects of running infrastructure and replaced it with exciting engineering projects with high ROI, huge efficiency improvements and more satisfying work for the ops engineering team.</text></item></parent_chain><comment><author>sillysaurus3</author><text>&lt;i&gt;post-Kubernetes era&lt;/i&gt;&lt;p&gt;Is it?</text></comment>