Re: [opnfv-tech-discuss] [Edge] Call to discuss next steps for Edge project proposal

[Zhipeng Huang]

We just established a new project called Cyborg[0] in OpenStack and we will
also be engaging kubernetes resources mgmt WG, with the focus on
acceleration management[1] which I would assume be very important for edge
case.

I would like to participate in the Edge project discussion on behalf of the
team and  try our best to accommodate any contribution necessary for F
release.

[0]: https://review.openstack.org/#/c/504940/
[1]: https://wiki.openstack.org/wiki/Cyborg



On Oct 5, 2017 3:48 AM, "Cooper, Trevor"  wrote:

> What do you think about using the Plugfest in December to focus activity
> on this? I think Intel can provide a POD in the OPNFV lab to work on it
> that would be physically accessible during the Plugfest.
>
>
>
> /Trevor
>
>
>
>
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *SULLIVAN,
> BRYAN L (BRYAN L)
> *Sent:* Wednesday, August 09, 2017 8:17 AM
> *To:* Pasi Vaananen ; Christopher Price <
> christopher.pr...@ericsson.com>; Stephen Wong ;
> Joel Halpern ; Timon Sloane <
> ti...@opennetworking.org>
> *Cc:* 'opnfv-tech-discuss@lists.opnfv.org'  opnfv.org>
> *Subject:* [opnfv-tech-discuss] [Edge] Call to discuss next steps for
> Edge project proposal
>
>
>
> Hi all,
>
>
>
> As those who expressed interest in the Edge project proposal
> https://wiki.opnfv.org/display/PROJ/Multi-Access+Edge I’d like to get us
> together with anyone else with interest in the project, to start planning
> OPNFV F release participation (with TSC approval of the project first of
> course).
>
>
>
> Poll for meeting times: https://beta.doodle.com/poll/imqnb8cbm6zan9ia
>
>
>
> It was mentioned on the OPNFV Marketing call today that the Marketing team
> plans to re-use the Beijing VCO demo content for further marketing of the
> concept. I commented that since we have the Edge project proposal on the
> table, I would recommend that the OPNFV technical community have a central
> role in the planning for future demos, e.g. through the Edge project. So we
> can use this call also to talk about next demo plans, and other things e.g.
> could we have anything ready for the December plugfest.
>
>
>
> Thanks,
>
> Bryan Sullivan | AT
>
>
>
> ___
> 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

[opnfv-tech-discuss] Canceled: [armband] Weekly Meetings Established for ARMBand project

[Bob Monkman]

BEGIN:VCALENDAR
METHOD:CANCEL
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=Bob Monkman:MAILTO:bob.monk...@arm.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Trevor Tao
 :MAILTO:trevor@arm.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=jcm@redhat
 .com:MAILTO:j...@redhat.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=ewahlig@qt
 i.qualcomm.com:MAILTO:ewah...@qti.qualcomm.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Shai Tsur:
 MAILTO:shai.t...@arm.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andy Wang:
 MAILTO:andy.w...@arm.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Ajanovic, 
 Jasmin":MAILTO:jas...@qti.qualcomm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Tim Dalton
 :MAILTO:t.dal...@kyrio.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lawrence L
 amers:MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Winn, Sean"
 :MAILTO:sean.w...@emc.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Beierl, Ma
 rk":MAILTO:mark.bei...@emc.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Rai, Shamb
 hu":MAILTO:s...@sonusnet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Dan Wester
 berg:MAILTO:dan.westerb...@enea.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ola Liljed
 ahl:MAILTO:ola.liljed...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Brian Broo
 ks:MAILTO:brian.bro...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Shobhan Ay
 yadevaraSesha (sayyadev):MAILTO:sayya...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Mishael We
 xler:MAILTO:mishael.wex...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Rooke, Mic
 hael (Nokia - FI/Espoo)":MAILTO:michael.ro...@nokia.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Kris Purce
 ll:MAILTO:kpurc...@apm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=邓灵莉/
 Lingli Deng:MAILTO:denglin...@chinamobile.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Liu, Kin-Y
 ip":MAILTO:kin-yip@caviumnetworks.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Liu, Kin-Y
 ip":MAILTO:kin-yip@cavium.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Peter Lawt
 hers (plawth...@apm.com):MAILTO:plawth...@apm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Cristina P
 auna:MAILTO:cristina.pa...@enea.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=Nicolas BO
 UTHORS:MAILTO:nicolas.bouth...@qosmos.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Thomas Lun
 dström:MAILTO:thomas.lundst...@enea.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alexandru 
 Nemes:MAILTO:alexandru.ne...@enea.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Charalampo
 s Kominos:MAILTO:charalampos.komi...@enea.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Bharat Bhu
 shan:MAILTO:bharat.bhus...@nxp.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=James Buch
 anan:MAILTO:jbucha...@advaoptical.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Cathy Zhan
 g:MAILTO:cathy.h.zh...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Trinath So
 manchi:MAILTO:trinath.soman...@nxp.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Marco Varl
 ese:MAILTO:marco.varl...@suse.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Vei
 tch:MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Gabor Hal
 ász:MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Masood Ul 
 Amin:MAILTO:masood.a...@aricent.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alan McNam
 ee:MAILTO:alan...@openet.com

[opnfv-tech-discuss] [dovetail] Dovetail weekly call on 10/6 CANCELLED

[Wenjing Chu]

Hi Dovetailers

Due to holidays for many Dovetail contributors, this Friday's call is cancelled.

Thanks.

Wenjing

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

Re: [opnfv-tech-discuss] [release] improving branch process

[Trevor Bramwell]

Hi David,

On Wed, Oct 04, 2017 at 01:44:38PM -0700, David McBride wrote:
> Here's what (I think) I know about what must be done when we branch.
> Please correct and fill in the details, including who owns the task.  Also,
> please comment on whether a task can be done in advance of branching.
> 
>1. Update docker yaml file
>2. Enable testing (RELENG repo)
>3. Create Jenkins jobs for branch for each installer

To clarify Jenkins jobs need to be made for all projects not just
installers.

Creating the branch specific Jenkins jobs is owned by Releng and this is
the specific activity I mentioned could be automated before the branch
is made. 

>4. Update the test results dashboard
> 
> I think that we can shave at least a week off of this process.  That, in
> combination with pulling MS7 in by a week should give our team sufficient
> time to complete the release.  I appreciate your input.
> 
> David
> 
> -- 
> *David McBride*
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride


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

[opnfv-tech-discuss] [release] improving branch process

[David McBride]

Team,

This will be a topic at our upcoming plugfest (Dec 4 - 8), but I'd like to
start the discussion now with the goal of having a draft proposal that we
can review and finalize at plugfest.  We can discuss this on the mailing
list and I will also devote some time to it during the weekly release call.

In both the Danube and Euphrates releases, the process of enabling CI and
test on the branch has taken as long as two weeks to complete, following
MS7.  As a result, we are left with just a few days to fix remaining bugs
and finalize the scenarios prior to the release date.

Therefore, as a starting point, I'd like to propose the following:

   1. Reduce the branch window from 2 weeks to 1 week, thereby pulling in
   MS7 by one week.
   2. Trevor B has told me that many of the activities that, in the past,
   we've waited until MS7 to complete, could actually be done *before*
   MS7.  So, let's address the following:
  - What activities must be performed when we branch (detailed
  description), such that we have builds, testing, and the test results
  dashboard operational on the branch?
  - Do each of those activities have an owner?
  - Which of these activities could be performed prior to MS7?

I'd like to set a goal of having builds, test, and test results dashboard
operational on the branch within 3 business days following the branch.
That is, if the branch occurs on a Friday, then we are operational on the
branch by COB on the following Wednesday.

Here's what (I think) I know about what must be done when we branch.
Please correct and fill in the details, including who owns the task.  Also,
please comment on whether a task can be done in advance of branching.

   1. Update docker yaml file
   2. Enable testing (RELENG repo)
   3. Create Jenkins jobs for branch for each installer
   4. Update the test results dashboard

I think that we can shave at least a week off of this process.  That, in
combination with pulling MS7 in by a week should give our team sufficient
time to complete the release.  I appreciate your input.

David

-- 
*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

Re: [opnfv-tech-discuss] [Edge] Call to discuss next steps for Edge project proposal

[Cooper, Trevor]

What do you think about using the Plugfest in December to focus activity on 
this? I think Intel can provide a POD in the OPNFV lab to work on it that would 
be physically accessible during the Plugfest.

/Trevor



From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, 
BRYAN L (BRYAN L)
Sent: Wednesday, August 09, 2017 8:17 AM
To: Pasi Vaananen ; Christopher Price 
; Stephen Wong ; Joel 
Halpern ; Timon Sloane 
Cc: 'opnfv-tech-discuss@lists.opnfv.org' 
Subject: [opnfv-tech-discuss] [Edge] Call to discuss next steps for Edge 
project proposal

Hi all,

As those who expressed interest in the Edge project proposal 
https://wiki.opnfv.org/display/PROJ/Multi-Access+Edge I'd like to get us 
together with anyone else with interest in the project, to start planning OPNFV 
F release participation (with TSC approval of the project first of course).

Poll for meeting times: https://beta.doodle.com/poll/imqnb8cbm6zan9ia

It was mentioned on the OPNFV Marketing call today that the Marketing team 
plans to re-use the Beijing VCO demo content for further marketing of the 
concept. I commented that since we have the Edge project proposal on the table, 
I would recommend that the OPNFV technical community have a central role in the 
planning for future demos, e.g. through the Edge project. So we can use this 
call also to talk about next demo plans, and other things e.g. could we have 
anything ready for the December plugfest.

Thanks,
Bryan Sullivan | AT

___
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-tsc] [release][euphrates] proposal to eliminate one of the two point releases for Euphrates

[Wenjing Chu]

+1

Wenjing

From: opnfv-tsc-boun...@lists.opnfv.org 
[mailto:opnfv-tsc-boun...@lists.opnfv.org] On Behalf Of David McBride
Sent: Wednesday, October 04, 2017 11:44 AM
To: TECH-DISCUSS OPNFV 
Cc: opnfv-project-leads ; TSC OPNFV 

Subject: [opnfv-tsc] [release][euphrates] proposal to eliminate one of the two 
point releases for Euphrates

Team,

Please respond to this mail with (+1, 0, -1) and your thoughts, suggestions, or 
alternatives.

During the TSC call on Tues, Oct 3, the TSC agreed to slip the initial 
Euphrates release (5.0) to October 20.  In addition, I also proposed 
eliminating one of the two point releases (5.1, 5.2) planned for Euphrates.  
The reasoning was as follows:

  1.  Moving the 5.0 release to Oct 20 places that release just 3 weeks before 
the planned release of 5.1 (Nov 10).
  2.  Slipping 5.1 and 5.2 could have negative consequences for the OPNFV "F" 
release, as happened with Euphrates when we decided to slip Danube 3.0.
Therefore, the proposal is to eliminate the planned release on Nov 10, so that 
there would just be one point release on Dec 15.

The proposal is described in more detail in the slide deck that I presented 
during the TSC 
meeting (see 
link labeled "euphrates contingency.pptx" under the heading "Euphrates update").

David

--
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] Cancelled - Technical Discussion this Week Oct 5

[HU, BIN]

Hello community,

Looks like there is no topic to discuss this week Oct 5 tomorrow. Thus I 
proposed to cancel our meeting tomorrow.

Thanks
Bin

From: HU, BIN
Sent: Monday, October 02, 2017 3:55 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: Agenda Items/Topics for Technical Discussion this Week Oct 5

Hello community,

Please let me know if you have any proposal/topics to discussion this Thursday 
Oct 5.

Thanks
Bin

___
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][euphrates] proposal to eliminate one of the two point releases for Euphrates

[HU, BIN]

+1

From: opnfv-project-leads-boun...@lists.opnfv.org 
[mailto:opnfv-project-leads-boun...@lists.opnfv.org] On Behalf Of David McBride
Sent: Wednesday, October 04, 2017 11:44 AM
To: TECH-DISCUSS OPNFV 
Cc: opnfv-project-leads ; TSC OPNFV 
; Raymond Paik ; Tapio 
Tallgren 
Subject: [opnfv-project-leads] [release][euphrates] proposal to eliminate one 
of the two point releases for Euphrates

Team,

Please respond to this mail with (+1, 0, -1) and your thoughts, suggestions, or 
alternatives.

During the TSC call on Tues, Oct 3, the TSC agreed to slip the initial 
Euphrates release (5.0) to October 20.  In addition, I also proposed 
eliminating one of the two point releases (5.1, 5.2) planned for Euphrates.  
The reasoning was as follows:

  1.  Moving the 5.0 release to Oct 20 places that release just 3 weeks before 
the planned release of 5.1 (Nov 10).
  2.  Slipping 5.1 and 5.2 could have negative consequences for the OPNFV "F" 
release, as happened with Euphrates when we decided to slip Danube 3.0.
Therefore, the proposal is to eliminate the planned release on Nov 10, so that 
there would just be one point release on Dec 15.

The proposal is described in more detail in the slide deck that I presented 
during the TSC 
meeting
 (see link labeled "euphrates contingency.pptx" under the heading "Euphrates 
update").

David

--
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

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][euphrates] proposal to eliminate one of the two point releases for Euphrates

[Jose Lausuch]

+1

Regards,
Jose





> On 04 Oct 2017, at 20:46, Beierl, Mark  wrote:
> 
> +1
> 
> Regards,
> Mark
> 
> Mark Beierl
> SW System Sr Principal Engineer
> Dell EMC | Office of the CTO
> mobile +1 613 314 8106 
> mark.bei...@dell.com 
>> On Oct 4, 2017, at 14:44, David McBride > > wrote:
>> 
>> Team,
>> 
>> Please respond to this mail with (+1, 0, -1) and your thoughts, suggestions, 
>> or alternatives.  
>> 
>> During the TSC call on Tues, Oct 3, the TSC agreed to slip the initial 
>> Euphrates release (5.0) to October 20.  In addition, I also proposed 
>> eliminating one of the two point releases (5.1, 5.2) planned for Euphrates.  
>> The reasoning was as follows:
>> Moving the 5.0 release to Oct 20 places that release just 3 weeks before the 
>> planned release of 5.1 (Nov 10).
>> Slipping 5.1 and 5.2 could have negative consequences for the OPNFV "F" 
>> release, as happened with Euphrates when we decided to slip Danube 3.0.
>> Therefore, the proposal is to eliminate the planned release on Nov 10, so 
>> that there would just be one point release on Dec 15.  
>> 
>> The proposal is described in more detail in the slide deck that I presented 
>> during the TSC meeting 
>>  (see link 
>> labeled "euphrates contingency.pptx" under the heading "Euphrates update").
>> 
>> 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 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][euphrates] proposal to eliminate one of the two point releases for Euphrates

[Beierl, Mark]

+1

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

On Oct 4, 2017, at 14:44, David McBride 
> wrote:

Team,

Please respond to this mail with (+1, 0, -1) and your thoughts, suggestions, or 
alternatives.

During the TSC call on Tues, Oct 3, the TSC agreed to slip the initial 
Euphrates release (5.0) to October 20.  In addition, I also proposed 
eliminating one of the two point releases (5.1, 5.2) planned for Euphrates.  
The reasoning was as follows:

  1.  Moving the 5.0 release to Oct 20 places that release just 3 weeks before 
the planned release of 5.1 (Nov 10).
  2.  Slipping 5.1 and 5.2 could have negative consequences for the OPNFV "F" 
release, as happened with Euphrates when we decided to slip Danube 3.0.

Therefore, the proposal is to eliminate the planned release on Nov 10, so that 
there would just be one point release on Dec 15.

The proposal is described in more detail in the slide deck that I presented 
during the TSC 
meeting (see 
link labeled "euphrates contingency.pptx" under the heading "Euphrates update").

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] [release][euphrates] proposal to eliminate one of the two point releases for Euphrates

[David McBride]

Team,

Please respond to this mail with (+1, 0, -1) and your thoughts,
suggestions, or alternatives.

During the TSC call on Tues, Oct 3, the TSC agreed to slip the initial
Euphrates release (5.0) to October 20.  In addition, I also proposed
eliminating one of the two point releases (5.1, 5.2) planned for
Euphrates.  The reasoning was as follows:

   1. Moving the 5.0 release to Oct 20 places that release just 3 weeks
   before the planned release of 5.1 (Nov 10).
   2. Slipping 5.1 and 5.2 could have negative consequences for the OPNFV
   "F" release, as happened with Euphrates when we decided to slip Danube 3.0.

Therefore, the proposal is to eliminate the planned release on Nov 10, so
that there would just be one point release on Dec 15.

The proposal is described in more detail in the slide deck that I presented
during the TSC meeting
 (see link
labeled "euphrates contingency.pptx" under the heading "Euphrates update").

David

-- 
*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

Re: [opnfv-tech-discuss] [infra-wg] Scheduling Infra Updates

[Raymond Paik]

All,

Again, these are just system updates and there will be no updates to the
applications (Gerrit, Jira, Confluence, Etherpad).  As Trevor noted,
Jenkins will not be impacted.

The reboot should take less than 30 minutes.  If there are no objections to
this maintenance window by Noon Pacific Time on Friday (October 6th), the
work will be done on Sunday (October 8th).

Thanks,

Ray

On Tue, Oct 3, 2017 at 6:51 AM, Trevor Bramwell <
tbramw...@linuxfoundation.org> wrote:

> Hi All,
>
> (Including Tech-Discuss in the discussion.)
>
> Given the delay in the release I'd like to propose these updates happen
> this weekend on the 8th.
>
> Regards,
> Trevor Bramwell
>
> On Mon, Oct 02, 2017 at 12:35:46PM -0700, Trevor Bramwell wrote:
> > Hey All,
> >
> > Since I didn't get a chance to bring this up at the Infra-WG call today,
> > I'd like to discuss it here.
> >
> > There are some pending system updates we'd like to apply to the
> > following managed systems, which will require a reboot due to kernel
> > updates:
> >
> >  * Gerrit (gerrit.opnfv.org)
> >  * JIRA (jira.opnfv.org)
> >  * Confluence (wiki.opnfv.org)
> >  * Etherpad (etherpad.opnfv.org)
> >
> > These updates do NOT include Jenkins (build.opnfv.org).
> >
> > Since we're obviously very close to a release these updates should wait
> > until there's some breathing room.
> >
> > My current thought is Saturday, October 14th may work well. Are there
> > any other suggestions for dates when these updates could happen, or any
> > concerns with scheduling these for the 14th?
> >
> > Regards,
> > Trevor Bramwell
>
>
> ___
> infra-wg mailing list
> infra...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/infra-wg
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [release][euphrates] release date for OPNFV Euphrates moved to October 20

[David McBride]

Team,

On Tuesday, October 3, the TSC approved slipping the release date for OPNFV
Euphrates by 2 weeks to October 20.  The schedule
 has been updated to
reflect this change.

There was also a discussion about eliminating one of the two point releases
planned after the initial release of Euphrates.  The TSC agreed to continue
this discussion on the mailing list.  Look for a separate email with this
topic.

Let me know if you have any questions.

David

-- 
*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] [mano-wg] Summary of Meeting #48 September Report and Best practices

[prakash RAMCHANDRAN via opnfv-tech-discuss]

Hi all,
Here is the link to summary of todays irc only discussions. 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-10-04-14.05.txt

We would like to close Release-E with evolving Best Practices with a White 
paper from OPNFV mano-wg and like any suggestions from community is welcome. 
Have an action to post template for white paper on wiki and will follow up on 
that soon.
We need to let new incoming TSC decide on plans for what should be done to deal 
with dwindling interest in OPNFV mano as one more of participating project 
Domino is dropping out. We will discuss this in next irc only meeting once we 
have new TSC team start transition next Tuesday.

ThanksPrakash



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

[opnfv-tech-discuss] MoMs SFC weekly meeting

[Manuel Buil]

Hi,

These are the MoMs of this week's meeting:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2017/opnfv-sfc.
2017-10-04-14.00.html

Regards,
Manuel___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Canceled: opnfvdocs project meeting

[Sofia Wallin]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Sofia Wallin:MAILTO:sofia.wal...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV (opnfv-tech-discuss@lists.opnfv.org):MAILTO:opnfv-tech-discuss@li
 sts.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Vul, Alex":
 MAILTO:alex@intel.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=Shobhan Ay
 yadevaraSesha (sayyadev):MAILTO:sayya...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lawrence L
 amers:MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Maria Toer
 oe:MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alan McNam
 ee:MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Bernier, D
 aniel":MAILTO:daniel.bern...@bell.ca
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Donald Hun
 ter (donaldh):MAILTO:dona...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Gabor Hal
 ász:MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Seiler, Gl
 enn":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ahmed Elbo
 rnou (amaged):MAILTO:ama...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Canio Cill
 is:MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Vei
 tch:MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Marco Varl
 ese:MAILTO:marco.varl...@suse.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Aron Wahl:
 MAILTO:a.w...@f5.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Piyush Sar
 wal:MAILTO:psar...@us.ibm.com
DESCRIPTION;LANGUAGE=en-GB:Nothing on the agenda for today.\n\n
 \n\nWelcome to join the opnfvdocs meeting.\n\nIntentio
 n is to cover:\nProject backlog and progress\nQuestions and issues\nImprov
 ements and ideas\n\n\nPlease join my meeting from your computer\, tablet o
 r smartphone.\nhttps://global.gotomeeting.com/join/819733085\nYou can also
  dial in using your phone.\nUnited States +1 (312) 757-3126\nAccess Code: 
 819-733-085\nMore phone numbers\nAustralia +61 2 8355 1040\nAustria +43 7 
 2088 0034\nBelgium +32 (0) 28 93 7018\nCanada +1 (647) 497-9350\nDenmark +
 45 69 91 88 64\nFinland +358 (0) 923 17 0568\nFrance +33 (0) 170 950 592\n
 Germany +49 (0) 692 5736 7211\nIreland +353 (0) 15 360 728\nItaly +39 0 24
 7 92 13 01\nNetherlands +31 (0) 208 080 219\nNew Zealand +64 9 280 6302\nN
 orway +47 75 80 32 07\nSpain +34 911 82 9906\nSweden +46 (0) 853 527 836\n
 Switzerland +41 (0) 435 0167 13\nUnited Kingdom +44 (0) 330 221 0086\n\n
UID:A33628A4-F208-4CFB-8047-2C411E118F69
RECURRENCE-ID;TZID=W. Europe Standard Time:20171004T15
SUMMARY;LANGUAGE=en-GB:Canceled: [opnfv-tech-discuss] opnfvdocs project mee
 ting 
DTSTART;TZID=W. Europe Standard Time:20171004T15
DTEND;TZID=W. Europe Standard Time:20171004T154500
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20171004T101630Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:3
LOCATION;LANGUAGE=en-GB:https://global.gotomeeting.com/join/819733085 
X-MICROSOFT-CDO-APPT-SEQUENCE:3
X-MICROSOFT-CDO-OWNERAPPTID:2115450860
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
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] [opnfvdocs] Question on font size and page width

[Kunzmann, Gerald]

Hi Sofia,

thanks for the feedback and explanation. I will then merge the patch and check 
its result on docs.opnfv.org.

Best regards,
Gerald

From: Sofia Wallin [mailto:sofia.wal...@ericsson.com]
Sent: Dienstag, 3. Oktober 2017 17:47
To: SULLIVAN, BRYAN L (BRYAN L) ; Kunzmann, 
Gerald ; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [opnfvdocs] Question on font size and page 
width

Hi Bryan and Gerald,
The artifact urls doesn’t give you complete fair view of the rendering in 
comparison to the actual result on docs.opnfv.org.

We currently have the old toolchain running which give you a somewhat 
reasonable idea on the final result. This is unfortunately not possible to do 
with readthedocs since the builds are triggered when something is merged.
And that is why we have chosen to keep the artifact urls for now.

If you look at the Promise 
documentation
 for example on the docs.opnfv.org you can see that you have a different result.

Best regards,
Sofia

From: 
>
 on behalf of "SULLIVAN, BRYAN L (BRYAN L)" 
>
Date: Monday, 2 October 2017 at 18:03
To: Gerald Kunzmann 
>, OPNFV 
>
Subject: Re: [opnfv-tech-discuss] [opnfvdocs] Question on font size and page 
width

I agree, that for use on the web that the presentation should:
1)  use the full width of the screen
2)  offer the ability to specify column-width as in CSS (percent, or pixels)
3)  if possible offer the ability to minimize the navigation links on the 
left - that might be something we could also hack via CSS

Thanks,
Bryan Sullivan | AT

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Kunzmann, 
Gerald
Sent: Monday, October 02, 2017 8:37 AM
To: 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [opnfvdocs] Question on font size and page 
width

Dear Opnfvdocs-Team,

I have not received any feedback on this email, so I’d like to bring it up 
again.
How can I get a different rendering of the HTML page, e.g. similar to the one 
for Euphrates release docs: 
http://artifacts.opnfv.org/opnfvdocs/review/42243/index.html
 ?

Best regards,
Gerald

From: Kunzmann, Gerald
Sent: Freitag, 1. September 2017 13:43
To: 'opnfv-tech-discuss@lists.opnfv.org' 
>
Subject: [opnfvdocs] Question on font size and page width

Dear Opnfvdocs-Team,

I have created this table but I am quite unhappy about the narrow, and thus 
long, description column:
http://artifacts.opnfv.org/promise/review/40835/development_manuals/index.html

Is there a way to specify font size for specific tables or change page width 
for specific pages?

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

Managing Directors (Geschaeftsfuehrer):
Atsushi Takeshita, Takatoshi Okagawa, Dr. Thomas Walter, Hisahiro Hamahata, 
Takaaki Sato, Junichi Igarashi
Amtsgericht Müchen, HRB 132976

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

[opnfv-tech-discuss] [mano-wg] Meeting #48 Wednesday (IRC only) - Focus on September Report and E/F best practices

[prakash RAMCHANDRAN via opnfv-tech-discuss]

Oct  4, Wednesday : 14.00 UTC /7.00 PDT  Meeting #48

(IRC Only meeting, no GTM this & next week)

For IRC can use can use http://webchat.freenode.net/   

IRC#opnfv-mano
Hi all,Welcome to MANO WG IRC only meeting ...
1.Agenda Bashing
2. September Month end report and Actions from last week

3. Best practices that can be carried forward from E  to F and upstream (ONAP - 
VNF Model . Usecase def. )

4. White paper for on State of MANO in OPNFV? - Discussions on content and 
formats

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