Hi Paul,
thanks for the explanation. It's good to know, that existing installation procedure can be reused for auto project. Regards, Martin ________________________________ Od: Paul Vaduva <paul.vad...@enea.com> Odesláno: úterý 12. června 2018 11:49 Komu: Klozik Martin Kopie: Tina Tsou; gerard.d...@wipro.com; Cristina Pauna; Joe Kidder; opnfv-tech-discuss@lists.opnfv.org Předmět: RE: [Auto] Jenkins for Auto Hi Martin, See my comments inline... -----Original Message----- From: Klozik Martin <martin.klo...@tieto.com> Sent: Tuesday, June 12, 2018 10:46 AM To: Paul Vaduva <paul.vad...@enea.com> Cc: Tina Tsou <tina.t...@arm.com>; gerard.d...@wipro.com; Cristina Pauna <cristina.pa...@enea.com>; Joe Kidder <joe.kid...@gmail.com>; opnfv-tech-discuss@lists.opnfv.org Subject: Re: [Auto] Jenkins for Auto Hi Paul, thanks for taking care about initial yaml file definition at jjb/auto/auto.yaml. I've also noticed your +1 to my "ci/build-auto.sh" patch. It was acked by other team members too, so we will go ahead with my proposal. Let me try to summarize my understanding of your CI job configuration. Please let me know your comments (that applies to all). Your idea is to utilize Armband project for OPNFV installation via FUEL at ARM POD. I'm not familiar with the details, but it seems, that current configuration (with PROJECT=armband) works only for armband repository. Do you know if it can be modified/configured to properly install OPNFV at our pod while still utilizing existing build framework? [Paul Vaduva] Yes, thats true I made a job for deploying fuel armband version, it there will be other installers we would probably need other ci jobs that will install (compass, apex, etc..), Yes I already proposed a patch to extend armband deploy job template to accept project parameter. https://gerrit.opnfv.org/gerrit/#/c/58415/ If not, we would probably need to do it "manually", e.g. to introduce "install_opnfv" function into ci/build-auto.sh, which will: 1) clone armband repo as part of our CI job 2) modify WORKSPACE to point to armband repo 3) execute ci/deploy.sh from armband (and other steps if required) to take care about OPNFV installation 4) restore WORKSPACE to its orignal value before ONAP deployment [Paul Vaduva] I thought about this as well (deploying Openstack as part of auto ci job but it seem to be much more effort in maintaining the deploy procedure then the previous variant (just using armband template for deploying their project). It seems to make more sense to keep the Openstack deploying separated from ONAP deployment. Of course we would have to update this logic in the future to support both arm and x64 pods. Best Regards, Martin Od: Klozik Martin Odesláno: čtvrtek 7. června 2018 9:57 Komu: Joe Kidder; Paul Vaduva Kopie: Tina Tsou; gerard.d...@wipro.com<mailto:gerard.d...@wipro.com>; Cristina Pauna Předmět: Re: Jenkins for Auto Direct link to previously mentioned gerrit draft review: https://gerrit.opnfv.org/gerrit/#/c/58307/ --Martin Od: Klozik Martin Odesláno: čtvrtek 7. června 2018 9:48 Komu: Joe Kidder; Paul Vaduva Kopie: Tina Tsou; gerard.d...@wipro.com<mailto:gerard.d...@wipro.com>; Cristina Pauna Předmět: Re: Jenkins for Auto Hi Paul, just for the sake of discussion, I've prepared a draft patch of possible ci script skeleton. In case that we will decide to go in this direction it can be used as an initial version straight away and simply called from jenkins yaml file. May be we can do a simple vote in gerrit by adding +1 or -1. Best Regards, Martin Od: Klozik Martin Odesláno: čtvrtek 7. června 2018 9:07:36 Komu: Joe Kidder; Paul Vaduva Kopie: Tina Tsou; gerard.d...@wipro.com<mailto:gerard.d...@wipro.com>; Cristina Pauna Předmět: Re: Jenkins for Auto Thanks Joe for adding me in the loop. Hi Paul, I'm sorry, I was not aware of your activities. I've sent a few thoughts about possible Auto CI (initial) configuration into the Auto mailing list. Could you please have a look at it? Based on this thread I can see that you're about to define a yaml file and prepare initial body of Auto jobs (daily/verify/merge). Let me know if I can be of any help. In a nutshell, I was proposing the same concept as is used by vswitchperf project for some time and later adopted by storperf too. It means, to define only minimalistic YAML file with definition of jobs frequency, allowed slaves, etc. and then to invoke a script stored inside Auto repo (e.g. ci/build-auto.sh) with the name of the job (e.g. ci/build-auto.sh verify). We can start with empty body, so all jobs will always end with success if slave (unh-pod1) is up and auto repository clones smoothly. Later we can add a real stuff there, based on the progress of platform installation scripts (for OPNFV and ONAP) and Auto tests automation. My idea was to start with a common functions (inside build-auto.sh) for platform installation (which can be shared among all jobs). Based on the experience we can later split it to separate jobs to get some visibility of particular "sub-task" stability directly in the Jenkins job history. Best Regards, Martin BTW, could you please CC "auto mailing list" in the future discussions? So the knowledge is spread among the team and properly archived by the mailing list. Thanks. Od: Joe Kidder <joe.kid...@gmail.com<mailto:joe.kid...@gmail.com>> Odesláno: středa 6. června 2018 13:11 Komu: Paul Vaduva Kopie: Tina Tsou; gerard.d...@wipro.com<mailto:gerard.d...@wipro.com>; Cristina Pauna; Klozik Martin Předmět: Re: Jenkins for Auto Paul, Martin Klozic is also looking at CI. Just a heads up to avoid collisions. Joe On Jun 6, 2018, at 6:48 AM, Paul Vaduva <paul.vad...@enea.com<mailto:paul.vad...@enea.com>> wrote: Hi Tina, I was in vacation last week, I will take a look at auto jobs now. Best Regards Paul From: Tina Tsou <tina.t...@arm.com<mailto:tina.t...@arm.com>> Sent: Friday, June 1, 2018 10:50 PM To: Paul Vaduva <paul.vad...@enea.com<mailto:paul.vad...@enea.com>>; Joe Kidder <joe.kid...@gmail.com<mailto:joe.kid...@gmail.com>> Cc: gerard.d...@wipro.com<mailto:gerard.d...@wipro.com>; Cristina Pauna <cristina.pa...@enea.com<mailto:cristina.pa...@enea.com>> Subject: RE: Jenkins for Auto Dear Paul, Are you waiting for either Joe or Gerard to do something, before you try an OPNFV install? Thank you, Tina Tsou Enterprise Architect Arm tina.t...@arm.com<mailto:tina.t...@arm.com> +1 (408)931-3833 From: Paul Vaduva <paul.vad...@enea.com<mailto:paul.vad...@enea.com>> Sent: Friday, May 18, 2018 9:49 AM To: Joe Kidder <joe.kid...@gmail.com<mailto:joe.kid...@gmail.com>> Cc: gerard.d...@wipro.com<mailto:gerard.d...@wipro.com>; Tina Tsou <tina.t...@arm.com<mailto:tina.t...@arm.com>>; Cristina Pauna <cristina.pa...@enea.com<mailto:cristina.pa...@enea.com>> Subject: RE: Jenkins for Auto Hi, Due to some naming conflictes we had to rename arm-pod7 to unh-pod1 https://build.opnfv.org/ci/computer/unh-pod1/ So the previous link is the correct one. I will start Monday on the next phase: deploying mcp. Joe I saw a lot of diskspace used in the /armband dir of the jumpserver, bringing the total disk space used to 96% of available space it looks like deploy tests does anyone use them or I can delete them, cause when autodeploy will create environment I expect the jenkins slave to run out of space. Thsanks Paul From: Paul Vaduva Sent: Thursday, May 17, 2018 12:01 PM To: 'Joe Kidder' <joe.kid...@gmail.com<mailto:joe.kid...@gmail.com>> Cc: gerard.d...@wipro.com<mailto:gerard.d...@wipro.com>; tina.t...@arm.com<mailto:tina.t...@arm.com>; Cristina Pauna <cristina.pa...@enea.com<mailto:cristina.pa...@enea.com>> Subject: RE: Jenkins for Auto Hi, I finished setting up the Jenkins Slave (10.10.50.12) to register it for a CI pod in the Jenkins Master of OPNFV (It new appers as amr-pod7 https://build.opnfv.org/ci/computer/arm-pod7/ ) according to instruction here: http://docs.opnfv.org/en/stable-fraser/submodules/octopus/docs/octopus_docs/opnfv-jenkins-slave-connection.html The next phase is to set up the deploy of MCP on the UNH lab pod. I will wait for an OK from you Joe as in a prior conversation you said you still have to save some work from the pod) Cheers, Paul From: Joe Kidder <joe.kid...@gmail.com<mailto:joe.kid...@gmail.com>> Sent: Wednesday, May 16, 2018 1:50 PM To: Paul Vaduva <paul.vad...@enea.com<mailto:paul.vad...@enea.com>> Cc: gerard.d...@wipro.com<mailto:gerard.d...@wipro.com>; tina.t...@arm.com<mailto:tina.t...@arm.com>; Cristina Pauna <cristina.pa...@enea.com<mailto:cristina.pa...@enea.com>> Subject: Re: Jenkins for Auto Paul, Now at my computer - the section “Network Topology” on the https://wiki.opnfv.org/display/AUTO/Auto+Lab+Deployment page has much of the information you asked about. Joe On May 16, 2018, at 6:27 AM, Paul Vaduva <paul.vad...@enea.com<mailto:paul.vad...@enea.com>> wrote: Morning Joe, The redeploy it’s a bit premature now but I will let you know so you can save your work of course. Thanks Paul From: Joe Kidder <joe.kid...@5thlayer.com<mailto:joe.kid...@5thlayer.com>> Sent: Wednesday, May 16, 2018 1:16 PM To: Paul Vaduva <paul.vad...@enea.com<mailto:paul.vad...@enea.com>> Cc: gerard.d...@wipro.com<mailto:gerard.d...@wipro.com>; tina.t...@arm.com<mailto:tina.t...@arm.com>; Cristina Pauna <cristina.pa...@enea.com<mailto:cristina.pa...@enea.com>> Subject: Re: Jenkins for Auto Paul, Just waking up here but there is some info on the auto lab deployment page in the wiki (towards the bottom). I think I put pages holding the idf and pdf, but the files are sitting in a labs directory in /home/ubuntu on the jumphost. I should have also put the deploy command line on the wiki. 10.10.50.12 is the jumphost. ubuntu is user ubuntu is pass I’ll send you the ipmi info shortly, but the network is 10.10.52.0/24. You can use ipmitool and a web based ipmi interface. I may want to extract some things from the pod prior to redeploy so let me know if you are going to do that. Thanks! Joe On May 16, 2018, at 6:00 AM, Paul Vaduva <paul.vad...@enea.com<mailto:paul.vad...@enea.com>> wrote: Hi again, I just realized that I need a bit more info about the pod, how can I connect to the targets, how can I find ipmi info ? Also how do I connect to the jump server, I couldn’t find it on the booking page. Joe, Cristina tells me you have an initiall pdf/idf, are the ones from the wiiki the version of the files you have ? Thanks, Paul From: Paul Vaduva Sent: Wednesday, May 16, 2018 12:05 PM To: 'gerard.d...@wipro.com' <gerard.d...@wipro.com<mailto:gerard.d...@wipro.com>>; tina.t...@arm.com<mailto:tina.t...@arm.com>; Cristina Pauna <cristina.pa...@enea.com<mailto:cristina.pa...@enea.com>>; Joe Kidder <joe.kid...@5thlayer.com<mailto:joe.kid...@5thlayer.com>> Subject: RE: Jenkins for Auto Hi all, The info seems to be complete and very detailded. I will start Seting up the Jenkins slave on the UNH laab accroding to step 1, and keep you posted. Cheers, Paul From: gerard.d...@wipro.com<mailto:gerard.d...@wipro.com> <gerard.d...@wipro.com<mailto:gerard.d...@wipro.com>> Sent: Wednesday, May 16, 2018 12:10 AM To: tina.t...@arm.com<mailto:tina.t...@arm.com>; Cristina Pauna <cristina.pa...@enea.com<mailto:cristina.pa...@enea.com>>; Joe Kidder <joe.kid...@5thlayer.com<mailto:joe.kid...@5thlayer.com>> Cc: Paul Vaduva <paul.vad...@enea.com<mailto:paul.vad...@enea.com>> Subject: Jenkins for Auto Hi, Cristina, Joe and I had a meeting this morning, and Cristina very helpfully walked us through the steps to get Jenkins jobs up and running. I captured some notes on the Auto wiki page: https://wiki.opnfv.org/display/AUTO/CI+Plan+for+Auto (all, please review/update if anything is missing or incorrect). We’ll look into that, and Paul was volunteered ;) to help with the initial setup of the Jenkins slave on the Arm pod and the initial Auto YAML file. Once the first Auto Jenkins job has run successfully, we’ll be pretty much independent (to make updates down the road). Cheers, Gerard The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com<http://www.wipro.com> 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. 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. 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. 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.
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
