Hey, so upstream Fedora has been working on this: https://pagure.io/pungi
And I'd like to discuss trying to use it for Atomic Host work. The concept of a "compose" that ties together the ISO and cloud images is nice for example. It's going to need to gain some more sophistication around OSTree, and there'd likely be some details that need changing such as how signing happens.
But having a common codebase here would be nice, and I think we could also stop doing this in Jenkins for https://wiki.centos.org/SpecialInterestGroup/Atomic/Devel too. (We'd retain the auto-generated RPMs at least though)
On Thu, Oct 27, 2016 at 8:06 AM, Colin Walters walters@verbum.org wrote:
Hey, so upstream Fedora has been working on this: https://pagure.io/pungi
And I'd like to discuss trying to use it for Atomic Host work. The concept of a "compose" that ties together the ISO and cloud images is nice for example. It's going to need to gain some more sophistication around OSTree, and there'd likely be some details that need changing such as how signing happens.
Is this what they're using for their atomic host? I'm in favor of using the same tools across atomic host projects.
But having a common codebase here would be nice, and I think we could also stop doing this in Jenkins for https://wiki.centos.org/SpecialInterestGroup/Atomic/Devel too. (We'd retain the auto-generated RPMs at least though) _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Thu, Oct 27, 2016, at 11:39 AM, Jason Brooks wrote:
Is this what they're using for their atomic host? I'm in favor of using the same tools across atomic host projects.
Yeah.
So let me flesh this out a little bit more; I think it would be possible (and make sense as an incremental transition) to use pungi *just* for images/ostree, while consuming RPMs built via whatever the CentOS process is that's not Koji.
Similarly, for https://wiki.centos.org/SpecialInterestGroup/Atomic/Devel we use https://github.com/cgwalters/rpmdistro-gitoverlay but if our Jenkins jobs had access to the CBS Koji instance, we could use it for image generation and composes.
Note that I'm scoping in here potentially making this change not just for AH but also for CentOS Core, but that's obviously optional.