Thanks your Trevor Best Regards, Paul
From: LOVETT, TREVOR J <[email protected]> Sent: Friday, July 19, 2019 4:22 PM To: [email protected]; Paul Vaduva <[email protected]> Cc: WRIGHT, STEVEN A <[email protected]>; Jessica Wagantall <[email protected]>; Jim Baker <[email protected]>; Kenny Paul <[email protected]> Subject: RE: [onap-discuss][vvp] docker image dependency chart Yes, the information for vvp is correct. We have no special requirements for a base image as long as it has Python 3.6+. If a new standard base is chosen, then please let us know and we will migrate. Please note that this image is not deployed as part of OOM. Thanks, Trevor Lovett Lead Member of Technical Staff AT&T Labs, Operational Automation and Program Management From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Paul Vaduva Sent: Friday, July 19, 2019 2:51 AM To: [email protected]<mailto:[email protected]> Cc: WRIGHT, STEVEN A <[email protected]<mailto:[email protected]>>; Jessica Wagantall <[email protected]<mailto:[email protected]>>; Jim Baker <[email protected]<mailto:[email protected]>>; Kenny Paul <[email protected]<mailto:[email protected]>> Subject: [onap-discuss][vvp] docker image dependency chart Hi vvp team I am Paul Vaduva and I am part of the dockerhub migration effort together with Linux Foundation, as presented in various meetings at the DDF in June and anounced in multiple TSC meetings we need to create a dependency chart of docker images for every ONAP project before the migration happens in order for it to run smoothly according to Linux Foundation. As the team who is working on the vvp project you are the ones to ask about this docker images dependency list. However because your time is preciouse and there is a constant need of resources, I started this effort to create the dependency chart of all the docker images for all the project. Due to the multitude of docker iamges the manual process is tedious at best so I used an automated text parser to make a best effort list which is not complete and cannot be due to multiple inconsistent type of formated text output in docker build jobs logs. However it's a starting point and since each tech team should have the final work I invite you to have a look at the dependency list for vvp porject and give input in some form of your choosing (comments, edits, reply to this email, etc.) here: https://wiki.onap.org/display/DW/Docker+images+dependency+list<https://url10.mailanyone.net/v1/?m=1hoSqC-0004Dw-60&i=57e1b682&c=fwhxqVA0VVwldIgczfGQr_WyXiDznwlui-zBq6D3i2p-4-ybmcvGZ6JOchMS_alNHrSRRMX1sAVQj2CNbRnVgplqTgvIuuW_DfLa6RSQrGwsMNlrWnAdo9hgdwKvCBnhIHtTx23F8EEO_wm0f2-ZCAVGKT-bFRlP1m46Oabxj4cLKuMVi5oe2IuW87_UKH1Llbz3tNe7F0h7CGm3jHgsNTvRIPZkilPBi21TA1RUMjWPEaiRFmQzmbkBGh1KqQEZcICKtay2vhmYz1Xkswzy-erm9QVCfUhd7siURXJMeKcjfAs4P16TzuuntvbN2Hegt14Tb2fchGCZkbzwJTBVex_NdxOO8dCSEmOxV9eGOJAAEo4OwV4tw9a0HWq-sQfXxacTf6aNGgzbA2Hga4z13MYZz_Bj52yHn2VCW5VV3TBF7eJP1rfhUks6ArCIdnIJCtb_ALqJtflFd82hO4K_cXare5CyfHHp05seQYHI47Q-OZPtIFsNgTGquhZOuT5nDBRWtPlRrRsi2kmQovz8ciE5mCExktDqFFJ2yo-ie3wxfhstSdg_TExf0TQjXSws> You can see the list of docker images dependencies for each project in a roughly form like this: 1 --> 2 --> 3 ... --> n where 1 is the dependency for the image (what you find in the FROM clause of a Dcokerfile), 2 is the dependent image (the name of the image that your project builds) and form 3 onward there are usually other tags of the same proejct image. The previous wiki page is just a way to centralize the information regarding docker iamges dependency chart. As Martial (PTL of clamp project) mentioned you can intruduce in the list the docker-compose dependencies (They are usually upstream project so already in dockerhub but better check them as well). Thank you, Paul This message, including attachments, is CONFIDENTIAL. It may also be privileged or otherwise protected by law. If you received this email by mistake please let us know by reply and then delete it from your system; you should not copy it or disclose its contents to anyone. All messages sent to and from Enea may be monitored to ensure compliance with internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, a mended, lost or destroyed, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Anyone who communicates with us by email accepts these risks. This message, including attachments, is CONFIDENTIAL. It may also be privileged or otherwise protected by law. If you received this email by mistake please let us know by reply and then delete it from your system; you should not copy it or disclose its contents to anyone. All messages sent to and from Enea may be monitored to ensure compliance with internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, a mended, lost or destroyed, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Anyone who communicates with us by email accepts these risks. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#18213): https://lists.onap.org/g/onap-discuss/message/18213 Mute This Topic: https://lists.onap.org/mt/32524592/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
