> Can we handle these in same way as user events? Maybe exactly like user
events, as in use a single service to process both topics.
good call - the user events already contains much of the activation record
(if not all modulo the logs)?
-r
The logs issue is mostly separate from the activation records.
RE activation records:
Can we handle these in same way as user events? Maybe exactly like user events,
as in use a single service to process both topics.
RE logging:
We deal with logs this way (collect from container via fluent),
Rodric Rabbah wrote on 06/20/2019 09:37:38 PM:
>
> Overflowing to Kafka (option b) is better. Actually I would dump all
> the activations there and have a separate process to drain that
> Kafka topic to the datastore or logstore.
I agree. Spilling to Kafka is desirable to avoid OOMs in the
As a budding security engineer, I’ll suggest to emphasize role based
security authorization rather than a permission model. It’s easier to
maintain over time, and it’ll map well to OAuth scopes as well as in JWT
metadata, plus it’ll likely still adapt well to whatever new security
standards are
Hi Nick,
> we have the need to create namespaces/authkeys
I have added an initial readme with steps on how to register custom
namespace at [1]. Can you give it a try and let us know if it meet
your requirements. Otherwise we can look into support a minimal REST
api to add user in standalone case
> Just curious why the jar can’t be build in Windows can you log an issue for
> this?
So far never tried building openwhisk core repo on Windows hence the
doubt. We can try checking that. However eventually users would be
downloading this jar either from Maven or Github release. So windows
build
we have the need to create namespaces/authkeys (so that we can run tests in
parallel); is this supported by the current build env? or would we have to
launch a separate openwhisk process for each tenant?
On Fri, Jun 21, 2019 at 8:03 AM Carlos Santana wrote:
> Chetan thanks for thinking on
Chetan thanks for thinking on Windows users +1
Just curious why the jar can’t be build in Windows can you log an issue for
this?
My 2 cents for Windows or Mac I think the best way to build the jar would be
inside a docker container. A one liner with a single command should be able to
produce
Rodric I think having additional authentication methods no one will object, but
the devil are in the details :-)
Also when you say things like “replace” with no more context some folks that
are using the software in production, quickly jump into the conclusion on “Now
I have thousands of end
Just to share some more progress. With runnable jar its now possible
to run OpenWhisk standalone even on Windows and execute basic actions.
Tested it with Docker on Windows 2.0.0.3 on Windows 10
Note you would probably not be able to build the project on windows.
But copying the produced jar
thanks chetan for doing this!
could you provide some example startup sequences, e.g. with sample configs?
i'm willing to try this out for our CI/CD pipeline -- i'm sick of 1)
waiting 5-7 minutes for openwhisk to start up; and b) fighting ansible
versus xenial :)
@starpit
On Fri, Jun 21, 2019 at
I'm curious if anyone has thought about or implemented an oauth based
authentication mechanism in the controller. I've thought about replacing
the subject authentication with oauth and think it would not be a lot of
work to do although it does have some wider implications.
-r
2019-06-20 01:14:59 UTC - Rodric Rabbah: Just read the blog @rawkintrevo. Very
cool I’d like to try this out.
Note that “OpenWhisk expects its Docker functions to start off from the
dockerSkelaton image.” isn’t quite right. You can use any image as your base as
long as you implement the
13 matches
Mail list logo
