Comments for Java Application Deployment Automation with Deployit | XebiaLabs http://blog.xebialabs.com ava Application Deployment Automation with Deployit Thu, 09 Feb 2012 16:40:05 +0000 hourly 1 http://wordpress.org/?v=3.0.3 Comment on Ergonomics and Deployment Frameworks by Bhorsoft http://blog.xebialabs.com/2012/02/07/ergonomics-and-deployment-frameworks/#comment-721 Bhorsoft Thu, 09 Feb 2012 16:40:05 +0000 http://blog.xebialabs.com/?p=6100#comment-721 When I first started my current position I had 8 apps to deploy on deployment night (that started at 12:00 AM). Deployment instructs for the apps had between 8 and 26 steps. Easy to make a mistake at 2:00 AM after putting in a full 10 hour day. Over time I scripted deployment for each application so now all I have to do is run the command. The command is identical for each application. We've now grown to 20 apps to deploy and I use the same interface for each. Because of this work, we've had perfect deployments for the past 4 years. So yes, deployment ergonomics are very important. Because my deployments are so easy now, I can hand some of the work off to others and get some occasional sleep. When I first started my current position I had 8 apps to deploy on deployment night (that started at 12:00 AM). Deployment instructs for the apps had between 8 and 26 steps. Easy to make a mistake at 2:00 AM after putting in a full 10 hour day. Over time I scripted deployment for each application so now all I have to do is run the command. The command is identical for each application. We’ve now grown to 20 apps to deploy and I use the same interface for each. Because of this work, we’ve had perfect deployments for the past 4 years. So yes, deployment ergonomics are very important. Because my deployments are so easy now, I can hand some of the work off to others and get some occasional sleep.

]]> Comment on Continuous Delivery with Deployit, Puppet, JBoss and VMware by Coert http://blog.xebialabs.com/2012/01/20/continuous-delivery-with-deployit-puppet-jboss-and-vmware/#comment-720 Coert Thu, 09 Feb 2012 08:42:23 +0000 http://blog.xebialabs.com/?p=6029#comment-720 Hi Chris, this is Marks reply on the Xebia website. Mark van Holsteijn Says: Posted at: February 6, 2012 at 10:53 pm Chris, We are using Puppet for automated provisioning of the operating system and all the middleware system software. We use Deployit so that we can provide self-service deployments to the software development teams: This means that we provide the infrastructure for the different environments (development, test, acceptance, production), while giving the development teams the freedom to deploy their system(s) any time they want as often as they want. The integration with hudson and maven also allows them to deploy to create fully automated build and deployment processes (continuous integration/delivery). So why not everything with Puppet? Our applications can be deployed across multiple layers and machines, so we needed to order the actions for the deployment. Puppet plans have a declarative nature, that does not work well with the order we need in a deployment process. Furthermore, the deployment processes of applications have more diversity and change more often than the provision of the operating system and systems software. Giving access to the puppet plans to the development teams meant that they would have full control over the operating system aswell as Puppet always run as root. Deployit’s security subsystem we still retain control over the configuration of the operation system. If you have any other questions, please do not hesitate the contact me. Cheers, Mark Hi Chris, this is Marks reply on the Xebia website.

Mark van Holsteijn Says:
Posted at: February 6, 2012 at 10:53 pm

Chris,

We are using Puppet for automated provisioning of the operating system and all the middleware system software. We use Deployit so that we can provide self-service deployments to the software development teams: This means that we provide the infrastructure for the different environments (development, test, acceptance, production), while giving the development teams the freedom to deploy their system(s) any time they want as often as they want. The integration with hudson and maven also allows them to deploy to create fully automated build and deployment processes (continuous integration/delivery).

So why not everything with Puppet? Our applications can be deployed across multiple layers and machines, so we needed to order the actions for the deployment. Puppet plans have a declarative nature, that does not work well with the order we need in a deployment process. Furthermore, the deployment processes of applications have more diversity and change more often than the provision of the operating system and systems software. Giving access to the puppet plans to the development teams meant that they would have full control over the operating system aswell as Puppet always run as root. Deployit’s security subsystem we still retain control over the configuration of the operation system.

If you have any other questions, please do not hesitate the contact me.

Cheers,

Mark

]]> Comment on Continuous Delivery with Deployit, Puppet, JBoss and VMware by Andrew Phillips http://blog.xebialabs.com/2012/01/20/continuous-delivery-with-deployit-puppet-jboss-and-vmware/#comment-714 Andrew Phillips Wed, 01 Feb 2012 00:17:50 +0000 http://blog.xebialabs.com/?p=6029#comment-714 <em>@Chris:</em> Thanks for the comment, which I've copied to Mark's original post <a href="http://blog.xebia.com/2011/12/14/continuous-delivery-for-enterprise-java-applications/#comment-117381" target="_new" rel="nofollow">here</a>. Looking forward to his response! @Chris: Thanks for the comment, which I’ve copied to Mark’s original post here. Looking forward to his response!

]]> Comment on Continuous Delivery with Deployit, Puppet, JBoss and VMware by My Latest Shared Bookmarksfboiton's blog | fboiton's blog http://blog.xebialabs.com/2012/01/20/continuous-delivery-with-deployit-puppet-jboss-and-vmware/#comment-711 My Latest Shared Bookmarksfboiton's blog | fboiton's blog Tue, 24 Jan 2012 03:13:10 +0000 http://blog.xebialabs.com/?p=6029#comment-711 [...] Continuous Delivery with Deployit, Puppet, JBoss and VMware http://t.co/XsdBYmvK – [...] [...] Continuous Delivery with Deployit, Puppet, JBoss and VMware http://t.co/XsdBYmvK – [...]

]]> Comment on Continuous Delivery with Deployit, Puppet, JBoss and VMware by Chris http://blog.xebialabs.com/2012/01/20/continuous-delivery-with-deployit-puppet-jboss-and-vmware/#comment-708 Chris Sun, 22 Jan 2012 11:39:32 +0000 http://blog.xebialabs.com/?p=6029#comment-708 Mark - great post. Can you elaborate on why you're not deploying your apps using Puppet? Why use another product? We're currently looking at app deployment tools from XebiaLabs, Nolio and UC4, but using Puppet for the app layer seems to be a viable alternative. - Chris. Mark – great post. Can you elaborate on why you’re not deploying your apps using Puppet? Why use another product? We’re currently looking at app deployment tools from XebiaLabs, Nolio and UC4, but using Puppet for the app layer seems to be a viable alternative.

- Chris.

]]> Comment on Deployment is the new build (part 1) by Taking Application Release Automation to the Next Level | Java Application Deployment Automation with Deployit | XebiaLabs http://blog.xebialabs.com/2011/05/03/deployment-is-the-new-build-part-1/#comment-685 Taking Application Release Automation to the Next Level | Java Application Deployment Automation with Deployit | XebiaLabs Tue, 29 Nov 2011 18:43:10 +0000 http://blog.xebialabs.com/?p=5693#comment-685 [...] This advance closely mirrors the development of build frameworks from tools like Ant to today's industry standards like Maven and on to the next generation of Gradle, SBT and others. // Tags: Application Release Automation, continuous value, deployment automation Filed under: XebiaLabs. Bookmark the permalink.   ← Leading Real Estate and Financial Services Entity chooses Deployit [...] [...] This advance closely mirrors the development of build frameworks from tools like Ant to today's industry standards like Maven and on to the next generation of Gradle, SBT and others. // Tags: Application Release Automation, continuous value, deployment automation Filed under: XebiaLabs. Bookmark the permalink.   ← Leading Real Estate and Financial Services Entity chooses Deployit [...]

]]> Comment on Deployment automation vs. server provisioning by Taking Application Release Automation to the Next Level | Java Application Deployment Automation with Deployit | XebiaLabs http://blog.xebialabs.com/2010/12/20/deployment-automation-vs-server-provisioning/#comment-684 Taking Application Release Automation to the Next Level | Java Application Deployment Automation with Deployit | XebiaLabs Tue, 29 Nov 2011 18:26:07 +0000 http://blog.xebialabs.com/?p=5593#comment-684 [...] processes, it is also hardly surprising that the initial drive has been to automate the actual rollout of the application itself: copying the files to the target machines, restarting the servers, running the SQL against [...] [...] processes, it is also hardly surprising that the initial drive has been to automate the actual rollout of the application itself: copying the files to the target machines, restarting the servers, running the SQL against [...]

]]> Comment on Deployit integrated with WebSphere CloudBurst Appliance for applications on demand by Deployit integrated with DPAdmin for heterogeneous deployments to IBM DataPower appliances | Java Application Deployment Automation with Deployit | XebiaLabs http://blog.xebialabs.com/2011/05/08/deployit-integrated-with-websphere-cloudburst-appliance-for-applications-on-demand/#comment-594 Deployit integrated with DPAdmin for heterogeneous deployments to IBM DataPower appliances | Java Application Deployment Automation with Deployit | XebiaLabs Wed, 06 Jul 2011 16:42:41 +0000 http://blog.xebialabs.com/?p=5718#comment-594 [...] a previous blog I talked about the integration we've achieved between XebiaLabs' Deployit and IBM's Workload [...] [...] a previous blog I talked about the integration we've achieved between XebiaLabs' Deployit and IBM's Workload [...]

]]> Comment on Deployment is the new build (part 3) by Deployment is the new build (part 2) | Java Application Deployment Automation with Deployit | XebiaLabs http://blog.xebialabs.com/2011/06/16/deployment-is-the-new-build-part-3/#comment-592 Deployment is the new build (part 2) | Java Application Deployment Automation with Deployit | XebiaLabs Thu, 16 Jun 2011 21:15:31 +0000 http://blog.xebialabs.com/?p=5768#comment-592 [...] cover the details of these three concepts in the next blog… // Tags: cloud, Deployment, devops Filed under: Uncategorized. Bookmark the permalink. [...] [...] cover the details of these three concepts in the next blog… // Tags: cloud, Deployment, devops Filed under: Uncategorized. Bookmark the permalink. [...]

]]> Comment on Deployment is the new build (part 2) by Deployment is the new build (part 3) | Java Application Deployment Automation with Deployit | XebiaLabs http://blog.xebialabs.com/2011/05/21/deployment-is-the-new-build-part-2/#comment-591 Deployment is the new build (part 3) | Java Application Deployment Automation with Deployit | XebiaLabs Thu, 16 Jun 2011 21:12:47 +0000 http://blog.xebialabs.com/?p=5750#comment-591 [...] the previous post, we looked at how Reusable commands, Models and Conventions++ helped turn build from a “black [...] [...] the previous post, we looked at how Reusable commands, Models and Conventions++ helped turn build from a “black [...]

]]>