MMS service should use sidecar pattern, sidecar container runs with MMS helper service, main container with MMS consumer service. They both attach to a shared volume.
MMS helper service will need to
[ ] read auth and cert from binded secret, read objectType, agent-namespace from env.
[ ] making calls to agent service to poll updated models.
[ ] save or delete model based on the response
MMS example operator will need:
[ ] bind 2 ESS secrets to MMS helper, helper service will use those 2 secrets to make https call
[ ] read envs from configmap: ESS envs, agent-namespace, agent storageclass. The storageclass and pvc size could be pass in from userinput. If storageclass not passed in as input during registering, will use agent storageclass as default. Default will be 10G (? not decide yet). The objectType could be read from userinput -> configmap -> env. The default value of objectType needs to be defined in service definition.
[ ] operator needs to create shared volume for MMS helper and MMS consumer service
[ ] operator needs to deploy MMS helper and consumer service using sidecar pattern, and binding the volume
[ ] remove MMS deployment, and volume when agreement is terminated
MMS service should use sidecar pattern, sidecar container runs with MMS helper service, main container with MMS consumer service. They both attach to a shared volume.