Hello, I want to ask you a question: What is ONAP?
I asked multiple contributors this simple question and the answer was always something vague like: ONAP is a platform. I also asked: What is the "core" of ONAP then - What cannot be removed from ONAP - otherwise it would stop being ONAP anymore. Why am I asking this? Because I cannot get my head around of some docker image sizes - like: pndareg.ctao6.net/onap/org.onap.dcaegen2.deployments.pnda-mirror-container 5.0.0 64f81260635d 8 months ago 11.4GB What it makes so big? Well inside is a rpm repo (1.9GB) and ELK stack (1.2GB) and Hadoop installation (6.8GB) and other packages. I frankly have no idea what purpose this container has but that can be another question later. How many hadoops are already in all of ONAP? How many ELK stacks? How many databases? Why is there so much of a redundancy? Why the user of ONAP has to know zookeeper or consul when etcd is the clustered key-value store of choice in kubernetes. Why invent wheels when already the whole orchestration can be done via kubernetes facilities. Why AAF looks like that it is reinventing LDAP and radius maybe? Can we just use already made rock-solid and battle-tested frameworks which are de facto industry standards already? Saying that ONAP is some umbrella word for "platform" is IMHO insufficient. If someone says that Linux is a platform then that is valid. What is the difference? Linux can serve as a desktop, a server, a mobile phone, a watches, a microwave, a fridge or an atm. So what is the core of such linux platform? The linux kernel of course and libc. Everything else running on this platform uses those at the end. Every piece of software will end up calling the linux kernel syscalls (through layers of abstraction and indirection) - that is the core - that is the ultimate interface. Kubernetes is a platform - kubernetes is that layer between our software and the kernel - kubernetes provides the interface. Everyone knows that - it is no strange concept. So, what is the ONAP interface? What are the core components? Is PNDA and AAF and other the core components? Are they integrated in such a way that if one is missing ONAP as a platform breaks? It seems to me that ONAP had some hype and some projects just wanted to make a PR: We are part of the ONAP platform! Whatever that means. So they provided helm charts to be installed together with the rest of ONAP but there is zero integration, zero benefit and it only bloats the size. I am not trying to shame any component in particular (I mentioned PNDA - no hard feelings) - I think that they are many such components in ONAP as of now. What stops you to install PNDA in the kubernetes outside of ONAP helm charts? Nothing. And result is the same - because there is no integration - am I wrong? ONAP platform with all images together take cca 100 GB - that can be improved by using shared layers and base every ONAP component from one - maybe alpine. But that will not solve the problem I mentioned before - redundancy of frameworks, reinventing wheels and lack of any common ground - no core, no interface. Sorry for my rant - but, please, what is ONAP? Thank you -- Best regards, Petr Ospalý -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#17994): https://lists.onap.org/g/onap-discuss/message/17994 Mute This Topic: https://lists.onap.org/mt/32429722/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
