Open Stack

Hi,

The current change requires python26, and I seem to have a reasonable way of installing that now. We can always just install the appropriate rpms from EPEL rather than using yum (I have listed what is required in the wiki).

> It's great to hear that you got this working.
> Yum was not working for us after having installed python26
Can you sent to the list the errors you were seeing?

> however will give it a try this way.
Cool, thank you.
 
> However, we are looking for a more friendly solution to the
 > automated deployment process, to the very least trying to
> avoid a flaky yum
I think that should be the above method.
Is there anything not covered by the above plans?

> Until we all find a cleaner way out, we'r going to work on submitting
> a minimal necessary patch for review which does not hurt the
> OpenStack code and community in general.
OK, but the current patch still needs python 2.6 in Dom0?
Would it not be simpler to use the standard swift client to upload the VHD file, and sort any deployment niggles later?

You could imagine an "optimisation" might be to include your current cut down version as a drop in replacement for the standard xenapi plugin that can uses the standard swift client.

Thanks,
John

-----Original Message-----
From: "John Garbutt" <John.Garbutt at citrix.com>
Sent: Thursday, January 24, 2013 11:58am
To: "OpenStack Development Mailing List" <openstack-dev at lists.openstack.org>
Cc: "Nikhil Komawar" <nikhil.komawar at rackspace.com>
Subject: RE: [openstack-dev] swift client for Xen on dom0
Hi Nikhil,
I have just had a quick look at installing python-swiftclient and python-keystoneclient into XenServer/XCP’s Dom0.
It seems to have installed OK by following these steps: http://wiki.openstack.org/XenServer/PostInstall#Install_Python_2.6_in_Dom0
In the XenAPI meeting you said there were some issues with yum after installing python 2.6. I managed to reproduce issues doing “yum upgrade”. It was getting very confused with package differences between the EPEL and Citrix repositories (gdisk in particular). I managed to “fix” this by removing the EPEL repo once I installed python2.6 and easy-install-2.6
Does that sound OK?
Were there any other issues blocking you going for (2)?
John 
From: Chmouel Boudjnah [mailto:chmouel at chmouel.com] 
Sent: 23 January 2013 12:00
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] swift client for Xen on dom0
 
Hi Nikhil,
I would definitively go for options 2 having to redo a swiftclient would not be very useful. What are the pain point about option 2?
We have as well a Swift meeting tonight (Wed/23) if you want to come talk with the swift core about it.
 
Regards,
Chmouel.
 
On Wed, Jan 23, 2013 at 12:29 AM, Nikhil Komawar <nikhil.komawar at rackspace.com> wrote:
Hi,

We have a review patch in Nova https://review.openstack.org/#/c/17803/, which is making us contemplate on the best possible way to communicate with swift from the dom0. The two  options mentioned below have pros and cons:-

1. either emulate swift client
2. or install python-swiftclient on dom0

On trying out both on them, we have realized some pain points involved in deployment and maintenance process. Also, as John has correctly pointed out in the review, we need to keep in mind about having the same code in 2 different places, especially for security fixes.

Your opinions and comments would be greatly appreciated and we wish to discuss about this in the XenAPI IRC meeting on Wednesday Jan 23rd as well.

thanks,
-Nikhil


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev