date:20160908

Re: [opnfv-tech-discuss] [doctor] For the issue about the notification time is large than 1S

2016-09-08 Thread Juvonen, Tomi (Nokia - FI/Espoo)

Hi,

This is why inspector should be topology aware, meaning here it should already 
know the VMs belonging to the host. Also in real world when event is received  
in most cases that need to be analyzed before get to calling actions to VM or 
host as need to know what is affected by the event.

What comes to failing testing, I think it is normal to temporarily make it pass 
before get the bug fix. Anyhow this is sample inspector, so how complex code we 
want to put into it?

Br,
Tomi

From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn]
Sent: Friday, September 09, 2016 8:00 AM
To: Carlos Goncalves ; souvi...@docomolab-euro.com; 
r-m...@cq.jp.nec.com; Juvonen, Tomi (Nokia - FI/Espoo) 
; kunzm...@docomolab-euro.com
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [doctor] For the issue about the notification 
time is large than 1S


Hi doctors,

For the issue about the notification time is large than 1S.
I check the log and find out that from the inspector received the event to 
nova-api begin to handle the reset_state is taken up most of the time, about 
over 80%. For example, the total notification time is 2.26s, the process of 
inspector takes 1.983s.

In the test inspector script, we find all the VM under all telant, and then set 
all the VM states as error.
As we need to improve the performance,but it can not be handle in a short time.

Shall we extned 1S to 3S or change back to no failed to notification time 
calculation to let functest green?
Meanwhile doing the performance improvement, then change it back?

Any suggestions will be welcome. Thank you~

BR,
dwj



董文娟   Wenjuan Dong

控制器四部 / 无线产品   Controller Dept Ⅳ. / Wireless Product Operation

[icon]

[logo]
上海市浦东新区碧波路889号中兴通讯D3
D3, ZTE, No. 889, Bibo Rd.
T: +86 021 85922M: +86 13661996389
E: dong.wenj...@zte.com.cn
www.ztedevice.com



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

[opnfv-tech-discuss] [dovetail]dovetail weekly meeting 9/9

2016-09-08 Thread Tianhongbo

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Australia Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Tianhongbo:MAILTO:hongbo.tianhon...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='TECH-DISC
 USS OPNFV':MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Christoph
 er Price':MAILTO:christopher.pr...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Dave Near
 y':MAILTO:dne...@redhat.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='marko.a.k
 ui...@nokia.com':MAILTO:marko.a.kui...@nokia.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Rautakump
 u, Mika (Nokia - FI/Espoo)'":MAILTO:mika.rautaku...@nokia.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='sheng-ann
 .y...@ericsson.com':MAILTO:sheng-ann...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='yangjiany
 j...@chinamobile.com':MAILTO:yangjian...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='zhang.jun
 3...@zte.com.cn':MAILTO:zhang.ju...@zte.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'HU, BIN'":
 MAILTO:bh5...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='lma@biigr
 oup.cn':MAILTO:l...@biigroup.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Tetsuya N
 akamura':MAILTO:t.nakam...@cablelabs.com
DESCRIPTION;LANGUAGE=en-US:Hi all:\n\nLet us discuss more about the dovetai
 l.\n\n•   Weekly on Friday at 1400-1500 UTC\n•   Gotomeeting A
 ccess\no   https://global.gotomeeting.com/join/969604901\no   Unit
 ed States +1 (224) 501-3318\no   Access Code: 458-547-813\n•   I
 RC channel\no#opnfv-meeting@ Freenode (Web Chat)\n\n\nFor more detail\, please refer to
  :\nhttps://wiki.opnfv.org/display/dovetail\n\nAgenda:\n1)  Approve th
 e last minutes\n2)  Update for Dovetail tool\n3)  Update for Test 
 plan list\n4)  other issues.\n\nBest Regards\n\nhongbo\n\n\n
SUMMARY;LANGUAGE=en-US:[dovetail]dovetail weekly meeting  9/9
DTSTART;TZID=W. Australia Standard Time:20160909T22
DTEND;TZID=W. Australia Standard Time:20160909T23
UID:04008200E00074C5B7101A82E008504D7CAE7C0AD201000
 0100023F9396F39F3174EB688177533E88226
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20160909T012936Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:-1557555232
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
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] [opnfv-project-leads] [release] D-release schedule

2016-09-08 Thread Yujun Zhang

Is it the same one from release D page?
https://wiki.opnfv.org/display/SWREL/D-Release
I assume I can track the update in the wiki page, can I?
--
Yujun

On Fri, Sep 9, 2016 at 6:46 AM David McBride 
wrote:

> Team,
>
> I've posted an update to the schedule
> .
> Please review and provide feedback.
>
> Note:  during the release meeting on Tuesday, we discussed removing the
> JIRA milestone, since it was not considered release gating.  Since then,
> I've changed my mind.  For the D-release, I expect that we will have
> implemented our JIRA processes sufficiently that we will be able to rely on
> JIRA to understand project status.  Therefore, it is appropriate to believe
> that if we still have unresolved JIRA issues assigned to the release, then
> the release is not complete.  We will be discussing exactly how this will
> be accomplished in the coming weeks.
>
> David
>
>
> --
> *David McBride*
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
> ___
> 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] Does any one have updates for OPNFV VNFs avilable for on-boarding and testing

2016-09-08 Thread Prakash Ramchandran

Hi all,

We in   OPNFV Dovetail  as well opnfv-mano-wg ,would like to revisit and see 
what VNFs are available mainly  through Open Source and may be  through 
Licensing by OPNFV members.

This will help compliance use case testing and   newer projects Opera, 
Orchestra, Domino as well multi-release Parser, Copper and Model to build their 
use case to test around what is available.

Please update with what you have or know to enable us helping define what 
descriptors / image formats are available for us to help zero on what we can 
use or leverage in Release D and later.

https://wiki.opnfv.org/display/functest/List+Of+VNFs


Thanks
Prakash



Prakash Ramchandran
[logo_huawei] R USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com
Work:  +1 (408) 330-5489
Mobile: +1 (408) 406-5810
2330 Central Expy, Santa Clara, CA 95050, USA






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

Re: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

2016-09-08 Thread Prakash Ramchandran

Ashish,

I hear your approach from Neutron managing this, so this assumes some topology 
for multisite. Based on Release notes of OpenStack  Mitaka... I see

Deprecate security_group_api configuration option. The current values are nova 
and neutron. In future the correct security_group_api option will be chosen 
based on the value of use_neutron which provides a more coherent user 
experience.

I heard that JuJu uses its own secgroup which is different from Neutron and 
thus JOID installer had no issues based on changes to secgroup in Mitaka

So prescribing some flow you have mentioned  for security group is interesting 
and  like to know what topology of multisite you are referring to,  to be able 
to absorb, what actually is being proposed here for tech team to understand. 
Suggest you refer this to security working group or may be bring to weekly tech 
discussions as what exactly is current state of security group in OPNFV 
multisite project and what you would like to change to make it better.

If this is out of context please ignore it.

Thanks
Prakash


Prakash Ramchandran
[logo_huawei] R USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com
Work:  +1 (408) 330-5489
Mobile: +1 (408) 406-5810
2330 Central Expy, Santa Clara, CA 95050, USA






From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ashish singh
Sent: Thursday, September 08, 2016 8:58 AM
To: opnfv-tech-discuss; caizhiyuan (A); Meimei; Sama, Malla Reddy; Zhipeng 
Huang; Ashish singh; Dimitri Mazmanov; joehuang; Ashish Singh7
Subject: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

Hi All,

I have drafted a basic approach for security group synching in release D and it 
is as follows.

- Get list of secgroups  with rules for a tenant from all the regions which do 
not have remote group references(currently, we ignore remote secgroup 
references as there can be lot nested dependencies).
- Traverse each region and do the following
- Get the list of secgroup which are present in all the regions except 
the current region, These are the secgroups which we need to sync in current 
region: say it GRP_TO_BE_SYNCED
- There can be case where the secgroup from GRP_TO_BE_SYNCED may have 
the same rules as the secgroup in current region(If not initially but which 
will obviously happen after a sync job).
- Traverse through the GRP_TO_BE_SYNCED and check if there are such 
secgroups(rules overlapping groups), if there, ignore it. After this filtering, 
the remaining secgroup will be the final list of secgroup which should be 
created for the current region.
- Create the secgroup with the final list of secgroups in the region.
- Repeat the process for all the tenant in batches.
The default security group is not syned, as I feel region specific default 
secgroup has to there in each region.

We must use neutron to perform all our operations as with neutron we have total 
control over it.


For creating a security group we need the following information

  --tenant-id TENANT_ID
The owner tenant ID.
  --description DESCRIPTION
Description of security group rule.
  --direction {ingress,egress}
Direction of traffic: ingress/egress.
  --ethertype ETHERTYPE
IPv4/IPv6
  --protocol PROTOCOL   Protocol of packet. Allowed values are [icmp, icmpv6,
tcp, udp] and integer representations [0-255]
  --port-range-min PORT_RANGE_MIN
Starting port range. For ICMP it is type.
  --port-range-max PORT_RANGE_MAX  Ending port range. For ICMP it is code.
  --remote-ip-prefix REMOTE_IP_PREFIX
CIDR to match on.
We have all these details with us available.


Let us take this forward, Please review/comment.

--
Best Regards,
Ashish Singh
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite] Secgroup syncing Approach

2016-09-08 Thread Ashish singh

Hi All,

I have drafted a basic approach for security group synching in release D
and it is as follows.

- Get list of secgroups  with rules for a tenant from all the regions which
do not have remote group references(currently, we ignore remote secgroup
references as there can be lot nested dependencies).
- Traverse each region and do the following
- Get the list of secgroup which are present in all the regions
except the current region, These are the secgroups which we need to sync in
current region: say it GRP_TO_BE_SYNCED
- There can be case where the secgroup from GRP_TO_BE_SYNCED may
have the same rules as the secgroup in current region(If not initially but
which will obviously happen after a sync job).
- Traverse through the GRP_TO_BE_SYNCED and check if there are such
secgroups(rules overlapping groups), if there, ignore it. After this
filtering, the remaining secgroup will be the final list of secgroup which
should be created for the current region.
- Create the secgroup with the final list of secgroups in the
region.
- Repeat the process for all the tenant in batches.
The default security group is not syned, as I feel region specific default
secgroup has to there in each region.

We must use neutron to perform all our operations as with neutron we have
total control over it.


For creating a security group we need the following information

  --tenant-id TENANT_ID
The owner tenant ID.
  --description DESCRIPTION
Description of security group rule.
  --direction {ingress,egress}
Direction of traffic: ingress/egress.
  --ethertype ETHERTYPE
IPv4/IPv6
  --protocol PROTOCOL   Protocol of packet. Allowed values are [icmp,
icmpv6,
tcp, udp] and integer representations [0-255]
  --port-range-min PORT_RANGE_MIN
Starting port range. For ICMP it is type.
  --port-range-max PORT_RANGE_MAX  Ending port range. For ICMP it is
code.
  --remote-ip-prefix REMOTE_IP_PREFIX
CIDR to match on.
We have all these details with us available.


Let us take this forward, Please review/comment.

-- 
Best Regards,
Ashish Singh
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite] Approach for Secgroup syncing

2016-09-08 Thread Ashish Singh7

Hi All,

I have drafted a basic approach for security group synching in release D 
and it is as follows.

- Get list of secgroups  with rules for a tenant from all the regions 
which do not have remote group references(currently, we ignore remote 
secgroup references as there can be lot nested dependencies). 
- Traverse each region and do the following 
- Get the list of secgroup which are present in all the regions 
except the current region, These are the secgroups which we need to sync 
in current region: say it GRP_TO_BE_SYNCED
- There can be case where the secgroup from GRP_TO_BE_SYNCED may 
have the same rules as the secgroup in current region(If not initially but 
which will obviously happen after a sync job).
- Traverse through the GRP_TO_BE_SYNCED and check if there are 
such secgroups(rules overlapping groups), if there, ignore it. After this 
filtering, the remaining secgroup will be the final list of secgroup which 
should be created for the current region.
- Create the secgroup with the final list of secgroups in the 
region.
- Repeat the process for all the tenant in batches.
The default security group is not syned, as I feel region specific default 
secgroup has to there in each region.

We must use neutron to perform all our operations as with neutron we have 
total control over it. 


For creating a security group we need the following information

  --tenant-id TENANT_ID
The owner tenant ID.
  --description DESCRIPTION
Description of security group rule.
  --direction {ingress,egress}
Direction of traffic: ingress/egress.
  --ethertype ETHERTYPE
IPv4/IPv6
  --protocol PROTOCOL   Protocol of packet. Allowed values are [icmp, 
icmpv6,
tcp, udp] and integer representations [0-255]
  --port-range-min PORT_RANGE_MIN
Starting port range. For ICMP it is type.
  --port-range-max PORT_RANGE_MAX  Ending port range. For ICMP it is 
code.
  --remote-ip-prefix REMOTE_IP_PREFIX
CIDR to match on.
We have all these details with us available.


Let us take this forward, Please review/comment.

Regards
Ashish Singh
Tata Consultancy Services
Cell:- 9030419618
Mailto: ashish.sin...@tcs.com
Website: http://www.tcs.com

Experience certainty.   IT Services
Business Solutions
Consulting

=-=-=
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you


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

Re: [opnfv-tech-discuss] Following up on Project Health metrics discussion

2016-09-08 Thread Heather Kirksey

Good point, Frank. This shouldn't be viewed as set in stone but as an
evolving way to monitor our health as a project and to help ourselves
continue to improve and remain healthy over time. It's an attempt to give
ourselves some more quantitative insight there.

I know that it's considered part of the community manager's role within
OpenStack, for example, to monitor these sorts of metrics on a regular
basis and it use them to see trends or concerns and to help the project,
both at the TSC level and the PTL level. I know some other projects do this
as well, so we're trying to adopt best practices and learn from our fellow
travelers.

Heather

On Thu, Sep 8, 2016 at 8:27 AM, Frank Brockners (fbrockne) <
fbroc...@cisco.com> wrote:

> Hi Chris,
>
>
>
> thanks – as long as we clearly position this effort as one of “trying to
> drive proper metrics”, we should be fine. I’m just concerned that once we
> have these toy metrics that people will start to rely on them and read
> things into them that are just not reflecting reality.  This should
> obviously be avoided.
>
> I just updated the title of the wiki to reflect that this is a discussion
> page – and now a page with health metrics…
>
>
>
> Thanks, Frank
>
>
>
> *From:* Christopher Price [mailto:chrispric...@gmail.com]
> *Sent:* Donnerstag, 8. September 2016 15:57
> *To:* Frank Brockners (fbrockne) ; Raymond Paik <
> rp...@linuxfoundation.org>
> *Cc:* Daniel Smith ; Dave Neary <
> dne...@redhat.com>; SULLIVAN, BRYAN L ;
> opnfv-tech-discuss@lists.opnfv.org
>
> *Subject:* Re: [opnfv-tech-discuss] Following up on Project Health
> metrics discussion
>
>
>
> Hi Frank,
>
>
>
> I’m not sure I would equate the “rough metrics” implied in the current
> project lifecycle as providing significant guidance or establishing a
> meaningful measure of a projects maturity.  I might argue that they are
> sorely lacking on community discussion and agreement.
>
>
>
> I see this dialog on community metrics as one vehicle for our community to
> chime in and help set these guidelines with the TSC.  I would not propose
> we stop doing this because we feel the lifecycle metrics are sufficient,
> rather the opposite in that this work may help us find meaningful lifecycle
> metrics as a community.
>
>
>
> / Chris
>
>
>
> *From: *"Frank Brockners (fbrockne)" 
> *Date: *Thursday 8 September 2016 at 15:28
> *To: *Raymond Paik 
> *Cc: *Daniel Smith , Christopher Price <
> chrispric...@gmail.com>, Dave Neary , "SULLIVAN, BRYAN
> L" , TECH-DISCUSS OPNFV  opnfv.org>
> *Subject: *RE: [opnfv-tech-discuss] Following up on Project Health
> metrics discussion
>
>
>
> Ray,
>
>
>
> thanks – in which case, let’s first try to get the overall project
> lifecycle concept adopted. Once done – and we have experiences with the
> project life cycle, we can look into whether we need to create additional
> metrics etc. We could do that as another iteration of the project lifecycle
> doc – but for now, it would be key to get the lifecycle really adopted by
> projects. Let’s do one step after the other.
>
>
>
> Thanks, Frank
>
>
>
> *From:* Raymond Paik [mailto:rp...@linuxfoundation.org
> ]
> *Sent:* Donnerstag, 8. September 2016 15:23
> *To:* Frank Brockners (fbrockne) 
> *Cc:* Daniel Smith ; Christopher Price <
> chrispric...@gmail.com>; Dave Neary ; SULLIVAN, BRYAN
> L ; opnfv-tech-discuss@lists.opnfv.org
> *Subject:* Re: [opnfv-tech-discuss] Following up on Project Health
> metrics discussion
>
>
>
> Frank,
>
>
>
> It's in the same spirit as the project lifecycle you mentioned earlier.
> For example, I'd like to use it as one of the data points for guidance (as
> you noted) to highlight projects that are not doing as well
>
>
>
> Thanks,
>
>
>
> Ray
>
>
>
> On Thu, Sep 8, 2016 at 2:28 AM, Frank Brockners (fbrockne) <
> fbroc...@cisco.com> wrote:
>
> Hi Ray,
>
>
>
> question: What problem are we trying to solve with the metrics for project
> health?
>
> For the project lifecycle we have a defined process already – so nothing
> new is needed.
>
>
>
> Thanks, Frank
>
>
>
> *From:* Raymond Paik [mailto:rp...@linuxfoundation.org]
> *Sent:* Donnerstag, 8. September 2016 07:14
> *To:* Daniel Smith 
> *Cc:* Christopher Price ; Dave Neary <
> dne...@redhat.com>; Frank Brockners (fbrockne) ;
> SULLIVAN, BRYAN L ; opnfv-tech-discuss@lists.opnfv.org
>
>
> *Subject:* Re: [opnfv-tech-discuss] Following up on Project Health
> metrics discussion
>
>
>
> All,
>
>
>
> Glad to see the thread coming back to life (plus comments on the wiki) :-)
> Definitely understand concerns about the composite score.  Maybe another
> option would

Re: [opnfv-tech-discuss] Following up on Project Health metrics discussion

2016-09-08 Thread Frank Brockners (fbrockne)

s/now a page/not a page/

Frank

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Frank 
Brockners (fbrockne)
Sent: Donnerstag, 8. September 2016 17:28
To: Christopher Price ; Raymond Paik 

Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Following up on Project Health metrics 
discussion

Hi Chris,

thanks – as long as we clearly position this effort as one of “trying to drive 
proper metrics”, we should be fine. I’m just concerned that once we have these 
toy metrics that people will start to rely on them and read things into them 
that are just not reflecting reality.  This should obviously be avoided.
I just updated the title of the wiki to reflect that this is a discussion page 
– and now a page with health metrics…

Thanks, Frank

From: Christopher Price [mailto:chrispric...@gmail.com]
Sent: Donnerstag, 8. September 2016 15:57
To: Frank Brockners (fbrockne) >; 
Raymond Paik >
Cc: Daniel Smith >; 
Dave Neary >; SULLIVAN, BRYAN L 
>; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Following up on Project Health metrics 
discussion

Hi Frank,

I’m not sure I would equate the “rough metrics” implied in the current project 
lifecycle as providing significant guidance or establishing a meaningful 
measure of a projects maturity.  I might argue that they are sorely lacking on 
community discussion and agreement.

I see this dialog on community metrics as one vehicle for our community to 
chime in and help set these guidelines with the TSC.  I would not propose we 
stop doing this because we feel the lifecycle metrics are sufficient, rather 
the opposite in that this work may help us find meaningful lifecycle metrics as 
a community.

/ Chris

From: "Frank Brockners (fbrockne)" 
>
Date: Thursday 8 September 2016 at 15:28
To: Raymond Paik >
Cc: Daniel Smith >, 
Christopher Price >, Dave 
Neary >, "SULLIVAN, BRYAN L" 
>, TECH-DISCUSS OPNFV 
>
Subject: RE: [opnfv-tech-discuss] Following up on Project Health metrics 
discussion

Ray,

thanks – in which case, let’s first try to get the overall project lifecycle 
concept adopted. Once done – and we have experiences with the project life 
cycle, we can look into whether we need to create additional metrics etc. We 
could do that as another iteration of the project lifecycle doc – but for now, 
it would be key to get the lifecycle really adopted by projects. Let’s do one 
step after the other.

Thanks, Frank

From: Raymond Paik [mailto:rp...@linuxfoundation.org]
Sent: Donnerstag, 8. September 2016 15:23
To: Frank Brockners (fbrockne) >
Cc: Daniel Smith >; 
Christopher Price >; Dave 
Neary >; SULLIVAN, BRYAN L 
>; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Following up on Project Health metrics 
discussion

Frank,

It's in the same spirit as the project lifecycle you mentioned earlier.  For 
example, I'd like to use it as one of the data points for guidance (as you 
noted) to highlight projects that are not doing as well

Thanks,

Ray

On Thu, Sep 8, 2016 at 2:28 AM, Frank Brockners (fbrockne) 
> wrote:
Hi Ray,

question: What problem are we trying to solve with the metrics for project 
health?
For the project lifecycle we have a defined process already – so nothing new is 
needed.

Thanks, Frank

From: Raymond Paik 
[mailto:rp...@linuxfoundation.org]
Sent: Donnerstag, 8. September 2016 07:14
To: Daniel Smith >
Cc: Christopher Price >; 
Dave Neary >; Frank Brockners 
(fbrockne) >; SULLIVAN, BRYAN L 
>; 
opnfv-tech-discuss@lists.opnfv.org

Subject: Re: [opnfv-tech-discuss]

[opnfv-tech-discuss] [linuxfoundation.org #28648] Re: [linuxfoundation.org #28648] 答复: Re: [OPNFV Helpdesk #28648] AutoReply: [qtip] Nomination of Committer promotion for jiang.zhif...@zte.com.cn

2016-09-08 Thread Aric Gardner via RT

I have sent a second invite.
-Aric

On Thu, Sep 8, 2016 at 6:43 AM, jiang.zhif...@zte.com.cn via RT
 wrote:
> Hello
>  I check my history mail but I can not find it, maybe I delete it by
> mistake. Could you send me again.Thanks
> Regards,
> zhifeng.jiang
>
>
>
> "Aric Gardner via RT" 
> 09/06/2016 11:22 PM
> 请答复 给
> opnfv-helpd...@rt.linuxfoundation.org
>
>
> 收件人
> zhangyujun+...@gmail.com
> 抄送
> jiang.zhif...@zte.com.cn, opnfv-tech-discuss@lists.opnfv.org,
> opnfv-...@lists.opnfv.org
> 主题
> Re: [OPNFV Helpdesk #28648] AutoReply: [qtip] Nomination of Committer
> promotion for jiang.zhif...@zte.com.cn
>
>
>
>
>
>
> Hi,
>
> I have sent jiang.zhif...@zte.com.cn an invite to join the qtip
> submitters group.
> In the future please do all of the voting on the same channel (Ie
> gerrit or email) as this is easier to keep track of and refer to.
>
> Regards,
> Aric
>
>
> On Tue, Sep 6, 2016 at 9:32 AM, zhangyujun+...@gmail.com via RT
>  wrote:
>>
>> https://rt.linuxfoundation.org/Ticket/Display.html?id=28648 >
>>
>> How is it going?
>>
>> On Mon, Aug 29, 2016 at 1:53 PM OPNFV Helpdesk via RT <
>> opnfv-helpd...@rt.linuxfoundation.org> wrote:
>>
>>>
>>> Greetings,
>>>
>>> Your support ticket regarding:
>>> "[qtip] Nomination of Committer promotion for
>>> jiang.zhif...@zte.com.cn",
>>> has been entered in our ticket tracker.  A summary of your ticket
> appears
>>> below.
>>>
>>> If you have any follow-up related to this issue, please reply to this
>>> email or include:
>>>
>>>  [OPNFV Helpdesk #28648]
>>>
>>> in the subject line of subsequent emails.
>>>
>>> Thank you,
>>> Linux Foundation Support Team
>>>
>>>
> -
>>> I would like to inform TSC that Zhifeng Jiang has been added as a
> committer
>>> to qtip project.
>>>
>>> Voted by Email
>>>
>>> +1 Morgan  Richommemorgan.richo...@orange.com
>>> +1 Nauman  Ahadnauman.a...@xflowresearch.com
>>> +1 Prabu   Kuppuswamy  prabu.kuppusw...@spirent.com
>>> +1 Prakash Ramchandran prakash.ramchand...@huawei.com
>>>
>>> Voted in Gerrit [1][2]
>>>
>>> +1 Wenjing Chu chu.wenj...@gmail.com
>>> +1 Yujun   Zhang   zhang.yuj...@zte.com.cn
>>>
>>> No response yet
>>>
>>> Michael Haugh   mha...@ixiacom.com
>>> Trevor  Cooper  trevor.coo...@intel.com
>>>
>>> [1] https://gerrit.opnfv.org/gerrit/#/c/19141/
>>> [2] https://gerrit.opnfv.org/gerrit/#/c/19703/
>>>
>>> Nominating Zhifeng Jiang  as new committer
> for
>>> QTIP project. Zhifeng has been contributed a majority of code to QTIP
> since
>>> last season[1][2]. I believe she will help QTIP project to make a
> success
>>> in next release. All qtip committers, please vote +1 or +2 if you
> support
>>> this nomination [3]. This patch reopens #19141 [4]. Please DO NOT merge
>>> until we get a majority. [1]
>>>
>>>
> http://stackalytics.com/?project_type=opnfv-group=commits=qtip
>
>>> [2]
>>>
> https://git.opnfv.org/cgit/qtip/log/?qt=author=jiang.zhifeng%40zte.com.cn
>
>>> [3] https://wiki.opnfv.org/display/DEV/Committer+Promotions [4]
>>> https://gerrit.opnfv.org/gerrit/#/c/19141/
>>>
>>>
>>> On Mon, Aug 29, 2016 at 1:25 PM Kuppuswamy, Prabu <
>>> prabu.kuppusw...@spirent.com> wrote:
>>>
>>> > +1
>>> >
>>> >
>>> >
>>> > *From:* Yujun Zhang [mailto:zhangyujun+...@gmail.com]
>>> > *Sent:* Monday, August 29, 2016 7:55 AM
>>> > *To:* Kuppuswamy, Prabu ; Prakash
>>> > Ramchandran ; Cooper, Trevor <
>>> > trevor.coo...@intel.com>; iben.rodrig...@vmsec.com
>>> > *Cc:* TECH-DISCUSS OPNFV 
>>> >
>>> >
>>> > *Subject:* Re: [qtip] nominating Zhifeng Jiang as committer
>>> >
>>> >
>>> >
>>> > A reminder for committers who haven't vote yet.
>>> >
>>> >
>>> >
>>> > Please either reply to this thread or vote on gerrit [1]
>>> >
>>> >
>>> >
>>> > Thank you for your supporting to qtip project.
>>> >
>>> >
>>> >
>>> > [1] https://gerrit.opnfv.org/gerrit/#/c/19703/
>>> >
>>> >
>>> >
>>> > On Mon, Aug 22, 2016 at 11:47 AM Yujun Zhang
> 
>>> > wrote:
>>> >
>>> > Dear Qtip committers,
>>> >
>>> >
>>> >
>>> > I'd like to nominate Zhifeng Jiang  as new
>>> > committer for QTIP project.
>>> >
>>> >
>>> >
>>> > Zhifeng has been contributed a majority of code to QTIP since last
>>> > season[1]. I believe she will help QTIP project to make a success in
> next
>>> > release.
>>> >
>>> >
>>> >
>>> > Please vote +2 in https://gerrit.opnfv.org/gerrit/#/c/19141/ if you
>>> agree.
>>> >
>>> >
>>> >
>>> > [1]
>>> >
>>>
> http://stackalytics.com/?project_type=opnfv-group=commits=qtip
>
>>> >
>>> >
>>> >
>>> > [image: image001.png]
>>> >
>>> >
>>> >
>>> > --
>>> >
>>> > Yujun
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > Spirent Communications e-mail confidentiality.
>>> >
>

Re: [opnfv-tech-discuss] [opnfv-mano-wg] Need Subscription list plus discussions for Sept 14 VNF onbaoarding & Mapping TOSCA service to NFV{VNFD+NSD}

2016-09-08 Thread SULLIVAN, BRYAN L

Prakash,

Some responses inline.

Thanks,
Bryan Sullivan | AT

From: Prakash Ramchandran [mailto:prakash.ramchand...@huawei.com]
Sent: Tuesday, September 06, 2016 6:53 PM
To: opnfv-tech-discuss@lists.opnfv.org
Cc: Margaret Chiosi ; SULLIVAN, BRYAN L 
; denglin...@chinamobile.com; 
giuseppe.care...@fokus.fraunhofer.de; Ulas Kozat ; 
Yingjun Li ; artur.tyl...@canonical.com; 
dne...@redhat.com; sric...@gmail.com; bob.monk...@arm.com; 
christopher.pr...@ericsson.com; raghavendrachari.kams...@hpe.com; 
ljlam...@live.com
Subject: [opnfv-tech-discuss][opnfv-mano-wg] Need Subscription list plus 
discussions for Sept 14 VNF onbaoarding & Mapping TOSCA service to NFV{VNFD+NSD}

Hi all,
There  was a request from Margret that she cannot  get this as without joining 
opnfv-tech-list and that she and many in Polestar/S would prefer that we have 
a separate opnnfv-mano-wg subscription. My understanding is that this will be 
addressed by LF helpdesk. Until then I am copying the listed participants of 
MANO WG on wiki page and this is for September 14th meeting. We still have a 
week's time to get things moving.

If so can I request LF helpdesk to enable the opnfv-mano-wg subscription list.
 We do have #opnfv-mano channel that we use besides the scheduled

As part of MANO WG tasks would like to initiate debate on following items:

Like to verify with Models & Domino/parser if they would create a opnfv-mano-wg 
tags and create a Jira tickets for the  same?
[bryan] Not sure what you mean by tags or why we need to create Jira tickets. I 
recommend to avoid getting too deep into Jira for project management at the 
level that these groups work (analysis, experimentation, specification). My 
experience is that except for code dev/bug tracking, Jira brings a lot of 
overhead that I don't think we need. Outlining the work of the group at a 
high-level is fine with Jira, but let's watch out for the overhead.

1.   VNF On boarding as listed by Polestar / S team by Bryan

[bryan] I will add some of the aspects of this to the wiki, as I described on 
the call, including a high-level outline of a conceptual process for 
onboarding, highlighting aspects that I think are potentially in scope for 
OPNFV projects (including those underway, today). This is work that is in the 
scope of the MANO WG, since it helps draw a thread through many of the systems 
and processes that make up a MANO stack, and above (e.g. business processes 
that are outside OPNFV/OpenSource scope).
? VNF Packaging - Compare and contrast  in how JuJu and Tacker  use OpenStack 
Glance or SDN-C (ODL/ONOS/OC}  {how do they align with IFA011?}
[bryan] This analysis is underway (or at least in scope) in the Models project, 
as a test/documentation exercise. The current state of that project is setting 
up the test environment (Cloudify, Tacker, JuJu, OpenBaton, etc) to assess how 
MANO-stack projects require/support various VNF Package elements, starting with 
TOSCA-based blueprints for reference VNFs (which will become part of the OPNFV 
CI/CD inventory along with vIMS). I welcome the support of anyone that wants to 
focus on the specific question Prakash mentioned.

2. Mapping between TOSCA and NFV for using VNFD from oasis for VNFM to use 
(http://docs.oasis-open.org/tosca/tosca-nfv/v1.0/csd03/tosca-nfv-v1.0-csd03.pdf 
)
? Review how Service Descriptors from TOSCA match with NFV and if mapped 
correctly can  Template Distribution and Parsing manage this to deliver to 
orchestrators   like Heat or any controller that can support Pub/Sub via OPNFV 
project like Domino/Parser?
[bryan] VNF Package cataloging/distribution is one of the key aspects of an 
onboarding process. As mentioned AFAIK only the Domino project has been 
considering so far some of the technical approaches to blueprint/template 
distribution (along with other VNF assets). The mapping of elements (e.g. 
Service Descriptors) is part of the information model - data model analysis 
that needs to be done; work that so far is still in the SDO realm AFAICT.

3. Would like to see OPEN-O(Opera) / OpenBaton (Orchestra) to add any Jira 
tickets that will help them on IFA007, use case or API aspects that would like 
to bring to opnfv-mano-wg

Once we know JIRA tickets are established will let Bryan lead us on 1 and will 
try bring some proposal for 2 working with Domino/Parser projects and PTLS of 
Opera and Orchestra as what they will need guidance from MANO WG to support 
them.

Thanks
Prakash

Prakash Ramchandran
[logo_huawei] R USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com
Work:  +1 (408) 330-5489
Mobile: +1 (408) 406-5810
2330 Central Expy, Santa Clara, CA 95050, USA

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

[opnfv-tech-discuss] [Polestar] ODL Summit Bellevue F2F meeting

2016-09-08 Thread Margaret Chiosi

Folks we are planning on getting together with the EUG and MANO WG in a F2F
in Bellevue on thursday 9/29 12-3PM PST. I added a meeting agenda in the
Polestar WG meetings section. Feel freel to topics. Main focus is to flush
out VNF onboarding.

For folks who will be at the ODL summit - let me know if you want to attend
this meeting but 12-3 is too late for you due to flights. thanks.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Following up on Project Health metrics discussion

2016-09-08 Thread Frank Brockners (fbrockne)

Ray,

thanks – in which case, let’s first try to get the overall project lifecycle 
concept adopted. Once done – and we have experiences with the project life 
cycle, we can look into whether we need to create additional metrics etc. We 
could do that as another iteration of the project lifecycle doc – but for now, 
it would be key to get the lifecycle really adopted by projects. Let’s do one 
step after the other.

Thanks, Frank

From: Raymond Paik [mailto:rp...@linuxfoundation.org]
Sent: Donnerstag, 8. September 2016 15:23
To: Frank Brockners (fbrockne) 
Cc: Daniel Smith ; Christopher Price 
; Dave Neary ; SULLIVAN, BRYAN L 
; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Following up on Project Health metrics 
discussion

Frank,

It's in the same spirit as the project lifecycle you mentioned earlier.  For 
example, I'd like to use it as one of the data points for guidance (as you 
noted) to highlight projects that are not doing as well

Thanks,

Ray

On Thu, Sep 8, 2016 at 2:28 AM, Frank Brockners (fbrockne) 
> wrote:
Hi Ray,

question: What problem are we trying to solve with the metrics for project 
health?
For the project lifecycle we have a defined process already – so nothing new is 
needed.

Thanks, Frank

From: Raymond Paik 
[mailto:rp...@linuxfoundation.org]
Sent: Donnerstag, 8. September 2016 07:14
To: Daniel Smith >
Cc: Christopher Price >; 
Dave Neary >; Frank Brockners 
(fbrockne) >; SULLIVAN, BRYAN L 
>; 
opnfv-tech-discuss@lists.opnfv.org

Subject: Re: [opnfv-tech-discuss] Following up on Project Health metrics 
discussion

All,

Glad to see the thread coming back to life (plus comments on the wiki) :-) 
Definitely understand concerns about the composite score.  Maybe another option 
would be to start by looking at 4 areas (git, Jira, wiki, etc.) individually.

I also want to suggest that if a project is active (and even if most of the 
work is being done upstream) I doubt the activities in OPNFV repo or other 
tools would be zero over a period of 3-6 months.  So I think having a regular 
metrics (composite or otherwise) would be helpful in identifying projects that 
are either in need of help or are candidates for "archiving"

My 2 cents

Ray

On Wed, Sep 7, 2016 at 9:42 PM, Daniel Smith 
> wrote:
Hello All.

My take on this and sorry maybe a bit blunt, but I don’t see what the purpose 
is here?

While guideline, guidance and such are good things, the discussion below seems 
awfully heavy and very boxed in.

As Chris in the evaluation on how to improve the community, I am not sure how 
we could ever resolve what one person thinks is an adequate measure of 
something over another (i.e endless debate), since metrics, improvements - 
unless we are talking about something quantifiable - and that would mean taking 
this to code optimization level ultimately - are subjective based and 
implement/reaction based measured over time in the case of adjustment.

As well +1 to doing our own assessments - since it should be us that outlines 
what we want to say about how we feel we have improved, and this only makes 
sense I would think as we are the only ones who have the context to see where 
we came from to where we are and what we are talking about doing next.

I would say however, that I am really concerned at that level of discussion 
across all meetings on project handling and process and such - release and 
otherwise - while this shows we are active and "moving" sure - there is a lot 
of dissonance in the communication, mixed messages and again, lots of 
information overflow.   I would like to see the "Operational" parts of OPNFV 
(Release Project, INFRA, TSC) focus more on how we support the projects in 
terms of day to day pain points - that is a solid, referable release process, a 
solid, regularly maintained method of publish,  a solid Change process (for 
anything) that ensures that we don’t discuss and move from one week to another 
- not because an idea is good or bad, but simply cause we need to recognize 
that there are more than the 25 or so regular attendees in the groups / this 
mailing list.

Would there be a market for such publishing outside our domain I would wonder?  
For Code stats and fun numbers those are nice to have, but a qualitative review 
of how we have improved our processes as a community, im not sure?  I would 
vouchsafe that our work in the projects themselves are what OPNFV is pushing 
out, the operational

Re: [opnfv-tech-discuss] Following up on Project Health metrics discussion

2016-09-08 Thread Raymond Paik

Frank,

It's in the same spirit as the project lifecycle you mentioned earlier.
For example, I'd like to use it as one of the data points for guidance (as
you noted) to highlight projects that are not doing as well

Thanks,

Ray

On Thu, Sep 8, 2016 at 2:28 AM, Frank Brockners (fbrockne) <
fbroc...@cisco.com> wrote:

> Hi Ray,
>
>
>
> question: What problem are we trying to solve with the metrics for project
> health?
>
> For the project lifecycle we have a defined process already – so nothing
> new is needed.
>
>
>
> Thanks, Frank
>
>
>
> *From:* Raymond Paik [mailto:rp...@linuxfoundation.org]
> *Sent:* Donnerstag, 8. September 2016 07:14
> *To:* Daniel Smith 
> *Cc:* Christopher Price ; Dave Neary <
> dne...@redhat.com>; Frank Brockners (fbrockne) ;
> SULLIVAN, BRYAN L ; opnfv-tech-discuss@lists.opnfv.org
>
> *Subject:* Re: [opnfv-tech-discuss] Following up on Project Health
> metrics discussion
>
>
>
> All,
>
>
>
> Glad to see the thread coming back to life (plus comments on the wiki) :-)
> Definitely understand concerns about the composite score.  Maybe another
> option would be to start by looking at 4 areas (git, Jira, wiki, etc.)
> individually.
>
>
>
> I also want to suggest that if a project is active (and even if most of
> the work is being done upstream) I doubt the activities in OPNFV repo or
> other tools would be zero over a period of 3-6 months.  So I think having a
> regular metrics (composite or otherwise) would be helpful in identifying
> projects that are either in need of help or are candidates for "archiving"
>
>
>
> My 2 cents
>
>
>
> Ray
>
>
>
> On Wed, Sep 7, 2016 at 9:42 PM, Daniel Smith 
> wrote:
>
> Hello All.
>
> My take on this and sorry maybe a bit blunt, but I don’t see what the
> purpose is here?
>
> While guideline, guidance and such are good things, the discussion below
> seems awfully heavy and very boxed in.
>
> As Chris in the evaluation on how to improve the community, I am not sure
> how we could ever resolve what one person thinks is an adequate measure of
> something over another (i.e endless debate), since metrics, improvements -
> unless we are talking about something quantifiable - and that would mean
> taking this to code optimization level ultimately - are subjective based
> and implement/reaction based measured over time in the case of adjustment.
>
> As well +1 to doing our own assessments - since it should be us that
> outlines what we want to say about how we feel we have improved, and this
> only makes sense I would think as we are the only ones who have the context
> to see where we came from to where we are and what we are talking about
> doing next.
>
> I would say however, that I am really concerned at that level of
> discussion across all meetings on project handling and process and such -
> release and otherwise - while this shows we are active and "moving" sure -
> there is a lot of dissonance in the communication, mixed messages and
> again, lots of information overflow.   I would like to see the
> "Operational" parts of OPNFV (Release Project, INFRA, TSC) focus more on
> how we support the projects in terms of day to day pain points - that is a
> solid, referable release process, a solid, regularly maintained method of
> publish,  a solid Change process (for anything) that ensures that we don’t
> discuss and move from one week to another - not because an idea is good or
> bad, but simply cause we need to recognize that there are more than the 25
> or so regular attendees in the groups / this mailing list.
>
> Would there be a market for such publishing outside our domain I would
> wonder?  For Code stats and fun numbers those are nice to have, but a
> qualitative review of how we have improved our processes as a community, im
> not sure?  I would vouchsafe that our work in the projects themselves are
> what OPNFV is pushing out, the operational aspects of "how we are doing
> things" - while nice to outline, against the backdrop of every growing
> laundry list of things to "Decide" is really not high on a list?I
> didn’t understand from below the "why" and "who" for this fully.
>
>
> Cheers and thank you
> D
>
>
>
>
>
> -Original Message-
> From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Christopher Price
> Sent: Wednesday, September 07, 2016 9:20 PM
> To: Dave Neary ; Frank Brockners (fbrockne) <
> fbroc...@cisco.com>; SULLIVAN, BRYAN L ; Raymond Paik <
> rp...@linuxfoundation.org>; opnfv-tech-discuss@lists.opnfv.org
> Subject: Re: [opnfv-tech-discuss] Following up on Project Health metrics
> discussion
>
> Good comments Dave and everyone, I’d like to share my take on it is this.
>
> I don’t see any problem in looking at the metrics we already publish and
> using them to help us create a better understanding

[opnfv-tech-discuss] [linuxfoundation.org #28648] 答复: Re: [OPNFV Helpdesk #28648] AutoReply: [qtip] Nomination of Committer promotion for jiang.zhif...@zte.com.cn

2016-09-08 Thread jiang.zhif...@zte.com.cn via RT

Hello
 I check my history mail but I can not find it, maybe I delete it by 
mistake. Could you send me again.Thanks
Regards,
zhifeng.jiang



"Aric Gardner via RT"  
09/06/2016 11:22 PM
请答复 给
opnfv-helpd...@rt.linuxfoundation.org


收件人
zhangyujun+...@gmail.com
抄送
jiang.zhif...@zte.com.cn, opnfv-tech-discuss@lists.opnfv.org, 
opnfv-...@lists.opnfv.org
主题
Re: [OPNFV Helpdesk #28648] AutoReply: [qtip] Nomination of Committer 
promotion for jiang.zhif...@zte.com.cn






Hi,

I have sent jiang.zhif...@zte.com.cn an invite to join the qtip
submitters group.
In the future please do all of the voting on the same channel (Ie
gerrit or email) as this is easier to keep track of and refer to.

Regards,
Aric


On Tue, Sep 6, 2016 at 9:32 AM, zhangyujun+...@gmail.com via RT
 wrote:
>
> https://rt.linuxfoundation.org/Ticket/Display.html?id=28648 >
>
> How is it going?
>
> On Mon, Aug 29, 2016 at 1:53 PM OPNFV Helpdesk via RT <
> opnfv-helpd...@rt.linuxfoundation.org> wrote:
>
>>
>> Greetings,
>>
>> Your support ticket regarding:
>> "[qtip] Nomination of Committer promotion for
>> jiang.zhif...@zte.com.cn",
>> has been entered in our ticket tracker.  A summary of your ticket 
appears
>> below.
>>
>> If you have any follow-up related to this issue, please reply to this
>> email or include:
>>
>>  [OPNFV Helpdesk #28648]
>>
>> in the subject line of subsequent emails.
>>
>> Thank you,
>> Linux Foundation Support Team
>>
>> 
-
>> I would like to inform TSC that Zhifeng Jiang has been added as a 
committer
>> to qtip project.
>>
>> Voted by Email
>>
>> +1 Morgan  Richommemorgan.richo...@orange.com
>> +1 Nauman  Ahadnauman.a...@xflowresearch.com
>> +1 Prabu   Kuppuswamy  prabu.kuppusw...@spirent.com
>> +1 Prakash Ramchandran prakash.ramchand...@huawei.com
>>
>> Voted in Gerrit [1][2]
>>
>> +1 Wenjing Chu chu.wenj...@gmail.com
>> +1 Yujun   Zhang   zhang.yuj...@zte.com.cn
>>
>> No response yet
>>
>> Michael Haugh   mha...@ixiacom.com
>> Trevor  Cooper  trevor.coo...@intel.com
>>
>> [1] https://gerrit.opnfv.org/gerrit/#/c/19141/
>> [2] https://gerrit.opnfv.org/gerrit/#/c/19703/
>>
>> Nominating Zhifeng Jiang  as new committer 
for
>> QTIP project. Zhifeng has been contributed a majority of code to QTIP 
since
>> last season[1][2]. I believe she will help QTIP project to make a 
success
>> in next release. All qtip committers, please vote +1 or +2 if you 
support
>> this nomination [3]. This patch reopens #19141 [4]. Please DO NOT merge
>> until we get a majority. [1]
>>
>> 
http://stackalytics.com/?project_type=opnfv-group=commits=qtip

>> [2]
>> 
https://git.opnfv.org/cgit/qtip/log/?qt=author=jiang.zhifeng%40zte.com.cn

>> [3] https://wiki.opnfv.org/display/DEV/Committer+Promotions [4]
>> https://gerrit.opnfv.org/gerrit/#/c/19141/
>>
>>
>> On Mon, Aug 29, 2016 at 1:25 PM Kuppuswamy, Prabu <
>> prabu.kuppusw...@spirent.com> wrote:
>>
>> > +1
>> >
>> >
>> >
>> > *From:* Yujun Zhang [mailto:zhangyujun+...@gmail.com]
>> > *Sent:* Monday, August 29, 2016 7:55 AM
>> > *To:* Kuppuswamy, Prabu ; Prakash
>> > Ramchandran ; Cooper, Trevor <
>> > trevor.coo...@intel.com>; iben.rodrig...@vmsec.com
>> > *Cc:* TECH-DISCUSS OPNFV 
>> >
>> >
>> > *Subject:* Re: [qtip] nominating Zhifeng Jiang as committer
>> >
>> >
>> >
>> > A reminder for committers who haven't vote yet.
>> >
>> >
>> >
>> > Please either reply to this thread or vote on gerrit [1]
>> >
>> >
>> >
>> > Thank you for your supporting to qtip project.
>> >
>> >
>> >
>> > [1] https://gerrit.opnfv.org/gerrit/#/c/19703/
>> >
>> >
>> >
>> > On Mon, Aug 22, 2016 at 11:47 AM Yujun Zhang 

>> > wrote:
>> >
>> > Dear Qtip committers,
>> >
>> >
>> >
>> > I'd like to nominate Zhifeng Jiang  as new
>> > committer for QTIP project.
>> >
>> >
>> >
>> > Zhifeng has been contributed a majority of code to QTIP since last
>> > season[1]. I believe she will help QTIP project to make a success in 
next
>> > release.
>> >
>> >
>> >
>> > Please vote +2 in https://gerrit.opnfv.org/gerrit/#/c/19141/ if you
>> agree.
>> >
>> >
>> >
>> > [1]
>> >
>> 
http://stackalytics.com/?project_type=opnfv-group=commits=qtip

>> >
>> >
>> >
>> > [image: image001.png]
>> >
>> >
>> >
>> > --
>> >
>> > Yujun
>> >
>> >
>> >
>> >
>> >
>> > Spirent Communications e-mail confidentiality.
>> > 

>> > This e-mail contains confidential and / or privileged information
>> > belonging to Spirent Communications plc, its affiliates and / or
>> > subsidiaries. If you are not the intended recipient, you are hereby
>> > notified that any disclosure, copying, distribution and / or the 
taking
>> of

[opnfv-tech-discuss] 答复: Re: [OPNFV Helpdesk #28648] AutoReply: [qtip] Nomination of Committer promotion for jiang.zhif...@zte.com.cn

2016-09-08 Thread Jiang . ZhiFeng

Hello
 I check my history mail but I can not find it, maybe I delete it by 
mistake. Could you send me again.Thanks
Regards,
zhifeng.jiang



"Aric Gardner via RT"  
09/06/2016 11:22 PM
请答复 给
opnfv-helpd...@rt.linuxfoundation.org


收件人
zhangyujun+...@gmail.com
抄送
jiang.zhif...@zte.com.cn, opnfv-tech-discuss@lists.opnfv.org, 
opnfv-...@lists.opnfv.org
主题
Re: [OPNFV Helpdesk #28648] AutoReply: [qtip] Nomination of Committer 
promotion for jiang.zhif...@zte.com.cn






Hi,

I have sent jiang.zhif...@zte.com.cn an invite to join the qtip
submitters group.
In the future please do all of the voting on the same channel (Ie
gerrit or email) as this is easier to keep track of and refer to.

Regards,
Aric


On Tue, Sep 6, 2016 at 9:32 AM, zhangyujun+...@gmail.com via RT
 wrote:
>
> https://rt.linuxfoundation.org/Ticket/Display.html?id=28648 >
>
> How is it going?
>
> On Mon, Aug 29, 2016 at 1:53 PM OPNFV Helpdesk via RT <
> opnfv-helpd...@rt.linuxfoundation.org> wrote:
>
>>
>> Greetings,
>>
>> Your support ticket regarding:
>> "[qtip] Nomination of Committer promotion for
>> jiang.zhif...@zte.com.cn",
>> has been entered in our ticket tracker.  A summary of your ticket 
appears
>> below.
>>
>> If you have any follow-up related to this issue, please reply to this
>> email or include:
>>
>>  [OPNFV Helpdesk #28648]
>>
>> in the subject line of subsequent emails.
>>
>> Thank you,
>> Linux Foundation Support Team
>>
>> 
-
>> I would like to inform TSC that Zhifeng Jiang has been added as a 
committer
>> to qtip project.
>>
>> Voted by Email
>>
>> +1 Morgan  Richommemorgan.richo...@orange.com
>> +1 Nauman  Ahadnauman.a...@xflowresearch.com
>> +1 Prabu   Kuppuswamy  prabu.kuppusw...@spirent.com
>> +1 Prakash Ramchandran prakash.ramchand...@huawei.com
>>
>> Voted in Gerrit [1][2]
>>
>> +1 Wenjing Chu chu.wenj...@gmail.com
>> +1 Yujun   Zhang   zhang.yuj...@zte.com.cn
>>
>> No response yet
>>
>> Michael Haugh   mha...@ixiacom.com
>> Trevor  Cooper  trevor.coo...@intel.com
>>
>> [1] https://gerrit.opnfv.org/gerrit/#/c/19141/
>> [2] https://gerrit.opnfv.org/gerrit/#/c/19703/
>>
>> Nominating Zhifeng Jiang  as new committer 
for
>> QTIP project. Zhifeng has been contributed a majority of code to QTIP 
since
>> last season[1][2]. I believe she will help QTIP project to make a 
success
>> in next release. All qtip committers, please vote +1 or +2 if you 
support
>> this nomination [3]. This patch reopens #19141 [4]. Please DO NOT merge
>> until we get a majority. [1]
>>
>> 
http://stackalytics.com/?project_type=opnfv-group=commits=qtip

>> [2]
>> 
https://git.opnfv.org/cgit/qtip/log/?qt=author=jiang.zhifeng%40zte.com.cn

>> [3] https://wiki.opnfv.org/display/DEV/Committer+Promotions [4]
>> https://gerrit.opnfv.org/gerrit/#/c/19141/
>>
>>
>> On Mon, Aug 29, 2016 at 1:25 PM Kuppuswamy, Prabu <
>> prabu.kuppusw...@spirent.com> wrote:
>>
>> > +1
>> >
>> >
>> >
>> > *From:* Yujun Zhang [mailto:zhangyujun+...@gmail.com]
>> > *Sent:* Monday, August 29, 2016 7:55 AM
>> > *To:* Kuppuswamy, Prabu ; Prakash
>> > Ramchandran ; Cooper, Trevor <
>> > trevor.coo...@intel.com>; iben.rodrig...@vmsec.com
>> > *Cc:* TECH-DISCUSS OPNFV 
>> >
>> >
>> > *Subject:* Re: [qtip] nominating Zhifeng Jiang as committer
>> >
>> >
>> >
>> > A reminder for committers who haven't vote yet.
>> >
>> >
>> >
>> > Please either reply to this thread or vote on gerrit [1]
>> >
>> >
>> >
>> > Thank you for your supporting to qtip project.
>> >
>> >
>> >
>> > [1] https://gerrit.opnfv.org/gerrit/#/c/19703/
>> >
>> >
>> >
>> > On Mon, Aug 22, 2016 at 11:47 AM Yujun Zhang 

>> > wrote:
>> >
>> > Dear Qtip committers,
>> >
>> >
>> >
>> > I'd like to nominate Zhifeng Jiang  as new
>> > committer for QTIP project.
>> >
>> >
>> >
>> > Zhifeng has been contributed a majority of code to QTIP since last
>> > season[1]. I believe she will help QTIP project to make a success in 
next
>> > release.
>> >
>> >
>> >
>> > Please vote +2 in https://gerrit.opnfv.org/gerrit/#/c/19141/ if you
>> agree.
>> >
>> >
>> >
>> > [1]
>> >
>> 
http://stackalytics.com/?project_type=opnfv-group=commits=qtip

>> >
>> >
>> >
>> > [image: image001.png]
>> >
>> >
>> >
>> > --
>> >
>> > Yujun
>> >
>> >
>> >
>> >
>> >
>> > Spirent Communications e-mail confidentiality.
>> > 

>> > This e-mail contains confidential and / or privileged information
>> > belonging to Spirent Communications plc, its affiliates and / or
>> > subsidiaries. If you are not the intended recipient, you are hereby
>> > notified that any disclosure, copying, distribution and / or the 
taking
>> of

Re: [opnfv-tech-discuss] Following up on Project Health metrics discussion

2016-09-08 Thread Frank Brockners (fbrockne)

Hi Ray,

question: What problem are we trying to solve with the metrics for project 
health?
For the project lifecycle we have a defined process already – so nothing new is 
needed.

Thanks, Frank

From: Raymond Paik [mailto:rp...@linuxfoundation.org]
Sent: Donnerstag, 8. September 2016 07:14
To: Daniel Smith 
Cc: Christopher Price ; Dave Neary ; 
Frank Brockners (fbrockne) ; SULLIVAN, BRYAN L 
; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Following up on Project Health metrics 
discussion

All,

Glad to see the thread coming back to life (plus comments on the wiki) :-) 
Definitely understand concerns about the composite score.  Maybe another option 
would be to start by looking at 4 areas (git, Jira, wiki, etc.) individually.

I also want to suggest that if a project is active (and even if most of the 
work is being done upstream) I doubt the activities in OPNFV repo or other 
tools would be zero over a period of 3-6 months.  So I think having a regular 
metrics (composite or otherwise) would be helpful in identifying projects that 
are either in need of help or are candidates for "archiving"

My 2 cents

Ray

On Wed, Sep 7, 2016 at 9:42 PM, Daniel Smith 
> wrote:
Hello All.

My take on this and sorry maybe a bit blunt, but I don’t see what the purpose 
is here?

While guideline, guidance and such are good things, the discussion below seems 
awfully heavy and very boxed in.

As Chris in the evaluation on how to improve the community, I am not sure how 
we could ever resolve what one person thinks is an adequate measure of 
something over another (i.e endless debate), since metrics, improvements - 
unless we are talking about something quantifiable - and that would mean taking 
this to code optimization level ultimately - are subjective based and 
implement/reaction based measured over time in the case of adjustment.

As well +1 to doing our own assessments - since it should be us that outlines 
what we want to say about how we feel we have improved, and this only makes 
sense I would think as we are the only ones who have the context to see where 
we came from to where we are and what we are talking about doing next.

I would say however, that I am really concerned at that level of discussion 
across all meetings on project handling and process and such - release and 
otherwise - while this shows we are active and "moving" sure - there is a lot 
of dissonance in the communication, mixed messages and again, lots of 
information overflow.   I would like to see the "Operational" parts of OPNFV 
(Release Project, INFRA, TSC) focus more on how we support the projects in 
terms of day to day pain points - that is a solid, referable release process, a 
solid, regularly maintained method of publish,  a solid Change process (for 
anything) that ensures that we don’t discuss and move from one week to another 
- not because an idea is good or bad, but simply cause we need to recognize 
that there are more than the 25 or so regular attendees in the groups / this 
mailing list.

Would there be a market for such publishing outside our domain I would wonder?  
For Code stats and fun numbers those are nice to have, but a qualitative review 
of how we have improved our processes as a community, im not sure?  I would 
vouchsafe that our work in the projects themselves are what OPNFV is pushing 
out, the operational aspects of "how we are doing things" - while nice to 
outline, against the backdrop of every growing laundry list of things to 
"Decide" is really not high on a list?I didn’t understand from below the 
"why" and "who" for this fully.

Cheers and thank you
D

-Original Message-
From: 
opnfv-tech-discuss-boun...@lists.opnfv.org

[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org]
 On Behalf Of Christopher Price
Sent: Wednesday, September 07, 2016 9:20 PM
To: Dave Neary >; Frank Brockners 
(fbrockne) >; SULLIVAN, BRYAN L 
>; Raymond Paik 
>; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Following up on Project Health metrics 
discussion

Good comments Dave and everyone, I’d like to share my take on it is this.

I don’t see any problem in looking at the metrics we already publish and using 
them to help us create a better understanding across our community on how we go 
about getting things done.  (Maybe also helping find ways of improving 
ourselves.)

As was mentioned we publish all these metrics today.  I would prefer to see the 
OPNFV community drawing

Re: [opnfv-tech-discuss] Failing floating IP in Boron

2016-09-08 Thread Paraskevopoulos Georgios

I tested today autorelease 1477 manually and I confirm that SSH via floating 
IPs works. 
Link: 
https://nexus.opendaylight.org/content/repositories/autorelease-1477/org/opendaylight/integration/distribution-karaf/0.5.0-Boron/

BR,
George Paraskevopoulos

-Original Message-
From: Tim Rozet [mailto:tro...@redhat.com] 
Sent: Wednesday, September 07, 2016 9:03 PM
To: TECH-DISCUSS OPNFV; Brady Allen Johnson; Jose Lausuch; Georgios 
Paraskevopoulos (geo...@intracom-telecom.com); Sam Hague
Subject: [SFC] [FUNCTEST] Failing floating IP in Boron

Hi,
I pulled the Apex build from last night, and it looks like the problem (as 
previously thought) is fixed in RC2.  Our build last night included an 
autorelease RC2 build, and I can ssh into cirros instances via floating IP.  
Our daily has not made it to the SFC deployment yet, but I expect functest 
vping ssh to pass.  Let's wait and see...

Tim Rozet
Red Hat SDN Team




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

Re: [opnfv-tech-discuss] [multisite]Weekly meeting of Sept.8

2016-09-08 Thread Dimitri Mazmanov

Thanks to Fatih the node is back. Currently a build is in progress. So far the 
installation job has passed successfully.
-
Dimitri

From: joehuang 
Date: Wednesday 7 September 2016 at 10:38
To: Dimitri Mazmanov , 
"ashishsingh...@gmail.com" , "zhipengh...@gmail.com" 
, "Sama, Malla Reddy" , Meimei 
, "caizhiyuan (A)" , 
"opnfv-tech-discuss@lists.opnfv.org" 
Subject: [opnfv-tech-discuss] [multisite]Weekly meeting of Sept.8

Hello, team,



Last week, some topics to be worked in D-release were discussed, let's discuss 
more on these topics


Agenda of Sept.8 2016
•   Next step for Multisite project, scope, focus, etc

IRC: http://webchat.freenode.net/?channels=opnfv-meeting  7:00-8:00 UTC (During 
summer time, means CET 9:00 AM).

if you would like to discuss other topics in the weekly meeting, please reply 
in this mail.

Best Regards
Chaoyi Huang ( joehuang )


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of joehuang 
[joehu...@huawei.com]
Sent: 01 September 2016 16:13
To: Dimitri Mazmanov; ashishsingh...@gmail.com; zhipengh...@gmail.com; Sama, 
Malla Reddy; Meimei; caizhiyuan (A); opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [multisite]Weekly meeting minutes of Sept.1

Sept.1 2016: Agenda & Minutes
· Agenda

· Next step for Multisite project, scope, focus, etc
· Minutes
· 1)KB CLI 
(joehuang,
 07:26:12)
· 2)KB SDK 
(joehuang,
 07:26:21)
· 3)Resources Sync 
(joehuang,
 07:26:37)
· 3.1)SEG 
(joehuang,
 07:27:36)
· 3.2)FLAVOR 
(joehuang,
 07:27:54)
· 3.3)SSH KEY 
(joehuang,
 07:28:08)
· Revisit Geographical Redundancy
· 4)cross neutron networking automation 
(joehuang,
 07:28:31)
· 5) installation cooperation 
(joehuang,
 07:32:18)
· Link
· Minutes:  
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-09-01-07.06.html
· Minutes (text): 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-09-01-07.06.txt
· Log: 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-09-01-07.06.log.html


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of joehuang 
[joehu...@huawei.com]
Sent: 31 August 2016 17:32
To: Dimitri Mazmanov; ashishsingh...@gmail.com; zhipengh...@gmail.com; Sama, 
Malla Reddy; Meimei; caizhiyuan (A); opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [multisite]Weekly meeting of Sept.1
Hello, team,



Thanks to all of us, the functest in CI job can work successfully now. 
Congratulation!


Agenda of Aug.31 2016
•   Next step for Multisite project, scope, focus, etc

IRC: http://webchat.freenode.net/?channels=opnfv-meeting  7:00-8:00 UTC (During 
summer time, means CET 9:00 AM).

if you would like to discuss other topics in the weekly meeting, please reply 
in this mail.

Best Regards
Chaoyi Huang ( joehuang )



From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of joehuang 
[joehu...@huawei.com]
Sent: 24 August 2016 16:37
To: Dimitri Mazmanov; ashishsingh...@gmail.com; zhipengh...@gmail.com; Sama, 
Malla Reddy; Meimei; caizhiyuan (A); opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [multisite]Weekly meeting of Aug.25

Hello, team,


Agenda of Aug.25 2016
•   Unstable CI job running
•   Next step for Multisite project, scope, focus, etc


IRC: http://webchat.freenode.net/?channels=opnfv-meeting  7:00-8:00 UTC (During 
summer time, means CET 9:00 AM).

if you would like to discuss other topics in the weekly meeting, please reply 
in this mail.

Best Regards
Chaoyi Huang ( joehuang )

Re: [opnfv-tech-discuss] [Promise]Capacity Management User Story

2016-09-08 Thread Arturo Martin De Nicolas

Hi Madhu, Gerald, all.

Please, see some comments from my side.

Best regards,
Arturo



From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Kunzmann, 
Gerald
Sent: Friday, September 02, 2016 12:06 PM
To: Kashyap, Madhu; opnfv-tech-discuss@lists.opnfv.org
Cc: Souville, Bertrand; Thulasi, Arun; Gangur, Hrushikesh
Subject: Re: [opnfv-tech-discuss] [Promise]Capacity Management User Story

Hi Madhu, all,

Find attached a commented version of the user story. I believe we need to do 
further changes to make it read more like a user story instead of specific 
detailed requirements. I am not sure defining requirements would be accepted by 
the PWG.

Looking forward to your feedback.

Best regards,
Gerald

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Kashyap, Madhu
Sent: Donnerstag, 1. September 2016 20:19
To: opnfv-tech-discuss@lists.opnfv.org
Cc: Gangur, Hrushikesh ; Thulasi, Arun 

Subject: [opnfv-tech-discuss] [Promise]Capacity Management User Story

Hi,

As discussed during the call, attached is the capacity management user story 
with my edits. Please review and  provide comments. Also think about the 
granularity of the scope the reservation request.

Thanks
-Madhu


Capacity_Management_User_Story-MK-GK-AMN.docx
Description: Capacity_Management_User_Story-MK-GK-AMN.docx
___
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 September 8, 2016

2016-09-08 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 September 8, 2016

  *   Date and Time

 *   Thursday at 
0100-0200
 UTC, August 25, 2016
 *   Thursday at 0900-1000 Beijing, August 25, 2016
 *   Wednesday at 1800-1900 PDT, August 24, 2016

  *   Minutes

 *   Yang Yu

  *   Participants (4 peoples):

 *   Yang Yu
 *   Mingjiang Li
 *   Qi Liang
 *   Liang Gao
Agenda:

  *   Bottlenecks Colorado Discuss

 *   Colorado Release Report

*   Colorado Stable Branch
*   Release Meeting Report
*   AI from Testperf Meeting

 *   Bottlenecks Colorado Testing Framework (Rubbos example)

  *   The proposed Posca Test Suite in Bottlenecks (Draft)

 *   Goals and Scope (Draft)
 *   The Proposals (Draft)
 *   Metrics & Tools Discussion (Draft)
 *   Work Plan Discussion for the proposal (Draft)
 *   Test Results and Test Cases Discussion
Discussion & Action Item

1. Bottlenecks Colorado Discuss

  *   Hongbo is on an another meeting. So Yang is delegated to organize the 
discussion
  *   Yang mentions that the Colorado release will on September 22 and Project 
D release plan shall begin to be developed
  *   The Planned D release date is March 27 2017

 *   https://wiki.opnfv.org/display/SWREL/D-Release

  *   Yang reports the discussion from last Release meeting

 *   Minutes: 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-09-06-15.02.html
 *   Discussion Agenda for Release Meeting

*   Open Daylight
*   documentation
*   Colorado 2.0 and 3.0 planning
*   D Release planning

  *   Yang reports the discussion from last testperf meeting

 *   An action item is assigned to yang to cross review for testing project
 *   Minutes: 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-testperf/2016/opnfv-testperf.2016-09-01-14.00.html
 *   Discussion Agenda for Testperf Meeting

*   Question Fastdatatracks
*   Action point follow-up
*   Automatic reporting
*   Documentation
*   AoB

2. The proposed Posca Test Suite in Bottlenecks (Draft)

  *   Yang briefly introduces the proposal

 *   The proposal classifies the test cases and results into 5 categories. 
Then the results will be analyzed and bottlenecks will be searched among these 
categories.
 *   Goals of the proposals in Bottlenecks

*   Automatically locate the bottlenecks in a iterative manner
*   Automatically generate the testing report for bottlenecks in 
different categories
*   Implementing Automated Staging

 *   Scope of the proposals in Bottlenecks

*   Modeling, Testing and Test Result analysis
*   Parameters choosing and Algorithms

  *   Yang briefly go through the metrics/sets categories that will be needed 
in the proposal

 *   Some metrics are listed in the following web page

*   https://cloud.google.com/monitoring/api/metrics

 *   Some draft metrics set that are developed to find specific bottlenecks

*   Compute: Short of Processor
*   Network: bandwidth, latency and throughput
*   Storage: Short of Memory, memory leak, I/O

  *   Yang briefly go through tools categories that will be needed in the 
proposal

 *   Some tools are listed in the following web page

*   http://www.slac.stanford.edu/xorg/nmtf/nmtf-tools.html
*   
http://www.applicationperformancemanagement.org/network-monitoring/network-monitoring-tools/
*   A comparison of existing tools is also provided

  *   Yang introduces the proposed Posca (Parametric Bottlenecks Testing 
Catalogue) test suite

 *   Posca currently has 3 test stories

*   Facter Test: base test cases that Feature test and Optimization 
will be dependant
*   Feature Test: test cases for features/scenarios
*   Optimization Test: test to optimize the system parameter

  *   Yang explains about the work plan for the proposals

 *   Adding Posca testing suite to Bottlenecks projects

*   Jenkins job and proposed test suite
*   Code structure in the Bottlenecks repo

 *   Adding test case to Bottlenecks Project

*   System Bandwidth Bottleneck test case as the first step
*   Need to cooperate with yardstick with Restful API design

   *   Liang replies that yardstick has planned Restful API in D release



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

Re: [opnfv-tech-discuss] [doctor] For the issue about the notification time is large than 1S

[opnfv-tech-discuss] [dovetail]dovetail weekly meeting 9/9

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release] D-release schedule

[opnfv-tech-discuss] Does any one have updates for OPNFV VNFs avilable for on-boarding and testing

Re: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

[opnfv-tech-discuss] [multisite] Secgroup syncing Approach

[opnfv-tech-discuss] [multisite] Approach for Secgroup syncing

Re: [opnfv-tech-discuss] Following up on Project Health metrics discussion

Re: [opnfv-tech-discuss] Following up on Project Health metrics discussion

[opnfv-tech-discuss] [linuxfoundation.org #28648] Re: [linuxfoundation.org #28648] 答复: Re: [OPNFV Helpdesk #28648] AutoReply: [qtip] Nomination of Committer promotion for jiang.zhif...@zte.com.cn

Re: [opnfv-tech-discuss] [opnfv-mano-wg] Need Subscription list plus discussions for Sept 14 VNF onbaoarding & Mapping TOSCA service to NFV{VNFD+NSD}

[opnfv-tech-discuss] [Polestar] ODL Summit Bellevue F2F meeting

Re: [opnfv-tech-discuss] Following up on Project Health metrics discussion

Re: [opnfv-tech-discuss] Following up on Project Health metrics discussion

[opnfv-tech-discuss] [linuxfoundation.org #28648] 答复: Re: [OPNFV Helpdesk #28648] AutoReply: [qtip] Nomination of Committer promotion for jiang.zhif...@zte.com.cn

[opnfv-tech-discuss] 答复: Re: [OPNFV Helpdesk #28648] AutoReply: [qtip] Nomination of Committer promotion for jiang.zhif...@zte.com.cn

Re: [opnfv-tech-discuss] Following up on Project Health metrics discussion

Re: [opnfv-tech-discuss] Failing floating IP in Boron

Re: [opnfv-tech-discuss] [multisite]Weekly meeting of Sept.8

Re: [opnfv-tech-discuss] [Promise]Capacity Management User Story

[opnfv-tech-discuss] [Bottlenecks] Minutes of Bottlenecks Discussion on September 8, 2016

21 matches

Site Navigation

Mail list logo

Footer information