Deployment of plume in Fedora Infrastructure
by Sayan Chowdhury
Hi all,
Over the last few months, I was working on integrating Fedora as a
sub-system to plume. This is to migrate from fedimg to plume, and
finally deprecating plume.
The work on plume has been completed and over the next few days, I
prepare for the deployment of plume. I've prepared a spec document for
the same[1]. I plan to move this to Fedora wiki in some time but if
someone wants to do a review can have a look at it and post comments.
[1] https://hackmd.io/fpDWrtuJT7-jt8jy2yJC1Q?view
--
Sayan Chowdhury <https://words.yudocaa.in/>
GPG Fingerprint : 0F16 E841 E517 225C 7D13 AB3C B023 9931 9CD0 5C8B
5 years, 2 months
[releng] Issue #8270: Container Base Image Release process improvement
by Clement Verna
cverna reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
We currently have 2 differents process to release the Fedora Container Base image.
1 - To release the images on Docker Hub (@cverna responsible)
2 - To release the images on registry.fp.o and quay.io (@releng responsible)
I would like to merge the 2 processes into one to make it easier and stop needing to ping 2 people to release the images. Docker Hub has it's own way of doing things but both processes share a good common base.
The merged process would be as follow :
1 - Get the latest container compose for a specified tag (ie f29)
2 - Download the artifacts from the koji tasks
3 - For registry.fp.o and quay.io.
3.1 push each arch images to the registry (ie fedora:29-aarch64)
3.2 generate manifest list with all the arches
3.3 push the manifest list to the correct tags (ie fedora:latest, fedora:29)
4 - For Docker Hub
4.1 create a temporary workspace for each arch (ie workspace-29/aarch64)
4.2 extract the layer.tar from the archive into the workspace
4.3 Update the Dockerfile template with the name of the layer.tar
4.4 Clone https://github.com/fedora-cloud/docker-brew-fedora
4.5 Add and commit new files (Dockerfile and layer.tar) to the correct branch (ie 29)
4.6 Push to github
4.7 Update https://github.com/fedora-cloud/official-images/blob/master/library/fedora
4.8 Create a Pull Request
I have most (4.7 and 4.8 are not yet automated) of the Docker Hub process automated in a Python Script (https://pagure.io/docker-image-release/blob/master/f/tasks.py). And the releng process is scripted (https://pagure.io/releng/blob/master/f/scripts/sync-latest-container-base...).
I would like to merge these 2 scripts and see if we can make the container release process more available to people that are interested to help (For example Container SIG members). One possibility is to have this run in the infra OpenShift instance for example.
I am requesting feedback from the @releng group on these ideas ?
* When do you need this? (YYYY/MM/DD)
* When is this no longer needed or useful? (YYYY/MM/DD)
* If we cannot complete your request, what is the impact?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8270
5 years, 2 months
Fedora Release Engineering Meeting Summary for 2018-04-17
by Mohan Boddu
======================================
#fedora-meeting-2: RELENG (2019-04-18)
======================================
Meeting started by mboddu at 16:01:29 UTC. The full logs are available
athttps://meetbot.fedoraproject.org/fedora-meeting-2/2019-04-17/releng.20...
.
Meeting summary
---------------
* init process (mboddu, 16:01:29)
* #8265 RFC: Separate target for Rust packages (mboddu, 16:06:34)
* LINK: https://pagure.io/releng/issue/8265 (mboddu, 16:06:40)
* ignatenkobrain and/or mizdebsk will comment on the changes they need
in koji and we will proceed further based on the changes. (mboddu,
16:41:28)
* Open Floor (mboddu, 16:44:18)
* LINK: https://pagure.io/releng/issue/8293 (mboddu, 16:44:40)
* Since everything seems to be fine now, we will make the change after
the F30 Final freeze. (mboddu, 17:02:07)
Meeting ended at 17:03:00 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* mboddu (51)
* nirik (31)
* ignatenkobrain (15)
* mizdebsk (11)
* zodbot (8)
* bcotton (4)
* tyll (0)
* puiterwijk (0)
* masta (0)
* jednorozec (0)
* pbrobinson (0)
* dustymabe (0)
* pingou (0)
* ksinny (0)
* maxamillion (0)
* sharkcz (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
5 years, 2 months
[releng] Issue #8288: unretirement request for keybinder and claim for
ownership
by Mamoru TASAKA
mtasaka reported a new issue against the project: `releng` that you are following:
``
* Name of the package?
keybinder
* FAS username of the new maintainer?
mtasaka
* Branches that you need it to be unretired for?
master
* Package re-review BZ URL?
Not necessary, packages have been retired for only a week.
* Any extra information?
Well, I completely overlooked this. This is needed for lxpanel, core component of LXDE spin.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8288
5 years, 2 months