There is a reaper that releases nodes after a certain duration. I believe
it's set to 6 hours right now.
This is a safeguard for nodes that may not have been released properly in a
job and are "leaking".
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Dec 5, 2016 7:08 AM, "Julien Pivotto" <roidelapluie(a)inuits.eu> wrote:
On 05 Dec 11:49, Karanbir Singh wrote:
> On 30/11/16 04:55, Julien Pivotto wrote:
> > Well, I do think that the code is relevant for every user. I would have
> > liked to understand a bit better how we provision upfront, how we do the
> > garbage collection, at which point are the nodes killed... With more
> > details than what is available in the wiki.
>
> the user handoff happens at the point where the duffy call is made, and
> then again the collection happens when the done call is made, or there
> is a timeout on the allocation.
>
> What specific details are you looking for beyond this ? and how would it
> impact your test workers and your use of these nodes ?
>
I was mainly wondering what happens if I do not release a node. The wiki
page is not clear if a garbage collector is actually implemented. I
wanted to know if it would have been useful that I create a jenkinsjob
running daily that would kill my unreleased nodes.
> Regards
>
> --
> Karanbir Singh
> +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
> GnuPG Key : http://www.karan.org/publickey.asc
> _______________________________________________
> CentOS-devel mailing list
> CentOS-devel(a)centos.org
> https://lists.centos.org/mailman/listinfo/centos-devel
--
(o- Julien Pivotto
//\ Config Management SIG
V_/_ https://frama.link/cfgmgmt
_______________________________________________
CentOS-devel mailing list
CentOS-devel(a)centos.org
https://lists.centos.org/mailman/listinfo/centos-devel
Hi all,
As per our policies: https://wiki.centos.org/SpecialInterestGroup
> All code produced within the SIG must be compatible with a FOSS license
> presently used by CentOS; if a new license is wanted, again, please
> consult with the Devteam member
I think that it would be valuable that the SIG in charge of the infra
releases the source code of Duffy. It works really well and might be
used by other people.
I did not find the source code anywhere, sorry if I missed it.
Thanks,
--
(o- Julien Pivotto
//\ Open-Source Consultant
V_/_ Inuits - https://www.inuits.eu
Hi all,
I would like to enquire if there will be a plan for CentOS 7.3 version
specified on Power PPC64le platform. If there is, when will it be
released?
Regards
Vivian
On Tue, 2016-11-29 at 12:00 +0000, centos-devel-request(a)centos.org
wrote:
> Send CentOS-devel mailing list submissions to
> centos-devel(a)centos.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.centos.org/mailman/listinfo/centos-devel
> or, via email, send a message with subject or body 'help' to
> centos-devel-request(a)centos.org
>
> You can reach the person managing the list at
> centos-devel-owner(a)centos.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of CentOS-devel digest..."
>
>
> Today's Topics:
>
> 1. Proposed additions to CentOS 7.3 release notes (Phil Wyett)
> 2. Update on status of CentOS Community Container Pipeline
> (Bamacharan Kundu)
> 3. Duffy Source Code (Julien Pivotto)
> 4. Re: Duffy Source Code (Ratnadeep Debnath)
>
>
> ---------------------------------------------------------------------
> -
>
> Message: 1
> Date: Mon, 28 Nov 2016 16:29:47 +0000
> From: Phil Wyett <philwyett.hemisphere(a)gmail.com>
> To: centos-devel(a)centos.org
> Subject: [CentOS-devel] Proposed additions to CentOS 7.3 release
> notes
> Message-ID: <1480350587.3550.6.camel(a)gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi all,
>
> I would like to propose a few additions for possible inclusion into
> the
> CentOS 7.3 release notes.
>
>
> * Bug 1370134 - Several ipa-* packages conflict with themself
> https://bugzilla.redhat.com/show_bug.cgi?id=1370134
>
> * Bug 1373082 - SELinux is preventing /usr/libexec/colord from read
> access on the file /etc/udev/hwdb.bin
> https://bugzilla.redhat.com/show_bug.cgi?id=1373082
>
> Above link is locked to some. My report that dup'ed is not.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1398030
>
> * Bug 1396775 - Cover art placeholder visible when viewing disabled
> https://bugzilla.redhat.com/show_bug.cgi?id=1396775
>
> Regards
>
> Phil
>
> --
>
> Google+: https://goo.gl/CPjvNo
> Blog: https://philwyett-hemi.blogspot.co.uk/
> GitLab: https://gitlab.com/philwyett_hemi/
>
>
>
We started using CentOS7.2 ppc64le a few months ago, and would like to see
7.3 soon as said some new stuffs like NVLINK are there..Thanks to share the
plan if any.
2016-11-29 20:00 GMT+08:00 <centos-devel-request(a)centos.org>:
> Send CentOS-devel mailing list submissions to
> centos-devel(a)centos.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.centos.org/mailman/listinfo/centos-devel
> or, via email, send a message with subject or body 'help' to
> centos-devel-request(a)centos.org
>
> You can reach the person managing the list at
> centos-devel-owner(a)centos.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of CentOS-devel digest..."
>
>
> Today's Topics:
>
> 1. Proposed additions to CentOS 7.3 release notes (Phil Wyett)
> 2. Update on status of CentOS Community Container Pipeline
> (Bamacharan Kundu)
> 3. Duffy Source Code (Julien Pivotto)
> 4. Re: Duffy Source Code (Ratnadeep Debnath)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 28 Nov 2016 16:29:47 +0000
> From: Phil Wyett <philwyett.hemisphere(a)gmail.com>
> To: centos-devel(a)centos.org
> Subject: [CentOS-devel] Proposed additions to CentOS 7.3 release notes
> Message-ID: <1480350587.3550.6.camel(a)gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi all,
>
> I would like to propose a few additions for possible inclusion into the
> CentOS 7.3 release notes.
>
>
> * Bug 1370134 - Several ipa-* packages conflict with themself
> https://bugzilla.redhat.com/show_bug.cgi?id=1370134
>
> * Bug 1373082 - SELinux is preventing /usr/libexec/colord from read
> access on the file /etc/udev/hwdb.bin
> https://bugzilla.redhat.com/show_bug.cgi?id=1373082
>
> Above link is locked to some. My report that dup'ed is not.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1398030
>
> * Bug 1396775 - Cover art placeholder visible when viewing disabled
> https://bugzilla.redhat.com/show_bug.cgi?id=1396775
>
> Regards
>
> Phil
>
> --
>
> Google+: https://goo.gl/CPjvNo
> Blog: https://philwyett-hemi.blogspot.co.uk/
> GitLab: https://gitlab.com/philwyett_hemi/
>
>
>
Hello,
It's time for our weekly PaaS SIG sync-up meeting
Time: 1700 UTC - Wedensdays
Date: Today Wedensday, 30 November 2016
Where: IRC- Freenode - #centos-devel
Agenda:
- OpenShift Current Status
-- rpms
-- Documentation
-- Automated testing
-- images / image building
- Multi-arch
- Open Floor
Minutes from last meeting:
https://www.centos.org/minutes/2016/november/centos-devel.2016-11-23-16.59.…
Hi,
Here is update for the work done recently in CentOS Community
Container Pipeline.
* Containerized Workers for resolving conflicts in writing the
configs by multiple workers.
* Triggering docker linter before each build with linter worker to
notify user about problems in target file to be built and have a feed back.
* Jenkins jobs triggering dependency images on built of dependent images.
* Builds were getting failed without proper logs, we solved that with
necessary openshift build configuration.
In the coming days, we will be focusing on:
* Set weekly scans for the images present in registry.centos.org.
* Scaling out OpenShift nodes for speeding up container build rate.
* Fixing All in one and multi node setup for proper installation and
running.
Regards
Bamacharan Kundu
Dear All,
Since this morning, 08:30 UTC, all koji buildroot for CentOS 7 have the
CR repository enabled.
Few notes :
- For multi-arch SIGs, until arch specific CR is populated your
buildroot will be different on a per arch basis but will NOT fail. We
are looking into a better way to handle this.
- The plan is to leave this repository enabled by default for the
lifetime of a SIG target as it will be empty until we need it again.
- Please report any issue you may find on http://bugs.centos.org.
thanks,
--
Thomas Oulevey
There was a discussion earlier today in #centos-devel about a way to
build live iso images on cbs.centos.org.
Koji seems to permit to do that through "koji spin-livecd"
Documentation is available here : https://docs.pagure.org/koji/image_build/
One thing to keep in mind though is that one needs to have livecd-tools
pkg installed, and corresponding to the os distro/version the livecd
will be based on : you need a centos 7 host to build a centos 7 liveCD
and that can't work to build a centos 6 liveCD (see as an example
https://bugzilla.redhat.com/show_bug.cgi?id=1035276)
Depending on the target audience, and if we only want to build centos 7
live media, I can add an additional koji builder, running centos 7 and
livecd-tools (from extras, and the one we use to build also the centos
live media found on mirror.centos.org)
My only concern (but has to be tested) is this : (from the koji doc
linked above) :
"The image building tasks will fail if your image tries to include a
package that was not built in your build system. This is because the
package does not have any origin information stored in Koji’s database."
That can be a problem as *no* pkg from the CentOS 7 distro was built on
cbs.centos.org
Opinions, ideas, workaround ?
--
Fabian Arrotin
The CentOS Project | http://www.centos.org
gpg key: 56BEC54E | twitter: @arrfab