 |
|
26 Feb 2008
Update, release notes and procedure:
H-Sphere 2.5 +:
This update includes the following packages:
Procedure:
- Run HS updater for the latest version of
H-Sphere 2.5
from the directory the updater is located.
sh U25.0P11
- To update
-
All packages to the latest version, execute:
hspackages
- PostgreSQL package to the latest version, execute:
hspackages postgres
Warning: If during the update process you get the message:
WARNING: pg_hba.conf must be configured more strictly.
it means that pg_hba.conf for a given Postgres database should be configured to
restrict IP access to Postgres databases from outside the H-Sphere cluster.
It is especially important to ensure that IP access to the H-Sphere system
database is provided only from CP.
Important: By default, CP PostgreSQL listens on localhost (parameter virtual_host=127.0.0.1
in PostgreSQL config file). To change this, please
customize PostgreSQL
config file template accordingly.
Note: If you want some packages to be skipped during update or only specific package to be updated,
refer to hspackages options.
H-Sphere 3.1 Beta 2:
This update includes the above mentioned packages as for H-Sphere 2.5 and:
Procedure:
- Run HS updater for the latest version of
H-Sphere 3.1
from the directory the updater is located.
sh U31.0b2
- To update
-
All packages to the latest version, execute:
hspackages
- PostgreSQL package to the latest version, execute:
hspackages postgres
Warning: If during the update process you get the message:
WARNING: pg_hba.conf must be configured more strictly.
it means that pg_hba.conf for a given Postgres database should be configured to
restrict IP access to Postgres databases from outside the H-Sphere cluster.
It is especially important to ensure that IP access to the H-Sphere system
database is provided only from CP.
Important: By default, CP PostgreSQL listens on localhost (parameter virtual_host=127.0.0.1
in PostgreSQL config file). To change this, please
customize PostgreSQL
config file template accordingly.
|
 |