@ekohl, @ehelms, @Justin_Sherrill, and I had a meeting today to discuss how to move forward with the Container Gateway. Here are the notes from the meeting:
Container Gateway meeting notes
Main concerns discussed:
-
It is not fully agreed-upon that the Smart Proxy should have clients interacting with it directly.
-
The Smart Proxy Container Gateway deviates from the idea that the Smart Proxy is a control surface for making changes, not for interacting with services. If the Smart Proxy goes down, container content cannot be consumed.
-
The PostgreSQL database adds extra complexity that is not necessary while the smart proxy is still single-threaded.
Main counter-arguments:
-
Without the Container Gateway, users would have to forgo upgrading their Smart Proxies when they upgrade to Katello 4.0. Delaying the release of the Container Gateway would cause continuity issues for the Katello 4.0 upgrade as such.
-
The database can be easily changed to SQLite to alleviate PostgreSQL concerns.
Resolution:
- The Container Gateway Smart Proxy plugin will be used with the changes below for Katello 4.0. It will support pulling unauthenticated repositories only for now. This is okay for Katello 4.0 since we are on a tight timeline, but the concerns should be resolved by Katello 4.1. Addressing these concerns will involve investigating whether or not pulp-container can handle the needs of the Container Gateway itself.
Immediately-required changes:
- Change database to SQLite