Re: DHCP and our hosts
> "MM" == Mike McGrath <[EMAIL PROTECTED]> writes: MM> [1] AFAIK DHCP cannot be done on aliased interfaces because it MM> shares a MAC with the physical interface. The DHCP protocol apparently allows one MAC address to acquire several IP addresses, with client identifiers. It looks like ISC DHCPD supports that. I haven't actually tried it. /Benny ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: intro. and help offer
Once upon a time Tuesday 13 March 2007, Jerry Amundson wrote: > Per AccountSystem, this account I just created, "currently includes > the various CVS repositories and Bugzilla." > It didn't. I created a Bugzilla account using the *e-mail address* of > my account system registration. That may not have been the right > thing... > > On 3/13/07, Jerry Amundson <[EMAIL PROTECTED]> wrote: > > On 3/13/07, Mike McGrath <[EMAIL PROTECTED]> wrote: > > > Jerry Amundson wrote: > > > > bacula testing (needs to get into extras) > > > > > > Excellent, Would you mind helping getting bacula into extras - > > > http://bugzilla.redhat.com/230344 > > So this needs to be assigned to me then? (unless there was some > original problem with the account, above, and I should be able to do > so myself...) > > Procedural things... > 1. Andreas Thienemann, who opened said bug, seemed well into this > already - was this lucrative position offered to Andreas first? ;-) Every package included in Fedora must be peer reviewed. So what you need to do is follow the procedure http://fedoraproject.org/wiki/Packaging/ReviewGuidelines > 2. Upstream is actively releasing a src.rpm - is there any criteria > whereby upstream's is used... hmm, I guess first requirement is > ability to "rpmbuild --rebuild", which this doesn't... I'll shut up > and start working now. :-) all packages must meet Fedora's guidelines. upstreams does not even come close. Dennis ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: intro. and help offer
On 3/14/07, Dennis Gilmore <[EMAIL PROTECTED]> wrote: Every package included in Fedora must be peer reviewed. So what you need to do is follow the procedure http://fedoraproject.org/wiki/Packaging/ReviewGuidelines Yes, that's the link I need. Thank you! jerry -- "Oh joy! Rapture! I've got a brain" -Scarecrow ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: Testers needed: mirrormanager
Francois Petillon wrote: Is there any reason why a GPG key ID & a SSH public key are needed to create an account ? Several people here manage the FTP mirrors server and we usually create a single account for mirrors management web interfaces. I could create a "fake" account (ie it would not be an official company account) but it is probably not the right way to solve the problem. For the most part people need the ssh key to access cvs though for general access I think it should be allowed to be blank. The GPG key is part of our current electronic signature process for the CLA, again should be allowed to be blank until the user wants to sign the CLA. We're working on writing a new account system we can examine those needs again. -Mike ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Smolt I18N
I've started working on internationalization for Smolt. It's not ready to commit to the main smolt repository, as it's not complete and I'm sure I've committed some boneheaded mistakes because I've never done any internationalizing of code before. I've set up a separate Mercurial repository here. You can access it through the web here: http://hg.ocjtech.us/smolt-i18n or check out a copy of the code: hg clone http://hg.ocjtech.us/smolt-i18n Jeff signature.asc Description: This is a digitally signed message part ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
puppet and our test boxes
I'm going to have all of our publictest and test boxes use puppet with the 'global' template. This will keep them in sync with FAS, SNMP, syslog, all that good stuff. Any objections? -Mike ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: DHCP and our hosts
On 13 Mar 2007 10:08:39 +0100, Benny Amorsen <[EMAIL PROTECTED]> wrote: > "MM" == Mike McGrath <[EMAIL PROTECTED]> writes: MM> [1] AFAIK DHCP cannot be done on aliased interfaces because it MM> shares a MAC with the physical interface. The DHCP protocol apparently allows one MAC address to acquire several IP addresses, with client identifiers. It looks like ISC DHCPD supports that. That'd be good. I'm inclined to use dhcp wherever possible... jerry -- "Oh joy! Rapture! I've got a brain" -Scarecrow ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Primary DNS server change
As part of creating people.fedoraproject.org I'm moving bind off of fpserv on to the torrent box just because of the nature of security on those two boxes. If you need to make a DNS change over the next week or so let me know so we can coordinate which one it be on. Jesse, the new primary IP will be 152.3.220.165 Once we've verified the install I'll send the request to iron mountain and send a follow up email to let everyone know when its complete. -Mike ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: Testers needed: mirrormanager
On Wed, Mar 14, 2007 at 08:27:35AM -0500, Mike McGrath wrote: > Francois Petillon wrote: > >Is there any reason why a GPG key ID & a SSH public key are needed to > >create an account ? Several people here manage the FTP mirrors server > >and we usually create a single account for mirrors management web > >interfaces. I could create a "fake" account (ie it would not be an > >official company account) but it is probably not the right way to > >solve the problem. > For the most part people need the ssh key to access cvs though for > general access I think it should be allowed to be blank. The GPG key is > part of our current electronic signature process for the CLA, again > should be allowed to be blank until the user wants to sign the CLA. > We're working on writing a new account system we can examine those needs > again. As you don't need to sign the CLA, you can choose to send your real GPG public key (preferred), or you can create a key which you then don't use. Likewise for the ssh public key - just create a keypair that you'll never use. And yes, folks working on the new account system know this seems odd and want to take care of it in the next version. :-) Thanks, Matt -- Matt Domsch Software Architect Dell Linux Solutions linux.dell.com & www.dell.com/linux Linux on Dell mailing lists @ http://lists.us.dell.com ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: cvsl10n CVSROOT
On Tue, 2007-03-13 at 18:17 +, Dimitris Glezos wrote: > Also, our TODO should somewhere include automerge: each time a new POT file is > committed the PO files could be automatically updated (currently not supported > at i18n.r.c but is in the TODO list there too). It was just turned on: http://www.redhat.com/archives/fedora-trans-list/2007-March/msg00037.html - Karsten -- Karsten Wade, RHCE, 108 Editor^ Fedora Documentation Project Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject quaid.108.redhat.com | gpg key: AD0E0C41 // signature.asc Description: This is a digitally signed message part ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: cvsl10n CVSROOT
On Tue, 2007-03-13 at 17:34 -0400, Bill Nottingham wrote: > Dimitris Glezos ([EMAIL PROTECTED]) said: > > Our translators have made it clear they want to use a SCM for the > > translations > > and said an *additional* web-based tool would be nice. So, let's first > > create > > our SCM and we'll see about whether we should use pootle. > > Use *one* SCM. How to gate currently hosted GIT/HG/etc into this is > unclear. :/ A first iteration at a solution could look like this: * Projects, regardless of SCM, generate POT file and use WUI or CLI to schedule pick-up of their POT into l10n.fp.o * l10n.fp.o has a WUI that sits in front of >1 SCM and has the ability to: - Translate through the WUI (download POT, upload PO) - Use one account (FAS) for all access (regardless of back-end SCM, it needs a *l10n group that all L10N members are within) - Provide statistics across all SCMs * For translators who want to use the CLI entirely for translations, they need to work directly with the SCM, however ... Note that I suggest a CLI for access to the same services the WUI is providing. The idea here would be to grow a CLI (fedoral10n?) that acts like the WUI - it interacts with >1 back-end SCM, uses FAS for auth+, etc. So, first feature of the fedoral10n CLI would be for developers (and scripts) to automate the management of POT/PO files. Second feature would be to give translators equivalent control that the WUI provides. This at least is my ideal. :) Now if I only new Python ... - Karsten -- Karsten Wade, RHCE, 108 Editor^ Fedora Documentation Project Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject quaid.108.redhat.com | gpg key: AD0E0C41 // signature.asc Description: This is a digitally signed message part ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
buildsys:/etc/cron.daily/sync-committers.sh
Can I move this to be hourly? We get people that are confused every so often. Is there a reason its set to only once a day? -Mike ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: puppet and our test boxes
On Wed, 2007-03-14 at 09:23 -0500, Mike McGrath wrote: > I'm going to have all of our publictest and test boxes use puppet with > the 'global' template. This will keep them in sync with FAS, SNMP, > syslog, all that good stuff. Any objections? Sounds good. Will puppet allow us to see what's been changed from the baseline config as well? So that it's easier to tell what things we need to take with us when we migrate a service from testing to production? -Toshio signature.asc Description: This is a digitally signed message part ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: buildsys:/etc/cron.daily/sync-committers.sh
On Wed, 2007-03-14 at 15:23 -0500, Mike McGrath wrote: > Can I move this to be hourly? We get people that are confused every so > often. Is there a reason its set to only once a day? > at one point in time it locked the db to add those so we didn't want to do it all the time. I don't believe there is any reason to have it be that way anymore. -sv ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: puppet and our test boxes
Toshio Kuratomi wrote: On Wed, 2007-03-14 at 09:23 -0500, Mike McGrath wrote: I'm going to have all of our publictest and test boxes use puppet with the 'global' template. This will keep them in sync with FAS, SNMP, syslog, all that good stuff. Any objections? Sounds good. Will puppet allow us to see what's been changed from the baseline config as well? So that it's easier to tell what things we need to take with us when we migrate a service from testing to production? -Toshio Yeah, on first run it logs to syslog. In addition it makes a backup of any file it replaces and stores the file on the puppet server. One interesting thing to note is package and service requirements. Lets say I need to deploy nrpe and nagios-plugins on a box so I can monitor it. If I say that /etc/nrpe.cfg requires nrpe to be installed and running and that it requires nagios-plugins-disk (to monitor the disk) it will automatically install them and start them. Which, if used properly, is a very nice feature. -Mike ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: Testers needed: mirrormanager
On Tue, 13 Mar 2007 14:13:27 -0500
<[EMAIL PROTECTED]> wrote:
> Try again, Toshio fixed it.
Seems to be broken again:
500 Internal error
The server encountered an unexpected condition which prevented it from
fulfilling the request. Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/cherrypy/_cphttptools.py", line
103, in _run applyFilters('before_main')
File "/usr/lib/python2.4/site-packages/cherrypy/filters/__init__.py",
line 151, in applyFilters method()
File "/usr/lib/python2.4/site-packages/turbogears/visit/api.py", line
157, in before_main plugin.record_request( visit )
File "/usr/lib/python2.4/site-packages/turbogears/identity/visitor.py",
line 165, in record_request identity= self.identity_from_request(visit.key)
File "/usr/lib/python2.4/site-packages/turbogears/identity/visitor.py",
line 89, in identity_from_request identity= source(visit_key)
File "/usr/lib/python2.4/site-packages/turbogears/identity/visitor.py",
line 146, in identity_from_form identity= self.provider.validate_identity
( user_name, pw, visit_key ) File
"/usr/lib/python2.4/site-packages/fedora/tg/identity/safasprovider.py",
line 105, in validate_identity except fedora.accounts.AuthError, e:
NameError: global name 'fedora' is not defined
Andreas aka ScottyTM
--
"Really, I'm not out to destroy Microsoft. That will just be a completely
unintentional side effect."
-- Linus Torvalds in NY Times interview
___
Fedora-infrastructure-list mailing list
Fedora-infrastructure-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: Testers needed: mirrormanager
On Tue, 2007-03-13 at 14:40 -0500, Mike McGrath wrote: > Axel Thimm wrote: > > > > Isn't the CLA supposed to contain the Export Compliance statement? I > > had signed the CLA some long time ago, and it still wants the Export > > Compliance statement from me. Or am I mixing apples and oranges? > > > I'm not sure if the CLA covers this (I don't think it does) but I do > know that you don't need a CLA to be a mirror but you do need to sign > the export agreement. Really we're not the right people to answer a > question like that, anyone know how legal questions like this should be > handled? I don't think you need a lawyer here. A read of the CLA makes it clear that it does not cover export control: http://fedoraproject.org/wiki/Legal/Licenses/CLA I've submitted my plain-English CLA to the appropriate legal counsel for approval -- that means this cannot be relied upon yet -- but it is at least close to the mark, and may help in clarifying for ya'll what the CLA is and is not: http://fedoraproject.org/wiki/KarstenWade/Drafts/PlainEnglishCLA IANAL, TINLA, YMMV, caveat emptor, etcetera. - Karsten -- Karsten Wade, RHCE, 108 Editor^ Fedora Documentation Project Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject quaid.108.redhat.com | gpg key: AD0E0C41 // signature.asc Description: This is a digitally signed message part ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: Testers needed: mirrormanager
On Wed, Mar 14, 2007 at 09:59:59PM +0100, Andreas Kupfer wrote: > On Tue, 13 Mar 2007 14:13:27 -0500 > <[EMAIL PROTECTED]> wrote: > > > Try again, Toshio fixed it. > > Seems to be broken again: > > 500 Internal error > > NameError: global name 'fedora' is not defined Toshio just found and fixed the FAS authentication code for real. Try now. Thanks for your patience. -Matt -- Matt Domsch Software Architect Dell Linux Solutions linux.dell.com & www.dell.com/linux Linux on Dell mailing lists @ http://lists.us.dell.com ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: Smolt I18N
O/H Jeffrey C. Ollie έγραψε: > I've started working on internationalization for Smolt. It's not ready > to commit to the main smolt repository, as it's not complete and I'm > sure I've committed some boneheaded mistakes because I've never done any > internationalizing of code before. I've set up a separate Mercurial > repository here. You can access it through the web here: > > http://hg.ocjtech.us/smolt-i18n > > or check out a copy of the code: > > hg clone http://hg.ocjtech.us/smolt-i18n Great! So, let me grab this opportunity to see our future possibilities for maintaining translations. I see us having three different scenarios in terms of hosting. 1. A project is hosted on `cvs.fedoraproject.org` (example: Docs) 2. A project is hosted on `hosted.fp.org` (example: Smolt) 3. A project is hosted elsewhere (example: yum) `cvs.fp.org` hosted = The first is quite easy to handle: we give read-write access to 'cvsl10n' group at the 'po/' subdirectory of each project. Translators use their FAS to checkout & checkin translations. A WUI shows statistics. Everything is great. The Docs project already decided to do it this way (and so will other projects if they move development off elvis). `hosted`-hosted = The second is more tricky since PO files are hosted on a different server & SCM of what translators use. Furthermore, the WUI needs somehow to "get" the statistics and show them together with the other ones. Three choices here: 2a. POs are hosted on `hosted` too. Translators can use the system with their existing FAS-account. We give them simple directions on how to use the different SCM (checkin, checkout, diff). Easier for maintainer, harder for translators. 2b. Same as 2a, but translators can submit the PO files from the WUI (addon to 2a, not substitute). The WUI will act as a SCM client (will need to be able to handle many types of SCM systems and be given commit access to po/ subdirs). 2c. The maintainer chooses to handle the burden and copies the POs over on `cvs.fp.org`, our "main" translation system when they need translation. Jesse & Jeremy tried this and said it is ugly. However, some maintainers might want to do it to ease the translators' job. With string & translation freeze dates, this might get easier. Hosted elsewhere Basically, same as the second, but 2a. is not an option here. (Note: Translators have showed preference to use only one SCM.) Conclusion == I, as a translator, would really like to have 2b. for every project not hosted on `cvs.fp.org`. Otherwise, I don't see a way I could handle different SCMs *plus* having to request CVS access to every project hosted elsewhere. Hope the above helped give a better picture. -d -- Dimitris Glezos Jabber ID: [EMAIL PROTECTED], GPG: 0xA5A04C3B http://dimitris.glezos.com/ "He who gives up functionality for ease of use loses both and deserves neither." (Anonymous) -- ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: Smolt I18N
Dimitris Glezos wrote: Great! So, let me grab this opportunity to see our future possibilities for maintaining translations. I see us having three different scenarios in terms of hosting. 1. A project is hosted on `cvs.fedoraproject.org` (example: Docs) 2. A project is hosted on `hosted.fp.org` (example: Smolt) 3. A project is hosted elsewhere (example: yum) `cvs.fp.org` hosted = The first is quite easy to handle: we give read-write access to 'cvsl10n' group at the 'po/' subdirectory of each project. Translators use their FAS to checkout & checkin translations. A WUI shows statistics. Everything is great. The Docs project already decided to do it this way (and so will other projects if they move development off elvis). Note: as far as actual servers go, hg, git and cvs are all being hosted at cvs.fedoraproject.org. `hosted`-hosted = The second is more tricky since PO files are hosted on a different server & SCM of what translators use. Furthermore, the WUI needs somehow to "get" the statistics and show them together with the other ones. Three choices here: 2a. POs are hosted on `hosted` too. Translators can use the system with their existing FAS-account. We give them simple directions on how to use the different SCM (checkin, checkout, diff). Easier for maintainer, harder for translators. This should be fairly simple to set up though I'm not that familiar with acls in mercurial right now. 2b. Same as 2a, but translators can submit the PO files from the WUI (addon to 2a, not substitute). The WUI will act as a SCM client (will need to be able to handle many types of SCM systems and be given commit access to po/ subdirs). 2c. The maintainer chooses to handle the burden and copies the POs over on `cvs.fp.org`, our "main" translation system when they need translation. Jesse & Jeremy tried this and said it is ugly. However, some maintainers might want to do it to ease the translators' job. With string & translation freeze dates, this might get easier. I agree, some maintainers may want this. In smolts case the strings probably won't change much and I'd be happy to treat the translators as 'upstream' for translations. In that scenario at least the translators get to keep on one, common, SCM and the hosted project can use whatever they want. There are drawbacks, its kind of nasty, and causes duplicate bits. -Mike ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
New List Member
Greetings to all! My name is Robert Pereira, I live at Brazil, on Salvador city. After open the Fedora Weekly News Issue 80, i saw tha announce "Fedora Infrastructure needs your help!" and then i decided get involved with the Infrastructure team. I work as Linux system administrator since 2001 focused on Red Hat and Fedora Core distributions to deploy Linux based network infrastructure solutions as mail, web, file, print and ftp services. Also virtualization, firewalls and migration to Linux and technical support. My first contribution with Fedora Project was the translation of some modules of the Fedora Project and translation of the Fedoras Core 4 Installation Guide to Brazilian Portuguese. Beyond of my sysadmin duties, I teach Linux in some educational institutions of the my city. I wish contribute as i can to sucess and growth of this project. My regards, Robert Pereira ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
