lp:~fwereade/juju-core/service-charm-trigger
- Get this branch:
- bzr branch lp:~fwereade/juju-core/service-charm-trigger
Branch merges
Branch information
Recent revisions
- 2013. By Ian Booth
-
[r=wallyworld],[bug=1209003],[bug=1246517] Update goose to rev 110 to fix bug 1246517 and bug 1209003
- 2012. By Roger Peppe
-
[r=rogpeppe],[bug=1205371] state: make Addresses use Machine.Addresses
... and APIAddresses likewise.
This requires changing some tests so that there is
actually a machine that pretends to be the state server. - 2011. By John A Meinel
-
[r=jameinel],[bug=1245770] worker/upgrader: check for tools before getting
When we moved Upgrader behind the API, we lost one of the checks that
it was doing. Namely, when it saw that an upgrade was requested, it
used to check if we already had that version of the tools available.
This restores that check.I noticed this while doing scale testing. If you have 1000 units all
trying to upgrade at the same time on a machine, you end up consuming
4.5MB*1000 = 4.5GB of temporary Tar data, plus 20MB*1000=40GB of
'unpacking-' files. Which is more than my VMs have available :).There is still a race condition, if you have all of the Unit agents
notice at the same time, they will still start trying to download
concurrently. The only thing I could really do there would be to add a
filesystem lock (like uniter-hook-execution) . I looked into it, but it
isn't very trivial to set up a fs hook correctly (in uniter.go there
is a lot of code around checking the Tomb to see if we are stopping,
if we held the lock before so we can break it now, etc.) I'd rather
not get the fs locking wrong and end up in a situation where we
deadlock trying to upgrade. - 2009. By John A Meinel
-
[r=jameinel] testing/
checkers/ log: Clearer failures When Andrew changed the LogMatches function to only assert the
existence of messages he accidentally removed the work I had done to
give clearer messages when there was a problem.This changes some types around and updates the params values like we
did before. So that instead of getting:log_test.go:47:
c.Check(log, jc.LogMatches, []string{"foo bar", "a2345"})
... obtained []loggo.TestLogValues = []loggo. TestLogValues{ loggo.TestLogVa lues{Level: 0x3, Module:"", Filename:"", Line:0, Timestamp: time.Time{ sec:0, nsec:0, loc:(*time. Location) (nil)}, Message:"foo bar"}, loggo.TestLogVa lues{Level: 0x3, Module:"", Filename:"", Line:0, Timestamp: time.Time{ sec:0, nsec:0, loc:(*time. Location) (nil)}, Message:"12345"}}
... expected []string = []string{"foo bar", "a2345"}We now get:
log_test.go:47:
c.Check(log, jc.LogMatches, []string{"foo bar", "a2345"})
... obtained checkers.SimpleMessages = SimpleMessages{
INFO 12345
}
... expected checkers.SimpleMessages = SimpleMessages{
UNSPECIFIED a2345
} - 2008. By Ian Booth
-
[r=wallyworld] Add option to generate simplestreams mirror info
When generating tools metadata using sync-tools or the
tools plugin, add option is provided to optionally generate
mirrors metadata. The option is --public because it is used
when generating tools metadata for public clouds. - 2007. By Ian Booth
-
[r=wallyworld] Remove environs PublicStorage()
With the simplestreams tools infrastructure now in
place, there is no longer any need for environment
provided public storage. To ensure a clean environment
config for 2.0, the relevant config attributes have been
removed rather than deprecated. No one much uses them anyway
eg public-bucket. - 2006. By Ian Booth
-
[r=wallyworld] Get tools metadata from streams.
canonical. com This branch removes all of the hard coded cloud specific
tools metadata urls and instead uses streams.canonical. com
as the source for tools metadata. The deprecated public
bucket url config item is also removed.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp:~go-bot/juju-core/trunk