@Emad-R said in k8s VS slack:

devops-me2.slack.com

Also another reason i decided to do this, notice how much developers have support inside company... like they have 40 others DEVs, but its not the same with system admins and devops

@marcinozga said in Why containers are free and easy but managing them is hard and costly:

You're comparing apples to oranges. Hypervisors vs k8s makes no sense. And what makes you think that running containers in production is only viable with tools like k8s? That's like saying running vm in production only makes sense on openstack. Docker for example can easily be managed with Ansible, or if you want web tool, Portainer, including managing swarm clusters.

Nomad is another popular one that does not only containers but a few different types of jobs.

@StorageNinja said in Containers on Bare Metal:

Also looking to acquire some beefier ARM platforms that I can run experimental ESXi builds on. - https://shop.solid-run.com/product/SRM8040S00D16GE008S00CH/ has caught my eye

Now this looks really sweet. That's some cool stuff... both the hardware and ESXi on ARM. $459 is a little high for that CPU and only 16GB, but not horrible.

@Obsolesce said in Does Container tech makes backups and RAID obsolete:

@Emad-R said in Does Container tech makes backups and RAID obsolete:

Hi,

Do containers and management platform for containers, makes all the hard work of making the server resilient obsolete like RAID and backups, however we will assume that the DB are hosted outside of this scope like on Amazon services.

If you have a server running 500 containers, would it be easier for automation to spin up another 500 containers on new hardware (while dealing with whatever issues are caused by 500 containers being down) or easier to have RAID and simply swap a disk and continue on?

Actually for "easier", the container spinups can be automated, but the drive swap requires a human. The real effort is in acquiring another server to spin them up on. One approach is ignoring that an entire replacement server is needed.

Having a full server die and take all of its workloads with it has all the same impact with containers as with anything else. Containers are really just "really heavy threads", nothing more.

@JaredBusch said in Conatainers (Docker) vs VMs - When and Why?:

@Obsolesce said in Conatainers (Docker) vs VMs - When and Why?:

Are there many use cases in the SMB outside of Dev?

Not even in dev really for the SMB. Just use a single VM to do the work. SMB rarely needs to scale.

Other than as you stated, the solution is presented that way. Like UNMS.

Even enterprise rarely need to scale that way. It's more for hosting companies than anything.

@devops1 said in Kubernetes (Kubespray) Issue.:

@stacksofplates Thank you very much It works.

No problem!

@flaxking said in Check my 2 min audio theory on Containers:

@scottalanmiller said in Check my 2 min audio theory on Containers:

@flaxking said in Check my 2 min audio theory on Containers:

What you're talking about is one aspect of part of implementing DevOps that is often misinterpreted to mean the whole of it. And yes, it is stupid to call that DevOps. That's just Ops using different tools.

I see it as the opposite. Patrick's core DevOps...

"Thanks to the devopsdays conference, the idea of devops seems to live on. While talking with other people about it, I realize that it is difficult to frame it within the current IT landscape. At lot of the ideas are coming from different kinds of emerging technologies (T) and process management (P) approaches.

For me the two most important observations are:

there is a increase in feedback loops between business, all parts of the delivery process and operations thanks to this feedback loops we increase the quality and speed up the flow"

This is the core of DevOps, not well described, but pretty clearly about IT, not development. This is the core. Very, very loosely defined to the point of useless, sure.

Then things like DevOps talking dev itself is the extra, the tack on later. It's not "part of" devops, any more than it is of any operations. And just how operations doesn't cease to exist without developers, neither does DevOps.

I believe everything on that page is all meant to be within the context of companies doing development. But I agree, the core of DevOps is about Ops and Business practices. However, I firmly believe the name DevOps comes from Ops and Development working together, and thus the reason why discussions of DevOps implementation specifics centre around companies doing software development. Though just based on that page, I could see why someone could still take a different view. However, I consider The DevOps Handbook to be the definitive source, rather than notes on the initial discussions.

I think doing that makes DevOps a pointless, useless concept. Hopefully that's not what he intended. As an ops practice, it has tremendous value. As a merger of dev and ops, it's just bluster.

@aaronstuder said in LXC 2.1 Containers Releases:

@mlnews said in LXC 2.1 Containers Releases:

Not an LTS release.

But does it matter?

It does if you are a person that wants LTS (e.g. you hate keeping your systems up to date) and like run Ubuntu LTS, and want to update LXC and this would cause an LTS conflict.

@black3dynamite said in Installing LXC Containerization on openSuse Tumbleweed:

@scottalanmiller said in Installing LXC Containerization on openSuse Tumbleweed:

@black3dynamite said in Installing LXC Containerization on openSuse Tumbleweed:

@scottalanmiller said in Installing LXC Containerization on openSuse Tumbleweed:

I have to say, though, I prefer the Ubuntu LXD approach much better.

I know Canonical is a big supporter of LXD. Who is the big supporter for LXC?

LXD is just an interface for LXC. So Canonical supports LXC through LXD. The biggest contributors to LXC are Virtuozzo, IBM and Google.

So LXD makes it easier to manage LXC?

Yes

That, too.

@RamblingBiped said in Containers in IT:

Do you automate configuration management and deployment using Puppet? Chef? Ansible?

This particular item (DevOps vs. Snowflakes) applies to VMs and containers equally.

https://meros.io/wp-content/uploads/2015/10/meros-tri.png

@coliver said:

@hobbit666 said:

@scottalanmiller said:

@hobbit666 said:

They will be running on ESXi FREE 5.5update3

I'd start by replacing that 😉

BUT I DON'T WANT TO!!!!!!

You don't have to... but that is going to be a limiting factor in a number of ways. Especially when you are looking at management or want to expand your infrastructure.

Or performance, ease of use....