Interest in a multi-site Pulp3 manager application?

Development
#1

Hi there,

My company has developed an in-house application for managing multiple Pulp instances from a central manager application. We’re trying to gauge interest in releasing it as an open source project – perhaps even as a new repository under the pulp org? Here’s what it does:

  1. Encourages good security practice of allowing only the primary instance to access upstream public repos, while the secondaries are synced only from the primary. Consumers only use the secondaries. A banned packages list is applied to all participating servers
  2. Schedules repository tasks (sync, etc) among the primary and secondaries, with fine grained timing (fast updates for rapidly changing packages, more occasional elsewhere).
  3. Multi-stage sync jobs
  4. Central reporting of task and server state for all members.

The roadmap / wishlist has some interesting ideas:

  1. UI (currently API-only)
  2. Improved logging (eg, see exact failure messages from Pulp3 instances so you don’t have to look at logs of specific hosts)
  3. Improved stability on large sync tasks (continue on failure, etc)
  4. Grafana dashboard integration

Let me know if this sounds useful – or if you’ve found another solution for this problem!

Thanks,
Geoff Wilson
G-Research Open Source Software

3 Likes
Multi-site pulp3 implementation
#2

Definitely interested

I have a similar architecture

  • I use ansible to manage it all
  • i have more classifications of servers (certain ones get certain repos)
  • syncs happen each time a new asset is added or manually in certain cases
1 Like
#3

This definitely sounds interesting! One question I have is, how does this compare to Katello’s “Smart Proxy” featureset? Have y’all looked at that at all?

Katello is way more than just content-curation, of course - so it might just be overkill for you.

#4

Very interested as well. In my opinion, this is something that should be included as part of multisite support. We’re currently implementing it ourselves—like others in the community—using Ansible, but it would be great if the idea were officially adopted.