I use this basic inventory with fedora atomic: https://github.com/michaelgugino/openshift-stuff/tree/master/fedora-atomic
I usually deploy to AWS for testing and development. Wherever you deploy, your instance's hostnames need to be resolvable. I don't have any recommendations for using any specific tags. I usually use the head of a release branch; I very rarely use specific tags or commits. I don't have any general recommendations for deploying any other than released openshift code. If you're trying to deploy testing images / rpms, your setup is going to depend on what you're trying to accomplish. I highly recommend deploying released code. That is the only way it's going to 'just work.' On Fri, Mar 16, 2018 at 4:41 PM, Charles Moulliard <cmoul...@redhat.com> wrote: > > > On Fri, Mar 16, 2018 at 8:57 PM, Michael Gugino <mgug...@redhat.com> wrote: >> >> I typically use the head of each release branch for openshift-ansible. >> Most of the time that's a good approach for anything that is already >> released (such as 3.7). > > >>> So using this tagged release is a good idea then : >>> https://github.com/openshift/openshift-ansible/releases/tag/openshift-ansible-3.7.38-1 >>> ? > >> Alternatively, you can install the >> openshift-ansible origin rpm on a centos host. > > >>> How can I do that ? >> >> >> I don't recommend using openshift_repos_enable_testing, it's been >> nothing but problems for me. I don't recommend using any testing >> versions of any packages either. > > >>> I agree as last run generayed such bad rpms installed > > Beginning of executing the playbook > origin.x86_64 3.7.0-1.0.7ed6862 > @centos-openshift-origin37 > origin-clients.x86_64 3.7.0-1.0.7ed6862 > @centos-openshift-origin37 > origin-master.x86_64 3.7.0-1.0.7ed6862 > @centos-openshift-origin37 > > Later ... > > origin.x86_64 3.7.1-1.el7.git.0.0a2d6a1 > @centos-openshift-origin37-testing > origin-clients.x86_64 3.7.1-1.el7.git.0.0a2d6a1 > @centos-openshift-origin37-testing > origin-master.x86_64 3.7.1-1.el7.git.0.0a2d6a1 > @centos-openshift-origin37-testing > origin-node.x86_64 3.7.1-1.el7.git.0.0a2d6a1 > @centos-openshift-origin37-testing > > >> >> >> For testing new origin code, I have had the best luck with Fedora >> Atomic 27. > > >>> Can you share what you did (info, doc, ...) ? > >> >> However, I don't think 3.9 origin is in great shape at the >> moment. >> >> On Fri, Mar 16, 2018 at 3:49 PM, Charles Moulliard <cmoul...@redhat.com> >> wrote: >> > Do you suggest to use a tagged version of the openshift ansible git repo >> > combined >> > with such parameters within the inventory ? >> > >> > E.g >> > >> > git clone -b >> > >> > https://github.com/openshift/openshift-ansible/releases/tag/openshift-ansible-3.7.38-1 >> > >> > inventory >> > ======= >> > openshift_repos_enable_testing = true >> > containerized = false >> > openshift_release = v3.7 >> > openshift_pkg_version = "-3.7.0-1.0.7ed6862" # See -> >> > https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin37/ >> > openshift_deployment_type = origin >> > ... >> > >> > ansible-playbook -i inventory openshift-ansible/playbooks/byo/config.yml >> > >> > On Fri, Mar 16, 2018 at 8:44 PM, Michael Gugino <mgug...@redhat.com> >> > wrote: >> >> >> >> I would start again with new hosts, probably the easiest way forward. >> >> I recommend using the released versions if you are not comfortable >> >> with troubleshooting openshift-ansible. >> >> >> >> On Fri, Mar 16, 2018 at 3:29 PM, Charles Moulliard >> >> <cmoul...@redhat.com> >> >> wrote: >> >> > Yep. I did a mistake but I have cleaned my machine and did a new >> >> > deployment >> >> > but we a get weird error again >> >> > >> >> > INSTALLER STATUS >> >> > >> >> > >> >> > ******************************************************************************************************************************************************************************************************************** >> >> > Initialization : Complete >> >> > Health Check : Complete >> >> > etcd Install : Complete >> >> > Master Install : Complete >> >> > Master Additional Install : Complete >> >> > Node Install : In Progress >> >> > This phase can be restarted by running: >> >> > playbooks/byo/openshift-node/config.yml >> >> > >> >> > >> >> > >> >> > Failure summary: >> >> > >> >> > >> >> > 1. Hosts: 192.168.99.50 >> >> > Play: Configure nodes >> >> > Task: Install sdn-ovs package >> >> > Message: Error: Package: >> >> > origin-sdn-ovs-3.7.0-1.0.7ed6862.x86_64 >> >> > (centos-openshift-origin37) >> >> > Requires: origin-node = 3.7.0-1.0.7ed6862 >> >> > Installed: >> >> > origin-node-3.7.1-1.el7.git.0.0a2d6a1.x86_64 >> >> > (@centos-openshift-origin37-testing) >> >> > origin-node = 3.7.1-1.el7.git.0.0a2d6a1 >> >> > Available: >> >> > origin-node-v3.7.1-0.3.7.1.el7.git.0.b113c29.x86_64 >> >> > (centos-openshift-origin37-testing) >> >> > >> >> > So it seems that the version calculated and downloaded from this repo >> >> > https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin37/ >> >> > is >> >> > not >> >> > consistent >> >> > >> >> > Is there a way to download / install properly all the required origin >> >> > rmps >> >> > as ansible playbook fails ? >> >> > >> >> > >> >> > On Fri, Mar 16, 2018 at 8:24 PM, Michael Gugino <mgug...@redhat.com> >> >> > wrote: >> >> >> >> >> >> Charles, >> >> >> >> >> >> You cannot install 3.9 from the openshift-ansible 3.7 branch. If >> >> >> you want to install 3.9, you need to use the openshift-ansible 3.9 >> >> >> branch, which is not officially released yet. >> >> >> >> >> >> There is not a testing repo for each release of openshift; just >> >> >> the >> >> >> latest unreleased version. If you enable testing repos on the 3.7 >> >> >> branch, you'll end up getting 3.9 packages which is what's happening >> >> >> here. >> >> >> >> >> >> On Fri, Mar 16, 2018 at 11:32 AM, Charles Moulliard >> >> >> <cmoul...@redhat.com> >> >> >> wrote: >> >> >> > Hi, >> >> >> > >> >> >> > Are the OpenShift Origin v3.9 rpms available from a repo ? >> >> >> > How can we get them in order to install openshift cluster using >> >> >> > ansible >> >> >> > playbook ? >> >> >> > >> >> >> > Regards >> >> >> > >> >> >> > Charles >> >> >> > >> >> >> > _______________________________________________ >> >> >> > dev mailing list >> >> >> > dev@lists.openshift.redhat.com >> >> >> > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> Michael Gugino >> >> >> Senior Software Engineer - OpenShift >> >> >> mgug...@redhat.com >> >> >> 540-846-0304 >> >> > >> >> > >> >> >> >> >> >> >> >> -- >> >> Michael Gugino >> >> Senior Software Engineer - OpenShift >> >> mgug...@redhat.com >> >> 540-846-0304 >> > >> > >> >> >> >> -- >> Michael Gugino >> Senior Software Engineer - OpenShift >> mgug...@redhat.com >> 540-846-0304 > > -- Michael Gugino Senior Software Engineer - OpenShift mgug...@redhat.com 540-846-0304 _______________________________________________ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
