resources - How to make Puppet track TCP ports to avoid conflicts? -


my puppet master has modules many different services (mysql, redis, jenkins, beanstalk, etc.). each module seems have own way of defining port(s) service listens on. there unified way track tcp ports across puppet modules? think there should resource type, file, enforces global uniqueness, don't see appropriate in puppet docs

the idea if accidentally configure 2 different services listen on same port, should error conflict when compiling catalog, not when second service restarts on node , gets eaddrinuse.

if want catch conflicts, can create defined type. example:

define port (   $port = $name ) { } 

you can use signal port being used (eg port { 8080: }) , puppet fail compile catalog if same port defined twice.


Comments

Popular posts from this blog

javascript - oscilloscope of speaker input stops rendering after a few seconds -

javascript - gulp-nodemon - nodejs restart after file change - Error: listen EADDRINUSE events.js:85 -

Fatal Python error: Py_Initialize: unable to load the file system codec. ImportError: No module named 'encodings' -