-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all,
I was asked to point out to upstream community that the way we did advanced service split introduced some challenges on the packaging side. Specifically, to make upgrade scenario from Juno to Kilo smooth for RDO users, we need to introduce a circular dependency between openstack-neutron and new openstack-neutron-*aas packages. Without that, users that used any of *aas services in Juno would not get *aas code installed during Kilo upgrade, and their setup would become broken. Circular dependencies are not a simple matter when it comes to CI that we run against our packages and requires some tweaks to the way we validate that generated packages are installable. Note that in case of pip-managed installations, upgrade scenario is still broken since we don't install *aas when neutron is upgraded to Kilo. We are handling the case in devstack, but for those who rely on some third party packaging tool that does not know about the hidden upgrade interdependency, it may become a problem. So just a heads-up for anyone involved in neutron packaging. /Ihar -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVAWRTAAoJEC5aWaUY1u57F1cH/jjD+IpYdEufN+M05qFqj89N 5VWX5whklW/g3VD7VT92UFqISrr2Cp74QHaRGRa2vumX2LEfGsI+4CHBv+vSPXqG 1FaDj1s7wPBQW3SKVpuaUhdTOnsb0FkzQAoXFoTKECznLCSXSJxrrOPbv+qbI3kb Y+5HlpjeJAgZOE3WMlsn6dP0cpRCuQgZwq9htiO4ov09YwX3XAyOOHpkDcz97KYe //8ghHo9GRYgo1VlgdN8NAYGCfQoy5NS9cqnnEF3JZcV8JoDF7tAk07800M78Qdn YsY9UXRMdrb826ezv+7428baqeZPDPB9G+DfmjFqxIJ0BAuJeqxCDu8PflD0YA8= =6KZu -----END PGP SIGNATURE----- __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
