=== lag` is now known as lag === KKmos is now known as Kmos === qwebirc57593 is now known as geco2 === angeldaker is now known as daker [12:56] exit [12:56] hiii [12:56] any one der [12:56] wat is dis abt [13:00] rrrrrrr23: this is the classroom where sessions for ubuntu are held. https://wiki.ubuntu.com/Classroom has more information. === msnsachin12 is now known as msnsachin [13:00] but no one is teaching [13:01] rrrrrrr23: you can see the schedule at http://is.gd/8rtIi === yofel_ is now known as yofel === Quintasan_ is now known as Quintasan === msnsachin12 is now known as msnsachin === msnsachin12 is now known as msnsachin === msnsachin12 is now known as msnsachin === med is now known as medberry === _LibertyZero is now known as LibertyZero === nigelb_ is now known as nigelb === chihchun- is now known as chihchun === kim0_ is now known as kim0 === mhall119_ is now known as mhall119 === tubadaz_ is now known as tubadaz === shadeslayer_ is now known as shadeslayer [15:56] HELLO EVERYBODY! WELCOME TO THE LAST DAY OF UBUNTU DEVELOPER WEEK! [15:56] I know it's unfortunate that it's the last day, but I promise it's going to be action packed and loads of fun. [15:56] if you haven't joined #ubuntu-classroom-chat yet, please do that now [15:56] because that's where all the chatter and the questions go [15:56] you know how it works... please prefix your question with QUESTION: [15:57] first up are Brian Murray and Nigel Babu who are going to tell us how to get better bug reports [15:57] we still have a few minutes left, so go and grab yourself some coffee, tea or water and let's get cracking in 3 minutes :) === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Event: Ubuntu Developer Week - Current Session: Getting better bug reports - Instructors: bdmurray, nigelb [16:01] alright... bdmurray, nigelb: the stage is yours [16:01] ok, that's our cue! [16:01] Logs for this session will be available at http://irclogs.ubuntu.com/2011/03/04/%23ubuntu-classroom.html following the conclusion of the session. [16:01] Hello and welcome everyone! [16:02] I'm nigel from the Bug Control Team and with me is bdmurray who's with the QA Team and the Bug Master for Ubuntu [16:02] We're both going to talk to you folks today about getting better bug reports for your application [16:02] Bugs happen with software. We can't control it. [16:03] Getting good bug reports is very essential to us developers. [16:03] Sometimes along with bugs we want the user to give us certain debugging information. [16:03] Sometimes we want to talk to users just before and just after they file a bug. [16:03] One of the first things we'd like to show you is a newish LP feature. [16:04] This new feature lets us set package specific bug reporting guidelines. [16:04] For example, the ubiquity package can have specific guidelines (and it does!). [16:04] Lets take a look at the information displayed for ubiquity. [16:04] Lets all look at https://bugs.staging.launchpad.net/ubuntu/+source/ubiquity/+filebug. This is LP's staging interface and feel free to play with it. [16:05] If you enter a summary and click next, you'll get to see what I'm talking about [16:06] If you get a list of duplicate bugs, click "No, I want to file a new bug" and you should see it [16:07] Here's a screenshot of what I see http://people.ubuntu.com/~nigelbabu/Screenshot.png [16:08] So, the cool bit is we can tell our users that "Please attach the files /var/log/syslog and /var/log/partman to your bug.... [16:08] and here we get a huge advantage, the bug report now has some information that is probably absolutely necessary for triaging it [16:09] Launchpad also lets developers set the bug reported acknowledgement. [16:09] This acknowledgment might be a good way to tell people to test this package from a PPA or tell them what to expect next [16:10] This would be awesome if you have a daily build PPA for your package [16:10] (If you dont, hang around and listen to Quintasan_ later today ;) ) [16:10] The Bug supervisor for Ubuntu, which is set to Bug Control has access to edit the bug reporting information and the acknowledgement [16:10] Since I'm part of bug control, I can see this edit page [16:10] Here's a screenshot of that page: http://goo.gl/t73Lj [16:11] Any questions so far? [16:11] Moving on then. [16:12] The next very important way to get good bug reports is through apport. [16:12] nigelb: if I may [16:12] bdmurray: please :) [16:13] If you can not set the bug reporting guidelines or the acknowledgement for a particular package please let nigelb or I know, or email the bug squad, and we'll be happy to set it for you. [16:13] Anything we can do to get higher quality bug reports is a win for everyone! ;-) [16:15] techbreak asked: can you explain bit more no syslog and partman ? [16:16] So ubiquity logs information to /var/log/partman and /var/log/syslog and the developers want / need to this information to sort out what is going on [16:17] After file in the title and the description and the bottom you'll notice an attach files dialog. There you can then add a log file as an attachment. [16:17] However, we have just the tool for you techbreak which makes bug reporting much easier. [16:18] Which we'll get to shortly. [16:18] Ok, so apport is that mystery tool :) [16:18] Apport is a system which intercepts crashes right when they happen, in development releases of Ubuntu [16:18] and gathers useful information about the crash and the operating system environment. [16:19] Additionally, it is used as a mechanism to file non-crash bug reports about software so that we receive more detailed reports. [16:19] Precisly what we're talking about. [16:19] Lets take a look at a bug filed by apport. [16:20] I filed a test bug in the staging environment. [16:20] https://bugs.staging.launchpad.net/ubuntu/+source/squid3/+bug/724766 [16:20] This bug is filed against the squid3 package (the proxy server for those curious). [16:20] The title and description isn't very helpful, but hey its a test bug! [16:21] Of note here is that the squid3 package does not have an apport hook. (we'll get to what it is later) [16:21] So the information we have here is generic information that apport would collect for any package. [16:22] We have the architecture, the release being used, the package version and the source package name. [16:22] Additionally, in the Dependencies.txt attachment we have information about the versions of packages upon which squid3 depends. [16:22] Really cool isn't it? [16:22] I was talking about hooks earlier. [16:23] Apport lets us write 2 types of hooks, [16:23] one is package specific hooks that run for a particular package. [16:23] like for example a squid3 package [16:23] The other is symptom based hooks like audio or storage or display. [16:24] audio is the problem but the actual bug may be in different packages depending on the symptoms [16:24] So, questions on apport so far? === mohammed_ is now known as Guest60593 [16:24] netsplit's playing havoc today, stay with us :) === Guest60593 is now known as Safwat [16:25] Lets take a look at /usr/share/apport/package-hooks to see what hooks are on your computer right now. [16:26] One thing common among a lot of files in that folder is that a majority of them were probably written by bdmurray ;) [16:26] When you open that folder there's going to be a lot of python files [16:27] almost all of them are of the pattern source_foo.py === Pendulum_ is now known as Pendulum === msnsachin12 is now known as msnsachin [16:27] Well, apport hooks are all written in python because apport itself, I belive, is written in python === _LibertyZero is now known as LibertyZero [16:28] nigelb: it is written in python [16:28] Aha! [16:28] I wasn't sure ;) [16:28] and now you are! ;-) [16:28] heh, thanks [16:28] Lets take a look at one of the hooks [16:29] There are some really simple ones and some really complicated ones in there [16:29] Open the source_totem.py file [16:29] That's the hook for totem, the media player [16:29] Its on the default install, so the hook should be in most of your computers [16:30] In case you don't have the file, head over to http://goo.gl/UUWpt [16:30] techbreak> can you tell me what actually a hook is ? a bug ? a problem ? [16:31] I figure this question would benefit a common answer. [16:31] A hook is a python script that gets executed when you run ubuntu-bug [16:31] So, we do smart things in the hook like as you questions, run certain processes, gather certain log files, and get them all onto launchpad === msnsachin12 is now known as msnsachin [16:34] Lets look at the import statements in the totem hook first [16:34] apport.hookutils and apport.packaging are the significant ones [16:34] You can look at 'pydoc apport.hookutils' and 'pydoc apport.packaging' to see the functions in both these imports [16:35] Basically both of them provide a collection of readymade and safe functions for many commonly used things. [16:35] There are functions for attaching a file's contents, getting a command's output, grabbing hardware information and much more. [16:36] In this hook, we start with asking the user a question and providing 3 choices for an answer. [16:36] The question is "How would you describe the issue?" and the options are "The totem interface is not working correctl", "No sound is being played", "Some audio files or videos are not being played correctly". [16:37] While the first one is definitely something to be filed against totem, the other 2 may not be a totem problem. [16:37] I mean, how can you blame the media player if your sound driver itself has a bug ;) [16:37] If the user selected "No sound is being played", we'd come to "if response[0] == 1:", which means the problem is actually a something to do with audio and not totem, so we open the audio hook. [16:38] there, we straightfoward use a python function to execute another program [16:38] And if the user selected "Some audio files or videos are not being played correctly", we come to if "response[0] == 2:" where we add the gstreamer package info. [16:39] Here we use a function provided by apport to add information about a package [16:39] Now turn your attention to lines 16, 17, and 18. [16:39] The lines are self explanatory, but I'll take a moment to name those functions [16:39] apport.hookutils.command_output, apport.hookutils.package_versions, and apport.hookutils.read_file [16:40] Very self explanatory and the pydoc command I gave earlier should explain all of these functions [16:40] With these 3 commands we've added valuable debugging information for the developer. All this information will be uploaded to launchpad and attached to the bug report. [16:40] As a developer you'll surely recognize the value of this information. [16:40] That was a bit of information cramming. Are there any questions so far? [16:42] techbreak asked: i just checked /var/log.. but there is neither syslog or partman directory.. [16:42] err, sorry [16:42] techbreak asked: can we edit this .py files if we think it can be better and submit ? [16:43] In short, yes! [16:43] All these files belong to a particular package. Like the source_totem.py in the totem package. [16:43] If you'd like to help make it better, get the code, open a bug, and submit a patch [16:44] report a bug about the sourcepackage providing the file so in this example totem [16:44] You can poke bdmurray or me in #ubuntu-bugs and we'd be happy to review and help get it packaged === popey_ is now known as popey [16:44] you can use dpkg S /path/to/file to figureout which package [16:45] err, that was dpkg -S /path/to/file [16:45] One of my favorite hooks is the new audio hook, http://goo.gl/r4dFW [16:45] Don't get alarmed by its size though [16:46] It asks good questions and manages to be very friendly in diagnosing audio problems. [16:46] There are some other neat things you could do with hooks, like add tags to the bug report. [16:47] For example, if a particular question is answered, you want to add a particular tag [16:47] This helps reduce the load with triaging [16:47] To see an example of that, see the cheese hook, http://goo.gl/tsJ6G [16:47] See line numbers 9, 42, 45, 72-76 for the bits where the tags come into play. [16:47] If you know python, its kind of simple to read what's done. [16:49] With the cheese hook tags are added based on symptoms, so the devs have a generic idea of the bugs === Quintasan_ is now known as Quintasan === dpm_ is now known as dpm [16:50] There's developer information for Apport available at https://wiki.ubuntu.com/Apport/DeveloperHowTo. [16:50] There are lots of packages without an apport hook. [16:51] Well, that's partially because there are a lot of packages. ;-) [16:51] Clearly we've shown how much an apport hook helps get better bug reports for a package [16:51] There are 10 minutes remaining in the current session. [16:51] heh, that too ;) [16:51] If you'd like to write a hook for your own package and need help, feel free to poke either me (nigelb) or Brian Murray (bdmurray) in #ubuntu-bugs. [16:52] Some of the fairly new hooks we've managed over the last few cycles is the rhythmbox book (I wrote that one), cheese hook (kermiac, a fellow bug control member wrote that one), and a few more that I now forget [16:53] ah, thanks techbreak. rhythmbox *hook* :0 [16:53] :) [16:53] I fail at typing :p [16:53] Anyway, that's the end of our session. [16:54] We'll take questions now :) [16:54] bdmurray: Anything you want to add? [16:55] Once you have bugs reported by apport in Launchpad because the data is in a regular format it is also possible to some automated processing of those bug reports using the Launchpad API. === maxb_ is now known as maxb [16:56] There are 5 minutes remaining in the current session. [16:56] With the combination of high quality reports and some automatic processing your bug life can become much easier. [16:56] and our triaging life too ;) [16:58] Another neat thing about the cheese hook is that it asks you to close cheese so that it gets run in debug mode. [16:58] The possibilities of what you can do with apport really are amazing. [16:59] Feel free to ask nigelb or I any questions. We are always in #ubuntu-bugs. [17:00] ok, I guess we're done [17:00] Next up is kim0, the man behind the clouds ;) [17:01] Hello Hello everyone o/ [17:01] Logs for this session will be available at http://irclogs.ubuntu.com/2011/03/04/%23ubuntu-classroom.html following the conclusion of the session. [17:01] Kim0 is going to talk about Introducing boto EC2 Cloud API. kim0, the stage is all yours :) [17:01] Thanks nigelb === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Event: Ubuntu Developer Week - Current Session: Introducing boto EC2 Cloud API - Instructors: kim0 [17:02] It's really a pleasure to be presenting in UDW [17:02] So the topic of the session is "intro to boto ec2 api" [17:02] basically what that means is [17:02] how to control the Amazon EC2 cloud [17:02] from the ease and comfort of your python shell [17:03] Please feel free to shoot any questions to me in #ubuntu-classroom-chat [17:03] just prepend your questions with QUESTION: [17:03] I'll give a few lines intro [17:03] since many might not be totally familiar with cloud means [17:04] basically, cloud computing has tons of different definitions [17:04] however, almost everyone will agree [17:04] resources have to be allocated by an api call [17:04] and that resource allocation is instantaneuous [17:04] and that it should be elastic and almost infinite [17:05] Amazon ec2 cloud meets those conditions [17:05] so basically [17:05] through an api call [17:05] you're able to very quickly allocate computing resources [17:05] i.e. servers, networking gear, IPs, storage space [17:05] ...etc [17:05] you use them for as much as you want [17:05] then you simply "delete" them [17:06] So in real life [17:06] assuming you (as a developer) were tasked with the compute heavy task of say converting 100k text files into PDFs [17:07] a "typical" implementation would be to spawn 20 servers in the cloud [17:07] kick them crunching on the conversion .. and finish in say 2 hours [17:07] then delete that infrastructure! [17:07] and yes, you only pay for the used resources (40 hours of compute time) [17:07] lovely, isn't it :) [17:08] Any questions so far on the general concepts [17:08] before I start digging into boto [17:09] Ok .. assuming no one has questions [17:09] let's get started [17:09] the first step would be to install the python-boto package [17:10] sudo apt-get install pyton-boto [17:10] I also prefer to work in the ipython envrionment [17:10] sudo apt-get install ipython [17:11] short break .. taking questions [17:11] techbreak asked: short introduction to urself please.. we wonder who our session master is :) [17:11] hi techbreak :) I'm Ahmed Kamal, the ubuntu cloud community liaison [17:11] My role is to help the ubuntu cloud community grow and succeed [17:12] I always hang-out at #ubuntu-cloud [17:12] feel free to ping me anytime [17:12] techbreak asked: i have seen examples of cloud to be "facebook" too.. how facebook can be a cloud ? [17:13] well yes, FB is considered a cloud app [17:13] It is a cloud "application" [17:13] not a cloud platform [17:13] the likes of Google apps (gmail, gdocs...) facebook .. [17:13] are all considered cloud apps [17:13] because the data and code are distributed in highly distributed system [17:14] I could go into all sorts of details, but that question is a bit offtopic .. feel free to pick it up later :) [17:14] techbreak asked: ipython ? iron ptyhon ? [17:14] ipython is "interactive python shell" afaik [17:14] ok .. assuming you're all set [17:15] → back to boto === msnsachin12 is now known as msnsachin [17:15] In order to actually execute the steps here .. you'd need to have an amazon ec2 account [17:15] setup and have generated secret keys and stored your variables in ~/.ec2/ec2rc [17:16] this is outside the scope of this tutorial however [17:16] for those interested [17:16] follow along with https://help.ubuntu.com/community/EC2StartersGuide [17:16] If you spot any wrong info, let me know [17:16] In all examples, I will copy/paste [17:16] the api calls and the results [17:17] so that everyone can follow along easily [17:17] $ ipython [17:17] we're now inside the ipython interperter [17:17] import boto [17:17] the boto python module is imported (ready to be used) [17:17] The Amazon cloud is composed of multiple regions [17:17] similar to "data centers" all around the world === ampelbein_ is now known as Ampelbein [17:18] we need to pick one to connect to [17:18] let's see how to do that [17:19] from boto import ec2 [17:19] regions = ec2.regions() [17:19] Out[7]: [17:19] [RegionInfo:eu-west-1, [17:19] RegionInfo:us-east-1, [17:19] RegionInfo:ap-northeast-1, [17:19] RegionInfo:us-west-1, [17:19] RegionInfo:ap-southeast-1] [17:19] What you see are the Amazon regions (data-centers) around the world [17:19] we'll pick the one in us-east-1 to work with and connect to! [17:20] >> useast = regions[1] [17:20] I will prepend all python input code with (>>) to make it easily distinguishable [17:21] >>useast.endpoint [17:21] u'ec2.us-east-1.amazonaws.com' [17:21] Let's connect [17:21] >> useconn = useast.connect() [17:21] Awesome [17:22] we're now connected [17:22] let's do something useful [17:22] by default .. Amazon configure its cloud firewall [17:22] to block all incoming port connections [17:22] the rule-sets .. are called "secutiy groups" in its jargon [17:23] let's get a list of security groups available [17:23] >> useconn.get_all_security_groups() [17:23] Out[14]: [SecurityGroup:default] [17:23] the result is a single group called "default" ... makes sense! [17:25] just a little note, for anyone trying to setup a new account with amazon, you're gonna need a credit card [17:26] while they offer a completely free instance (micro type) free for a year [17:26] i.e. you most likely won't be charged anything .. but you still need a valid one [17:26] try to follow along with me in the session, I'll be pasting all input on output [17:26] back on track [17:26] so let's get our security group (firewall rule) [17:26] sg=useconn.get_all_security_groups()[0] [17:27] let's "open" port 22 [17:27] that's for ssh [17:27] >> sg.authorize('tcp', 22, 22, '0.0.0.0/0') [17:28] Ok .. [17:28] so let's quickly recap [17:29] what we've done [17:29] we've enumerated amazon cloud datacenters .. and chose to connect to the one in us-east [17:29] and we're manipulated the firewall to open port 22 [17:29] all using API calls .. all on-demand and elastic [17:30] let's start the really cool stuff :) [17:30] let's start our own cloud server [17:30] a little intro [17:30] Ubuntu created official ubuntu cloud images, and publishes them to the amazon cloud [17:30] each published image is called AMI [17:30] Amazon Machine Image [17:31] and each AMI .. has its own "id" .. which is like a long number identifying it [17:31] when you want to start a new cloud server, you tell amazon what ami you want to use .. then it clones that ami and starts an "instance" of that ami for you! [17:31] so let's do that [17:32] >> ubuimages=useconn.get_all_images(owners= ['099720109477', ]) [17:32] note that useconn .. is the us-east connection we had setup [17:32] get_all_images() is the call to get a list of images from amazon [17:32] the "owners=['099720109477', ]" part .. is basically a filter .. that number is the ID for Canonical .. so that you only get official ubuntu images [17:33] while you can start using fancy code to filter the huge list [17:33] of images to what you want! [17:33] You could use code like [17:33] nattymachines = [ x for x in ubuimages if (x.type == 'machine' and re.search("atty", str(x.name))) ] [17:33] I prefer a simpler approach [17:34] Visit the Ubuntu cloud portal [17:34] http://cloud.ubuntu.com/ami/ [17:34] this page shows a listing of all publicly available ubuntu images [17:34] You just use the search box on the top right to search for what you want [17:35] In my case, I searched for "us-east natty" [17:35] the ami ID is shown in the table and you can simply copy it! [17:35] For me it's ami-7e4ab917 [17:36] so let's filter the list using that ID [17:36] >> natty = [ x for x in ubuimages if x.id == 'ami-7e4ab917' ][0] [17:36] >> natty.name [17:36] Out[22]: u'ebs/ubuntu-images-milestone/ubuntu-natty-alpha3-amd64-server-20110302.2' [17:36] voila .. as you can see [17:36] it's a natty image .. alpha3! [17:36] hot from the oven :) [17:37] Let's go ahead and start a server [17:37] >> reservation = natty.run(key_name='default',instance_type='t1.micro') [17:37] natty.run() starts an image [17:37] the key_name .. is your ssh key .. this is part of setting up your Amazon ec2 account [17:38] that key is injected into the ubuntu instance as it boots, so that you're able to ssh into it later [17:38] The instance_type parameter .. is the "size" of the server you want [17:38] in my case, I'm starting the smallest one .. micro [17:38] since I'm executing this live [17:38] the server must have been created right now [17:39] in a matter of seconds [17:39] the API call [17:39] returns as "reservation" [17:39] let's interrogate that [17:40] >> instance = reservation.instances[0] [17:40] Let's see if the server is ready [17:40] >> instance.state [17:40] Out[26]: u'pending' [17:40] oh .. that's interesting [17:40] state pending means it's still being allocated [17:40] any questions so far ? [17:41] now is a good time while amazon allocates the instance :) [17:41] not that it takes more than a few seconds actually [17:41] Great [17:41] it's ready [17:41] >> : instance.update() [17:41] Out[28]: u'running' [17:42] The serer has been created, booted, my ssh key "default" injected into it [17:42] how do we login you say [17:42] let's ask about the serer's name [17:42] >> instance.public_dns_name [17:42] Out[29]: u'ec2-184-72-132-193.compute-1.amazonaws.com' [17:43] I can now ssh into that Ubuntu cloud server just like that [17:43] ssh ubuntu@ec2-184-72-132-193.compute-1.amazonaws.com [17:44] If I had used a different ssh key, I would nice ssh "-i" parameter .. but I'm using my default "~/.ssh/id_rsa" .. so no need to do anything [17:46] I've just configured the server to allow [17:46] you guys to ssh into it [17:46] Go ahead [17:46] ssh session@ec2-184-72-132-193.compute-1.amazonaws.com [17:47] password: session [17:47] please don't do anything nasty :) [17:47] Once logged in .. feel free to start byobu [17:47] a nice colorful gnu/screen customization [17:47] I'm ready to take some questions [17:49] ranamalo asked: when new packages are released are they incorporated in the ubuntu ami's? Like if openssh is currently 5.3 and 5.4 is released today, if fire up the ubuntu ami tomorrow will i have 5.4 installed? [17:49] ranamalo: Well, with package being updated [17:49] new AMIs are pushed [17:50] remember that AMI-ID we got ami-7e4ab917 [17:50] that we got from cloud.ubuntu.com/ami [17:50] every couple of weeks or so [17:50] updates will be pushed [17:50] and a new image will be created [17:50] however [17:50] if you're running an older image .. there's nothing preventing you from apt-get dist-upgrade 'ing it [17:51] There are 10 minutes remaining in the current session. [17:51] this is espeically true if you're running natty or a recent maverick (pvgrub booted instance) .. not too important for now [17:52] techbreak asked: if you are copy pasting can you link us to the python code ? so that we can have the code and you can explain one by one / [17:52] Here you are [17:52] http://paste.ubuntu.com/575608/ [17:52] That's all the commands I've written so far [17:52] you can practice on your own later [17:53] and if you need any help .. everyone at #ubuntu-cloud is more than helpful (at least I hope so) :) [17:54] mhall119 asked: does boto work on UEC as well? [17:54] mhall119: yes it does AFAIK [17:54] UEC is Ubuntu Enterprise Cloud [17:54] it's a private cloud product [17:54] that you can use to run your own cloud (like Aamzon) [17:54] on your own hardware [17:54] It is based on the eucalyptus open source project [17:54] for more info on using boto with UEC .. check out this link http://open.eucalyptus.com/wiki/ToolsEcosystem_boto [17:55] ranamalo asked: what advantages are there to using boto over ec2-ami-tools and ec2-api-tools? [17:56] There are 5 minutes remaining in the current session. [17:56] ranamalo: well, you can use command line tools in those packages [17:56] to effectively do the same thing [17:56] however the benefit of using python bindings [17:56] is clear .. if you're writing a tool [17:56] or some program [17:56] running external commands [17:56] and parsing results from the stdout text [17:56] is effectively hell [17:56] for programmers [17:57] an API provides a consistent clean interface [17:57] akshatj asked: What would be the advantages of deploying dmedia( https://launchpad.net/dmedia ) on clous? [17:57] * kim0 checking that out [17:58] akshatj: I'm not familiar with that project [17:58] however the generic advantages would be [17:58] you don't worry about hardware [17:58] you don't manage the infrastrucutre [17:58] you can scale-up/down easily cheaply [17:58] ranamalo asked: Is there a howto url you can give us? [17:59] * kim0 racing to answer :) [17:59] howto url for ? [17:59] a boto howto [17:59]