commit | 8256de1dce1c7ab01f684283062822a6429d7cf3 | [log] [tgz] |
---|---|---|
author | Rob Allen <rob@akrabat.com> | Wed Dec 12 11:31:41 2018 +0000 |
committer | Carlos Santana <csantanapr@apache.org> | Wed Dec 12 03:31:41 2018 -0800 |
tree | d94d26601b67370bd11ce776bb71ae9b51021240 | |
parent | ab65b675e55d03c6e67e550e6d766e07a734401d [diff] |
PHP 7.3 runtime (#46) * PHP 7.3 runtime This runtime uses the Go runtime's ActionProxy as the front end. This speeds things up nicely. However, it also means that the detailed error reporting for invalid data being uploaded to /init is not possible as this is handled by the proxy. As a result, the specific tests that this affects have been moved to the PHP 7.1 and 7.2 test classes. Also, it's not possible to send back specific error messages for output with the action proxy, so the fatal error test no longer checks for the specific error text.
This runtime provides PHP 7.3, 7.2 and 7.1.
To use as a docker action
PHP 7.3:
wsk action update myAction myAction.php --docker openwhisk/action-php-v7.3:latest
PHP 7.2:
wsk action update myAction myAction.php --docker openwhisk/action-php-v7.2:latest
PHP 7.1:
wsk action update myAction myAction.php --docker openwhisk/action-php-v7.1:latest
This works on any deployment of Apache OpenWhisk
To use as a kind action
PHP 7.3:
wsk action update myAction myAction.php --kind php:7.3
PHP 7.2:
wsk action update myAction myAction.php --kind php:7.2
PHP 7.1:
wsk action update myAction myAction.php --kind php:7.1
./gradlew core:php7.3Action:distDocker ./gradlew core:php7.2Action:distDocker ./gradlew core:php7.1Action:distDocker
This will produce the images whisk/action-php-v7.3
, whisk/action-php-v7.2
& whisk/action-php-v7.1
Build and Push image
docker login ./gradlew core:php7.3Action:distDocker -PdockerImagePrefix=$prefix-user -PdockerRegistry=docker.io ./gradlew core:php7.2Action:distDocker -PdockerImagePrefix=$prefix-user -PdockerRegistry=docker.io ./gradlew core:php7.1Action:distDocker -PdockerImagePrefix=$prefix-user -PdockerRegistry=docker.io
Deploy OpenWhisk using ansible environment that contains the kinds php:7.3
, php:7.2
& php:7.1
Assuming you have OpenWhisk already deploy locally and OPENWHISK_HOME
pointing to root directory of OpenWhisk core repository.
Set ROOTDIR
to the root directory of this repository.
Redeploy OpenWhisk
cd $OPENWHISK_HOME/ansible ANSIBLE_CMD="ansible-playbook -i ${ROOTDIR}/ansible/environments/local" $ANSIBLE_CMD setup.yml $ANSIBLE_CMD couchdb.yml $ANSIBLE_CMD initdb.yml $ANSIBLE_CMD wipe.yml $ANSIBLE_CMD openwhisk.yml
Or you can use wskdev
and create a soft link to the target ansible environment, for example:
ln -s ${ROOTDIR}/ansible/environments/local ${OPENWHISK_HOME}/ansible/environments/local-php wskdev fresh -t local-php
To use as docker action push to your own dockerhub account
docker tag whisk/php7.2Action $user_prefix/action-php-v7.3 docker push $user_prefix/action-php-v7.3
docker tag whisk/php7.2Action $user_prefix/action-php-v7.2 docker push $user_prefix/action-php-v7.2
docker tag whisk/php7.1Action $user_prefix/action-php-v7.1 docker push $user_prefix/action-php-v7.1
Then create the action using your the image from dockerhub
wsk action update myAction myAction.php --docker $user_prefix/action-php-v7.3
The $user_prefix
is usually your dockerhub user id.
Install dependencies from the root directory on $OPENWHISK_HOME repository
./gradlew install
Using gradle for the ActionContainer tests you need to use a proxy if running on Mac, if Linux then don't use proxy options You can pass the flags -Dhttp.proxyHost=localhost -Dhttp.proxyPort=3128
directly in gradle command. Or save in your $HOME/.gradle/gradle.properties
systemProp.http.proxyHost=localhost systemProp.http.proxyPort=3128
Using gradle to run all tests
./gradlew :tests:test
Using gradle to run some tests
./gradlew :tests:test --tests *ActionContainerTests*
Using IntelliJ:
-Dhttp.proxyHost=localhost -Dhttp.proxyPort=3128
Apache OpenWhisk Runtime PHP is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.