NFV Issue Tracker: Difference between revisions

From NFVwiki
No edit summary
No edit summary
 
(75 intermediate revisions by 5 users not shown)
Line 1: Line 1:
The following DRAFTs are working documents of ETSI ISG NFV. They are provided for information only and are still under development within ETSI ISG NFV. DRAFTS may be updated, deleted, replaced, or obsoleted by other documents at any time.
== Login to the Issue Tracker ==
'''Login with EOL:''' NFV members and participants can login to the ETSI NFV Issue Tracker with their '''ETSI Online (EOL) account''' (used to log into the ETSI Portal).  


ETSI and its Members accept no liability for any further use/implementation of the following DRAFTs.
Go to the [https://forge.etsi.org/rep/nfv/issues ETSI NFV Issue Tracker] and login.
Do not use as reference material.
Do not cite these documents other than as "work in progress"


To report feedback on a public DRAFT, click on "Submit issue"
User with '''EOL account''' can view and create issues, but users without EOL account can only view issues.


{| class="wikitable"
Issue tracker allows normal users to submit new issues and view public issues, but does not allow to process issues.
! style="font-weight: bold;" | DRAFT
! style="font-weight: bold;" | Issue Tracker
|-
| NFV-EVE001 "Hypervisor Rqmts spec"
|
|-
| NFV-EVE002 "MEF Use Cases report"
|
|-
| NFV-EVE003 "NFVI Node  Arch report"
|
|-
| NFV-EVE004 "Virtualisation technologies Report"
|
|-
| NFV-EVE005 "SDN usage in NFV Report"
|
|-
| NFV-IFA001 "Acceleration 1 - UCs report"
|
|-
| NFV-IFA002 "Acceleration 2 - VNF Intface Spec"
|
|-
| NFV-IFA003 "Acceleration  3 - vSwitch Spec"
|
|-
| NFV-IFA004 "Acceleration  4 - Mgmt aspects Spec"
|
|-
| NFV-IFA005 "Or-Vi  ref point Spec"
|
|-
| NFV-IFA006 "Vi-Vnfm ref point Spec"
|
|-
| NFV-IFA007 "Or-Vnfm ref point Spec"
|
|-
| NFV-IFA008 "Ve-Vnfm ref point Spec"
|
|-
| NFV-IFA009 "MANO architectural options report"
|
|-
| NFV-IFA010 "MANO Functional Rqmts Spec"
|
|-
| NFV-IFA011 "VNF Packaging Spec"
|
|-
| NFV-IFA012 "Os-Ma-Nfvo ref  point Spec -  svc mgmt & info model"
|
|-
| NFV-IFA013 "Os-Ma-Nfvo ref  point Spec - info model"
|
|-
| NFV-IFA014 "Network Service Templates Specification"
|
|-
| NFV-REL002 "Scalable Arch for Reliability Report"
|
|-
| NFV-REL003 "E2E reliability models report"
|
|-
| NFV-REL004 "Active monitoring & failure detection report"
|
|-
| NFV-SEC002 "Security features in mgmt sofware report"
|
|-
| NFV-SEC004 "LI report"
|
|-
| NFV-SEC005 "Certificate mgmt report"
|
|-
| NFV-SEC006 "Sec & Regulation report"
|
|-
| NFV-SEC007 "NFV Attestation report"
|
|-
| NFV-SEC008 "Security Monitoring report"
|
|-
| NFV-SEC009 "UCs for multi-layer host admin"
|
|-
| NFV-TST001 "Pre-deployment Validation report"
|
|-
| NFV-TST002 "Iop Testing Methodology report"
|
|}


Chairs, Vice-Chairs, and Rapporteurs have a "'''Developer'''" or "'''Maintainer'''" role, which additionally allows viewing private issues and processing issues.


NFV-EVE001 "Hypervisor Rqmts spec"
[[File:Login bug tracker.png|599x599px]]


NFV-EVE002 "MEF Use Cases report"
== View Issues ==
1. Go to the [https://forge.etsi.org/rep/nfv/issues ETSI NFV Issue Tracker] and login.


NFV-EVE003 "NFVI Node  Arch report"
2. To view the list of all issues, click "'''Issues'''" under "'''Pinned'''" drop down button.


NFV-EVE004 "Virtualisation technologies Report"
3. To view issues by '''assignee''', '''author''', or '''label''', click the search bar and choose the relevant option.


NFV-EVE005 "SDN usage in NFV Report"
4. To find issues related to a specific '''specification''', '''version''', or '''other details''', use the '''search bar''' to enter your keywords.


NFV-IFA001 "Acceleration 1 - UCs report"
[[File:Review issues.png|707x707px]]


NFV-IFA002 "Acceleration 2 - VNF Intface Spec"


NFV-IFA003 "Acceleration  3 - vSwitch Spec"
5. To view the details of a specific issue, click title of the issue.


NFV-IFA004 "Acceleration  4 - Mgmt aspects Spec"
[[File:To open existing issue.png|707x707px]]


NFV-IFA005 "Or-Vi  ref point Spec"
=== Else how to navigate to the Issues Repository ===
1. Go to the [https://forge.etsi.org/rep/nfv/ ETSI Forge NFV Group].


NFV-IFA006 "Vi-Vnfm ref point Spec"
2. Click on the "'''Issues'''" repository.


NFV-IFA007 "Or-Vnfm ref point Spec"
[[File:Navigate to issues repo.png|707x707px]]


NFV-IFA008 "Ve-Vnfm ref point Spec"
3. View issues as mentioned in the [https://nfvprivatewiki.etsi.org/index.php?title=Issue_Tracker_Process#:~:text=2.%20To%20view%20the%20list%20of%20all%20issues%2C%20click%20%22Issues%22%20under%20%22Pinned%22%20drop%20down%20button. Step 2] of the previous section.


NFV-IFA009 "MANO architectural options report"
== Submitting an Issue to the Issue Tracker ==


NFV-IFA010 "MANO Functional Rqmts Spec"
=== For Non-EOL Users ===
Non-EOL users cannot report issues directly via the '''ETSI NFV Issue Tracker'''. However, it is recommended that they submit their issues by sending an email to "'''NFVsupport@etsi.org"'''.


NFV-IFA011 "VNF Packaging Spec"
=== For EOL Users ===
Go to the [https://forge.etsi.org/rep/nfv/issues/-/issues ETSI NFV Issue Tracker] and login.


NFV-IFA012 "Os-Ma-Nfvo ref  point Spec -  svc mgmt & info model"
Before creating a new issue, please check that:


NFV-IFA013 "Os-Ma-Nfvo ref  point Spec - info model"
a) The issue still exists in the latest version of the respective GS document, and


NFV-IFA014 "Network Service Templates Specification"
b) The issue has not yet been reported by someone else. If the latter is the case, please add a comment to the existing issue rather than reporting a new one.


NFV-REL002 "Scalable Arch for Reliability Report"
To create a new issue:
# Go to [https://forge.etsi.org/rep/nfv/issues ETSI NFV Issue Tracker], click "'''Issues'''" under "'''Pinned'''" drop down button, and click "'''New issue'''".[[File:New issue.png|center|806x806px]]
# The '''Type''' is default set to "'''Issue'''" don't change it.
# '''Issue Title:''' In the issue Title input field, provide a clear and concise one-line summary of the issue.
#* '''Following the format: [Version] <NFV-Specification> <Issue_title>'''
#* '''For example:''' [v5.1.1] NFV-SOL003 Missing attribute in Query Compute Resources
#'''Issue description:''' In the description input box, clearly explain the issue. Describe what the issue is, what the expected outcome should be, and include any additional details or links to relevant documents if available.
#'''Setting additional fields:'''
#*'''Assignee:'''  If you are going to resolve the issue yourself, choose "'''assign yourself'''" in the "'''Assignee'''" field. Otherwise, its Chair, Co-chair, or rapporteur, responsibility to assign the issue to the relevant individual.
#*'''Labels:''' Use labels to help organize and filter issues. When creating an issue, make sure to:
#**Add the appropriate ISG NFV Working Group (WG) label (e.g., "'''NFV-SOL'''" for a SOL specification issue).
#**Choose a label that describes the issue category: '''Bug''', '''Clarification''', or '''Feature Gap'''.
#*'''Dates and Milestone:''' If you are unsure with the dates and milestone, leave these fields as they are. These fields are supposed to be managed by Chairs, Vice-Chairs, or Rapporteurs, if needed.
#Once all necessary details are added, click "'''Create issue'''" to submit.
[[File:How to add new issue.png|center|796x796px]]
'''In case of confidential issues:'''


NFV-REL003 "E2E reliability models report"
* If this is an ETSI NFV internal issue (e.g. gap tracking by the rapporteur) and this issue is still confidential because it refers to a non-public document, send it via email to "'''NFVsupport@etsi.org'''".
* Note: We should keep our own issues public whenever possible, as this helps reducing duplicate reports.


NFV-REL004 "Active monitoring & failure detection report"
Issue categories:
 
{| class="wikitable"
NFV-SEC002 "Security features in mgmt sofware report"
! Category
 
! Semantic
NFV-SEC004 "LI report"
|- style="vertical-align:top;"
 
| Bug
NFV-SEC005 "Certificate mgmt report"
| Some aspect of the spec cannot be implemented as described.
 
|- style="vertical-align:top;"
NFV-SEC006 "Sec & Regulation report"
| Clarification
 
| Some aspect of the spec is ambiguous or unclear.
NFV-SEC007 "NFV Attestation report"
|- style="vertical-align:top;"
 
| Feature Gap
NFV-SEC008 "Security Monitoring report"
| The specs are missing a feature (e.g. an operation, parameter) without which the described features cannot be implemented.
|}


NFV-SEC009 "UCs for multi-layer host admin"
== Monitoring Relevant Issue(s) ==
By default, the issue reporter (or creator) receives email notifications when someone comments on the issue, updates its status (e.g., closed or reopened), or performs other related actions. However, if you want to manage notifications for the issue(s) you are involved in:


NFV-TST001 "Pre-deployment Validation report"
1. Log in to the [https://forge.etsi.org/rep/nfv/issues ETSI NFV Issue Tracker].


NFV-TST002 "Iop Testing Methodology report"
2. In the Issue repository, click the '''bell icon''' in the issue repository and select "'''Participate'''" to receive updates on issues you are part of.


3. Select "'''On mention'''" option, to get notified only when you are specifically mentioned in a comment.


4. To stop receiving email notifications, select the "'''Disabled'''" option.


[[File:Relevant notification settings.png|762x762px]]


== Monitor All Issues ==
Users can also subscribe to receive email notifications for all activities within the repository.


1. Log in to the [https://forge.etsi.org/rep/nfv/issues ETSI NFV Issue Tracker].


2. In the Issue repository, click the '''bell icon''' in the issue repository and select "'''Watch'''" to get notified for all activity in the Issue repository.


3. To stop receiving email notifications, select the "'''Disabled'''" option.


Approved and PUBLISHED deliverables shall be obtained via the ETSI Standards search page at:http://www.etsi.org/standards-search
[[File:All notification settings.png|762x762px]]

Latest revision as of 13:53, 25 July 2025

Login to the Issue Tracker

Login with EOL: NFV members and participants can login to the ETSI NFV Issue Tracker with their ETSI Online (EOL) account (used to log into the ETSI Portal).

Go to the ETSI NFV Issue Tracker and login.

User with EOL account can view and create issues, but users without EOL account can only view issues.

Issue tracker allows normal users to submit new issues and view public issues, but does not allow to process issues.

Chairs, Vice-Chairs, and Rapporteurs have a "Developer" or "Maintainer" role, which additionally allows viewing private issues and processing issues.

Login bug tracker.png

View Issues

1. Go to the ETSI NFV Issue Tracker and login.

2. To view the list of all issues, click "Issues" under "Pinned" drop down button.

3. To view issues by assignee, author, or label, click the search bar and choose the relevant option.

4. To find issues related to a specific specification, version, or other details, use the search bar to enter your keywords.

Review issues.png


5. To view the details of a specific issue, click title of the issue.

To open existing issue.png

Else how to navigate to the Issues Repository

1. Go to the ETSI Forge NFV Group.

2. Click on the "Issues" repository.

Navigate to issues repo.png

3. View issues as mentioned in the Step 2 of the previous section.

Submitting an Issue to the Issue Tracker

For Non-EOL Users

Non-EOL users cannot report issues directly via the ETSI NFV Issue Tracker. However, it is recommended that they submit their issues by sending an email to "NFVsupport@etsi.org".

For EOL Users

Go to the ETSI NFV Issue Tracker and login.

Before creating a new issue, please check that:

a) The issue still exists in the latest version of the respective GS document, and

b) The issue has not yet been reported by someone else. If the latter is the case, please add a comment to the existing issue rather than reporting a new one.

To create a new issue:

  1. Go to ETSI NFV Issue Tracker, click "Issues" under "Pinned" drop down button, and click "New issue".
    New issue.png
  2. The Type is default set to "Issue" don't change it.
  3. Issue Title: In the issue Title input field, provide a clear and concise one-line summary of the issue.
    • Following the format: [Version] <NFV-Specification> <Issue_title>
    • For example: [v5.1.1] NFV-SOL003 Missing attribute in Query Compute Resources
  4. Issue description: In the description input box, clearly explain the issue. Describe what the issue is, what the expected outcome should be, and include any additional details or links to relevant documents if available.
  5. Setting additional fields:
    • Assignee: If you are going to resolve the issue yourself, choose "assign yourself" in the "Assignee" field. Otherwise, its Chair, Co-chair, or rapporteur, responsibility to assign the issue to the relevant individual.
    • Labels: Use labels to help organize and filter issues. When creating an issue, make sure to:
      • Add the appropriate ISG NFV Working Group (WG) label (e.g., "NFV-SOL" for a SOL specification issue).
      • Choose a label that describes the issue category: Bug, Clarification, or Feature Gap.
    • Dates and Milestone: If you are unsure with the dates and milestone, leave these fields as they are. These fields are supposed to be managed by Chairs, Vice-Chairs, or Rapporteurs, if needed.
  6. Once all necessary details are added, click "Create issue" to submit.
How to add new issue.png

In case of confidential issues:

  • If this is an ETSI NFV internal issue (e.g. gap tracking by the rapporteur) and this issue is still confidential because it refers to a non-public document, send it via email to "NFVsupport@etsi.org".
  • Note: We should keep our own issues public whenever possible, as this helps reducing duplicate reports.

Issue categories:

Category Semantic
Bug Some aspect of the spec cannot be implemented as described.
Clarification Some aspect of the spec is ambiguous or unclear.
Feature Gap The specs are missing a feature (e.g. an operation, parameter) without which the described features cannot be implemented.

Monitoring Relevant Issue(s)

By default, the issue reporter (or creator) receives email notifications when someone comments on the issue, updates its status (e.g., closed or reopened), or performs other related actions. However, if you want to manage notifications for the issue(s) you are involved in:

1. Log in to the ETSI NFV Issue Tracker.

2. In the Issue repository, click the bell icon in the issue repository and select "Participate" to receive updates on issues you are part of.

3. Select "On mention" option, to get notified only when you are specifically mentioned in a comment.

4. To stop receiving email notifications, select the "Disabled" option.

Relevant notification settings.png

Monitor All Issues

Users can also subscribe to receive email notifications for all activities within the repository.

1. Log in to the ETSI NFV Issue Tracker.

2. In the Issue repository, click the bell icon in the issue repository and select "Watch" to get notified for all activity in the Issue repository.

3. To stop receiving email notifications, select the "Disabled" option.

All notification settings.png