<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>Sounds pretty good Vish.<br>
<br>
Since we are mostly deployers, and the ones who are gonna try the
new code from day zero, whats good for Sandy, its good for us.<br>
<br>
Alejandro.<br>
</tt>
<div class="moz-signature">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<title></title>
<br>
</div>
On 02/01/2012 06:57 PM, Vishvananda Ishaya wrote:
<blockquote
cite="mid:26D49C04-5875-4406-8FD5-5C237DAD2569@gmail.com"
type="cite">Thanks for the feedback. It is good to get input from
one of the largest openstack installs! So it sounds like the
existing code is pretty broken. Based on this feedback I would
like to propose the following:
<div><br>
</div>
<div>1) cut out zones code</div>
<div> (meaning merge the existing branch)</div>
<div><br>
</div>
<div>2) grant an FFe for the new rpc based zone code as long is it
can be merged without heavily modifying core.</div>
<div><br>
</div>
<div>This means:</div>
<div>a) it should be deployable with the feature disabled</div>
<div>b) it should only include minor modifications to core
components</div>
<div>c) if a major change is needed to distributed_scheduler (for
example), consider leaving the existing version in, and copying
the code to a new file (distributed_scheduler_v2) and doing the
modifications there. That way we can minimize chances of
breakage</div>
<div>d) it needs to be merged by the 15th</div>
<div><br>
</div>
<div><br>
</div>
<div>Does that seem reasonable?</div>
<div><br>
</div>
<div>Vish</div>
<div><br>
<div>
<div>
<div>On Feb 1, 2012, at 1:42 PM, Alejandro Comisario wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div bgcolor="#FFFFFF" text="#000000"> Hi guys.<br>
Its true that we are trying to make multizones work,
actually we did, but we get into an instance were
listing all vms from the parent zone ( where is has to
go thru all the child zones ) is buggy ( if not
impossible by now ).<br>
So, if there is a new zone architecture that actually
works ( we want to stop using our own deployer to do
that ) or has a chance to be fully working when 2012-1
is out, (we would prefer not to wait till Folsom) we are
totally into it ! since by now, we were actually waiting
for this new Zones code to come out to try again.<br>
<br>
Alejandro.<br>
<br>
On 02/01/2012 06:17 PM, Nathanael Burton wrote:
<blockquote
cite="mid:CAHTGUNShAzRJpaRuE71m-NJWCa2LSvHROCpuYzi16SrADrJCqQ@mail.gmail.com"
type="cite">
<p>+1</p>
<div class="gmail_quote">On Feb 1, 2012 4:13 PM,
"Vishvananda Ishaya" <<a moz-do-not-send="true"
href="mailto:vishvananda@gmail.com">vishvananda@gmail.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
I would prefer that if it can be done super-super
fast. :)<br>
<br>
Vish<br>
<br>
On Feb 1, 2012, at 1:04 PM, Chris Behrens wrote:<br>
<br>
> I wonder if we can use some of the
architecture of the new code and move the current
implementation to that model. It'd preserve the
existing functionality, set us up for the new
implementation, and fits in with 'cleanup' for E4,
etc.<br>
><br>
> On Feb 1, 2012, at 2:41 PM, Vishvananda
Ishaya <<a moz-do-not-send="true"
href="mailto:vishvananda@gmail.com">vishvananda@gmail.com</a>>
wrote:<br>
><br>
>> I am all for pulling this out, but I'm a
bit concerned with the fact that we have nothing
to replace it with. There are some groups still
trying to use it. MercadoLibre is trying to use it
for example. I know you guys are trying to replace
this with something better, but it would be nice
not to break people for 7+ months<br>
>><br>
>><br>
>> So I guess I have some questions:<br>
>> 1.a) is the current implementation
completely broken?<br>
>><br>
>> 1.b) if yes, is it fixable<br>
>><br>
>> 2) If we do remove this, what can we tell
people that need something like zones between now
and the Folsom release?<br>
>><br>
>> Vish<br>
>> On Feb 1, 2012, at 12:16 PM, Sandy Walsh
wrote:<br>
>><br>
>>> As part of the new (and optional)
Zones code coming down the pipe, part of this is
to remove the old Zones implementation.<br>
>>><br>
>>> More info in the merge prop:<br>
>>> <a moz-do-not-send="true"
href="https://review.openstack.org/#change,3629"
target="_blank">https://review.openstack.org/#change,3629</a><br>
>>><br>
>>> So, can I? can I? Huh?<br>
>>>
_______________________________________________<br>
>>> Mailing list: <a
moz-do-not-send="true"
href="https://launchpad.net/%7Eopenstack"
target="_blank">https://launchpad.net/~openstack</a><br>
>>> Post to : <a
moz-do-not-send="true"
href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
>>> Unsubscribe : <a
moz-do-not-send="true"
href="https://launchpad.net/%7Eopenstack"
target="_blank">https://launchpad.net/~openstack</a><br>
>>> More help : <a
moz-do-not-send="true"
href="https://help.launchpad.net/ListHelp"
target="_blank">https://help.launchpad.net/ListHelp</a><br>
>><br>
>><br>
>>
_______________________________________________<br>
>> Mailing list: <a moz-do-not-send="true"
href="https://launchpad.net/%7Eopenstack"
target="_blank">https://launchpad.net/~openstack</a><br>
>> Post to : <a moz-do-not-send="true"
href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
>> Unsubscribe : <a moz-do-not-send="true"
href="https://launchpad.net/%7Eopenstack"
target="_blank">https://launchpad.net/~openstack</a><br>
>> More help : <a moz-do-not-send="true"
href="https://help.launchpad.net/ListHelp"
target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br>
<br>
_______________________________________________<br>
Mailing list: <a moz-do-not-send="true"
href="https://launchpad.net/%7Eopenstack"
target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a moz-do-not-send="true"
href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a moz-do-not-send="true"
href="https://launchpad.net/%7Eopenstack"
target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a moz-do-not-send="true"
href="https://help.launchpad.net/ListHelp"
target="_blank">https://help.launchpad.net/ListHelp</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Mailing list: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://launchpad.net/%7Eopenstack">https://launchpad.net/~openstack</a>
Post to : <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>
Unsubscribe : <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://launchpad.net/%7Eopenstack">https://launchpad.net/~openstack</a>
More help : <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a>
</pre>
</blockquote>
</div>
_______________________________________________<br>
Mailing list: <a moz-do-not-send="true"
href="https://launchpad.net/%7Eopenstack">https://launchpad.net/~openstack</a><br>
Post to : <a moz-do-not-send="true"
href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a moz-do-not-send="true"
href="https://launchpad.net/%7Eopenstack">https://launchpad.net/~openstack</a><br>
More help : <a moz-do-not-send="true"
href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</body>
</html>