Planning configuration and templates export/import in RHQ

We are currently starting to think about what would it take to implement exporting and importing various "configuration" elements including metric and alert templates, server configuration, dynagroup definitions, users & roles and possibly other "entities" between different RHQ installations.

We were asked for this functionality a couple of times in the past and now has come the time when we’d like to take a stab at it. But for that to be truly useful, we need user feedback. If you have some strong opinions about what parts of the RHQ server’s "configuration" (which in essence is everything but the inventory) should be exportable, please shout now. You can leave your feedback here or send a message to either of our mailing lists (rhq-devel, rhq-users) or even post a message to our forums.

I’ve started a wiki page about the subject if you want to know what our current thinking about all this is. Since this is in a very early stage of planning, just about everything is up to debate. To start off the discussion, I’d like to answer the following questions:

  1. What parts of RHQ would you like to sync between RHQ servers?
    • server configuration
    • users
    • roles
    • metric templates
    • alert templates
    • content sources
    • repos
    • packages
    • dyna groups
    • plugins
    • configuration, connection settings of a resource
    • metric schedules of a resource
    • alert definitions of a resource
  2. How granular should the export be?
    • all or nothing – i.e. "true" sync
    • per "subsystem" (i.e. all users&roles, all templates, content sources &repos & packages, …)
    • pick and choose individual entities
  3. How segmented should the export be?
    • lump different entity types together in one export file
    • export per "subsystem"
  4. When should the import be run?
    • during RHQ server installation
    • any time

If you want to shape the future of RHQ, now’s the time! 😉

Posted in RHQ. 2 Comments »

2 Responses to “Planning configuration and templates export/import in RHQ”

  1. Mike Battles Says:

    I’ve seen this requested by several clients that I’ve configured with JON. I’ll just leave my two cents there..

    1. The metric templates & alert templates, dynamic groups, roles (minus resource access) apply globally and should transfer over cleanly.

    I think an important concept you should consider is the mapping of resources from one system to another. So, consider a system with JBoss servers A, B & C in each env. An instance of server A would fufill the same logical purpose in both DEV & PROD, but most likely will have different resource ids. A UI which allows you take the exported DEV configuration of server A (resource id 10001) and map to PROD’s server A (resource 10050) would be very powerful. You’d also be able to exclude servers which don’t translate into the different environment.

    2. Probably would recommend per subsystem for all the global stuff, then the ability to specify individual servers (which could then be mapped using the feature described previously).

    3. Let the admin download a one big honking XML file which could be imported into another JON env.

    4. Any time. Add “Import\Export” functions under “Administration”. If you restrict it to just initial installation, you wouldn’t be able to map any resource centric configurations (because they wouldn’t be imported into inventory yet).

    • Lukáš Krejčí Says:

      Thanks Mike, this is very interesting.

      I agree that the inventory mapping feature would be a killer. But as you correctly noted yourself, it’s not going to be easy to implement right.

      There hasn’t been done much on this feature in the past couple of months as I had to deal with other things but now I am going to concentrate on it once more.

      There are definitely going to be some discussions around this feature so if you want to get involved further, follow our developer mailing list or IRC channel where I am going to post the invites for public meetings, etc. (

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: