DM-44844: Deploy Cassandra for production Prompt Processing #174
Conversation
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
Keyspaces like pp_apdb_latiss are now reserved for production; development spaces are suffixed with _dev.
hsinfang
approved these changes
Jun 20, 2024
| password: PASSWORD | ||
| # Workaround for list-cassandra not having keyspace-agnostic credentials, MUST go after all other entries | ||
| - url: cassandra://sdfk8sk001.sdf.slac.stanford.edu:9042/* | ||
| username: ANY_CASSANDRA_ACCOUNT |
There was a problem hiding this comment.
Do you mean ANY_CASSANDRA_ACCOUNT literally here and not apdb?
There was a problem hiding this comment.
You can use apdb, apdb-prod, or anything else, so long as it's a valid account. How to express that?
Having all keyspaces use the apdb credentials is potentially problematic. The revised example leaves room for prod APDB configs later, even though those are outside the scope of the Playbook.
Adding comments to the file makes it easier to understand. Users should not be using the service accounts instead of the developer account.
This allows developers to use db-auth-only setups if they don't need to work with Postgres.
We want labels for all our APDBs for ease of analysis and management, even if Prompt Processing itself can't read the index.
Fixed some typos and removed the dashboard link, which is now in Slack with the others.
--init-only guarantees that dataset types are registered, and it's much faster than actually running the pipeline.
This message is directed towards new users, who might not know what to do when they want to run, say, 10 visits.
kfindeisen
force-pushed
the
tickets/DM-44844
branch
from
ff47f31 to
ba2db4a
Compare
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.
This PR updates the docs to reflect current conventions for managing APDB configs with both Postgres and Cassandra.