for many of endpoint classes, which methods are for RPC is not clear
Bug #1413041 reported by
YAMAMOTO Takashi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
as discussed in https:/
for many of RPC endpoint classes, there are no clear separation between internal methods and RPC methods.
heavy uses of mixing made the situation worse.
| Changed in neutron: | |
| assignee: | nobody → YAMAMOTO Takashi (yamamoto) |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on neutron (master) | #1 |
Revision history for this message
| Armando Migliaccio (armando-migliaccio) wrote | #2 |
| Changed in neutron: | |
| assignee: | YAMAMOTO Takashi (yamamoto) → nobody |
| status: | In Progress → Incomplete |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in neutron: | |
| status: | Incomplete → Expired |
To post a comment you must log in.
Change abandoned by Kyle Mestery (<email address hidden>) on branch: master
Review: https:/
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.