-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot upload model to rasa x 1.1 #289
Comments
Was facing a similar problem, I solved it by enabling |
Why was this closed? rasa-x-helm/charts/rasa-x/values.yaml Lines 223 to 235 in 68b3682
States that we should be able to disable the rasa production deployment if we use an external server. I have populated the external server url, and set it to true. I am trying to use the rasa-oss chart to deploy the models as suggested, but so much seems broken/inconsistent between them. |
From the helm chart:
|
@virtualroot could you please look into this? |
@nyejon Rasa Enterprise 1.1 is no longer compatible with Rasa Open Source 2. |
No, I am trying to upload a freshly trained model with rasa 3.0.9. |
I would guess there is something wrong with this line:
Also, with the logic from the charts, when using rasa-x as the config endpoint, should all the values for the rasa-oss deployment be populated in the rasa-x helm chart or the rasa-oss helm chart? For example, the tracker-database name -> According to the rasa-X chart, the rasa config is deprecated, but according to the rasa-oss chart, the config is pulled from rasa-x This would apply to the rasa worker too. I don't see a way to specify from the Rasa OSS deployment, if it should pull production config from rasa x or the worker config. |
ok, I seem to have gotten something more working. It now populates the environments if I enable: |
No, using Rasa X as a config endpoint for Rasa OSS makes that Rasa OSS knows about Tracker Store, Lock Store, and so on, but it doesn't mean that Rasa X knows about Rasa OSS. External deployments for the Example: rasa:
token: rasaToken
versions:
rasaProduction:
enabled: false
external:
enabled: true
url: "http://rasa:5005" # address of an external Rasa OSS deployment |
I have all of that configured. How would I let a worker know which tracker database to use? I can now get the OSS deployment to try and load a model I uploaded and was trained with 3.0.9.
Edit, found this: RasaHQ/rasa#10908 |
The text was updated successfully, but these errors were encountered: