Project

Profile

Help

Issue #1137

closed

fix dev-setup.sh script

Added by igulina@redhat.com over 9 years ago. Updated over 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
1. Low
Version:
Master
Platform Release:
2.8.0
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

When we had talked about removing dev-setup.sh I had forgotten that Vagrant will only work for developers who are working on physical hosts with virtualization extensions. Since some developers may use Openstack or EC2 for development, there may[0] still be a place for a dev-setup.sh script.

It's been reported by igulina that our dev-setup.sh script fails in some way (I am not sure what the issue is). We should fix the dev-setup.sh script so that it works again.

It would be wise to also refactor it so that it uses the same Ansible code that is used by Vagrant so we can benefit from some code sharing. The dev-setup.sh script does do a little more than the Vagrant setup so it will still need to be a separate thing, but if we can get it down to just checking out the code and calling Ansible that would be a win, and would decrease the chance of future breakage.

[0] I say "may", because technically I think Vagrant can also provision EC2 and Openstack environments, though our current implementation of the Vagrantfile does not support this.

Also available in: Atom PDF