# DBOD Daemon
===============================================================================
This repository contains the code for the DB On Demand daemon and the tools
and supporting resources required to build its RPM packages using the CERN
Koji service.

Package Maintaner: Ignacio Coterillo <icoteril@cern.ch>

## DEVELOPMENT
===============================================================================
If you want to commit any code to the project, contact the DB On Demand team
about how to get the right permissions to the repository, and feel free to 
create and use topic branches as required.

Once you have tested your code you can submit a pull request by mailing the
package maintainer output of  'git request-pull':

E.g: This is an example in which I create a pull request from the qa branch
to the master branch of the it-puppet-module-dbod repository:

    pcitdb46~/workspace/it-puppet-module-dbod(qa|…) % git request-pull master origin
    The following changes since commit a83a1505c231cd98cc7b08511459c2d704431795:

      MySQL: Fixed conditions test for XX_install_db (2014-09-16 12:18:59 +0200)

    are available in the git repository at:

      https://:@git.cern.ch/kerberos/it-puppet-module-dbod 

    for you to fetch changes up to 135540c7842ad9b39aeb37f2ec4fa0f698304b81:

      Added Koji db6 prod repo creation (2014-10-10 15:00:26 +0200)

    ----------------------------------------------------------------
    icoteril (2):
          Added customization for SYSTEM type entities (daemons)
          Added Koji db6 prod repo creation

     code/manifests/customization.pp    |  2 +-
     code/manifests/init.pp             |  9 ++++++++-
     code/manifests/system/customize.pp | 26 ++++++++++++++++++++++++++
     3 files changed, 35 insertions(+), 2 deletions(-)
     create mode 100644 code/manifests/system/customize.pp

## JIRA
===============================================================================
All related issues should be tracked on the [DBOD Jira project](https://its.cern.ch/jira/browse/DBOD) 
hosted on the CERN Central jira service.

## CODE CONVENTIONS
===============================================================================
While  the totallity of the code itself doesn't at the moment adhere to any
strict conventions (ongoing effort!), there are some guidelines which all new 
code should be following:

- Explicit is better than implicit. This means avoid using Perl magic if it
 makes the code hard to read or maintain
- Use spaces instead of TAB'S (a TAB should be translated to 4 spaces)
- Failing non-void methods should return 'undef'
- 80 characters or less per line if possible
- Naming convention:
    - configuration variables or constants: $UPPERCASE
    - regular variables: $lowercase
    - methods: lowercase_underscore_joined_words()
- When in doubt, try to follow the style already present on the code