plone: deploy website-editors.gnome.org and update to website-test.gnome.org

[Carsten Senger-3]

Hi all,

new configuration to deploy a development plone site and a permanent
editors instance on socket.gnome.org are ready.

I've updated the deployment README[1].
It's a rather big change for the administrative part. The plone site is now
splitted into two server processes:

  * zope/plone on port 8090 (respectively 8091)
  * deliverance on port 5000 (respectively 5001)

Apache has to rewrite requests to the deliverance server.

website-test.gnome.org
----------------------
The buildout contains an update script for a continous build of the site.
It brings the buildout up to date, drops the current test site and installs
a new one.
This means that with every update of the test site, previews changes are
lost.

website-editors.gnome.org
-------------------------
The editors instance is intended as a editing envirionment for the content
team. It comes with backup scripts:
bin/backup: A full, then incremental backupsbin/backup
bin/restore: restore the last backup made by bin/backup
bin/snapshotbackup: separte, full backups
bin/repozo: the backend script that can be used with command line
parameters.

After running the buildout for website editors for the first time, there
are some manuall steps to do that are not listed in the README. I will add
them later:

 * change the admin password. By default, the user admin has the password
   admin.
   To change that log into the "ZMI": http://<hostname>:8091/manage
   Go to acl_users -> users
   Click on "Password" for the admin and set a new password
 * Log into the Plone Control Panel
   http://website-editors.gnome.org/plone_control_panel as "admin"
 * Adjust the mail settings so mails from the plone site work
 * Remove the automatically created users in the plone site:
   Go to "Users and Groups", click "Show all" and remove all users that are
   not needed by checking the last box "Remove user" and "Apply Changes".
   You can add new users now and reset the password for the remaining
users.
   They will get a Mail to set a new password.

To do maintainance tasks it would be good to add another virtual host that
points to the backend server on port 8091 and is accessible under a
hostname like "zope.website-editors.gnome.org".
website-editors.gnome.org does only expose the Plone frontend, not the
underlying application server management interface (the "ZMI").

..Carsten

[1]
<http://dev.plone.org/collective/browser/gnomeweb-plone/buildout/trunk/README.deployment>

_______________________________________________
gnome-web-list mailing list
gnome-web-list@...
http://mail.gnome.org/mailman/listinfo/gnome-web-list

[Jaap A. Haitsma]

Hi Carsten,

Great work.

The website-editors.gnome.org is not up yet? Is this intentional?

Jaap

BTW are you planning to move the svn plone repo to the GNOME git repo?
Would be handier for other GNOME people to participate in setting up
the site

On Wed, Sep 2, 2009 at 23:47, Carsten Senger<senger@...> wrote:

> Hi all,
>
> new configuration to deploy a development plone site and a permanent
> editors instance on socket.gnome.org are ready.
>
> I've updated the deployment README[1].
> It's a rather big change for the administrative part. The plone site is now
> splitted into two server processes:
>
>  * zope/plone on port 8090 (respectively 8091)
>  * deliverance on port 5000 (respectively 5001)
>
> Apache has to rewrite requests to the deliverance server.
>
> website-test.gnome.org
> ----------------------
> The buildout contains an update script for a continous build of the site.
> It brings the buildout up to date, drops the current test site and installs
> a new one.
> This means that with every update of the test site, previews changes are
> lost.
>
> website-editors.gnome.org
> -------------------------
> The editors instance is intended as a editing envirionment for the content
> team. It comes with backup scripts:
> bin/backup: A full, then incremental backupsbin/backup
> bin/restore: restore the last backup made by bin/backup
> bin/snapshotbackup: separte, full backups
> bin/repozo: the backend script that can be used with command line
> parameters.
>
> After running the buildout for website editors for the first time, there
> are some manuall steps to do that are not listed in the README. I will add
> them later:
>
> * change the admin password. By default, the user admin has the password
>  admin.
>  To change that log into the "ZMI": http://<hostname>:8091/manage
>  Go to acl_users -> users
>  Click on "Password" for the admin and set a new password
> * Log into the Plone Control Panel
>  http://website-editors.gnome.org/plone_control_panel as "admin"
> * Adjust the mail settings so mails from the plone site work
> * Remove the automatically created users in the plone site:
>  Go to "Users and Groups", click "Show all" and remove all users that are
>  not needed by checking the last box "Remove user" and "Apply Changes".
>  You can add new users now and reset the password for the remaining users.
>  They will get a Mail to set a new password.
>
> To do maintainance tasks it would be good to add another virtual host that
> points to the backend server on port 8091 and is accessible under a
> hostname like "zope.website-editors.gnome.org".
> website-editors.gnome.org does only expose the Plone frontend, not the
> underlying application server management interface (the "ZMI").
>
> ..Carsten
>
> [1]
> <http://dev.plone.org/collective/browser/gnomeweb-plone/buildout/trunk/README.deployment>
>
> _______________________________________________
> gnome-web-list mailing list
> gnome-web-list@...
> http://mail.gnome.org/mailman/listinfo/gnome-web-list
>

_______________________________________________
gnome-web-list mailing list
gnome-web-list@...
http://mail.gnome.org/mailman/listinfo/gnome-web-list

[Carsten Senger-3]

Hi Jaap,

--On Sonntag, September 06, 2009 22:32:31 +0200 "Jaap A. Haitsma"
<jaap@...> wrote:

> Hi Carsten,
>
> Great work.
>
> The website-editors.gnome.org is not up yet? Is this intentional?

No, it's not up yet. Alexsandro did a great job setting up the current
website-test on socket.
Alexsandro, can you update the website-test and add a new website-editors
instance?

..Carsten


> BTW are you planning to move the svn plone repo to the GNOME git repo?
> Would be handier for other GNOME people to participate in setting up
> the site

> On Wed, Sep 2, 2009 at 23:47, Carsten Senger<senger@...> wrote:
>> Hi all,
>>
>> new configuration to deploy a development plone site and a permanent
>> editors instance on socket.gnome.org are ready.
>>
>> I've updated the deployment README[1].
>> It's a rather big change for the administrative part. The plone site is
>> now splitted into two server processes:
>>
>>  * zope/plone on port 8090 (respectively 8091)
>>  * deliverance on port 5000 (respectively 5001)
>>
>> Apache has to rewrite requests to the deliverance server.
>>
>> website-test.gnome.org
>> ----------------------
>> The buildout contains an update script for a continous build of the site.
>> It brings the buildout up to date, drops the current test site and
>> installs a new one.
>> This means that with every update of the test site, previews changes are
>> lost.
>>
>> website-editors.gnome.org
>> -------------------------
>> The editors instance is intended as a editing envirionment for the
>> content team. It comes with backup scripts:
>> bin/backup: A full, then incremental backupsbin/backup
>> bin/restore: restore the last backup made by bin/backup
>> bin/snapshotbackup: separte, full backups
>> bin/repozo: the backend script that can be used with command line
>> parameters.
>>
>> After running the buildout for website editors for the first time, there
>> are some manuall steps to do that are not listed in the README. I will
>> add them later:
>>
>> * change the admin password. By default, the user admin has the password
>>  admin.
>>  To change that log into the "ZMI": http://<hostname>:8091/manage
>>  Go to acl_users -> users
>>  Click on "Password" for the admin and set a new password
>> * Log into the Plone Control Panel
>>  http://website-editors.gnome.org/plone_control_panel as "admin"
>> * Adjust the mail settings so mails from the plone site work
>> * Remove the automatically created users in the plone site:
>>  Go to "Users and Groups", click "Show all" and remove all users that
>> are  not needed by checking the last box "Remove user" and "Apply
>> Changes".  You can add new users now and reset the password for the
>> remaining users.  They will get a Mail to set a new password.
>>
>> To do maintainance tasks it would be good to add another virtual host
>> that points to the backend server on port 8091 and is accessible under a
>> hostname like "zope.website-editors.gnome.org".
>> website-editors.gnome.org does only expose the Plone frontend, not the
>> underlying application server management interface (the "ZMI").
>>
>> ..Carsten
>>
>> [1]
>> <http://dev.plone.org/collective/browser/gnomeweb-plone/buildout/trunk/R
>> EADME.deployment>
>>
>> _______________________________________________
>> gnome-web-list mailing list
>> gnome-web-list@...
>> http://mail.gnome.org/mailman/listinfo/gnome-web-list
>>

_______________________________________________
gnome-web-list mailing list
gnome-web-list@...
http://mail.gnome.org/mailman/listinfo/gnome-web-list

[Carsten Senger-3]

Hi Jaap,
hi infrastructure team,

--On Dienstag, September 08, 2009 12:36:35 +0200 Carsten Senger
<senger@...> wrote:

> Hi Jaap,
>
> --On Sonntag, September 06, 2009 22:32:31 +0200 "Jaap A. Haitsma"
> <jaap@...> wrote:
>
>> Hi Carsten,
>>
>> Great work.
>>
>> The website-editors.gnome.org is not up yet? Is this intentional?
>
> No, it's not up yet. Alexsandro did a great job setting up the current
> website-test on socket.
> Alexsandro, can you update the website-test and add a new website-editors
> instance?

Unfortunately I had no luck contacting Alexandro. Can someone from the
infrastructure team help to update website-test.g.o and install
website-editors.g.o on socket?

..Carsten
_______________________________________________
gnome-web-list mailing list
gnome-web-list@...
http://mail.gnome.org/mailman/listinfo/gnome-web-list

[Alexandro Silva]

Hi all,

Caster and all my apologies but I'm too busy working on some projects.
I will work on website-test and website-editors this weekend and I give
everything ready by Sunday.

Sorry and Cheers

Alexandro Silva
http://blog.alexos.com.br






Carsten Senger wrote:

> Hi Jaap,
> hi infrastructure team,
>
> --On Dienstag, September 08, 2009 12:36:35 +0200 Carsten Senger
> <senger@...> wrote:
>
>> Hi Jaap,
>>
>> --On Sonntag, September 06, 2009 22:32:31 +0200 "Jaap A. Haitsma"
>> <jaap@...> wrote:
>>
>>> Hi Carsten,
>>>
>>> Great work.
>>>
>>> The website-editors.gnome.org is not up yet? Is this intentional?
>>
>> No, it's not up yet. Alexsandro did a great job setting up the current
>> website-test on socket.
>> Alexsandro, can you update the website-test and add a new website-editors
>> instance?
>
> Unfortunately I had no luck contacting Alexandro. Can someone from the
> infrastructure team help to update website-test.g.o and install
> website-editors.g.o on socket?
>
> ..Carsten
> _______________________________________________
> gnome-infrastructure mailing list
> gnome-infrastructure@...
> http://mail.gnome.org/mailman/listinfo/gnome-infrastructure

_______________________________________________
gnome-web-list mailing list
gnome-web-list@...
http://mail.gnome.org/mailman/listinfo/gnome-web-list

[Carsten Senger-3]

Hi Alexandro,

--On Mittwoch, September 23, 2009 16:27:38 -0300 Alexandro Silva
<penguim@...> wrote:

> Hi all,
>
> Caster and all my apologies but I'm too busy working on some projects.
> I will work on website-test and website-editors this weekend and I give
> everything ready by Sunday.

Thanks for your quick reqly. If you've too much to do and no time I can
always happily bug some other infrastructure team member :). Anyway I try
to drop in on irc saturday/sunday sometime between morning and afternoon
your time.

Cheers,

..Carsten


_______________________________________________
gnome-web-list mailing list
gnome-web-list@...
http://mail.gnome.org/mailman/listinfo/gnome-web-list

[Christopher Warner-2]

Nice.. Alexandro if you need me to do anything or need anything please let me know as i'm pretty idle over the next two weeks.

Thanks,

-C

On Wed, Sep 23, 2009 at 5:02 PM, Carsten Senger <senger@...> wrote:

Hi Alexandro,

--On Mittwoch, September 23, 2009 16:27:38 -0300 Alexandro Silva <penguim@...> wrote:

Hi all,

Caster and all my apologies but I'm too busy working on some projects.
I will work on website-test and website-editors this weekend and I give
everything ready by Sunday.

Thanks for your quick reqly. If you've too much to do and no time I can always happily bug some other infrastructure team member :). Anyway I try to drop in on irc saturday/sunday sometime between morning and afternoon your time.

Cheers,

..Carsten


_______________________________________________
gnome-web-list mailing list
gnome-web-list@...
http://mail.gnome.org/mailman/listinfo/gnome-web-list

_______________________________________________
gnome-web-list mailing list
gnome-web-list@...
http://mail.gnome.org/mailman/listinfo/gnome-web-list

[Alexandro Silva]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Carsten,
       
I started setting up website-editors. I am following your README but
when you run the steps below an error has been shown:

alexos@socket:/srv/wgoplone/development/wgo-buildout$ bin/buildout -c
../editors/deploy-editors.cfg

Creating directory '/srv/wgoplone/development/editors/parts'.
While:
  Installing.
  Setting up buildout directories

An internal error occured due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
  File
"/tmp/tmpNhKtmp/zc.buildout-1.2.1-py2.4.egg/zc/buildout/buildout.py",
line 1509, in main
  File
"/tmp/tmpNhKtmp/zc.buildout-1.2.1-py2.4.egg/zc/buildout/buildout.py",
line 315, in install
  File
"/tmp/tmpNhKtmp/zc.buildout-1.2.1-py2.4.egg/zc/buildout/buildout.py",
line 545, in _setup_directories
OSError: [Errno 13] Permission denied:
'/srv/wgoplone/development/editors/parts'
alexos@socket:/srv/wgoplone/development/wgo-buildout$ sudo bin/buildout
- -c ../editors/deploy-editors.cfg
Creating directory '/srv/wgoplone/development/editors/parts'.
Creating directory '/srv/wgoplone/development/editors/eggs'.
Creating directory '/srv/wgoplone/development/editors/develop-eggs'.
Getting distribution for 'infrae.subversion>=1.4'.
zip_safe flag not set; analyzing archive contents...
infrae.subversion.tests.test_impl: module references __file__
Got infrae.subversion 1.4.5.
Getting distribution for 'py'.
warning: no files found matching 'CHANGELOG'
warning: no files found matching 'LICENSE'
warning: no previously-included files found matching '*.orig'
warning: no previously-included files found matching '*.rej'
no previously-included directories found matching '.svn'
no previously-included directories found matching '.hg'
Got py 1.0.2.
Getting distribution for 'plone.recipe.zope2install==3.0'.
Got plone.recipe.zope2install 3.0.
Getting distribution for 'plone.recipe.zope2instance==3.2'.
Got plone.recipe.zope2instance 3.2.
Getting distribution for 'zc.recipe.egg==1.2.2'.
Got zc.recipe.egg 1.2.2.
Getting distribution for 'z3c.recipe.staticlxml'.
Got z3c.recipe.staticlxml 0.7.1.
Getting distribution for 'zc.recipe.cmmi'.
Got zc.recipe.cmmi 1.3.1.
While:
  Installing.
  Getting section lxml.
  Initializing section lxml.
  Installing recipe z3c.recipe.staticlxml.
Error: There is a version conflict.
We already have: zc.buildout 1.2.1
but zc.recipe.cmmi 1.3.1 requires 'zc.buildout>=1.4'.

Can you help me please?

Cheers

Alexandro



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkq+qFgACgkQWp/oJ20l6yRdZACeMB6xAq8Ll6kkHZae4FnPuynB
8HMAoK06DkNrSyf88BbywdSW1qyyXnBp
=ntAK
-----END PGP SIGNATURE-----
_______________________________________________
gnome-web-list mailing list
gnome-web-list@...
http://mail.gnome.org/mailman/listinfo/gnome-web-list

[Carsten Senger-3]

Hi Alexandro,

--On Samstag, September 26, 2009 20:48:44 -0300 Alexandro Silva
<penguim@...> wrote:

> I started setting up website-editors. I am following your README but
> when you run the steps below an error has been shown:
>
> alexos@socket:/srv/wgoplone/development/wgo-buildout$ bin/buildout -c
> ../editors/deploy-editors.cfg

[...]

> Got zc.recipe.cmmi 1.3.1.
> While:
>   Installing.
>   Getting section lxml.
>   Initializing section lxml.
>   Installing recipe z3c.recipe.staticlxml.
> Error: There is a version conflict.
> We already have: zc.buildout 1.2.1
> but zc.recipe.cmmi 1.3.1 requires 'zc.buildout>=1.4'.

The z.c buildout version that is used is 1.2.1, but 1.4+ is needed.
Buildout is probably installed into the python environment you use,
otherwise a new version of zc.buildout would have been downloaded.

Please do the following:

* call bootstrap.py with the python we need. That will probably be
  `python2.4 bootstrap.py`
* try `bin/buildout -c deploy-editors.cfg` again.

If it fails post the content of bin/buildout.
It extends the sys.path variable of python with buildout-specific packages,
which are normally setuptools and buildout:

># !/srv/zope/instances/gnome/../../_appserver/python-2.4/bin/python
>
> import sys
> sys.path[0:0] = [
>   '/srv/zope/instances/gnome/eggs/setuptools-0.6c9-py2.4.egg',
>   '/srv/zope/instances/gnome/eggs/zc.buildout-1.4.1-py2.4.egg',
>   ]
>
> import zc.buildout.buildout
>
> if __name__ == '__main__':
>     zc.buildout.buildout.main()

If either of these are missing they are already installed in the python
installation and used from there. It is better to at least not have
zc.buildout installed in the systems python so it can be installed in a
current version by bootstrap.

Then you need to
* either update them in the python installation:
 `easy_install-2.4 -U zc.buildout` or `easy_install -U zc.buildout`
* or better remove zc.buildout from the system's python installation
  maybe in /lib/python/dist-packages/zc.buildout

If its not working post the contents of bin/buildout and the output of
bin/buildout -vvvv -c deploy-editors.cfg

Cheers,

..Carsten

_______________________________________________
gnome-web-list mailing list
gnome-web-list@...
http://mail.gnome.org/mailman/listinfo/gnome-web-list

[Alexandro Silva-2]

Hi Carsten,

Really didn't work. I see a way to generate a file with the errors and I
forward to you.

Cheers

Alexandro Silva
http://blog.alexos.com.br


Carsten Senger wrote:

> Hi Alexandro,
>
> --On Samstag, September 26, 2009 20:48:44 -0300 Alexandro Silva
> <penguim@...> wrote:
>
>> I started setting up website-editors. I am following your README but
>> when you run the steps below an error has been shown:
>>
>> alexos@socket:/srv/wgoplone/development/wgo-buildout$ bin/buildout -c
>> ../editors/deploy-editors.cfg
>
> [...]
>
>> Got zc.recipe.cmmi 1.3.1.
>> While:
>>   Installing.
>>   Getting section lxml.
>>   Initializing section lxml.
>>   Installing recipe z3c.recipe.staticlxml.
>> Error: There is a version conflict.
>> We already have: zc.buildout 1.2.1
>> but zc.recipe.cmmi 1.3.1 requires 'zc.buildout>=1.4'.
>
> The z.c buildout version that is used is 1.2.1, but 1.4+ is needed.
> Buildout is probably installed into the python environment you use,
> otherwise a new version of zc.buildout would have been downloaded.
>
> Please do the following:
>
> * call bootstrap.py with the python we need. That will probably be
>  `python2.4 bootstrap.py`
> * try `bin/buildout -c deploy-editors.cfg` again.
>
> If it fails post the content of bin/buildout.
> It extends the sys.path variable of python with buildout-specific packages,
> which are normally setuptools and buildout:
>
>
>> # !/srv/zope/instances/gnome/../../_appserver/python-2.4/bin/python
>>
>> import sys
>> sys.path[0:0] = [
>>   '/srv/zope/instances/gnome/eggs/setuptools-0.6c9-py2.4.egg',
>>   '/srv/zope/instances/gnome/eggs/zc.buildout-1.4.1-py2.4.egg',
>>   ]
>>
>> import zc.buildout.buildout
>>
>> if __name__ == '__main__':
>>     zc.buildout.buildout.main()
>
> If either of these are missing they are already installed in the python
> installation and used from there. It is better to at least not have
> zc.buildout installed in the systems python so it can be installed in a
> current version by bootstrap.
>
> Then you need to
> * either update them in the python installation:
> `easy_install-2.4 -U zc.buildout` or `easy_install -U zc.buildout`
> * or better remove zc.buildout from the system's python installation
>  maybe in /lib/python/dist-packages/zc.buildout
>
> If its not working post the contents of bin/buildout and the output of
> bin/buildout -vvvv -c deploy-editors.cfg
>
> Cheers,
>
> ..Carsten
>

_______________________________________________
gnome-web-list mailing list
gnome-web-list@...
http://mail.gnome.org/mailman/listinfo/gnome-web-list

[Carsten Senger-3]

Hi Alexandro,

--On Donnerstag, Oktober 01, 2009 11:17:21 -0300 Alexandro Silva
<penguim@...> wrote:

> Hi Carsten,
>
> Really didn't work. I see a way to generate a file with the errors and I
> forward to you.

Yes, that's good. When you have time we can meet on IRC to sort all
problems out at once.

..Carsten

> Cheers
>
> Alexandro Silva
> http://blog.alexos.com.br
>
>
> Carsten Senger wrote:
>> Hi Alexandro,
>>
>> --On Samstag, September 26, 2009 20:48:44 -0300 Alexandro Silva
>> <penguim@...> wrote:
>>
>>> I started setting up website-editors. I am following your README but
>>> when you run the steps below an error has been shown:
>>>
>>> alexos@socket:/srv/wgoplone/development/wgo-buildout$ bin/buildout -c
>>> ../editors/deploy-editors.cfg
>>
>> [...]
>>
>>> Got zc.recipe.cmmi 1.3.1.
>>> While:
>>>   Installing.
>>>   Getting section lxml.
>>>   Initializing section lxml.
>>>   Installing recipe z3c.recipe.staticlxml.
>>> Error: There is a version conflict.
>>> We already have: zc.buildout 1.2.1
>>> but zc.recipe.cmmi 1.3.1 requires 'zc.buildout>=1.4'.
>>
>> The z.c buildout version that is used is 1.2.1, but 1.4+ is needed.
>> Buildout is probably installed into the python environment you use,
>> otherwise a new version of zc.buildout would have been downloaded.
>>
>> Please do the following:
>>
>> * call bootstrap.py with the python we need. That will probably be
>>  `python2.4 bootstrap.py`
>> * try `bin/buildout -c deploy-editors.cfg` again.
>>
>> If it fails post the content of bin/buildout.
>> It extends the sys.path variable of python with buildout-specific
>> packages, which are normally setuptools and buildout:
>>
>>
>>> # !/srv/zope/instances/gnome/../../_appserver/python-2.4/bin/python
>>>
>>> import sys
>>> sys.path[0:0] = [
>>>   '/srv/zope/instances/gnome/eggs/setuptools-0.6c9-py2.4.egg',
>>>   '/srv/zope/instances/gnome/eggs/zc.buildout-1.4.1-py2.4.egg',
>>>   ]
>>>
>>> import zc.buildout.buildout
>>>
>>> if __name__ == '__main__':
>>>     zc.buildout.buildout.main()
>>
>> If either of these are missing they are already installed in the python
>> installation and used from there. It is better to at least not have
>> zc.buildout installed in the systems python so it can be installed in a
>> current version by bootstrap.
>>
>> Then you need to
>> * either update them in the python installation:
>> `easy_install-2.4 -U zc.buildout` or `easy_install -U zc.buildout`
>> * or better remove zc.buildout from the system's python installation
>>  maybe in /lib/python/dist-packages/zc.buildout
>>
>> If its not working post the contents of bin/buildout and the output of
>> bin/buildout -vvvv -c deploy-editors.cfg
>>
>> Cheers,
>>
>> ..Carsten
>>
>

_______________________________________________
gnome-web-list mailing list
gnome-web-list@...
http://mail.gnome.org/mailman/listinfo/gnome-web-list