enpribus – Automating Business Infrastructure

Ever wonder why we have all these fantastic tools, but they seem to be so hard to implement and maintain into our businesses? Me too. I’m creating an open source […]

Ever wonder why we have all these fantastic tools, but they seem to be so hard to implement and maintain into our businesses? Me too.

I’m creating an open source project that hopes to address that issue by making some of those hard decisions for you. With years of experience of knowing what businesses want and need in infrastructure and development, I hope to create an open-source product that automates tools for business. Basically, you install a CD on some servers and they automatically go and install what your business needs! In one place, you have centralized administration of hosted projects and integrated development and testing environments. Need it to scale? It’ll interact with elastic computing resources in the cloud too.

Take a look and follow the project to see how things come along. It’s just a start, but  I’d love help from others willing to jump in too, especially as I progress.

As the project evolves, I will update this post.

https://github.com/ipauldev/enpribus

The project is in its infancy but so far, the framework and idea I wish to implement is as follows:

  • Based off of Ubuntu, shell scripts are intended to modify the Ubuntu installer. A preseeded .iso Ubuntu installer is created.
  • The preseeded .iso is run on a bare-metal machine and installs enpribus Suite and installs a Puppet master and git repository (for puppet configuration) into virtualized machines.
  • Alternatively, the preseeded .iso runs separate installations of the Puppet master and the git repository which accomodates existing-infrastructure installation such as existing virtualized environments or elastic computing providers.
  • The preseeded .iso is run on a bare-metal machine and installs enpribus OpenNebula nodes to increase in-house virtualized capacity/HA, etc.
  • DNS configuration would be auto-confgured. Puppet would be able to configure itself, and recreate an entire environment from a backup.
  • Resources could be moved from bare-metal virtualized hosts to elastic computing resources in the “cloud”.
  • A centralized web dashboard would be available for all administration of projects
  • PHP projects would be the intended first-supported project type

For the future:

  • Implement other supported technologies for projects besides PHP (Tomcat/Ruby/etc)
  • Implement other server types (Email/Storage/just about anything)
  • Implement Enterprise features such as user and security restrictions, integration with existing directory services, etc.
  • Whatever we can imagine, it’s almost endless
Share

About ipaul

My name is Paul Hassinger, the founder of ipaul.com. I have been an avid user of computers since a child. I started when I was about 10 years old working on an Atari computer. Since then, I grew and have had exposure to all types of technologies. I started using FIDONet on a BBS as a child and grew to the Internet. My first graphical world wide web experience was in 1993 using Mosaic. Over time I've worked with both small and large computing systems even maintaining systems serving millions of users on some of the largest social networking sites. I hope to use this blog to capture what I've learned over the years and what I do in my daily life so that others and myself may find the information useful.