Uploaded image for project: 'Logging analytics'
  1. Logging analytics
  2. LOG-510

AWS CD system should apply AMIs to switch to deploy per run instead of deploy/undeploy

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Won't Do
    • Icon: Medium Medium
    • Frankfurt Release
    • None

      A continuous system is not really working because tearing down onap still leaves hanging artifacts.
      To be clean either deploy a new system for each CD run or use pre-saved AMI's
      Flow

      • spot request for master.onap.info using json template for saved ami
      • spot request for 9 master0-8.onap.info using json template for saved ami
      • register A record on onap.info
      • copy and run rancher agent on all the client vms
      ubuntu@ip-172-31-1-119:~$ sudo scp -i shared_aws_cd_onap_201801.pem logging-analytics/deploy/aws/oom_cluster_host_install.sh  ubuntu@master0.onap.info:~/
      oom_cluster_host_install.sh                                                                                                                  100% 4440     4.3KB/s   00:00    
      # run remote
      ubuntu@ip-172-31-1-119:~$ sudo ssh -i shared_aws_cd_onap_201801.pem ubuntu@master1.onap.info './oom_cluster_host_install.sh -n true -s master.onap.info -e fs-...26 -r us-east-2 -t CD96.......mUK6t8M -h 1.2.10 -v true'
      
      

            pau2882 pau2882
            michaelobrien michaelobrien
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: