lp:~allenap/maas/node-networking-api-get-mac-addresses-and-interfaces

Branch merges

Propose for merging

No branches dependent on this one.

Rejected for merging into lp:~maas-committers/maas/trunk

Mike Pontillo (community): Needs Fixing on 2015-08-18

Blake Rouse (community): Needs Information on 2015-08-18

Diff: 203 lines (+191/-0)

2 files modified

src/maasserver/networking/__init__.py (+62/-0)
src/maasserver/networking/tests/test_networking.py (+129/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

4205. By Gavin Panella on 2015-08-18

Docstrings.

4204. By Gavin Panella on 2015-08-18

get_interfaces() works with nested interfaces.

4203. By Gavin Panella on 2015-08-18

NodeNetworking.get_mac_addresses() and NodeNetworking.get_interfaces().

4202. By Gavin Panella on 2015-08-18

Start of a maasserver/networking package.

4201. By Gavin Panella on 2015-08-18

[r=blake-rouse][bug=1485584][author=allenap] Forbid multiple interfaces with the same MAC and name, where a MAC is specified.

4200. By Gavin Panella on 2015-08-17

[r=andreserl][bug=1485677][author=allenap] Revert to the template-based IPMI power driver.

The new driver is not reliable yet. Once the cause is fixed this will be landed again.

4199. By Blake Rouse on 2015-08-17

[r=mpontillo][bug=1485584][author=blake-rouse] Move the creation of physical interface from start_up to its own migration. Fix that migration to use DISTINCT on the SELECT. Add migration that removes the extra interfaces linked to a MAC address.

4198. By Gavin Panella on 2015-08-17

[r=mpontillo][bug=][author=allenap] Replace lockfile.FileLock with a locking mechanism that works.

lockfile.FileLock permits double-locking of a file from the same process, making it unsuitable when a process contains multiple threads.

4197. By Gavin Panella on 2015-08-17

[r=blake-rouse][bug=1459168][author=allenap] Use non-transactional advisory locks for critical regions of DNS and security activity.

Previously locks were obtained after transactions had begun. This meant that, once the lock was acquired, the transaction may be working with stale data. This causes breakage when dealing with the shared-secret on the filesystem and when writing DNS zones with old data.

4196. By Gavin Panella on 2015-08-17

[r=blake-rouse][bug=1458895][author=allenap] Use non-transactional advisory locks when starting the region and setting up the event-loop.

Previously locks were obtained after the transaction had begun. This meant that, once the lock was acquired, the transaction may be working with stale data, resulting in serialization failures at best.