[openstack-dev] [Telco] [NFV] [Heat] Telco Orchestration

Yuriy.Babenko at telekom.de Yuriy.Babenko at telekom.de
Tue Nov 25 14:06:03 UTC 2014

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:asalkeld at 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 <marc at koderer.com<mailto:marc at 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

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.


Goal is to discuss this document and move it onto the Telco WG wiki [2] when
it becomes stable.

Feedback welcome ;)

Deutsche Telekom

[1] https://etherpad.openstack.org/p/telco_orchestration
[2] https://wiki.openstack.org/wiki/TelcoWorkingGroup

OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141125/573a92f6/attachment.html>

More information about the OpenStack-dev mailing list