Thanks @sjtomlinson for an update on where "EA" reviewed this. Will check the recording.
Back to my earlier point - final decision should be with the person(s) who acts as "maintainer" for security & compliance. I'm guessing that's @hmarkovic. Any other approach risks forcing through a change than no-one feels ownership of or wants to maintain.
Hi @chad - it's not been discussed in the formal EA calls - either the biweekly Wednesday calls or the Monday Data Architecture calls.
As I think you've heard me say many times, we are working on empowering the PMC projects to make their own implementation design decisions - and supporting this through re-invigorating the Data Platform Principles to provide directional alignment, improving the ADR process going forward, and providing a forum for all PMC projects to receive Architecture Advice (not approvals, but advice).
As such, I'd say that if the code affected is in the "Security and Compliance" platform capability, then the best person to make the final call on an appropriate implementation (and which milestone we target this for) is the "maintainer" for both old Legal and new E&O implementation - I know we're not 100% formal on these definitions of maintainer yet but I think that's probably SLB as org and @hmarkovic as best point-person. EA will be more than happy to provide advice - either at one of the open Architecture Advice Forum meetings (every 2nd Wednesday) or a dedicated call.
Thank you! Did as you have documented - enabled istio add-ons (duh!), increased the cpus and memory - and deployment seems to have completed successfully :-) Services seem to be starting.
Will report back on my "science experiment" of OSDU on a macbook later.
Thanks again!
I'm trying something I know is completely unsupported :-). Bit of a science project. But if you have time to help, I'd appreciate it.
I'm trying to deploy the on-prem version via the instructions here : https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-gcp-provisioning/-/tree/master/examples/simple_osdu_onprem
I'm doing this on my MacBook with MiniKube, so trying to keep it as small as possible.
My understanding of reading the instructions was that istio was not required for "dev mode" (and that so long as the namespace was not labelled with istio, the helm chart would deploy in "dev mode".
However - the errors I get when I run helm install all refer to istio. Have I misunderstood the way to install in dev mode?
janemcconnell@Janes-MacBook-Pro simple_osdu_onprem % helm install -f custom-values.yaml osdu-onprem ../../helm/osdu-infra-onprem/
etc etc.
I've done nothing "smart" in the setup. M1Max MacBook, so installed MiniKube on Docker. Added a couple of worker nodes. Working in "Default" namespace.
Jane McConnell (f7db22ee) at 16 Jun 16:43