is not deterministic and could be defined based on the further ops
experience.
If you have any feedback regarding this change, you could respond in this
thread, ping me on slack or comment in this PR:
https://github.com/apache/incubator-openwhisk/pull/2531
regards, Vadim Raskin.
regards, Vadim Raskin.
hnically a big difference to enable it by default (vs disabled), but I
> would err on the side that will produce the best results for more operators.
>
> WDYT?
>
> Thanks
> Tyson
>
> > On Sep 22, 2017, at 9:00 AM, Vadim Raskin <raskinva...@gmail.com> wrote:
> >
&g
uce log generation
> - replace log marker counter impl (with kamon?)
> - replace logging approach (with TraceContext or similar, if an option
> even exists, with the goal being to NOT pass whisk Logging around
> everywhere)
>
> (I’m really not sure about the last one, but it would
e “dynamic IP” scenario,
> > there needs to be documentation to indicate exactly what steps need to be
> > take to handle downing, and what the risks are of NOT doing this.
> >
> > Of course this could be seen as "just a matter of defaults”, so its not
> > technica
em to behave correctly without this stability.
>
> If there are questions on this, maybe we can discuss on the call tomorrow,
> or else I am happy to join a call but my mornings are already booked this
> week, so my earliest available is Monday.
>
> Thanks
> Tyson
>
>
>
Hi OpenWhisk community,
while doing our profiling tests on the controller we have found that the
way we log and the logging per se make a huge impact on the controller
thoughput. In a short, the more parallel activations you have, the more
blocking threads waiting for the logger will be there.
Hi everyone,
after much of effort was done by several people to make controller HA work
(kudos to Christian, Jeremias, Tyson and others) we are finally going to
enable it as default (
https://github.com/apache/incubator-openwhisk/pull/2994) in the open
repository. What does it mean?
* Edge is
hey Priti and Matt,
I think this is a big improvement in terms of the site content, thank you
for doing that!
The only thing that I will be missing after this PR gets merged is our
current web site design. Probably you have already considered several
options, just asking to verify. Is there a
d technology projects such as Kubernetes, etc. You can see some of
> the analysis in the linked wiki notes and the content is loss-less between
> old and new (and enhanced to a great degree). Is there something specific
> from the old site front page, content-wise, that we are missing?
hi Ben,
I won't be able to join, have an overlapping appointment.
Perhaps Carlos could say a couple of sentences on the topic.
cheers, Vadim
On Wed, Aug 15, 2018 at 12:56 AM Dragos Dascalita Haut
wrote:
> Unfortunately I'm in a flight during the meeting and I won't be able to
> attend.
>
>
>
Hi,
currently the list of system environment variables that are exposed in user
containers is configured in several places. First in the Invoker, it
defines api_host env var during container creation, the rest of the env
vars is configured for each run command via passing a json object [1] as a
Right, invoker already has the changes provided by the Entitlement spi.
Additional variables are provided via `authEnvironment`val in the
ContainerProxy.scala.
Just want to point out that the new variables will be only available for
the downstream implementations of the Entitlement SPI, e.g. IBM
Ideally we need to remove most of our env vars from /run to /init, I agree.
But wouldn't it be a breaking change then?
Coming back to my original question, I'm ok with leaving the env vars on
the root level of the json object. I think Carlos already has PRs that
could enable that functionality.
I see how performance of certain components could benefit from switching
its implementation to Go.
Earlier this year I did performance measurements of Go vs Scala http
servers / logging systems. I was able to find a combo of Go based
components that outperformed Scala implementation by 3-4x times.
Hi everybody,
this is a reminder of this week’s community interlock meeting - 28.02 16.00
UTC.
Apart from the standard topics we have the following items notched up in
our agenda:
Spring Cloud Functions and OW - Kamesh
Latest updates on Composer - Olivier
Updates on the Apache release process -
>> So, how can I check the process is actually terminated ?
Hi Michele,
what about using cmd.Wait() to check whether the process exited after you
started a go action? It will return a non-nil in case of error, otherwise
blocks forever waiting the process to finish. Waiting for a reasonable
o Kafka and consume the activations in real-time.
>
> May be we also include a basic default implementation out of the box
> which collect aggregated stats using Kamon metrics already being used
> Chetan Mehrotra
>
>
> On Mon, Apr 16, 2018 at 9:51 PM, Vadim Raskin <r
when to use
> > which - I caution that we are proliferating multiple ways of doing
> similar
> > things with no consistency or articulated long term vision.
> >
> > -r
> >
> > On Apr 17, 2018, at 12:01 PM, Vadim Raskin <raskinva...@gmail.com
> > ras
Hey there,
here is the full agenda we are going to have in today’s interlock meeting:
- Introduction of new participants
- Highlights of notable changes
- Updates on the release management process for Openwhisk - Vincent 10 mins
- New go runtime and action proxy - Michele - 15 minutes
- Spring
20 matches
Mail list logo
