<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Dina,<br>
<br>
Le 14/10/2013 17:14, Dina Belova a écrit :<br>
</div>
<blockquote
cite="mid:CACsCO2ytjm18gC7gT8mNg7Pe-2m+ZBT4Vnte9B8MSCV0-CekEQ@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div dir="ltr">Hello everyone!
<div><br>
</div>
<div>Guys, now we have Nova dependency in Climate like:</div>
<div><br>
</div>
<div>
<div>-f <a moz-do-not-send="true"
href="http://tarballs.openstack.org/nova/nova-master.tar.gz#egg=nova-master">http://tarballs.openstack.org/nova/nova-master.tar.gz#egg=nova-master</a></div>
<div>nova>=master</div>
<div><br>
</div>
<div style="">That was done to implement Nova-based scheduler
filter for physical reservations and store its code in
Climate project itself. Now Climate is really light weighted
project, that do not really need all these deps connected
wit Nova. Still, now that future filter is part of Climate
physical reservations logic.</div>
<div style=""><br>
</div>
</div>
</div>
</blockquote>
<br>
I'm unsure the concern is only related to physical reservations. Let
me explain further.<br>
<br>
Actually, for Climate v0.1, we would not need to deliver our own
filter, as we'll be relying on Pcloud filter [1] as we will have a
1:1 relation in between a reservation and a pcloud.<br>
<br>
As the pcloud is only provided with hosts when the lease starts, the
pcloud filter is giving results only when the lease is running. At
the end of the lease, the pcloud is deleted even if the hosts are
still running VMs, so the magic still does.<br>
<br>
The clear reason why we need to provide a Lease Filter is that we
don't want to provide to end-users unclear messages : if the user is
trying to boot a VM using a pcloud UUID for a lease that hasn't
started yet, he should get an ERROR message "Sorry, the lease hasn't
started yet" instead of "Sorry, there is no hosts to match for your
request". <br>
<br>
That's actually a matter of having a deferred scheduling system, not
particularly related to physical hosts. Provided you would like to
provision an Heat stack *which would be scheduled when the lease
starts, and not when the lease is created*, you would have same
concern. On the implementation you're starting with, you won't have
need for a filter, but you can't assess it would be the case later
on.<br>
<br>
<br>
<blockquote
cite="mid:CACsCO2ytjm18gC7gT8mNg7Pe-2m+ZBT4Vnte9B8MSCV0-CekEQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div style="">That's why we have the following question: do
you think it's normal to have such dependency there, or it
will be better to create separate repo like
"climate-filters" and put there any filters and their
dependencies?</div>
<div><br>
</div>
What can you advise?</div>
</div>
</blockquote>
<br>
Well, I don't have a clear opinion on that. The main pros for moving
out are :<br>
1. Climate gate testing is less dependent on Nova<br>
2. Build time for testing is quicker<br>
<br>
On the other hand, the cons are :<br>
1. Having two repos could mean duplicate work <br>
2. There is need for maintaining a backwards compatibility in
between Climate and its filters (as there are two projects, like
Nova and its client)<br>
3. We would be more documentation-dependent, as it's up to the
operator to deploy both Climate and Climate-filters for having
physical reservations working<br>
<br>
<br>
Of course, I also feel pain when doing a tox -r on Climate as Nova
is pulling lots of dependencies, but I don't want to put complexity
in place just because I want to run faster my tests... :(<br>
<br>
-Sylvain<br>
<br>
<br>
<blockquote
cite="mid:CACsCO2ytjm18gC7gT8mNg7Pe-2m+ZBT4Vnte9B8MSCV0-CekEQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
<div dir="ltr">
<div
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<p
style="font-size:small;margin:0px;font-family:Helvetica">
Best regards,</p>
<p
style="font-size:small;margin:0px;font-family:Helvetica">Dina
Belova</p>
<p
style="font-size:small;margin:0px;font-family:Helvetica">Software
Engineer</p>
<p
style="font-size:small;margin:0px;font-family:Helvetica">
Mirantis Inc.</p>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>