"Hosting a Custom Forge with Pulp" by Michael Hrivnak of Red Hat at Puppet Camp Raleigh 2013.

1. Private Forge and More with Pulp
Presented by:
Michael Hrivnak
mhrivnak@redhat.com
mhrivnak in #pulp
http://www.pulpproject.org

2. What is Pulp?
Manage repositories of content
Push content out to client machines
Supports RPM and Puppet Modules today
Part of the Future Red Hat Satellite
OSS under GPL2
https://github.com/pulp
Python

3. Create New Repositories
Create a new repository in Pulp
Sync content from a remote repo, manually or
on a schedule
Upload your own content
Copies are cheap

4. Publish Your Repository
Mix and match content, then publish
Push content out to any number of consumers
Not limited to any particular kind of content

5. Content Types
RPM family
Puppet Modules
More in the pipeline

6. Consumers
Pulp Agent runs on the consumer
Communicates via AMQP message broker
Install / Update / Remove content remotely
Other actions, such as reboot

7. DEMO

8. Pulp Nodes
Parent Pulp server distributes content to child
Pulp servers
Central management with multi-site scalability
Children can exist behind strict firewalls

9. Use Case: Dev / Test / Production
Pull content into a development repository
“Promote” by copying to a Test repository, and
then to a Production repository
Useful for testing upstream content, such as
new RHEL point releases

10. DEMO

11. Use Case: Mirror PuppetForge
Sync part or all of PuppetForge to a local
repository
Add or remove modules as desired
Retain old versions

12. Future Use Case: Mirror PyPi
Sync part or all of PyPi to a local repository
Add custom packages
Retain old versions

13. Extensible
Standard ways to support new content types
Auto-discovery of support for new types

14. Plugins
Type Definition
JSON file
Importer
Used to pull in upstream content
One per repository
Distributor
Used to publish content
Many per repository

15. Extensions
Okaara framework
https://github.com/jdob/okaara
Hierarchical design, makes it easy to extend
Many generic commands for re-use and
customization

16. Handlers
Perform any action on a consumer
Install / Update / Remove
Restart service
Reboot machine
Operates manually or on a schedule

17. Integration
REST API
Events published to AMQP topic exchange
HTTP callbacks
Email

18. Coordinator
Many actions can be asynchronous
Coordinator manages resource contention

19. Documentation
http://www.pulpproject.org/docs/

20. Questions?
Michael Hrivnak
mhrivnak@redhat.com
mhrivnak in #pulp
http://www.pulpproject.org