Update RPM specfile for 0.9 version

- Use RPM macros
- Build python module using setuptools
- Reorganize %files section and dependencies
- Buildroot declaration compliant with Fedora/CentOS policy
Update PEP references to www.python.org

Update from legacy.python.org to www.python.org (which currently
redirects to legacy.python.org :p)

legacy.python.org will probably exist for a while, but the actual PEP
URLs should stay www IMHO
Merge pull request #32 from ptitoliv/wip/rpm

Update RPM specfile for 0.9 version
Merge pull request #33 from romuald/no-legacy-url

Update PEP references to www.python.org
we are currently basing kernel list on image.list()
some issues:
1. the list contains duplicates since we extract each kernel from all
   images
2. if the kernel is not included on an image, we will not be able to set
   it
   example:
   for grub, we currently don't have any image based on grub, so I had
   to insert an empty image with the grub kernel in order to make it
   work
3. we should check if the datacenter has the needed kernel before
setting it

this patch proposes to base the kernel list on the first datacenter
since for now, we may consider that all datacenter have the same
kernels.
This solution is not ideal but it avoids to insert an empty image with
the grub kernel which could confuse users.

A second patch should check the kernel depending on the disk's
datacenter.

Signed-off-by: William Dauchy <william@gandi.net>
Revert "we are currently basing kernel list on image.list()"

This reverts commit 3f3143b0f517abc0c8019a104620a2300948deac.
core: enhance kernel list

we are currently basing kernel list on image.list()
some issues:
1. the list contains duplicates since we extract each kernel from all
   images
2. if the kernel is not included on an image, we will not be able to set
   it
   example:
   for grub, we currently don't have any image based on grub, so I had
   to insert an empty image with the grub kernel in order to make it
   work
3. we should check if the datacenter has the needed kernel before
setting it

this patch proposes to base the kernel list on the first datacenter
since for now, we may consider that all datacenter have the same
kernels.
This solution is not ideal but it avoids to insert an empty image with
the grub kernel which could confuse users.

A second patch should check the kernel depending on the disk's
datacenter.

Signed-off-by: William Dauchy <william@gandi.net>