Hi all,
It occurs to me that the bash update isn't going to be available for the Atomic image(s) since the users can't install new packages.
What do we need to do to get new images spun up and get a new tree for people to grab with rpm-ostree update?
My understanding is this is manual now, how much lifting do we have yet to do to make this automatic?
Thanks,
jzb
On Thu, Sep 25, 2014, at 12:25 PM, Joe Brockmeier wrote:
Hi all,
It occurs to me that the bash update isn't going to be available for the Atomic image(s) since the users can't install new packages.
Right - and this is different from the Docker image base, where users can use yum "manually".
What do we need to do to get new images spun up and get a new tree for people to grab with rpm-ostree update?
There are a few streams of images; there is a rawhide compose that comes from a custom box outside of Fedora official rel-eng, and then there's the F21 composes which are done manually by rel-eng.
My understanding is this is manual now, how much lifting do we have yet to do to make this automatic?
The rawhide trees/images was automated, then stopped being automated when we started working on a new script, now I'll be looking at automating it again.
I'm doing a new compose now, and it does have bash-4.3.24-2.fc22. (Which, AIUI, may not actually fix everything per https://lists.fedoraproject.org/pipermail/test/2014-September/122976.html ...but we'll keep the trees flowing)
This content will land in: http://dl.fedoraproject.org/pub/alt/fedora-atomic/repo/ under the "fedora-atomic/rawhide/x86_64/docker-host" ref.
I'm doing a new compose now, and it does have bash-4.3.24-2.fc22. (Which, AIUI, may not actually fix everything per https://lists.fedoraproject.org/pipermail/test/2014-September/122976.html ...but we'll keep the trees flowing)
Hey -- any chance you can send me the Koji IDs for the createImage tasks when they're done? Then I can register new AMIs.
On Thu, Sep 25, 2014, at 06:43 PM, David Gay wrote:
I'm doing a new compose now, and it does have bash-4.3.24-2.fc22. (Which, AIUI, may not actually fix everything per https://lists.fedoraproject.org/pipermail/test/2014-September/122976.html ...but we'll keep the trees flowing)
Hey -- any chance you can send me the Koji IDs for the createImage tasks when they're done? Then I can register new AMIs.
There's two steps. First the tree is composed, that's:
https://git.fedorahosted.org/cgit/releng/tree/scripts/run-pungi#n40
Then imaagefactory runs using that as input:
https://git.fedorahosted.org/cgit/releng/tree/scripts/build-cloud-images#n37
At the moment, my understanding is the scripts are only run manually for Alpha/Beta/RC type situations. AIUI someone in infrastructure would have to kick off the compose tree, and then anyone with createImage privileges could use it as input?
On Thu, Sep 25, 2014, at 04:36 PM, Colin Walters wrote:
This content will land in: http://dl.fedoraproject.org/pub/alt/fedora-atomic/repo/ under the "fedora-atomic/rawhide/x86_64/docker-host" ref.
This is done now, and I'm starting a f21 compose now too.