<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;"><font size="2"><span style="font-size:10pt;">Hi All,<br>
I need your advice for the implementation of the following blueprint. <a href="https://review.openstack.org/#/c/160605" target="_blank">
https://review.openstack.org/#/c/160605</a> .<br>
All the use cases mentioned in the blueprint have been implemented and the complete code is up for review.<br>
<a href="https://review.openstack.org/#/c/149828/" target="_blank">https://review.openstack.org/#/c/149828/</a><br>
However, we have an issue on which we need your input. In the nova quota api call, keystone calls are made to<br>
get the parent_id and the child project or sub project list. This is required because nova doesn't store any information
<br>
regarding the hierarchy. Hierarchy Information is taken during run time, from keystone. Since the keystone calls are
<br>
made inside the api call, it is not possible to give any dummy or fake values while writing the unit tests. If the keystone<br>
call was made outside the api call, we could have given fake values in the test cases. However, the keystone calls for
<br>
parent_id and child projects are made inside the api call.<br>
Can anyone suggest an elegant solution to this problem? What is the proper way to implement this ?
<br>
Did anybody encounter and solve a similar problem ? Many thanks for any suggestions!<br>
best regards<br>
sajeesh</span></font></div>
</body>
</html>