Skip to content
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

PaaS deployment - take over Solve API #15

Open
1 of 6 tasks
nirlipo opened this issue Apr 28, 2021 · 2 comments
Open
1 of 6 tasks

PaaS deployment - take over Solve API #15

nirlipo opened this issue Apr 28, 2021 · 2 comments

Comments

@nirlipo
Copy link
Collaborator

nirlipo commented Apr 28, 2021

  • Look at pending issues https://github.com/AI-Planning/planning-as-a-service/issues
  • Integrate with editor.planning.domains
  • Mirror the old solver end-point so that an informative error message is provided
  • Make sure mysql database is persistent when the system is rebuilt. Currently the make command would rebuild the mysql doker image and flash all the data.
  • Make sure the persistent option is exposed
  • do a test period coexisting both interfaces to check reliability of the workers, and how do they recover from failure.
@haz
Copy link
Contributor

haz commented Apr 18, 2023

@nirlipo Shall we use this issue to document the full process to replacing the online editor "Solve" functionality? Old solver should go away entirely.

@nirlipo
Copy link
Collaborator Author

nirlipo commented Apr 19, 2023

Sounds like a good place to keep track of it, I'll edit the title too for clarity and add more items to the checklist.

@nirlipo nirlipo changed the title Planning as a service PaaS deployment - take over Solve API Apr 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants