4 Replies Latest reply on Jan 31, 2015 10:24 PM by emanuelebaldassarre

    could not find export button on redhat fuse 6.1 profile

    rvashishth

      I have start evaluating the new feature of redhat fuse 6.1, newly released. Its all amazing, but as of now one thing i couldnt find is the export button to export the profiles.

      This is a must have thing for me.

        • 1. Re: could not find export button on redhat fuse 6.1 profile
          davsclaus

          The profiles are now stored in the embedded git repository. So you can clone the git repo to get all the profiles exported.

           

          In the fabric runtime page, you can click on the root container, and then on the profile page, there is a URLs tab that list the git url. There is a copy to clipboard button you can click, and then use that to clone the git repo.

          • 2. Re: could not find export button on redhat fuse 6.1 profile
            rvashishth

            I understand the cloning of git repository for profiles. But is it okay to install a git just for fabric profiles, and second thing again i couldnt find a way to import profiles also.

            • 3. Re: could not find export button on redhat fuse 6.1 profile
              davsclaus

              The git comes out of the box in JBoss Fuse 6.1 onwards. And as its a just a regular git repo, you can import by adding and committing files to it. And use any of the standard git tools to do so.

              • 4. Re: could not find export button on redhat fuse 6.1 profile
                emanuelebaldassarre

                I understand that each container in a fabric has its git and git instances are kept aligned. this means that at each change to a profile all the git datastores are aligned and while running a karaf script to change several profiles this generates a big overhead since all the containers need to be aligned at each operation. My ask is: is there a way to change the ZK /fabric/registry/clusters/git and keep only the rootcontainers aligned having all the child/ssh containers to refer to the root containers ? I imagine that with 100 profiles and 100 containers each change has a big overhead on the whole system, preventing large scalability. Let me know if I missed something. thanks.