FAQ-RDK-CLOUD

To know the Complete steps for xconf local setup , Please refer : Xconf Server - User guide for configuration and feature validation

 In service.properties, you can add the following properties.  The "seeds" property is just a comma-separated list of a few Cassandra hosts.  If you are using a single host, then it's just that one.  The other properties may not be needed.

connectionPools.SharedConnectionPool.seeds=192.168.0.100,192.168.0.101
connectionPools.SharedConnectionPool.localDatacenter=DC_NAME
connectionPools.SharedConnectionPool.readConsistencyLevel=CL_LOCAL_QUORUM
connectionPools.SharedConnectionPool.writeConsistencyLevel=CL_LOCAL_QUORUM
connectionPools.SharedConnectionPool.autoDiscoverHosts=true

Yes, it can be run on separate nodes. The admin and data service do not need to discover each other.  They both use the Cassandra database, so they need to be able to reach it.  If you install the admin and data service on separate nodes, you will probably have Cassandra on a third node.  The service.properties file for each service should include the "seeds" property.

Steps -

1. Go to the Firmware menu and select Download Location Filter.
2. Select Edit.
3. Enter the FQDN for the firmware download server.
4. Enter the full http location for the firmware download server.
5. Enter an IP address for TFTP and enter 100%.  (This download method will not be used.)
6. Select Save.

Refer Xconf Server - User guide for configuration and feature validation#FeatureValidation(Firmwareupdate) for more details.

There should be a webpa server running somewhere (to which the device can contact). If the server is in place, you can run the commands to fetch data models from a PC that can connect to server or even from the RPi terminal itself.

• As such they don't have any connection between them.
• While xconf is for pushing device specific configurations to CPE, webPA is for remote device management.
• You can refer the xconf server section in wiki and  WebPA for more details.

As of now we don't have a provision to update the webPA url from xconf.

This is setting a parameter using webPA 

• Setting the SSID Password :

curl -X PATCH http://35.155.171.121:9003/api/v2/device/mac:b827eb5681cd/config -d '{"parameters": [ {"dataType": 0, "name": "Device.WiFi.SSID.10001.SSID", "value": "Testing"}]}' -H 'Authorization:Basic d2VicGFAMTIzNDU2Nzg5MAo='

• Getting the SSID for the board.

curl -X GET 'http://35.155.171.121:9003/api/v2/device/mac:b827eb5681cd/config?names=Device.WiFi.SSID.10001.SSID' -H 'Authorization:Basic d2VicGFAMTIzNDU2Nzg5MAo='

You can delete a model using below command

• $ curl -i -X DELETE http://xconf_server_ip:9092/delete/models/XYZ123

Retrieve list of models & check the particular entry is deleted:

• $ curl -i http://xconf_server_ip:9092/queries/models

.ns list for mac list

Themis was not part of the community XMidt server, we will discuss with developer and update the wiki.

• WebPA is the communication channel from Cloud to RDK based home gateway devices. It helps to manage devices from Cloud. It was built from the ground up specifically with security and performance as priorities.  
• WEBPA protocol provides functionality of read/write access to device management parameters.
• The “PA” in WebPA stands for “Protocol Adapter.” It’s a component used to connect devices to clouds in a way that RDK licensees call “trivially scalable.”

Refer WebPA for more information.

Refer Environment Setup in RDK-C : WebPA Support#C:WebPASupport-EnvironmentSetup

TR-69 polls wide-and-deep across a device landscape, on a less frequent basis whereas WebPA can precision-poll for the most useful data, much more quickly. That’s mainly because it’s lightweight, and because the load can be redistributed into all the apps needing to access the data.

Example 1: Fetch device or feature parameter detail from client( RPI ) device through parodus by using webpa server.

• curl -H 'Authorization:Basic dXNlcjp3ZWJwYQo=' -i 'http://192.168.2.75:9003/api/v2/device/mac:b827eb2e722b/config?names=Device.DeviceInfo.X_RDKCENTRAL-COM_IMAGENAME'

Example 2: Setting the SSID Password :

• curl -X PATCH http://35.155.171.121:9003/api/v2/device/mac:b827eb5681cd/config -d '{"parameters": [ {"dataType": 0, "name": "Device.WiFi.SSID.10001.SSID", "value": "Testing"}]}' -H 'Authorization:Basic d2VicGFAMTIzNDU2Nzg5MAo='

Example 3: Getting the SSID for the board.

• curl -X GET 'http://35.155.171.121:9003/api/v2/device/mac:b827eb5681cd/config?names=Device.WiFi.SSID.10001.SSID' -H 'Authorization:Basic d2VicGFAMTIzNDU2Nzg5MAo='

Refer WEBPA Validation Procedure Steps in RDK-C : WebPA Support#C:WebPASupport-WEBPAValidationProcedure for more information.

Yes ,it is possible to configure TFTP ipv4 and ipv6 locations in Xconf. Follow the steps specified here Xconf Server - User guide for configuration and feature validation#AddTFTPlocation

Xconf doesn’t store any data, be it logs or telemetry data. It only provides the configuration to the client device regarding where to upload the data, when to upload the data and what data it needs to be uploaded. So Xconf server doesn’t need any big data processing tools.

There is no direct interaction, both Xconf and WebPA serve different purpose. While Xconf is used by devices to fetch and configure the rules, webPA can be used to push/set the rules/attributes on a CPE device.

No, xconf doesn’t directly facilitate upload logs/telemetry data. It provides devices information on where/when to upload the log files or telemetry json files.

No, the maven-frontend-plugin plugin downloads/installs Node and NPM locally for your project, runs npm install. It's supposed to work on Windows, OS X and Linux.

Yes, If anyone needs to override the firmware download location, it's best to do it with a define property rule. It will only affect those devices identified in the rule.
Just like tftp location is overridden like this - Xconf Server - User guide for configuration and feature validation#AddTFTPlocation