devel

devel@lists.centos.org

5 participants
4641 discussions

CBS/Infra Meeting 13-Apr-2015 14:00 UTC
by Brian Stinson 13 Apr '15

13 Apr '15

Hi All! It's time for another meeting to discuss the Community Build System. We will be meeting in #centos-devel on Freenode. Here's our Agenda: #info Topic: Quick Updates #info Topic: Koji Project Tags and Git Branches #info Topic: Open Floor See you there! Brian -- Brian Stinson brian(a)bstinson.com | IRC: bstinson | Bitbucket/Twitter: bstinsonmhk

1 0

Hosting CentOS bugs on RH bugzilla
by Lokesh Mandvekar 12 Apr '15

12 Apr '15

Given that we now have a lot of co-operation amongst CentOS-RHEL-Fedora, I was hoping we could host CentOS bugs on RH's bugzilla instance itself under a CentOS product, just like how we have Fedora and RHEL products. My guess is this should make life easier for people who file/deal with bugs related to all 3 distros. Considering docker as an example, when people complain about docker bugs they notice on CentOS7, I'm not sure whether to ask them to file bugs on bugs.c.o or bugzilla.rh.c, as that bug is actually something from RHEL. My guess is their first choice is to file bugs on bugs.c.o. There's also the virt SIG 'docker' and 'docker-master' variants and these are not pulled from RHEL. For bugs related to these, I'll need to ask users to file bugs on bugs.c.o and if this affects fedora/rhel as well, there would be separate bugs on RH's bugzilla about this. I feel it'd be much more convenient for me (and possibly others) to keep track of bugs and reference them if they're all hosted in a single place. Comments? * This issue has been apparently raised in the past as per conversations with Evolution on #centos-devel but it's kinda hard to find out recorded history about it. If anyone could send logs about why this was rejected or whatever, it'd be great. -- Lokesh Freenode, OFTC: lsm5 GPG: 0xC7C3A0DD

5 8

No Storage SIG meeting today
by Lalatendu Mohanty 10 Apr '15

10 Apr '15

Looks like we have not made much progress on the action items. Hence moving the meeting to next week. Thanks, Lala #lalatenduM on Freenode

1 0

including 3rd party repo release RPMs in Extras
by Carl George 10 Apr '15

10 Apr '15

Howdy, My name is Carl, and I'm a developer for the IUS Community repository. CentOS users have easy access to the EPEL repo because the epel-release RPM is in the CentOS Extras repository. Obviously CentOS and EPEL have a special relationship, since they are both sponsored by Red Hat. A coworker suggested to me that it would be nice if the ius-release RPM could be included in Extras as well. I brought the idea up in IRC, and Karanbir suggested I draft up a specification that any third party repository can follow to be considered for inclusion. Here is what I have so far. https://gist.github.com/cgtx/b854281462a18007f509 If this looks familiar, it's because I used the IUS SafeRepo Initiative as a starting point. Please share your feedback and ideas. Carl George Rackspace RPM Development

8 17

etcd fails to start in latest CentOS Atomic images
by Lalatendu Mohanty 10 Apr '15

10 Apr '15

I was trying to use/test the latest CentOS Atomic images [1] [2] and got in to this issue i.e. "systemctl start etcd " is failing. =============================== -bash-4.2# systemctl start etcd -bash-4.2# systemctl status etcd etcd.service - Etcd Server Loaded: loaded (/usr/lib/systemd/system/etcd.service; disabled) Active: failed (Result: exit-code) since Fri 2015-04-10 05:26:54 UTC; 6s ago Process: 1724 ExecStart=/usr/bin/etcd (code=exited, status=200/CHDIR) Main PID: 1724 (code=exited, status=200/CHDIR) Apr 10 05:26:54 myhost.localdomain systemd[1]: Started Etcd Server. Apr 10 05:26:54 myhost.localdomain systemd[1724]: Failed at step CHDIR spawning /usr/bin/etcd: No such file or directory Apr 10 05:26:54 myhost.localdomain systemd[1]: etcd.service: main process exited, code=exited, status=200/CHDIR Apr 10 05:26:54 myhost.localdomain systemd[1]: Unit etcd.service entered failed state. ================================ I suspect there is something wrong with systemd unit file of etcd. The service file looks like below as of now. I think "WorkingDirectory=/var/lib/etcd/`$hostname`.etcd" should have only 'hostname' not '$hostname'. -bash-4.2# cat /usr/lib/systemd/system/etcd.service [Unit] Description=Etcd Server After=network.target [Service] Type=simple # etc logs to the journal directly, suppress double logging StandardOutput=null WorkingDirectory=/var/lib/etcd/`$hostname`.etcd User=etcd ExecStart=/usr/bin/etcd [Install] WantedBy=multi-user.target [1] CentOS-7-x86_64-AtomicHost-20150228_01.qcow2 [2] http://wiki.centos.org/SpecialInterestGroup/Atomic/Download Thanks, Lala #lalatenduM on Freenode

1 0

Atomic SIG Meeting Minutes & Meeting Reminder (Thursday 16:00 UTC)
by Joe Brockmeier 07 Apr '15

07 Apr '15

Next meeting is Thursday 9 April at 16:00 UTC. ========================= #centos-devel: Atomic SIG ========================= Meeting started by jzb at 16:03:35 UTC. The full logs are available at http://centos.org/minutes/2015/april/centos-devel.2015-04-02-16.03.log.html . Meeting summary --------------- * LINK: http://centos.org/minutes/2015/march/centos-devel.2015-03-19-16.00.html (jzb, 16:04:15) * signing (jzb, 16:04:23) * ACTION: imcleod take lead on getting signing ready for imminent "stable" release (jzb, 16:06:00) * document release checklist (jzb, 16:06:36) * LINK: http://wiki.centos.org/Atomic/ReleaseManagement (jzb, 16:07:49) * LINK: http://wiki.centos.org/Atomic/ReleaseManagement (jzb, 16:07:56) * LINK: http://wiki.centos.org/SpecialInterestGroup/Atomic has a bunch of stuff under there, maybe this can also live there ? (kbsingh, 16:08:51) * LINK: http://wiki.centos.org/SpecialInterestGroup/Atomic/Download as an example (kbsingh, 16:09:00) * LINK: http://wiki.centos.org/Atomic/WeeklyMeeting (kbsingh, 16:09:23) * ACTION: jzb move Release Management page after meeting (jzb, 16:10:29) * release scheme for image kickstarts and Dockerfiles (jzb, 16:11:01) * ACTION: imcleod Establish ongoing release process for non-RPM artifacts, ideally into g.c.o (jzb, 16:15:47) * get final dates/info on two and four-week update plans. (jzb, 16:17:11) * ACTION: jzb set up meeting to align 4-week cycle. (jzb, 16:20:19) * atomic info in /etc/os-release (jzb, 16:20:44) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1200122 (walters, 16:29:48) * ACTION: lalatenduM set up discussion with kbsingh and langdon about os-release, report back to atomic-devel (jzb, 16:32:39) * open floor (jzb, 16:32:49) Meeting ended at 16:36:47 UTC. Action Items ------------ * imcleod take lead on getting signing ready for imminent "stable" release * jzb move Release Management page after meeting * imcleod Establish ongoing release process for non-RPM artifacts, ideally into g.c.o * jzb set up meeting to align 4-week cycle. * lalatenduM set up discussion with kbsingh and langdon about os-release, report back to atomic-devel -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

1 0

Atomic release checklist
by Jason Brooks 07 Apr '15

07 Apr '15

As discussed in last week's meeting (http://centos.org/minutes/2015/march/centos-devel.2015-03-19-16.00.html) I've put a CentOS Atomic release checklist in the wiki at: http://wiki.centos.org/Atomic/ReleaseManagement Regards, Jason --- Jason Brooks Red Hat Open Source and Standards @jasonbrooks | @redhatopen http://community.redhat.com

4 5

enhancing /etc/*-release
by Karanbir Singh 06 Apr '15

06 Apr '15

hi, We have spent a lot of time working out how best to work the /etc/centos-release file in order to satisfy most use cases. We've had a lot of positive feedback on the three digit release numbering that went into the first CentOS-7 release. And in the coming months, as the rolling builds onramp we will start seeing movement around those. This will also help address some points learned from the community during the 7.0.1406 cycle. We have also decided to split the /etc/redhat-release link to /etc/centos-release and use that as a way to better indicate what codebase the running CentOS Linux instance was derived from. Examples of what these files will look like in say March 2015 ( if .1 is released upstream by then ): ------------------- /etc/centos-release: CentOS Linux release 7.1.1503 (Core) /etc/redhat-release Derived from Red Hat Enterprise Linux 7.1 (Source) ------------------- The /etc/os-release file remains unchaged to indicate CentOS-7 as being the distro being consumed. We will however, be adding ABRT specific content to the os-release file once we have bugs.centos.org setup to accept abrt requests - and we have the required patched rolled out into the distro. These additions will have no impact on numbering reported via tools that consume /etc/os-release. The /etc/centos-release file will then evolve with every monthly release, with the updated file being pushed into updates repo. This implies if someone was to install from the March rolling build, their /etc/centos-release will already have 7.1.1503 and anyone having a previously installed machine, doing a yum update would see the same file drop in. The net result is an impact for new people installing from rolling build media ( and instance media like live images, cloud images, containers etc ). One installed or running, there is no change to how CentOS Linux has been in the past. You just get regular updates, and any machine, regardless of how it was installed and when, updated to the same point in time will have identical content. -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc

14 27

CentOS SCLo SIG sync-up meeting on #centos-devel (2015-04-08)
by Honza Horak 02 Apr '15

02 Apr '15

Unfortunately I'm not available this week on Wed, I'm sorry, so let's arrange the SCLo meeting the next week. Since we have DST in Europe already as well, let's change to 15:00 UTC, that should fit to out schedules the same as it did on non-DST. So, SCLo meeting will be at 15:00 UTC (11:00 EST, 17:00 Brno, 11:00 Boston, 0:00+1d Tokyo, 1:00+1d Brisbane) in #centos-devel on Freenode. = Topics = * sync-up on current status * propose some other topics:) Honza

3 4

Building Centos 7 Cloud images
by Andrei DRAGOMIR 02 Apr '15

02 Apr '15

Hi, I have a question related to the cloud images available here: http://cloud.centos.org/centos/7/images/ 1. How do I build an image ? I looked at the source repos on git.centos.org, the closest one seems to be the sig-cloud-instance/build-instance repository, but I cannot find centos 7 related kickstarts in there. (I am assuming that the images are being built in an automated fashion, using unattended installation) Thank you, Andrei Dragomir -- /A

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel