Comments (11)
I created vespa-engine/vespa#24907 to track this issue wrt. to Vespa CLI.
from pyvespa.
pyvespa
allows only deployment to dev. pyvespa
was built primarily to allow data scientists to experiment more quickly. It was not made for production use.
from pyvespa.
Understood. What is the right way to convert the experiment into a production app? Currently, I have a sample app in dev that I'd like to deploy to prod. I generated the application package but prod deployment requires a test package as well. Do I have to manually create json files specifying the tests to run and then do vespa prod submit
?
from pyvespa.
from pyvespa.
Hi, I'll get back to you shortly on this
from pyvespa.
Hi again! The process to go from a pyvespa app to Vespa Cloud production is not as smooth as it should be, so many thanks for submitting this! I have reproduced/found the following problems:
- The Vespa Cloud console does not allow uploading the application zip only (as you noticed) - I have created a ticket for the console to look into that
- If there were test files in the pyvespa project, it would not generate the test zip
- Documentation for this process in pyvespa is weak/missing
I will take a step back and look into how this process should be, document it and follow up on bug fixes. This will take a little time, I hope you are able to work around using the Vespa Cloud documentation to deploy application packages
from pyvespa.
Thanks for looking into this.
- It's not just the console.
vespa prod submit
CLI command didn't work until I added a test package. - What would test files in a pyvespa project look like?
- It would be great if you could include a simple test in the documentation to demonstrate the process. pyvespa generated or otherwise.
I am trying to find a work around. I'm not sure how to create a simple test to pass the checks and deploy the app to prod. Currently, I have this under tests/system-tests
.
{
"name": "Very simple test",
"comment": "Just want to deploy",
"steps": [
{
"name": "query for foo",
"request": {
"parameters": {
"yql": "select * from sources * where True"
}
}
}
]
}
from pyvespa.
Hi, sorry for the trouble! I think there was a code change on Vespa Cloud today for this, I am not sure if it is fully rolled out yet - you can please let me know tomorrow if the CLI still fails after testing again then.
from pyvespa.
@mpolden does the vespa CLI require a test package for prod deployment?
from pyvespa.
CLI itself shouldn't require a test package, but maybe the controller API does.
from pyvespa.
Without the tests folder, this is what I get:
> vespa prod submit
Warning: We recommend doing this only from a CD job
Hint: See https://cloud.vespa.ai/en/getting-to-production
Error: could not submit application for deployment: '' should be an application package zip or dir, but does not exist
After I added a tests/system-test and a test file:
Warning: We recommend doing this only from a CD job
Hint: See https://cloud.vespa.ai/en/getting-to-production
Success: Submitted . for deployment
See https://console.vespa-cloud.com/tenant/dummycorp/application/myapp/prod/deployment for deployment progress
from pyvespa.
Related Issues (20)
- VespaAsync _open_aiohttp_session method doesn't need to be async
- add ability to manage client lifecycles outside of VespaClients
- FR: expose visit api HOT 3
- FR: async feed_iterable
- FR: expand feed iterable callback args HOT 1
- update only supports assign updates
- Add timeout-parameters to `VespaDeployment`
- Better documentation of restrictions with regards to VespaDocker volume mounts
- document v1 paths should be urlencoded
- Add support for conditional writes
- Integrate `vespacli` python package HOT 1
- pyvespa assumes vespaengine/vespa is pulled HOT 2
- Replace old logos with new in notebooks
- Async data operations does not apply retry strategy
- Improve user feedback on error from container logs
- Generate application packages from existing Vespa applications HOT 4
- Can't feed result of get operation into feed delete/update HOT 1
- Convert notebooks to use new prepend syntax
- Make docker dependency optional HOT 6
- Deploy the Vespa application with docker for bge-m3 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pyvespa.