It's amazing and blazingly fast!
It will enable a lot of things.
Thanks, Chetan!
2019년 6월 26일 (수) 오전 12:52, James Thomas 님이 작성:
> That is incredible. Great work Chetan! I've been playing around with
> it and have no issues so far...
>
> Would love to starting using this in the CI/CD setups
That is incredible. Great work Chetan! I've been playing around with
it and have no issues so far...
Would love to starting using this in the CI/CD setups for some of the
repos I work on to massively improve the CI/CD delay in testing new
PRs.
On Tue, 25 Jun 2019 at 14:00, Rodric Rabbah wrote:
I tried this out - it is awesome... and fast!
-r
On Mon, Jun 24, 2019 at 6:08 AM Chetan Mehrotra
wrote:
> Hi Team,
>
> At this stage the OpenWhisk Standalone jar works fine. So would like
> to get it tried out in real world and for that need some volunteers!
>
> You can follow the steps at
>
oh, one thing worth mentioning: when testing on electron, on linux, i have
to use an http keep-alive http agent when talking to the standalone. this
has been a perennial problem with electron/linux versus openwhisk (i still
have no idea why); but the standalone jar made the problem considerably
it's been working well for our CI/CD tests. standalone openwhisk, combined
with microk8s, are a perfect combination for test pipelines against this
kind of infrastructure.
thanks!!
On Mon, Jun 24, 2019 at 6:08 AM Chetan Mehrotra
wrote:
> Hi Team,
>
> At this stage the OpenWhisk Standalone jar
Hi Team,
At this stage the OpenWhisk Standalone jar works fine. So would like
to get it tried out in real world and for that need some volunteers!
You can follow the steps at
https://github.com/chetanmeh/incubator-openwhisk/releases/tag/v0.10
and download the jar and try out a hello world or
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
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
> What's the performance like on startup time
It starts in < 5 secs.
So far no major blocking issue apart from fetching docker logs on Mac.
Current approach of directly reading the log json does not work. So
need to have a mac version which uses `docker logs` command to
somewhat handle such a
That is mind-blowingly cool!
What's the performance like on startup time?
On Thu, 20 Jun 2019 at 06:14, Carlos Santana wrote:
>
> Genius!
> https://www.adminsub.net/tcp-udp-port-finder/whisker
>
>
> - Carlos Santana
> @csantanapr
>
> > On Jun 19, 2019, at 12:30 PM, David P Grove wrote:
> >
> >
Genius!
https://www.adminsub.net/tcp-udp-port-finder/whisker
- Carlos Santana
@csantanapr
> On Jun 19, 2019, at 12:30 PM, David P Grove wrote:
>
> WhiskerControl
> Port 8080 is a highly conflicted default port,
Good point!. Thats the current default which does not posed problem
when running alone in a container env.
So which port should be "branded" for OpenWhisk. May be we use 1.
Any suggestions for that
Chetan Mehrotra
On Wed, Jun 19, 2019 at
On Tue, Jun 18, 2019 at 3:22 PM Chetan Mehrotra
wrote:
> ...Thoughts?..
I think we need better emoticon support on this list to express how
cool this is ;-)
-Bertrand
Very cool! Port 8080 is a highly conflicted default port, though. ;)
On Tue, 18 Jun 2019 at 08:37, Felix Meschberger
wrote:
>
> Wow ! This goes a long way to developer ease of getting to know.
>
> Kudos !
>
> Regards
> Felix
>
> > Am 18.06.2019 um 15:22 schrieb Chetan Mehrotra :
> >
> > Hi Team,
Wow ! This goes a long way to developer ease of getting to know.
Kudos !
Regards
Felix
> Am 18.06.2019 um 15:22 schrieb Chetan Mehrotra :
>
> Hi Team,
>
> Recently based on some feedback by end users I felt a need for a
> simpler way to test out OpenWhisk for end users. Towards that end
>
That's very cool! +1.
-r
On Tue, Jun 18, 2019 at 9:22 AM Chetan Mehrotra
wrote:
> Hi Team,
>
> Recently based on some feedback by end users I felt a need for a
> simpler way to test out OpenWhisk for end users. Towards that end
> there is a new PR #4516 which enables launching OpenWhisk as a
Hi Team,
Recently based on some feedback by end users I felt a need for a
simpler way to test out OpenWhisk for end users. Towards that end
there is a new PR #4516 which enables launching OpenWhisk as a simple
runnable jar.
java -jar openwhisk-standalone-1.0.0-SNAPSHOT.jar
Post this OpenWhisk
21 matches
Mail list logo
