From df996b9a7e3efef95ed01827d6125ed6475222f1 Mon Sep 17 00:00:00 2001 From: Moshe Levi Date: Thu, 24 Jan 2019 11:48:06 +0200 Subject: [PATCH] Better explain how do we know that the Smart NIC is ready to be programmed This is a follow-up patch to f358fbdde9a1cadc838327b8bf34ee54a7e7f43a which clarifies how do we know that the Smart NIC is ready to be programmed Change-Id: I896e3811b801784fa07475d5f48e3794e254c450 --- specs/approved/support-smart-nic.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/specs/approved/support-smart-nic.rst b/specs/approved/support-smart-nic.rst index 13f5b62c..f8a869f6 100755 --- a/specs/approved/support-smart-nic.rst +++ b/specs/approved/support-smart-nic.rst @@ -104,7 +104,8 @@ The enhancements for Neutron OVS L2 agent captured in [1]_, [2]_ and [3]_. deployment interfaces will intermittently boot the baremetal into the BIOS shell, providing a state where the ovs on the smart NIC may be configured properly before rebooting the bare metal into the actual guest image or - ramdisk. + ramdisk. The ovs on the smart NIC will get programmed after we verify that + the neutron ovs agent is alive. The following code for configure/unconfigure network: