Re: Adding Github app (Depend-a-bot) to Client JS SDK repo?

2019-07-01 Thread Carlos Santana 
The Github repos are managed by INFRA they are the only ones with admin. 

You need to open a JIRA ticket for the request. 

- Carlos Santana
@csantanapr

> On Jul 1, 2019, at 8:00 AM, Rodric Rabbah  wrote:
> 
> Hey James, I don't know the answer but can offer this anecdotal evidence. I
> attempted to add github app, and requested access for our apache repo over
> a week ago and nothing has happened in terms of approval. So I suspect
> without INFRA's help, the request falls on the floor.
> 
> -r
> 
>> On Mon, Jul 1, 2019 at 9:50 AM James Thomas  wrote:
>> 
>> Hello Whiskers.
>> 
>> If I want to add a Github app to one of our repos - do I just need to open
>> a JIRA ticket with Infra? Does anyone know if there are any rules about
>> what apps are allowed?
>> 
>> I'm continuing work[1] on updating the project dependencies for the Client
>> JS SDK, which had not been updated for a long time. I want to make sure
>> this doesn't happen again and add a Github app to send PRs each time a
>> major dependency upgrade is available using Depend-a-bot:
>> https://github.com/marketplace/dependabot-preview
>> 
>> Does anyone have any issues with this?
>> 
>> [1] - https://github.com/apache/incubator-openwhisk-client-js/pull/180
>> --
>> Regards,
>> James Thomas
>>

Re: Re: automated builds of all runtimes now publishing using `nightly`

2019-07-01 Thread Matt Rutkowski 
Dave,

You're the best!

Kind regards,
Matt




From:   Matt Sicker 
To: dev@openwhisk.apache.org
Date:   07/01/2019 04:40 PM
Subject:[EXTERNAL] Re: automated builds of all runtimes now 
publishing using `nightly`



Fantastic, thanks for handling this!

On Sun, 30 Jun 2019 at 06:19, David P Grove  wrote:
>
>
>
> The travis setup for all the runtime repos has been changed to use the
> nightly tag to indicate the most recent build from the master branch.
>
> I've submitted a PR to update runtimes.json for core repo's master 
branch
> accordingly [1].
>
> My plan is that 48 hours after [1] merges, I will go through all the
> runtime images on dockerhub and change the latest tag to refer to the 
image
> that was built from the last official release (1.13.0-incubating).  In 
some
> cases (due to image naming convention changes after the 
1.13.0-incubating
> release), there is no such tag.  I believe in most (all?) cases I can
> simply do some docker operations to publish the appropriate version of 
the
> old-style name image under the new-style name with the 1.13.0-incubating
> tag.
>
> --dave
>
> [1] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_incubator-2Dopenwhisk_pull_4529&d=DwIBaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=6zQLM7Gc0Sv1iwayKOKa4_SFxRIxS478q2gZlAJj4Zw&m=TCGf8zwqExer_aEt3hJd5e7UakbpZJQQA9PtUUQUvJE&s=3tnNo1L-7l8N4K9bgs2_7UDDwblXOYJiEchLZMxO5uQ&e=
 




-- 
Matt Sicker

Re: automated builds of all runtimes now publishing using `nightly`

2019-07-01 Thread Matt Sicker 
Fantastic, thanks for handling this!

On Sun, 30 Jun 2019 at 06:19, David P Grove  wrote:
>
>
>
> The travis setup for all the runtime repos has been changed to use the
> nightly tag to indicate the most recent build from the master branch.
>
> I've submitted a PR to update runtimes.json for core repo's master branch
> accordingly [1].
>
> My plan is that 48 hours after [1] merges, I will go through all the
> runtime images on dockerhub and change the latest tag to refer to the image
> that was built from the last official release (1.13.0-incubating).  In some
> cases (due to image naming convention changes after the 1.13.0-incubating
> release), there is no such tag.  I believe in most (all?) cases I can
> simply do some docker operations to publish the appropriate version of the
> old-style name image under the new-style name with the 1.13.0-incubating
> tag.
>
> --dave
>
> [1] https://github.com/apache/incubator-openwhisk/pull/4529



-- 
Matt Sicker

Re: api gateway with standalone controller

2019-07-01 Thread Rodric Rabbah 
Thanks Dragos.

The resolver contents are:

bash-4.4# cat  "/etc/api-gateway/conf.d/includes/resolvers.conf"
resolver 192.168.65.1;


I'm trying to run the API gateway along with the standalone controller. I
started the gateway with "wskdev apigw", and using
http://host.docker.internal:3233 as my openwhisk API host for the wsk CLi.

-r


On Thu, Jun 27, 2019 at 11:28 AM Dascalita Dragos 
wrote:

> Rodric, are you running a custom api gateway container ?
> The lines at [1] should fix the issue for you.
>
> NGINX has its own internal DNS resolution for performance considerations.
> I'm curios what the content of
> "/etc/api-gateway/conf.d/includes/resolvers.conf"
>  is inside the apigateway container.
>
> Also, in case you use a custom configuration file for OW, it's possible
> that the config doesn't include "resolvers.conf" and hence the DNS
> resolution doesn't work ?
>
> [1] -
>
> https://github.com/apache/incubator-openwhisk-apigateway/blob/master/init.sh#L58-L59
>
> On Wed, Jun 26, 2019 at 5:28 PM Rodric Rabbah  wrote:
>
> > I tried to use the api gateway with the standalone controller and ran
> into
> > a few issues which I'll document in the relevant docs soon. I'm now
> hitting
> > an issue where the api gateway cannot resolve the host for routing a
> > request.
> >
> > I opened
> > https://github.com/apache/incubator-openwhisk-apigateway/issues/345
> > to summarize the findings. I created an API successfully which when I
> curl
> > fails in the gateway because it can't resolve the upstream host.
> >
> > I can nslookup/ping the stanalone controller from the api gateay
> container,
> > and I can successfully the webaction URL from the api gateway container
> as
> > well.
> >
> > How does the API gateway resolve a hostname and where is that code?
> Thanks
> > for the help.
> >
> > -r
> >
>

Re: Adding Github app (Depend-a-bot) to Client JS SDK repo?

2019-07-01 Thread Rodric Rabbah 
Hey James, I don't know the answer but can offer this anecdotal evidence. I
attempted to add github app, and requested access for our apache repo over
a week ago and nothing has happened in terms of approval. So I suspect
without INFRA's help, the request falls on the floor.

-r

On Mon, Jul 1, 2019 at 9:50 AM James Thomas  wrote:

> Hello Whiskers.
>
> If I want to add a Github app to one of our repos - do I just need to open
> a JIRA ticket with Infra? Does anyone know if there are any rules about
> what apps are allowed?
>
> I'm continuing work[1] on updating the project dependencies for the Client
> JS SDK, which had not been updated for a long time. I want to make sure
> this doesn't happen again and add a Github app to send PRs each time a
> major dependency upgrade is available using Depend-a-bot:
> https://github.com/marketplace/dependabot-preview
>
> Does anyone have any issues with this?
>
> [1] - https://github.com/apache/incubator-openwhisk-client-js/pull/180
> --
> Regards,
> James Thomas
>

Adding Github app (Depend-a-bot) to Client JS SDK repo?

2019-07-01 Thread James Thomas 
Hello Whiskers.

If I want to add a Github app to one of our repos - do I just need to open
a JIRA ticket with Infra? Does anyone know if there are any rules about
what apps are allowed?

I'm continuing work[1] on updating the project dependencies for the Client
JS SDK, which had not been updated for a long time. I want to make sure
this doesn't happen again and add a Github app to send PRs each time a
major dependency upgrade is available using Depend-a-bot:
https://github.com/marketplace/dependabot-preview

Does anyone have any issues with this?

[1] - https://github.com/apache/incubator-openwhisk-client-js/pull/180
-- 
Regards,
James Thomas

Re: [VOTE] Release Apache OpenWhisk Catalog (v0.10.0-incubating, rc1)

2019-07-01 Thread James Thomas 
+1

  [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 NOTICE files are correct for each OpenWhisk repository.
  [x] All files have license headers as specified by OpenWhisk project
policy [1].
  [x] No compiled archives bundled in source archive.

On Mon, 1 Jul 2019 at 05:37, Dominic Kim  wrote:

> +1
>
>  [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 NOTICE files are correct for each OpenWhisk repository.
>   [x] All files have license headers as specified by OpenWhisk project
> policy [1].
>   [x] No compiled archives bundled in source archive.
>
> 2019년 7월 1일 (월) 오전 9:33, Carlos Santana 님이 작성:
>
> > +1
> >
> >   [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 NOTICE files are correct for each OpenWhisk repository.
> >   [x] All files have license headers as specified by OpenWhisk project
> > policy [1].
> >   [x] No compiled archives bundled in source archive.
> >
> > On Sun, Jun 30, 2019 at 6:20 PM Rodric Rabbah  wrote:
> >
> > > +1
> > >
> > >   [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 NOTICE files are correct for each OpenWhisk
> repository.
> > >   [x] All files have license headers as specified by OpenWhisk project
> > > policy [1].
> > >   [x] No compiled archives bundled in source archive.
> > >
> > > On Sun, Jun 30, 2019 at 3:34 PM David P Grove 
> wrote:
> > >
> > > >
> > > >
> > > > Hi,
> > > >
> > > > This is a call to vote on releasing version 0.10.0-incubating release
> > > > candidate rc1 of the following project module with artifacts built
> from
> > > the
> > > > Git repositories and commit IDs listed below.
> > > >
> > > > * OpenWhisk Catalog: cb8d5c73
> > > >
> > https://github.com/apache/incubator-openwhisk-catalog/commits/cb8d5c73
> > > >
> > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-catalog-0.10.0-incubating-sources.tar.gz
> > > >
> > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-catalog-0.10.0-incubating-sources.tar.gz.asc
> > > >
> > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-catalog-0.10.0-incubating-sources.tar.gz.sha512
> > > >
> > > > This release is comprised of source code distribution only.
> > > >
> > > > You can use this UNIX script to download the release and verify the
> > > > checklist below:
> > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=incubator-openwhisk-release.git;a=blob_plain;f=tools/rcverify.sh;hb=HEAD
> > > >
> > > > Usage:
> > > > curl -s "
> > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=incubator-openwhisk-release.git;a=blob_plain;f=tools/rcverify.sh;hb=HEAD
> > > > " -o rcverify.sh
> > > > chmod +x rcverify.sh
> > > > rcverify.sh openwhisk-catalog 'OpenWhisk Catalog' 0.10.0-incubating
> rc1
> > > >
> > > > Please vote to approve this release:
> > > >
> > > >   [ ] +1 Approve the release
> > > >   [ ]  0 Don't care
> > > >   [ ] -1 Don't release, because ...
> > > >
> > > > Release verification checklist for reference:
> > > >   [ ] Download links are valid.
> > > >   [ ] Checksums and PGP signatures are valid.
> > > >   [ ] DISCLAIMER is included.
> > > >   [ ] Source code artifacts have correct names matching the current
> > > > release.
> > > >   [ ] LICENSE and NOTICE files are correct for each OpenWhisk
> > repository.
> > > >   [ ] All files have license headers as specified by OpenWhisk
> project
> > > > policy [1].
> > > >   [ ] No compiled archives bundled in source archive.
> > > >
> > > > This majority vote is open for at least 72 hours.
> > > >
> > > >
> > > > [1]
> > > >
> > > >
> > >
> >
> https://github.com/apache/incubator-openwhisk-release/blob/master/docs/license_compliance.md
> > > >
> > >
> >
> >
> > --
> > Carlos Santana
> > 
> >
>


-- 
Regards,
James Thomas

Re: [DISCUSS] Final draft of project Charter and graduation Resolution

2019-07-01 Thread Bertrand Delacretaz 
On Thu, Jun 27, 2019 at 5:40 PM Matt Rutkowski  wrote:
> ...draft link: 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=115526932 ...

Looks good to me, thank you!

-Bertrand

[slack-digest] [2019-06-30] #general

2019-07-01 Thread OpenWhisk Team Slack 
2019-06-30 10:25:08 UTC - Adam Varsano: Hi, I've deployed openwhisk on 
kubernetes, how can I set environment variables to actions?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1561890308102300

2019-06-30 12:24:41 UTC - Rodric Rabbah: Hi @Adam Varsano you attach parameters 
to actions via the cli using the -p parameter. All parameters become input to 
the main function.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1561897481104100?thread_ts=1561897481.104100&cid=C3TPCAQG1

2019-06-30 12:26:02 UTC - Rodric Rabbah: Here’s a recent discussion on the 
Apache dev list that might be if interest given your question  

https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1561897562105000

2019-06-30 12:49:27 UTC - Adam Varsano: Hi, thanks for replying,
you mean on creation of the actions I should pass -p parameter?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1561898967105100?thread_ts=1561897481.104100&cid=C3TPCAQG1

2019-06-30 12:54:26 UTC - Rodric Rabbah: yes `wsk action create actionName 
actionSourceFile -p MY_PARAM some_value` then you will see `{ MY_PARAM: 
some_value }` as the argument to your action’s main function.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1561899266105300?thread_ts=1561897481.104100&cid=C3TPCAQG1

2019-06-30 12:55:07 UTC - Rodric Rabbah: later you can `wsk action update 
actionName -p MY_PARAM some_value -p ANOTHER_PARAM some_value` to attach more 
parameters or change existing ones
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1561899307105500?thread_ts=1561897481.104100&cid=C3TPCAQG1

2019-06-30 12:58:45 UTC - Adam Varsano: I found this library of env vars:


usually you get env vars by typing os.Getenv
with your solution is it still work?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1561899525105900?thread_ts=1561897481.104100&cid=C3TPCAQG1

2019-06-30 13:00:05 UTC - Rodric Rabbah: not today because openwhisk does not 
export any parameters to the environment (the discussion on the dev list above 
would change that)
you wouldn’t need godotenv since the parameters are directly available in your 
“main” function
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1561899605106100?thread_ts=1561897481.104100&cid=C3TPCAQG1

2019-06-30 13:00:42 UTC - Rodric Rabbah: are you writing a go function?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1561899642106300?thread_ts=1561897481.104100&cid=C3TPCAQG1

2019-06-30 13:03:22 UTC - Rodric Rabbah: if so it would be something like
```
func Main(args map[string]interface{}) map[string]interface{} {
 MY_PARAM, _ := args["MY_PARAM"].(string)
 ...
}
```
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1561899802106500?thread_ts=1561897481.104100&cid=C3TPCAQG1

2019-06-30 13:11:22 UTC - Adam Varsano: I'm writing go functions yes
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1561900282106900?thread_ts=1561897481.104100&cid=C3TPCAQG1

[slack-digest] [2019-06-30] #apigateway

2019-07-01 Thread OpenWhisk Team Slack 
2019-06-30 19:50:46 UTC - Dave Grove: fyi, apigateway travis jobs have been 
failing for 3 days. Looks like the problem is an upstream publishing screwup of 
`busted`.  Will hopefully get resolved upstream without fixes on our part.   

thankyou : Carlos Santana
https://openwhisk-team.slack.com/archives/C3TP33Y2U/p1561924246001700