
--IO7NNQOluoOKbJ3SiH5OQ2qAtQXtRVcvw Content-Type: multipart/mixed; boundary="fNDvEC3nBnSjb0l71fCnA3e548ooCxqfJ"; protected-headers="v1" From: Sven Kieske <s.kieske@mittwald.de> To: devel@ovirt.org Message-ID: <a9c99f7a-82b6-bc93-6e01-ce36666d3b4d@mittwald.de> Subject: Re: [ovirt-devel] Heads-up: moving Libvirt xml creation to the engine References: <929621053.971772.1479905980625.JavaMail.zimbra@redhat.com> In-Reply-To: <929621053.971772.1479905980625.JavaMail.zimbra@redhat.com> --fNDvEC3nBnSjb0l71fCnA3e548ooCxqfJ Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi, very first question which comes to mind is: will vdsm hooks which alter the libvirt xml still work? I believe this is a much used feature and if it would not work anymore out of the box this would be a huge pain in upgrading existing systems. furthermore I don't really see the benfits when you generate the xml in engine: you still need to alter it in vdsm as you write, to fill in host specific things like storagepaths anyway, meaning you have to maintain twice the codebase _and_ coordinate between the two of them, so nothing goes wrong if one project changes something in the xml. but this are just my 2 cent :-) --=20 Mit freundlichen Gr=FC=DFen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG K=F6nigsberger Stra=DFe 6 32339 Espelkamp T: +495772 293100 F: +495772 293333 https://www.mittwald.de Gesch=E4ftsf=FChrer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhause= n Komplement=E4rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynha= usen --fNDvEC3nBnSjb0l71fCnA3e548ooCxqfJ-- --IO7NNQOluoOKbJ3SiH5OQ2qAtQXtRVcvw Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJYNZdbAAoJEMby9TMDAbQR/9AP/2vV10htQJ451J34OG0IdaVz UDHpVAAwlDp167ijmCYi5j8/cWhpu8bVl19p9N1euWRuNMv/8Z425IaNPp5kqM7u kL5ytNpcpTh36yhRbTT1tXl4gdttk+2vsHJ6KnKroIDSAVKHWQEfqJcOAfwMUJh5 5IBMT5f34y0x8DItEGA8sak26fP/UeaH71ZuKbKB2DUpNPWcebeId91XjTj0VjPf HkVbcvac8G96AooaTaNcs8w2U9ZRIEDBtlDNpJ99tjq6vCGa/ND4HiwPuYjY017M 1/knq0zSSnSZpMamcvgQ7YXY3puLCyiR6spOtqHdk6Xxk3xGlnrdt3dR3NLMZkjL PYXi1oUthGj5kSqegQB+kz2YrQ3tKwZvArtWNi6f701jtNRzFlnOouiKYTdhT/AM vvtRDmLaBhJB9jObDvoVht+Mwlr0znVzwH18Oh6R3PSlnX47RluMEU0eG99JA0vQ 6kUyyaAAPBtarFqWIHialE7dJXfnEOjfdxDPS1azyRowv6T1hvtXUUflJ24bh5HK XP1PdJlttdBDxWJ6wFiQlsaEyEFjPBvNKwf88NLQ9TP7MYhRnCXeSNwVJG1vb6ua pIltWX/PhSnVKO15PUcnlgXpb49yVxuxahYRA7YpQL/psmZBmVf2lrCNmfr7NNVt RaYR6mM2SLTdHWYJlKIi =uOPB -----END PGP SIGNATURE----- --IO7NNQOluoOKbJ3SiH5OQ2qAtQXtRVcvw--