In This Section

Overview

The Lumino Starter bundle is a fully self-contained, standalone instance containing all required Lumino components in a ready-to-launch package. 

This page contains instructions for installing and upgrading the Lumino Starter package.

Prerequisites

Install

Once the prerequisites are installed, getting the starter bundle up and running is quite simple.

First, download the starter tarball on the host on which you want to install the starter bundle. Be sure to substitute a real username in place of service-user – we suggest creating a lumino user and running Lumino services as that user.

ssh service-user@some.host.com
 
#
# all commands from this point should be run as service-user on some.host.com.
#
# note that $NEXUS_USERNAME and $NEXUS_PASSWORD should be replaced by your own Neeve Nexus credentials.
#

curl -L \
    -u "$NEXUS_USERNAME:$NEXUS_PASSWORD" \
    -o nvx-lumino.tar.gz \
    'http://nexus.neeveresearch.com/nexus/service/local/artifact/maven/redirect?r=neeve-licensed&g=com.neeve&a=nvx-lumino&v=LATEST&p=tar.gz'

Once the download is complete, you can unpack the tarball:

tar xvfz nvx-lumino.tar.gz
cd nvx-lumino

(Optional) If you like, you can get a better idea of the installed directory structure using the 'find' command:

find -maxdepth 3 -type d -ls

Next we create a symlink to the new release. Strictly speaking, this is optional, but it can make upgrades easier should you have other scripts that need to reference the installation:

ln -s releases/v<VERSION> current

Customizing the Configuration

Configuring The Server

Optionally, you may want to configure ports used by the Lumino server. The default port values used by the server are:

Setting
Default
Description
Lumino Server Port8001

The port on which Lumino will listen for traffic.

The Lumino server proxies to its back end Grafana server on the Grafana Port as well as to the Lumino agents that it is configured to proxy to.

To change:

  • update "args": [8001] to the desired port in current/ecosystem.json
  • update "lumino_port" in current/app/vendor/grafana/conf/lumino.ini
    • Edit <install-root>data/grafana/conf/lumino.ini if it exists.
    • If this is a fresh install and the server has not been launched lumino.ini is found in <intstall-root>current/app/vendor/grafana/conf/lumino.ini.
      (info) When the Lumino server is first launched this file is copied to <install-root>data/grafana/conf/lumino.ini to preserve config changes across upgrades.
Lumino Public Host Address...

Thepublichostnameusedin links created by the Lumino Server will use thehostnamespecifedbythe domain property in thelumino.ini

To change:

  • update the "domain" property in lumino.ini to the public hostname (e.g. www.myhost.com)
    • Edit <install-root>data/grafana/conf/lumino.ini if it exists.
    • If this is a fresh install and the server has not been launched lumino.ini is found in <intstall-root>current/app/vendor/grafana/conf/lumino.ini.
      (info) When the Lumino server is first launched this file is copied to <install-root>data/grafana/conf/lumino.ini to preserve config changes across upgrades.
Lumino Agent Connection...

You can add additional agents that the server will add to the set of available agents on startup.

By default, the Local Agent is configured with "url": "http://localhost:7778/lumino-agent". If you plan on changing the agent's HTTP port below, it should be updated here.

To change, update "url": "http://localhost:7778/lumino-agent" to the desired host port combination.

Grafana Port3000

The Grafana back-end port.

By default, Grafana is bound to 127.0.0.1 (localhost) only so as not to be made accessible externally.

(info) Changing this port is only recommended if it would cause a port conflict otherwise.

To change this port you must also update http_port in current/app/vendor/grafana/conf/lumino.ini

Configuring the Lumino Agent

Optionally, the agent's properties can be configured in the current/lumino-agent/robin.conf. When the agent first starts up the robin.conf file is copied to data/robin/robin.conf so that in future upgrades the configuration is preserved. So if you have already attempted to start the agent, then the values below should be edited in data/robin/robin.conf. 

Port
Property
Default
Description
Lumino Agent Portlumino.agent.http.port7778

The port exposed by the agent to Lumino Server.

Changing this port is only recommended if you anticipate a port conflict.

(warning) Note that changing this value requires that the agent's connection information be updated in the Lumino Server's Lumino Agents UI once the server is started.

Lumino Discoverynv.discovery.descriptormcast://224.0.1.200:4090

Sets the discovery descriptor to be used to discover running XVMS.

  • Each Lumino agent should have a unique discovery address which isolates the set of XVMs that it manages.
  • The discovery address specified here overrides that in config.xml from applications this agent deploys unless those applications define server discovery addresses explicitly.

Update nv.discovery.descriptor=mcast://224.0.1.200:4090

Admin Transportsnv.server.admin.transportsdirect

The default behavior of a Lumino agent is to directly connect to discovered XVMs over direct tcp connections. If you'd prefer to use messaging as the monitoring transport this may be changed to 'sma' and the bus.descriptor must be specified (see below).

Example: nv.server.admin.transports=sma

SINCE 1.4

nv.server.admin.sma.bus.descriptor-

If configuring to use Admin over SMA, this property sets the bus connection descriptor that is used to monitor and control discovered XVMs.

Example (admin over solace):
nv.server.admin.sma.bus.descriptor=solace://solaceaddress:55555&SESSION_VPN_NAME=default&use_default_queue_name=false&use_default_queue_name_as_default_client_id=true&topic_starts_with_channel=false&single_session=true

SINCE 1.4

Influx Urllumino.agent.influx.urlhttp://localhost:8086

The connection url to influx.

By default, this is set to the bundled influx instance. It should be changed if you change influx connection information below or plan to point the agent at a difference influx instance.

(warning) When changing the agent's data source, the corresponding changes need to be made in the server's Data Source configuration UI once the server is started.

Influx Usernamelumino.agent.influx.usernamerootThe username used to connect to influx to write agent collected data.
Influx Passwordlumino.agent.influx.passwordrootThe password used to connect to influx to write agent collected data.

Configuring Influx DB

Optionally, the bundled influx instance configuration properties can be configured in the current/conf/influxdb.conf file. When the agent first starts up the influxdb.conf file is copied to data/influxdb/influx.conf so that in future upgrades the configuration is preserved. So if you have already attempted to start the agent, then the values below should be edited in data/influxdb/influx.conf . 

Setting
Default
Description
Influx Bind Address8086

The port on which Lumino will listen for traffic.

The lumino server proxies to its back end Grafana server on the Grafana Port as well as to the Lumino agents that is configured to proxy to.

To change uncomment the bind-address = ":8086" and be sure to make the corresponding change to the agent configuration.

Launching Lumino

Finally, we're ready to start all the components in the starter bundle. JAVA_HOME must be set to point to the home directory of java 8 JVM, and don't forget to ensure that the X License is installed on the target host (for example in the user home folder of the user used to launch Lumino). 

#
# N.B. you don't need to override JAVA_HOME if it already points to a Java 8 installation
#

cd current
./start.sh

You should now be able to log in to the Lumino Server instance running on port 8001 (unless you changed it above) using the credentials admin:admin. Be sure to change your admin account password after you log in.

Upgrade

Upgrades of the starter bundle can be done in-place using a process very similar to the initial installation.

First, we start by downloading the latest release on the target host:

ssh service-user@some.host.com
 
#
# all commands from this point should be run as service-user on some.host.com.
#
# note that $NEXUS_USERNAME and $NEXUS_PASSWORD should be replaced by your own Neeve Nexus credentials.
#

curl -L \
    -u "$NEXUS_USERNAME:$NEXUS_PASSWORD' \
    -o nvx-lumino.tar.gz \
    'http://nexus.neeveresearch.com/nexus/service/local/artifact/maven/redirect?r=neeve-licensed&g=com.neeve&a=nvx-lumino&v=LATEST&p=tar.gz'

Next, we unpack the tarball passing --no-overwrite-dir to the tar command to avoid some quirks related to the way tar handles directories:

tar xvfz nvx-lumino.tar.gz --no-overwrite-dir
cd nvx-lumino

Now we're ready to stop the previous instance. Use the stop.sh script in the old Lumino installation directory to shut everything down:

#
# N.B. you don't need to override JAVA_HOME if it already points to a Java 8 installation
#
 
current/stop.sh

Now that everything has stopped, update the "current" symlink to point to the latest release:

ln -sfn releases/v<VERSION> current

Now we're ready to start everything up again:

current/current/start.sh

Again, the new release should be up and running on port 8001.