rsan
Table of Contents
- Description
- Setup - The basics of getting started with rsan
- Usage - Configuration options and additional functionality
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
Description
The Remote Support Access Node (RSAN) will allow Puppet support engineers to conduct live troubleshooting, resolving problems more quickly and efficiently and lead to a reduction of system disruption to the customer.
Customers currently must deliver large volumes of data to support and resolution time is hindered by transfer logistics and privacy concerns. This same data must then be processed by internal support engineers leading to artificially decreased capacity of the support team.
The RSAN platform is designed to be a contained infrastructure endpoint in the customer Puppet Enterprise environment, collating data and access, useful in incident resolution for the target customer deployment. The node will allow for read-only access to Puppet Entperise Component Data and configiration, and limit other access through Puppet Enterprise’s built-in Role Based Access Control(RBAC). The Node will has the functionality to make session-based outward connections towards the Puppet Support Network, controllable by the customer user in duration.
Setup
What rsan affects
RSAN When
Setup Requirements
Dependencies
derdanne/nfs (>= 2.1.5) puppetlabs/postgresql (>= 6.6.0) puppetlabs/puppet_metrics_collector (>= 6.1.0) puppetlabs/puppet_metrics_dashboard (>= 2.3.0) puppetlabs/stdlib (>= 4.5.0 < 7.0.0) puppetlabs/concat (>= 1.1.2 < 7.0.0) puppetlabs/transition (>= 0.1.0 < 1.0.0) herculesteam/augeasproviders_core (>= 2.1.5 < 4.0.0) herculesteam/augeasproviders_shellvar (>= 1.2.0 < 5.0.0) puppetlabs/apt (>= 2.0.0 < 8.0.0) puppet-grafana (>= 3.0.0 < 7.0.0) puppet-telegraf (>= 2.0.0 < 4.0.0) puppetlabs-apt (>= 4.3.0 < 8.0.0) puppetlabs-inifile (>= 2.0.0 < 5.0.0) puppetlabs-puppetserver_gem (>= 1.1.1 < 3.0.0)
Beginning with rsan
Usage
Limitations
Contributions
For feature development + bug reporting
A Git Issue should exist or be created PRs should be created from a Fork PRS should aways reference a git issue
