Links

blueprint: reverse engineers servers

blueprint reverse engineers servers for you:

* See what's been installed.
* Standardize development environments.
* Share stacks with your team.
* Generate configurations for Puppet or Chef.
* Audit your infrastructure.

blueprint is DevStructure's workhorse tool that looks inside popular package managers, finds changes you made to configuration files, and archives software you built from source to generate Puppet, Chef, or shell code. Everything blueprint sees is stored in Git to be diffed and pushed. It runs on Ubuntu Linux 10.04 and newer.

https://github.com/devstructure/blueprint
http://devstructure.com/

Filed under // automation chef environment management puppet server

Posted March 22, 2011 by email

LinkedIn Glu: deployment automation platform

GLU is a deployment automation platform. It has been built and deployed at LinkedIn in early 2010 and then released as open source in November 2010. The goal is to be able to automate the deployment of any kind of applications accross many nodes. Although written in groovy/java, the type of applications that can be deployed through GLU is not limited to java applications. GLU is a platform and the way it was architected and designed allows you to pick and choose which part you want to use... Check the docs folder (and soon the wiki) for more documentation on GLU.

https://github.com/linkedin/glu/

Filed under // agent automation cloud deployment grid groovy java network

Posted December 8, 2010 by email

openHAB: open Home Automation Bus

Introduction

The open Home Automation Bus (openHAB) project aims at providing a universal integration platform for all things around home automation.

It is designed to be absolutely vendor-neutral as well as hardware/protocol-agnostic. openHAB brings together different bus systems, hardware devices and interface protocols by dedicated bindings. These bindings send and receive commands and status updates on the openHAB event bus. This concept allows designing user interfaces with a unique look&feel, but with the possibility to operate devices based on a big number of different technologies. Besides the user interfaces, it also brings the power of automation logics across different system boundaries.

The Technology Stack

openHAB is a pure Java solution, fully based on OSGi. The Equinox OSGi runtime and Jetty as a web server build the core foundation of the runtime.

The openHAB Designer, which is the configuration tool for the openHAB Runtime, is an Eclipse RCP application with Xtext-based editors to offer a highly user-friendly way of editing configuration files, UI definitions and automation rules. For the automation rules, JBoss Drools builds the backbone.

If you are a fan of Java/OSGi/Eclipse, openHAB should be the perfect match for you. If you are not, you might want to consider other tools like Misterhouse, which aim at almost the same thing and are very mature already.

Bindings

As the OSGi platform allows a highly modular architecture, the bindings are realized as different bundles, which can be dynamically plugged to openHAB, so that every user can decide on the bindings he is interested in.

Here are some examples for bindings (but please be aware that most are not yet implemented):

KNX
X10
1-wire
RS-232
Jabber
HTTP
Bluetooth
IrMon
Asterisk
Media player (Winamp, WMP, iTunes, Amarok, etc.)
Wake-on-LAN

User Interfaces

Currently, there is only one user interface available for openHAB, a web-based UI, which can be used from many different devices. Nonetheless, openHAB is designed in a way that there can easily be added further user interfaces; be it a remote terminal or a native iPad application.

http://code.google.com/p/openhab/