Few comments on this * To Fatih’s point (also developed in the thread [1]) and t repeat myself, we need to converge on the issue of container versioning first before deciding on which toolchain to use (internal Jenkins build or dockerhub build server). From what I can see dockerhub builds may have some restrictions in the way you can tag your images, let’s just make sure it works with whatever versioning scheme we decide to use. We will get more and more containers built, if we don’t get versioning right it will be real hard to track artifacts to code commits * I have not followed the thread but I’m curious to know why a container build order is needed (given that containers by design are independent of other containers at the build level)
Thanks Alec From: <opnfv-tech-discuss-boun...@lists.opnfv.org> on behalf of "morgan.richo...@orange.com" <morgan.richo...@orange.com> Date: Wednesday, August 30, 2017 at 2:43 AM To: Trevor Bramwell <tbramw...@linuxfoundation.org>, "opnfv-helpd...@rt.linuxfoundation.org" <opnfv-helpd...@rt.linuxfoundation.org> Cc: OLLIVIER Cédric IMT/OLN <cedric.olliv...@orange.com>, "opnfv-tech-discuss@lists.opnfv.org" <opnfv-tech-discuss@lists.opnfv.org> Subject: [opnfv-tech-discuss] [OPNFV] 2 questions on OPNFV docker repo Hi, 2 pending questions regarding the way we are managing our docker files 1) Cedric sent a mail 2 weeks ago ([OPNFV Helpdesk #42909] New Functest Docker repositories) in order to create new docker repositories: opnfv/functest-features, opnfv/functest-components and opnfv/functest-vnf As it has not been done yet we are currently using Cedric's private docker repo (where he customized the different hook) ollivier/functest-components, ollivier/functest-features and ollivier/functest-vnf and we referenced them in releng But, of course, it would make more sense to rely on official OPNFV docker... José asked Trevor B. to create the first repo (opnfv/functest-core, opnfv/functest-healthcheck and opnfv/functest-smoke) before he left in PTO. Cedric asked for the new repo on this mail thread. Should we create a new ticket? BTW it seems that there is an issue on the hooks used for OPNFV docker repos. Builds must be done in a precise order (core must be built prior to any other built), which seems not the case on OPNFV docker hub. Cedric detailed the issue and the fix (screenshots) in the same mail thread. Any help will be welcome to reference official sources. 2) At the moment the Docker automated builds are used per gerrit merge for all OPNFV projects. As we are using a basic account and the number of docker produced within OPNFV is increasing there is a high risk of congestion. Could it be possible to migrate to an account allowing parallel builds (https://hub.docker.com/billing-plans/). The cost is reasonable, we could start with a Medium or Large one. As docker management is transverse, widely used by testing projects, Who should take the lead to ask for such change to the TSC? Releng? Infra Group? Testig group? Any comment welcome /Morgan _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss _______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
