Re: How to use DNS hostname of OpenShift on AWS

[Roland Lichti]

Hi Joel,

kubernetes is using the AWS inventory information directly as soon as it
detects the AWS cloud. Until now I did not find any solution to get to nice
hostnames.

Instead we label the "nice name" as "host" (oc label node  host=abc)
and use "oc get node -L host" to get the names listed.


2018-02-21 13:13 GMT+01:00 Joel Pearson <japear...@agiledigital.com.au>:

> Hi,
>
> I'm trying to figure out how to use the DNS hostname when deploying
> OpenShift on AWS using https://github.com/openshift/openshift-ansible-
> contrib/tree/master/reference-architecture/aws-ansible Currently it uses
> private dns name, eg, ip-10-2-7-121.ap-southeast-2.compute.internal but
> that isn't too useful a name for me.  I've managed to set the hostname on
> the ec2 instance properly but disabling the relevant cloud-init setting,
> but it still grabs the private dns name somehow.
>
> I tried adding "openshift_hostname" to be the same as "name" on this line:
> https://github.com/openshift/openshift-ansible-
> contrib/blob/master/reference-architecture/aws-ansible/
> playbooks/roles/instance-groups/tasks/main.yaml#L11
>
> Which did set the hostname in the node-config.yaml, but then when running
> "oc get nodes" it still returned the private dns name somehow, and
> installation failed waiting for the nodes to start properly, I guess a
> mismatch between node names somewhere.
>
> I found an old github issue, but it's all referring to files in ansible
> that exist no longer:
> https://github.com/openshift/openshift-ansible/issues/1170
>
> Even on OpenShift Online Starter, they're using the default ec2 names,
> eg: ip-172-31-28-11.ca-central-1.compute.internal, which isn't a good
> sign I guess.
>
> Has anyone successfully used a DNS name for OpenShift on AWS?
>
> Thanks,
>
> Joel
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>


-- 
Mit freundlichen Grüßen / Kind Regards,

Roland T. Lichti

Red Hat Ambassador | Senior Middleware Consultant

Red Hat GmbH

Technopark II

Werner-von-Siemens-Ring 14, 85630 Grasbrunn

rlic...@redhat.com M: +49-172-6328604

www.redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted


Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael
O'Neill, Eric Shander
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: How to use DNS hostname of OpenShift on AWS

[Joel Pearson]

Michael are you running OpenShift on AWS?

https://github.com/openshift/openshift-ansible-contrib/tree/master/reference-architecture/aws-ansible
is the AWS reference architecture and it does use openshift-ansible once
the infrastructure is built, but it uses a dynamic inventory.

It’s not an option for us not to use the aws reference architecture to
install OpenShift as it would be rather painful as we’re relying heavily on
cloud formation and the dynamic inventory.

While ansible is running the hostnames are correct, so I’m suspecting that
maybe OpenShift itself is detecting the cloud provider and overriding the
hostname or maybe the ansible playbook is doing something similar. Inside
the ansible openshift_facts python library I saw some custom hostname
handling for Google Cloud, but not for AWS, but it made me suspicious
thinking it might be hiding somewhere else.
On Wed, 21 Feb 2018 at 11:38 pm, Feld, Michael (IMS) <fe...@imsweb.com>
wrote:

> Deploying with https://github.com/openshift/openshift-ansible you can
> define the hostnames in your inventory file. There is a sample inventory
> file at
> https://docs.openshift.org/latest/install_config/install/advanced_install.html
> that shows how to define the master/etcd/nodes, and those names should be
> used as the hostnames in the cluster.
>
>
>
> *From:* users-boun...@lists.openshift.redhat.com [mailto:
> users-boun...@lists.openshift.redhat.com] *On Behalf Of *Joel Pearson
> *Sent:* Wednesday, February 21, 2018 7:14 AM
> *To:* users <users@lists.openshift.redhat.com>
> *Subject:* How to use DNS hostname of OpenShift on AWS
>
>
>
> Hi,
>
>
>
> I'm trying to figure out how to use the DNS hostname when deploying
> OpenShift on AWS using
> https://github.com/openshift/openshift-ansible-contrib/tree/master/reference-architecture/aws-ansible
>  Currently
> it uses private dns name, eg, ip-10-2-7-121.ap-southeast-2.compute.internal
> but that isn't too useful a name for me.  I've managed to set the hostname
> on the ec2 instance properly but disabling the relevant cloud-init setting,
> but it still grabs the private dns name somehow.
>
>
>
> I tried adding "openshift_hostname" to be the same as "name" on this line:
> https://github.com/openshift/openshift-ansible-contrib/blob/master/reference-architecture/aws-ansible/playbooks/roles/instance-groups/tasks/main.yaml#L11
>
>
>
> Which did set the hostname in the node-config.yaml, but then when running
> "oc get nodes" it still returned the private dns name somehow, and
> installation failed waiting for the nodes to start properly, I guess a
> mismatch between node names somewhere.
>
>
>
> I found an old github issue, but it's all referring to files in ansible
> that exist no longer:
>
> https://github.com/openshift/openshift-ansible/issues/1170
>
>
>
> Even on OpenShift Online Starter, they're using the default ec2 names,
> eg: ip-172-31-28-11.ca-central-1.compute.internal, which isn't a good sign
> I guess.
>
>
>
> Has anyone successfully used a DNS name for OpenShift on AWS?
>
>
>
> Thanks,
>
>
>
> Joel
>
> --
>
> Information in this e-mail may be confidential. It is intended only for
> the addressee(s) identified above. If you are not the addressee(s), or an
> employee or agent of the addressee(s), please note that any dissemination,
> distribution, or copying of this communication is strictly prohibited. If
> you have received this e-mail in error, please notify the sender of the
> error.
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

RE: How to use DNS hostname of OpenShift on AWS

[Feld, Michael (IMS)]

Deploying with https://github.com/openshift/openshift-ansible you can define 
the hostnames in your inventory file. There is a sample inventory file at 
https://docs.openshift.org/latest/install_config/install/advanced_install.html 
that shows how to define the master/etcd/nodes, and those names should be used 
as the hostnames in the cluster.

From: users-boun...@lists.openshift.redhat.com 
[mailto:users-boun...@lists.openshift.redhat.com] On Behalf Of Joel Pearson
Sent: Wednesday, February 21, 2018 7:14 AM
To: users <users@lists.openshift.redhat.com>
Subject: How to use DNS hostname of OpenShift on AWS

Hi,

I'm trying to figure out how to use the DNS hostname when deploying OpenShift 
on AWS using 
https://github.com/openshift/openshift-ansible-contrib/tree/master/reference-architecture/aws-ansible
 Currently it uses private dns name, eg, 
ip-10-2-7-121.ap-southeast-2.compute.internal but that isn't too useful a name 
for me.  I've managed to set the hostname on the ec2 instance properly but 
disabling the relevant cloud-init setting, but it still grabs the private dns 
name somehow.

I tried adding "openshift_hostname" to be the same as "name" on this line: 
https://github.com/openshift/openshift-ansible-contrib/blob/master/reference-architecture/aws-ansible/playbooks/roles/instance-groups/tasks/main.yaml#L11

Which did set the hostname in the node-config.yaml, but then when running "oc 
get nodes" it still returned the private dns name somehow, and installation 
failed waiting for the nodes to start properly, I guess a mismatch between node 
names somewhere.

I found an old github issue, but it's all referring to files in ansible that 
exist no longer:
https://github.com/openshift/openshift-ansible/issues/1170

Even on OpenShift Online Starter, they're using the default ec2 names, eg: 
ip-172-31-28-11.ca-central-1.compute.internal, which isn't a good sign I guess.

Has anyone successfully used a DNS name for OpenShift on AWS?

Thanks,

Joel



Information in this e-mail may be confidential. It is intended only for the 
addressee(s) identified above. If you are not the addressee(s), or an employee 
or agent of the addressee(s), please note that any dissemination, distribution, 
or copying of this communication is strictly prohibited. If you have received 
this e-mail in error, please notify the sender of the error.
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

How to use DNS hostname of OpenShift on AWS

[Joel Pearson]

Hi,

I'm trying to figure out how to use the DNS hostname when deploying
OpenShift on AWS using
https://github.com/openshift/openshift-ansible-contrib/tree/master/reference-architecture/aws-ansible
Currently
it uses private dns name, eg, ip-10-2-7-121.ap-southeast-2.compute.internal
but that isn't too useful a name for me.  I've managed to set the hostname
on the ec2 instance properly but disabling the relevant cloud-init setting,
but it still grabs the private dns name somehow.

I tried adding "openshift_hostname" to be the same as "name" on this line:
https://github.com/openshift/openshift-ansible-contrib/blob/master/reference-architecture/aws-ansible/playbooks/roles/instance-groups/tasks/main.yaml#L11

Which did set the hostname in the node-config.yaml, but then when running
"oc get nodes" it still returned the private dns name somehow, and
installation failed waiting for the nodes to start properly, I guess a
mismatch between node names somewhere.

I found an old github issue, but it's all referring to files in ansible
that exist no longer:
https://github.com/openshift/openshift-ansible/issues/1170

Even on OpenShift Online Starter, they're using the default ec2 names,
eg: ip-172-31-28-11.ca-central-1.compute.internal, which isn't a good sign
I guess.

Has anyone successfully used a DNS name for OpenShift on AWS?

Thanks,

Joel
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Openshift on AWS using Terraform

[Walters, Todd]

Hello Krzysztof,

We started with this guide  https://github.com/dwmkerr/terraform-aws-openshift 
to  install on aws. We have since broken a lot of it out into separate modules 
and modified it as needed, but it was a decent starting point.

Thanks,

Todd


The information contained in this message, and any attachments thereto,
is intended solely for the use of the addressee(s) and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination, copying, or other use of the transmitted information is
prohibited. If you received this in error, please contact the sender
and delete the material from any computer. UNIGROUP.COM


___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: OpenShift on AWS using Terraform

[Joel Pearson]

If you’re ok with CloudFormation then these ansible scripts can do that
https://github.com/openshift/openshift-ansible-contrib/tree/master/reference-architecture/aws-ansible
On Sun, 31 Dec 2017 at 4:46 am, Krzysztof Sobkowiak <
krzys.sobkow...@gmail.com> wrote:

> Hi
>
> I'd like to provision an OpenShift HA cluster on AWS. I'm wondering, if I
> can find somewhere Terraform scripts which can be used to initially
> provision the infrastructure on AWS (bastion, masters, nodes,
> infranodes,...)
> Do you know such solution?
>
> Kindly regards
> Krzysztof
>
>
> --
> Krzysztof Sobkowiak (@ksobkowiak)
>
> JEE & OSS Architect, Integration Architect
> Apache Software Foundation Member (http://apache.org/)
> Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
> Senior Delivery Architect @ Capgemini SSC (
> http://www.capgeminisoftware.pl/)
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

OpenShift on AWS using Terraform

[Krzysztof Sobkowiak]

Hi

I'd like to provision an OpenShift HA cluster on AWS. I'm wondering, if I can 
find somewhere Terraform scripts which can be used to initially provision the 
infrastructure on AWS (bastion, masters, nodes, infranodes,...) 
Do you know such solution?

Kindly regards
Krzysztof


-- 
Krzysztof Sobkowiak (@ksobkowiak)

JEE & OSS Architect, Integration Architect
Apache Software Foundation Member (http://apache.org/)
Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
Senior Delivery Architect @ Capgemini SSC (http://www.capgeminisoftware.pl/)
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Openshift on AWS regions with 2 AZs

[Isaac Christoffersen]

With the ETCD quorum dependency (
https://coreos.com/etcd/docs/latest/faq.html), I don't see a how one could
do this.  The probability of losing an AZ is probably low, but in the event
that it does happen, you have the possibility to lose more than 50% of the
quorum members.



Isaac Christoffersen
Technical Director, Vizuri
Office: (703) 318-7800 x8202 | Mobile: (571) 510-5029
ichristoffer...@vizuri.com

13880 Dulles Corner Lane, Suite 300
Herndon, VA 20171




On Wed, Nov 1, 2017 at 10:16 PM, Behnam Marandi <bmara...@noggin.io> wrote:

> That's right but some AWS regions just have two AZs. Trying to find a way
> to install Openshift in that regions.
>
> On Thu, Nov 2, 2017 at 12:30 PM, Isaac Christoffersen <
> ichristoffer...@vizuri.com> wrote:
>
>> Three AZs with one master and infra node in each is better.  Particularly
>> if the master is also an etcd node.
>>
>> On Nov 1, 2017 20:41, "Behnam Marandi" <bmara...@noggin.io> wrote:
>>
>>> Hi,
>>> Is there a method to install Openshift on AWS regions which just have
>>> two Availability Zones? Like installing 2 Master nodes one one AZ and
>>> another one on the other.
>>>
>>> ___
>>> users mailing list
>>> users@lists.openshift.redhat.com
>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>>
>>>
>
>
> --
> [image: Noggin IT Logo]
> <http://www.noggin.io?utm_source=Email-Signature_medium=Email-Signature_campaign=Email-Signature?utm_source=Email-Signature-Rescue_medium=Email-Signature_campaign=Email-Signature-Rescue>
> Behnam Marandi • DevOps Engineer
> Noggin IT
> e bmara...@noggin.io w www.noggin.io
> <http://www.noggin.io?utm_source=Email-Signature_medium=Email-Signature_campaign=Email-Signature?utm_source=Email-Signature-Rescue_medium=Email-Signature_campaign=Email-Signature-Rescue>
> a Level 22, 175 Liverpool Street, Sydney, NSW, Australia
> <https://maps.google.com/?q=Level+22,+175+Liverpool+Street,+Sydney,+NSW,+Australia=gmail=g>,
> 2000
> [image: Facebook] <http://www.facebook.com/nogginIT> [image: Twitter]
> <http://www.twitter.com/nogginoca> [image: Linkedin]
> <http://www.linkedin.com/company/noggin-it> [image: Were Hiring]
> <http://www.noggin.io/job-board>
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Openshift on AWS regions with 2 AZs

[Behnam Marandi]

That's right but some AWS regions just have two AZs. Trying to find a way
to install Openshift in that regions.

On Thu, Nov 2, 2017 at 12:30 PM, Isaac Christoffersen <
ichristoffer...@vizuri.com> wrote:

> Three AZs with one master and infra node in each is better.  Particularly
> if the master is also an etcd node.
>
> On Nov 1, 2017 20:41, "Behnam Marandi" <bmara...@noggin.io> wrote:
>
>> Hi,
>> Is there a method to install Openshift on AWS regions which just have two
>> Availability Zones? Like installing 2 Master nodes one one AZ and another
>> one on the other.
>>
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>>


-- 
[image: Noggin IT Logo]
<http://www.noggin.io?utm_source=Email-Signature_medium=Email-Signature_campaign=Email-Signature?utm_source=Email-Signature-Rescue_medium=Email-Signature_campaign=Email-Signature-Rescue>
Behnam Marandi • DevOps Engineer
Noggin IT
e bmara...@noggin.io w www.noggin.io
<http://www.noggin.io?utm_source=Email-Signature_medium=Email-Signature_campaign=Email-Signature?utm_source=Email-Signature-Rescue_medium=Email-Signature_campaign=Email-Signature-Rescue>
a Level 22, 175 Liverpool Street, Sydney, NSW, Australia, 2000
[image: Facebook] <http://www.facebook.com/nogginIT> [image: Twitter]
<http://www.twitter.com/nogginoca> [image: Linkedin]
<http://www.linkedin.com/company/noggin-it> [image: Were Hiring]
<http://www.noggin.io/job-board>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Openshift on AWS regions with 2 AZs

[Isaac Christoffersen]

Three AZs with one master and infra node in each is better.  Particularly
if the master is also an etcd node.

On Nov 1, 2017 20:41, "Behnam Marandi" <bmara...@noggin.io> wrote:

> Hi,
> Is there a method to install Openshift on AWS regions which just have two
> Availability Zones? Like installing 2 Master nodes one one AZ and another
> one on the other.
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Openshift on AWS regions with 2 AZs

[Behnam Marandi]

Hi,
Is there a method to install Openshift on AWS regions which just have two
Availability Zones? Like installing 2 Master nodes one one AZ and another
one on the other.
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: OpenShift on AWS - Playbooks

[Tobias Brunner]

On 26.10.2017 15:23, Clayton Coleman wrote:
> The latter is still being actively developed - that will be the future
> direction but is not yet ready for genera use.  Our work towards
> leveraging node bootstrapping and using pre-baked AMIs is also not
> completely finalized, so no expectation of stability on the latter.

Thanks for the clarification! We'll have a deeper look at the
"playbooks/aws" stuff... Maybe we can help to bring it forward!



signature.asc
Description: OpenPGP digital signature
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: OpenShift on AWS - Playbooks

[Clayton Coleman]

The latter is still being actively developed - that will be the future
direction but is not yet ready for genera use.  Our work towards
leveraging node bootstrapping and using pre-baked AMIs is also not
completely finalized, so no expectation of stability on the latter.

> On Oct 26, 2017, at 9:18 AM, Tobias Brunner <tob...@tobru.ch> wrote:
>
> Hi,
>
> There are at least two different "official" approaches to get OpenShift
> on AWS up and running:
>
> 1.
> https://github.com/openshift/openshift-ansible-contrib/tree/master/reference-architecture/aws-ansible
> 2. https://github.com/openshift/openshift-ansible/tree/master/playbooks/aws
>
> Which one of these two should we chose to get startet and have a
> maintained version? We're commited to contribute, but it's unclear which
> one we should use...
>
> Best,
> Tobias
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

OpenShift on AWS - Playbooks

[Tobias Brunner]

Hi,

There are at least two different "official" approaches to get OpenShift
on AWS up and running:

1.
https://github.com/openshift/openshift-ansible-contrib/tree/master/reference-architecture/aws-ansible
2. https://github.com/openshift/openshift-ansible/tree/master/playbooks/aws

Which one of these two should we chose to get startet and have a
maintained version? We're commited to contribute, but it's unclear which
one we should use...

Best,
Tobias



signature.asc
Description: OpenPGP digital signature
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: OpenShift and AWS

[Jason DeTiberus]

On Tue, Feb 2, 2016 at 10:32 AM, Lorenz Vanthillo <
lorenz.vanthi...@outlook.com> 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:
>
> Infra
> node instances:
>
>- export ec2_infra_instance_type='m4.large'
>
>
> 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
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>


-- 
Jason DeTiberus
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

OpenShift and AWS

[Lorenz Vanthillo]

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?
- I saw:
Infra node instances:

export ec2_infra_instance_type='m4.large'

Non-infra node instances:

export ec2_node_instance_type='m4.large'


What is the difference between infra nodes and non-infra nodes?


Thanks


  ___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users