Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-22433

Properties: Add Storage tab

    XMLWordPrintable

Details

    Description

      We should be able to display Persistent Volume (aka Storage) informations in the OpenShift properties.

      Need to define the extent of the informations to display. At the very least, it should be the same as what the OpenShift Console provides.

      Using persistent volumes:

      1. https://blog.openshift.com/experimenting-with-persistent-volumes/
      2. https://docs.openshift.com/enterprise/3.0/dev_guide/persistent_volumes.html

      Briefly: to see how persistent volume claims work, add the following json as a resource to the project:

      Persistent Volume Claim Object Definition
      {
    "apiVersion": "v1",
    "kind": "PersistentVolumeClaim",
    "metadata": {
        "name": "claim1"
    },
    "spec": {
        "accessModes": [ "ReadWriteOnce" ],
        "resources": {
            "requests": {
                "storage": "1Gi"
            }
        }
    }
}

      Attachments

        Issue Links

          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-22727 Openshift resources managed by explorer and watcher are declared in both place leading to inconsistency

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open
          relates to

          Feature Request - Feature requests from customers and/or users OSJC-266 PVC: add information about the volume the claim is bounded to

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Activity

            People

              dbocharo@redhat.com Dmitrii Bocharov (Inactive)
              fbricon@redhat.com Fred Bricon
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: