You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: bump rag da version + associated extra parameters (#4)
* feat: add inputs
* fix: remove problematic iam
* fix: image link
* fix: image link
* feat: more inputs
* feat: more wiring
* feat: add alm DA in stack
* feat: add watson
* feat: add RAG config da to stack
* feat: add RAG config da to stack
* feat: configure watsonx plans
* fix: add workaround for unique watson project name
* Use project name and config name pattern to deploy many
* chore: merge with master
* feat: bump RAG DA version
* fix: use prefix as registry namepsace for now
* fix: set context strategy
* docs: prefix
* feat: change rag app image name
---------
Co-authored-by: Igor Naumov <[email protected]>
Copy file name to clipboardExpand all lines: README.md
+15-2Lines changed: 15 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# Retrievel Augmented Generation (RAG) stack
1
+
# Retrieval Augmented Generation (RAG) stack
2
2
3
3
To run the full stack. These steps will be updated as development progresses on the stack and underlaying DAs.
4
4
@@ -17,7 +17,11 @@ Click the "Add to project" button, and select create in new project.
17
17
## 3. Set the input configuration for the stack
18
18
19
19
- Clone this repository locally - and checkout the dev branch.
20
-
- Create a file with name ".def.json" with the following content. Important: ensure region is either us-south or eu-de as watsonx can only be deployed in those 2 locations for now.
20
+
- Create a file with name ".def.json" with the following content.
21
+
22
+
**Important**:
23
+
- Ensure region is either us-south or eu-de as watsonx can only be deployed in those 2 locations for now.
24
+
- Ensure that the prefix is globally unique. It is used for the container registry namespace (which needs to be globally unique) in this alpha version.
Tips: If deployment fail in one of the DA, you may need to remove the configuration name of the deployment that already passes from the pattern before re-running the script.
69
73
70
74
Tips: to accelerate iteration you may deploy only a subset of the configurations: the bare minimum are key management, security manager, watson saas, alm and rag configuration da. Base account, observability and SCC are not on the critical path to get the app running.
75
+
76
+
77
+
# 5. Deploy the sample app
78
+
79
+
A few manual steps are required in the alpha version to trigger the deployment of the app:
80
+
1. In the secret manager instance, in the default group, create an arbitrary secret named "ibmcloud-api-key". Put the used api key as secret.
81
+
2. Follow the steps at https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops-image-signing to generate a gpg key
82
+
3. In the secret manager instance, in the default group, create an arbitrary secret named "signing_key". Put the signing key. See https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops-image-signing#cd-devsecops-gpg-store-secretsmgr
83
+
4. Navigate to the "Generative AI Sample App-CI-Toolchain" CD instance, click "ci-pipeline" and execute the "Manual Trigger".
0 commit comments