Re: Referencing labels/annotations in templates?

[Andrew Lau]

I was more thinking:

- user has annotation with region=datacenter1
- creates new project1
- project1 with node-selector=region=datacenter1
- user deploys a template (eg. mysql-persistent)
  - sane default provided as input would be storage-class=datacenter1

On Mon, 24 Oct 2016 at 10:54 Jordan Liggitt  wrote:

> Storage classes were intended to be globally visible. One per project
> would be both unmanageable and would leak a lot of info about the projects
> on the system.
>
> On Oct 23, 2016, at 7:46 PM, Andrew Lau  wrote:
>
> Question was in regards to templates that users would deploy in an
> existing project (but it'd also be useful for project request template).
>
> storage-class-per-user or storage-class-per-project would provide a
> dynamic sane default. Use case being, a user's project node selector is
> allocated to a specific region. I don't believe it's possible to allocate
> PVs (or dynamic PVs) to a specific region/datacenter?
>
> On Mon, 24 Oct 2016 at 10:30 Jordan Liggitt  wrote:
>
> It's not possible to reference labels or annotations on existing
> objects as input parameter values for a template today.
>
> Are you referring to the project template, or a template a user would
> instantiate in an existing project?
>
> Mechanics aside, I didn't think storage-class-per-user or
> storage-class-per-project was a recommended approach
>
>
>
> > On Oct 23, 2016, at 7:15 PM, Andrew Lau  wrote:
> >
> > Is it possible to reference annotations from a project or user
> label/annotation to be used in templates?
> >
> > Eg. With kube 1.4 storage class, can we set the templates pvc storage
> class to automatically be the value of the user/project annotation/label?
> > ___
> > 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: Referencing labels/annotations in templates?

[Jordan Liggitt]

Storage classes were intended to be globally visible. One per project would
be both unmanageable and would leak a lot of info about the projects on the
system.

On Oct 23, 2016, at 7:46 PM, Andrew Lau  wrote:

Question was in regards to templates that users would deploy in an existing
project (but it'd also be useful for project request template).

storage-class-per-user or storage-class-per-project would provide a dynamic
sane default. Use case being, a user's project node selector is allocated
to a specific region. I don't believe it's possible to allocate PVs (or
dynamic PVs) to a specific region/datacenter?

On Mon, 24 Oct 2016 at 10:30 Jordan Liggitt  wrote:

> It's not possible to reference labels or annotations on existing
> objects as input parameter values for a template today.
>
> Are you referring to the project template, or a template a user would
> instantiate in an existing project?
>
> Mechanics aside, I didn't think storage-class-per-user or
> storage-class-per-project was a recommended approach
>
>
>
> > On Oct 23, 2016, at 7:15 PM, Andrew Lau  wrote:
> >
> > Is it possible to reference annotations from a project or user
> label/annotation to be used in templates?
> >
> > Eg. With kube 1.4 storage class, can we set the templates pvc storage
> class to automatically be the value of the user/project annotation/label?
> > ___
> > 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: Referencing labels/annotations in templates?

[Jordan Liggitt]

It's not possible to reference labels or annotations on existing
objects as input parameter values for a template today.

Are you referring to the project template, or a template a user would
instantiate in an existing project?

Mechanics aside, I didn't think storage-class-per-user or
storage-class-per-project was a recommended approach



> On Oct 23, 2016, at 7:15 PM, Andrew Lau  wrote:
>
> Is it possible to reference annotations from a project or user 
> label/annotation to be used in templates?
>
> Eg. With kube 1.4 storage class, can we set the templates pvc storage class 
> to automatically be the value of the user/project annotation/label?
> ___
> 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: Why I don't have debug information in DockerRegistry logs?

[Skarbek, John]

In my opinion, I don’t believe this is an auth issue.

If it were an auth issue, you would’ve seen something from the builder 
indicating a failure to push with incorrect credentials. Instead you are 
looking at what appears as his inability to talk to the registry entirely.

Your log output you produce is from two different spans of time. I would 
suggest gathering the logs from the same time range and let’s take another look.


--
John Skarbek


On October 23, 2016 at 06:19:37, Stéphane Klein 
(cont...@stephane-klein.info) wrote:

I see some debug message here 
https://github.com/openshift/origin/blob/master/pkg/dockerregistry/server/token.go#L60

Why I didn't see it in container logs ?

2016-10-23 11:41 GMT+02:00 Stéphane Klein 
>:
Hi,

I've some auth issue with my OpenShift DockerRegistry:

I1023 08:54:24.043049   1 docker.go:118] Pushing image 
172.30.201.95:5000/openshift/ta-s2i-base-prod:latest
 ...
E1023 08:54:24.046357   1 dockerutil.go:86] push for image 
172.30.201.95:5000/openshift/base-prod:latest
 failed, will retry in 5s ...
E1023 08:54:29.051732   1 dockerutil.go:86] push for image 
172.30.201.95:5000/openshift/base-prod:latest
 failed, will retry in 5s ...
E1023 08:54:34.054921   1 dockerutil.go:86] push for image 
172.30.201.95:5000/openshift/base-prod:latest
 failed, will retry in 5s ...
E1023 08:54:39.058377   1 dockerutil.go:86] push for image 
172.30.201.95:5000/openshift/base-prod:latest
 failed, will retry in 5s ...
E1023 08:54:44.061671   1 dockerutil.go:86] push for image 
172.30.201.95:5000/openshift/base-prod:latest
 failed, will retry in 5s ...
E1023 08:54:49.064716   1 dockerutil.go:86] push for image 
172.30.201.95:5000/openshift/base-prod:latest
 failed, will retry in 5s ...
E1023 08:54:54.067985   1 dockerutil.go:86] push for image 
172.30.201.95:5000/openshift/base-prod:latest
 failed, will retry in 5s ...
F1023 08:54:59.068275   1 builder.go:204] Error: build error: Failed to 
push image: unable to ping registry endpoint 

Re: HELP - Image pull back off

[Philippe Lafoucrière]

It's definitely ansible :(
We have updated by hand all nodes, and after an ansible run, the wrong
config is back
​We'll investigate from here
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Why I don't have debug information in DockerRegistry logs?

[Stéphane Klein]

I see some debug message here
https://github.com/openshift/origin/blob/master/pkg/dockerregistry/server/token.go#L60

Why I didn't see it in container logs ?

2016-10-23 11:41 GMT+02:00 Stéphane Klein :

> Hi,
>
> I've some auth issue with my OpenShift DockerRegistry:
>
> I1023 08:54:24.043049   1 docker.go:118] Pushing image
> 172.30.201.95:5000/openshift/ta-s2i-base-prod:latest ...
> E1023 08:54:24.046357   1 dockerutil.go:86] push for image
> 172.30.201.95:5000/openshift/base-prod:latest failed, will retry in 5s ...
> E1023 08:54:29.051732   1 dockerutil.go:86] push for image
> 172.30.201.95:5000/openshift/base-prod:latest failed, will retry in 5s ...
> E1023 08:54:34.054921   1 dockerutil.go:86] push for image
> 172.30.201.95:5000/openshift/base-prod:latest failed, will retry in 5s ...
> E1023 08:54:39.058377   1 dockerutil.go:86] push for image
> 172.30.201.95:5000/openshift/base-prod:latest failed, will retry in 5s ...
> E1023 08:54:44.061671   1 dockerutil.go:86] push for image
> 172.30.201.95:5000/openshift/base-prod:latest failed, will retry in 5s ...
> E1023 08:54:49.064716   1 dockerutil.go:86] push for image
> 172.30.201.95:5000/openshift/base-prod:latest failed, will retry in 5s ...
> E1023 08:54:54.067985   1 dockerutil.go:86] push for image
> 172.30.201.95:5000/openshift/base-prod:latest failed, will retry in 5s ...
> F1023 08:54:59.068275   1 builder.go:204] Error: build error: Failed
> to push image: unable to ping registry endpoint
> https://172.30.201.95:5000/v0/
> v2 ping attempt failed with error: Get https://172.30.201.95:5000/v2/:
> http: server gave HTTP response to HTTPS client
>  v1 ping attempt failed with error: Get https://172.30.201.95:5000/v1/
> _ping: http: server gave HTTP response to HTTPS client
>
> In DockerRegistry logs I have only this informations:
>
> 10.1.3.1 - - [23/Oct/2016:09:38:35 +] "GET /healthz HTTP/1.1" 200 0 ""
> "Go-http-client/1.1"
> 10.1.3.1 - - [23/Oct/2016:09:38:45 +] "GET /healthz HTTP/1.1" 200 0 ""
> "Go-http-client/1.1"
> 10.1.3.1 - - [23/Oct/2016:09:38:45 +] "GET /healthz HTTP/1.1" 200 0 ""
> "Go-http-client/1.1"
> 10.1.3.1 - - [23/Oct/2016:09:38:55 +] "GET /healthz HTTP/1.1" 200 0 ""
> "Go-http-client/1.1"
> 10.1.3.1 - - [23/Oct/2016:09:38:55 +] "GET /healthz HTTP/1.1" 200 0 ""
> "Go-http-client/1.1"
> 10.1.4.1 - - [23/Oct/2016:09:39:05 +] "GET / HTTP/1.1" 200 0 ""
> "check_http/v2.0 (monitoring-plugins 2.0)"
> 10.1.3.1 - - [23/Oct/2016:09:39:05 +] "GET /healthz HTTP/1.1" 200 0 ""
> "Go-http-client/1.1"
> 10.1.3.1 - - [23/Oct/2016:09:39:05 +] "GET /healthz HTTP/1.1" 200 0 ""
> "Go-http-client/1.1"
> 10.1.3.1 - - [23/Oct/2016:09:39:15 +] "GET /healthz HTTP/1.1" 200 0 ""
> "Go-http-client/1.1"
> 10.1.3.1 - - [23/Oct/2016:09:39:15 +] "GET /healthz HTTP/1.1" 200 0 ""
> "Go-http-client/1.1"
> 10.1.3.1 - - [23/Oct/2016:09:39:25 +] "GET /healthz HTTP/1.1" 200 0 ""
> "Go-http-client/1.1"
> 10.1.3.1 - - [23/Oct/2016:09:39:25 +] "GET /healthz HTTP/1.1" 200 0 ""
> "Go-http-client/1.1"
>
> But I've this in DockerRegistry config file:
>
> $ cat /config.yml
> version: 0.1
> log:
>   level: debug
> http:
>   addr: :5000
> storage:
>   cache:
> layerinfo: inmemory
>   filesystem:
> rootdirectory: /registry
>   delete:
> enabled: true
> auth:
>   openshift:
> realm: openshift
> middleware:
>   repository:
> - name: openshift
>   options:
> pullthrough: true
>
> Why I don't have debug information in log?
>
> Best regards,
> Stéphane
> --
> Stéphane Klein 
> blog: http://stephane-klein.info
> cv : http://cv.stephane-klein.info
> Twitter: http://twitter.com/klein_stephane
>



-- 
Stéphane Klein 
blog: http://stephane-klein.info
cv : http://cv.stephane-klein.info
Twitter: http://twitter.com/klein_stephane
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Metric are visible in tab but not on the left side

[Miloslav Vlach]

Hi,

I can see the metrics on the left side aside the pod information.

but the metrics are available in the pod detail on the tab metrics.



Knows somebody why it is not displayed ? In this example there are metrics
started half hour before now, but this didn’t works even if the duration of
metrics was more and more longer.

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

Re: host resolving problem

[Miloslav Vlach]

The problem is that the sensible playbook (probably) didn’t register
dnsmasq to start after restart.

Thanks for reply,

Mila


 Dne 23. října 2016 v 7:43:03, Andrew Lau (and...@andrewklau.com) napsal/a:

Did you start it up with `oc cluster up` ? Sometimes the DNS server isn't
accessible, you need to flush iptables and restart docker

iptables -f
systemctl restart docker

On Sun, 23 Oct 2016 at 05:57 Miloslav Vlach 
wrote:

> Hi,
>
> I have installed 1.3.0 Origin and after restart (probably) some internal
> services didn’t start up (logging and metrics). The problem is maybe due to
> the name resolution…
>
>
>
> I can’t ping from one pod the other. The problem is in logging and in
> metrics
>
> but
>
>
> Can somebody point me please ?
>
> Thanks Mila
> ___
> 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