[Gluster-infra] [Bug 1711945] create account on download.gluster.org
https://bugzilla.redhat.com/show_bug.cgi?id=1711945 spame...@redhat.com changed: What|Removed |Added Status|NEW |ASSIGNED Flags||needinfo?(mscherer@redhat.c ||om) --- Comment #2 from spame...@redhat.com --- Hi Michael Please create the account for me as well. Below are the required details: Public ssh key: ssh-rsa B3NzaC1yc2EDAQABAAABAQDHKKTwASBKVg4nN3p1vUj87906qFi8KQb/gTmt7ITPDg1GAvVhMJhbC4pT58/k9YjDf2Ez07VZ7fTYs9hqWHF4ZsJ2rbO2MPaHl4Fnfb8MP+Wq33juiznKRZU9+TRTFt83rDoRjDFwzhfGt6zdBPam6Etu0mR55OvWg8XM35wbdW0OP/pjIdQdjVoDp+YdpaX43lCr3M80NsbjAxk7xcPTrpqAK90qpVw1C5mqwHNeqJIGK/enADhaDaMhBPoNpWK1cy5xMnJcBbYXjrUZ4yqmhzJ48yUQiHYzlZZkx4JirbdZzE7FfRZt88crec9KTp1a/GLznP3L0dFA59SWAMKV root@shep-mac User name: spamecha -- You are receiving this mail because: You are on the CC list for the bug. ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1744671] New: Smoke is failing for the changeset
https://bugzilla.redhat.com/show_bug.cgi?id=1744671 Bug ID: 1744671 Summary: Smoke is failing for the changeset Product: GlusterFS Version: 6 Status: NEW Component: project-infrastructure Assignee: b...@gluster.org Reporter: shegg...@redhat.com CC: b...@gluster.org, gluster-infra@gluster.org Target Milestone: --- Classification: Community Description of problem: Smoke job is failing for https://review.gluster.org/#/c/glusterfs/+/23284/ . Recheck is also not working properly. Please fix the issue. -- You are receiving this mail because: You are on the CC list for the bug. ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1711950] Account in download.gluster.org to upload the build packages
https://bugzilla.redhat.com/show_bug.cgi?id=1711950 --- Comment #12 from M. Scherer --- I created the user, tell me if it doesn't work. The server is download.rht.gluster.org (not download.gluster, who is a proxy). -- You are receiving this mail because: You are on the CC list for the bug. ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1727727] Build+Packaging Automation
https://bugzilla.redhat.com/show_bug.cgi?id=1727727 --- Comment #18 from hari gowtham --- (In reply to hari gowtham from comment #13) > (In reply to M. Scherer from comment #12) > > Ok, so I will install the packages on the builder we have, and then have it > > added to jenkins. > > (and while on it, also have 2nd one, just in case) > > Forgot to mention that this script file is also necessary: > https://github.com/Sheetalpamecha/packaging-scripts/blob/master/ > generic_package.sh > Will send a patch to have it in the repo. The above mentioned file is sent as a patch at: https://review.gluster.org/#/c/build-jobs/+/23289 > > > > > As for running different job running on specific machine, that's indeed > > pretty annoying on jenkins. I do not have enough experience with jjb, but > > JobTemplate is likely something that would help for that: > > https://docs.openstack.org/infra/jenkins-job-builder/definition.html#id2 > > Will look into it. I'm new to writing jobs for jenkins. > > > > > But afaik, gluster is not dependent on the kernel, so building that with > > pbuilder in a chroot should be sufficient no matter what Debian, as long as > > it is a up to date one, no ? > > Yes, gluster is not dependent on kernel, but I'm unaware of using chroot > for different debian version . > For this Kaleb would be the better person to answer. > @kaleb can you please answer this? -- You are receiving this mail because: You are on the CC list for the bug. ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1727727] Build+Packaging Automation
https://bugzilla.redhat.com/show_bug.cgi?id=1727727 --- Comment #17 from Kaleb KEITHLEY --- (In reply to M. Scherer from comment #15) > I did push the installation and I would like to defer the gnupg integration > for now, as it likely requires a bit more discussion (like, how do we > distribute the keys, etc, do we rotate it). > > And for the pbuilder cache, I would need to know the exact matrix of > distribution we want to build and how. That part seems not too hard: > https://wiki.debian.org/ > PbuilderTricks#How_to_build_for_different_distributions > > And if we aim to build on unstable, we also may need to do some work to keep > the chroot updated (same for stable in fact). The keys that we've been using were generated on an internal machine and distributed to the build machines, which are all internal as well. We were using a new, different key for every major version through 4.1, but some people complained about that, so for 5.x, 6.x, and now 7.x we have been using the same key. As 4.1 is about to reach EOL that essentially means we are only using a single key now for all the packages we build. AFAIK people expect the packages to be signed. And best practices suggests to me that they _must_ be signed. Given that 7.0rc0 is now out and packages will be signed with the current key, that suggests to me that we must keep using that key for the life of 7.x. We can certainly create a new key for 8.x, when that rolls around. And yes, we need a secure way to get the private key onto the jenkins build machines somehow. -- You are receiving this mail because: You are on the CC list for the bug. ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1727727] Build+Packaging Automation
https://bugzilla.redhat.com/show_bug.cgi?id=1727727 Kaleb KEITHLEY changed: What|Removed |Added Flags|needinfo?(kkeithle@redhat.c | |om) | --- Comment #16 from Kaleb KEITHLEY --- yes, pbuilder is a chroot tool, similar to mock. Each time you build you get a clean chroot. We are currently building for stretch/9, buster/10, and bullseye/unstable/11. AFAIK the buildroot should be updated periodically for all of them; bullseye/unstable should probably be updated more frequently than the others. I don't know anything about pbuilder apart from what I mentioned above, and specifically I don't know anything about how to use pbuilder to build for different distributions on a single machine. I've been using separate stretch, buster, and bullseye installs on dedicated boxes to build the packages for that release of Debian. -- You are receiving this mail because: You are on the CC list for the bug. ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1711950] Account in download.gluster.org to upload the build packages
https://bugzilla.redhat.com/show_bug.cgi?id=1711950 --- Comment #11 from M. Scherer --- ok so 3 months is enougn (cause i also do not want to push unrealisitic deadline or more pressure, plus shit happen), I will add the account as soon as the previous ansible run finish. And if that's not enough, we can of course keep it open longer, just to be clear. But after jenkins issue last month, and the old compromise last time, we can't let stuff open too long if they are not going to clean themself. -- You are receiving this mail because: You are on the CC list for the bug. ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1727727] Build+Packaging Automation
https://bugzilla.redhat.com/show_bug.cgi?id=1727727 --- Comment #15 from M. Scherer --- I did push the installation and I would like to defer the gnupg integration for now, as it likely requires a bit more discussion (like, how do we distribute the keys, etc, do we rotate it). And for the pbuilder cache, I would need to know the exact matrix of distribution we want to build and how. That part seems not too hard: https://wiki.debian.org/PbuilderTricks#How_to_build_for_different_distributions And if we aim to build on unstable, we also may need to do some work to keep the chroot updated (same for stable in fact). -- You are receiving this mail because: You are on the CC list for the bug. ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1711950] Account in download.gluster.org to upload the build packages
https://bugzilla.redhat.com/show_bug.cgi?id=1711950 hari gowtham changed: What|Removed |Added Flags|needinfo?(hgowtham@redhat.c | |om) | --- Comment #10 from hari gowtham --- We are trying to finish it within this sprint (each sprint is for 3 weeks). So we will assume that we should be done in a month with the automation. -- You are receiving this mail because: You are on the CC list for the bug. ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1711950] Account in download.gluster.org to upload the build packages
https://bugzilla.redhat.com/show_bug.cgi?id=1711950 Shwetha K Acharya changed: What|Removed |Added CC||hgowt...@redhat.com Flags||needinfo?(hgowtham@redhat.c ||om) --- Comment #9 from Shwetha K Acharya --- Hari, Can you please address the above query? -- You are receiving this mail because: You are on the CC list for the bug. ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1711950] Account in download.gluster.org to upload the build packages
https://bugzilla.redhat.com/show_bug.cgi?id=1711950 --- Comment #8 from M. Scherer --- As said in the comment #2 and comment #4, what is the deadline for the account closure ? If I do not get a answer, then I will just decide on "3 month after the creation" and then deploy. -- You are receiving this mail because: You are on the CC list for the bug. ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1711950] Account in download.gluster.org to upload the build packages
https://bugzilla.redhat.com/show_bug.cgi?id=1711950 --- Comment #7 from Shwetha K Acharya --- @misc (In reply to M. Scherer from comment #4) > Sure give me a deadline, and I will create the account. I mean, I do not > even need a precise one. > > Would you agree on "We do in 3 months", in which case I create the account > right now (with expiration as set). > > (I need a public ssh key and a username) We have already taken up the task of automating building and packaging. Details can be found at https://bugzilla.redhat.com/show_bug.cgi?id=1727727. Please create the account. Below are the required details: Public ssh key: ssh-rsa B3NzaC1yc2EDAQABAAABAQCifwFXjkLXFwnlTBMXFgTEHAA1Vavzti41B4Yp1RJYtCuJ91s+P5YHc2j4a/wpVquPJboNuv9wtqknmd5SJYBXB11dinNfHfvE+gCN9Osdn64/om9i3pIpQQeY6uvF4MF9yfyx8huEWFZeaOiljvmTZ3//4kzsJHK2yKCmJFhy5Zcg9+WMM2bjfACjlFDIuOG2kqaRM8tGggOQG9iQ/VElWOTxJkHUJaP50PWdwEHHoiCKmipe5xEcSR/6qubaF6VpMfBLmrjmJMqkjVozryVweHBLn3oQfOkJmlErwJox7hLFuk5V4fvVine5xrWKygw/kA2Mpr7Q1zXg5moZHbCP root@localhost.localdomain User name: sacharya -- You are receiving this mail because: You are on the CC list for the bug. ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1727727] Build+Packaging Automation
https://bugzilla.redhat.com/show_bug.cgi?id=1727727 --- Comment #14 from M. Scherer --- Pbuilder do setup chroots, afaik, so that's kinda like mock, if you are maybe more familliar with the Fedora/Centos tooling. Now, maybe there is limitation and they do not work exactly the same, but I would have expected a clean chroot created each time, to build the package. I didn't do debian package since a long time. -- You are receiving this mail because: You are on the CC list for the bug. ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1727727] Build+Packaging Automation
https://bugzilla.redhat.com/show_bug.cgi?id=1727727 hari gowtham changed: What|Removed |Added CC||kkeit...@redhat.com Flags||needinfo?(kkeithle@redhat.c ||om) --- Comment #13 from hari gowtham --- (In reply to M. Scherer from comment #12) > Ok, so I will install the packages on the builder we have, and then have it > added to jenkins. > (and while on it, also have 2nd one, just in case) Forgot to mention that this script file is also necessary: https://github.com/Sheetalpamecha/packaging-scripts/blob/master/generic_package.sh Will send a patch to have it in the repo. > > As for running different job running on specific machine, that's indeed > pretty annoying on jenkins. I do not have enough experience with jjb, but > JobTemplate is likely something that would help for that: > https://docs.openstack.org/infra/jenkins-job-builder/definition.html#id2 Will look into it. I'm new to writing jobs for jenkins. > > But afaik, gluster is not dependent on the kernel, so building that with > pbuilder in a chroot should be sufficient no matter what Debian, as long as > it is a up to date one, no ? Yes, gluster is not dependent on kernel, but I'm unaware of using chroot for different debian version . For this Kaleb would be the better person to answer. @kaleb can you please answer this? -- You are receiving this mail because: You are on the CC list for the bug. ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1727727] Build+Packaging Automation
https://bugzilla.redhat.com/show_bug.cgi?id=1727727 --- Comment #12 from M. Scherer --- Ok, so I will install the packages on the builder we have, and then have it added to jenkins. (and while on it, also have 2nd one, just in case) As for running different job running on specific machine, that's indeed pretty annoying on jenkins. I do not have enough experience with jjb, but JobTemplate is likely something that would help for that: https://docs.openstack.org/infra/jenkins-job-builder/definition.html#id2 But afaik, gluster is not dependent on the kernel, so building that with pbuilder in a chroot should be sufficient no matter what Debian, as long as it is a up to date one, no ? -- You are receiving this mail because: You are on the CC list for the bug. ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1727727] Build+Packaging Automation
https://bugzilla.redhat.com/show_bug.cgi?id=1727727 --- Comment #11 from hari gowtham --- By setup i meant doing the following prerequisites: these two steps are the ones necessary as of now: - `deb.packages.dot-gnupg.tgz`: has the ~/.gnupg dir with the keyring needed to build & sign packages - packages required: build-essential pbuilder devscripts reprepro debhelper dpkg-sig And for the first time we need to do this: # First time create the /var/cache/pbuilder/base.tgz # on debian: sudo pbuilder create --distribution wheezy --mirror ftp://ftp.us.debian.org/debian/ --debootstrapopts "--keyring=/usr/share/keyrings/debian-archive-keyring.gpg" # on raspbian: sudo pbuilder create --distribution wheezy --mirror http://archive.raspbian.org/raspbian/ --debootstrapopts "--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" NOTE: In future if any change is made here ( https://github.com/semiosis/glusterfs-debian/tree/wheezy-glusterfs-3.5/debian) then we might have to change it. The reason to go for the above two level implementation was, I wasn't aware of how to make the job run on a particular machine based on the arguments it gets. Like stretch has to be run on rhs-vm-16.storage-dev.lab.eng.bOS.redhat.com(which will be one of the jenkins debian slaves) And we have to run the script on multiple machines based on the number of distributions we want to build. -- You are receiving this mail because: You are on the CC list for the bug. ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
