How to use Example42 NextGen Modules
By Alessandro Franceschi
Lab42

Ten Design Choices for Example42 Puppet Modules

1 - Provide alternatives for Data Separation

2 - Provide choice on Configuration Files supply

3 - Configure everything but provide OS defaults.

4 - Allow management of general module's behavior

5 - Allow Custom Options for endless parameters

6 - Permit easy extension with custom classes

7 - Offer easy removal of the module's resources

8 - Limit cross-dependencies. Prerequisites as options.

9 - Automatically monitor and firewall resources

10 - Puppi integration: Puppet knowledge to the CLI

DATA SEPARATION ALTERNATIVES

PARAMS_LOOKUP EVERYWHERE

PARAMS LOOKUP ORDER

CUSTOMIZE: CONFIGURATION FILE

CUSTOMIZE: CONFIGURATION DIR

CUSTOMIZE: PATHS AND NAMES

DEFAULTS IN PARAMS.PP

MANAGE BEHAVIOR

CUSTOM OPTIONS

CUSTOMIZE: CUSTOM CLASS

EASY DECOMMISSIONING

CROSS-MODULE INTEGRATIONS

EXTEND: MONITOR

EXTEND: FIREWALL

EXTEND PUPPI

How to make a NextGen module

/

#