v0.3.0-RC3

fix(install): changed pull policy and upgrade strategy (#200)

Changed `ImagePullPolicy` to `IfNotPresent`. Earlier, during integration testing the old image from docker-hub was pulled which overwrite the newly built images. This resulted in integration tests being performed on the old image and also the old image was re-tagged and pushed. With the change, only the newly built image will be used.

The update strategy of Daemonset is now set to RollingUpdate, so that the new image will be applied without manual deletion.

Signed-off-by: Akhil Mohan <[email protected]>

v0.3.0-RC2

fix(install): changed pull policy and upgrade strategy (#200)

Changed `ImagePullPolicy` to `IfNotPresent`. Earlier, during integration testing the old image from docker-hub was pulled which overwrite the newly built images. This resulted in integration tests being performed on the old image and also the old image was re-tagged and pushed. With the change, only the newly built image will be used.

The update strategy of Daemonset is now set to RollingUpdate, so that the new image will be applied without manual deletion.

Signed-off-by: Akhil Mohan <[email protected]>

v0.3.0

• feat(install): enable core dump in node-disk-manager (#181)
• feat(probe): add seachest probe to get additional disk details (#185)
• feat(diskCR): add partition and filesystem info (#197)
• feat(diskCR): add support for unmanaged disk (#192)
• fix(install): change DS update policy to RollingUpdate (#200)
• fix(probe): avoid ndm restart when run in unprivileged mode (#198)
• fix(build): broken Makefile rule "vet" to do "go vet" (#182)
• test(filter): add integration test for path filter (#172)
• style(controller): fix lint error in sparsefilegenerator.go file #97 (#142)
• refactor(test): remove ineffectual assignments in udev_test.go (#167)

v0.3.0-RC1

[US4264] feat(diskCR): add partition and filesystem info

added partition and filesystem info to DiskCR. If partitions are present on
the disk, the partition type and filesystem information will be stored onto
the diskCR. If the whole disk is formatted with a filesystem, that info will
also be included

The change will give the following output when a partitioned disk is described
   ...
       links:
       - /dev/disk/by-path/pci-0000:00:03.0-scsi-0:0:3:0
     partitionDetails:
     - fileSystemType: None
       partitionType: "0x83"
     - fileSystemType: None
       partitionType: "0x8e"
     path: /dev/sdb
   stats:
   ...

If the disk is formatted as a whole with a filesystem
   ...
       links:
       - /dev/disk/by-path/pci-0000:00:03.0-scsi-0:0:5:0
     fileSystem: ext4
     path: /dev/sdb
   stats:
   ...

Signed-off-by: Akhil Mohan <[email protected]>

v0.2.0-RC2

feat(build): push docker images to quay repo (#165)

Refactor the code to push the images to the quay repo. The same script
used to push the images from other openebs repo is used.

Signed-off-by: kmova <[email protected]>

v0.2.0

feat(build): push docker images to quay repo (#165)

Refactor the code to push the images to the quay repo. The same script
used to push the images from other openebs repo is used.

Signed-off-by: kmova <[email protected]>

v0.2.0-RC1

Fix readDeviceCapacity method (#147)

`readDeviceCapacity` used to send only a SCSI READ CAPACITY(10) command.
If this reports an overflow, issue an additional READ CAPACITY(16)
command to get the correct device capacity.

Signed-off-by: Michael Kaiser <[email protected]>

v0.1.0

Getting Started

Prerequisite to install

• Kubernetes 1.9.7+ is installed
• Make sure you run the following kubectl command with cluster admin context. The installation will involve create a new Service Account assigned to NDM for managing the Disk CRD
• NDM pods run with privileged context that require access to the /dev, if you are running on CentOS - verify that selinux is off or the pods are granted sufficient privileges.

Install and Setup

wget https://raw.githubusercontent.com/openebs/node-disk-manager/v0.1.0/ndm-operator.yaml

#Customize the operator as per your cluster requirements. For example
#update the filter configuration with device types patters that you want excluded from discovering. 
#update DaemonSet with nodeSelector information to limit NDM to specific nodes
#update namespace - installed in `default` by default. 

kubectl apply -f ndm-operator.yaml

For more details, refer to User guide.

Supported Features

• Discover devices attached to node and add them as Disk CR.
• Support for filters to exclude some disks from being added like OS Disk, Loopback devices, etc.,
• Dynamically detect disk addition/removal
• Identify if the Disk (like GPD) has moved from one node to another.

Detailed CHANGELOG is maintained here.

v0.1.0-RC3

Add contributor guides with initial setup info (#70)


Signed-off-by: kmova <[email protected]>

v0.1.0-RC2

Merge pull request #68 from kmova/sparse-disk-provisioner

Include support for creating sparse file