Re: [Pulp-list] Content Signing for Pulp 3.y -- Use Cases

[Dennis Kliban]

I've written 4 stories to start the implementation on the use cases we have
come up with so far. Do these accurately capture what was discussed?

[0] https://pulp.plan.io/issues/5943
[1] https://pulp.plan.io/issues/5944
[2] https://pulp.plan.io/issues/5945
[3] https://pulp.plan.io/issues/5946

On Mon, Dec 9, 2019 at 4:40 PM Dennis Kliban  wrote:

> I've updated the document[0] with the meeting minutes from December 5. The
> full chat logs are here[1]. I would like to host another meeting at 9:30 AM
> EST (in your time zone
> )
> on Tuesday, December 10, 2019 (tomorrow). During this meeting we will focus
> on the details of the following 2 use cases:
>
>
>-
>
>As an administrator, I can use django-admin to add/remove a Signing
>Service.
>-
>
>As a REST API user (repo admin), I can assign a Signing Service to a
>repository and provide a key signature as additional configuration.
>
>
>
> [0]
> https://docs.google.com/document/d/1HSrRduFYuidhbc8ISjUnkb3IXk6FnJ2iXEqa4vDC-pA/edit#
> [1]
> https://pulpadmin.fedorapeople.org/triage/pulp-meeting/2019/pulp-meeting.2019-12-05-14.00.log.html
>
>
> On Tue, Nov 26, 2019 at 4:44 PM Dennis Kliban  wrote:
>
>> Thank you everyone who participated in the discussion earlier today. I
>> have moved the content to a google doc[0]. You can find the summary of
>> today's discussion below the use cases. The full log of the discussion is
>> here[1].
>>
>> I would like to continue the discussion at 9 AM EST (in your time zone
>> )
>> on Thursday, December 5, 2019 in #pulp-meeting on IRC. Your
>>
>> [0]
>> https://docs.google.com/document/d/1HSrRduFYuidhbc8ISjUnkb3IXk6FnJ2iXEqa4vDC-pA/edit#
>> [1]
>> https://pulpadmin.fedorapeople.org/triage/pulp-dev/2019/pulp-dev.2019-11-26-14.30.log.html
>>
>> On Thu, Nov 21, 2019 at 8:27 AM Dennis Kliban  wrote:
>>
>>> On Thu, Nov 21, 2019 at 7:59 AM Dennis Kliban 
>>> wrote:
>>>
 I will be hosting a chat meeting to discuss use cases for signing in
 Pulp 3.y.
 The meeting details and agenda link are below. Both users and plugin
 developers are invited. Please join if you're interested!

 When: Wednesday, November 26 9:30 – 10:30am EST or in your time zone
 
 .

>>>
>>> Correction: this will take place on Tuesday. The link is correct.
>>>
>>>
 Where: #pulp-dev on freenode
 Agenda: https://etherpad.net/p/Pulp_-_Signing_Use_Cases

 Questions and feedback are also welcome ahead of time.

 Thanks!

>>>
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] pulp3 s3 migration path

[Brian Bouterse]

It's a bit manual, but a second pulp system could be setup with the new
type of storage and it could sync from the first system.

On Tue, Jan 7, 2020 at 2:46 PM David Davis  wrote:

> No, there is not. You cannot change your storage once you have set up and
> started to use pulp.
>
> I'm not sure what would be involved in migrating a Pulp system from one
> storage type to another but you can open a story in our tracker if you'd
> like.
>
> David
>
>
> On Tue, Jan 7, 2020 at 2:31 PM Bin Li (BLOOMBERG/ 120 PARK) <
> bli...@bloomberg.net> wrote:
>
>>
>> Is there a migration path to move from local file system to s3 after
>> creating repos, publications and distributions?
>>
>> Thanks
>> ___
>> Pulp-list mailing list
>> Pulp-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-list
>
> ___
> Pulp-list mailing list
> Pulp-list@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] pulp3 s3 migration path

[David Davis]

No, there is not. You cannot change your storage once you have set up and
started to use pulp.

I'm not sure what would be involved in migrating a Pulp system from one
storage type to another but you can open a story in our tracker if you'd
like.

David


On Tue, Jan 7, 2020 at 2:31 PM Bin Li (BLOOMBERG/ 120 PARK) <
bli...@bloomberg.net> wrote:

>
> Is there a migration path to move from local file system to s3 after
> creating repos, publications and distributions?
>
> Thanks
> ___
> Pulp-list mailing list
> Pulp-list@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] relative-url issue

[Gravel Bone]

I created a repo:

sudo pulp-admin rpm repo create \

--repo-id=live-rhel6-opt \

--display-name="BLAH" \

--description="BLAH BLAH" \

--repoview=true \

--serve-http=true \

--feed=
https://cdn.redhat.com/content/dist/rhel/server/6/6Server/x86_64/optional/os
 \

--validate=true \

--relative-url=rhel6/opt \

--checksum-type=sha1 \

--remove-missing=true \

--gpg-key=/etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release \

--feed-ca-cert=/etc/rhsm/ca/redhat-uep.pem \

--feed-key=REDACTED \

--feed-cert=REDACTED

In a browser I can go to http://server/pulp/repos/rhel6/ks, however all
presented links (Packages, repoview, etc.) omit the ks and render as
http://server/pulp/repos/rhel6/Packages/ which of course don't work.

I've searched around and seen similar issues but no solutions or not quite
the same issue.   I'm sure I'm missing something either in my http
configuration or somewhere else.   Any pointers would be appreciated.


Gravelbone
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] pulp3 s3 migration path

[Bin Li (BLOOMBERG/ 120 PARK)]

Is there a migration path to move from local file system to s3 after creating 
repos, publications and distributions?

Thanks___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] pulp3 remote ca_cert

[Bin Li (BLOOMBERG/ 120 PARK)]

Happy new year.

I want to compare the cert configured in pulp with our current valid 
entitlement cert. If they are different, the cert in pulp will be updated. The 
question is if it is possible to compare since they always look different?

When I list a remote, the certs are showed like below{
"ca_cert": 
"b8bd944ff40f1756c08743800453b724f133029725dc762ed9ce6504a828a5ec", 
"client_cert": 
"d24baa45b4b554e782dd134e6c5f1eb1f88e1d88122d3d417b05f7f8153954a1", 
"client_key": 
"55ece66e807b5c979f425e55f90958b8fbc769320a0bdb5f4c3563464e8c9530", 
...
}

This is different than the cert when I created the remote:
('-BEGIN CERTIFICATE-\n'
 'MIIG/TCCBOWgAwIBAgIBNzANBgkqhkiG9w0BAQUFADCBsTELMAkGA1UEBhMCVVMx\n'
 'FzAVBgNVBAgMDk5vcnRoIENhcm9saW5hMRYwFAYDVQQKDA1SZWQgSGF0LCBJbmMu\n'
 'MRgwFgYDVQQLDA9SZWQgSGF0IE5ldHdvcmsxMTAvBgNVBAMMKFJlZCBIYXQgRW50\n'
 'aXRsZW1lbnQgT3BlcmF0aW9ucyBBdXRob3JpdHkxJDAiBgkqhkiG9w0BCQEWFWNh\n'
 'LXN1cHBvcnRAcmVkaGF0LmNvbTAeFw0xMDEwMDQxMzI3NDhaFw0zMDA5MjkxMzI3\n'
 'NDhaMIGuMQswCQYDV...


___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list