Open Stack

Hi Mathieu,

>Can you tell us more about those projects? Does it include
>mutli-datacenter use cases?

Most of this work was done as a custom projects for customers. I have to
ask them for a permission to share details.
We do not support multi-datacenter placement officially, but this feature
was developed for one of the customer and now is under review in upstream.
Here is a review link: https://review.openstack.org/#/c/125717/

Technically we can create multiple Heat stacks in different regions and
orchestrate Heat stack updates with proper resources through Murano
workflows.

>Can you provide us a link to such a Murano Application, how you define
>dependencies with apps, and how you translate those dependencies in
>networking configuration?

As I told, this was a custom work for customers, so they own these
packages. The best example we have publically available is here:
https://github.com/sergmelikyan/murano-app-incubator/blob/f5-loadbalancer/io.murano.traffic.f5.NeutronLoadBalancer/Classes/F5NeutronLoadBalancer.yaml

As you see, we do not translate dependencies to network configs. Instead of
translation we just provide a way to script necessary steps and expose them
as workflows or "functions" which can be invoked by other applications. In
this example we have F5LB which adds a Neutron resources to Heat template
to create VIP and Pool Memebers and then extends F5 configuration by adding
F5 specific LB method and adding IRule for redirect via calling BIGIP API
directly. Here is an application wich has a dependency for LB:
https://github.com/sergmelikyan/murano-app-incubator/blob/f5-loadbalancer/io.murano.apps.SimpleWebApp/Classes/SimpleWebApp.yaml

Dependency is a generic
loadBalancer:Contract: $.class(traffic:LoadBalancer)
Based on which actual LoadBalancer implementation is selected by user
during confutation step (NeutronLB or F5NeutronLB) the result of execution
of these lines
https://github.com/sergmelikyan/murano-app-incubator/blob/f5-loadbalancer/io.murano.apps.SimpleWebApp/Classes/SimpleWebApp.yaml#L42-L43
will be different.

Thanks
Georgy

On Wed, Nov 26, 2014 at 4:58 AM, Mathieu Rohon <mathieu.rohon at gmail.com>
wrote:

> Hi,
>
> On Wed, Nov 26, 2014 at 12:48 AM, Georgy Okrokvertskhov
> <gokrokvertskhov at mirantis.com> wrote:
> > Hi,
> >
> > In Murano we did couple projects related to networking orchestration. As
> NFV
>
> Can you tell us more about those projects? Does it include
> mutli-datacenter use cases?
>
> > 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.
>
> Can you provide us a link to such a murano Application, how you define
> dependencies with apps, and how you translate those dependencies in
> networking configuration?
>
> > 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 <marc at koderer.com> wrote:
> >>
> >> Hi Angus,
> >>
> >> Am 25.11.2014 um 12:48 schrieb Angus Salkeld <asalkeld at mirantis.com>:
> >>
> >> On Tue, Nov 25, 2014 at 7:27 PM, Marc Koderer <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
> >>> 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
> >>> OpenStack-dev at lists.openstack.org
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>
> >>
> >> _______________________________________________
> >> OpenStack-dev mailing list
> >> OpenStack-dev at lists.openstack.org
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>
> >>
> >>
> >> _______________________________________________
> >> OpenStack-dev mailing list
> >> OpenStack-dev at lists.openstack.org
> >> 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
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141126/ff3f8f27/attachment.html>