Difference between revisions of "Bellatrix"
From Fixme.ch
(→VM) |
|||
| Line 2: | Line 2: | ||
== Description == | == Description == | ||
| − | * Provisionning of the nodes and creation of VMs done with Ansible from | + | * Provisionning of the nodes and creation of VMs done with Ansible from KVM/LibVirt |
* Hosts a Kubernetes node: k8s.fixme.ch see [[Kubernetes]] | * Hosts a Kubernetes node: k8s.fixme.ch see [[Kubernetes]] | ||
* Replaced [[Foo]] and [[MetaFoo]] | * Replaced [[Foo]] and [[MetaFoo]] | ||
Latest revision as of 13:22, 14 July 2022
Contents
Description
- Provisionning of the nodes and creation of VMs done with Ansible from KVM/LibVirt
- Hosts a Kubernetes node: k8s.fixme.ch see Kubernetes
- Replaced Foo and MetaFoo
- Ask User:Francois or User:Rorist for the access
Hardware
We have received 2 chassis with 4 compute nodes each from the old Bellatrix cluster from EPFL.
- 2 Sandy Bridge processors running at 2.2 GHz, with 16 cores each
- Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz
- 94 GB of RAM
Status
- 02.2018 Ubuntu MaaS is installed and able to deploy other nodes
- 02.2019 Continuing to migrate services on K8S
- 11.2020 Upgrade CPU and RAM to 32 proc / 94G ram
VM
root@bellatrix:~# virsh list Id Name State ---------------------------------------------------- 1 k8s running 7 odoo.fixme.ch running 16 gitlab-test.fixme.ch running 18 gitlab-runner.fixme.ch running 19 runner0 running 21 k3s.fixme.ch running 24 meet-test.fixme.ch running 30 world.fixme.ch running 32 status.fixme.ch running 34 world-test.fixme.ch running 36 communr.fixme.ch running 38 crousille.fixme.ch running 40 mumble.fixme.ch running
