SOTA Client

Shaun Taheri shaun at advancedtelematic.com
Tue Oct 25 04:26:31 EDT 2016


Hi Cristina,

Right now the easiest way to find the UUID is from the URL when you view a specific vehicle (by clicking its VIN). Alternatively, it can be retrieved from the ‘Device’ table in the ‘sota_device_registry’ MySQL database.

Thanks,

Shaun

> On 25 Oct 2016, at 08:51, Cristina STANGACIU <certejan at dsplabs.cs.upt.ro> wrote:
> 
> Hi!
> 
> Thanks for all the support provided until now. Can anybody, please, help me with another problem:
> 
> I fail to generate an UUID:
> 
> Login to the UI and create a new Device/Vehicle. Copy the newly generated Device UUID (e.g. "9ea653bc-3486-44cd-aa86-d936bd957e52") into the client-rvi.yml file as environment variable DEVICE_ID:
> 
>     environment:
>       RVI_BACKEND: "rvi_backend"
>       DEVICE_ID: "9ea653bc-3486-44cd-aa86-d936bd957e52"
> 
> I have logged on the localhost:9000 and I have added a new Vehicle, but I do not know how to generate an UUID, I cannot find the menu. Can anyone, please, help me?
> Thank you!
> 
> Cristina S.
> 
> On 24.10.2016 19:11, Cristina Stangaciu wrote:
>> 
>> 
>> 
>> -------- Forwarded Message --------
>> Subject:	Re: SOTA Client
>> Date:	Mon, 24 Oct 2016 19:10:36 +0300
>> From:	Cristina Stangaciu <certejan at dsplabs.cs.upt.ro> <mailto:certejan at dsplabs.cs.upt.ro>
>> To:	Jon Oster <jon at advancedtelematic.com> <mailto:jon at advancedtelematic.com>
>> 
>> Hi!
>> 
>> I have already told you that I have fixed it. It was a wrong version of the docker-composer (it was too old and had some missing features).
>> 
>> Thanks again!
>> 
>> Cristina S.
>> 
>> On 21.10.2016 16:36, Jon Oster wrote:
>>> Hi Cristina,
>>> 
>>> I’m not sure exactly what you mean when you say that “the only message was the help menu”. Are you sure you have docker installed/configured correctly? (Does `docker run hello-world` work, for example?) You should see something like this as the output of that command:
>>> 
>>> $ docker-compose -f docker-compose.yml -f core-rvi.yml -f client-rvi.yml up -d
>>> Starting dockercompose_nats_1
>>> Starting dockercompose_mysql_1
>>> Starting dockercompose_ldapserver_1
>>> Starting dockercompose_device-registry_1
>>> Starting dockercompose_rvi_backend_1
>>> Recreating dockercompose_resolver_1
>>> Starting dockercompose_rvi_device_1
>>> Recreating dockercompose_core_1
>>> Recreating dockercompose_webserver_1
>>> 
>>> Once you’ve run that, you should be able to see the machines in `docker ps`:
>>> 
>>> $ docker ps
>>> CONTAINER ID        IMAGE                                    COMMAND                  CREATED              STATUS              PORTS                                            NAMES
>>> c6584942e7cd        advancedtelematic/sota-webserver         "/opt/sota-webserver/"   38 seconds ago       Up 31 seconds       0.0.0.0:9000->9000/tcp                           dockercompose_webserver_1
>>> 02bdef27fc71        advancedtelematic/sota-core              "/opt/sota-core/entry"   50 seconds ago       Up 42 seconds       0.0.0.0:8080->8080/tcp                           dockercompose_core_1
>>> 5ba422c977ec        advancedtelematic/sota-resolver          "/opt/sota-resolver/e"   About a minute ago   Up 52 seconds       0.0.0.0:8081->8081/tcp                           dockercompose_resolver_1
>>> 542498b7ab8f        advancedtelematic/sota-device_registry   "/opt/sota-device_reg"   3 weeks ago          Up About a minute   0.0.0.0:8083->8083/tcp                           dockercompose_device-registry_1
>>> e76114e1ab6f        advancedtelematic/rvi:0.5.0              "/usr/bin/run_rvi.sh "   3 weeks ago          Up 59 seconds       0.0.0.0:8901->8901/tcp                           dockercompose_rvi_device_1
>>> f5bb369e8282        advancedtelematic/mariadb:stable         "/docker-entrypoint.s"   6 weeks ago          Up About a minute   0.0.0.0:3306->3306/tcp                           dockercompose_mysql_1
>>> dbf5bb178c37        advancedtelematic/openldap:genivi        "/container/tool/run "   6 weeks ago          Up About a minute   636/tcp, 0.0.0.0:9389->389/tcp                   dockercompose_ldapserver_1
>>> 05abd1d6873e        advancedtelematic/rvi:0.5.0              "/usr/bin/run_rvi.sh "   6 weeks ago          Up About a minute   0.0.0.0:8801->8801/tcp, 0.0.0.0:8807->8807/tcp   dockercompose_rvi_backend_1
>>> 8f740efe15ce        nats:0.8.1                               "/gnatsd -c /gnatsd.c"   6 weeks ago          Up About a minute   6222/tcp, 0.0.0.0:4222->4222/tcp, 8222/tcp       dockercompose_nats_1
>>> 
>>> The admin gui will then be available in your web browser at localhost:9000.
>>> 
>>> Best,
>>> 
>>> Jon
>>> 
>>>> On Oct 19, 2016, at 12:21 PM, Cristina STANGACIU <certejan at dsplabs.cs.upt.ro <mailto:certejan at dsplabs.cs.upt.ro>> wrote:
>>>> 
>>>> Hi!
>>>> 
>>>> I have a question:
>>>> 
>>>> how to I check if the following command works properly. Do I have to get a message in the console?.
>>>> 
>>>> docker-compose -f docker-compose.yml -f core-rvi.yml -f client-rvi.yml up -d
>>>> 
>>>> I ask this, because I was following the instructions on
>>>> 
>>>> https://github.com/advancedtelematic/rvi_sota_client#testing-on-genivi-development-platform-over-rvi <https://github.com/advancedtelematic/rvi_sota_client#testing-on-genivi-development-platform-over-rvi>
>>>> and the following operation led to [SUCCESS] ...
>>>> 
>>>> ./sbt docker:publishLocal
>>>> 
>>>> After changing directory and running
>>>> docker-compose -f docker-compose.yml -f core-rvi.yml -f client-rvi.yml up -d
>>>> The only message was the help menu.
>>>> 
>>>> Other question that I have is how to login to the UI (how do I access the UI for the following context).
>>>> "Login to the UI and create a new Device/Vehicle. Copy the newly generated Device UUID (e.g. "9ea653bc-3486-44cd-aa86-d936bd957e52") into the client-rvi.yml file as environment variable DEVICE_ID:"
>>>> 
>>>> Thank you!
>>>> 
>>>> Cristina S.
>>>> 
>>>> On 18.10.2016 19:27, Shaun Taheri wrote:
>>>>> Hi all,
>>>>> 
>>>>> Apologies for the delayed reply regarding the messages last week around the SOTA client and DBus, although I was off and am just catching up with the requests.
>>>>> 
>>>>> Admittedly the instructions for starting the client are not as clear as they should be (and will be updated), however the steps for using the SOTA Client with RVI and GENIVI SWM are as follows:
>>>>> 
>>>>> * Start the SOTA server and RVI by following the instructions here: https://github.com/advancedtelematic/rvi_sota_client#testing-on-genivi-development-platform-over-rvi <https://github.com/advancedtelematic/rvi_sota_client#testing-on-genivi-development-platform-over-rvi>. (the username and password for the UI are “genivi” and “genivirocks!” respectively).
>>>>> 
>>>>> * Start the SOTA client (passing “RUST_LOG=debug” to see debug output) with the desired config file. An example config has been attached, although you will need to update:
>>>>>   - device.uuid to the device id created previously
>>>>>   - 192.168.50.1 to the correct IP for core.server and rvi.client
>>>>>   - 192.168.50.2 to the correct IP for the sota client
>>>>> 
>>>>> * From the software_loading_manager directory in the GENIVI SWM repository, run “python software_loading_manager.py” to start the SWM.
>>>>> 
>>>>> * Upload a package using the UI, then create a campaign which should trigger an “UpdateAvailable” Event in the client, which the DBus Gateway will pick up to initiate the download. (If you want the SOTA client to install the downloaded package, change “device.package_manager” in the config to “deb” or “rpm”.)
>>>>> 
>>>>> I’ve attached some log output as well to show the above flow in operation. Please let me know if anyone needs further assistance getting this running.
>>>>> 
>>>>> Many thanks,
>>>>> 
>>>>> Shaun
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> genivi-projects mailing list
>>>>> genivi-projects at lists.genivi.org <mailto:genivi-projects at lists.genivi.org>
>>>>> http://lists.genivi.org/cgi-bin/mailman/listinfo/genivi-projects <http://lists.genivi.org/cgi-bin/mailman/listinfo/genivi-projects>
>>>> 
>>>> _______________________________________________
>>>> genivi-projects mailing list
>>>> genivi-projects at lists.genivi.org <mailto:genivi-projects at lists.genivi.org>
>>>> http://lists.genivi.org/cgi-bin/mailman/listinfo/genivi-projects <http://lists.genivi.org/cgi-bin/mailman/listinfo/genivi-projects>
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> genivi-projects mailing list
>>> genivi-projects at lists.genivi.org <mailto:genivi-projects at lists.genivi.org>
>>> http://lists.genivi.org/cgi-bin/mailman/listinfo/genivi-projects <http://lists.genivi.org/cgi-bin/mailman/listinfo/genivi-projects>
>> 
>> 
>> 
>> _______________________________________________
>> genivi-projects mailing list
>> genivi-projects at lists.genivi.org <mailto:genivi-projects at lists.genivi.org>
>> http://lists.genivi.org/cgi-bin/mailman/listinfo/genivi-projects <http://lists.genivi.org/cgi-bin/mailman/listinfo/genivi-projects>
> 
> _______________________________________________
> genivi-projects mailing list
> genivi-projects at lists.genivi.org
> http://lists.genivi.org/cgi-bin/mailman/listinfo/genivi-projects

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.genivi.org/pipermail/genivi-projects_lists.genivi.org/attachments/20161025/c37ef3d3/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.genivi.org/pipermail/genivi-projects_lists.genivi.org/attachments/20161025/c37ef3d3/attachment.asc>


More information about the genivi-projects mailing list