Page for meeting notes with Claudio

Potential major change - Move from apptainer/podman to docker/kubernetes

• Claudio has personal hardware to run his kubernetes clusters (4 of them) And uses docker to build the containers, along with cmake to build the packages, then installs them using apt since he builds ubuntu containers
• He has an epics container (kafka epics) running on kubernetes with various packages

New (after lunch):

• Kubernetes is hosted on TID, but claudios cluster is avirual cluster on kubernetes
• Kubernetes host machine resources are usable
• Server is a tribute to s3df, 
• idea is to always work with TID, but we buy the resources
• we have no box, we just donate to tid to get some resources
• working with ye patrick pascual and jesse bellister for kubernetes virtual clusters
• we should make one new cluster for us
• each application is a namespace
• use rest api in go 
• Claudio made a proof of concept of a component database
• the database is deployed, but use docker composer to get access to mongodb
• claudio will prepare the docker composer
• the backend is in java spring which connects to the mongodb, so we will contact claudio if we want to modify the mongodb
  • Backend is needed for database modifications
  • But it has api for create component, delete component, etc.
  • we are considered a 'client/user' of the component db, and claudio will be the adminstrator.

Claudio comments about build system proposal:

• for now one cluster is enough
• claudio will talk to ye for the cluster
• building can be done internally with docker as long as have image
• would we need argo cd? Because TID manages the argo CD.
• I would like to use your build system but have argo cd for now. but problem with argo cd is repos are exponentially growing
• can be deployed on real machine or on kubernetes
• Able to build docker images for all the components 
• Build component deploy component, and pack it a package to install with ansible, the only difference is the package because luberntes is docker image, but deploy in real machine, it is normal rpm packages.
• Artifact storage
  • can put it in s3df somewhere, everything thats been built, 
  • claudio suggest: we can ask for kubernetes pod accessible storage on s3df.
  • Sef fs, you can also install artifactory on your kubernetes cluster (the open source version), claudio used arbor previously (docker repository) helps scan image for security.. Useful because no need to rebuild image in a new system. simple to manage updating a system.
  • for artifcatory, we can have images and built binaries
  • claudio used gitlab to deploy to artifactory for the libraries.
  • artifactory caches packages.
• Having your cluster you can install what you need