-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 24/08/14 20:40, Maru Newby wrote: > > On Aug 24, 2014, at 5:14 PM, Henry Gessau <ges...@cisco.com> > wrote: > >> Ihar Hrachyshka <ihrac...@redhat.com> wrote: >>> Now, maybe putting the module into requirements.txt is an >>> overkill (though I doubt it). In that case, we could be >>> interested in getting the info in some other centralized way. >> >> Maru is of the opinion that it is overkill. I feel the same way, >> but I am not involved much with deployment issues so my feelings >> should not sway anyone. >> >> Note that ncclient is not the only package used by vendor >> solutions that is not listed in requirements.txt. The ones I am >> aware of are: >> >> ncclient (cisco and brocade) heleosapi (embrane) >> a10_neutron_lbaas (a10networks) >> >> Maybe we should start exploring "some other centralized way" to >> list these type of dependencies? > > I think each plugin should be able to have its own requirements.txt > file to aid in manual deployment and in packaging of a given > plugin. This suggests the need to maintain a global plugin > requirements file (in the tree) to ensure use of only a single > version of any dependencies used across more than one plugin. > > Given that 3rd party CI is likely having to install these > dependencies anyway, I think it would be good to make this > deployment reproducible while avoiding the need to add new > dependencies to core Neutron. >
With plans to move most of plugins into separate trees, we will probably just move those plugin specific dependencies there, so that dependencies are both explicit AND not adding exotic dependencies to core package. This sounds like work for after-split time (=after Juno). /Ihar -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUDV53AAoJEC5aWaUY1u57qIIIANFifDL2/orIqZ4HL12IWteG YpQrExTHdPksz02gv2WAzbvegcIplHdoJ057vTMYxLXxDKYwomhXkF1AD0ByNsVZ 6gJUYtmNclBGXv1Mf9bDa7xue69Ce/imrRuNbycov+0bZcBm4ilavX2HF6vv3TMW AxF3N3FXlc+hIJYhu8SkgHoHDvonh+/oZ8KCQ8t53uAZWR54wUavQkIo7pwRVlcA CJeJPXWB+nFJVfl5a8yZAUtobhyaN5gJlftLvP4ZcLDTeIpIyaP12Kzf7Ui9f55B STK6VPBQcIr5rN85XaHm0h60bzOaRcJn0wj3pGDv2kEUEEldnLPXpLsRGsnFcnk= =EeG1 -----END PGP SIGNATURE----- _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev