Anyone working on a jboss cookbook?

Chef Infra (archive)
1

I am looking for a jboss cookbook but can’t find one on github or the
community site. I find it hard to believe that one doesn’t already exist or
that someone isn’t working on one.

If you have a jboss cookbook that you would like to share or collaborate on
one, please let me know.

BryanWB

2

Hi Bryan, I have been implementing ATG on JBoss for client for a few months
now and have been taking notes for a cookbook. I 've started working on it,
although I haven't figured out what level of detail I'm going to use on some
of the complex settings, like slimming and port management. My client is
not using config management and so I was using this as an excercise to keep
in practice with Chef. Ironically, I've just signed an actual client with
another client to evaluate and then implement something similar for them on
Puppet, which is kinda cool. I would welcome collaboration. My github page
is here: sbates (Sascha Bates) · GitHub

I am not sure why no one has published a cookbook because I know at least
one person has emailed me privately when I've had questions and they have
internal jboss cookbooks. I think that possibly the complexity is not
entirely apparent when you first start thinking about it and that it might
be difficult to scrub client data from an implementation or that it might be
hard to "do it right" enough to want to share or that employers may not
allow it. Those are my theories on why there is no cookbook for JBoss.

On Mon, Oct 17, 2011 at 12:14 AM, Bryan Berry bryan.berry@gmail.com wrote:

I am looking for a jboss cookbook but can't find one on github or the
community site. I find it hard to believe that one doesn't already exist or
that someone isn't working on one.

If you have a jboss cookbook that you would like to share or collaborate on
one, please let me know.

BryanWB

3

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Oct 17, 2011, at 8:47 AM, Sascha Bates wrote:

Hi Bryan, I have been implementing ATG on JBoss for client for a few months now and have been taking notes for a cookbook. I 've started working on it, although I haven't figured out what level of detail I'm going to use on some of the complex settings, like slimming and port management. My client is not using config management and so I was using this as an excercise to keep in practice with Chef. Ironically, I've just signed an actual client with another client to evaluate and then implement something similar for them on Puppet, which is kinda cool. I would welcome collaboration. My github page is here: sbates (Sascha Bates) · GitHub

I am not sure why no one has published a cookbook because I know at least one person has emailed me privately when I've had questions and they have internal jboss cookbooks. I think that possibly the complexity is not entirely apparent when you first start thinking about it and that it might be difficult to scrub client data from an implementation or that it might be hard to "do it right" enough to want to share or that employers may not allow it. Those are my theories on why there is no cookbook for JBoss.

Hmm. We're just getting started with Chef and I just sort of assumed there would be a JBoss cookbook out there. Is it because the platform implementations vary too widely for someone to make the effort for a platform-agnostic cookbook?

  • -Peter

Peter Burkholder | Sr. System Administrator (consultant)
AARP | Digital Strategy & Operations | 601 E Street NW | Washington, DC 20049
pburkholder@aarp.org | aim: peterbtech | w: 202-434-3530 | c: 202-344-7129
For optimal efficiency, I check email at 2-hour intervals during the workday
(except when on-call). Please use IM or phone to contact me for urgent matters

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk6cWKYACgkQLvy74DZcgeR82ACbBQj/WgcIC6Ve1nJovNjJPyKc
lQ0AoK89Twcf36GaGNshLHE8hBlYE0jl
=44hY
-----END PGP SIGNATURE-----

4

We have a pretty straight forward JBoss recipe that implements 5.1 GA.
We're still working on getting approvals to release any cookbooks we've
written or modified.

Since I can't share it at this time, I'd be happy to answer any questions
you have.

The current recipe we have sets up some basic attributes:
version, jboss user/group, install location, log location, bind host, server
name.

There are three templates for setting up /etc/default/jboss, the init.d
script and some environment variables. We run Ubuntu so the init.d script
is a modifed version of the default redhat one.

The recipe is pretty straight forward with setting up the user/group for
jboss, installing jboss if it doesn't exist, configures the service and
places the template in place.

On Mon, Oct 17, 2011 at 11:32 AM, Burkholder, Peter PBurkholder@aarp.orgwrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Oct 17, 2011, at 8:47 AM, Sascha Bates wrote:

Hi Bryan, I have been implementing ATG on JBoss for client for a few
months now and have been taking notes for a cookbook. I 've started working
on it, although I haven't figured out what level of detail I'm going to use
on some of the complex settings, like slimming and port management. My
client is not using config management and so I was using this as an
excercise to keep in practice with Chef. Ironically, I've just signed an
actual client with another client to evaluate and then implement something
similar for them on Puppet, which is kinda cool. I would welcome
collaboration. My github page is here: sbates (Sascha Bates) · GitHub

I am not sure why no one has published a cookbook because I know at least
one person has emailed me privately when I've had questions and they have
internal jboss cookbooks. I think that possibly the complexity is not
entirely apparent when you first start thinking about it and that it might
be difficult to scrub client data from an implementation or that it might be
hard to "do it right" enough to want to share or that employers may not
allow it. Those are my theories on why there is no cookbook for JBoss.

Hmm. We're just getting started with Chef and I just sort of assumed there
would be a JBoss cookbook out there. Is it because the platform
implementations vary too widely for someone to make the effort for a
platform-agnostic cookbook?

  • -Peter

Peter Burkholder | Sr. System Administrator (consultant)
AARP | Digital Strategy & Operations | 601 E Street NW | Washington, DC
20049
pburkholder@aarp.org | aim: peterbtech | w: 202-434-3530 | c: 202-344-7129
For optimal efficiency, I check email at 2-hour intervals during the
workday
(except when on-call). Please use IM or phone to contact me for urgent
matters

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk6cWKYACgkQLvy74DZcgeR82ACbBQj/WgcIC6Ve1nJovNjJPyKc
lQ0AoK89Twcf36GaGNshLHE8hBlYE0jl
=44hY
-----END PGP SIGNATURE-----

5

wow, great to see such a big response. I have no prior experience w/ jboss
but have a lot w/ tomcat.

I may ping you happy respondents, esp. Sascha and Bryan

My employer intends to have 30+ jboss instances (currently have 10) so there
is absolutely no way I am not going to automate it w/ chef

On Mon, Oct 17, 2011 at 6:49 PM, Bryan Brandau agent462@gmail.com wrote:

We have a pretty straight forward JBoss recipe that implements 5.1 GA.
We're still working on getting approvals to release any cookbooks we've
written or modified.

Since I can't share it at this time, I'd be happy to answer any questions
you have.

The current recipe we have sets up some basic attributes:
version, jboss user/group, install location, log location, bind host,
server name.

There are three templates for setting up /etc/default/jboss, the init.d
script and some environment variables. We run Ubuntu so the init.d script
is a modifed version of the default redhat one.

The recipe is pretty straight forward with setting up the user/group for
jboss, installing jboss if it doesn't exist, configures the service and
places the template in place.

On Mon, Oct 17, 2011 at 11:32 AM, Burkholder, Peter PBurkholder@aarp.orgwrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Oct 17, 2011, at 8:47 AM, Sascha Bates wrote:

Hi Bryan, I have been implementing ATG on JBoss for client for a few
months now and have been taking notes for a cookbook. I 've started working
on it, although I haven't figured out what level of detail I'm going to use
on some of the complex settings, like slimming and port management. My
client is not using config management and so I was using this as an
excercise to keep in practice with Chef. Ironically, I've just signed an
actual client with another client to evaluate and then implement something
similar for them on Puppet, which is kinda cool. I would welcome
collaboration. My github page is here: sbates (Sascha Bates) · GitHub

I am not sure why no one has published a cookbook because I know at
least one person has emailed me privately when I've had questions and they
have internal jboss cookbooks. I think that possibly the complexity is not
entirely apparent when you first start thinking about it and that it might
be difficult to scrub client data from an implementation or that it might be
hard to "do it right" enough to want to share or that employers may not
allow it. Those are my theories on why there is no cookbook for JBoss.

Hmm. We're just getting started with Chef and I just sort of assumed
there would be a JBoss cookbook out there. Is it because the platform
implementations vary too widely for someone to make the effort for a
platform-agnostic cookbook?

  • -Peter

Peter Burkholder | Sr. System Administrator (consultant)
AARP | Digital Strategy & Operations | 601 E Street NW | Washington, DC
20049
pburkholder@aarp.org | aim: peterbtech | w: 202-434-3530 | c:
202-344-7129
For optimal efficiency, I check email at 2-hour intervals during the
workday
(except when on-call). Please use IM or phone to contact me for urgent
matters

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk6cWKYACgkQLvy74DZcgeR82ACbBQj/WgcIC6Ve1nJovNjJPyKc
lQ0AoK89Twcf36GaGNshLHE8hBlYE0jl
=44hY
-----END PGP SIGNATURE-----