Re: OpenShift and AWS

2016-02-02 Thread 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 >

Re: Openshift Origin using ssh key (secret) inside a build

2016-02-02 Thread Johary RAVELONJATOVO
I saw the doc today and try to use it but my origin was not up to date :p. I try it once I update Origin (There's a lot of change) but I still have the same issue.  Here are my build config secret part  The "scmsecret" is my secret test key from ssh-key. Is there something that I'm doing

Re: swagger UI

2016-02-02 Thread Clayton Coleman
Hrm - works locally, is that path allowed by your proxy? On Tue, Feb 2, 2016 at 7:16 PM, Srinivas Naga Kotaru (skotaru) < skot...@cisco.com> wrote: > Thanks for quick reply > > Am getting method not allowed. Tried CLI and browser. Browser simply > throwing a blank download page > > # curl -Ik

Re: swagger UI

2016-02-02 Thread Nakayama Kenjiro
I could reproduce your error with "-I" option on my end. curl -Ik https://localhost:8443/swaggerapi/oapi/v1 HTTP/1.1 405 Method Not Allowed Date: Fri, 08 Jan 2016 11:48:17 GMT Content-Length: 23 Content-Type: text/plain; charset=utf-8 However, your browser should have worked, and so,

Openshift Origin using ssh key (secret) inside a build

2016-02-02 Thread Johary RAVELONJATOVO
Hi everyone, I actually try to deploy a symfony 2 project with OpenShift Origin. The source code of my project is on a private repository and I have create a secret with my ssh key to access on it "private-repo-secret". With that I have no problem to access on the source code with OpenShift

Re: Impossible to restart vagrant VM after one vagrant halt

2016-02-02 Thread Stéphane Klein
More information : * vagrant up master --no-provision * vagrant halt master * vagrant up master --no-provision * vagrant ssh all work perfectly but * vagrant provision master * vagrant halt master * vagrant up master * vagrant ssh I have : ``` ==> master: Configuring and enabling network

Re: Impossible to restart vagrant VM after one vagrant halt

2016-02-02 Thread Stéphane Klein
Before provision, I've this ``` [root@ose3-node1 vagrant]# nmcli d DEVICE TYPE STATE CONNECTION lbr0bridge connected lbr0 eth0ethernet connected eth0 vlinuxbrethernet connected vlinuxbr tun0openvswitch connected tun0 eth1

OpenShift and AWS

2016-02-02 Thread 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:

swagger UI

2016-02-02 Thread Srinivas Naga Kotaru (skotaru)
Does OSE master expose swagger-ui? I tested but not working. Wondering we have to do anything to get it work. I feel this is good way to learn and use master API -- Srinivas Kotaru ___ users mailing list users@lists.openshift.redhat.com

Re: swagger UI

2016-02-02 Thread Srinivas Naga Kotaru (skotaru)
Thanks for quick reply Am getting method not allowed. Tried CLI and browser. Browser simply throwing a blank download page # curl -Ik https://8443/swaggerapi/oapi/v1 HTTP/1.1 405 Method Not Allowed Date: Wed, 03 Feb 2016 00:15:20 GMT Content-Length: 23 Content-Type: text/plain; charset=utf-8

Re: after native HA install atomic-openshift-master service is not enabled

2016-02-02 Thread Dale Bewley
I didn't realize there was a difference in services for the native HA config. Thanks for that information. I did a fresh install and below is how I deployed the registry. [root@ose-ha-master-01 playbook-openshift]# oc status In project default on server

Docker volume group

2016-02-02 Thread Lorenz Vanthillo
If you want a master - node scenario with 1 master and 2 nodes (and the nodes are not on the same machine as the master). Is it than recommended to use only one volume for your master (and not create a volume-group etc) And use 2 volumes for your nodes. To create a volume group for docker on it.