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] ( <marathon-app-name>.gw.<your-domain-name>). Once the
controller is
installed in the cluster, it's accessible on
controller.gw.<your-domain-name>,
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? (( <marathon-app-name>.gw.<your-domain-name>) 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" <[email protected]> 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" <[email protected]> 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] ( <marathon-app-name>.gw.<your-domain-name>). Once the
controller is
installed in the cluster, it's accessible on
controller.gw.<your-domain-name>,
assuming the Marathon app name for the OpenWhisk Controller is called
"controller". Same goes for the "invoker":
invoker.gw.<your-domain-name>.
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_&d=DwIFaQ&c=uilaK90D4TOVoH58JNXRgQ&r=F5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo&m=Pq6qbuCjIV0NgXrQUGgzHlpwkfQ1iR-hlycfGmbR5_4&s=67DJMsbbLqbhR82ScYfqZ6g-hvjuOMnMeGOq-M6zmFQ&e=
[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&d=DwIFaQ&c=uilaK90D4TOVoH58JNXRgQ&r=F5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo&m=Pq6qbuCjIV0NgXrQUGgzHlpwkfQ1iR-hlycfGmbR5_4&s=6BVUN80-tqxdqO0yYyI2IuXRoe5XKGEUUwhJhjD8J-o&e=
On Wed, Feb 28, 2018 at 6:08 PM Carlos Santana <[email protected]>
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
<[email protected]
> >
> 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&d=DwIFaQ&c=uilaK90D4TOVoH58JNXRgQ&r=F5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo&m=Pq6qbuCjIV0NgXrQUGgzHlpwkfQ1iR-hlycfGmbR5_4&s=QTfB2-jYGp7UtoXJxEX8WZuWVF8NfYEZiu3nZ9GCJ3g&e=
> >
> >
> >
> > *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: <host_ip>
> > 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&d=DwIFaQ&c=uilaK90D4TOVoH58JNXRgQ&r=F5C8fYlpBJ270qrdwLq2iRQrPd1CLap8zItxk8laWpo&m=Pq6qbuCjIV0NgXrQUGgzHlpwkfQ1iR-hlycfGmbR5_4&s=iJzQ1LOzvwJ64ic_jZqFpVNTGMNzMROVn2tOwIqoiOE&e=
> >
> >
> >
> > *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?
> >
> >
> >
> > Thanks,
> >
> > Kumar.
> >
>
