csantanapr commented on issue #2311: Update nodejs6 runtime with utilities to 
allow building node_modules binaries
URL: 
https://github.com/apache/incubator-openwhisk/issues/2311#issuecomment-308829536
 
 
   I think we found a better way to handle this
   Increasing the size of the runtime image is the wrong direction we want to 
go, I'm actually looking into decreasing the size of the nodejs image.
   
   
   We will going to make it easier to add new kinds for the languages we 
already have in place.
   This PR #2383 will take the list from group vars manifest in ansbile and 
docker pull those images into the invoker.
   
   The way we can easily create an image that has a few packages more than the 
base nodejs, and be deploy in your environment, this would be something for 
operators to benefit, and then for users you would provide a new kind like 
`nodejs-acme:6` where this image extend `FROM` the base nodejs image but have 
more npm packages custom for acme.
   
   There is a related PR #2112, that would allow users to use their own docker 
images that could extend one of the language ones and create actions with a 
docker image and a zip, not requiring the operator to pre-populate the images 
to the invokers. It would be giving an user to create their own kinds
   
   In terms of nodejs actions use for building actions, they would require g++, 
git, and such so we are thinking on creating a new kind i.e. 
`action-nodejs-build-v6` were it doesn't matter if the image is bit big as it's 
not that critical for performance and is more important functionality for 
deployment time.
   We are thinking instead of creating this new image on this repo, we start 
the process and create a new repo `openwhisk-runtimes` were we build the images 
from starting with the init/build actions per language.
   
   
   cc @rabbah 
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to