Show Table of Contents
Chapter 4. Team and Global Team Management
Teams contain a group of developers that are part of a conjoined role within a domain, and are created and owned by developers.
As an OpenShift Enterprise administrator, you can create global teams from a preexisting source, such as an LDAP database, and synchronize team membership. Note that each global team must have a unique name.
Table 4.1. Teams and Global Teams
| Team Types | Owner | Use | Conditions |
|---|---|---|---|
| Team | Developer | To collaborate on an application | Each team name must be unique name within a domain. |
| Global team | Administrator | To reuse existing group definitions for user management, such as LDAP groups. | Each global team name must be unique. |
Note
By default, developers cannot view and search global teams. As an OpenShift Enterprise administer, you must enable this capability so that global teams can be viewed and searched by developers.
4.1. Setting the Maximum Number of Teams for Specific Users
On the broker host, you can set a limit to the number of teams a developer can create with the following command:
# oo-admin-ctl-user -l username --setmaxteams No_of_Teams
The default number is set to
0. Edit the DEFAULT_MAX_TEAMS setting located in the /etc/openshift/broker.conf file to change the default setting for any new users created after the setting has been modified. Restart the broker service for the changes to take effect.
For more information on teams, see the OpenShift Enterprise User Guide at https://access.redhat.com/site/documentation.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.