Install fabric8 on Windows with vagrant - step by step guide

[davsclaus]

From the mailing list we got a step by step guide how to install fabric8 on a windows 7 pc. There seems to be many steps.

Wonder if we can cut down on this and get to a simpler way. Logging a ticket here to not lose out of this great detail how to get working on windows.

The information shared in the blog post is great! and there are other blog posts introducing Kubernetes... I will definitely take a look

For the next step I will head back to study your "Camel in action" book and then will try to deploy my own Camel apps in fabric8 before I jump further on platform side stuff related to Docker, Kubernetes clustering... etc.

Lastly, I recap the steps I have done to make the vagrant vm run on my Win7 PC and start the quickstart camel-spring app in there. I think a consolidated guide with steps from end-to-end would be easier for beginners (like me)

Setup fabric8 vagrant image (v2.1.11) on Win7 PC and run quickstart camel-spring project:
1) Install the latest version of VirtualBox from https://www.virtualbox.org/
2) Install the latest version of vagrant from https://www.vagrantup.com/
3) Download the latest fabric8 release (2.1.11) source code zip from github https://github.com/fabric8io/fabric8/releases

3.1) Add the following environment variables in windows (Control Panel > System > Advanced System Settings > Environment Variables > System Variables):
 KUBERNETES_MASTER=https://172.28.128.4:8443
 KUBERNETES_DOMAIN=vagrant.local
 KUBERNETES_NAMESPACE=default
 KUBERNETES_TRUST_CERT=true
 DOCKER_HOST=tcp://vagrant.local:2375
3.2) add the following entry in Win7 host file
172.28.128.4 kubernetes.default.local vagrant.local fabric8.vagrant.local fabric8-master.vagrant.local docker-registry.vagrant.local gogs.vagrant.local nexus.vagrant.local jenkins.vagrant.local

4) Follow the below steps to startup vagrant vm (reference: http://fabric8.io/guide/openShiftWithFabric8Vagrant.html)
4.1) Open win7 command prompt, go to fabric8 source code directory (in which the file "VagrantFile" is located), type "vagrant up"... wait until loading finish
P.S "vagrant up" will startup a virtualbox Fabric8 VM according to the config in VagrantFile in Fabric8 source code
P.S. to Stop vagrant VM, type "vagrant halt" in win7 command prompt

4.2) in the same directory, type "vagrant ssh", the command prompt will transform into a linux-alike shell
4.3) type "osc login --server=http://172.28.128.4:8443" (login with admin/admin)
4.4) type "osc get pods", "sudo journalctl -u openshift" , "sudo journalctl -fu docker" to verify Kubernetes pods and openshift or docker log files
P.S to tail openshift log: "sudo journalctl -fu openshift"
P.S to tail docker log: "sudo journalctl -fu docker"

5) Now a VM with Openshift, Docker, Kubernetes and Fabric8 is running

6) Download Openshift 0.5.1 or later (the "openshift-origin-...-windows-...zip" file) from https://github.com/openshift/origin/releases/
7) Unzip the files to whatever directory. Add this directory into Path environment variable
8) Open another win7 command prompt, type "osc login --server=https://172.28.128.4:8443" (login with admin/admin)

9) Download the latest fabric8 quickstart release source code zip from https://github.com/fabric8io/quickstarts/releases
10) Unzip the source code to whatever directory, then go to <directory>\quickstarts\java\camel-spring folder
e.g. cd D:\Download\JbossFuse\quickstarts-project-2.1.11\quickstarts\java\camel-spring
11) Make sure your PC is using Maven 3.2.5 or later, run "mvn install docker:build fabric8:json fabric8:apply"
*** In case SSL Cert exception found during maven build... make sure env variable KUBERNETES_TRUST_CERT=true is there

12) To run the camel-spring quick start app, go to vagrant ssh shell, type "docker run -itP fabric8/quickstart-java-camel-spring:2.1.11"
P.S. "fabric8/quickstart-java-camel-spring:2.1.11" is the docker image name, might varies depending on release version

13) Type "docker ps" in vagrant ssh shell to list all available containers and images with status

14) To check the camel-spring runtime status through hawtio console:
14.1) Open browser and browse http://fabric8.vagrant.local, OpenShift Origin screen should appear. login with admin/admin
14.2) In case error found (e.g. 503 service unavailable), run the following command in win7 command prompt
"osc login --server=https://172.28.128.4:8443" (login with admin/admin)
"osc project default"  
"mvn io.fabric8:fabric8-maven-plugin:2.1.11:create-routes"
14.3) run "osc get routes", you should see the following entries
NAME                    HOST/PORT                       PATH      SERVICE           LABELS
docker-registry         docker-registry.vagrant.local             docker-registry
docker-registry-route   docker-registry.vagrant.local             docker-registry
elasticsearch           elasticsearch.vagrant.local               elasticsearch
fabric8                 fabric8.vagrant.local                     fabric8
influxdb                influxdb.vagrant.local                    influxdb
kibana                  kibana.vagrant.local                      kibana
router                  router.vagrant.local                      router

14.4) Browse http://fabric8.vagrant.local again. Openshift login screen will be shown, login with admin/admin
14.5) In hawtio console, scroll down and find the app "quickstart-java-camel-spring", click the arrow icon with 
popup tag "Open a new window and connect to this container"
14.6) The camel page for the quickstart project should be shown. Check the route diagram and profile for the runtime status

15) To stop the camel-spring quick start app, type "docker stop <container id>" in vagrant ssh shell
where <container id> can be obtained from the first column of "docker ps |grep quickstart"

[stevef1uk]

This helped me progress on my mac. A couple of comments:

1. https://github.com/fabric8io/quickstarts/releases - I need to drop the releases directory
2. No mention of setting up your settings.xml for mvn (on a mac in ~/.ssh). I added the lines from here: http://fabric8.io/gitbook/mavenPlugin.html e.g. add this to the element:

fabric8.upload.repo admin admin

I am not sure is that is still correct because although I built the quickstart using 'mvn install docker:build fabric8:json fabric8:apply' I got the error: [WARNING] Could not load routes; we maybe are not connected to an OpenShift environment? javax.ws.rs.WebApplicationException: HTTP 403 User "system:anonymous" cannot list routes in project "default" javax.ws.rs.WebApplicationException: HTTP 403 User "system:anonymous" cannot list routes in project "default" at io.fabric8.kubernetes.api.ExceptionResponseMapper.fromResponse(ExceptionResponseMapper.java:25)

[ERROR] Failed to execute goal io.fabric8:fabric8-maven-plugin:2.2.0:apply (default-cli) on project quickstart-java-camel-spring: HTTP 403 User "system:anonymous" cannot list replicationcontrollers in project "default" -> [Help 1] I then switched to https://github.com/fabric8io/fabric8-installer and followed the instructions to build the base app which worked. After running the quickstart-java-camel-spring docker image I was unable to access the hawtio console on Firefox due to the error: Secure Connection Failed An error occurred during a connection to fabric8.vagrant.local:8443. security library: improperly formatted DER-encoded message. (Error code: sec_error_bad_der) Safari gives me the option of accepting the certificate and I get the Openshift console up :-)

[christian-posta]

be careful mixing versions of the environment (that from 2.1.11, which uses v1beta3 api, and that from 2.2.0 which uses v1 API)... might want to start using the Vagrant image from here now: https://github.com/fabric8io/fabric8-installer/tree/master/vagrant

On Wed, Jun 17, 2015 at 12:33 PM, stevef1uk notifications@github.com wrote:

This helped me progress on my mac. A couple of comments:

1. https://github.com/fabric8io/quickstarts/releases - I need to drop the releases directory
2. No mention of setting up your settings.xml for mvn (on a mac in ~/.ssh). I added the lines from here: http://fabric8.io/gitbook/mavenPlugin.html e.g. add this to the element:

fabric8.upload.repo admin admin

I am not sure is that is still correct because although I built the quickstart using 'mvn install docker:build fabric8:json fabric8:apply' I got the error: [WARNING] Could not load routes; we maybe are not connected to an OpenShift environment? javax.ws.rs.WebApplicationException: HTTP 403 User "system:anonymous" cannot list routes in project "default" javax.ws.rs.WebApplicationException: HTTP 403 User "system:anonymous" cannot list routes in project "default" at io.fabric8.kubernetes.api.ExceptionResponseMapper.fromResponse(ExceptionResponseMapper.java:25)

[ERROR] Failed to execute goal io.fabric8:fabric8-maven-plugin:2.2.0:apply (default-cli) on project quickstart-java-camel-spring: HTTP 403 User "system:anonymous" cannot list replicationcontrollers in project "default" -> [Help 1]

I then switched to https://github.com/fabric8io/fabric8-installer and followed the instructions to build the base app which worked.

After running the quickstart-java-camel-spring docker image I was unable to access the hawtio console on Firefox due to the error: Secure Connection Failed An error occurred during a connection to fabric8.vagrant.local:8443. security library: improperly formatted DER-encoded message. (Error code: sec_error_bad_der)

Safari gives me the option of accepting the certificate and I get the Openshift console up :-)

— Reply to this email directly or view it on GitHub https://github.com/fabric8io/fabric8/issues/4198#issuecomment-112921873.

Christian Posta twitter: @christianposta http://www.christianposta.com/blog http://fabric8.io

[stevef1uk]

Thanks. Switched. Any idea why when running the console nothing appears under any of the tabs?

[davsclaus]

The web browser has a console log where you can likely see a bit more details.

[jstrachan]

I've tried to create a cleaner all in one page that's easier (and the vagrant image does most of the work now too)....

http://fabric8.io/guide/getStartedVagrant.html

So the user just needs to install the OpenShift binaries to use the CLI and some env vars; vagrant does the rest

[jimmidyson]

You don't really need many of the env vars now as long as you do an oc login the kube client used in the maven plugin will use settings from the kube config file. I'll add this to the documentation when I get a chance.

On 09:37, Sat, 20 Jun 2015 James Strachan notifications@github.com wrote:

I've tried to create a cleaner all in one page that's easier (and the vagrant image does most of the work now too)....

d24eb2a https://github.com/fabric8io/fabric8/commit/d24eb2afb5457f162d1d772344c010d32e037082

So the user just needs to install the OpenShift binaries to use the CLI and some env vars; vagrant does the rest

— Reply to this email directly or view it on GitHub https://github.com/fabric8io/fabric8/issues/4198#issuecomment-113730287.

[davsclaus]

Oh lovely @jimmidyson - wonder if we should have some way of outputting to the end user what options are in use, eg sometimes you dont know which docker repoistory is used, which namespace, kubernetes master etc.

Is there something oc can do?

[jimmidyson]

Not sure. There is an "oc whoami" which might output it but not sure - will check later.

On 09:58, Sat, 20 Jun 2015 Claus Ibsen notifications@github.com wrote:

Oh lovely @jimmidyson https://github.com/jimmidyson - wonder if we should have some way of outputting to the end user what options are in use, eg sometimes you dont know which docker repoistory is used, which namespace, kubernetes master etc.

Is there something oc can do?

— Reply to this email directly or view it on GitHub https://github.com/fabric8io/fabric8/issues/4198#issuecomment-113734089.

[stevef1uk]

James, that is a lot better! I started from scratch and followed your instructions and all as it should be. With Chrome everything is as expected. Safari doesn't work very well in that you can start an app but then not see anything in the Apps, Services or Pods tabs. Firefox won't even let me connect so Chrome seems to be the only working browser for now.

I am now much happier and no longer frustrated :-)

[jstrachan]

@stevef1uk sorry it's taken so long for a relatively painless install!

Hopefully now we're on v1 of the Kubernetes schema & 1.0 of OpenShift things will keep getting slicker and slicker (and more clear from the docs). Thanks for your feedback & patience!

[jstrachan]

@jimmidyson great point on the env vars! Once 2.2.2 is out we maybe only need DOCKER_HOST!

[christian-posta]

Thinking about this from a non-openshift perspective as well (ie, vanilla Kube)... is that kube config file that's created w/ oc login the same thing that'd be created somehow w/ plain kube tools and reused outside of openshift?

On Sat, Jun 20, 2015 at 6:41 AM, James Strachan notifications@github.com wrote:

@jimmidyson https://github.com/jimmidyson great point on the env vars! Once 2.2.2 is out we maybe only need DOCKER_HOST!

— Reply to this email directly or view it on GitHub https://github.com/fabric8io/fabric8/issues/4198#issuecomment-113769871.

Christian Posta twitter: @christianposta http://www.christianposta.com/blog http://fabric8.io

[jimmidyson]

Yeah it's the same. In 0.6 openshift changed from . config/openshift/config to .kube/config in line with kubernetes.

On 15:37, Sat, 20 Jun 2015 Christian Posta notifications@github.com wrote:

Thinking about this from a non-openshift perspective as well (ie, vanilla Kube)... is that kube config file that's created w/ oc login the same thing that'd be created somehow w/ plain kube tools and reused outside of openshift?

On Sat, Jun 20, 2015 at 6:41 AM, James Strachan notifications@github.com wrote:

@jimmidyson https://github.com/jimmidyson great point on the env vars! Once 2.2.2 is out we maybe only need DOCKER_HOST!

— Reply to this email directly or view it on GitHub <https://github.com/fabric8io/fabric8/issues/4198#issuecomment-113769871 .

Christian Posta twitter: @christianposta http://www.christianposta.com/blog http://fabric8.io

—

Reply to this email directly or view it on GitHub https://github.com/fabric8io/fabric8/issues/4198#issuecomment-113775956.

[jstrachan]

@christian-posta one of the last minute changes made in 0.6.2 of OpenShift was to use the same config file name as upstream kubernetes - ~/.kube/config. So whether you use kubernetes or OpenShift the login operation updates the same configuration file - and the kubernetes-api can read them both

[jstrachan]

@jimmidyson @davsclaus BTW the oc project is not bad; it shows the current namespace and master URL:

$ oc project
Using project "default" from context named "default/172-28-128-4:8443/admin" on server "https://172.28.128.4:8443".

[stevef1uk]

Sorry, one more newbie question. I have deployed the fabric8/quickstarts/quickstarts/java/cxf-cdi application and can see it running in hawtio ok, but how do I access the service from my mac? I have tried using curl http://fabric8-master.vagrant.local:8080/cxfcdi/cxfcdi/customerservice/customers/123 and also tried ports 9002 & 9092 but just get connection refused?

[christian-posta]

So after you've deployed it, do you see a "quickstart-java-cxf-cdi" service? ie, if you do "oc get service" or if you list the services in fabric8 console, do you see that one?

if so, then you should be able to connect to it. If you run "mvn fabric8:create-routes" it should set up the OpenShift routes for you to be able to connect to it directly. You'd need to add the

.vagrant.local into your /etc/hosts file (or equivalent for windows) and then it should work (make sure you use the right port that the CXF endpoint is on... from this json ( https://oss.sonatype.org/content/repositories/public/io/fabric8/jube/images/fabric8/quickstart-java-cxf-cdi/2.2.1/quickstart-java-cxf-cdi-2.2.1-kubernetes.json) seems like it should be available on port 9002 On Sat, Jun 20, 2015 at 11:25 AM, stevef1uk notifications@github.com wrote: > Sorry, one more newbie question. I have deployed the > fabric8/quickstarts/quickstarts/java/cxf-cdi application and can see it > running in hawtio ok, but how do I access the service from my mac? > I have tried using curl > http://fabric8-master.vagrant.local:8080/cxfcdi/cxfcdi/customerservice/customers/123 > and also tried ports 9002 & 9092 but just get connection refused? > > — > Reply to this email directly or view it on GitHub > https://github.com/fabric8io/fabric8/issues/4198#issuecomment-113800298. ## _Christian Posta_ twitter: @christianposta http://www.christianposta.com/blog http://fabric8.io

[stevef1uk]

Christian, yes, the service is deployed. I ran the mvn io.fabric8:fabric8-maven-plugin:2.1.11:create-routes previously and it resulted in a build error. The simple mvn fabric8:create-routes did run successfully. I already have the following entries in my /etc/hosts:

172.28.128.4 fabric8-master.vagrant.local vagrant.local fabric8.vagrant.local fabric8-master.vagrant.local jenkins.vagrant.local gogs.vagrant.local nexus.vagrant.local hubot-web-hook.vagrant.local letschat.vagrant.local kibana.vagrant.local taiga.vagrant.local fabric8-forge.vagrant.local

I still get a connection refused error from my mac. I took a quick look at the pretty complex Vagrantfile and I couldn't see any lines like: config.vm.network "forwarded_port", guest: 80, host: 8080

so I am not sure how the port forwarding works from my mac -> vagrant -> docker for these apps?

[christian-posta]

yah if you're running with the latest vagrant images and try to use 2.1.11, then you'll probably get an error about v1beta3 not being around anymore (or unable to parse the Status object,etc).

so when you try to run "oc get route" it should show you the routes that openshift knows about. here's an example output when i run it at this moment:

ceposta@postamac(foobar (master)) $ oc get route

NAME HOST/PORT PATH SERVICE LABELS

docker-registry docker-registry.vagrant.local docker-registry

docker-registry-route docker-registry.vagrant.local docker-registry

elasticsearch elasticsearch.vagrant.local elasticsearch

fabric8 fabric8.vagrant.local fabric8

You'd probably have something like this in yours too:

.vagrant.local So, if you add that .vagrant.local also to your hosts file: 172.28.128.4 fabric8-master.vagrant.local vagrant.local fabric8.vagrant.local fabric8-master.vagrant.local jenkins.vagrant.local gogs.vagrant.local nexus.vagrant.local hubot-web-hook.vagrant.local letschat.vagrant.local kibana.vagrant.local taiga.vagrant.local fabric8-forge.vagrant.local .vagrant.local Then you can try to reach your service: curl http://servicename.vagrant.local Now if you have the service exposed at a specific port (ie 9002) then do this curl http://servicename.vagrant.local:9002 On Sat, Jun 20, 2015 at 12:27 PM, stevef1uk notifications@github.com wrote: > Christian, yes, the service is deployed. I ran the mvn > io.fabric8:fabric8-maven-plugin:2.1.11:create-routes previously and it > resulted in a build error. The simple mvn fabric8:create-routes did run > successfully. I already have the following entries in my /etc/hosts: > > 172.28.128.4 fabric8-master.vagrant.local vagrant.local > fabric8.vagrant.local fabric8-master.vagrant.local jenkins.vagrant.local > gogs.vagrant.local nexus.vagrant.local hubot-web-hook.vagrant.local > letschat.vagrant.local kibana.vagrant.local taiga.vagrant.local > fabric8-forge.vagrant.local > > I still get a connection refused error from my mac. I took a quick look at > the pretty complex Vagrantfile and I couldn't see any lines like: > config.vm.network "forwarded_port", guest: 80, host: 8080 > > so I am not sure how the port forwarding works from my mac -> vagrant -> > docker for these apps? > > — > Reply to this email directly or view it on GitHub > https://github.com/fabric8io/fabric8/issues/4198#issuecomment-113808741. ## _Christian Posta_ twitter: @christianposta http://www.christianposta.com/blog http://fabric8.io

[jimmidyson]

Routes are only accessible via 80 & 443 - don't worry about the service port. OpenShift runs HAProxy for the router listening on 80 & 443, this will route it to the appropriate service port transparently.

On Sat, 20 Jun 2015 at 20:35 Christian Posta notifications@github.com wrote:

yah if you're running with the latest vagrant images and try to use 2.1.11, then you'll probably get an error about v1beta3 not being around anymore (or unable to parse the Status object,etc).

so when you try to run "oc get route" it should show you the routes that openshift knows about. here's an example output when i run it at this moment:

ceposta@postamac(foobar (master)) $ oc get route

NAME HOST/PORT PATH SERVICE LABELS

docker-registry docker-registry.vagrant.local docker-registry

docker-registry-route docker-registry.vagrant.local docker-registry

elasticsearch elasticsearch.vagrant.local elasticsearch

fabric8 fabric8.vagrant.local fabric8

You'd probably have something like this in yours too:

.vagrant.local So, if you add that .vagrant.local also to your hosts file: 172.28.128.4 fabric8-master.vagrant.local vagrant.local fabric8.vagrant.local fabric8-master.vagrant.local jenkins.vagrant.local gogs.vagrant.local nexus.vagrant.local hubot-web-hook.vagrant.local letschat.vagrant.local kibana.vagrant.local taiga.vagrant.local fabric8-forge.vagrant.local .vagrant.local Then you can try to reach your service: curl http://servicename.vagrant.local Now if you have the service exposed at a specific port (ie 9002) then do this curl http://servicename.vagrant.local:9002 On Sat, Jun 20, 2015 at 12:27 PM, stevef1uk notifications@github.com wrote: > Christian, yes, the service is deployed. I ran the mvn > io.fabric8:fabric8-maven-plugin:2.1.11:create-routes previously and it > resulted in a build error. The simple mvn fabric8:create-routes did run > successfully. I already have the following entries in my /etc/hosts: > > 172.28.128.4 fabric8-master.vagrant.local vagrant.local > fabric8.vagrant.local fabric8-master.vagrant.local jenkins.vagrant.local > gogs.vagrant.local nexus.vagrant.local hubot-web-hook.vagrant.local > letschat.vagrant.local kibana.vagrant.local taiga.vagrant.local > fabric8-forge.vagrant.local > > I still get a connection refused error from my mac. I took a quick look > at > the pretty complex Vagrantfile and I couldn't see any lines like: > config.vm.network "forwarded_port", guest: 80, host: 8080 > > so I am not sure how the port forwarding works from my mac -> vagrant -> > docker for these apps? > > — > Reply to this email directly or view it on GitHub > . ## _Christian Posta_ twitter: @christianposta http://www.christianposta.com/blog http://fabric8.io — Reply to this email directly or view it on GitHub https://github.com/fabric8io/fabric8/issues/4198#issuecomment-113809798.

[stevef1uk]

Christian,

Yes, my oc get route shows:

NAME HOST/PORT PATH SERVICE LABELS docker-registry docker-registry.vagrant.local docker-registry
docker-registry-route docker-registry.vagrant.local docker-registry
fabric8 fabric8.vagrant.local fabric8
quickstart-java-cxf-cdi quickstart-java-cxf-cdi.vagrant.local quickstart-java-cxf-cdi
router router.vagrant.local router

If I try curl curl http://vagrant.local/cxfcdi/cxfcdi/quickstart-java-cxf-cdi

I get:

503 Service Unavailable

No server is available to handle this request.

This is progress because I must be reaching something, but what does the URL need to be to actually route to the deployed service?

[jimmidyson]

The haproxy router uses the host header to route to the appropriate server, think Apache virtual hosts if you've used those before. So you need to use the route URL which in this case from your output is

http://quickstart-java-cxf-cdi.vagrant.local

I'm not sure of the context path under there for that quickstart though sorry.

Ensure that quickstart-java-cxf-cdi.vagrant.local is in your hosts file too.

Cheers Jimmi

On 21:01, Sat, 20 Jun 2015 stevef1uk notifications@github.com wrote:

Christian,

Yes, my oc get route shows:

NAME HOST/PORT PATH SERVICE LABELS docker-registry docker-registry.vagrant.local docker-registry

docker-registry-route docker-registry.vagrant.local docker-registry

fabric8 fabric8.vagrant.local fabric8

quickstart-java-cxf-cdi quickstart-java-cxf-cdi.vagrant.local quickstart-java-cxf-cdi

router router.vagrant.local router

If I try curl curl http://vagrant.local/cxfcdi/cxfcdi/quickstart-java-cxf-cdi

I get:

503 Service Unavailable No server is available to handle this request.

This is progress because I must be reaching something, but what does the URL need to be to actually route to the deployed service?

— Reply to this email directly or view it on GitHub https://github.com/fabric8io/fabric8/issues/4198#issuecomment-113814340.

[stevef1uk]

Don't worry I found: http://quickstart-java-cxf-cdi.vagrant.local/quickstart-java-cxf-cdi/cxfcdi?_wadl

:-)

[jimmidyson]

Excellent!

On 21:08, Sat, 20 Jun 2015 stevef1uk notifications@github.com wrote:

Don't worry I found: http://quickstart-java-cxf-cdi.vagrant.local/quickstart-java-cxf-cdi/cxfcdi?_wadl

:-)

— Reply to this email directly or view it on GitHub https://github.com/fabric8io/fabric8/issues/4198#issuecomment-113815704.

[breamoreboy]

My apologies for my complete ignorance in this field, however I've a vested interest in sorting things out as I'm intending to use the technology on the Python workflow, so please bear with me.

I'm following http://fabric8.io/guide/getStartedVagrant.html and I'm getting this:-

oc login https://172.28.128.4:8443 Unable to connect to the server: dial tcp 172.28.128.4:8443: ConnectEx tcp: A connection attempt failed because the connected party did not properly respond after a period of time or established connection failed because connected host has failed to respond.

What am I doing wrong?

Also if you need a test engineer on Windows 8.1 please feel free to ask, I've plenty of time on my hands as I don't work due to ill health.

[christian-posta]

Did the vagrant image come up correctly? Can you ping it?

On Sun, Jul 5, 2015 at 11:54 AM, breamoreboy notifications@github.com wrote:

My apologies for my complete ignorance in this field, however I've a vested interest in sorting things out as I'm intending to use the technology on the Python workflow, so please bear with me.

I'm following http://fabric8.io/guide/getStartedVagrant.html and I'm getting this:-

oc login https://172.28.128.4:8443 Unable to connect to the server: dial tcp 172.28.128.4:8443: ConnectEx tcp: A connection attempt failed because the connected party did not properly respond after a period of time or established connection failed because connected host has failed to respond.

What am I doing wrong?

Also if you need a test engineer on Windows 8.1 please feel free to ask, I've plenty of time on my hands as I don't work due to ill health.

— Reply to this email directly or view it on GitHub https://github.com/fabric8io/fabric8/issues/4198#issuecomment-118650512.

Christian Posta twitter: @christianposta http://www.christianposta.com/blog http://fabric8.io

[breamoreboy]

I've now successfully used oc login, thinking back I'm fairly certain that this was down to comms issues caused by a massive thunderstorm in the UK over the weekend. However I got this prompt that wasn't mentioned in the docs:-

"The server uses a certificate signed by an unknown authority. You can bypass the certificate check, but any data you send to the server could be intercepted by others. Use insecure connections? (y/n): "

I hit "y" just to get in.

[breamoreboy]

I've managed to get to http://fabric8.vagrant.f8/kubernetes/apps?main-tab=kubernetes&sub-tab=kube-apps&q= but I didn't see any message "Your connection is not private" hence I can't login.