Description of problem: Cumin currently has 3 different presentations that users can select from (default, messaging, and grid). Make the grid persona the choice ootb.
Fixed in revision 5231 Default value for the "persona" parameter has been changed to grid. Settings for "datas" in standard cumin.conf at installation have also been changed to run the grid cumin-data instances, with comments changed as well.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause Majority use of Cumin is in grid deployments but the default installation sets up the console for the "default" persona. Consequence Grid users have extra steps during configuration to switch the persona to "grid". Change Change the default installation to set up the "grid" persona. Result What now happens when the actions or circumstances above occur. Note: this is not the same as the feature request was fulfilled.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -8,5 +8,4 @@ Change the default installation to set up the "grid" persona. Result - What now happens when the actions or circumstances above occur. + The UI presentation and the set of cumin-data instances at runtime will now correspond to the "grid" persona in a default installation. Users may still choose the "messaging" or "default" persona by editing cumin.conf (the so-called "default" persona contains both messaging and grid UIs)- Note: this is not the same as the feature request was fulfilled.
How to test default grid persona on install: 1) Install cumin, condor, and qpid-cpp-server on a clean system. 2) Use an unmodified /etc/cumin/cumin.conf file. 3) start everything up 4) Check for presence of correct cumin-data instances after startup. Content in /var/log/cumin/master.log should look like this, with these cumin-data instances. # tail -f /var/log/cumin/master.log 6934 2012-04-25 15:55:53,649 INFO Started subprocess (pid 6940): cumin-web --section=web --daemon 6934 2012-04-25 15:55:53,660 INFO Started subprocess (pid 6941): cumin-data --section=data.grid --daemon 6934 2012-04-25 15:55:53,669 INFO Started subprocess (pid 6942): cumin-data --section=data.grid-slots --daemon 6934 2012-04-25 15:55:53,681 INFO Started subprocess (pid 6943): cumin-data --section=data.grid-submissions --daemon 6934 2012-04-25 15:55:53,689 INFO Started subprocess (pid 6944): cumin-data --section=data.sesame --daemon 5) Create a user and login. Initial page should be the Administrator->Grid->Overview tab. Inventory, Your account, and Grid user tabs should also be there with no Messaging.
Tested on RHEL 5/6 i386/x86_64 cumin-0.1.5624-1 All works as expected. --> VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0564.html