[atomic-wg] Issue #312: Enabling CI/CD: Experiment with building Atomic Host
out of a module
by Petr Šabata
psabata added a new comment to an issue you are following:
``
A couple of things here.
* the "fork" option implies a lot of overhead indeed, however, most of it can be automated with simple scripts here and there -- automatic depsolving on dist-git changes, automatic rebuilds, that's all possible;
* building on top of H&P is not only about having the build dependencies available, it also relies on currently undefined behavior where your module updates packages owned by another module (Atomic Host updating/overriding Host & Platform content in this case); we intend to make this impossible in the long term so I'm not sure how this would work
* if Atomic Host is just a Platform profile, you cannot actually change anything in the sources -- no custom patches, minimized builds or alternative implementations; not even different versions of anything; furthermore, what is actually installed in the composed OSTree is defined in the JSON file, not the module (although I would be awesome if we could generate it from a profile later on)
Regarding `atomic-build-deps`, such a module would be more or less identical to `bootstrap` and I would discourage you from pursuing that path.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/312
6 years, 8 months
[atomic-wg] Issue #312: Enabling CI/CD: Experiment with building Atomic Host
out of a module
by Colin Walters
walters added a new comment to an issue you are following:
``
But `atomic-build-deps` would include huge amounts of stuff...just think about all of the individual golang BR packages. Just *today* that's already vast amounts of painful busywork that is ad-hoc automated via https://github.com/gofed/gofed - modularity means having *another* list of all of those packages. (This again is a general problem with modularity layering on top of all the stuff that exists now rather than fixing any of it)
Now at least for docker it looks like we gave up on trying to use split-out golang BRs. And hmm, skopeo also just uses `with_bundled` now too.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/312
6 years, 8 months
[atomic-wg] Issue #312: Enabling CI/CD: Experiment with building Atomic Host
out of a module
by Matthew Miller
mattdm added a new comment to an issue you are following:
``
> The "build on top" thing brings in a requirement to modularize all of the build dependencies. I know there's a prototype "autotools" module for example, but taking this out requires modules for a vast array of stuff, from golang out to corner cases like gtk-doc (currently requires perl), etc.
FWIW, I'm completely okay with a "atomic-build-deps" module; this can start as an ugly grab-bag of anything required, and can over time instead reference more specific other modules (and possibly eventually _only_ reference other modules).
I feel like we _should_ be able to do "build on top", possibly with "Atomic Host" as a host&platform Profile.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/312
6 years, 8 months
[atomic-wg] Issue #312: Enabling CI/CD: Experiment with building Atomic Host
out of a module
by Colin Walters
walters added a new comment to an issue you are following:
``
So...I am still uncertain about the distinct paths of:
1) Build fork of host&platform
2) Build on top of host&platform
The "fork" option carries with it a lot of maintenance overhead imposed by the modularity build system - we'll have distinct binaries as well, and that's going to invalidate some of the testing.
The "build on top" thing brings in a requirement to modularize all of the build dependencies. I know there's a prototype "autotools" module for example, but taking this out requires modules for a vast array of stuff, from `golang` out to corner cases like `gtk-doc` (currently requires perl), etc.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/312
6 years, 8 months
Fedora Atomic WG Meeting Minutes 2017-09-06
by Jason Brooks
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-09-06/fedora_atom...
Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-09-06/fedora_atom...
#fedora-meeting-1: fedora_atomic_wg
Meeting started by jbrooks at 17:00:10 UTC (full logs).
Meeting summary
roll call (jbrooks, 17:00:26)
action items from last meeting (jbrooks, 17:04:46)
ACTION: jbrooks to submit asciibinder pkg for review (jbrooks, 17:05:58)
open floor (jbrooks, 17:07:09)
atomic-host-docs
https://github.com/projectatomic/atomic-host-docs/issues (jbrooks,
17:09:08)
ACTION: jberkus to follow up on partial container images from Flock
(jbrooks, 17:14:01)
ACTION: jbrooks to create issue for adding examples to container
guidelines (jbrooks, 17:16:40)
Meeting ended at 17:28:11 UTC (full logs).
Action items
jbrooks to submit asciibinder pkg for review
jberkus to follow up on partial container images from Flock
jbrooks to create issue for adding examples to container guidelines
Action items, by person
jberkus
jberkus to follow up on partial container images from Flock
jbrooks
jbrooks to submit asciibinder pkg for review
jbrooks to create issue for adding examples to container guidelines
People present (lines said)
jberkus (28)
jbrooks (24)
maxamillion (13)
zodbot (11)
ksinny (9)
kushal (5)
davdunc (4)
yzhang (4)
miabbott (2)
Generated by MeetBot 0.1.4.
6 years, 8 months
2wk atomic release candidate: 20170905
by Dusty Mabe
Tomorrow we will attempt to release the 20170905 images.
These images contain the following ostree version/commit:
26.120
0b0127864022dd6ffad1a183241fbd5482ef5a1642ff3c8751c2e6cae6070b1a
The atomic host VM images are here:
https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-26-20170...
The ISO image is here:
https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-26-20170...
The AMIs are here:
Fedora-Atomic-26-20170905.0.x86_64 EC2 (ap-northeast-1) ami-3205c154 hvm standard
Fedora-Atomic-26-20170905.0.x86_64 EC2 (ap-southeast-1) ami-09ed826a hvm standard
Fedora-Atomic-26-20170905.0.x86_64 EC2 (ap-southeast-2) ami-105bbe72 hvm standard
Fedora-Atomic-26-20170905.0.x86_64 EC2 (eu-central-1) ami-c6d266a9 hvm standard
Fedora-Atomic-26-20170905.0.x86_64 EC2 (eu-west-1) ami-4254903b hvm standard
Fedora-Atomic-26-20170905.0.x86_64 EC2 (sa-east-1) ami-b1cab9dd hvm standard
Fedora-Atomic-26-20170905.0.x86_64 EC2 (us-east-1) ami-dd9b8aa6 hvm standard
Fedora-Atomic-26-20170905.0.x86_64 EC2 (us-west-1) ami-4b71462b hvm standard
Fedora-Atomic-26-20170905.0.x86_64 EC2 (us-west-2) ami-b11febc9 hvm standard
Fedora-Atomic-26-20170905.0.x86_64 EC2 (ap-northeast-1) ami-3705c151 hvm gp2
Fedora-Atomic-26-20170905.0.x86_64 EC2 (ap-southeast-1) ami-f9ec839a hvm gp2
Fedora-Atomic-26-20170905.0.x86_64 EC2 (ap-southeast-2) ami-0d5bbe6f hvm gp2
Fedora-Atomic-26-20170905.0.x86_64 EC2 (eu-central-1) ami-81d266ee hvm gp2
Fedora-Atomic-26-20170905.0.x86_64 EC2 (eu-west-1) ami-6e549017 hvm gp2
Fedora-Atomic-26-20170905.0.x86_64 EC2 (sa-east-1) ami-1fcbb873 hvm gp2
Fedora-Atomic-26-20170905.0.x86_64 EC2 (us-east-1) ami-1c988967 hvm gp2
Fedora-Atomic-26-20170905.0.x86_64 EC2 (us-west-1) ami-ff7f489f hvm gp2
Fedora-Atomic-26-20170905.0.x86_64 EC2 (us-west-2) ami-f519ed8d hvm gp2
The diff between this and the previous released version is:
ostree diff commit old: 13ed0f241c9945fd5253689ccd081b5478e5841a71909020e719437bbeb74424
ostree diff commit new: 0b0127864022dd6ffad1a183241fbd5482ef5a1642ff3c8751c2e6cae6070b1a
Upgraded:
bind99-libs 9.9.10-1.P2.fc26.x86_64 -> 9.9.10-2.P3.fc26.x86_64
bind99-license 9.9.10-1.P2.fc26.noarch -> 9.9.10-2.P3.fc26.noarch
ca-certificates 2017.2.14-1.0.fc26.noarch -> 2017.2.16-1.0.fc26.noarch
compat-openssl10 1:1.0.2j-6.fc26.x86_64 -> 1:1.0.2j-9.fc26.x86_64
coreutils 8.27-5.fc26.x86_64 -> 8.27-6.fc26.x86_64
coreutils-common 8.27-5.fc26.x86_64 -> 8.27-6.fc26.x86_64
docker 2:1.13.1-21.git27e468e.fc26.x86_64 -> 2:1.13.1-22.gitb5e3294.fc26.x86_64
docker-common 2:1.13.1-21.git27e468e.fc26.x86_64 -> 2:1.13.1-22.gitb5e3294.fc26.x86_64
docker-rhel-push-plugin 2:1.13.1-21.git27e468e.fc26.x86_64 -> 2:1.13.1-22.gitb5e3294.fc26.x86_64
expat 2.2.3-1.fc26.x86_64 -> 2.2.4-1.fc26.x86_64
file 5.30-9.fc26.x86_64 -> 5.30-10.fc26.x86_64
file-libs 5.30-9.fc26.x86_64 -> 5.30-10.fc26.x86_64
glibc 2.25-8.fc26.x86_64 -> 2.25-10.fc26.x86_64
glibc-all-langpacks 2.25-8.fc26.x86_64 -> 2.25-10.fc26.x86_64
glibc-common 2.25-8.fc26.x86_64 -> 2.25-10.fc26.x86_64
kernel 4.12.5-300.fc26.x86_64 -> 4.12.9-300.fc26.x86_64
kernel-core 4.12.5-300.fc26.x86_64 -> 4.12.9-300.fc26.x86_64
kernel-modules 4.12.5-300.fc26.x86_64 -> 4.12.9-300.fc26.x86_64
krb5-libs 1.15.1-22.fc26.x86_64 -> 1.15.1-25.fc26.x86_64
libcrypt-nss 2.25-8.fc26.x86_64 -> 2.25-10.fc26.x86_64
libidn2 2.0.3-1.fc26.x86_64 -> 2.0.4-1.fc26.x86_64
libpsl 0.17.0-2.fc26.x86_64 -> 0.18.0-1.fc26.x86_64
librepo 1.7.20-3.fc26.x86_64 -> 1.8.0-1.fc26.x86_64
lz4-libs 1.7.5-4.fc26.x86_64 -> 1.8.0-1.fc26.x86_64
nspr 4.15.0-1.fc26.x86_64 -> 4.16.0-1.fc26.x86_64
nss 3.31.0-1.1.fc26.x86_64 -> 3.32.0-1.1.fc26.x86_64
nss-softokn 3.31.0-1.0.fc26.x86_64 -> 3.32.0-1.2.fc26.x86_64
nss-softokn-freebl 3.31.0-1.0.fc26.x86_64 -> 3.32.0-1.2.fc26.x86_64
nss-sysinit 3.31.0-1.1.fc26.x86_64 -> 3.32.0-1.1.fc26.x86_64
nss-tools 3.31.0-1.1.fc26.x86_64 -> 3.32.0-1.1.fc26.x86_64
nss-util 3.31.0-1.0.fc26.x86_64 -> 3.32.0-1.0.fc26.x86_64
oci-systemd-hook 1:0.1.11-1.git1ac958a.fc26.x86_64 -> 1:0.1.13-1.gitafe4b4a.fc26.x86_64
oci-umount 2:1.13.1-21.git27e468e.fc26.x86_64 -> 2:2.0.0-2.gitf90b64c.fc26.x86_64
ostree 2017.9-2.fc26.x86_64 -> 2017.10-2.fc26.x86_64
ostree-grub2 2017.9-2.fc26.x86_64 -> 2017.10-2.fc26.x86_64
ostree-libs 2017.9-2.fc26.x86_64 -> 2017.10-2.fc26.x86_64
p11-kit 0.23.5-3.fc26.x86_64 -> 0.23.8-1.fc26.x86_64
p11-kit-trust 0.23.5-3.fc26.x86_64 -> 0.23.8-1.fc26.x86_64
publicsuffix-list-dafsa 20170424-1.fc26.noarch -> 20170809-1.fc26.noarch
python3-rpm 4.13.0.1-5.fc26.x86_64 -> 4.13.0.1-7.fc26.x86_64
rpm 4.13.0.1-5.fc26.x86_64 -> 4.13.0.1-7.fc26.x86_64
rpm-build-libs 4.13.0.1-5.fc26.x86_64 -> 4.13.0.1-7.fc26.x86_64
rpm-libs 4.13.0.1-5.fc26.x86_64 -> 4.13.0.1-7.fc26.x86_64
rpm-ostree 2017.7-1.fc26.x86_64 -> 2017.8-2.fc26.x86_64
rpm-plugin-selinux 4.13.0.1-5.fc26.x86_64 -> 4.13.0.1-7.fc26.x86_64
selinux-policy 3.13.1-260.4.fc26.noarch -> 3.13.1-260.8.fc26.noarch
selinux-policy-targeted 3.13.1-260.4.fc26.noarch -> 3.13.1-260.8.fc26.noarch
skopeo 0.1.23-2.git1bbd87f.fc26.x86_64 -> 0.1.23-6.git1bbd87f.fc26.x86_64
skopeo-containers 0.1.23-2.git1bbd87f.fc26.x86_64 -> 0.1.23-6.git1bbd87f.fc26.x86_64
sqlite-libs 3.20.0-1.fc26.x86_64 -> 3.20.1-1.fc26.x86_64
vim-minimal 2:8.0.946-1.fc26.x86_64 -> 2:8.0.1030-1.fc26.x86_64
Added:
rpm-ostree-libs-2017.8-2.fc26.x86_64
A new rpm-ostree/ostree, new glibc, and new docker are the most notable changes.
Dusty
6 years, 9 months