Difference between revisions of "NFV SpecFest Wiki"
Line 3: | Line 3: | ||
Welcome to the Wiki page for the NFV SpecFest event. | Welcome to the Wiki page for the NFV SpecFest event. | ||
− | + | Today we offer you the opportunity to participate in the first collaborative OpenAPI specification on the ETSI Forge. | |
We will focus our attention on [https://link_to_be_done.com ETSI NFV GS SOL 002]. Each participant to the SpecFest will create a bit of machine readable description of the textual spec and, as a result, the entire group specification will be described in the OpenAPI description language. | We will focus our attention on [https://link_to_be_done.com ETSI NFV GS SOL 002]. Each participant to the SpecFest will create a bit of machine readable description of the textual spec and, as a result, the entire group specification will be described in the OpenAPI description language. | ||
− | What you need: | + | What you will need: |
* A laptop (any operating system supported) | * A laptop (any operating system supported) | ||
Line 21: | Line 21: | ||
# Log in at [https://forge.etsi.org/index.php/users/login ETSI Forge] inserting your EOL acconts | # Log in at [https://forge.etsi.org/index.php/users/login ETSI Forge] inserting your EOL acconts | ||
# If you do not have an account yet, simply register [https://forge.etsi.org/index.php/register here] | # If you do not have an account yet, simply register [https://forge.etsi.org/index.php/register here] | ||
+ | |||
+ | === Optional: Install an Editor application (VS Code) === | ||
+ | |||
+ | # Navigate to [https://code.visualstudio.com VS Code homepage] and download it for your platform | ||
+ | # Install the [https://marketplace.visualstudio.com/items?itemName=Arjun.swagger-viewer Swagger Viewer Plugin] | ||
+ | |||
+ | === Optional: Set up Git === | ||
+ | |||
+ | To install and configure Git on your machine please refer to [[Get started]]. | ||
== Starter Kit == | == Starter Kit == | ||
Line 53: | Line 62: | ||
=== With offline editor === | === With offline editor === | ||
− | # | + | # Open the template file with VS Code |
− | # | + | # Press F1, then write "Swagger preview". A new tab will open to show the graphical representation of the file. Note that as soon as you change the text, the other tab is automatically updated. |
− | |||
=== With online editor === | === With online editor === | ||
− | # Navigate to SOL002 OAS template. (Google Chrome recommended) | + | # Navigate to SOL002 OAS template. (Google Chrome recommended) |
− | # After editing, click File and then “Download YAML” | + | # After editing, click File and then “Download YAML” |
== Writing the definition == | == Writing the definition == | ||
Line 80: | Line 88: | ||
=== With Git (Advanced) === | === With Git (Advanced) === | ||
− | + | # Upload the contribution via the usual git workflow (please note the unsusual push operation endpoint) | |
− | + | ||
− | # Upload the contribution | + | $ git add |
+ | $ git commit -s -m "your message here" | ||
+ | $ git push origin HEAD:refs/for/master | ||
== Verify == | == Verify == | ||
# Check Jenkins result on Gerrit and on Jenkins Job | # Check Jenkins result on Gerrit and on Jenkins Job | ||
+ | |||
+ | [[File:Gerrit-verify-build-hid.PNG|thumb|center|To verify that the content of the contribution has been validated, look for the text you see in the red boxes in the picture.]] | ||
+ | |||
# If there is no feedback from Jenkins contact CTI | # If there is no feedback from Jenkins contact CTI | ||
# Wait for CTI to merge your contribution | # Wait for CTI to merge your contribution |
Revision as of 16:04, 20 July 2017
Contribute an OAS spec at ETSI Forge!
Welcome to the Wiki page for the NFV SpecFest event.
Today we offer you the opportunity to participate in the first collaborative OpenAPI specification on the ETSI Forge.
We will focus our attention on ETSI NFV GS SOL 002. Each participant to the SpecFest will create a bit of machine readable description of the textual spec and, as a result, the entire group specification will be described in the OpenAPI description language.
What you will need:
- A laptop (any operating system supported)
- A copy (paper or PDF) of NFV SOL 002 specification
- This wiki page.
Let's get started!
Contents
Set up
- Log in at ETSI Forge inserting your EOL acconts
- If you do not have an account yet, simply register here
Optional: Install an Editor application (VS Code)
- Navigate to VS Code homepage and download it for your platform
- Install the Swagger Viewer Plugin
Optional: Set up Git
To install and configure Git on your machine please refer to Get started.
Starter Kit
To help you starting up the activity we provided:
- A dedicated repository at the Forge, with the folder structure, a template of specification and some examples. Click here to visit the repository.
- A live spreadsheet to keep track of "who is doing what"
In the repository interface, click Snapshot in the menu at the top of the page to download an archive with the files. Otherwise click on tree to inspect the content. In the tree you will find the necessary folders and a template file called `sol002-template.yaml`.
The content of the template is as simple as:
swagger: '2.0' info: title: NFV SOL 002 Example - SpecFest! version: v1 host: www.example.com basePath: /ve-vnfm paths: # insert your paths or their json ref here definitions: # Insert your definitions or their json ref here
Open the given spreadsheet and tag one operation with your name
- The operation will then be assigned to you to be edited
Editing
With offline editor
- Open the template file with VS Code
- Press F1, then write "Swagger preview". A new tab will open to show the graphical representation of the file. Note that as soon as you change the text, the other tab is automatically updated.
With online editor
- Navigate to SOL002 OAS template. (Google Chrome recommended)
- After editing, click File and then “Download YAML”
Writing the definition
Edit the OpenApi specification:
- Look up the resource you have been assigned in NFV SOL 002
- Create the definition into the nfv002_main_template.yaml and check correctness with VS Code
- Cut&paste what you created into a proper resource in /paths/index.yaml and create the corresponding file
- E.g. create the Vnf_instance data type into a Vnf_instance.yaml files
- Configure the files so that the CI/CD validates the result
Online via Gerrit (Beginners)
- Upload the contribution via Gerrit ‘Create Change’ button
- Edit the ‘patch set’
- Paste the created files
With Git (Advanced)
- Upload the contribution via the usual git workflow (please note the unsusual push operation endpoint)
$ git add $ git commit -s -m "your message here" $ git push origin HEAD:refs/for/master
Verify
- Check Jenkins result on Gerrit and on Jenkins Job
- If there is no feedback from Jenkins contact CTI
- Wait for CTI to merge your contribution
Iterate!
All accomplished? Then it may be time to select a new part of the specification and create the OpenAPI version again!