developer:intern-projects-page
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
developer:intern-projects-page [2016/03/15 22:51] Trevor Cooper |
developer:intern-projects-page [2016/03/24 03:19] (current) hongbo tian [Project 3] |
||
|---|---|---|---|
| Line 20: | Line 20: | ||
| * Potential secondary mentor: Kontron | * Potential secondary mentor: Kontron | ||
| - | === Project 2 === | + | ==== Project 2 ==== |
| * Title: To contribute to the JOID project | * Title: To contribute to the JOID project | ||
| Line 39: | Line 39: | ||
| * Secondary mentor: Akash Chandrashekar - from Canonical | * Secondary mentor: Akash Chandrashekar - from Canonical | ||
| - | === Project 3 === | + | ==== Project 3 ==== |
| * Title: To contribute to the Dovetail project | * Title: To contribute to the Dovetail project | ||
| Line 54: | Line 54: | ||
| * Mentor(s) & contact info: | * Mentor(s) & contact info: | ||
| * Ritch Dusome (CEO) / rdusome@cengn.ca / 613-963-1196 | * Ritch Dusome (CEO) / rdusome@cengn.ca / 613-963-1196 | ||
| + | * Hongbo Tian:hongbo.tianhongbo@huawei.com | ||
| * Potential secondary mentor: TBD | * Potential secondary mentor: TBD | ||
| - | === Project 4 === | + | ==== Project 4 ==== |
| **Title**: Develop and test a "Pharos Qualification Tool" | **Title**: Develop and test a "Pharos Qualification Tool" | ||
| - | **Description**: Create a tool for the evaluation of OPNFV Communty labs for Pharos compliance. The test tool is intended to be hosted in a pre-packaged container or equivalent (as our test project work) that will perform the following tasks: | + | **Description**: Create a tool for the evaluation of OPNFV Community labs for Pharos compliance. The test tool is intended to be hosted in a pre-packaged container or equivalent (as our test project work) that will perform the following tasks: |
| 1. Establish connectivity to the Jenkins slave to execute the job | 1. Establish connectivity to the Jenkins slave to execute the job | ||
| + | 2. Establish Jump Host connectivity and ability to retreive the test suite and inventory file/s | ||
| + | 3. The test suite wil: | ||
| + | i) Pull the inventory and configuration files for the pod | ||
| + | ii) Use the above files to check for host availbitity, nic configuration, and pull the full IPMI query for uploading to the central DB server (LF hosted) | ||
| + | iii) Using a cirros image or equivalent PXE boot the servers | ||
| + | iv) SSH to each server an have each node check for internet connectivity | ||
| + | 4. If the above tests pass, return a positive result. If the tests fail return details of where the test failed. | ||
| + | 5. All activities and configurations performed by the test should be reset once the test is complete | ||
| + | i) Reboot each node | ||
| + | iv) uninstall the container | ||
| + | v) Log completion status | ||
| - | 2. Establish Jump Host connectivity and ability to retreive the test suite and inventory file/s | + | **Note that the POD being tested will only be connected to CI for duration of the test and then removed. Only once it is CI compliant will it be allowed to be connected to production (platform) CI permanently.** |
| - | 3. The test suite wil: | + | **Success metrics**: |
| + | - There is a test procedure established that is able to be run against pharos labs by Jenkins | ||
| + | - The test should: | ||
| + | - Return all information retreived from the lab to the Pharos server | ||
| + | - Return a positive or negative result to Jenkins based on the execution of the tests | ||
| + | - Return the POD to it's original state once complete. | ||
| - | i) Pull the inventory and configuration files for the pod | + | **Additional Information**: Pharos - https://wiki.opnfv.org/pharos, http://artifacts.opnfv.org/pharos/docs/index.html |
| - | ii) Use the above files to check for host availbitity, nic configuration, and pull the full IPMI query for uploading to the central DB server (LF hosted) | + | **Desirable Skills**: Linux, Networking, Scripting (ideally also virtualization) |
| - | iii) Using a cirros image or equivalent PXE boot the servers | + | **Expected Outcome**: A tool that is used by the OPNFV community for verifying compliance of Pharos spec. |
| - | iv) SSH to each server an have each node check for internet connectivity | + | **Difficultly**: Low/__Medium__/High |
| - | 4. If the above tests pass, return a positive result. If the tests fail return details of where the test failed. | + | **Desired project timeline/completion date**: needed for Release C deploy/test (start April – end June 2016) |
| - | 5. All activities and configurations performed by the test should be reset once the test is complete | + | **Mentor(s) & contact info**: |
| - | + | * Trevor Cooper (Pharos PTL) / trevor.cooper@intel.com | |
| - | i) Reboot each node | + | * Lincoln Lavoie (UNH) lylavoie@iol.unh.edu |
| - | + | ||
| - | iv) uninstall the container | + | |
| - | + | ||
| - | v) Log completions status | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | Success metrics: | + | |
| - | + | ||
| - | - There is a test procedure established that is able to be run against pharos labs by Jenkins | + | |
| - | + | ||
| - | - The test should: | + | |
| - | + | ||
| - | - Return all information retreived from the lab to the Pharos server | + | |
| - | + | ||
| - | - Return a positive or negative result to Jenkins based on the execution of the tests | + | |
| - | + | ||
| - | - Return the POD to it's original state once complete. | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | * Additional Information:Pharos - https://wiki.opnfv.org/pharos | + | |
| - | * Desirable Skills: Linux, Networking, and SDN | + | |
| - | * Expected Outcome: A production Pharos environment for CENGN, contribution to the project (Documentation, testing), and enhanced skills for the students | + | |
| - | * Difficultly: Low/Medium/__High__ | + | |
| - | * Desired project timeline/completion date: 3 month project, to be completed in May 2016 (desirable project timeline: February – April 2016) | + | |
| - | * Mentor(s) & contact info: | + | |
| - | * Ritch Dusome (CEO) / rdusome@cengn.ca / 613-963-1196 | + | |
| - | * Potential secondary mentor: Kontron | + | |
developer/intern-projects-page.1458082261.txt.gz · Last modified: 2016/03/15 22:51 by Trevor Cooper
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
