Hi,
Earlier in the evening today Ralph, Fabian and I had a chat about the
present state of the language subsites. This email sort of summarises
the main issue ( s/w ).
We seem to have run into a slight technical hitch with punbb/fluxbb.
They dont support LDAP as a backend. And we had decided a few months
back that all new rollouts must have ldap backend so we can rollin
CentOS-DS / openldap based backend.
So we need to look at alternatives, and since the primary focus of these
international sites is going be forums : Here is a shortlist ( if there
is anything else that people are aware of, please add to this list )
- phpBB
- SMF
- Fudforum
- phorum
- fluxbb
Requirements:
- Must be able to scale ( couple of hundred thousand msgs )
- Must be able to handle ldap auth ( if it cant, whats involved in
writing the ldap-auth portion )
- Must address the specific requirements raised by the present
www.centos.org forum users ( Can you please fill this section in ? )
- Must support all languages we need ( pure utf8 support would be good )
- Secure
- Skin'able
Nice to have:
- Capable of running multiple instances from a single deployment
- responsive community :D
Things we will need to do:
- Decide on what s/w to use.
- Give the ArtWork people enough time to get the look & feel sorted.
- Migrate newbb forums from www.centos.org to $system ( hey, english is
a language too :D ).
- Migrate fr.centos.org into the final s/w
- setup {de/es/ja/it/pt_br}.centos.org
Actions:
Ralph and Fabian are going to work on setting up a test ldap server,
once that is online we will then start by installing into our
test-vm-farm the various s/w to eval them.
If anyone would like to help, please feel free to jump right in.
I'll setup a wiki page for this issue, which might be a good place to
track progress.
--
Karanbir Singh : http://www.karan.org/ : 2522219@icq
I noticed on the SIG that people interested in other ports of interest. I'd like to express interest in the IA64 port. What is the best way to get started?
I have two SGI Itanium 2 based machines. One 64 processor x 64GB SGI Altix and a 32 processor x 32GB RAM SGI Prism. They are currently running CentOS 4.8 and I would love to be able to run CentOS 5.5 on them to get them into compliance with the rest of the cluster.
--
James A. Peltier
Systems Analyst (FASNet), VIVARIUM Technical Director
Simon Fraser University - Burnaby Campus
Phone : 778-782-6573
Fax : 778-782-3045
E-Mail : jpeltier(a)sfu.ca
Website : http://www.fas.sfu.ca | http://vivarium.cs.sfu.ca
MSN : subatomic_spam(a)hotmail.com
Does your OS has a man 8 lart?
http://www.xinu.nl/unix/humour/asr-manpages/lart.html
Hi Guys,
Realistically, what are the best-of forum software out there at the
moment ? And what are the top 10 items on the forums moderators wish
list at this time ?
We can either move the forums to forums.centos.org or export them behind
a proxy at www.centos.org/forums ( I prefer the second option ).
Finally, lots of people seem to think that moving towards a
serverfault.org type of interface is more 'these days' than a
conventional forum setup. Thoughts ?
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
ICQ: 2522219 | Yahoo IM: z00dax | Gtalk: z00dax
GnuPG Key : http://www.karan.org/publickey.asc
hi Guys,
with a bit of time opening up, I've gone back to looking at the
yum-security issue and how we can address it ( i.e: atleast get the
basics working ).
I plan on doing the work in multiple stages as :
step1: get a basic set of metadata online so that people can detect if
an update is tag'd security, bugfix or enhancement
step2: get some more metadata added in, with bug id's and cve's into
that metadata
step3: get everything rolled out by default on all centos installs and
look at how external projects like spacewalk/pulp etc consume this metadata
At the moment, I'm only thinking about things and trying to scope out
the work. However, there is one issue that might be a spanner in the
works based on how we have mirror.centos.org setup.
What we have right now only provides for the <version>.<release> rpmset
and updates but only in relation to that specific tree (eg. /6.3/ is
what /6/ maps to at the moment ). Yum-security metadata in this repo
would then only be relevant to the rpms contained in /6.3/, whatever
repo they might be in - however, someone running 6.0 or 6.1. when
checking for updates is likely to miss interim updates that were
security tag'd at some release level or the other.
One way to work around this would be to have yum consider all interim
package metadata between installed.rpm and latest-in-repo.rpm ( which
would then mean that we would need the yum-security metadata to contain
all info for everything ever released ; isnt a problem as such ).
Or we setup a repo that has everything ever released. This in turn has
some serious caveats. Storage on every mirror being a good problem to
start with - however, in limited tests it looks like yum will work with
redirect, so while we would need the metadata to contain all packages,
the physical packages can still be handed out from vault.centos.org, but
that redirect foo needs some level of smartness on the mirror end;
trivial to implement when we control the mirror.centos.org network,
however a very large part of the mirror services are offloaded to
external mirrors - hundreds of them. Its super tricky getting smartness
onto each and every one of their machines.
Thoughts, concerns, ideas ? There is no 'work' thats been done at this
point on the problem, so we can take pretty much any course of action
that seems sane.
I feel its important that if we are going to provide a mechanism that
people will then in turn rely on to get patch requirements for their
machines, we need to make sure we have 100% coverage.
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
ICQ: 2522219 | Yahoo IM: z00dax | Gtalk: z00dax
GnuPG Key : http://www.karan.org/publickey.asc
hi,
http://people.centos.org/z00dax/openstack/essex/
repo file:
http://people.centos.org/z00dax/openstack/essex/CentOS-OpenStack-Essex-test…
These should be considered as testing packages and are based on the
upstream Open Stack preview 1 rpms set. These rpms are also signed with
the CentOS-6-Testing key and not the regular distro key. The .el6.alt
distag indicates they were built on the Alt.BuildSys and not the primary
system.[1]
https://access.redhat.com/knowledge/docs/Red_Hat_OpenStack_Preview/ is
perhaps the best place to go for a quick start process. The only major
difference is section 1.1 of the docs, that explain howto get the rhn
repo setup should be replaced by just downloading the above mentioned
.repo file into /etc/yum.repos.d/
It takes about 15 minutes to walk through and the end result is a
functional open stack install.
If anyone wants to offer up some basic template images to use, please do
so.
I have not tested to see how these rpms are going to work with/conflict
with the EPEL hosted openstack. Some feedback on that would be
appreciated as well.
- KB
[1]: Lots more details on that over the next few weeks.
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
hi Guys,
I already began to download a working copy of The CentOS Artwork
Repository with the intention of committing up the changes I've been
working on through these last 3 years and this way, put in place all the
information you need to test, verify and validate the work. I'm using a
slow commutated connection with an average speed of 5KB/s but things are
going on. I think the new directory structure should be online to the
end of this month, if everything goes as planned so far.
The CentOS Artwork Repository has changed significantly from that
version currently online to that one I pretend to share this month. The
directory structure currently online suffered significant changes as to
be completely replaced. A preview of the new directory structure I want
to share is in the following file:
http://wiki.centos.org/AlainRegueraDelgado?action=AttachFile&do=get&target=…
I would like to know what do we do with the old directory structure
currently available online (https://projects.centos.org/svn/artwork/)?
Do we remove it completely in the sake of the new one, or do we preserve
it in some other place (maybe under tags/)? ...
Once all the information be online and ready to be used, my plan is to
update the wiki page (http://wiki.centos.org/ArtWork) to introduce the
changes and the steps you need to follow in order to test the new
directory structure of The CentOS Artwork Repository. This info might
probably answer some of the questions laying around.
Best Regards,
--
Alain Reguera Delgado <alain.reguera(a)gmail.com>
hi Guys,
There was a problem with some old design models inside The CentOS
Artwork Repository which prevented centos-art.sh script from rendering
images at preparation process. The exact problem was given because of a
wrong path inside those old design models, specifically when
centos-art.sh script verified them.
This problem was fixed and you should be able to render images right
away, after updating your working copy of The CentOS Artwork Repository.
Other changes were also committed. The exact changes can be found at:
https://projects.centos.org/trac/artwork/timeline
Best regards,
--
Alain Reguera Delgado <alain.reguera(a)gmail.com>
hi Guys,
The CentOS Artwork Repository has been updated and needs to be tested by
The CentOS Community.
To test The CentOS Artwork Repository, you need to:
1. Follow the steps described in the page http://wiki.centos.org/ArtWork
to configure your workstation and your working copy.
2. Read the documentation at
`trunk/Manuals/Tcar-ug/tcar-ug-xhtml/index.html' to get a background
information about the production environment your working copy
is and how you can make use of it.
3. Explore the directory structure and play with centos-art.sh script.
Specifically with functionalities like render, help and locale. This
functionalities are described in the documentation named before. The
source code of these functionalities is also available at
trunk/Scripts/Bash/Functions, in case you are interested to contribute.
The present state (revision 880) of The CentOS Artwork Repository
published at https://projects.centos.org/svn/artwork is still an ongoing
work and needs much more attention. So, if you consider that something
must be improved or isn't working as expected, please send an e-mail to
centos-devel(a)centos.org describing what you've found. Likewise if you
find your self in trouble performing any of the previous steps, send an
e-mail to centos-devel(a)centos.org to find answers.
Personally, I'm very interested about the community needs and wishes
related to the creation of a consistent visual identity for The CentOS
Project that can be refreshed/updated each time a new major release of
The CentOS Distribution be published. Initially it may not be possible
to satisfy everything immediately but knowing such information will help
us to identify and give priority to those areas with higher demand and,
this way, work on the routes that will help us to get there, where we
want to be.
Best regards,
--
Alain Reguera Delgado <alain.reguera(a)gmail.com>
The latest version of mod_security has been built for CentOS-5 and
CentOS-6. Also included with in the CentOS-5 build is the version of
lua that ships with CentOS-6.3 as it is a requirement for the latest
mod_security.
Please test this build and provide feedback so that we can get this
released or fixed if there are issues.
http://people.centos.org/hughesjr/mod_security/
Thanks,
Johnny Hughes