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.

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

modules should be restructured to allow extensions #26

Open
a5anka opened this issue Aug 10, 2017 · 1 comment
Open

modules should be restructured to allow extensions #26

a5anka opened this issue Aug 10, 2017 · 1 comment

Comments

@a5anka
Copy link
Member

a5anka commented Aug 10, 2017

I propose the following module restructuring to manage multiple coordination strategy implementations effectively.

List of modules,

  • org.wso2.carbon.cluster.coordinator.core - This will include the core logic independent of the coordination strategy implementation. This will use a configuration to select between the available CoordinationStrategy implementations. An OSGI service implementation can be used to indicate the availability of the component.
  • org.wso2.carbon.cluster.coordinator.rdbms - This component will provide the rdbms based implementation as a OSGi service
  • org.wso2.carbon.cluster.coordinator.zookeeper - This component will provide the ZooKeeper based implementation as a OSGi service

coordination-module-restructure

@a5anka
Copy link
Member Author

a5anka commented Aug 14, 2017

Part of the implementation is done in #28. Tasks left to do are,

  • Using a configuration to select a coordination strategy when multiple implementations are available in the OSGI environment.
  • Packing the config with feature (not directly related to the feature)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant