VPP/Meeting

From fd.io
< VPP
Revision as of 14:03, 11 May 2016 by Hagbard (Talk | contribs)

Jump to: navigation, search

Meeting Details

Weekly on Tuesday from 8-9am PST. WebEx Link

Meeting number: 	207 546 363 
Meeting password:	cVt69ppV

Join by phone
+1-408-525-6800 Call-in toll number (US/Canada)
+1-866-432-9903 Call-in toll-free number (US/Canada)
Access code: 207 546 363
Numeric meeting password: 04537446

Global call-in numbers:
https://ciscosales.webex.com/ciscosales/globalcallin.php?serviceType=MC&ED=348266027&tollFree=1

Toll-free dialing restrictions: 
https://www.webex.com/pdf/tollfree_restrictions.pdf

Agenda

The next VPP meeting is scheduled for May 10, 2016 with the following agenda:

  • Agenda Additions
  • Reports from other fd.io projects
    • CSIT
    • Honeycomb
    • NSH / SFC
    • ONE-LISP
    • Sandbox
  • VPP release 16.06 planning
    • see [16.06 release plan]
    • packaging updates (CJ Collier, Tom Herbert, Ed Warnicke)
    • Until we pull the RC0 throttle: committers, please do not merge change-sets with large blast radii. If in doubt, ask for a recorded vote of all committers.
    • Remaining pre-RC0 commits
      • NSH refactoring patch [move code from vnet to plugin]
      • Bugfixes
      • Others?
  • JIRA walkthrough
    • Can we install the MediaWiki Jira plugin?
    • Setting the "resolution" field
    • Bug scrub:
      • Hate bug scrubs
      • We need to clean up multiple completed issues
      • Decide which remaining issues must be addressed in r16.06
  • Code Base activity report - 23 merged (down from 50+ last week) - highlights
    • A dozen bugfixes
    • Ipv6-IOAM proof-of-work
  • Consumability
    • Switched tarball download to fd.io Nexus. Any problems?
    • Moderate to severe verify job issues: switch from openjdk-7 to openjdk-8, calmed down now
    • Other issues getting in the way?
  • Tech topics:
    • Plugin Signing
      • RSA-encrypted SHA256 signature draft.
      • What's the right way to manage certificates and/or keychain APIs to acquire a set of public keys of the form shown below?
/* 
 * Extract these bits from a .pem file as follows:
 * 
 * openssl rsa -in <mykeys.pem> -out <textfile> -pubout -modulus -text
 * 
 * pubkey_N shows up in <textfile> as "Modulus=<long-hex-string>",
 * right before -----BEGIN PUBLIC KEY-----
 *
 * pubkey_E shows up as "publicExponent: <decimal>(<hex>)", right
 * after the (private) key modulus. Seems to be constant, 0x10001.
 */
static const char *pubkey_N = "DEADBEEFFEEDFACE blah blah blah";  
static const char *pubkey_E = "010001";
    • API trace replay fast restart

Meeting Minutes

2016-05-10

2016-05-03

2016-04-26

2016-04-19

Note meeting ended on 2016-04-26 on IRC

2016-04-12

2016-04-05

  • Meeting cancelled due to Training/Hackfest

2016-03-22

2016-03-15

2016-03-08

2016-03-01

2016-02-23

2016-02-16