Plugins » Katello

h1. PulpV3GapAnalysis

h1.  Content Tab

h2.  Content -> Red Hat Repositories

Katello knows the content URLs from candlepin, matches on the CDN, presents them to the user, the user selects them

* Katello creates a Repo tracking this in Pulp with client certificates and CA certificate

* Katello specifies custom options from the 'Custom Repo Creation Page' but these use cases are covered in that section

Katello deletes a Repository

h2.  Content -> Products

h3.  Content -> Products -> New Product (used for things like CentOS, SLES, etc)

All data here is stored only in Katello since this is a Product not a Repository and Pulp doesn't have a concept of a Product

Sync Plans will *not* be handled inside of Pulp

h3.  Content -> Products -> {product_name} -> Repositories

The user selects a type and content-specific fields are shown.

h4. Debian:

h5. Sync Options

* Upstream URL (str)

* Releases (csv list)

* Components (csv list)

* Architectures (csv list)

* Verify SSL (boolean)

* Upstream username (str)

* Upstream password (str)

* Ignore Global http Proxy (bool)

h5. Publish Options

* Publish via HTTP (bool)       <----------------------------- PROBLEM AREA

h4. Docker

* Sync Options

* Ustream URL (str)

* Upstream Repository Name (str)

* Verify SSL (bool)

* Upstream username (str)

* Upstream password (str)

* Ignore Global http Proxy (bool)

h4. File

h5. Sync Options

* Upstream URL (str)

* Verify SSL (boolean)

* Upstream username (str)

* Upstream password (str)

* Ignore Global http Proxy (bool)

h5. Publish Options

* Publish via HTTP (bool)       <----------------------------- PROBLEM AREA

h4. OSTree

h5. Sync Options

* Upstream URL (str)

* Upstream Sync Policy (choice):  Latest Only, All History, Custom Depth (with a number specified)    <--- in Pulp2 also specified on distributor

* Verify SSL (boolean)

* Upstream username (str)

* Upstream password (str)

* Ignore Global http Proxy (bool)

h4. Puppet

h5. Sync Options

* Upstream URL (str)

* Verify SSL (boolean)

* Upstream username (str)

* Upstream password (str)

* Mirror on Sync (boolean)

* Ignore Global http Proxy (bool)

h5. Publish Options

* Publish via HTTP (bool)       <----------------------------- PROBLEM AREA

h4. Yum

h5. General Fields   <------ not used by Pulp

* Restrict to Architecture (choice)

* GPG Key (str)  

h5. Sync Settings

* Upstream URL (str)

* Ignorable Content (multiselect): RPM, DRPM, SRPM, Errata, Distribution

* Verify SSL (boolean)

* Upstream username (str)

* Upstream password (str)

* Download Policy (choice): (On Demand, Background, Immediate)   <---- Background does not have a strong use case

* Mirror on Sync (bool)

* Ignore Global http Proxy (bool)

* SSL CA Cert (str)

* SSL Client Cert (str)

* SSL Client Key(str)

h5. Publish Settings

* Checksum: (choice) Default, sha256, sha1   <----- for all repodata including primary.xml

h2.  Content -> Content Credentials

h2.  Content -> Sync Plans

h2.  Content -> Sync Status

h2.  Content -> Lifecycle

h2.  Content -> Lifecycle Environments

h2.  Content -> Content Views

h2.  Content -> Activation Keys

h2.  Content -> Content Types

h2.  Content -> Deb Packages

h2.  Content -> Container Image Tags

h2.  Content -> Errata

h2.  Content -> Files

h2.  Content -> OSTree Branches

h2.  Content -> Packages

h2.  Content -> Puppet Modules

h1.  Hosts -> Content Hosts

h1.  Non UI things

* the API endpoint that clients upload their enabled repos

* the API endpoint that clients upload their package profiles

* the API endpoint that clients register

* the API endpoint that clients unregister

* speed throttling and other global settings?

h1.  Terminology

Candlepin Manifest - Defines Products, Subscriptions, and a Content Sets

Product - A collection of repositories. A repository can only belong to one product

Repository Set - Has a name, Label, and URL of the form:  /content/rhel/server/7/$RELVER/$BASEARCH/os/