Consumos por electrodomésticos

As a convenience, the Pure Directory Service can attempt to automatically fetch certificate data from the directory server. If certificate data is successfully retrieved from the server, it undergoes the same trust check as manually entered certificate data, however if trust cannot be determined the operation will not continue. If certificate data is successfully retrieved and the CA certificate is trusted, a final prompt to confirm the data is displayed.

pureds Subcommands

The pureds disable subcommand disables the directory service. This will stop any users in the directory from logging in. If used with the --checkpeer option, server authenticity enforcement using a certificate is disabled, but the directory service status remains unchanged.

The pureds enable subcommand enables the directory service. This will allow users in the directory to log in. At a minimum, a URI, base DN, bind user and bind pw, and at least one group must be configured before the Pure Directory Service can be enabled. If used with the --checkpeer option, server authentic-ity enforcment using the configured CA certificate is enabled, but the directory service status remains unchanged. A certificate must be configured before enabling the checkpeer option.

The pureds list subcommand displays the current base configuration. Alternatively, if the --groups option is specified, group configuration consisting of the group names and group base is displayed. If the --certificate option is specified, currently configured CA --certificate data is displayed.

The pureds setattr subcommand can be used to set or clear URIs, base DN, bind user, bind password, read-only group, user group, admin group, group base, and certificate data.

The pureds test subcommand tests the current configuration by running a series of tests. This command can be run at any time. Running the command verifies that the URI can be resolved and that we can bind and query the tree using the bind user credentials. It also verifies that it can find all the configured groups to ensure the Common Names and group base are correctly configured. If checkpeer is enabled, the intial bind and query test is repeated while enforcing server authenticity using the CA certificate. Addtionally, the tests to find configured groups also enforce server authenticity.

Examples

Example 1

pureds setattr --uri "ldaps://ad1.mycompany.com,ldaps://ad2.mycompany.com" --basedn "DC=mycompany,DC=com" --binduser ldapreader

Sets the URI to both ad1.mycompany.com and ad2.mycompany.com and the scheme to ldaps:// to enable SSL. This also sets the base DN to be the correct Domain Components and sets the bind user username (or sAMAccountName). If there was no base DN set previously, explicitly setting the base DN is unnecessary.

Example 2

pureds setattr --readonlygroup purereadonly --usergroup pureusers --admingroup pureadmins pureds setattr --groupbase "OU=PureGroups,OU=SAN,OU=IT,OU=US"

pureds

Example 3

pureds setattr --bindpw Enter bind password:

Retype bind password:

Shows the interactive prompt for entering a password for the bind user account. The password is not shown while typing, so a confirmation prompt is presented. If the passwords do not match, no change is made.

Example 4

pureds test

Testing from ct0:

Searching ldaps://ad1.mycompany.com... PASSED Searching for group CN=purereadonly... PASSED Searching for group CN=pureusers... PASSED Searching for group CN=pureadmins... PASSED Searching ldaps://ad2.mycompany.com... PASSED Searching for group CN=purereadonly... PASSED Searching for group CN=pureusers... PASSED Searching for group CN=pureadmins... PASSED pureds enable

Shows successful output of testing the current configuration and enabling the service following the suc-cessful test.

See Also

puredns(1),

Author

Pure Storage Inc. <[email protected]>

Name

purehgroup, purehgroup-create, purehgroup-delete — manage the creation, deletion, and population of Purity host group (hgroup) objects.

Synopsis

purehgroup create [--hostlist HOST-LIST] HGROUP...

purehgroup delete HGROUP...

purehgroup setattr { --addhostlist HOST-LIST | --hostlist HOST-LIST | --remhostlist HOST-LIST } HGROUP

Arguments

HGROUP

Host group name. The purehgroup create command assigns the name to the host group being created.

The purehgroup delete and purehgroup setattr commands use host group names to identify the host groups to be operated upon.

Object Names

Purity object names use the Internet domain name (RFC 1035) character set plus the underscore character (_). The valid characters are letters (A-Z and a-z), digits (0-9), and the hyphen (-) and underscore (_) characters. The first and last characters of a name must be alphanumeric, and a name may not be entirely numeric.

Array names may be 1-56 characters in length; other objects that can be named (host groups, hosts, SN-MP managers, and volumes) may be 1-63 characters in length. (Array name length is shorter so that the names of individual controllers, which are assigned by Purity based on the array name, do not exceed the maximum allowable by DNS.)

Names are case-insensitive on input. For example, vol1, Vol1, VOL1, etc. all represent the same volume.

Purity displays names in the case in which they were specified in the create or rename subcommand that created the objects, regardless of the case in which they are entered in management commands.

Options

-h | --help

Can be used with any command or subcommand to display a brief syntax description.

--addhostlist (purehgroup setattr only)

Comma-separated list of one or more additional hosts to be associated with the host group. Has no effect on hosts already associated with the group.

--hostlist

Comma-separated list of one or more hosts to be associated with the host group. When specified in the purehgroup setattr command, replaces the entire membership of a host group.

--remhostlist (purehgroup setattr only)

Comma-separated list of one or more host objects whose associations with the host group are to be broken.

purehgroup

Description

A Purity host group is an abstraction that implements consistent connections between a set of hosts and one or more volumes. Connections are consistent in the sense that all hosts associated with a host group address a volume connected to the group by the same LUN. Host groups are typically used to provide a common view of storage volumes to the hosts in a clustered application.

When a host is associated with a host group, Purity automatically connects it to all volumes connected to the group.

The hosts associated with a host group may be specified via the --hostlist option when the group is created.

Hosts may be added to and removed from a host group at any time by the purehgroup setattr command.

A host may only be associated with one host group at a time, whereas a volume may be connected to multiple host groups as well as to individual hosts simultaneously.