Databases
StackOverflow2013
Postsdbo
PODistributed OSGi - what is the proper way to manage bundles across all containers?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODistributed OSGi - what is the proper way to manage bundles across all containers?
    primarykey
    data
    text
    <p>We are considering utilizing distributed OSGi in our enterprise environment.<br/> We would have the following setup:</p> <ul> <li>10 to 100 OSGi containers on many hosts offer various services.</li> <li>Many of these services are provided by more than one container.</li> <li>Some of these services may require being consistent across all containers (same version deployed).</li> </ul> <p>What is the proper way to manage bundles' lifecycle (install, start, update, stop, uninstall) across all containers?</p> <p>Several requirements:</p> <ul> <li>As there may be so many containers, all of them should be handled together; i.e. when I am about to update a bundle, a single command should update all containers where that bundle already present.</li> <li>Commands must be repeatable: first perform a command on test systems, and then repeat the exact same command on production system once testing is complete.</li> </ul> <p>I appreciate any suggestion regarding the above question.</p> <p>Best regards, Marton</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USMarton Sigmond
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODistributed OSGi - what is the proper way to manage bundles across all containers?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODistributed OSGi - what is the proper way to manage bundles across all containers?
      1. USDanail Nachev
      1. VTFavorite
    3. VO
      singulars
      1. PODistributed OSGi - what is the proper way to manage bundles across all containers?
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODo all these OSGi containers build one big distributed OSGi container where service A on host X can use service B on host Y just like it would be on the same host X? or are they separated to each other and you have just 10-100 OSGi containers you want to maintain? and are they all the same like 10-100 OSGi containers having all exactly the same bundles and you want to send a command (like "install") to all these OSGi containers at the same time? Or are they different that host X have an OSGi container with N bundles and the OSGi container on host Y have a different set of bundles?
      singulars
      1. PODistributed OSGi - what is the proper way to manage bundles across all containers?
      1. USProgman
    2. COThis is one big distributed OSGi environment: service A on host X can use service B on host Y. Each container may have a different set of bundles. Thanks!
      singulars
      1. PODistributed OSGi - what is the proper way to manage bundles across all containers?
      1. USMarton Sigmond
    3. COI would try to build such system using Apache Karaf (because it provides easy way to automate commands and easy management of bundles) . I'll set it up with a shared bundle store, so whenever I update a bundle, all runtimes will pick it up. Karaf is designed to support executing commands from scripts, so it shouldn't be hard to write the required scripts, which will manage the system. However, you won't get distributed transaction. At some point of time, there would be versions mismatch and I don't think that there is a solution to this currently.
      singulars
      1. PODistributed OSGi - what is the proper way to manage bundles across all containers?
      1. USDanail Nachev
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload