[Pulp-dev] pulplift with source installs for developers

Tue Jan 15 22:12:26 UTC 2019

Excellent.

Then unless no objections show up, let's plan on moving this on Wednesday.
@dkliban can initiate as the admin (granted privs from ehelms), and I can
configure as a Pulp organization admin.

On Tue, Jan 15, 2019 at 12:42 PM Robin Chan <rchan at redhat.com> wrote:

> No issues with transferring ownership as Eric says he's ready.
> And target location sounds good.
>
> On Tue, Jan 15, 2019 at 11:06 AM Dana Walker <dawalker at redhat.com> wrote:
>
>> Big shout out to Eric for all the work on pulplift--thank you!
>>
>> Dana Walker
>>
>> Associate Software Engineer
>>
>> Red Hat
>>
>> <https://www.redhat.com>
>> <https://red.ht/sig>
>>
>>
>> On Tue, Jan 15, 2019 at 4:08 AM Eric Helms <ehelms at redhat.com> wrote:
>>
>>> Ready to transfer! Dennis I sent you a collaborator invite to make you
>>> an admin to do the transfer.
>>>
>>> On Mon, Jan 14, 2019 at 5:08 PM Dennis Kliban <dkliban at redhat.com>
>>> wrote:
>>>
>>>> I just merged the changes to ansible-pulp3 and the Eric already merged
>>>> the changes to pulplift.
>>>>
>>>> On Mon, Jan 14, 2019 at 4:00 PM Brian Bouterse <bbouters at redhat.com>
>>>> wrote:
>>>>
>>>>> I switched to it today, and it's been working well for me. +1 to
>>>>> adopting it as the official dev environment since it consolidates the
>>>>> ansible playbooks into one asset so we can stop maintaining two.
>>>>>
>>>>> When is the right time to move pulplift from @ehelms to the Pulp
>>>>> organization on github?
>>>>>
>>>>
>>>> I'd like this to happen ASAP.
>>>>
>>>>
>>>>> When we do move it can we just land it where we land all the general
>>>>> repos which is the "Pulp Team" group on github?
>>>>>
>>>>
>>>> Yes.
>>>>
>>>>
>>>>> On Fri, Jan 11, 2019 at 11:16 AM Dennis Kliban <dkliban at redhat.com>
>>>>> wrote:
>>>>>
>>>>>> Thanks for putting this together. After checking out your PRs I was
>>>>>> able to provision a development environment. Everything worked as expected.
>>>>>> I'd like to see us switch to these developer environments next week.
>>>>>>
>>>>>> Has anyone else had a chance to try it out?
>>>>>>
>>>>>> On Wed, Jan 9, 2019 at 6:10 PM Dana Walker <dawalker at redhat.com>
>>>>>> wrote:
>>>>>>
>>>>>>> I have some initial PRs [0][1][2] up for using pulplift to create a
>>>>>>> development environment for pulp3 as described in 4243. [3]  Please take a
>>>>>>> look and provide feedback on any changes we might want to make.  Feel free
>>>>>>> to discuss what we'd like to see here or comment directly on the PRs.
>>>>>>>
>>>>>>> Note, I haven't added the requirements for building the docs yet, so
>>>>>>> that update will come tomorrow, but I wanted to get this out here and start
>>>>>>> hearing from all of you.
>>>>>>>
>>>>>>> [0] https://github.com/pulp/ansible-pulp3/pull/61
>>>>>>> [1] https://github.com/ehelms/pulplift/pull/3
>>>>>>> [2] https://github.com/pulp/pulp/pull/3824
>>>>>>> [3] https://pulp.plan.io/issues/4234
>>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>> --Dana
>>>>>>>
>>>>>>> Dana Walker
>>>>>>>
>>>>>>> Associate Software Engineer
>>>>>>>
>>>>>>> Red Hat
>>>>>>>
>>>>>>> <https://www.redhat.com>
>>>>>>> <https://red.ht/sig>
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Jan 7, 2019 at 8:34 PM Eric Helms <ehelms at redhat.com> wrote:
>>>>>>>
>>>>>>>> The current setup would have each individual configure custom boxes
>>>>>>>> to suit their needs. If there was a fairly common setup for location of
>>>>>>>> source code and mount options we could update the source boxes or create a
>>>>>>>> set of boxes designed for mounting by default to make spinning up easier.
>>>>>>>>
>>>>>>>> On Fri, Jan 4, 2019 at 4:58 PM Dennis Kliban <dkliban at redhat.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Thanks Brian! This looks like exactly what we need.
>>>>>>>>>
>>>>>>>>> On Fri, Jan 4, 2019 at 4:54 PM Brian Bouterse <bbouters at redhat.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> pulplift itself relies heavily on "forklift" which itself has
>>>>>>>>>> some good docs. Take a look at these docs and see if it generates new
>>>>>>>>>> questions.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> https://github.com/theforeman/forklift#using-sshfs-to-share-folders
>>>>>>>>>> https://github.com/theforeman/forklift#adding-custom-boxes
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Fri, Jan 4, 2019 at 4:49 PM Dennis Kliban <dkliban at redhat.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> We currently use Vagrant directly to create our development
>>>>>>>>>>> environment[0]. I would like to be able to use pulplift to create a
>>>>>>>>>>> development environment for Pulp 3. Our current Vagrantfile uses SSHFS to
>>>>>>>>>>> mount source code on the host onto the vagrant box[1]. This allows
>>>>>>>>>>> developers to make changes locally on their laptop and the same code to run
>>>>>>>>>>> inside the vagrant box.
>>>>>>>>>>>
>>>>>>>>>>> pulplift already provides boxes named 'pulp3-source-*'. These
>>>>>>>>>>> boxes use a playbook[2] from ansible-pulp3 repo to perform the
>>>>>>>>>>> installation. By default, this playbook assumes that the vagrant box has
>>>>>>>>>>> pulp source code at "/home/vagrant/devel/pulp". However,
>>>>>>>>>>> without the synced folders, the  source code is not there and the install
>>>>>>>>>>> fails.
>>>>>>>>>>>
>>>>>>>>>>> I would like to extend pulplift to use synced folders for the
>>>>>>>>>>> source install boxes. However, I am not sure where to add such directives
>>>>>>>>>>> for vagrant.
>>>>>>>>>>>
>>>>>>>>>>> Eric, can you point me in the right direction?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> [0]
>>>>>>>>>>> https://github.com/pulp/devel/blob/master/Vagrantfile.example
>>>>>>>>>>> [1]
>>>>>>>>>>> https://github.com/pulp/devel/blob/master/Vagrantfile.example#L8
>>>>>>>>>>> [2]
>>>>>>>>>>> https://github.com/pulp/ansible-pulp3/blob/master/source-install.yml
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> Pulp-dev mailing list
>>>>>>>>>>> Pulp-dev at redhat.com
>>>>>>>>>>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>> Pulp-dev mailing list
>>>>>>>> Pulp-dev at redhat.com
>>>>>>>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>>>>>>>
>>>>>>> _______________________________________________
>>>>>> Pulp-dev mailing list
>>>>>> Pulp-dev at redhat.com
>>>>>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>>>>>
>>>>> _______________________________________________
>>>> Pulp-dev mailing list
>>>> Pulp-dev at redhat.com
>>>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>>>
>>> _______________________________________________
>>> Pulp-dev mailing list
>>> Pulp-dev at redhat.com
>>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>>
>> _______________________________________________
>> Pulp-dev mailing list
>> Pulp-dev at redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>
> _______________________________________________
> 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/20190115/e145e5e4/attachment.htm>