You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2018/01/04 13:36:33 UTC

[GitHub] jonpspri opened a new issue #271: Support Multi-architecture Images

jonpspri opened a new issue #271: Support Multi-architecture Images
URL: https://github.com/apache/incubator-openwhisk-apigateway/issues/271
 
 
   We've added capabilities to build the apigateway images on multiple architectures, with s390x as our first candidate.  
   
   While reviewing https://github.com/apache/incubator-openwhisk/pull/3133 , @csantanapr noted that, we should manage apigateway images directly to support s390x.  
   
   I propose we build and ship the images as a single "fat manifest" or "multi-architecture manifest" from Docker.  This would likely be best implemented as part of the travis build but will likely require some reconfiguration and parameterization of the Makefile.  I'm opening this issue to track comments and concerns on the approach.  
   
   Open question:  How tied is apigateway to Make as the build/test engine?  Most of the rest of the incubator-openwhisk projects appear to be using Gradle for build/test, travis for CI/publication, and ansible for deploy.  We may also want to take advantage of the multi-architecture build capabilities offered by DockerHub.
   
   P.S.  I'm willing to do the work on this issue -- I'm not usually one to drop an issue without a PR, but this one seems to warrant some discussion.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services