Initial commit: itential.valkey collection - #2
Open
Amunagala-itential wants to merge 2 commits into
Open
Amunagala-itential wants to merge 2 commits into
Amunagala-itential wants to merge 2 commits into
Conversation
Standalone Ansible collection installing Valkey as a Remi-free, EL9/Amazon Linux 2023-only alternative to itential.deployer's redis role. Depends on itential.deployer at runtime for the shared common and offline utility roles. This collection is transitional: it exists separately from itential.deployer only until roles/redis is retired there, at which point roles/valkey and its playbooks are intended to be merged directly into itential.deployer.
8 tasks
Amunagala-itential
requested review from
Madias2222,
Nick-Andreano and
kvelarde-itential
September 17, 2026 10:53
Replaces the "Quick Start" stub (which just linked out to itential.deployer's own README) with an actual step-by-step flow: installing both collections, setting up the working directory, building a combined inventory (Valkey + MongoDB + Platform), and the verify/install/certify command sequence across both collections. Also documents a real gap found while writing this: itential.deployer's os.yml doesn't yet target valkey_master/valkey_replica/valkey_sentinel, so baseline OS/firewalld setup doesn't run against fresh Valkey hosts via the normal flow. Tracked as a known limitation for now, not fixed here since it lives in a different repo.
There was a problem hiding this comment.
I think we can remove this action. The changelog is updated by the publish action. Please make sure I'm not missing something.
Comment on lines
+6
to
+7
| # Valkey is only supported on RHEL/Rocky/AlmaLinux 9. A host on any other OS or major version | ||
| # will fail validate-vars.yml immediately. Use the redis role on EL8. |
|
|
||
| # Target node download directories | ||
| valkey_offline_target_node_rpms_dir: "{{ valkey_offline_target_node_root }}/rpms" | ||
| valkey_offline_target_node_archives_dir: "{{ valkey_offline_target_node_root }}/archives" |
|
|
||
| # Control node download directories | ||
| valkey_offline_control_node_rpms_dir: "{{ valkey_offline_control_node_root }}/rpms" | ||
| valkey_offline_control_node_archives_dir: "{{ valkey_offline_control_node_root }}/archives" |
| ansible-galaxy collection install itential.valkey | ||
| ``` | ||
|
|
||
| This does not automatically install `itential.deployer` — install both: |
There was a problem hiding this comment.
Is this true? I thought if itential.deployer is listed as a dependency in the galaxy.yml then it would get install automatically?
Comment on lines
+55
to
+60
| This walks through deploying Valkey alongside the rest of the Itential stack (MongoDB, | ||
| Platform, Gateway), using `itential.deployer`'s own bootstrap flow. If you've already got a | ||
| working directory set up for `itential.deployer` (see its README's "Running the Deployer" | ||
| section for the full explanation of each step below), skip to | ||
| [3. Add Valkey to your inventory](#3-add-valkey-to-your-inventory). | ||
|
|
There was a problem hiding this comment.
I don't think we need to go over installing the Platform stack in this readme.
Comment on lines
+168
to
+170
| | `verify_valkey.yml` | `itential.valkey.verify_valkey` | Pre-install verification for Valkey hosts | | ||
| | `certify_valkey.yml` | `itential.valkey.certify_valkey` | Generate Valkey/Sentinel installation certification reports | | ||
| | `download_packages_valkey.yml` | `itential.valkey.download_packages_valkey` | Download Valkey packages for offline install | |
There was a problem hiding this comment.
Since this is a standalone collection for Valkey, should we remove the _valkey from these playbook names? It made sense in the Deployer because we had multiple components.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Initial scaffold of the standalone
itential.valkeyAnsible collection: installs Valkey as a Remi-free, EL9/Amazon Linux 2023-only alternative toitential.deployer'sredisrole.This collection is transitional — it exists separately from
itential.deployeronly untilroles/redisis retired there, at which pointroles/valkeyand its playbooks are intended to be merged directly intoitential.deployer.Depends on
itential.deployerat runtime for the sharedcommon/offlineutility roles (referenced by FQCN).Contents
roles/valkey/— the role, ported fromitential.deployer's in-progress PR (#374 there), withcommon/offlinecalls rewritten to FQCN and internal variables renamed with avalkey_prefix for namespace safetyplaybooks/valkey.yml,verify_valkey.yml,certify_valkey.yml,download_packages_valkey.ymldocs/valkey_guide.md,example_inventories/valkey/itential.deployer's conventions (ansible-lint,role-readme-check, changelog/publish workflows)Test plan
ansible-lintclean (0 failures) with bothitential.valkeyanditential.deployerregistered as collectionscertify_valkey.ymlpasses clean on all hosts, cross-collection FQCN resolution confirmed working end-to-end