Reviewed: https://review.openstack.org/453036 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=cc59e9f159ace557a61586e1df3f4d0b6054ed2f Submitter: Jenkins Branch: master
commit cc59e9f159ace557a61586e1df3f4d0b6054ed2f Author: Kevin Benton <[email protected]> Date: Tue Apr 4 00:06:52 2017 -0700 Remove EXTERNAL_NETWORK callbacks external networks are not really independent resources that have their own lifecycles independent from networks. The only use cases for this callback can be achieved with just regular NETWORK callbacks. The only users of this event have been adjusted to use NETWORK callbacks (according to codesearch.openstack.org). Closes-Bug: #1678041 Change-Id: Ie8249ddc3de643bfcb5c97480f30dc3500699256 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1678041 Title: eliminate callbacks for EXTERNAL_NETWORK Status in neutron: Fix Released Bug description: EXTERNAL_NETWORK is not a real resource. It's just a network with a specific attribute so having an independent callback is not necessary, nor do the semantics make sense (e.g. a network changing from external to non-external is a DELETE or an UPDATE?). We should be able to get by with just NETWORK events. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1678041/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
