The project file is a local source of project information. The project file can be used in conjunction with other project sources, including the NIS maps project.byname and project.bynumber and the LDAP database project. Programs use the getprojent(3PROJECT) routines to access this information.
The example /etc/project file defines two projects: database and appserver. The user defaults are user.database and user.appserver. The admin default can switch between user.database or user.appserver.
hostname$ cat /etc/project … user.database:2001:Database backend:admin:: user.appserver:2002:Application Server frontend:admin:: …
The example /etc/project file shows the resource controls for the application.
hostname$ cat /etc/project … development:2003:Developers:::task.ax-lwps=(privileged,10,deny); process.max-addressspace=(privileged,209715200,deny) …
The example /etc/project file shows the resource pools for the application.
hostname$ cat /etc/project … batch:2001:Batch project:::project.pool=batch_pool process:2002:Process control:::project.pool=process_pool …
The example /etc/project file shows the FSS for two projects: database and appserver. The database project has 20 CPU shares. The appserver project has 10 CPU shares.
hostname$ cat /etc/project … user.database:2001:database backend:admin::project.cpu-shares=(privileged,20,deny) user.appserver:2002:Application Server frontend:admin::project.cpu-shares=(privileged,10,deny) …
If the FSS is enabled but each user and application is not assigned to a unique project, then the users and applications will all run in the same project. By running in the same project, all compete for the same share, in a timeshare fashion. This occurs because shares are assigned to projects, not to users or processes. To take advantage of the FSS scheduling capabilities, assign each user and application to a unique project.
To configure a project, see Local /etc/project File Format in Administering Resource Management in Oracle Solaris 11.4.
The following example configures five applications with different characteristics.
|
Edit the /etc/project file. Map users to resource pools for the app_server, app_db, development, tp_engine, and geo_db project entries.
hostname$ cat /etc/project … user.app_server:2001:Production Application Server::project.pool=appserver_pool user.app_db:2002:App Server DB:::project.pool=db_pool,project.cpu-shares=(privileged,1,deny) development:2003:Test and delopment::staff:project.pool=dev.pool,process.max-addressspace=(privileged,536870912,deny) user.tp_engine:Transaction Engine:::project.pool=tp_pool user.geo_db:EDI DB:::project.pool=db_pool;project.cpu-shares=(privileged,3,deny)
Create the pool.host script and add entries for resource pools.
hostname$ cat pool.host create system host create pset dev_pset (uint pset.max = 2) create pset tp_pset (uint pset.min = 2; uint pset.max = 2) create pset db_pset (uint pset.min = 4; uint pset.max = 6) create pset app_pset (uint pset.min = 1; uint pset.max = 2) create pool dev_pool (string pool.scheduler="IA") create pool appserver_pool (string pool.scheduler="TS") create pool db_pool (string pool.scheduler="FSS") create pool tp_pool (string pool.scheduler="TS") associate pool pool_default (pset pset_default) associate pool dev_pool (pset dev_pset) associate pool appserver_pool (pset app_pset) associate pool db_pool (pset db_pset) associate pool tp_pool (pset tp_pset)
Run the pool.host script and modify the configuration as specified in the pool.host file.
hostname$ poolcfg -f pool.host
Read the pool.host resource pool configuration file and initialize the resource pools on the system.
hostname$ pooladm -c