lp://staging/~maas-deployers/maas-deployer/next
- Get this branch:
- bzr branch lp://staging/~maas-deployers/maas-deployer/next
Branch merges
Branch information
Recent revisions
- 78. By Edward Hope-Morley
-
Skip get_status for images import
MAAS 1.9 api seems to behave differently to before and no longer
returns JSON so skipping check until we have a better fix.Closes-Bug: 1630325
- 77. By Billy Olsen
-
Split 'arch' into 'build_arch' and 'kernel_arch'
This allows to make a clear differentiation what's the expected 'arch'
in libvirt (kernel arch) versus the 'arch' expected by MAAS (build arch).So users can define the arch in deployment.yaml as 'ppc64el' or 'pp64'
and get a functional deployment, as the juju/maas vms will be launched
using 'ppc64' and using the ubuntu ppc64el cloud image.Closes-Bug: #1570218
- 76. By Billy Olsen
-
[freyes] Add python 3.5 support
This is specially important when running maas-deployer in Xenial, because
MAAS API client package (python3-maas-client) is only available for python3 - 75. By Billy Olsen
-
[freyes] Fix check of 'ls' output
In Xenial the output of the path in ls for no such file or directory is
surrounded by single quotes, while in Trusty is not. This patch checks
for both possible outputs and if none is found, then the test is marked
as fail. - 74. By Billy Olsen
-
[hopem,
r=billy- olsen] Don't fetch csrf token if non-existent in response.
Closes Bug: #1577910
- 72. By Billy Olsen
-
[hopem,
r=billy- olsen] add juju_environment option section and
default_series= trusty. - 69. By Billy Olsen
-
[freyes, r=billy-olsen]
Add 'virtual-nodes' config key to create extra VMs during deployment.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp://staging/maas-deployer