Project

Profile

Help

Story #2421

closed

As a user I can manage Pulp's database migrations using a systemwide command

Added by dkliban@redhat.com about 6 years ago. Updated about 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Low
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Sprint:
Sprint 17
Quarter:

Description

In Pulp 2.Y, users use pulp-manage-db to migrate their database when installing for the first time or upgrading to a new version.

It's important that users are able to continue to run migrations in Pulp 3.Y. Since we are leveraging Django's migration management capabilities, Pulp users will need to use the manage.py that is part of the Pulp Django app.

As a result of this story, a new executable should be created. This executable will take the same arguments that manage.py takes and simply forward them to the manage.py in the Pulp app that is installed.

We can add any custom commands we need[0]. One such command could be 'reset-admin-pass' as I mentioned here[1].

A possible name for the executable is 'pulp-manager'.

[0] https://docs.djangoproject.com/en/1.8/howto/custom-management-commands/
[1] https://pulp.plan.io/issues/2358?pn=1#note-8

Actions #1

Updated by dkliban@redhat.com about 6 years ago

  • Description updated (diff)
Actions #2

Updated by dkliban@redhat.com about 6 years ago

  • Description updated (diff)
Actions #3

Updated by dkliban@redhat.com about 6 years ago

  • Description updated (diff)
Actions #4

Updated by bmbouter about 6 years ago

  • Groomed changed from No to Yes

+1 to this story.

Generically forwarding the commands to manage.py could make the user experience strange/dangerous, but I think as a first-cut at having a utility we should do just this. We can add some filtering later to the forwarded commands.

+1 to pulp-manager as the name. We could also use pulp-server or pulp-config. We can also change this name easily later.

I added some checklist items, and specified that it should be done using a setup.py entrypoint.

I wonder if this would be runnable by any user, or do we need to have it continue to be the apache user?

Actions #6

Updated by mhrivnak about 6 years ago

  • Sprint/Milestone set to 30
Actions #7

Updated by bmbouter about 6 years ago

  • Priority changed from Normal to Low

Moving to low priority so that it's picked up behind other higher work.

Actions #8

Updated by fdobrovo almost 6 years ago

  • Status changed from NEW to ASSIGNED
Actions #9

Updated by fdobrovo almost 6 years ago

  • Status changed from ASSIGNED to POST
Actions #10

Updated by mhrivnak almost 6 years ago

  • Sprint/Milestone changed from 30 to 36

Added by fdobrovo almost 6 years ago

Revision 67b13412

As a user I can manage Pulp using a systemwide command

closes #2421 https://pulp.plan.io/issues/2421

Added by fdobrovo almost 6 years ago

Revision 67b13412

As a user I can manage Pulp using a systemwide command

closes #2421 https://pulp.plan.io/issues/2421

Actions #11

Updated by ttereshc almost 6 years ago

  • Assignee set to fdobrovo
Actions #12

Updated by fdobrovo almost 6 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions #13

Updated by bmbouter almost 5 years ago

  • Sprint set to Sprint 17
Actions #14

Updated by bmbouter almost 5 years ago

  • Sprint/Milestone deleted (36)
Actions #15

Updated by daviddavis almost 4 years ago

  • Sprint/Milestone set to 3.0.0
Actions #16

Updated by bmbouter almost 4 years ago

  • Tags deleted (Pulp 3)
Actions #17

Updated by bmbouter about 3 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF