1.8. Provision Containers
Provisioning containers
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
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
- 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
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:
Looking up for compute service. Creating 1 nodes on aws-ec2. It may take a while ... Node fabric-72d5f553 has been succesfully created. Installing fabric agent on container mqserver. It may take a while... Overriding resolver to publichostname. [id] [container] [public addresses] [status] us-east-1/i-72d5f553 mqserver [54.81.141.252] success
Create container and deploy profile in two steps
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
- 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
- Deploy the profiles
mq-default
andfabric
into the new container, as follows:Fabric8:admin@registry> fabric:container-change-profile mqserver mq-default fabric
Check the provision status
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