~mpontillo/maas:backport-index-on-ip-family--2.2

Last commit made on 2017-07-10
Get this branch:
git clone -b backport-index-on-ip-family--2.2 https://git.launchpad.net/~mpontillo/maas
Only Mike Pontillo can upload to this branch. If you are Mike Pontillo please log in for upload directions.

Branch merges

Branch information

Name:
backport-index-on-ip-family--2.2
Repository:
lp:~mpontillo/maas

Recent commits

c02824b... by Mike Pontillo

Add index on family(ip) for each StaticIPAddress.

 * This change greatly improves the execution time of the
   maasserver_routable_pairs view.

LP: #1702669

767ed0e... by Blake Rouse

Backport #1703403: Lower the maximum number of connections per worker to 9 connections is allowed as 1 is reserved for the .

Allowing each worker to have a maximum of 10 connections open at a time. A region controller with 4 workers will use a maximum of 40 connections. This allows 2 region controllers to run without needing to increase the maximum number of PostgreSQL connection (default is 100 connections).

3e0d3eb... by Andres Rodriguez

snap/snapcraft.yaml: Add missing dependency to 'bzr'

c0bd1dd... by Newell Jensen

Allows the domain of controllers to be changed in the UI.

Backport of aaf45021ce806cebd1700e5fd5403b94c08965fd from master.

d6e7440... by Andres Rodriguez

Add CHANGELOG entry for 2.2.2

bf2ab1f... by Andres Rodriguez

Merge packaging into 2.2

2a6d96e... by Blake Rouse

Backport d39a0e21fd14125a6cceb45cd692d34051f4a474 from master: Fix machinesTable directive so that it works with vs-repeat.

The machines, filteredMachines, and osinfo where placed on the scope directly. Once vs-repeat was added it changed the scope inside the directive to be the scope of vs-repeat and not the scope of machines-table. Moving those variables to the table variable on the machines-table scope fixes the issue as the table object will be copied by reference into the nested vs-repeat scope.

0adb563... by Andres Rodriguez

Update CHANGELOG

cab4bf5... by Lee Trager

Backport from master: Run badblocks using the physical blocksize of the disk.

By default badblocks always runs using a blocksize of 1024 and uses a 32bit int for the number of blocks it can test. For large disks the number of blocks exceeds the 32bit int limit and causes badblocks to fail. Many large uses use a larger physical blocksize which avoids hitting the 32bit int limit which helps avoid hitting LP:1695229.

88f916f... by Blake Rouse

Use calc-snap-version to generate the snap name.

Backport of be118a137d38299060fd323c98c9b1bc44ff2569 and d2e085af59091bfecffe181f4532ab898501aa09 from master.