Hi everyone,
This is to call for a vote for the release of Apache OpenWhisk
0.9.0-incubating: OpenWhisk Deploy Kube.
List of JIRA ticket(s) resolved for this release can be found at
https://issues.apache.org/jira/browse/INCUBATOR-219.
To learn more about Apache OpenWhisk, please visit
https:/
> A second idea that comes to my mind would be to implement a shared
counter (it can easily be eventually consistent, consistency is I think not
a concern here).
This is simply a drive-by comment, as I have not directly weighed in on the
rest of the discussion. But this comment about a shared coun
Hi,
Am Fr., 24. Aug. 2018 um 00:07 Uhr schrieb Tyson Norris
:
> > Router is not pulling at queue for "specific actions", just for any
> action
> > that might replace idle containers - right? This is complicated with
> > concurrency though since while a container is not idle (paused +
> Router is not pulling at queue for "specific actions", just for any action
> that might replace idle containers - right? This is complicated with
> concurrency though since while a container is not idle (paused +
> removable), it may be useable, but only if the action received is
I have verified all the bulletins in the checklist.
I vote +1 to release wskdeploy module.
Best wishes.
Vincent Hou (侯胜博)
Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud
Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address:
I have verified the checklist for both of the modules, and they are all fine.
I go with the vote +1 to release catalog and apigateway.
Best wishes.
Vincent Hou (侯胜博)
Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud
Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@u
I highly support the idea to start experimenting to help us make more
informed decisions vs basing decisions on assumptions.
Should we also agree on a performance goal (aside from the other goals you
called out ) ? I'm thinking at setting a performance goal i.e. run
X/requests per second on a mach
Hi Chetan,
The gpg: WARNING message is normal. The signature is fine based on the result.
Best wishes.
Vincent Hou (侯胜博)
Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud
Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4
Hi Justin,
Please be advised that this line of code:
https://github.com/apache/incubator-openwhisk-catalog/blob/master/tools/travis/build.sh#L66
VCAP_SERVICES_FILE="$(readlink -f $ROOTDIR/tests/credentials.json)"
The credentials are saved in credentials.json, which is generated by the Travis
fr
Hi OpenWhiskers,
We've been discussing a new direction for our architecture based on a
proposal I made here:
https://cwiki.apache.org/confluence/display/OPENWHISK/OpenWhisk+future+architecture
Discussion threads:
-
https://lists.apache.org/thread.html/29289006d190b2c68451f7625c13bb8020cc8e9928db6
Hi Dave,
I agree! I'll start another thread on a discussion of how/where we
prototype things to hash out some of the unknowns.
Cheers,
Markus
Am Do., 23. Aug. 2018 um 22:05 Uhr schrieb David P Grove :
>
> Related to the random vs. smart routing discussion.
>
> A key unknown that influences the
Hi Tyson,
Am Do., 23. Aug. 2018 um 21:28 Uhr schrieb Tyson Norris
:
> >
> > And each ContainerRouter has a queue consumer that presumably pulls
> from
> > the queue constantly? Or is consumption based on something else? If
> all
> > ContainerRouters are consuming at the same rate,
Related to the random vs. smart routing discussion.
A key unknown that influences the design is how much load we can drive
through a single ContainerRouter.
+ If they are highly scalable (500 to 1000 containers per router),
then even a fairly large OpenWhisk deployment could be running wi
I vote +1 Release as Apache OpenWhisk 0.9.0-incubating: apigateway
+1 Release as Apache OpenWhisk 0.9.0-incubating: catalog
- Justin
> On Aug 23, 2018, at 3:51 PM, David P Grove wrote:
>
> I vote:
> +1 Release as Apache OpenWhisk 0.9.0-incubating: apigateway
> +1 Release as Apache OpenWhisk 0.
I vote:
+1 Release as Apache OpenWhisk 0.9.0-incubating: apigateway
+1 Release as Apache OpenWhisk 0.9.0-incubating: catalog
Checklist for reference:
[X ] Download links are valid.
[X ] Checksums and PGP signatures are valid.
[X ] DISCLAIMER is included.
[X ] Source code artifacts have correct nam
I vote:
+1 Release as Apache OpenWhisk 0.9.0-incubating: wskdeploy
Checklist for reference:
[X ] Download links are valid.
[X ] Checksums and PGP signatures are valid.
[X ] DISCLAIMER is included.
[X ] Source code artifacts have correct names matching the current release.
[X ] LICENSE and
>
> And each ContainerRouter has a queue consumer that presumably pulls from
> the queue constantly? Or is consumption based on something else? If all
> ContainerRouters are consuming at the same rate, then while this does
> distribute the load across ContainerRouters, it doesn'
I vote +1!
- Justin
> On Aug 23, 2018, at 11:44 AM, Priti Desai wrote:
>
> Thanks Vincent.
>
> I vote +1 Release as Apache OpenWhisk 0.9.0-incubating: wskdeploy
>
> Checklist for reference:
> [X] Download links are valid.
> [ ] Checksums and PGP signatures are valid.
> [X] DISCLAIMER is inclu
I believe the uri feature is now under "fetch" [1] and makes use of Mesos
Fetcher [2]. This should mostly work for our usecase with below caveats
1. Where to host - Most likely S3 with IAM based secure access
2. Corelate running service config with one in S3 - In k8s case if there is
a change in C
Thanks Vincent.
I vote +1 Release as Apache OpenWhisk 0.9.0-incubating: wskdeploy
Checklist for reference:
[X] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[X] DISCLAIMER is included.
[X] Source code artifacts have correct names matching the current release.
[X] LICENSE a
Hi Chetan -
As mentioned in the linked DCOS issue, using a marathon "uri" for config files
(fetched before container is started) is an option - is there any reason that
won't work for us?
Files will end up in /mnt/mesos/sandbox in the container, not sure if that path
matters (we can copy the fi
+1 for release.
Minor issue around signature validation
$ gpg --verify openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz.asc
openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz
gpg: Signature made Tue Aug 21 02:45:00 2018 IST
gpg:using RSA key 72AF0CC22C4CF320
gpg: Good signatur
I vote +1
-Matt
matthew.ham...@gmail.com
On Thu, Aug 23, 2018 at 9:04 AM Bertrand Delacretaz
wrote:
> Hi,
>
> I'm surprised that nobody is voting on this - voting on releases is
> not only for mentors, it's an essential function of Apache projects
> that podlings need to practice. It's not har
Awesome!
I'm working on the matching PR for the kube-deploy repo now.
--dave
Christian Bickel wrote on 08/23/2018 05:11:56 AM:
> From: Christian Bickel
> To: dev@openwhisk.apache.org
> Date: 08/23/2018 05:12 AM
> Subject: Re: Proposal: Memory Aware Scheduling
>
> Hi everyone,
>
> The impleme
Great discussion; I'm not entirely convinced on part of this point though.
> We need a work-stealing queue here to dynamically rebalance between the
> Routers since the layer above the Routers has no idea about capacity and
> (at least that's my assumption) schedules randomly.
I agree we can't
Please vote on releasing this package as Apache OpenWhisk 0.9.8-incubating:
OpenWhisk wskdeploy.
The vote will be open for at least 72 hours.
[X] +1 Release as Apache OpenWhisk 0.9.0-incubating: wskdeploy
[ ] +0 no opinion
[ ] -1 Do not release and the reason
On 2018/08/21 03:03:45, "Vincent S
Hi,
On Tue, Aug 21, 2018 at 5:04 AM Vincent S Hou wrote:
> The source code artifact of openwhisk wskdeploy can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.8-incubating-rc1/openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz
+1 for this release,
Hi,
I'm surprised that nobody is voting on this - voting on releases is
not only for mentors, it's an essential function of Apache projects
that podlings need to practice. It's not hard ;-)
Not much fun either maybe, but
https://blogs.apache.org/foundation/entry/success-at-apache-the-apache1
help
> How will this impact other deployment tools, like Docker Compose? I'm
aware
that your change keeps the old path working, but do we envision to drop
that at some point?
Docker compose can also make use of config mount to make config file
available. As to dropping support for current transformatio
Hi everyone,
The implementation of this proposal has just been merged with
https://github.com/apache/incubator-openwhisk/commit/5b3e0b6a334b78fc783a2cd655f0f30ea58a68e8.
Greetings
Christian
Am Do., 10. Mai 2018 um 13:36 Uhr schrieb Markus Thoemmes
:
>
> Thanks Dominic!
>
> Yep, that's exactly the
Hi Chetan,
Am Do., 23. Aug. 2018 um 10:28 Uhr schrieb Chetan Mehrotra <
chetan.mehro...@gmail.com>:
> > Is it possible to layer configurations with this? For example: If I
> create
> a `database.conf` and a `controller.conf`, is there a way to mount these in
> a way that they are both read and me
Hi Dominic,
this is certainly a good thought and would simplify debugging production
systems as well.
A rough and dirty idea for the uniqueness issue you mentioned:
What if we just append a suffix for each of the child ids (essentially they
are in a parent/child relationship). A simple example:
> Is it possible to layer configurations with this? For example: If I create
a `database.conf` and a `controller.conf`, is there a way to mount these in
a way that they are both read and merged by the specific component?
This should be possible as of now also. If file mount option is used [1]
then
Hi Tyson,
Am Do., 23. Aug. 2018 um 00:33 Uhr schrieb Tyson Norris
:
> Hi - thanks for the discussion! More inline...
>
> On 8/22/18, 2:55 PM, "Markus Thömmes" wrote:
>
> Hi Tyson,
>
> Am Mi., 22. Aug. 2018 um 23:37 Uhr schrieb Tyson Norris
> :
>
> > Hi -
> > >
> >
Hi Chetan,
good idea!
A bit of background on why it is how it is: When I implemented the approach
we're having today, the basic thought was to be able to detect on a quite
granular level what changes are needed to which components, even when they
share values. For example: In the Kubernetes case,
35 matches
Mail list logo
