Task #4586: add vagrant installation instructions to pulplift - Pulp

Agile board
Agile charts

Agile boards

Pulp 2 QE Agile Board
Pulp 2 QE Agile Board - Priority View
Pulp 3 QE Agile Board
Pulp 3 RPM Tests Agile Board
Sprint 112 Agile Board

Custom queries

[All Projects] All Test Trackers
2.21.4 - Next Bugfix Release
2.21.4 MODIFIED
2.21.5
3.14.3
CI/CD
Easy Fix
FIPS open
Functional Tests
Galaxy NG
Groomed
Installer - Triage
Installer Items
Issues for Triage
Katello Integration
Next Docs Day
Operator issues
POST/ASSIGNED - no Sprint - Pulp2
POST/ASSIGNED - no Sprint - Pulp3
Prioritized Bugs
Pulp 3 Docs issues
Pulp2 issues available for next release
Pulpcore
SELinux related
Sprint 111
Sprint 112
Sprint Candidates (also groomed)
Un-Triaged Bugs
Verification Required

Actions

Send by e-mail Copy link

Task #4586

closed

add vagrant installation instructions to pulplift

Added by amacdona@redhat.com almost 6 years ago. Updated over 4 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

ppicka

Category:

Installer - Moved to GitHub issues

Sprint/Milestone:

Start date:

Due date:

% Done:

100%

Estimated time:

Platform Release:

Groomed:

Yes

Sprint Candidate:

Yes

Tags:

Dev Environment, Documentation

Sprint:

Sprint 52

Quarter:

Description

Currently, there isn't anything about vagrant, installation is left to the user following vagrant docs. This isn't ideal because there are vagrant plugins that should be installed as well.

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by amacdona@redhat.com almost 6 years ago

Requirements that should be documented (whoever takes this should confirm):

vagrant
sshfs (do we need to start this service?)
vagrant-ssh
vagrant-hostmanager
libvirt
vagrant-libvirt

FWIW, I think you can install the vagrant plugins with vagrant itself, avoiding the differences between the operating systems.

After some discussion on IRC, the consensus is that there isn't a need to hand hold. We should list our requirements similarly to forklift. https://github.com/theforeman/forklift#requirements

Actions

Copy link

Updated by bmbouter almost 6 years ago

I'm +1 on documenting the requirements similarly to forklift. https://github.com/theforeman/forklift#requirements

Actions

Copy link

Updated by bmbouter almost 6 years ago

Groomed changed from No to Yes
Sprint Candidate changed from No to Yes

Actions

Copy link

Updated by dkliban@redhat.com almost 6 years ago

Sprint set to Sprint 51

Actions

Copy link

Updated by amacdona@redhat.com almost 6 years ago

Tracker changed from Issue to Task
% Done set to 0

Actions

Copy link

Updated by rchan over 5 years ago

Sprint changed from Sprint 51 to Sprint 52

Actions

Copy link

Updated by bmbouter over 5 years ago

Tags deleted (~~Pulp 3~~)

Actions

Copy link

Updated by ppicka over 5 years ago

Status changed from NEW to ASSIGNED
Assignee set to ppicka

Added by ppicka over 5 years ago

Revision 9bb77b14 | View on GitHub

Add requirements

Add requirements of pulplift to README.

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

Signed-off-by: Pavel Picka ppicka@redhat.com

Actions

Copy link

Updated by ppicka over 5 years ago

Status changed from ASSIGNED to POST

PR: https://github.com/pulp/pulplift/pull/30

I didn't specify libvirt deps as virtualbox is supported too. I think it depends on user to choose what he want to use.
Or it can be expanded 'in case user want libvirt/vb' or something like that.

Actions

Copy link

#10