We maintain certain instance standards that must be preserved, such as: LDAP, DNS, security settings, administrative accounts, etc. In order to test and develop puppet manifests for Cloud VPS it might be helpful to setup a Standalone puppetmaster. The node definitions for a VPS instances are not stored in manifests/site.pp - they are configured via the OpenStack Horizon user interface and stored in a backing persistent data store. VPS users should always be ready for their instance to vanish at a moment's notice, and have a plan to reproduce the same functionality on a new instance - generally this is accomplished using Puppet. public test sites, bot hosts, etc.) should be fully puppetized. That said, any system being used for semi-production purposes (e.g. Toolforge) often have their own systems for maintaining code and configuration. Deploying software via Scap3 can be achieved in Puppet by using the puppet class scap::target.Ĭloud VPS users have considerable freedom in the configuration of their systems, and the state of machines is frequently not puppetized. Depending on the case, Debian packages or the use of our deployment system ( Scap3) should be employed. with the define git::clone should be avoided. However, Puppet is not being used as a deployment system at Wikimedia. There are a few cases where configurations are deployed into systems without involving Puppet but these are the exceptions rather than the rule ( MediaWiki configuration etc.) all package installs and configurations should happen via Puppet in order to ensure peer review and reproducibility. Anything related to the configuration files & state of a server should be puppetized. Puppet is our configuration management system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |