Settings¶
Pulp uses three types of settings:
Django settings Pulp is configuring
RQ settings Pulp is using
Django Settings¶
Pulp is a Django project, so any Django Django setting can also be set to configure your Pulp deployment.
SECRET_KEY¶
In order to get a pulp server up and running a Django SECRET_KEY must be provided.
The following code snippet can be used to generate a random SECRET_KEY.
1 2 3 4 | import random
chars = 'abcdefghijklmnopqrstuvwxyz0123456789!@#$%^&*(-_=+)'
print(''.join(random.choice(chars) for i in range(50)))
|
DATABASES¶
By default Pulp uses PostgreSQL on localhost. For all possible configurations please refer to Django documentation on databases
DEFAULT_FILE_STORAGE¶
By default, Pulp uses the local filesystem to store files. The default option which uses the local filesystem is
pulpcore.app.models.storage.FileSystem
.This can be configured though to alternatively use Amazon S3. To use S3, set
DEFAULT_FILE_STORAGE
tostorages.backends.s3boto3.S3Boto3Storage
. For more information about different Pulp storage options, see the storage documentation.
MEDIA_ROOT¶
The location where Pulp will store files. By default this is /var/lib/pulp/.
If you’re using S3, point this to the path in your bucket you want to save files. See the storage documentation for more info.
It should have permissions of:
mode: 750
owner: pulp (the account that pulp runs under)
group: pulp (the group of the account that pulp runs under)
SELinux context: system_u:object_r:var_lib_t:s0
LOGGING¶
By default Pulp logs at an INFO level to syslog. For all possible configurations please refer to Django documenation on logging.
AUTHENTICATION_BACKENDS¶
By default, Pulp has two types of authentication enabled, and they fall back for each other:
Basic Auth which is checked against an internal users database
Webserver authentication that relies on the webserver to perform the authentication.
To change the authentication types Pulp will use, modify the
AUTHENTICATION_BACKENDS
settings. See the Django authentication documentation for more information.
RQ Settings¶
The following RQ settings can be set in your Pulp config:
REDIS_URL
REDIS_HOST
REDIS_PORT
REDIS_DB
REDIS_PASSWORD
SENTINEL
These will be used by any worker loaded with the -c 'pulpcore.rqconfig'
option.
Below are some common settings used for RQ configuration. See the RQ settings documentation for information on these settings.
REDIS_HOST¶
The hostname for Redis. By default Pulp will try to connect to Redis on localhost. RQ documentation contains other Redis settings supported by RQ.
REDIS_PORT¶
The port for Redis. By default Pulp will try to connect to Redis on port 6380.
REDIS_PASSWORD¶
The password for Redis.
Pulp Settings¶
Pulp defines the following settings itself:
WORKING_DIRECTORY¶
The directory used by workers to stage files temporarily. This defaults to
/var/lib/pulp/tmp/
.It should have permissions of:
mode: 755
owner: pulp (the account that pulp runs under)
group: pulp (the group of the account that pulp runs under)
SELinux context: unconfined_u:object_r:var_lib_t:s0
Note
It is recommended that WORKING_DIRECTORY
and MEDIA_ROOT
exist on the same storage
volume for performance reasons. Files are commonly staged in the WORKING_DIRECTORY
and
validated before being moved to their permanent home in MEDIA_ROOT
.
CONTENT_ORIGIN¶
A required string containing the protocol, fqdn, and port where the content app is reachable by users. This is used by
pulpcore
and various plugins when referring users to the content app. For example if the API should refer users to content at using http to pulp.example.com on port 24816, (the content default port), you would set:https://pulp.example.com:24816
.
CONTENT_PATH_PREFIX¶
A string containing the path prefix for the content app. This is used by the REST API when forming URLs to refer clients to the content serving app, and by the content serving application to match incoming URLs.
Defaults to
'/pulp/content/'
.
CONTENT_APP_TTL¶
The number of seconds before a content app should be considered lost.
Defaults to
30
seconds.
REMOTE_USER_ENVIRON_NAME¶
The name of the WSGI environment variable to read for webserver authentication.
Warning
Configuring this has serious security implications. See the Django warning at the end of this section in their docs for more details.
Defaults to
'REMOTE_USER'
.
PROFILE_STAGES_API¶
A debugging feature that collects profile data about the Stages API as it runs. See staging api profiling docs for more information.
Warning
Profiling stages is provided as a tech preview in Pulp 3.0. Functionality may not fully work and backwards compatibility when upgrading to future Pulp releases is not guaranteed.