Sunday, March 21, 2010

Large scale Linux Migration - Issues and Lessons learned

An excellent article in problems faced during a whole scale migration to Linux. A must read for those wondering/planning to migrate. The simple lesson brought out for a painless migration is:
(a) Adopt Open Document Format (ODF) by using OpenOffice - even on Windows platform
(b) Start with 10% change/migration, then assess the application and then move ahead
The typical issues faced (how true - the profound truth):-

The lack of open standards for interoperability and the domination of lock-in interfaces was awful," bemoans the Linux advocate. He notes that this only becomes apparent when you try to make yourself independent of a single vendor, and stop being a "happy slave

Also worthy of mention were Microsoft Office macros, written in Visual Basic and present "in large numbers". This dependence was significantly reduced during the switch to OpenOffice by using alternatives such as the in-house, platform-independent WollMux for managing templates, text building blocks and web applications

Check out this article dated 19 Mar 10 at http://tinyurl.com/ybtmqqo

LiMux project management, "We were naïve"

LiMux Project Logo

19 Mar 10. Florian Schießl, deputy head of Munich's LiMux project for migrating the city's public administration to Linux, has, for the first time, explained why migrating the city's computing landscape to open source software has taken longer than originally planned. On his blog, the IT expert admits that "We were naïve," and confesses to a "miscalculation". Following approval of the project in 2003, LiMux was conceived as the sole Linux client, which "fits into every different environment inside the IT units." This may have been "theoretically possible", but, according to Schießl, would have meant failing to unify the existing patchwork of IT applications and essentially continuing to muddle through.

Previously, around 1,000 staff had been maintaining the 15,000 PCs making up the Munich computing landscape in 21 independent IT centres. There was, according to Schießl, no common directory, no common user management, no common hardware or software management. There were more than 300 applications in use, many of which did the same job. On the desktop side, there were 21 different Windows systems with different update levels and security settings.

Consequently, problems were encountered in switching to the new Linux client in accordance with the original plan. Schießl explains that the process ran smoothly in some departments, but failed to progress in others, because the "technical back end structure hampered or even declined cooperation". They found implementation errors in basic server protocols and proprietary tools which were not compatible with any other software-based management solution. "The lack of open standards for interoperability and the domination of lock-in interfaces was awful," bemoans the Linux advocate. He notes that this only becomes apparent when you try to make yourself independent of a single vendor, and stop being a "happy slave".

In an interview with heise online, Schießl has expounded on some examples of proprietary "digital waste". A "classic ActiveX dependence" on Microsoft's Internet Explorer was found in some areas, even in specialist procedures. "We had to either make the specialist software independent in consultation with the vendor or select an alternative product." Also worthy of mention were Microsoft Office macros, written in Visual Basic and present "in large numbers". This dependence was significantly reduced during the switch to OpenOffice by using alternatives such as the in-house, platform-independent WollMux for managing templates, text building blocks and web applications. The use of a range of file and printing services was also an impediment during the consolidation process. Samba, with support for the CIFS protocol, is now operating as the standard file server.

After the difficulties with the first wave of migrations, in 2007 the LiMux administrative team agreed on a new strategy. This involved implementing pilot projects in all departments to convert at least ten percent of existing PCs to the basic LiMux client in order to assess the degree of heterogeneity of the existing organic IT landscape. The city council decided at the same time to comprehensively reorganise its entire computer infrastructure in line with LiMux' "Quality over time" motto.

Since the end of last year, test runs have, says Schießl, shown that the Linux client can be fully integrated into these heterogeneous environments. According to Schießl, the pilot projects have been successfully concluded. A total of 3,000 computers are running open source software, twice as many as planned under the new initiative. Converting all computers to the Open Document Format (ODF) standard has overcome dependency on a single office software suite. The team is now getting down to the optimisation phase, aimed at improving efficiency and supporting "digital sustainability". Schießl is confident that the remainder of the migration will proceed in a similarly smooth and rapid fashion.

Wednesday, March 17, 2010

Web Developers Handbook

Completely bowled over by this site:
http://www.alvit.de/handbook/

A must visit for web developers/designers/hobbyist and free-lancers!!
Seems an encyclopaedia for CSS/XHTML/Standards with excellent references and blog links!! Loved it - and needed to bookmark it in my blog.

Sunday, March 14, 2010

Ramasseri Idli 


Fun & Info @ Keralites.net


Got this as a forward in my mailbox. And being an avid 'idlli-fan' /eater could not resist recording this in my blog to ensure that next time I am ther in that part of the country, should have a go at Ramasseri Idli!!

Dedicated to all the 'idlli lovers'!!!

Ramasseri Idli
Ramasseri, an offbeat village in Palakkad is known all over Kerala for the idlis. It make the delicious Ramasseri Idli. Take an 8 - km drive from Palakkad town and embark on a culinary trip to Ramasseri , a nondescript hamlet , reputed for its fluffy idlis. Unique in shape , size and taste. Spongy and soft Ramasseri Idli is slightly different in shape from the conventional idlis. It is a little flat and round... just like ‘’ dosa ‘’.. Ramasseri Idli is eaten with Podi mixed in coconut oil. The beginning was from a Mudaliar family living near Mannath Bhagavathi Temple in Ramasseri near Elappully.

Fun & Info @ Keralites.net


Fun & Info @ Keralites.net


The recipe of Ramasseri idli dates back to about one century,which again is a trade secret. The Muthaliyar family had migrated to Palakkad from Kanchipuram in Tamil Nadu. The new generation in the profession says that the secret of the recipe and taste were handed down to them from the older women of the community. Now the idli business is confined to four families in Ramasseri. Selection of rice is very important in making Ramasseri idli. Usually the varieties used are Kazhama, Thavalakannan, Ponni etc.

Fun & Info @ Keralites.net



The Idli Cooker
The taste depends on the boiling of paddy itself. Drying and dehusking are also important and need to be done in a particular way. The combination of rice and black gram is also equally important. For 10 kg of rice, one kg of black gram is used. Idli is made only after four hours of fermentation. Steaming of the idli is done on a cloth covered on the mud pot using firewood ( wood from tamarind trees ). Steaming time is only 2 - 3 minutes .This allegedly provides a special taste to the preparation. Idlis can be preserves for two to three days in moderate climate.
Fun & Info @ Keralites.net


Be at Saraswathi Tea Stall at the crack of dawn to avoid the separate queues. It is fascinating to watch these idlis being steam cooked in mud pots arranged in a unique three - tiered manner. These flat , round idlis - served with sambar , chutney , idli podi - melt in your mouth. You won’t be able to stop at one.

Available at

Sankara Nivas Tea Stall
Ramasseri
Palakkad

Saraswathi Tea Stall
Ramasseri
Palakkad
Tel # 04922 - 2583995

__._,_.___