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

Allow topologies to be executed as specific users #43

Open
pdread100 opened this issue May 28, 2015 · 6 comments
Open

Allow topologies to be executed as specific users #43

pdread100 opened this issue May 28, 2015 · 6 comments

Comments

@pdread100
Copy link
Contributor

Some users want the option of running their topologies as a specific user. This on the surface would be easy to do by setting the FrameworkInfo.setUser() to that user. However that would force the Supervisor and LogViewer (PR) to run as that user as well. There may be scenarios where this is not advisable.

It appears that if CommandInfo.setUser() is set then the supervisor/topologies will be run as that user. I know mesos/myriad has gone through extensive coding to get this right, including chown of the installation directories.

@erikdw
Copy link
Collaborator

erikdw commented Jan 31, 2016

This relates to extensive efforts in storm-0.10.0+ to have user-specific topologies via "storm authentication":

@erikdw
Copy link
Collaborator

erikdw commented Nov 6, 2016

I'm not planning to work on this.

@erikdw erikdw closed this as completed Nov 6, 2016
@erikdw erikdw reopened this Feb 28, 2017
@erikdw
Copy link
Collaborator

erikdw commented Feb 28, 2017

@fuji-151a & @JessicaLHartog : FYI, this relates to PR #195. Please take note of @pdread100's initial comment about the user for the Supervisor and Logviewer. Since the launching of Logviewer is not supported by me in this project (not until STORM-1342 is fixed!), I don't particularly care about that part of it. And considering the Supervisor -- I don't see a problem with it being the same user as the workers.

@erikdw
Copy link
Collaborator

erikdw commented Feb 28, 2017

Notably, the idea with this issue was I think to not only allow the storm processes to run as a non-root user, but also to be able to allow different topologies to have different users. That would be a further enhancement beyond the change proposed to #195. I suppose it could be a Topology-specific configuration option, similar to the topology.mesos.worker.cpu option. e.g., topology.mesos.user.

@fuji-151a
Copy link
Contributor

@erikdw

I don't see a problem with it being the same user as the workers.

I agree.
However, I want to specify separately for the user of Nimbus outside the Mesos cluster and the user of Supervisor inside the Mesos cluster.
I think the function of this issue is very wonderful, but I don't need that thing.

@erikdw
Copy link
Collaborator

erikdw commented Mar 4, 2017

@fuji-151a : gotcha. Please give us a bit of time to merge the proposed change in #195, I wanna test it myself first.

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