Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Attachments

        Activity

        Hide
        sjagarap saideepthi jagarapu added a comment -

        Before upgrade hub-facade uses python <=3.10, django==3.2.3

        Upgraded to python 3.13, django 4.2.10, other dependencies upgraded based on these versions.

        Branch changes:
        https://bitbucket.org/lorainelab-deepthi/hub-facade/branch/IGBF-4326

        Show
        sjagarap saideepthi jagarapu added a comment - Before upgrade hub-facade uses python <=3.10, django==3.2.3 Upgraded to python 3.13, django 4.2.10, other dependencies upgraded based on these versions. Branch changes: https://bitbucket.org/lorainelab-deepthi/hub-facade/branch/IGBF-4326
        Hide
        sjagarap saideepthi jagarapu added a comment -

        I have run ansible-playbook and tested the branch IGBF-4326 using EC2 instance created by Ann Loraine at this url https://dev2025.bioviz.org/
        the functionality works as expected.

        Attaching relevant succesful screenshots after running the command
        This command basically runs the playbook (tasks in setup.yml) on the servers listed in inventory.ini (dev2025 in this case)
        ansible-playbook -i inventory.ini setup.yml

        Show
        sjagarap saideepthi jagarapu added a comment - I have run ansible-playbook and tested the branch IGBF-4326 using EC2 instance created by Ann Loraine at this url https://dev2025.bioviz.org/ the functionality works as expected. Attaching relevant succesful screenshots after running the command This command basically runs the playbook (tasks in setup.yml) on the servers listed in inventory.ini (dev2025 in this case) ansible-playbook -i inventory.ini setup.yml
        Hide
        uchinta Udaya Chinta (Inactive) added a comment -

        The libraries have newer versions available, but after discussing with Deepthi, the current upgraded versions are considered the most stable for Python 3.13.
        Hence moving the ticket to PR.

        Show
        uchinta Udaya Chinta (Inactive) added a comment - The libraries have newer versions available, but after discussing with Deepthi, the current upgraded versions are considered the most stable for Python 3.13. Hence moving the ticket to PR.
        Hide
        uchinta Udaya Chinta (Inactive) added a comment -

        Currently all the libraries are upgraded but I think python version needs to be upgraded in server.
        Cc : saideepthi jagarapu

        Show
        uchinta Udaya Chinta (Inactive) added a comment - Currently all the libraries are upgraded but I think python version needs to be upgraded in server. Cc : saideepthi jagarapu
        Hide
        ann.loraine Ann Loraine added a comment - - edited

        saideepthi jagarapu I have a doubt about the upgrade.

        On the host (dev2025) there is a file named "requirements.txt" which I believe is the list of versions of libraries and dependencies that will be deployed to the host when we run deploy using ansible.

        The "requirements.txt" file that is current is listing versions that don't match what is listed above. Here is what is in the file "requirements.txt":

        ubuntu $ more requirements.txt 
        asgiref==3.3.4
        certifi==2021.5.30
        chardet==4.0.0
        Django==3.2.3
        django-cors-headers==3.10.0
        idna==2.10
        python-decouple==3.1
        pytz==2021.1
        requests==2.25.1
        sqlparse==0.4.1
        urllib3==1.26.6
        

        I think this is because the branch that is deployed on the testing host is actually branch "main".

        To truly test the deployment of upgraded libraries, we need to deploy your new branch (IGBF-4326) on the testing host.

        You can do this by configured the inventory.ini file, I believe. Using the inventory.ini file, I think you can specify both the branch you want to deploy (for testing) and the repository (your fork).

        Can you take a look and re-run the playbooks using your repository and your development branch (IGBF-4326) to deploy your new code onto the testing host dev2025.bioviz.org.

        Show
        ann.loraine Ann Loraine added a comment - - edited saideepthi jagarapu I have a doubt about the upgrade. On the host (dev2025) there is a file named "requirements.txt" which I believe is the list of versions of libraries and dependencies that will be deployed to the host when we run deploy using ansible. The "requirements.txt" file that is current is listing versions that don't match what is listed above. Here is what is in the file "requirements.txt": ubuntu $ more requirements.txt asgiref==3.3.4 certifi==2021.5.30 chardet==4.0.0 Django==3.2.3 django-cors-headers==3.10.0 idna==2.10 python-decouple==3.1 pytz==2021.1 requests==2.25.1 sqlparse==0.4.1 urllib3==1.26.6 I think this is because the branch that is deployed on the testing host is actually branch "main". To truly test the deployment of upgraded libraries, we need to deploy your new branch ( IGBF-4326 ) on the testing host. You can do this by configured the inventory.ini file, I believe. Using the inventory.ini file, I think you can specify both the branch you want to deploy (for testing) and the repository (your fork). Can you take a look and re-run the playbooks using your repository and your development branch ( IGBF-4326 ) to deploy your new code onto the testing host dev2025.bioviz.org.
        Hide
        sjagarap saideepthi jagarapu added a comment -

        Sure Ann Loraine, I will deploy the developed branch with my fork and re-run the playbooks now.

        Show
        sjagarap saideepthi jagarapu added a comment - Sure Ann Loraine , I will deploy the developed branch with my fork and re-run the playbooks now.
        Hide
        sjagarap saideepthi jagarapu added a comment - - edited

        Ann Loraine I have doubt here, this is the inventory.ini file

        [hub_facade_hosts]
        # this is what we're using for the production site (commented out)
        # translate2 ansible_host=3.209.223.181 domain=translate.bioviz.org secret_key=dkasdkhjwns igb_repository=https://bitbucket.org/lorainelab/integrated-genome-browser/ igb_branch=main quickload_contents_txt=https://data.bioviz.org/quickload/contents.txt stack=Prod
        
        # this is your test / development host target (for Deepthi)
        dev2025 ansible_host=34.225.101.234 domain=dev2025.bioviz.org secret_key=dldlalkdselcekd igb_repository=https://bitbucket.org/lorainelab-deepthi/integrated-genome-browser/ igb_branch=main quickload_contents_txt=https://data.bioviz.org/quickload/contents.txt stack=Develop
        
        [hub_facade_hosts:vars]
        ansible_ssh_common_args="-o StrictHostKeyChecking=no"
        ansible_ssh_user=ubuntu
        
        

        Here igb_branch and repo is related to igb not hub-facade
        So, do you think i should update the igb_branch to IGBF-4326 because this is developed branch in hub-facade not igb.

        Show
        sjagarap saideepthi jagarapu added a comment - - edited Ann Loraine I have doubt here, this is the inventory.ini file [hub_facade_hosts] # this is what we're using for the production site (commented out) # translate2 ansible_host=3.209.223.181 domain=translate.bioviz.org secret_key=dkasdkhjwns igb_repository=https: //bitbucket.org/lorainelab/integrated-genome-browser/ igb_branch=main quickload_contents_txt=https://data.bioviz.org/quickload/contents.txt stack=Prod # this is your test / development host target ( for Deepthi) dev2025 ansible_host=34.225.101.234 domain=dev2025.bioviz.org secret_key=dldlalkdselcekd igb_repository=https: //bitbucket.org/lorainelab-deepthi/integrated-genome-browser/ igb_branch=main quickload_contents_txt=https://data.bioviz.org/quickload/contents.txt stack=Develop [hub_facade_hosts:vars] ansible_ssh_common_args= "-o StrictHostKeyChecking=no" ansible_ssh_user=ubuntu Here igb_branch and repo is related to igb not hub-facade So, do you think i should update the igb_branch to IGBF-4326 because this is developed branch in hub-facade not igb.
        Hide
        sjagarap saideepthi jagarapu added a comment - - edited

        Update Ann Loraine Nowlan Freese
        I made changes to setup_vars.yml to make use of my repo fork and branch.
        Updated setup_vars.yml looks like this

        ---
        ### Variables needed to run setup.yml ###
        
        #
        # Hub facade code repository and branch to deploy
        #
        repo: https://bitbucket.org/lorainelab-deepthi/hub-facade.git
        branch: IGBF-4326
        
        #
        # Certificates for supporting https. Place in files directory.
        #
        #ssl_cert_file:
        #ssl_cert_key_file:
        #ssl_chain_file:
        
        ssl_cert_file: 2025.star.bioviz.org.crt
        ssl_cert_key_file: 2025.star.bioviz.org.key
        ssl_chain_file: 2025.star.bioviz.org.ca-bundle
        
        #
        # Web apps deploy directory
        #
        app_dir: /var/www/vhosts
        ...
        
        

        I have tested the dev deployment with these changes by deploying udaya's trackhub changes as I couldn't see any visible UI change with 4326 dependency upgrade to figure out if the branch is deployed to dev or not.

        Now, I have test new changes in dev after deploying IGBF-4326 changes, and everything works as expected.

        Show
        sjagarap saideepthi jagarapu added a comment - - edited Update Ann Loraine Nowlan Freese I made changes to setup_vars.yml to make use of my repo fork and branch. Updated setup_vars.yml looks like this --- ### Variables needed to run setup.yml ### # # Hub facade code repository and branch to deploy # repo: https: //bitbucket.org/lorainelab-deepthi/hub-facade.git branch: IGBF-4326 # # Certificates for supporting https. Place in files directory. # #ssl_cert_file: #ssl_cert_key_file: #ssl_chain_file: ssl_cert_file: 2025.star.bioviz.org.crt ssl_cert_key_file: 2025.star.bioviz.org.key ssl_chain_file: 2025.star.bioviz.org.ca-bundle # # Web apps deploy directory # app_dir: / var /www/vhosts ... I have tested the dev deployment with these changes by deploying udaya's trackhub changes as I couldn't see any visible UI change with 4326 dependency upgrade to figure out if the branch is deployed to dev or not. Now, I have test new changes in dev after deploying IGBF-4326 changes, and everything works as expected.
        Show
        sjagarap saideepthi jagarapu added a comment - PR https://bitbucket.org/lorainelab/hub-facade/pull-requests/53
        Hide
        ann.loraine Ann Loraine added a comment -

        PR is merged.

        Show
        ann.loraine Ann Loraine added a comment - PR is merged.
        Hide
        uchinta Udaya Chinta (Inactive) added a comment -

        Tested the changes. Everything is working as expected.

        Show
        uchinta Udaya Chinta (Inactive) added a comment - Tested the changes. Everything is working as expected.

          People

          • Assignee:
            sjagarap saideepthi jagarapu
            Reporter:
            ann.loraine Ann Loraine
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: