merge changes from ITXT-4
add missing files from ITXT-4
[Bundler] Use Bundler to manage gems (for development)

This was added in the past, but it apparently caused problems so was
disabled (instead of fixing the actual issues).

Using the official code from http://gembundler.com/v1.3/rails23.html.

This change makes the development workflow much more sane - just update
the Gemfile and `bundle install` to install and develop against the
specific gems and versions. This is particularly useful when
adding, testing, updating, or removing Gems. We can also be sure that
(eg. with `bundle exec`) we're ONLY using the specified set of Gems and
corresponding versions.

The product will still use Gems installed from RPMs (NOT `bundle
install`), so we need to keep the Gemfile updated accordingly.
[Bundler] Use 'https://rubygems.org' instead of :rubygems

Avoids deprecation warning (with Ruby 1.9) and is more secure.
[Bundler] Remove unused gems: thin and formtastic
[Bundler] Specify exact Gem versions

This ensures that we use the same Gems both in development, where one
may use `bundle install`, and in the product, where they are installed
via RPMs.

Well, more or less the same since the RPM Gems, even if of the same
version, may contain additional patches, but this is rare and even so
usually does not affect the behavior.

We'll need to manually update the version strings here to match what we
package and release as RPMs, which should be fine since they don't
change much.
[Bundler] Add gems needed for running in production mode
Simplify the bus_index code

Instead of comparing the paths components by components just compare the
complete strings. The behavior of this change should be backwards compatible
with the old code.
Merge final changes
some code-level documentation
Move navigation data to crowbar.yml

The navigation.rb file will now be completely re-generated by
barclamp_install.rb.
DE1262: Fix rabbitmq-server going away.

When the logs are rotated, bluepill chef-server restart winds up
getting restarted several times in quick succession.  This can cause
bluepill to get trapped in a state where it thinks Rabbit is up when
it is not.

To work around this, have logrotate make a copy of the current log and
then truncate it.  This gets rid of the need to have the services
restart in order to continue logging messages.
Add oneshot? method to service objects

This allows barclamp to specify that there should not be a second
chef-client run in case of failures. This is needed for one-shot
barclamps, where a second chef-client run won't do anything anymore and
therefore will always result with a success.

See discussion at
http://lists.us.dell.com/pipermail/crowbar/2013-June/003302.html
Merge pull request #9 from MirantisDellCrowbar/release/pebbles/master

pull changes from dell
refactoring feature of validating chef attributes
tiny fix
raise error when node not ready -> rescue to sleep(1)
Merge pull request #569 from VictorLowther/pull-req-release-pebbles-master-b44626e09606dabf238fe782cf459142a8c080ab

Fix DE1262 -- Rabbitmq going away randomly. [1/1]
typo
Add a public_name attribute to each node

This public name can be used by the user to specify a DNS name that will
point to the the public IP of this node. This is needed since the
deployer might not want to rely on automatic DNS names added for this
host in the subdomain used for the cloud.