[chef] Re: Re: Re: rewriting my tomcat LWRP, how best to group options?

[Bryan Berry < >]

Hey Peter,

can you point me to the code you use for configuring your jmx access?
Of the top of my head this would be best served by an heavyweight
resource provider (HWRP? PORO?) and some helper functions, both of
which could live in the in the java cookbook

Actually depositing user credentials into the credentials file for the
jvm could be a helper function that you invoke from your users recipe

What kind of resource would you like to see for the jdk logging and
jmx configuration?

Do you prefer the layout of what i have in the following example or w/
the more explicit   xx_opts, d_opts, additional_opts attributes?

jvm  do
    xms   '256m'
    xmx   '512m'
    jmx  do
        auth
        ssl
    end
    logging do
         ...
    end
end

If you myself and Andrea could find the time to chat I think it would
be very beneficial to all of us.

I am on irc from 07:00 - 18:00 CET most days and will be coding this
weekend on the tomcat cookbook. Both Andrea and I are on CET. Peter, u
r in Australia?

On Tue, Apr 17, 2012 at 3:14 AM, Peter Donald 
<
 >
 wrote:
> Hi,
>
> On Mon, Apr 16, 2012 at 4:35 PM, Andrea Campi
> <
 >
>  wrote:
>> First of all, I like what you're doing but I think it doesn't belong
>> in the Tomcat cookbook.
>> Looking at your examples, I would say every option except perhaps the
>> ports would make sense for a standalone non-web-app.
>> And what about running on JBoss or Jetty? What about JRuby or Scala apps?
>>
>> The goal of the application cookbook is to abstract away commonalities
>> and provide a single language to as many frameworks as reasonable,
>> while still allowing specific configuration.
>>
>> Without getting too specific, my main point here is: let's join effort
>> and make sure we don't invent almost the same thing twice.
>
> I would be interested in this. Currently in my setup we actually have
> common bits of code that I use to set up jmx across all the jvms. i.e.
> Our users databag gives credentials for jmx and then we can use this
> combined with app specific groups to generated access control files
> and password files for jmx access. We have also a common bit of code
> that we use to setup all the jdk logging options across our jvms.
> (Mostly so we can ship stuff over to a graylog server)
>
>
> --
> Cheers,
>
> Peter Donald