Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Crowbar 2.0

Judd Maltin edited this page · 105 revisions
Clone this wiki locally

OpenCrowbar is the community oriented project: Just about everything is here: https://github.com/opencrowbar/core

Crowbar 2 is an evolution of the framework to enable both initial (à la Crowbar 1.x) and continuous deployment. The changes outlined below provide the foundation for upgrades and orchestration of complex deployments. Creating this type of dynamic infrastructure is a journey, this is our next step.

Want to participate?

In addition to the technical information on this page, please see the development page.

Background

Recent Pivot

See the Crowbar 2.0 FAQ

Project Kickoff

We kicked off the Crowbar 2.0 refactoring with an open online briefing (http://crowbar.sync.in/crowbar2) and in-person design review (http://crowbar.sync.in/crowbar2-summit).

Refactoring Objectives (from http://wp.me/pF6d2-sZ)

Our technical objective for Crowbar 2.0 is to simplify and streamline development efforts as the development and user community grows. We are seeking to:

  1. simplify our use of Chef and eliminate Crowbar requirements in our Opscode Chef recipes.
    1. reduce the initial effort required to leverage Crowbar
    2. opens Crowbar to a broader audience (see Upstreaming)
  2. provide heterogeneous / multiple operating system deployments. This enables:
    1. multiple versions of the same OS running for upgrades
    2. different operating systems operating simultaneously (and deal with heterogeneous packaging issues)
    3. accommodation of no-agent systems like locked systems (e.g.: virtualization hosts) and switches (aka external entities)
    4. UEFI booting in Sledgehammer
  3. strengthen networking abstractions
    1. allow networking configurations to be created dynamically (so that users are not locked into choices made before Crowbar deployment)
    2. better manage connected operations
    3. enable pull-from-source deployments that are ahead of (or forked from) available packages.
  4. improvements in Crowbar's core database and state machine to enable
    1. larger scale concerns
    2. controlled production migrations and upgrades
  5. other important items
    1. make documentation more coupled to current features and easier to maintain
    2. upgrade to Rails 3 to simplify code base, security and performance
    3. deepen automated test coverage and capabilities

Beyond these great technical targets, we want Crowbar 2.0 is to address barriers to adoption that have been raised by our community, customers and partners. We have been tracking concerns about the learning curve for adding barclamps, complexity of networking configuration and packaging into a single ISO.

Something went wrong with that request. Please try again.