Re: Design questions around Container logs, EFK & OCP

M, Mohamed A. Shahat wrote: > Thanks Luke, extremely enlightening. > > Now, can you help list the logs that are actually forwarded by the fluentd > pods on worker nodes ? e.g. you mentioned (all node's logs ) , container > logs and service logs. Can you please clarify the dif

Re: Design questions around Container logs, EFK & OCP

Although you can set up the fluentd instances to send logs either to the integrated storage or an external ES, it will be tricky to do both with the same deployment. They are deployed with a daemonset. What you can do is copy the daemonset and configure both as you like (with different secrets/conf

Re: 答复: dev Digest, Vol 71, Issue 1

On Sun, Feb 4, 2018 at 7:51 AM, Zhang William wrote: > So there is no v3.8 version? > None was released. By the time the kubernetes 1.8 code was rolled into master, it was time to also roll in 1.9 changes. So 3.8 exists in the git repo but was effectively skipped to catch up with kubernetes. ___

Re: New rolling pre-release tags for Origin v3.9

Just to make sure I'm clear on what you're saying here... the docker images for these components will have tags that are updated as changes are made to master. At some point, when we consider code "released", git tags will be created, and at that point the corresponding docker image tags should rem

Re: [aos-devel] optimizing go guru

ojects. So that's one more vote for VS... On Tue, Dec 5, 2017 at 10:53 AM, Dan Mace wrote: > > > On Tue, Dec 5, 2017 at 10:43 AM, Luke Meyer wrote: > >> In the context of the vim-go plugin. However behavior seems much the same >> if I run the same command at the

Re: [aos-devel] optimizing go guru

e reusing compiled artifacts? Is there some config that controls this? I don't think I've customized anything. It does seem to speed up a little bit after the first run but then it's still pretty slow. > 3. Get faster laptop :) > > On Dec 5, 2017, at 9:44 AM, Luke Meyer

Re: [aos-devel] optimizing go guru

2017 9:40 AM, "Luke Meyer" wrote: > >> >> >> On Tue, Dec 5, 2017 at 9:36 AM, Sebastian Jug wrote: >> >>> Sounds like you have got auto compile still on? >>> >>> >> What does this mean in the context of go guru? Is there an env va

Fwd: [aos-devel] optimizing go guru

-- Forwarded message -- From: Luke Meyer Date: Tue, Dec 5, 2017 at 10:39 AM Subject: Re: [aos-devel] optimizing go guru To: Sebastian Jug Cc: dev On Tue, Dec 5, 2017 at 9:36 AM, Sebastian Jug wrote: > Sounds like you have got auto compile still on? > > What does

Re: [aos-devel] optimizing go guru

mac/gpgme real 0m10.041s user 1m0.303s sys 0m7.648s On Tue, Dec 5, 2017 at 9:36 AM, Dan Mace wrote: > > > On Tue, Dec 5, 2017 at 9:31 AM, Luke Meyer wrote: > >> I must be doing something wrong. Whenever go guru is fired off against >> the origin codebase (for example, w

optimizing go guru

I must be doing something wrong. Whenever go guru is fired off against the origin codebase (for example, with godef or callstack or whicherrs) it takes several seconds (or more) to do anything, sucking up GB of RAM and all CPUs. I imagine it must be compiling the world, which is rather large. Perha

Re: GithubGraphs

Yeah, neat! You know of course when you provide a visualization like this, people will want to expand the options :) For instance it would be nice to see the duration starting from applying the "lgtm" label (in repos where that applies), or from the first approval response, or from the first [merge

Re: OpenShift Origin v3.6.0 is released

On Mon, Jul 31, 2017 at 11:34 AM, Clayton Coleman wrote: > Remember to use the Ansible release-3.6 branch for your installs. > > You can also skip installing Ansible and checking out the repo and just use the containerized install image

alpha features

How do I turn on alpha features in Origin? E.g. dynamic provisioning, auto service cert generation... ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev

Re: /etc/localtime

t JEE tech, then having the app timezone set (regardless of client >> timezone) may be useful. I can also see a case for scheduled/cron-like >> jobs being more readable with an assumed timezone. >> >> >> >> *Brandon Richins* >> >> >> >> *F

Re: /etc/localtime

ttp://olavgg.com/post/117506310248/docker-how-to-fix-date-and-timezone-issues > > sudo docker run --rm -it \ > > -v /etc/localtime:/etc/localtime:ro \ > > -v /etc/timezone:/etc/timezone:ro \ > > --name my_container debian:jessie date > > > > Please correct me i

/etc/localtime

Is there a simple way to find out the host's local timezone without having to mount /etc/localtime (which is pretty painful given it requires hostmount)? Could there be some way it's passed in as an env var or something? ___ dev mailing list dev@lists.ope

Re: packaging

it? > > On Jun 29, 2016, at 8:12 AM, Luke Meyer wrote: > > The origin project itself doesn't maintain spec files. However you might > find the Fedora and EPEL source rpms interesting: > > Fedora - > https://kojipkgs.fedoraproject.org//packages/origin/1.2.0/1.g

Re: packaging

The origin project itself doesn't maintain spec files. However you might find the Fedora and EPEL source rpms interesting: Fedora - https://kojipkgs.fedoraproject.org//packages/origin/1.2.0/1.git.0.2e62fab.fc24/src/origin-1.2.0-1.git.0.2e62fab.fc24.src.rpm CentOS/EPEL - http://cbs.centos.org/kojif

Re: OpenShift Origin v1.3.0-alpha.2 has been released

docker.io/openshift/origin-logging-auth-proxy does not seem to have the v1.3.0-alpha.2 tag (or .1 for that matter). The other logging images all have the tag. auth-proxy was added to the build/release scripts in the last few weeks as it was brought into git as a submodule; perhaps an older script v

Re: fsGroup vs. supplementalGroups

On Wed, Jun 22, 2016 at 12:14 PM, Alan Jones wrote: > I have a configuration for a PV/PVC with a block device that works in the > default namespace with the fsGroup tag in the pod spec's securityContext. > I was able to create the pod in a non-default namespace with combination > of 'openshift.io

Re: "manifest unknown" test flakes

the issue here that that ruby-22-centos7 image itself needs to be >> rebuild/pushed from docker 1.10? >> >> if so (and if our AMIs are on docker 1.10) i can kick off a fresh round >> of our s2i image build/push job to refresh everything. >> ​ >> >&

Re: "manifest unknown" test flakes

hed images (alpha.1) was pushed from Docker 1.9. > > This might just be docker flaking, but we'd probably need more info from > the Docker logs. > > On Tue, Jun 7, 2016 at 9:41 PM, Luke Meyer wrote: > >> I've seen this twice in logging tests, in the ruby STI

"manifest unknown" test flakes

I've seen this twice in logging tests, in the ruby STI builder today and in the origin image last week, so I'm wondering if it's a trend. https://ci.openshift.redhat.com/jenkins/job/test-origin-aggregated-logging/381/artifact/origin/artifacts/logs/container-ruby-sample-build-1-build-sti-build.log

readiness probes and clustered discovery

We have a plugin for Elasticsearch to cluster based on looking up endpoints on its clustering service (which runs at separate port 9300 instead of http port 9200). But in order to be among the endpoints on a service, the cluster members have to be considered "up"; so this must occur before they can

Fwd: linux file caching in containers?

Does anyone know if Linux file caching is compartmentalized in Docker containers or accounted for in their memory limits? The particular context of this question is Elasticsearch: https://www.elastic.co/guide/en/elasticsearch/guide/current/heap-sizing.html#_give_less_than_half_your_memory_to_lucen

Re: SSL error on vagrant up in origin

One of the three mirror backends has an outdated cert, which we're working on fixing. In the meantime, if you just try it again, you have a pretty good chance of success. On Wed, May 11, 2016 at 2:02 AM, Suraj Deshmukh wrote: > Hi, > > > When doing `vagrant up` on the origin root directory, ssl

Re: binary source in a Custom type build

tom > image would need to read stdin as a tar stream. > > On Thu, May 5, 2016 at 4:31 PM, Luke Meyer wrote: > >> How in a custom builder do you retrieve binary build content (from e.g. >> the --from-dir flag)? >> https://docs.openshift.org/latest/dev_guide/builds.html#binar

binary source in a Custom type build

How in a custom builder do you retrieve binary build content (from e.g. the --from-dir flag)? https://docs.openshift.org/latest/dev_guide/builds.html#binary-source does not seem to give any clues. SOURCE_URI comes in blank. Is there a secret handshake I'm missing? __

Re: Three-tier application deployment on OpenShift origin

getting Abdala's small environment going, I guess it > doesn't much "matter"... > > > Erik M Jacobs, RHCA > Principal Technical Marketing Manager, OpenShift Enterprise > Red Hat, Inc. > Phone: 646.462.3745 > Email: ejac...@redhat.com > AOL Instant Messenger:

Re: Three-tier application deployment on OpenShift origin

On Tue, May 3, 2016 at 10:57 AM, Erik Jacobs wrote: > Hi Olga, > > Some responses inline/ > > > Erik M Jacobs, RHCA > Principal Technical Marketing Manager, OpenShift Enterprise > Red Hat, Inc. > Phone: 646.462.3745 > Email: ejac...@redhat.com > AOL Instant Messenger: ejacobsatredhat > Twitter: @

Re: Excluding replacement pods from quota?

Use the Recreate deploy strategy rather than Rolling. https://docs.openshift.org/latest/dev_guide/deployments.html#recreate-strategy On Sat, Apr 30, 2016 at 10:24 PM, Andrew Lau wrote: > Hi, > > Is there a way to have the old pod moved into the terminating scope? Or is > there an alternative sol

Re: OpenShift containerized installation and EFK logging

.com > AOL Instant Messenger: ejacobsatredhat > Twitter: @ErikonOpen > Freenode: thoraxe > > On Wed, Feb 17, 2016 at 1:48 PM, Luke Meyer wrote: > >> For the containerized install, I am not sure it is documented that you >> need to mount /var/log into each node containe

Re: OpenShift containerized installation and EFK logging

For the containerized install, I am not sure it is documented that you need to mount /var/log into each node container for fluentd to be able to get to logs. On Sat, Feb 6, 2016 at 11:32 AM, Akram Ben Aissi wrote: > Hi guys, > > I am running a containarized install of OpenShift, and after the >

Re: pod DNS change

ure why you can' get through the firewall. > > On Fri, Jan 15, 2016 at 11:27 AM, Luke Meyer wrote: > > I rebuilt my dev cluster from HEAD recently and pods were having DNS > > problems. I'm set up with dnsmasq at port 53 on the master, forwarding > > cl

pod DNS change

I rebuilt my dev cluster from HEAD recently and pods were having DNS problems. I'm set up with dnsmasq at port 53 on the master, forwarding cluster requests to SkyDNS running at port 8053, per https://developerblog.redhat.com/2015/11/19/dns-your-openshift-v3-cluster/ I discovered that pods are now

Re: SDN config for HEAD

On Tue, Jan 12, 2016 at 1:27 PM, Brenton Leanhardt wrote: > On Tue, Jan 12, 2016 at 11:50 AM, Luke Meyer wrote: > > Right on target, thanks. > > > > Manually fixing things up as suggested seems to work (also needed: oadm > > policy reconcile-cluster-roles --conf

Re: SDN config for HEAD

ons for building RPMs from source? On Tue, Jan 12, 2016 at 10:02 AM, Dan Winship wrote: > On 01/12/2016 09:31 AM, Luke Meyer wrote: > > I ran an "advanced install" of Origin (which installs and configures > > RPMs from early December), then updated the openshift binary t

SDN config for HEAD

I ran an "advanced install" of Origin (which installs and configures RPMs from early December), then updated the openshift binary to be compiled from master. Perhaps not surprisingly, my nodes won't come up now: I0111 21:36:41.7568711259 start_node.go:178] Starting a node connected to https://

Re: logging service in openshift

te: > >> On 8 January 2016 at 15:14, Luke Meyer wrote: >> > >> > >> > On Fri, Jan 8, 2016 at 10:08 AM, priyanka Gupta >> > wrote: >> >> >> >> Hi, I have deployed EFK in openshift 3.1, In doc it is mentoined >> >>