We have an access token for one course in the Leipziger Moodle in order to obtain data from their students. This data has to be collected by us and it to be added to the learning record store. However, it is currently difficult to start an additional data proxy if one is already running in the same las2peer network.
Specification
This yaml file is currently deployed in the eal Namespace inside the Kubernetes cluster, however the amount of Pods has been scaled down to 0, effectively pausing the Deployment. The Deployment itself however, should be functional. The thread polling for Moodle updates currently has to be started manually which is a problem, since [the POST request]((https://github.com/rwth-acis/moodle-data-proxy/blob/master/src/main/i5/las2peer/services/moodleDataProxyService/MoodleDataProxyService.java#L146-L174) to do so is randomly forwarded to one of the data proxy nodes running in the las2peer network. Thus, it may take multiple attempts to start this thread if one or more data-proxies are already running. The POST is required, as the context is only available, once the node has connected to the network.
Furthermore, a number of functions have to be enabled in the Moodle API for the given token (complete list here), and our Moodle plugin has to be installed and activated. Otherwise, the data proxy will be unable to create any or all xAPI statements. These things can only done by an administrator of the Leipzig Moodle.
Finalized state
A moodle-data-proxy running in the eal Namespace inside the Kubernetes cluster should be running which is successfully retrieving data from it and which gets stored to the tech4comp LRS. Also don't forget to add the YAML files of this Deployment to the cluster repo
Motivation
We have an access token for one course in the Leipziger Moodle in order to obtain data from their students. This data has to be collected by us and it to be added to the learning record store. However, it is currently difficult to start an additional data proxy if one is already running in the same las2peer network.
Specification
This yaml file is currently deployed in the eal Namespace inside the Kubernetes cluster, however the amount of Pods has been scaled down to 0, effectively pausing the Deployment. The Deployment itself however, should be functional. The thread polling for Moodle updates currently has to be started manually which is a problem, since [the POST request]((https://github.com/rwth-acis/moodle-data-proxy/blob/master/src/main/i5/las2peer/services/moodleDataProxyService/MoodleDataProxyService.java#L146-L174) to do so is randomly forwarded to one of the data proxy nodes running in the las2peer network. Thus, it may take multiple attempts to start this thread if one or more data-proxies are already running. The POST is required, as the context is only available, once the node has connected to the network.
Furthermore, a number of functions have to be enabled in the Moodle API for the given token (complete list here), and our Moodle plugin has to be installed and activated. Otherwise, the data proxy will be unable to create any or all xAPI statements. These things can only done by an administrator of the Leipzig Moodle.
Finalized state
A moodle-data-proxy running in the eal Namespace inside the Kubernetes cluster should be running which is successfully retrieving data from it and which gets stored to the tech4comp LRS. Also don't forget to add the YAML files of this Deployment to the cluster repo