openstack/kolla.git/docker/ceph/ceph-mon/extend_start.sh, branch stein-eol

ceph mds cap 'allow *' in extend_start

2019-08-02T08:28:43+00:00

This applies the fix made in kolla-ansible (see [1]) to kolla ceph mon image directly. [1] https://review.opendev.org/670035 Change-Id: I1822a8c610db72654bbacc7148e25a837090b680 Signed-off-by: Radosław Piliszek (cherry picked from commit b1d4ed51f41721c86a33d766fdfd80aaccf1df60)

Ceph: Update to Nautilus on CentOS and OracleLinux

2019-06-06T06:36:44+00:00

The CentOS Stein OpenStack distribution depends on the Ceph Nautilus release, while Kolla currently deploys Luminous on CentOS. This change switches CentOS and OracleLinux builds to use Ceph Nautilus. Support for auth UID has been removed in the Nautilus release [1][2], so we have removed the --set-uid argument from calls to ceph-authtool. Also ceph-osd bootstrap mode fails when no mon config is provided, so we added --no-mon-config (mon config is injected later after bootstrap). Due to ceph-nfs build issues (ceph upstream nfs-ganesha rpms relied on older version of userspace-rcu, than CentOS Storage SIG packages) we need to move to ceph upstream rpm repos. [1] https://github.com/ceph/ceph/commit/d6def8ba1126209f8dcb40e296977dc2b09a376e [2] http://docs.ceph.com/docs/master/releases/nautilus/ Co-Authored-By: Michal Nasiadka Change-Id: I000398f587c5f4d6cc8995e34e162eebc77bc3e3 Implements: blueprint centos-ceph-nautilus (cherry picked from commit e0cae62c4aab001fa7b5cc324f178793f4e88f3c)

Fix multiple mon deployment failures

2019-05-23T01:19:02+00:00

When 4 or 5 mons are deployed, all mons will always be in the election state, and the ceph cluster cannot be accessed. After comparing with ceph-deploy, I found that when the cluster was initialized, it did not use monmap. When adding a new mon node, it needs to use monmap. According to the above situation, I fixed the problem. Change-Id: Idbfc6741d371adcb06ed97d578d75d3bce862743 Closes-bug: #1824783 (cherry picked from commit 285814353af29395932e15d78c6a154796978a21)

Add cap mgr 'allow *' for ceph admin key

2018-02-22T06:50:38+00:00

Some ceph cluster commands require this caps Change-Id: Idfa19667f1fb83f2cb89712c594513188d859359 Closes-Bug: #1750967

Make Heka collect Ceph logs

2016-05-05T17:26:44+00:00

Change-Id: Ibaa5f8ba600afafa111d2ef204ee9192b8babdfc Closes-Bug: #1570529

Switch ceph to use storage network

2016-02-24T17:19:52+00:00

Ceph was not properly using storage network. TrivialFix Change-Id: Ibf3da5d19cd2ca874d251b455a7eb856154fc3f7

reset $(hostname) to $(hostname -s) in ceph extend_start.sh

2016-01-28T04:37:17+00:00

$(hostname) is Ceph Monitor name in extend_start.sh, {{ ansibe_hostanme }} is Ceph Monitor name in ceph.conf. $(hostname) not always equal to ansible_hostname , that makes ceph_mon container can't start. Closes-Bug: #1538870 Change-Id: I312bf8d74c855aa4c72f12285e3092df96f60048

Rename ceph-mon bootstrap container to avoid conflict

2016-01-17T23:20:54+00:00

Ceph-mon bootstrap container shares the same name of `ceph_mon` with real ceph-mon service. When bootstrapping, it will sleep forever for the purpose of distribute rings. Later on, when starting real `ceph_mon` service, kolla_docker module will take bootstrap container as real one because bootstrap container has a super set of env variables and kolla_docker doesn't do strict comparing of env variable items. This change follows the pattern of other bootstrap containers and rename to use `bootstrap_ceph_mon` to avoid conflict. Co-Authored-By: Sam Yaple Change-Id: I0082820900928c42f9cc778ffd705980fea9ad1c Closes-Bug: #1535140

Add RadosGW container

2015-12-29T12:49:03+00:00

Implements blueprint radosgw-container Change-Id: Idc88a67a0979be626d3eaa9b2b9a527010aa2006

Common start.sh

2015-10-06T03:30:26+00:00

The majority of the start.sh code is identical. This removes that duplicate code while still maintaining the ability to call code in a specific container. The start.sh is moved into /usr/local/bin/kolla_start in the container The extend_start.sh script is called by the kolla_start script at the location /usr/local/bin/kolla_extend_start . It always exists because we create a noop kolla_extend_start in the base directory. We override it with extend_start.sh in a specific image should we need to. Of note, the neutron-agents container is exempt from this new structure due to it being a fat container. Additionally, we fix the inconsistent permissions throughout. 644 for repo files and the scripts are set to 755 via a Docker RUN command to ensure someones local perm change won't break upstream containers. Change-Id: I7da8d19965463ad30ee522a71183e3f092e0d6ad Closes-Bug: #1501295