Skip to content

QA discussion

Jump to bottom
Shahzeb Siddiqui edited this page Feb 7, 2020 · 2 revisions

Easybuild Questions

  • Currently, easybuild automates recipe generation and container build (--container-build-image). Should easybuild support both features?
  • Should we store recipe files in GitHub (https://github.com/easybuilders/eb-singularity)
  • Should we build and publish all containers in Sylabs Cloud library?
  • Can we allow easybuild containers to be built locally? If so which architecture do we support?
  • Should we sign all containers that is pushed to Sylabs? If so which user signs it?
  • Can we integrate eb -–new-pr for recipe files?
  • Shall we create multiple easybuild base images (Centos 7, 8)
  • Should we create domain specific base images (Bio-informatics, Genomics, Chemistry, Statistics)
  • Do we agree on the naming scheme for container recipe Singularity.<APP>-<VERSION>-<TOOLCHAIN>
  • Should easybuild release a container library similar to toolchain release (2x per year)?
  • If easybuild release a container library should all containers be built with one eb version or can they span multiple version? For example is it ok to build GCCcore with eb 4.1.0 and foss with version 4.1.1 where foss was bootstrapped from GCCcore or some older version of eb version.
  • Which architecture shall we support for container library (x86_64, amd64, power8, power9, cray, arm)?
  • Which operating system shall we support (centos, ubuntu, or something else?)
  • Shall we support more than one operating system or architecture in one release. Let's say eb-2020a container library release support centos 7 for x86_64. For subsequent release (eb-2020b), shall we add support for additional OSversion (centos 8, ubuntu xenial)
  • Shall we attempt to even try building licensed software as container? This only assumes eb can build software without license and user can pass the license key as environment variable from host.
  • If we support license software shall we support intel toolchain?
  • Shall we build one container per major version (GCC version 6,7,8). What about Python (3.6, 3.7, 3.8), R(3.4.x, 3.5.x, 3.6.x)?
  • Should container library encompass outdated version of tools on older OS (Centos 5 or 6)
  • Shall we create a regression test against all published containers
  • Should easybuild container library pursue something like nightly CI-CD approach when building and publishing container to pursue reproducible container build coupled with regression test.

Sylabs Question

  • Shall we pursue Sylabs Enterprise? if so who pays for it? Can we get a demo on features?

Sylabs: If you are interested in a commercial enterprise license then you can contact us via the sylabs.io contact form here: https://sylabs.io/contact-us/ regarding demo / questions.

  • Can we merge two containers together if they are SIF images. If so how can it be done?

Sylabs: This is not really possible in a manner that makes logical sense. Each built SIF container image holds a root filesystem which is an OS userspace. You could dump out the first rootfs into a directory, then dump the second on top of it but this is equivalent to copying an OS install from your laptop over your desktop’s hard drive - it may have very odd behavior.

  • What configurable options can be provided on build-system in free edition of Sylabs Cloud?

Sylabs: We don’t have any configuration options at present on the free public cloud. The best way to approach any needs would be for you to let us know what you need, so we could consider it.

  • Is it possible to have a GitHub action to trigger singularity remote build? If so do you have an example?

Sylabs: Integration with GitHub web hooks is in development.

Clone this wiki locally