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. 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. Thanks for all the suggestions! Anna On Thu, Mar 17, 2016 at 9:43 PM, Jason DeTiberus <[email protected]> wrote: > Anna, > > 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: > - https://github.com/openshift/openshift-ansible/issues/942 > - https://github.com/openshift/openshift-ansible/issues/705 > > 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. > > Thanks, > -- > Jason DeTiberus > > > > > On Thu, Mar 17, 2016 at 8:29 PM, Jonathan Yu <[email protected]> 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! >> >> Cheers, >> >> Jonathan >> >> >> Warm wishes, >> >> Jonathan Yu / Software Engineer, OpenShift by Red Hat / Twitter >> (@jawnsy) is the quickest way to my heart <https://twitter.com/jawnsy> >> *“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 >> <https://hbr.org/2015/06/navigating-the-dozens-of-different-strategy-options> >> (HBR) >> >> On Thu, Mar 17, 2016 at 5:13 PM, Anna Liao <[email protected]> wrote: >> >>> Hello! >>> >>> 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? >>> >>> Thanks, >>> Anna >>> >>> _______________________________________________ >>> dev mailing list >>> [email protected] >>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >>> >>> >> > >
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
