Provide an ISO 15118-2 AC plus OCPP 1.6J demo

[drmrd]

These changes include the addition of a new SteVe-based OCPP 1.6J demo that can be executed as a one-liner. Updates to the existing SteVe images (such as the one in the everest-utils repository) were made to obtain a SteVe server that operates well on macOS, Linux, and Windows.

Unfortunately, the build process for the SteVe image is not fully automated at this time. Fully automating it requires disabling or tracking CSRF tokens produced by the SteVe server.

The good news is that the build process is straightforward, with its only manual steps being configuring a charge point and several OCPP ID tags within SteVe before calling docker commit for the SteVe and OCPP DB containers. Instructions for the build process are captured in steve/README.md.

[drmrd]

Requesting a review from @shankari

[drmrd]

One note: This demo only works with manager images that include the changes from EVerest/everest-core#388. For instance, the version of everest-core pinned in the manager image in #8 is compatible with the OCPP 1.6J demo.

[drmrd]

@shankari: This PR should be ready to merge after the following:

• SteVe and OCPP-DB images are created in the EVerest organization. I've built and pushed two images to the US-JOET org that you can re-label and push here:
  • ghcr.io/us-joet/everest-demo/steve-configured:0.0.1 changed to ghcr.io/everest/everest-demo/steve-configured:0.0.1 and
  • ghcr.io/us-joet/everest-demo/ocpp-db-compiled:0.0.1 changed to ghcr.io/everest/everest-demo/ocpp-db-compiled:0.0.1
• changes from Impose resource constraints on demos #6 are incorporated into this branch
  • I'm happy to do this once we're otherwise ready to merge.

[shankari]

I don't have create_package permissions

6041800a8d9d: Mounted from us-joet/everest-demo/steve-configured
denied: permission_denied: create_package

@hikinggrass @caller can one of you pull + push, or give me the appropriate permissions so that we can push these manually created images?

Here are the instructions:

$ docker login ghcr.io --username <username>
$ docker pull ghcr.io/us-joet/everest-demo/steve-configured:0.0.1
$ docker tag ghcr.io/us-joet/everest-demo/steve-configured:0.0.1 ghcr.io/everest/everest-demo/steve-configured:0.0.1
$ docker push ghcr.io/everest/everest-demo/steve-configured:0.0.1

[shankari]

@drmrd since OCPP 1.6J integration will be deprecated soon anyway, and we are not rebuilding the images automatically,
I would suggest using the steve images (pre-built, docker committed) directly from US-JOET, and only use the everest containers (manager etc) from everest.

Once we have true end-to-end automated testing (including EV <-> EVSE <-> CSMS), we can include it as part of the smoke tests and know when to update the steve images (if necessary).

[shankari]

Merging, excited to finally see the end to end test working!

[shankari]

oh wait, I missed the

changes from #6 are incorporated into this branch
I'm happy to do this once we're otherwise ready to merge.

@drmrd when you are updating #6, you can apply the same changes to this docker-compose as well 😄