Angus, do you have specific questions? We could describe in detail what we mean with all these abbreviations.. ) This is kind of telco slang, but surely there is a need to describe this in more detail for OpenStack Community should the need be.
Kind regards/Mit freundlichen Grüßen Yuriy Babenko Von: Angus Salkeld [mailto:asalk...@mirantis.com] Gesendet: Dienstag, 25. November 2014 12:48 An: OpenStack Development Mailing List (not for usage questions) Betreff: Re: [openstack-dev] [Telco] [NFV] [Heat] Telco Orchestration On Tue, Nov 25, 2014 at 7:27 PM, Marc Koderer <m...@koderer.com<mailto:m...@koderer.com>> wrote: Hi all, as discussed during our summit sessions we would like to expand the scope of the Telco WG (aka OpenStack NFV group) and start working on the orchestration topic (ETSI MANO). Therefore we started with an etherpad [1] to collect ideas, use-cases and requirements. Hi Marc, You have quite a high acronym per sentence ratio going on that etherpad;) From Heat's perspective, we have a lot going on already, but we would love to support what you are doing. You need to start getting specific about what you need and what the missing gaps are. I see you are already looking at higher layers (TOSCA) also check out Murano as well. Regards -Angus Goal is to discuss this document and move it onto the Telco WG wiki [2] when it becomes stable. Feedback welcome ;) Regards Marc Deutsche Telekom [1] https://etherpad.openstack.org/p/telco_orchestration [2] https://wiki.openstack.org/wiki/TelcoWorkingGroup _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
