dev-lxc 0.1.2

data/.gitignore

@@ -0,0 +1,17 @@
+*.gem
+*.rbc
+.bundle
+.config
+.yardoc
+Gemfile.lock
+InstalledFiles
+_yardoc
+coverage
+doc/
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp

data/Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in dev-lxc.gemspec
+gemspec

data/LICENSE

@@ -0,0 +1,201 @@
+                              Apache License
+                        Version 2.0, January 2004
+                     http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf
+   of any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "[]"
+   replaced with your own identifying information. (Don't include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

data/README.md

@@ -0,0 +1,275 @@
+# dev-lxc
+
+A tool for creating Chef server clusters using LXC containers.
+
+Using [ruby-lxc](https://github.com/lxc/ruby-lxc) it builds a standalone server or
+tier cluster composed of a backend and multiple frontends with round-robin DNS resolution.
+
+The dev-lxc tool is well suited as a tool for support related work, customized
+cluster builds for demo purposes, as well as general experimentation and exploration.
+
+### Features
+
+1. LXC 1.0 Containers - Resource efficient servers with fast start/stop times and standard init
+2. Btrfs - Storage efficient container backend provides fast container cloning
+3. Dnsmasq - DHCP networking and DNS resolution
+4. Base platforms - Containers that are built to resemble a traditional server
+5. ruby-lxc - Ruby bindings for LXC
+6. YAML - Simple, customizable definition of clusters; No more setting ENV variables
+7. Build process closely models the docs instructions
+
+Its containers, standard init, networking and build process are designed to be similar
+to what you would build if you follow the product installation documentation so the end
+result is a cluster that is relatively similar to a more traditionally built cluster.
+
+The Btrfs backed clones provides a quick clean slate which is so helpful especially
+for experimenting and troubleshooting. Or it can be used to build a customized cluster
+for demo purposes and be able to bring it up quickly and reliably.
+
+While most of the plumbing is already in place for an HA cluster it actually can't be
+used since I haven't been able to get DRBD working inside containers yet.
+
+If you aren't familiar with using containers please read this introduction.
+
+[LXC 1.0 Introduction](https://www.stgraber.org/2013/12/20/lxc-1-0-blog-post-series/)
+
+## Requirements
+
+The dev-lxc tool is designed to be used in platform built by the
+[dev-lxc-platform](https://github.com/jeremiahsnapp/dev-lxc-platform) cookbook.
+
+Please follow the dev-lxc-platform usage instructions to create a suitable platform.
+
+The cookbook will automatically install this dev-lxc tool.
+
+### Mounts and Packages (batteries not included)
+
+As described below `dev-lxc` uses a YAML config file for each cluster.
+
+This config file describes what directories get mounted from the Vagrant VM host into
+each container. You need to make sure that you configure the mount entries to be
+appropriate for your environment.
+
+The same goes for the paths to each package. The paths that are provided in the default
+configs are just examples.  You need to make sure that you have each package you want to
+use downloaded to appropriate directories that will be available to the container when
+it is started.
+
+I recommend downloading the packages to a directory on your workstation.
+Then configure the `dev-lxc-platform` `Vagrantfile` to mount that directory in the
+Vagrant VM. Finally, configure the cluster's YAML config mount entries to mount the Vagrant
+VM directory into each container.
+
+## Upgrade dev-lxc gem
+
+To upgrade the dev-lxc gem at any time you can run `gem uninstall -x dev-lxc` inside
+the Vagrant VM and then reprovision the VM using `vagrant provision`.
+
+## Usage
+
+### Shorter Commands are Faster (to type that is :)
+
+I like to create an alias for `dev-lxc` for ease of use but for the purpose of these
+instructions I will use `dev-lxc`.
+
+	echo 'alias dl=dev-lxc' >> ~/.bashrc && source ~/.bashrc
+
+You only have to type enough of a `dev-lxc` subcommand to make it unique.
+
+The following commands are equivalent:
+
+    dev-lxc cluster init tier
+	dl cl i
+
+    dev-lxc cluster start
+	dl cl start
+
+    dev-lxc cluster destroy
+	dl cl d
+
+### Base Servers
+
+One of the key things this tool uses is the concept of "base" servers.
+It creates servers with "b-" prepended to the name to signify it as a base server.
+Base servers are then snapshot cloned using the btrfs filesystem to provide very
+quick, lightweight duplicates of the base server that are either used to build
+another base server or a usable server.
+
+The initial creation of base servers for the various platforms can take awhile so
+let's go ahead and start creating an Ubuntu 12.04 base server now.
+
+    dev-lxc create b-ubuntu-1204
+
+You can see a menu of base servers this tool can create by using the following command.
+
+    dev-lxc create
+
+### Cluster Config Files
+
+dev-lxc uses a yaml configuration file to define a cluster.
+
+The following command generates sample config files for various cluster topologies.
+
+	dev-lxc cluster init
+
+`dev-lxc cluster init tier` generates the following file:
+
+    base_platform: b-ubuntu-1204
+    topology: tier
+    api_fqdn: chef-tier.lxc
+    mounts:
+      - /dev-shared dev-shared
+    packages:
+      server: /dev-shared/chef-packages/ec/private-chef_11.1.2-1.ubuntu.12.04_amd64.deb
+    #  reporting: /dev-shared/chef-packages/ec/reporting/opscode-reporting_1.1.0-1.ubuntu.12.04_amd64.deb
+    #  push-jobs-server: /dev-shared/chef-packages/ec/push-jobs-server/opscode-push-jobs-server_1.1.0-1.ubuntu.12.04_amd64.deb
+    #  manage: /dev-shared/chef-packages/ec/manage/opscode-manage_1.1.1-1.ubuntu.12.04_amd64.deb
+    servers:
+      be-tier.lxc:
+        role: backend
+        ipaddress: 10.0.3.202
+        bootstrap: true
+      fe1-tier.lxc:
+        role: frontend
+        ipaddress: 10.0.3.203
+    #  fe2-tier.lxc:
+    #    role: frontend
+    #    ipaddress: 10.0.3.204
+
+This config defines a tier cluster consisting of a single backend and a single frontend.
+A second frontend is commented out to conserve resources.
+
+If you uncomment the second frontend then both frontends will be created and dnsmasq will
+resolve the `api_fqdn` [chef-tier.lxc](chef-tier.lxc) to both frontends using a round-robin policy.
+
+The config file is very customizable. You can add or remove mounts, packages or servers,
+change ip addresses, change server names, change the base_platform and more.
+
+Make sure the mounts and packages represent paths that are available in your environment.
+
+### Managing Multiple Clusters
+
+By default, `dev-lxc` looks for a `dev-lxc.yaml` file in the present working directory.
+You can also specify a particular config file as an option for most dev-lxc commands.
+
+I use the following to avoid specifying each cluster's config file while managing multiple clusters.
+
+	mkdir -p ~/clusters/{clusterA,clusterB}
+	dev-lxc cluster init tier > ~/clusters/clusterA/dev-lxc.yaml
+	dev-lxc cluster init standalone > ~/clusters/clusterB/dev-lxc.yaml
+	cd ~/clusters/clusterA && dev-lxc cluster start  # starts clusterA
+	cd ~/clusters/clusterB && dev-lxc cluster start  # starts clusterB
+
+### Maintain Uniqueness Across Multiple Clusters
+
+The default cluster configs are already designed to be unique from each other but as you build
+more clusters you have to maintain uniqueness across the YAML config files for the following items.
+
+1. Server names and `api_fqdn`
+
+    Server names should really be unique across all clusters.
+
+    Even when cluster A is shutdown, if cluster B uses the same server names when it is created it
+	will use the already existing servers from cluster A.
+
+    `api_fqdn` uniqueness only matters when clusters with the same `api_fqdn` are running.
+
+    If cluster B is started with the same `api_fqdn` as an already running cluster A, then cluster B
+	will overwrite cluster A's DNS resolution of `api_fqdn`.
+
+    It is easy to provide uniqueness. For example, you can use the following command to replace `-tier`
+	with `-1234` in a tier cluster's config.
+
+        sed -i 's/-tier/-1234/' dev-lxc.yaml
+
+2. IP Addresses
+
+    IP addresses uniqueness only matters when clusters with the same IP's are running.
+	
+    If cluster B is started with the same IP's as an already running cluster A, then cluster B
+	will overwrite cluster A's DHCP reservation of the IP's but dnsmasq will still refuse to
+	assign the IP's to cluster B because they already in use by cluster A. dnsmasq then assigns
+	random IP's from the DHCP pool to cluster B leaving it in an unexpected state.
+
+    The `dev-lxc-platform` creates the IP range 10.0.3.150 - 254 for DHCP reserved IP's.
+	
+    Use unique IP's from that range when configuring clusters.
+   
+### Create and Manage a Cluster
+
+The following instructions will use a tier cluster for demonstration purposes.
+The size of this cluster uses about 3GB ram and takes a long time for the first
+build of the servers. Feel free to try the standalone config first.
+
+The following command saves a predefined config to dev-lxc.yaml.
+
+	dev-lxc cluster init tier > dev-lxc.yaml
+
+Starting the cluster the first time takes awhile since it has a lot to build.
+
+The tool automatically creates snapshot clones at appropriate times so future
+creation of the cluster's servers is very quick.
+
+	dev-lxc cluster start
+
+[https://chef-tier.lxc](https://chef-tier.lxc) resolves to the frontend.
+
+Ponyville and wonderbolts orgs, users, knife.rb and keys are automatically created in
+the bootstrap backend server in /srv/piab/users for testing purposes.
+
+Show the status of the cluster.
+
+    dev-cluster status
+
+Stop the cluster's servers.
+
+	dev-lxc cluster stop
+
+Clones of the servers as they existed immediately after initial installation and configuration
+are available so you can destroy the cluster and "rebuild" it within seconds effectively starting
+with a clean slate.
+
+    dev-lxc cluster destroy
+	dev-lxc cluster start
+
+The abspath subcommand can be used to prepend each server's rootfs path to a particular file.
+
+For example, to edit each server's private-chef.rb file you can use the following command.
+
+    emacs $(dev-lxc cluster abspath /etc/opscode/private-chef.rb)
+
+After modifying the private-chef.rb you could use the run_command subcommand to tell each server
+to run `private-chef-ctl reconfigure`.
+
+    dev-lxc cluster run_command 'private-chef-ctl reconfigure'
+
+Use the following command to destroy the cluster's servers and also destroy their corresponding
+base servers so you can build them from scratch.
+
+    dev-lxc cluster destroy -b
+
+You can also run most of these commands against individual servers by using the server subcommand.
+
+    dev-lxc server ...
+
+### Using the dev-lxc library
+
+dev-lxc can also be used as a library if preferred.
+
+    irb(main):001:0> require 'yaml'
+	irb(main):002:0> require 'dev-lxc'
+	irb(main):003:0> cluster = DevLXC::ChefCluster.new(YAML.load(IO.read('dev-lxc.yaml')))
+	irb(main):004:0> cluster.start
+	irb(main):005:0> server = DevLXC::ChefServer.new("fe1-tier.lxc", YAML.load(IO.read('dev-lxc.yaml')))
+	irb(main):006:0> server.stop
+	irb(main):007:0> server.start
+	irb(main):008:0> server.run_command("private-chef-ctl reconfigure")
+	irb(main):009:0> cluster.destroy
+
+## Contributing
+
+1. Fork it
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Add some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create new Pull Request

data/Rakefile

@@ -0,0 +1 @@
+require "bundler/gem_tasks"

data/bin/dev-lxc

@@ -0,0 +1,6 @@
+#!/usr/bin/env ruby
+require 'dev-lxc/cli'
+
+raise "Must run as root" unless Process.uid == 0
+
+DevLXC::CLI::DevLXC.start

data/dev-lxc.gemspec

@@ -0,0 +1,25 @@
+# coding: utf-8
+lib = File.expand_path('../lib', __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require 'dev-lxc/version'
+
+Gem::Specification.new do |spec|
+  spec.name          = "dev-lxc"
+  spec.version       = DevLXC::VERSION
+  spec.authors       = ["Jeremiah Snapp"]
+  spec.email         = ["jeremiah@getchef.com"]
+  spec.description   = %q{A tool for creating Chef server clusters using LXC containers}
+  spec.summary       = spec.description
+  spec.licenses	     = "Apache2"
+  spec.homepage      = "https://github.com/jeremiahsnapp/dev-lxc"
+
+  spec.files         = `git ls-files`.split($/)
+  spec.executables   = spec.files.grep(%r{^bin/}) { |f| File.basename(f) }
+  spec.test_files    = spec.files.grep(%r{^(test|spec|features)/})
+  spec.require_paths = ["lib"]
+
+  spec.add_development_dependency "bundler", "~> 1.3"
+  spec.add_development_dependency "rake", "~> 0"
+  spec.add_runtime_dependency "thor", "~> 0"
+  spec.add_runtime_dependency "ruby-lxc", "~> 1.0.1"
+end

data/files/configs/ha.yaml

@@ -0,0 +1,31 @@
+base_platform: b-ubuntu-1204
+topology: ha
+api_fqdn: chef-ha.lxc
+mounts:
+  - /dev-shared dev-shared
+packages:
+  server: /dev-shared/chef-packages/ec/private-chef_11.1.2-1.ubuntu.12.04_amd64.deb
+#  reporting: /dev-shared/chef-packages/ec/reporting/opscode-reporting_1.1.0-1.ubuntu.12.04_amd64.deb
+#  push-jobs-server: /dev-shared/chef-packages/ec/push-jobs-server/opscode-push-jobs-server_1.1.0-1.ubuntu.12.04_amd64.deb
+#  manage: /dev-shared/chef-packages/ec/manage/opscode-manage_1.1.1-1.ubuntu.12.04_amd64.deb
+servers:
+  be1-ha.lxc:
+    role: backend
+    ipaddress: 10.0.3.206
+    bootstrap: true
+    cluster_ipaddress: 192.168.0.5
+  be2-ha.lxc:
+    role: backend
+    ipaddress: 10.0.3.207
+    cluster_ipaddress: 192.168.0.6
+  fe1-ha.lxc:
+    role: frontend
+    ipaddress: 10.0.3.208
+#  fe2-ha.lxc:
+#    role: frontend
+#    ipaddress: 10.0.3.209
+backend_vip:
+  be-ha.lxc:
+    ipaddress: 10.0.3.210
+    device: eth0
+    heartbeat_device: eth1

data/files/configs/open-source.yaml

@@ -0,0 +1,10 @@
+base_platform: b-ubuntu-1204
+topology: open-source
+api_fqdn: chef-osc.lxc
+mounts:
+  - /dev-shared dev-shared
+packages:
+  server: /dev-shared/chef-packages/osc/chef-server_11.0.10-1.ubuntu.12.04_amd64.deb
+servers:
+  chef-osc.lxc:
+    ipaddress: 10.0.3.205

data/files/configs/standalone.yaml

@@ -0,0 +1,13 @@
+base_platform: b-ubuntu-1204
+topology: standalone
+api_fqdn: chef-standalone.lxc
+mounts:
+  - /dev-shared dev-shared
+packages:
+  server: /dev-shared/chef-packages/ec/private-chef_11.1.2-1.ubuntu.12.04_amd64.deb
+#  reporting: /dev-shared/chef-packages/ec/reporting/opscode-reporting_1.1.0-1.ubuntu.12.04_amd64.deb
+#  push-jobs-server: /dev-shared/chef-packages/ec/push-jobs-server/opscode-push-jobs-server_1.1.0-1.ubuntu.12.04_amd64.deb
+#  manage: /dev-shared/chef-packages/ec/manage/opscode-manage_1.1.1-1.ubuntu.12.04_amd64.deb
+servers:
+  chef-standalone.lxc:
+    ipaddress: 10.0.3.201

data/files/configs/tier.yaml

@@ -0,0 +1,21 @@
+base_platform: b-ubuntu-1204
+topology: tier
+api_fqdn: chef-tier.lxc
+mounts:
+  - /dev-shared dev-shared
+packages:
+  server: /dev-shared/chef-packages/ec/private-chef_11.1.2-1.ubuntu.12.04_amd64.deb
+#  reporting: /dev-shared/chef-packages/ec/reporting/opscode-reporting_1.1.0-1.ubuntu.12.04_amd64.deb
+#  push-jobs-server: /dev-shared/chef-packages/ec/push-jobs-server/opscode-push-jobs-server_1.1.0-1.ubuntu.12.04_amd64.deb
+#  manage: /dev-shared/chef-packages/ec/manage/opscode-manage_1.1.1-1.ubuntu.12.04_amd64.deb
+servers:
+  be-tier.lxc:
+    role: backend
+    ipaddress: 10.0.3.202
+    bootstrap: true
+  fe1-tier.lxc:
+    role: frontend
+    ipaddress: 10.0.3.203
+#  fe2-tier.lxc:
+#    role: frontend
+#    ipaddress: 10.0.3.204

data/files/create_users/create_users.rb

@@ -0,0 +1,53 @@
+# Authors
+# Seth Chisamore
+# Seth Falcon
+# Jeremiah Snapp
+
+require 'chef/mixin/shell_out'
+include Chef::Mixin::ShellOut
+
+class PiabHelper
+
+  VALID_OMNIBUS_ROOTS = %w{
+    /opt/opscode
+    /opt/chef-server
+  }
+
+  def self.omnibus_root
+    @@root_path ||= begin
+      root_path = VALID_OMNIBUS_ROOTS.detect{|path| File.exists?(path) }
+      raise "Could not locate one of #{VALID_OMNIBUS_ROOTS.join(', ')}" unless root_path
+      root_path
+    end
+  end
+
+  def self.omnibus_bin_path
+    self.omnibus_root + "/embedded/bin"
+  end
+
+  def self.private_chef_ha?
+    File.exists?("/etc/opscode/private-chef.rb") && File.read("/etc/opscode/private-chef.rb") =~ /topology\s+.*ha/
+  end
+
+  def self.private_chef?
+    File.exists?("/opt/opscode/bin/private-chef-ctl")
+  end
+
+  def self.open_source_chef?
+    File.exists?("/opt/chef-server/bin/chef-server-ctl")
+  end
+
+  def self.existing_config
+    config_files = {
+      "private_chef" => "/etc/opscode/chef-server-running.json",
+      "chef_server" => "/etc/chef-server/chef-server-running.json"
+    }
+    config_files.each do |key, path|
+      if ::File.exists?(path)
+        return Chef::JSONCompat.from_json(IO.read(path))[key]
+      end
+    end
+    raise "No existing config found"
+  end
+
+end