EVI-EnLitePy Endpoint for EV Charging Profiles

[Bill-Becker]

• Update python version to 3.12, from 3.8.
  • Mainly for running EVI-EnLitePy (below) but also good for functionality and security
  • Only bump Django to LTS v4.2 for compatibility
• Add /ensite endpoint to run EVI-EnLitePy (light-weight python API for EVI-EnSite)
• Updates to pod/service resource allocation to:
  • Less CPU and memory allocations for the development and staging servers, except:
  • More memory needed for celery on all servers because of the new python
  • Less memory for non-optimization Julia pods (the standalone ones, whereas the celery+julia pods do the optimizations)

[bpulluta]

@Bill-Becker This sets default enrichment (normalized + annual metrics + utilization) and adds enrichment_version=1 so the UI only sends the minimal input JSON (chargers / vehicles / arrival / maxChargeDurationMin). run_enlitepy_compare.py defaults were updated to match. Docs now clearly explain the simplified contract. No breaking changes—only additive. We can remove the helper scripts once we have a working test with the ui

[Bill-Becker]

@bpulluta we'll want to delete this before merging if it's just for reference to migrate code to the /ensite view.

[Bill-Becker]

@bpulluta should this go inside of the /load_builder directory, or did you want to keep it at the top-level?

[Bill-Becker]

@bpulluta I assume you tested this locally based on the documentation, but just checking if you wanted me to deploy this update to the development server yet?

[bpulluta]

@bpulluta I assume you tested this locally based on the documentation, but just checking if you wanted me to deploy this update to the development server yet?

@Bill-Becker I couldn't run the docker container locally to test but i did test with the deployed server so i think this will work. Can you test locally and confirm that it works. We can remove the extra script and README that i used for testing

[Bill-Becker]

@bpulluta I assume you tested this locally based on the documentation, but just checking if you wanted me to deploy this update to the development server yet?

@Bill-Becker I couldn't run the docker container locally to test but i did test with the deployed server so i think this will work. Can you test locally and confirm that it works. We can remove the extra script and README that i used for testing

I think the README is useful to keep if we think it will help users/developers, but maybe we move it into that /load_builder folder where the /ensite endpoint lives.

[Bill-Becker]

@rathod-b could you do a quick sanity check on these updates to Python 3.12. You don't have to review the new /ensite endpoint with all the new code. @bpulluta and I can handle that review part.

[rathod-b]

Validated expected API functionality and fixed some migration issues.

[bpulluta]

@Bill-Becker @rathod-b, everything seems to be working on my side

@Bill-Becker will you be merging?

[bpulluta]

I tested Ensite intergation and it works correctly