Re: [Pulp-dev] Pulp 3 in One Container

[Dennis Kliban]

I've moved the git repository to the pulp org[0]. I've also pushed the
image to the pulp org on docker hub[1]. I also updated the blog post with
the new locations. I also changed the commands slightly to make them more
user friendly. The launched container now has the name 'pulp' so the final
command for changing the password no longer uses a checksum to refer to the
container.


[0] https://github.com/pulp/pulp-fedora31
[1] https://hub.docker.com/repository/docker/pulp/pulp-fedora31
[2] https://pulpproject.org/2020/03/15/pulp-fedora31-single-container/

On Thu, Apr 16, 2020 at 2:02 PM David Davis  wrote:

> +1 from me. @mcorr, thank you for raising this.
>
> David
>
>
> On Thu, Apr 16, 2020 at 1:46 PM Dennis Kliban  wrote:
>
>> That sounds like a great idea. I'll move the git repository under 'pulp'
>> organization on GitHub and the same for Docker Hub image repository. I'll
>> update this thread when this has been done.
>>
>> On Thu, Apr 16, 2020 at 10:26 AM Melanie Corr  wrote:
>>
>>> Hi all,
>>>
>>> I was reading Dennis Kilban's blog post [1] that talks about using Pulp
>>> 3 in a container. Although this is not production-ready as of yet, it is a
>>> valuable tool for users.
>>>
>>> I would like to take the content of Dennis's blog and create a 'Try Pulp
>>> 3 in a Container' page so that it is easy for new users to find, with the
>>> caveat that this is not production ready.
>>>
>>> One thing that I think could improve is the location of the container.
>>> Currently it is located in Dennis's GitHub space. It would be better, if we
>>> were to store it somewhere within the main Pulp project space.
>>>
>>> Do you think that would be possible?
>>>
>>> Thanks,
>>>
>>> Melanie
>>>
>>> [1]
>>> https://pulpproject.org/2020/03/15/pulp-fedora31-single-container/
>>>
>>> --
>>>
>>> Melanie Corr, RHCE
>>>
>>> Community Manager
>>>
>>> Red Hat 
>>>
>>> Remote, Ireland
>>>
>>> mc...@redhat.com
>>> M: +353857774436 IM: mcorr
>>> 
>>>
>>> ___
>>> Pulp-dev mailing list
>>> Pulp-dev@redhat.com
>>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>>
>> ___
>> Pulp-dev mailing list
>> Pulp-dev@redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] Pulp 3 in One Container

[David Davis]

+1 from me. @mcorr, thank you for raising this.

David


On Thu, Apr 16, 2020 at 1:46 PM Dennis Kliban  wrote:

> That sounds like a great idea. I'll move the git repository under 'pulp'
> organization on GitHub and the same for Docker Hub image repository. I'll
> update this thread when this has been done.
>
> On Thu, Apr 16, 2020 at 10:26 AM Melanie Corr  wrote:
>
>> Hi all,
>>
>> I was reading Dennis Kilban's blog post [1] that talks about using Pulp 3
>> in a container. Although this is not production-ready as of yet, it is a
>> valuable tool for users.
>>
>> I would like to take the content of Dennis's blog and create a 'Try Pulp
>> 3 in a Container' page so that it is easy for new users to find, with the
>> caveat that this is not production ready.
>>
>> One thing that I think could improve is the location of the container.
>> Currently it is located in Dennis's GitHub space. It would be better, if we
>> were to store it somewhere within the main Pulp project space.
>>
>> Do you think that would be possible?
>>
>> Thanks,
>>
>> Melanie
>>
>> [1]
>> https://pulpproject.org/2020/03/15/pulp-fedora31-single-container/
>>
>> --
>>
>> Melanie Corr, RHCE
>>
>> Community Manager
>>
>> Red Hat 
>>
>> Remote, Ireland
>>
>> mc...@redhat.com
>> M: +353857774436 IM: mcorr
>> 
>>
>> ___
>> Pulp-dev mailing list
>> Pulp-dev@redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>
> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] Pulp 3 in One Container

[Dennis Kliban]

That sounds like a great idea. I'll move the git repository under 'pulp'
organization on GitHub and the same for Docker Hub image repository. I'll
update this thread when this has been done.

On Thu, Apr 16, 2020 at 10:26 AM Melanie Corr  wrote:

> Hi all,
>
> I was reading Dennis Kilban's blog post [1] that talks about using Pulp 3
> in a container. Although this is not production-ready as of yet, it is a
> valuable tool for users.
>
> I would like to take the content of Dennis's blog and create a 'Try Pulp 3
> in a Container' page so that it is easy for new users to find, with the
> caveat that this is not production ready.
>
> One thing that I think could improve is the location of the container.
> Currently it is located in Dennis's GitHub space. It would be better, if we
> were to store it somewhere within the main Pulp project space.
>
> Do you think that would be possible?
>
> Thanks,
>
> Melanie
>
> [1]
> https://pulpproject.org/2020/03/15/pulp-fedora31-single-container/
>
> --
>
> Melanie Corr, RHCE
>
> Community Manager
>
> Red Hat 
>
> Remote, Ireland
>
> mc...@redhat.com
> M: +353857774436 IM: mcorr
> 
>
> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] Pulp 3 in One Container

[Mike DePaulo]

On Thu, Apr 16, 2020 at 10:26 AM Melanie Corr  wrote:

> Hi all,
>
> I was reading Dennis Kilban's blog post [1] that talks about using Pulp 3
> in a container. Although this is not production-ready as of yet, it is a
> valuable tool for users.
>
> I would like to take the content of Dennis's blog and create a 'Try Pulp 3
> in a Container' page so that it is easy for new users to find, with the
> caveat that this is not production ready.
>
> One thing that I think could improve is the location of the container.
> Currently it is located in Dennis's GitHub space. It would be better, if we
> were to store it somewhere within the main Pulp project space.
>
> Do you think that would be possible?
>
> Thanks,
>
> Melanie
>
> [1]
> https://pulpproject.org/2020/03/15/pulp-fedora31-single-container/
>
> --
>
> Melanie Corr, RHCE
>
> Community Manager
>
> Red Hat 
>
> Remote, Ireland
>
> mc...@redhat.com
> M: +353857774436 IM: mcorr
> 
>
> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>

Hi Melanie,

Creating a new page is a good idea, but I think we need to do some other
documentation/overviews first, to avoid confusion around our multiple
containers approaches (single container vs pulp-operator.) Also to decide
on which easy approach to promote as the best way to *try* pulp.

I agree with you on moving the repo, but note that a rename is planned, so
they should probably be done at the same time.


*Background*:

We started work on pulp-operator (a Kubernetes operator) as a sophisticated
set of containers for running Pulp months ago. Once production ready, it
will be easy to run for users *if* they already have a full Kubernetes
container infrastructure; operators are supposed to provide an app-store
like experience where the # of containers is abstracted away.

Later on, we discovered that we could provide a quick & easy way for users
to try Pulp 3 by writing an install script around pulp-operator and K3s
(lightweight kubernetes.) It's almost like an alternate mode of
pulp-operator. It is called "pulp-insta-demo.sh", and it is listed on our
home page as "Quickly Try Pulp": https://pulpproject.org/ . All users have
to do is run it on a standard Linux desktop. laptop or server, without any
options or config, and it usually works.

Because many users need to use a single host to run a single container,
with directories for storage, etc, we later started work on the single
container.

I've been meaning to write a post about pulp-operator, introducing it, but
didn't have time.

Then Dennis and I intended to add a comparison to pulp-operator in his
post, but it fell through the cracks in this hectic (global crisis) month.

I did however write a related-tooling page afterwards, that minimally
introduces pulp-operator, and compares pulp-operator to the single
container:
https://pulpproject.org/related-tooling/
https://github.com/pulp/pulpproject.org/pull/253 (PR I just submitted to
add pulp-insta-demo.sh)


*What I propose we do*:

I think we should write a post introducing pulp-operator, including
pulp-insta-demo.sh .

Then write another post comparing the 2 container solutions
(pulp-operator/pulp-insta-demo vs the single container) in greater detail
than the "related tooling" page does.
Perhaps it should be a page (rather than blog post) comparing
pulp_installer as well. An overview of all the ways to install Pulp 3.
(To make matters more complicated, we also have manual install
instructions, which is a manual way of deploying Pulp how pulp_installer
does.)

Then we should decide which approach (single container vs pulp-insta-demo
mod of pulp-operator) to list as the recommended way to try Pulp 3. (Again,
currently the home page has pulp-insta-demo.)

Then we should write a page about the easiest way to try Pulp 3.


Again, these are only my thoughts, and what I've been planning to do. I am
very glad you joined our team; because having multiple installers/packages
is a situation that I really feel we need community manager guidance on.

-Mike

-- 

Mike DePaulo

He / Him / His

Service Reliability Engineer, Pulp

Red Hat 

IM: mikedep333

GPG: 51745404

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

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   Query for the upcoming release
   -

  https://pulp.plan.io/projects/pulp_rpm/issues?query_id=149
  -

 Copy API docs
 -

Maybe we can publish them after the release? +1
-

 PR reviews
 -

   “Relative_path” problem
   -

  https://www.redhat.com/archives/pulp-dev/2020-April/msg0.html
  -

  Need to come back to it and bump the thread
  -

  Will be discussed at the pulpcore meeting
  -

   Import/export
   -

  Main path works, tech-preview in 3.3
  -

 pulp_file/pulp_rpm happy-path available
 -

  Docs in progress
  -

  Setting up handoff mtg w/katello next week
  -

 Public invite to list
 -

 Dennis volunteered to manage accepts
 -

 Invite QE folks
 -

   Katello timeline and deliverables
   -

  Ask if anything is unclear
  -

   3.3.0 release
   -

  Monday or Tuesday
  -

  Daniel to take care of the release
  -

   Testing publish task
   -

  Easy to test using the REST API:
  
https://github.com/pulp/pulp_rpm/blob/master/pulp_rpm/tests/functional/api/test_publish.py#L347
  -

  Problem: how to test publish task directly? How to emulate a synced
  repo? (Unit and Functional tests run on different places on CI)
  - Brian to write a proposal to solve this type of testing problems


Pulp 2:

   -

   Both items from last week needs to be taken care of
   -

  for the RPM migration to Pulp 3
  -

 https://pulp.plan.io/issues/6354
 -

 https://pulp.plan.io/issues/6355
 -

  CentOS directory KS structure is no longer RH compatible
  -

 https://pulp.plan.io/issues/6470
 -

 the same problem in Pulp3
 - Dennis to test more and file an issue if needed


Open PRs:

   -

   https://github.com/pulp/pulp_rpm/pulls


Triage:

   -

   Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30


Tests:

   - Pulp 3 https://pulp.plan.io/projects/pulp_rpm/issues?query_id=153
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Pulp 3 in One Container

[Melanie Corr]

Hi all,

I was reading Dennis Kilban's blog post [1] that talks about using Pulp 3
in a container. Although this is not production-ready as of yet, it is a
valuable tool for users.

I would like to take the content of Dennis's blog and create a 'Try Pulp 3
in a Container' page so that it is easy for new users to find, with the
caveat that this is not production ready.

One thing that I think could improve is the location of the container.
Currently it is located in Dennis's GitHub space. It would be better, if we
were to store it somewhere within the main Pulp project space.

Do you think that would be possible?

Thanks,

Melanie

[1]
https://pulpproject.org/2020/03/15/pulp-fedora31-single-container/

-- 

Melanie Corr, RHCE

Community Manager

Red Hat 

Remote, Ireland

mc...@redhat.com
M: +353857774436 IM: mcorr

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