A pupperware based load and performance tester for Puppet 6
This section will need to be fleshed out, once the MVP is available. In this section, there will be a a way to get started quickly, for those who don't want to read all the documentation.
You will need an existing puppetserver, running at least version 6. You will also need to have a Docker Engine available.
Additionally, you will need your puppet master to be able to autosign the certificates for the nodes created by this process. Your puppet code will also need to be set up in a way that nodes can be automatically classified - use of a naming scheme, or facts that can be placed at provision time for example.
Installation steps will go here, once those have been determined.
- All the things
- Flesh out the README better
- Add Usage section
- Define MVP for inital release
- Decide language to use for generating yaml for dockerfiles/composefile
- Determine what needs to go into the dockerfiles/composefile
Add adr for licensing choice- Decide and define initial supported naming scheme for nodes
- Decide name for test nodes
- Decide metrics to be gathered during tests
- Average compile time
- Min/Max compile time
- Average resources per catalog
- function calls?
- templates used?
- epp vs erb?
- Number of file resources?
- % change?
- memory usage of master?
- Create a logo
- Decide on a language/format for config files
- JSON?
- Hocon?
- YAML?
- raw key value pairs?
- Determine what options can be configured via the config files
Determine where config files should live and in what order they should be parsed- /etc/pupperware-party/ will house global config files (system wide defaults)
- ~/.pupperware-party/ will house per user config files (user specific overrides)
Determine where the application should install to- The application will install to /opt/pupperware-party by default
- Create a roadmap
- Find people to test MVP and offer feedback
- Determine how to install
- OS packages?
- Unpack a tarball?
- Clone from github?
This section looks at why I started this project and what I hope to be able to accomplish with it.
Testing is an important part of the software lifecycle, and this is true even for infrastructure as code. Web applications are often load tested to ensure that they are able to work at "web scale", and this sort of testing is also useful for performance tuning. For infrastructure as code. Companies often experience periods of rapid growth, and it can be difficult to know when or how to scale your infrastructure as code setup. Do you just need to throw more ram and processors into your master? Or do you need to add more compile masters? Or can you just adjust the configuration? Performance and load testing can help you make informed decisions.
The goal of this project is to provide a simple way to perform load and performance testing to be able to make informed decisions about scaling a puppet 6 stack and be able to tune your stack to be able to get the most out of your existing hardware.
This project is open source, and hosted on github. There are many ways to contribute to this project.
- File bug reports
- File feature requests
- Improve documentation
- Submit or review pull requests
We use SemVer for versioning. For versions available, please see the tags on this repository.
- Lee "FriedBob" Lowder - Initial Author - llowder
This project is licensed under the Apache 2.0 License - see the LICENSE for details.
- afisher for inspiring the name of this project
- binford2k for inspiting actualyl creating this project