Page History

...

1. Est. release process for ZIP of source code
2. Est. release process for Docker and other platform binaries
3. Increase additional company and individual Contributors to maintain all project repos.

   Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be  aware of?    

• It had been our intent to have Apache host our staging (and move it out of disparate private builds within various companies). However, INFRA indicates they only typically allocate 1 VM per project for use with demos and minor things.  They indicate that typically perhaps a corporate donation is in order (ala. Spark).
  • Goal: standup testing resources at Apache and utilize for public CI and performance testing of OpenWhisk on Kubernetes
  • Needed resources:
    • Minimum 5 worker node kubernetes cluster.  Each worker nodes can be fairly modest (2-4 virtual cores; 4-8GB of memory)
      
      • 2 nodes for control plane:
      controller
      • Controller,
      kafka, nginx
      • Kafka,Nginx (each Docker containers)
      • 1 node for CouchDB
      • 2 nodes for
      invokers4 cores allows us to allow us to run key components as clusters with stateful sets
      • Invokers (containers)
    • See discussion here: OpenWhisk / Kubernetes proposed epics/action items/questions
• Formal hand-off of OpenWhisk trademark/logo from IBM needs to be executed; need to identify process for this.
  • Matt emailed apache legal via legal-discuss mailing list with subject "Trademark handoff for "OpenWhisk" name and logo".

How has the community developed since the last report?    

• TBD
• First substantive design changes allowing for Service Provider Interfaces (SPIs) developed within Apache community (dev list, WIki, etc.).
• Established bi-weekly Zoom "Technical Interchange" calls that have been well received.
  
  • Complete videos posted to OW YouTube channel and detailed notes to our CWIKI.
• Kubernetes on OpenWhisk work hosted a few ad-hoc to continue design discussions (CWIKI has designs and comments) for how best to move away from Ansible deployments to self-configuring, autoscalable containers (for use in Kube, Mesos, Compose, etc.).Increased community discussions (design topics, features) of substance moved to dev list.
  • Increased interest/list/Slack traffic in general due to experiment Kube work, as it is applicable to Mesos, etc.
  Increased community discussions (design topics, features) of substance moved to dev list
  • .

New Contributors:

• Brendan McAddams: Red Hat: Akka expert working on creating separate Akka dispatchers for CouchDB and Kafka Clients

How has the project developed since the last report?

• incubator-openwhisk Github stars: 1928
• incubator-openwhisk GitHub forks: 417
• Movement to become more "pluggable" via Service Provider Interfaces (SPI), several PRs that are ongoing.
  
  • So far there are now interfaces for MessagingProvider.scala, ArtifactStoreProvider.scala and proposals for others such as LogStore, ContainerFactory, LoadBalancer,
    

...

• 10/27: Emit metrics via kamon #2857
  • This PR implements the capability to send metric information via Kamon (http://kamon.io/) to statsd (https://github.com/etsy/statsd) instead or additionally to the existing metrics information
    which is written into the system logs.
    

     

• 
  

   

• 
  

  PREVIOUS: TODO REMOVE

• initial work on no root ansible #2669

• Simplify Spi implementations. #2663

Sig. discussions (dev list):

• TBD
  

   How would you assess the podling's maturity?  Please feel free to add your own commentary.    

   [ ] Initial setup
   [X] Working towards first release
   [X] Community building
   [ ] Nearing graduation
   [ ] Other:
 

...