Sorry if that sounds trollish. It wasn't intended to be. Look at it this
way.
There are two approaches to running an IT installation. One is the
free-wheeling idependent aproach. The other is the stuffy corporate
approach.
Free-wheeling shops run things like Ubuntu. Or even BSD (but that's
I should know to not feed the trolls, but here goes. I was answering a
question asked to the list, not arguing for or against containers.
> 2. Logs in containerized ceph almost all go straight to the system journal.
> Specialized subsystems such as Prometheus can be configured in other ways,
I used the steps under this article for setting up a Ceph cluster in my homelab
environment. It uses Ansible in a couple of ways, but honestly you could
probably take a number of the manual steps and make your own playbook out of it.
https://computingforgeeks.com/install-ceph-storage-cluster-on-
Those are reasonable objections, although some are now dated. In the
context of Ceph some of those issues are also further addressed by Ceph
itself. So let me present my take.
1. Networking. You can set up some gnarly virtual networks in both
container and cloud systems, it's true. Docker has
* Docker networking is a hassle
* Not always clear how to get logs
* Not being able to update iptables without stopping all services
* Docker package management when the name changes at random
* Docker core leaks and kernel compatibility
* When someone isn’t already using containers, or has their
Den lör 31 aug. 2024 kl 15:42 skrev Tim Holloway :
>
> I would greatly like to know what the rationale is for avoiding
> containers.
>
> Especially in large shops. From what I can tell, you need to use the
> containerized Ceph if you want to run multiple Ceph filesystems on a
> single host. The leg
I would greatly like to know what the rationale is for avoiding
containers.
Especially in large shops. From what I can tell, you need to use the
containerized Ceph if you want to run multiple Ceph filesystems on a
single host. The legacy installations only support dumping everything
directly under
Den fre 30 aug. 2024 kl 20:43 skrev Milan Kupcevic :
>
> On 8/30/24 12:38, Tim Holloway wrote:
> > I believe that the original Ansible installation process is deprecated.
>
> This would be a bad news as I repeatedly hear from admins running large
> storage deployments that they prefer to stay away
On 8/30/24 12:38, Tim Holloway wrote:
I believe that the original Ansible installation process is deprecated.
This would be a bad news as I repeatedly hear from admins running large
storage deployments that they prefer to stay away from containers.
Milan
--
Milan Kupcevic
Research Computing
Hi Michel,
This is likely related to your ansible installation or system locale
configuration. Try to gather more info. E.g.:
which ansible
ansible --version
locale
locale -a
Also check if you run matching versions of ansible, ceph-ansible and
ceph as is listed in Releases section at
https:
I believe that the original Ansible installation process is deprecated.
It was pretty messy, anyway, since it had to do a lot of grunt work.
Likewise the ceph-install program, which is in the Octopus docs, but
wasn't actually available in the release of Octopus I installed on my
servers.
The Ansib
11 matches
Mail list logo
