netapp_eseries.beegfs
The NetApp E-Series BeeGFS collection provides roles to deploy supported versions of BeeGFS on hosts using NetApp E-Series storage.
Health score
75 / 100
Healthy, with room to improve.
- Excellent
- Good (this collection)
- Fair
- Poor
- Not scored
Observed 6 of 8 signal groups.
Four are needed before a score is published.
4 needed
Category subscores
- Security
- 0%
- Trust
- 85%
- Quality
- 82%
- Maintenance
- 74%
- ansible-core compatibility
- 100%
| Signal | Verdict | What we found | Points | Proved by |
|---|---|---|---|---|
| Signals we could observe | ||||
| security.dependency_boundedness | Not met | 0 of 2 dependencies bounded | 0 / 1 | Published artifact |
| trust.link_claims | Partly met | 3 of 4 link URLs declared | 0.85 / 1 | Published artifact |
| quality.docs | Passed | readme, 14 doc files | 3 / 3 | Published artifact |
| quality.changelog | Partly met | CHANGELOG.md only, 0 fragments | 0.9 / 2 | Published artifact |
| quality.license_quality | Passed | SPDX id declared (BSD-3-Clause) | 1 / 1 | Published artifact |
| maintenance.release_recency | Partly met | last release 198 days ago | 2.55 / 3 | Galaxy index |
| maintenance.changelog_recency | Partly met | 0 unreleased changelog fragments | 0.4 / 1 | Published artifact |
| compat.requires_ansible | Passed | >=2.19 | 3 / 3 | Published artifact |
| Signals we could not observeNot observed — these are left out of the score rather than counted against it. | ||||
| trust.ansible_membership | Not observed | not shipped in the ansible package | excluded from this score | ansible-build-data |
| quality.tests | Not observed | no test evidence in the published artifact | excluded from this score | Published artifact |
| quality.ci | Not observed | no CI evidence in the published artifact | excluded from this score | Published artifact |
| compat.membership_currency | Not observed | not shipped in the ansible package | excluded from this score | ansible-build-data |
No repository evidence yet. ansible.care has not read any collection's Git repository, so every signal above was proved from a published artifact or from Ansible’s own build data. Tests and CI in particular can be proved present this way but never proved absent — so when we cannot see them, we leave them out of the score rather than counting them against you.
What is costing points
Each of these is a signal we observed and could not fully credit.
- quality.changelog
Ship a `changelogs/changelog.yaml` — the structured form `antsibull-changelog` generates and the `ansible` package consumes — rather than only a hand-maintained `CHANGELOG.md`, and write a fragment into `changelogs/fragments/` as each change lands rather than reconstructing release notes at release time. Both have to be inside the published tarball to be observable: a changelog that lives only in your Git repository is one we cannot read. This is the single highest-leverage change for most collections, because the same missing file is what holds down both changelog rules in this rubric. If you already publish `changelog.yaml` with fragments, this rule is answered.
- security.dependency_boundedness
Give every collection dependency you declare in `galaxy.yml` an upper or pinned bound — `<`, `<=`, `==` or `~=` — so that installing your collection cannot silently pull in an arbitrary future release of somebody else’s. If your collection declares no dependencies at all this rule already awards full marks and there is nothing here to change. If we reported a dependency we could not read, the fix is the syntax of its version range rather than the dependency itself.
- maintenance.release_recency
Cut a release to Galaxy. This is the heaviest single rule in the rubric because a release is the one unambiguous, publisher-controlled act of maintenance we can observe without reading your repository — which is also its limitation, and worth saying plainly: a collection under active development that rarely releases is under-credited here, and that is a gap in what we can see rather than a judgement about the work. If your collection is finished rather than abandoned, there is nothing here you should change on our account.
- trust.link_claims
Declare the link fields your collection actually has in `galaxy.yml` — `repository`, `documentation`, `homepage` and `issues` — and correct any we reported as unparseable, which is usually a stray character rather than a wrong address. This is a metadata edit: we never fetch what is behind these URLs, so nothing about your hosting is being graded. Do not invent a URL to fill a field — a scaffolding placeholder left where it was born is shown on your page as the placeholder it is, and an honestly empty field reads better than a link that goes nowhere.
Links
Authors
- Vu Tran (@VuTran007)
- Christian Whiteside (@mcwhiteside)