[Pulp-dev] Signing Service Meeting Schedule on #pulp-meeting

Tue Jun 16 14:51:35 UTC 2020

Hi Brian,

I have been thinking some more about the Signing Service, since the meeting, but I am afraid my thinking gets very muddled/blocked when it comes to the idea of a pulp instance "without shared storage".
I think my problem is that I am missing some relevant background knowledge in basic pulp architecture.
I am in need of some knowledge transfer here (even if it is just a pointer to some relevant documentation, I don't want to take up to much of your time for it).

So my current vague understanding of pulp architecture and components, goes something like as follows:

Pulp components/services:

* A postgres database (or some other functionally equivalent DB? I don't really care about the details... :wink:)
* The REST API (which I think is running as some separate technical service in some way shape or form?)
* A webserver to serve "distributed" content to clients (is that right?).
* Exactly one "resource manager" service to coordinate the workers.
* One or more workers, that actually execute tasks.
* Anything else I forgot?

If all of these components are running on the same host, then trivially they have some "shared storage" at "/var/lib/pulp".
However, I have no clear idea of what is actually stored at "/var/lib/pulp", and I also have no clear idea of what components/services would commonly be installed on separate hosts (I imagine the DB, webserver, and workers would be obvious candidates?).
Finally, I have no clear idea of how components/services communicate with each other (specifically what communication isn't network based, and thereby problematic if components are on separate hosts)?

One final point I am hung up on: My understanding of the term "Artifact" is vague. Is it one artifact corresponds to exactly one file? Is the entire file stored in the DB or is the file itself stored under "/var/lib/pulp/" like with Pulp 2? How exactly does the webserver access and serve files to clients?

I feel like if you could clear some of these points up for me (either directly, or by pointing me in the right direction), I could better contribute to design discussions in the future.

thanks,
Quirin

________________________________
From: Brian Bouterse <bmbouter at redhat.com>
Sent: 10 June 2020 21:03:45
To: Quirin Pamp <pamp at atix.de>
Cc: Pulp-dev <pulp-dev at redhat.com>
Subject: Re: [Pulp-dev] Signing Service Meeting Schedule on #pulp-meeting

We met today, see the video and meeting notes links below. Here's what we determined (there is more reasoning in the document), please send feedback:

* We do see value in adding a public key to the SigningService (base model).
* Having the SigningService be immutable would be good. This causes changes in model changes to require Content Administrators to update their repositories to use the newly created object and update their clients if necessary making this process explicit instead of implicit.
* We want to ship a generic version of the script to make it easier to use
* To make the script generic for gpg use at least, the key_id also should be passed it, this would also be a new field added to SigingService (base_model)

Here are some concerns we don't yet know how to address:
* How would the signing service work if /var/lib/pulp is not providing shared storage?
* Should the checksum also be added to the model?

Please share ideas, feedback, and concerns.

[0]: https://hackmd.io/k5xm4WZ7QpeX0HF80XS9OQ
[1]: https://youtu.be/uecwUFJTWno

On Wed, Jun 10, 2020 at 11:06 AM Brian Bouterse <bmbouter at redhat.com<mailto:bmbouter at redhat.com>> wrote:
Here's the link where we're meeting:  https://meet.google.com/rpw-agrj-gyd

On Tue, Jun 2, 2020 at 2:35 PM Brian Bouterse <bmbouter at redhat.com<mailto:bmbouter at redhat.com>> wrote:
Sounds good. @pamp if it's possible for you to invite @Manisha15 that would be great too.

On Tue, Jun 2, 2020 at 11:18 AM Quirin Pamp <pamp at atix.de<mailto:pamp at atix.de>> wrote:

Wednesday June 10th 11:00 EDT. If I am not mistaken that is 17:00 CET, which works for me.

________________________________
From: pulp-dev-bounces at redhat.com<mailto:pulp-dev-bounces at redhat.com> <pulp-dev-bounces at redhat.com<mailto:pulp-dev-bounces at redhat.com>> on behalf of Brian Bouterse <bmbouter at redhat.com<mailto:bmbouter at redhat.com>>
Sent: 01 June 2020 17:42:17
To: Pulp-dev <pulp-dev at redhat.com<mailto:pulp-dev at redhat.com>>
Subject: Re: [Pulp-dev] Signing Service Meeting Schedule on #pulp-meeting

New time based on feedback:  Wednesday June 10th, 11AM EDT.

On Fri, May 29, 2020 at 4:45 PM Brian Bouterse <bmbouter at redhat.com<mailto:bmbouter at redhat.com>> wrote:
I'd like to organize a discussion around the following topics on #pulp-meeting. It affects several folks so we should get together.

Here's the open agenda (feel free to add to it):  https://hackmd.io/k5xm4WZ7QpeX0HF80XS9OQ

I'm tentatively setting the time for June 11 @ 10am EDT. Please let me know if you want to join but cannot due to a time conflict.

Thanks!
Brian

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20200616/afbdaadc/attachment.htm>