Archive for the ‘candlepin’ Category

Latest Release of Candlepin

Posted: August 30, 2011 in candlepin, geek stuff, work

We continue to use Scrum at work, and it is working very well. The team is able to work very independently, and very quickly. We continue to roll out new features every three weeks.

Version 0.4.11 is the latest release which adds partially subscribed logic, activation keys, and lots of additional features.

Please come on bye, and help out. You can find us at http://candlepinproject.org.

Advertisements

Good blog artcile on adding search to rails apps. Used in Foreman, soon to be used in Katello and Headpin.

http://scopedsearch.wordpress.com/2011/07/11/adding-search-to-an-activerecord-rails-model/

As a followup to the Candlepin Post.. we have just opened up the larger project for Open Source Systems Management. The project is called Katello. The name rhymes with Jello, so that should help. The goal of this project is to bring together Content Management, Subscription Management, and Configuration Management.

If you are interested in participating, we would love the help. Come on bye, check it out, and say hi!

At work we have been doing alot of development around Software Subscriptions, and how to represent them to a machine as a collection of Entitlements (what a machine is entitled to have or do). It is a FOSS project which we have been working on it for a while, but have finally hung out an offical shingle. You can checkout the website at candlepinproject.org. The name is based on a place up near our offices in Westford. It is called the Bowladrome. The folks came up with the idea while bowling.

Tech wise, it is a pretty interesting project. Java Stateless App Server using Guice. It exposes a REST API provided by RESTEasy.  It has  Rails 3.0 front end, and some linux clients which are written in Python. All we are missing is Erlang and we would be all set.

Come on bye, check it out. The project is open and is being actively developed. If you work in and around software subscriptions we would be interested in your opinions.

 

If you write a framework, please do not use private. You may think that you know how I am going to use it. I promise, if it works as it should I will not try and override the basic functionality. However, if I am looking at the code to know it is private then I have a use case you did not expect.

My current example is rails active resource. This is a great framework if you are planning to use it to talk to another rails app. If your url does not end in .json then you have to override / reimplement many high level methods because of one or two private methods.

I know they teach you this in school. I know it makes you feel smart. Stop it. Private methods makes your frameworks less usable and less extensible.

We have been playing alot more with Rest at work, and we are seeing that there is alot of docs on how easy it is to spin up a REST interface. However, there is not much on how to make them good. Fortunately, I work with alot of smart people we can have good discussions with. Bill Burke has put up the results of one of the discussions on a good way of modeling state transitions on rest. Check out his post