Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Chor registry should use a database instead a static map #14

Open
leonardofl opened this issue Jan 4, 2013 · 0 comments
Open

Chor registry should use a database instead a static map #14

leonardofl opened this issue Jan 4, 2013 · 0 comments
Labels
Choreography Deployer improvement

Comments

@leonardofl
Copy link
Member

If the Choreography Deployer is restarted it can not lose information about the running choreographies, so we must transform the static map that stores choreographies information in a database.

This is not necessary to the Deployment Manager, since the available nodes can be retrieved from the cloud gateway, and the installed services in each node can be retrieved from Chef.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Choreography Deployer improvement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@leonardofl