This is an internal documentation. There is a good chance you’re looking for something else. See Disclaimer.

Delete Tocco Installation

Delete Installation at Nine

Clean Up App Server

  1. Remove the installation from ~tocco/manager/etc/manager.xml.

  2. Reload config with mgrctl restart.

  3. Remove configuration from /etc/nginx/sites-enabled/*.conf and reload nginx (nginx -s reload)

  4. Remove Let’s Encrypt certificate configuration on app03 at /etc/letsencrypt/renewal/*.conf

  5. Remove installation directory

    On app server:

    rm -rf ~/nice2/${INSTALLATION}/
    

Everything Else

  1. Remove monitoring (StatusCake).

  2. Remove DNS (https://cockpit.nine.ch).

    Username/password in secrets2.yml.

  3. Remove the project of installation in Teamcity.

  4. Update status on the installation to “veraltet” in the Tocco BackOffice.

  5. Set the customer module that is linked to the installation to “Obsolete” if all associated installations are obsolete.

    TQL finding all customers with only obsolete installations:

    relModule_status.unique_id != "outdated"
      and relModule_type.unique_id == "customer_module"
      and exists(relInstallation)
      and not exists(relInstallation where relInstallation_status.unique_id != "obsolete")
    
  6. Delete the customer’s Maven module from the Nice2 Git repository (if there are no other installations that require the Customer module)

  7. Remove Solr index

    Only required when solr_server is set in config.yml.

    Obtain password to access Solr:

    cd ${ANSIBLE_GIT_REPO}/tocco
    ansible-vault view secrets2.yml |grep solr
    

    On solr server (e.g. solr2.tocco.cust.vshn.net):

    curl 'https://localhost:8983/solr/admin/cores?action=UNLOAD&deleteInstanceDir=true&core=nice-${INSTALLATION}' --insecure -u tocco -p
  8. Drop databases:

    Warning

    Consider waiting a few days before removing the databases to ensure the final states of the databases have been backed up.

    DROP DATABASE nice2_${INSTALLATION};
    DROP DATABASE nice2_${INSTALLATION}_history;
    
  9. Remove S3 bucket

    Warning

    Consider waiting a few days before removing the S3 bucket to ensure the final state of the S3 bucket has been backed up.

    Only do this if there is no other installation left for the customer. Buckets are shared among all installations of a customer.

    s3cmd rm -rf s3://tocco-nice-${CUSTOMER}
    s3cmd rb s3://tocco-nice-${CUSTOMER}
    

Delete Installation at VSHN

See Remove Installation/Customer