search

sonata-nfv / son-catalogue-repos

SONATA's Service Platform Catalogue and Repository
http://www.sonata-nfv.eu
Apache License 2.0
4 stars 10 forks source link

API vs AMQP for catalogues and repositories #3

Closed felipevicens closed 8 years ago

felipevicens commented 8 years ago

As we know, we need to communicate the SLM with the repositories. We have two choices: a. Use an API (We have done some work here) b. Use AMQP plugin to use rabbitmq

Questions a. What should we implement for the repositories in the first cycle, API, AMQP plugin or both?

For the SP Catalogue, the communication is directly between gatekeeper and catalogue. At this point we have the catalogue separated from the repositories but our intention is merge it because they have the same functionalities (same API language --Ruby-- , same database engine --mongo--).

Questions b. If the answer of question "a" was go for AMQP plugin. Are we going to keep divided the github's repositories for the sp repos(AMQP) and the Catalogue(API)? c. Are we going to use API for the first cycle of Catalogues, and then later implement AMQP?

https://github.com/sonata-nfv/son-mano-framework/issues/23 https://github.com/sonata-nfv/son-gkeeper/issues/33

shuaibsiddiqui commented 8 years ago

Hi Felipe,

After todays call, I believe it is a common understanding that for Y1, the sp catalogues and NS & NF repositories will interact with GK and MANO framework, respectively, using a REST based API.

If you agree we can close this issue.

felipevicens commented 8 years ago

Hi Shuaib!

I'm agree. I proceed to close this issue.

Thank you