From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastian Blank Subject: Re: 4.3 Planning: Taking stock Date: Thu, 24 Jan 2013 13:57:30 +0100 Message-ID: <20130124125729.GA3466@waldi.eu.org> References: <6035A0D088A63A46850C3988ED045A4B3563C214@BITCOM1.int.sbss.com.au> <1359020727.17440.83.camel@zakaz.uk.xensource.com> <6035A0D088A63A46850C3988ED045A4B3563DB51@BITCOM1.int.sbss.com.au> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8631129455585573178==" Return-path: In-Reply-To: <6035A0D088A63A46850C3988ED045A4B3563DB51@BITCOM1.int.sbss.com.au> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: James Harper Cc: Ian Campbell , Konrad Rzeszutek Wilk , George Dunlap , "xen-devel@lists.xen.org" , Stefano Stabellini , Jan Beulich List-Id: xen-devel@lists.xenproject.org --===============8631129455585573178== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="d6Gm4EdcadzBjdND" Content-Disposition: inline --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Please fix four mail client. It lacks proper attribution and produces too long lines. On Thu, Jan 24, 2013 at 11:48:39AM +0000, James Harper wrote: > > The lack of a cleanup script getting run correctly on network devices > > was something Roger solved with his hotplug rework for xl in 4.2 > > (essentially the script used to be run after the backend was torn down > > in xenstore so it couldn't get at many of its parameters) > The problem here is that ovs remembers all the ports in its database. You= do add-port once and the port is there forever until you remove it again, = even over reboots. It's great for eth0 etc because everything "just works" = once ovs is started, but it's not so great for your vif's if your Dom0 cras= hes and you have stale ports around, or at least it isn't if you expect the= brctl compatibility layer to do the right thing. This is no problem as openvswitch does not add new devices, which appears somewhere after the setup on boot, to existing ports. At least my test setup works this way. And my script explicitely removes pre-existing ports. > A 'transient' option to ovs to not keep the port in the database would so= lve that problem, but such a thing doesn't seem to exist. Why don't wo handle this on your own with openvswitch upstream? Bastian --=20 Earth -- mother of the most beautiful women in the universe. -- Apollo, "Who Mourns for Adonais?" stardate 3468.1 --d6Gm4EdcadzBjdND Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAlEBL7QACgkQnw66O/MvCNG9UwCfWbVthiWc5K3vCkeg67Q90SBk FswAoI9s4CrG2IYcZi7ZuNc6jFB3UCDD =P7Km -----END PGP SIGNATURE----- --d6Gm4EdcadzBjdND-- --===============8631129455585573178== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============8631129455585573178==--