On Sat, Aug 18, 2018 at 4:12 AM Viswanath V Kumar Skand Priya < [email protected]> wrote:
> Hi Tal / All, > > Thanks for starting this thread to address this important issue and I > second both Tal's & Michael's view as well. Infact we are now currently > breaking our heads to bring up ONAP "behind corporate proxies" and almost > 80% of operational issue which we always run into is this internet > dependencies. > I was thinking about this more over the weekend, and I am starting to think that a process like this would work reasonably: - Create a repo for "official ONAP base images", basing the contents off what is currently used in OOM -- so for example if there are lots of users of Ubuntu 16.04, then we just create a ubuntu-lts image in said repo. - Rebase existing Dockerfiles to use the official base image which maps to their current base. This at least makes it clearer what we're using, as well as making it easier to then "push dependancies down" into those central base images. I think its pretty clear that we need to simplify what we depend on (15 different JDK base images right now, 11 different specifications for the Ubuntu version, etc). I'm not opposed to letting deployers substitute their chosen SOE images in for the central ones, and having those all in one place would certainly make that easier. For reference, there are 96 unique "FROM" lines in ONAP Dockerfiles at the moment. Thoughts? Michael -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11937): https://lists.onap.org/g/onap-discuss/message/11937 Mute This Topic: https://lists.onap.org/mt/24626855/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
