yahoo-eng-team team mailing list archive

[Armando Migliaccio <1005616@xxxxxxxxxxxxxxxxxx>]

This no longer applies.

Running the OVS quantum agent in dom0 only applies to Essex and I don't
thin that's on the support agenda.

** Changed in: neutron
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to quantum.
https://bugs.launchpad.net/bugs/1005616

Title:
  Windows instances may not get correct port configuration as set by
  quantum

Status in OpenStack Quantum (virtual network service):
  Invalid

Bug description:
  Typically Windows instances go through a sysprep configuration that
  may mean that the instance goes through a number of reboots before
  being fully up and running.

  In one of my deployments (XenServer-based) I have experienced that the
  command issued by ovs_quantum_agent gets wiped out while the VM is
  boostrapping. Below you'll find an example of the chain of events I
  saw:

  1) May 27 22:02:27 comp-3-6 ovs-vsctl: 00001|vsctl|INFO|Called as
  /usr/bin/ovs-vsctl --timeout=30 -- --if-exists del-port vif103.0 --
  add-port xapi2 vif103.0 -- set interface vif103.0 "external-ids:\"xs-
  vm-uuid\"=\"8d547a8b-429a-7729-6f2a-f01777659e16\"" -- set interface
  vif103.0 "external-ids:\"xs-vif-uuid\"=\"dc7c30ec-9cd0-eb62-d0fa-
  9e76cfc75e98\"" -- set interface vif103.0 "external-ids:\"xs-network-
  uuid\"=\"bebf9442-9791-67f8-ced0-7751ccfa1306\"" -- set interface
  vif103.0 "external-ids:\"attached-mac\"=\"fa:16:3e:10:0a:b2\""

  2) May 27 22:02:28 comp-3-6 ovs-vsctl: 00001|vsctl|INFO|Called as ovs-
  vsctl --timeout=2 set Port vif103.0 tag=2100

  3) May 27 22:02:49 comp-3-6 ovs-vsctl: 00001|vsctl|INFO|Called as
  /usr/bin/ovs-vsctl --timeout=30 -- --if-exists del-port vif103.0 --
  add-port xapi2 vif103.0 -- set interface vif103.0 "external-ids:\"xs-
  vm-uuid\"=\"8d547a8b-429a-7729-6f2a-f01777659e16\"" -- set interface
  vif103.0 "external-ids:\"xs-vif-uuid\"=\"dc7c30ec-9cd0-eb62-d0fa-
  9e76cfc75e98\"" -- set interface vif103.0 "external-ids:\"xs-network-
  uuid\"=\"bebf9442-9791-67f8-ced0-7751ccfa1306\"" -- set interface
  vif103.0 "external-ids:\"attached-mac\"=\"fa:16:3e:10:0a:b2\""

  1 and 3 are issued by the vif script in /etc/xensource/scripts/vif and
  2 is issued by the quantum agent; xapi2 is my integration-bridge,
  vif103.0 is my Windows VM's vif.

  Not sure how easy to reproduce this is, but the conclusion is: the
  ovs_quantum_agent may need to periodically re-apply configuration of
  the ports it knows about, because other system entities may interfere
  with it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1005616/+subscriptions