Adding a README file

As the title suggests, adding a README
Adding a Gemfile and its lock file

Adding a Gemfile to this example repo.
Add omnibus-software to the Gemfile

We need some of the dependencies offered by omnibus-software, so include
that gem in the Gemfile.
Add my fork or omnibus-ruby to the Gemfile

I have added a feature to omnibus that allows for multiple omnibus
artifacts to share from a shared library_path. That library_path also
comes from another omnibus artifact...in this case it is from the
common python dependencies.

I have opened a PR which has yet to be accepted. Add my fork to this
Gemfile in the interim.
Adding a sample config file

This config file only calls out keystone, but it could be used to pin
any of the supported projects to a specific git ref.
hack in vagrantfile from omni-chef to build openstack stuffs

this adds the vagrantfile from openstack-chef but running omni-openstack
:)
add gitignore for bundle/vagrant chaff
update readme with vagrant info
Merge pull request #1 from spheromak/vagrant

Vagrant
Removing cruft from Vagrantfile

For right now I will be concentrating on Ubuntu builds as those seem to
be the most widely supported. Therefore, for the sake of simplicity, I
have updated the Vagrantfile to remove things like freebsd and smartos
as well as all platforms other than 12.04 LTS. This will get augmented
in a future iteration - at this point this is still somewhat of a proof
of concept.
tell berks about cookbook-omnibus
user lates omnibus-openstack and omnibus-software gems
Merge pull request #2 from wilreichert/fixes

updates for package deps
Update Gemfile to use the new omnibus-ruby branch

With a major refactoring of the omnibus-openstack code, I was able to
minimize my changes to omnibus-ruby. Therefore, update the Gemfile here
accordingly.
Update Vagrantfile to use yaml config

YAML is a much more readable format than json. Both can be parsed by
the YAML parser, so both are viable options. However, YAML allows me to
add much-needed comments.
Remove json example in favor of yaml example

yaml is more human-friendly than json, though both will work. Moving
this example to use yaml only at this point. Will backfill with
documentation indicating that both can be used.
version attributes were in the wrong place

version attributes are part of the top-level omnibus namespace, not
a part of source...counter-intuitive as that may be.
Update Gemfile.lock to bring omnibus-ruby changes

I made some changes to my fork of omnibus-ruby. So, update the Gemfile
accordingly.
Merge remote-tracking branch 'fork/master'