Hi, I need a pointer to some documentation (possibly).
I've always done Streams application development on my laptop with a single user account for both Streams administration and for programming.
But soon I'll be helping configure a single machine for use by multiple developers, so I'm wondering how to give multiple people all the ability to write Streams applications and run them as both standalone and distributed without clobbering each others work.
Assuming that we install Streams into the /opt/ibm path with owner as "streamsadmin", do I then create separate Linux user accounts for each developer? Do I need to do anything special with their group ID's, file permissions, or anything else to make this work?
Or is it better if each developer installs their own copy of Streams under their respective home directories?
This topic has been locked.
1 reply Latest Post - 2012-10-16T12:54:49Z by laurieaw
Pinned topic multiple Streams application developers on a single Linux machine?
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
laurieaw 1100006HTR72 PostsACCEPTED ANSWER
Re: multiple Streams application developers on a single Linux machine?2012-10-16T12:54:49Z in response to Kevin_FosterYou can setup your environment in multiple ways. It depends on where you want the burden of the administration of the product and instance to be, one user or spread out; and the characteristics of the Streams instance; if you have multi-host environment etc.....
1. Shared installation with each user creating their own instance.
2. Shared installation with only one instance that all users share.
3. Each user installs the product and uses their own private copy and own instance.
4. Combinations of the above.
We do have various topics in the documentation that will be of interest for you to review. I will point them out in the following information. Some of these areas could be better documented and we are working on that and we always welcome suggestions to improve the documentation.
1. Install the product to a directory that is accessible by all users. This can be the shared file system except if you run with SELinux set to enforcing you cannot install to the shared file system.
See this link for details: http://publib.boulder.ibm.com/infocenter/streams/v2r0/topic/com.ibm.swg.im.infosphere.streams.install-admin.doc/doc/ibminfospherestreams-install-options-configuration.html
2. In a multi-host environment, users home directories must be in a shared file system.
3. Users have to have search permissions to the install owners .streams configuration directories and its parent. See http://publib.boulder.ibm.com/infocenter/streams/v2r0/topic/com.ibm.swg.im.infosphere.streams.install-admin.doc/doc/ibminfospherestreams-instance-host-dynamic-selection.html. Note: you have to either have a install-owner/.streams/bin/streams_get_available_hosts script or ~install-owner/.streams/config/hostfile file; but you don't need both. The installation program will create a default host file.
Setting up a instance that is shared:
In essence you will want to create an instance owned by an administrator ID (i.e. streamsadmin). There is a shipped template called shared that you can use. If you use this you also need to specify an AdminGroup (and optionally a UsersGroup) property. This is strictly your choice. You can also just create an instance without a template then start it and manage the permissions from the Streams Console. You can add groups and users and manage the permissions. There is also a streamtool setacl command that can be used to do this as well, but using Streams Console is easier.
There is a table in this links that describes what the permissions mean for that object. http://publib.boulder.ibm.com/infocenter/streams/v2r0/topic/com.ibm.swg.im.infosphere.streams.install-admin.doc/doc/ibminfospherestreams-user-security-authorization.html
You will also want to look into copying the users public key to the instance's Security Public Key directory. This will eliminate the user from being prompted for user id and pwd when submitting jobs. The documentation in the following links will talk about that.
Setting up security for IBM® InfoSphere® Streams
Creating and configuring Streams instances