#opnfv-domino: domino-models

Meeting summary

1. 1. Ulas Kozat (uck, 13:07:17)
   
   
2. E Release Plan (uck, 13:07:50)
   1. https://wiki.opnfv.org/display/domino (rprakash, 13:08:17)
   2. https://wiki.opnfv.org/display/domino?preview=/2925446/2925447/opnfv_technical_discussion_-_domino_proposal.pptx (rprakash, 13:11:33)
   3. you mean template will contain vnf redundancy for HA? (rprakash, 13:14:47)
   4. no, it will create multiple Domino Servers for Domino HA (uck, 13:15:31)
   5. however what you say also is interesting!! (uck, 13:16:04)
   6. we need to scope and time is limited so state what and we will fill in how after some delibrationbs (rprakash, 13:17:24)
   7. Especially in the case of edge cloud, Domino can push the same template to many locations and returns the publisher the list of locations where VNFD is onboarded (uck, 13:17:29)
   8. Let's stick with template HA onboarding. (uck, 13:18:25)
   9. We state as a wishlist the Kubernetes orchestartion for now and if able to cover include that as one more target (rprakash, 13:21:53)
   10. Is this an installer project? (uck, 13:22:04)
   11. ok ignore Openretriever just focus on orchetsration for resource by kubernetes instaed of heat (rprakash, 13:22:57)
   12. what is the maturity level of tosca2kubernetes? (uck, 13:23:01)
   13. parser project did not complete that in D and we may have to look at ARIA then http://ariatosca.org/about/ (rprakash, 13:24:35)
   14. does aria perform any translation? (uck, 13:27:45)
   15. the way tosca template vs. kubernetes yaml file represent are quite different (uck, 13:29:04)
   16. I mean how they represent a service (uck, 13:29:27)
   17. openstackplugin supports heat so translation seems to be part of that, but need to confirm (rprakash, 13:30:06)
   18. Maybe they do. Since they have their own "tosca" types, it may not be a big issue to translate from one to another (uck, 13:32:53)
   19. yes the apllication/service templates are different called blueprints but seems thy still use tosca node types and other elements links etc. (rprakash, 13:33:23)
   20. we can do a "requirements" type of documentation target maybe, rather than delivering a code (uck, 13:33:52)
   21. agreed that makes sense since we have no clue at this time on details of implementaions on any of the 3 listed work items (rprakash, 13:34:34)
   22. or as I said, we do not worry about translation and support kubernetes yaml input for distribution (uck, 13:34:38)
   23. when a file is published, Domino can automatically identify if it is a kubernetes file and then pick a domain that supports containers. (uck, 13:35:24)
   24. Bryan do you want anything for models to discuss? (rprakash, 13:37:18)

Action items

1. (none)

People present (lines said)

1. uck (28)
2. rprakash (27)
3. collabot (5)
4. bryan_att (0)