amits is currently certified at Journeyer level.

Name: Amit Shah
Member since: 2003-01-31 07:23:08
Last Login: 2010-02-22 09:45:10

FOAF RDF Share This

Homepage: http://www.amitshah.net/

Notes:

Interests
* Virtualization (KVM , QEMU)
* Linux
* Free Software
* Debian
* Fedora

Hobbies:
* AudioLink project, which makes managing and searching music on local storage a breeze. It's basically a music cataloger / categorizer and a playlist generator.

Projects

Recent blog entries by amits

Syndication: RSS 2.0

Speaking at the CentOS Dojo, Pune

I’ll be speaking about KVM, progress since EL6, and other virt stuff at the CentOS Dojo in Pune this Saturday, 22nd November.  If you’re in Pune, feel free to register and drop by!

Syndicated 2014-11-17 09:56:30 from Think. Debate. Innovate.

Fedora Activity Day: Security I

Last Saturday a few of us gathered to work on Fedora Security.  This FAD (Fedora Activity Day) was the second in recent times held in Pune, after the testing FAD held in August.

Security FAD

The goal of the FAD was to get introduced to the newly-formed Fedora Security Team, pick up a few bug reports that were tagged as security-relevant bug reports, and triage them.  Fixing the bugs wasn’t part of the agenda, as actually pushing package updates needs one to be a provenpackager or the maintainer of the package.

We were assembled at the Red Hat Pune office.  I took a shot at transcribing PJP’s intro talk on the #fedora-india IRC channel, and a couple of people joined remotely in the triaging activity, which was quite nice to see.

The FAD wiki page had all the relevant information on how to go about triaging the bugs, so it was all quite straightforward from there.

I got a bit bored by just going through bug reports, without much “action” happening — it depended on the bug we selected on whether we just needed to set needinfo? on the assignee of the bug, or actually check progress of packages upstream, whether a patch was available, etc.  I just looked through bugs which looked relevant to virtualization, and then wanted to look at different ways to contribute.

PJP suggested looking at some fuzzers, and actually running them.  He pointed me to Radamsa as an example.  That does look like a good tool to generate some random input to programs, and see how they behave under unexpected input.  I didn’t actually get to run it, but now have an idea on what to do when I feel bored again.

While reading about Radamsa, I also thought a bit on how to fuzz qemu.  Nothing concrete came up, but one thought is to send weird stuff from guests to the host, by way of weirdly-formatted network packets (to test virtio-net or other net device emulations), or block device requests (to test virtio-blk / virtio-scsi / ide / ahci).  That’s an idea for a side project.

There also was a Docker meetup running at the same time at the office, so I dropped in there a couple of times to see what they were upto.  The organizers had split the session into talks + hackathon; and both were very well-attended.  In my lurking there, I overheard what Kubernetes is about, and a few terminologies it introduces into the tech world: minions and pods.  I’m sure we’re going to run out of words in the English language to re-purpose to technical usage very soon.

The FAD was originally supposed to happen in September, but got delayed to November.  For the next installation of Fedora-related activities, we may do an F21 release party along with a few user talks.  Regular FADs should resume in January, I suppose.

Syndicated 2014-11-03 18:28:12 (Updated 2014-11-03 18:29:12) from Think. Debate. Innovate.

KVM Forum 2014

It’s been a couple of weeks that I’ve returned from Düsseldorf, Germany, after attending the seventh KVM Forum; an event where developers and users of the Linux virtualization technology gather to discuss the state of the hypervisor and tools around it, and brainstorm on future plans. As with the previous few years, the event was co-located with LinuxCon Europe.

IMA_4326

A few observations from the event, in random order:

  • Linux Foundation did a great job of hosting and planning the event.
  • This was the first time when the food was great!  There were even options for vegetarians, vegans, and kosher food.
  • The venue, Congress Centre Düsseldorf, was huge, and located perfectly along the picturesque Rhine river.
  • It was the first KVM Forum which Avi did not attend.
  • The schedule was nicely-paced, with not too many parallel talks, and plenty of opportunities for hallway discussions and meeting people.
  • Co-locating with the Linux Plumbers Conference, LinuxCon, CloudOpen, etc., conferences ensured there were a lot of people interested in Linux in general; and since almost everyone is at least a user of virt technologies, discussions with almost anyone is fruitful around how KVM/QEMU/libvirt get used, and what users expect from us.
  • All the talks were recorded on video, and are available in this youtube playlist.
  • Photos from the event are here
  • All the slides from talks are at the KVM Forum wiki page
  • The QEMU Summit was also held along with the Forum; notes from the Summit are posted on the qemu devel mail list.
  • Jeff Cody’s talk on an intro to writing and submitting patches to qemu, and working with the community, got very positive feedback.  At least two people told me it would’ve been good to have that talk a year back, when they were getting started.  Well, it’s now available on the ‘net, and archived for people just starting out!
  • The OVA (Open Virtualizaiton Alliance) session on connecting users and developers of KVM by hosting a panel of KVM users (from cloud providers / builders) had one interesting insight: everyone wants more performance from KVM networking (well, the session was focussed on NFV, so that isn’t surprising).  No matter how fast you go, you want stuff to go faster still.  No one talked of stability, reliability, manageability, etc., so I suppose they’re just happy with those aspects.
  • A discussion with Chris Wright on KVM and OpenStack brought to me a surprise: KVM “just works” on OpenStack, and KVM is not the layer where there are problems.  No matter how many features we add or how much more performance we can eke out of the hypervisor, the most user-visible changes are now going to happen in the upper layers, most specially within the OpenStack project.  Obviously, there’s a need for us to collaborate with the OpenStack teams, but for most purposes, KVM is hardly the bottleneck or blocker for taking stuff to the clouds.  (We do have a huge list of things to do, but we’re ahead of the curve — what we are planning to do is needed and anticipated, but we need a better way to expose what we already have, and the OpenStack teams are going full-throttle at it.)

I suppose these are the highlights; I may have forgotten a few things due to the intervening holiday season.

Syndicated 2014-11-03 17:59:47 from Think. Debate. Innovate.

KVM Forum 2014 Schedule

The 2014 edition of KVM Forum is less than a week away.  The schedule of the talks is available at this location.  Use this link to add the schedule to your calendar.  A few slides have already been uploaded for some of the talks.

As with last year, we’ll live-stream and record all talks, keep an eye on the wiki page for details.

One notable observation about the schedule is that it’s much relaxed from the last few years, and there are far fewer talks in parallel this time around.  There’s a lot of time for interaction / networking / socializing.  If you’re in Dusseldorf next week, please come by and say ‘hello!’

Syndicated 2014-10-09 19:34:42 (Updated 2014-10-09 19:51:08) from Think. Debate. Innovate.

OpenStack Pune Meetup

I participated in the OpenStack Meetup at the Red Hat Pune office a few weekends ago.  I have been too caught up on the lower-level KVM/QEMU layers of the virt stack, and know there aren’t too many people involved in those layers in Pune (or even India); and was curious to learn more about OpenStack and also find out more about the OpenStack community in Pune.  The event was on a Saturday, which means sacrificing one day of rest and relaxation – but I went along because curiousity got the better of me.

This was a small, informal event where we had a few talks and several hallway discussions.  Praveen has already blogged about his experiences, here are my notes about the meetup.

There were a few scheduled talks for the day; speakers nominated themselves on the meetup page and the event organizers allotted slots for them.  The proceedings started off with configuring and setting up OpenStack via DevStack.  I wished (for the audience present there) there would’ve been an introductory talk before a deep-dive into DevStack.  I could spot a few newbies in the crowd, and they would have benefitted by an intro.

In a few discussions with the organizers, I learnt one of their pain points for such meetups: there inevitably are newbies at each meetup, and they can’t move on to advanced topics just because they have to start from scratch for each meetup.  I suggested they have a clear focus for each meetup: tell explicitly what each meetup is about, and the expertise level that’s going to be assumed.  For example, there’s nothing wrong with a newbie-focused event; but then some other event could focus on the networking part of OpenStack, and they assume people are familiar with configuring and deploying openstack and are familiar with basic networking priciples.  This suggestion is based on the Pune FADs we want to conduct and have in the pipeline; and was welcomed by the organizers.

Other talks followed; and I noticed a trend: not many people understood, or even knew about, the lower layers that make up the infrastructure beneath OpenStack.  I asked the organizers if they could spare 10 mins for me to provide a peek into the lower levels, and they agreed.  Right after a short working-lunch break, I took the stage.

I spoke about Linux, KVM and QEMU; dove into details of how each of them co-operate and how libvirt drives the interactions between the upper layers and the lower layers.  Also spoke a little about the alternative hypervisor support that libvirt has, but the advantages of the default hypervisor, QEMU/KVM has over others.  I then spoke about how improvements in Linux in general (e.g. the memory management layer) benefits the thousands of people running Linux, the thousands people running the KVM hypervisor, and in effect, benefit all the OpenStack deployments.  I then mentioned a bit about how features flow from upstream into distributions, and how all the advantages trickle down naturally, without anyone having to bother about particular parts of the infrastructure.

The short talk was well received, and judging by the questions I got asked, it was apparent that some people didn’t know the dynamics involved, and the way I presented it was very helpful to them and they wanted to learn more.  I also got asked a few hypervisor comparison questions.  I had to cut the interaction because I easily overflowed the 15 mins allotted to me, and asked people to follow up with me later, which several did.

One of the results of all those conversations was that I got volunteered to do more in-depth talks on the topic at future meetups.  The organizers lamented there’s a dearth of such talks and subject-matter experts; and many meetups generally end up being just talks from people who have read or heard about things rather than real users or implementers of the technology.  They said they would like to have more people from Red Hat talking about the work we do upstream and all the contributions we make.  I’m just glad our contributions are noticed :-)

Another related topic that came up during discussions with the organizers are hackathons, and getting people to contribute and actually do stuff.  I expect a hackathon to be proposed soon.

I had a very interesting conversation with Sajid, one of the organizers.  He mentioned Reliance Jio are setting up data centres across India, and are going to launch cloud computing services with their 4G rollout.  Their entire infrastructure is based on OpenStack.

There were other conversations as well, but I’ll perhaps talk about them in other posts.

Internally at Red Hat, we had a few discussions on how to improve our organization for such events (even though they’re community events; we should be geared up to serve the attendees better).  Mostly included stuff around making it easier to get people in (ie working with security), getting the AV equipment in place, etc.  All of this was working fine during this event, but basically ensuring all of the things that do go right are also part of the list of things to look at while organizing events so we don’t slip up.

Syndicated 2014-10-05 07:09:10 from Think. Debate. Innovate.

87 older entries...

 

amits certified others as follows:

  • amits certified mulix as Master
  • amits certified rms as Master
  • amits certified riel as Master
  • amits certified fxn as Journeyer
  • amits certified gby as Journeyer
  • amits certified alan as Master
  • amits certified corbet as Master
  • amits certified BrucePerens as Master
  • amits certified zwane as Journeyer
  • amits certified rmk as Master
  • amits certified marcelo as Master
  • amits certified axboe as Master
  • amits certified davej as Master
  • amits certified rml as Master
  • amits certified kroah as Master
  • amits certified wli as Master
  • amits certified erikm as Journeyer
  • amits certified akpm as Master
  • amits certified ahu as Journeyer
  • amits certified aniruddha as Journeyer
  • amits certified mishan as Journeyer
  • amits certified movement as Master
  • amits certified ladypine as Journeyer
  • amits certified amberpalekar as Journeyer
  • amits certified DV as Master

Others have certified amits as follows:

  • fxn certified amits as Journeyer
  • mulix certified amits as Journeyer
  • aniruddha certified amits as Journeyer
  • mishan certified amits as Journeyer
  • gby certified amits as Journeyer
  • davej certified amits as Apprentice
  • ladypine certified amits as Journeyer
  • amberpalekar certified amits as Journeyer

[ Certification disabled because you're not logged in. ]

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!

X
Share this page