[Pulp-dev] [pulp-internal] Vagrant pulp2 pulp3 switching usage question

Brian Bouterse bbouters at redhat.com
Fri Apr 7 17:48:27 UTC 2017

I end up just remaking my vagrant environments often. It has the side
benefit of regularly checking that the vagrant environment is working which
is great for the community and other developers. The environment and
ansible playbooks are so different between master and 3.0-dev that it's not
practical to take a pulp2 vagrant environment and change it to a pulp3
environment (that I know of). Maybe I should keep two totally isolated
checkouts like @asmacdo does and just not run both of them at the same time.

Whenever I am about to `vagrant up` I always use the checkout.py script
which is only on the master branch of pulp/devel. I run it with:

python scripts/checkout.py    (it defaults to master so this checks out
pulp2 cleanly)
python scripts/checkout.py --version 3.0-dev      (for a pulp3 environment)

On Thu, Apr 6, 2017 at 6:54 PM, Austin Macdonald <amacdona at redhat.com>

> Ambiguity! I keep my pulp code in $HOME/devel, which is the directory I
> copied. As opposed to the devel project that holds our vagrant and ansible
> stuff. (Sadly that lives in devel/devel for me.)
> On Thu, Apr 6, 2017 at 6:45 PM, Austin Macdonald <amacdona at redhat.com>
> wrote:
>> I recursively copied my entire devel directory. I have one that stays in
>> 2 mode, and one that stays in 3 mode. They need different hostnames to run
>> simultaneously, but I don't bother with that-- I just shut it down.
>> On Thu, Apr 6, 2017 at 6:30 PM, Filip Dobrovolny <fdobrovo at redhat.com>
>> wrote:
>>> Hi all,
>>> I would like to ask when you are using Vagrant and switch between pulps
>>> how do you do it. If you do both of them in one env or you "re-up" when
>>> switching. I switch quite often so I ended up basically hacking the
>>> Vagrantfile and now i have vagrant up dev and vagrant up dev-old and
>>> starting the one I need. And I'm wondering if there is some easier solution.
>>> Filip
> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20170407/1ce67e4e/attachment.htm>

More information about the Pulp-dev mailing list