Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • VM creation, management, and monitoring from within ProVision
  • Minimal requirements - Managed Servers only requires Python3 and Docker as dependencies
  • OS options include CentOS and Ubuntu
  • Supports both remote and manual setups
  • Supports both root and non-root installations (for the latter, some root steps may be required)
  • Installation and upgrade may be performed either via internet connection or locally:
    • Remote internet install/upgrade connects to 6connect's servers to get new versions
    • Local installs/upgrades will require users to upload the new version locally into their ProVision instance
    • No kernel updates or other system updates are required for local updates - only the Docker container will be updated.
  • Pre-defined Pre-and-Post Commands

Monitoring Features include:

...

If RabbitMQ has not already been installed on your ProVision instance / VM, you will need to install it by running the included shell script (Note: RabbitMQ installation requires internet access.):


1) Run install_rabbitmq.sh

...

2) You may verify the installation is working by opening http://your.host:15672 

3) Once confirmed working, go to ProVision Admin Settings → Managed Server Settings. Then, enter the RabbitMQ IP, port, username, and password into the RabbitMQ Settings section. When done, click "Save Changes".

...

  • Default Monitoring API IP: The default IP to be used for API calls (heartbeat, activation, etc.) for managed server monitoring.  This This is the IP of ProVision's server, at which the managed servers will send API requests. This is because if systemd-resolved is stopped, it is highly possible that ProVision's host is not resolvable. For this reason we make the API requests similar to "curl https://194.24.189.120/api/endpoint -H 'provision.mycompany.com'". Here, we list the local IPs of ProVision.
    • Note: The Default Monitoring API IP can be set to a default value in this area, but it may also be set individually per managed server as an override.  
  • Verify CA: Toggle to "on" if you wish to enable the CA check.
  • Communication type: Push (when the server pushes data to ProVision) and pull (when ProVision connects to the server and pulls the data). Push is preferred, but Pull-based may be desirable in cases where a firewall would not allow inbound connections to ProVision.
  • Monitoring of the system: Toggle to "on" to enable monitoring of system statistics.
  • System monitoring interval: How often (in seconds) the system will be checked. The smaller the interval, the more data there will be to store. 
  • Monitoring of the DNS: Toggle to "on" to enable gathering statistics from the DNS server.
  • DNS monitoring interval: How often (in seconds) the DNS server will be monitored. Data will be aggregated for the set period of time and the aggregated results will be sent. 
  • Raw data retention: The number of minutes to retain raw data. By default, this is set to 1440 minutes (1 day). Raw data requires sizable storage needs.
  • Aggregated data retention: The number of days to retain aggregated data.

...