Separate murano service broker from murano itself

Registered by Nikolay Starodubtsev

In current implementation service broker can be only installed on the node with murano itself. To avoid this in the future we need to support this things:
1) Create separate db for murano service broker
2) Create separate paste.ini
3) Service broker should use python-muranoclient for communication with murano
4) Probably we should move it to a separate repository entirely.

Blueprint information

Status:
Complete
Approver:
Serg Melikyan
Priority:
Low
Drafter:
Nikolay Starodubtsev
Direction:
Approved
Assignee:
zhurong
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Nikolay Starodubtsev
Completed by
Nikolay Starodubtsev

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/separate-service-broker-from-murano,n,z

Addressed by: https://review.openstack.org/302081
    Add models and migration for new service broker db

Addressed by: https://review.openstack.org/302528
    Generator new service broker db

Addressed by: https://review.openstack.org/305298
    Create separate paste.ini for service broker

Addressed by: https://review.openstack.org/307239
    Remove cloudfoundry api from murano.api

Addressed by: https://review.openstack.org/308133
    [WIP]Fix service broker test failed when separate from murano

Gerrit topic: https://review.openstack.org/#q,topic:bug/1500777,n,z

Addressed by: https://review.openstack.org/349156
    [Docs]Update the Murano service broker install guide

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.