4 ms·
The full quote is: > People started doing silly things like run containers on top of their cloud providers VMs (creating a second layer of isolation and massiv
by nailer 7y ago
The full quote is:
> People started doing silly things like run containers on top of their cloud providers VMs (creating a second layer of isolation and massive amounts of engineering burden)
Regarding your statement:
> When you need more instances of a service running you replicate a container instance, and if a container instance is idling then you shut it down.
> monitoring resources and managing how container and VM instances are initialized or shut down
You're confusing orchestration with isolation. Orchestration has existed far before containers. You are already paying your cloud provider for isolation.
Containers are not needed for orchestration. I'm going to take a guess here and say you have been in the tech industry for about five years.
And regarding your claim:
> You never have to worry about anything because it just works.
No. Running a Kubernetes or Docker cluster is a non trivial task.
Here's a more likely scenario for running your own container farm on top of the platform your employer already pays for from your cloud provider: you just want to learn Kubernetes and have someone else pay you to do it, despite the lack of business benefit.
- rumanator 7y ago> People started doing silly things like run containers on top of their cloud providers VMs (creating a second layer or isolation and massive amounts of engineering burden) I've addressed the full quote, and it's entirely wrong and made by someone who clearly has no practical experience running containerized apps. If you read my comment you'll check the points that address that misconception. > No. Running a Kubernetes or Docker cluster is a non trivial task. Kubernetes is not containers. It's a container orchestration service. That's an entirely different thing. It's like you are confounding application installers with the OS that runs the application. And it seems you also confused Docker Swarm, Docker's container orchestration system, with Docker. Those are two entirely different things. And container orchestration services are not a problem. If you ever get the opportunity to learn about containers and container orchestration services, you'll see that Docker Swarm is trivial to use even in bare VMs or even directly in dedicated hardware, once you get the ingress controller thing sorted out. In cloud providers it's even much simpler because ingress controllers are already provided out of the box and you have nifty UIs to configure everything. And by the way, I appreciate if you stop rewriting your points midquote and after you get replies addressing the points you rewrite, because you're misrepresenting everything you and I am saying with each edit.
- nailer 7y agoI wrote a comment then spent a minute editing it, because I am in bed on a phone. Shrug Here's a shorter version of the entire conversation, quoting you: > By firing up a VM you're actually allocating in the cloud the computational resources you need, and by running containers you are using those computational resources as you need. When you need more instances of a service running you replicate a container instance, and if a container instance is idling then you shut it down. You're confusing isolatation with orchestration. You haven't been in the tech industry a long time. You do not need containers for orchestration. You do not need containers for isolation if you are already paying for VMs.
- deleted 7y ago[deleted]
- scarface74 7y agoContainers are not needed for orchestration. See HashiCorp’s Nomad....
- nailer 7y agoIndeed. Or anything else on https://en.m.wikipedia.org/wiki/Orchestration_%28computing%29 https://en.m.wikipedia.org/wiki/Orchestration_%28computing%2.... To write as if Kubernetes is required to orchestrate computing (particularly in an environment where other containment tech is already available) shows unfamiliarity with a huge body of work from the last two decades.
- scarface74 7y agoI wouldn’t call CloudFormation or Terraform “Orchestration” despite what Wikipedia says. Neither adjust resources dynamically based on health checks, workload, a certain time or based on resources available on the underlying VM. I don’t know the other tools but it makes me doubt the entire Wikipedia article based on what I know.
- nailer 7y agoIn cloud formation you'd make an autoscale group to handle dynamic adjustment of EC2 resources (ie, Xen VMs) or make Lambdas which are started and terminated as needed (is, Firecracker VMs).
- scarface74 7y agoCloudFormation isn’t doing the orchestration though. The orchestration is being done by the load balancer, APIGW, CloudWatch alarms, or whatever AWS uses to route events and trigger lambdas.
- nailer 7y agoYes, agreed. You're creating a resource to do the orchestration built with particular rules, rather than creating and applying those rules directly. I'm not sure the distinction is significant though - ultimately the rules in CF determine your scale-up/scale-down behaviour, directly or indirectly. Perhaps more to the point of the other poster: autoscale groups existed pre-containers and microVMs exist after, orchestration being orthogonal to containment tech.