date:20180301

Re: Release policy compliance: Adding license headers and the excluded files

2018-03-01 Thread Ying Chun Guo

Hi, Matt

I tested. The answer is NO. Apache Rat cannot recognize short header format.
That will cause a problem because the large size of action files will slow down 
the tests running.
We can ignore these files till Rat supports short header format.

Best regards
Ying Chun Guo (Daisy)


-"Matt Rutkowski"  wrote: -

>To: dev@openwhisk.apache.org
>From: "Matt Rutkowski" 
>Date: 02/12/2018 11:53PM
>Subject: Re: Release policy compliance: Adding license headers and
>the excluded files
>
>Is there any way for the RAT tool to acknowledge the "minified" ASF
>header 
>that is approved for use in .js (and other files)?
>
>See "short form" approved here: 
>https://urldefense.proofpoint.com/v2/url?u=https-3A__www.apache.org_l
>egal_src-2Dheaders.html=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=V_NQebMEs
>ahq0wRsMMLN8VHG-pcqPRpdHygvo4rmK4o=V06q35OiWjYJAWe2jq-3fSk7CreRb6Ah
>wORWCs2KSJw=iNii7yGWwSTIBwziwicIhtKB91LCc5XgQpmAu_bTb9k=
>
>Kind regards,
>Matt 
>
>
>
>
>From: "Ying Chun Guo" 
>To: dev@openwhisk.apache.org
>Date: 02/12/2018 08:18 AM
>Subject: Re: Release policy compliance: Adding license headers
>and 
>the excluded files
>
>
>
>Hi, Bertrand
>
>Thank you for the inputs.
>
>My original thought was to maintain different Rat exclusions for
>different 
>repo because they may have different files. If we want to maintain a 
>unique version, we may need to collect all exclusions in all the repo
>
>together and maintain a set. Sometimes it's difficult to tell whether
>a 
>file shall be excluded or not. Hope you can help review after the 
>collection is ready. 
>
>OpenWhisk has a repo in github to track release documents and
>scripts.
>Here it is: 
>https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apach
>e_incubator-2Dopenwhisk-2Drelease_blob_master_README.md=DwIFaQ=jf
>_iaSHvJObTbx-siA1ZOg=6zQLM7Gc0Sv1iwayKOKa4_SFxRIxS478q2gZlAJj4Zw=
>tuRJI4eVUHlqHACnIGwvLgDqy1D9dIaSeLjOME3KJJg=RqfPKNiDPwlE1yljo6i5Rct
>CRB6jXLLbQ5gickneycE=
>. I think these information can be documented here: 
>https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apach
>e_incubator-2Dopenwhisk-2Drelease_blob_master_docs_work-5Fitems.md-23
>2-2Dverify-2Dthe-2Dcompliance-2Dof-2Dthe-2Dsource-2Dcode-2Dopen-2Diss
>ue=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=6zQLM7Gc0Sv1iwayKOKa4_SFxRIxS4
>78q2gZlAJj4Zw=tuRJI4eVUHlqHACnIGwvLgDqy1D9dIaSeLjOME3KJJg=t34yGdw
>cAE-qLfsKcS0ueeVqUAffslBtsP_kxQmK2fk=
>.
>
>Best regards
>Ying Chun Guo (Daisy)
>
>
>-Bertrand Delacretaz  wrote: -
>To: dev@openwhisk.apache.org
>From: Bertrand Delacretaz 
>Date: 02/09/2018 06:41PM
>Subject: Re: Release policy compliance: Adding license headers and
>the 
>excluded files
>
>Hi Daisy,
>
>On Thu, Feb 8, 2018 at 1:24 PM, Ying Chun Guo 
>wrote:
>> ...I use Apache Rat to audit license headers. I use wskdeploy repo
>as 
>the trial repo.
>> I reported an issue (
>https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apach
>e_incubator-2Dopenwhisk-2Dwskdeploy_issues_716=DwIBaQ=jf_iaSHvJOb
>Tbx-siA1ZOg=V_NQebMEsahq0wRsMMLN8VHG-pcqPRpdHygvo4rmK4o=m3ygIAacP
>w2tdx9MhWLfpLzsW1V32RO3z5g6A2YFWCo=zY3fWnnLVXjHDVQvYS73Db0ljWoQg4Oa
>YlqNm1mbjWE=
>)
>> to wskdeploy including a report generated by Apache Rat. In the
>report, 
>all the files
>> with unapproved licenses will be listed...
>
>This sounds great.
>
>What you want basically is that for any build that's meant to create
>a 
>release:
>
>-Rat should run
>-The build should fail if Rat reports any anomalies
>-The Rat exclusions should ideally be defined in the same way for all
>modules, for consistency
>-The Rat exclusions should be commented to indicate why each
>exclusion
>(or family of exclusions) is here
>
>I think this should be documented in a "coding standards" or "release
>management" page, does OpenWhisk have this already?
>
>-Bertrand (with my incubation mentor hat on)
>
>
>
>
>
>
>

Re: Install Api Gateway in dcos

2018-03-01 Thread Dragos Dascalita Haut

"...Is there any place I have to define the url?..."

We usually configure a DNS entry like *.gw. and have it pointing 
to the LB for the Public Mesos Agents. The Gateway then looks at the Host 
header and routes to the specific Marathon app.

"...DC/OS VERSION: 1.9.4..."

Are you planning to run Kafka inside the cluster ? We had some issues and 
upgraded to 1.9.6.

Thanks,
dragos

From: Kumar Subramanian 
Sent: Thursday, March 1, 2018 9:27:45 AM
To: dev@openwhisk.apache.org
Cc: d...@openwhisk.incubator.apache.org
Subject: Re: Install Api Gateway in dcos

Hi Dragos,
I am not sure I understood your point about “Note that by default the 
Gateway listens on this domain defined in config
at [2] ( .gw.). Once the 
controller is
installed in the cluster, it's accessible on 
controller.gw.,
assuming the Marathon app name for the OpenWhisk Controller is called
"controller" “

apigateway is the first app that I tried to install on DCOS. Is there any place 
I have to define the url? (( .gw.) and may 
be I am missing that? The only Url I mentioned is the default one in the 
Environment settings of apigateway package (during installation). The default 
value was 
"default":https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarathon.mesos%3A8080=02%7C01%7Cddascal%40adobe.com%7C13c7e7acff6d4ca2527008d57f99c65f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636555220791160814=jqCRcem3GhT%2BChCsOiUI33YxQ5euJqECQfzeSf92yCE%3D=0;
 and I kept it as is when installing.

Thanks,
Kumar.

On 3/1/18, 9:18 AM, "Kumar Subramanian"  wrote:

Hi Dragos,
Here is the DCOS Version
DC/OS VERSION: 1.9.4

Marathon Version: 1.4.7

Thanks,
Kumar.

On 2/28/18, 11:10 PM, "Dascalita Dragos"  wrote:

Hi Kumar,
Can you provide details on the DCOS version as well ?

*"...The (api gateway) service status shows waiting and there are no 
logs;
nothing getting deployed also"*
Depending on the DCOS version, you may find in the DCOS UI debug
information in regards to the resource offered by Mesos and what's 
missing.
[1] It's possible that some constraints are not matched, and Marathon is
still waiting to get offers, which would explain this effect you're 
seeing.
Note that by default the Gateway listens on this domain defined in 
config
at [2] ( .gw.). Once the 
controller is
installed in the cluster, it's accessible on 
controller.gw.,
assuming the Marathon app name for the OpenWhisk Controller is called
"controller". Same goes for the "invoker": 
invoker.gw..
Same for Exhibitor, CouchDB etc, any other app installed in the cluster 
is
exposed in this way. Of course, these domain names can be easily 
configured
differently in NGINX, I'm just explaining the default rules.

We might have to provide a DCOS universe for 1.9 or 1.10 as well. We've
tested with both versions successfully; we need to strip customizations
particular to our deployment, prior to sharing the updated universe.

HTH,
Dragos

[1] - 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__docs.mesosphere.com_1.10_monitoring_debugging_gui-2Ddebugging_%26d%3DDwIFaQ%26c%3DuilaK90D4TOVoH58JNXRgQ%26r%3DF5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo%26m%3DPq6qbuCjIV0NgXrQUGgzHlpwkfQ1iR-hlycfGmbR5_4%26s%3D67DJMsbbLqbhR82ScYfqZ6g-hvjuOMnMeGOq-M6zmFQ%26e=02%7C01%7Cddascal%40adobe.com%7C13c7e7acff6d4ca2527008d57f99c65f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636555220791160814=HrhKFD6hNFtAHbQ%2BIc%2F2%2FNz4eOGlRvFblXBG5YRFtzc%3D=0=
[2] -

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__github.com_adobe-2Dapiplatform_apigateway_blob_master_api-2Dgateway-2Dconfig_conf.d_marathon-5Fapis.conf-23L35%26d%3DDwIFaQ%26c%3DuilaK90D4TOVoH58JNXRgQ%26r%3DF5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo%26m%3DPq6qbuCjIV0NgXrQUGgzHlpwkfQ1iR-hlycfGmbR5_4%26s%3D6BVUN80-tqxdqO0yYyI2IuXRoe5XKGEUUwhJhjD8J-o%26e=02%7C01%7Cddascal%40adobe.com%7C13c7e7acff6d4ca2527008d57f99c65f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636555220791160814=7FXGWVCediKn4vRUuely%2BbquelFxHl3xvYaa97KOBJA%3D=0=

On Wed, Feb 28, 2018 at 6:08 PM Carlos Santana  
wrote:

> Hi Kumar welcome to list
>
>   Adobe team is currently deploying OpenWhisk on DCOS/Mesos I bet one 
of
> them will be able to assist you on this task and point you int he 
right
> direction
>
> The file you point is no longer on the repo, Maybe  Dragos or Tyson 
could
> also clarify that and the apigateway issues.
>
> -- Carlos
>
> On Wed, Feb

Podling Report Reminder - March 2018

2018-03-01 Thread johndament

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 21 March 2018, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, March 07).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://wiki.apache.org/incubator/March2018

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: Install Api Gateway in dcos

2018-03-01 Thread Tyson Norris

On Mar 1, 2018, at 12:30 PM, Kumar Subramanian 
> wrote:

Hi Tyson/Dragos,
I was able to progress and install apiGateway. The change I made was to the 
config; specifically the “acceptedResourceRoles”: [“slave_public”]; I set this 
to null and I was able to deploy the apiGateway Successfully.

Question: Is it necessary to set the value to “slave_public” ?

This depends on your cluster config and how you want to expose the apigateway 
to public users that should not have other access to your cluster.

See https://docs.mesosphere.com/1.9/deploying-services/expose-service/

Tyson

Thanks,
Kumar.

On 3/1/18, 12:18 PM, "Tyson Norris" 
> wrote:

   Ok, you might want to verify your agents are running properly, with the 
resource attributes that you expect.

   On the mesos ui, click the “Agents” nav at the top, and verify the 
apigateway resource requirements can be satisfied (default is 0.5 cpu, 256MB 
memory, and constraint for unique hostname)

On Mar 1, 2018, at 11:09 AM, Kumar Subramanian 
> wrote:

Hi Tyson,

Under Debug>>Recent Resource Offers, I only see “Rejected offer analysis is not 
currently supported.” Also on the /mesos pages >> Offers (tab), the table 
contents is empty.

Thanks,

Kumar.

On 3/1/18, 10:29 AM, "Tyson Norris" 
> wrote:

  Hi Kumar -

  If it is stuck in “waiting” status check the debug page for that service in 
DCOS gui 
(https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.proofpoint.com-252Fv2-252Furl-253Fu-253Dhttps-2D3A-5F-5Fdocs.mesosphere.com-5F1.10-5Fmonitoring-5Fdebugging-5Fgui-2D2Ddebugging-5F-2526d-253DDwIGaQ-2526c-253DuilaK90D4TOVoH58JNXRgQ-2526r-253DF5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo-2526m-253DPMpLWk-2DomxV9OEMjTizFWDKWJNG85Nf-2DIsvoagjL6X4-2526s-253DTOHffBumq67TyI2YR7oFirrjGztyjBTa1J6kJinwv6I-2526e-26data-3D02-257C01-257Ctnorris-2540adobe.com-257Cb9a19b0d304c4775a32808d57fa7fc19-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636555281818017113-26sdata-3D1RzoZScZnamq-252FZWEImlDNYqAfloLWjcjNCv7vG2hu0Y-253D-26reserved-3D0-3D%26d%3DDwIGaQ%26c%3DuilaK90D4TOVoH58JNXRgQ%26r%3DF5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo%26m%3D5Fs4kuHy5ihfjroTdU5Q1qPItydbH9BE5-9DnJmknUU%26s%3D585OO58K8U6ikUcmpojqPLXUwLI-0Ukoft-Cs6KuOfE%26e=02%7C01%7Ctnorris%40adobe.com%7Ca5af1f458b8845a506f808d57fb351ec%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636555330503435891=AVvEzBIYC0ar%2BEl3oKD5wW2wLB2wG9lFC8J09YTy1So%3D=0=)
 to see why offers are not matching.

  Tyson

  On Mar 1, 2018, at 10:05 AM, Kumar Subramanian 
>
 wrote:

  Hi Dragos,

  One more information I noticed is that; as the apigateway status is in 
“waiting” status, the Error icon right next to it states “DC/OS has been 
waiting for resources and is unable to complete this deployment for XX minutes.

  Thanks,

  Kumar.

  On 3/1/18, 9:28 AM, "Kumar Subramanian" 
>
 wrote:

 Hi Dragos,

 I am not sure I understood your point about “Note that by default 
the Gateway listens on this domain defined in config

 at [2] ( .gw.). Once the 
controller is

 installed in the cluster, it's accessible on 
controller.gw.,

 assuming the Marathon app name for the OpenWhisk Controller is 
called

 "controller" “

 apigateway is the first app that I tried to install on DCOS. Is there any 
place I have to define the url? (( .gw.) 
and may be I am missing that? The only Url I mentioned is the default one in 
the Environment settings of apigateway package (during installation). The 
default value was

Re: Install Api Gateway in dcos

2018-03-01 Thread Kumar Subramanian

Hi Tyson/Dragos,
I was able to progress and install apiGateway. The change I made was to the 
config; specifically the “acceptedResourceRoles”: [“slave_public”]; I set this 
to null and I was able to deploy the apiGateway Successfully.

Question: Is it necessary to set the value to “slave_public” ?

Thanks,
Kumar.

On 3/1/18, 12:18 PM, "Tyson Norris"  wrote:

Ok, you might want to verify your agents are running properly, with the 
resource attributes that you expect. 

On the mesos ui, click the “Agents” nav at the top, and verify the 
apigateway resource requirements can be satisfied (default is 0.5 cpu, 256MB 
memory, and constraint for unique hostname)



> On Mar 1, 2018, at 11:09 AM, Kumar Subramanian  
wrote:

> 

> Hi Tyson,

> Under Debug>>Recent Resource Offers, I only see “Rejected offer analysis 
is not currently supported.” Also on the /mesos pages >> Offers (tab), the 
table contents is empty.

> 

> Thanks,

> Kumar.

> 

> On 3/1/18, 10:29 AM, "Tyson Norris"  wrote:

> 

>Hi Kumar -

> 

>If it is stuck in “waiting” status check the debug page for that 
service in DCOS gui 
(https://urldefense.proofpoint.com/v2/url?u=https-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.proofpoint.com-252Fv2-252Furl-253Fu-253Dhttps-2D3A-5F-5Fdocs.mesosphere.com-5F1.10-5Fmonitoring-5Fdebugging-5Fgui-2D2Ddebugging-5F-2526d-253DDwIGaQ-2526c-253DuilaK90D4TOVoH58JNXRgQ-2526r-253DF5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo-2526m-253DPMpLWk-2DomxV9OEMjTizFWDKWJNG85Nf-2DIsvoagjL6X4-2526s-253DTOHffBumq67TyI2YR7oFirrjGztyjBTa1J6kJinwv6I-2526e-26data-3D02-257C01-257Ctnorris-2540adobe.com-257Cb9a19b0d304c4775a32808d57fa7fc19-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636555281818017113-26sdata-3D1RzoZScZnamq-252FZWEImlDNYqAfloLWjcjNCv7vG2hu0Y-253D-26reserved-3D0-3D=DwIGaQ=uilaK90D4TOVoH58JNXRgQ=F5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo=5Fs4kuHy5ihfjroTdU5Q1qPItydbH9BE5-9DnJmknUU=585OO58K8U6ikUcmpojqPLXUwLI-0Ukoft-Cs6KuOfE=)
 to see why offers are not matching.

> 

> 

> 

>Tyson

> 

> 

> 

>On Mar 1, 2018, at 10:05 AM, Kumar Subramanian 
> wrote:

> 

> 

> 

>Hi Dragos,

> 

>One more information I noticed is that; as the apigateway status is in 
“waiting” status, the Error icon right next to it states “DC/OS has been 
waiting for resources and is unable to complete this deployment for XX minutes.

> 

> 

> 

>Thanks,

> 

>Kumar.

> 

> 

> 

>On 3/1/18, 9:28 AM, "Kumar Subramanian" 
> wrote:

> 

> 

> 

>   Hi Dragos,

> 

> 

> 

>   I am not sure I understood your point about “Note that by 
default the Gateway listens on this domain defined in config

> 

> 

> 

>   at [2] ( .gw.). Once 
the controller is

> 

> 

> 

>   installed in the cluster, it's accessible on 
controller.gw.,

> 

> 

> 

>   assuming the Marathon app name for the OpenWhisk Controller 
is called

> 

> 

> 

>   "controller" “

> 

> 

> 

> 

> 

> 

> 

>   apigateway is the first app that I tried to install on DCOS. Is 
there any place I have to define the url? (( 
.gw.) and may be I am missing that? The 
only Url I mentioned is the default one in the Environment settings of 
apigateway package (during installation). The default value was

Re: Install Api Gateway in dcos

2018-03-01 Thread Tyson Norris

Ok, you might want to verify your agents are running properly, with the 
resource attributes that you expect. 
On the mesos ui, click the “Agents” nav at the top, and verify the apigateway 
resource requirements can be satisfied (default is 0.5 cpu, 256MB memory, and 
constraint for unique hostname)

> On Mar 1, 2018, at 11:09 AM, Kumar Subramanian  
> wrote:
> 
> Hi Tyson,
> Under Debug>>Recent Resource Offers, I only see “Rejected offer analysis is 
> not currently supported.” Also on the /mesos pages >> Offers (tab), the table 
> contents is empty.
> 
> Thanks,
> Kumar.
> 
> On 3/1/18, 10:29 AM, "Tyson Norris"  wrote:
> 
>Hi Kumar -
> 
>If it is stuck in “waiting” status check the debug page for that service 
> in DCOS gui 
> (https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__docs.mesosphere.com_1.10_monitoring_debugging_gui-2Ddebugging_%26d%3DDwIGaQ%26c%3DuilaK90D4TOVoH58JNXRgQ%26r%3DF5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo%26m%3DPMpLWk-omxV9OEMjTizFWDKWJNG85Nf-IsvoagjL6X4%26s%3DTOHffBumq67TyI2YR7oFirrjGztyjBTa1J6kJinwv6I%26e=02%7C01%7Ctnorris%40adobe.com%7Cb9a19b0d304c4775a32808d57fa7fc19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636555281818017113=1RzoZScZnamq%2FZWEImlDNYqAfloLWjcjNCv7vG2hu0Y%3D=0=)
>  to see why offers are not matching.
> 
> 
> 
>Tyson
> 
> 
> 
>On Mar 1, 2018, at 10:05 AM, Kumar Subramanian 
> > wrote:
> 
> 
> 
>Hi Dragos,
> 
>One more information I noticed is that; as the apigateway status is in 
> “waiting” status, the Error icon right next to it states “DC/OS has been 
> waiting for resources and is unable to complete this deployment for XX 
> minutes.
> 
> 
> 
>Thanks,
> 
>Kumar.
> 
> 
> 
>On 3/1/18, 9:28 AM, "Kumar Subramanian" 
> > wrote:
> 
> 
> 
>   Hi Dragos,
> 
> 
> 
>   I am not sure I understood your point about “Note that by 
> default the Gateway listens on this domain defined in config
> 
> 
> 
>   at [2] ( .gw.). Once the 
> controller is
> 
> 
> 
>   installed in the cluster, it's accessible on 
> controller.gw.,
> 
> 
> 
>   assuming the Marathon app name for the OpenWhisk Controller is 
> called
> 
> 
> 
>   "controller" “
> 
> 
> 
> 
> 
> 
> 
>   apigateway is the first app that I tried to install on DCOS. Is there 
> any place I have to define the url? (( 
> .gw.) and may be I am missing that? The 
> only Url I mentioned is the default one in the Environment settings of 
> apigateway package (during installation). The default value was 
> "default":https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.proofpoint.com-252Fv2-252Furl-253Fu-253Dhttp-2D3A-5F-5Fmarathon.mesos-2D3A8080-2526d-253DDwIGaQ-2526c-253DuilaK90D4TOVoH58JNXRgQ-2526r-253DF5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo-2526m-253DSnzzg-2DsR6t5CY7El-5F-2DGNWwuD-5FWMAn1nbqP6taqWUSXo-2526s-253DztUsE0shjeKqrwdPc2TAGnBPCWlRPjo-5FHE9TL74FUcU-2526e-26data-3D02-257C01-257Ctnorris-2540adobe.com%26d%3DDwIGaQ%26c%3DuilaK90D4TOVoH58JNXRgQ%26r%3DF5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo%26m%3DPMpLWk-omxV9OEMjTizFWDKWJNG85Nf-IsvoagjL6X4%26s%3DtzvuX_C6QuK3rjJu7OFDRiN7_cfu4lSdlNGYNlLwahg%26e=02%7C01%7Ctnorris%40adobe.com%7Cb9a19b0d304c4775a32808d57fa7fc19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636555281818017113=o6y0ObDTz7VJvoFLYZvH8LYvosiUJuTkOsnCbngrs5o%3D=0=%7C4c8760a6baa149a4998608d57f9f015b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636555243255443290=g6fpgmaBZSJyuCkfuYx2fq%2FlUn%2BOTlu%2BfzI6XtuFt5Y%3D=0=;
>  and I kept it as is when installing.
> 
> 
> 
> 
> 
> 
> 
>   Thanks,
> 
> 
> 
>   Kumar.
> 
> 
> 
> 
> 
> 
> 
>   On 3/1/18, 9:18 AM, "Kumar Subramanian" 
> > wrote:
> 
> 
> 
> 
> 
> 
> 
>   Hi Dragos,
> 
> 
> 
>   Here is the DCOS Version
> 
> 
> 
>   DC/OS VERSION: 1.9.4
> 
> 
> 
> 
> 
> 
> 
>   Marathon Version: 1.4.7
> 
> 
> 
> 
> 
> 
> 
>   Thanks,
> 
> 
> 
>   Kumar.
> 
> 
> 
> 
> 
> 
> 
>   On 2/28/18, 11:10 PM, "Dascalita Dragos" 
> > wrote:
>

Re: Install Api Gateway in dcos

2018-03-01 Thread Kumar Subramanian

Hi Tyson,
Under Debug>>Recent Resource Offers, I only see “Rejected offer analysis is not 
currently supported.” Also on the /mesos pages >> Offers (tab), the table 
contents is empty.

Thanks,
Kumar.

On 3/1/18, 10:29 AM, "Tyson Norris"  wrote:

Hi Kumar -

If it is stuck in “waiting” status check the debug page for that service in 
DCOS gui 
(https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.mesosphere.com_1.10_monitoring_debugging_gui-2Ddebugging_=DwIGaQ=uilaK90D4TOVoH58JNXRgQ=F5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo=PMpLWk-omxV9OEMjTizFWDKWJNG85Nf-IsvoagjL6X4=TOHffBumq67TyI2YR7oFirrjGztyjBTa1J6kJinwv6I=)
 to see why offers are not matching.

Tyson

On Mar 1, 2018, at 10:05 AM, Kumar Subramanian 
> wrote:

Hi Dragos,

One more information I noticed is that; as the apigateway status is in 
“waiting” status, the Error icon right next to it states “DC/OS has been 
waiting for resources and is unable to complete this deployment for XX minutes.

Thanks,

Kumar.

On 3/1/18, 9:28 AM, "Kumar Subramanian" 
> wrote:

   Hi Dragos,

   I am not sure I understood your point about “Note that by 
default the Gateway listens on this domain defined in config

   at [2] ( .gw.). Once the 
controller is

   installed in the cluster, it's accessible on 
controller.gw.,

   assuming the Marathon app name for the OpenWhisk Controller is 
called

   "controller" “

   apigateway is the first app that I tried to install on DCOS. Is there 
any place I have to define the url? (( 
.gw.) and may be I am missing that? The 
only Url I mentioned is the default one in the Environment settings of 
apigateway package (during installation). The default value was 
"default":https://urldefense.proofpoint.com/v2/url?u=https-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.proofpoint.com-252Fv2-252Furl-253Fu-253Dhttp-2D3A-5F-5Fmarathon.mesos-2D3A8080-2526d-253DDwIGaQ-2526c-253DuilaK90D4TOVoH58JNXRgQ-2526r-253DF5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo-2526m-253DSnzzg-2DsR6t5CY7El-5F-2DGNWwuD-5FWMAn1nbqP6taqWUSXo-2526s-253DztUsE0shjeKqrwdPc2TAGnBPCWlRPjo-5FHE9TL74FUcU-2526e-26data-3D02-257C01-257Ctnorris-2540adobe.com=DwIGaQ=uilaK90D4TOVoH58JNXRgQ=F5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo=PMpLWk-omxV9OEMjTizFWDKWJNG85Nf-IsvoagjL6X4=tzvuX_C6QuK3rjJu7OFDRiN7_cfu4lSdlNGYNlLwahg=%7C4c8760a6baa149a4998608d57f9f015b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636555243255443290=g6fpgmaBZSJyuCkfuYx2fq%2FlUn%2BOTlu%2BfzI6XtuFt5Y%3D=0=;
 and I kept it as is when installing.

   Thanks,

   Kumar.

   On 3/1/18, 9:18 AM, "Kumar Subramanian" 
> wrote:

   Hi Dragos,

   Here is the DCOS Version

   DC/OS VERSION: 1.9.4

   Marathon Version: 1.4.7

   Thanks,

   Kumar.

   On 2/28/18, 11:10 PM, "Dascalita Dragos" 
> wrote:

   Hi Kumar,

   Can you provide details on the DCOS version as well ?

   *"...The (api gateway) service status shows waiting and there 
are no logs;

   nothing getting deployed also"*

   Depending on the DCOS version, you may find in the DCOS UI debug

   information in regards to the resource offered by Mesos and 
what's missing.

   [1] It's possible that some constraints are not matched, and 
Marathon is

   still waiting to get offers, which would explain this effect 
you're seeing.

   Note that by default the Gateway listens on this domain defined 
in config

   at [2] ( .gw.). Once the 
controller is

   installed in the cluster, it's accessible on 
controller.gw.,

   assuming the Marathon app name for the OpenWhisk Controller is 
called

Re: Install Api Gateway in dcos

2018-03-01 Thread Tyson Norris

Hi Kumar -
If it is stuck in “waiting” status check the debug page for that service in
DCOS gui (https://docs.mesosphere.com/1.10/monitoring/debugging/gui-debugging/)
to see why offers are not matching.

Tyson

On Mar 1, 2018, at 10:05 AM, Kumar Subramanian
> wrote:

Hi Dragos,
One more information I noticed is that; as the apigateway status is in
“waiting” status, the Error icon right next to it states “DC/OS has been
waiting for resources and is unable to complete this deployment for XX minutes.

Thanks,
Kumar.

On 3/1/18, 9:28 AM, "Kumar Subramanian"
> wrote:

Hi Dragos,

I am not sure I understood your point about “Note that by default
the Gateway listens on this domain defined in config

at [2] ( .gw.). Once the
controller is

installed in the cluster, it's accessible on
controller.gw.,

assuming the Marathon app name for the OpenWhisk Controller is called

"controller" “

apigateway is the first app that I tried to install on DCOS. Is there any
place I have to define the url? (( .gw.)
and may be I am missing that? The only Url I mentioned is the default one in
the Environment settings of apigateway package (during installation). The
default value was
"default":https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttp-3A__marathon.mesos-3A8080%26d%3DDwIGaQ%26c%3DuilaK90D4TOVoH58JNXRgQ%26r%3DF5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo%26m%3DSnzzg-sR6t5CY7El_-GNWwuD_WMAn1nbqP6taqWUSXo%26s%3DztUsE0shjeKqrwdPc2TAGnBPCWlRPjo_HE9TL74FUcU%26e=02%7C01%7Ctnorris%40adobe.com%7C4c8760a6baa149a4998608d57f9f015b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636555243255443290=g6fpgmaBZSJyuCkfuYx2fq%2FlUn%2BOTlu%2BfzI6XtuFt5Y%3D=0=;
and I kept it as is when installing.

Thanks,

Kumar.

On 3/1/18, 9:18 AM, "Kumar Subramanian"
> wrote:

Hi Dragos,

Here is the DCOS Version

DC/OS VERSION: 1.9.4

Marathon Version: 1.4.7

Thanks,

Kumar.

On 2/28/18, 11:10 PM, "Dascalita Dragos"
> wrote:

Hi Kumar,

Can you provide details on the DCOS version as well ?

*"...The (api gateway) service status shows waiting and there are no
logs;

nothing getting deployed also"*

Depending on the DCOS version, you may find in the DCOS UI debug

information in regards to the resource offered by Mesos and what's
missing.

[1] It's possible that some constraints are not matched, and
Marathon is

still waiting to get offers, which would explain this effect you're
seeing.

Note that by default the Gateway listens on this domain defined in
config

at [2] ( .gw.). Once the
controller is

installed in the cluster, it's accessible on
controller.gw.,

assuming the Marathon app name for the OpenWhisk Controller is called

"controller". Same goes for the "invoker":
invoker.gw..

Same for Exhibitor, CouchDB etc, any other app installed in the
cluster is

exposed in this way. Of course, these domain names can be easily
configured

differently in NGINX, I'm just explaining the default rules.

We might have to provide a DCOS universe for 1.9 or 1.10 as well.
We've

tested with both versions successfully; we need to strip
customizations

particular to our deployment, prior to sharing the updated universe.

HTH,

Dragos

[1] -
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__docs.mesosphere.com_1.10_monitoring_debugging_gui-2Ddebugging_%26d%3DDwIFaQ%26c%3DuilaK90D4TOVoH58JNXRgQ%26r%3DF5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo%26m%3DPq6qbuCjIV0NgXrQUGgzHlpwkfQ1iR-hlycfGmbR5_4%26s%3D67DJMsbbLqbhR82ScYfqZ6g-hvjuOMnMeGOq-M6zmFQ%26e=02%7C01%7Ctnorris%40adobe.com%7C4c8760a6baa149a4998608d57f9f015b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636555243255443290=juKGgSDAFtt0ci1tG%2BqQVJ9FP1c%2FFgRjSAb1i2H%2B4yk%3D=0=

[2] -

Re: Install Api Gateway in dcos

2018-03-01 Thread Kumar Subramanian

Hi Dragos,
One more information I noticed is that; as the apigateway status is in 
“waiting” status, the Error icon right next to it states “DC/OS has been 
waiting for resources and is unable to complete this deployment for XX minutes.

Thanks,
Kumar.

On 3/1/18, 9:28 AM, "Kumar Subramanian"  wrote:

Hi Dragos,

I am not sure I understood your point about “Note that by default 
the Gateway listens on this domain defined in config

at [2] ( .gw.). Once the 
controller is

installed in the cluster, it's accessible on 
controller.gw.,

assuming the Marathon app name for the OpenWhisk Controller is 
called

"controller" “

apigateway is the first app that I tried to install on DCOS. Is there any 
place I have to define the url? (( .gw.) 
and may be I am missing that? The only Url I mentioned is the default one in 
the Environment settings of apigateway package (during installation). The 
default value was 
"default":https://urldefense.proofpoint.com/v2/url?u=http-3A__marathon.mesos-3A8080=DwIGaQ=uilaK90D4TOVoH58JNXRgQ=F5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo=Snzzg-sR6t5CY7El_-GNWwuD_WMAn1nbqP6taqWUSXo=ztUsE0shjeKqrwdPc2TAGnBPCWlRPjo_HE9TL74FUcU=;
 and I kept it as is when installing.

Thanks,

Kumar.

On 3/1/18, 9:18 AM, "Kumar Subramanian"  wrote:

Hi Dragos,

Here is the DCOS Version

DC/OS VERSION: 1.9.4

Marathon Version: 1.4.7

Thanks,

Kumar.

On 2/28/18, 11:10 PM, "Dascalita Dragos"  wrote:

Hi Kumar,

Can you provide details on the DCOS version as well ?

*"...The (api gateway) service status shows waiting and there are 
no logs;

nothing getting deployed also"*

Depending on the DCOS version, you may find in the DCOS UI debug

information in regards to the resource offered by Mesos and what's 
missing.

[1] It's possible that some constraints are not matched, and 
Marathon is

still waiting to get offers, which would explain this effect you're 
seeing.

Note that by default the Gateway listens on this domain defined in 
config

at [2] ( .gw.). Once the 
controller is

installed in the cluster, it's accessible on 
controller.gw.,

assuming the Marathon app name for the OpenWhisk Controller is 
called

"controller". Same goes for the "invoker": 
invoker.gw..

Same for Exhibitor, CouchDB etc, any other app installed in the 
cluster is

exposed in this way. Of course, these domain names can be easily 
configured

differently in NGINX, I'm just explaining the default rules.

We might have to provide a DCOS universe for 1.9 or 1.10 as well. 
We've

tested with both versions successfully; we need to strip 
customizations

particular to our deployment, prior to sharing the updated universe.

HTH,

Dragos

[1] - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.mesosphere.com_1.10_monitoring_debugging_gui-2Ddebugging_=DwIFaQ=uilaK90D4TOVoH58JNXRgQ=F5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo=Pq6qbuCjIV0NgXrQUGgzHlpwkfQ1iR-hlycfGmbR5_4=67DJMsbbLqbhR82ScYfqZ6g-hvjuOMnMeGOq-M6zmFQ=

[2] -

https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_adobe-2Dapiplatform_apigateway_blob_master_api-2Dgateway-2Dconfig_conf.d_marathon-5Fapis.conf-23L35=DwIFaQ=uilaK90D4TOVoH58JNXRgQ=F5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo=Pq6qbuCjIV0NgXrQUGgzHlpwkfQ1iR-hlycfGmbR5_4=6BVUN80-tqxdqO0yYyI2IuXRoe5XKGEUUwhJhjD8J-o=

On Wed, Feb 28, 2018 at 6:08 PM Carlos Santana 
 wrote:

> Hi Kumar welcome to list

>

>   Adobe team is currently deploying OpenWhisk on DCOS/Mesos I bet 
one of

> them will be able to assist you on this task and point you int he 
right

> direction

>

> The file you point is no longer on the repo, Maybe  Dragos or 
Tyson could

> also clarify that and the apigateway issues.

>

> -- Carlos

>

> On Wed, Feb 28, 2018 at 8:27 PM Kumar Subramanian 
 >

> wrote:

>

> > Hi,

> >

Re: Install Api Gateway in dcos

2018-03-01 Thread Kumar Subramanian

Hi Dragos,
I am not sure I understood your point about “Note that by default the 
Gateway listens on this domain defined in config
at [2] ( .gw.). Once the 
controller is
installed in the cluster, it's accessible on 
controller.gw.,
assuming the Marathon app name for the OpenWhisk Controller is called
"controller" “

apigateway is the first app that I tried to install on DCOS. Is there any place 
I have to define the url? (( .gw.) and may 
be I am missing that? The only Url I mentioned is the default one in the 
Environment settings of apigateway package (during installation). The default 
value was "default":http://marathon.mesos:8080; and I kept it as is when 
installing.

Thanks,
Kumar.

On 3/1/18, 9:18 AM, "Kumar Subramanian"  wrote:

Hi Dragos,
Here is the DCOS Version
DC/OS VERSION: 1.9.4

Marathon Version: 1.4.7

Thanks,
Kumar.

On 2/28/18, 11:10 PM, "Dascalita Dragos"  wrote:

Hi Kumar,
Can you provide details on the DCOS version as well ?

*"...The (api gateway) service status shows waiting and there are no 
logs;
nothing getting deployed also"*
Depending on the DCOS version, you may find in the DCOS UI debug
information in regards to the resource offered by Mesos and what's 
missing.
[1] It's possible that some constraints are not matched, and Marathon is
still waiting to get offers, which would explain this effect you're 
seeing.
Note that by default the Gateway listens on this domain defined in 
config
at [2] ( .gw.). Once the 
controller is
installed in the cluster, it's accessible on 
controller.gw.,
assuming the Marathon app name for the OpenWhisk Controller is called
"controller". Same goes for the "invoker": 
invoker.gw..
Same for Exhibitor, CouchDB etc, any other app installed in the cluster 
is
exposed in this way. Of course, these domain names can be easily 
configured
differently in NGINX, I'm just explaining the default rules.

We might have to provide a DCOS universe for 1.9 or 1.10 as well. We've
tested with both versions successfully; we need to strip customizations
particular to our deployment, prior to sharing the updated universe.

HTH,
Dragos

[1] - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.mesosphere.com_1.10_monitoring_debugging_gui-2Ddebugging_=DwIFaQ=uilaK90D4TOVoH58JNXRgQ=F5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo=Pq6qbuCjIV0NgXrQUGgzHlpwkfQ1iR-hlycfGmbR5_4=67DJMsbbLqbhR82ScYfqZ6g-hvjuOMnMeGOq-M6zmFQ=
[2] -

https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_adobe-2Dapiplatform_apigateway_blob_master_api-2Dgateway-2Dconfig_conf.d_marathon-5Fapis.conf-23L35=DwIFaQ=uilaK90D4TOVoH58JNXRgQ=F5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo=Pq6qbuCjIV0NgXrQUGgzHlpwkfQ1iR-hlycfGmbR5_4=6BVUN80-tqxdqO0yYyI2IuXRoe5XKGEUUwhJhjD8J-o=

On Wed, Feb 28, 2018 at 6:08 PM Carlos Santana  
wrote:

> Hi Kumar welcome to list
>
>   Adobe team is currently deploying OpenWhisk on DCOS/Mesos I bet one 
of
> them will be able to assist you on this task and point you int he 
right
> direction
>
> The file you point is no longer on the repo, Maybe  Dragos or Tyson 
could
> also clarify that and the apigateway issues.
>
> -- Carlos
>
> On Wed, Feb 28, 2018 at 8:27 PM Kumar Subramanian 
 >
> wrote:
>
> > Hi,
> >
> > I am trying to install OpenWhisk on Mesos Cluster.
> >
> >
> >
> > I followed the steps described at
> >
> 
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_incubator-2Dopenwhisk-2Ddevtools_tree_1f42e6057de42babc2bf88870fabb61d172d728d_dcos-2Duniverse=DwIFaQ=uilaK90D4TOVoH58JNXRgQ=F5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo=Pq6qbuCjIV0NgXrQUGgzHlpwkfQ1iR-hlycfGmbR5_4=QTfB2-jYGp7UtoXJxEX8WZuWVF8NfYEZiu3nZ9GCJ3g=
> >
> >
> >
> > *Steps Completed:*
> >
> >1. In the universe home directory, run command 
./scripts/build.sh.
> >2. Upload /target/repo-up-to-1.8.json to a host service (e.g. 
AWS S3)
> >   - Make sure Content-Type =
> >   application/vnd.dcos.universe.repo+json in the file's headers.
> >3. In DC/OS admin console, under System > Overview > 
Repositories, add
> >the link to the new repository.
> >
> >
> >
> > Note: I’ve attached the repository file repo-uo-to-1.8.json.
> >
> >
> >
> > *Next:*
> >
> >1. I added the

Re: Install Api Gateway in dcos

2018-03-01 Thread Kumar Subramanian

Hi Dragos,
Here is the DCOS Version
DC/OS VERSION: 1.9.4

Marathon Version: 1.4.7

Thanks,
Kumar.

On 2/28/18, 11:10 PM, "Dascalita Dragos"  wrote:

Hi Kumar,
Can you provide details on the DCOS version as well ?

*"...The (api gateway) service status shows waiting and there are no logs;
nothing getting deployed also"*
Depending on the DCOS version, you may find in the DCOS UI debug
information in regards to the resource offered by Mesos and what's missing.
[1] It's possible that some constraints are not matched, and Marathon is
still waiting to get offers, which would explain this effect you're seeing.
Note that by default the Gateway listens on this domain defined in config
at [2] ( .gw.). Once the controller is
installed in the cluster, it's accessible on 
controller.gw.,
assuming the Marathon app name for the OpenWhisk Controller is called
"controller". Same goes for the "invoker": invoker.gw..
Same for Exhibitor, CouchDB etc, any other app installed in the cluster is
exposed in this way. Of course, these domain names can be easily configured
differently in NGINX, I'm just explaining the default rules.

We might have to provide a DCOS universe for 1.9 or 1.10 as well. We've
tested with both versions successfully; we need to strip customizations
particular to our deployment, prior to sharing the updated universe.

HTH,
Dragos

[1] - 
https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.mesosphere.com_1.10_monitoring_debugging_gui-2Ddebugging_=DwIFaQ=uilaK90D4TOVoH58JNXRgQ=F5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo=Pq6qbuCjIV0NgXrQUGgzHlpwkfQ1iR-hlycfGmbR5_4=67DJMsbbLqbhR82ScYfqZ6g-hvjuOMnMeGOq-M6zmFQ=
[2] -

https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_adobe-2Dapiplatform_apigateway_blob_master_api-2Dgateway-2Dconfig_conf.d_marathon-5Fapis.conf-23L35=DwIFaQ=uilaK90D4TOVoH58JNXRgQ=F5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo=Pq6qbuCjIV0NgXrQUGgzHlpwkfQ1iR-hlycfGmbR5_4=6BVUN80-tqxdqO0yYyI2IuXRoe5XKGEUUwhJhjD8J-o=



On Wed, Feb 28, 2018 at 6:08 PM Carlos Santana  wrote:

> Hi Kumar welcome to list
>
>   Adobe team is currently deploying OpenWhisk on DCOS/Mesos I bet one of
> them will be able to assist you on this task and point you int he right
> direction
>
> The file you point is no longer on the repo, Maybe  Dragos or Tyson could
> also clarify that and the apigateway issues.
>
> -- Carlos
>
> On Wed, Feb 28, 2018 at 8:27 PM Kumar Subramanian  >
> wrote:
>
> > Hi,
> >
> > I am trying to install OpenWhisk on Mesos Cluster.
> >
> >
> >
> > I followed the steps described at
> >
> 
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_incubator-2Dopenwhisk-2Ddevtools_tree_1f42e6057de42babc2bf88870fabb61d172d728d_dcos-2Duniverse=DwIFaQ=uilaK90D4TOVoH58JNXRgQ=F5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo=Pq6qbuCjIV0NgXrQUGgzHlpwkfQ1iR-hlycfGmbR5_4=QTfB2-jYGp7UtoXJxEX8WZuWVF8NfYEZiu3nZ9GCJ3g=
> >
> >
> >
> > *Steps Completed:*
> >
> >1. In the universe home directory, run command ./scripts/build.sh.
> >2. Upload /target/repo-up-to-1.8.json to a host service (e.g. AWS S3)
> >   - Make sure Content-Type =
> >   application/vnd.dcos.universe.repo+json in the file's headers.
> >3. In DC/OS admin console, under System > Overview > Repositories, 
add
> >the link to the new repository.
> >
> >
> >
> > Note: I’ve attached the repository file repo-uo-to-1.8.json.
> >
> >
> >
> > *Next:*
> >
> >1. I added the repository to dcos
> >2. Installed redis successfully.
> >   1. Container port : 6379
> >   2. Host: 
> >   3. Ports: 3774
> >3. Then I tried to install api gateway package (default settings –
> >mentioned below)
> >
> >
> >
> > *Stage I am stuck at:*
> >
> >
> >
> >1. Api Gateway Installation
> >   1. Environment: MarathonHost: 
https://urldefense.proofpoint.com/v2/url?u=http-3A__marathon.mesos-3A8080=DwIFaQ=uilaK90D4TOVoH58JNXRgQ=F5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo=Pq6qbuCjIV0NgXrQUGgzHlpwkfQ1iR-hlycfGmbR5_4=iJzQ1LOzvwJ64ic_jZqFpVNTGMNzMROVn2tOwIqoiOE=
> >
> >
> >
> > *What’s happening?* The (api gateway) service status shows waiting and
> > there are no logs; nothing getting deployed also.
> >
> >
> >
> > *Questions:*
> >
> >1. Why is it stuck and not even getting deployed?
> >2. How can I debug
> >3. Where can I look for logs
> >4. Is there anything wrong with my settings for api-gateway(from json
> >file attached)?
> >5. Is there anything else that needs to be installed?
> >

Re: Release policy compliance: Adding license headers and the excluded files

Re: Install Api Gateway in dcos

Podling Report Reminder - March 2018

Re: Install Api Gateway in dcos

Re: Install Api Gateway in dcos

Re: Install Api Gateway in dcos

Re: Install Api Gateway in dcos

Re: Install Api Gateway in dcos

Re: Install Api Gateway in dcos

Re: Install Api Gateway in dcos

Re: Install Api Gateway in dcos

11 matches

Site Navigation

Mail list logo

Footer information