brainstorm - ravenadm without null mounts

Ravenports / ravenadm

Administration tool for Ravenports

http://www.ravenports.com

ISC License

17 stars 3 forks source link

brainstorm - ravenadm without null mounts #46

Open jrmarino opened 3 years ago

jrmarino commented 3 years ago

provide mtree specification with each mount on ravensys-root
when ravenadm starts up, compare builder mtree spec with ravensys-root. If build does not exist, copy it over. if it does not match, fix it.
for common mounts (packages, distfiles)
- before chroot ented, copy distfiles (if available) and packages (known to be available) to builder
- before chroot destroyed copy new distfiles back to common folder.
- before chroot destroyed copy produced package to common folder

This might be a new stage. One benefit is no stuck mounts. Make null mounts an option rather than an internal alternative?

jrmarino commented 3 years ago

avoid ~~NFS and~~ fuse systems

jrmarino commented 2 years ago

I think actually we'll need NFS for ccache (recommended localhost only though) In theory, NFS should work for /packages and /distfiles as well.

jrmarino commented 2 years ago

For the way of resetting build environment, we might consider cpdup or rsync as well. cpdup would probably work pretty well.

jrmarino commented 2 years ago

How to eliminate READ/WRITE /packages mount:

With null mounts: Mount as READ-ONLY.
without null mounts: ravenadm copies all dependencies packages in root's /packages directory after the build environment is initialized
when a package set gets produced, ravenadm copies packages from /new-packages to repository's packages directory. Don't copy over any portion of incomplete set (e.g. "complete" subpackage exists but nothing else, don't copy just that one subpackage).

This should be done regardless of no-null-mount support. It's just safer.

jrmarino commented 2 years ago

How to eliminate READ/WRITE /distfiles mount: Change how "fetch" phase works.

with null mounts, mount /distfiles as READ-ONLY
if distfile is not cached, or it fails the checksum, it's downloaded to a temporary directory if it's not already being downloaded by another builder
try to be smart -- if there are multiple distfiles and one is "locked" move on to the next one, and come back. When lock is released, check /distfiles mount to see if it exists there
If locked, sleep for 1 second and check lock status again
after each successful distfile retrieval, copy to distfiles location and release the lock

jrmarino commented 1 year ago

I forgot I wrote this -- and had the idea again, #65

jrmarino commented 1 year ago

current mount situation

root@capricorn:/var/ravenports/distfiles # mount | grep SL03
/raven/share/raven/sysroot/FreeBSD/bin on /var/ravenports/builders/SL03/bin (nullfs, local, read-only)
/raven/share/raven/sysroot/FreeBSD/usr on /var/ravenports/builders/SL03/usr (nullfs, local, read-only)
/var/ravenports/RELEASE-12.2/packages on /var/ravenports/builders/SL03/packages (nullfs, local, read-only)
/var/ravenports/distfiles on /var/ravenports/builders/SL03/distfiles (nullfs, local)
/var/cache/raven-ccache on /var/ravenports/builders/SL03/ccache (nullfs, local)
devfs on /var/ravenports/builders/SL03/dev (devfs, local, multilabel)

jrmarino commented 1 year ago

could rsync help copy files to /bin, /usr/ etc?

added: do netbsd bulk approach 1) populate X builders permanently based highest number of builders in any profile 2) sync with rsync all builders used by current profile as part of kicking off build

hmmm, still need to think about R/W part of this. Maybe rsync can remove write permissions on all files and the /usr, /bin directories.