Open Stack

On 12/10/2013 10:47 AM, Alexandre Levine wrote:
> Does nova actually have add-ons infrastructure in which our GCE API can
> fit? I see the plugins with xen-server only and have found this link:
> http://docs.openstack.org/developer/nova/api/nova.openstack.common.plugin.plugin.html.
> Is it the thing? I'm trying to understand what you meant by this: "If it
> doesn't go into Nova, this would be a good way to manage it as an add-on".

I mean as a place to host the code with infrastructure that can help
make sure it stays in sync with Nova.

There's no real plugin infrastructure that this would fit in to.  It
would be a new service in your repo, based on Nova's service code, that
loads the GCE API.  Your code would be importing nova.* stuff, even
though it's in a separate repo.

> Also if we do it a separate service does it remove necessity for support
> commitment from the nova core team? 

Yes.

> And if it does who would have to commit instead?

It could be anyone.  I presume it would be the original authors who were
planning to help maintain it anyway, as well as anyone else that the
project can attract that is interested in GCE.

> Sorry if I ask some obvious questions.

No problem ... there isn't an existing example for you follow exactly,
so it's not obvious.

-- 
Russell Bryant