[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
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@windriver.com> Sent: Thursday, February 20, 2020 5:41 PM To: starlingx-discuss@lists.starlingx.io <starlingx-discuss@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
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@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@windriver.com> *Sent:* Thursday, February 20, 2020 5:41 PM *To:* starlingx-discuss@lists.starlingx.io < starlingx-discuss@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@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
-- *Alfredo*
Hello, At this moment in time only the Ceph storage backend in supported. As I said, this feature was designed for less powerful systems where Ceph was not needed. Also, small correction. I said "the new command is not officially required". What I meant to say was "the new command is now officially required". ________________________________ From: Alfredo De Luca <alfredo.deluca@gmail.com> Sent: Friday, February 21, 2020 1:42 PM To: Dinescu, Stefan <Stefan.Dinescu@windriver.com> Cc: starlingx-discuss@lists.starlingx.io <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] Changes to Ceph storage backend provisioning 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@windriver.com<mailto:Stefan.Dinescu@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@windriver.com<mailto:Stefan.Dinescu@windriver.com>> Sent: Thursday, February 20, 2020 5:41 PM To: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@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@lists.starlingx.io<mailto:Starlingx-discuss@lists.starlingx.io> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- Alfredo
great! Thanks for clarifying Cheers On Fri, Feb 21, 2020 at 1:42 PM Dinescu, Stefan < Stefan.Dinescu@windriver.com> wrote:
Hello,
At this moment in time only the Ceph storage backend in supported. As I said, this feature was designed for less powerful systems where Ceph was not needed.
Also, small correction. I said *"the new command is not officially required". *What I meant to say was "*the new command is now officially required*". ------------------------------ *From:* Alfredo De Luca <alfredo.deluca@gmail.com> *Sent:* Friday, February 21, 2020 1:42 PM *To:* Dinescu, Stefan <Stefan.Dinescu@windriver.com> *Cc:* starlingx-discuss@lists.starlingx.io < starlingx-discuss@lists.starlingx.io> *Subject:* Re: [Starlingx-discuss] Changes to Ceph storage backend provisioning
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@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@windriver.com> *Sent:* Thursday, February 20, 2020 5:41 PM *To:* starlingx-discuss@lists.starlingx.io < starlingx-discuss@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@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
-- *Alfredo*
-- *Alfredo*
Has someone updated docs.starlingX.io for this change? brucej From: Alfredo De Luca [mailto:alfredo.deluca@gmail.com] Sent: Friday, February 21, 2020 7:21 AM To: Dinescu, Stefan <Stefan.Dinescu@windriver.com> Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Changes to Ceph storage backend provisioning great! Thanks for clarifying Cheers On Fri, Feb 21, 2020 at 1:42 PM Dinescu, Stefan <Stefan.Dinescu@windriver.com<mailto:Stefan.Dinescu@windriver.com>> wrote: Hello, At this moment in time only the Ceph storage backend in supported. As I said, this feature was designed for less powerful systems where Ceph was not needed. Also, small correction. I said "the new command is not officially required". What I meant to say was "the new command is now officially required". ________________________________ From: Alfredo De Luca <alfredo.deluca@gmail.com<mailto:alfredo.deluca@gmail.com>> Sent: Friday, February 21, 2020 1:42 PM To: Dinescu, Stefan <Stefan.Dinescu@windriver.com<mailto:Stefan.Dinescu@windriver.com>> Cc: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Subject: Re: [Starlingx-discuss] Changes to Ceph storage backend provisioning 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@windriver.com<mailto:Stefan.Dinescu@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@windriver.com<mailto:Stefan.Dinescu@windriver.com>> Sent: Thursday, February 20, 2020 5:41 PM To: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@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@lists.starlingx.io<mailto:Starlingx-discuss@lists.starlingx.io> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- Alfredo -- Alfredo
participants (3)
-
Alfredo De Luca
-
Dinescu, Stefan
-
Jones, Bruce E