openwhisk-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chetan Mehrotra <chetan.mehro...@gmail.com>
Subject Re: Simplifying configuring OpenWhisk Components (#3984)
Date Thu, 23 Aug 2018 17:07:40 GMT
I believe the uri feature is now under "fetch" [1] and makes use of Mesos
Fetcher [2]. This should mostly work for our usecase with below caveats

1. Where to host - Most likely S3 with IAM based secure access
2. Corelate running service config with one in S3 - In k8s case if there is
a change in ConfigMap then the related pod would be restarted. In Mesos
case its possible that config may get changed later but Mesos task is not
restarted. This can be avoided by ensuring automation ensures that if
config gets changes then Mesos task is also restarted.

Current proposed approach would at least keep the config at one place and
bound to container lifecycle. As its useful for non Mesos/k8s setups ... so
good to have it in anycase. For Mesos based setup the fetch approach can be
explored

Chetan Mehrotra
[1]
https://docs.mesosphere.com/1.11/deploying-services/marathon-parameters/#fetch
[2] http://mesos.apache.org/documentation/latest/fetcher/

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message