2618.1.2
|
|
|
John Arbash Meinel |
10 years ago
|
|
|
2618.1.1
|
|
|
John Arbash Meinel |
10 years ago
|
|
|
2618
|
|
|
Roger Peppe |
10 years ago
|
|
|
2617
|
|
|
Jesse Meek |
10 years ago
|
|
|
2616
|
|
|
Jesse Meek |
10 years ago
|
|
|
2615
|
|
|
William Reade |
10 years ago
|
|
|
2614
|
|
|
Ian Booth |
10 years ago
|
|
|
2613
|
|
|
Tim Penhey |
10 years ago
|
|
|
2612
|
|
|
Dave Cheney |
10 years ago
|
|
|
2611
|
|
|
Dave Cheney |
10 years ago
|
|
|
2610
|
|
|
Jesse Meek |
10 years ago
|
|
|
2609
|
|
|
Casey Marshall |
10 years ago
|
|
|
2608
|
|
|
Michael Foord |
10 years ago
|
|
|
2607
|
|
|
Andrew Wilkins |
10 years ago
|
|
|
2606
|
|
|
William Reade |
10 years ago
|
|
|
2605
|
|
|
Roger Peppe |
10 years ago
|
|
|
2604
|
|
|
Tim Penhey |
10 years ago
|
|
|
2603
|
|
|
mattyw |
10 years ago
|
|
|
2602
|
|
[r=dimitern] various: Provision machines with networks
This changes a few things in the provisioner API: * AddNetworks() and AddNetworkInterfaces() are removed (both from state/api and state/apiserver); * SetInstanceInfo added (see below)
Changes in state: * Machine.SetInstanceInfo replaces the SetProvisioned method and does the same job, but also accepts two lists - networks and NICs to create, which are created before calling SetProvisioned internally. This is just a quick-and-dirty fix to enable VLAN support. Later, this method will be changed to execute all steps in a single transaction. As before, existing networks/interfaces are not an error when given to SetInstanceInfo, but invalid ones cause errors and stop the provisioning.
Changes in worker/provisioner: * Now, once we get the networks from StartInstance, we prepare the args and call SetInstanceInfo. * If SetInstanceInfo fails, we set StatusError on the machine, stop the instance and keep going instead of killing the provisioner task (added test for that).
Changes in provider/maas: * After lots of live testing, the procedure for getting networks for the instance, lists of connected MACs for each network and the discovered NICs of the instance, is completed and works. Some changes to the internals were needed to make sure it works with a live MAAS. * Fixed a small typo in the log message "picked arbitrary tools...".
Changes in provider/dummy: * Now the dummy provider prepares []environs.NetworkInfo when IncludeNetworks are given to StartInstance, and returns it. As a special case, network names with "bad-" prefix cause the dummy provider to generate invalid NetworkInfo so we can test failures on SetInstanceInfo.
Although this CL is got big, it's the penultimate step to have MAAS networks/VLANs support - the only thing left is to setup the discovered network interfaces as needed with cloudinit scripts, which will be done in a follow-up. But before that, as requested bug #1304905 will be fixed (s/NetworkName/NetworkId/ and add network tags througout).
https://codereview.appspot.com/85220044/
R=fwereade
|
Dimiter Naydenov |
10 years ago
|
|
|
2601
|
|
|
Dave Cheney |
10 years ago
|
|
|