-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 08/19/2015 10:54 AM, Bence Romsics wrote: > Hi, > > I'm not sure I need it. :-) > > My first idea was, that if two plugins implement an extension > together (neither the new first class resource, nor the new port > attributes is a usable feature in themselves in my case), then it > would be nice to express this. > > However thinking a bit more, I believe the only practical > difference between your solution in the qos patches and my first > idea is that we could catch some bad neutron configurations (ie. > loading only one of the two plugins). Which is probably really > rare, so it does not seem to justify the extra complexity. So I > will just go with your stuff. Thanks. >
Well, if we can move into dreams area, we may think of a way to express such inter-dependency, f.e. by introducing hidden sub-extensions; and meta-extensions that are satisfied only if all sub-extension pieces are present. But we like simple solutions, so we just hacked around the limitation. Our fault. :) Ihar -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJV1FfcAAoJEC5aWaUY1u57QrAH/A7qwU0EI9GE7yLI3pKckxnQ 7WJrjeLkewJkAH4LgPPkrD37ENgvKihF7MeEONzLaGll3OPp0xqTMGelLf+xPQ83 Cp2FNvG32kBi9EI/ge/VNxKBqpP+b6GcVP+UiH87dL4o35GHdbdC8uopKXjjDEKL uP2yVvJNz2IsojPUgbNw7GlWsP43EL93Piig6T7aRpApafSair3unc0/FbiYZlD/ WGepc+vwni+NC+Hk8PAb2jKCWA7xNvmZzpFKrTvY7Z75t0AK39a6SdCPbUvjwU/9 XL+gcPOggLq9LElZjdnyEW+EmVO0euAbl3YYLbyPdJWxM4d3sk+KGQCBhfwgsOs= =B0T+ -----END PGP SIGNATURE----- __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev