Tim Buckley

@kornicameister I think that would be a good idea, those entries predate our proper stable branches. That said, I'm not sure where tagged versions belong, e.g. monasca/client:1.7.0. I guess we...

That seems to solve a fairly similar problem as our own pr-bot: https://github.com/monasca/pr-bot. We don't see it much in monasca-docker (yet...) but it's been pushing updates to monasca-helm for a...

My feeling about restarting quickly on failure is that you tend to generate a lot of noise for a situation that you generally expect to happen. As an example, Kubernetes...

A couple of points I missed.. > Overall, the presence of a “wait for kafka” raises questions as to the system overall behavior once under load and components fail or...

> There is an additional problem with the current "wait" implementation: It relies on Python not on bash/sh. [...] But, currently, all containers need to package Python in the image....

p2cli does look nice! I've really come to appreciate jinja2-style templates over go's builtin templates after working with Helm, and that utility would be a nice way to slim down...

As a side note, we are planning to move away from :latest and :master tags as soon as we can, the main blocker on that right now is that a...

Right, that's exactly what we want to support. keystone-init is a separate container and can create all our Monasca users and projects in any target keystone instance (or really any...

first 3 added in https://github.com/monasca/monasca-docker/pull/180

I agree that travis's stages could be a lot simpler, but unfortunately they can be very slow. Even during quiet periods it takes 3-5 minutes for our code to actually...