Fuse Fabric
Projects

This page contains all the frequently asked questions about the Fuse Fabric project.

General Questions

General questions on the Fabric project.

What is the license?

This software is completely open source under the Apache 2.0 license.

How do I get support?

See the support guide for more details.

How do I build it?

First get the source then see the building guide

How do I contribute or become a committer?

We love contributions! More details on how to contribute and how to become a committer are in the contributing guide.

How do I register for the issue tracker?

For more detail see the support page.

How does the website work?

For details on how to edit the website and how it works see How the Site works

Using Fabric

Why should I use Fabric?

To help provision, configure and manage a number of machines or a public or private cloud of Apache Karaf, Apache ServiceMix or Fuse installations.

How do I get started?

Try the Getting Started Guide which should get you started nice and quick!

I can't connect to the fabric registry right after I join a container to it.

When using the fabric:join command, the container that joins the cluster uses the name of the container (karaf.name) system property. Currently, it is to the responsibilty of the user to prevent name clashes. Such name clashes can have unpredictable side effects and one of them can be, to not being able to connect to the registry. To modify the (karaf.name) property you can edit the etc/system.properties file under the home of the karaf container.

Why do I get timeout errors, when adding containers to the ensemble.

There can be a lot of reasons, the most popular of which are:

Where does the fabric-agent download artifacts from?

Profiles can define a list of maven repositories which can be used by the fabric agent in order to download maven artifacts. The default list of repositories is defined as part of the default profile. The list of repositories can be modified or overridden by modifying the org.fusesource.fabric.agent pid of the default or any other profile respectively.

  fabric:profile-edit --pid org.fusesource.fabric.agent/org.ops4j.pax.url.mvn.repositories=http://username:password@repohostname myprofile

Please note, that the command above will replace the list of repositories. If you need to add one, then you'll need to specify the existing repositories as a comma separated list.

Before reaching any of the repositories defined in the profile, fabric will lookup the runtime registry and find any fabric-maven-proxy running in the cluster. It will first lookup the maven proxy and then fallback to the repositories, if the maven proxy can't find the artifact.

How do I add additional remote maven repositories to the fabric-maven-proxy?

There are a lot of cases where a user needs to add additional maven repositories to the fabric-maven-proxy. A common case is adding a nexus repository. To add additional repositories to the fabric-maven-proxy just add them inside the org.fusesource.fabric.maven pid.

Adding a repository to the fabric-maven-proxy:

  config:propappend --pid org.fusesource.fabric.maven remoteRepositories ,http://username:password@repohostname myprofile

Replacing the remote repository list of to the fabric-maven-proxy:

  config:propset --pid org.fusesource.fabric.maven remoteRepositories http://username:password@repohostname myprofile