devel

devel@lists.centos.org

11 participants
4618 discussions

Presto drpms in vault.centos.org
by Johnny Hughes 14 Jan '14

14 Jan '14

All, We currently provide "presto - drpm" data in our current CentOS-6 tree and we all like that its there for speed of updates ... however, it is a couple hundred GB of space now in vault.centos.org for previous point releases. I would like to remove the drpms and rebuild metadata for the older centos repos to reclaim that space as we have 800GB of data there and if we don't cut back on size or get new machines for vault.centos.org to distribute, we are going to run out of space soon. I believe we can save between 100 and 150 GB by doing this now. It would also cut the size of repos moved to vault by 40-50 GB every point release. That means we can keep the current vault infrastructure for the foreseeable future with minimal impact on the mainline trees. Thanks, Johnny Hughes

4 5

updateinfo.xml data for CentOS repositories
by Shatil Rafiullah 14 Jan '14

14 Jan '14

Hi all, Could we revisit the missing updateinfo.xml in CentOS repos? A previous post (http://lists.centos.org/pipermail/centos-devel/2011-May/007480.html) mentioned it's difficult to get ahold of this data, but there have been developments since then. The Scientific Linux project publishes this data without issue, thanks to work done by OpenSUSE (http://lists.baseurl.org/pipermail/yum/2008-April/021802.html) and Oracle (https://blogs.oracle.com/linux/entry/updates_to_errata_on_uln) I'd love to get updateinfo.xml (or updateinfo.xml.gz) from CentOS rather than rely on another project, and I'm happy to contribute to making this happen. Shatil (@shatil)

5 7

CentOS Cloud SIG?
by Greg DeKoenigsberg 14 Jan '14

14 Jan '14

I remember once upon a time sending the first email to the Fedora Cloud SIG. Funny now to find myself sending an email asking about the CentOS Cloud SIG. :) Would love to find out what's required to get Eucalyptus packages into CentOS, and to build a Eucalyptus spin of CentOS. CentOS is already our platform of choice, all of our dependencies are either in CentOS or EPEL, and we've got an installer that sits as an updates.img on top of CentOS. Want to make sure we know the proper way of integrating into the new community. --g

10 17

Qt Creator for CentOS
by Dave Johansen 14 Jan '14

14 Jan '14

Is Qt Creator for Qt 4 available for CentOS (either 5 or 6)? I've installed the qt and qt-devel packages on CentOS 6 and I can launch Qt Designer, but is there a version of Qt Creator available? Thanks, Dave

1 1

oVirt and CentOS Cloud SIG
by Doron Fediuck 14 Jan '14

14 Jan '14

Hi guys, on behalf of the oVirt project, happy to join the community and we'll be happy to help where possible. Cloud SIG seems very relevant to oVirt. We're looking forward to assist with oVirt support as well. We have some CentOS fans in the oVirt community, so this should work well for everyone. - Currently we have our live oVirt [1] built using CentOS. So having you guys reviewing it would be beneficial. - For the standard el platform, we need some help with dependencies. Here's a short list which we would like to see go in over & above 6.5 * qemu-kvm compiled with RHEV flags * Support of librbd, libgfapi in qemu-kvm & libvirt, including sanlock & kernel modules * Network namespaces, VXLAN, GRE support in the IP stack (kernel through iproute, dnsmasq, etc) * The cloud-init version being used in RHEL 6.5. * Support of cgroups * selinux policies * Anything else you may be aware of. We'll probably find some more things on the way, but this would be a good start ;) Any suggestions from your side or things you'd like help with? Doron Fediuck [1] http://wiki.ovirt.org/OVirt_Live#oVirt-Live-1.1.iso_-_Oct_14th_2013

2 1

Documentation SIG
by Philip Mather 13 Jan '14

13 Jan '14

Has there been any interest or progress in the suggested Documentation SIG? -- Regards, Phil

4 3

A format request to create a Eucalyptus Special Interest Group
by Greg DeKoenigsberg 13 Jan '14

13 Jan '14

Hi folks. As I understand the "variants" proposal as it exists currently: http://www.centos.org/variants/ ...I think that the Eucalyptus installer, which relies upon CentOS currently, would do well as a variant. Which means that I would like to formally request the formation of a Eucalyptus SIG, according to protocol here: http://wiki.centos.org/SpecialInterestGroup So let me go through the requirements, one by one. * The topic for the group must be related to CentOS, or a use scenario for CentOS We build Eucalyptus, a cloud infrastructure application, around CentOS and have for 3 years now. We have an installer that is derived from Anaconda. We've sponsored CentOS events, and we deliver CentOS images to our users. Our packages are currently in a standalone repository, but we would be happy to merge these into whatever CentOS repository emerges (EPEL? Some new version of EPEL? CentOS core itself? I'm unclear on where this sits currently.) * There must be adequate control and feedback into the CentOS community Happy to discuss what this means to members of the CentOS community. * Generally, all communication as to the work of the SIG should be public, understanding that sometimes a matter may need to be private; in such cases, please consult with the Devteam member out of band of the SIG Happy to do business on a centos-eucalyptus mailing list. * 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 All code is GPL or Apache. * All documentation produced within the SIG must be compatible with the license of this wiki Happy to do that. * We would expect teams to be watchful of general CentOS directions from the Devteam It would be a great advantage to have help from the Devteam to do this. * At least one member of the SIG, who need not be the lead, needs to be a member of the CentOS Devteam. We are not trying to enforce any moderation, however, we feel that the actions of each SIG using CentOS resources needs to have visibility to the Devteam Happy to work with anyone on the Devteam for this. How do we proceed? What discussion needs to take place, and who can say yes to move this request forward? --g

5 14

Unified Cloud SIG
by Rich Bowen 13 Jan '14

13 Jan '14

There seems to be some consensus in various different threads that what we need is a single consolidated Cloud SIG effort, and decide, over time, if it's sensible to split into project-specific SIGs. Easier to start consolidated than try to figure out how to merge later. For those of you not following all of the various threads, here's some high points: Dave Neary says: What I would like to see is a CentOS stack which allows all of the cloud storage, networking, virt management and IaaS projects to show themselves in a good light - we will need newer stuff that isn't available in RHEL 6 to do so (and the sam will doubtless happen during the RHEL 7 release cycle), and it makes sense for us to talk & share the burden of supporting those newer components on top of core CentOS. Karanbir says, in response to me: On 01/10/2014 02:36 PM, Rich Bowen wrote: > I'd love to see a "choose your own cloud adventure" LiveCD variant, > where one could easily compare, OpenStack, Eucalyptus, CloudStack, > OpenNebula, etc., either side-by-side, or as options during the startup. > That would be quite cool. Technically, if we can get nested virt going, the livecd need only be a bare min CentOS6 install, with VM's that run complete cloud instances inside it. That would also sort out the massive pain of network setup, since we could make some levels of predictions on what the state is on the host. In a few days time, we should have the live media churn process going, this might be an interesting PoC to start with. Sebastien Gosaquen says: My personal view is that it would seem strange to have one SIG per project, a single cloud SIG will require coordination efforts amongst project to agree on a somewhat common framework for build. We could probably start with a single cloud SIG to discuss and identify requirements/issues and then see if a split is necessary. Does this seem a reasonable approach to everyone as a way forward? -- Rich Bowen - rbowen(a)redhat.com OpenStack Community Liaison http://openstack.redhat.com/

1 0

Cloud SIG interest from CloudStack
by Sebastien Goasguen 13 Jan '14

13 Jan '14

Hi, First, congrats to the centos community on the recent development. Reading the call for SIG, there is definitely interest from CloudStack to participate and create a ClouStack centOS variant for both instances and head/hypervisor nodes. Our default image template is already a centos template and our best quick start guide is based on CentOS. We also have a community run yum repo for all our packages. I see interest to create a Cloud Image for CloudStack clouds as well as creating variants for our management server and our hypervisor setup. I will be at the Dojo on January 31st and would be happy to discuss further. Cheers, -Sebastien Apache CloudStack PMC member

3 3

NethServer as CentOS Variant and SME SIG Proposal
by Alessio Fattorini 13 Jan '14

13 Jan '14

Hello everybody, my name is Alessio Fattorini and I'm part of a team of FLOSS developers that is working on a project named NethServer. We’d like to share with you our experience and our ideas for the future developments. You could think of NethServer as CentOS with some extra packages, particularly a powerful and extensible web interface that simplifies common administration tasks. NethServer is for the sysadmin who appreciates the effectiveness of a user interface which saves time compared to direct configuration file modification and for users who want to approach CentOS without having Linux skills. We didn't reinvent the wheel, NethServer is a partial rewrite of the original SME Server code, focusing on maintainability, extensibility and standard compliance with CentOS. We think we achieved those goals with: * A dynamic, streamlined user-interface * Standard components, tested widespread configurations * Minimal differences with upstream (CentOS) * Easy installation * Simplified administration tasks * Use of templates and text-based db for configuration (configuration will always be consistent) * Built-in extensibility NethServer architecture explicitly supports developers by making it easy to install and integrate additional software. We quickly added some pre-configured modules, installable with a “single click”, for example: LAMP framework Caching + filtering web proxy (with SSL filter) SOGo Groupware Mail Server with Antispam and Antivirus VPN (OpenVPN and IPsec/L2TP) Firewall (Shorewall) Intrusion detection (Snort) ownCloud More informations could be found on the official project website: www.nethserver.it. As soon as we read about CentOS variants, we have developed the idea of releasing NethServer as a CentOS variant and we are thinking of a SME SIG, a group exploring the needs of small enterprises (we are based in Italy, where the vast majority of enterprises is really small). According to you, does NethServer meet the basic requirements? We’ll be at Brussels Dojo and FOSDEM and we'd love to discuss directly with you our ideas. Cheers, Alessio and the NethServer team

10 16

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