<div dir="auto">Unfortunately Neutron doesn't know anything about the hypervisor to make that type of call. That will require support in Nova to listen for the port admin state change from Neutron and reflect it in the loaded hypervisor. <div dir="auto"><br></div><div dir="auto">It's worth filing a request with Nova to see if that's something they would accept. </div><div dir="auto"><br></div><div dir="auto">Nova already listens for port data plane status to unpause the VM on boot so that communication channel is already in place. </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Aug 11, 2017 01:21, "Volodymyr Litovka" <<a href="mailto:doka.ua@gmx.com">doka.ua@gmx.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    <br>
    <div class="m_8673467958336458686moz-cite-prefix">On 8/8/17 7:18 PM, Kevin Benton wrote:<br>
      <br>
    </div>
    <blockquote type="cite">
      <div dir="ltr">The best way to completely ensure the instance
        isn't trying to use it is to detach it from the instance using
        the 'nova interface-detach' command.</div>
    </blockquote>
    Sure, but this introduces additional complexity in complex
    environments when it's required to have predictable interface naming
    accordingly to roles (e.g. eth0 is always WAN connection, eth1 is
    always LAN1, eth2 is always control/mgmt, etc etc).
    Attaching/detaching interfaces changes this and requires to manage
    udev rules, which adds issues when creating new VM from snapshot,
    ... :-)<br>
    <br>
    Not too critical, everything can be handled using more or less
    complex workarounds, but, since libvirt has support to set interface
    state (using '<b>virsh domif-setlink domain interface-device state</b>'),
    why don't use this call to reflect interface state according to
    Openstack's settings?<br>
    <br>
    Thanks.<br>
    <blockquote type="cite">
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Tue, Aug 8, 2017 at 7:49 AM,
          Volodymyr Litovka <span dir="ltr"><<a href="mailto:doka.ua@gmx.com" target="_blank">doka.ua@gmx.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div text="#000000" bgcolor="#FFFFFF">
              <p><font face="SFNS Display">Hi Kevin,</font></p>
              see below<span><br>
                <br>
                <div class="m_8673467958336458686m_8858115156911540876moz-cite-prefix">On
                  8/8/17 1:06 AM, Kevin Benton wrote:<br>
                </div>
                <blockquote type="cite">
                  <div dir="ltr">What backend are you using? That bug is
                    about the port showing ACTIVE when
                    admin_state_up=False but it's still being
                    disconnected from the dataplane. If you are seeing
                    dataplane traffic with admin_state_up=False, then
                    that is a separate bug.</div>
                </blockquote>
              </span> I'm using OVS<span><br>
                <blockquote type="cite">
                  <div dir="ltr">
                    <div>Also, keep in mind that marking the port down
                      will still not be reflected inside of the VM via
                      ifconfig or ethtool. It will always show active in
                      there. So even after we fix bug 1672629, you are
                      going to see the port is connected inside of the
                      VM.</div>
                  </div>
                </blockquote>
              </span> Is there way to disconnect port, thus putting it
              into DOWN state on VM, using Openstack API ? This is
              important for <b>public clouds</b> when it can be
              necessary to shutdown port of unmanaged (customer's) VM.
              The only idea I have is to set admin_state_up to False
              and, actually, it's the only command, which control port
              state.<br>
              <br>
              As I mentioned earlier, it seems it was working in Kilo
              ("I have checked the behavior of admin_state_up of Kilo
              version, when port admin-state-up is set to False, the
              port status will be DOWN.") but Ocata shows another
              behaviour, ignoring this parameter.<br>
              <br>
              So, any ideas on how to shutdown port on VM using
              Openstack API?<br>
              <br>
              Thank you!<span><br>
                <blockquote type="cite">
                  <div class="gmail_extra"><br>
                    <div class="gmail_quote">On Mon, Aug 7, 2017 at 5:21
                      AM, Volodymyr Litovka <span dir="ltr"><<a href="mailto:doka.ua@gmx.com" target="_blank">doka.ua@gmx.com</a>></span>
                      wrote:<br>
                      <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                        <div text="#000000" bgcolor="#FFFFFF">
                          <p><font face="SFNS Display">Hi colleagues,</font></p>
                          <p><font face="SFNS Display">am I the only who
                              care about this case? - <a class="m_8673467958336458686m_8858115156911540876m_-3719320261500074392moz-txt-link-freetext" href="https://bugs.launchpad.net/neutron/+bug/1672629" target="_blank">https://bugs.launchpad.net/neu<wbr>tron/+bug/1672629</a></font></p>
                          <p><font face="SFNS Display">The problem is
                              when I set port admin_state_up to False,
                              it still UP on the VM thus continuing to
                              route statically configured networks (e.g.
                              received from DHCP host_routes), sending
                              DHCP reqs, etc</font></p>
                          <p><font face="SFNS Display">As people
                              discovered, in Kilo everything was ok - "</font>I
                            have checked the behavior of admin_state_up
                            of Kilo version, when port admin-state-up is
                            set to False, the port status will be DOWN."
                            - but at least in Ocata it is broken.</p>
                          <p>Anybody facing this problem too? Any ideas
                            on how to work around it?</p>
                          <p>Thank you.<span class="m_8673467958336458686m_8858115156911540876HOEnZb"><font color="#888888"><br>
                              </font></span></p>
                          <span class="m_8673467958336458686m_8858115156911540876HOEnZb"><font color="#888888">
                              <pre class="m_8673467958336458686m_8858115156911540876m_-3719320261500074392moz-signature" cols="72">-- 
Volodymyr Litovka
  "Vision without Execution is Hallucination." -- Thomas Edison
</pre>
                            </font></span></div>
                        <br>
                        ______________________________<wbr>_________________<br>
                        OpenStack-operators mailing list<br>
                        <a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.open<wbr>stack.org</a><br>
                        <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-operators</a><br>
                        <br>
                      </blockquote>
                    </div>
                    <br>
                  </div>
                </blockquote>
                <br>
                <pre class="m_8673467958336458686m_8858115156911540876moz-signature" cols="72">-- 
Volodymyr Litovka
  "Vision without Execution is Hallucination." -- Thomas Edison
</pre>
              </span></div>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
    <pre class="m_8673467958336458686moz-signature" cols="72">-- 
Volodymyr Litovka
  "Vision without Execution is Hallucination." -- Thomas Edison
</pre>
  </div>

</blockquote></div></div>