On 18-09-05 17:50:59, thomas.mo...@orange.com wrote: > Mathew, > > networking-odl has now been removed from the requirements of > networking-bgpvpn [1], on master, so networking-odl could be removed from > requirements. > > This is not the case on stable branches, though. > > -Thomas > > [1] https://review.openstack.org/#/c/599422/ > > On 05/09/2018 17:03, Matthew Thode wrote: > > On 18-08-31 19:52:09, Matthew Thode wrote: > > > The requirements project has a co-installability test for the various > > > projects, networking-odl being included. > > > > > > Because of the way the dependancy on ceilometer is done it is blocking > > > all reviews and updates to the requirements project. > > > > > > http://logs.openstack.org/96/594496/2/check/requirements-integration/8378cd8/job-output.txt.gz#_2018-08-31_22_54_49_357505 > > > > > > If networking-odl is not meant to be used as a library I'd recommend > > > it's removal from networking-bgpvpn (it's test-requirements.txt file). > > > Once that is done networking-odl can be removed from global-requirements > > > and we won't be blocked anymore. > > > > > > As a side note, fungi noticed that when you branched you are still > > > installing ceilometer from master. Also, the ceilometer team > > > doesnt wish it to be used as a library either (like networking-odl > > > doesn't wish to be used as a library). > > > > > The requirements team has gone ahead and made a aweful hack to get gate > > unwedged. The commit message is a very good summary of our reasoning > > why it has to be this way for now. My comment explains our plan going > > forward (there will be a revert prepared as soon as this merges for > > instance). > > > > step 1. merge this > > step 2. look into and possibly fix our tooling (why was the gitref addition > > not rejected by gate) > > step 3. fix networking-odl (release ceilometer) > > step 4. unmerge this > > > > > > __________________________________________________________________________ > > 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 > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. >
Yep, we discussed doing that (and it's still an option). We decided to do something a bit more verbose though and have a plan. Just need to get ceilometer to release to pypi... -- Matthew Thode (prometheanfire)
signature.asc
Description: 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
