Setting up Atlassian Suite via Chef


#1

Ohai Chefs!

has anyone tried to set up the whole Atlassian Suite via Chef? I know there
is a JIRA cookbook, but I would need to set up Bamboo, Fisheye, Crowd, etc.
as well. And git or SVN as well. And everything nicely configured. :slight_smile:

I’m wondering whether this is possible at all, as far as I can remember the
configuration of the Atlassian tools (and especially the linkage between
them) is heavily web-based…

Cheers,
Torben


#2

It’s possible to a certain degree. We have crowd, jira, bamboo, svn,
artifactory, confluence and sonar all installed and configured with chef
but there are many settings db bound. You can get the base install and some
generic setup going.

Currently we don’t have these cookbooks open sourced. They are on a list
of many that we need to clean-up and then release.

-Bryan

On Thu, Feb 16, 2012 at 4:01 AM, Torben Knerr ukio@gmx.de wrote:

Ohai Chefs!

has anyone tried to set up the whole Atlassian Suite via Chef? I know
there is a JIRA cookbook, but I would need to set up Bamboo, Fisheye,
Crowd, etc. as well. And git or SVN as well. And everything nicely
configured. :slight_smile:

I’m wondering whether this is possible at all, as far as I can remember
the configuration of the Atlassian tools (and especially the linkage
between them) is heavily web-based…

Cheers,
Torben


#3

On Thu, Feb 16, 2012 at 5:01 AM, Torben Knerr ukio@gmx.de wrote:

has anyone tried to set up the whole Atlassian Suite via Chef? I know there
is a JIRA cookbook, but I would need to set up Bamboo, Fisheye, Crowd, etc.
as well. And git or SVN as well. And everything nicely configured. :slight_smile:

I wrote these internally at Opscode about a year ago, but they only go
as far as you would expect. You’ve still got to load up a web browser
for all the configuration. Going any further would be a feat of
engineering and unfortunately probably not stable between upstream
releases.

Bryan


#4

Hey Bryan,

that sounds good. Do you already know when they are going to be released?
Or would you mind sharing a preliminary version of what you have?

Thanks a lot,
Torben

On Thu, Feb 16, 2012 at 9:08 PM, Bryan Brandau agent462@gmail.com wrote:

It’s possible to a certain degree. We have crowd, jira, bamboo, svn,
artifactory, confluence and sonar all installed and configured with chef
but there are many settings db bound. You can get the base install and some
generic setup going.

Currently we don’t have these cookbooks open sourced. They are on a list
of many that we need to clean-up and then release.

-Bryan

On Thu, Feb 16, 2012 at 4:01 AM, Torben Knerr ukio@gmx.de wrote:

Ohai Chefs!

has anyone tried to set up the whole Atlassian Suite via Chef? I know
there is a JIRA cookbook, but I would need to set up Bamboo, Fisheye,
Crowd, etc. as well. And git or SVN as well. And everything nicely
configured. :slight_smile:

I’m wondering whether this is possible at all, as far as I can remember
the configuration of the Atlassian tools (and especially the linkage
between them) is heavily web-based…

Cheers,
Torben


#5

On Thu, Feb 16, 2012 at 9:58 PM, Bryan McLellan btm@loftninjas.org wrote:

On Thu, Feb 16, 2012 at 5:01 AM, Torben Knerr ukio@gmx.de wrote:

has anyone tried to set up the whole Atlassian Suite via Chef? I know
there
is a JIRA cookbook, but I would need to set up Bamboo, Fisheye, Crowd,
etc.
as well. And git or SVN as well. And everything nicely configured. :slight_smile:

I wrote these internally at Opscode about a year ago, but they only go
as far as you would expect. You’ve still got to load up a web browser
for all the configuration. Going any further would be a feat of
engineering and unfortunately probably not stable between upstream
releases.

Bryan

Yeah, that’s what I expected. I could imagine to mechanize these steps, but
not sure if it would be worth the effort given that the webui changes quite
often between atlassian versions…

Btw: so these are the same cookbooks that Bryan Brandau refers to?

Cheers,
Torben


#6

No, these were internal Opscode cookbooks. I doubt we would want to support
them officially the way we do others, but I probably wrote them such that
they’re modular enough. I’ll take a look at pulling them out and putting
them on github somewhere if you’re interested.
On Feb 17, 2012 4:03 AM, “Torben Knerr” ukio@gmx.de wrote:

On Thu, Feb 16, 2012 at 9:58 PM, Bryan McLellan btm@loftninjas.orgwrote:

On Thu, Feb 16, 2012 at 5:01 AM, Torben Knerr ukio@gmx.de wrote:

has anyone tried to set up the whole Atlassian Suite via Chef? I know
there
is a JIRA cookbook, but I would need to set up Bamboo, Fisheye, Crowd,
etc.
as well. And git or SVN as well. And everything nicely configured. :slight_smile:

I wrote these internally at Opscode about a year ago, but they only go
as far as you would expect. You’ve still got to load up a web browser
for all the configuration. Going any further would be a feat of
engineering and unfortunately probably not stable between upstream
releases.

Bryan

Yeah, that’s what I expected. I could imagine to mechanize these steps,
but not sure if it would be worth the effort given that the webui changes
quite often between atlassian versions…

Btw: so these are the same cookbooks that Bryan Brandau refers to?

Cheers,
Torben


#7

On Friday, February 17, 2012 at 1:03 AM, Torben Knerr wrote:

On Thu, Feb 16, 2012 at 9:58 PM, Bryan McLellan <btm@loftninjas.org (mailto:btm@loftninjas.org)> wrote:

On Thu, Feb 16, 2012 at 5:01 AM, Torben Knerr <ukio@gmx.de (mailto:ukio@gmx.de)> wrote:

has anyone tried to set up the whole Atlassian Suite via Chef? I know there
is a JIRA cookbook, but I would need to set up Bamboo, Fisheye, Crowd, etc.
as well. And git or SVN as well. And everything nicely configured. :slight_smile:

I wrote these internally at Opscode about a year ago, but they only go
as far as you would expect. You’ve still got to load up a web browser
for all the configuration. Going any further would be a feat of
engineering and unfortunately probably not stable between upstream
releases.

Bryan

Yeah, that’s what I expected. I could imagine to mechanize these steps, but not sure if it would be worth the effort given that the webui changes quite often between atlassian versions…
Btw: so these are the same cookbooks that Bryan Brandau refers to?

Cheers,
Torben

Having a mix of Chef and backups isn’t necessarily a bad thing when you run into tricky applications like this. I recently set up Jenkins so that Chef would install the software and dependencies, install plugins, and install the libraries and such we needed to run the builds. For the actual Jenkins config, I didn’t have the time to reverse engineer the job XML files and write an LWRP to generate them, so I decided to just back up the data to S3. It worked pretty well when I tested rebuild/restore. It does require one extra step beyond just running Chef, but I restore the build history when I do this, so I do get some value out of it.

I wouldn’t be happy with this if this was for my revenue generating infrastructure, but for one-offs I’m primarily automating to make DR work smoothly so it’s an acceptable trade off.

–
Dan DeLeo


#8

On Fri, Feb 17, 2012 at 9:26 AM, Bryan McLellan btm@loftninjas.org wrote:

No, these were internal Opscode cookbooks. I doubt we would want to support
them officially the way we do others, but I probably wrote them such that
they’re modular enough. I’ll take a look at pulling them out and putting
them on github somewhere if you’re interested.

Someone asked for these so I stuck them up on github:


#9

Hey Bryan,

awesome, thanks! Will check them out as soon as I’m back on a git enabled
device :slight_smile:

Cheers,
Torben
Am 18.02.2012 02:10 schrieb “Bryan McLellan” btm@loftninjas.org:

On Fri, Feb 17, 2012 at 9:26 AM, Bryan McLellan btm@loftninjas.org
wrote:

No, these were internal Opscode cookbooks. I doubt we would want to
support
them officially the way we do others, but I probably wrote them such that
they’re modular enough. I’ll take a look at pulling them out and putting
them on github somewhere if you’re interested.

Someone asked for these so I stuck them up on github:
https://github.com/btm/btm-cookbooks


#10

Hi Dan,

Didn’t think of this so far, but it’s definitely an option. Thanks for the
hint!

Cheers,
Torben
Am 17.02.2012 18:09 schrieb “Daniel DeLeo” dan@kallistec.com:

On Friday, February 17, 2012 at 1:03 AM, Torben Knerr wrote:

On Thu, Feb 16, 2012 at 9:58 PM, Bryan McLellan <btm@loftninjas.org(mailto:
btm@loftninjas.org)> wrote:

On Thu, Feb 16, 2012 at 5:01 AM, Torben Knerr <ukio@gmx.de (mailto:
ukio@gmx.de)> wrote:

has anyone tried to set up the whole Atlassian Suite via Chef? I
know there

is a JIRA cookbook, but I would need to set up Bamboo, Fisheye,
Crowd, etc.

as well. And git or SVN as well. And everything nicely configured.
:slight_smile:

I wrote these internally at Opscode about a year ago, but they only go
as far as you would expect. You’ve still got to load up a web browser
for all the configuration. Going any further would be a feat of
engineering and unfortunately probably not stable between upstream
releases.

Bryan

Yeah, that’s what I expected. I could imagine to mechanize these steps,
but not sure if it would be worth the effort given that the webui changes
quite often between atlassian versions…
Btw: so these are the same cookbooks that Bryan Brandau refers to?

Cheers,
Torben

Having a mix of Chef and backups isn’t necessarily a bad thing when you
run into tricky applications like this. I recently set up Jenkins so that
Chef would install the software and dependencies, install plugins, and
install the libraries and such we needed to run the builds. For the actual
Jenkins config, I didn’t have the time to reverse engineer the job XML
files and write an LWRP to generate them, so I decided to just back up the
data to S3. It worked pretty well when I tested rebuild/restore. It does
require one extra step beyond just running Chef, but I restore the build
history when I do this, so I do get some value out of it.

I wouldn’t be happy with this if this was for my revenue generating
infrastructure, but for one-offs I’m primarily automating to make DR work
smoothly so it’s an acceptable trade off.

–
Dan DeLeo