devel

devel@lists.centos.org

5 participants
4641 discussions

Start a nNew thread

Re: [CentOS-devel] CentOS-7 / powerpc BE bring up
by Akira Kuno 18 Sep '15

18 Sep '15

I vote Little Endian. Akira Kuno Manager Power Systems Sales Promotion Server Solutions IBM Systems IBM Japan

3 3

Re: [CentOS-devel] CentOS 7 on power64 status
by sauvignon2015＠yahoo.co.jp 18 Sep '15

18 Sep '15

I vote for little Endian. I want same Endian as x86.

1 0

CentOS/Fedora Atomic Test Day 09/22
by Dusty Mabe 17 Sep '15

17 Sep '15

Hey all, Sorry for the wide distribution.. We'd like to promote the joint test day we are doing next week for Atomic. Please see Jason's blog post for more details and join us on the test day: http://www.projectatomic.io/blog/2015/09/combined-fedora-centos-atomic-test… - Dusty

1 0

CentOS SCLo SIG sync-up meeting on #centos-devel (2015-09-16)
by Honza Horak 16 Sep '15

16 Sep '15

SCLo SIG 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 = * are we ready to remove the temp pkgs from CBS? * dist-git repos creation -- anything missing? * docker images on the hub based on SCLo collections Honza

1 1

Re: [CentOS-devel] CentOS-7 / powerpc BE bring up
by Takashi Ohsawa 15 Sep '15

15 Sep '15

>Perhaps we can get folks who have shown interest in having Power on CentOS to post their preferred architecture here? My vote is LE architecture. Currently , I am using CentOS on IA. My application porting is easy because LE is same as IA's endian. -- -- Takashi Ohsawa --

4 3

Intent to participate to a ppc64le beta test
by Takashi Ohsawa 15 Sep '15

15 Sep '15

Hi, We are using CentOS on x86 server to our system. I appreciate your contribution in CentOS community. Your cooperation is really helping our system infrastructure. We are evaluating the new server of OpenPOWER community. We can find the technology innovation in this community, such as fast I/O accelerator, fast GPGPU. We would like to use CentOS on OpenPOWER because our skill and some operation tools are optimized on CentOS. I would like to contribute of evaluation CentOS ppc64le beta build when we can use it. -- -- Takashi Ohsawa --

3 2

Intent to Participate in CentOS for ppc64le Beta Validation
by Sameer Kumar 15 Sep '15

15 Sep '15

Hi, We, at Ashnik, are enterprise open source experts providing Operating system, virtualization, Infrastructure, database, Web server and Business Intelligence services and solutions across India and South East Asia. Ashnik is partner with EnterpriseDB, MongoDB, Pentaho, NGINX, Red Hat. We are excited about goods of open source coming to the hardware world with OpenPOWER. We wish to help in best way we can in bringing choice to enterprise segment and a cost effective Linux on Power Platform. The customer segment we work with and kind of solution which we have seen picking up works on Little Endian platform. Ashnik team from India is keen to be involved in CentOS initiative and build for ppc64le. We are keen to be part of Open Power consortium and contribute towards Beta Validations as CentOS ppc64le build progresses -- -- Best Regards Sameer Kumar | DB Solution Architect *ASHNIK PTE. LTD.* 101 Cecil Street, #11-11 Tong Eng Building, Singapore 069 533 T: +65 6438 3504 | M: +65 8110 0350 | www.ashnik.com

2 3

The Right Way to mount tmpfs using systemd with the right selinux security context
by George Dunlap 14 Sep '15

14 Sep '15

In the context of packaging Xen, I'm looking for the Right Way(tm) to mount a tmpfs with a suitable security context. = Background = xenstored is a daemon run in a Xen domain 0 (control domain). It acts as a sort of registry that domains and the toolstack can use to communicate and store important information. xenstored uses a simple database stored in /var/lib/xenstored/tdb . This file is not persistent across reboots, it is fairly small, and the access speed has a major impact on the speed of the system. For this reason, mounting /var/lib/xenstored as a tmpfs results is highly recommended. The Xen project ships a number of recommended systemd initscripts with its distribution. One of these is var-lib-xenstored.mount, which simply mounts tmpfs on /var/lib/xenstored. xenstored.service requires var-lib-xenstored.mount. The default CentOS selinux policies in /etc/selinux/targeted/modules/active/file_contexts contain labels for xenstored: /var/lib/xenstored(/.*)? system_u:object_r:xenstored_var_lib_t:s0 /usr/sbin/xenstored -- system_u:object_r:xenstored_exec_t:s0 (Presumably somewhere there's a connection defined between the two labels; I haven't found it yet.) The security context for /var/lib/xenstored is set automatically (I presume due to the above rule): # ls -aZ /var/lib/xenstored/ drwxr-xr-x. root root system_u:object_r:xenstored_var_lib_t:s0 . = The Problem = When var-lib-xenstored.mount mounts tmpfs at /var/lib/xenstored, the security context reverts to the default for tmpfs: # systemctl start var-lib-xenstored.mount # ls -aZ /var/lib/xenstored/ drwxr-xr-x. root root system_u:object_r:tmpfs_t:s0 . SELinux subsequently denies permission to xenstored to access the location, and xenstore fails. = Discussion = The version of var-lib-xenstored.mount in Xen 4.5 contains a security context in the mount options, which can be set at configure time; the result looks something like this: Options=mode=755,context=system_u:object_r:xenstored_var_lib_t:s0 Unfortunately, the way this was set up meant that if your system did *not* have selinux, then the mount would fail. So this was removed, leaving us the way things are above. I *could* patch var-lib-xenstored.mount in my xen package; but I would like to avoid patches as much as possible. Furthermore, as someone whose main job is to be an upstream Xen developer, I would prefer to make var-lib-xenstored.mount as useful as possible *by default*, without needing to be patched / modified by people downstream using selinux. One solution which has been proposed is to use a config file (say, /etc/sysconfig/xenstored) which contains a custom set of options for var-lib-xenstored.mount. However, when poking around, I couldn't find any other places where a context is manually added to a mounted place like that, which made me wonder if there was a better, more generic way to automatically get things to work properly. I did some poking around, and found that /usr/lib/systemd/rhel-readonly mounts things with tmpfs, and sorts out the selinux stuff by running restorecon after mounting it. I tried that, and it seems to work: # restorecon -R /var/lib/xenstored # ls -aZ /var/lib/xenstored/ drwxr-xr-x. root root system_u:object_r:xenstored_var_lib_t:s0 . Running "systemctl start xenstored.sevrice" afterwards gets a working xenstore. So I guess I was wondering if there was a better way to get /var/lib/xenstored labelled with the right contexts than trying to shove the contexts in at mount time. Is there a way to have systemd automatically call restorecon after mounting the filesystem? Or is there a better way to get systemd to mount a suitable tmpfs at /var/lib/xenstored? Thanks, -George

1 0

Request to join CentOS Atomic SIG
by Dusty Mabe 14 Sep '15

14 Sep '15

Hey Everyone, As a member of the Fedora Cloud Working Group (the group within Fedora that is most focused on atomic) I am interested in joining the CentOS Atomic SIG. My hopes are to find differences in the Fedora and CentOS versions of Atomic and try to minimize those where it makes sense so that we can provide a more consistent approach for people using Atomic Host. Additionally it would be nice to find places where Fedora and CentOS can re-use the same or similar processes to generate these deliverables. What are the steps I need to take to become a SIG member? Thanks, Dusty

6 6

CentOS-7 / powerpc BE bring up
by Karanbir Singh 14 Sep '15

14 Sep '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi Ashish, Fabian is putting together a VM ( or 2 if you need more ), for the BE bringup. This would be a fedora19 VM. Fabian: Ashish has confirmed that he has all the mock configs required to bringup the CentOS 7.1406 os/ release content, then build the updates upto May 2015 content. So here is what I see happening, 1) Fabian to setup a VM for ppc64 BE 2) Fabian to setup a VM for ppc ( multilib, 32 bit ) 3) Ashish to file a bug report at bugs.centos.org to req direct access, include ssh key 4) Fabian to get Ashish setup, and get Ashish an account on the ipv4 jumphost. 5) One that is in place, Ashish to build mock itself on the machines for either 64bit or 32bit 6) Fabian to let Ashish know the mirror url for fedora19, which would be the base of the builds 7) Ashish should then be able to kick off the first bringup cycle, with mock configs he already has in place. 8) build to CentOS-7 1406 content being complete. 9) Checkpoint at this stage, to evaluate payload, build process, build delivery and workout path to automating builds from there on. We are going to use the centos-devel mailing list for communications, and irc channel #centos-ppc I am going to once again request everyone to keep AWAY from private conversations, and stick to the community visible avenues, so we can all track ( and help! ) as things evolve. We can repeat the same process for LE, s/Ashish/James/ for that. I would defer to letting Ashish and James to include other people in the process as needed, however - all user accounts MUST be created via the bugs.centos.org process, and its important that Fabian is able to execute the creation + access ( so its logged and auditable ). Once we have step-5 in place, we can engage with Jim Perrin, and workout the modalities and process of including the effort into the CentOS AltArch SIG - which would give us a distro, test, delivery proces s. does this work for everyone involved here ? regards, - -- 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJV8ro0AAoJEI3Oi2Mx7xbtdV8IAIJTE2kiEXZNUpWo5K+q0OMh ArYZCdquv/ZHD6/HqO0Q3IkeuBEacm/yxtoAyDF3fE3j6TvO4WT1zmpAxGq3RtAS 0PwTqTjeqoFChXxmHu17IwSDgCCCtZr8KKQgbT42RYWdMtU01jFC/LxM1PPOfABR 4adO74Gp1Pl+Zprxd8x384nH3bppUq0Br7sz0jyIWG3AKgBchRoRwvIBnj6//zqo wkX9KtajxtpmJPrZh1n0ZKndyDiXAMWDkUTk6YQX4aVOqOI5ELgjjKiiR7GY1NFy NPSI/7lNLjyDtehl+NpcwJ+6UWd8oLTltA885f0ieSGfiuMOTb7+vBq9tA/R+cI= =Vrbc -----END PGP SIGNATURE-----

6 12

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