I just deleted 1,372 disks from Google cloud and 7 project spaces.
-
Taggart :donor:replied to Scott Williams 🐧 last edited by
@vwbusguy @Viss @arichtman While the concept of containers is old, I think we can both agree that the "productization" of them is less so.
And as far as scale, I'm referring specifically to choosing a container orchestrator as the deployment target from day one.
-
Scott Williams 🐧replied to Taggart :donor: last edited by [email protected]
@mttaggart @Viss @arichtman Nope - Solaris did it first and *very* commercially.
Solaris ContainersMenu
With Oracle Solaris Containers you can maintain the one-application-per-server deployment model while simultaneously sharing hardware resources.
(www.oracle.com)
-
Taggart :donor:replied to Scott Williams 🐧 last edited by
@vwbusguy @Viss @arichtman Fair enough. To what do you attribute the rise of Docker?
-
@mttaggart @vwbusguy @arichtman im gonna vote 'entirely 100% hype'. because thats what i saw in the infosec space. lots of people with little to no technical accumen suddenly going 500% in on docker and self-labeling themselves experts in it, while at the same time having little to no actual experience at the linux command line
-
Scott Williams 🐧replied to Taggart :donor: last edited by
@mttaggart @Viss @arichtman Ripe timing with the advent of nodejs making stateless applications more mainstream plus complete lack of a coherent business model that meant others managed to productize Docker before Docker itself could figure out how to do it.
-
@Viss @mttaggart @arichtman That's also true. Much in the same way all the junior devs are putting AI on their resume today when their core experience is sticking an OpenAI token into some code they copy and pasted off the internet to make a chat bot.
-
Taggart :donor:replied to Scott Williams 🐧 last edited by
@vwbusguy @Viss @arichtman Node resonates because that is a lot of how I got started using it. But it wasn't just hype. There were real problems of deployability and reproducibility that it solved for Linux admins and developers targeting Linux servers.
I'll cop to missing Solaris on account of being still in school and not being a BSD expert, but when I was running school IT systems, Docker arrived and immediately solved longstanding complications.
-
Taggart :donor:replied to Taggart :donor: last edited by
@vwbusguy @Viss @arichtman And I wasn't alone. I distinctly remember the conversation amongst a lot of working Linux folks at the time being one of excitement and optimism.
-
Scott Williams 🐧replied to Taggart :donor: last edited by
@mttaggart @Viss @arichtman Indeed. In context, Red Hat had bought Qumranet and was competing with Xen, VMWare, and VirtualBox and saying things like you could run 5 VMs on Red Hat for the cost of 3 on VMWare, etc. Hypervisors were a huge deal. OpenStack vs Eucalyptus was the big hype.
On top of that, proprietary PaaS like Heroku was huge.
Docker came along as a way to do VM-like workloads with the overhead of a PaaS in the midst of all of that discussion.
-
Scott Williams 🐧replied to Scott Williams 🐧 last edited by
@mttaggart @Viss @arichtman Docker was way less complicated to deploy than something like Eucalyptus or OpenStack and you could run it on your existing Linux servers instead of a proprietary PaaS or something awkward like Red Hat OpenShift 2 was.
Now you also had a way for a developer to actually ship what "works on my laptop" to the server with more assurances than before.
-
spmatich :blobcoffee:replied to Scott Williams 🐧 last edited by
@vwbusguy I have done a bit of on-prem midrange support in a past life. Oncall is so bad for your health. Are you running openshift on prem? Who is supporting the clusters?
-
Scott Williams 🐧replied to spmatich :blobcoffee: last edited by
@spmatich I did Openshift at my last two employers, but currently using Rancher here, on prem, with paid support. We have a team that supports it in addition to other infrastructure.