Re: Freeze break request for sigul fine tuning
On Tue, 18 Aug 2009, Ricky Zhou wrote: > On 2009-08-18 11:28:04 PM, Jesse Keating wrote: > > Sigul changes are very low risk, as we're mostly done with the signing > > and puppet is currently disabled on these hosts. However vault may be > > rebuilt tomorrow and if so I want the puppet modules to be correct for > > the rebuild. > +1 > +1 here as well though techncally they're not frozen yet only because we've not yet added them to the "is frozen" doc :) -Mike ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: Freeze break request for sigul fine tuning
On 2009-08-18 11:28:04 PM, Jesse Keating wrote: > Sigul changes are very low risk, as we're mostly done with the signing > and puppet is currently disabled on these hosts. However vault may be > rebuilt tomorrow and if so I want the puppet modules to be correct for > the rebuild. +1 Thanks, Ricky pgpPb3NIMbaE5.pgp Description: PGP signature ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Freeze break request for sigul fine tuning
Sigul changes are very low risk, as we're mostly done with the signing and puppet is currently disabled on these hosts. However vault may be rebuilt tomorrow and if so I want the puppet modules to be correct for the rebuild. -- Jes ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
[PATCH] Fix up the puppet modules for bridge and vault
New certs for bridge and server Make sure puppet remains off after the initial run --- .../nodes/sign-bridge1.fedora.phx.redhat.com.pp| 11 ++- .../nodes/sign-vault1.fedora.phx.redhat.com.pp | 12 ++-- modules/sigul/files/server.conf|2 +- modules/sigul/templates/bridge.conf.erb|2 +- 4 files changed, 14 insertions(+), 13 deletions(-) diff --git a/manifests/nodes/sign-bridge1.fedora.phx.redhat.com.pp b/manifests/nodes/sign-bridge1.fedora.phx.redhat.com.pp index 5251155..d710016 100644 --- a/manifests/nodes/sign-bridge1.fedora.phx.redhat.com.pp +++ b/manifests/nodes/sign-bridge1.fedora.phx.redhat.com.pp @@ -1,4 +1,5 @@ node "sign-bridge1.fedora.phx.redhat.com" { +$autodisablePuppet = 1 $fas_groups = [ 'sysadmin-main', 'sysadmin-releng' ] include phx include fas::client @@ -13,11 +14,11 @@ node "sign-bridge1.fedora.phx.redhat.com" { # cwd => '/', # command => '/etc/init.d/sshd stop; /sbin/chkconfig sshd off', # } -# exec { "disable-puppet": -# cwd => '/', -# onlyif => '/bin/ls /var/run/puppet/puppetd.pid > /dev/null 2>&1', -# command => '/etc/init.d/puppet stop; /sbin/chkconfig puppet off', -# } + exec { "disable-puppet": + cwd => '/', + onlyif => '/bin/ls /var/run/puppet/puppetd.pid > /dev/null 2>&1', + command => '/etc/init.d/puppet stop; /sbin/chkconfig puppet off', + } # Firewall Rules, allow sigul server through. $tcpPorts = [ '44333:443334' ] diff --git a/manifests/nodes/sign-vault1.fedora.phx.redhat.com.pp b/manifests/nodes/sign-vault1.fedora.phx.redhat.com.pp index 20c1615..1b5641d 100644 --- a/manifests/nodes/sign-vault1.fedora.phx.redhat.com.pp +++ b/manifests/nodes/sign-vault1.fedora.phx.redhat.com.pp @@ -1,5 +1,5 @@ node "sign-vault1" { -#$autodisablePuppet = 1 +$autodisablePuppet = 1 $fas_groups = [ 'sysadmin-main', 'sysadmin-releng' ] include phx include fas::client @@ -14,11 +14,11 @@ node "sign-vault1" { # cwd => '/', # command => '/etc/init.d/sshd stop; /sbin/chkconfig sshd off', # } -# exec { "disable-puppet": -# cwd => '/', -# onlyif => '/bin/ls /var/run/puppet/puppetd.pid > /dev/null 2>&1', -# command => '/etc/init.d/puppet stop; /sbin/chkconfig puppet off', -# } + exec { "disable-puppet": + cwd => '/', + onlyif => '/bin/ls /var/run/puppet/puppetd.pid > /dev/null 2>&1', + command => '/etc/init.d/puppet stop; /sbin/chkconfig puppet off', + } # Need iptables blocking everything here diff --git a/modules/sigul/files/server.conf b/modules/sigul/files/server.conf index 9145343..6b57753 100644 --- a/modules/sigul/files/server.conf +++ b/modules/sigul/files/server.conf @@ -10,7 +10,7 @@ max-file-payload-size: 1073741824 # Maximum accepted size of payload stored in server's memory max-memory-payload-size: 1048576 # Nickname of the server's certificate in the NSS database specified below -server-cert-nickname: sigul-server - Fedora Project +server-cert-nickname: sign-vault1 - Fedora Project [database] # Path to a directory containing a SQLite database diff --git a/modules/sigul/templates/bridge.conf.erb b/modules/sigul/templates/bridge.conf.erb index dde6bf7..f834e52 100644 --- a/modules/sigul/templates/bridge.conf.erb +++ b/modules/sigul/templates/bridge.conf.erb @@ -2,7 +2,7 @@ [bridge] # Nickname of the bridge's certificate in the NSS database specified below -bridge-cert-nickname: sigul - Fedora Project +bridge-cert-nickname: sign-bridge1 - Fedora Project # Port on which the bridge expects client connections client-listen-port: 44334 # Port on which the bridge expects server connections -- 1.5.5.6 ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: Seeking comments on my proposal
Mel Chua wrote: >> Got the outline of my proposal here >> https://fedoraproject.org/wiki/SugarZilla > > Nifty. My only comment: How can we make sure that the workflow/interface > for SugarZilla is what its intended userbase needs? (It's easy for us to > sit here and say "yes, that will be better for 8-year-olds," but how do > we know that?) > > Might be a good thing to get a Design team consultation on. > > --Mel I had planned to get some design folks involved, in fact I will need help in that area. I am shooting for the simplest interface possible that is able to gather the needed info. Steven -- = Steven M. Parrish - gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: Seeking comments on my proposal
Got the outline of my proposal here https://fedoraproject.org/wiki/SugarZilla Nifty. My only comment: How can we make sure that the workflow/interface for SugarZilla is what its intended userbase needs? (It's easy for us to sit here and say "yes, that will be better for 8-year-olds," but how do we know that?) Might be a good thing to get a Design team consultation on. --Mel ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Seeking comments on my proposal
Got the outline of my proposal here https://fedoraproject.org/wiki/SugarZilla I welcome any comments Steven -- = Steven M. Parrish - gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Last call for talking points - what makes you excited about F12?
If you've got a moment for some last-minute help... We (Marketing) will be freezing the F12 talking points list today, and are still somewhat light in the "what makes Fedora awesome for admins and developers?" categories. Right now we have "libguestfs and kvm improvements" for admins and "maybe moblin" for developers, but there must be more - and more reasons why they're awesome (why *is* libguestfs something that makes admins happy?). We figured you would know. The features list is at https://fedoraproject.org/wiki/Releases/12/FeatureList. If you've got a moment, please take a look at that, then edit https://fedoraproject.org/wiki/F12_talking_points with the things that are making you (as admins and devels) happy about F12 coming out. Help us promote the heck out of your work. ;) Thanks! --Mel PS: I know this is last-minute notice - sorry about that. We're still learning how to do things on a schedule, and next time around we'll put the call out here much earlier. ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: Wan't to join and why
Paul W. Frields wrote: > On Tue, Aug 18, 2009 at 09:15:48AM -0400, Steven M. Parrish wrote: >> Rahul Sundaram wrote: >> >> > On 08/18/2009 05:51 PM, Steven M. Parrish wrote: >> > >> What I am looking to do now is create a very simplified bugzilla >> interface that can be used by OLPC users, mostly children, to report >> issues with Sugar >> Activities in Fedora. Will develop in PHP and would like to develop >> and test it on one of the publictest servers. >> >> Also would like to help maintain the cvs servers and projects >> contained there. >> >> Any questions just ask. >> >> >>> Is this intended to be deployed onto Fedora Infrastructure boxes >> >>> eventually or just be developed/demoed on the publictest >> >>> infrastructure? >> >>> We haven't had development of known-non-Fedora stuff done previously >> >>> but this might be a valid first case. If it's intended to run on >> >>> Fedora >> >>> Infrastructure, we very much prefer developing them in python. In >> >>> fact, I don't think we have any non-python developed stuff. >> >>> >> >>> -Toshio >> >> >> >> It is intended to run on Fedora infrastructure. It is going to be an >> >> alternate front end to our current bugzilla instance. It could be >> >> built upon to create different front ends for other user groups as >> >> well. >> >> >> >> Developing it in Python will not be a problem. I am just in the >> >> beginning design stage atm. >> > >> > Very interesting. A related project >> > >> > https://fedoraproject.org/wiki/Bugzilla_Desktop_Client >> > >> > Rahul >> >> Sounds like we both have similar goals here. I think having both a OS >> based app and a simple web interface for our bugreporting is a great >> idea. >> >> Anything that makes it easier for normal users to report issues and give >> feedback will only lead to making Fedora a more user friendly distro. > > I know that there were folks in the Desktop SIG who were interested > in a more friendly bug filing Web interface, as well as other > possibilities for lowering the fright factor of Bugzilla. > Yes its something that was discussed at FudCon in January, but now that Sugar/OLPC is basing itself on Fedora I feel its important to get something going. -- = Steven M. Parrish - gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: Wan't to join and why
On Tue, Aug 18, 2009 at 09:15:48AM -0400, Steven M. Parrish wrote: > Rahul Sundaram wrote: > > > On 08/18/2009 05:51 PM, Steven M. Parrish wrote: > > > What I am looking to do now is create a very simplified bugzilla > interface that can be used by OLPC users, mostly children, to report > issues with Sugar > Activities in Fedora. Will develop in PHP and would like to develop > and test it on one of the publictest servers. > > Also would like to help maintain the cvs servers and projects contained > there. > > Any questions just ask. > > >>> Is this intended to be deployed onto Fedora Infrastructure boxes > >>> eventually or just be developed/demoed on the publictest infrastructure? > >>> We haven't had development of known-non-Fedora stuff done previously > >>> but this might be a valid first case. If it's intended to run on Fedora > >>> Infrastructure, we very much prefer developing them in python. In fact, > >>> I don't think we have any non-python developed stuff. > >>> > >>> -Toshio > >> > >> It is intended to run on Fedora infrastructure. It is going to be an > >> alternate front end to our current bugzilla instance. It could be built > >> upon to create different front ends for other user groups as well. > >> > >> Developing it in Python will not be a problem. I am just in the > >> beginning design stage atm. > > > > Very interesting. A related project > > > > https://fedoraproject.org/wiki/Bugzilla_Desktop_Client > > > > Rahul > > Sounds like we both have similar goals here. I think having both a OS based > app and a simple web interface for our bugreporting is a great idea. > > Anything that makes it easier for normal users to report issues and give > feedback will only lead to making Fedora a more user friendly distro. I know that there were folks in the Desktop SIG who were interested in a more friendly bug filing Web interface, as well as other possibilities for lowering the fright factor of Bugzilla. -- Paul W. Frieldshttp://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: Wan't to join and why
Rahul Sundaram wrote: > On 08/18/2009 05:51 PM, Steven M. Parrish wrote: > What I am looking to do now is create a very simplified bugzilla interface that can be used by OLPC users, mostly children, to report issues with Sugar Activities in Fedora. Will develop in PHP and would like to develop and test it on one of the publictest servers. Also would like to help maintain the cvs servers and projects contained there. Any questions just ask. >>> Is this intended to be deployed onto Fedora Infrastructure boxes >>> eventually or just be developed/demoed on the publictest infrastructure? >>> We haven't had development of known-non-Fedora stuff done previously >>> but this might be a valid first case. If it's intended to run on Fedora >>> Infrastructure, we very much prefer developing them in python. In fact, >>> I don't think we have any non-python developed stuff. >>> >>> -Toshio >> >> It is intended to run on Fedora infrastructure. It is going to be an >> alternate front end to our current bugzilla instance. It could be built >> upon to create different front ends for other user groups as well. >> >> Developing it in Python will not be a problem. I am just in the >> beginning design stage atm. > > Very interesting. A related project > > https://fedoraproject.org/wiki/Bugzilla_Desktop_Client > > Rahul Sounds like we both have similar goals here. I think having both a OS based app and a simple web interface for our bugreporting is a great idea. Anything that makes it easier for normal users to report issues and give feedback will only lead to making Fedora a more user friendly distro. Steven -- = Steven M. Parrish - gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: Wan't to join and why
On 08/18/2009 05:51 PM, Steven M. Parrish wrote: >>> What I am looking to do now is create a very simplified bugzilla >>> interface that can be used by OLPC users, mostly children, to report >>> issues with Sugar >>> Activities in Fedora. Will develop in PHP and would like to develop and >>> test it on one of the publictest servers. >>> >>> Also would like to help maintain the cvs servers and projects contained >>> there. >>> >>> Any questions just ask. >>> >> Is this intended to be deployed onto Fedora Infrastructure boxes >> eventually or just be developed/demoed on the publictest infrastructure? >> We haven't had development of known-non-Fedora stuff done previously >> but this might be a valid first case. If it's intended to run on Fedora >> Infrastructure, we very much prefer developing them in python. In fact, >> I don't think we have any non-python developed stuff. >> >> -Toshio > > It is intended to run on Fedora infrastructure. It is going to be an > alternate front end to our current bugzilla instance. It could be built > upon to create different front ends for other user groups as well. > > Developing it in Python will not be a problem. I am just in the beginning > design stage atm. Very interesting. A related project https://fedoraproject.org/wiki/Bugzilla_Desktop_Client Rahul ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: Wan't to join and why
Toshio Kuratomi wrote: > On 08/17/2009 03:48 PM, Steven M. Parrish wrote: >> Hi guys and gals, >> >> I am looking to join both the sysadmin-test and sysadmin-cvs groups. Why >> you >> might ask? Well I'll tell you. I wan't to get more involved in Fedora. >> >> Here is my current Fedora resume... >> >> - BugZapper for both KDE and Packagekit. >> - Maintain 20+ packages and am a Sponsor in the packaging group. >> - Work closely with the OLPC and Sugar folks at getting and maintaining >> the packages in Fedora >> - Responsible for creating builds of F11 with Sugar specifically for the >> OLPC XO-1 (Hope to get an XO-1.5 soon) see >> http://wiki.laptop.org/go/F11_for_XO-1 for info on this. >> >> What I am looking to do now is create a very simplified bugzilla >> interface that can be used by OLPC users, mostly children, to report >> issues with Sugar >> Activities in Fedora. Will develop in PHP and would like to develop and >> test it on one of the publictest servers. >> >> Also would like to help maintain the cvs servers and projects contained >> there. >> >> Any questions just ask. >> > Is this intended to be deployed onto Fedora Infrastructure boxes > eventually or just be developed/demoed on the publictest infrastructure? > We haven't had development of known-non-Fedora stuff done previously > but this might be a valid first case. If it's intended to run on Fedora > Infrastructure, we very much prefer developing them in python. In fact, > I don't think we have any non-python developed stuff. > > -Toshio It is intended to run on Fedora infrastructure. It is going to be an alternate front end to our current bugzilla instance. It could be built upon to create different front ends for other user groups as well. Developing it in Python will not be a problem. I am just in the beginning design stage atm. Steven = Steven M. Parrish - gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list