[Pulp-dev] plugin_template changes

What's new? - bootstrap.py is now called plugin-template - Plugins now use a template_config.yml to store all the options that they want to use when interacting with plugin-template commands What's gone? - the command line arguments that told bootstrap.py what options to use Find out

Re: [Pulp-dev] Database support in Pulp 3

+1 to drop support for mariadb On Mon, Jul 15, 2019 at 10:04 AM Austin Macdonald wrote: > +1 to remove. > > On Sun, Jul 14, 2019 at 4:10 PM Brian Bouterse > wrote: > >> I believe we have reached a point where Pulp (core and its plugins) can >> no longer support MariaDB due to technical problems

Re: [Pulp-dev] filtering tasks by reserved resources

orical > model. > > > David > > > On Thu, Jul 11, 2019 at 4:46 PM Dennis Kliban wrote: > >> On Thu, Jul 11, 2019 at 4:21 PM David Davis >> wrote: >> >>> ReservedResources are unique[0] and the tasking code relies on this >>> uniquen

Re: [Pulp-dev] filtering tasks by reserved resources

> https://github.com/pulp/pulpcore/blob/master/pulpcore/app/models/task.py#L35 > [1] > https://github.com/pulp/pulpcore/blob/ae6be0d89c5df26ac1cfdc876f3b131aa6e9bcf8/pulpcore/app/models/task.py#L229-L246 > > David > > > On Thu, Jul 11, 2019 at 4:04 PM Dennis Kliban wrote: >

[Pulp-dev] filtering tasks by reserved resources

I just wrote up a story to add an ability to filter Tasks by the resources that they reserved. This is needed for the migration plan tasks and will be just as useful for other tasks. The design requires storing ReservedResources permanently in the database. The status of the task associated with t

Re: [Pulp-dev] pulp 2 + pulp 3 dev environment problem

rt for > httpd? I think the latter makes sense. > > David > > > On Tue, Jul 9, 2019 at 9:06 PM Dennis Kliban wrote: > >> Our ansible role[0] for deploying Pulp 2 deploys httpd and has it bind to >> ports 80 and 443. The ansible-pulp roles[1] deploy nginx and have it

[Pulp-dev] pulp 2 + pulp 3 dev environment problem

Our ansible role[0] for deploying Pulp 2 deploys httpd and has it bind to ports 80 and 443. The ansible-pulp roles[1] deploy nginx and have it bind to port 80 also. When Pulp 2 is already installed, nginx fails to start. We need to add support to ansible-pulp for deploying Pulp 3 with httpd instea

Re: [Pulp-dev] pulp 3 bindings change proposal

On Thu, Jun 20, 2019 at 9:53 AM Justin Sherrill wrote: > > On 6/20/19 8:02 AM, Dennis Kliban wrote: > > On Wed, Jun 19, 2019 at 1:57 PM Dennis Kliban wrote: > >> On Wed, Jun 19, 2019 at 11:34 AM Dennis Kliban >> wrote: >> >>> On Wed, Jun 19, 2

Re: [Pulp-dev] pulp 3 bindings change proposal

On Wed, Jun 19, 2019 at 1:57 PM Dennis Kliban wrote: > On Wed, Jun 19, 2019 at 11:34 AM Dennis Kliban wrote: > >> On Wed, Jun 19, 2019 at 11:20 AM Justin Sherrill >> wrote: >> >>> If a plugin provided multiple remotes, for example, what would that look

Re: [Pulp-dev] [Pulp-list] Pulp 2 to 3 Migration meeting on Wednesday June 19th

On Wed, Jun 19, 2019 at 2:10 PM Eric Helms wrote: > Thanks for these updates. > > On Wed, Jun 19, 2019, 1:59 PM Tatiana Tereshchenko > wrote: > >> The logs from the meeting can be viewed here[0]. >> >> We covered: >> - hard links approach for "migrating" files, good or bad; alternatives >>

Re: [Pulp-dev] pulp 3 bindings change proposal

On Wed, Jun 19, 2019 at 11:34 AM Dennis Kliban wrote: > On Wed, Jun 19, 2019 at 11:20 AM Justin Sherrill > wrote: > >> If a plugin provided multiple remotes, for example, what would that look >> like? >> >> in your example: >> >> -file_remote = fil

Re: [Pulp-dev] pulp 3 bindings change proposal

ancy_remote = filefancyremote.create(fancy_remote_data) My current implementation does not support this, but I am working toward the above solution. > > Justin > > On 6/19/19 9:45 AM, Dennis Kliban wrote: > > I didn't get a note in my email, but I did see one on in the l

Re: [Pulp-dev] pulp 3 bindings change proposal

n't produce problems when generating client code. Does this address your concerns? [0] https://www.redhat.com/archives/pulp-dev/2019-June/msg00061.html On Wed, Jun 19, 2019 at 8:54 AM Dennis Kliban wrote: > As pointed out in a recent issue[0], the method names in the bindings > gene

[Pulp-dev] pulp 3 bindings change proposal

As pointed out in a recent issue[0], the method names in the bindings generated from Pulp's OpenAPI schema are unnecessarily verbose. Each method name corresponds to an Operation Id in the OpenAPI schema. The Operation Id is also used as an HTML anchor in the REST API docs[1]. It is possible to ge

[Pulp-dev] Pulp 2 to 3 Migration meeting on Friday June 7th

An IRC meeting will be held on Monday June 3rd at 11am Eastern[0]. The meeting will take place in #pulp-2to3-sig on Freenode IRC network. We will be discussing the schema for the Migration Plan described here[1]. Please put any questions or ideas into that etherpad before the meeting. [0] https:/

Re: [Pulp-dev] Pulp 2 to 3 Migration meeting on Monday June 3rd

/pulp-2to3-migration [2] https://pulp.plan.io/issues/3821 On Thu, May 30, 2019 at 3:20 PM Dennis Kliban wrote: > An IRC meeting will be held on Monday June 3rd at 11am Eastern[0]. The > meeting will take place in #pulp-2to3-sig on Freenode IRC network. We will > be discussing the schem

[Pulp-dev] Pulp 2 to 3 Migration meeting on Monday June 3rd

An IRC meeting will be held on Monday June 3rd at 11am Eastern[0]. The meeting will take place in #pulp-2to3-sig on Freenode IRC network. We will be discussing the schema for the Migration Plan described here[1]. Please put any questions or ideas into that etherpad before the meeting. [0] https:/

Re: [Pulp-dev] Release Note Process Improvements

+1 I updated the task[0] slightly and marked it as groomed. [0] https://pulp.plan.io/issues/4875 On Tue, May 28, 2019 at 12:14 PM Austin Macdonald wrote: > The proposed changes look awesome! I'm +1 for moving forward with it for > pulpcore and pulpcore-plugin. > > If there is consensus (looks

Re: [Pulp-dev] breaking change: accept Null instead of empty string

om >>> <https://www.redhat.com> >>> >>> >>> >>> On Tue, May 21, 2019 at 2:47 PM Tatiana Tereshchenko < >>> ttere...@redhat.com> wrote: >>> >>>> +1 and +1 to allow only null and not both. >>>> >>>&g

[Pulp-dev] breaking change: accept Null instead of empty string

Pulp 3's REST API does not accept Null as a value for a string field. The only way for a user to unset a string field is to pass in an empty string. This makes it awkward to integrate Pulp with other systems that use Null to represent unset fields. We discovered this usability problem when investig

Re: [Pulp-dev] 2.19.1 Dev Freeze, Wednesday, May, 15, at 23:59 UTC

On Fri, May 3, 2019 at 3:35 PM Dennis Kliban wrote: > A 2.19.1 is planned to released soon with some recent bug fixes[0]. > > GA is currently planned for May 29th. The release schedule can be found on > the wiki[1]. > > [0] https://pulp.plan.io/versions/68 > [1] https://

Re: [Pulp-dev] ergonomics of providing Pulp with lists of items

Justin said it all very well. On Tue, May 7, 2019 at 8:55 AM Brian Bouterse wrote: > I was initially in favor of adopting the comma separated change, but > reading @jsherril's response (which I agree with) I think straightened my > thinking out. I think we should continue the escaping as is. We

[Pulp-dev] 2.19.1 Dev Freeze, Wednesday, May, 15, at 23:59 UTC

A 2.19.1 is planned to released soon with some recent bug fixes[0]. GA is currently planned for May 29th. The release schedule can be found on the wiki[1]. [0] https://pulp.plan.io/versions/68 [1] https://pulp.plan.io/projects/pulp/wiki/2191_Release_Schedule __

Re: [Pulp-dev] problems with publishers in Pulp 3

+1 ... Want to write up a story? On Mon, Apr 29, 2019 at 2:45 PM Simon Baatz wrote: > On Fri, Apr 12, 2019 at 04:51:00PM -0400, Brian Bouterse wrote: > >After some discussion the proposal has been adjusted to leave > >publishers as-is and only introduce Master/Detail Publications with >

Re: [Pulp-dev] Pulp2 Bug Backlog Closing?

gt;> >>> >>> Regards, >>> >>> Ina Panova >>> Software Engineer| Pulp| Red Hat Inc. >>> >>> "Do not go where the path may lead, >>> go instead where there is no path and leave a trail." >>> >>&

Re: [Pulp-dev] problems with publishers in Pulp 3

s area originally? > > I believe these are changes we should explore. The top one is a pretty > simple add on and mostly not a breaking change. The bottom one would be a > larger change, but one that I believe we could make and should seriously > consider pre 3.0 GA. > > >

Re: [Pulp-dev] Pulp2 Bug Backlog Closing?

t;> >>>>>>> I think it would be great if we can copy over the correct issues >>>>>>> over to GitHub issues and close the rest of others. >>>>>>> >>>>>>> For issues linked to an external bug tracker -David Davis o

[Pulp-dev] CI requirements

I wrote up a short task[0] about our Testing infrastructure needs. I was only able to name one additional requirement on top of what Travis already provides. What else do we need from our CI infrastructure? [0] https://pulp.plan.io/issues/4652 - Dennis

[Pulp-dev] problems with publishers in Pulp 3

TLDR: Auto-distribution of publications is performed implicitly instead of explicitly. Plugins that don't generate metadata during publish have to provide a generic publisher. Users have to keep track of publishers to make sure auto-distribution of new publications works. More background: Publis

Re: [Pulp-dev] [Pulp-list] Pulp 3.0 RC release

The latest pulpcore REST API documentation can be found here[0]. Similar documentation + more is available with every install of pulpcore and the plugins[1]. [0] https://docs.pulpproject.org/en/3.0/nightly/restapi.html [1] https://pulpproject.org/pulp-3-plugins/ On Thu, Mar 28, 2019 at 2:04 PM D

Re: [Pulp-dev] Pulp2 Bug Backlog Closing?

Byan, What you are saying makes a lot of sense to me. The architectural differences between Pulp 2 and Pulp 3 are so great that most bugs don't translate well from one to the other. I would prefer if we just mass close Pulp 2 issues. On Thu, Apr 4, 2019 at 9:27 AM Bryan Kearney wrote: > I was i

Re: [Pulp-dev] [Pulp-list] Pulp 3.0 RC release

The Maven plugin 0.1.0b1 is now available on PyPI[0] and on GitHub[1]. It is compatible with pulpcore 3.0.0rc1. This release allows users to cache Maven artifacts in Pulp as they are requested by clients. [0] https://pypi.org/project/pulp-maven/ [1] https://github.com/pulp/pulp_maven On Thu, Mar

Re: [Pulp-dev] YouTube Custom URL

PulpProj On Fri, Mar 22, 2019 at 4:07 PM Dana Walker wrote: > Hey! > > We've grown and now qualify for a custom URL on our YouTube Channel--but > which one? youtube.com/Pulp is already taken, but I suggest either: > > A) youtube.com/PulpProj (like our Twitter handle) > or > B) youtube.com/PulpP

[Pulp-dev] pulpcore 3.0.0b23 is available

pulpcore 3.0.0b23 is available on PyPI[0]. The release notes can be found here [1]. The beta documentation is available here[2]. [0]: https://pypi.org/project/pulpcore/3.0.0b23 [1]: https://docs.pulpproject.org/en/3.0/nightly/release-notes/pulpcore/3.0.x.html#b23 [2] https://docs.pulpproject.org/

Re: [Pulp-dev] Changing behavior of the pclean alias

ometimes >>>> test let there some (it doesn't affect pulp but when clean db so clean it >>>> whole)? >>>> >>>> On Wed, Mar 20, 2019 at 12:12 PM Dennis Kliban >>>> wrote: >>>> >>>>> +1 >>>>>

Re: [Pulp-dev] pulp_file ownership

+1 On Wed, Mar 20, 2019 at 9:04 AM Daniel Alley wrote: > +1 > > On Wed, Mar 20, 2019 at 7:16 AM Brian Bouterse > wrote: > >> +1 to moving pulp_file to the core team >> >> We should also remove the 'File' team on github with this change, since >> it won't be a thing anymore. For those with Pulp

Re: [Pulp-dev] Changing behavior of the pclean alias

+1 On Tue, Mar 19, 2019 at 5:39 PM Daniel Alley wrote: > I created a new PR here [0] which changes the behavior of the pclean alias > so that it also wipes out /var/lib/pulp/ in addition to dropping and > recreating the database. > > Unless anyone objects, I plan to merge it tomorrow afternoon (

[Pulp-dev] pulpcore 3.0.0b22 and pulpcore-plugin 0.1.0b21 are available

The following packages are now available on PyPI: - pulpcore 3.0.0b22 [0] with its release notes here [1] - pulpcore-plugin 0.1.0b21 [2] with its release notes here [3] The beta documentation is available here[4]. [0]: https://pypi.org/project/pulpcore/3.0.0b22 [1]: https://docs.pulpproject

Re: [Pulp-dev] Nomenclature Clarification

> On Wed, Mar 13, 2019 at 10:47 AM Dennis Kliban wrote: > >> On Fri, Mar 8, 2019 at 10:34 AM Eric Helms wrote: >> >>> Howdy, >>> >>> Within Pulp 3, I've found myself struggling to refer to the pieces of >>> the runtime deployment and wanted

Re: [Pulp-dev] Nomenclature Clarification

On Fri, Mar 8, 2019 at 10:34 AM Eric Helms wrote: > Howdy, > > Within Pulp 3, I've found myself struggling to refer to the pieces of the > runtime deployment and wanted to raise a few questions I keep coming back > to. > > 1) Per [1], pulpcore seems to reference the entirety of the server, > wor

Re: [Pulp-dev] Pulp 2 and 3 Service Name Clashes

I agree with @rchan that we will require users to upgrade to a minimal version of Pulp 2 before they can upgrade to Pulp 3. We should just rename Pulp 2 services in a future release of Pulp 2. On Mon, Mar 4, 2019 at 11:31 AM Eric Helms wrote: > Howdy, > > In some migration of Pulp 2 to Pulp 3

Re: [Pulp-dev] Moving the pulp/pulp repo to pulp/pulpcore

Can we please schedule this for Thursday February 28? On Fri, Feb 22, 2019 at 7:56 AM Brian Bouterse wrote: > I believe we're to the point where pulp3 would benefit from having a repo > that was separate from pulp2. There are a few reasons, but rather than > recap it here I wrote up this issue [

Re: [Pulp-dev] Pulplift responsibilities

A new mini-team should be responsible for pulplift. I would like to be part of that team. I welcome others to join the team or to just send contributions. On Tue, Feb 5, 2019 at 9:15 AM Dana Walker wrote: > Eric Helms did a great job getting Pulplift off the ground and transferred > it to the Pu

[Pulp-dev] pulpcore 3.0.0b21 and pulp_file 0.0.1b8 are available

The following packages are now available on PyPI: - pulpcore 3.0.0b21 [0] with its release notes here [1] - pulp_file 0.0.1b8 [2] The beta documentation is available here[3]. This release adds support for S3 as the storage backend for Pulp. [0]: https://pypi.org/project/pulpcore/3.0.0b21 [

[Pulp-dev] pulpcore 3.0.0b20 and pulpcore-plugin 0.1.0b19 are available

The following packages are now available on PyPI: - pulpcore 3.0.0b20 [0] with its release notes here [1] - pulpcore-plugin 0.1.0b19 [2] with its release notes here [3] The beta documentation is available here[4]. [0]: https://pypi.org/project/pulpcore/3.0.0b20 [1]: https://docs.pulpproject

[Pulp-dev] pulpcore-plugin 0.1.0b18 available

A new version of pulpcore-plugin has been published to PyPI[0]. The list of changes can be found in the release notes[1]. [0] https://pypi.org/project/pulpcore-plugin/0.1.0b18/ [1] https://docs.pulpproject.org/en/pulpcore-plugin/nightly/release-notes/index.html#b18

Re: [Pulp-dev] pulplift with source installs for developers

are Engineer >>> >>> Red Hat >>> >>> <https://www.redhat.com> >>> <https://red.ht/sig> >>> >>> >>> On Tue, Jan 15, 2019 at 4:08 AM Eric Helms wrote: >>> >>>> Ready to transfer! Dennis I sent you

Re: [Pulp-dev] pulplift with source installs for developers

s > which is the "Pulp Team" group on github? > Yes. > On Fri, Jan 11, 2019 at 11:16 AM Dennis Kliban wrote: > >> Thanks for putting this together. After checking out your PRs I was able >> to provision a development environment. Everything worked as expecte

[Pulp-dev] Pulp Docker Plugin 4.0.0 beta 1 is available

The beta 1 release of pulp_docker for Pulp 3 is now available: https://pypi.org/project/pulp-docker/4.0.0b1/ Checkout a demo of the features: https://www.youtube.com/watch?v=IeY4lI8jG38&t=703s ___ Pulp-dev mailing list Pulp-dev@redhat.com https://www.r

Re: [Pulp-dev] pulplift with source installs for developers

source boxes or create a set of >> boxes designed for mounting by default to make spinning up easier. >> >> On Fri, Jan 4, 2019 at 4:58 PM Dennis Kliban wrote: >> >>> Thanks Brian! This looks like exactly what we need. >>> >>> On Fri, Jan 4, 20

Re: [Pulp-dev] pulplift with source installs for developers

om/theforeman/forklift#using-sshfs-to-share-folders > https://github.com/theforeman/forklift#adding-custom-boxes > > > On Fri, Jan 4, 2019 at 4:49 PM Dennis Kliban wrote: > >> We currently use Vagrant directly to create our development >> environment[0]. I would like to b

[Pulp-dev] pulplift with source installs for developers

We currently use Vagrant directly to create our development environment[0]. I would like to be able to use pulplift to create a development environment for Pulp 3. Our current Vagrantfile uses SSHFS to mount source code on the host onto the vagrant box[1]. This allows developers to make changes loc

Re: [Pulp-dev] Concerns about bulk_create and PostgreSQL

Thank you Daniel for the explanation and for filing an issue[0] to do performance analysis of UUIDs. I really hope that we can switch back to using UUIDs so we can bring back MariaDB support for Pulp 3. [0] https://pulp.plan.io/issues/4290 On Wed, Dec 5, 2018 at 1:35 PM Daniel Alley wrote: > T

Re: [Pulp-dev] Initial Release of python-rhsm on Pypi

Thank you Chris! This is great news. On Wed, Dec 19, 2018 at 4:38 PM Chris Snyder wrote: > Hi all, > > Announcing the initial release of python-rhsm 1.19.1 on pypi. As I've > understood it, Pulp Core depends on python-rhsm. Hopefully this will get > you all unblocked. > > If there is a need for

Re: [Pulp-dev] Single-Table Content API Changes, Performance Discussion

;>> > information and consistent with the summary counts. >>> >>> Just thought of something. The URLs for specific content types are at >>> the discretion of the plugin writer so now I'm not convinced the user >>> has a way to re

Re: [Pulp-dev] Single-Table Content API Changes, Performance Discussion

bindings user would know that when listing all the file content that she can provide keyword arguments to filter that content. Does that alleviate the concern? > > > On Thu, Dec 6, 2018 at 4:53 PM Dennis Kliban wrote: > >> On Tue, Nov 20, 2018 at 12:31 PM Dennis Kliban >>

Re: [Pulp-dev] Single-Table Content API Changes, Performance Discussion

On Tue, Nov 20, 2018 at 12:31 PM Dennis Kliban wrote: > On Mon, Nov 19, 2018 at 6:20 PM Daniel Alley wrote: > >> Some of the API changes that are required by single-table-content would >> be beneficial even if we didn't go forwards with the modelling changes. >> Fo

Re: [Pulp-dev] Proposal: merge the content-app & streamer

b.com/pulp/pulp/pull/3779 [1] https://pulp.plan.io/issues/3894 On Tue, Dec 4, 2018 at 1:54 PM Tatiana Tereshchenko wrote: > +1 to merge > +1 to have clear docs for plugin writers how to create their own content > app > > On Mon, Dec 3, 2018 at 11:25 PM Dennis Kliban wrote: > &

Re: [Pulp-dev] Proposal to remove 'notes' fields from the Pulp 3 RC

+1 to removing it On Tue, Dec 4, 2018 at 8:34 AM Austin Macdonald wrote: > +1, nice catch Daniel. > > On Tue, Dec 4, 2018, 7:14 AM David Davis >> Big +1. This seems like something we could add later on at any time when >> we need it. Hopefully we can get Katello and our users involved in sussin

Re: [Pulp-dev] Proposal: merge the content-app & streamer

; <https://www.redhat.com> > <https://red.ht/sig> > > > On Mon, Dec 3, 2018 at 2:40 PM Dennis Kliban wrote: > >> I like the idea of combining the two applications for all the reasons >> already outlined on this thread. The user experience is going to be >&g

Re: [Pulp-dev] Proposal: merge the content-app & streamer

I like the idea of combining the two applications for all the reasons already outlined on this thread. The user experience is going to be simplified by this change. However, I want to point out that it will also alter the plugin writer experience. Plugin writers that want to have their own content

Re: [Pulp-dev] Distributing Pulp3 Plans

No objections from me. On Thu, Nov 29, 2018 at 7:50 AM Brian Bouterse wrote: > The plan about 12-24 months ago was to distribute Pulp3 with Pulp itself > on a machine hosted in the osci.io community environment. We have this > ticket tracking that work [0] (still at NEW). > > I commented [1] tha

[Pulp-dev] pulpcore-3.0.0b16 and pulpcore-plugin-0.1.0b14 available

The following packages are now available on PyPI: - pulpcore 3.0.0b16 [0] with its release notes here [1] - pulpcore-plugin 0.1.0b14 [2] with its release notes here [3] The beta documentation is available here [4]. [0]: https://pypi.org/project/pulpcore/3.0.0b16/ [1]: https://docs.pulpproje

Re: [Pulp-dev] Chunked uploads of artifacts in Pulp 3

s > files larger than the limit imposed by the web server. > > I agree. I'll update the issue to reflect that this is a request for a new API that supports chunked uploads. > On Tue, Nov 27, 2018 at 3:38 PM Dennis Kliban wrote: > >> Looks like this is a problem

Re: [Pulp-dev] Chunked uploads of artifacts in Pulp 3

Looks like this is a problem with the nginx config. https://pulp.plan.io/issues/4196#note-3 On Tue, Nov 27, 2018 at 2:59 PM Andrew Kofink wrote: > I've reported this issue to support chunked uploads in Pulp 3: > https://pulp.plan.io/issues/4196. This is currently not implemented in > Pulp 3 but

Re: [Pulp-dev] Java Project patch update

I used that planning document to write up some stories around Maven[0]. The pull-through cache use case[1] should be implemented first. This work is blocked by changes needed in pulpcore[1]. However, once that feature is implemented in pulpcore, it should be very simple to implement the rest of the

Re: [Pulp-dev] Single-Table Content API Changes, Performance Discussion

On Mon, Nov 19, 2018 at 6:20 PM Daniel Alley wrote: > Some of the API changes that are required by single-table-content would be > beneficial even if we didn't go forwards with the modelling changes. For > instance, currently we have single endpoints for each of > repository_version/.../content/

[Pulp-dev] pulpcore-3.0.0b14 and pulpcore-plugin-0.1.0b12 available

The following packages are now available on PyPI: - pulpcore 3.0.0b14 [0] with its release notes here [1] - pulpcore-plugin 0.1.0b12 [2] with its release notes here [3] The beta documentation is available here[4]. [0]: https://pypi.org/project/pulpcore/3.0.0b14/ [1]: https://docs.pulpprojec

Re: [Pulp-dev] Dev freeze

On Mon, Nov 5, 2018 at 3:22 PM David Davis wrote: > I was looking at the release schedule page[0] and I saw that we define > release terms like ‘beta’ and ‘release candidate’ but we don’t define what > a ‘dev freeze’ means. I’d like to add the definition of ‘dev freeze' to our > release schedule

[Pulp-dev] pulpcore-3.0.0b12 and pulpcore-plugin-0.1.0b10 available

The following packages are now available on PyPI: - pulpcore 3.0.0b12 [0] with its release notes here [1] - pulpcore-plugin 0.1.0b10 [2] with its release notes here [3] The beta documentation is available here[4]. [0] https://pypi.org/project/pulpcore/3.0.0b12/ [1]: https://docs.pulpproject

Re: [Pulp-dev] 2.18.0 Dev Freeze - Tuesday, September 18 at 16:00 UTC

t should be available on Wednesday, October 3rd. > > > On Tue, Sep 25, 2018 at 4:11 PM Dennis Kliban wrote: > >> The 2.18.0 beta release of Pulp is delayed by one week. It should be >> available on Tuesday, October 2nd. >> >> On Tue, Sep 18, 2018 at 3:05 PM Den

[Pulp-dev] pulpcore 3.0.0b10 released

The following packages are now available on PyPI: - pulpcore 3.0.0b10 [0] - pulpcore-plugin 0.1.0b8 [1] Comprehensive list of changes and bugfixes for beta 10 can be found here[2]. The beta documentation is available here[3]. [0] https://pypi.org/project/pulpcore/3.0.0b10/ [1] https://pypi

[Pulp-dev] pulpcore 3.0.0b9 released

The following packages are now available on PyPI: - pulpcore 3.0.0b9 [0] - pulpcore-plugin 0.1.0b7 [1] Comprehensive list of changes and bugfixes for beta 9 can be found here[2]. Breaking changes include: * Problem: Pulp can't be configured using environment variable [3] * Problem: pulpcor

[Pulp-dev] update your pulp 3 dev environment

Pulp 3 now uses dynaconf[0]. This change required a change[1] to the dev environment. The simplest way to get the required changes is to run vagrant destroy. Fetch latest devel repo. Run vagrant up. You can update the environment without destroying it by updating the systemd files and creating /e

Re: [Pulp-dev] 2.18.0 Dev Freeze - Tuesday, September 18 at 16:00 UTC

The 2.18.0 beta release of Pulp is delayed by one week. It should be available on Tuesday, October 2nd. On Tue, Sep 18, 2018 at 3:05 PM Dennis Kliban wrote: > All the changes going into 2.18.0 need to be merged today. The current > list of features slated for 2.18.0 can be found here[0].

[Pulp-dev] pulpcore 3.0.0b8 released

The following packages are now available on PyPI: - pulpcore 3.0.0b8 [0] - pulpcore-plugin 0.1.0b6 [1] Comprehensive list of changes and bugfixes for beta 7 can be found here[2]. Breaking changes include: * Dropped support for Python 3.5 [3] * Id field no longer returned by REST API [4]

Re: [Pulp-dev] pulp-cookbook 0.0.2a2 released

It's merged and the changes are live[0]. [0] https://docs.pulpproject.org/en/3.0/nightly/plugins/index.html#plugin-list On Tue, Sep 18, 2018 at 3:19 PM, Simon Baatz wrote: > On Sat, Sep 15, 2018 at 05:40:15PM -0400, Dennis Kliban wrote: > >That's great news Simon! It sho

Re: [Pulp-dev] 2.18.0 Dev Freeze - Tuesday, September 18 at 16:00 UTC

?query_id=61 [1] https://pulp.plan.io/projects/pulp/wiki/2180_Release_Schedule On Wed, Sep 12, 2018 at 8:11 PM, Dennis Kliban wrote: > This is a reminder that the dev freeze for 2.18.0 will be next Tuesday. > This release is going to contain the features listed here[0]. > >

[Pulp-dev] 2.17.1 Dev Freeze -- Tuesday, September 18 at 21:00 UTC

All changes slated for 2.17.1 need to be merged today. The current list of bug fixes to be included in 2.17.1 can be found here[0]. Please let me know if there is anything missing from the list. The beta schedule[1] shows the 2.17.1 beta release date as Tuesday September 25th. [0] https://pulp.p

Re: [Pulp-dev] pulp-cookbook 0.0.2a2 released

That's great news Simon! It should be added to the plugins page of the docs[0]. What do you think? [0] https://docs.pulpproject.org/en/3.0/nightly/plugins/index.html On Fri, Sep 14, 2018 at 4:15 PM, Simon Baatz wrote: > Version 0.0.2a2 of the pulp_cookbook plugin is now available on PyPI > as

[Pulp-dev] 2.18.0 Dev Freeze - Tuesday, September 18 at 16:00 UTC

This is a reminder that the dev freeze for 2.18.0 will be next Tuesday. This release is going to contain the features listed here[0]. [0] https://pulp.plan.io/versions/64 ___ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listi

[Pulp-dev] pulpcore 3.0.0b7 released

The following packages are now available on PyPI: pulpcore 3.0.0b7 [0] pulpcore-plugin 0.1.0b5 [1] Comprehensive list of changes and bugfixes for beta 7 can be found here[2]. New features in Plugin API: * Stages API added to support sync workflows[3] Breaking changes include: * GroupDow

Re: [Pulp-dev] Triage of #3915

I've investigated the issue and agree with Jeff's assessment[0]. [0] https://pulp.plan.io/issues/3915#note-4 -Dennis On Tue, Sep 11, 2018 at 11:20 AM, Jeff Ortel wrote: > Issue 3915 has been skipped several times during triage with a request for > discussion on the issue. I feel this issue i

Re: [Pulp-dev] commit-bit nomination

-1 Milan has been a great contributor to the Pulp 2 RPM effort. I am looking forward to all the future contributions in both Pulp 2 and Pulp 3. However, after collaborating with Milan on issue 2619[0], I decided that he needs more mentorship. I can provide more feedback directly to you Milan. The

Re: [Pulp-dev] Proposal to drop support of Python 3.5 for Pulp 3

I am +1 on this also. On Fri, Sep 7, 2018 at 10:29 AM, Dana Walker wrote: > This sounds like a great idea. +1 > > My only hesitation would be if this hurts a significant portion of users. > Do we know how many users use older versions of Ubuntu or Debian that this > would impact? Any other gr

Re: [Pulp-dev] Plan to handle ids and hrefs

All the follow up work is now complete. The REST API returns relative paths in the 'href' field. pulp_file, pulp_python, and pulp_ansible have been updated with the required changes also. On Fri, Aug 31, 2018 at 1:52 PM, Dennis Kliban wrote: > > On Fri, Aug 24, 2018 at 7:00

Re: [Pulp-dev] Plan to handle ids and hrefs

On Fri, Aug 24, 2018 at 7:00 AM, David Davis wrote: > # Next Steps > > * enable the bindings by merging https://github.com/pulp/pulp/pull/3561 > * Need to switch full hrefs currently returned for relative href's to be > returned. i.e. https://example.com/pulp/api/v3/repositories/file/1/ -> > /p

[Pulp-dev] 2.18.0 Release Schedule

A 2.18.0 is being planned with some features and recent fixes. Here [0] is a release schedule page which outlines some tentative dates, starting with a dev freeze on September 18, 2018 @ 22:00 UTC. If this schedule needs to be adjusted, please reply with alternate dates. [0] https://pulp.plan.io/

Re: [Pulp-dev] Requiring 2FA in Github

ble to either (a) turn this into a short pup and call for a vote or >>>> (b) add a date to close this email thread decision by? >>>> >>>> Let me know if I should help write/review any. >>>> >>>> On Sat, Jul 28, 2018 at 6:09 AM, Tatiana Tereshche

Re: [Pulp-dev] PUP-1 template missing field

+1 On Tue, Aug 14, 2018 at 1:18 PM, Dana Walker wrote: > +1 > > Dana Walker > > Associate Software Engineer > > Red Hat > > > > > On Mon, Aug 13, 2018 at 4:18 PM, Brian Bouterse > wrote: > >> +1 >> >> On Mon, Aug 13, 2018 at 3:57 PM, Daniel Alley w

Re: [Pulp-dev] 2.17.0 Dev Freeze - Tuesday, August 7 at 16:00 UTC

This seems like a regression from behavior in 2.16.4. It was introduced with the new features added in 2.17. We should run the same test against 2.16.4 and see the results. On Tue, Aug 7, 2018 at 2:23 PM, Jeremy Audet wrote: > #3875 was discovered when running tests against nightly RPMs. > > ___

Re: [Pulp-dev] How to retrieve file via pulp API?

When docker communicates with Crane, the docker client receives redirects that specify the full path to all the files you are interested in. Docker then follows the redirects to retrieve the content from Pulp. The path for the redirects is formed using the docker_web_distributor config. The redirec

Re: [Pulp-dev] Proposed Update to PUP-4

+1 On Fri, Jul 27, 2018 at 9:57 AM, Tatiana Tereshchenko wrote: > +1 > > > On Tue, Jul 24, 2018 at 8:10 PM, Brian Bouterse > wrote: > >> +1 Thank you! >> >> On Tue, Jul 24, 2018 at 11:37 AM, Dana Walker >> wrote: >> >>> A PR [0] is up with a proposed update to PUP-4: Code of Conduct [1]. >>> >

Re: [Pulp-dev] Requiring 2FA in Github

+1, but I already have it enabled. On Thu, Jul 26, 2018 at 3:53 PM, David Davis wrote: > I got a notification from another organization I am a member of on > Github[0] that they are going to require Two Factor Authentication[1] in > response to recent news about some malicious code being shipped

Re: [Pulp-dev] proposed changes to Pulp 3 auto generated docs

API. On Wed, Jul 25, 2018 at 3:55 PM, David Davis wrote: > Correct me if I’m wrong but Pulp 2 supported @bizhang’s model of providing > both hrefs and ids. Was that a source of problems or complaints by Pulp 2 > users? > > David > > > On Wed, Jul 25, 2018 at 3:08 PM D

Re: [Pulp-dev] proposed changes to Pulp 3 auto generated docs

we can find a way to make that work. Overall I think >> users should be able to specify things in the most intuitive way possible, >> and I don't see how API data formats directly influence that. For example I >> think referring to a repository by it's name is the most nat

Re: [Pulp-dev] proposed changes to Pulp 3 auto generated docs

, 2018 at 8:30 AM, Daniel Alley wrote: > >> Keep in mind that as of yesterday, unless we revert the change, we are >> using Integers IDs instead of UUIDs >> >> https://github.com/pulp/pulp/pull/3549 >> >> On Wed, Jul 18, 2018 at 9:57 PM, Bihan Zhang

Re: [Pulp-dev] proposed changes to Pulp 3 auto generated docs

ifying the resources available via REST API. - The path parameters don't have a description in the schema. Do others agree with these problem statements? On Wed, Jul 18, 2018 at 9:31 AM, Dennis Kliban wrote: > I am working on improving the OpenAPI 2.0 schema for Pulp 3. I would like > to

[Pulp-dev] proposed changes to Pulp 3 auto generated docs

I am working on improving the OpenAPI 2.0 schema for Pulp 3. I would like to get some input on the improvements I am proposing. The schema is used to generate our REST API documentation as well as the bindings with swagger-codegen. The docs generated from our current schema look something like thi

Re: [Pulp-dev] CI not working on RHEL7 (for pulp_rpm)

On Thu, Jul 12, 2018 at 9:56 AM, Jeremy Audet wrote: > https://github.com/pulp/pulp-ci/pull/556 does this, correct? > I thought it did, but it was incomplete. Also needed https://github.com/pulp/pulp-ci/pull/558 ___ Pulp-dev mailing list Pulp-dev@redha

<    1   2   3   4   5   >