Re: Unable to start openshift in VM, AWS or google cloud

2016-11-03 Thread Cesar Wong 
Looks like we're not displaying the public address after it starts.
However, you should be able to access it at the server's public address:

https://ec2-54-227-129-18.compute-1.amazonaws.com:8443/

On Nov 3, 2016, at 4:23 PM, Ravi Kapoor  wrote:

I tried this, it still starts at private IP address. My logs are copied
below notice that I want to start at 54.227.129.18 but server starts at
https://172.31.32.131:8443

What am I doing wrong?
--

[ec2-user@ip-172-31-32-131 openshift131]$ ./oc cluster up --public-hostname=
ec2-54-227-129-18.compute-1.amazonaws.com --routing-suffix=
54.227.129.18.xip.io --metrics
-- Checking OpenShift client ... OK
-- Checking Docker client ... OK
-- Checking Docker version ... OK
-- Checking for existing OpenShift container ... OK
-- Checking for openshift/origin:v1.3.1 image ... OK
-- Checking Docker daemon configuration ... OK
-- Checking for available ports ... OK
-- Checking type of volume mount ...
   Using nsenter mounter for OpenShift volumes
-- Creating host directories ... OK
-- Finding server IP ...
   Using 172.31.32.131 as the server IP
-- Starting OpenShift container ...
   Creating initial OpenShift configuration
   Starting OpenShift using container 'origin'
   Waiting for API server to start listening
   OpenShift server started
-- Installing registry ... OK
-- Installing router ... OK
-- Install Metrics ... OK
-- Importing image streams ... OK
-- Importing templates ... OK
-- Login to server ... OK
-- Creating initial project "myproject" ... OK
-- Server Information ...
   OpenShift server started.
   The server is accessible via web console at:
   https://172.31.32.131:8443

   The metrics service is available at:
   https://metrics-openshift-infra.54.227.129.18.xip.io

   You are logged in as:
   User: developer
   Password: developer

   To login as administrator:
   oc login -u system:admin


On Thu, Nov 3, 2016 at 9:00 AM, Cesar Wong  wrote:

> Hi Ravi,
>
> On AWS, the magic incantation is:
>
> oc cluster up --public-hostname=[public dns name] --routing-suffix=[ip
> address].xip.io
>
> Don't specify the numeric ip address in --public-hostname, rather the dns
> name.
>
> You can then access the web console at https://[public dns name]:8443/
>
>
> On Windows 7 + VirtualBox + Ubuntu ... is it unable to connect to a route
> because the address/port is not reachable or because the dns name is not
> found?
>
> On Nov 2, 2016, at 9:34 PM, Ravi  wrote:
>
>
> I am not able to start openshift, I tried three different ways.
>
> 1. Windows 7 + Virtual Box + Ubuntu
> oc cluster up works well. I went to console and launched nodejs-ex
> example. Console shows it is up, however when I click on route, it says
> "unable to connect". I tried going directly to POD's IP address and it does
> work. In other words, somehow load balancer was failing in virtualbox
> Ubuntu VM.
>
> 2. Then I moved on to AWS. I launched a RedHat image and installed docker
> and started openshift. Here, OC starts on private IP address, so I am not
> able to access it from public internet. I even tried
> oc cluster up --public-hostname='my ip address' but since the public ip
> address is some magic, oc is not able to detect etcd etc and fails.
>
> 3. Then I tried on google cloud. I faced exactly same issue as AWS.
>
> If any one of them works, I will be ok but no idea how to get past these
> issues.
>
> ___
> 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

Re: Unable to start openshift in VM, AWS or google cloud

2016-11-03 Thread Ravi Kapoor 
> Have you installed a router? Does DNS or /etc/hosts for the route direct
your browser to the host's IP?

my browser is running within the same VM where openshift is starting. Also
it is able to load the console.
The issue is that when I do a deployment, I am not able to access the
route. I am able to ping the route hostname. I am also able to access pods
directly through their individual ip addresses.
Does that help?



On Thu, Nov 3, 2016 at 8:54 AM, Luke Meyer  wrote:

>
>
> On Wed, Nov 2, 2016 at 11:34 PM, Ravi  wrote:
>
>>
>> I am not able to start openshift, I tried three different ways.
>>
>> 1. Windows 7 + Virtual Box + Ubuntu
>> oc cluster up works well. I went to console and launched nodejs-ex
>> example. Console shows it is up, however when I click on route, it says
>> "unable to connect". I tried going directly to POD's IP address and it does
>> work. In other words, somehow load balancer was failing in virtualbox
>> Ubuntu VM.
>>
>
> Have you installed a router? Does DNS or /etc/hosts for the route direct
> your browser to the host's IP?
>
>
>>
>> 2. Then I moved on to AWS. I launched a RedHat image and installed docker
>> and started openshift. Here, OC starts on private IP address, so I am not
>> able to access it from public internet. I even tried
>> oc cluster up --public-hostname='my ip address' but since the public ip
>> address is some magic, oc is not able to detect etcd etc and fails.
>>
>> 3. Then I tried on google cloud. I faced exactly same issue as AWS.
>>
>> If any one of them works, I will be ok but no idea how to get past these
>> issues.
>>
>> ___
>> 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

Re: Unable to start openshift in VM, AWS or google cloud

2016-11-03 Thread Ravi Kapoor 
I tried this, it still starts at private IP address. My logs are copied
below notice that I want to start at 54.227.129.18 but server starts at
https://172.31.32.131:8443

What am I doing wrong?
--

[ec2-user@ip-172-31-32-131 openshift131]$ ./oc cluster up --public-hostname=
ec2-54-227-129-18.compute-1.amazonaws.com --routing-suffix=
54.227.129.18.xip.io --metrics
-- Checking OpenShift client ... OK
-- Checking Docker client ... OK
-- Checking Docker version ... OK
-- Checking for existing OpenShift container ... OK
-- Checking for openshift/origin:v1.3.1 image ... OK
-- Checking Docker daemon configuration ... OK
-- Checking for available ports ... OK
-- Checking type of volume mount ...
   Using nsenter mounter for OpenShift volumes
-- Creating host directories ... OK
-- Finding server IP ...
   Using 172.31.32.131 as the server IP
-- Starting OpenShift container ...
   Creating initial OpenShift configuration
   Starting OpenShift using container 'origin'
   Waiting for API server to start listening
   OpenShift server started
-- Installing registry ... OK
-- Installing router ... OK
-- Install Metrics ... OK
-- Importing image streams ... OK
-- Importing templates ... OK
-- Login to server ... OK
-- Creating initial project "myproject" ... OK
-- Server Information ...
   OpenShift server started.
   The server is accessible via web console at:
   https://172.31.32.131:8443

   The metrics service is available at:
   https://metrics-openshift-infra.54.227.129.18.xip.io

   You are logged in as:
   User: developer
   Password: developer

   To login as administrator:
   oc login -u system:admin


On Thu, Nov 3, 2016 at 9:00 AM, Cesar Wong  wrote:

> Hi Ravi,
>
> On AWS, the magic incantation is:
>
> oc cluster up --public-hostname=[public dns name] --routing-suffix=[ip
> address].xip.io
>
> Don't specify the numeric ip address in --public-hostname, rather the dns
> name.
>
> You can then access the web console at https://[public dns name]:8443/
>
>
> On Windows 7 + VirtualBox + Ubuntu ... is it unable to connect to a route
> because the address/port is not reachable or because the dns name is not
> found?
>
> On Nov 2, 2016, at 9:34 PM, Ravi  wrote:
>
>
> I am not able to start openshift, I tried three different ways.
>
> 1. Windows 7 + Virtual Box + Ubuntu
> oc cluster up works well. I went to console and launched nodejs-ex
> example. Console shows it is up, however when I click on route, it says
> "unable to connect". I tried going directly to POD's IP address and it does
> work. In other words, somehow load balancer was failing in virtualbox
> Ubuntu VM.
>
> 2. Then I moved on to AWS. I launched a RedHat image and installed docker
> and started openshift. Here, OC starts on private IP address, so I am not
> able to access it from public internet. I even tried
> oc cluster up --public-hostname='my ip address' but since the public ip
> address is some magic, oc is not able to detect etcd etc and fails.
>
> 3. Then I tried on google cloud. I faced exactly same issue as AWS.
>
> If any one of them works, I will be ok but no idea how to get past these
> issues.
>
> ___
> 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

Re: Unable to start openshift in VM, AWS or google cloud

2016-11-03 Thread Cesar Wong 
Hi Ravi,

On AWS, the magic incantation is:

oc cluster up --public-hostname=[public dns name] --routing-suffix=[ip 
address].xip.io 

Don't specify the numeric ip address in --public-hostname, rather the dns name.

You can then access the web console at https://[public  dns 
name]:8443/


On Windows 7 + VirtualBox + Ubuntu ... is it unable to connect to a route 
because the address/port is not reachable or because the dns name is not found?

> On Nov 2, 2016, at 9:34 PM, Ravi  wrote:
> 
> 
> I am not able to start openshift, I tried three different ways.
> 
> 1. Windows 7 + Virtual Box + Ubuntu
> oc cluster up works well. I went to console and launched nodejs-ex example. 
> Console shows it is up, however when I click on route, it says "unable to 
> connect". I tried going directly to POD's IP address and it does work. In 
> other words, somehow load balancer was failing in virtualbox Ubuntu VM.
> 
> 2. Then I moved on to AWS. I launched a RedHat image and installed docker and 
> started openshift. Here, OC starts on private IP address, so I am not able to 
> access it from public internet. I even tried
> oc cluster up --public-hostname='my ip address' but since the public ip 
> address is some magic, oc is not able to detect etcd etc and fails.
> 
> 3. Then I tried on google cloud. I faced exactly same issue as AWS.
> 
> If any one of them works, I will be ok but no idea how to get past these 
> issues.
> 
> ___
> 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

Re: Unable to start openshift in VM, AWS or google cloud

2016-11-03 Thread Luke Meyer 
On Wed, Nov 2, 2016 at 11:34 PM, Ravi  wrote:

>
> I am not able to start openshift, I tried three different ways.
>
> 1. Windows 7 + Virtual Box + Ubuntu
> oc cluster up works well. I went to console and launched nodejs-ex
> example. Console shows it is up, however when I click on route, it says
> "unable to connect". I tried going directly to POD's IP address and it does
> work. In other words, somehow load balancer was failing in virtualbox
> Ubuntu VM.
>

Have you installed a router? Does DNS or /etc/hosts for the route direct
your browser to the host's IP?


>
> 2. Then I moved on to AWS. I launched a RedHat image and installed docker
> and started openshift. Here, OC starts on private IP address, so I am not
> able to access it from public internet. I even tried
> oc cluster up --public-hostname='my ip address' but since the public ip
> address is some magic, oc is not able to detect etcd etc and fails.
>
> 3. Then I tried on google cloud. I faced exactly same issue as AWS.
>
> If any one of them works, I will be ok but no idea how to get past these
> issues.
>
> ___
> 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