I wish I would have known that communities need to grow over time and be nurtured with a lot of care.

The chapter about community management, in Open Advice, isn't probably very long but was for me of great interest. I've got the chance (especially in the past times) to participate into some mailing lists and irc discussions related to the projects I've been involved, but I always thought I sucked at community. That is partially true!

It's about Python again. I happen to work with some Red Hat customers used to manage some rather large deployments interested in automating some of their management tasks via RHN API. I'll be trying to publish some of the tools I happened to "code" when in need of bulk actions against systems on Red Hat Network. Please give a look at the repo https://github.com/giulivo/rhn-api-tools and contribute if you can (like?).

In case you were wondering if it is possible and how to migrate a legacy NIS environment into FreeIPA (ldap/kerberos), I prepared a quick HOWTO which I hope will be useful. http://freeipa.org/page/NIS_accounts_migration_preserving_Passwords

A quickstart to the OpenShift command line client tools (rhc)

I published a small reference guide to the rhc command line tool, here it is https://github.com/giulivo/openshift-rhc-quickstart

A demo app for mobiles written using Flask and jQuery Mobile. The backend storage is MongoDB. The app allows you to check and edit some shopping lists from your mobile phone! So if your fellow file it from home, you’ll have it at your fingers later, when at the mall!

It has been deployed on OpenShift which offers MongoDB instances for free, as well as support for any Python WSGI app. Flask is installed using virtualenv.

https://github.com/giulivo/openshift-myshoppinglist, enjoy!

planning or developing for Android devices? did you know about this:

http://developer.android.com/resources/dashboard/platform-versions.html

"this page provides data about the relative number of active devices running a given version of the Android platform. This can help you understand the landscape of device distribution and decide how to prioritize the development of your application features for the devices currently in the hands of users."

Back again on OpenShift. I managed to write down some notes on how to deploy a tornado app on it: https://github.com/giulivo/openshift-hellotornado

There is also a typical 'hello world' app in the repo, hope you'll have fun, as I did.

Did you know that OpenShift allows the deployment of web apps using rails, sinatra, django, pylons, turbogears, perldancer, cake, zend, codeigniter, symfony, ee6, spring, seam, mysql, postgresql, sqlite, mongodb and cron jobs free of charge?.

Good morning! Hey, wait a second, is this Rome?

DNS Classless IN-ADDR.ARPA delegation
from http://tools.ietf.org/html/rfc2317

Let us assume we have assigned the address spaces to three different parties as follows:

   192.0.2.0/25   to organization A
   192.0.2.128/26 to organization B
   192.0.2.192/26 to organization C

In the classical approach, this would lead to a single zone like this:

   $ORIGIN 2.0.192.in-addr.arpa.
   ;
   1               PTR     host1.A.domain.
   2               PTR     host2.A.domain.
   3               PTR     host3.A.domain.
   ;
   129             PTR     host1.B.domain.
   130             PTR     host2.B.domain.
   131             PTR     host3.B.domain.
   ;
   193             PTR     host1.C.domain.
   194             PTR     host2.C.domain.
   195             PTR     host3.C.domain.

The administration of this zone is problematic. Authority for this zone can only be delegated once, and this usually translates into "this zone can only be administered by one organization." The other organizations with address space that corresponds to entries in this zone would thus have to depend on another organization for their address to name translation. With the proposed method, this potential problem can be avoided. Since a single zone can only be delegated once, we need more points to do delegation on to solve the problem above. These extra points of delegation can be introduced by extending the IN-ADDR.ARPA tree downwards, e.g. by using the first address or the first address and the network mask length (as shown below) in the corresponding address space to form the the first component in the name for the zones. The following four zone files show how the problem in the motivation section could be solved using this method.

   $ORIGIN 2.0.192.in-addr.arpa.
   @       IN      SOA     my-ns.my.domain. hostmaster.my.domain. (...)
   ;...
   ;  <<0-127>> /25
   0/25            NS      ns.A.domain.
   0/25            NS      some.other.name.server.
   ;
   1               CNAME   1.0/25.2.0.192.in-addr.arpa.
   2               CNAME   2.0/25.2.0.192.in-addr.arpa.
   3               CNAME   3.0/25.2.0.192.in-addr.arpa.
   ;
   ;  <<128-191>> /26
   128/26          NS      ns.B.domain.
   128/26          NS      some.other.name.server.too.
   ;
   129             CNAME   129.128/26.2.0.192.in-addr.arpa.
   130             CNAME   130.128/26.2.0.192.in-addr.arpa.
   131             CNAME   131.128/26.2.0.192.in-addr.arpa.
   ;
   ;  <<192-255>> /26
   192/26          NS      ns.C.domain.
   192/26          NS      some.other.third.name.server.
   ;
   193             CNAME   193.192/26.2.0.192.in-addr.arpa.
   194             CNAME   194.192/26.2.0.192.in-addr.arpa.
   195             CNAME   195.192/26.2.0.192.in-addr.arpa.

   $ORIGIN 0/25.2.0.192.in-addr.arpa.
   @       IN      SOA     ns.A.domain. hostmaster.A.domain. (...)
   @               NS      ns.A.domain.
   @               NS      some.other.name.server.
   ;
   1               PTR     host1.A.domain.
   2               PTR     host2.A.domain.
   3               PTR     host3.A.domain.
   $ORIGIN 128/26.2.0.192.in-addr.arpa.
   @       IN      SOA     ns.B.domain. hostmaster.B.domain. (...)
   @               NS      ns.B.domain.
   @               NS      some.other.name.server.too.
   ;
   129             PTR     host1.B.domain.
   130             PTR     host2.B.domain.
   131             PTR     host3.B.domain.
   $ORIGIN 192/26.2.0.192.in-addr.arpa.
   @       IN      SOA     ns.C.domain. hostmaster.C.domain. (...)
   @               NS      ns.C.domain.
   @               NS      some.other.third.name.server.
   ;
   193             PTR     host1.C.domain.
   194             PTR     host2.C.domain.
   195             PTR     host3.C.domain.