lp://qastaging/~gz/juju-core/juju-update-bootstrap
- Get this branch:
- bzr branch lp://qastaging/~gz/juju-core/juju-update-bootstrap
Branch merges
- Juju Engineering: Pending requested
-
Diff: 164 lines (+159/-0)1 file modifiedcmd/plugins/juju-update-bootstrap/updatebootstrap.go (+159/-0)
Related source package recipes
Related bugs
| Bug #1254579: juju-update-bootstrap-address plugin | High | Fix Released |
|
Related blueprints
Branch information
Recent revisions
- 2101. By Martin Packman
-
Merge changes from rogpeppe for bumping conf version and parallel ssh execution
- 2098. By Tim Penhey
-
[r=thumper] Implement a container manager factory method.
In order for the local provider to support kvm
containers, we need a generic way to create container
managers. - 2097. By Tim Penhey
-
[r=thumper] Implement kvm start, stop and list.
The implementation here uses a mix of:
* uvt-simplestream-libvirt
* uvt-kvm
* virshThese are provided by the uvtool package and the
dependencies. The implementation of the low level
calls out to the shell are in container/kvm/libvirt. go These low level calls are then used by the container
factory and container instances in container/kvm.These are used by the container manager instance.
There are some live tests for the kvm calls.
cd container/kvm
sudo -E go test
This will take quite some time the first time it is
run on any particular machine as it is syncing the
kvm machine instances. But it does work \o/
The machines won't actually boot functional juju
machines in the test because the tools location is
fake. - 2096. By Tim Penhey
-
[r=thumper] local provider uses rsyslog and all-machines.log
For local providers, we now write out rsyslog configuration which is
namespaced, so multiple local environments don't step on each other's
toes.The syslog config has been simplified slightly. The first $InputFileStateFile
has been removed because the value was overridden later on at the bottom
of the block. Also, now we have just one template format that is used
both for local and remote logs. Appropriate values in the config file
are namespaced.The other big change here is that all-machines.log now instead of just
having %HOSTNAME%, it uses the tag of the agent sending the log messages,
so now we have 'machine-0' and 'unit-ubuntu-0' etc.We have to define our own long tag format for the udp sending in order
to have tags longer than 32 characters go through. This is needed for
the above agent names.I have considered the situation on upgrades. Newer machines will be started
with the newer long tag forwarder template, but this makes no difference
as the current host is ignoring that and will continue to write out
the hostname. - 2095. By Tim Penhey
-
[r=thumper] Make the syslog udp port configurable.
Instead of having the syslog port hard-coded to 514 it makes
sense to make this configurable.Any existing config that doesn't specify one will get the default,
which is 514.This config port is passed through the cloud init machine config
structure so the syslog config that is written out forwards to the
correct port. This syslog port is needed, so a number of tests had
to be updated to make this work.The (rather generic) 'suite' test in environs/
config_ test was updated
to use the LoggingSuite base to silence the logging that was leaked
out when running just the package tests.The port number is now a template param in the rsyslog config.
The only other place where this was needed was with the deployer.
It was making multiple calls to get the state and api addresses.
Instead of adding another call, we now make one call to the api
to get the address information we need.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp://qastaging/~go-bot/juju-core/trunk
