This documentation is for WSO2 Puppet Modules version 2.0.0. View documentation for the latest release.
We have moved WSO2 Puppet Modules to separate product specific repositories, and as a result the puppet-modules repository, which this documentation is based on has been deprecated.
A new puppet-common repository has been introduced. Please find the new repository list here.
Introduction - WSO2 Puppet Modules 2.0.0 - WSO2 Documentation
WSO2 Puppet Modules 2.0.0
Expand all   Collapse all
||
Skip to end of metadata
Go to start of metadata

Puppet is a configuration automation tool. Using either a distributed (Master-Agent) setup or a standalone setup, configuration instructions, which are referred to as manifests in Puppet, are executed on a target resource, such as Virtual Machines, physical servers, Docker images etc., to maintain a given state of a set of resources, such as services, files etc.

WSO2 Puppet Modules provide configuration data, Puppet manifests, and Puppet templates that are required to configure the following WSO2 products.

  • WSO2 API Manager (APIM)
  • WSO2 Application Server (AS)
  • WSO2 Business Process Server (BPS)
  • WSO2 Governance Registry (G-Reg)
  • WSO2 Business Rules Server (BRS)
  • WSO2 Complex Event Processor (CEP)
  • WSO2 Data Analytics Server (DAS)
  • WSO2 Message Broker (MB)
  • WSO2 Data Services Server (DSS)
  • WSO2 Enterprise Store (ES)
  • WSO2 Enterprise Service Bus (ESB)
  • WSO2 Identity Server (IS)

WSO2 Puppet Modules are used to configure product instances that are targeted towards various platforms. In addition, WSO2 Puppet Modules also ship specific configuration data so that you can use Docker images on the Kubernetes platform.

  • No labels
||