Fuse 6 is no longer supported
As of February 2025, Red Hat Fuse 6 is no longer supported. If you are using Fuse 6, please upgrade to Red Hat build of Apache Camel.1.8. Provision Containers
Provisioning containers Copy linkLink copied to clipboard!
Copy linkLink copied to clipboard!
All of the prerequisites are now in place for provisioning Red Hat JBoss Fuse containers in the cloud. After joining your local container to the fabric (which enables you to administer the fabric remotely), you can provision a new container in the cloud by entering a single console command.
Create container and deploy profile in one step Copy linkLink copied to clipboard!
Copy linkLink copied to clipboard!
If you already know what profiles you want to deploy in the new containers, the most efficient approach is to create the compute instances and specify the profiles all in the same command.
For example, to create a new compute instances as part of the current fabric, and to deploy the profiles
mq-default
and fabric
into it, perform the following steps:
- Log on to the Fabric Server on EC2 using the
client
utility:./client -u admin -p admin -h 50.19.18.91
./client -u admin -p admin -h 50.19.18.91
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Enter the following console command:
Fabric8:admin@registry> fabric:container-create-cloud --name aws-ec2 --hardwareId t1.micro --os-family rhel --os-version 6.4 --profile mq-default --profile fabric mqserver
Fabric8:admin@registry> fabric:container-create-cloud --name aws-ec2 --hardwareId t1.micro --os-family rhel --os-version 6.4 --profile mq-default --profile fabric mqserver
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Note how you can deploy multiple profiles, by specifying the--provider
option multiple times.
The preceding
fabric:container-create-cloud
command produces output like the following:
Create container and deploy profile in two steps Copy linkLink copied to clipboard!
Copy linkLink copied to clipboard!
You can create containers and deploy profiles in separate steps, as follows:
- Log on to the Fabric Server on EC2 using the
client
utility:./client -u admin -p admin -h 50.19.18.91
./client -u admin -p admin -h 50.19.18.91
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Create a new Fabric container,
mqserver
, as follows:Fabric8:admin@registry> fabric:container-create-cloud --name aws-ec2 --hardwareId t1.micro --os-family rhel --os-version 6.4 mqserver
Fabric8:admin@registry> fabric:container-create-cloud --name aws-ec2 --hardwareId t1.micro --os-family rhel --os-version 6.4 mqserver
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Deploy the profiles
mq-default
andfabric
into the new container, as follows:Fabric8:admin@registry> fabric:container-change-profile mqserver mq-default fabric
Fabric8:admin@registry> fabric:container-change-profile mqserver mq-default fabric
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Check the provision status Copy linkLink copied to clipboard!
Copy linkLink copied to clipboard!
After creating and deploying, you can test the provision status of the new containers using the
fabric:container-list
command, as follows:
Fabric8:admin@registrygt container-list [id] [version] [connected] [profiles] [provision status] mqserver 1.0 true mq-default, fabric success registry* 1.0 true fabric, fabric-ensemble-0000-1, cloud-aws.ec2 success
Fabric8:admin@registrygt container-list
[id] [version] [connected] [profiles] [provision status]
mqserver 1.0 true mq-default, fabric success
registry* 1.0 true fabric, fabric-ensemble-0000-1, cloud-aws.ec2 success