openwhisk-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [incubator-openwhisk] style95 commented on issue #4460: How to specify -v parameter for docker containers that run functions?
Date Fri, 26 Apr 2019 06:16:09 GMT
style95 commented on issue #4460: How to specify -v parameter for docker containers that run
functions?
URL: https://github.com/apache/incubator-openwhisk/issues/4460#issuecomment-486939310
 
 
   @YangZhou1997 
   What kinds of scenario do you keep in your mind?
   IMHO, it is not that simple to provide volume mapping features in OpenWhisk.
   
   Currently, it is not guaranteed for actions to run on the same invoker, it's not easy to
mount the same directory on each call. Even if a container runs with volume mapping, it will
be paused after 50ms.
   Since we can add volume at container creation time, it will induce a bigger ColdStart time.
   And if you are thinking of a shared volume at the host level, you need to take care of
a concurrent modification issue. Also, one user's volume should not be accessed by the others,
you need proper permission and multi-tenancy support as well. I think there might be more
issues than I described.
   So it is generally recommended to use object storages for serverless.
   
   If you still want to try the way, I think `DockerClient` would be a good starting point.
   Since users should be able to configure their volume, one option could be relying on annotations.
   So users would specify volume information in annotation and OpenWhisk adds volume mapping
based on the information at container creation time. 
   
   Since I pondered on this shortly and naively, please consider that there would be some
issues.
   
   And you may find this useful for this kind of discussion.
   https://github.com/apache/incubator-openwhisk/blob/master/CONTRIBUTING.md#discussion
   
   We have slack channels and dev mailing list.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message