curl to scytale URL returns 404 Not Found error

[xmidt-org]

curl to scytale URL returns 404 Not Found error

[joe94]

@fchan2, @johnabass is currently working to add support for that feature. We will keep you posted.

[fchan2]

Hi @joe94, can you clarify which feature is not yet supported?

I was attempting to GET device parameters as documented in the link here:
RDK-B WEBPA Commands

...so I was under the impression that this should work?

[joe94]

The feature I am referring to is the ability to get the stats for a given device (specifically the stat endpoint is not yet supported in scytale).

That said, you can get the device stats using talaria today using the following endpoint form:

[your-talaria-machine]:[your-bind-address]/api/v2/device/mac:[your-device-mac-address]/stat

[fchan2]

Cool, I can pull the stat now if I point it to talaria as you mentioned.

Should GET TR-181 data models work if I point it to talaria as well? I gave it a try using this command and I got a "404 page not found" error.

curl -i http://[my-talaria-machine]:[talaria bind address]/api/v2/device/mac:[device mac address]/config?names=Device.DeviceInfo.SerialNumber

[joe94]

No, that won't work because that's outside talaria's concern.

Few things:

• Last time I checked, the stat feature was more than 50% done.

• From my limited understanding of your business requirements (working with TR-181 data models), most of your direct API hits should be to tr1d1um and not scytale or talaria. Remember you can also get the device stats using tr1d1um (once scytale supports it) using the same endpoint form as talaria!

[fchan2]

From my limited understanding of your business requirements (working TR-181 data models), most of your direct API hits should be to tr1d1um and not scytale or talaria.

Can you elaborate on what this means from the context of server configuration? I believe the RDK-B device still needs to connect to the talaria websocket port in order to get to tr1d1um -- do I have that right?

[joe94]

Yes, absolutely. I just mean that for endpoints like stat and config, you would want to use tr1d1um directly (but of coursetr1d1um then in turns uses scytale and talaria under the hood). But yes, all the device connections (websocket) you mentioned are done with talaria.

[fchan2]

Hmm...by using tr1d1um directly, do you mean using the config command above, but just replacing with the tr1d1um machine/ports? I just gave that a try and met with a 404 error again.

[fchan2]

Just to clarify, this is the command that I am using:
curl -i http://[tr1d1um ip]:[tr1d1um port]/api/v2/device/mac:f8a097ea7206/config?names=Device.DeviceInfo.SerialNumber

I did not modify any JSON files before running this since device stats using tr1d1um as an endpoint from scytale is not supported yet.

HTTP/1.1 404 Not Found
Content-Type: text/plain; charset=utf-8
X-Content-Type-Options: nosniff
Date: Tue, 05 Dec 2017 17:36:41 GMT
Content-Length: 19
404 page not found

[johnabass]

Since you tried this via tr1d1um, this should be considered a tr1d1um issue externally. You should not be invoking scytale directly.