Define GK - MANO Framework API for initial implmentaion of year 1

[smendel]

as initial step for year 1 demo we would like to implement a simple deploy service flow.
more details from the MANO framework side can be found here -
sonata-nfv/son-mano-framework#23.

we need to define the GK-MANO API as the GK will be invoking the process in the MANO framework.

[jbonnet]

Check my comment here.

[smendel]

@jbonnet i believe you refereed to sonata-nfv/son-mano-framework#23
(the link in the comment above seems to be corrupted )

[jbonnet]

@smendel Yes I did, thanks

[jbonnet]

Suggested GK-MANO Framework API of Y1:

1. instantiation request (with all the info fetched from the catalogues, including a call-back URL for 'instance ready' notification)
2. list current instantiations (per user), with status

[mpeuster]

Regarding 1.: Why do we need a call-back URL? Does the GK not directly use RabbitMQ to talk to the MANO framework (option a)? With this, we can simply send back a broker message when the service instance is ready and do not need a callback URL. Or should the communication between GK and MANO framework be REST-based (option b)?

a) GK <- (AMQP) -> RabbitMQ Broker <- (AMQP) -> SLM plugin

b) GK <- (HTTP REST) -> GK-Adaptor <- (AMQP) -> RabbitMQ Broker <- (AMQP) -> SLM plugin

Both is doable. Its a design decision.