Hello, We simply require concurrent jobs properties which can be simplified here as parallel builds, concurrency control and dependency. They are mainly required as: - functest-core must be built before other Functest containers - other containers should be built in parallel as soon as functest-core is published - amd64 containers and arm64 containers should be built in parallel
I am not directly involved in Releng and I have read in reviews or mails that today's jjobs don't support that. All proposals to build Alpine containers haven't conformed with the concurrency control and the dependencies. @Fatih could you please confirm that? I'm quite sure that Jenkins supports them. In case of cross building arm64 images on amd64 PODs, we also require several operations on PODs: - to install qemu-user-static - to support binfmt-misc [1] The current Docker Automated builds had been fine before we were asked to build Alpine arm64 images and to publish stable tags: - arm64 images can't be built via this CI tool as it requires qemu-user-static and binfmt_misc [1] support on Docker hosts. - publishing stable tags triggers useless builds simply because they are already triggered by euphrates tags. I'm currently beta testing travis-ci to meet all requirements: - https://travis-ci.org/collivier/functest/builds/287849046 (stable/euphrates) - https://travis-ci.org/collivier/functest/builds/287745681 (master) It works very well and all scripts are ran in parallel for all steps: - build functest-core images - publish functest-core manifests - build all functest images - publish all manifests I am considering we do switch from Docker Automated builds to travis-ci for official Functest images if releng jjobs are not updated. But I think it's too late regarding the deadline for E as we should multiply CI runs. @David, do you agree? (Of course I am not allowed to configure travis-ci for OPNFV github repositories). I will deeply update the wiki page "Docker Requirements on Releng" [2] [1] https://www.kernel.org/doc/html/v4.11/admin-guide/binfmt-misc.html [2] https://wiki.opnfv.org/display/functest/Docker+Requirements+on+Releng Cédric 2017-10-11 9:56 GMT+02:00 Jose Lausuch <[email protected]>: > Maybe late for 5.0, but not late for Euphrates 5.1. > > Can we collect a list the requirements we need from Releng in this wiki [1]? > It will facilitate the support and I will help to speed it up. Otherwise, > nothing will happen as people don’t know what we need. > > [1] https://wiki.opnfv.org/display/functest/Docker+Requirements+on+Releng > > > > > > > On 11 Oct 2017, at 09:42, Cristina Pauna <[email protected]> wrote: > > Hi Cedric, > > Which E are you refering to in this email? The one with deadline on 15th > December? > > Cristina > > From: [email protected] [mailto:[email protected]] > Sent: Wednesday, October 11, 2017 7:24 AM > To: RICHOMME Morgan IMT/OLN <[email protected]>; > [email protected]; Delia Popescu <[email protected]>; Alexandru > Avadanii <[email protected]>; Cristina Pauna > <[email protected]>; [email protected] > Cc: opnfv-tech-discuss <[email protected]> > Subject: Re: [functest] Alpine for arch > > > Hello, > > I quickly tested to build aarch64 Functest images via Docker automated > builds what is impossible (several prerequisites are unmet). I precise the > first published images were built locally. > > I'm thinking about an alternative way which will be too much disruptive for > E release. Again it will be suitable for my own repositories. But releng > should have been the target to build all Docker images (I bet it won't be > ready for E). Today's releng can't meet functest prerequisites about Docker. > > I will inform as soon as my own repositories are ready. > > Cédric > > ---- Cristina Pauna a écrit ---- > > Hi, > > There has been a lot of confusion and changes around this topic and I want > to clear things up going forward, so we do not waste any of our time. > What I understand from all the disparate discussions around this topic is: > 1. We will not do alpine for E0 release on arm, we are targeting E1/E2 > 2. For the Functest-core image we will have 1 Dockerfile for x86, and > a patch for arm that overrides this Dockerfile; from this file we will > create one Functest-core image and thearchitecture will be mentioned in its > tag > 3. The subsequent images (Functest-healthcheck, Functest-smoke, etc) > will be based on the previously built Functest-core image. We will do a > manifest to choose the correct Functest-core image based on its tag. These > dependent images will also have its arch in the tag. > 4. The problem we are facing now is how to make sure that for 1 build, > the Functest-core image always get built before the other ones. For x86 that > is now done with a workaround directly in dockerhub. The target is to do it > with Jenkins jobs builders, considering image dependencies. > > Is this the approach we are all agreeing on? > > Thanks, > Cristina > > _________________________________________________________________________________________________________________________ > > > > 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 > [email protected] > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > _______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
