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 <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]> > [mailto:[email protected] <mailto:[email protected]>] > Sent: Wednesday, October 11, 2017 7:24 AM > To: RICHOMME Morgan IMT/OLN <[email protected] > <mailto:[email protected]>>; [email protected] > <mailto:[email protected]>; Delia Popescu <[email protected] > <mailto:[email protected]>>; Alexandru Avadanii > <[email protected] <mailto:[email protected]>>; Cristina > Pauna <[email protected] <mailto:[email protected]>>; > [email protected] <mailto:[email protected]> > Cc: opnfv-tech-discuss <[email protected] > <mailto:[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
