On 04/13/2012 06:51 PM, Marek Goldmann wrote: > Hi All, > > With the upcoming jboss-as-7.1.0-3 the usage outside of > /usr/share/jboss-as directory and by different user to jboss-as was > simplified. Below you can find steps how you'll be able to use it. > > Let's go with an example. I'm assuming you have a user called "tom". > > 1. Create required directory structure > > # Let's go to his home directory > cd /home/tom > # Create the root directory where we want to store > # JBoss AS configuration and temporary data > mkdir jboss-as > cd jboss-as > # Create required direcotries > mkdir data deployments log tmp configuration > > 2. Copy required configuration files (feel free to use your own!) > > # Let's copy the logging.properties > cp /usr/share/jboss-as/standalone/configuration/logging.properties > configuration/ > # Let's copy the mgmt-users.properties > cp /usr/share/jboss-as/standalone/configuration/mgmt-users.properties > configuration/ > # Copy standalone.xml > cp /usr/share/jboss-as/standalone/configuration/standalone-web.xml > configuration/ are these considered .conf files under /etc? if not, what happens on yum update of jboss, which will not update these files?

>>> # Let's copy the logging.properties >>> cp /usr/share/jboss-as/standalone/configuration/logging.properties >>> configuration/ >>> # Let's copy the mgmt-users.properties >>> cp /usr/share/jboss-as/standalone/configuration/mgmt-users.properties >>> configuration/ >>> # Copy standalone.xml >>> cp /usr/share/jboss-as/standalone/configuration/standalone-web.xml >>> configuration/ >> >> are these considered .conf files under /etc? >> if not, what happens on yum update of jboss, which will not update these >> files? > > In general above example is for users not interested in storing anything > in /etc. > > But yes, in your case all above files are stored (for example) in > /etc/ovirt-engine/jboss-as/ dir and it's symlinked to the configuration/ > dir in $JBOSS_BASE_DIR. > > Does it make sense? my question was actually if the original files are being updated via yum update, since now we'd be using copies.

On 04/13/2012 06:55 PM, Marek Goldmann wrote: > > On 04/13/2012 06:41 PM, Itamar Heim wrote: >>>>> # Let's copy the logging.properties >>>>> cp /usr/share/jboss-as/standalone/configuration/logging.properties >>>>> configuration/ >>>>> # Let's copy the mgmt-users.properties >>>>> cp /usr/share/jboss-as/standalone/configuration/mgmt-users.properties >>>>> configuration/ >>>>> # Copy standalone.xml >>>>> cp /usr/share/jboss-as/standalone/configuration/standalone-web.xml >>>>> configuration/ >>>> are these considered .conf files under /etc? >>>> if not, what happens on yum update of jboss, which will not update these >>>> files? >>> In general above example is for users not interested in storing anything >>> in /etc. >>> >>> But yes, in your case all above files are stored (for example) in >>> /etc/ovirt-engine/jboss-as/ dir and it's symlinked to the configuration/ >>> dir in $JBOSS_BASE_DIR. >>> >>> Does it make sense? >> my question was actually if the original files are being updated via yum >> update, since now we'd be using copies. > You're shipping your configuration files and therefore you're > maintaining these files. Above cp commands were just an example how to > quick-start. > > Original files stored in /etc/jboss-as/standalone are not used at all > when starting AS in the way I presented above. They can be changed and > it'll not make any difference to your environment. More, they can be > even removed and your service will still work. The original jboss-as configuration files are marked as %config(noreplace), so they will be updated during "yum update" only if the user didn't do any change since the initial installation. The installation process of ovirt-engine does such changes (it edits standalone.xml). This means that the update of jboss-as will never update those files. Instead of that I think that the ovirt-engine configuration files should go in /etc/ovirt-engine/jboss-as (and symlinked to /usr/share/ovirt-engine/standalone/configuration). These configuration files should be part of the ovirt-engine RPM and untouched during the installation, so they are updated when ovirt-engine is updated with "yum update", unless the end-user decides to manually modify them. (If at all possible I would use jboss-as system properties instead of symlinks. Are there such system properties in AS7?)

On 04/13/2012 07:35 PM, Marek Goldmann wrote: > > On 04/13/2012 06:16 PM, Itamar Heim wrote: >> On 04/13/2012 06:51 PM, Marek Goldmann wrote: >>> Hi All, >>> >>> With the upcoming jboss-as-7.1.0-3 the usage outside of >>> /usr/share/jboss-as directory and by different user to jboss-as was >>> simplified. Below you can find steps how you'll be able to use it. >>> >>> Let's go with an example. I'm assuming you have a user called "tom". >>> >>> 1. Create required directory structure >>> >>> # Let's go to his home directory >>> cd /home/tom >>> # Create the root directory where we want to store >>> # JBoss AS configuration and temporary data >>> mkdir jboss-as >>> cd jboss-as >>> # Create required direcotries >>> mkdir data deployments log tmp configuration >>> >>> 2. Copy required configuration files (feel free to use your own!) >>> >>> # Let's copy the logging.properties >>> cp /usr/share/jboss-as/standalone/configuration/logging.properties >>> configuration/ >>> # Let's copy the mgmt-users.properties >>> cp /usr/share/jboss-as/standalone/configuration/mgmt-users.properties >>> configuration/ >>> # Copy standalone.xml >>> cp /usr/share/jboss-as/standalone/configuration/standalone-web.xml >>> configuration/ >> are these considered .conf files under /etc? >> if not, what happens on yum update of jboss, which will not update these >> files? > In general above example is for users not interested in storing anything > in /etc. > > But yes, in your case all above files are stored (for example) in > /etc/ovirt-engine/jboss-as/ dir and it's symlinked to the configuration/ > dir in $JBOSS_BASE_DIR. > > Does it make sense? my question was actually if the original files are being updated via yum update, since now we'd be using copies.

On 04/13/2012 07:00 PM, Carlo de Wolf wrote: >>> Does it make sense? >> my question was actually if the original files are being updated via yum >> update, since now we'd be using copies. >> > I would expect ovirt-engine to install standalone.xml into > /var/lib/ovirt-engine/jboss-as/.... > As it is an appliance, that makes use of JBoss AS, not something to be > re-configured by users. Yes, this is way better. --Marek