devel

devel@lists.centos.org

4 participants
4592 discussions

Start a nNew thread

No CentOS SCLo SIG meeting today by hhorak
by Honza Horak 16 Mar '15

16 Mar '15

Guys, I'm very sorry, especially for the late announcement, but I'm not able to hold today's SCLo SIG meeting.. Honza

2 2

docker 1.5 in virt7-testing
by Karanbir Singh 13 Mar '15

13 Mar '15

hi guys, docker 1.5 is now in virt7-testing repos, please test and feedback so we can move to release.. thanks lokesh! - KB -- 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

3 3

Anaconda CentOS 7 error points to Red Hat
by Gianluca Cecchi 12 Mar '15

12 Mar '15

Hello, I'm playing with a CentOS 7 iso (CentOS-7.0-1406-x86_64-DVD.iso) in Oracle VM, configuring the virtual machine as PVHVM. When starting a graphic installation the VM gets a blocking error (a text install completes ok instead). Apart from debugging the probable reason of graphic driver, taht I'll investigate later, I see that the anaconda error debug page contains: Report a bug to Red Hat Customer Portal that should be changed in my opinion. See: https://drive.google.com/file/d/0BwoPbcrMv8mvbTVEN3FYRWJ0dFh4WFVGeWs2ZjE1SF… Donna if already fixed in follwing ISOs. Gianluca

1 0

cbs feature req: building embargoed content
by Karanbir Singh 12 Mar '15

12 Mar '15

hi guys, we need a way to build embargo'd content like reimzul's priv-build, that does not make stuff public till a specific date ( the actual push to public can be manual ); how would we achieve this on cbs ? I guess the git stuff is easier since it can just be a scratch build from srpm and people need not push the git content back to git.centos.org till embargo expiry. - KB -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

7 14

Re: [CentOS-devel] brctl command in Atomic host
by Gianluca Cecchi 11 Mar '15

11 Mar '15

On Wed, Mar 11, 2015 at 12:44 PM, Marcelo Ricardo Leitner < marcelo.leitner(a)gmail.com> wrote: > >> > Hi Gianluca, > > You probably have the 'bridge' command available in there, it's the > iproute2 version of brctl tool. Just like we had ifconfig->ip, we are > having brctl->{bridge,ip}.. > > Note that 'bridge' is for bridge-specific stuff, like: > > $ bridge link help > Usage: bridge link set dev DEV [ cost COST ] [ priority PRIO ] [ state > STATE ] > [ guard {on | off} ] > [ hairpin {on | off} ] > [ fastleave {on | off} ] > [ root_block {on | off} ] > [ hwmode {vepa | veb} ] > bridge link show [dev DEV] > > while you may create the bridge itself via ip command. > > Marcelo > > Ah ok.. indeed I verified I have it inside the Atomic host image. I've been already using the "ip" command but I didn't know about the "bridge" one. Hey, but the developers could have done it better: one more character to type now vs the previous "brctl" one; I will create an alias named "brdg"... ;-) At the end, "less" is better than "more".... Thanks for the notice Gianluca

1 0

Atomic Download page
by Karanbir Singh 11 Mar '15

11 Mar '15

hi, I've put together a rough wiki page with all the Atomic image download resources that I've pushed for this last build. It also includes Ian's Vagrant images. http://wiki.centos.org/SpecialInterestGroup/Atomic/Download Could this become the generic download url to point people at when looking for CentOS Atomic images ? - KB -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

3 3

brctl command in Atomic host
by Gianluca Cecchi 11 Mar '15

11 Mar '15

Hello, I'm testing the latest CentOS Atomic host rolling build (20150228_01). Apparently the brctl command, as normally provided inside bridge-utils rpm package, is not present. I can query /sys/class/net/docker0 and /sys/class/net/veth*/ subtrees, but it would be nice to have it, unless superseded by another docker/atomic command... Thanks in advance, Gianluca PS: I posted here because I'm not subscribed to atomic-devel too atm.. let me know if it's a problem

3 2

SIG repo layout and conflicts between projects within a SIG
by George Dunlap 10 Mar '15

10 Mar '15

At the moment, we're essentially using yum repos as the "patch" mechanism to CentOS Base: SIGs populate a repo with packages they want to add / override, and all other packages default to Base. The current setup is that every sig has exactly one production repo per CentOS version. Also, we seem to be wanting to see SIGs not as individual projects, but to make the 'G' an actual "group": so, for instance, the Virt SIG has both Xen and Docker, and we've recently approved oVirt. But there's a bit of a conflict here: what if one project in the SIG wants to use the package from Base, and another project in the SIG wants to use a custom-built package? Or what if both projects want to customize their packages in different ways? In particular: the Docker project in the Virt SIG wants to supply updated versions of Docker; but at the moment uses the kernel package from Base. The Xen project, on the other hand, needs to supply a different kernel package that has dom0 support enabled. Up until this point, this hasn't been an issue because I've been doing Xen development in virt6-testing, and Lokesh has been doing Docker development in virt7-testing. But I'm hoping to get Xen for CentOS 7 out soon, and I was just about to upload the Xen kernel to the CBS, when it occurred to me that if I did so, then everyone using the virt7-testing repo for Docker would suddenly get my updated kernel as well. So it seems we have a couple of ways to approach it. 1. Keep it one repo per SIG, and make all projects in a SIG sort out shared dependencies. 2. Allow one repo per *project* within a SIG (e.g., virt6-xen, virt7-docker) 3. Have some alternate way of doing a "patch", instead of repos. In the case of xen / docker, I haven't talked with Lokesh about this at all; it may be that he's fine with sharing a kernel with Xen. But it does increase the workload: now Lokesh needs to maintain the Docker side of the kernel, whereas before they could just rely on our upstream to do a lot of that testing. Furthermore, it increases the complexity of development and testing: before when doing kernel work, I could just test Xen; now the kernel needs to be tested by both Xen and Docker. And finally, now users of both projects get a kernel update whenever either one does. Which, of course, is pretty much the same as any other distro; but as a whole, at the moment at least, we have a lot less resources than any other distro our size and popularity. On the whole I'm inclined to prefer #2. Thoughts? -George

5 8

making distro evolving content available to CBS
by Karanbir Singh 10 Mar '15

10 Mar '15

hi, I'd like to see how we can get pre-release distro content into the cbs so that SIG's are able to start doing their thing and looking at / building / CI / release prep while the distro is shaping up. this content will need to come with the assumption that the rpms might need to be rebuilt, and none of them will be signed, and some of them will not see an EVR change as they are rebuilt. Within those constraints - what sort of a mechanism would work for : - the CBS team , to bring this content in - the SIGs - who want to consume some of this - the testing / CI team - to make sure these dont get - the CentOS QA team - who likely dont want to see bug reports filed against unreleased content ( in some cases, they actually might want to see problem reports, so they can help fix before release! ) and we just need to make sure we dont release anything built against this unsigned content. -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

2 1

Release for Atomic Host Feb 2015 rolling builds
by Karanbir Singh 10 Mar '15

10 Mar '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We are pleased to announce CentOS Atomic host rolling builds for CentOS Linux. This release is tagged 20150228_01 : It represents content from Feb 2015 CentOS Linux 7 + Atomic SIG and Virtualisation SIG. A major change in this release is that all images are now built via anaconda and no longer consume the ostree-toolbox chain. This includes the generic cloud image ( qcow2 file ) and the Vagrant-VirtualBox and Vagrant-LibVirt ( .box ) files. The upstream ostree repo remains unchanged, including centos-release-atomic. Note that the Generic Cloud image ( qcow2 file ) still requires a NoCloud cloud-init configuration iso to enable access. The Vagrant images, do not. They will just work with the vagrant default access policy. - ----------- File: CentOS-7-x86_64-AtomicHost-20150228_01.qcow2 Sha256: ec94554d92558328e2ce7627996ce21faf76105be125d7f711615c1850956e0a File: CentOS-7-x86_64-AtomicHost-20150228_01.qcow2.xz Sha256: b366f73e4445e139a2df2bef935be863a377960714bdad22d5b47593d7ccec93 File: CentOS-7-x86_64-AtomicHost-Vagrant-LibVirt-20150228_01.box Sha256: fbf23af105258df88a85393dff2104348c7f4004562502a2b5711309eeaac473 File: CentOS-7-x86_64-AtomicHost-Vagrant-VirtualBox-20150228_01.box Sha256: 4dbeeba41dbf4d8f07047494399c7b0997bfde9fe049aba34f8f199e65c9e862 Symlinks are provided that will always map to the latest released builds, as follows ( including their current mapping ) http://buildlogs.centos.org/rolling/7/isos/x86_64/CentOS-7-x86_64-AtomicHos… - -> CentOS-7-x86_64-AtomicHost-20150228_01.qcow2 http://buildlogs.centos.org/rolling/7/isos/x86_64/CentOS-7-x86_64-AtomicHos… - -> CentOS-7-x86_64-AtomicHost-20150228_01.qcow2.xz http://buildlogs.centos.org/rolling/7/isos/x86_64/CentOS-7-x86_64-AtomicHos… - -> CentOS-7-x86_64-AtomicHost-Vagrant-LibVirt-20150228_01.box http://buildlogs.centos.org/rolling/7/isos/x86_64/CentOS-7-x86_64-AtomicHos… - -> CentOS-7-x86_64-AtomicHost-Vagrant-VirtualBox-20150228_01.box These symlinks will be updated to point at the latest tested and released media and make for a good target in automation that requires CentOS Linux media. - ---------- For more information and comments please join us on the centos-devel mailing list ( http://lists.centos.org/ ) Thanks to Colin Walters, Ian McLeod, Fabian Arrotin, Thomas Oulevey, Jason Brooks and Joe Brockmeier for their help in building up this process and their contributions to the Atomic SIG efforts. Enjoy! - -- Karanbir Singh, Project Lead, The CentOS Project -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJU+b/EAAoJEI3Oi2Mx7xbtCywH/09SPCZwGW2q0D0k0f6tK7Tl F71n4UUIpDAMKOPF9b2AGWsOpY09GadlTDTl3+uB3nbt+eLQuYbWVM4id+bpnkEO 5RecghMaP5VkA+Lkc8NbyBPYz1rtcGfR4R+JLMI1qf+BW7KOlOzAlI/asxLEwDzJ 1w0k+qzU0FXzDvxzRRAE/dqFDdVAIF2CZmEsxmBUPVGW+hRaKAEa3Sn8GV1NtPhH 4cQODF1QwpEQUQ4zbf1JcKWRZk94wUuv585chaHIbq4pz5Mi05zVtR2w9jhcUVvm BzQhvRf7zSQDvInBewBW3VZHRih9I0/XtGbHRpjrNEmPO5lvScihOlLG9+YzA6Q= =rYcU -----END PGP SIGNATURE-----

3 4

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