I'm concerned about a need to support python 2.4 as well, especially if it would have a ripple effect into openstack-common, which otherwise does not have that requirement. <div><br></div><div>With XenServer, nova-compute actually runs in a service VM (which is running a modern version of python). I believe Salvatore or others may have done some work around forcing network traffic through this service VM to allow iptables rules from nova-compute / nova-network to be enforced, but I'm not familiar enough with that work to say for sure. Can anyone shed light on this? </div>
<div><br></div><div>Another option would be to just create a simple Quantum plugin specific to XenServer that doesn't require an agent. This plugin could use XAPI to create networks, but as a result might only support a base feature set (e.g., L2 connectivity using VLANs). </div>
<div><br></div><div>Dan</div><div><br><br><div class="gmail_quote">On Wed, May 9, 2012 at 9:07 AM, Robert Kukura <span dir="ltr"><<a href="mailto:rkukura@redhat.com" target="_blank">rkukura@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">[I'm moving this thread to the openstack list because it potentially<br>
impacts openstack-common.]<br>
<div class="im"><br>
On 05/07/2012 11:53 PM, Maru Newby wrote:<br>
> Hi,<br>
><br>
> Python 2.4 compatibility is required, but only for agent code. Agent<br>
> code needs to be deployable on Xen dom0, which uses CentoOS 5.5 and only<br>
> supports 2.4 out of the box.<br>
<br>
</div>Maru,<br>
<br>
I'm very concerned about the potential of this XenServer/XCP requirement<br>
to interfere with making the various Quantum agents first-class<br>
OpenStack services by utilizing current and future openstack-common<br>
facilities for configuration, logging, DB, RPC, etc.. Are there any<br>
other possible ways forward here? How is the nova compute service<br>
currently handled for XenServer? Could a fully supported version of<br>
python be parallel-installed on dom0? Could the actual quantum agent run<br>
somewhere else and remotely execute commands on dom0? Or does the python<br>
2.4 compatibility requirement need to be applied to openstack-common?<br>
<br>
Thanks,<br>
<br>
-Bob<br>
<div><div class="h5"><br>
><br>
> Both quantum and nova have agent code that needs to be deployed to dom0,<br>
> but up until now both projects have relied on savvy reviewers and bug<br>
> reports to ensure compatibility. I'm working on it, though. I'll<br>
> be adding a tox build to quantum that will run agent tests - and agent<br>
> tests only - under 2.4, and then openstack-ci can add a jenkins job to<br>
> run that build on CentOS and gate merges.<br>
><br>
> The relevant bug: <a href="https://bugs.launchpad.net/quantum/+bug/995278" target="_blank">https://bugs.launchpad.net/quantum/+bug/995278</a><br>
><br>
> Thanks,<br>
><br>
><br>
> Maru<br>
><br>
><br>
> On 2012-05-07, at 6:54 PM, Yong Sheng Gong wrote:<br>
><br>
>> Hi,<br>
>> I see some ones are trying to support python2.4. But our tox.ini under<br>
>> quantum is only supporting test py26 and py27.<br>
>> So my question is if we are trying to support py24. In addition I<br>
>> remember that we will support py30.<br>
>><br>
>> As far as I know, py2.4 does not support many new syntaxes introduced<br>
>> by py2.5+. Other projects such as nova, horizon are also adopting some<br>
>> of these new syntaxes. Moreover some third party components such as<br>
>> Django 1.4 required by horizon are only tested under py2.6 and py2.7.<br>
>><br>
>> So if py2.4 is out of our scope, we should stop that trying. If we<br>
>> need py2.4, we have to make all of us know it and keep our code 2.4<br>
>> compatible.<br>
>><br>
>> Thanks<br>
>><br>
>> Yong Sheng Gong<br>
>><br>
>> --<br>
>> Mailing list: <a href="https://launchpad.net/~netstack" target="_blank">https://launchpad.net/~netstack</a><br>
>> Post to : <a href="mailto:netstack@lists.launchpad.net">netstack@lists.launchpad.net</a><br>
</div></div>>> <mailto:<a href="mailto:netstack@lists.launchpad.net">netstack@lists.launchpad.net</a>><br>
<div class="im">>> Unsubscribe : <a href="https://launchpad.net/~netstack" target="_blank">https://launchpad.net/~netstack</a><br>
>> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
><br>
><br>
><br>
<br>
<br>
</div>_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>Dan Wendlandt <div>Nicira, Inc: <a href="http://www.nicira.com" target="_blank">www.nicira.com</a><br><div>twitter: danwendlandt<br>
~~~~~~~~~~~~~~~~~~~~~~~~~~~<br></div></div><br>
</div>