Project

Profile

Help

Story #2421

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

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

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

100%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
Sprint 17

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 need0. One such command could be 'reset-admin-pass' as I mentioned here1.

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


Checklist

Associated revisions

Revision 67b13412 View on GitHub
Added by fdobrovo over 2 years ago

As a user I can manage Pulp using a systemwide command

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

Revision 67b13412 View on GitHub
Added by fdobrovo over 2 years ago

As a user I can manage Pulp using a systemwide command

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

Revision 67b13412 View on GitHub
Added by fdobrovo over 2 years ago

As a user I can manage Pulp using a systemwide command

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

History

#1 Updated by dkliban@redhat.com almost 3 years ago

  • Description updated (diff)

#2 Updated by dkliban@redhat.com almost 3 years ago

  • Description updated (diff)

#3 Updated by dkliban@redhat.com almost 3 years ago

  • Description updated (diff)

#4 Updated by bmbouter almost 3 years ago

  • Checklist item define the pulp-manager binary as a python entry point added
  • Checklist item have all commands be passed along to the manage.py for pulp_app added
  • 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?

#5 Updated by dkliban@redhat.com almost 3 years ago

  • Checklist item update REST API docs with the new command name (instead of manage.py) added

#6 Updated by mhrivnak almost 3 years ago

  • Sprint/Milestone set to 30

#7 Updated by bmbouter almost 3 years ago

  • Priority changed from Normal to Low

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

#8 Updated by fdobrovo over 2 years ago

  • Status changed from NEW to ASSIGNED

#9 Updated by fdobrovo over 2 years ago

  • Status changed from ASSIGNED to POST

#10 Updated by mhrivnak over 2 years ago

  • Sprint/Milestone changed from 30 to 36

#11 Updated by ttereshc over 2 years ago

  • Assignee set to fdobrovo

#12 Updated by fdobrovo over 2 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#13 Updated by bmbouter over 1 year ago

  • Sprint set to Sprint 17

#14 Updated by bmbouter over 1 year ago

  • Sprint/Milestone deleted (36)

#15 Updated by daviddavis 6 months ago

  • Sprint/Milestone set to 3.0

#16 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF