Draft Belgium as dot star server#3283
Conversation
|
Very exciting! Would it be possible to connect your metrics to those presented here: https://gxy.io/kui @afgane is the contact for this |
|
The criteria have been clarified: #2657 |
Thanks @mschatz, we'll contact Enis for this! |
|
Update: usegalaxy BE has been added to https://status.galaxyproject.org/. Thanks @martenson! |
|
Please let us know if the "make playbooks public" is a big problem for you. Thanks! |
|
Galaxy BE is now present in the KUI dashboard, with numbers that have been double checked: https://lookerstudio.google.com/u/0/reporting/8cfee054-2ddd-4711-af5a-a7a8d62076bb/page/p_zfz14zckwd. |
We are working on making our playbook public, and will give an update when this is ready! |
Quick update, to be revised after galaxyproject#3283 would be merged.
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?