New Design for Tricircle

Registered by Saggi Mizrahi on 2015-07-22

This is a suggestion to change the current design of Tricircle to a design the will be easier to implement and integrate with the current OpenStack source code.

Instead of changes to the core component we push Tricircle specific plugins and drivers instead of the stock ones. This allows us to override the implementation in a way that conforms with OpenStack's current architecture.

Blueprint information

Status:
Complete
Approver:
Chaoyi Huang
Priority:
Essential
Drafter:
Saggi Mizrahi
Direction:
Approved
Assignee:
Saggi Mizrahi
Definition:
Approved
Series goal:
Accepted for mitaka
Implementation:
Implemented
Milestone target:
None
Started by
Eran Gampel
Completed by
Chaoyi Huang

Related branches

Sprints

Whiteboard

Addressed by: https://blueprints.launchpad.net/tricircle/+spec/implement-stateless
    Implement Stateless Design

Addressed by: https://review.openstack.org/#/c/267293/
    Move statless design from experiment to master branch

Addressed by: https://blueprints.launchpad.net/tricircle/+spec/implement-dal
    Implement database access layer for cascade service.

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

Addressed by: https://review.openstack.org/208508
    nova skeleton

Addressed by: https://review.openstack.org/208507
    networking-tricircle core plugin and security group

Addressed by: https://review.openstack.org/208506
    Base devstack install script first patch only handle networking

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

Addressed by: https://review.openstack.org/208889
    cascade_service dal

Addressed by: https://review.openstack.org/203692
    cascade_service framework

Blueprint Status Etherpad: https://etherpad.openstack.org/p/TricircleToDo

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.