4 Neutron (client, core, FwaaS, LBaaS, VPNaaS) maintains all of its bugs in the following
7 * `Launchpad Neutron <https://bugs.launchpad.net/neutron>`_
8 * `Launchpad python-neutronclient <https://bugs.launchpad.net/python-neutronclient>`_
11 Neutron Bugs Team In Launchpad
12 ------------------------------
14 The `Neutron Bugs <https://launchpad.net/~neutron-bugs>`_ team in Launchpad
15 is used to allow access to the projects above. Members of the above group
16 have the ability to set bug priorities, target bugs to releases, and other
17 administrative tasks around bugs. The administrators of this group are the
18 members of the `neutron-drivers-core
19 <https://review.openstack.org/#/admin/groups/464,members>`_ gerrit group.
20 Non administrators of this group include anyone who is involved with the
21 Neutron project and has a desire to assist with bug triage.
23 If you would like to join this Launchpad group, it's best to reach out to a
24 member of the above mentioned neutron-drivers-core team in #openstack-neutron
25 on Freenode and let them know why you would like to be a member. The team is
26 more than happy to add additional bug triage capability, but it helps to know
27 who is requesting access, and IRC is a quick way to make the connection.
29 As outlined below the bug deputy is a volunteer who wants to help with defect
30 management. Permissions will have to be granted assuming that people sign up
31 on the deputy role. The permission won't be given freely, a person must show
32 some degree of prior involvement.
38 Neutron maintains the notion of a "bug deputy". The bug deputy plays an
39 important role in the Neutron community. As a large project, Neutron is
40 routinely fielding many bug reports. The bug deputy is responsible for
41 acting as a "first contact" for these bug reports and performing initial
42 screening/triaging. The bug deputy is expected to communicate with the
43 various Neutron teams when a bug has been triaged. In addition, the bug
44 deputy should be reporting "High" and "Critical" priority bugs.
46 To avoid burnout, and to give a chance to everyone to gain experience in
47 defect management, the Neutron bug deputy is a rotating role. The rotation
48 will be set on a period (typically one or two weeks) determined by the team
49 during the weekly Neutron IRC meeting and/or according to holidays. During
50 the Neutron IRC meeting we will expect a volunteer to step up for the period.
51 Members of the Neutron core team are invited to fill in the role,
52 however non-core Neutron contributors who are interested are also
53 encouraged to take up the role.
55 This contributor is going to be the bug deputy for the period, and he/she
56 will be asked to report to the team during the subsequent IRC meeting. The
57 PTL will also work with the team to assess that everyone gets his/her fair
58 share at fulfilling this duty. It is reasonable to expect some imbalance
59 from time to time, and the team will work together to resolve it to ensure
60 that everyone is 100% effective and well rounded in their role as
61 _custodian_ of Neutron quality. Should the duty load be too much in busy
62 times of the release, the PTL and the team will work together to assess
63 whether more than one deputy is necessary in a given period.
65 The presence of a bug deputy does not mean the rest of the team is simply off
66 the hook for the period, in fact the bug deputy will have to actively work
67 with the Lieutenants/Drivers, and these should help in getting the bug report
68 moving down the resolution pipeline.
70 During the period a member acts as bug deputy, he/she is expected to watch
71 bugs filed against the Neutron projects (as listed above) and do a first
72 screening to determine potential severity, tagging, logstash queries, other
73 affected projects, affected releases, etc.
75 From time to time bugs will be filed and auto-assigned by members of the
76 core team to get them to a swift resolution. Obviously, the deputy is exempt
79 Finally, the PTL will work with the deputy to produce a brief summary of the
80 issues of the week to be shared with the larger team during the weekly IRC
81 meeting and tracked in the meeting notes.
84 Plugin and Driver Repositories
85 ------------------------------
87 Many plugins and drivers have backend code that exists in another repository.
88 These repositories may have their own Launchpad projects for bugs. The teams
89 working on the code in these repos assume full responsibility for bug handling
90 in those projects. For this reason, bugs whose solution would exist solely in
91 the plugin/driver repo should not have Neutron in the affected projects section.
92 However, you should add Neutron (Or any other project) to that list only if you
93 expect that a patch is needed to that repo in order to solve the bug.
95 It's also worth adding that some of these projects are part of the so
96 called Neutron `stadium <http://governance.openstack.org/reference/projects/neutron.html#deliverables-and-tags>`_.
97 Because of that, their release is managed centrally by the Neutron
98 release team; requests for releases need to be funnelled and screened
99 properly before they can happen. To this aim, the process to request a release
102 * Create a bug report to your Launchpad project: provide details as to what
103 you would like to release;
104 * Add Neutron to the list of affected projects.
105 * Add 'release-subproject' tag to the list of tags for the bug report.
106 * The Neutron release management team will watch these bugs, and work with
107 you to have the request fulfilled by following the instructions found `here <http://docs.openstack.org/developer/neutron/devref/sub_project_guidelines.html#sub-project-release-process>`_.
112 Bug Screening Best Practices
113 ----------------------------
115 When screening bug reports, the first step for the bug deputy is to assess
116 how well written the bug report is, and whether there is enough information
117 for anyone else besides the bug submitter to reproduce the bug and come up
118 with a fix. There is plenty of information on the `OpenStack wiki <https://wiki.openstack.org/wiki/Bugs>`_
119 on how to write a good bug `report <https://wiki.openstack.org/wiki/BugFilingRecommendations>`_
120 and to learn how to tell a good bug report from a bad one. Should the bug
121 report not adhere to these best practices, the bug deputy's first step
122 would be to redirect the submitter to this section, invite him/her to supply
123 the missing information, and mark the bug report as 'Incomplete'. For future
124 submissions, the reporter can then use the template provided below to ensure
125 speedy triaging. Done often enough, this practice should (ideally) ensure that
126 in the long run, only 'good' bug reports are going to be filed.
131 The more information you provide, the higher the chance of speedy triaging and
132 resolution: identifying the problem is half the solution. To this aim, when
133 writing a bug report, please consider supplying the following details and
134 following these suggestions:
136 * Summary (Bug title): keep it small, possibly one line. If you cannot describe
137 the issue in less than 100 characters, you are probably submitting more than
139 * Further information (Bug description): conversely from other bug trackers,
140 Launchpad does not provide a structured way of submitting bug-related
141 information, but everything goes in this section. Therefore, you are invited
142 to break down the description in the following fields:
144 * High level description: provide a brief sentence (a couple of lines) of
145 what are you trying to accomplish, or would like to accomplish differently;
146 the 'why' is important, but can be omitted if obvious (not to you of course).
147 * Pre-conditions: what is the initial state of your system? Please consider
148 enumerating resources available in the system, if useful in diagnosing
149 the problem. Who are you? A regular tenant or a super-user? Are you
150 describing service-to-service interaction?
151 * Step-by-step reproduction steps: these can be actual neutron client
152 commands or raw API requests; Grab the output if you think it is useful.
153 Please, consider using `paste.o.o <http://paste.openstack.org>`_ for long
154 outputs as Launchpad poorly format the description field, making the
155 reading experience somewhat painful.
156 * Expected output: what did you hope to see? How would you have expected the
157 system to behave? A specific error/success code? The output in a specific
158 format? Or more than a user was supposed to see, or less?
159 * Actual output: did the system silently fail (in this case log traces are
160 useful)? Did you get a different response from what you expected?
163 * OpenStack version (Specific stable branch, or git hash if from trunk);
164 * Linux distro, kernel. For a distro, it's also worth knowing specific
165 versions of client and server, not just major release;
166 * Relevant underlying processes such as openvswitch, iproute etc;
167 * DevStack or other _deployment_ mechanism?
169 * Environment: what services are you running (core services like DB and
170 AMQP broker, as well as Nova/hypervisor if it matters), and which type
171 of deployment (clustered servers); if you are running DevStack, is it a
172 single node? Is it multi-node? Are you reporting an issue in your own
173 environment or something you encountered in the OpenStack CI
174 Infrastructure, aka the Gate?
175 * Perceived severity: what would you consider the `importance <https://wiki.openstack.org/wiki/Bugs#Importance>`_
178 * Tags (Affected component): try to use the existing tags by relying on
179 auto-completion. Please, refrain from creating new ones, if you need
180 new "official" tags_, please reach out to the PTL. If you would like
181 a fix to be backported, please add a backport-potential tag.
182 This does not mean you are gonna get the backport, as the stable team needs
183 to follow the `stable branch policy <https://wiki.openstack.org/wiki/StableBranch#Stable_branch_policy>`_
184 for merging fixes to stable branches.
185 * Attachments: consider attaching logs, truncated log snippets are rarely
186 useful. Be proactive, and consider attaching redacted configuration files
187 if you can, as that will speed up the resolution process greatly.
193 The process of bug triaging consists of the following steps:
195 * Check if a bug was filed for a correct component (project). If not, either
196 change the project or mark it as "Invalid".
197 * Check if a similar bug was filed before. Rely on your memory if Launchpad
198 is not clever enough to spot a duplicate upon submission. If so, mark it
199 as a duplicate of the previous bug.
200 * Check if the bug meets the requirements of a good bug report, by checking
201 that the guidelines_ are being followed. Omitted information is still
202 acceptable if the issue is clear nonetheless; use your good judgement and
203 your experience. Consult another core member/PTL if in doubt. If the bug
204 report needs some love, mark the bug as 'Incomplete', point the submitter
205 to this document and hope he/she turns around quickly with the missing
208 If the bug report is sound, move next:
210 * Revise tags as recommended by the submitter. Ensure they are 'official'
212 * Depending on ease of reproduction (or if the issue can be spotted in the
213 code), mark it as 'Confirmed'. If you are unable to assess/triage the
214 issue because you do not have access to a repro environment, consider
215 reaching out the Lieutenant, go-to person for the affected component;
216 he/she may be able to help: assign the bug to him/her for further
217 screening. If the bug already has an assignee, check that a patch is
218 in progress. Sometimes more than one patch is required to address an
219 issue, make sure that there is at least one patch that 'Closes' the bug
220 or document/question what it takes to mark the bug as fixed.
221 * If the bug is the result of a misuse of the system, mark the bug either
222 as 'Won't fix', or 'Opinion' if you are still on the fence and need
223 other people's input.
224 * Assign the importance after reviewing the proposed severity. Bugs that
225 obviously break core and widely used functionality should get assigned as
226 "High" or "Critical" importance. The same applies to bugs that were filed
228 * Choose a milestone, if you can. Targeted bugs are especially important
229 close to the end of the release.
230 * (Optional). Add comments explaining the issue and possible strategy of
231 fixing/working around the bug. Also, as good as some are at adding all
232 thoughts to bugs, it is still helpful to share the in-progress items
233 that might not be captured in a bug description or during our weekly
234 meeting. In order to provide some guidance and reduce ramp up time as
235 we rotate, tagging bugs with 'needs-attention' can be useful to quickly
236 identify what reports need further screening/eyes on.
238 You are done! Iterate.
241 Bug Expiration Policy and Bug Squashing
242 ---------------------------------------
244 More can be found at this `Launchpad page <https://help.launchpad.net/BugExpiry>`_.
245 In a nutshell, in order to make a bug report expire automatically, it needs to be
246 unassigned, untargeted, and marked as Incomplete.
248 The OpenStack community has had `Bug Days <https://wiki.openstack.org/wiki/BugDays>`_
249 but they have not been wildly successful. In order to keep the list of open bugs set
250 to a manageable number (more like <100+, rather than closer to 1000+), at the end of
251 each release (in feature freeze and/or during less busy times), the PTL with the
252 help of team will go through the list of open (namely new, opinion, in progress,
253 confirmed, triaged) bugs, and do a major sweep to have the Launchpad Janitor pick
254 them up. This gives 60 days grace period to reporters/assignees to come back and
255 revive the bug. Assuming that at regime, bugs are properly reported, acknowledged
256 and fix-proposed, losing unaddressed issues is not going to be a major issue,
257 but brief stats will be collected to assess how the team is doing over time.
265 Launchpad's Bug Tracker allows you to create ad-hoc groups of bugs with tagging.
267 In the Neutron team, we have a list of agreed tags that we may apply to bugs
268 reported against various aspects of Neutron itself. The list of approved tags
269 used to be available on the `wiki <https://wiki.openstack.org/wiki/Bug_Tags#Neutron>`_,
270 however the section has been moved here, to improve collaborative editing, and
271 keep the information more current. By using a standard set of tags, each
272 explained on this page, we can avoid confusion. A bug report can have more than
273 one tag at any given time.
278 New tags, or changes in the meaning of existing tags (or deletion), are to be
279 proposed via patch to this section. After discussion, and approval, a member of
280 the bug team will create/delete the tag in Launchpad. Each tag covers an area
281 with an identified go-to contact or `Lieutenant <http://docs.openstack.org/developer/neutron/policies/core-reviewers.html#core-review-hierarchy>`_,
282 who can provide further insight. Bug queries are provided below for convenience,
283 more will be added over time if needed.
285 +-------------------------------+---------------------------------------+----------------------+
286 | Tag | Description | Contact |
287 +===============================+=======================================+======================+
288 | access-control_ | A bug affecting RBAC and policy.json | Kevin Benton |
289 +-------------------------------+---------------------------------------+----------------------+
290 | api_ | A bug affecting the API layer | Salvatore Orlando |
291 +-------------------------------+---------------------------------------+----------------------+
292 | baremetal_ | A bug affecting Ironic support | Sukhdev Kapur |
293 +-------------------------------+---------------------------------------+----------------------+
294 | db_ | A bug affecting the DB layer | Henry Gessau |
295 +-------------------------------+---------------------------------------+----------------------+
296 | dns_ | A bug affecting DNS integration | Miguel Lavalle |
297 +-------------------------------+---------------------------------------+----------------------+
298 | doc_ | A bug affecting in-tree doc | Edgar Magana |
299 +-------------------------------+---------------------------------------+----------------------+
300 | fullstack_ | A bug in the fullstack subtree | Assaf Muller |
301 +-------------------------------+---------------------------------------+----------------------+
302 | functional-tests_ | A bug in the functional tests subtree | Assaf Muller |
303 +-------------------------------+---------------------------------------+----------------------+
304 | fwaas_ | A bug affecting neutron-fwass | Sean Collins |
305 +-------------------------------+---------------------------------------+----------------------+
306 | gate-failure_ | A bug affecting gate stability | Armando Migliaccio |
307 +-------------------------------+---------------------------------------+----------------------+
308 | ipv6_ | A bug affecting IPv6 support | Henry Gessau |
309 +-------------------------------+---------------------------------------+----------------------+
310 | l2-pop_ | A bug in L2 Population mech driver | Kevin Benton |
311 +-------------------------------+---------------------------------------+----------------------+
312 | l3-dvr-backlog_ | A bug affecting distributed routing | Ryan Moats |
313 +-------------------------------+---------------------------------------+----------------------+
314 | l3-ha_ | A bug affecting L3 HA (vrrp) | Assaf Muller |
315 +-------------------------------+---------------------------------------+----------------------+
316 | l3-ipam-dhcp_ | A bug affecting L3/DHCP/metadata | Miguel Lavalle |
317 +-------------------------------+---------------------------------------+----------------------+
318 | lbaas_ | A bug affecting neutron-lbaas | Brandon Logan |
319 +-------------------------------+---------------------------------------+----------------------+
320 | linuxbridge_ | A bug affecting ML2/linuxbridge | Sean Collins |
321 +-------------------------------+---------------------------------------+----------------------+
322 | loadimpact_ | Performance penalty/improvements | Ryan Moats |
323 +-------------------------------+---------------------------------------+----------------------+
324 | logging_ | An issue with logging guidelines | Matt Riedemann |
325 +-------------------------------+---------------------------------------+----------------------+
326 | low-hanging-fruit_ | Starter bugs for new contributors | N/A |
327 +-------------------------------+---------------------------------------+----------------------+
328 | metering_ | A bug affecting the metering layer | ? |
329 +-------------------------------+---------------------------------------+----------------------+
330 | needs-attention_ | A bug that needs further screening | PTL/Bug Deputy |
331 +-------------------------------+---------------------------------------+----------------------+
332 | opnfv_ | Reported by/affecting OPNFV initiative| Drivers team |
333 +-------------------------------+---------------------------------------+----------------------+
334 | ops_ | Reported by or affecting operators | Drivers Team |
335 +-------------------------------+---------------------------------------+----------------------+
336 | oslo_ | An interop/cross-project issue | Ihar Hrachyshka |
337 +-------------------------------+---------------------------------------+----------------------+
338 | ovs_ | A bug affecting ML2/OVS | Kevin Benton |
339 +-------------------------------+---------------------------------------+----------------------+
340 | ovs-lib_ | A bug affecting OVS Lib | Terry Wilson |
341 +-------------------------------+---------------------------------------+----------------------+
342 | py34_ | Issues affecting the Python 3 porting | Cedric Brandily |
343 +-------------------------------+---------------------------------------+----------------------+
344 | qos_ | A bug affecting ML2/QoS | Miguel Ajo |
345 +-------------------------------+---------------------------------------+----------------------+
346 | released-neutronclient_ | A bug affecting released clients | Kyle Mestery |
347 +-------------------------------+---------------------------------------+----------------------+
348 | release-subproject_ | A request to release a subproject | Kyle Mestery |
349 +-------------------------------+---------------------------------------+----------------------+
350 | rfe_ | Feature enhancements being screened | Drivers Team |
351 +-------------------------------+---------------------------------------+----------------------+
352 | rfe-approved_ | Approved feature enhancements | Drivers Team |
353 +-------------------------------+---------------------------------------+----------------------+
354 | sg-fw_ | A bug affecting security groups | Kevin Benton |
355 +-------------------------------+---------------------------------------+----------------------+
356 | sriov-pci-pt_ | A bug affecting Sriov/PCI PassThrough | Moshe Levi |
357 +-------------------------------+---------------------------------------+----------------------+
358 | troubleshooting_ | An issue affecting ease of debugging | Assaf Muller |
359 +-------------------------------+---------------------------------------+----------------------+
360 | unittest_ | A bug affecting the unit test subtree | Cedric Brandily |
361 +-------------------------------+---------------------------------------+----------------------+
362 | usability_ | UX, interoperability, feature parity | PTL/Drivers Team |
363 +-------------------------------+---------------------------------------+----------------------+
364 | vpnaas_ | A bug affecting neutron-vpnaas | Paul Michali |
365 +-------------------------------+---------------------------------------+----------------------+
366 | xxx-backport-potential_ | Cherry-pick request for stable team | Ihar Hrachyshka |
367 +-------------------------------+---------------------------------------+----------------------+
374 * `Access Control - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=access-control>`_
375 * `Access Control - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=access-control>`_
382 * `API - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=api>`_
383 * `API - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=api>`_
390 * `Baremetal - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=baremetal>`_
391 * `Baremetal - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=baremetal>`_
398 * `DB - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=db>`_
399 * `DB - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=db>`_
406 * `DNS - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=dns>`_
407 * `DNS - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=dns>`_
414 * `DOC - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=doc>`_
415 * `DOC - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=doc>`_
422 * `Fullstack - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=fullstack>`_
423 * `Fullstack - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=fullstack>`_
425 .. _functional-tests:
430 * `Functional tests - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=functional-tests>`_
431 * `Functional tests - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=functional-tests>`_
438 * `FWaaS - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=fwaas>`_
439 * `FWaaS - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=fwaas>`_
446 * `Gate failure - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=gate-failure>`_
447 * `Gate failure - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=gate-failure>`_
454 * `IPv6 - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=ipv6>`_
455 * `IPv6 - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=ipv6>`_
462 * `L2 Pop - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=l2-pop>`_
463 * `L2 Pop - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=l2-pop>`_
470 * `L3 DVR - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=l3-dvr-backlog>`_
471 * `L3 DVR - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=l3-dvr-backlog>`_
478 * `L3 HA - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=l3-ha>`_
479 * `L3 HA - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=l3-ha>`_
486 * `L3 IPAM DHCP - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=l3-ipam-dhcp>`_
487 * `L3 IPAM DHCP - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=l3-ipam-dhcp>`_
494 * `LBaaS - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=lbaas>`_
495 * `LBaaS - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=lbaas>`_
502 * `LinuxBridge - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=linuxbridge>`_
503 * `LinuxBridge - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=linuxbridge>`_
510 * `Load Impact - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=loadimpact>`_
511 * `Load Impact - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=loadimpact>`_
518 * `Logging - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=logging>`_
519 * `Logging - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=logging>`_
521 .. _low-hanging-fruit:
526 * `Low hanging fruit - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=low-hanging-fruit>`_
527 * `Low hanging fruit - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=low-hanging-fruit>`_
534 * `Metering - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=metering>`_
535 * `Metering - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=metering>`_
542 * `Needs Attention - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=needs-attention>`_
549 * `OPNFV - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=opnfv>`_
553 Operators/Operations (ops)
554 ++++++++++++++++++++++++++
556 * `Ops - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=ops>`_
563 * `Oslo - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=oslo>`_
564 * `Oslo - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=oslo>`_
571 * `OVS - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=ovs>`_
572 * `OVS - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=ovs>`_
579 * `OVS Lib - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=ovs-lib>`_
580 * `OVS Lib - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=ovs-lib>`_
587 * `Py34 - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=py34>`_
588 * `Py34 - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=py34>`_
595 * `QoS - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=qos>`_
596 * `QoS - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=qos>`_
598 .. _released-neutronclient:
600 Released Neutron Client
601 +++++++++++++++++++++++
603 * `Released Neutron Client - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=released-neutronclient>`_
604 * `Released Neutron Client - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=released-neutronclient>`_
606 .. _release-subproject:
611 * `Release Subproject - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=release-subproject>`_
612 * `Release Subproject - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=release-subproject>`_
619 * `RFE - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=rfe>`_
620 * `RFE - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=rfe>`_
627 * `RFE-Approved - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=rfe-approved>`_
628 * `RFE-Approved - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=rfe-approved>`_
632 SRIOV-PCI PASSTHROUGH
633 +++++++++++++++++++++
635 * `SRIOV/PCI-PT - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=sriov-pci-pt>`_
636 * `SRIOV/PCI-PT - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=sriov-pci-pt>`_
643 * `Security groups - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=sg-fw>`_
644 * `Security groups - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=sg-fw>`_
651 * `Troubleshooting - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=Troubleshooting>`_
652 * `Troubleshooting - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=Troubleshooting>`_
659 * `Unit test - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=unittest>`_
660 * `Unit test - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=unittest>`_
667 * `UX - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=usability>`_
668 * `UX - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=usability>`_
675 * `VPNaaS - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=vpnaas>`_
676 * `VPNaaS - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=vpnaas>`_
678 .. _xxx-backport-potential:
680 Backport/RC potential
681 +++++++++++++++++++++
683 * `All Liberty bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=liberty-backport-potential>`_
684 * `All Kilo bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=kilo-backport-potential>`_
685 * `All Juno bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=juno-backport-potential>`_