Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc/release-notes: ensure RBD users can blacklist prior to upgrade #17755

Merged
merged 1 commit into from Sep 28, 2017

Conversation

Projects
None yet
4 participants
@dillaman
Copy link
Contributor

commented Sep 15, 2017

Fixes: http://tracker.ceph.com/issues/21353
Signed-off-by: Jason Dillaman dillaman@redhat.com

@@ -163,7 +163,8 @@ Major Changes from Kraken
* Specifying user authorization capabilities for RBD clients has been
simplified. The general syntax for using RBD capability profiles is
"mon 'profile rbd' osd 'profile rbd[-read-only][ pool={pool-name}[, ...]]'".
For more details see "User Management" in the documentation.
For more details see :doc:`rados/operations/user-management/`

This comment has been minimized.

Copy link
@amitkumar50

amitkumar50 Sep 18, 2017

Contributor

rados/operation/user-management does not looks to be directory.
this is file user-management.rst

This comment has been minimized.

Copy link
@dillaman

dillaman Sep 24, 2017

Author Contributor

The ":doc:" tag used throughout this file just links to the directories that are created when the .rst files are processed.

@@ -417,6 +418,12 @@ Upgrade from Jewel or Kraken

# ceph osd set noout

#. Verify that all RBD client users have sufficient caps to blacklist
other client users. RBD client users with only ``"allow r"``
monitor caps shold to be updated as follows::

This comment has been minimized.

Copy link
@amitkumar50

amitkumar50 Sep 18, 2017

Contributor

shold spelling wrong

@smithfarm smithfarm requested a review from theanalyst Sep 21, 2017

@smithfarm

This comment has been minimized.

Copy link
Contributor

commented Sep 21, 2017

@theanalyst Do we need to include this in the v12.2.1 release notes?

@dillaman Can you correct the spelling of "should" as per @amitkumar50 review?

@dillaman

This comment has been minimized.

Copy link
Contributor Author

commented Sep 21, 2017

I am out of the country presently -- if it can wait until next week, I'll fix it. Otherwise, can someone else open a new PR w/ the spelling fix? Thanks!

@theanalyst

This comment has been minimized.

Copy link
Member

commented Sep 22, 2017

@smithfarm since this is a doc only change lets just wait until we have a decision on whether we are going for a new build, if not I'll just merge in after we do a release

@dillaman dillaman force-pushed the dillaman:wip-21353 branch from 5fd7cef to 58e8bd8 Sep 24, 2017

@dillaman

This comment has been minimized.

Copy link
Contributor Author

commented Sep 24, 2017

spelling correction pushed

@theanalyst theanalyst merged commit 7e253f8 into ceph:master Sep 28, 2017

5 checks passed

Docs: build check OK - docs built
Details
Signed-off-by all commits in this PR are signed
Details
Unmodified Submodules submodules for project are unmodified
Details
make check make check succeeded
Details
make check (arm64) make check succeeded
Details

@dillaman dillaman deleted the dillaman:wip-21353 branch Sep 28, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.