Open Stack

Ok, I belive we can take it in mind as possible resolution. The problem is
that it will take it us too long, so we can discuss it while we will plan
Mitaka development.
However it's not a decision of the problem with service broker API for now.



Nikolay Starodubtsev

Software Engineer

Mirantis Inc.


Skype: dark_harlequine1

2015-08-27 23:25 GMT+03:00 Dmitry <meytin at gmail.com>:

> I would say to extend murano with additional capabilities.
> Dependency management for composite applications is very important for
> modern development so, I think, adding additional use-cases could be very
> benifitial for Murano.
> On Aug 27, 2015 2:53 PM, "Nikolay Starodubtsev" <
> nstarodubtsev at mirantis.com> wrote:
>
>> Dmitry,
>> Does I understand properly and your recommendation is to change some
>> murano logic?
>>
>>
>>
>> Nikolay Starodubtsev
>>
>> Software Engineer
>>
>> Mirantis Inc.
>>
>>
>> Skype: dark_harlequine1
>>
>> 2015-08-24 23:31 GMT+03:00 Dmitry <meytin at gmail.com>:
>>
>>> I think that you can model application dependencies in a way it will
>>> allow multi-step provisioning and further  maintenance of each component.
>>> The example of such modeling could be seen in OASIS TOSCA.
>>> On Aug 24, 2015 6:19 PM, "Nikolay Starodubtsev" <
>>> nstarodubtsev at mirantis.com> wrote:
>>>
>>>> Hi all,
>>>> Today I and Stan Lagun discussed a question "How we can provision
>>>> complex murano app through Cloud Foundry?"
>>>> Here you can see logs from #murano related to this discussion:
>>>> http://eavesdrop.openstack.org/irclogs/%23murano/%23murano.2015-08-24.log.html#t2015-08-24T09:53:01
>>>>
>>>> So, the only way we see now is to provision apps which have
>>>> dependencies is step by step provisioning with manually updating JSON files
>>>> each iteration. We appreaciate any ideas.
>>>> Here is the link for review:
>>>> https://review.openstack.org/#/c/196820/
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Nikolay Starodubtsev
>>>>
>>>> Software Engineer
>>>>
>>>> Mirantis Inc.
>>>>
>>>>
>>>> Skype: dark_harlequine1
>>>>
>>>>
>>>> __________________________________________________________________________
>>>> OpenStack Development Mailing List (not for usage questions)
>>>> Unsubscribe:
>>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>
>>>>
>>>
>>> __________________________________________________________________________
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150828/773dbf84/attachment.html>