Repository navigation
feat(load): run the member ramp and the group fan-out in local campaigns - #5112
Merged
Merged
Conversation
…assword The report masks the admin password everywhere, so the bundled Stack's 'cozy' turned the schema into '[redacted]-load-result/1' and every local fan-out was inconclusive. The envelope's schema, producer and workload are the harness's constants and are never masked.
The bundled Stack gets the load-org-sharing context and a loopback admin port, and Make points the seeder at it locally. The campaign seeds one organization, runs the ramp with its writer and reader members and the fan-out to its members, then removes it. Shared DEV is unchanged.
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
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.
Part of #5107 (step 2).
Locally, the campaign now seeds one organization, runs the shared-drive ramp with its writer and reader members and the group fan-out to its members, then removes it. Shared DEV is unchanged.
load-org-sharingcontext and its admin API on 127.0.0.1:16060 (the VM's private override did this). Make points the seeder at it for local runs only, never withLOAD_TARGET=devor a Cloudery token.cozyturned the envelope's schema into[redacted]-load-result/1and every local fan-out was inconclusive.Checked with
make node-checks(645/645) and a localmake campaign CAMPAIGN=smoke(exit 0, every step completed); the fan-out and the member ramp show in Grafana.