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

Automatically create resources on EnMasse #613

Open
ctron opened this issue May 8, 2018 · 3 comments
Open

Automatically create resources on EnMasse #613

ctron opened this issue May 8, 2018 · 3 comments

Comments

@ctron
Copy link
Contributor

ctron commented May 8, 2018

I would like to create some kind of functionality which extracts the Tenant information from Hono in order to automatically provision messaging resources in EnMasse.

Basically taking newly created tenants (or recently dropped ones) to requests addresses from EnMasse instead of manually executing a curl command.

@sysexcontrol
Copy link
Contributor

Would that be plugged into the creation of a tenant then?
Or are you more thinking of a making all tenant information accessible from EnMasse, so it could synchronize at any time?

In the latter case, I would have the concern that in true multi tenant setups IMHO usually there is no "super user" that can access all tenants, but only single tenant users that can access exactly the tenant that they were created for.

@ctron
Copy link
Contributor Author

ctron commented May 9, 2018

Up until now I haven't any specific plans other than getting rid of manual provisioning.

The way the service broker works (at least my basic understanding of it) would be that some component (e.g. the Hono component having all the tenant informations) would publish a request for new resources. EnMasse would pick this up (or would get informed) and provision the new resources.

If there is a "super user" it would be OpenShift/Kubernetes probably with service accounts.

@sophokles73
Copy link
Contributor

I would like to make sure, though, that we do not introduce a direct dependency on an enMasse component in Hono. An elegant way to solve this might be to publish corresponding events from within the Tenant service which could be processed by enMasse in order to manage the resources ...

@sysexcontrol sysexcontrol added this to the 0.8 milestone Aug 23, 2018
@sophokles73 sophokles73 removed this from the 0.8 milestone Nov 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants