Testing

All current OS rpmbuild hosts:

• Leap-15.5/15.6(x86_64 & aarch64)
• Slowroll.X86_64, Tumblweeed.aarch64
  were able to rpmbuild and install an rpm based on this branch.

Here we are initiating our Slowroll compatibility, starting with the ability to roll-out future adaptations/fixes via the testing/stable channels.

Re associated issue comment: #2971 (comment)

This branches Slowroll built & hosted rpm install was able to establish the intended Tumblweed repo, for both our dnf & zypper configurations:

DNF / yum

rslowroll:~ # yum repolist
repo id                                                         repo name
Rockstor-Testing                                                Subscription channel for testing updates

rslowroll:~ # cat /etc/yum.repos.d/Rockstor-Testing.repo 
[Rockstor-Testing]
name=Subscription channel for testing updates
baseurl=http://updates.rockstor.com:8999/rockstor-testing/tumbleweed
enabled=1
gpgcheck=1
gpgkey=file:///opt/rockstor/conf/ROCKSTOR-GPG-KEY
metadata_expire=1h
exclude=*.src

Zypper

rslowroll:~ # zypper lr -U | grep Testing
 2 | Rockstor-Testing | Rockstor-Testing| Yes | ( p) Yes  | Yes| http://updates.rockstor.com:8999/rockstor-testing/tumbleweed

Testing continued

Re our docker config Slowroll adaptations, after having configured and enabled Rock-ons:

JSON config file

Our 'derived from OS package config' override file:

rslowroll:~ # cat /opt/rockstor/conf/docker-daemon.json 
{
  "data-root": "/mnt2/rockons-root",
  "log-driver": "journald",
  "log-level": "warn",
  "log-opts": {
    "tag": "{{.ImageName}}/{{.Name}}"
  },
  "storage-driver": "btrfs",
  "storage-opts": [
    "btrfs.min_space=1G"
  ]
}

And its adoption/application via the OS systemd service file machine-edit:

rslowroll:~ # cat /etc/systemd/system/docker.service | grep rockstor
After=network.target lvm2-monitor.service firewalld.service rockstor-bootstrap.service
ExecStart=/usr/bin/dockerd --add-runtime oci=/usr/sbin/runc $DOCKER_OPTS --config-file /opt/rockstor/conf/docker-daemon.json

Thanks again to @FroggyFlox for this clean adaptation mechanism.

@FroggyFlox In the next testing phase we may want to look at a systemd override file mechanism here, rather than directly machine-editing the OS provided docker.service file. I.e. as we have already adopted for our nginx for example. That is,
maintain your machine edit but output only what we need to change to an override file that we can simply wipe and re-create.

Regarding the SSHD/SFTP testing, we have an outstanding spin-off issue by way of dependency that blocks proper testing for the time being:

• "Tumbleweed & Slowroll SFTP chroot libs issue" Tumbleweed & Slowroll SFTP chroot libs issue #2973

However, in all other regards, the adaptation to Slowrool sshd config here is as per elsewhere: we treat it identically to our current treatment of Tumbleweed.