<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Thanks,<br>
<br>
I uploaded the patch only to start the conversation early, I plan to add all the <br>
necessary methods to cover the needs now for bandwidth, and have a <br>
basic framework for adding more things later.<br>
<br>
Regards<br>
Lajos<br>
<br>
<div class="moz-cite-prefix">On 2018. 12. 04. 19:50, Archit Modi wrote:<br>
</div>
<blockquote type="cite" cite="mid:CANnpN_2eu+RV+MmytH2njdOrv8rizAvSxdZpR-imgN_ujOONkQ@mail.gmail.com">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div>Great! There is already a patch from Lajos [1]. I'd like resource_provider_aggregates_client to be added too. (/resource_providers/{uuid}/aggregates)</div>
<div><br>
</div>
[1] <a href="https://review.openstack.org/#/c/622316/" moz-do-not-send="true">https://review.openstack.org/#/c/622316/</a></div>
<div dir="ltr"><br>
<div class="gmail_quote">
<div dir="ltr">On Tue, Dec 4, 2018 at 1:32 PM Chris Dent <<a href="mailto:cdent%2Bos@anticdent.org" moz-do-not-send="true">cdent+os@anticdent.org</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
On Tue, 4 Dec 2018, Dan Smith wrote:<br>
<br>
>> On 12/04/2018 06:13 AM, Chris Dent wrote:<br>
>>> Existing Tempests tests that do things like launching, resizing,<br>
>>> migrating servers already touch placement so may be sufficient. If<br>
>>> we wanted to make these more complete adding verification of<br>
>>> resource providers and their inventories before and after the tests<br>
>>> might be useful.<br>
<br>
[snip]<br>
<br>
> I don't disagree either. However, I do think that there are cases where<br>
> it may make sense to be _able_ to hit the placement endpoint from<br>
> tempest in order to verify that certain things are happening, even in a<br>
> scenario that involves other services.<br>
<br>
[snip]<br>
<br>
Based on conversation with Dan in IRC, we decided it might be useful<br>
to clarify that Dan and I are in agreement. It had seemed to me that<br>
he was saying something different from me, but we're both basically<br>
saying "yes, tempest needs to be able to talk to placement to<br>
confirm what it's holding because that's useful sometimes" and "no,<br>
tempest doesn't need to verify the workings of placement api itself".<br>
<br>
Which boils out to this:<br>
<br>
> I *think* that gmann's<br>
> question in the email was actually about placement endpoint support,<br>
> which is the former, and I think is probably legit.<br>
<br>
Yes.<br>
<br>
-- <br>
Chris Dent ٩◔̯◔۶ <a href="https://anticdent.org/" rel="noreferrer" target="_blank" moz-do-not-send="true">https://anticdent.org/</a><br>
freenode: cdent tw: @anticdent</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>