openwhisk-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Rutkowski (Confluence)" <conflue...@apache.org>
Subject [CONF] OpenWhisk > 2017-08-16 OW Tech. Interchange - Meeting Notes
Date Wed, 16 Aug 2017 16:29:58 GMT
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> 
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0">

<base href="https://cwiki.apache.org/confluence"> 
<title>Message Title</title>  
<style type="text/css">@media only screen and (max-device-width: 480px) {.mobile-only
{
    width: auto !important;
    height: auto !important;
    overflow: visible !important;
    line-height: normal !important;
    font-size: inherit !important;
    mso-hide: all;
}

.desktop-only {
    display: none !important;
}

/* iPhone 3GS fix for unwanted 20px right margin */
body {
    min-width: 100% !important;
    padding: 0;
    margin: 0;
}

#center-content-table {
    max-width: none;
!important;
}

#header-pattern-container {
    padding: 10px 10px 10px 10px !important;
    line-height: 20px !important;
}

#header-avatar-image-container {
    padding-right: 8px !important;
}

#email-content-container {
    padding: 0 !important;
}

.mobile-expand {
    border-radius: 0 !important;
    border-left: 0 !important;
    border-right: 0 !important;
    padding-left: 26px !important;
}

.mobile-resize-text {
    font-size: 16px !important;
    line-height: 22px !important;
}

#page-title-pattern-header {
    font-size: 20px !important;
    line-height: 28px !important;
}

#page-title-pattern-icon-image-container-cell {
    padding-top: 7px !important;
}

#inline-user-pattern {
    display: block !important;
}

#inline-user-pattern-avatar {
    padding-top: 3px !important;
}

.contextual-area-pattern {
    border-bottom: 1px solid #ccc !important;
    padding: 15px 10px 0 10px !important;
}

.users-involved-pattern-column-table {
    width: 100% !important;
}

.users-involved-pattern-avatar-table-cell {
    padding: 3px 5px 5px 0 !important;
}

.users-involved-pattern-column-container {
    padding-right: 0 !important;
}

.contextual-excerpt-pattern, #users-involved-pattern {
    border: 0 !important;
}

/** Aui Typography upsized for mobile **/
#content-excerpt-pattern-container, #contextual-excerpt-pattern-text-container {
    font-size: 16px !important;
    line-height: 22px !important;
}

#content-excerpt-pattern-container h1, #contextual-excerpt-pattern-text-container h1 {
    font-size: 24px !important;
    line-height: 28px !important;
}

#content-excerpt-pattern-container h2, #contextual-excerpt-pattern-text-container h2 {
    font-size: 20px !important;
    line-height: 28px !important;
}

#content-excerpt-pattern-container h3, #contextual-excerpt-pattern-text-container h3 {
    font-size: 18px !important;
    line-height: 24px !important;
}

#content-excerpt-pattern-container h4, #contextual-excerpt-pattern-text-container h4 {
    font-size: 16px !important;
    line-height: 22px !important;
}

#content-excerpt-pattern-container h5, #contextual-excerpt-pattern-text-container h5 {
    font-size: 14px !important;
    line-height: 20px !important;
}

#content-excerpt-pattern-container h6, #contextual-excerpt-pattern-text-container h6 {
    font-size: 14px !important;
    line-height: 20px !important;
}

.user-mention {
    line-height: 18px !important;
}

/** Aui Typography end **/

/* Show appropriate footer logo on mobile, display links vertically */
#footer-pattern {
    padding: 15px 10px !important;
}

#footer-pattern-logo-desktop-container {
    padding: 0 !important;
}

#footer-pattern-logo-desktop {
    width: 0 !important;
    height: 0 !important;
}

#footer-pattern-logo-mobile {
    padding-top: 10px !important;
    width: 30px !important;
    height: 27px !important;
    display: inline !important;
}

#footer-pattern-text {
    display: block !important;
}

#footer-pattern-links-container {
    line-height: 0 !important;
}

.footer-pattern-links.mobile-resize-text,
.footer-pattern-links.mobile-resize-text,
#footer-pattern-text.mobile-resize-text,
#footer-pattern-links-container.no-footer-links {
    font-size: 14px !important;
    line-height: 20px !important;
}

.footer-link {
    display: block !important;
}

#footer-pattern-links-container table {
    display: inline-block !important;
    float: none !important;
}

#footer-pattern-links-container, #footer-pattern-text {
    text-align: center !important;
}

#footer-pattern-links {
    padding-bottom: 5px !important;
}

/** Team Calendar overrides, these should be removed when notifications are updated in Team
Calendars. For now CSS
    overrides are being used because the structure of the content can't change without rereleasing
the plugin */
.mail-calendar-container .day-header + table tr td:first-child {
    vertical-align: top !important;
    padding-top: 5px !important;
}}
@media (min-width: 900px) {#center-content-table { width: 900px; }}
@media all {#outlook a {
    padding: 0;
}

/* Force Outlook to provide a "view in browser" menu link. */
/* Prevent Webkit and Windows Mobile platforms from changing default font sizes.*/
body {
    -webkit-text-size-adjust: 100%;
    -ms-text-size-adjust: 100%;
}

.ExternalClass {
    width: 100%;
}

/* Force Hotmail to display emails at full width */
#background-table {
    margin: 0;
    padding: 0;
    width: 100% !important;
}

/* Needed to override highlighting on date and time links in iOS */
.grey a {
    color: #707070;
    text-decoration: none;
}/* These styles are appended to the head element of a notification in order to prevent Apple
Mail and similar
   clients from underlining the due dates with a blue hyperlink */
/* a lozenge outside an inline task should always be #333, lozenges inside an inline task
should be
   colored according to their upcoming due dates, a completed task date lozenge or deleted
task date
   lozenge should always be #707070 */
.date-time-lozenge a {color: #333333; text-decoration: none; }
.inline-task-text-container .date-time-lozenge.date-upcoming a {color: #DF6F00; text-decoration:
none; }
.inline-task-text-container .date-time-lozenge.date-past a {color: #D04437; text-decoration:
none; }
.inline-task-text-container.content-deleted-color .date-time-lozenge a,
.inline-task-text-container.checked .date-time-lozenge a {
    color: #707070; text-decoration: none;
}}
</style> 
</head>
<body>
<table id="background-table" cellpadding="0" cellspacing="0" width="100%" style="border-collapse:
collapse; mso-table-lspace: 0pt; mso-table-rspace: 0pt; color: #333; background-color: #f5f5f5">

<tbody> 
<tr> 
<td id="header-pattern-container" style="padding: 0px; border-collapse: collapse; padding:
10px 20px"> 
<table id="header-pattern" cellspacing="0" cellpadding="0" border="0" style="border-collapse:
collapse; mso-table-lspace: 0pt; mso-table-rspace: 0pt; color: #333"> 
<tbody> 
<tr> 
<td id="header-avatar-image-container" valign="top" style="padding: 0px; border-collapse:
collapse; vertical-align: top; width: 32px; padding-right: 9px"><a href="https://cwiki.apache.org/confluence/display/~mrutkows?src=mail&amp;src.mail.timestamp=1502900998287&amp;src.mail.notification=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification&amp;src.mail.recipient=8aa980875bf24635015c9267bc8e02f6"
style="color: #3b73af; text-decoration: none"><img id="header-avatar-image" class="image_fix"
src="cid:avatar_1c1ec99848547cb9f4e49b30ec5da36b" height="32" width="32" border="0" style="border-radius:
3px; vertical-align: top"></a></td>
<td id="header-text-container" valign="middle" style="padding: 0px; border-collapse: collapse;
vertical-align: middle; font-family: Arial, sans-serif; font-size: 14px; line-height: 20px;
mso-line-height-rule: exactly; mso-text-raise: 1px">Matt Rutkowski <strong>edited</strong>
a page</td> 
</tr> 
</tbody> 
</table> </td> 
</tr> 
<!-- End Header pattern --> 
<tr> 
<td id="email-content-container" style="padding: 0px; border-collapse: collapse; padding:
0 20px"> 
<table id="email-content-table" cellspacing="0" cellpadding="0" border="0" width="100%"
style="border-collapse: collapse; mso-table-lspace: 0pt; mso-table-rspace: 0pt; color: #333;
border-spacing: 0; border-collapse: separate"> 
<tbody> 
<tr> 
<td class="email-content-rounded-top mobile-expand" style="padding: 0px; border-collapse:
collapse; color: #fff; padding: 0 15px 0 16px; height: 15px; background-color: #fff; border-left:
1px solid #ccc; border-top: 1px solid #ccc; border-right: 1px solid #ccc; border-bottom: 0;
border-top-right-radius: 5px; border-top-left-radius: 5px">&nbsp;</td> 
</tr> 
<tr> 
<td class="email-content-main mobile-expand" style="padding: 0px; border-collapse: collapse;
border-left: 1px solid #ccc; border-right: 1px solid #ccc; border-top: 0; border-bottom: 0;
padding: 0 15px 15px 16px; background-color: #fff"> 
<table id="page-title-pattern" cellspacing="0" cellpadding="0" border="0" width="100%"
style="border-collapse: collapse; mso-table-lspace: 0pt; mso-table-rspace: 0pt; color: #333">

<tbody> 
<tr> 
<td id="page-title-pattern-icon-image-container" valign="top" style="padding: 0px; border-collapse:
collapse; width: 16px; vertical-align: top"> 
<table cellspacing="0" cellpadding="0" border="0" style="border-collapse: collapse; mso-table-lspace:
0pt; mso-table-rspace: 0pt; color: #333"> 
<tbody> 
<tr> 
<td id="page-title-pattern-icon-image-container-cell" style="padding: 0px; border-collapse:
collapse; width: 16px; padding: 9px 8px 0px 0px; mso-text-raise: 5px; mso-line-height-rule:
exactly"><a href="https://cwiki.apache.org/confluence/display/OPENWHISK/2017-08-16+OW+Tech.+Interchange+-+Meeting+Notes?src=mail&amp;src.mail.timestamp=1502900998287&amp;src.mail.notification=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification&amp;src.mail.recipient=8aa980875bf24635015c9267bc8e02f6&amp;src.mail.action=view"
title="page icon" style="vertical-align: top;; color: #3b73af; text-decoration: none"><img
style="vertical-align: top; display: block;" src="cid:page-icon" alt="page icon" title="page
icon" height="16" width="16" border="0"></a></td> 
</tr> 
</tbody> 
</table> </td>
<td style="vertical-align: top;; padding: 0px; border-collapse: collapse; padding-right:
5px; font-size: 20px; line-height: 30px; mso-line-height-rule: exactly" id="page-title-pattern-header-container"><span
id="page-title-pattern-header" style="font-family: Arial, sans-serif; padding: 0; font-size:
20px; line-height: 30px; mso-text-raise: 2px; mso-line-height-rule: exactly; vertical-align:
middle"><a href="https://cwiki.apache.org/confluence/display/OPENWHISK/2017-08-16+OW+Tech.+Interchange+-+Meeting+Notes?src=mail&amp;src.mail.timestamp=1502900998287&amp;src.mail.notification=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification&amp;src.mail.recipient=8aa980875bf24635015c9267bc8e02f6&amp;src.mail.action=view"
title="2017-08-16 OW Tech. Interchange - Meeting Notes" style="color: #3b73af; text-decoration:
none">2017-08-16 OW Tech. Interchange - Meeting Notes</a></span></td>

</tr> 
</tbody> 
</table> </td> 
</tr> 
<tr> 
<td class="email-content-main mobile-expand" style="padding: 0px; border-collapse: collapse;
border-left: 1px solid #ccc; border-right: 1px solid #ccc; border-top: 0; border-bottom: 0;
padding: 0 15px 15px 16px; background-color: #fff"> 
<table class="content-excerpt-pattern" cellspacing="0" cellpadding="0" border="0" width="100%"
style="border-collapse: collapse; mso-table-lspace: 0pt; mso-table-rspace: 0pt; color: #333;
font-family: Arial, sans-serif; font-size: 14px; line-height: 20px; mso-line-height-rule:
exactly; mso-text-raise: 1px"> 
<tbody> 
<tr> 
<td class="content-excerpt-pattern-container mobile-resize-text " style="padding: 0px;
border-collapse: collapse; padding: 0 0 0 24px"> 
<div> 
<span style="text-decoration: underline;">Attendees:</span> Matt Rutkowski, Rob
Allen, Tyson, Rodric, Lorna Mitchell, Vadim, James Thomas, Duy Nguyen, Markus, posada, Mark
Peek, Dragos, Carlos, Daisy, Berndt Jung, Kavitha, 
</div> 
<div> 
<span style="text-decoration: underline;">Meeting Notes - (against Agenda)</span>

</div> 
<ul style="margin: 10px 0 0 0"> 
<li>Intros:<br> 
<ul style="margin: 10px 0 0 0"> 
<li>Estaban Posada (Adobe intern)</li> 
<li>Vadim Raskin (IBM)</li> 
<li>Mark Peek (VMWare)</li> 
<li>Duy Nguyen (Adobe) with Tyson, Dragos' team</li> 
<li>Ying Guo (Daisy)</li> 
</ul> </li> 
<li>Noteworthy PRs:<br> 
<ul style="margin: 10px 0 0 0"> 
<li>Markus: have a PR today merged? on dev list, removal of old Invoker code<br>

<ul style="margin: 10px 0 0 0"> 
<li>since last call SPI got in (from Tyson)</li> 
<li>Gradle bumped 4.1, merged today</li> 
</ul> </li> 
<li>Tyson: not a lot of feedback for agenda topics</li> 
</ul> </li> 
</ul> 
<ul style="margin: 10px 0 0 0"> 
<li>Releases<br> 
<ul style="margin: 10px 0 0 0"> 
<li>Duy: <br> 
<ul style="margin: 10px 0 0 0"> 
<li>started looking into releases for OW in general</li> 
<li>not easy to manage deployments</li> 
<li>gathered ideas on Wiki, will send out notes on mailing lists</li> 
<li>idea is stick we have right now, add versions to Docker images, utilize DockerHub</li>

<li>use of GitHub issues would continue</li> 
</ul> </li> 
<li>Tyson: summary somewhere?</li> 
<li>Duy: provided this link:&nbsp;</li> 
<li>Matt: how do we coord. client tooling CLI etc. and Kube/Mesos dep.?</li> 
<li>Duy: doing Mavin further out?</li> 
<li>Tyson: thinking about, not how to do releases on sep. repos, but how do sep. repos
consume release artifacts from core repos</li> 
<li> <br> 
<ul style="margin: 10px 0 0 0"> 
<li>common Scala jar for example, how do we get that released/versioned/Mavin artifact</li>

</ul> </li> 
<li>Matt: client and server have to match</li> 
<li>Rob: commits break cross repos. need to document these dependencies</li> 
<li>Tyson: maybe produce a dependency map across core pieces, client/invoker-controller,
common Scala, etc.</li> 
<li> <br> 
<ul style="margin: 10px 0 0 0"> 
<li>what broke? client-core?</li> 
</ul> </li> 
<li>Rob: cannot recall (after my holiday) /grin</li> 
<li> <br> 
<ul style="margin: 10px 0 0 0"> 
<li>Agree on dep. graph Tyson suggested, like the Wiki page</li> 
<li>Get discussion going on dev list?</li> 
</ul> </li> 
<li>Markus: why are we releasing to Maven repo? jars vs. docker images?</li> 
<li> <br> 
<ul style="margin: 10px 0 0 0"> 
<li>only now only considered docker mages?</li> 
</ul> </li> 
<li>Tyson: from purpose of impl. non-default SPI impl that can be built into a sep.
Docker images. &nbsp;Doing this with Docker image could be awkward, easier with fine-grained
JAR artifacts, use them as building blocks in other impls.</li> 
<li>e.g.,Kubernetes would (and Mesos) have SPI for container factory, implication building
and alternate container factory, you have an interface you build to that exists as a JAR somewhere..
&nbsp;could extract that from the Docker images (locally) but conventional approach of
interfaces released as part of a JAR and consumed by your separate repo would be easier</li>

<li>Markus: makes sense. slightly diff POV we should clear up these issues first. &nbsp;we
need to be cautious about lots of custom SPIs in depl. everywhere; would expect/hope they
get contribute back to the “core”<br> 
<ul style="margin: 10px 0 0 0"> 
<li>should have configurable classes (now we have which is great)</li> 
<li>need to be cautious about driving the plug in system to its mac… make sense?</li>

</ul> </li> 
<li>Tyson: there is having diff. pieces and diff. pieces in diff repos.<br> 
<ul style="margin: 10px 0 0 0"> 
<li>once you have repos sep. you have this dep. graph complication. would hope to keep
this as small as possible, but are you suggesting keeping all plugins in one repo?</li>

</ul> </li> 
<li>Markus: personally used to be a fan of many diff. repos. but the issues with complex
dep. graph perhaps I have grown more cautious with this approach. &nbsp;I think if we
want to go that route, we need processes to manage this properly. for the time being, we could
start merging SPIs into “main; openwhisk repo. this gives us flex. to maintain releases.<br>

<ul style="margin: 10px 0 0 0"> 
<li>This SPI adds a “whole ne later” we have not considered before; tooling could
more easily tell us of binary breaking changes</li> 
<li>Could be overkill, might be fine. &nbsp;just wanted to raise this</li>

</ul> </li> 
<li>Tyson: if someone provides an SPI impl. and does not want to merge to master, then
they will have the complications</li> 
<li>Rodric: i think there are 2 thing to consider: 1) rapid experimentation and expansion,
SPI lets us decouple (a good thing)</li> 
<li>2) to Markus' pt. if something matures 2) we should consider merging into “core
feature set”.</li> 
<li> <br> 
<ul style="margin: 10px 0 0 0"> 
<li>initially makes sense to keep sep. and decoupled, creates ind. processes and experimentation
(velocity), but need to look to treat mature things as part of main/core.</li> 
<li>Tyson: how do we do this without Maven?</li> 
<li>Rodric: I think its a fine approach</li> 
<li>Markus: alternative would be forks</li> 
<li>Rodric: slippery slope, if a fork becomes too popular you never catch up. &nbsp;Keep
everyone on master makes sense</li> 
</ul> </li> 
<li>Dragos: echo Markus. Keep code in same repo (support). &nbsp;</li> 
<li>Rodric: trade off in creating a docker file (partial) you would have to “inject”
you dependencies (plug ins). Is there a concern for creating releases with Maven drops it
becomes un-maintainable</li> 
<li>Markus: yes, that is why i raised, need to keep interfaces stable (document and
deprecate interfaces)</li> 
<li>Rodric: isn't that what semantic versioning is for?</li> 
<li>Markus: sure, in theory , but “falling from the sky”; i have done lots of refactoring.
&nbsp;we throw lots of code out, and if we do this it makes it harder</li> 
<li>Rodric: core is still immature, we are changing core impls. how this impact releases…?
&nbsp;do we have to become good citizens and do we get in the way of project velocity.
&nbsp;Need to be sensitive to downstream dependencies. &nbsp;It may be unpleasant,
but it may be the right thing to do? Carlos Rob opinions?</li> 
<li>Carlos: at end of day, you have to build container form controller and invoker.
I think that extending the controller we can use an image we are posting to Docker Hub today
and build on top and extend it and add JAR files, but as Markus said, people will create their
own containers (which may not boot). &nbsp;We invested in creating the container, is that
a concern?</li> 
<li>Tyson: people would have to consider how they build their own container, we may
need to create guidance.<br> 
<ul style="margin: 10px 0 0 0"> 
<li>can we allow things to be extensible wo/ having this ,ore rigid release process,
which will include other aspects of the system. e.g., without producing the JARs for these
extension; if they are produced outside main openwhisk this presents problems</li> 
</ul> </li> 
<li>Markus: maybe we can tune the dependence a bit, for current SPIs, we could live
with releasing a JAR of interfaces (a smallish release) and see how far this gets us?</li>

<li>Tyson: Maybe: perhaps move into sep. package in parallel to common and try</li>

<li>Markus: schema of entities and wire protocol messages are the important “bits”.
we should keep the surface of our interfaces as small as possible. be careful which interfaces
we release as “extension points” and count on. versus releasing everything. &nbsp;Matter
of internal/external</li> 
<li>Rodric: Apache, does this put us on the path</li> 
<li>Markus: not directly related, as openwhisk as a whole we can release as a git tag/hash</li>

<li>Rodric what are parms for official Apache release</li> 
<li>Carlos: minimum, git clone a tag (tag version 1.0.1) ZIP that and run license tooling,
no binaries on there, put on Apache FTP site<br> 
<ul style="margin: 10px 0 0 0"> 
<li>not related, min. is source code tagged zipped and blessed as legal.</li>

<li>then release binary assets, not official per-se, more headaches to get approved</li>

<li>other Apache projects use Maven for binary releases.</li> 
</ul> </li> 
<li>Tyson: for building extensions, only convenient way is pushing binary JAR to Maven.</li>

<li>Markus: forks will be a mess, discard that idea.<br> 
<ul style="margin: 10px 0 0 0"> 
<li>define public interfaces and just “do it”. &nbsp;Be aware people will “count
on” these interfaces. &nbsp;Ideally tooling, would tell us we are breaking a public
interfaces and tell us to make version bump</li> 
</ul> </li> 
<li>Rob: conflating 2 things. v1, v1.1 etc.<br> 
<ul style="margin: 10px 0 0 0"> 
<li>2nd thing is what we consider a stable API for release</li> 
<li>binary stuff, what do we consider to call “stable” to use as integration pt.</li>

<li>ideally make as small as poss. and grow it</li> 
<li>smallest that is possible stable, do not say everything is a public interface</li>

<li>create a list of “What are our ext. points” then look at how refactoring code
might be affected</li> 
</ul> </li> 
<li>Carlos: is there a convention? &nbsp;is there a common, top-level API we need
to define? &nbsp;There are things in core that we may not want to be public interfaces</li>

<li>Markus: build the artifact tyson referenced</li> 
<li>Rob: collect use cases, what people expect to extend and that decides what we export</li>

<li>Carlos: makes sense</li> 
<li>Markus; artifacts tore, messaging provider, other interfaces we are doing now; do
these ext. points have impact on DB artifacts or messages (as the messaging tech. use them)<br>
<br> </li> 
</ul> </li> 
<li>Other SPIs<br> 
<ul style="margin: 10px 0 0 0"> 
<li>Tyson: good segue<br> 
<ul style="margin: 10px 0 0 0"> 
<li>other SPI: Container factory (add a jumping pt. rom using Docker to create containers,
but either use Kube or Mesos to create containers</li> 
<li>Logging: related to container factory, once container delegated away from docker,
log handling also needs delegation</li> 
</ul> </li> 
<li>Markus :user/comp logging?</li> 
<li>Tyson: <br> 
<ul style="margin: 10px 0 0 0"> 
<li>Another one is authentication SPI</li> 
<li>That is the short list of SPIs we [Adobe] are looking at</li> 
</ul> </li> 
<li>Dragos: makes sense<br> 
<ul style="margin: 10px 0 0 0"> 
<li>assume we create a new module for these</li> 
<li>there is one artifact we release that has all interfaces for all these SPIs?</li>

</ul> </li> 
<li>Tyson: yes, gets tricky with DB entities… do not know exactly what that looks
like. &nbsp;Some of these impls. may not have entity stores on their interfaces, but still
depend on entities. Perhaps these are a special case</li> 
<li>Markus: gets tricky, we can freely add attributes today (as its a CouchDB), but
may not translate to schema how we release the code wise<br> 
<ul style="margin: 10px 0 0 0"> 
<li>Rob’s pt. applies well. we have existing ext. points, let’s start releasing
these and develop plug point for others as needed at that point in time. &nbsp;</li>

<li>Wait for the req. for that ext. pt. then develop it</li> 
</ul> </li> 
<li>Tyson: we do have req. for these ext. points, perhaps I can summarize in a Wiki
page and start a discussion</li> 
<li>Rob: yes, the we would&nbsp;</li> 
<li>Markus: for what are you trying to plug into that makes sense</li> 
<li>Tyson: next topic was release JARs, we covered that.<br> 
<ul style="margin: 10px 0 0 0"> 
<li>any other topics?</li> 
<li>None…?</li> 
</ul> </li> 
<li>Dragos: we only have 15 mins… but concurrent activations discussion was had in
the past; not sure if we had an agreement<br> 
<ul style="margin: 10px 0 0 0"> 
<li>having mult. action kinds. Developer controls those kinds along with mult. Load
Balancing impls.</li> 
</ul> </li> 
<li>Tyson: PR #2584: SPI PR for LoadBalancer, separately we had asked (and Markus commented)
it has been suggested this would be done on sep. PR later. &nbsp;There would be a particular
mapping from a particular kind to a particular LB.&nbsp; <br> 
<ul style="margin: 10px 0 0 0"> 
<li>For concurrent activation loads, there would be a sep. LB in place</li> 
</ul> </li> 
<li>Markus: choose the existing publish interface to choose LB; current interface takes
entire action and activation message; info. night be relevant (map from kinds to LB) but also
need other annotations and info.</li> 
<li>Tyson: agree: a broader mapping cap. would be good there</li> 
<li>Rob: what is process to get this through impl and code?</li> 
<li>Tyson: which process to agree/code?</li> 
<li>Tyson: general process.. for alt. impl. submit PR to extract that interface as an
SPI and default impl. would retain existing behavior and build out alt. impl (on your own
or inside codebase) and that is it.</li> 
<li>Rob: sounds too easy. This concurrent activation thing was on meeting a month ago,
was “Dev” discussion. Is someone actual coding this?</li> 
<li>Tyson: yes, will update the Wiki page. <br> 
<ul style="margin: 10px 0 0 0"> 
<li>There are a few points where there are distinctions from current codebase. container
factory using Mesos instead of Docker cmds. directly. &nbsp;other thing is LB that has
an API that only supports one impl (i.e., concurrent). &nbsp;</li> 
<li>The container pool is not an Actor, it is a Java object ad does not have queueing
behavior, but executes HTTP requests to containers in a concurrent fashion.</li> 
<li>will update wiki with branch (Git) that it is being built in; now a WIP (clearly).
&nbsp;looking at proper ext. points without corrupting orig. behavior of OpenWhisk. &nbsp;Honing
an API now...</li> 
</ul> </li> 
</ul> </li> 
<li>Tyson: 5 mins left… 
<ul style="margin: 10px 0 0 0; margin-top: 0"> 
<li>Next week topics? 
<ul style="margin: 10px 0 0 0; margin-top: 0"> 
<li>SPI / release topic, should likely continue… keep conversation going</li>

</ul> </li> 
<li>Kavitha:&nbsp; 
<ul style="margin: 10px 0 0 0; margin-top: 0"> 
<li>Will we discuss performance? &nbsp;Frameworks? what measurements?</li>

</ul> </li> 
<li>Markus: Repo. got created…<br> 
<ul style="margin: 10px 0 0 0"> 
<li>Tyson pls open your PR again</li> 
<li>Tyson ok</li> 
<li>Markus: do not wait for Zoom call, just use dev list to discuss</li> 
</ul> </li> 
<li>Carlos: tried enabling Travis for that repo. ...</li> 
</ul> </li> 
<li>Tyson: Who will moderate next call?<br> 
<ul style="margin: 10px 0 0 0"> 
<li>Rodric: I nominate Carlos...</li> 
<li>Carlos: accepted.</li> 
</ul> </li> 
<li>Rodric: need followup on “dev” list on the 2 main topics (release, SPI)?</li>

<li>Markus: dev list might engage our mentors as well</li> 
<li>Tyson: will start those discussions on the “dev” list</li> 
<li>Adjourned.</li> 
</ul> </td> 
</tr> 
</tbody> 
</table> </td> 
</tr> 
<tr> 
<td class="email-content-main mobile-expand action-padding last-row-padding" style="padding:
0px; border-collapse: collapse; border-left: 1px solid #ccc; border-right: 1px solid #ccc;
border-top: 0; border-bottom: 0; padding: 0 15px 15px 16px; background-color: #fff; padding-bottom:
10px; padding-bottom: 10px"> 
<table id="actions-pattern" cellspacing="0" cellpadding="0" border="0" width="100%" style="border-collapse:
collapse; mso-table-lspace: 0pt; mso-table-rspace: 0pt; color: #333; font-family: Arial, sans-serif;
font-size: 14px; line-height: 20px; mso-line-height-rule: exactly; mso-text-raise: 1px">

<tbody> 
<tr> 
<td id="actions-pattern-container" valign="middle" style="padding: 0px; border-collapse:
collapse; padding: 15px 0 0 24px; vertical-align: middle"> 
<table align="left" style="border-collapse: collapse; mso-table-lspace: 0pt; mso-table-rspace:
0pt; color: #333"> 
<tbody> 
<tr> 
<td class="actions-pattern-action-icon-container" style="padding: 0px; border-collapse:
collapse; font-family: Arial, sans-serif; font-size: 14px; line-height: 20px; mso-line-height-rule:
exactly; mso-text-raise: 0px; vertical-align: middle"><a href="https://cwiki.apache.org/confluence/display/OPENWHISK/2017-08-16+OW+Tech.+Interchange+-+Meeting+Notes?src=mail&amp;src.mail.timestamp=1502900998287&amp;src.mail.notification=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification&amp;src.mail.recipient=8aa980875bf24635015c9267bc8e02f6&amp;src.mail.action=view"
title="View page Icon" style="color: #3b73af; text-decoration: none"><img class="actions-pattern-action-icon-image"
height="16" width="16" border="0" title="View page Icon" src="cid:com.atlassian.confluence.plugins.confluence-email-resources_view-page-email-adg-footer-item_icon"
alt="View page Icon" style="vertical-align: middle"></a></td>
<td class="actions-pattern-action-text-container" style="padding: 0px; border-collapse:
collapse; font-family: Arial, sans-serif; font-size: 14px; line-height: 20px; mso-line-height-rule:
exactly; mso-text-raise: 4px; padding-left: 5px; white-space: nowrap"><a href="https://cwiki.apache.org/confluence/display/OPENWHISK/2017-08-16+OW+Tech.+Interchange+-+Meeting+Notes?src=mail&amp;src.mail.timestamp=1502900998287&amp;src.mail.notification=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification&amp;src.mail.recipient=8aa980875bf24635015c9267bc8e02f6&amp;src.mail.action=view"
title="View page" style="color: #3b73af; text-decoration: none">View page</a></td>
<td class="actions-pattern-action-bull" style="padding: 0px; border-collapse: collapse;
font-family: Arial, sans-serif; font-size: 14px; line-height: 20px; mso-line-height-rule:
exactly; mso-text-raise: 4px; color: #999; padding: 0 5px">•</td> 
</tr> 
</tbody> 
</table> 
<table style="border-collapse: collapse; mso-table-lspace: 0pt; mso-table-rspace: 0pt;
color: #333"> 
<tbody> 
<tr> 
<td class="actions-pattern-action-icon-container" style="padding: 0px; border-collapse:
collapse; font-family: Arial, sans-serif; font-size: 14px; line-height: 20px; mso-line-height-rule:
exactly; mso-text-raise: 0px; vertical-align: middle"><a href="https://cwiki.apache.org/confluence/plugins/likes/like.action?contentId=73633637&amp;src=mail&amp;src.mail.timestamp=1502900998287&amp;src.mail.notification=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification&amp;src.mail.recipient=8aa980875bf24635015c9267bc8e02f6&amp;src.mail.action=like"
title="Like Icon" style="color: #3b73af; text-decoration: none"><img class="actions-pattern-action-icon-image"
height="16" width="16" border="0" title="Like Icon" src="cid:com.atlassian.confluence.plugins.confluence-like_view-email-adg-content-item_icon"
alt="Like Icon" style="vertical-align: middle"></a></td>
<td class="actions-pattern-action-text-container" style="padding: 0px; border-collapse:
collapse; font-family: Arial, sans-serif; font-size: 14px; line-height: 20px; mso-line-height-rule:
exactly; mso-text-raise: 4px; padding-left: 5px; white-space: nowrap"><a href="https://cwiki.apache.org/confluence/plugins/likes/like.action?contentId=73633637&amp;src=mail&amp;src.mail.timestamp=1502900998287&amp;src.mail.notification=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification&amp;src.mail.recipient=8aa980875bf24635015c9267bc8e02f6&amp;src.mail.action=like"
title="Like" style="color: #3b73af; text-decoration: none">Like</a></td> 
</tr> 
</tbody> 
</table> </td> 
</tr> 
</tbody> 
</table> </td> 
</tr> 
<tr> 
<td class="email-content-rounded-bottom mobile-expand" style="padding: 0px; border-collapse:
collapse; color: #fff; height: 5px; line-height: 5px; padding: 0 15px 0 16px; background-color:
#fff; border-bottom-right-radius: 5px; border-bottom-left-radius: 5px; border-top: 0; border-left:
1px solid #ccc; border-bottom: 1px solid #ccc; border-right: 1px solid #ccc; mso-line-height-rule:
exactly">&nbsp;</td> 
</tr> 
</tbody> 
</table> </td> 
</tr> 
<tr> 
<td id="footer-pattern" style="padding: 0px; border-collapse: collapse; padding: 12px 20px">

<table id="footer-pattern-container" cellspacing="0" cellpadding="0" border="0" width="100%"
style="border-collapse: collapse; mso-table-lspace: 0pt; mso-table-rspace: 0pt; color: #333">

<tbody> 
<tr> 
<td id="footer-pattern-links-container" width="100%" style="padding: 0px; border-collapse:
collapse; color: #999; font-size: 12px; line-height: 18px; font-family: Arial, sans-serif;
mso-line-height-rule: exactly; mso-text-raise: 2px"> 
<table align="left" style="border-collapse: collapse; mso-table-lspace: 0pt; mso-table-rspace:
0pt; color: #333; font-size: 12px; line-height: 18px; font-family: Arial, sans-serif; mso-line-height-rule:
exactly; mso-text-raise: 2px"> 
<tbody> 
<tr> 
<td class="footer-pattern-links mobile-resize-text" style="padding: 0px; border-collapse:
collapse"><a href="https://cwiki.apache.org/confluence/users/removespacenotification.action?spaceKey=OPENWHISK&amp;src=mail&amp;src.mail.timestamp=1502900998287&amp;src.mail.notification=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification&amp;src.mail.recipient=8aa980875bf24635015c9267bc8e02f6&amp;src.mail.action=stop-watching"
title="" style="color: #3b73af; text-decoration: none">Stop watching space</a></td>
<td class="footer-pattern-links-bull" style="padding: 0px; border-collapse: collapse; padding:
0 5px; color: #999">•</td> 
</tr> 
</tbody> 
</table> 
<table style="border-collapse: collapse; mso-table-lspace: 0pt; mso-table-rspace: 0pt;
color: #333; font-size: 12px; line-height: 18px; font-family: Arial, sans-serif; mso-line-height-rule:
exactly; mso-text-raise: 2px"> 
<tbody> 
<tr> 
<td class="footer-pattern-links mobile-resize-text" style="padding: 0px; border-collapse:
collapse"><a href="https://cwiki.apache.org/confluence/users/editmyemailsettings.action?src=mail&amp;src.mail.timestamp=1502900998287&amp;src.mail.notification=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification&amp;src.mail.recipient=8aa980875bf24635015c9267bc8e02f6&amp;src.mail.action=manage"
title="" style="color: #3b73af; text-decoration: none">Manage notifications</a></td>

</tr> 
</tbody> 
</table> </td>
<td id="footer-pattern-logo-desktop-container" rowspan="2" valign="top" style="padding:
0px; border-collapse: collapse; padding-left: 20px; vertical-align: top"> 
<table style="border-collapse: collapse; mso-table-lspace: 0pt; mso-table-rspace: 0pt;
color: #333"> 
<tbody> 
<tr> 
<td id="footer-pattern-logo-desktop-padding" style="padding: 0px; border-collapse: collapse;
padding-top: 3px"><img id="footer-pattern-logo-desktop" src="cid:footer-desktop-logo"
alt="Confluence logo big" title="Confluence logo big" width="132" height="20" class="image_fix"></td>

</tr> 
</tbody> 
</table> </td> 
</tr> 
<tr> 
<td id="footer-pattern-text" class="mobile-resize-text" width="100%" style="padding: 0px;
border-collapse: collapse; color: #999; font-size: 12px; line-height: 18px; font-family: Arial,
sans-serif; mso-line-height-rule: exactly; mso-text-raise: 2px; display: none">This message
was sent by Atlassian Confluence 5.8.17<br> <img id="footer-pattern-logo-mobile"
src="cid:footer-mobile-logo" alt="" title="" width="0" height="0" style="display: none; mso-hide:
all"></td> 
</tr> 
</tbody> 
</table> </td> 
</tr> 
</tbody> 
</table> 
<table id="sealed-section" border="0" cellpadding="0" cellspacing="0" width="0" style="border-collapse:
collapse; mso-table-lspace: 0pt; mso-table-rspace: 0pt; color: #333; display: none"> 
<tbody> 
<tr> 
<td style="padding: 0px; border-collapse: collapse; border: 0; font-size: 0px; line-height:
0; mso-line-height-rule: exactly"></td> 
</tr> 
</tbody> 
</table>
</body>
</html>
Mime
View raw message