Dear Ed, What do we need to do to pass CI? Make build Make test?
Also including Make verify? Thank you, Tina On Apr 19, 2018, at 9:58 AM, Ed Kern <e...@cisco.com<mailto:e...@cisco.com>> wrote: On Apr 19, 2018, at 6:59 AM, Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco) <pmi...@cisco.com<mailto:pmi...@cisco.com>> wrote: Hello Ed, I rewrite the script to use apt-get/yum instead, but I have one concern if this is in compliance with you POC system. Can you please check? Dont see anything here that gives me pause about converting to container builds.. Many other questions about this gerrit..most I will include on the gerrit but… Without vratko working on the repo manifests those will still be incorrect is that right? This seems to lock to master branch only…you dont want/need ability to test release branches with whatever job runs this script? Not using ‘standard’ REPO_NAME also locks you into xenial which means this will be one more thing we need to revisit when we do bionic swing until im told otherwise opensuse is a ‘full citizen’ so please take that into account (in this case its easy since its the same as centos with the exception of the ARTIFACTS list. Ed I tested locally and looks like it is ok. But need to properly review. [1] https://gerrit.fd.io/r/#/c/11928/ Thank you. Peter Mikus Engineer – Software Cisco Systems Limited From: Ed Kern (ejk) Sent: Wednesday, April 18, 2018 5:10 PM To: Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco) <pmi...@cisco.com<mailto:pmi...@cisco.com>> Cc: Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) <vrpo...@cisco.com<mailto:vrpo...@cisco.com>>; Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgrad...@cisco.com<mailto:mgrad...@cisco.com>>; Maciek Konstantynowicz (mkonstan) <mkons...@cisco.com<mailto:mkons...@cisco.com>>; Vanessa Valderrama <vvalderr...@linuxfoundation.org<mailto:vvalderr...@linuxfoundation.org>>; csit-...@lists.fd.io<mailto:csit-...@lists.fd.io>; vpp-dev <vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>>; hc2...@lists.fd.io<mailto:hc2...@lists.fd.io>; honeycomb-...@lists.fd.io<mailto:honeycomb-...@lists.fd.io> Subject: Re: [csit-dev] [vpp-dev] ARM vpp-dpdk-dkms nexus artifacts - CSIT Dont get me wrong..im behind vratko’s thinking about doing the restructure…just didnt want to rush that in..(unless that fix is more simple than it appears) but wanted to get you working again right away. There is no point in just deleting the arm packages since they would just get repopulated quickly although I am still thinking about other options to explore.. Ed On Apr 18, 2018, at 9:05 AM, Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco) <pmi...@cisco.com<mailto:pmi...@cisco.com>> wrote: Thank you for the inputs. I agree that we can put temporary workaround although. Unless someone beats me I will do tomorrow. I think that long term solution is more than welcomed. Looking on this not only thru optics of CSIT but anyonw who will look on Nexus and would wonder why RELEASE is only arm64. Any views who is maintaining nexus storage from configuration point of view? Peter Mikus Engineer – Software Cisco Systems Limited From: Ed Kern (ejk) Sent: Wednesday, April 18, 2018 5:00 PM To: Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) <vrpo...@cisco.com<mailto:vrpo...@cisco.com>>; Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco) <pmi...@cisco.com<mailto:pmi...@cisco.com>> Cc: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgrad...@cisco.com<mailto:mgrad...@cisco.com>>; Maciek Konstantynowicz (mkonstan) <mkons...@cisco.com<mailto:mkons...@cisco.com>>; Vanessa Valderrama <vvalderr...@linuxfoundation.org<mailto:vvalderr...@linuxfoundation.org>>; csit-...@lists.fd.io<mailto:csit-...@lists.fd.io>; vpp-dev <vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>>; hc2...@lists.fd.io<mailto:hc2...@lists.fd.io>; honeycomb-...@lists.fd.io<mailto:honeycomb-...@lists.fd.io> Subject: Re: [csit-dev] [vpp-dev] ARM vpp-dpdk-dkms nexus artifacts - CSIT vratko: responding to the thread but NOT to your email.. im going to assume your correct that it is abusing the version field and that nexus could/should be doing something different..and what your saying about version timing makes sense since the arm64 flavor certainly came long after the amd64 was build and pushed to nexus. BUT..just as a datapoint and possible short term workaround If csit would just use apt-get download vpp-dpdk-dkms it appears (even with the current config/misconfig ) to pull the correct deb depending on your source arch. not sure if this could be a short term fix/workaround/replacement to your curl command. Ed On Apr 18, 2018, at 8:46 AM, Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) <vrpo...@cisco.com<mailto:vrpo...@cisco.com>> wrote: I have some experience with Maven and Nexus. > <groupId>io.fd.vpp</groupId> > <artifactId>vpp-dpdk-dkms</artifactId> > <version>18.02-vpp1_arm64</version> > <classifier>deb</classifier> > <type>deb</type> That sets "deb" to be both the classifier and the type. That is correct for the type, as it usually corresponds to the file extension. But we can use classifier to designate architecture. For more information, search for "Classifier:" (without quotes) here [3]. By the way, the incorrect thing we currently do is to overload the version field. Versions are assumed to be ordered linearly, so when comparing 18.02-vpp1_arm64 and 18.02-vpp1_amd64, one has to be newer. Here is my proposed fix: <groupId>io.fd.vpp</groupId> <artifactId>vpp-dpdk-dkms</artifactId> <version>18.02-vpp1</version> <classifier>arm64</classifier> <type>deb</type> Also, the code snippets which currently download the deb file should be updated to include the classifier value in the URL. Vratko. [3] https://maven.apache.org/pom.html#Dependencies From: csit-...@lists.fd.io<mailto:csit-...@lists.fd.io> <csit-...@lists.fd.io<mailto:csit-...@lists.fd.io>> On Behalf Of Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) Sent: Wednesday, 2018-April-18 16:24 To: Maciek Konstantynowicz (mkonstan) <mkons...@cisco.com<mailto:mkons...@cisco.com>>; Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco) <pmi...@cisco.com<mailto:pmi...@cisco.com>>; Ed Kern (ejk) <e...@cisco.com<mailto:e...@cisco.com>>; Vanessa Valderrama <vvalderr...@linuxfoundation.org<mailto:vvalderr...@linuxfoundation.org>> Cc: csit-...@lists.fd.io<mailto:csit-...@lists.fd.io>; vpp-dev <vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>>; hc2...@lists.fd.io<mailto:hc2...@lists.fd.io>; honeycomb-...@lists.fd.io<mailto:honeycomb-...@lists.fd.io> Subject: Re: [csit-dev] [vpp-dev] ARM vpp-dpdk-dkms nexus artifacts - CSIT +hc2vpp list From: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> [mailto:vpp-dev@lists.fd.io] On Behalf Of Maciek Konstantynowicz (mkonstan) Sent: 18 kwietnia 2018 16:23 To: Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco) <pmi...@cisco.com<mailto:pmi...@cisco.com>>; Ed Kern (ejk) <e...@cisco.com<mailto:e...@cisco.com>>; Vanessa Valderrama <vvalderr...@linuxfoundation.org<mailto:vvalderr...@linuxfoundation.org>> Cc: csit-...@lists.fd.io<mailto:csit-...@lists.fd.io>; vpp-dev <vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>> Subject: Re: [vpp-dev] ARM vpp-dpdk-dkms nexus artifacts - CSIT Thanks Peter ! This is affecting all CSIT vpp and honeycomb jobs that rely on Nexus images, including ALL periodic jobs - daily performance trending jobs, and semi-weekly and weekly jobs.. Ed, Vanessa, Could you pls help here? We will open the helpdesk ticket (Peter pls do that). -Maciek goo.gl/pR4k3y<http://goo.gl/pR4k3y> On 18 Apr 2018, at 12:47, Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco) <pmi...@cisco.com<mailto:pmi...@cisco.com>> wrote: Hello, I’ve recently found that a new package was introduced: 18.02-vpp1_arm64. I guess this is expected as of adding new architecture and onboarding ARM. I also found that currently vpp-dpdk-dkms package points the RELEASE version to arm64 instead of amd64 [1]. <metadata> <groupId>io.fd.vpp</groupId> <artifactId>vpp-dpdk-dkms</artifactId> <versioning> <latest>17.11-vpp1_amd64</latest> <release>18.02-vpp1_arm64</release> <versions> <version>18.02-vpp1_amd64</version> <version>18.02-vpp1_arm64</version> </versions> <lastUpdated>20180417190341</lastUpdated> </versioning> </metadata> This breaks our CSIT trending jobs as we are always pulling latest RELEASE version (once job is fired) and expecting that correct version is downloaded. Our command $ curl https://nexus.fd.io/service/local/artifact/maven/content?r=${REPO}&g=${GROUP}&a=${ART}&p=${PAC}&v=${VER}&c=${CLASS}<https://nexus.fd.io/service/local/artifact/maven/content?r=$%7bREPO%7d&g=$%7bGROUP%7d&a=$%7bART%7d&p=$%7bPAC%7d&v=$%7bVER%7d&c=$%7bCLASS%7d>" -O –J + curl 'https://nexus.fd.io/service/local/artifact/maven/content?r=fd.io.master.ubuntu.xenial.main&g=io.fd.vpp&a=vpp-dpdk-dkms&p=deb.md5&v=RELEASE&c=deb' -O -J As of now, is there any way to get the proper release version from nexus based on ARCH? E.g “PLATFORM” or similar [2]? <groupId>io.fd.vpp</groupId> <artifactId>vpp-dpdk-dkms</artifactId> <version>18.02-vpp1_arm64</version> <classifier>deb</classifier> <type>deb</type> If no, may I suggest to start using a new field in nexus for architecture if they will sit in one repo/dir so it can be easily downloaded for target platform? Thank you. [1] https://nexus.fd.io/service/local/repositories/fd.io.master.ubuntu.xenial.main/content/io/fd/vpp/vpp-dpdk-dkms/maven-metadata.xml [2] https://nexus.fd.io/#view-repositories;fd.io.master.ubuntu.xenial.main~browsestorage Peter Mikus Engineer – Software Cisco Systems Limited <image002.jpg> Think before you print. This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/index.html IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
