Re: [Pulp-dev] [breaking] Redeploy your Environment

Hi Fabricio, 1st, this seems unrelated to the change. Rather than doing that, I suggest you: 1. Make sure vagrant is up-to date. The Fedora 30 RPMs work well. The upstream RPM may or may not on work well Fedora 30, and require additional plugin updates / configuration work. My Fedora 30 vagrant*

Re: [Pulp-dev] [breaking] Redeploy your Environment

I don't know if I did something wrong, or it was related to this update, but I got this error: ➜ pulplift git:(master) vagrant up pulp3-source-fedora30 Bringing machine 'pulp3-source-fedora30' up with 'libvirt' provider... Name `pulplift_pulp3-source-fedora30` of domain about to create is already

[Pulp-dev] RPM plugin meeting notes

Pulp 2: - MONGO_X509 auth PR in - discussions w/ewoud about impacts on Katello installation - not pulp_rpm specific Pulp 3: - 3.0.0b7 released - Blockers status - Couple are waiting on 3541 https://pulp.plan.io/issues/3541 - If you have th

[Pulp-dev] [breaking] Redeploy your Environment

With 51395 pulpcore no longer has a hard-coded settings file, but the installer maintains this functionality by keeping it's settings at /etc/pulp/settings.py. This was part of https://pulp.plan.io/issues/5560 You'l

Re: [Pulp-dev] Merging pulpcore.plugin into pulp/pulpcore repo?

I agree that it makes sense to talk about it next week. I have a few concerns both in favor and against merging the repos that are not expressed on the issue. Let's remove it off the sprint for now. David On Thu, Oct 17, 2019 at 1:13 PM Brian Bouterse wrote: > Thank you for sharing your concer

Re: [Pulp-dev] Merging pulpcore.plugin into pulp/pulpcore repo?

Thank you for sharing your concerns. Let's think it over more. On Thu, Oct 17, 2019 at 12:39 PM Tatiana Tereshchenko wrote: > Do I understand correctly, that the suggestion is not to have versioned > api at all but document some conventions/expectations between pulpcore > releases and plugin AP

Re: [Pulp-dev] Merging pulpcore.plugin into pulp/pulpcore repo?

Do I understand correctly, that the suggestion is not to have versioned api at all but document some conventions/expectations between pulpcore releases and plugin API? I wonder if there is still a benefit to keep it as a separate package and as-is. I understand that now we need to release both at

Re: [Pulp-dev] Merging pulpcore.plugin into pulp/pulpcore repo?

Done. David On Thu, Oct 17, 2019 at 11:49 AM Brian Bouterse wrote: > Yes the issue is here: https://pulp.plan.io/issues/5580 > > If someone else can groom, I'm +1 to adding to sprint and labelling 3.0 > blocker. > > On Thu, Oct 17, 2019 at 11:01 AM David Davis > wrote: > >> Any chance we open

Re: [Pulp-dev] Merging pulpcore.plugin into pulp/pulpcore repo?

Yes the issue is here: https://pulp.plan.io/issues/5580 If someone else can groom, I'm +1 to adding to sprint and labelling 3.0 blocker. On Thu, Oct 17, 2019 at 11:01 AM David Davis wrote: > Any chance we open an issue and get this on the sprint so that we can > maybe release this change in RC8

Re: [Pulp-dev] Merging pulpcore.plugin into pulp/pulpcore repo?

Any chance we open an issue and get this on the sprint so that we can maybe release this change in RC8? David On Thu, Oct 17, 2019 at 10:49 AM Mike DePaulo wrote: > On Thu, Oct 17, 2019 at 10:25 AM Brian Bouterse > wrote: > >> I put some responses inline. I'm interested in what you think. >>

Re: [Pulp-dev] Merging pulpcore.plugin into pulp/pulpcore repo?

On Thu, Oct 17, 2019 at 10:25 AM Brian Bouterse wrote: > I put some responses inline. I'm interested in what you think. > > On Thu, Oct 17, 2019 at 10:10 AM Mike DePaulo > wrote: > >> Q: Will both pulpcore & pulpcore-plugin be published on PyPI as 1 >> package, or as 2? >> > I had imagined it wo

Re: [Pulp-dev] Merging pulpcore.plugin into pulp/pulpcore repo?

I put some responses inline. I'm interested in what you think. On Thu, Oct 17, 2019 at 10:10 AM Mike DePaulo wrote: > Q: Will both pulpcore & pulpcore-plugin be published on PyPI as 1 package, > or as 2? > I had imagined it would be 1. Users wouldn't be able to receive pulpcore.plugin except thr

Re: [Pulp-dev] Merging pulpcore.plugin into pulp/pulpcore repo?

Q: Will both pulpcore & pulpcore-plugin be published on PyPI as 1 package, or as 2? If so, how will you pip install from a pip VCS URL ? With #egg=pulpcore , and then #egg=pulpcore-plugin ? -Mike On Thu, Oct 17, 2019 at 5:17 AM Simon Baa

Re: [Pulp-dev] Merging pulpcore.plugin into pulp/pulpcore repo?

+1 On Wed, Oct 16, 2019 at 03:50:54PM -0400, Mike DePaulo wrote: >+1. > >On Wed, Oct 16, 2019 at 3:26 PM Pavel Picka <[1]ppi...@redhat.com> >wrote: > >+1 > >On Wed, Oct 16, 2019 at 9:23 PM Dana Walker <[2]dawal...@redhat.com> >wrote: > >+1, more straightforward > >

Re: [Pulp-dev] Merging pulpcore.plugin into pulp/pulpcore repo?

+1 from me. I never understood the dissection. It was never clear, why content serializers should be core, while the whole stages process should be api. On Wed, 16 Oct 2019 15:50:54 -0400 Mike DePaulo wrote: > +1. > > On Wed, Oct 16, 2019 at 3:26 PM Pavel Picka wrote: > > > +1 > > > > On Wed,