<div dir="ltr">Hi all,<div><br></div><div>I discussed the change with other cores in -keystone and, looking at the</div><div>API change guidelines, it should be an allowed API change.</div><div><br></div><div>I had a doubt whether the rule "Changing or removing a property in a</div><div>resource representation." could make it a forbidden API change or not.</div><div>However, since it is not changing the returned attribute itself (type), but</div><div>only the returned data in it, it should be okay.</div><div><br></div><div>[1] <a href="http://specs.openstack.org/openstack/api-wg/guidelines/evaluating_api_changes.html">http://specs.openstack.org/openstack/api-wg/guidelines/evaluating_api_changes.html</a></div><div><br></div><div>Regards,</div><div>Samuel</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 17, 2016 at 11:06 AM, Raildo Mascena <span dir="ltr"><<a href="mailto:raildom@gmail.com" target="_blank">raildom@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Henry,<div><br></div><div>I know about two patches related:</div><div><span style="line-height:1.5">Fixes cinder quota mgmt for keystone v3 -</span><span style="color:rgb(0,0,0);font-family:monospace;line-height:normal;white-space:pre-wrap"> </span><span style="line-height:1.5"><a href="https://review.openstack.org/#/c/253759" target="_blank">https://review.openstack.org/#/c/253759</a></span></div><div><table style="border-spacing:0px;color:rgb(0,0,0);font-family:sans-serif;line-height:normal"><tbody><tr><td style="padding:0px;vertical-align:top;width:560px">Split out NestedQuotas into a separate driver - </td></tr></tbody></table> <a href="https://review.openstack.org/#/c/274825" target="_blank">https://review.openstack.org/#/c/274825</a><br></div><div><br></div><div>The first one was abandoned, so I think the second patch is enough to fix this issue.</div><div><br></div><div>Cheers,</div><div><br></div><div>Raildo</div><div><div class="h5"><br><div class="gmail_quote"><div dir="ltr">On Wed, Feb 17, 2016 at 8:07 AM Henry Nash <<a href="mailto:henrynash9@mac.com" target="_blank">henrynash9@mac.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Michal & Raildo,<div><br></div><div>So the keystone patch (<a href="https://review.openstack.org/#/c/270057/" target="_blank">https://review.openstack.org/#/c/270057/</a>) is now merged. Do you perhaps have a cinder patch that I could review so we can make sure that this is likely to work with the new projects acting as domains? Currently it is the cinder tempest tests that are failing.</div><div><br></div><div>Thanks</div></div><div style="word-wrap:break-word"><div><br></div><div>Henry</div></div><div style="word-wrap:break-word"><div><br></div><div><br><div><blockquote type="cite"><div>On 2 Feb 2016, at 13:30, Raildo Mascena <<a href="mailto:raildom@gmail.com" target="_blank">raildom@gmail.com</a>> wrote:</div><br><div><div dir="ltr" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">See responses inline.<br><br><div class="gmail_quote"><div dir="ltr">On Mon, Feb 1, 2016 at 6:25 PM Michał Dulko <<a href="mailto:michal.dulko@intel.com" target="_blank">michal.dulko@intel.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">On 01/30/2016 07:02 PM, Henry Nash wrote:<br>> Hi<br>><br>> One of the things the keystone team was planning to merge ahead of milestone-3 of Mitaka, was “projects acting as a domain”. Up until now, domains in keystone have been stored totally separately from projects, even though all projects must be owned by a domain (even tenants created via the keystone v2 APIs will be owned by a domain, in this case the ‘default’ domain). All projects in a project hierarchy are always owned by the same domain. Keystone supports a number of duplicate concepts (e.g. domain assignments, domain tokens) similar to their project equivalents.<br>><br>> <snip><br>><br>> I’ve got a couple of questions about the impact of the above:<br>><br>> 1) I already know that if we do exactly as described above, the cinder gets confused with how it does quotas today - since suddenly there is a new parent to what it thought was a top level project (and the permission rules it encodes requires the caller to be cloud admin, or admin of the root project of a hierarchy).<br><br>These problems are there because our nested quotas code is really buggy<br>right now. Once Keystone merges a fix allowing non-admin users to fetch<br>his own project hierarchy - we should be able to fix it.<br></blockquote><div><br></div><div>++ The patch to fix this problem are closer to be merged, there is just minor comments to fix: <a href="https://review.openstack.org/#/c/270057/" target="_blank">https://review.openstack.org/#/c/270057/</a> So I believe that we can fix this bug on cinder in in next days.</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>> 2) I’m not sure of the state of nova quotas - and whether it would suffer a similar problem?<br><br>As far as I know Nova haven't had merged nested quotas code and will not<br>do that in Mitaka due to feature freeze. </blockquote><div>Nested quotas code on Nova is very similar with the Cinder code and we are already fixing the bugs that we found on Cinder. Agreed that It will not be merged in Mitaka due to feature freeze. <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>> 3) Will Horizon get confused by this at all?<br>><br>> Depending on the answers to the above, we can go in a couple of directions. The cinder issues looks easy to fix (having had a quick look at the code) - and if that was the only issue, then that may be fine. If we think there may be problems in multiple services, we could, for Mitaka, still create the projects acting as domains, but not set the parent_id of the current top level projects to point at the new project acting as a domain - that way those projects acting as domains remain isolated from the hierarchy for now (and essentially invisible to any calling service). Then as part of Newton we can provide patches to those services that need changing, and then wire up the projects acting as a domain to their children.<br>><br>> Interested in feedback to the questions above.<br><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe:<span> </span><a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br></blockquote></div></div><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">__________________________________________________________________________</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">OpenStack Development Mailing List (not for usage questions)</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">Unsubscribe:<span> </span></span><a href="mailto:OpenStack-dev-request@lists.openstack.org" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">OpenStack-dev-request@lists.openstack.org</a><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">?subject:unsubscribe</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></div></blockquote></div><br></div></div>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div></div></div></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>