Modify charts to represent the latest IOP configuration.

[redblom]

As discussed in the FDTF meetings:
The sciencemesh charts must be modified such that they lead to the deployment of 3 revad instances that are needed for IOP supported (OCM) federated sharing in the sciencemesh.
The configuration for these 3 instances can be found in the .toml files sciencemesh1.toml, sciencemesh2.toml, sciencemesh3.toml at https://github.com/cs3org/ocm-test-suite/tree/main/servers/revad.

[david-antos]

Can we expect any reactions to this issue?

[david-antos]

Well, can we expect any reactions in this century?

[dagl]

I'll take a look at this

[david-antos]

It would be highly appreciated.

[dagl]

@david-antos I created a branch with modifications: https://github.com/sciencemesh/charts/tree/29-modify-charts-to-represent-the-latest-iop-configuration. After checkout you have to add the sciencemesh.toml files (configured for your instance) there and then it can be deployed like this:

helm repo update && helm dependency build && helm upgrade -i iop . -f values.yaml --set-file gateway.configFiles.revad\.toml=sciencemesh1.toml --set-file revad2.configFiles.revad\.toml=sciencemesh2.toml --set-file revad3.configFiles.revad\.toml=sciencemesh3.toml

Let me know if this works for you

[dagl]

Might also need to use double "\\" instead of "\"

[marqsbla]

I used the corrected templates to deploy 3 revas. I still have problems with the deployment but I don't think it is related to the helm chargs.
What I can say, is that a bit problematic, at least for me, are different ports in *toml and the helm charts. I had to spend some time to deduce which service should connect with which, modify the ports accordingly, etcd.
Also, I believe revad3 do not open http port (only grpc). I couldn't disable http port in the helm chart definition (service, pod definition) without modifing the charts.