Draft Belgium as dot star server #3283
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey all!
The useGalaxy Belgium team would like to open the discussion on the requirements on becoming an official usegalaxy.* or 'dot star' instance.
Below I copied the current listed requirements (updated on Dec 23, 2023) with a comment underneath where I added the current state of https://usegalaxy.be. Points of discussion marked in bold.
.* Membership current requirements
Since upgrading our Galaxy BE from version 24.1 to version 24.2, we've implemented a 'Request for change' or RFC method as part of change management that we are now applying to basically all our services. This solidifies the whole upgrade process as it comes with risk assessment, peer and technical review, step-by-step documentation, an upgrade checklist,... . We have been committed and successful in upgrading within 90 bussiness days, which we are now applying to v25.0.
We don't have any restrictions on access or registration as anyone can make an account. We do not have anonymous usage enabled, but this might not be a hard requirement anymore?
Most of the repositories of our usegalaxy-be are public on Github: https://github.com/orgs/usegalaxy-be/repositories?q=visibility%3Apublic. Our infrastructure playbook is not. Is this still a hard requirement?
We provide CVMFS reference data (https://usegalaxy.be/libraries), and have 1400+ tools available on our instance.
EDIT: We are now also part of the official status page, and are also in this one. We have also been monitoring https://usegalaxy.be internally for some months, and can quite confidently say that we have been providing (and will continue to provide) well above 90 percent of uptime. We just lack the historical numbers to back this up properly. What are these automated cross-usegalaxy testing initiatives refering to?