Loss of connection after reboot on single interface scenario on Windows

[Michał Cłapiński]

To reproduce:
1. Deploy Tungsten Fabric on Windows with single interface
2. Reboot compute node
In most cases compute node will lose connectivity.

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/48306
Submitter: Micha? C?api?ski (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/48308
Submitter: Micha? C?api?ski (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/48308
Committed: http://github.com/Juniper/contrail-windows-docker-driver/commit/93077729ba79259e3b4aead0b6c412b2272948e9
Submitter: Zuul v3 CI (<email address hidden>)
Branch: master

commit 93077729ba79259e3b4aead0b6c412b2272948e9
Author: Michal Clapinski <email address hidden>
Date: Thu Dec 20 17:42:00 2018 +0100

Wait for .spec file instead of pipe in contrail-autostart

1. Test-Path on pipes blocks them, so run it on .spec file
2. New-Item returns something, so silence it with Out-Null

Change-Id: I9ec28068dc6c29f378b122c961090ff22744963f
Partial-Bug: #1809282

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/48306
Committed: http://github.com/Juniper/contrail-vrouter/commit/86cd58b66bf7626000a5bd1957a6d150529e9dc7
Submitter: Zuul v3 CI (<email address hidden>)
Branch: master

commit 86cd58b66bf7626000a5bd1957a6d150529e9dc7
Author: Michal Clapinski <email address hidden>
Date: Thu Dec 20 17:22:02 2018 +0100

Clean basic NICs info before loading vrouter

In single interface scenario after reboot vrouter is enabled twice.
Sometimes connection loss could be noticed due to stale values in
basic NICs info. In this change we clean that info every time vrouter
is enabled.

Change-Id: I7fcd7b89d6b17e2419927faff2f8e5a0137836cb
Partial-Bug: #1809282