The following packages are now available on PyPI:
pulpcore 3.0.0b6 [0]
pulpcore-plugin 0.1.0b4 [1]
pulp-file 0.0.1b4 [2]
Comprehensive list of changes and bugfixes for beta 6 can be found here
[3].
Breaking changes include:
* Use querysets for add/remove_content methods [4]
* Switch to u
I'm exploring the changes required to use IDs and hrefs on the PR here:
https://github.com/pulp/pulp/pull/3561#issuecomment-407888652
On Wed, Jul 25, 2018 at 4:24 PM, David Davis wrote:
> I know we don’t support things like accepting hrefs as references to
> resources but if I remember correctly
I know we don’t support things like accepting hrefs as references to
resources but if I remember correctly we do return hrefs alongside ids in
responses in Pulp 2. Is that not correct?
David
On Wed, Jul 25, 2018 at 4:17 PM Dennis Kliban wrote:
> I don't think we support both hrefs and ids in P
I don't think we support both hrefs and ids in Pulp 2. The Pulp 2 REST API
does not accept HREFs as references to resources. In Pulp 2's REST API we
do not even have resources that have relationships to other resources. The
relationships between resources are established by nesting them under one
a
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 Dennis Kliban wrote:
> For everyone following along, the conversation has moved to Github - on
> the
For everyone following along, the conversation has moved to Github - on the
PR[0] with the proposed changes.
[0] https://github.com/pulp/pulp/pull/3561
On Tue, Jul 24, 2018 at 11:15 AM, Bihan Zhang wrote:
> @dkliban I've tried out your PR and left a question: https://github.com/
> pulp/pulp/pul
Sorry, meant to include the issue:
https://pulp.plan.io/issues/3883
On Wed, Jul 25, 2018 at 11:31 AM, Eric Helms wrote:
> Thanks for the quick discussion. I went ahead and opened an issue and
> accompanying PR for the work to make this change for y'all to consider.
>
> On Wed, Jul 25, 2018 at 1
Thanks for the quick discussion. I went ahead and opened an issue and
accompanying PR for the work to make this change for y'all to consider.
On Wed, Jul 25, 2018 at 10:59 AM, Daniel Alley wrote:
> Not to say syslog is dead, it's especially useful for clustered installs
>> which need fancier log
>
> Not to say syslog is dead, it's especially useful for clustered installs
> which need fancier logging like centralization or off-site replication, etc.
And a lot of people who do use syslog are just telling journald to forward
logs there, in which case, console logging is still a good default
Thanks for the info about how systemd handles output. I’m +1 to using
console logging as the default.
David
On Wed, Jul 25, 2018 at 10:42 AM Brian Bouterse wrote:
> I think console logging is also probably the right logging default in non
> containerized environments too. The majority of OSes
Have you contributed to Pulp or the Pulp community in some way since the
last community demo? Show the community what you've done!
The next community demo is scheduled for Wednesday, August 1 at 14:00 UTC
[0].
All demos should be pre-recorded; here are some docs on how to do that [1].
Once you ha
I think console logging is also probably the right logging default in non
containerized environments too. The majority of OSes Pulp will run on will
run systemd which has it's logging facilities reading from stdout and
stderr [0]. So for the majority of non-containerized userbase systemd is
their l
You actually can run with console logging today. There is a bug where if
you are in an environment without syslog and enable console logging you
will get errors, see https://pulp.plan.io/issues/3879
Since background running typically translates to systemd based, perhaps
considering making logging
I definitely think that we should support console logging (and it looks
like we currently don’t) but I’m a bit hesitant to make it the default. I
think right now a majority of non-dev users will be running these services
in the background. But I could see perhaps one day where Pulp is mostly run
in
Howdy,
As I understand things, the default logging in Pulp 3 is set to syslog. I
am proposing changing this to be console by default and optionally letting
users configure syslog. I think these days console as a default makes
general sense for running things in a simple terminal, or as a developer
15 matches
Mail list logo
