package user

[WW451512]

Hi All,

How can we create a package-user for serviceguard package. This user will be present where the package runs.

I know there are some "Access Control Policy Pararmeters" in cluster config file. I am not sure if this is exactly the thing.
But is there anything apart from this related to "package user"?

Thanks

[Basheer_2]

Hello,

in the cluster config file, there are 3 access control policy for the CLUSTER

USER_NAME
USER_HOST
USER_ROLE

for USER_ROLE

* MONITOR: read-only capabilities for the cluster and packages
# * PACKAGE_ADMIN: MONITOR, plus administrative commands for packages
# in the cluster
# * FULL_ADMIN: MONITOR and PACKAGE_ADMIN plus the administrative
# commands for the cluster.


Access control policy does not set a role for configuration
# capability. To configure, a user must log on to one of the
# clusterâ s nodes as root (UID=0). Access control
# policy cannot limit root usersâ access.
#
# MONITOR and FULL_ADMIN can only be set in the cluster configuration file,
# and they apply to the entire cluster. PACKAGE_ADMIN can be set in the
# cluster or a package configuration file. If set in the cluster
# configuration file, PACKAGE_ADMIN applies to all configured packages.
# If set in a package configuration file, PACKAGE_ADMIN applies to that
# package only.

[rariasn]

Hi,


Sample "Access Control Policy":

USER_NAME root
USER_HOST node1
USER_ROLE full_admin

USER_NAME root
USER_HOST node2
USER_ROLE full_admin

# Advanced user
USER_NAME user1
USER_HOST CLUSTER_MEMBER_NODE
USER_ROLE package_admin

# Monitor user

USER_NAME user2
USER_HOST CLUSTER_MEMBER_NODE
USER_ROLE monitor

# cmgetconf -v -K -c cluster_name cluster_name.txt

Modify cluster_name.txt to add Policy Parameter.

# cmcheckconf -v -k -C cluster_name.txt

# cmapplyconf -v -k -C cluster_name.txt

rgs,

[Stephen Doud]

Newer versions of Serviceguard support package-level administration by users.
The modular package configuration file contains the following text:

# Access Control Policy Parameters.
#
# "user_name", "user_host" and "user_role" specify who can administer
# this package.
#
# Three entries set the access control policy for the package: the
# first line must be "user_name", the second "user_host", and the third "user_role".
# Enter a value after each.
#
# 1. "user_name" can either be "any_user", or a maximum of
# 8 login names from the /etc/passwd file on user host.
# 2. "user_host" is where the user can issue Serviceguard commands.
# Choose one of these three values: "any_serviceguard_node",
# or (any) "cluster_member_node", or a specific node. For node,
# use the name portion of the official hostname supplied by the
# domain name server, not the IP addresses or fully qualified name.
# 3. "user_role" must be "package_admin". This role grants permission
# to "monitor", plus for administrative commands for the package.
#
# These policies do not affect root users. Access Policies defined in
# this file must not conflict with policies defined in the cluster
# configuration file.
#
# Example: to configure a role for user john from node noir to
# administer the package, enter:
# user_name john
# user_host noir
# user_role package_admin
#
# Legal values for user_name:
# A string of tokens each of which starts with alphanumeric character and contains
# only alphanumeric and underscore(_) characters. The tokens must be separated by a space
# or a tab character.
# Maximum length of each user_name is 39 character.
#
# Legal values for user_host:
# Any string that starts and ends with an alphanumeric character, and
# contains only alphanumeric characters, dot(.), dash(-), or underscore(_)
# in the middle.
# Maximum length is 39 character.
#
# Legal values for user_role: package_admin.

#user_name
#user_host
#user_role

[WW451512]

Thanks to all for confirming....!