Project

General

Profile

Bug #6398

default working directory for ceph-deploy

Added by Alfredo Deza about 9 years ago. Updated almost 8 years ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):

Description

ceph-deploy creates configurations (and a couple of other things like a keyring) in the current working directory.

This is not entirely bad, but for new users it can be difficult to adhere to this "execute from anywhere but continue to
call ceph-deploy from that same directory" mentality.

And ceph-deploy does this because it is easier (lazier!) to assume that wherever it is being executed is where the configs
should be.

If we change this to default to something like `$HOME/ceph_deploy/` or `$HOME/.ceph_deploy` by default and allow a user to
specify a different main working directory via an environment variable (e.g. "$CEPH_DEPLOY_HOME") or with a flag ("--home")
it would mean it can allow other users to tweak as needed.

Some thoughts from Ian:

  • most users will not have multiple configs
  • you should have to do something special if you are a non standard-user (e.g. teuthology)

History

#1 Updated by Loïc Dachary almost 9 years ago

In the context where ceph-deploy is used as a helper for puppet / chef / ..., it would be most convenient to use values from the environment instead of relying on files. The puppet module would then need to call ceph-deploy with the required environment variables on the target host instead of creating the files and then calling ceph-deploy and then delete them.

#2 Updated by Neil Levine almost 8 years ago

  • Project changed from devops to Ceph-deploy
  • Category deleted (ceph-deploy)

Also available in: Atom PDF