User Tools

Site Tools


developer:getting_started

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
developer:getting_started [2015/03/16 15:32]
Aric Gardner
developer:getting_started [2015/11/27 15:39] (current)
Mark D. Gray [Mailing List]
Line 4: Line 4:
  
 For access to OPNFV'​s infrastructure,​ you will need a [[https://​identity.linuxfoundation.org/​user/​|LinuxFoundation account]]. ​ (Please use your company email address for the Linux Foundation account and don't have spaces or special characters in your username) ​ For access to OPNFV'​s infrastructure,​ you will need a [[https://​identity.linuxfoundation.org/​user/​|LinuxFoundation account]]. ​ (Please use your company email address for the Linux Foundation account and don't have spaces or special characters in your username) ​
 +
 +[[https://​www.youtube.com/​watch?​v=TsM4LV6cDr4|Tutorial video for Linux Foundation ID creation]]
  
 === Participating in a project === === Participating in a project ===
  
-To participate,​ via contribution,​ in any [[/​project_proposals|project]] in OPNFV, you will need to contact the project manager for the project, listed in the "Key Project Facts" section of the project page requesting to be added as a contributor of the project. ​ Send a mail to the project manager copying the helpdesk opnfv-helpdesk@rt.linuxfoundation.org to have your role in the project set up.  ​+To participate,​ via contribution,​ in any [[/​project_proposals|project]] in OPNFV, you will need to contact the project manager for the project, listed in the "Key Project Facts" section of the project page requesting to be added as a contributor of the project. ​ Send a mail to the project manager copying the helpdesk opnfv-helpdesk@rt.linuxfoundation.org to have your role in the project set up.  If you are not from an OPNFV member company, you will have to agree to be subject to and bound by the OPNFV IP Policy prior to your project contribution.  ​
  
 Once the rights have been set-up you are ready to add your contributions to the project. Once the rights have been set-up you are ready to add your contributions to the project.
Line 14: Line 16:
 === Common Tools === === Common Tools ===
 There are a number of tools used to communicate amongst OPNFV project teams. While many of these are listed on our [[https://​www.opnfv.org/​developers/​tools|www site]] that list is not 100% complete so we will replicate and update the list here.  There are a number of tools used to communicate amongst OPNFV project teams. While many of these are listed on our [[https://​www.opnfv.org/​developers/​tools|www site]] that list is not 100% complete so we will replicate and update the list here. 
- 
 ==== Mailing List ==== ==== Mailing List ====
 The main mailing list is called **Technical Discuss**. The main mailing list is called **Technical Discuss**.
Line 32: Line 33:
     * vnfgraph: Discussion channel for the OpenStack Based VNF Forwarding Graph (vnf_forwarding_graph) project ​     * vnfgraph: Discussion channel for the OpenStack Based VNF Forwarding Graph (vnf_forwarding_graph) project ​
     * octopus: Discussion channel for the Continuous Integration (Octopus) project ​     * octopus: Discussion channel for the Continuous Integration (Octopus) project ​
 +    * joid: Discussion channel for the Juju OPNFV Infrastructure Deployer (JOID) project
     * ipv6: Discussion channel for the IPv6-enabled OPNFV (ipv6) project ​     * ipv6: Discussion channel for the IPv6-enabled OPNFV (ipv6) project ​
     * pharos: Discussion channel for the Testbed infrastructure (Pharos) project ​     * pharos: Discussion channel for the Testbed infrastructure (Pharos) project ​
     * functest: Discussion channel for the Base system functionality testing (functest) project ​     * functest: Discussion channel for the Base system functionality testing (functest) project ​
     * parser: Discussion channel for the Deployment Template Translation (Parser) project ​     * parser: Discussion channel for the Deployment Template Translation (Parser) project ​
 +    * oscar: Discussion channel for the OSCAR (OPNFV System Config & Reporting) project ​
     * announce: Discussion channel for general announcements     * announce: Discussion channel for general announcements
     * opnfv-sec: Discussion channel for the OPNFV Security group     * opnfv-sec: Discussion channel for the OPNFV Security group
     * infra: Discussion channel for the OPNFV hardware infrastructure     * infra: Discussion channel for the OPNFV hardware infrastructure
     * release: Discussion channel for OPNFV release discussions     * release: Discussion channel for OPNFV release discussions
 +    * SFC: Discussion channel for OPNFV Service Function Chaining
 +    * yardstick: Discussion channel for OPNFV Yardstick
 +    * onosfw: Discussion channel for ONOS Framework project
 +    * ovsnfv: Discussion channel for the Open vSwitch for NFV project
     * (You can select topics you want to subscribe to in the configuration page at [[https://​lists.opnfv.org/​mailman/​options/​opnfv-tech-discuss]])     * (You can select topics you want to subscribe to in the configuration page at [[https://​lists.opnfv.org/​mailman/​options/​opnfv-tech-discuss]])
 +
 +Please subscribe to at least [yourproject] and [announce] Your sysadmin will use [announce] for any downtimes that may be needed. (I'll post downtime requests to infra as well)
 ==== IRC ==== ==== IRC ====
 There are a number of IRC channels used for various OPNFV purposes. We will list some here. If this list gets too long we should make a new page: There are a number of IRC channels used for various OPNFV purposes. We will list some here. If this list gets too long we should make a new page:
Line 50: Line 59:
   * #​opnfv-octopus <-- CI team   * #​opnfv-octopus <-- CI team
   * #​opnfv-testperf <-- performance testing team   * #​opnfv-testperf <-- performance testing team
-  *  ​+  * #​opnfv-yardstick <-- used by Yardstick project for day-to-day communication¬†
 +  * #opnfv-sfc <-- used by the Service Function Chaining project for day-to-day communication and weekly meetings¬†
 +  * 
   * please add the rest here... we need help to fill in this list.   * please add the rest here... we need help to fill in this list.
 +
 +=== ASK.OPFNV.ORG ===
 +
 +Another place for help in getting setup, technical questions and other resources is to post a question in the [[http://​ask.opnfv.org|Ask OPNFV Site]] forum.
  
 ==== Git ==== ==== Git ====
Line 86: Line 101:
 The name of the topic branch should be something related to what's being changed, since it will show up in Gerrit. The name of the topic branch should be something related to what's being changed, since it will show up in Gerrit.
  
-When you submit your changes to gerrit, even though they will show the name of the topic branch, they will end up being merged to master. When crafting your commits, you might find [[https://​wiki.openstack.org/​wiki/​GitCommitMessages|Git Commit Good Practice]] useful.+When you submit your changes to gerrit ​with git-review (see: [[:​developer|Welcome to the OPNFV developer resources page.]]), even though they will show the name of the topic branch, they will end up being merged to master. When crafting your commits, you might find [[https://​wiki.openstack.org/​wiki/​GitCommitMessages|Git Commit Good Practice]] useful.
  
 For more information,​ you may find the [[http://​docs.openstack.org/​infra/​manual/​developers.html|OpenStack Developer'​s guide]] and [[http://​www.mediawiki.org/​wiki/​Gerrit/​Tutorial|MediaWiki Gerrit Tutorial]] useful. For more information,​ you may find the [[http://​docs.openstack.org/​infra/​manual/​developers.html|OpenStack Developer'​s guide]] and [[http://​www.mediawiki.org/​wiki/​Gerrit/​Tutorial|MediaWiki Gerrit Tutorial]] useful.
Line 108: Line 123:
  
 Check out the [[:​git|OPNFV Git/​Gerrit]] page for a collection of setup suggestions for the OPNFV Source Code Repositories. Check out the [[:​git|OPNFV Git/​Gerrit]] page for a collection of setup suggestions for the OPNFV Source Code Repositories.
 +
 +A sample procedure for start hacking in Parser Project: [[https://​wiki.opnfv.org/​parser/​howto|Parser HowTo Start]]
developer/getting_started.1426519977.txt.gz · Last modified: 2015/03/16 15:32 by Aric Gardner