Portworx offers a SaaS service called Lighthouse. Lighthouse can monitor and manage your PX clusters and storage. However you can also run your own Lighthouse.

This guide shows you how you can run Lighthouse locally.

Note: The example in this section uses Amazon Web Services (AWS) Elastic Compute Cloud (EC2) for servers in the cluster. In your deployment, you can use physical servers, another public cloud, or virtual machines.

Minimum Requirements

Lighthouse runs as a Docker container and has the same minumum requirements as the Portworx storage solution. Please consult this guide for the minumum requirements.

Install Lighthouse: Run the PX-Lighthouse container

Lighthouse communicates with your Portworx cluster via the Key Value Database (KVDB) that Portworx was configured to use. Note the use of the KVDB_IP_ADDR variable in the commands below:

For ETCD, start the container with the following run command:

sudo docker run --restart=always                                        \
       --name px-lighthouse -d --net=bridge                             \
       -p 80:80                                                         \
       portworx/px-lighthouse                                           \
       -d http://${ADMIN_USER}:${ADMIN_PASSWORD}@${IP_ADDR}:8086        \
       -k etcd:http://${KVDB_IP_ADDR}:2379

For Consul, start the container with the following run command:

sudo docker run --restart=always --name px-lighthouse -d --net=bridge    \
       -p 80:80                                                          \
       portworx/px-lighthouse                                            \
       -d http://${ADMIN_USER}:${ADMIN_PASSWORD}@${IP_ADDR}:8086         \
       -k consul:http://${KVDB_IP_ADDR}:8500

Runtime command options

-d http://{ADMIN_USER}:{ADMIN_PASSWORD}@{IP_Address}:8086
   > Connection string of your influx db
-k {etcd/consul}:http://{IP_Address}:{Port_NO}
   > Connection string of your kbdb.
   > Note: Specify port 2379 for etcd and 8500 for consul
   > If you have multinode etcd cluster then you can specify your connection string as
       > 'etcd:http://{KVDB_IP_ADDR_1}:2379,etcd:http://{KVDB_IP_ADDR_2}:2379,etcd:http://{KVDB_IP_ADDR_3}:2379'

In your browser visit http://{IP_ADDRESS}:80 to access your locally running PX-Lighthouse.

LH-ON-PREM-FIRST-LOGIN

Upgrading PX-Lighthouse

You can upgrade your PX-Lighthouse as shown below:

For ETCD, upgrade with the following commands:

sudo docker stop px-lighthouse
sudo docker rm px-lighthouse
sudo docker run --restart=always                                        \
       --name px-lighthouse -d --net=bridge                             \
       -p 80:80                                                         \
       portworx/px-lighthouse                                           \
       -d http://${ADMIN_USER}:${ADMIN_PASSWORD}@${IP_ADDR}:8086        \
       -k etcd:http://${KVDB_IP_ADDR}:2379

For Consul, upgrade with the following commands:

sudo docker stop px-lighthouse
sudo docker rm px-lighthouse
sudo docker run --restart=always --name px-lighthouse -d --net=bridge    \
       -p 80:80                                                          \
       portworx/px-lighthouse                                            \
       -d http://${ADMIN_USER}:${ADMIN_PASSWORD}@${IP_ADDR}:8086         \
       -k consul:http://${KVDB_IP_ADDR}:8500

PX-Lighthouse repository is located here. Above mentioned docker commands will upgrade your PX-Lighthouse container to the latest release. There should be minimal downtime in this upgrade process.

Provider Specific Instructions

Azure

  • Make sure you have set inbound security rule to ‘Allow’ for port 80.

AZURE-SECURITY-RULES

  • Access the web console in browser at http://{public-ip-address}:80