ha: Fix race on creation of drbd resources

The drbd OCF resource agent expects the drbd primitive and the drbd ms
resource to be created in the same transaction. When it doesn't, then
the drbd primitve will fail to be monitored, which can lead to fencing.

We didn't see that all the time because we create the ms resource fast,
so most of the time, it just works.
add travis testing support
Add optional crowbar-applied boolean attribute to schema

We add a crowbar applied attribute to mark the proposal as applied after
the chef run. This allows the UI to show that the current form of the
proposal has been 'applied' successfully (i.e. chef-client completed the
run w/ success) and that the proposal was not modified after that.

Update the proposal_schema_revision, so we can add the attribute to
schema for ('3rd party') barclamps that currently do not have it.

Refs: crowbar/crowbar#2044 (which adds this attribute to barclamps which
lack it), crowbar/barclamp-crowbar#1068 (which marks the proposals as
applied) and https://bugzilla.novell.com/show_bug.cgi?id=877486
Merge pull request #49 from dirkmueller/master

add travis testing support
Merge pull request #50 from bkutil/add_applied_attribute

Add optional crowbar-applied boolean attribute to schema
Merge pull request #42 from vuntz/fix-drbd-race

ha: Fix race on creation of drbd resources
Merge branch 'release/roxy/master' into merge-roxy
Merge pull request #51 from rhafer/merge-roxy

Merge latest changes from roxy into master
Remove the guest user

It has too many privileges and a known password.
Merge pull request #52 from dirkmueller/master

Remove the guest user
Fix drag n drop for deployment

For the HA parts we added the ```data-elements-path``` attribute, and
this should be named ```rabbitmq-server``` instead of
```database-server```.
Merge pull request #55 from tboerger/feature/master/dragndrop-fix

Fix drag n drop for deployment
Don't set NODE_IP_ADDRESS and -PORT in the env file

We already set them via tcp_listeners in the main configuration file. The
config file allow specifying multiple listeners which we will need for allowing
trove to access rabbitmq. But those setting are overridden if NODE_IP_ADDRESS
and/or NODE_PORT are present in the env file.
Allow to specifying multiple tcp_listener addresses
Add support for rabbitmq to listen on the public network

This is a requirement of Trove. The trove-guest-agent, running inside an
instance, needs access to a rabbitmq instance to be able receive messages from
trove-api. As instances don't have access to the "admin" network we need to be
able to open up the rabbitmq configuration to additionally listen on the public
interface.
Allow to create trove configuration

This includes crating a vhost, a user and permissions for that user to the
vhost.
Clarify comment on set_permissions call
Cleanup when trove features are disabled
With HA, really wait for rabbitmq to be started

Until now, we were just checking that pacemaker has marked the resource
has started. But what we really want is to start making use of rabbitmq,
and it sometimes happen that rabbitmq is still starting while we try to
add the vhost and so on.

So on top of waiting for pacemaker to mark the resource as started, also
wait for "rabbitmqctl status" to tell us that the rabbit application is
really running. This makes the wait more synchronous, like the init
script.

The sed magic comes from
http://unix.stackexchange.com/questions/10226/multiline-pattern-match-using-sed-awk-or-grep/10250#10250

This is also similar to what we do with postgresql, where we try to
connect to it when checking it's running.
Merge pull request #53 from rhafer/trove

trove related enhancements