Table of contents:

Table of Contents

AWS AMI: Install Luminoso Daylight and Luminoso Compass Onsite

Background

Luminoso provides virtual appliances to run Luminoso Compass and Luminoso Daylight in clients’ data center. Follow these instructions to install the virtual appliance so you can configure and use the product.

Launch a new instance from the AMI shared by Luminoso

Luminoso offers several methods for delivering Onsite images to clients. This document assumes you provided Luminoso with your AWS account number and that the AMI is shared with your account.

Log into your AWS Account and navigate to EC2. The EC2 Dashboard opens.
Under Images select AMIs and search for the AMI using the AMI ID that Luminoso provided.
Select the AMI that matches your build number and click Launch to open the Launch Wizard.
Choose an Instance Type. At minimum, Luminoso recommends an instance type that has at least 4 vCPUs and 16GiB of memory. If you select an instance type below this level, Luminoso functionality does not run properly.
Click Next: Configure Instance Details. The Step 3: Configure Instance Details page opens.
Use the options to configure your instance based on your company requirements.
Click Add New Volume to add and configure the data disk.
- For new installations, change the size of the additional volume. Disk size depends on the number of projects processed. Your Luminoso Account Manager is responsible for communicating the recommended size of the data disk
  - Select "Delete on Termination" or "Encryption" based on your company requirements.
- For upgrades, enter the Snapshot ID of the previous instances’ data volume snapshot so the new system starts with a data volume based off that snapshot.
Click Next: Add Tags. Step 5: Add Tags opens.
Add tags as applicable to your organization. If you don’t need tags, skip this step. Within AWS, tags allow you to place arbitrary labels on resources that help you report. If you have a tagging policy that says “every resource needs to have a tag” then you can see what resources everyone is using
Click Next: Configure Security Groups.
Configure security groups as required by your organization.
Click Review and Launch. The Review Instance Launch page opens.
Review the details and confirm that the settings you selected are correct.
Click Launch. A Select an existing key pair or create a new key pair window opens.
Select Proceed without a key pair. The Luminoso Daylight image is prepopulated with credentials that your CSM provides.
Click Launch Instances. Your instance begins the launch process.
For configuration steps, refer to the appropriate Luminoso Daylight or Compass Onsite product documentation.

Upgrade Procedure for AMI Deployment

Shut down the previous onsite VM.
Click Volumes and select the data volume of your old instance.
Go through the steps on the Create Snapshot page. Click Create Snapshot and record the snapshot ID provided on the page.
Follow the steps in the installation guide to create a new Onsite VM. Instead of adding a new data disk, attach the snapshot from the previous on-site version.
1. On the Add Storage page, select the same storage size that you used for your previous instance. You must change the device name when you add this disk.
2. Difference between sdb and sdf. These are how you address the disk.
Start the new VM and connect via ssh with admin credentials. The system runs any necessary data migrations. If the upgrade involves large schema changes, or if you have many existing projects, this may take a while. We recommend running it overnight.
Note: The new admin password should work, so you don’t need to remember the admin password for the previous machine.
Check the configuration to ensure that your settings were imported correctly.
Start the application.

KVM/QEMU: Install Luminoso Daylight and Luminoso Compass Onsite

There are many ways to use KVM and QEMU and many ways to interact with hypervisor systems, so this installation guide only offers high-level directions.

Copy the Appliance file

Copy the onsite file to a location where your virtualization management software can access it.
Uncompress the file.
After the file is uncompressed, check that it is available in the storage location you selected.

Create the Virtual Machine

These instructions assume you are using Virtual Machine Manager (virt-manager). The image Luminoso provides uses qcow2, so these instructions assume that you also use qcow2.

Open the Virtual Machine Manager and create a new virtual machine. A New VM wizard opens.
Select Import existing disk image and click Next.
Locate and select the new VM image storage path you uploaded in the prior section. It should have:
- OS Type: Linux.
- Version: Ubuntu 18.04 LTS (Bionic Beaver).
Select memory and core options. At minimum, Luminoso recommends an instance type that has at least 4 vCPUs and 16GiB of memory. Luminoso functionality does not run properly on instance types below this level. Depending on your project size, you may need to select larger options to avoid build failures. Click Forward.
Provide a name for your VM and select Customize configuration before install.
Click Finish.
Add a data storage device for application data. If you’re upgrading from a previous version, skip this step. Find out your storage size information from your Luminoso Account Manager.
- Format must be: ‘qcow2’
- Bus type must be: ‘VirtIO’
Attach newly added data storage or re-attach your existing data storage device.
Select network configuration options appropriate to your environment.
Review configuration and confirm that the settings correspond with your virtualization environment.
Open Advanced options and:
- Change root drive to format ‘qcow2’
- Change Bus type to ‘VirtIO’
Click Begin Installation to start your onsite instance.
For configuration steps, refer to the appropriate Luminoso Daylight or Compass Onsite product documentation for the configuration steps.

Upgrade Procedure for KVM/QEMU

Shut down the previous onsite VM and create a copy of the data disk.
Follow the steps in the installation guide to create a new onsite VM. Instead of adding a new data disk, attach the data disk from the previous onsite version.
Start the new VM and connect via ssh with admin credentials. The system runs any necessary data migrations. If the upgrade involves large schema changes, or if you have many existing projects, this may take a while. We recommend running it overnight.
Note: The new admin password should work, so you don’t need to remember the admin password for the previous machine.
Check the configuration to ensure that your settings were imported correctly.
Start the application.

VirtualBox: Install Luminoso Daylight and Luminoso Compass Onsite

Because there are many ways to interact with hypervisor systems, this installation guide only offers high-level directions.

Create the Virtual Machine

Launch VirtualBox.
Click Import Appliance… in the File menu and select the OVA file.
Adjust the CPU and RAM settings for the new virtual appliance. At minimum, Luminoso recommends an instance type that has at least 4 vCPUs and 16GiB of memory. Luminoso functionality does not run properly on instance types below this level. Depending on your project size, you may need to select larger options to avoid build failures.
Click Import. It may take a few minutes for your system to load the virtual disk image.
Select the newly imported VM and choose Settings.
Add a name for your VM.
Add a data storage device for application data. If you’re upgrading from a previous version, skip this step. This storage device is for application data only. Your Luminoso Account Manager communicates storage size to you.
Select network configuration options appropriate to your environment.
Click OK to save the updated settings.
Start your new Luminoso onsite instance.
Refer to the appropriate Luminoso Daylight or Compass Onsite product documentation for the configuration steps.

Upgrade Procedure for VirtualBox

Shut down the previous onsite VM and create a copy of the data disk.
Follow the steps in the installation guide to create a new onsite VM. Instead of adding a new data disk, attach the data disk from the previous onsite version.
Start the new VM and connect via ssh with admin credentials. The system runs any necessary data migrations. If the upgrade involves large schema changes, or if you have many existing projects, this may take a while. We recommend running it overnight.
Note: The new admin password should work, so you don’t need to remember the admin password for the previous machine.
Check the configuration to ensure that your settings were imported correctly.
Start the application.

VMware: Install Luminoso Daylight and Luminoso Compass Onsite

Upload the virtual appliance

This document assumes you have the most recent Luminoso on-site image(s) available in your environment. The upload process uses VMware’s vSphere product for transferring the image to vCenter. These instructions were developed using vCenter 6.7. If you’re using a different version of VCenter, your options may be slightly different.

Log into vCenter using vSphere.
Right click on the esxi host you would like to deploy to and select Deploy OVF Template... The Deploy OVF Template wizard opens.
Click Choose File and select the image file. File name format is [product name]_vmware-version-ID-[client]. For example, daylight_vmware-1.0-201602221217-acme.
Click Open.
Click Next and complete the wizard with information applicable to your environment.
Review your choices and click Finish to close the wizard. The VM begins to deploy. View the build progress in the Recent Tasks pane.

Create Data Disk

Our software requires you to use a disk separate from the OS disk to store all Luminoso data and configuration files. At minimum, Luminoso recommends an instance type that has at least 4 vCPUs and 16GiB of memory. Luminoso functionality does not run properly on instance types below this level. Depending on your project size, you may need to select larger options to avoid build failures.

Create a data disk and attach it to the Luminoso Onsite virtual machine you just deployed.

Start the VM

Right click the VM instance and select Power > Power on the virtual machine.
Refer to the appropriate Luminoso Daylight or Compass Onsite product documentation for the configuration steps.

Upgrade Procedure for VMware

Shut down your old machine.
Deploy a new machine and keep both machines powered off.
In Storage, under the correct datastore, select the directory of your old virtual machine.
Select your data disk and click Copy to and copy the data drive from your old Luminoso virtual machine directory to the new one. The copy progress displays in the Recent Tasks pane.
Right click your new machine and select Edit Settings. The Edit Settings window opens.
Click Add New Device and select Add Hard Disk. A file explorer opens.
In the Datastores column, select your new virtual machine. In the Contents column, select the disk you copied from your previous machine.
Click OK. The File explorer closes.
Click OK. The Edit Settings window closes.
Power on your new machine.

Luminoso Compass Onsite: Configuration Guide

Getting Started with Compass

Select Manage Compass Service from the Main Menu and press ENTER. The Manage Compass Service menu opens.

...

Select Edit Compass Environment Variables.

...

A list of available variables displays with blank slots for you to fill in. ALLOWED_HOSTS is used for a (list of) domain/host name(s) where you access the Compass service. If you use multiple hostnames, separate them with commas.

Note: Do not enclose values in quotation marks. Tab to the OK button in the bottom right and press ENTER to finish and save your values. If you press CANCEL, you exit without saving changes and erase all values.

...

You are now ready to start the Compass service. Select Manage Compass
Service -> Manage Service -> Start Compass. The startup sequence begins. This may take up to two minutes during the first deployment.

...

The names of the services being started appear on the screen. A screen like this appears when the sequence is finished:

...

Tab to the OK button and press ENTER. A screen like the following appears:

...

Use tab to highlight the OK button and press ENTER to return to the main menu. Your Compass Service is now ready to use.
Log in to the application using the name master and password master.
Note: We recommend changing the password for master after you first log in.

Additional Configuration Options

To complete any of these tasks, you must log in to the on-site virtual machine using admin credentials.

To make system changes:

Select Manage System from the menu.
Select the appropriate menu option, make the necessary changes, and click OK.

Change Hostname

Open Manage System -> Configure Networking -> Configure Hostname
Change the fully-qualified domain name to your preferred domain name.
Select OK.

NOTE: If you have DHCP and are changing the hostname, you must reboot the machine to report the new hostname to the DHCP server.

Change DHCP to Static IP

Open Manage System -> Configure Networking -> Configure Interface
Change “DHCP” to “Static”.
Enter the desired IP address, Netmask, Gateway, and DNS Server. These fields are only valid if you have selected “Static” above.
Select OK.

Use an internal NTP server

Open Manage System -> Configure Networking -> Configure NTP
Change “DHCP” to “Static”.
Enter the domain name of the NTP server you wish to use.
Select OK.

NOTE: You must already have successfully changed to a static IP address in order to configure a static NTP server.

Change admin password

Open Manage System -> Change admin password
Change the admin password.
Select OK.

NOTE: You cannot log into the Compass software as “admin”, but must log in as one of the created users.

Configure HTTPS

Open Manage Compass Service -> Configure HTTPS
Select “Enable HTTPS”.
Upload your certificate and key to the Virtual Machine via sftp using a command similar to
sftp certcopy@[hostname]:https <<< $’put [/path/to/certificate.pem]’
If prompted for a password, use the admin password.
Your certificate and key should both appear in the lists below; select the certificate file in the “Select Certificate File” list and the associated key in the “Select Key File” list.
Select OK.

Proxy Settings

If your deployment requires one or more http reverse proxies in front of Luminoso on-site, we recommend configuring all proxies so that requests are limited to 200 MiB in size. 200 MiB is Luminoso’s internal limit.

Compass Documentation: Managing Users and Accounts

Manage Accounts and Users via API commands on your Compass admin account. For a detailed list of endpoints, refer to the Compass API Reference, which outlines how to accomplish typical user management tasks.

Note: You can access the DRF via browser to the Compass API. The screenshots displayed used here were taken with DRF.

You can log in to the application with login name master and password master. We recommend you change the password for master after you first log in.

Overview

Action	Details
Step 1: Add an Account	You can create one or more accounts in Compass. Accounts are containers for projects and users receive permissioned access to accounts. Typically, accounts segregate users and their projects to specific groups or departments. Use the POST /api/accounts/ endpoint to create and specify the name of the account (“Marketing” in the example below). Image Added Save or copy the ID of the account for future steps.
Step 2: Add a User	Use the POST /api/users endpoint to add a user and specify the user’s email, name, default account and admin option. Once you call the endpoint, it creates the user (as seen below) Image Added Note: Since admin users have full access to the system, including creating other users and accounts assign the option sparingly. Image Added IMPORTANT: Save the user id and temporary password for future steps. Note: If you forget to save the temporary password, call this endpoint to reset it: /api/users/USERID/password/reset
Step 3: Assigning Permissions	Grant the user you created a permission on the account. The available permissions are: read: provides read-only access to projects, can only view projects, not create or edit them readwrite: provides create and edit permissions on projects in the account manage: (to be expanded in the future, but for now the same as readwrite) provides create and edit permissions on projects in the account listener: reserved, do not use To give the user a permission on the account, use the POST /api/permissions/ endpoint and specify the User ID from Step 2, the account from Step 1 and the Level. Image Added Now the user is granted a permission to the account: Image Added

You have now created an account, a user, and have given the user desired access to the account. Lastly, tell the user their temporary password that you set in Step 2.

Note: if you forget to save the temporary password, you can reset it by calling this endpoint: /api/users/USERID/password/reset

Luminoso Daylight Onsite Configuration Guide

Getting Started

After installing the Luminoso Daylight Onsite Virtual Appliance, connect to it via ssh using the username ‘admin’ and the associated password that Luminoso support provided. After you log in, a menu appears where you can configure various properties of the machine.

...

Configuring the Virtual Appliance

The following steps configure the Onsite Appliance to match your data center environment. For example, the network card defaults to DHCP. If your data center environment requires static IPs, you can change it using the Manage System menu in the Onsite Menu.

Other system configuration options:

Manage System	Configure hostname
	Configure interface
	Configure inactivity timeout
	Configure NTP
	Change admin password
	Configure root certificate
	Configure SMTP
	Configure system notifications
	Configure application notifications
	Configure HTTPS
	Configure SAML
	Configure rsylog server
	Support Shell
Manage Users	List Users
	Create User
	Delete User
	Change User Access
	Change Account
	Delete Account
	Rename Accounts
Manage Service	Start Daylight
	Stop Daylight
	Collect Support Logs
Quit

Update Luminoso Daylight Settings:

To complete any of the following tasks, you must log in to the on-site virtual machine using admin credentials.