strong-liberty-pm v1.0.1

apiconnect-collective-member

A Liberty Collective process manager that runs Node.js servers.

This is a Beta release and the README is not up-to-date, for more information see:

• Managing a polyglot environment
• Deploying StrongLoop servers
• CLI commands

Usage

• wlpn-controller
• wlpn-server
• wlpn-collective
  • wlpn-collective join
  • wlpn-collective remove

TBD

• should the above commands be in slc, or should only the API Mesh flow commands (slc config, slc build, slc deploy) be in slc?

Controller installation

Install/upgrade with

    npm install -g apiconnect-collective-controller

Setup password (only on first time install, not on upgrade):

    wlpn-controller setup --password=<PASSWORD>

Start the controller:

    wlpn-controller start

Open controller admin UI, login with user name and password that was set with the setup command.

TBD

• Install controller as a service (using strong-service-install)
• Install secondary controllers... and join them to the collective

Router installation

TBD

• Install IHS... and join it to the collective; or
• Install DataPower... and join it to the collective

Building a package

Pack an appliction for deployment:

    npm install -g apiconnect-collective-member
    wlpn-server pack .

Alternatively, use slc:

    slc build --npm

Deploying a package using scripting (or manually)

1. Prepare the execution host:

   npm install -g apiconnect-collective-controller

2. Transport the package to the execution host

3. Unpack the package for execution:

   wlpn-server unpack <server name> <npm pack file>

4. Join server to the collective:

     wlpn-collective join <server name>
       --host=<controller host name> --port=<controller port>
       --user=<admin user> --password=<admin password>
       ... hostname of this system, rpc/ssh credentials for this system, etc.

   If you receive Error: self signed certificate in certificate chain, then add --autoAcceptCertificates to the command line arguments.

5. Start the server:

   wlpn-server start <server name>

TBD

• port should have a default for join
• it shouldn't be necessary to hand-edit JSON to configure the server. Specifically, the admin port, work port, cluster name, and the routing options (vhost, api root, port) should be listable and configurable via CLI

Deploying a package using collective/controller

TBD

• Intended to use a CLI, or the admin centre UI, for the API Mesh flow, but that's not ready yet. Basically, there would be a wlpn-collective registerHost that would take many of the same options as wlpn-collective join, but not identify a specific server to join, just the host information.