Re: [Framework-Team] Testing for PLIP 209: Unified Installer Plus Buildout

[Tom Lazar]

On 18.02.2008, at 00:20, Steve McMahon wrote:


Tom,

The obvious just occurred to me: I'll be you're trying this from an
SVN checkout.


obvious to you (well, and everybody else, so it seems...)

you see, that tidbit isn't mentioned in the README that's part of the  
svn nor at the actual plip[1], although the latter does refer to a  
tarball in the deliverables section and once more in the progress log.


i guess it's simply due to the fact that prior to this plip review i  
have never used any of the unified installers and hence probably just  
missed that it's all about the tarball.



The svn does not include all the many megabytes of
third-party tarballs required to run the installer. (Wiggy has very
reasonably requested that they be kept out of svn.)

So, to test the new UN+BO, you'll need to download it from Launchpad:

https://launchpad.net/plone/3.0/3.0.5/+download/Plone-3.0.5-UnifiedInstallerBuildout-beta2.tar.gz


i downloaded this and everything worked fine from then on. i created a  
zeo setup with its own python and libjpeg(!). this is great stuff. i  
shall be using this for my own client work from now on, as the  
buildouts i have so far used were very nice for the client but still  
needed to be accompanied by a lengthy README as how to install the  
dependencies.


beyond this particular installation i haven't done any further  
testing, but as mentioned, others have done that already, so all i can  
say is: +1 ;-)





(BTW, I expect to be doing a version for Plone 3.0.6 early next week.
It will include the fix for the relative path issue discovered by
Raphael.)

Steve

On 2/17/08, Steve McMahon [EMAIL PROTECTED] wrote:

Hi Tom,

I'm at a loss as to what's not working here. That message should only
show up if the helper_scripts or packages directories aren't present
or aren't searchable. I wonder if we've got an odd variety of sh or
some extra ACL permissions at work. What's your platform?

By the way, the same component execution code is in the existing
(non-buildout) installer. So there's a good chance that it also
wouldn't work for you.

Steve

On 2/17/08, Tom Lazar [EMAIL PROTECTED] wrote:

hi graham, thanks for the hint, however, i had tried that already
myself and it didn't work, either.

sudo sh ./install.sh --target=/opt/zope/instances/209 -- 
user=tomster --

instance=plip209 zeo
ZEO Cluster Install selected


This install script must be run within the installer's top  
directory.

That directory should contain packages and helper_scripts
subdirectories.

so, for me the plip is not functional and i can't give it a +1 in  
this

state. i'm sure it's just something trivial, but the point is that
it's supposed to be *easy* for the end user lateron, and they will
likely stumble over the same issues.

tom

On Feb 16, 2008, at 3:54 PM, Graham Perrin wrote:


On 16 Feb 2008, at 11:55, Tom Lazar wrote:


sudo sh install.sh --target=/opt/zope/instances/209 --user=tomster
--instance=plip209 zeo


Where you have

sudo sh install.sh

should that be,

sudo sh ./install.sh

This install script must be run within the installer's top  
directory.


I received that message once, when I tried specifying the path
from my working directory
to install.sh

Regards
Graham







--

__

Steve McMahon
Reid-McMahon, LLC
[EMAIL PROTECTED]
[EMAIL PROTECTED]




--

__

Steve McMahon
Reid-McMahon, LLC
[EMAIL PROTECTED]
[EMAIL PROTECTED]




___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team

Re: [Framework-Team] Testing for PLIP 209: Unified Installer Plus Buildout

[Tom Lazar]

hi graham, thanks for the hint, however, i had tried that already  
myself and it didn't work, either.


sudo sh ./install.sh --target=/opt/zope/instances/209 --user=tomster -- 
instance=plip209 zeo

ZEO Cluster Install selected


This install script must be run within the installer's top directory.
That directory should contain packages and helper_scripts  
subdirectories.


so, for me the plip is not functional and i can't give it a +1 in this  
state. i'm sure it's just something trivial, but the point is that  
it's supposed to be *easy* for the end user lateron, and they will  
likely stumble over the same issues.


tom

On Feb 16, 2008, at 3:54 PM, Graham Perrin wrote:


On 16 Feb 2008, at 11:55, Tom Lazar wrote:

sudo sh install.sh --target=/opt/zope/instances/209 --user=tomster  
--instance=plip209 zeo


Where you have

sudo sh install.sh

should that be,

sudo sh ./install.sh


This install script must be run within the installer's top directory.


I received that message once, when I tried specifying the path
from my working directory
to install.sh

Regards
Graham




___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team

Re: [Framework-Team] Testing for PLIP 209: Unified Installer Plus Buildout

[Steve McMahon]

Hi Tom,

I'm at a loss as to what's not working here. That message should only
show up if the helper_scripts or packages directories aren't present
or aren't searchable. I wonder if we've got an odd variety of sh or
some extra ACL permissions at work. What's your platform?

By the way, the same component execution code is in the existing
(non-buildout) installer. So there's a good chance that it also
wouldn't work for you.

Steve

On 2/17/08, Tom Lazar [EMAIL PROTECTED] wrote:
 hi graham, thanks for the hint, however, i had tried that already
 myself and it didn't work, either.

 sudo sh ./install.sh --target=/opt/zope/instances/209 --user=tomster --
 instance=plip209 zeo
 ZEO Cluster Install selected


 This install script must be run within the installer's top directory.
 That directory should contain packages and helper_scripts
 subdirectories.

 so, for me the plip is not functional and i can't give it a +1 in this
 state. i'm sure it's just something trivial, but the point is that
 it's supposed to be *easy* for the end user lateron, and they will
 likely stumble over the same issues.

 tom

 On Feb 16, 2008, at 3:54 PM, Graham Perrin wrote:

  On 16 Feb 2008, at 11:55, Tom Lazar wrote:
 
  sudo sh install.sh --target=/opt/zope/instances/209 --user=tomster
  --instance=plip209 zeo
 
  Where you have
 
  sudo sh install.sh
 
  should that be,
 
  sudo sh ./install.sh
 
  This install script must be run within the installer's top directory.
 
  I received that message once, when I tried specifying the path
  from my working directory
  to install.sh
 
  Regards
  Graham
 




-- 

__

Steve McMahon
Reid-McMahon, LLC
[EMAIL PROTECTED]
[EMAIL PROTECTED]

___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team

Re: [Framework-Team] Testing for PLIP 209: Unified Installer Plus Buildout

[Raphael Ritz]

Tom Lazar wrote:
i just realized, that steve might not get notifications from trac, so 
i hereby post my previous comment:




Hi,


after checking out :



checking out what? As Steve said, you should download the tarball.


and issueing the following command:

sudo sh install.sh --target=/opt/zope/instances/209 --user=tomster 
--instance=plip209 zeo

i get the following output:



I just tried this on my box (Linux/Ubuntu 7.10) and it just worked.
With other words: I cannot reproduce the issue you are seeing.

Raphael


ZEO Cluster Install selected Detailed installation log being written 
to /opt/zope/instances/plip209installer/install.log This install 
script must be run within the installer's top directory. That 
directory should contain packages and helper_scripts subdirectories.
however, i am issuing that command from within the toplevel directory. 
the log file is empty except for these two lines:


Detailed installation log Starting at Fr 15 Feb 2008 16:17:24 CET
since nobody else (i.e. martijn and raphael) has reported this, i 
either have found some bug (unlikely) or (more likely) other folks 
will overlook the same thing I overlooked... ;-)


either way something (probably the README) would need to be clarified.



On Feb 16, 2008, at 12:26 AM, Steve McMahon wrote:


On 2/14/08, Raphael Ritz [EMAIL PROTECTED] wrote:

...
(ii) maybe I screwed it up myself but I couldn't specify a
relative path when specifying the target as follows:


Thanks! Fixed in svn.

__

Steve McMahon
Reid-McMahon, LLC
[EMAIL PROTECTED]
[EMAIL PROTECTED]

___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team






___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team

Re: [Framework-Team] Testing for PLIP 209: Unified Installer Plus Buildout

[Tom Lazar]

i just realized, that steve might not get notifications from trac, so  
i hereby post my previous comment:


after checking out :

and issueing the following command:

sudo sh install.sh --target=/opt/zope/instances/209 --user=tomster -- 
instance=plip209 zeo

i get the following output:

ZEO Cluster Install selected Detailed installation log being written  
to /opt/zope/instances/plip209installer/install.log This install  
script must be run within the installer's top directory. That  
directory should contain packages and helper_scripts subdirectories.
however, i am issuing that command from within the toplevel directory.  
the log file is empty except for these two lines:


Detailed installation log Starting at Fr 15 Feb 2008 16:17:24 CET
since nobody else (i.e. martijn and raphael) has reported this, i  
either have found some bug (unlikely) or (more likely) other folks  
will overlook the same thing I overlooked... ;-)


either way something (probably the README) would need to be clarified.



On Feb 16, 2008, at 12:26 AM, Steve McMahon wrote:


On 2/14/08, Raphael Ritz [EMAIL PROTECTED] wrote:

...
(ii) maybe I screwed it up myself but I couldn't specify a
relative path when specifying the target as follows:


Thanks! Fixed in svn.

__

Steve McMahon
Reid-McMahon, LLC
[EMAIL PROTECTED]
[EMAIL PROTECTED]

___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team




___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team

Re: [Framework-Team] Testing for PLIP 209: Unified Installer Plus Buildout

[Raphael Ritz]

Steve McMahon wrote:

Thanks for the great review and suggestions, Martijn!

I'm pleased to report that the PID problem is taken care of. Nouri
fixed it for zope2instance in:

http://dev.plone.org/collective/changeset/55898

and for zope2zeoserver in:

http://dev.plone.org/collective/changeset/55899

The other CLIENT_HOME problems are messier than they should be, but
should be taken care of by the

command =
...
find ${buildout:directory} -type d -name var -exec chown -R
${client1:effective-user} \{\} \;

section of buildout.cfg that's inserted for root-mode installs.

  


Excellent news. Almost +1 on all of this from me as well
but (there's always a but, isn't it ;-) there is one issue
I currently consider a show-stopper (sorry, but it should
be easy to fix as you'll see):

When going to the 'prefs_install_products_form' of a
Plone site it says:

To make new products show up here, put them in the directory
*/tmp/test_PloneUI/Plone-3.0.5-UnifiedInstallerBuildout/zinstance/parts/instance/Products* 


on the file system, and restart the server process.

The problem here is that we point people to *parts/instance/Products*
which is plain wrong! Update your buildout and your add-ons will be 
gone. :-(

This should rather point to zinstance/products instead.

Apart from that I've only two suggestions for eventually
improving the already excellent documentation:

(i) when describing start/stop/status we might want to add
'fg' (foreground) as a simple means to start in debug mode
without changing the configuration

(ii) maybe I screwed it up myself but I couldn't specify a
relative path when specifying the target as follows:

[EMAIL PROTECTED]:/tmp/test_PloneUI/Plone-3.0.5-UnifiedInstallerBuildout$ 
./install.sh --target=. standalone

Stand-Alone Zope Instance selected

Detailed installation log being written to 
/tmp/test_PloneUI/Plone-3.0.5-UnifiedInstallerBuildout/install.log


Rootless install method chosen. Will install for use by system user ritz
zlib installation: no
libjpeg installation: no

Installing Plone 3.0.5 + Buildout at .

Skipping zlib compile and install
Skipping libjpeg compile/install
Installing Python 2.4.4. This takes a while...
Install of Python 2.4.4 has failed.

Installation has failed.
See the detailed installation log at 
/tmp/test_PloneUI/Plone-3.0.5-UnifiedInstallerBuildout/install.log

to determine the cause.

(end of transcript)

Specifying an absolute path, however, worked like a brise.
Should there be a issue hidden here this could be fixed
or mentioned.

Anyway, this is all excellent work. I'm all for adopting
it as soon as possible (although I consider this quite
a drastic change for a x.1 release). But please fix the
wrong pointer in the 'prefs_install_products_form'.

Cheers,

   Raphael



Ideally, though, we should work towards a setup where the server and
client processes never write into parts.

Thanks, Steve


On 2/10/08, Martijn Pieters [EMAIL PROTECTED] wrote:
  

On Jan 17, 2008 2:00 AM, Steve McMahon [EMAIL PROTECTED] wrote:


An implementation of PLIP 209: Unified Installer Plus Buildout is
available for testing at:

https://launchpad.net/plone/3.0/3.0.5/+download/Plone-3.0.5-UnifiedInstallerBuildout-beta1.tar.gz
  

You have since created a beta2:

  
https://launchpad.net/plone/3.0/3.0.5/+download/Plone-3.0.5-UnifiedInstallerBuildout-beta2.tar.gz

:-)

As there is no review bundle possible for this, I'll give my review
notes in this reply:

I tested the full download and tested the different installation
options on both Mac OS X and Linux (Debian Etch). Everything worked
absolutely beautifully. In short, my verdict can be summed up as
'absolutely ruddy brilliant!'. I am very impressed with the execution
and the polish on the buildout-version of the unified installer, and
I'll certainly be reusing the precompile recipe in production
buildouts.

One remark about the as-root install using the effective user setup.
There is a problem with that setup which lies outside of the scope of
the Unified Installer, but which will perhaps come up in support
requests. Currently, zope2instance sets CLIENT_HOME as
$INSTANCE_HOME/var, which means on that this variable points to a
subdirectory of the part directory (usually parts/instance). This
means that this directory will get wiped and re-created when updating
the buildout settings for that recipe.

That wouldn't be so big a problem if it weren't for the fact that
various things get written to the CLIENT_HOME, such as the zopectl
daemon PID (at least at some point, it may be that Florian Schulze has
fixed that one). Any files written there are of course written by the
effective user, meaning that a buildout update can perhaps not delete
these files, and/or that the effective user cannot write in the
directory afterwards.

The solution is to create subdirectories of the buildout var/
directory (where filestorage and log live) for each Zope client and
for a zeo server, and setting these directories as the 

Re: [Framework-Team] Testing for PLIP 209: Unified Installer Plus Buildout

[Steve McMahon]

Thanks for the great review and suggestions, Martijn!

I'm pleased to report that the PID problem is taken care of. Nouri
fixed it for zope2instance in:

http://dev.plone.org/collective/changeset/55898

and for zope2zeoserver in:

http://dev.plone.org/collective/changeset/55899

The other CLIENT_HOME problems are messier than they should be, but
should be taken care of by the

command =
...
find ${buildout:directory} -type d -name var -exec chown -R
${client1:effective-user} \{\} \;

section of buildout.cfg that's inserted for root-mode installs.

Ideally, though, we should work towards a setup where the server and
client processes never write into parts.

Thanks, Steve


On 2/10/08, Martijn Pieters [EMAIL PROTECTED] wrote:
 On Jan 17, 2008 2:00 AM, Steve McMahon [EMAIL PROTECTED] wrote:
  An implementation of PLIP 209: Unified Installer Plus Buildout is
  available for testing at:
 
  https://launchpad.net/plone/3.0/3.0.5/+download/Plone-3.0.5-UnifiedInstallerBuildout-beta1.tar.gz

 You have since created a beta2:

   
 https://launchpad.net/plone/3.0/3.0.5/+download/Plone-3.0.5-UnifiedInstallerBuildout-beta2.tar.gz

 :-)

 As there is no review bundle possible for this, I'll give my review
 notes in this reply:

 I tested the full download and tested the different installation
 options on both Mac OS X and Linux (Debian Etch). Everything worked
 absolutely beautifully. In short, my verdict can be summed up as
 'absolutely ruddy brilliant!'. I am very impressed with the execution
 and the polish on the buildout-version of the unified installer, and
 I'll certainly be reusing the precompile recipe in production
 buildouts.

 One remark about the as-root install using the effective user setup.
 There is a problem with that setup which lies outside of the scope of
 the Unified Installer, but which will perhaps come up in support
 requests. Currently, zope2instance sets CLIENT_HOME as
 $INSTANCE_HOME/var, which means on that this variable points to a
 subdirectory of the part directory (usually parts/instance). This
 means that this directory will get wiped and re-created when updating
 the buildout settings for that recipe.

 That wouldn't be so big a problem if it weren't for the fact that
 various things get written to the CLIENT_HOME, such as the zopectl
 daemon PID (at least at some point, it may be that Florian Schulze has
 fixed that one). Any files written there are of course written by the
 effective user, meaning that a buildout update can perhaps not delete
 these files, and/or that the effective user cannot write in the
 directory afterwards.

 The solution is to create subdirectories of the buildout var/
 directory (where filestorage and log live) for each Zope client and
 for a zeo server, and setting these directories as the CLIENT_HOME for
 each Zope instance. This is something that needs to be fixed in
 zope2instance. Once that's done, PlacelessTranslationService has to be
 fixed to use CLIENT_HOME instead of INSTANCE_HOME/var to write it's
 translation files, as it does currently.

 So, in summary, this PLIP has my big thumbs up. Just be aware of
 potential problems around the instance home part and the effective
 user due to a misconfigured CLIENT_HOME.

 --
 Martijn Pieters



-- 

__

Steve McMahon
Reid-McMahon, LLC
[EMAIL PROTECTED]
[EMAIL PROTECTED]

___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team