[opnfv-tech-discuss] [Functest][Multisite] check_os.sh failed during openstack endpoint list

2016-08-18 Thread joehuang 
Hello, Functest and Multisite:



The CI job failed again and again at "OpenStack endpoint list" in check_os.sh. 
But if log into the Functest container, and "source 
~/functest/conf/openstack.creds" , then manually execute "OpenStack endpoint 
list", it succeeds.



Please help to find out why the check_os.sh failed.







https://build.opnfv.org/ci/job/functest-fuel-virtual-suite-master/64/console



https://build.opnfv.org/ci/job/functest-fuel-virtual-suite-master/63/console



https://build.opnfv.org/ci/job/functest-fuel-virtual-suite-master/56/console



..



Started by user m00133142
[EnvInject] - Loading node environment variables.
Building remotely on 
intel-virtual6 
(opnfv-sysinfo multisite ci-resource) in workspace 
/home/jenkins/opnfv/slave_root/workspace/functest-fuel-virtual-suite-master
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository https://gerrit.opnfv.org/gerrit/functest
 > git init 
 > /home/jenkins/opnfv/slave_root/workspace/functest-fuel-virtual-suite-master 
 > # timeout=10
...

2016-08-19 05:11:47,270 - prepare_env - INFO - # Preparing Functest 
environment #

2016-08-19 05:11:47,271 - prepare_env - INFO - 
==
2016-08-19 05:11:47,271 - prepare_env - INFO - Checking environment variables...
2016-08-19 05:11:47,271 - prepare_env - INFO - INSTALLER_TYPE=fuel
2016-08-19 05:11:47,271 - prepare_env - INFO - INSTALLER_IP=10.20.0.2
2016-08-19 05:11:47,271 - prepare_env - INFO - 
DEPLOY_SCENARIO=os-odl_l2-multisite-ha
2016-08-19 05:11:47,271 - prepare_env - INFO - CI_DEBUG=false
2016-08-19 05:11:47,271 - prepare_env - INFO - NODE_NAME=intel-virtual6
2016-08-19 05:11:47,271 - prepare_env - INFO - 
BUILD_TAG=jenkins-functest-fuel-virtual-suite-master-64
2016-08-19 05:11:47,271 - prepare_env - INFO - 
==
2016-08-19 05:11:47,271 - prepare_env - INFO - Creating needed directories...
2016-08-19 05:11:47,272 - prepare_env - INFO - 
==
2016-08-19 05:11:47,272 - prepare_env - INFO - Fetching RC file...
2016-08-19 05:11:47,272 - prepare_env - INFO - RC file not provided. Fetching 
it from the installer...
fetch_os_creds.info: Verifying connectivity to 10.20.0.2...
fetch_os_creds.info: 10.20.0.2 is reachable!
fetch_os_creds.info: Fetching rc file from controller 10.20.0.3...
Warning: Permanently added '10.20.0.2' (ECDSA) to the list of known hosts.
Warning: Permanently added '10.20.0.3' (ECDSA) to the list of known hosts.
fetch_os_creds.info: Exchanging keystone public IP in rc file to 
http://172.16.0.3:5000/v2.0
2016-08-19 05:11:53,358 - prepare_env - INFO - Sourcing the OpenStack RC file...
2016-08-19 05:11:53,371 - prepare_env - INFO - 
==
2016-08-19 05:11:53,371 - prepare_env - INFO - Verifying OpenStack services...
2016-08-19 05:11:53,378 - prepare_env - INFO - Checking OpenStack endpoints:
2016-08-19 05:11:53,386 - prepare_env - INFO - >>Verifying connectivity to the 
public endpoint 172.16.0.3:5000...
2016-08-19 05:11:53,393 - prepare_env - INFO -   ...OK
2016-08-19 05:11:54,520 - prepare_env - INFO - >>Verifying connectivity to the 
admin endpoint 192.168.0.2:35357...
2016-08-19 05:11:54,526 - prepare_env - INFO -   ...OK
2016-08-19 05:11:54,526 - prepare_env - INFO - Checking OpenStack basic 
services:
2016-08-19 05:11:54,530 - prepare_env - INFO - >>Checking openstack service...
2016-08-19 05:11:59,269 - prepare_env - ERROR - ERROR: Failed execution 
openstack endpoint list. The openstack does not seem to be working.
Problem while running 'check_os.sh'.
Build step 'Execute shell' marked build as failure
Finished: FAILURE
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] TSC & Colorado release meetings next week

2016-08-18 Thread Raymond Paik 
All,

I have not heard any feedback or concerns regarding the proposed schedule
change next Tuesday.  So we'll go ahead and move both TSC (6am PT) and
release meetings (7am PT) an hour earlier on August 23rd.

I also made a note of this on the TSC page (
https://wiki.opnfv.org/display/meetings/TSC#TSC-August23,2016)

Thanks,

Ray


On Tue, Aug 16, 2016 at 10:19 AM, Raymond Paik 
wrote:

> All,
>
> As discussed during the TSC call earlier, I wanted to propose shifting
> both the TSC & Colorado release meetings an hour earlier next week since we
> have the Q3 Hackfest in Toronto starting on Tuesday.  So the TSC call would
> start at 6am Pacific Time and the Release meeting at 7am Pacific Time.
>
> Can you let me know by EOD Pacific Time on Thursday (18th) if you are
> concerned with moving both meetings an hour earlier?  For people attending
> the Hackfest, the plan is to have both meetings in the Hackfest room...
>
> Thanks,
>
> Ray
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [ovsnfv] How to install OPNFV testbed (virtual deployment) ?

2016-08-18 Thread Lee, Chunghan 
Hi Billy and Tom,

In the previous meeting (7/18), Mark mentioned virtual and bare-metal 
deployments.
I’d like to try to install OPNFV (Brahmaputra or Colorado) using
virtual deployments (VM base) in my local environment (one or two physical 
machines).

In the public links
(https://www.opnfv.org/software/download
http://artifacts.opnfv.org/fuel/brahmaputra/docs/installation-instruction.html),
it provides iso images and bare-metal deployments only.
Is there any image or information for the virtual deployments (Fuel and Apex)?

Regards,
Chunghan Lee

--
Chunghan Lee
Cloud Network Project. Fujitsu Laboratories Ltd.
4-1-1 Kamikodanaka, Nakahara-ku,
Kawasaki-shi, Kanagawa 211-8588, Japan
E-mail： lee.chung...@jp.fujitsu.com
--

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [Bottlenecks] Minutes of Bottlenecks Discussion on August 18, 2016

2016-08-18 Thread Yuyang (Gabriel) 
Hi,

Please find the minutes of Thursday's Bottlenecks meeting below and welcome to 
our next meeting!

Thanks,
Yang

Minutes of Bottlenecks Discussion on August 18, 2016

  *   Date and Time
 *   Thursday at 
0100-0200
 UTC, August 18, 2016
 *   Thursday at 0900-1000 Beijing, August 18, 2016
 *   Wednesday at 1800-1900 PDT, August 17, 2016
  *   Minutes
 *   Yang Yu
  *   Participants (5 peoples):
 *   Yang Yu
 *   Qi Liang
 *   Mingjiang Li
 *   Prakash Ramchandran
 *   1 Web user
Agenda:

 *   Bottlenecks Colorado DiscussYang
*   Colorado Release Report
   *   Colorado Milestones
   *   Release Meeting Report
*   Bottlenecks Colorado Testing Framework (Rubbos example)
 *   Proposals in Bottlenecks (Draft) Yang
*   Goals and Scope (Draft)
*   The Proposals (Draft)
*   Metrics & Tools Discussion
Discussion & Action Item

1.  Bottlenecks Colorado Discuss

  *   Hongbo is on a business trip. So Yang is delegated to organize the 
discussion
  *   Yang mentions that there will be a window period for stable branches and 
documents which lasts one week from August 15-22
 *   PTLs of each projects should determine their Milestone time that 
within this window period.
 *   Bottlenecks also plans to be branched at August 22
 *   MS9:Stable branch created
*   Projects are branched from main
*   Commits are limited to critical issues
*   Commits must be cherry-picked
 *   MS10:Documentation completed
*   Updated
*   Reviewed
*   Verified
*   Committed to repo
  *   Yang reports the discussion from last Release meeting
 *   Minutes: 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-08-16-15.00.html
*   Discussion of Release Meeting
*   release meeting next week during LinuxCon
*   stable branch and release participation
*   Documentation
*   scenario status
 *   Yang ask Prakash about the principle of feature projects C release
*   Prakash explains the discussion in last release meeting that 
feature projects could move features forward to updated environment, and pass 
deployment and test requirements within this week.
  *   Prakash asks the Bottlenecks Colorado Framework
 *   Yang explains that Bottleneck uses puppet to refactor the testing 
framework
*   Jumper server is the CI entrance for the Bottlenecks and will 
download all the codes
*   Environment and resources are configured and provided in the Jumper 
server
*   By taking Rubbos as an example, Yang introduce that the softwares 
that are needed in each nodes are downloaded and configured, and how puppet 
master/slave distributes. The Rubbos controller triggers the testing and the 
results will be sent to DB.

2.  Proposals in Bottlenecks (Draft)

  *   Prakash asks the intention of this proposal
 *   Yang explains the goals and scope
*   Goals of the proposals in Bottlenecks
   *   Enhance interaction with other project
   *   Feedback development suggestions to upstream through OPNFV 
feature projects
   *   Improve the performance of OPNFV reference platform
*   Scope of the proposals in Bottlenecks
   *   OPNFV Testing projects
   *   OPNFV Feature projects
   *   Modeling, Testing and Data analysis
   *   Parameters choosing and Algorithms
  *   Prakash asks about the Modeling
 *   Yang explains that the modeling is the theoretical method to profile 
the system behaviors which could perfectly simulate the real testing results.
  *   Yang briefly introduces the proposal
 *   Yang suggests that Bottlenecks communicates with testing and feature 
projects about the test cases, uses yardstick for testing and collects data 
from DB. Then the results will be analyzed and the bottlenecks will be 
classified into 5 categories. In addition, the bottlenecks analysis results 
will be feedback to each feature projects to output development suggestions to 
upstream projects.
 *   Yang explain that for feature testing, this proposal needs to design 
metrics sets to reflect bottlenecks in the 5 categories
 *   Prakash suggests to work further with Yardstick
*   An action item for Yang to work further with Yardstick and 
determine the detailed plan with Yardstick
  *   Yang introduce the metrics/sets and tools categories that will be needed 
in the proposal
 *   Yang introduces the metrics from Yardstick
*   Prakash asks that the proposal is to load the system or to measure 
the load
   *   Yang explains that the proposal is use Yardstick to load the 
system, then Bottlenecks profiles it and analyzes the results which could be

[opnfv-tech-discuss] Invitation: OPNFV SPC Polestar WG Call (8/25-9/29) @ Weekly from 8am to 9am on Thursday from Thu Aug 25 to Thu Sep 29 (CDT) (m...@linuxfoundation.org)

2016-08-18 Thread myu 
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/Chicago
X-LIC-LOCATION:America/Chicago
BEGIN:DAYLIGHT
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
TZNAME:CDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
TZNAME:CST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Chicago:20160825T08
DTEND;TZID=America/Chicago:20160825T09
RRULE:FREQ=WEEKLY;UNTIL=20160929T13Z;BYDAY=TH
DTSTAMP:20160818T201728Z
ORGANIZER;CN=m...@linuxfoundation.org:mailto:m...@linuxfoundation.org
UID:9bs4mpq30n39jgd0pmg9hm9...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=sandra.l.riv...@intel.com;X-NUM-GUESTS=0:mailto:sandra.l.rivera@int
 el.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=hkirk...@linuxfoundation.org;X-NUM-GUESTS=0:mailto:hkirksey@linuxfo
 undation.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=jonne.soini...@nokia.com;X-NUM-GUESTS=0:mailto:jonne.soininen@nokia
 .com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=prodip@hpe.com;X-NUM-GUESTS=0:mailto:prodip@hpe.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=john.v.he...@intel.com;X-NUM-GUESTS=0:mailto:john.v.he...@intel.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=zhangyujun+...@gmail.com;X-NUM-GUESTS=0:mailto:zhangyujun+zte@gmail
 .com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=bob.monk...@arm.com;X-NUM-GUESTS=0:mailto:bob.monk...@arm.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=ulrich.kle...@huawei.com;X-NUM-GUESTS=0:mailto:ulrich.kleber@huawei
 .com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=margaretchiosi.o...@gmail.com;X-NUM-GUESTS=0:mailto:margaretchiosi.
 o...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=cyo...@clearpathnet.com;X-NUM-GUESTS=0:mailto:cyoung@clearpathnet.c
 om
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=fbroc...@cisco.com;X-NUM-GUESTS=0:mailto:fbroc...@cisco.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=anthony.so...@huawei.com;X-NUM-GUESTS=0:mailto:anthony.soong@huawei
 .com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=tf4...@att.com;X-NUM-GUESTS=0:mailto:tf4...@att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dmcbr...@linuxfoundation.org;X-NUM-GUESTS=0:mailto:dmcbride@linuxfo
 undation.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=m...@linuxfoundation.org;X-NUM-GUESTS=0:mailto:m...@linuxfoundation.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=pyeg...@juniper.net;X-NUM-GUESTS=0:mailto:pyeg...@juniper.net
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=sw3...@att.com;X-NUM-GUESTS=0:mailto:sw3...@att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=christopher.pr...@ericsson.com;X-NUM-GUESTS=0:mailto:christopher.pr
 i...@ericsson.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Raymond Paik;X-NUM-GUESTS=0:mailto:rp...@linuxfoundation.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=bs3...@att.com;X-NUM-GUESTS=0:mailto:bs3...@att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=opnfv-tech-discuss@lists.opnfv.org;X-NUM-GUESTS=0:mailto:opnfv-tech
 -disc...@lists.opnfv.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=paul...@emc.com;X-NUM-GUESTS=0:mailto:paul...@emc.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dick.c...@ztetx.com;X-NUM-GUESTS=0:mailto:dick.c...@ztetx.com
CREATED:20160818T200846Z
DESCRIPTION:OPNFV SPC Polestar Working Group Call every Thursday from Aug 2
 5 to Sep 29\n\nPlease join my meeting from your computer\, tablet or smartp
 hone.\nhttps://global.gotomeeting.com/join/976518869\n\nYou can also dial i
 n using your phone.\nUnited States +1 (571) 317-3117\nUnited States (Toll-f
 ree): 1 866 899 4679\n\nAccess Code: 976-518-869 \n\nMore phone numbers\nAu
 stralia (Toll-free): 1 800 189 049\nAustralia (Long distance): +61 2 8355 1
 039\nAustria (Toll-free): 0 800 202144\nAustria (Long distance): +43 7 2088
  1033\nBelgium (Toll-free): 0 800 81382\nBelgium (Long distance): +32 (0) 2
 8 93 7001\nBrazil (Toll-free): 0 800 047 4902\nBulgaria

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][jira] JIRA process status report

2016-08-18 Thread Beierl, Mark 
Hey, David.

Are you asking that all subtasks also be assigned to a version when you are 
doing your check for Unassigned Issues found?  I only track fix version to the 
story level as subtasks are assigned to the story and it has a fix version.

Regards,
Mark

Mark Beierl | Advisory Solutions Architect
Communication & Media Cloud – CTO Office
EMC Federation
+1 (613) 314-8106
@MarkBeierl

On Aug 18, 2016, at 1:57 PM, David McBride 
> wrote:

Team,

As you know, I've been asking PTLs to update their JIRA projects to improve 
accuracy and to enable use of JIRA as a project management tool.  Note that 
these updates will also improve the accuracy and relevance of JIRA reports 
produced by Bitergia.

Essentially, I'm asking the team to follow four basic principles:

  1.  All JIRA issues must be assigned to a common version string, using the 
"fix version" field.
  2.  Commit messages must include a reference to the issue ID.
  3.  JIRA issue status should be updated whenever the status changes.
  4.  All JIRA issues assigned to a particular release must either be closed, 
or pushed out to a future release (i.e. update "fix version") by the release 
date.

In order to track progress for 1 and 3, I've put together a script that pulls 
data from JIRA.  The first report is attached.  Please locate your project in 
the report and make plans to resolve any issues that are identified.

Notes on the report:

  *   "no versions" - indicates that the admin page contains no version strings 
for selection in the "fix version" field.
 *   To fix this, add the common version strings to the "Versions" section 
on the project admin page.
  *   "Version list NOT correct" - the project contains version strings, but is 
missing one or more of the common version strings.
 *   All projects must use the common set of version strings.
  *   "Unassigned issues found: [list]" - the project has issues where the "fix 
version" field is empty.
 *   Remember, all issues must be assignee to a version, using the "fix 
version" field.
 *   About 85% of the projects have unassigned issues.
 *   There are two solutions to this: (a) educate your project team to set 
the field when they create the ticket; (b) when you conduct a bug scrub, or 
triage, search your JIRA project for issues that are unassigned and update them.

Kudos!  Note that the Domino, Models, and IPv6 projects all have the correct 
version list and no unassigned issues.  An inspiration to us all :)

Final note:  this script is new, so it wouldn't surprise me if there are 
errors.  If you see something that doesn't make sense, please let me know.

David

--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
<08182016_opnfv_jira.txt>___
opnfv-project-leads mailing list
opnfv-project-le...@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-project-leads

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [release][jira] JIRA process status report

2016-08-18 Thread David McBride 
Team,

As you know, I've been asking PTLs to update their JIRA projects to improve
accuracy and to enable use of JIRA as a project management tool.  Note that
these updates will also improve the accuracy and relevance of JIRA reports
produced by Bitergia.

Essentially, I'm asking the team to follow four basic principles:

   1. All JIRA issues must be assigned to a common version string, using
   the "fix version" field.
   2. Commit messages must include a reference to the issue ID.
   3. JIRA issue status should be updated whenever the status changes.
   4. All JIRA issues assigned to a particular release must either be
   closed, or pushed out to a future release (i.e. update "fix version") by
   the release date.

In order to track progress for 1 and 3, I've put together a script that
pulls data from JIRA.  The first report is attached.  Please locate your
project in the report and make plans to resolve any issues that are
identified.

Notes on the report:

   - "no versions" - indicates that the admin page contains no version
   strings for selection in the "fix version" field.
  - To fix this, add the common version strings to the "Versions"
  section on the project admin page.
   - "Version list NOT correct" - the project contains version strings, but
   is missing one or more of the *common* version strings.
  - All projects must use the common set of version strings.
   - "Unassigned issues found: [list]" - the project has issues where the
   "fix version" field is empty.
  - Remember, all issues must be assignee to a version, using the "fix
  version" field.
  - About 85% of the projects have unassigned issues.
  - There are two solutions to this: (a) educate your project team to
  set the field when they create the ticket; (b) when you conduct a bug
  scrub, or triage, search your JIRA project for issues that are unassigned
  and update them.

*Kudos! * Note that the Domino, Models, and IPv6 projects all have the
correct version list and no unassigned issues.  An inspiration to us all :)

Final note:  this script is new, so it wouldn't surprise me if there are
errors.  If you see something that doesn't make sense, please let me know.

David

-- 
*David McBride*
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
APEX
Version list correct
Unassigned issues found:
APEX-237, APEX-228, APEX-227, APEX-23

ARMBAND
Version list correct
Unassigned issues found:
ARMBAND-52, ARMBAND-49, ARMBAND-20

FUNCTEST
Version list correct
Unassigned issues found:
FUNCTEST-396, FUNCTEST-372, FUNCTEST-343, FUNCTEST-336, FUNCTEST-335, 
FUNCTEST-334, FUNCTEST-332, FUNCTEST-283, FUNCTEST-237, FUNCTEST-232, 
FUNCTEST-211, FUNCTEST-210, FUNCTEST-209, FUNCTEST-203, FUNCTEST-200, 
FUNCTEST-192, FUNCTEST-187, FUNCTEST-185, FUNCTEST-177, FUNCTEST-176, 
FUNCTEST-175, FUNCTEST-173, FUNCTEST-172, FUNCTEST-169, FUNCTEST-168, 
FUNCTEST-167, FUNCTEST-166, FUNCTEST-163, FUNCTEST-162, FUNCTEST-161, 
FUNCTEST-160, FUNCTEST-157, FUNCTEST-88, FUNCTEST-87, FUNCTEST-67, FUNCTEST-15

BOTTLENECK
Version list correct
Unassigned issues found:
BOTTLENECK-90, BOTTLENECK-89, BOTTLENECK-88, BOTTLENECK-87, BOTTLENECK-82, 
BOTTLENECK-81, BOTTLENECK-80, BOTTLENECK-79, BOTTLENECK-77, BOTTLENECK-75, 
BOTTLENECK-74, BOTTLENECK-70, BOTTLENECK-66, BOTTLENECK-65, BOTTLENECK-61, 
BOTTLENECK-59, BOTTLENECK-43, BOTTLENECK-34, BOTTLENECK-22, BOTTLENECK-20, 
BOTTLENECK-18, BOTTLENECK-14, BOTTLENECK-13, BOTTLENECK-12, BOTTLENECK-11, 
BOTTLENECK-9

COMPASS
Version list correct
Unassigned issues found:
COMPASS-457, COMPASS-445, COMPASS-443, COMPASS-435, COMPASS-434, COMPASS-388, 
COMPASS-350, COMPASS-244, COMPASS-48, COMPASS-37, COMPASS-27, COMPASS-26, 
COMPASS-25, COMPASS-2

OCTO
Version list correct
Unassigned issues found:
OCTO-141

CPERF
Version list correct
Unassigned issues found:
CPERF-4, CPERF-3, CPERF-2, CPERF-1

DAISY
no versions

PREDICTION
Version list correct
Unassigned issues found:
PREDICTION-33

DPACC
Version list correct
Unassigned issues found:
DPACC-15, DPACC-14, DPACC-13, DPACC-12, DPACC-11, DPACC-10, DPACC-9, DPACC-8, 
DPACC-6, DPACC-5, DPACC-4, DPACC-3, DPACC-2

PARSER
Version list correct
Unassigned issues found:
PARSER-59

ENFV
no versions

ESCALATOR
no versions

FDS
Version list correct
Unassigned issues found:
FDS-14, FDS-13, FDS-12, FDS-11, FDS-10, FDS-9, FDS-8, FDS-7, FDS-6, FDS-5, 
FDS-4, FDS-3, FDS-2, FDS-1

DOCTOR
Version list correct
Unassigned issues found:
DOCTOR-68, DOCTOR-54, DOCTOR-52, DOCTOR-28, DOCTOR-26, DOCTOR-16

FUEL
Version list correct
Unassigned issues found:
FUEL-164, FUEL-160, FUEL-117, FUEL-89, FUEL-88

GENESIS
Version list correct
Unassigned issues found:
GENESIS-90, GENESIS-89, GENESIS-88, GENESIS-87, GENESIS-86, GENESIS-85, 
GENESIS-84, GENESIS-82, GENESIS-81, GENESIS-80, GENESIS-77, GENESIS-75, 
GENESIS-69, GENESIS-63, GENESIS-57, GENESIS-56, GENESIS-55, GENESIS-54, 
GENESIS-53, GENESIS-50,

Re: [opnfv-tech-discuss] [VSPERF] How to config the VSPerf and Moongen correctly.

2016-08-18 Thread Bill Michalowski 
Hi David:

How are you invoking vsperf for the tput test?  Would you try the following:

./vsperf --trafficgen Moongen phy2phy_tput --test-params 
'rfc2544_trials=1;duration=30;lossrate=90'

- Bill

- Original Message -From: David XF1 Cui To: Bill 
Michalowski Cc: opnfv-tech-discuss@lists.opnfv.orgSent: 
Thu, 18 Aug 2016 01:21:44 -0400 (EDT)Subject: RE: [opnfv-tech-discuss] [VSPERF] 
How to config the VSPerf and Moongen correctly.


Hi Bill,
 
Yes. I can get MoonGen  running indpendently on a PC without VSPERF enviroment 
referred to the MoonGenSetUp.html. Currently, I set the VSWITCH config to 
'OvsVanilla' to debug the OVS which not using the DPDK.  Could I need to config 
the MoonGen on the another PC. I use the defual config file: opnfv-vsperf.lua?
 
 
Thanks & BRs
David
 
From: Bill Michalowski [mailto:bmich...@redhat.com]

Sent: Wednesday, August 17, 2016 10:33 PMTo: David XF1 CuiCc: 
opnfv-tech-discuss@lists.opnfv.orgSubject: Re: [opnfv-tech-discuss] [VSPERF] 
How to config the VSPerf and Moongen correctly.
 

Hi David:


Let's break this down and see if you can get MoonGen running outside of the 
VSPERF infrastructure first.  Once that's done, we will try to get the 
phy2phy_tput tests running.


Please refer to the instructions within the MoonGenSetUp.html file on the 
MoonGen side and see if you have any success passing data.


Regards,


Bill


- Original Message -

From: David XF1 Cui 

To: opnfv-tech-discuss@lists.opnfv.org

Sent: Mon, 15 Aug 2016 18:39:52 -0400 (EDT)

Subject: Re: [opnfv-tech-discuss] [VSPERF] How to config the VSPerf and Moongen 
correctly.


Sorry, I forget the log files. Attach again.
 


From: David XF1 Cui
Sent: Tuesday, August 16, 2016 6:34 AMTo: 
'opnfv-tech-discuss@lists.opnfv.org'Subject: [VSPERF] How to config the VSPerf 
and Moongen correctly.


 
Hi guys,
 
Sorry for troubling you. I try to setup a test environment use VSPerf and 
MoonGen to benchmark the performance of OVS.  I use two PCs to setup the 
environment, one for VSPerf and another for MoonGen. I run the phy2phy_tput

test on the VSPerf side.  But I can not get the correct test result. I attached 
the configurations and logs here. Could you help me to check if I config the 
VSperf and Moongen correctly?
 
Thanks & BRs
David
 
some logs as below

[INFO ]  2016-08-16 06:20:14,908 : (moongen) - In moongen 
send_rfc2544_throughput method
[INFO ]  2016-08-16 06:20:14,908 : (moongen) - In Moongen traffic_defaults 
method
[DEBUG]  2016-08-16 06:20:14,908 : (root) - traffic['frame_rate'] = 100
[DEBUG]  2016-08-16 06:20:14,908 : (root) - traffic['multistream'] = 0
[DEBUG]  2016-08-16 06:20:14,908 : (root) - traffic['stream_type'] = L2
[DEBUG]  2016-08-16 06:20:14,908 : (root) - traffic['l2']['srcmac'] = 
6c:0b:84:45:4b:53
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['l2']['dstmac'] = 
6c:0b:84:dd:ed:07
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['l3']['proto'] = udp
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['l3']['srcip'] = 
10.100.206.96
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['l3']['dstip'] = 
10.100.203.102
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['l4']['srcport'] = 3000
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['l4']['dstport'] = 3001
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['vlan']['enabled'] = False
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['vlan']['id'] = 0
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['vlan']['priority'] = 0
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['vlan']['cfi'] = 0
[DEBUG]  2016-08-16 06:20:14,909 : (root) - 64
[DEBUG]  2016-08-16 06:20:14,909 : (root) - startRate = 14.880952380952381
opnfv-vsperf-cfg.lua
 
100%  297 0.3KB/s   00:00   
2016-08-15T22:20:15Z|00056|poll_loop|INFO|wakeup due to [POLLIN] on fd 37 (FIFO 
pipe:[1366939]) at lib/netdev.c:1918 (78% CPU usage)
moongen_log.txt 
 
100%0 0.0KB/s   00:00   
[ERROR]  2016-08-16 06:20:15,296 : (root) - There was a problem parsing Moongen 
REPORT section of Moongen log file
[ERROR]  2016-08-16 06:20:15,296 : (root) - There was a problem parsing Moongen 
PARAMETERS section of Moongen log file

2016-08-15T22:20:15Z|00061|poll_loop|INFO|wakeup due to [POLLIN] on fd 37 (FIFO 
pipe:[1366939]) at lib/netdev.c:1918 (78% CPU usage)
2016-08-15T22:20:16Z|00062|poll_loop|INFO|wakeup due to [POLLIN] on fd 37 (FIFO 
pipe:[1366939]) at lib/netdev.c:1918 (78% CPU usage)
2016-08-15T22:20:16Z|00063|poll_loop|INFO|wakeup due to [POLLIN] on fd 37 (FIFO 
pipe:[1366939]) at lib/netdev.c:1918 (78% CPU usage)

[opnfv-tech-discuss] Updated Invitation: [SPC Polestar] OPNFV SPC Polestar WG Call @ Weekly at 8am on Thursday from Thu Aug 25 to Thu Sep 29 (CDT) (m...@linuxfoundation.org)

2016-08-18 Thread myu 
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/Chicago
X-LIC-LOCATION:America/Chicago
BEGIN:DAYLIGHT
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
TZNAME:CDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
TZNAME:CST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Chicago:20160825T08
DTEND;TZID=America/Chicago:20160930T09
RRULE:FREQ=WEEKLY;UNTIL=20160929T13Z;BYDAY=TH
DTSTAMP:20160818T161935Z
ORGANIZER;CN=m...@linuxfoundation.org:mailto:m...@linuxfoundation.org
UID:98chtbam8e24pgh3orlhvne...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=sandra.l.riv...@intel.com;X-NUM-GUESTS=0:mailto:sandra.l.rivera@int
 el.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=jonne.soini...@nokia.com;X-NUM-GUESTS=0:mailto:jonne.soininen@nokia
 .com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=prodip@hpe.com;X-NUM-GUESTS=0:mailto:prodip@hpe.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=john.v.he...@intel.com;X-NUM-GUESTS=0:mailto:john.v.he...@intel.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=bob.monk...@arm.com;X-NUM-GUESTS=0:mailto:bob.monk...@arm.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=cyo...@clearpathnet.com;X-NUM-GUESTS=0:mailto:cyoung@clearpathnet.c
 om
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=fbroc...@cisco.com;X-NUM-GUESTS=0:mailto:fbroc...@cisco.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=anthony.so...@huawei.com;X-NUM-GUESTS=0:mailto:anthony.soong@huawei
 .com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=tf4...@att.com;X-NUM-GUESTS=0:mailto:tf4...@att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=m...@linuxfoundation.org;X-NUM-GUESTS=0:mailto:m...@linuxfoundation.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=pyeg...@juniper.net;X-NUM-GUESTS=0:mailto:pyeg...@juniper.net
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=christopher.pr...@ericsson.com;X-NUM-GUESTS=0:mailto:christopher.pr
 i...@ericsson.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Raymond Paik;X-NUM-GUESTS=0:mailto:rp...@linuxfoundation.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=mc3...@att.com;X-NUM-GUESTS=0:mailto:mc3...@att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=paul...@emc.com;X-NUM-GUESTS=0:mailto:paul...@emc.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dick.c...@ztetx.com;X-NUM-GUESTS=0:mailto:dick.c...@ztetx.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=opnfv-tech-discuss@lists.opnfv.org;X-NUM-GUESTS=0:mailto:opnfv-tech
 -disc...@lists.opnfv.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=ulrich.kle...@huawei.com;X-NUM-GUESTS=0:mailto:ulrich.kleber@huawei
 .com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=margaretchiosi.o...@gmail.com;X-NUM-GUESTS=0:mailto:margaretchiosi.
 o...@gmail.com
CREATED:20160729T153946Z
DESCRIPTION:OPNFV SPC Polestar Working Group Call Bi-weekly\n\nPlease join 
 my meeting from your computer\, tablet or smartphone.\nhttps://global.gotom
 eeting.com/join/976518869\n\n\nYou can also dial in using your phone.\nUnit
 ed States +1 (571) 317-3117\nUnited States (Toll-free): 1 866 899 4679\n\nA
 ccess Code: 976-518-869 \n\nMore phone numbers\nAustralia (Toll-free): 1 80
 0 189 049\nAustralia (Long distance): +61 2 8355 1039\nAustria (Toll-free):
  0 800 202144\nAustria (Long distance): +43 7 2088 1033\nBelgium (Toll-free
 ): 0 800 81382\nBelgium (Long distance): +32 (0) 28 93 7001\nBrazil (Toll-f
 ree): 0 800 047 4902\nBulgaria (Toll-free): 00800 120 4420\nCanada (Toll-fr
 ee): 1 888 299 1889\nCanada (Long distance): +1 (647) 497-9379\nChina (Toll
 -free): 4008 866143\nColombia (Toll-free): 01 800 012 9056\nCzech Republic 
 (Toll-free): 800 500443\nDenmark (Toll-free): 8025 3112\nDenmark (Long dist
 ance): +45 69 91 89 33\nFinland (Toll-free): 0 800 94503\nFinland (Long dis
 tance): +358 (0) 923 17 0555\nFrance (Toll-free): 0 805 541 043\nFrance (Lo
 ng distance): +33 (0) 170 950 585\nGermany (Toll-free): 0 800 723 5120\nGer
 many (Long distance): +49 (0) 692 5736 7303\nGreece (Toll-free): 00 800 441
 4 3554\nHong Kong (Toll-free): 30713171\nHungary (Toll-free): (06) 80 986

[opnfv-tech-discuss] Pharos Bi-Weekly Meeting

2016-08-18 Thread Morgan, Jack 
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Morgan, Jack":MAILTO:jack.mor...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -discuss (opnfv-tech-discuss@lists.opnfv.org):MAILTO:opnfv-tech-discuss@li
 sts.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ramki_Kris
 h...@dell.com:MAILTO:ramki_krish...@dell.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Marcel Ses
 tak -X (msestak - PANTHEON TECHNOLOGIES at Cisco):MAILTO:mses...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Bob Monkma
 n:MAILTO:bob.monk...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Mario Torr
 ecillas Rodriguez:MAILTO:mario.rodrig...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Christophe
 r Price:MAILTO:christopher.pr...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Sen, Prodi
 p":MAILTO:prodip@hpe.com
DESCRIPTION;LANGUAGE=en-US:Pharos Team..\n\nI’m scheduling a bi-weekly me
 eting to cover Pharos specific topics. Agenda and meeting topics on wiki.\n\nGoToMeeting (Wed
 nesday at 6:00 am PST / 13:00 UTC)\nPlease join my meeting from your compu
 ter\, tablet or smartphone.\nhttps://global.gotomeeting.com/join/349781141
 \n\nYou can also dial in using your phone.\nUnited States (Toll-free): 1 8
 66 899 4679\nUnited States : +1 (312) 757-3117\n\nAccess Code: 349-781-141
 \nMore phone numbers\nAustralia : +61 2 8355 1039\nAustria : +43 7 2088 10
 33\nBelgium : +32 (0) 28 93 7001\nCanada : +1 (647) 497-9379\nDenmark : +4
 5 69 91 89 21\nFinland : +358 (0) 923 17 0555\nFrance : +33 (0) 170 950 58
 5\nGermany : +49 (0) 692 5736 7301\nIreland : +353 (0) 19 030 050\nItaly :
  +39 0 693 38 75 50\nNetherlands : +31 (0) 208 080 208\nNew Zealand : +64 
 9 925 0481\nNorway : +47 21 54 82 21\nSpain : +34 911 82 9890\nSweden : +4
 6 (0) 853 527 817\nSwitzerland : +41 (0) 435 0167 65\nUnited Kingdom : +44
  (0) 330 221 0099\n\n
SUMMARY;LANGUAGE=en-US:Pharos Bi-Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20160831T06
DTEND;TZID=Pacific Standard Time:20160831T07
UID:04008200E00074C5B7101A82E008F0EC14D714F9D101000
 01000E0F204B45F660247842A338E5586EE5B
RECURRENCE-ID;TZID=Pacific Standard Time:20160831T06
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20160818T160445Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:1
LOCATION;LANGUAGE=en-US:GTM and #opnfv-pharos
X-MICROSOFT-CDO-APPT-SEQUENCE:1
X-MICROSOFT-CDO-OWNERAPPTID:529696736
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [genesis] Genesis in Colorado

2016-08-18 Thread David McBride 
Thanks for the update, Frank.

David

On Thu, Aug 18, 2016 at 7:35 AM, Frank Brockners (fbrockne) <
fbroc...@cisco.com> wrote:

> Hi David, team,
>
>
>
> FYI: Given that Genesis did not document any additional requirements for
> deployment tools beyond what had already been defined for Brahmaputra and
> the fact that we still haven’t arrived at defining and adopting common
> configuration files across all installers, the Genesis project decided to
> not participate in the upcoming Colorado release. I’ve updated the Colorado
> project release page accordingly.
>
>
>
> Regards,
>
> Frank
>
>
>
>
>



-- 
*David McBride*
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Pharos Bi-Weekly Meeting

2016-08-18 Thread Morgan, Jack 
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Morgan, Jack":MAILTO:jack.mor...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -discuss (opnfv-tech-discuss@lists.opnfv.org):MAILTO:opnfv-tech-discuss@li
 sts.opnfv.org
DESCRIPTION;LANGUAGE=en-US:Pharos Team..\n\nI’m scheduling a bi-weekly me
 eting to cover Pharos specific topics. Agenda and meeting topics on wiki.\n\nGoToMeeting (Wed
 nesday at 6:00 am PST / 14:00 UTC)\nPlease join my meeting from your compu
 ter\, tablet or smartphone.\nhttps://global.gotomeeting.com/join/349781141
 \n\nYou can also dial in using your phone.\nUnited States (Toll-free): 1 8
 66 899 4679\nUnited States : +1 (312) 757-3117\n\nAccess Code: 349-781-141
 \nMore phone numbers\nAustralia : +61 2 8355 1039\nAustria : +43 7 2088 10
 33\nBelgium : +32 (0) 28 93 7001\nCanada : +1 (647) 497-9379\nDenmark : +4
 5 69 91 89 21\nFinland : +358 (0) 923 17 0555\nFrance : +33 (0) 170 950 58
 5\nGermany : +49 (0) 692 5736 7301\nIreland : +353 (0) 19 030 050\nItaly :
  +39 0 693 38 75 50\nNetherlands : +31 (0) 208 080 208\nNew Zealand : +64 
 9 925 0481\nNorway : +47 21 54 82 21\nSpain : +34 911 82 9890\nSweden : +4
 6 (0) 853 527 817\nSwitzerland : +41 (0) 435 0167 65\nUnited Kingdom : +44
  (0) 330 221 0099\n\n
RRULE:FREQ=WEEKLY;INTERVAL=2;BYDAY=WE;WKST=SU
SUMMARY;LANGUAGE=en-US:Pharos Bi-Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20160831T06
DTEND;TZID=Pacific Standard Time:20160831T07
UID:04008200E00074C5B7101A82E008F0EC14D714F9D101000
 01000E0F204B45F660247842A338E5586EE5B
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20160818T145614Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:GTM and #opnfv-pharos
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:529696736
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [Polestar]Agenda for today's meeting at 15UTC today

2016-08-18 Thread Margaret Chiosi 
Folks:
wiki - https://wiki.opnfv.org/display/polestar
IRC - #opnfv-polestar
Agenda:

   - Meeting Minutes/Agenda  Approval
   - Time Alternatives and do we want to use 8/25 SPC timeslot but use
   Polestar GTM
   - Discussion on Pain Point clarification by Bryan Sullivan or Steven
   Wright
   - Review Margaret's mapping of OPNFV WG to SPC Initiatives and mapping
   of EUG Pain Points to SPC initiatives
   - Discussion on picking 1-2 top Priorities to work through
   - AOB
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Promise] Agenda for today's meeting at 4pm UTC

2016-08-18 Thread Kunzmann, Gerald 
Sorry, I meant 4pm UTC, 18:00 CET:
http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016=8=18=16=0=0=37=64

Sorry for any confusion caused.

Gerald

From: Kunzmann, Gerald
Sent: Donnerstag, 18. August 2016 12:35
To: 'TECH-DISCUSS OPNFV' ; 'Arturo Martin 
De Nicolas' ; 
'rchund...@clearpathnet.com' ; 
'serge.mann...@sprint.com' ; 'Carella, Giuseppe' 

Cc: Ashiq Khan ; 'Ryota Mibu' ; 
Carlos Goncalves (carlos.goncal...@neclab.eu) 
Subject: [Promise] Agenda for today's meeting

Dear all,

Today's Promise meeting will take place at 5pm UTC.

The tentative agenda is (https://wiki.opnfv.org/display/meetings/Promise) :


1.   Colorado release status (15 min)

-  Status of Promise Colorado work

-  Promise documentation (PROMISE-78)

-  Promise installation (FUEL-52)

-  Stable branch cut



2.   Blazar (20 min)

-  Presentation by HPE on planned steps for Blazar


3.   (tentative) Orchestra project (5 min)

-  Introduction to Orchestra project with focus on relation with 
Promise project


Best regards,
Gerald

===
Dr. Gerald Kunzmann, Manager
DOCOMO Communications Laboratories Europe GmbH
Landsberger Strasse 312, 80687 Munich
Tel: +49-89-56824-239 / Fax: +49-89-56824-300
Web: http://www.docomoeurolabs.de

Geschäftsführer: Atsushi Takeshita, Dr. Thomas Walter, Hisahiro Hamahata, 
Takaaki Sato, Junichi Igarashi
Amtsgericht München, HRB 132976

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Shout out: Julien Zhang

2016-08-18 Thread DENG Hui 
+1

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of
morgan.richo...@orange.com
Sent: Thursday, August 18, 2016 3:47 PM
To: Jack Morgan; opnfv-tech-discuss
Subject: Re: [opnfv-tech-discuss] Shout out: Julien Zhang

+1
Le 18/08/2016 à 00:31, Jack Morgan a écrit :
> OPNFV,
>
> I would like to take a moment to recognize Julien Zhang for his hard
> work and dedication during this Colorado release cycle. I really
> appreciate his input even though I as the Pharos PTL didn't provide much
> direction. Julien worked the JIRA issues in his name and created new
> ones when needed. He tirelessly focused on getting things done this
> cycle and even harassed me several times to approve his Gerrit hanges. I
> hope to be more like him moving forward.
>
> Since Julien is currently a contributor to the Pharos project, I'm going
> to recommend he be a committer via Gerrit. Please consider his
> nomination and add your +1 in Gerrit.
>
>
> Thanks,
>


-- 
Morgan Richomme
Orange/ IMT/ OLN/ CNC/ NCA/ SINA 

Network architect for innovative services
Future of the Network community member
Open source Orange community manager


tel. +33 (0) 296 072 106
mob. +33 (0) 637 753 326
morgan.richo...@orange.com



_

Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu
ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.

This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and
delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss



___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Shout out: Julien Zhang

2016-08-18 Thread morgan.richomme 
+1
Le 18/08/2016 à 00:31, Jack Morgan a écrit :
> OPNFV,
>
> I would like to take a moment to recognize Julien Zhang for his hard
> work and dedication during this Colorado release cycle. I really
> appreciate his input even though I as the Pharos PTL didn't provide much
> direction. Julien worked the JIRA issues in his name and created new
> ones when needed. He tirelessly focused on getting things done this
> cycle and even harassed me several times to approve his Gerrit hanges. I
> hope to be more like him moving forward.
>
> Since Julien is currently a contributor to the Pharos project, I'm going
> to recommend he be a committer via Gerrit. Please consider his
> nomination and add your +1 in Gerrit.
>
>
> Thanks,
>


-- 
Morgan Richomme
Orange/ IMT/ OLN/ CNC/ NCA/ SINA 

Network architect for innovative services
Future of the Network community member
Open source Orange community manager


tel. +33 (0) 296 072 106
mob. +33 (0) 637 753 326
morgan.richo...@orange.com


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [daisy4nfv] Agenda for IRC meeting Aug. 19 2016

2016-08-18 Thread hu . zhijiang 
1) Roll Call
2) OPNFV CI Evolution Study Progress
3) Bare Metal Deployment(PXE/IPMI) Status Update
4) Daisy Bare Metal Related DB Deployment Status Update
5) Bifrost/Ironic Integration


B.R.,
Zhijiang

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Technical Community Discussion Canceled Tomorrow (8/18)

2016-08-18 Thread HU, BIN 
Hello community,



Sorry for the late notice.



There is no new project proposal in the backlog. And there is not urgent issue 
to discuss either.



So I propose to cancel our technical discussion tomorrow (8/18) so that 
everyone can focus on Colorado release, catch stable branch window, and meet 
documentation milestone.



Thank you

Bin

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss