New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 601598 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Move cloudtail from /opt/infra-python to /opt/infra-tools

Project Member Reported by aga...@chromium.org, Apr 7 2016

Issue description

Currently, cloudtail is deployed to masters inside /opt/infra-python. This is confusing, because it is a go binary (and in fact is located at /opt/infra-python/go/bin). Can this get changed so it lives in a less confusing place>
 
Cc: vadimsh@chromium.org
This was vadimsh's idea originally: https://codereview.chromium.org/1365583002/diff/40001/infra/services/service_manager/__main__.py#newcode28

I don't have an opinion one way or the other.
Cloudtail is used in two ways:

1. By service_manager.
2. As a standalone tool (hooked up to stuff via puppet configs).

In case (1) it makes sense to bundle it with infra_python, where service_manager is. Otherwise infra_python would have to know where cloudtail is installed, and will become less self-contained. Currently it is possible to "atomically" update service_manager and cloudtail version it is uses.

In case (2) cloudtail is installed in /opt/infra-tools and used from there.

tl;dr /opt/infra-python/go/bin/cloudtail is private copy of cloudtail and must not be used outside of infra_python.

Comment 3 by jpar...@google.com, Apr 11 2016

Owner: aga...@chromium.org
Status: Assigned (was: Untriaged)
Is this resolved then?

Comment 4 by aga...@chromium.org, Apr 12 2016

Status: WontFix (was: Assigned)
Yep, this can be wont-fix.

Comment 5 by benhenry@google.com, Apr 27 2016

Components: Infra>Monitoring
Labels: -Infra-Monitoring

Comment 6 by benhenry@google.com, Apr 27 2016

Labels: -Infra

Sign in to add a comment