Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Gyrex/Administrator Guide/Software Installation"
(New page: == Software Installation == Gyrex supports installation of software into a running cluster. The implementation is based in p2 - the standard for software installation of OSG...) |
|||
| Line 5: | Line 5: | ||
In order to install software, you need to produce a p2 repository containing the artifacts to install. Repositories are the ''source'' of installation. In Gyrex, everything is installed from a repository. However, Gyrex does not know about any repositories by default. Therefore you need to configure the list of available repositories. | In order to install software, you need to produce a p2 repository containing the artifacts to install. Repositories are the ''source'' of installation. In Gyrex, everything is installed from a repository. However, Gyrex does not know about any repositories by default. Therefore you need to configure the list of available repositories. | ||
| − | ==== | + | ==== Adding and Removing Repositories using the Console ==== |
In the OSGi console a <code>sw</code> command is available which allows to perform a basic administration and handling of software installations. | In the OSGi console a <code>sw</code> command is available which allows to perform a basic administration and handling of software installations. | ||
<pre> | <pre> | ||
| − | osgi> help | + | osgi> help sw |
| − | + | ---SoftwareConsoleCommands--- | |
| − | --- | + | |
sw <cmd> [args] | sw <cmd> [args] | ||
| − | + | [...] | |
| − | + | ls repos|packages [filterString] - list repos or packages | |
| − | + | [...] | |
| − | ls | + | addRepo <id> <uri> [filter] - adds a repository |
| − | + | ||
| − | + | ||
rmRepo <id> - removes a repository | rmRepo <id> - removes a repository | ||
| − | + | [...] | |
| − | + | osgi> | |
| − | [...] | + | |
| − | osgi> | + | |
</pre> | </pre> | ||
| + | |||
| + | The <code>addRepo</code> and <code>rmRepo</code> commands should be used to add or remove p2 repositories. | ||
| + | |||
| + | ==== Repository Node Filters ==== | ||
| + | When adding repositories it's possible to specify a node filter. Such a filter can be used to limit the visibility of repositories to certain nodes. This is interesting in a multiple data center scenario when nodes in a specific region should use the repository located within their data center. | ||
| + | |||
| + | Another usage scenario is staging/testing/production repositories. Special "testing" nodes might see a testing repository which may contain newer information. | ||
Revision as of 10:01, 7 February 2013
Contents
Software Installation
Gyrex supports installation of software into a running cluster. The implementation is based in p2 - the standard for software installation of OSGi bundles at Eclipse. Please make yourself familiar with p2 concepts.
Repositories
In order to install software, you need to produce a p2 repository containing the artifacts to install. Repositories are the source of installation. In Gyrex, everything is installed from a repository. However, Gyrex does not know about any repositories by default. Therefore you need to configure the list of available repositories.
Adding and Removing Repositories using the Console
In the OSGi console a sw command is available which allows to perform a basic administration and handling of software installations.
osgi> help sw
---SoftwareConsoleCommands---
sw <cmd> [args]
[...]
ls repos|packages [filterString] - list repos or packages
[...]
addRepo <id> <uri> [filter] - adds a repository
rmRepo <id> - removes a repository
[...]
osgi>
The addRepo and rmRepo commands should be used to add or remove p2 repositories.
Repository Node Filters
When adding repositories it's possible to specify a node filter. Such a filter can be used to limit the visibility of repositories to certain nodes. This is interesting in a multiple data center scenario when nodes in a specific region should use the repository located within their data center.
Another usage scenario is staging/testing/production repositories. Special "testing" nodes might see a testing repository which may contain newer information.