Task #4495: Rename pulp-wsgi to be more descriptive - Pulp

Actions

Send by e-mail Copy link

Task #4495

closed

Rename pulp-wsgi to be more descriptive

Added by ehelms@redhat.com about 5 years ago. Updated almost 4 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

amacdona@redhat.com

Category:

Installer - Moved to GitHub issues

Sprint/Milestone:

3.0.0

Start date:

Due date:

% Done:

100%

Estimated time:

Platform Release:

Groomed:

Sprint Candidate:

Tags:

Sprint:

Sprint 50

Quarter:

Description

The rest of Pulp services describe their function while pulp-wsgi describes the interface used to serve the application. I think it would be more useful to rename this service to describe the functionality. Some ideas:

pulp-core
pulp-api
pulp-api-server

Actions

Copy link

Updated by daviddavis about 5 years ago

Tags Pulp 3 added

Actions

Copy link

Updated by CodeHeeler about 5 years ago

Tracker changed from Issue to Task
% Done set to 0
Sprint set to Sprint 49
Tags Pulp 3 RC Blocker added

Actions

Copy link

Updated by rchan about 5 years ago

Sprint changed from Sprint 49 to Sprint 50

Actions

Copy link

Updated by ehelms@redhat.com about 5 years ago

Related I sent an email to pulp-dev discussing this a bit more broadly:

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, workers and resource manager that live within the repository at [2]. Is that correct?
2) What is the 'server' called? I keep wanting to call it the 'pulp-api-server' or 'pulp-api-app' or 'pulp-api'.

- Eric

[1] https://docs.pulpproject.org/en/3.0/nightly/glossary.html#term-pulpcore
[2] https://github.com/pulp/pulpcore

Actions

Copy link