Hi Marvin,

There is no need to wait for the primary tier storage backend to be configured, it's enabled by default at config_controller. Thus, this backend is already in 'configured' state.

Ovidiu

From: Huang, Marvin
Sent: Thursday, April 18, 2019 11:38 PM
To: Poncea, Ovidiu; starlingx-discuss@lists.starlingx.io
Subject: RE: [Starlingx-discuss] For automation: Instalation workflow update will be merged soon

Hi Ovidiu,

 

How long (in worst case) should users wait for Ceph-backend be configured?
Or what is the timeout value we should use for automated waiting/polling, after which we can considerate that there is likely an issue?

 

 

Thanks,

Marvin

 

From: Poncea, Ovidiu [mailto:Ovidiu.Poncea@windriver.com]
Sent: Wednesday, April 17, 2019 5:50 PM
To: starlingx-discuss@lists.starlingx.io
Subject: Re: [Starlingx-discuss] For automation: Instalation workflow update will be merged soon

 

Change was merged, wiki was updated...

 


From: Poncea, Ovidiu [Ovidiu.Poncea@windriver.com]
Sent: Tuesday, April 16, 2019 10:36 PM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] For automation: Instalation workflow update will be merged soon

Hi Folks,

 

Be aware that we will merge a change soon that may impact automated deployments and testing. The gerrit is this: https://review.openstack.org/#/c/644256/ and it will make Ceph the default storage backend. Therefore, once merged, users will no longer have to run this (as currently stated by the wikis):

 

echo ">>> Enable primary Ceph backend"
system storage-backend-add ceph --confirmed
 
echo ">>> Wait for primary ceph backend to be configured"
echo ">>> This step really takes a long time"
while [ $(system storage-backend-list | awk '/ceph-store/{print $8}') != 'configured' ]; do echo 'Waiting for ceph..'; sleep 5; done
 
echo ">>> Ceph health"
ceph -s

Regards,

Ovidiu