Puppet (company)

From Wikipedia, the free encyclopedia
  (Redirected from Puppet (software))
Jump to navigation Jump to search
Puppet
Private[1]
IndustryComputer software[1]
Founded2005; 14 years ago (2005)[2]
HeadquartersPortland, Oregon, U.S.
Key people
Luke Kanies (Founder), Yvonne Wassenaar (CEO), Andrew Shafer[2]
ProductsPuppet, Puppet Enterprise, and Puppet Forge[3]
Websitepuppet.com

Puppet is a privately held information technology (IT) automation software company based in Portland, Oregon.

Products[edit]

Headquartered in Portland, showing their present location

Puppet's primary product, Puppet Enterprise,[4] comprises a commercially supported version of its open-source configuration management tool, Puppet. Puppet IT automation software uses Puppet's declarative language to manage various stages of the IT infrastructure lifecycle, including the provisioning, patching, configuration, and management of operating system and application components across enterprise data centers and cloud infrastructures.[5]

In February 2011 Puppet released its first commercial product, Puppet Enterprise, built on the open-source base and providing commercial users with improved usability as well as some commercial components.[6] In September 2011, the company released Puppet Enterprise 2.0, which introduced integration with MCollective, acquired by Puppet in 2010,[7] as well as provisioning for virtual machines directly on Amazon EC2 and VMware.[8] In June 2013, Puppet released Puppet Enterprise 3.0, which features a rewritten orchestration engine that will ease the automated rollout of changes across multiple sites and clouds.[9]

Puppet partners and has technology integrations with VMware, Amazon Web Services, Cisco, OpenStack, Microsoft Azure, Eucalyptus, Rightscale, and Zenoss.[10]

Built as cross-platform software, Puppet and Puppet Enterprise operate on Linux distributions, including RHEL (and clones such as CentOS and Oracle Linux), Fedora, Debian, Mandriva, Ubuntu, and SUSE, as well as on multiple Unix systems (Solaris, BSD, Mac OS X, AIX, HP-UX), and has Microsoft Windows support.[11][12] It is a model-driven solution that requires limited programming knowledge to use.[13]

Puppet purchased the infrastructure automation Distelli in September 2017[14]. Puppet rebranded Distelli's VM Dashboard (a continuous integration / continuous delivery product) as Puppet Pipelines for Applications,[15] and K8S Dashboard as Puppet Pipelines for Containers.[16] The products were made generally available in October, 2017.[17]

Puppet released Puppet Discovery, a tool to discover and manipulate resources in hybrid networks, in May 2018.[18] It is Puppet's third stand-alone enterprise product.

Puppet[edit]

Puppet
Puppet Logo.svg
Developer(s)Puppet
Initial release2005; 14 years ago (2005)
Stable release6.10.1 (October 15, 2019; 29 days ago (2019-10-15)[19]) [±]
Preview release5.5.0.134.g0251aa7 (March 31, 2018; 19 months ago (2018-03-31)) [±]
Repositoryhttps://github.com/puppetlabs/puppet
Written inC++ & Clojure from 4.0,[20] Ruby
Operating systemLinux, Unix-like, Microsoft Windows
Type
LicenseOpen Source Puppet: Apache for >2.7.0, GPL for prior versions. Puppet Enterprise: Puppet Master License Agreement
Websitepuppet.com

In computing, Puppet is an open-core software configuration management tool. It runs on many Unix-like systems as well as on Microsoft Windows, and includes its own declarative language to describe system configuration. It is written in C++, Clojure and Ruby, with its free-software version released under the Apache License 2.0 (the GNU General Public License (GPL) until version 2.7.0).[21]

Puppet is designed to manage the configuration of Unix-like and Microsoft Windows systems declaratively. The user describes system resources and their state, either using Puppet's declarative language or a Ruby DSL (domain-specific language). This information is stored in files called "Puppet manifests". Puppet discovers the system information via a utility called Facter, and compiles the Puppet manifests into a system-specific catalog containing resources and resource dependency, which are applied against the target systems. Any actions taken by Puppet are then reported.

Puppet consists of a custom declarative language to describe system configuration, which can be either applied directly on the system, or compiled into a catalog and distributed to the target system via client–server paradigm (using a REST API), and the agent uses system specific providers to enforce the resource specified in the manifests. The resource abstraction layer enables administrators to describe the configuration in high-level terms, such as users, services and packages without the need to specify OS specific commands (such as rpm, yum, apt).

Puppet is model-driven, requiring limited programming knowledge to use.[22]

Puppet comes in two versions, Puppet Enterprise and Open Source Puppet. In addition to providing functionalities of Open Source Puppet, Puppet Enterprise also provides GUI, API and command line tools for node management.

Architecture[edit]

Puppet manually invoked on a client

Puppet usually follows client-server architecture. The client is known as an agent and the server is known as the master. For testing and simple configuration, it can also be used as a stand-alone application run from the command line.

Puppet Server is installed on one or more servers, and Puppet Agent is installed on all the machines that the user wants to manage. Puppet Agents communicate with the server and fetch configuration instructions. The Agent then applies the configuration on the system and sends a status report to the server.[23] Devices can run Puppet Agent as a daemon, that can be triggered periodically as a cron job or can be run manually whenever needed.

Puppet architecture consists of:

  • Configuration language: The Puppet programming language is a declarative language that describes the state of a computer system in terms of "resources", which represent underlying network and operating system constructs. The user assembles resources into manifests that describe the desired state of the system. These manifests are stored on the server and compiled into configuration instructions for agents on request. [24]

Puppet resource syntax:

type { 'title':
  attribute => value
}

Example resource representing a Unix user:

user { 'harry':
  ensure => present,
  uid    => '1000',
  shell  => '/bin/bash',
  home   => '/var/tmp'
}
  • Resource abstraction: Puppet allows users to configure systems in a platform-agnostic way by representing operating system concepts as structured data. Rather than specifying the exact commands to perform a system action, the user creates a resource, which Puppet then translates into system-specific instructions which are sent to the machine being configured. For example, if a user wants to install a package on three different nodes, each of which runs a different operating system, they can simply declare one resource, and Puppet will determine which commands need to be run based on the data obtained from Facter, a program that collects data about the system it is running on, including its operating system, IP address, and some hardware information.[25] Providers on the node use Facter facts and other system details translate resource types in the catalog into machine instructions that will actually configure the node.
  • Transaction: A normal Puppet run has the following stages:
    1. An agent sends facts from Facter to the master.
    2. Puppet builds a graph of the list of resources and their interdependencies, representing the order in which they need to be configured, for every client. The master sends the appropriate catalog to each agent node.
    3. The actual state of the system is then configured according to the desired state described in manifest file. If the system is already in the desired state, Puppet will not make any changes, making transactions idempotent.
    4. Finally, the agent sends a report to the master, detailing what changes were made and any errors that occurred.

Funding[edit]

In June of 2018 Puppet raised $42 million for a total of $150 million in funding. The round was led by Cisco and included Kleiner Perkins, True Ventures, EDBI, and VMware.[26]

History[edit]

Puppet Founder Luke Kanies

In 2005, Puppet was founded by former CEO Luke Kanies.[2] On Jan. 29, 2019 Yvonne Wassenaar replaced Sanjay Mirchandani as CEO. Wassenaar has held key leadership positions at Airware, New Relic and VMware.

See also[edit]

References[edit]

  1. ^ a b "Company Overview of Puppet Labs, Inc". Bloomberg Businessweek.
  2. ^ a b c "Puppet Labs". Crunchbase.
  3. ^ "Puppet Enterprise". Puppet.
  4. ^ Rao, Leena. "Cisco, Google Ventures, VMware Put $8.5M In Data Center Automation Startup Puppet Labs". TechCrunch.
  5. ^ Graner, Amber. "Puppet Labs Announces Puppet Enterprise".
  6. ^ Kerner, Sean Michael. "Puppet Goes After Enterprise System Management". Enterprise Networking Planet.
  7. ^ Rao, Leena. "Data Center Automation Startup Puppet Labs Acquires OPen Source Project The Marionette Collective". TechCrunch.
  8. ^ Finley, Klint. "Puppet 2.0 Will Support Amazon EC2 and VMware Provisioning". Silicon Angle.
  9. ^ New Puppet tool beefs up orchestration automation for enterprise use — Tech News and Analysis. Gigaom.com (2013-06-25). Retrieved on 2013-12-09.
  10. ^ Rao, Leena. "Cisco, Google Ventures, VMware Put $8.5M in Data Center Automation Startup Puppet Labs". TechCrunch.
  11. ^ "Docs: PE 2.0 - Installing - System Requirements". Puppet.
  12. ^ "Puppet system requirements". Puppet.
  13. ^ Dehaan, MP. "Deploying Apache Tomcat Applications With Puppet". tomcatexpert.
  14. ^ https://puppet.com/blog/welcome-distelli-to-puppet-family
  15. ^ https://puppet.com/docs/pipelines-for-apps/enterprise/index.html
  16. ^ https://puppet.com/docs/pipelines-for-containers/enterprise/index.html
  17. ^ https://puppet.com/blog/introducing-puppet-pipelines-and-puppet-container-registry
  18. ^ https://puppet.com/blog/announcing-puppet-discovery-general-availability
  19. ^ "Puppet release notes". Retrieved 22 October 2019.
  20. ^ "Evolving Puppet for the Next 10 Years". Luke Kanies. 2014-09-23. Retrieved 2017-05-26.
  21. ^ "Puppet Frequently Asked Questions". Puppet Labs. Retrieved 10 March 2010.
  22. ^ "Deploying Apache Tomcat Applications With Puppet". tomcatexpert.com. Retrieved 23 January 2015.
  23. ^ "Overview of Puppet's architecture — Documentation — Puppet". docs.puppet.com. Retrieved 2016-09-14.
  24. ^ Krum, Hevelingen, Kero, Turnbull, McCune. Pro Puppet. Apress. ISBN 978-1430260400.CS1 maint: multiple names: authors list (link)
  25. ^ https://puppet.com/docs/facter
  26. ^ "Puppet raises $42M led by Cisco as its DevOps automation platform passes 40,000 businesses". TechCrunch. Retrieved 2019-03-22.

External links[edit]