yahoo-eng-team team mailing list archive

[Dolph Mathews <1485712@xxxxxxxxxxxxxxxxxx>]

This is truly by design. But by disallowing it today, we've given
ourselves the option to allow it in the future (we can't do the
opposite: take an API feature away). The consequences of a mutable
hierarchy are complicated and affect the rest of OpenStack (think
quotas, for example), and the risk of unintended consequences, bugs, and
security vulnerabilities is simply too great.

It's far too early in hierarchical multitenancy's lifecycle to consider
introducing all that extra complexity today. Perhaps once hierarchical
multitenancy is a mature feature and we have a strong grasp of the
consequences of a mutable hierarchy we could have that discussion again.

** Changed in: keystone
       Status: New => Won't Fix

** Changed in: keystone
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1485712

Title:
  Can't set parent_id of project for hierarchical multi-tenancy

Status in Keystone:
  Won't Fix

Bug description:
  I understand reading some of the specs for hierarchical multi-tenancy
  that you cannot change the parent_id of a project. But i would've
  hoped that if a project was created without a parent_id , you can
  later assign a parent, otherwise there's no clear migration path for
  projects that wish to utilize this feature and would have to
  destroy/recreate the project.

  When i tried it i get a 403, "Update of `parent_id` is not allowed.".
  Is this just in place until it can be supported later, or is this
  truly by design?

  thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1485712/+subscriptions