On 09/04/2018 12:49 PM, Srini wrote:
It is not clear at all whether Akraino is the right owner for the APIs or not --- many other projects and communities are working on addressing the pieces of this rather large & diverse puzzle (ONAP, CNCF/k8s, various projects in OPNFV & OpenStack, etc. etc.), and IMHO, the last think that we need is more duplication for the ongoing efforts which would result in even more fragmentation of the landscape.
So, whenever possible, optimally Akraino would pull from upstreams like OPNFV does and identify/address the gaps. Obviously in the cases where there is nothing (or existing approaches are deemed unsuitable / unfixable after careful consideration), Akraino could be in good position to resolve.
I am saying the above, as ownership of the APIs does and should
belong to the projects implementing them, not something like
Akraino. If it is identifying, selecting and requesting additions
/ modifications, or Akraino hosted development projects, then that
would be ok. Blueprint for the infrastructure is expected to make
some selections for the projects that go in, so that implicitly
makes some picks on the APIs as well - but that would not make
Akraino "developer" for such cases, more like Endorser / selector.
That said, there is very much confusion between the ONAP edge as
well as Akraino (on both sides) on who is going to do what and
when which should get resolved sooner rather than later, as the
context of the comment was "regional orchestration".