Policy Manager Project.
Lorenz, Jens (ADITG/SW1)
jlorenz at de.adit-jv.com
Mon Mar 20 08:33:11 EDT 2017
I have read the statement of work and I have some worries about it.
While looking at the ESOW I feel strongly remembered to a project called
Murphy https://01.org/murphy which was driven by Intel in AGL and used LUA for policy description.
I am not sure if you are not going to develop things again…
Secondly, while looking to the architecture overview the first example is already solved by the GENIVI AudioManager.
The only Policy who will be informed and does the decision in a GENIVI system is the AudioManager’s Policy.
The Policy is implemented by the Controller Plugin and can be implemented by each OEM differently – also with a C++ -> LUA converter.
Based on this policy the respective Applications will be informed – not only in the local node!
I see the need to have the vehicle information properly notified to different applications and I see a need to standardize
the mechanism in a generic way as much as possible; This is obviously the benefit of the VSC.
Also see the need to have car network policy evaluated locally for some rear use cases in IVI-HMI.
But I fear we have already a lot of policy engines defined in GENIVI e.g.:
- AudioManager (inter domain media resource manager connected directly to HMI)
- Node State Manager
- Popup Manager (possibly already implementable by AudioManager)
- Device Manager
The second scenario with the RVC use case also causes some worries on my side.
RVC usually has low latency requirements in communication and early startup requirements.
If you use Python as a development language aren’t you enforced to load additional libraries like CPyhton?
Furthermore, LUA scripting and evaluation of policy needs also be loaded.
Was there already an evaluation done beforehand how long the start of modules and evaluation of policy takes?
While reading the development purpose section I thought, why isn’t there only a module developed
which can be loaded e.g. by the AudioManager and connects to the car network to get additional information
like speed, gear state and other vehicle states.
So far, the AudioManager team considered that this is OEM specific and could be connected to the Controller.
There is already an Generic Controller for AudioManager available which can be configured with XML.
The configuration mechanism is meant to be exchangeable and e.g. LUA can be supported also.
But what we still miss is an (open source) interface to get the different vehicle states in order to evaluate and react on state changes like speed?
Don’t get me wrong:
I appreciate the idea to get new things in GENIVI defined but we should also consider the entire architecture and
we should look also to available existing solutions and already developed and defined components in GENIVI/OSS.
I would like to discuss the architecture and the background idea in more detail with you.
I will attend the GENIVI AMM and maybe we can solve the concerns I have.
Software Group I (ADITG/SW1)
Tel. +49 5121 49 6927
From: Feuer, Magnus [mailto:mfeuer1 at jaguarlandrover.com]
Sent: Mittwoch, 15. März 2017 00:19
To: Genivi Project
Subject: Policy Manager Project.
JLR has sent out the attached Engineering Statement Of Work (ESOW) to select vendors. Our preference is to run this project as open source under the GENIVI umbrella with discussions and implementation being carried out in the open.
With that in mind, we would very much appreciate feedback on the scope of the project and in which direction we can take this project in future phases. We are actively seeking participants in the community to contribute to the initial phase, adding weight to our case for open sourcing the project.
Head System Architect - Open Source Projects
Jaguar Land Rover
Email: mfeuer1 at jaguarlandrover.com<mailto:mfeuer1 at jaguarlandrover.com>
Mobile: +1 949 294 7871
Jaguar Land Rover North America, LLC
1419 NW 14th Ave, Portland, OR 97209
Jaguar Land Rover Limited
Registered Office: Abbey Road, Whitley, Coventry CV3 4LF
Registered in England No: 1672070
This e-mail and any attachments contain confidential information for a specific individual and purpose. The information is private and privileged and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient, please e-mail us immediately. We apologise for any inconvenience caused but you are hereby notified that any disclosure, copying or distribution or the taking of any action in reliance on the information contained herein is strictly prohibited.
This e-mail does not constitute an order for goods or services unless accompanied by an official purchase order.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the genivi-projects