Difference between revisions of "Bellatrix"
From Fixme.ch
Line 19: | Line 19: | ||
* 02.2018 Ubuntu MaaS is installed and able to deploy other nodes | * 02.2018 Ubuntu MaaS is installed and able to deploy other nodes | ||
* 02.2019 Continuing to migrate services on K8S | * 02.2019 Continuing to migrate services on K8S | ||
+ | |||
+ | == VM == | ||
+ | |||
+ | <pre> | ||
+ | fixme@bellatrix:~$ virsh list | ||
+ | Id Name State | ||
+ | ---------------------------------------------------- | ||
+ | 1 k8s running | ||
+ | 2 odoo.fixme.ch running | ||
+ | 20 fire running | ||
+ | </pre> | ||
== Participants == | == Participants == |
Revision as of 10:10, 12 February 2019
Contents
Description
- Provisionning of the nodes and creation of VMs done from: https://bellatrix.fixme.ch/MAAS/
- One of the VM hosts a Kubernetes node: k8s.fixme.ch see Kubernetes
- Meant to replace Foo and possibly 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
- 32 GB of RAM
Status
- 02.2018 Ubuntu MaaS is installed and able to deploy other nodes
- 02.2019 Continuing to migrate services on K8S
VM
fixme@bellatrix:~$ virsh list Id Name State ---------------------------------------------------- 1 k8s running 2 odoo.fixme.ch running 20 fire running