wskdeploy for exporting OpenWhisk assetswskdeploy export can be used to export OpenWhisk assets previously deployed as a managed project via wskdeploy sync -m manifest.yaml. wskdeploy export will create a manifest for the managed project assets and separate manifests for each managed project that this managed project depends upon, if such dependencies exist and have been described in manifest.yml when the managed project has been initially deployed. The manifest(s) resulting from executing wskdeploy export can be later used for deploying at a different OpenWhisk instance. The code of actions, which are defined in the packages of the exported project will be saved into folders with the names being the names of the package, the actions belong to.
OpenWhisk AssetsOne common scenario, in which the export feature is useful, is populating a newly installed OpenWhisk instance with assets from another OpenWhisk instance. One might consider a scenario, in which an OpenWhisk instance is installed on premises with another OpenWhisk instance residing in the cloud. Consider, for example using one OpenWhisk instance on premises and another one in the cloud (e.g., the second OpenWhisk instance can be IBM Cloud Functions). A fairly common scenario is that a developer will need to deploy assets from the cloud OpenWhisk instance on the on premises one and vice-versa.
OpenWhisk at the EdgeIn a variety of IoT and other edge computing scenarios, such as running Virtual Network Functions (VNF) as OpenWhisk actions in “edge Data Centers” embedded with 5G-MEDIA infrastructure (as pioneered in 5G-MEDIA EU H2020 project), there is a need to distribute OpenWhisk assets developed centrally in the cloud (e.g., IBM Cloud Functions) to multiple OpenWhisk instances running at the edge Data Centers. Again, wskdeploy export is handy as a basic tool that allows to automate this management task.
Consider a simple manifest file manifest_lib1.yml for a sample project lib1. The project contains a single lib1_package package that comprise three actions (the code of the action in this simple example is the same for all three, but the action names are different).
lib1 as a managed project$ ./wskdeploy sync -m manifest_lib1.yaml
lib1 deployment$ ./wsk package get lib1_package
ok: got package lib1_package { "namespace": "your_namespace", "name": "lib1_package", "version": "0.0.2", "publish": false, "annotations": [ { "key": "whisk-managed", "value": { "file": "/root/go_projects/src/github.com/apache/openwhisk-wskdeploy/tests/src/integration/export/manifest_lib1.yaml", "projectDeps": [], "projectHash": "80eec5f8e3ee874e22bdacb76aa4cc69aad459c1", "projectName": "lib1" } } ], "binding": {}, "actions": [ { "name": "lib1_greeting3", "version": "0.0.1", "annotations": [ { "key": "whisk-managed", "value": { "file": "/root/go_projects/src/github.com/apache/openwhisk-wskdeploy/tests/src/integration/export/manifest_lib1.yaml", "projectDeps": [], "projectHash": "80eec5f8e3ee874e22bdacb76aa4cc69aad459c1", "projectName": "lib1" } }, { "key": "exec", "value": "nodejs:default" } ] }, { "name": "lib1_greeting2", "version": "0.0.1", "annotations": [ { "key": "whisk-managed", "value": { "file": "/root/go_projects/src/github.com/apache/openwhisk-wskdeploy/tests/src/integration/export/manifest_lib1.yaml", "projectDeps": [], "projectHash": "80eec5f8e3ee874e22bdacb76aa4cc69aad459c1", "projectName": "lib1" } }, { "key": "exec", "value": "nodejs:default" } ] }, { "name": "lib1_greeting1", "version": "0.0.1", "annotations": [ { "key": "whisk-managed", "value": { "file": "/root/go_projects/src/github.com/apache/openwhisk-wskdeploy/tests/src/integration/export/manifest_lib1.yaml", "projectDeps": [], "projectHash": "80eec5f8e3ee874e22bdacb76aa4cc69aad459c1", "projectName": "lib1" } }, { "key": "exec", "value": "nodejs:default" } ] } ] }
lib1 projectExporting lib1 project into the current directory. Please note that the manifest name should be explicitly specified.
$ ./wskdeploy export --projectname lib1 -m my_new_lib1_manifest.yaml
One can also export a project into a different directory, by specifying a manifest name containing this directory. The directory does not have to exist. wskdeploy will automatically create it, if needed.
$ ./wskdeploy export --projectname lib1 -m mydirectory/my_new_lib1_manifest.yaml
my_new_lib1_manifest.yaml)project: name: lib1 namespace: "" credential: "" apiHost: "" apigwAccessToken: "" version: "" packages: {} packages: lib1_package: name: lib1_package version: 0.0.2 license: "" dependencies: {} namespace: your_namespace credential: "" apiHost: "" apigwAccessToken: "" actions: lib1_greeting1: name: lib1_greeting1 location: "" version: 0.0.1 function: lib1_package/lib1_greeting1.js code: "" runtime: nodejs:default namespace: your_namespace/lib1_package credential: "" exposedUrl: "" main: "" limits: null inputs: {} outputs: {} annotations: exec: nodejs:default web-export: "" lib1_greeting2: name: lib1_greeting2 location: "" version: 0.0.1 function: lib1_package/lib1_greeting2.js code: "" runtime: nodejs:default namespace: your_namespace/lib1_package credential: "" exposedUrl: "" main: "" limits: null inputs: {} outputs: {} annotations: exec: nodejs:default web-export: "" lib1_greeting3: name: lib1_greeting3 location: "" version: 0.0.1 function: lib1_package/lib1_greeting3.js code: "" runtime: nodejs:default namespace: your_namespace/lib1_package credential: "" exposedUrl: "" web-export: "" main: "" limits: null inputs: {} outputs: {} annotations: exec: nodejs:default triggers: {} feeds: {} rules: {} inputs: {} sequences: {} apis: {} filepath: ""
The code of the actions defined in the packages comprising the exported project will be saved into the folders named after the respective packages. The packages' folders will be created in the same directory into which the manifest file of the project is exported. Let's examine the current directory into which my_new_lib1_manifest.yaml was exported in Step 3 above.
$ ls -al lib1_package
The dependencies mechanism allows to express a project structure, in which one project uses another project as a library. Also dependencies can be defined for multiple projects. Consider a project lib2 with the manifest manifest_lib2.yml and a project EXT_PROJECT with the manifest manifest_ext.yml. EXT_PROJECT (stands for extending project) uses actions from both package lib1_package (defined in the lib1 project) and lib2_package (defined in the lib2 project) in order to define rules specific to EXT_PROJECT.
wskdeploy export will automatically export both lib1 and lib2 along with EXT_PROJECT. It will not export bindings, because they will be automatically created when re-deploying lib1, lib2, and EXT_PROJECT at another OpenWhisk instance. Each exported project will have a manifest and package folder structure similar to the explained above. The dependency projects will be placed into dependencies folder beneath the folder where the manifest of the top project (EXT_PROJECT in our example) is placed.
EXT_PROJECT$ ./wskdeploy export --projectname EXT_PROJECT -m ext_test1/ext.yaml
$ ls -al ./ext1
$ ls -al ./ext1/dependencies
lib1 and lib2 in our example) and only after that, EXT_PROJECT can be deployed successfully.wskdeploy export does not check for circular dependencies. In case of circular dependencies specified by the user, wskdeploy's behavior is undefined.EXT_PROJECT in our case) should be explicitly specified.