7 Replies Latest reply on May 30, 2014 3:14 AM by Krzysztof Sobkowiak

    Installing ec2 profile in fabric

    Krzysztof Sobkowiak Newbie

      Hi

       

      I have created a fabric in Fuse 6.1.0 and next tried to add ec2 profile to the root container. After the command is finished the fabric commands does not exist anymore for very long time

       

      JBossFuse:karaf@root> fabric:create --zookeeper-password admin --wait-for-provisioning

      Waiting for container: root

      Waiting for container root to provision.

      Using specified zookeeper password:admin

      JBossFuse:karaf@root>

      JBossFuse:karaf@root>

      JBossFuse:karaf@root> container-list

      [id]                           [version] [connected] [profiles]                                         [provision status]

      root*                          1.0       true        fabric, fabric-ensemble-0000-1, jboss-fuse-full    success

      JBossFuse:karaf@root> fabric:container-add-profile root cloud-aws.ec2 

      JBossFuse:karaf@root> container-list

      [id]                           [version] [connected] [profiles]                                         [provision status]

      root*                          1.0       true        fabric, fabric-ensemble-0000-1, jboss-fuse-full, cloud-aws.ec2 resolving

      JBossFuse:karaf@root> container-list

      Command not found: container-list

      JBossFuse:karaf@root> container-list

      Command not found: container-list

      JBossFuse:karaf@root> container-list

      .......

      JBossFuse:karaf@root> container-list

      [id]                           [version] [connected] [profiles]                                         [provision status]

      root*                          1.0       true        fabric, fabric-ensemble-0000-1, jboss-fuse-full, cloud-aws.ec2 success

      JBossFuse:karaf@root>

       

      The impatient user can be confused and think something is wrong with the fabric. Is this behavior ok? I have only accidentally realized the container has been provisioned because I haven"t shut down the "failed" container for a long time (some minutes)

       

       

      Best regards

      Krzysztof