Re: Warm containers

[Markus Thömmes]

Hi Mandeep,

OpenWhisk relies on container reuse (i.e. using warm containers) heavily to 
reach its performance goals. Currently, containers are kept around for a 
maximum of 10 minutes if they are not replaced by the need of some other 
container.

You can refer to this article written by me (shameless self-advertisement) to 
get some insights into how our container caching works: 
https://medium.com/openwhisk/squeezing-the-milliseconds-how-to-make-serverless-platforms-blazing-fast-aea0e9951bd0

You can refer to the relevant source code here:
- 
https://github.com/apache/incubator-openwhisk/blob/master/core/invoker/src/main/scala/whisk/core/containerpool/ContainerProxy.scala
- 
https://github.com/apache/incubator-openwhisk/blob/master/core/invoker/src/main/scala/whisk/core/containerpool/ContainerPool.scala

Anything more you can think of for your use-case?

Cheers,
Markus

Am 06. September 2017 um 07:50 schrieb mandeep gandhi 
:

Hi,

I was looking for the support of warm containers for JVM and Python based
containers. I have a use case where I want to run some scala/java micro
services and some TensorFlow containers for my workflow.

Now as these containers would take some seconds to get up, I would like to
know -

a. What is the current status for the same?
b. How can we contribute to it if the support is missing?


Thanks,
Mandeep Gandhi

Warm containers

[mandeep gandhi]

Hi,

I was looking for the support of warm containers for JVM and Python based
containers. I have a use case where I want to run some scala/java micro
services and some TensorFlow containers for my workflow.

Now as these containers would take some seconds to get up, I would like to
know  -

a. What is the current status for the same?
b. How can we contribute to it if the support is missing?


Thanks,
Mandeep Gandhi

Podling Report Reminder - September 2017

[johndament]

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 20 September 2017, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, September 06).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://wiki.apache.org/incubator/September2017

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: Release for OpenWhisk

[Bertrand Delacretaz]

Hi,

On Mon, Aug 28, 2017 at 1:19 PM, Duy Nguyen  wrote:
> ...I started with a wiki page with some initial ideas for doing releases based
> on what we have for now.
> https://cwiki.apache.org/confluence/display/OPENWHISK/OpenWhisk+Release+Process
...

Note that there is a defined process for Apache releases, you cannot
just tag stuff and upload to some binary distribution service.

There's more information at
http://www.apache.org/legal/release-policy.html ,
http://www.apache.org/dev/release-distribution.html and
http://incubator.apache.org/guides/releasemanagement.html

-Bertrand