You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@forrest.apache.org by Torsten Schlabach <ts...@apache.org> on 2005/05/01 22:08:10 UTC

Re: [RT] Serving Apache Forrest site from live Forrest

 > Apache is getting more hardware donated lately, so it may be that we
 > get to use it. In any case, I don't want to ask for the usage of it if
 > we don't yet know what to do with it, hence the RT.

Before making the full move and serve the websites entirely dynamically, 
how about providing a Forrestbot infrastructure for projects to use in 
order for the generation of today's static sites to be server based. We 
in the Apache Lenya project each have to maintain our personal Forrest 
installation and generate the HTML locally in order to maintain our 
website, see: http://lenya.apache.org/community/website-update.html

(This is painful, time consuming and error-prone IMO and experience.)

I was looking at this issue some time ago and learned that there are no 
alternatives to this at that point in time because the ASF does not have 
a hardware to host a production Forrest(bot). Or is that available in 
the meanwhile and we just missed it?

Regards,
Torsten

Nicola Ken Barozzi schrieb:
> Ross Gardler wrote:
> ...
> 
>> Whilst I totally agree with the sentiment of this RT, can I ask one 
>> simple question before even starting on this discussion:
>>
>> Where will we be able to host a live version of Forrest?
> 
> 
> Apache is getting more hardware donated lately, so it may be that we get 
> to use it. In any case, I don't want to ask for the usage of it if we 
> don't yet know what to do with it, hence the RT.
>

Re: zone for testing forrest

Posted by David Crossley <cr...@apache.org>.

Tim Williams wrote:
> out of curiousity, is there something that explains what a "zone" is
> at a higher level than the "solaris-zones" doc that David pointed to
> above?  Just an explanation of what it's for, is it a testbed? live
> demo site? or what?  What are/will be the benefit to non-committers if
> any?

It is a new server that was donated to ASF.
See helios.apache.org at http://www.apache.org/dev/machines.html
Basically a zone is a virtual server.

This means that each project can finally run their own dynamic
services. Everything has needed to be static documents in the past.

We are now able to eat our own dogfood. Yes it is a testbed.
Yes it is a live demo site. We also hope to work with Apache Lenya
to integrate our wares. That will need a place to experiment.

Benefit to non-committers? Good question.

The demo site will enable everyone to use Forrest in its dynamic
mode, and hopefully better understand its abilities. We expect
to have various demo sites, which you can run locally so won't
be much benefit there.

We will be able to run continuous testing, as with today's message.
That should help us to have a more reliable SVN trunk, which is a
benefit to everyone.

We should be able to provide statistics about resource usage
to help people estimate their own rerquirements.

It will enable our developer/user community to get more involved
with bug hunting and suggestions for enhancement. Use it live,
report the problems following some SVN change. Enabling the
community to help, should benefit everyone.

I can't think of any more benefits at the moment. We are actually
still in planning mode about what it can be used for. Suggestions
are welcome.

-David

Re: zone for testing forrest

Posted by Tim Williams <wi...@gmail.com>.

out of curiousity, is there something that explains what a "zone" is
at a higher level than the "solaris-zones" doc that David pointed to
above?  Just an explanation of what it's for, is it a testbed? live
demo site? or what?  What are/will be the benefit to non-committers if
any?
Thanks,
--tim

On 6/30/05, Ross Gardler <rg...@apache.org> wrote:
> David Crossley wrote:
> > I have done the next step in setting up some services on our zone.
> >
> > There is now a forrestbot running there to build the current "seed site".
> > Just the cron side of forrestbot for the moment. The forrestbot web interface
> > is the next thing to set up.
> >
> > There are cron jobs to automatically refresh the trunk every hour:
> > 'svn update; cd main; build clean; build'
> > and then generate the seed site. That works nicely.
> >
> > The result is at forrest.zones.apache.org ... point your browser
> > at the /ft/build/ directory (shorthand for forrestbot-trunk).
> 
> Superb, thanks David.
> 
> > I still need to figure out how to send mail if something fails.
> > Thorsten/Antonio: have the Lenya/Cocoon people been able to
> > send mail from their zone.
> 
> The Daisy install on the Cocoon zone is sending mails. Steven Noels set
> this up, and I believe he documented it somewhere in their zone.
> 
> > If other comitters want to look behind-the-scenes:
> > ssh forrest.zones.apache.org
> > cd /export/home/config
> > cat README.txt
> >
> > More later ...
> 
> Again, thanks David, I hope to dive in there next week.
> 
> Thorsten, has there been any progress on a Lenya instance for Doco, I'd
> like to set up an instance of Forrest over there to publish from Lenya
> (actually Daisy in the first instance since that is what I have working,
> but I am hoping this will show the way for a Lenya integration).
> 
> Ross
>

Re: zone for testing forrest

Posted by David Crossley <cr...@apache.org>.

Revive an old thread which has some good past info.

David Crossley wrote:
> Just a reminder that our zone is working.
> 
> The Forrest demos there are still very minimal.
> Anyway, there is at least something useful now working.
> The home page now describes what is available so far:
> 
> http://forrest.zones.apache.org/
> 
> Basically it is updating the trunk every hour
> and reporting any build problems. Then it builds
> the "forrest seed site" with forrestbot.
> 
> If any Forrest committers want a UNIX account, then just ask.
> 
> See more info about the zone, and what we hope to
> do with it, earlier in this thread.
> 
> More about the mail-from-zones situation below ...
> 
> On Thu, Jun 30, 2005 David Crossley wrote:
> > I have done the next step in setting up some services on our zone.
> > 
> > There is now a forrestbot running there to build the current "seed site".
> > Just the cron side of forrestbot for the moment. The forrestbot web interface
> > is the next thing to set up.
> > 
> > There are cron jobs to automatically refresh the trunk every hour:
> > 'svn update; cd main; build clean; build'
> > and then generate the seed site. That works nicely.
> > 
> > The result is at forrest.zones.apache.org ... point your browser
> > at the /ft/build/ directory (shorthand for forrestbot-trunk).
> > 
> > I still need to figure out how to send mail if something fails.
> > Thorsten/Antonio: have the Lenya/Cocoon people been able to
> > send mail from their zone.
> 
> Mads from Infra@ helped to sort that out just before
> ApacheCon EU 2005. So now we can send mail from the
> zone when one of our tests fail.
> 
> -David
> 
> > If other comitters want to look behind-the-scenes:
> > ssh forrest.zones.apache.org
> > cd /export/home/config
> > cat README.txt
> > 
> > More later ...
> > 
> > -David

Re: zone for testing forrest

Posted by David Crossley <cr...@apache.org>.

Thorsten Scherler wrote:
> David Crossley wrote:
> > 
> > I still need to figure out how to send mail if something fails.
> > Thorsten/Antonio: have the Lenya/Cocoon people been able to
> > send mail from their zone.
> 
> I was in #asfinfra, here the log:
> (16:40:43) target-x: hello all
> (16:41:12) target-x: Can we send mails from our zones?
> (16:41:51) quasi: it needs to be allowed on hermes
> (16:43:04) target-x: How can we from lenya and forrest request this
> permission?
> (16:43:16) target-x: mail to infrastructure list?
> (16:43:24) quasi: or a jira issue
> (16:43:24) target-x: from pmc head
> (16:43:37) target-x: or normal committer which is in the pmc?
> (16:44:52) gregor: what do we need it for, target-x?
> (16:45:02) quasi: if you send the mail cc to the pmc, then documentation
> should be ok 
> 
> HTH

Thanks, however i had already asked on Infra@
Will try again.

-David

Re: zone for testing forrest

Posted by David Crossley <cr...@apache.org>.

Just a reminder that our zone is working.

The Forrest demos there are still very minimal.
Anyway, there is at least something useful now working.
The home page now describes what is available so far:

http://forrest.zones.apache.org/

Basically it is updating the trunk every hour
and reporting any build problems. Then it builds
the "forrest seed site" with forrestbot.

If any Forrest committers want a UNIX account, then just ask.

See more info about the zone, and what we hope to
do with it, earlier in this thread.

More about the mail-from-zones situation below ...

On Thu, Jun 30, 2005 David Crossley wrote:
> I have done the next step in setting up some services on our zone.
> 
> There is now a forrestbot running there to build the current "seed site".
> Just the cron side of forrestbot for the moment. The forrestbot web interface
> is the next thing to set up.
> 
> There are cron jobs to automatically refresh the trunk every hour:
> 'svn update; cd main; build clean; build'
> and then generate the seed site. That works nicely.
> 
> The result is at forrest.zones.apache.org ... point your browser
> at the /ft/build/ directory (shorthand for forrestbot-trunk).
> 
> I still need to figure out how to send mail if something fails.
> Thorsten/Antonio: have the Lenya/Cocoon people been able to
> send mail from their zone.

Mads from Infra@ helped to sort that out just before
ApacheCon EU 2005. So now we can send mail from the
zone when one of our tests fail.

-David

> If other comitters want to look behind-the-scenes:
> ssh forrest.zones.apache.org
> cd /export/home/config
> cat README.txt
> 
> More later ...
> 
> -David

Re: zone for testing forrest

Posted by Thorsten Scherler <th...@apache.org>.

On Thu, 2005-06-30 at 14:15 +1000, David Crossley wrote:
> I have done the next step in setting up some services on our zone.
> 
> There is now a forrestbot running there to build the current "seed site".
> Just the cron side of forrestbot for the moment. The forrestbot web interface
> is the next thing to set up.
> 
> There are cron jobs to automatically refresh the trunk every hour:
> 'svn update; cd main; build clean; build'
> and then generate the seed site. That works nicely.
> 
> The result is at forrest.zones.apache.org ... point your browser
> at the /ft/build/ directory (shorthand for forrestbot-trunk).
> 
> I still need to figure out how to send mail if something fails.
> Thorsten/Antonio: have the Lenya/Cocoon people been able to
> send mail from their zone.
> 

I will ask.

> If other comitters want to look behind-the-scenes:
> ssh forrest.zones.apache.org
> cd /export/home/config
> cat README.txt
> 
> More later ...
> 

Nice, thanks. I will have a look on the weekend.
:)

> -David

salu2
-- 
thorsten

"Together we stand, divided we fall!" 
Hey you (Pink Floyd)

Re: zone for testing forrest

Posted by Ross Gardler <rg...@apache.org>.

David Crossley wrote:
> I have done the next step in setting up some services on our zone.
> 
> There is now a forrestbot running there to build the current "seed site".
> Just the cron side of forrestbot for the moment. The forrestbot web interface
> is the next thing to set up.
> 
> There are cron jobs to automatically refresh the trunk every hour:
> 'svn update; cd main; build clean; build'
> and then generate the seed site. That works nicely.
> 
> The result is at forrest.zones.apache.org ... point your browser
> at the /ft/build/ directory (shorthand for forrestbot-trunk).

Superb, thanks David.

> I still need to figure out how to send mail if something fails.
> Thorsten/Antonio: have the Lenya/Cocoon people been able to
> send mail from their zone.

The Daisy install on the Cocoon zone is sending mails. Steven Noels set 
this up, and I believe he documented it somewhere in their zone.

> If other comitters want to look behind-the-scenes:
> ssh forrest.zones.apache.org
> cd /export/home/config
> cat README.txt
> 
> More later ...

Again, thanks David, I hope to dive in there next week.

Thorsten, has there been any progress on a Lenya instance for Doco, I'd 
like to set up an instance of Forrest over there to publish from Lenya 
(actually Daisy in the first instance since that is what I have working, 
but I am hoping this will show the way for a Lenya integration).

Ross

Re: zone for testing forrest

Posted by Thorsten Scherler <th...@apache.org>.

On Thu, 2005-06-30 at 14:15 +1000, David Crossley wrote:
> I have done the next step in setting up some services on our zone.
> 
> There is now a forrestbot running there to build the current "seed site".
> Just the cron side of forrestbot for the moment. The forrestbot web interface
> is the next thing to set up.
> 
> There are cron jobs to automatically refresh the trunk every hour:
> 'svn update; cd main; build clean; build'
> and then generate the seed site. That works nicely.
> 
> The result is at forrest.zones.apache.org ... point your browser
> at the /ft/build/ directory (shorthand for forrestbot-trunk).
> 
> I still need to figure out how to send mail if something fails.
> Thorsten/Antonio: have the Lenya/Cocoon people been able to
> send mail from their zone.
> 

I was in #asfinfra, here the log:
(16:40:43) target-x: hello all
(16:41:12) target-x: Can we send mails from our zones?
(16:41:51) quasi: it needs to be allowed on hermes
(16:43:04) target-x: How can we from lenya and forrest request this
permission?
(16:43:16) target-x: mail to infrastructure list?
(16:43:24) quasi: or a jira issue
(16:43:24) target-x: from pmc head
(16:43:37) target-x: or normal committer which is in the pmc?
(16:44:52) gregor: what do we need it for, target-x?
(16:45:02) quasi: if you send the mail cc to the pmc, then documentation
should be ok 

HTH

> If other comitters want to look behind-the-scenes:
> ssh forrest.zones.apache.org
> cd /export/home/config
> cat README.txt
> 
> More later ...
> 
> -David
-- 
thorsten

"Together we stand, divided we fall!" 
Hey you (Pink Floyd)

Re: zone for testing forrest

Posted by David Crossley <cr...@apache.org>.

I have done the next step in setting up some services on our zone.

There is now a forrestbot running there to build the current "seed site".
Just the cron side of forrestbot for the moment. The forrestbot web interface
is the next thing to set up.

There are cron jobs to automatically refresh the trunk every hour:
'svn update; cd main; build clean; build'
and then generate the seed site. That works nicely.

The result is at forrest.zones.apache.org ... point your browser
at the /ft/build/ directory (shorthand for forrestbot-trunk).

I still need to figure out how to send mail if something fails.
Thorsten/Antonio: have the Lenya/Cocoon people been able to
send mail from their zone.

If other comitters want to look behind-the-scenes:
ssh forrest.zones.apache.org
cd /export/home/config
cat README.txt

More later ...

-David

Re: zone for testing forrest

Posted by Ross Gardler <rg...@apache.org>.

David Crossley wrote:
> Antonio Gallardo wrote:
> 
>>David Crossley dijo:
>>
>>>David Crossley wrote:
>>>
>>>>David Crossley wrote:

...

>>>We would need either Tomcat or Jira so that we can test
>>>our webapp in a servlet container. We also would run the
>>>forrestbot webapp interface there, probably building the
>>>"seed site" and maybe our trunk website.

I would propose Tomcat for the simple reason that it will force us to
test another aspect of Forrest, i.e. the generation of the WAR and
hosting on a different servlet container.

>>>We already have an Apache HTTP Server 2.0 on port 80.
>>>I suppose that we would use ProxyPass etc. to hide the
>>>servlet container.
>>>
>>>How do we make people aware that this is not our production
>>>website? I have already added a robots.txt to keep the
>>>honourable ones out.
>>
>>Perhaps as brutus does. A home page stating: "Beaware: This is only a demo
>>site". Or something like that.
> 
> 
> That is easy for the front page, but each page of content is
> more difficult. For the moment stopping Google from indexing
> is a good start.

Use a different site/project logo?

Add it to the MOTD?

Ross

Re: zone for testing forrest

Posted by David Crossley <cr...@apache.org>.

Antonio Gallardo wrote:
> David Crossley dijo:
> > David Crossley wrote:
> >> David Crossley wrote:
> 
> I saw the link, perhaps we can setup the default profile for all the users
> as stated in the link:
> 
> PATH=/usr/bin:/usr/sfw/bin:/usr/sfw/sbin:/opt/sfw/bin: \
> /opt/sfw/sbin:/opt/SUNWspro/bin:/usr/X/bin:/usr/ucb: \
> /usr/sbin:/usr/ccs/bin:/opt/subversion-1.1.4/bin

Yes that would be good. For the moment i have just added it
to my own ~/.bash_profile

> Also, will be fine to set bash as the default shell for all the users too.
> People using linux will love that. ;-)

Not just Linux people. I would be prefer bash. I have just configured
it as my own default.

> <snip/>
> 
> > So what services do we want to establish?
> 
> Perhaps a distribution of plugins? Is posible to distribute there some
> skins? I still remember our idea that was reject by sourceforge.

This is ASF equipment, so rules about licensing are still the same.

My question was rather about whether to use Tomcat or Jira, etc.
See below.

> Also, I noted we are running in the zone java 1.5_01, perhaps we should
> move to 1.5_03? ;-)

That is a global zone thing. If you want Java updated then
need to ask at infrastructure@ list. It will apply to all zones.

> > We would need either Tomcat or Jira so that we can test
> > our webapp in a servlet container. We also would run the
> > forrestbot webapp interface there, probably building the
> > "seed site" and maybe our trunk website.
> >
> > We already have an Apache HTTP Server 2.0 on port 80.
> > I suppose that we would use ProxyPass etc. to hide the
> > servlet container.
> >
> > How do we make people aware that this is not our production
> > website? I have already added a robots.txt to keep the
> > honourable ones out.
> 
> Perhaps as brutus does. A home page stating: "Beaware: This is only a demo
> site". Or something like that.

That is easy for the front page, but each page of content is
more difficult. For the moment stopping Google from indexing
is a good start.

--David

Re: zone for testing forrest

Posted by Juan Jose Pablos <ch...@apache.org>.

David Crossley wrote:
> We would need either Tomcat or Jira so that we can test
> our webapp in a servlet container. 
Jira ---> jetty

Re: zone for testing forrest

Posted by Antonio Gallardo <ag...@agssa.net>.

On Vie, 27 de Mayo de 2005, 1:03, David Crossley dijo:
> David Crossley wrote:
>> David Crossley wrote:
>> > We have now been allocated a zone on the new server.
>> > So we need to define our goals and then start setting up
>> > some demo servers. We should get out of this RT thread
>> > and start planning. But lets concentrate on the 0.7
>> > release first.
>>
>> What do people think about setting up our zone now?
>>
>> It would actually be a good way to test our upcoming release.
>>
>> I can create an account for any forrest committers.
>
> Okay, accounts are set up for antonio, rgardler, cheche.

Thanks.

> So you need to scp your key to forrest.zones.apache.org
> Then you can ssh in, change your password, and configure
> your account. Any difficulties, then ask on our "dev" list.

> This page will help:
> http://www.apache.org/dev/solaris-zones.html

I saw the link, perhaps we can setup the default profile for all the users
as stated in the link:

PATH=/usr/bin:/usr/sfw/bin:/usr/sfw/sbin:/opt/sfw/bin: \
/opt/sfw/sbin:/opt/SUNWspro/bin:/usr/X/bin:/usr/ucb: \
/usr/sbin:/usr/ccs/bin:/opt/subversion-1.1.4/bin

Also, will be fine to set bash as the default shell for all the users too.
People using linux will love that. ;-)

<snip/>

> So what services do we want to establish?

Perhaps a distribution of plugins? Is posible to distribute there some
skins? I still remember our idea that was reject by sourceforge.

Also, I noted we are running in the zone java 1.5_01, perhaps we should
move to 1.5_03? ;-)

> We would need either Tomcat or Jira so that we can test
> our webapp in a servlet container. We also would run the
> forrestbot webapp interface there, probably building the
> "seed site" and maybe our trunk website.
>
> We already have an Apache HTTP Server 2.0 on port 80.
> I suppose that we would use ProxyPass etc. to hide the
> servlet container.
>
> How do we make people aware that this is not our production
> website? I have already added a robots.txt to keep the
> honourable ones out.

Perhaps as brutus does. A home page stating: "Beaware: This is only a demo
site". Or something like that.

Best Regards,

Antonio Gallardo.

zone for testing forrest

Posted by David Crossley <cr...@apache.org>.

David Crossley wrote:
> David Crossley wrote:
> > We have now been allocated a zone on the new server.
> > So we need to define our goals and then start setting up
> > some demo servers. We should get out of this RT thread
> > and start planning. But lets concentrate on the 0.7
> > release first.
> 
> What do people think about setting up our zone now?
> 
> It would actually be a good way to test our upcoming release.
> 
> I can create an account for any forrest committers.

Okay, accounts are set up for antonio, rgardler, cheche.
When any other committers want one, then ask me.

So you need to scp your key to forrest.zones.apache.org
Then you can ssh in, change your password, and configure
your account. Any difficulties, then ask on our "dev" list.

This page will help:
http://www.apache.org/dev/solaris-zones.html

I have not created any UNIX groups yet. We are all in the
default group "other".

                 -----0-----

Now to start a little planning, so that we can get on
with testing.

I have a forrestbot (just the cron side of it, not the
user interface) running in my home directory to help the
Cocoon people with the generation of their development
documentation for their trunk. Later that will probably move
to the shared zone being proposed on the site-dev mail list
as we don't want to be providing ad-hoc infrastructure services
for other projects (unless it is planned to be so).

So what services do we want to establish?

We would need either Tomcat or Jira so that we can test
our webapp in a servlet container. We also would run the
forrestbot webapp interface there, probably building the
"seed site" and maybe our trunk website.

We already have an Apache HTTP Server 2.0 on port 80.
I suppose that we would use ProxyPass etc. to hide the
servlet container.

How do we make people aware that this is not our production
website? I have already added a robots.txt to keep the
honourable ones out.

--David