On Tue, Feb 2, 2016 at 10:32 AM, Lorenz Vanthillo < [email protected]> wrote:
> I was taking a look at > https://github.com/openshift/openshift-ansible/blob/master/README_AWS.md > > I've 2 questions about it. > - For having ETCD you really need a new EC2-instance? (Does it need > configuration or is it enough to describe it in the inventory file? > The README_AWS.md file is specifically for using the bin/cluster script (un-official and community supported) for provisioning ec2 instances. To use the external etcd (and subsequently the multi-master capabilities of it, it would indeed require etcd have it's own host). The best supported method of deploying currently is to use the "byo" playbooks and a user-defined inventory file as documented here: https://docs.openshift.org/latest/install_config/install/advanced_install.html - I saw: > > <https://github.com/openshift/openshift-ansible/blob/master/README_AWS.md#infra-node-instances>Infra > node instances: > > - export ec2_infra_instance_type='m4.large' > > > <https://github.com/openshift/openshift-ansible/blob/master/README_AWS.md#non-infra-node-instances>Non-infra > node instances: > > - export ec2_node_instance_type='m4.large' > > > > > What is the difference between infra nodes and non-infra nodes? > Infra nodes are meant to be used for deploying OpenShift cluster infrastructure services (currently consisting of the router and registry, but will also include the log aggregation and metrics components as well). The non-infra nodes are meant for hosting general applications. > > > Thanks > > > > _______________________________________________ > users mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > > -- Jason DeTiberus
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
