Hi, In Murano we did couple projects related to networking orchestration. As NFV is a quite broad term I can say that Murano approach fits into it too. In our case we had bunch of virtual appliances with specific networking capabilities and requirements. Some of these appliances had to work together to provide a required functionality. These virtual appliances were exposed as Murano applications with defined dependencies between apps and operators were able to create different networking configuration with these apps combining them according their requirements\capabilities. Underlying workflows were responsible to bind these virtual appliances together. I will be glad to participate in tomorrow meeting and answer any questions you have.
Thanks Georgy On Tue, Nov 25, 2014 at 6:14 AM, Marc Koderer <[email protected]> wrote: > Hi Angus, > > Am 25.11.2014 um 12:48 schrieb Angus Salkeld <[email protected]>: > > On Tue, Nov 25, 2014 at 7:27 PM, Marc Koderer <[email protected]>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;) > > > Haha, welcome to the telco world :) > > > From Heat's perspective, we have a lot going on already, but we would love > to support > what you are doing. > > > That’s exactly what we are planning. What we have is a long list of > use-cases and > requirements. We need to transform them into specs for the OpenStack > projects. > Many of those specs won’t be NFV specify, for instance a Telco cloud will > be highly > distributed. So what we need is a multi-region heat support (which is > already a planned > feature for Heat as I learned today). > > > 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. > > > Yep, I will check Murano.. I never had a closer look to it. > > Regards > Marc > > > 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 >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Georgy Okrokvertskhov Architect, OpenStack Platform Products, Mirantis http://www.mirantis.com Tel. +1 650 963 9828 Mob. +1 650 996 3284
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
