As per more recent changes to our Update Channels docs and following our ongoing developer doc:
We now have very early testing channel rpms available for openSUSE Leap15.1 and Tumbleweed. The latter is particularly experimental and is used by developers as a ‘heads up’ on what’s coming. Neither repositorys offerings are yet at feature parity with our CentOS offering but given they are getting closer all the time I would like to inviting linux proficient / ideally developer capable forum members to try these rpms out. Another prerequisite is a familiarity with the state of our current Stable Channel updates function on CentOS. The main focus is on the Leap15.1 variant as that is what will become our Stable channel offering, which is a necessity for Rockstor’s sustainability. Tumbleweed is, for now, just a future indicator.
Please note that the above “openSUSE dev notes and status” is a controlled document (mostly) and is under continuous development. As from this paragraphs addition we have a new section on AppArmor, please refer to that wiki entry again if you are having difficulties authenticating Rockstor initiated Samba shares.
Please do not expect full function as this is simply not their, and familiarity with both of the above referenced docs is assumed as it is expected that you will be, as the testing channel is defined, contributing fixes while finding them. Or at least giving detailed and informed reports of your findings with hopefully some pointers as to the failure cause. Please do not report issues that you cannot re-produce.
Some but not all known issues are listed in the above wiki entry and in addition:
- The system drive is known to be non functional with regard to Rockstor created shares (they vanish after a few seconds). So any system used to test these rpms must have at least one dedicated data drive.
- The Web-UI ‘System Shell’ is non functional.
It is expected that as from 3.9.2-51 these rpms should be able to update themselves when new versions become available so the hope is that we can iterate, as before, within the testing channel, with the aim of initially reaching a CentOS feature parity, or near enough, where upon we can then establish our first openSUSE compatible Stable Channel release.
Initial requirements prior to rpm install.
- Apply all pending updates to the base openSUSE install.
- Establish and enable Network manager and stop and disable wicked
For the above 2 items see the linked wiki entry up until but not including “Packages for Building Rockstor from source”.
Import Rockstor’s public key, our rpms and repositories are now signed.
As the root user:
rpm --import https://raw.githubusercontent.com/rockstor/rockstor-core/master/conf/ROCKSTOR-GPG-KEY
Add the relevant repository.
On a Leap15.1 install:
zypper addrepo -f http://updates.rockstor.com:8999/rockstor-testing/leap/15.1/ Rockstor-Testing
On a Tumbleweed install:
zypper addrepo -f http://updates.rockstor.com:8999/rockstor-testing/tumbleweed/ Rockstor-Testing
Both repos will be updated in sync and will carry the same version of Rockstor’s code, assuming both are able to build at the time of that release.
Again please note that these rpms are not nearly ready for production, but with skilled community feedback we can get them that way.
If you are particularly interested in this effort but are struggling with this install method, or need to ask more on how to do this, then please wait until our Alpha openSUSE based installer is released. It may not be all that long
Thanks to all those how have helped to get us this far. I’m chuffed to at least get here and special thanks to our forum moderator come major contributor @Flox who has done a tone of Rockstor on Leap15.1 / Tumbleweed testing / developing.
Again please only try these rpms if you are very familiar with linux and current Rockstor Stable Channel updates and have familiarised yourself with the above referenced docs. There is of course every intention of making these openSUSE compatible offerings our main stay, where upon they will be fit for purpose as best we can make them. But for the time being these are early developer releases that need a lot of work. But are nevertheless, within some areas, surprisingly functional.
Hope you enjoy the testing and remember that we are still supporting our current CentOS subscribers so please be patient.