[Pulp-dev] [Breaking Changes] Concurrent dev envs for Pulp 2 and Pulp 3

Austin Macdonald austin at redhat.com
Thu Jul 6 14:59:44 UTC 2017


Correction: If you use vagrant-hostmanager (not vagrant-hostname), you will
have a slight adjustment to your workflow,

On Wed, Jul 5, 2017 at 7:58 AM, Austin Macdonald <austin at redhat.com> wrote:

> This work [0] will make it easier to have 2 Vagrant vms, one for Pulp 2
> and one for Pulp 3. It is optional and instructions on the wiki [1]. This
> work was done in these PRs. [2][3]
>
> Action Required:
>
> 1. Pick up the Vagrantfile.example changes
> 2. Delete the old libvirt machine with virt-manager
> 3. Provision a fresh vm.
>
> *If you use vagrant-hostname*, you will have a slight adjustment to your
> workflow, even if you only use one Vagrant vm at a time:
>     Pulp 2 --> "pulp2.dev". Ex: "https://pulp2.dev/pulp/api/
> v2/repositories/"
>     Pulp 3 --> "pulp3.dev". Ex: "http://pulp3.dev:8000/api/v3/
> repositories/
>
>
>
> [0]: https://pulp.plan.io/issues/2829
> [1]: https://pulp.plan.io/projects/pulp/wiki/Developer_
> Install_Options#Keep-a-Vagrant-box-for-Pulp-2-and-Pulp-3
> [2]: https://github.com/pulp/devel/pull/66
> [3]: https://github.com/pulp/devel/pull
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20170706/02f1a4d8/attachment.htm>


More information about the Pulp-dev mailing list