Hi David, Our cluster is a mix of different architectures. We compile the scientific code for each architecture and generate the same package for different architectures.
To do this we use EasyBuild https://easybuild.readthedocs.io/en/latest/ EasyBuild gives something like skylake/2018a/GCCcore-6.4.0-eb_3.5.1-1.x86_64.rpm skylake/2018a/ScaLAPACK-2.0.2-gompi-2018a-OpenBLAS-0.2.20-eb_3.5.1-1.x86_64.rpm haswell/2018a/GCCcore-6.4.0-eb_3.5.1-1.x86_64.rpm haswell/2018aScaLAPACK-2.0.2-gompi-2018a-OpenBLAS-0.2.20-eb_3.5.1-1.x86_64.rpm We want to have a distribution for each architecture and 2 versions per year. dev-pulp-server.ptci.dev:24816/pulp/content/skylake/2018a/ dev-pulp-server.ptci.dev:24816/pulp/content/haswell/2018a/ dev-pulp-server.ptci.dev:24816/pulp/content/skylake/2018b/ dev-pulp-server.ptci.dev:24816/pulp/content/haswell/2018b/ For the moment I am looking how to do it and, for this, I write a task to create the repo, add the packages, publish and distribute. But I need to fix some bugs because it does not works for the moment. Also we want to freeze the remote Centos and epel repositories using the synchronization to be sure that all the nodes have the same packages. I will see how to put my role from our gitlab to github. About the plugins, the most important for us is the rpm plugin. Later we could use the python and ansible plugin to distribute our python code and our roles. Regards Juan On 24/05/19 19:16, David Davis wrote: > Juan, > > First off, which plugins are you using? I'm asking because the plugins > are in various states of development--some are beta while others are RC. > > I don't think we can guarantee that there won't be any major breaking > changes in the API between now and Pulp 3.0 GA but personally I think > that it's unlikely as I don't foresee any. Maybe other Pulp developers > can weigh in. > > The concern that I have is that we don't support upgrades from one RC > to the next. Maybe we can consider this though with the next release > (RC3) since we know at least one user will be using it in production. > > About these ansible tasks, I'm interesting in what you're doing. Is > there some code you could open source and share us and with other Pulp > users? > > David > > > On Fri, May 24, 2019 at 11:36 AM Juan Cabrera <[email protected] > <mailto:[email protected]>> wrote: > > Hi pulp developers, > > We are very interested on using pul3 in our HPC cluster at the > university of UNamur (Belgium). We want to have our own repository > with the programs that we compile for the scientist that use the > cluster. > > This is why I am working on creating "ansible" tasks to create the > repositories with pulp3 and I am asking you a lot of questions. > > There will be a maintenance of the cluster on July and we would > like to install and use repositories with versioning like pulp3. > > I want to know if you think that we could use pulp3 on production > for July. Do you expect to do big modifications on the API structure? > > Thanks for the help you give. > > Regards > > Juan > > > -- > > Juan CABRERA > Correspondant informatique > Département de Mathématiques > > T. 081724919 > [email protected] <mailto:[email protected]> > http://staff.unamur.be/jbcabrer > > Université de Namur ASBL > Rue de Bruxelles 61 - 5000 Namur > Belgique > > Let’s respect the environment together. > Only print this message if necessary! > > _______________________________________________ > Pulp-list mailing list > [email protected] <mailto:[email protected]> > https://www.redhat.com/mailman/listinfo/pulp-list > -- Juan CABRERA Correspondant informatique Département de Mathématiques T. 081724919 [email protected] <mailto:[email protected]> http://staff.unamur.be/jbcabrer Université de Namur ASBL Rue de Bruxelles 61 - 5000 Namur Belgique Let’s respect the environment together. Only print this message if necessary!
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
