Nachi Ueno

Basic update support merged. We still need - update references see https://github.com/Juniper/contrail/blob/master/tools/templates/db.tmpl#L71 - sharing support see https://github.com/Juniper/contrail/blob/master/tools/templates/db.tmpl#L99

Contrail repos are under migration now. so I would like to use git subtree once main repo get ready git sub tree: https://www.atlassian.com/blog/git/alternatives-to-git-submodule-git-subtree

kk let's keep open this issue until this issue get fixed.

Could you add reason why we need both of PUT and PATCH? I know they have different meanings but I don't see use cases.

We only use PUT in contrail API or OpenStack API for simplicity, and only specified properties will be updated. I still don't see enough benefit for supporting this.

Could you give me an example for the vertex? yes Contrai/Neutron PUT is PATCH, but we don't have any problem around it. and I don't see many use of completely...

Let's call it as Bluk create/update/delete API. I've created an issue for discussing it . https://github.com/Juniper/contrail/issues/46

@cyrilMargaria That should be handled by orchestrator layer only.

We pick PostgreSQL for DB for this project, so updated description.

Oh I thought the PR answered your questions because you approved it. I believe I've updated README to answer your questions, so if current description isn't enough clear could you...