Re: OpenWhisk as a single docker image?
On Wed, Nov 13, 2019 at 8:37 PM David P Grove wrote: > ...I don't think > building the jar actually requires much more software on your machine than > what is required to successfully run the jar, so the gap may be small... And if there's a significant gap, a Docker image with build tools can help. -Bertrand
RE: OpenWhisk as a single docker image?
Carlos Santana wrote on 11/13/2019 01:30:31 PM: > > Yes that’s fine to be “alongside” with the release, but I would not > want to wait months for another release just get a minor update to the jar > > I would prefer in addition to have a nightly jar built and easy to get. > We might be on better ground if we make it very easy to build a nightly jar from a git clone. Then there's a clear line between a `compiled package` that is derived from an Apache release and other things. I don't think building the jar actually requires much more software on your machine than what is required to successfully run the jar, so the gap may be small. Seems like that could become clearly documented and not that big a barrier. --dave > - Carlos Santana > @csantanapr > > > On Nov 13, 2019, at 9:09 AM, Bertrand Delacretaz > wrote: > > > > On Wed, Nov 13, 2019 at 3:02 PM Carlos Santana > wrote: > >> ...The jar can’t and should not be distributed as part of an > Apache release... > > > > It won't be an Apache Release but it's fine to distribute that jar as > > a "compiled package" [1] alongside its released source code. > > > > -Bertrand
Re: OpenWhisk as a single docker image?
Yes that’s fine to be “alongside” with the release, but I would not want to wait months for another release just get a minor update to the jar I would prefer in addition to have a nightly jar built and easy to get. - Carlos Santana @csantanapr > On Nov 13, 2019, at 9:09 AM, Bertrand Delacretaz > wrote: > > On Wed, Nov 13, 2019 at 3:02 PM Carlos Santana wrote: >> ...The jar can’t and should not be distributed as part of an Apache >> release... > > It won't be an Apache Release but it's fine to distribute that jar as > a "compiled package" [1] alongside its released source code. > > -Bertrand > > [1] http://www.apache.org/legal/release-policy.html
Re: OpenWhisk as a single docker image?
On Wed, Nov 13, 2019 at 3:02 PM Carlos Santana wrote: > ...The jar can’t and should not be distributed as part of an Apache release... It won't be an Apache Release but it's fine to distribute that jar as a "compiled package" [1] alongside its released source code. -Bertrand [1] http://www.apache.org/legal/release-policy.html
Re: OpenWhisk as a single docker image?
I think we're ready for a new release - at the last community call we set a goal of pushing out a release vote before the end of November. I expect we'll take stock today on the community call and should be ready to follow it up with a vote shortly thereafter. Given some recent feedback and questions about vagrant and compose, I'd like to see if we can remove vagrant from the docs (or entirely), and make sure the standalone controller is front and center on the README/getting started. -r On Wed, Nov 13, 2019 at 9:02 AM Carlos Santana wrote: > +1 The jar can be build and made available as a nightly/dev artifact for > quick development and testing purposes for convenience. > > Then provide the one liner command to get up and running, assuming jre and > docker is present :-) > > The jar can’t and should not be distributed as part of an Apache release. > > - Carlos Santana > @csantanapr > > > On Nov 13, 2019, at 8:55 AM, Michele Sciabarra > wrote: > > > > I did some experimentations with the docker in docker and ultimately I > am convinced it is actually better just to use the jar. I would then > suggest to distribute at least the precompiled jar instead of requiring to > compile by himself. > > > > -- > > Michele Sciabarra > > mich...@sciabarra.com > > > > ----- Original message - > > From: Chetan Mehrotra > > To: dev@openwhisk.apache.org > > Subject: Re: OpenWhisk as a single docker image? > > Date: Wednesday, November 13, 2019 6:00 AM > > > > Running standalone logic within a Docker would be tricky as there is > quite > > a bit of logic involved to use the right IP for inter docker > communications > > specially in Kafka and Api Gateway part. > > > > Hence currently we expect that to use standalone the user has at minimum > > JDK + Docker on the host > > > > Chetan Mehrotra > > > > > >> On Tue, Nov 12, 2019 at 10:58 PM Matt Sicker wrote: > >> > >> Docker in Docker has some slight security improvements depending on > >> your use case, too, compared to just mounting your docker socket into > >> the running container. > >> > >>> On Sat, 9 Nov 2019 at 10:30, Tyson Norris > >>> wrote: > >>> > >>> I suspect that due to Docker-in-Docker scenario, it will be easier to > >> use java+jar (+local docker) instead of running the jar in a container. > >>> > >>> Today you can start the jar with only java , but you will need a > >> bunch of parameters (probably different per OS?) to run it in a > container, > >> I think. > >>> Local docker client is switched per OS here > >> > https://github.com/apache/openwhisk/blob/231e739373ef681c44b5647a6956d5838a87db2e/core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/docker/StandaloneDockerContainerFactory.scala#L37 > >>> I guess this wouldn't apply if running in a container, but it arguably > >> makes running the jar simpler than running the container IMHO. > >>> I also suspect you won't get the behavior of launching playground ui to > >> browser either, which I would miss. > >>> > >>> Tyson > >>> > >>> On 11/9/19, 5:38 AM, "Michele Sciabarra" > wrote: > >>> > >>>Wow. I missed those evolutions. So I guess it should not be hard to > >> package it as a docker image. > >>> > >>> To be able to say to people: execute "docker run -p 8080:8080 > >> openwhisk/standalone" and enjoy... > >>> > >>>If it is possible I can volounteer to write the dockerfile do > that... > >>> > >>>I have a question: does it use the local docker? Where is the > >> invoker? > >>> > >>> > >>>-- > >>> Michele Sciabarra > >>> mich...@sciabarra.com > >>> > >>>- Original message - > >>>From: Rodric Rabbah > >>>To: dev@openwhisk.apache.org > >>>Subject: Re: OpenWhisk as a single docker image? > >>>Date: Saturday, November 09, 2019 2:31 PM > >>> > >>>Do you mean the standalone controller? > >> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fopenwhisk%2Fblob%2Fmaster%2Fcore%2Fstandalone%2FREADME.mddata=02%7C01%7Ctnorris%40adobe.com%7Cfc313c39337a44a5882a08d7651a0cbc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637089034867332217sdata=OCnWo8R5OfbKLaSQCEeI%2B7pqz0ewp%2BYQGBK2msMoMtc%3Dreserved=0 > >>> > >>>-r > >>> > >>>> On Nov 9, 2019, at 8:18 AM, Michele Sciabarra < > >> mich...@sciabarra.com> wrote: > >>>> > >>>> Hello all, > >>>> > >>>> I remember the discussion about the openwhisk as a single > >> executable that includes also Kafka. So I wonder: is it now possible to > run > >> (for development purposes of course) OpenWhisk as single docker image > if we > >> add also couchdb to that one? Because I have an use case where even a > >> docker-compose can be inconvenient... > >>>> > >>>> -- > >>>> Michele Sciabarra > >>>> mich...@sciabarra.com > >>> > >>> > >> > >> > >> -- > >> Matt Sicker > >> >
Re: OpenWhisk as a single docker image?
+1 The jar can be build and made available as a nightly/dev artifact for quick development and testing purposes for convenience. Then provide the one liner command to get up and running, assuming jre and docker is present :-) The jar can’t and should not be distributed as part of an Apache release. - Carlos Santana @csantanapr > On Nov 13, 2019, at 8:55 AM, Michele Sciabarra wrote: > > I did some experimentations with the docker in docker and ultimately I am > convinced it is actually better just to use the jar. I would then suggest to > distribute at least the precompiled jar instead of requiring to compile by > himself. > > -- > Michele Sciabarra > mich...@sciabarra.com > > - Original message - > From: Chetan Mehrotra > To: dev@openwhisk.apache.org > Subject: Re: OpenWhisk as a single docker image? > Date: Wednesday, November 13, 2019 6:00 AM > > Running standalone logic within a Docker would be tricky as there is quite > a bit of logic involved to use the right IP for inter docker communications > specially in Kafka and Api Gateway part. > > Hence currently we expect that to use standalone the user has at minimum > JDK + Docker on the host > > Chetan Mehrotra > > >> On Tue, Nov 12, 2019 at 10:58 PM Matt Sicker wrote: >> >> Docker in Docker has some slight security improvements depending on >> your use case, too, compared to just mounting your docker socket into >> the running container. >> >>> On Sat, 9 Nov 2019 at 10:30, Tyson Norris >>> wrote: >>> >>> I suspect that due to Docker-in-Docker scenario, it will be easier to >> use java+jar (+local docker) instead of running the jar in a container. >>> >>> Today you can start the jar with only java , but you will need a >> bunch of parameters (probably different per OS?) to run it in a container, >> I think. >>> Local docker client is switched per OS here >> https://github.com/apache/openwhisk/blob/231e739373ef681c44b5647a6956d5838a87db2e/core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/docker/StandaloneDockerContainerFactory.scala#L37 >>> I guess this wouldn't apply if running in a container, but it arguably >> makes running the jar simpler than running the container IMHO. >>> I also suspect you won't get the behavior of launching playground ui to >> browser either, which I would miss. >>> >>> Tyson >>> >>> On 11/9/19, 5:38 AM, "Michele Sciabarra" wrote: >>> >>>Wow. I missed those evolutions. So I guess it should not be hard to >> package it as a docker image. >>> >>>To be able to say to people: execute "docker run -p 8080:8080 >> openwhisk/standalone" and enjoy... >>> >>> If it is possible I can volounteer to write the dockerfile do that... >>> >>>I have a question: does it use the local docker? Where is the >> invoker? >>> >>> >>>-- >>> Michele Sciabarra >>> mich...@sciabarra.com >>> >>>- Original message - >>>From: Rodric Rabbah >>>To: dev@openwhisk.apache.org >>>Subject: Re: OpenWhisk as a single docker image? >>>Date: Saturday, November 09, 2019 2:31 PM >>> >>>Do you mean the standalone controller? >> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fopenwhisk%2Fblob%2Fmaster%2Fcore%2Fstandalone%2FREADME.mddata=02%7C01%7Ctnorris%40adobe.com%7Cfc313c39337a44a5882a08d7651a0cbc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637089034867332217sdata=OCnWo8R5OfbKLaSQCEeI%2B7pqz0ewp%2BYQGBK2msMoMtc%3Dreserved=0 >>> >>>-r >>> >>>> On Nov 9, 2019, at 8:18 AM, Michele Sciabarra < >> mich...@sciabarra.com> wrote: >>>> >>>> Hello all, >>>> >>>> I remember the discussion about the openwhisk as a single >> executable that includes also Kafka. So I wonder: is it now possible to run >> (for development purposes of course) OpenWhisk as single docker image if we >> add also couchdb to that one? Because I have an use case where even a >> docker-compose can be inconvenient... >>>> >>>> -- >>>> Michele Sciabarra >>>> mich...@sciabarra.com >>> >>> >> >> >> -- >> Matt Sicker >>
Re: OpenWhisk as a single docker image?
I did some experimentations with the docker in docker and ultimately I am convinced it is actually better just to use the jar. I would then suggest to distribute at least the precompiled jar instead of requiring to compile by himself. -- Michele Sciabarra mich...@sciabarra.com - Original message - From: Chetan Mehrotra To: dev@openwhisk.apache.org Subject: Re: OpenWhisk as a single docker image? Date: Wednesday, November 13, 2019 6:00 AM Running standalone logic within a Docker would be tricky as there is quite a bit of logic involved to use the right IP for inter docker communications specially in Kafka and Api Gateway part. Hence currently we expect that to use standalone the user has at minimum JDK + Docker on the host Chetan Mehrotra On Tue, Nov 12, 2019 at 10:58 PM Matt Sicker wrote: > Docker in Docker has some slight security improvements depending on > your use case, too, compared to just mounting your docker socket into > the running container. > > On Sat, 9 Nov 2019 at 10:30, Tyson Norris > wrote: > > > > I suspect that due to Docker-in-Docker scenario, it will be easier to > use java+jar (+local docker) instead of running the jar in a container. > > > > Today you can start the jar with only java , but you will need a > bunch of parameters (probably different per OS?) to run it in a container, > I think. > > Local docker client is switched per OS here > https://github.com/apache/openwhisk/blob/231e739373ef681c44b5647a6956d5838a87db2e/core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/docker/StandaloneDockerContainerFactory.scala#L37 > > I guess this wouldn't apply if running in a container, but it arguably > makes running the jar simpler than running the container IMHO. > > I also suspect you won't get the behavior of launching playground ui to > browser either, which I would miss. > > > > Tyson > > > > On 11/9/19, 5:38 AM, "Michele Sciabarra" wrote: > > > > Wow. I missed those evolutions. So I guess it should not be hard to > package it as a docker image. > > > > To be able to say to people: execute "docker run -p 8080:8080 > openwhisk/standalone" and enjoy... > > > > If it is possible I can volounteer to write the dockerfile do that... > > > > I have a question: does it use the local docker? Where is the > invoker? > > > > > > -- > > Michele Sciabarra > > mich...@sciabarra.com > > > > - Original message - > > From: Rodric Rabbah > > To: dev@openwhisk.apache.org > > Subject: Re: OpenWhisk as a single docker image? > > Date: Saturday, November 09, 2019 2:31 PM > > > > Do you mean the standalone controller? > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fopenwhisk%2Fblob%2Fmaster%2Fcore%2Fstandalone%2FREADME.mddata=02%7C01%7Ctnorris%40adobe.com%7Cfc313c39337a44a5882a08d7651a0cbc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637089034867332217sdata=OCnWo8R5OfbKLaSQCEeI%2B7pqz0ewp%2BYQGBK2msMoMtc%3Dreserved=0 > > > > -r > > > > > On Nov 9, 2019, at 8:18 AM, Michele Sciabarra < > mich...@sciabarra.com> wrote: > > > > > > Hello all, > > > > > > I remember the discussion about the openwhisk as a single > executable that includes also Kafka. So I wonder: is it now possible to run > (for development purposes of course) OpenWhisk as single docker image if we > add also couchdb to that one? Because I have an use case where even a > docker-compose can be inconvenient... > > > > > > -- > > > Michele Sciabarra > > > mich...@sciabarra.com > > > > > > > -- > Matt Sicker >
Re: OpenWhisk as a single docker image?
Running standalone logic within a Docker would be tricky as there is quite a bit of logic involved to use the right IP for inter docker communications specially in Kafka and Api Gateway part. Hence currently we expect that to use standalone the user has at minimum JDK + Docker on the host Chetan Mehrotra On Tue, Nov 12, 2019 at 10:58 PM Matt Sicker wrote: > Docker in Docker has some slight security improvements depending on > your use case, too, compared to just mounting your docker socket into > the running container. > > On Sat, 9 Nov 2019 at 10:30, Tyson Norris > wrote: > > > > I suspect that due to Docker-in-Docker scenario, it will be easier to > use java+jar (+local docker) instead of running the jar in a container. > > > > Today you can start the jar with only java , but you will need a > bunch of parameters (probably different per OS?) to run it in a container, > I think. > > Local docker client is switched per OS here > https://github.com/apache/openwhisk/blob/231e739373ef681c44b5647a6956d5838a87db2e/core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/docker/StandaloneDockerContainerFactory.scala#L37 > > I guess this wouldn't apply if running in a container, but it arguably > makes running the jar simpler than running the container IMHO. > > I also suspect you won't get the behavior of launching playground ui to > browser either, which I would miss. > > > > Tyson > > > > On 11/9/19, 5:38 AM, "Michele Sciabarra" wrote: > > > > Wow. I missed those evolutions. So I guess it should not be hard to > package it as a docker image. > > > > To be able to say to people: execute "docker run -p 8080:8080 > openwhisk/standalone" and enjoy... > > > > If it is possible I can volounteer to write the dockerfile do that... > > > > I have a question: does it use the local docker? Where is the > invoker? > > > > > > -- > > Michele Sciabarra > > mich...@sciabarra.com > > > > - Original message - > > From: Rodric Rabbah > > To: dev@openwhisk.apache.org > > Subject: Re: OpenWhisk as a single docker image? > > Date: Saturday, November 09, 2019 2:31 PM > > > > Do you mean the standalone controller? > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fopenwhisk%2Fblob%2Fmaster%2Fcore%2Fstandalone%2FREADME.mddata=02%7C01%7Ctnorris%40adobe.com%7Cfc313c39337a44a5882a08d7651a0cbc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637089034867332217sdata=OCnWo8R5OfbKLaSQCEeI%2B7pqz0ewp%2BYQGBK2msMoMtc%3Dreserved=0 > > > > -r > > > > > On Nov 9, 2019, at 8:18 AM, Michele Sciabarra < > mich...@sciabarra.com> wrote: > > > > > > Hello all, > > > > > > I remember the discussion about the openwhisk as a single > executable that includes also Kafka. So I wonder: is it now possible to run > (for development purposes of course) OpenWhisk as single docker image if we > add also couchdb to that one? Because I have an use case where even a > docker-compose can be inconvenient... > > > > > > -- > > > Michele Sciabarra > > > mich...@sciabarra.com > > > > > > > -- > Matt Sicker >
Re: OpenWhisk as a single docker image?
Docker in Docker has some slight security improvements depending on your use case, too, compared to just mounting your docker socket into the running container. On Sat, 9 Nov 2019 at 10:30, Tyson Norris wrote: > > I suspect that due to Docker-in-Docker scenario, it will be easier to use > java+jar (+local docker) instead of running the jar in a container. > > Today you can start the jar with only java , but you will need a bunch > of parameters (probably different per OS?) to run it in a container, I think. > Local docker client is switched per OS here > https://github.com/apache/openwhisk/blob/231e739373ef681c44b5647a6956d5838a87db2e/core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/docker/StandaloneDockerContainerFactory.scala#L37 > I guess this wouldn't apply if running in a container, but it arguably makes > running the jar simpler than running the container IMHO. > I also suspect you won't get the behavior of launching playground ui to > browser either, which I would miss. > > Tyson > > On 11/9/19, 5:38 AM, "Michele Sciabarra" wrote: > > Wow. I missed those evolutions. So I guess it should not be hard to > package it as a docker image. > > To be able to say to people: execute "docker run -p 8080:8080 > openwhisk/standalone" and enjoy... > > If it is possible I can volounteer to write the dockerfile do that... > > I have a question: does it use the local docker? Where is the invoker? > > > -- > Michele Sciabarra > mich...@sciabarra.com > > - Original message ----- > From: Rodric Rabbah > To: dev@openwhisk.apache.org > Subject: Re: OpenWhisk as a single docker image? > Date: Saturday, November 09, 2019 2:31 PM > > Do you mean the standalone controller? > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fopenwhisk%2Fblob%2Fmaster%2Fcore%2Fstandalone%2FREADME.mddata=02%7C01%7Ctnorris%40adobe.com%7Cfc313c39337a44a5882a08d7651a0cbc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637089034867332217sdata=OCnWo8R5OfbKLaSQCEeI%2B7pqz0ewp%2BYQGBK2msMoMtc%3Dreserved=0 > > -r > > > On Nov 9, 2019, at 8:18 AM, Michele Sciabarra > wrote: > > > > Hello all, > > > > I remember the discussion about the openwhisk as a single executable > that includes also Kafka. So I wonder: is it now possible to run (for > development purposes of course) OpenWhisk as single docker image if we add > also couchdb to that one? Because I have an use case where even a > docker-compose can be inconvenient... > > > > -- > > Michele Sciabarra > > mich...@sciabarra.com > > -- Matt Sicker
Re: OpenWhisk as a single docker image?
I suspect that due to Docker-in-Docker scenario, it will be easier to use java+jar (+local docker) instead of running the jar in a container. Today you can start the jar with only java , but you will need a bunch of parameters (probably different per OS?) to run it in a container, I think. Local docker client is switched per OS here https://github.com/apache/openwhisk/blob/231e739373ef681c44b5647a6956d5838a87db2e/core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/docker/StandaloneDockerContainerFactory.scala#L37 I guess this wouldn't apply if running in a container, but it arguably makes running the jar simpler than running the container IMHO. I also suspect you won't get the behavior of launching playground ui to browser either, which I would miss. Tyson On 11/9/19, 5:38 AM, "Michele Sciabarra" wrote: Wow. I missed those evolutions. So I guess it should not be hard to package it as a docker image. To be able to say to people: execute "docker run -p 8080:8080 openwhisk/standalone" and enjoy... If it is possible I can volounteer to write the dockerfile do that... I have a question: does it use the local docker? Where is the invoker? -- Michele Sciabarra mich...@sciabarra.com - Original message - From: Rodric Rabbah To: dev@openwhisk.apache.org Subject: Re: OpenWhisk as a single docker image? Date: Saturday, November 09, 2019 2:31 PM Do you mean the standalone controller? https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fopenwhisk%2Fblob%2Fmaster%2Fcore%2Fstandalone%2FREADME.mddata=02%7C01%7Ctnorris%40adobe.com%7Cfc313c39337a44a5882a08d7651a0cbc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637089034867332217sdata=OCnWo8R5OfbKLaSQCEeI%2B7pqz0ewp%2BYQGBK2msMoMtc%3Dreserved=0 -r > On Nov 9, 2019, at 8:18 AM, Michele Sciabarra wrote: > > Hello all, > > I remember the discussion about the openwhisk as a single executable that includes also Kafka. So I wonder: is it now possible to run (for development purposes of course) OpenWhisk as single docker image if we add also couchdb to that one? Because I have an use case where even a docker-compose can be inconvenient... > > -- > Michele Sciabarra > mich...@sciabarra.com
Re: OpenWhisk as a single docker image?
Wow. I missed those evolutions. So I guess it should not be hard to package it as a docker image. To be able to say to people: execute "docker run -p 8080:8080 openwhisk/standalone" and enjoy... If it is possible I can volounteer to write the dockerfile do that... I have a question: does it use the local docker? Where is the invoker? -- Michele Sciabarra mich...@sciabarra.com - Original message - From: Rodric Rabbah To: dev@openwhisk.apache.org Subject: Re: OpenWhisk as a single docker image? Date: Saturday, November 09, 2019 2:31 PM Do you mean the standalone controller? https://github.com/apache/openwhisk/blob/master/core/standalone/README.md -r > On Nov 9, 2019, at 8:18 AM, Michele Sciabarra wrote: > > Hello all, > > I remember the discussion about the openwhisk as a single executable that > includes also Kafka. So I wonder: is it now possible to run (for development > purposes of course) OpenWhisk as single docker image if we add also couchdb > to that one? Because I have an use case where even a docker-compose can be > inconvenient... > > -- > Michele Sciabarra > mich...@sciabarra.com
