Following on from the first visit to Bhagmalpur, a second round of software development, bugfixes and finally deployment took place in the ensuing three weeks or so. There were some lessons we had learned watching the server in action:
- Power is a huge issue. A server needs to come across as a reliable ‘always-on’ kind of appliance, and the situation in the village was not helping on this. While there are efforts to install solar panels to provide uninterrupted power, I took a UPS containing two 7.2 AH batteries, enough to supply continuous power for 12-14 hrs on average.
- Since the server (xo-1.75 laptop) was not installed in a readily accessible place, as would normally be the case, it was important it would turn itself on as soon as AC power was supplied. Thanks to Richard Smith for helping get around this.
- The server shouldn’t go into suspend when the laptop’s lid is closed. A simple setting change sufficed.
- If for any reason, some of the services being hosted by the server go down, they should be brought back up automatically. For this we experimented with a tool called monit, which proved itself to be quite useful. Monit can be smartly configured to restart many types of services.
- The service that converts the collected statistical data into usable information needs to run on the server itself, so we don’t have to transfer large amounts of data to do a proper analysis.
- A reliable method of updating and installing new server software. Since doing a vanilla install while present in the village was a cumbersome task, we had to come up with a mechanism to install all these updates/fixes in a robust, fast and repeatable manner. We used a tool called ansible to carry this out. (Hint: you will hear a lot more about ansible in future XSCE releases).
We also installed power backup to a second ubiquity picostation working in repeater mode to increase the available server uptime. The picostation consumes about 5W, so a single 7.2AH battery provides decent backup. In the evening while we were testing the range of both the AP’s, unknown to us, a bunch of kids gathered on the rooftop of Dr. Verma’s house, and started collaborating through various sugar activities and the internet.
Earlier during the day, some kids brought in a broken screen, and asked me to replace it. However, being the constructionist project that OLPC is (and the lazy person that I am), I told them to figure it out on their own. One of the kids already knew how to fix the screen, so he taught the other kid all by himself to remove the battery, unscrew the relevant parts, gently remove the display and it’s cables, plug in the new one, screw everything back in and voila! Instant joy. Just for the fun of it, a few more kids got into this hardware debugging exercise.
One byproduct of constructivism, which is often ignored is the inculcation of qualities like grit, determination and confidence, which Paul Tough has explored at some length. Having been to the village 3 weeks ago, and a year ago, I could see the change in the way the kids went about themselves and around the laptops. We will only be able to see the true effect of such changes in learning methods a few years down the line, however, we hope to carry out research analyzing the data we collect. (and discussed at length in a soon-to-be-published blog post :-)).
At night, I took a few moments to pause and reflect on a job well done, and the part everyone played to perfection. Sameer, with an accurate assessment of what was needed, and his expert insights; Santi, Nitika for handling the technology side of things, the XSCE community for providing us with a stable base, Upendra and Tripti-ji without whose everyday effort, the deployment wouldn’t even exist, the parents, who encourage their little ones to learn “the computer” even if they don’t themselves understand it’s implications and finally; the never-ending passion and curiosity of the children of Bhagmalpur. To me, the true power of democratized, community driven efforts made itself as conspicuous as the brilliant shimmering stars in the sky that night!
The following morning, I had to get up early and leave for the airport, since I was unable to find a train reservation on the way back. The newly spruced up airport named after Shri Lal Bahadur Shastri at Varanasi was a 2.5 hour bus ride away from the nearby town of Shahganj (which is also the nearest railhead to Bhagmalpur). It was interesting to note that there was no functional WiFi internet at a national airport, while we had quietly empowered the kids in a remote village unknown to the rest of the world. Saludos, Anish