• Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      The documentation should be enrich with more precise explaination on different scenario to cover which is far from clear.

      • For instance it is not really clear if a cluster node(2 containers need to run exact same version of Jira as before or note
      • Upgrade process is not clear also on how to do, a step by step process as explain in previous datacenter document should be describe for saving time and error prone
      • How to handle custom file configuration should be better describe and explain in detail on how to process to update it.
            For exemple the dbconfig.xml is configured with default value in the image but in case we have an already configured database how can we update this file and push it to the install docker image

      Thanks for that

       

            [SCALE-5] Docker image process installation documentation

            yes

            serge calderara added a comment - yes

            Hi 0b69573696ac, does the explanation from Don helped you? Would you be ok if we close this ticket?

            Thanks,

            Carlos 

            Carlos Corredor added a comment - Hi  0b69573696ac , does the explanation from Don helped you? Would you be ok if we close this ticket? Thanks, Carlos 

            ddomingo added a comment -

            Hi 0b69573696ac, hope this helps:

            How to handle custom file configuration should be better describe and explain in detail on how to process to update it.
                For exemple the dbconfig.xml is configured with default value in the image but in case we have an already configured database how can we update this file and push it to the install docker image

            We post all documentation relating to each Atlassian product's Docker image is in its respective dockerhub repo:

            https://hub.docker.com/r/atlassian/jira-core

            https://hub.docker.com/r/atlassian/jira-software

            https://hub.docker.com/r/atlassian/jira-servicedesk

            https://hub.docker.com/r/atlassian/confluence-server/

            https://hub.docker.com/r/atlassian/bitbucket-server/

            Each repo page contains information on which environment variables you can set to customize your deployment. In your case, the Database configuration section on each page lists the variables you'd need to set the same info in your dbconfig.xml.

            Upgrade process is not clear also on how to do, a step by step process as explain in previous datacenter document should be describe for saving time and error prone

            Each page also features an Upgrades section that covers this briefly. Basically, you stop the product container (jira, confluence, or bitbucket), remove it, and then relaunch it with the new version. The process is consistent with the way you normally destroy/re-create containers in Docker. 

            For instance it is not really clear if a cluster node(2 containers need to run exact same version of Jira as before or note

            Yes, all node clusters need to run the exact same version of a product.

             

             

             

            ddomingo added a comment - Hi 0b69573696ac , hope this helps: How to handle custom file configuration should be better describe and explain in detail on how to process to update it.     For exemple the dbconfig.xml is configured with default value in the image but in case we have an already configured database how can we update this file and push it to the install docker image We post all documentation relating to each Atlassian product's Docker image is in its respective dockerhub repo: https://hub.docker.com/r/atlassian/jira-core https://hub.docker.com/r/atlassian/jira-software https://hub.docker.com/r/atlassian/jira-servicedesk https://hub.docker.com/r/atlassian/confluence-server/ https://hub.docker.com/r/atlassian/bitbucket-server/ Each repo page contains information on which environment variables you can set to customize your deployment. In your case, the  Database configuration  section on each page lists the variables you'd need to set the same info in your dbconfig.xml . Upgrade process is not clear also on how to do, a step by step process as explain in previous datacenter document should be describe for saving time and error prone Each page also features an Upgrades section that covers this briefly. Basically, you stop the product container ( jira , confluence , or bitbucket ), remove it, and then relaunch it with the new version. The process is consistent with the way you normally destroy/re-create containers in Docker.  For instance it is not really clear if a cluster node(2 containers need to run exact same version of Jira as before or note Yes, all node clusters need to run the exact same version of a product.      

              Unassigned Unassigned
              0b69573696ac serge calderara
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: