Skip to content

Commit

Permalink
Merge pull request #1189 from kokhang/update-pending-releasenotes
Browse files Browse the repository at this point in the history
Update pending release notes
  • Loading branch information
bassam committed Nov 8, 2017
2 parents 0ceddcf + 9179d04 commit 116f088
Show file tree
Hide file tree
Showing 2 changed files with 39 additions and 8 deletions.
3 changes: 2 additions & 1 deletion Documentation/k8s-filesystem.md
Original file line number Diff line number Diff line change
Expand Up @@ -117,7 +117,8 @@ spec:

You now have a docker registry which is HA with persistent storage.

**NOTE:** If the Rook cluster has more than one filesystem and the application pod is scheduled to a node with kernel version older than 4.7, inconsistent results may arise since kernels older than 4.7 do not support specifying filesystem namespaces.
#### Kernel Version Requirement
If the Rook cluster has more than one filesystem and the application pod is scheduled to a node with kernel version older than 4.7, inconsistent results may arise since kernels older than 4.7 do not support specifying filesystem namespaces.

## Test the storage

Expand Down
44 changes: 37 additions & 7 deletions PendingReleaseNotes.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,18 +2,30 @@

## Action Required

## Known Issues

## Deprecations

## Notable Features

- Rook Flexvolume
- Introduces a new Rook plugin based on [Flexvolume](https://github.com/kubernetes/community/blob/master/contributors/devel/flexvolume.md)
- Integrates with Kubernetes' Volume Controller framework
- Handles all volume attachment requests such as attaching, mounting and formatting volumes on behalf of Kubernetes
- Simplifies the deployment by not requiring to have ceph-tools package installed
- Allows block devices and filesystems to be consumed without any user secret management
- Improves experience with fencing and volume locking
- Rook-Agents
- Configured and deployed via Daemonset by Rook-operator
- Installs the Rook Flexvolume plugin
- Handles all storage operations required on the node, such as attaching devices, mounting volumes and formatting filesystem.
- Performs node cleanups during Rook cluster teardown
- File system
- File systems are defined by a CRD and handled by the Operator
- Multiple file systems can be created, although still experimental in Ceph
- Multiple data pools can be created
- Multiple MDS instances can be created per file system
- An MDS is started in standby mode for each active MDS
- Shared filesystems are now supported by the Rook Flexvolume plugin
- Improved and streamlined experience, now there are no manual steps to copy monitor information or secrets
- Multiple shared filesystems can be created and consumed within the cluster
- More information can be found in the [shared filesystems user guides](/Documentation/k8s-filesystem.md#consume-the-file-system)
- Object Store
- Object Stores are defined by a CRD and handled by the Operator
- Multiple object stores supported through Ceph realms
Expand All @@ -31,8 +43,8 @@
- Standalone mode has been disabled and is no longer supported. A Kubernetes environment is required to run Rook.
- Rook-operator now deploys in `rook-system` namespace
- If using the example manifest of [rook-operator.yaml](/cluster/examples/kubernetes/rook-operator.yaml), the rook-operator deployment is now changed to deploy in the `rook-system` namespace.
- Introduces a new flexvolume plugin that will handle all volume attachment requests. This will simplify the deployment by not requiring to have ceph-tools package installed.
- For Kubernetes cluster 1.7.x and older, Kubelet will need to be restarted in order to load the new flexvolume. This has been resolve in K8S 1.8. For more information about the requirements, refer to this [doc](/Documentation/k8s-pre-reqs.md)
- Rook Flexvolume
- Persistent volumes from previous releases were created using the RBD plugin. These should be deleted and recreated in order to use the new Flexvolume plugin.
- Pool CRD
- `replication` renamed to `replicated`
- `erasureCode` renamed to `erasureCoded`
Expand All @@ -41,4 +53,22 @@
An upgraded operator will create the necessary service account, role, and role bindings to enable this.
- API
- The API pod now uses RBAC permissions that are scoped only to the namespace it is running in.
An upgraded operator will create the necessary service account, role, and role bindings to enable this.
An upgraded operator will create the necessary service account, role, and role bindings to enable this.
- Filesystem
- The Rook Flexvolume uses the `mds_namespace` option to specify a cephFS. This is only available on Kernel v4.7 or newer. On older kernel, if there are more than one filesystems in the cluster, the mount operation could be inconsistent. See this [doc](/Documentation/k8s-filesystem.md#kernel-version-requirement).

## Known Issues

- Rook Flexvolume
- For Kubernetes cluster 1.7.x and older, Kubelet will need to be restarted in order to load the new flexvolume. This has been resolved in K8S 1.8. For more information about the requirements, refer to this [doc](/Documentation/kubernetes.md#restart-kubelet)
- For Kubernetes cluster 1.6.x, the attacher/detacher controller needs to be disabled in order to load the new Flexvolume. This is caused by a [regression](https://github.com/kubernetes/features/blob/master/release-1.6/release-notes-draft.md#volume) on 1.6.x. For more information about the requirements, refer to this [doc](Documentation/kubernetes.md#disable-attacher-detacher-controller)
- For CoreOS and Rancher Kubernetes, the Flexvolume plugin dir will need to be specified to be different than the default. Refer to [Flexvolume configuration pre-reqs](/Documentation/k8s-pre-reqs.md#coreos-container-linux)

## Deprecations

- Rook Standalone
- Standalone mode has been disabled and is no longer supported. A Kubernetes environment is required to run Rook.
- Rook API
- Rook has a goal to integrate natively and deeply with container orchestrators such as Kubernetes and using extension points to manage and access the Rook storage cluster. More information can be found in the [tracking issue](https://github.com/rook/rook/issues/704#issuecomment-338738511).
- Rookctl
- The `rookctl` client is being deprecated. With the deeper and more native integration of Rook with Kubernetes, `kubectl` now provides a rich Rook management experience on its own. For direct management of the Ceph storage cluster, the [Rook toolbox](/Documentation/toolbox.md) provides full access to the Ceph tools.

0 comments on commit 116f088

Please sign in to comment.