For 3.7 and below, you need to do some manual preparation steps and
then the playbook you want to run is:
openshift-ansible/playbooks/byo/config.yml
Prerequisites:
https://docs.openshift.org/latest/install_config/install/prerequisites.html
Host prep:
I see from your github repo that you use playbook committed under master
branch
as you use these commands to install ocp
ansible-playbook -i inventory/hosts.localhost playbooks/prerequisites.yml
ansible-playbook -i inventory/hosts.localhost playbooks/deploy_cluster.yml
Unfortunately that fails
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
On Fri, Mar 16, 2018 at 8:57 PM, Michael Gugino 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
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). Alternatively, you can install the
openshift-ansible origin rpm on a centos host.
I don't recommend using
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
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 wrote:
> Yep. I did a mistake but I have
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
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
It's there, in both the origin39-testing area (which isn't getting
used), as well as the origin-testing area (which is getting used),
https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin39/origin-sdn-ovs-3.9.0-0.alpha.4.el7.git.23454.881f1dd.x86_64.rpm
It seems that a rpm is missing for origin-sdn when we run openshift-ansible
3.7
TASK [openshift_node : Install sdn-ovs package]
On Fri, Mar 16, 2018 at 8:32 AM, Charles Moulliard 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
>
>
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
Hi,
It seems that v3.8.0[1] has been released 3 days ago but
I am not able to find its artifacts.
Is there any issue during artifact uploads?
[1] https://github.com/openshift/origin/releases/tag/v3.8.0
Regards,
Budh Ram Gurung
___
dev mailing list
14 matches
Mail list logo