background preloader

Deployment

Facebook Twitter

Vagrant와 chef로 개발서버 구축 자동화하기. Continuous Delivery with Maven, Puppet and Tomcat - ApacheCon NA 2013. A Fabric/Puppet Build/Deploy System. Learning Puppet — Index. Welcome This is Learning Puppet, a series of lessons about managing system configuration with Puppet Enterprise. Installation instructions and a complete reference to the Puppet language are available elsewhere on the site; this series is meant to be a guided tour to building things with Puppet. If you’ve heard good things about Puppet but don’t know where to start, this is the best place to begin.

Get the Free VM Puppet can configure or misconfigure nearly any aspect of a system, so when learning how to use it, it’s best to have some test systems around. To help with this, we provide a free virtual machine with Puppet already installed. Experiment fearlessly! Get the Learning Puppet VM While it downloads, move on to the first chapter of Learning Puppet.

The Learning Puppet VM is available in VMWare .vmx format and the cross-platform OVF format, and has been tested with VMWare Fusion and VirtualBox. Login Info Log in as root, with the password puppet. Contents ↑ Back to top. Continuous Delivery. Automation for the people: Deployment-automation patterns, Part 2. Deployment is yet another aspect of software creation that lends itself well to automation. Automated deployments reap the benefits of a reliable, repeatable process: improved accuracy, speed, and control. Part 1 of this two-part article describes eight deployment-automation patterns. In this installment, I expand the discussion to cover seven more equally beneficial approaches to deployment: Figure 1 illustrates the relationships among the deployment patterns covered in this article (the unshaded patterns were covered in Part 1): Figure 1.

Deployment-automation patterns These seven additional deployment-automation patterns build upon the first eight to help you create one-click deployments. Compile once, deploy to many environments Name: Binary Integrity Pattern: For each tagged deployment, the same archive (WAR or EAR) is used in each target environment. Antipatterns: Separate compilation for each target environment on the same tag. Figure 2. Back to top Name: Disposable Container Figure 3. <! Fabric — Fabric 1.5.3 documentation. Pds3.egloos.com/pds/200611/26/16/capistrano_niceview.pdf. Architecture. From ControlTier The ControlTier administrative framework is comprised of a server and a client.

The server can run standalone to execute distributed commands. In this mode a user runs ad hoc commands via ctl-exec or Jobs via Ctlcenter running on a central host. Alternatively, a user might install the client on remote hosts to run defined commands in CTL Modules. The diagram above provides an overview to the ContolTier server and client components, their relationships and the network protocols they use. Server The ControlTier server hosts a variety of services to support the automation activity running across the ControlTier managed hosts.

The following sections describe each server component covering their role and function. Central Command Dispatcher The Central Command Dispatcher provides a centralized interface to the ControlTier command dispatcher. The Jobcenter webapp provides a graphical interface to the Central Command Dispatcher. Modules Resource model Transforms File Share Event Logger.