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

RKE 0.16 / Docker 18.06 for ONAP installation - migrate from Rancher for Dublin - script support

    XMLWordPrintable

Details

    • Story
    • Status: Closed
    • Highest
    • Resolution: Duplicate
    • None
    • Dublin Release
    • OOM-Dublin (M3-03/14)

    Description

      https://github.com/rancher/rke

      https://rancher.com/docs/rke/v0.1.x/en/example-yamls/#minimal-cluster-yml-example

      20190225: RKE system up via https://wiki.onap.org/display/DW/OOM+RKE+Kubernetes+Deployment
      and
      OOM-1598
      +) 20190224 test config
      doc in https://wiki.onap.org/display/DW/OOM+RKE+Kubernetes+Deployment

      1. install docker
        curl https://releases.rancher.com/install-docker/17.03.sh | sh
      2. install rke
        sudo wget https://github.com/rancher/rke/releases/download/v0.1.15/rke_linux-amd64
        mv rke_linux-amd64 rke
        sudo mv ./rke /usr/local/bin/rke
      3. copy your private ssh key to the VMs
      4. provision a static EIP/VIP - optionally register a domain name
      5. edit cluster.yaml
      6. run rke up
        sudo rke up --config cluster2.yaml
      7. install kubectl
        https://git.onap.org/logging-analytics/tree/deploy/rancher/oom_rancher_setup.sh#n97
      8. test cluster
      1. RBAC lockdown cluster

       

      Attachments

        Issue Links

          blocks

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. LOG-487 LOG Pipeline Integrity: Docker to Filebeat to Logstash to ElasticSearch to Kibana

          • Highest - Catastrophic defect that causes total failure of the software or unrecoverable data loss with no available workaround. Complete shut-down of the process, nothing can proceed further. Blocks testing of the product / feature. Must be fixed in the next build.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. OOM-1532 kubectl exec/log pod connection problems after x days - k8s 1.12 upgrade candidate

          • High - Severely impaired functionality. Erratic performance and reduced system availability. It may cause major components or features of the system to be unavailable although certain parts of the system remain functional. A workaround may exist but its use is unsatisfactory or at a high time cost (manual intervention required). Must be fixed in any of the upcoming builds and should be included in the current release.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. LOG-380 Platform Maturity: Performance, Stability, Resiliency, Scalability

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. LOG-707 Logging El-Alto (moved from) Dublin Scope

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed
          duplicates

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OOM-1598 Document a Highly-Available K8s Cluster Deployment (RKE 0.2.1 / K8S 1.13.5 / Helm (2.12.3 - not 2.13.1) / Docker 18.09.5)

          • High - Severely impaired functionality. Erratic performance and reduced system availability. It may cause major components or features of the system to be unavailable although certain parts of the system remain functional. A workaround may exist but its use is unsatisfactory or at a high time cost (manual intervention required). Must be fixed in any of the upcoming builds and should be included in the current release.
          • Closed
          is blocked by

          Task - A task that needs to be done. LOG-325 CD: Kubernetes Automated Provisioning Rancher Script - for Ubuntu 16 VMs

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. OOM-1496 Update K8s and Helm for Dublin Release

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed
          relates to

          Task - A task that needs to be done. TSC-25 Task Force to implement CD (Continuous Deployment)

          • High - Severely impaired functionality. Erratic performance and reduced system availability. It may cause major components or features of the system to be unavailable although certain parts of the system remain functional. A workaround may exist but its use is unsatisfactory or at a high time cost (manual intervention required). Must be fixed in any of the upcoming builds and should be included in the current release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OOM-1492 Upgrade Rancher to 1.6.19 with k8s 1.10.5 - to fix kubelet upgrade issue - actually go past 1.6.22 to 1.6.23 to get a jetty CVE fix

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed
          mentioned in

          Page Loading...

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              michaelobrien Michael O'Brien
              michaelobrien Michael O'Brien
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: