Story #2555

As a developer, I should be able to vagrant up into CentOS7 or a Support Fedora.

Added by sysadmind almost 5 years ago. Updated about 1 year ago.

Installer - Moved to GitHub issues
Start date:
Due date:
% Done:


Estimated time:
Platform Release:
Sprint Candidate:
Dev Environment


As a developer, it would be nice to have each platform supported by pulp available in Vagrant. Each of these can be named (i.e. fedora_25, centos_7) and each could be started separately. This would help test pulp across distributions and allow for easily testing changes, running tests, and triaging bugs.

Related issues

Related to Pulp - Story #2612: As a developer, I `vagrant up` into a rawhide boxCLOSED - WONTFIX

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>


#1 Updated by semyers almost 5 years ago

I think the cost of this is too high. We have enough trouble as it is keeping "the" vagrant environment healthy, so to have to do that for all supported platforms is frankly terrifying. The CI platform largely exists to mitigate cross-distribution problems, so I'd suggest that the real thing we need to fix is that our jenkins server lives behind a firewall, and the build logs are sadly not publicly available.

#2 Updated by bmbouter over 4 years ago

I think this story has a lot of value. I'm just not sure how to get there with the scope it's written as. I think this is mostly about having Vagrant support CentOS 7. Switching between Fedoras is pretty easy already by changing one line in the Vagrant file[0]. That also gets us Rawhide which we should be able to do by enabling this line[1]. We could use some docs to help devs understand how they can receive different versions of Fedora so that is one improvement that could be done.

The Vagrant environment of pulp3 is pretty different than pulp2 so if we do something like this, I think we should do it with Pulp3.

@sysadmind, do you think that repurposing this story to focus on adding Vagrant support for CentOS7 with Pulp3? Is that consistent with your intent when you filed it?


#3 Updated by sysadmind over 4 years ago

bmbouter, I think that your proposed changes make a lot of sense. I was thinking that I see issues come up from time to time that only effect one platform and it would be nice for the developer to be able to replicate any issues easily on the problem platform. I also think that having any supported OS available means that you can run the tests on all systems and potentially catch any issues earlier. I think this may be less of a problem in pulp3 because of the way automated testing is performed.

I'm ok with narrowing the scope of this down to CentOS 7 as that will get the project much closer to what I initially thought while not making this a ton of work.

#4 Updated by bmbouter over 4 years ago

  • Subject changed from As a developer, I want all supported platforms in vagrant to As a developer, I should be able to vagrant up into CentOS7 or a Support Fedora.
  • Description updated (diff)
  • Tags Pulp 3 added

I retitled it based on the CentOS 7 idea.

I think we should do this as part of Pulp3 so I gave it the "Pulp 3" tag. The Pulp3 ansible dev playbooks have gotten some good updates recently, but they have completely diverged from the Pulp2 playbooks.

#5 Updated by bmbouter over 4 years ago

  • Tags Dev Environment added

I created a 'Dev Environment' tag to track all of the developer environment improvements.

#6 Updated by over 4 years ago

  • Related to Story #2612: As a developer, I `vagrant up` into a rawhide box added

#7 Updated by about 3 years ago

  • Tags Pulp 3 installer added

#8 Updated by bmbouter over 2 years ago

  • Tags deleted (Pulp 3)

#9 Updated by bmbouter over 1 year ago

  • Category set to Installer - Moved to GitHub issues
  • Tags deleted (Pulp 3 installer)

#10 Updated by daviddavis about 1 year ago

  • Status changed from NEW to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF