Differences

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

--- get_started:ericsson_hosting:qna [2015/01/14 11:39]
Frank Brockners
+++ get_started:ericsson_hosting:qna [2015/02/28 21:23] (current)
Iben Rodriguez
@@ Line 1: / Line 1: @@
-**Ericsson OPNFV Server hosting Questions and answers:**
+====== Ericsson OPNFV Server hosting Questions and answers ======
-**Q: I cannot access the ssh server provided in the access instructions (jonas.bjurel@ericsson.com)**
+  - Q) Where is the lab located?
+    - The Ericsson Lab is located in the United States.
+  - Q) Are other labs planned for the future?
+    - Yes. As the community grows another lab is planned. See [[http://youtu.be/MCLj5SbZFeA?t=21m|this video]] and [[https://wiki.opnfv.org/_media/wiki/opnfv_test_performance_team_meeting_20141106.pdf|preso]] from Ericsson shown at the OpenStack Summit in Paris, November 2014.
-Details:
+====== Miscellaneous Information to sort out ======
-I have logged in to my VPN account, but I can't establish an ssh session with the ssh server.
-**A: (jonas.bjurel@ericsson.com)**
-The VPN JAVA client is a port forwarder, you need to establish a ssh session towards local host using port 9022 - ''ssh -p 9022 myuser@uri''
+The basic Gerrit-Jenkins stuff set up in Feb 2015 to run some things (bgs fuel build) on a VM until we get the hw.
-**Q:** Navigating to the "https:<URI provided with your access grant>" does not start host-checker properly or fails to bring up JSAM. \\
+It is agreed to use Jenkins Job Builder to make things more visible, easily maintainable, and everyone can contribute to CI and so on.
-**A:** Try a different browser. Chrome 39.0.2171.95 is known to work, Firefox 31.0 has shown issues.
+Jobs will be treated the same as we now handle the source code; committed, tested, reviewed and deployed.
+Zuul is something we should look into. We should first focus on getting basic CI up and running for R1 and then fine tune what we have and perhaps introduce Zuul.
+When it comes to what to run;
+We discussed and agreed that the CI comes up with guidelines for the community and enable some standard/basic checks for all the projects right now.
+So we will have a basic commit message check for all projects in short term, triggered by Gerrit events.
+We will add more to shorter loops while we move on based on what projects require and perhaps what upstream projects do. (if we use upstream projects for OPNFV, why not do CI in similar way.)
+Longer loops can either be executed periodically or manually.
+But we should strive for "the CI" and evolve it while we move forward; do the things when things happen in order to give feedback as early (and fast) as possible. (this naturally depends on what resources we have.)

Wiki

User Tools

Site Tools

Differences

Page Tools