77
88The Pulp Manager application is used to coordinate common Pulp
99workflows and provide additional reporting capabilities about a
10- cluster of Pulp servers. It is designed to work with Pulp3.
10+ cluster of Pulp servers. It is designed to work with Pulp3 servers in
11+ a primary/secondary setup.
1112
12- ## About the Project
13+ ## Why Pulp Manager?
1314
14- We recommend that Pulp be operated in a primary/secondary setup. There
15- is a single Pulp instance known as the Pulp Primary which syncs repos
16- from the Internet and can also have custom or internal packages
17- uploaded to it. Secondaries are then configured to sync these
18- snapshots and internal repos.
15+ Pulp Manager provides centralized orchestration of a clustger of Pulp3
16+ instances and is particularly usfeful for organizations with
17+ multi-tiered or multi-zone deployments who need coordinated syncs
18+ between primary and secondary servers.
1919
2020Pulp3 doesn't provide a method to schedule the synchronisation of
2121repos, and in some repository types (deb) may require multiple steps
@@ -26,7 +26,8 @@ or Jenkins.
2626
2727## Core Team
2828
29- This project is maintained by G-Research. For details on our team and
29+ This project originated at [ G-Research] ( https://github.com/G-Research )
30+ but is now owned by the Pulp project. For details on our team and
3031roles, please see the [ MAINTAINERS.md] ( MAINTAINERS.md ) file.
3132
3233## Documentation Index
@@ -128,17 +129,22 @@ components:
128129
129130## Quick Start
130131
131- 1 . ** Using DevContainers (Recommended) **
132+ 1 . ** For Development (running tests, exploring APIs, etc) **
132133 ``` bash
133- # Open in VS Code and select " Reopen in Container"
134- # Or use the CLI:
134+ # Open in VS Code and select action "Dev Containers: Reopen in Container"
135+ # Or use the Dev Container CLI:
135136 devcontainer up --workspace-folder .
136137 ```
138+
139+ From a terminal in the devcontainer, 'make t' will run the tests.
140+
137141
138- 2 . ** Manual Setup **
142+ 2 . ** For Demo cluster, use the make target to setup a complete Docker Compose environment **
139143 ``` bash
140- make run-pulp-manager
144+ make demo
141145 ```
146+
147+ When startup is finished, ` docker ps ` will show you the components, and all APIs will be listening.
142148
143149For detailed development setup, see the [ Development
144150Info] ( #development-info ) section.
@@ -168,6 +174,7 @@ default_domain=example.com
168174jwt_algorithm=HS256
169175jwt_token_lifetime_mins=480
170176admin_group=pulpmaster-rw
177+ require_jwt_auth=true
171178
172179[pulp]
173180deb_signing_service=pulp_deb
@@ -180,6 +187,7 @@ internal_package_prefix=corp_
180187package_name_replacement_pattern=
181188package_name_replacement_rule=
182189remote_tls_validation=true
190+ use_https_for_sync=true
183191
184192[redis]
185193host=redis
@@ -220,6 +228,9 @@ Defines authentication allowed against the API
220228- ` jwt_token_lifetime_mins ` : Number of minutes JWT is valid for
221229- ` admin_group ` : Directory group user must be a member of to carry out
222230 priveldged actions agains the API
231+ - ` require_jwt_auth ` : Boolean whether to require JWT authentication for
232+ protected API endpoints. Set to false for local development environments
233+ where authentication is not needed. Defaults to true
223234
224235### pulp
225236
@@ -239,6 +250,8 @@ Settings to apply to all pulp servers
239250 the pulp repo config
240251- ` remote_tls_validation ` : Boolean whether to require TLS validation
241252 of remote hosts
253+ - ` use_https_for_sync ` : Boolean whether to use HTTPS for repository sync URLs.
254+ Set to false for local HTTP-only development environments. Defaults to true.
242255
243256### redis
244257
0 commit comments