You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by gi...@git.apache.org on 2017/08/16 18:06:48 UTC

[GitHub] csantanapr commented on issue #2622: ansible playbooks for deploying each of the providers

csantanapr commented on issue #2622: ansible playbooks for deploying each of the providers
URL: https://github.com/apache/incubator-openwhisk/pull/2622#issuecomment-322853149
 
 
   This integration would be same as we have today for catalog.
   catalog doesn't get deploy as part of default `openwhisk.yml` playbook
   But catalog get's deploy using ansible bits from main repo.
   
   I will mark this PR as `wip` since I don't want to merge it in this repo until there is CI test and integration in the individual repos for alarm, cloudant, and kafka so we know how the final version will look like for this ansible work here.
   
   The CI will look similar as catalog:
   - pull down openwhisk from master
   - deploy local repo content (package and container) using ansible from openwhisk core
   - run tests from local repo content
   
   I agree maybe there is an optimal way to this with ansible but we would also do it for catalog, and push. Right now I don't what's best practice in terms of ansible distributed structure.
   
   I would prefer to make progress and this will allow for individual repos to have CI/Travis integration, and also allow something like vagrant to deploy alarms
 
----------------------------------------------------------------
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