[
https://issues.apache.org/jira/browse/BIGTOP-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13857620#comment-13857620
]
Konstantin Boudnik commented on BIGTOP-1136:
--------------------------------------------
Replying to the ticket and somewhat to the email thread you have started here
http://is.gd/yYZDhF. While my heart is bleeding to the people using LDAP ;), I
don't think it would be practical to embed it into Bigtop stack. Mainly, I am
talking from experience of producing Sun's Java Enterprise Stack (JES) a decade
ago. Directory servers are tricky to get right in the vast set of the user
environments.
Bigtop has the toolchain mechanism for setting up development environment,
including users and software. I don't see why the same Puppet module - or an
extension of it - can't be used to populate one's multitenant environment. The
beauity of Puppet is flexibility and a straight-forward way of updating the
achieve an immediate result. Also, it is already there.
While it won't provide a user with ability to test his HDFS with LDAP it will
guarantee the presence of the particular users on all the hosts of the cluster.
I am Ok with having iTests cases that will rely on the existence of certain
users in their scenarios: the test should fail with a comprehensive message if
a particular user isn't present, IMO.
Does it make sense?
> Testing Multitenancy and Multiuser applications
> -----------------------------------------------
>
> Key: BIGTOP-1136
> URL: https://issues.apache.org/jira/browse/BIGTOP-1136
> Project: Bigtop
> Issue Type: New Feature
> Components: Tests
> Reporter: jay vyas
> Priority: Minor
>
> One of the items which is important for emerging, more flexible hadoop
> deployments is multitenancy.
> JIRA's such as this one: https://issues.apache.org/jira/browse/MAPREDUCE-5571
> Are very hard to test, and it would be extremely useful to many people
> deploying non standard hadoop environments , if they could test that
> multitenant and multiuser support was functional on their cluster.
> This is sort of related to the stress tests jira
> https://issues.apache.org/jira/browse/BIGTOP-1065, also recently created.
> I'm not really even sure this is possible in a fully automated / iTest sort
> of fashion... so to start, any thoughts on how bigtop should test multi user,
> multi tenant workloads? One simple way to do it would be to launch 4 or 5
> "calculate pi" jobs at one time, maybe from different users? But how could
> we "predict" off hand the usernames which will be available and appropriate
> to submit jobs on a cluster, without the user specifying them?
> In any case, bigtop smokes is ideal for this kind of testing, because this
> kind of testing is really only applicable to a cluster which is being used by
> for a real deployment. Other tests (i.e. pig smoke tests) are well handled
> and covered by the individual ecosystem projects.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
