Lionel, So is it working for you now?
> On Aug 9, 2016, at 11:10 PM, Lionel Orellana <lione...@gmail.com> wrote: > > Digging through the go libraries used for parsing the command options I found > that setting the no_proxy variable like this works: > > -e \"no_proxy=172.17.0.3,172.17.0.4\" > > It all comes down to https://golang.org/pkg/encoding/csv > <https://golang.org/pkg/encoding/csv> > > which is used by the pflag package. > On Tue, 9 Aug 2016 at 10:31 PM, Lionel Orellana <lione...@gmail.com > <mailto:lione...@gmail.com>> wrote: > Setting the log level to 4 I found the following > > Starting OpenShift using container 'origin' > I0809 22:21:26.415373 20151 run.go:143] Creating container named "origin" > config: > image: openshift/origin:v1.3.0-alpha.2 > command: > start > > --master-config=/var/lib/origin/openshift.local.config/master/master-config.yaml > > --node-config=/var/lib/origin/openshift.local.config/node-poc-docker03.aipo.gov.au/node-config.yaml > <http://node-poc-docker03.aipo.gov.au/node-config.yaml> > environment: > http_proxy=http://proxy.aipo.gov.au:3128 <http://proxy.aipo.gov.au:3128/> > https_proxy=http://proxy.aipo.gov.au:3128 <http://proxy.aipo.gov.au:3128/> > no_proxy=172.17.0.3 > 172.17.0.4 > > I've tried different ways of setting multiple ip's in no_proxy but they > always seem to be getting split on the comma. > > -e "no_proxy=172.17.0.3,172.17.0.4" > -e no_proxy="172.17.0.3\,172.17.0.4" > -e no_proxy=’172.17.0.3,172.17.0.4’ > -e no_proxy=172.17.0.3,172.17.0.4 > > This might be causing some of my problems. The fact that I can't set more > than one ip address in no_proxy. > > > > > > > > On 9 August 2016 at 11:18, Lionel Orellana <lione...@gmail.com > <mailto:lione...@gmail.com>> wrote: > I guess what I need is a way to configure the proxy as per > https://docs.openshift.org/latest/install_config/http_proxies.html#configuring-hosts-for-proxies > > <https://docs.openshift.org/latest/install_config/http_proxies.html#configuring-hosts-for-proxies> > > > On Tue, 9 Aug 2016 at 10:05 AM, Lionel Orellana <lione...@gmail.com > <mailto:lione...@gmail.com>> wrote: > It's been difficult to get a functional poc going with oc cluster up behind a > proxy. > > I need to maintain the registry's address so I can add it to the no_proxy > variable of the docker deamon. Clayton's procedure works for reusing the > address . I will try --use-existing-config. > > But I also need to add the registry's internal address (which always seems to > be initially set to 172.17.0.4) to the no_proxy variable of the cluster up > command itself. Otherwise the health checks try to go through the proxy and > fail. > > When I recreate the registry (in order to set a known service ip) the pod ip > changes and the health checks start to fail again. > > Obviously I am making this harder than it should be. But I just can't get the > right combination to run a cluster behind a proxy where I can login to the > registry (docker login). Maybe I should have said that's what I'm trying to > do from the beginning. > > Cheers > > > Lionel. > > On Tue, 9 Aug 2016 at 1:16 AM, Clayton Coleman <ccole...@redhat.com > <mailto:ccole...@redhat.com>> wrote: > Generally deep configuration is not the goal of oc cluster up - that's more > the Ansible installs responsibility. oc cluster up is about getting a > running cluster up for test / dev as quickly as possible, but we don't want > to add fine grained tuning to it. > > On Mon, Aug 8, 2016 at 10:49 AM, Cesar Wong <cew...@redhat.com > <mailto:cew...@redhat.com>> wrote: > Hi Lionel, > > You can always reuse the same data/config dirs and keep your service ips: > > oc cluster up --host-data-dir=blah --host-config-dir=blah > --use-existing-config > >> On Aug 7, 2016, at 9:17 PM, Lionel Orellana <lione...@gmail.com >> <mailto:lione...@gmail.com>> wrote: >> >> Thanks Clayton. >> >> Would be nice to have a way of setting the address when using cluster up >> though. >> On Mon, 8 Aug 2016 at 11:03 AM, Clayton Coleman <ccole...@redhat.com >> <mailto:ccole...@redhat.com>> wrote: >> When you create the registry you can specify the service IP that is assigned >> (as long as another service hasn't claimed it). >> >> $ oadm registry -o yaml > registry.yaml >> $ vi registry.yaml >> # Set the registry service `spec.clusterIP` field to a valid service IP >> (must be within the service CIDR, typically 172.30.0.0/16 >> <http://172.30.0.0/16>) >> $ oc create -f registry.yaml >> >> >> On Sun, Aug 7, 2016 at 8:55 PM, Lionel Orellana <lione...@gmail.com >> <mailto:lione...@gmail.com>> wrote: >> Hi >> >> I'm facing a similar problem to this: >> https://github.com/openshift/origin/issues/7879 >> <https://github.com/openshift/origin/issues/7879> >> >> Basically I need to configure the NO_PROXY variable of the Docker deamon to >> include the registry address. Problem is with cluster up I can't control the >> ip address that will be assigned to the registry. Or at least I can't find a >> way to do it. Is there an option that I'm not seeing? >> >> Thanks >> >> Lionel. >> >> _______________________________________________ >> users mailing list >> users@lists.openshift.redhat.com <mailto:users@lists.openshift.redhat.com> >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> <http://lists.openshift.redhat.com/openshiftmm/listinfo/users> >> >> >> _______________________________________________ >> users mailing list >> users@lists.openshift.redhat.com <mailto:users@lists.openshift.redhat.com> >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> <http://lists.openshift.redhat.com/openshiftmm/listinfo/users> > > >
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
