| *** mnaser has quit IRC | 01:13 | |
| *** mnaser has joined #airshipit | 01:16 | |
| *** aedan9902_2 has joined #airshipit | 02:13 | |
| *** aedan9902_1 has quit IRC | 02:15 | |
| *** aedan9902_2 has quit IRC | 02:17 | |
| *** aedan9902_2 has joined #airshipit | 02:43 | |
| *** thansen1 has joined #airshipit | 03:33 | |
| *** thansen has quit IRC | 03:38 | |
| *** thansen1 is now known as thansen | 03:38 | |
| *** aedan9902_3 has joined #airshipit | 09:04 | |
| *** aedan9902_2 has quit IRC | 09:04 | |
| *** uzumaki has joined #airshipit | 10:48 | |
| *** uzumaki has quit IRC | 11:17 | |
| *** uzumaki has joined #airshipit | 12:30 | |
| *** mnaser has quit IRC | 13:00 | |
| *** mnaser has joined #airshipit | 13:01 | |
| *** uzumaki has quit IRC | 13:38 | |
| *** aedan9902_3 is now known as aedan9902 | 14:45 | |
| *** uzumaki has joined #airshipit | 15:25 | |
| aedan9902 | Hello. Are there hardware profiles for anything other than a dell r720? | 15:33 |
|---|---|---|
| *** ThePherm has joined #airshipit | 15:34 | |
| airship-irc-bot1 | <kk6740> Hello everyone, please note that jenkins for airshipctl fails to report results back to zuul after conducting tests. Arijit is working to resolve the issue | 16:03 |
| airship-irc-bot1 | <tr.airship.slack> Hello, if someone can advise me how to install OpenStack (a link is OK) after the installation of developer airshipctl v2, I would be "happy". Thanks in advance | 16:31 |
| airship-irc-bot1 | <alexander.hughes> airshipui minor gosec updates ready for review https://review.opendev.org/c/airship/airshipui/+/773087 | 16:46 |
| airship-irc-bot1 | <alexander.hughes> Arijit reports Zuul issue is resolved now, if you had a successful run but no +1 vote please mention the patch here for manual +1 | 16:48 |
| airship-irc-bot1 | <kk6740> Issue with jenkins seems to be fixed | 19:16 |
| *** uzumaki has quit IRC | 19:27 | |
| aedan9902 | Hi All. It looks like nobody here is willing or able one of the two to answer my earlier question. So is there somewhere else I should be asking the question? | 20:17 |
| aedan9902 | for the sake of just making sure you know what the question was. Here it is again | 20:18 |
| aedan9902 | Are there hardware profiles for anything other than a dell r720? | 20:18 |
| airship-irc-bot1 | <steven.fitzpatrick> After Sirajudeen's PS merged to Reuse phase, executor from airshipctl in treasuremap, is there a recommended place to add new phases? Previously I had them added to `treasuremap/manifests/type/airship-core/phases/phases.yaml` | 20:42 |
| airship-irc-bot1 | <alexander.hughes> @aedan9902 we use Treasuremap as a reference to base your deployments off. there's sample documents for a dell r720 profile there, but that's all. you can create your own profiles as needed for your specific use cases | 20:45 |
| airship-irc-bot1 | <steven.fitzpatrick> Hey @tr.airship.slack, I don't believe this is fully ready to go at the moment, but there is an effort underway to manage the openstack-helm charts as airship 2 composites. https://review.opendev.org/admin/repos/openstack/openstack-helm-deployments | 20:47 |
| airship-irc-bot1 | <tr.airship.slack> Thanks Steven. | 20:49 |
| airship-irc-bot1 | <tr.airship.slack> Indeed, I saw it some days ago. But I thought that something was 'more' integrated into airship to manage OpenStack. Thus my new understanding is that Airship install "K8s" and OpenStack is installed through Helm. Is that the big picture? | 20:54 |
| aedan9902 | ok so the dell r720 in treasuremap is only an example and others need to be created in order to represent your specific hardware. There is no repo with a list of pre-configured hardware. I understand that. Makes sense. Thank you for the response | 20:57 |
| *** aedan has joined #airshipit | 21:01 | |
| airship-irc-bot1 | <steven.fitzpatrick> Yeah, I think you've got it. Airship plays the role of managing the documents that define your k8s cluster and the workloads you'll run on it. Those workloads could be openstack via the openstack-helm charts, or anything else you could deploy on k8s. | 21:06 |
| airship-irc-bot1 | <mattmceuen> Hey, it looks like we have the airship-airshipctl-gate-script-runner enabled as a voting gate these days. I thought we'd planned to make that non-voting (or take out the job) now that we have 3rd-party gating running the same test? | 21:29 |
| airship-irc-bot1 | <mattmceuen> Did we not turn voting off yet, or did we turn it back on for some reason? | 21:29 |
| airship-irc-bot1 | <alexander.hughes> blame looks like it's been enabled for 3 months https://opendev.org/airship/airshipctl/commit/68542a8c0a77a6ab3179de4cd5b8395b9333e201 I believe we just forgot to disable this after our conversations are leveraging 3rd party CI instead, but would need to look through meeting logs to be sure | 21:33 |
| airship-irc-bot1 | <dwalt> yeah, the PS that added it to the gate list precedes the one that moved it to experimental | 21:33 |
| airship-irc-bot1 | <dwalt> it's only in the gate list, so it looks like it was just left by accident | 21:34 |
| airship-irc-bot1 | <alexander.hughes> simple enough fix, who wants it? | 21:34 |
| airship-irc-bot1 | <kk6740> no no no :slightly_smiling_face: | 21:34 |
| airship-irc-bot1 | <kk6740> gate runner is voting only on merges | 21:34 |
| airship-irc-bot1 | <kk6740> if it doesn’t | 21:34 |
| airship-irc-bot1 | <kk6740> we going to have broken code | 21:34 |
| airship-irc-bot1 | <mattmceuen> ah, yes | 21:35 |
| airship-irc-bot1 | <kk6740> because it compares it against current state of master | 21:35 |
| airship-irc-bot1 | <sirajudeen.yasin> yes, jenkins runs only on new PS | 21:35 |
| airship-irc-bot1 | <kk6740> tests in patchset is run against patchset, not against master | 21:35 |
| airship-irc-bot1 | <kk6740> so zuul merges patchset into current master, and runs tests, jenkins can not do that | 21:35 |
| airship-irc-bot1 | <alexander.hughes> jenkins can trigger on change-merged events, but I think what you meant to say is that jenkins can't act as a voting gate during the merge but zuul can | 21:36 |
| airship-irc-bot1 | <kk6740> yes | 21:37 |
| airship-irc-bot1 | <alexander.hughes> so am I understanding correctly then, 3rd party CI is running the same checks, but Zuul runs the final gate and that's intentional | 21:37 |
| airship-irc-bot1 | <kk6740> well i think it can, but it would require completely different configuration | 21:37 |
| airship-irc-bot1 | <kk6740> @alexander.hughes yes, @sirajudeen.yasin has more on this i think | 21:38 |
| airship-irc-bot1 | <kk6740> i think he is the mastermind :slightly_smiling_face: | 21:38 |
| airship-irc-bot1 | <sirajudeen.yasin> @alexander.hughes, change-merged event will be after merge right.. can that stop merging the PS | 21:39 |
| airship-irc-bot1 | <alexander.hughes> right, change-merged is when a particular patchset has already merged into master, and then jenkins evaluates that patchset (master) | 21:40 |
| airship-irc-bot1 | <dwalt> Can you trigger from a WF +1 event? | 21:41 |
| airship-irc-bot1 | <sirajudeen.yasin> yes, so if i understand correct, it is important to run gate runner via zuul at gate stage | 21:41 |
| airship-irc-bot1 | <sirajudeen.yasin> @dwalt, checking for that option | 21:41 |
| airship-irc-bot1 | <alexander.hughes> not sure on the WF +1 thinking... if you get WF +1 you already have in normal cases 2x +2s and then Zuul's gates begin | 21:42 |
| airship-irc-bot1 | <alexander.hughes> unless Jenkins can place a blocking vote like Zuul's -2 when gates fail, and that actually block the merge, may have cases where zuul gates complete before jenkins and then merges | 21:43 |
| airship-irc-bot1 | <dwalt> Jenkins would have to restore its -1, rebase the patch, and test again | 21:43 |
| airship-irc-bot1 | <dwalt> not sure about the -2, good point | 21:44 |
| airship-irc-bot1 | <sirajudeen.yasin> the current trigger criteria for jenkins is whenever ther is a new PS. | 21:44 |
| airship-irc-bot1 | <sirajudeen.yasin> these are the only options to trigger jenkins | 21:45 |
| airship-irc-bot1 | <alexander.hughes> yeah I think Drew was looking for a relatively easy way to shift airship gate running 100% to third party CI | 21:45 |
| airship-irc-bot1 | <sirajudeen.yasin> | 21:45 |
| airship-irc-bot1 | <alexander.hughes> rather than checks on 3rd party and gate on Zuul | 21:45 |
| airship-irc-bot1 | <alexander.hughes> cuts down on maintaining duplicate code, etc. | 21:45 |
| airship-irc-bot1 | <dwalt> Bummer. There is also a gerrit setting that will treat patches that are not rebased on the tip of master as merge conflict, but that would probably be more of a headache than its worth to move that job out of voting | 21:46 |
| airship-irc-bot1 | <dwalt> especially if the nodepool has the capacity | 21:47 |
| airship-irc-bot1 | <alexander.hughes> Siraj, are there additional options on Comment Added? I wonder if one of the comment categories can be a work flow/code review event? | 21:49 |
| airship-irc-bot1 | <alexander.hughes> https://plugins.jenkins.io/gerrit-trigger/ | 21:49 |
| airship-irc-bot1 | <sirajudeen.yasin> @alexander.hughes, i just see option to add regex to comment messages, otherwise nothing on the comment category for WF/CR, may be there should be some option/plugin to extend the event categories but not available directly | 21:53 |
| airship-irc-bot1 | <alexander.hughes> ah gotcha. just scratching my head on how we could accomplish 3rd party CI being the sole runner of airshipctl-gate-runner but still have it function right before merge without burdening code reviewers with strange comment conventions | 21:54 |
| airship-irc-bot1 | <alexander.hughes> e.g., leaving a -1 from Jenkins until zuul gives +1, then having the cores drop a "want to merge" comment to trigger the jenkins run for a +1 | 21:55 |
| airship-irc-bot1 | <alexander.hughes> anyway I'm out, have a good weekend all | 21:55 |
| airship-irc-bot1 | <sirajudeen.yasin> happy weekend.. we can explore options | 21:56 |
| *** uzumaki has joined #airshipit | 22:44 | |
| *** uzumaki has quit IRC | 22:49 | |
| *** uzumaki has joined #airshipit | 22:51 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!