openfoodfacts / openfoodfacts-infrastructure

Where we collaboratively plan and maintain the infrastructure of Open Food Facts
0 stars 4 forks source link

Create containers for deployment automation #47

Open teolemon opened 2 years ago

teolemon commented 2 years ago

Who for

Producer Platform

Blocking

ocervell commented 2 years ago

We would need the estimates for how big the currently running versions of those apps are, and then open one request / container so that we can track them in our main table referencing all VM requests.

stephanegigandet commented 2 years ago

Before creating tons of containers, I would suggest to do things incrementally, so that we can have a better idea of how things will work, as there are still a lot of open questions / things that we have not tested.

We can do things in this order:

  1. Deploy a OFF pre-prod environement (.net) with a full scale database of products (MongoDB + product files + image files).
  2. Test it out completely: from a functional point of view (live requests, batch operations etc.) but also from a performance point of view. In particular we need to see how well MongoDB works on the OVH cluster, when there is a full scale DB. We also need to load test the website.
  3. If things go well, proceed with Open Pet Food Facts (smaller and less visible). First a preprod environment.
  4. Try to migrate the production Open Pet Food Facts to a container.
  5. See how things turn out, if things break when we have tons of crawling robots etc.