Project

Profile

Help

Story #5230

Story #3821: As a user, I can migrate from Pulp 2 to Pulp 3

As a user, I have a default configuration for MongoDB connection

Added by ttereshc 3 months ago. Updated 2 months ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

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

Description

Currently users need to add this config manually to their /etc/pulp/settings.py.

The following config should be added automatically into /etc/pulp/settings.py at installation time.

PULP2_MONGODB = {
    'name': 'pulp_database',
    'seeds': 'localhost:27017',
    'username': '',
    'password': '',
    'replica_set': '',
    'ssl': False,
    'ssl_keyfile': '',
    'ssl_certfile': '',
    'verify_ssl': True,
    'ca_path': '/etc/pki/tls/certs/ca-bundle.crt',
}

History

#1 Updated by dkliban@redhat.com 3 months ago

The ansible-pulp installer provides all the configs. This config is only needed when the pulp-2to3-migrate plugin is installed. We have two options for adding this functionality to the installer:

1. Add a new role to ansible-pulp0 called pulp-2to3-migrate and it

2. Create a seprate role published on galaxy called pulp-2to3-migrate-pre-requisite - rpm plugin does this and this will be easier to execute after a related task is done1.

I am leaning toward 1 in this case, but 2 seems more correct.

[0] https://github.com/pulp/ansible-pulp/tree/master/roles
[1] https://pulp.plan.io/issues/4770

#2 Updated by amacdona@redhat.com 2 months ago

  • Tags Documentation added

The `pulp_settings` ansible variable allows arbitrary nested fields. The playbook user can specify:

pulp_settings:
    pulp2_mongodb:
         'name': 'pulp_database',
         'seeds': 'localhost:27017'
         ...etc

This will add PULP2_MONGDB to /etc/pulp/settings.py. Since thats all we need at the moment, I suggest we do not create a new role yet and just make this a documentation issue for the pulp-2to3-migration plugin.

Please register to edit this issue

Also available in: Atom PDF