@demobox @zack-shoylev Yes, this is currently how the extensions work in OpenStack Nova today. I was planning on aligning the APIs mentioned in the JIRA for the time being.
I made an ignorant comment in another PR a while back stating that the extensions were broken, which was how I felt at that time. After investigating it further, it should suffice for now. I do find it a little awkward in the way it is designed at the moment, and we could possibly revisit the design for 2.0. In addition to the `@Extension` annotation, I believe that it would also be beneficial to annotate Admin APIs `@Admin`, since they typically require a special role to access them. Something else to kick around... I had experimented with different approaches, but it wasn't working how I envisioned. I was hoping that the top level APIs could expose something like a `getExtensionApi(<alias>)`, and just pass the extension alias, but then you get into the casting game, which is complete yuck. All that said, is there additional information I can provide here? Are we all in alignment on how the extensions work today? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/143#issuecomment-55417341
