Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add m3coordinator Dockerfile and update Prometheus test to use standalone coordinator #792

Merged
merged 4 commits into from
Jul 12, 2018

Conversation

robskillington
Copy link
Collaborator

@robskillington robskillington commented Jul 12, 2018

This will also fix our documentation, as we'll be able to start building each service with quay.io on each push to master.

LABEL maintainer="The M3DB Authors <m3db@googlegroups.com>"

# Install Glide
RUN apk add --update glide git make bash
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should reuse these steps across the Dockerfiles at some point, but let's just move forward quickly for now to unblock others using the images?

@codecov
Copy link

codecov bot commented Jul 12, 2018

Codecov Report

Merging #792 into master will decrease coverage by 0.17%.
The diff coverage is 37.5%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #792      +/-   ##
==========================================
- Coverage   78.38%   78.21%   -0.18%     
==========================================
  Files         363      363              
  Lines       30812    30850      +38     
==========================================
- Hits        24152    24129      -23     
- Misses       5065     5117      +52     
- Partials     1595     1604       +9
Flag Coverage Δ
#coordinator 61.01% <37.5%> (-0.41%) ⬇️
#dbnode 81.57% <ø> (-0.13%) ⬇️
#m3ninx 72.7% <ø> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 69b0ea0...16e83d7. Read the comment docs.

Copy link
Collaborator

@schallert schallert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, left 2 nits

@@ -98,3 +100,35 @@ func TestPromNativeReadPost(t *testing.T) {
h.Router.ServeHTTP(res, req)
require.Equal(t, res.Code, http.StatusMethodNotAllowed, "POST method not defined")
}

func TestRooutesGet(t *testing.T) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/Rooutes/Routes

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ta, good catch.

@@ -159,6 +174,9 @@ func Run(runOpts RunOptions) {
}
}

namespaces := clusters.ClusterNamespaces()
logger.Info("resolved cluster namespaces", zap.Int("namespaces", len(namespaces)))
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be useful to list the names instead of the count?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure thing.

@@ -0,0 +1,45 @@
listenAddress: 0.0.0.0:7201
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this never going to be useful for end users ? Maybe consider it moving out of integration-tests ?

@robskillington robskillington merged commit ab8ddee into master Jul 12, 2018
@robskillington robskillington deleted the r/add-m3coordinator-dockerfile branch July 12, 2018 20:00
@robskillington robskillington restored the r/add-m3coordinator-dockerfile branch July 16, 2018 02:16
@robskillington robskillington deleted the r/add-m3coordinator-dockerfile branch July 16, 2018 02:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants