[Starlingx-discuss] Changes to Ceph storage backend provisioning

Alfredo De Luca alfredo.deluca at gmail.com
Fri Feb 21 11:42:02 UTC 2020


Hi Stefan. does it mean that it will be possible to have a different
storage backend?

Cheers

On Fri, Feb 21, 2020 at 9:36 AM Dinescu, Stefan <
Stefan.Dinescu at windriver.com> wrote:

> Hello,
>
> Changes have been merged, so the new command is not officially required to
> provision the Ceph storage-backend.
>
> Let me know if you encounter any issues.
>
> Thanks,
> Stefan
> ------------------------------
> *From:* Dinescu, Stefan <Stefan.Dinescu at windriver.com>
> *Sent:* Thursday, February 20, 2020 5:41 PM
> *To:* starlingx-discuss at lists.starlingx.io <
> starlingx-discuss at lists.starlingx.io>
> *Subject:* [Starlingx-discuss] Changes to Ceph storage backend
> provisioning
>
> Hello guys.
>
> I have been working on a feature to make provisioning of Ceph storage
> backend optional and the changes will soon merge. Reviews: [1], [2], [3]
> and [4].
>
> The main purpose of this feature is to allow STX to be installed on
> systems with a limited number of resources (CPU and RAM mainly, but also
> hard-drives). If people want to deploy applications that don't require any
> persistent storage, ceph shouldn't consume RAM and CPU time.
>
> *IMPORTANT: *The stx-openstack application requires persistent storage,
> and thus requires a ceph storage backend.
>
> This change adds a new command that needs to run after the ansible
> bootstrap, in order to provision the ceph storage backend. The command is:
>
> *system storage-backend-add ceph --confirmed*
>
>
> These changes are also documented in review [4].
>
> There is also the option for users to install a full system *without*
> provisioning the Ceph storage backend and then provision it later using the
> same command.
>
> Make sure you update your workflow to take into account this new command.
> If you encounter any bugs or issues once these changes are merged, feel
> free to send me an email.
>
> Thanks,
> Stefan
>
> [1]: https://review.opendev.org/705234
> [2]: https://review.opendev.org/705235
> [3]: https://review.opendev.org/705236
> [4]: https://review.opendev.org/707385
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
>


-- 
*Alfredo*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20200221/7ba5850a/attachment.html>


More information about the Starlingx-discuss mailing list