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
#mkdocs/docs/deployment/adw_private.md # cleaned up sensitive info
95
105
96
106
# Reference to idcs discovery url
97
-
mkdocs/docs/deployment/business_api_gateway.md
107
+
#mkdocs/docs/deployment/business_api_gateway.md # cleaned up/masked sensitive data
98
108
99
109
# Reference to oda instance
100
-
mkdocs/docs/deployment/business_idcs.md
110
+
#mkdocs/docs/deployment/business_idcs.md # cleaned/masked data
101
111
102
112
# Reference to oracle redis
103
-
mkdocs/docs/deployment/nl2sql_engine.md
113
+
#mkdocs/docs/deployment/nl2sql_engine.md # removed sensitive data. There are a lot of references to websocket... maybe we can remove this in the near future
104
114
105
115
# Reference to API GW url
106
-
mkdocs/docs/deployment/oda.md
116
+
#mkdocs/docs/deployment/oda.md # masked sensitive data
107
117
108
118
# Reference to OCI tenancy
109
-
mkdocs/docs/deployment/trust-service.c.md
110
-
mkdocs/docs/deployment/trust-service.md
119
+
#mkdocs/docs/deployment/trust-service.c.md # cleaned sensitive data. There are a couple references to artifactory here
Copy file name to clipboardExpand all lines: README.md
+24-17Lines changed: 24 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,29 +64,30 @@ I ran a dry deployment using the cleaned repo on our tenancy. Listed are some of
64
64
- Would have to be refactored if using e.g. cohere on demand
65
65
- The existing documentation suggests deploying api gateway on private subnet due to lack of authentication.
66
66
- I was able to deploy the api gateway on public subnet with oauth2.0 authentication to idcs server and invoke from oda with token, so not sure why private subnet deployment for api gateway is suggested
67
+
- Possible separate deployment down the line for connecting customer vpn
67
68
- The existing code expects api keys and wallets configured directly on the server, at least for the client business engine
69
+
- Possible future code refactor
68
70
- Redis is required but no instructions given
69
71
- There was no example data given for the vendors table, so I exported the table from the main deployment as a csv and imported to ours
70
72
- Vendors table is for client business db
71
-
-How do we want to provide this csv?
73
+
-Provided csv in clientApp folder
72
74
- The business app is dependent on the trust db (trust library), i.e. the trusted prompts, which isn't intuitive
73
75
- The code expects the TRUST_LIBRARY table to have at least one entry, otherwise it bombs
74
76
- I provided a sample entry in the sql file
75
-
The sql for the client business db is outside the clientapp directory, & there are no instructions given on which db to upload to (upload to business db)
76
-
77
-
The business app is exposed on an API Gateway with the main entry /prompt, which maps to <business-app-ip>:8000... this will be used by ODA app.
77
+
- The sql for the client business db is outside the clientapp directory
78
+
- There are no instructions given on which db to upload to
79
+
- Execute nl2sql_datamodel_schema on business db
80
+
- sample_setup_ras seems to apply to trust db
81
+
- sample_setup_ras wasn't required to run the business app
82
+
- The business app is exposed on an API Gateway with the main entry /prompt, which maps to <business-app-ip>:8000... this will be used by ODA app.
78
83
79
84
There are a handful of files required and provided within the repo, but no instructions on how/when to use them.
80
85
Examples include :
81
-
1. Under sql, nl2sql_datamodel_schema.sql needds to be ran in the trust database
82
-
- Was able to run the client engine without the sql/sample_setup_ras.sql file.
83
-
- This is a prequisite to run the business client engine, which isn't intuitive
84
-
2. Within the rest (trust) directory there are docker files... I think we can remove these?
86
+
1. Within the rest (trust) directory there are docker files... I think we can remove these?
85
87
- Haven't tested full trust deployment yet.
86
-
87
-
Some files I don't think are necessary at all
88
-
1. autoprompt
89
88
2. mkdocs... this is documentation we can perhaps repurpose (at least the md files)
89
+
- Repurposed documentation in latest commit
90
+
3. sqlGenApp. Not sure where this is used
90
91
91
92
Below are the various requirements and findings from deploying the infrastructure components on our tenancy -
92
93
@@ -105,31 +106,33 @@ Below are the various requirements and findings from deploying the infrastructur
105
106
106
107
1. The zipped askdata vbcs app in here looks to be outdated.
107
108
- It's a more simple implementation, which might be best for now
109
+
- The deployment with the extra navigation pane uses new apis on the engine
110
+
- These apis haven't been pushed to main yet
108
111
2. Reference to websocket - to be deprecated? Need to test if working without
109
112
- Tested, seems to be unnecessary
110
-
3. App import relies on various images in the directory... do we want to provide these images in the repo?
111
-
- I'm going to include them for now, since they are dependencies
112
113
113
114
### API Gateway
114
115
1. API Gateway is configured with Single Authentication OAuth2.0 which requires a vault.
115
116
2. The existing mkdocs documentation said to deploy the api gateway to private subnet due to lack of authentication... authentication can be added to api gateway on public subnet
117
+
- Can possibly add different implementation later for connecting to customer vpn
116
118
117
119
### Redis
118
120
1. Redis is required but there were no instructions given on configuration
119
121
120
122
### Generative AI
121
123
1. Existing deployment was using dedicated ai cluster/data science. I was able to get it to work with on demand model.
122
124
- Code is hard coded to handle only the llama models. Cohere models would require refactoring.
125
+
- Haven't tested the deployment with dedicated cluster. This would require gpus which we don't have for our tenancy
126
+
- Haven't tested data science deployment
123
127
124
128
### NL2SQL Business Engine
125
-
1. The code is currently expecting the user to upload their own api keys
129
+
1. The code is currently expecting the user to upload their own api keys to the server
126
130
2. Database wallets need to be uploaded manually
127
131
3. png files trusted & untrusted.png are required to run the server.
128
-
4. autoprompt - need to test if working without (deprecated?)
129
132
130
133
### Client Database
131
134
1. The vendors table didn't have any example data. I had to export the table from the existing implementation and import as csv
132
-
-Do we want to include this csv in the repo, or add to object storage bucket and provide link?
135
+
-Included csv in repo
133
136
134
137
### Trust Database
135
138
1. Engine code expects at least one entry in Trust library table before execution
@@ -139,5 +142,9 @@ Below are the various requirements and findings from deploying the infrastructur
139
142
Haven't gotten this far, but the basic prompt endpoint does use the trust library table.
140
143
141
144
## APEX
142
-
tbd ... do we want to include this in the first version?
145
+
tbd ...
146
+
147
+
### Troubleshooting
143
148
149
+
1. Graph isn't showing in Table Graph VB App
150
+
- Solution: Make sure to assign user role to idcs group in app settings
0 commit comments