~rogpeppe/juju-core/azure : changes

~rogpeppe/juju-core/azure » Changes from revision 1482

From Revision 1477 to 1458

Rev	Summary	Authors	Date
1477	[r=jtv] Convert MAAS provider to loggo. [r=jtv] Convert MAAS provider to loggo. We've been told this was desired, so we might as well do it. Why keep the obsolete approach around to set a bad example?	jtv at canonical	11 years ago
1476	[r=thumper] Enable the local provider. [r=thumper] Enable the local provider. This branch changes how the local storage is handled. It really wasn't possible to have the client keep serving the storage on dynamic ports and expect other running services to work. Also we need something always acting as the storage. After discussion with William last night, we agreed that this should be a worker in the machine agent. https://codereview.appspot.com/11333043/	Tim Penhey	11 years ago
1475	[r=jtv] Fix for gwacl update. [r=jtv] Fix for gwacl update.	Gavin Panella	11 years ago
1474	[r=thumper] Conditionally install lxc [r=thumper] Conditionally install lxc There are two primary situations where we don't want the machine agent to install lxc: 1. when the machine agent is inside an lxc container as known by state 2. when the machine has been provisioned by the local provider (because it is an lxc container) When lxc is installed inside a container, it adds a bridge network device with the same defaults as the host. This kills any routing in or out of the container. Upstart provides support for setting environment variables as part of the config, and we use this to pass the provider type through. https://codereview.appspot.com/11330043/	Tim Penhey	11 years ago
1473	[r=thumper] Have the lxc manager log dir be configurable. [r=thumper] Have the lxc manager log dir be configurable. Since the local provider wants to store the log files in a different location, the ContainerManager needs to be configured with the location. The default log location is still the same, but is now able to be configured. Also factored out the function for getting the IPv4 address for a named interface. The containers have "eth0" as their network interface, so this is used to get the DNSName. https://codereview.appspot.com/11327044/	Tim Penhey	11 years ago
1472	[r=thumper] Machine agent for local provider bootstrap [r=thumper] Machine agent for local provider bootstrap If you are using a local provider, always upload tools. This uses the standard mechanism for getting tools into the local provider storage. From there the tools are unpacked the same way as an agent would normally do it, although we do cheat and go directly to the file on disk so we don't have to pretend to download it somewhere else. https://codereview.appspot.com/11327043/	Tim Penhey	11 years ago
1471	[r=thumper] Use pre-built jujud if found. [r=thumper] Use pre-built jujud if found. Instead of rebuilding jujud everytime we want to upload some tools, try to find jujud next to the juju being executed. https://codereview.appspot.com/11326043/	Tim Penhey	11 years ago
1470	[r=wallyworld] Assign clean/empty policies obey constraints [r=wallyworld] Assign clean/empty policies obey constraints The assign clean/empty policy has been updated to check the hardware characteristics of a machine and if these are incompatible with any unit constraints, the machine is not used. If there are no hardware constraints recorded because the machine is not yet provisioned, the machine is excluded (better to err on the side of caution). https://codereview.appspot.com/11208044/	Ian Booth	11 years ago
1469	[r=thumper] Add the initial bootstrap implementation. [r=thumper] Add the initial bootstrap implementation. This isn't all that is needed to bootstrap, but it is the start. In particular, this adds the mongo upstart service. This branch also adds a very simple instance implementation for the local instances. https://codereview.appspot.com/11325043/	Tim Penhey	11 years ago
1468	[r=wallyworld] add-unit supports the force-machine argument [r=wallyworld] add-unit supports the force-machine argument Semantics are the same as for deploy. Only one unit can be added with force-machine, or else an error occurs. https://codereview.appspot.com/10962046/	Ian Booth	11 years ago
1467	[r=wallyworld] Add container support to force-machine [r=wallyworld] Add container support to force-machine The deploy --force-machine option now supports containers, either deploying to existing containers or creating new ones on nominated machines. Example syntax: juju deploy mysql --force-machine 23 juju deploy mysql --force-machine 24/lxc/3 juju deploy mysql --force-machine lxc:25 The last example creates a new lxc container on machine 25. The add-machine syntax has been tweaked to remove the leading "/" from the container arg. https://codereview.appspot.com/10777044/	Ian Booth	11 years ago
1466	[r=thumper] Change the default root-dir to be in $HOME [r=thumper] Change the default root-dir to be in $HOME Instead of having the root-dir in /usr/lib/juju, make it in ~/.juju (well, $JUJU_HOME) by default. The root dir is now the environment name under the ~/.juju dir. https://codereview.appspot.com/11319044/	Tim Penhey	11 years ago
1465	[r=thumper] Add some extra tests around the sudo checks. [r=thumper] Add some extra tests around the sudo checks. Encapsulate the sudo checks, and make a function to get the uid and gid for the user. https://codereview.appspot.com/11321043/	Tim Penhey	11 years ago
1464	[r=jtv] Skip the service-label dance in Azure. [r=jtv] Skip the service-label dance in Azure. We're still working out how we're supposed to determine an instance's DNS name in Azure. We may have been chasing a red herring early on: on the one hand the documentation hinted that a service's name also formed the hostname part of its DNS name, but on the other, we were getting what looked like a randomly generated DNS name assigned by Azure. And a little dance was orchestrated around that: get the instance URL from the Deployment object, store it in the Service's label field, use the label field as the source of the DNS name. As we understand it now, the weird randomly assigned hostnames only happen in Staging deployments, and the instance URLs don't even resolve when we deploy to Production (as we must do in Juju). And so this branch does away with the little dance, uses the service name as the instance's DNS name, and rips out all code that I could find that was only there to support the dance. The service label is now a mere courtesy; it's required but we may as well set it to be identical to the service name.	jtv at canonical	11 years ago
1463	[r=jtv] Change how an Azure instance finds its ID. [r=jtv] Change how an Azure instance finds its ID. This can now come from the service name it digs out of the WALA config, rather than from the deployment ID. This means that the deployment ID no longer matters, and that in turn opens the door to multiple instances per hosted service.	jtv at canonical	11 years ago
1462	[r=rvb] Azure provider: implement more methods [r=rvb] Azure provider: implement more methods This branch does two things: - it replaces the panic() calls in the port-related methods with empty methods. The goal here is to be able to test the provider more easily, provided that you open/close the ports manually. - it updates the name of the image used because an image with support for Azure in cloud-init has just been made available. In case you wonder, the change s/ExtraSmall/Small is there to accomodate installing mysql on a node. ExtraSmall does not have enough memory. This is all for the sake of testing, all of the code that this branch changes will be re-worked later.	Raphael Badin	11 years ago
1461	[r=jtv] Constructor for cloudinit.MachineConfig. [r=jtv] Constructor for cloudinit.MachineConfig. This is preparation for a refactoring discussed with William Reade and outlined in bug 1199847. Much of the work of creating a cloudinit.MachineConfig is repetitive between providers, so we might as well extract it. This also makes it easier to move the construction from one function to another, as is likely to happen during the further refactoring. You'll see that "tools" is not a parameter. That's because the projected refactoring moves construction of the MachineConfig ahead of where the tools are selected. If these two steps end up fitting together, uniformly across providers, once the code starts to stabilize again then we can make "tools" a parameter after all.	jtv at canonical	11 years ago
1460	[r=wallyworld] New assignment policy is AssignCleanEmpty [r=wallyworld] New assignment policy is AssignCleanEmpty Add container support to AssignClean(Empty) policies and make the default policy AssignCleanEmpty. This allows manual deployment of charms into existing clean and empty containers/instances, with the fallback that a new container/instance is created if none are available. The system behaves the same as previously if a simple bootstrap and deploy is performed, but if add-machine is used to create some containers/instances, then those are no longer ignored. https://codereview.appspot.com/11019044/	Ian Booth	11 years ago
1459	[r=jtv] Remove unneeded internalStartInstance parameter. [r=jtv] Remove unneeded internalStartInstance parameter. This matters because it tightens up the signature of a function that is doing the advance reconnaissance for an ongoing refactoring in the StartInstance() and Bootstrap() methods.	jtv at canonical	11 years ago
1458	[r=jtv] Pointer receives for maas/azure tests. [r=jtv] Pointer receives for maas/azure tests. We've been told that gocheck may get confused when it sees test methods with non-pointer receivers, and fail to run some. So here's a branch to fix up the receivers for all pointers in the maas and azure providers. Those are the only providers I'm directly involved with; I didn't touch the others but I could if that's appreciated.	jtv at canonical	11 years ago

Older »