Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
devops-toolchain
Home
+ new post
About this group
Join this group
Message from discussion Versioning multiple components
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Yaakov Nemoy  
View profile   Translate to Translated (View Original)
 More options Aug 22 2012, 5:14 pm
From: Yaakov Nemoy <loupgaroubl...@gmail.com>
Date: Wed, 22 Aug 2012 14:14:05 -0700
Local: Wed, Aug 22 2012 5:14 pm
Subject: Re: Versioning multiple components
Print | View thread | Show original | Report this message | Find messages by this author
When we have a very complicated deployment like this, we simplify our
deployment pipeline by building up a parallel network with all the
correct versions installed. The actual deployment is pointing the load
balancers to the new parallel network. Rollbacks are simple. When the
deployment is done, we just throw away all the old hosts from the old
environment.
On Wed, Aug 22, 2012 at 9:24 AM, Diptanu Choudhury <dipta...@gmail.com> wrote:
> A couple of questions, do you have a Deployment Pipeline already? If not
> then you will have to think about constructing one so that the artifacts can
> be deployed automatically to different environments. If you do, then first
> of all you will have to look at your current deployment pipeline, does it
> always aid in moving forward by checkout out code from the source control
> and progressing the built artifacts all the way through to your different
> environments? Or does your deployment pipeline allow you to deploy any
> arbitrary version of your application?

> Rollbacks are trickier because they involve restoring the state of the
> environment to the exact same state where a previous version of the
> application was. I think it would be better if you provide some more
> information about your current state of CD.

> We have been doing all this quite successfully for a long time now.

> On Wed, Aug 22, 2012 at 4:30 PM, jdtangney <jo...@jdtangney.com> wrote:

>> We are extending our Continuous Delivery process and I am looking for
>> advice about managing and installing/rolling back across multiple hosts.

>> Each release consists of several components, each of which is installed by
>> a Debian package (.deb file.) Ours is a distributed system, so different
>> packages are installed on different hosts. But they all need to stay in
>> sync, meaning we need to move a release through the pipeline as a whole. In
>> other words, all hosts need to be brought up to the same release level by
>> installing a group of packages. When things go wrong, all those packages
>> need to be rolled back across all hosts in order to revert to the previous
>> release.

>> Do you have any thoughts about how we should approach this? Are there
>> tools available that can help or should we roll our own? I have heard that
>> tools like Artifactory and Nexus Artifact Manager but I know nothing about
>> them.

>> Apologies for the vague and open-ended question.
>> --johnt

> --
> Thanks,
> Diptanu Choudhury
> Senior Consultant, ThoughtWorks
> Mobile - +447808024919
> Web - www.linkedin.com/in/diptanu
> Twitter - @diptanu


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google