Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(138)

Issue 7712046: environs: send bootstrap constraints in cloudinit

Can't Edit
Can't Publish+Mail
Start Review
Created:
12 years, 9 months ago by fwereade
Modified:
12 years, 9 months ago
Reviewers:
dimitern, mp+153788, jameinel, thumper
Visibility:
Public.

Description

environs: send bootstrap constraints in cloudinit This closes the circuit, and causes the bootstrap constraints to be set as the initial environment constraints in state. https://code.launchpad.net/~fwereade/juju-core/bootstrap-constraints-5/+merge/153788 Requires: https://code.launchpad.net/~fwereade/juju-core/bootstrap-constraints-4/+merge/153759 (do not edit description out of merge proposal)

Patch Set 1 #

Total comments: 5

Patch Set 2 : environs: send bootstrap constraints in cloudinit #

Unified diffs Side-by-side diffs Delta from patch set Stats (+32 lines, -5 lines) Patch
A [revision details] View 1 1 chunk +2 lines, -0 lines 0 comments Download
M environs/cloudinit/cloudinit.go View 2 chunks +4 lines, -0 lines 0 comments Download
M environs/cloudinit/cloudinit_test.go View 1 3 chunks +14 lines, -3 lines 0 comments Download
M environs/ec2/ec2.go View 1 1 chunk +1 line, -0 lines 0 comments Download
M environs/jujutest/livetests.go View 1 2 chunks +8 lines, -1 line 0 comments Download
M environs/openstack/provider.go View 1 4 chunks +3 lines, -1 line 0 comments Download

Messages

Total messages: 5
fwereade
Please take a look.
12 years, 9 months ago (2013-03-18 13:05:05 UTC) #1
jameinel
overall this seems pretty straightforward LGTM I was a little surprised about the mem normalization, ...
12 years, 9 months ago (2013-03-18 17:13:56 UTC) #2
thumper
LGTM https://codereview.appspot.com/7712046/diff/1/environs/cloudinit/cloudinit_test.go File environs/cloudinit/cloudinit_test.go (right): https://codereview.appspot.com/7712046/diff/1/environs/cloudinit/cloudinit_test.go#newcode43 environs/cloudinit/cloudinit_test.go:43: func mustConstraints(s string) state.Constraints { Despite what appears ...
12 years, 9 months ago (2013-03-19 01:30:24 UTC) #3
dimitern
LGTM https://codereview.appspot.com/7712046/diff/1/environs/cloudinit/cloudinit_test.go File environs/cloudinit/cloudinit_test.go (right): https://codereview.appspot.com/7712046/diff/1/environs/cloudinit/cloudinit_test.go#newcode43 environs/cloudinit/cloudinit_test.go:43: func mustConstraints(s string) state.Constraints { On 2013/03/19 01:30:24, ...
12 years, 9 months ago (2013-03-19 09:23:39 UTC) #4
fwereade
12 years, 9 months ago (2013-03-20 11:47:47 UTC) #5
*** Submitted:

environs: send bootstrap constraints in cloudinit

This closes the circuit, and causes the bootstrap constraints to be set as
the initial environment constraints in state.

R=jameinel, thumper, dimitern
CC=
https://codereview.appspot.com/7712046

https://codereview.appspot.com/7712046/diff/1/environs/cloudinit/cloudinit_te...
File environs/cloudinit/cloudinit_test.go (right):

https://codereview.appspot.com/7712046/diff/1/environs/cloudinit/cloudinit_te...
environs/cloudinit/cloudinit_test.go:43: func mustConstraints(s string)
state.Constraints {
On 2013/03/19 09:23:39, dimitern wrote:
> On 2013/03/19 01:30:24, thumper wrote:
> > Despite what appears to be some form of standard, I find that must*
functions
> > hinder readability as they don't follow the standard method naming
guidelines
> of
> > starting with some verb.  Personally I'd prefer "mustParseConstraints",
> however
> > I'm not going to block on any of this, just for comment.
> 
> +1 for mustParseConstraints

SGTM, I hope to have a constraints.MustParse for use in similar situations
before too long but it's not a focus right now.

https://codereview.appspot.com/7712046/diff/1/environs/jujutest/livetests.go
File environs/jujutest/livetests.go (right):

https://codereview.appspot.com/7712046/diff/1/environs/jujutest/livetests.go#...
environs/jujutest/livetests.go:348: c.Assert(cons.String(), Equals, "mem=2048M")
On 2013/03/18 17:13:56, jameinel wrote:
> This seems a little bit odd that the mem constraint is normalized back to M.

Rational laziness in the Constraints type. Not opposed to improving it, just not
very keen to focus on it until it starts generating complaints.
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b