[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Outreachy openshift-ansible vagrant project

Hi Jason,

I am currently looking into the bug with Ansible 2.0 for setting up Vagrant with VirtualBox on Mac OS.  I have ran into the same issues when trying to install on my Macbook Pro.  I am planning to submit a contribution for this for the Outreachy application.

Since the application for Outreachy is due March 22 (Tuesday), I am planning to submit the application and continue to work on this issue to April.

What do you think of the following Outreachy proposal to work on the Openshift-Ansible Vagrant issues?
1.  Address open issues related to openshift-ansible with Ansible 2.0 and Vagrant 1.8.1 with VirtualBox on Mac OS.
2. Improve vagrantfile to work reliably with this set up.
3. Check that vagrantfile still works with other supported OS and environments.
4. Add documentation for this work.
5. If there is still time available, I would also be interested in getting Origin onto CentOS (if that isn't already taken by another intern.)

Also, for testing the vagrantfile in other environments/OS, is it sufficient to just use a VirtualBox VM?  For example, if I needed to test the vagrantfile on Windows.

Thanks for the guidance,


On Thu, Mar 17, 2016 at 11:12 PM, Jason DeTiberus <jdetiber redhat com> wrote:

On Fri, Mar 18, 2016 at 1:37 AM, Anna Liao <aliao22 gmail com> wrote:
Hi Jason,

Ok, cool, I will definitely take a look through the issues and see what I can do.  I installed the packages on a fedora system, and I also have a Mac so I can see if I can tackle some of the open issues.

In fact, while trying to run openshift-ansible vagrant on Fedora 21 system, I came across this same error: https://github.com/openshift/openshift-ansible/issues/373
And installing the latest vagrant 1.8.1 fixed it for me.

Nice work getting through that hiccup and thank you for providing an update on that issue. I was able to find this related issue on the vagrant github repo: https://github.com/mitchellh/vagrant/issues/5746, Reading through that and the linked issues it appears it's caused by a bug in Bundler and they were looking for a way to work around it in 1.8. So it looks like they were successful.

We probably just need to document the need to use vagrant 1.8+ in the README file to close out that issue for good.

Just wondering, is there a minimum system spec for the base platform to run the openshift-ansible on Fedora?  I assume the computer I have suffices, but thought I would check.  I can't upgrade the F21 I have, because it is used for another project.  But I may try to install F23 on something else.

So, I don't think there is anything that would cause an issue with Fedora 21. I can vouch for Fedora 22 working, and everything works under Fedora 23 as well. We really only test the versions of Fedora in use by our developers and the platforms that we deploy to (CentOS 7 for Origin and RHEL 7 for Enterprise). If you do run into issues using Fedora 21, then I would consider those bugs that we would need to address.

The main requirement that we have for openshift-ansible is to use ansible version 1.9.4 (earlier versions have known issues that we have started removing workarounds for and we haven't finished working on the issues preventing Ansible 2.0+ support yet). 

It sounds like you are already off to a great start. Just let us know if you need anything from us. I'm looking forward to seeing your first openshift-ansible Pull Request.


Thanks for all the suggestions!


On Thu, Mar 17, 2016 at 9:43 PM, Jason DeTiberus <jdetiber redhat com> wrote:

First off, thank you for reaching out to us about this project, our Vagrantfile for openshift-ansible is in some desperate need of some attention.

I've also cc'd Andrew Butcher who is one of our other mentors in case he wants to provide any additional information/ideas.

The links that Jonathan provided are definitely a good introduction to both openshift-ansible and the vagrant based environment we are looking for help with. Quite honestly, the Vagrantfile hasn't been receiving updates and testing as openshift-ansible has been evolving and I'm not even sure if it is currently in a working state.

An issue search (https://github.com/openshift/openshift-ansible/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+vagrant) on our github repo turns up quite a few outstanding issues that users have reported with the Vagrant setup and would definitely be a good place to start contributing, especially if you already have some experience with using Vagrant.

The majority of the issues reported have been related to issues using the Vagrantfile with VirtualBox on a Mac system, but I believe most of those are general issues related to the VirtualBox configuration. My main system runs Fedora and I use the libvirt provider for vagrant, so I don't have a good way to reproduce the reported issues (and I don't have a good enough understanding of configuring advanced networking for VirtualBox through vagrant to help remote troubleshooting of the issues).

A few of the VirtualBox related issues:

There are also a few known issues related to networking configuration and dns resolution between containers, VMs and the host that will need to be addressed, but I think that would be secondary to being able to get an environment that completes the provisioning steps.

Please let us know if you run into any questions or run into any issues along the way.

Jason DeTiberus

On Thu, Mar 17, 2016 at 8:29 PM, Jonathan Yu <jawnsy redhat com> wrote:
Hey Anna!

That's great that you'd like to contribute! I've never worked on this project myself (so I don't know anything), but I suggest taking a look at the documents linked under the "Contributing" section of the openshift-ansible README: https://github.com/openshift/openshift-ansible#contributing and running a Vagrant build as a start: https://github.com/openshift/openshift-ansible/blob/master/README_vagrant.md

For the contributing docs, I'd suggest starting with the Core Concepts doc, then the Best Practices and/or Code Style guides. Luckily it's a pretty brief guide.

This will let you get your feet wet, and give some time for our resident OpenShift/Ansible expert (Jason, on cc) to give you some more specific guidance. I also suggest reading through Jason's previous answer on the list, here: http://lists.openshift.redhat.com/openshift-archives/dev/2016-March/msg00047.html (though I'm not sure how relevant it is to your goals personally.) I also recommend joining the IRC channel (Freenode #openshift-outreachy) during business hours in US Eastern time.

If you somehow finish looking through all those things before Jason chimes in, then maybe getting a handle on Vagrant would be a good next step - this was the first hit for "Vagrant introduction": http://blog.scottlowe.org/2014/09/12/a-quick-introduction-to-vagrant/

We're excited to have you here. Welcome!



Warm wishes,

Jonathan Yu / Software Engineer, OpenShift by Red Hat / Twitter (@jawnsy) is the quickest way to my heart
“Ever tried. Ever failed. No matter. Try again. Fail again. Fail better.” — Samuel Beckett, Worstward Ho (1983) 

“In an adaptive environment, winning comes from adapting to change by continuously experimenting and identifying new options more quickly and economically than others. The classical strategist's mantra of sustainable competitive advantage becomes one of serial temporary advantage.” — Navigating the Dozens of Different Strategy Options (HBR)

On Thu, Mar 17, 2016 at 5:13 PM, Anna Liao <aliao22 gmail com> wrote:

I will be applying for Outreachy Round 12.  I am interested in Project 1: Vagrantfile improvements for openshift-ansible.  Python is my primary language and I have used Vagrant for one project.  I have been programming in Python for the past 4 years, though I'm a beginner with Vagrant.

I would like to make a contribution for my application.  Can you provide some guidance on how to get started with this project?


dev mailing list
dev lists openshift redhat com

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]