Details

    • Type: Improvement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
    • Story Points:
      4
    • Sprint:
      Summer 2019 Sprint 12, Fall 2019 Sprint 1, Fall 2019 Sprint 2, Fall 2019 Sprint 3, Fall 4 : 30 Sep to 11 Oct, Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov, Fall 7 : 11 Nov to 22 Nov

      Description

      Set up test EC2 instance for galaxy project using ansible.

        Attachments

          Issue Links

            Activity

            Hide
            aloraine Ann Loraine added a comment -

            Another question:

            It looks like most of what appears in galaxy-ec2-setup repository has come originally from a Galaxy project repository.
            I'm worried that when they fix bugs or otherwise improve that repository, we will not be able to easily get their updates because our bitbucket repository does not appear to be a fork of theirs.
            If this indeed was originally a clone of a Galaxy project repository, can you give the address of that repository in the README?
            If yes, are you able to add their github repository as a remote and then let your new bitbucket repository track and merge their master branch?
            Let's talk!!

            Show
            aloraine Ann Loraine added a comment - Another question: It looks like most of what appears in galaxy-ec2-setup repository has come originally from a Galaxy project repository. I'm worried that when they fix bugs or otherwise improve that repository, we will not be able to easily get their updates because our bitbucket repository does not appear to be a fork of theirs. If this indeed was originally a clone of a Galaxy project repository, can you give the address of that repository in the README? If yes, are you able to add their github repository as a remote and then let your new bitbucket repository track and merge their master branch? Let's talk!!
            Hide
            sameer Sameer Shanbhag (Inactive) added a comment -

            The Files in the role folder get downloaded from the latest code at Ansible Galaxy. I forgot to add that part to the README.md file.
            You need to run "ansible-galaxy install -p roles -r requirements.yml" < this command to get that role folder which has all the automation scripts for the deployment.

            Look at "ansible-galaxy" is a command maintained by Ansible in collaboration with Galaxy and the role files it refers to can be viewed at: https://galaxy.ansible.com/ which is updated regularly.

            I'll make the required changes in the Git Repository and the Readme file regarding ansible-galaxy command.

            Show
            sameer Sameer Shanbhag (Inactive) added a comment - The Files in the role folder get downloaded from the latest code at Ansible Galaxy. I forgot to add that part to the README.md file. You need to run "ansible-galaxy install -p roles -r requirements.yml" < this command to get that role folder which has all the automation scripts for the deployment. Look at "ansible-galaxy" is a command maintained by Ansible in collaboration with Galaxy and the role files it refers to can be viewed at: https://galaxy.ansible.com/ which is updated regularly. I'll make the required changes in the Git Repository and the Readme file regarding ansible-galaxy command.
            Hide
            sameer Sameer Shanbhag (Inactive) added a comment -

            Updated the Git Repository:
            1. Removed Unwanted Files
            2. Updated the README.md file

            Git Repository: https://bitbucket.org/sshanbh1/galaxy-ec2-setup/src/master/

            Show
            sameer Sameer Shanbhag (Inactive) added a comment - Updated the Git Repository: 1. Removed Unwanted Files 2. Updated the README.md file Git Repository: https://bitbucket.org/sshanbh1/galaxy-ec2-setup/src/master/
            Hide
            aloraine Ann Loraine added a comment -

            See https://launch.usegalaxy.org/catalog (top one) for image already packaged.
            Should not need to modify anything for HTTP byte range requests. (using uwsgi)

            Show
            aloraine Ann Loraine added a comment - See https://launch.usegalaxy.org/catalog (top one) for image already packaged. Should not need to modify anything for HTTP byte range requests. (using uwsgi)
            Hide
            aloraine Ann Loraine added a comment -

            see read the docs for API instructions

            Show
            aloraine Ann Loraine added a comment - see read the docs for API instructions

              People

              • Assignee:
                sameer Sameer Shanbhag (Inactive)
                Reporter:
                noor91zahara Noor Zahara
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: