Re: Gump on Moof
Adam Jack wrote: I know we are about to install on new hardware, but do we wish to send the moof install live? Surely having an OSX run is a good thing, since it allows greater coverage. If we chose to proceed, I think we need: 1) A 'gump' account on moof that we can su to. 2) A cronjob in that account (with environment set up). 3) Perhaps tomcat/forrest installed (for webapp xdocs). regards, Adam Sounds good, Antoine PS : I am impressed by the work you are doing on gump Adam. Cheers, Antoine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: User id that runs Gump on moof (and LSD...)
Adam R. B. Jack wrote: Anybody know how to do a share cronjob any other way? use a cronjob to update the crontab. snip/ I hope that we can still get these. with all the e-mail traffic, we really need to start putting that kind of stuff in places where it'll be found again. -- cheers, - Leo Simons --- Weblog -- http://leosimons.com/ IoC Component Glue -- http://jicarilla.org/ Articles Opinions -- http://articles.leosimons.com/ --- We started off trying to set up a small anarchist community, but people wouldn't obey the rules. -- Alan Bennett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: User id that runs Gump on moof (and LSD...)
Adam R. B. Jack wrote: BTW: Here is my request. For each person taking over a machine, please document that machines config/set-up in the wiki. [I think Leo asked for this in a JIRA entry.] I strongly dislike the concept of having a machine owned by a single person. I'm all in favor of creating the workgroup gump and let everybody be responsible for it on moof. I also think that we should start thinking about a better way to do a gump federation. ah, I also think that gump should not be a static webapp anymore. -- Stefano. smime.p7s Description: S/MIME Cryptographic Signature
Re: User id that runs Gump on moof (and LSD...)
Adam R. B. Jack wrote: Since I have LSD running under 'ajack' as are gump.try.sybase.com and gump.dotnot.org, I think we need somebody else's id to run the Apache Python Gump on moof. This is especially important with me going away next week. Seems my orig email didn't make it to the list... what we could also do is create a 'gump' user, and give multiple people the password. Alternatively, we don't give out the password, but add multiple people's keys to the authorized_keys file. The former has the advantage that you could 'su gump', the latter is probably a little safer. I don't like the single point of failure we have now at all. As far as lsd goes, I'm familiar with the setup, and I'm root so I can 'su ajack' all I want. The same goes for Stefano on moof, I think. I'm also supposed to be catching a train in five mins so I don't have time to change anything over there right now. -- cheers, - Leo Simons --- Weblog -- http://leosimons.com/ IoC Component Glue -- http://jicarilla.org/ Articles Opinions -- http://articles.leosimons.com/ --- We started off trying to set up a small anarchist community, but people wouldn't obey the rules. -- Alan Bennett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: User id that runs Gump on moof (and LSD...)
what we could also do is create a 'gump' user, and give multiple people the password. Alternatively, we don't give out the password, but add multiple people's keys to the authorized_keys file. I've always frowned on shared user ids (assuming they were excuses for not getting group permissions right) but that isn't the case here, we are working around an SVN bug. [If the bug really does only have a life expectancy of a few weeks, the rollout might take longer.] As such +1 to this idea. So long as gump is a member of the gump group, that we all have ids within, then it can be easily obsoleted once unecessary. I don't like the single point of failure we have now at all. 100% agreed. Anybody know how to do a share cronjob any other way? I'm also supposed to be catching a train in five mins so I don't have time to change anything over there right now. I agree, it'd be daft to do a quick transition without everybody around. That said, what I am really hoping for is: 1) Grant folks access to live/working Gumps so they can do 'quick runs' (like python gump/debug.py xmlunit --debug --quick, to test properties, etc.) 2) Grant folks access to live/working Gumps to spread the knowledge, and get more input/opinions on how to install this nicely. 3) Get documentation for the installs into the wiki, and that documentation come from somebody unfamiliar with the config, so they explain it better. I hope that we can still get these. regards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: User id that runs Gump on moof (and LSD...)
I am also +1 I am also +1 on the idea of the gump user. Impersonal users are often used by organizations setting up automated jobs. I have seen impersonal users used for : - running application servers in a bank, - running builds in a large software house, The impersonal user is a good medium to make sure that an application will go on running, whoever takes care of managing it, and whatever the vagaries of personal turnover in open source organizations or in for-profit companies. Adam R. B. Jack wrote: what we could also do is create a 'gump' user, and give multiple people the password. Alternatively, we don't give out the password, but add multiple people's keys to the authorized_keys file. I've always frowned on shared user ids (assuming they were excuses for not getting group permissions right) but that isn't the case here, we are working around an SVN bug. [If the bug really does only have a life expectancy of a few weeks, the rollout might take longer.] As such +1 to this idea. So long as gump is a member of the gump group, that we all have ids within, then it can be easily obsoleted once unecessary. I don't like the single point of failure we have now at all. 100% agreed. Anybody know how to do a share cronjob any other way? No. I do not know how to share a cronjob without an impersonal user. Also, one can only control (kill) the processes of one's own UNIX user. I'm also supposed to be catching a train in five mins so I don't have time to change anything over there right now. I agree, it'd be daft to do a quick transition without everybody around. That said, what I am really hoping for is: 1) Grant folks access to live/working Gumps so they can do 'quick runs' (like python gump/debug.py xmlunit --debug --quick, to test properties, etc.) 2) Grant folks access to live/working Gumps to spread the knowledge, and get more input/opinions on how to install this nicely. 3) Get documentation for the installs into the wiki, and that documentation come from somebody unfamiliar with the config, so they explain it better. I hope that we can still get these. regards Adam5o Cheers, Antoine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
User id that runs Gump on moof (and LSD...)
Since I have LSD running under 'ajack' as are gump.try.sybase.com and gump.dotnot.org, I think we need somebody else's id to run the Apache Python Gump on moof. This is especially important with me going away next week. I think it has to be one id (sadly) because an SVN bug (which I hear might get fixed in a few weeks) does nasties with the permissions on the .svn/entries file. Any takers? BTW: I'm also game to spread the wealth and give up on my id being the one on LSD, if folks things that is a good idea. regards, Adam -- Experience the Unwired Enterprise: http://www.sybase.com/unwiredenterprise Try Sybase: http://www.try.sybase.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: New software on moof (Re: Gump on moof)
Wilfredo Sánchez wrote: On Mar 16, 2004, at 7:04 PM, Stefano Mazzocchi wrote: Fred, we would like to have gump sending notice emails to the groups when failures appear, can we relay from moof? if not, what's the alternative? We can relay through mail.opensource.apple.com, which is on the same subnet. Postfix needs to be set up if we want delivery with /usr/sbin/sendmail, etc. to work. If you just need an SMTP server, mail.opensource.apple.com should do. I don't know what gump needs. Gump needs to send notice emails to the lists that own a particular project if the build fails, that's all. If we can relay thru mail.opensource.apple.com, that's fine for me. Ah, another thing, is the httpd in /usr/local/apache the one that is started up by default on moof now? No. That one is httpd 2.0, installed because it was part of my svn build (tarballs for which, by the way, are on my public iDisk). We'd need to edit the Startup Item if we want to start 2.0 instead (or also). I personally would like to have one web server running and that would be 2.0, but I really don't care, as long as I know which one is the default one. -- Stefano. smime.p7s Description: S/MIME Cryptographic Signature
RE: New software on moof (Re: Gump on moof)
Infrastructure@ I need you guys to change the proxy from port 16080 to 8080 for gump.apache.org. Done. Just waiting for an httpdadmin to do a cvs up and graceful. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gump on moof
gump group created: [moof:/usr/local/gump] wsanchez% nicl . / cd /groups/gump /groups/gump . name: gump gid: 100 passwd: * users: wsanchez bodewig antoine jerenkrantz ajack stefano [moof:/usr/local/gump] wsanchez% l total 8 -rw-r--r-- 1 ajack gump 1263 12 Mar 10:38 README drwxr-xr-x 14 ajack gump 476 12 Mar 09:52 forrest drwxrwsr-x 44 ajack gump 1496 3 Mar 00:13 packages drwxr-xr-x 6 ajack gump 204 12 Mar 10:15 public drwxr-xr-x 21 ajack gump 714 12 Mar 09:51 xml-forrest Let me know if anything broke there. Admins, to add a user to the group: [moof:/usr/local/gump] wsanchez% nicl . / cd /groups/gump /groups/gump append . users wsanchez I'm not sure what needs to happen with the Apache config. I think moof needs a new httpd.conf. The current one is the OS X Server default, which is mildy wonky. -wsv On Mar 12, 2004, at 9:45 AM, Adam R. B. Jack wrote: --On Friday, March 12, 2004 5:05 PM +0100 Antoine Lévy-Lambert [EMAIL PROTECTED] wrote: I would like also to be in this group. That directory is owned by the default group (admin). Fred might want to change it to a different group though. -- justin I believe we were hoping for a 'gump' group, but I'm game to let admins determine what they want. regards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gump on moof
Wilfredo Sánchez wrote: gump group created: [moof:/usr/local/gump] wsanchez% nicl . / cd /groups/gump /groups/gump . name: gump gid: 100 passwd: * users: wsanchez bodewig antoine jerenkrantz ajack stefano [moof:/usr/local/gump] wsanchez% l total 8 -rw-r--r-- 1 ajack gump 1263 12 Mar 10:38 README drwxr-xr-x 14 ajack gump 476 12 Mar 09:52 forrest drwxrwsr-x 44 ajack gump 1496 3 Mar 00:13 packages drwxr-xr-x 6 ajack gump 204 12 Mar 10:15 public drwxr-xr-x 21 ajack gump 714 12 Mar 09:51 xml-forrest Let me know if anything broke there. Admins, to add a user to the group: [moof:/usr/local/gump] wsanchez% nicl . / cd /groups/gump /groups/gump append . users wsanchez I'm not sure what needs to happen with the Apache config. I think moof needs a new httpd.conf. The current one is the OS X Server default, which is mildy wonky. I can take care of this. Adam, tell me what you want and I'll set it up. -- Stefano. smime.p7s Description: S/MIME Cryptographic Signature
Re: Gump on moof
I'm not sure what needs to happen with the Apache config. I think moof needs a new httpd.conf. The current one is the OS X Server default, which is mildy wonky. I can take care of this. Adam, tell me what you want and I'll set it up. Something along the lines of: http://moof.apache.org:16080/gump/public - /usr/local/gump/public/results and then (something like) http://gump.apache.org/results/public which ProxyPasses to above moof URL? Thanks. regards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: New software on moof (Re: Gump on moof)
We can relay through mail.opensource.apple.com, which is on the same subnet. Postfix needs to be set up if we want delivery with /usr/sbin/sendmail, etc. to work. If you just need an SMTP server, mail.opensource.apple.com should do. I don't know what gump needs. Gumpy uses Python's SMTP library, so we ought be able to just teach it this server use default port. Thanks. regards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gump on moof
BTW: Can somebody [I believe infr wanted to know of this, if not do it] create: http://moof.apache.org/gump/public - /usr/local/gump/public/results and (something like) http://gump.apache.org/results/public which ProxyPasses to above moof URL? Thanks in advance. Anybody on the Gump team willing/able to do this, or ought I make the request directly to infrastructure folks? regards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gump on moof
--On Monday, March 15, 2004 11:22 AM -0700 Adam R. B. Jack [EMAIL PROTECTED] wrote: Anybody on the Gump team willing/able to do this, or ought I make the request directly to infrastructure folks? I thought moof was still behind the firewall which blocks port 80. Has that changed? -- justin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gump on moof
Gump on moof --On Monday, March 15, 2004 11:22 AM -0700 Adam R. B. Jack [EMAIL PROTECTED] wrote: Anybody on the Gump team willing/able to do this, or ought I make the request directly to infrastructure folks? I thought moof was still behind the firewall which blocks port 80. Has that changed? -- justin I know nothing about moof, let me re-iterate *nothing* ;-) -- but wouldn't the ProxyPass be ok with that? The request come in to gump.apache.org (on Nagoya) and get forwarded to moof from an internal IP? Or, is the firewall on moof? I'm not trying to break any pre-defined rules, so if (for security/whatever), this isn't to be, so be it... regards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Gump on moof
As for : http://moof.apache.org:16080/gump/ I'm not sure where this translates too I don't have access to moof, so I can't look, but I'm sure that Stefano can find out, understood the ProxyPass directive, and knows how to get the data into the right place for the URL. When there is something on moof to redirect to, we can add the proxy to the configuration. Hopefully that won't be for too long, and we can get GUMP running within the data center. We might add more flavours (maybe smaller test ones), and we might want to add move content under the /public alias. Just design your URL. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gump on moof
Noel J. Bergman wrote: FWIIW: There has been content in there [/usr/local/gump/public/results] since Friday when I installed Gump and asked for this change. That's not helpful without changing the httpd server configuration to map a URL to that file system location. :-) Which is what I figured Stefano could do. I'm right on it. But I don't have access to the gump.apache.org descriptor, so if anybody could add this file to minotaur as /usr/local/apache2-install/www.apache.org/conf/vhosts/gump.apache.org requires: mod_proxy mod_cache mod_deflate mod_expire -- cut here - # # gump.apache.org # VirtualHost * DocumentRoot /x1/www/gump.apache.org ServerName gump.apache.org # # Start the rewriting engine and the expires heading # RewriteEngine On ExpiresActive On # # If the responses don't already contain expiration headers # make sure to set them, so that we don't get hit back # with resources of this type since they are not going # to change that frequently anyway # ExpiresByType text/css access plus 1 day ExpiresByType text/javascript access plus 1 day ExpiresByType image/gif access plus 1 day ExpiresByType image/jpeg access plus 1 day ExpiresByType image/png access plus 1 day # # Enable response deflation in those browsers that support it # and for those resources that are no already compressed # (since it would result in expansion rather than compression) # Also, make sure that proxies understand that this response # varies with the user agent so they don't cache results of # one browser for another one # Location / SetOutputFilter deflate BrowserMatch ^Mozilla/4 gzip-only-text/html BrowserMatch ^Mozilla/4\.0[678] no-gzip BrowserMatch \bMSIE !no-gzip !gzip-only-text/html SetEnvIfNoCase Request_URI .(?:gif|jpe?g|png)$ no-gzip dont-vary Header append Vary User-Agent env=!dont-vary /Location # # Enable gump to reside on another machine and proxy it transparently # ProxyPass/results/public/ http://moof.apache.org:16080/gump/ ProxyPassReverse /results/public/ http://moof.apache.org:16080/gump/ # # Since proxying happens on a machine from a different network, # we turn on response caching so that we avoid hitting back the server # if potentially avoidable. # CacheEnable mem /results/public/ CacheDefaultExpire 86400 MCacheSize 4096 MCacheMaxObjectCount 100 MCacheMinObjectSize 1 MCacheMaxObjectSize 2048 /VirtualHost --- end of file - Thanks much. -- Stefano. smime.p7s Description: S/MIME Cryptographic Signature
Re: Gump on moof
Copying Fred since he's the administrator of that machine and the osx man [FYI, he's the one who wrote parts of the Darwin kernel for OSX] Adam R. B. Jack wrote: It jumped onto moof and ran gump/check.py, and it (at least) runs our of the box (ok, out of CVS), which is a beautiful thing. nice to hear. Now, after a little planning, it is time to install Gumpy proper... A set of location questions (and as you know, I know nada about OSX, so feel free to completely alter all suggestions): 1) Where ought we put the code (checked out from cvs:gump)? /Gump/gump? put it on /usr/local/gump/gump [which mounts to /Volumes/data that has 33gb of free disk] 2) Where ought we put the packages? /Gump/Opt? /usr/local/gump/packages 3) Where ought we put the workspace /Gump/WS? [It will be *big*] /usr/local/gump/workspace 4) Where ought we put the HTML log output (so http://moof... can pick them up?] /usr/local/gump/results I will setup the apache conf files accordingly once you have something to show [this makes it easier to remap it to the URL space] I'd like the opportunity to run multiple Gump workspaces on this machine (perhaps some simple test ones, perhaps some 'docs centric ones', etc.) so I'd like to do some sort of /X/ on the end of each of these, where X is Public or ... in that case, I would suggest you keep /usr/local/gump as the base location and then do /usr/local/gump/[flavor]/gump /usr/local/gump/[flavor]/packages /usr/local/gump/[flavor]/workspace /usr/local/gump/[flavor]/results for each flavor. Please populate a README file on /usr/local/gump/README to describe the installation and how to replicate it in case somebody wants to do it or to understand what's in there. Thanks much for you work on this, it's very appreciated! ah, last thing, can you give us an estimation of the amount of disk space that you need? -- Stefano. smime.p7s Description: S/MIME Cryptographic Signature
Re: Gump on moof
Stefano Mazzocchi wrote: ah, last thing, can you give us an estimation of the amount of disk space that you need? [EMAIL PROTECTED] /data3]$ df -h FilesystemSize Used Avail Use% Mounted on (...) /dev/hdb2 27G 7.7G 18G 31% /data3 so that's approx. 8 GB per full instance/flavor at the moment, and some more during the runs. Expect this to grow as gump grows (and the success percentage increases); a minimum 15GB to start with I think for the initial setup. -- cheers, - Leo Simons --- Weblog -- http://leosimons.com/ IoC Component Glue -- http://jicarilla.org/ Articles Opinions -- http://articles.leosimons.com/ --- We started off trying to set up a small anarchist community, but people wouldn't obey the rules. -- Alan Bennett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gump on moof
put it on /usr/local/gump/gump Thanks. Somebody mind creating a /use/local/gump directory that the gump group has permissions to? regards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gump on moof
I would like also to be in this group. Cheers, Antoine Stefan Bodewig wrote: On Fri, 12 Mar 2004, Adam R. B. Jack [EMAIL PROTECTED] wrote: Somebody mind creating a /use/local/gump directory that the gump group has permissions to? And please add me to that group while you are at it. Thanks Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
