GENIVI software as portfolio. Where can we go next?
Transcript of GENIVI software as portfolio. Where can we go next?
![Page 1: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/1.jpg)
Copyright © GENIVI Alliance 2016 | October 18, 2016 | Copyright © GENIVI Alliance 2016 | October 18, 2016 | GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries. Copyright © GENIVI Alliance 2016.
GENIVI software as portfolio.Where can we go next? How?October 20, 2016 | AMM Burlingame - All Members
Agustín Benito BethencourtPrincipal Consultant - FOSS at Codethink Ltd
![Page 2: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/2.jpg)
Who are Codethink?
● Provide software engineering & consultancy services.
● Expert in Linux and Open Source software.
● Focus on automotive industry, embedded devices &
enterprise infrastructure.
● UK Headquarters, serving clients in EU, US and Asia.
● Independent and unbiased.
● GENIVI Associate Member since 2012
![Page 3: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/3.jpg)
Why Codethink?
Open Source company.
+
Automotive experience.
+
Passionate about building & delivering complex Linux
systems.
![Page 4: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/4.jpg)
The speaker
● Principal Consultant - FOSS at Codethink Ltd
● Experienced in managing people & programs/projects in the
open. Product ownership experience.
● At GENIVI Alliance.○ Codethink Ltd representative.
○ GDP Delivery Team Lead.
○ Tools Team Expert Group Coordinator.
● More about myself at http://www.toscalix.com
![Page 5: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/5.jpg)
Copyright © GENIVI Alliance 2016 | October 18, 2016 |
Background: 14th AMM
![Page 6: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/6.jpg)
Background: 14th AMM. One organization, one delivery chain for a portfolio
Challenge: 3.- Design of GENIVI portfolio1. The current portfolio design present several structural and tactical
challenges.
2. GENIVI has a better chance to take advantage of FLOSS by approaching
these challenges with a FLOSS mindset.
Potential Solutions: Work with a portfolio approach first. Then
focus on product transits.
![Page 7: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/7.jpg)
Copyright © GENIVI Alliance 2016 | October 18, 2016 |
GENIVI Today
![Page 8: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/8.jpg)
Current GDP delivery project main goal
Increase GENIVI’s consumers base:
Application Developers
![Page 9: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/9.jpg)
![Page 10: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/10.jpg)
![Page 11: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/11.jpg)
GENIVI portfolio today
Outcome Target group DescriptionMaster GENIVI contributors
Build the latest available software from scratch.
GDPGENIVi software consumers. Towards
application developers.Consume GDP through binaries.
meta-ivi GENIVI Members Outcome of the compliance process.
SDE Application developers Just released the initial version
GDP spins Specific target groups: automotive Qt developers.
Just released the initial version.
![Page 12: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/12.jpg)
![Page 13: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/13.jpg)
Copyright © GENIVI Alliance 2016 | October 18, 2016 |
Challenges
![Page 14: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/14.jpg)
Statement 1
Professional application developers main target are in
production platforms that ensure a potential market.
![Page 15: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/15.jpg)
Challenge 1
GDP is not meant to be a system for production (any
time soon).
![Page 16: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/16.jpg)
Statement 2
Adopters of any given system in professional
environments demand a high level of quality from that
system.
![Page 17: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/17.jpg)
Challenge 2
By moving fast to adapt to developers needs GDP
cannot meet the stability demands required in
automotive.
![Page 18: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/18.jpg)
Statement 3
A platform delivery project requires a significant
contribution base to reach a high quality level.
![Page 19: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/19.jpg)
Challenge 3
Application developers are not, by definition, potential
contributors of a system/platform, but consumers.
![Page 20: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/20.jpg)
Engagement
![Page 21: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/21.jpg)
Who do we start with?1. Today’s advocates:
a. Any taker?
2. Today’s contributors:a. EG members
b. GDP contributors
3. Today’s consumers:a. Automotive system devs. who
demo apps.
b. Those who build products
including GENIVI software.
![Page 22: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/22.jpg)
Who is the target?
1. Tomorrow’s potential advocates:a. Today’s contributors: EG Members
and GDP current contributors.
2. Tomorrow’s potential
contributors:a. Today’s consumers: automotive
system developers.
3. Tomorrow’s potential consumers:a. Application developers.
![Page 23: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/23.jpg)
Target groups: Who? Today Tomorrow? Target Group
GENIVI component dev. Contributor Advocate GENIVI Member system dev.
GENIVI integrator / testers Contributor Advocate GENIVI Member system dev.
Industry sys developer who need a base system to demo apps
Consumer Contributor Automotive system dev.
GENIVI Members system devs. who interact with GENIVI components.
Consumers Contributor GENIVI Member system dev.
Industry system devs. who interact with GENIVI soft components.
Consumers Contributor Automotive system dev.
Industry application devs. who interact with GENIVI soft. components.
Follower ConsumerAutomotive app dev. For
GENIVI dev.
Industry system or app devs who does not use GENIVI software
Aware Followers Automotive dev.
Embedded system or application developers ---- Aware -----
![Page 24: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/24.jpg)
Quote 1
“In open source, we feel strongly that
to really do something well, you have to
get a lot of people involved.” - Linus Torvalds
![Page 25: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/25.jpg)
Quote 2
“You can’t sell it outside if you can’t sell
it inside.” - Stan Slap
![Page 26: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/26.jpg)
Quote 3
“Stop selling. Start helping.” – Zig Ziglar
![Page 27: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/27.jpg)
Quote 4
“If you want to go fast, go alone. If you
want to go far, go together.” - African
proverb
![Page 28: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/28.jpg)
Quote 5
“Don't hurry your code. Make sure it
works well and is well designed. Don't
worry about timing.” - Linus Torvalds
![Page 29: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/29.jpg)
GDP Delivery project main goal
contributors
Increase GENIVI’s consumers base:
Application DevelopersAutomotive system developers
![Page 30: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/30.jpg)
Copyright © GENIVI Alliance 2016 | October 18, 2016 |
Tomorrow: proposal
![Page 31: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/31.jpg)
![Page 32: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/32.jpg)
GENIVI's porfolio
●1.- Master: targets automotive system devs.○Central integration point of all GENIVI software.
○Provides the latest available software in an easy way to build from scratch.
●2.- GDP Core: targets GENIVI Members.○Base system very limited in scope system.
○Focus on commodity software for production systems.
○Include GENIVI components that are ready for production only.
![Page 33: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/33.jpg)
GENIVI's porfolio
●3.- GDP: targets automotive system consumers.○Branched from Master. Stabilization. Focus on a pleasant consumption
experience.
●Other deliverables (by third parties)○4.- GDP Spins
○5.- SDE: targets automotive application developers.
■ Integration with GDP for an efficient development experience.
![Page 34: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/34.jpg)
![Page 35: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/35.jpg)
![Page 36: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/36.jpg)
![Page 37: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/37.jpg)
Portfolio designPriority Target group Outcome Description
1 GENIVI Members GENIVI CorePre-production system. Base system + Fully functional
GENIVI automotive components from Compliance program.
2Automotive system
developersGENIVI Master
System used to develop automotive components. Central integration point for third party software. Magma first
policy.
3 Automotive developers. GDPFull system easy to consume used to promote GENIVI and also as base system for developers, focusing on application developers.
4 Specific target groups GDP spinsGDP + software targeting specific group. The additional
software makes use of the GENIVI APIs and auto software components.
5 Application developers SDETools kit, integrated with GDP, that is, use GENIVI’s API
and software components to save time to developers.
![Page 38: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/38.jpg)
What about Baseline
Meta-ivi Yocto layer
QEMU
Compliance program
Component Component
Component Component
15th AMM
Component Component
Component Component
Specific layer
Specific layer
Master
GENIVI Core
Compliance program
Component definition+
Validation+
verification
16th AMM
maturity
![Page 39: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/39.jpg)
What about Baseline?● Compliance is important. The program should remain.
● Separate compliance from delivery.
● Follow a declarative approach.○ Separate components in functional layers that makes them easier to
manage based on different criteria, like maturity.
○ Leave behind the brick/block concept applied to systems.
● Single integration team managing a single integration
production chain.○ Embrace efficiency and collaboration vs structure and isolation.
![Page 40: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/40.jpg)
Copyright © GENIVI Alliance 2016 | October 18, 2016 |
Software “life cycle” / path within GENIVI
![Page 41: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/41.jpg)
![Page 42: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/42.jpg)
![Page 43: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/43.jpg)
![Page 44: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/44.jpg)
Copyright © GENIVI Alliance 2016 | October 18, 2016 |
From GDP project to Delivery Program
![Page 45: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/45.jpg)
From GDP project to Delivery program
● Coordination with PMO, IT, Marketing and CEO
at management level.
● Coordination with EGs at engineering level.
● Coordination with Members and community at per
product level.
![Page 46: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/46.jpg)
From GDP project to GENIVI delivery program● Delivery team formed by release managers.
○ SDE requires also a development tools specialist.
● Total of five people.○ One full time release manager per outcome.
■ Master + Code + GDP = 3 maintainers (FTE)
■ Devops engineer to support the porfolio delivery.
■ All four engineers work together in Master.
○ Project owner.
![Page 47: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/47.jpg)
Copyright © GENIVI Alliance 2016 | October 18, 2016 |
Roadmap
![Page 48: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/48.jpg)
From GDP project to GENIVI delivery program
13th AMM 14th AMM 15th AMM 16th AMM
gnivi-dev-platform
Core
Master
Core
GDP
SphereSpin
SDE
From demoTo
development
Auto system
dev
ReleaseSpin
Spins
SDK
ReleaseSDE
Meta-iviReform meta-ivi
Master
ReleaseCore
Deprioritise SDE
![Page 49: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/49.jpg)
Decisions
1. Define system automotive developers as primary target group.
2. Switch current focus of GDP accordingly. De-prioritise SDE.
3. Separate meta-ivi from the compliance program. Merge the
code part into GDP delivery program
4. Restructure GDP layers for easier maintenance and individual
components consumption.
5. Define the initial requirements for Core system. Towards 16th
AMM
![Page 50: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/50.jpg)
Copyright © GENIVI Alliance 2016 | October 18, 2016 |
Infrastructure and service improvements
![Page 51: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/51.jpg)
Deployment infrastructure
● Automated deployment.○ Towards continuous deployment.
● p2p capabilities and mirroring.
● Public/private instance to control what is not
ready to distribute.
● Analytic to comprehend binaries consumption.
● Steps forward towards reproducibility.
![Page 52: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/52.jpg)
Sources mirroring
Mirror GENIVI sources (from Github and upstream) in
GENIVI’s infrastructure because:● Increase reliability at building time.
● Compliance revision at commit stage to reduce overhead at
validation stage.
● Increase build performance.
● Step forward towards reproducibility.
● Analytic to understand how source are consumed.
![Page 53: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/53.jpg)
Build system
● Capacity increase.
● Differentiation between production quality builds
and other builds.
● ACL capabilities.
● Trigger sources from GENIVI mirror.
● Parallelization.
![Page 54: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/54.jpg)
Testing
● First stage: focus on acceptance testing:○ Processes and tests first, initially through scripting.
○ Tests like patches approach.
● Second stage: focus on boot testing automation○ Though kernelci.org for simple systems
○ Through openQA for full systems.
● Third stage: focus on production quality○ Integrate automated tests.
● Compliance include specs, code and tests.
![Page 55: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/55.jpg)
Other important improvements
● Increase download bandwidth to improve
integrators efficiency.
● Get rid of unmaintained code.
● Limit PoC to Master for maturing.
● Improve flexibility in Master for customizations.
![Page 56: GENIVI software as portfolio. Where can we go next?](https://reader034.fdocuments.in/reader034/viewer/2022042619/58a2e59d1a28ab26788b8af6/html5/thumbnails/56.jpg)
Questions?
www.codethink.co.uk