[Starlingx-discuss] Reviews for the Docs mega-spec
I'd like to close out the Docs mega spec review this week. Thank you to all of the reviewers. I believe I have addressed all of your comments. If I have not, please let me know. More reviews are welcome, of course. https://review.openstack.org/#/c/635641/ brucej
On Mon, Mar 4, 2019 at 4:50 PM Jones, Bruce E <bruce.e.jones@intel.com> wrote:
I’d like to close out the Docs mega spec review this week. Thank you to all of the reviewers. I believe I have addressed all of your comments. If I have not, please let me know. More reviews are welcome, of course.
I still have a couple outstanding questions that were part of the reviews but are easy to miss. :) * Is multi-region a thing in STX? Will we be doing both distributed cloud and multi-region? There's a fairly long history of the term "multi-region" in openstack and I'm wondering if that is the same thing or not? * Can we point to upstream docs for things like provider networks? * Overall, if we did all this documentation, which is fairly aggressive in a good way, a lot of it would be valuable upstream. Does it make sense to try to work with openstack docs? I think it would be useful to get other people introduced to StarlingX and help to show how STX relates to OpenStack. The multi-region question is really more me trying to understand what the project is doing, ie. if we aren't actually doing both then we don't need to document both. Otherwise I like the direction and am happy to add my +2. Thanks for all your effort in this. :) Thanks, Curtis
https://review.openstack.org/#/c/635641/
brucej _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
-- Blog: serverascode.com
* Is multi-region a thing in STX? Will we be doing both distributed cloud and multi-region? There's a fairly long history of the term "multi-region" in openstack and I'm wondering if that is the same thing or not? I’ve heard conflicting views from multiple folks on whether Multi-Region will be supported in the May release. Given that the work to implement the Mega-spec spans multiple releases, we could leave it in as a placeholder if the feature isn’t ready for May but will be in November. * Can we point to upstream docs for things like provider networks? Of course. My assumption was that such would be a level of detail for that document’s author to address. * Overall, if we did all this documentation, which is fairly aggressive in a good way, a lot of it would be valuable upstream. Does it make sense to try to work with openstack docs? We are already using the standard OpenStack docs tools and processes. Speaking just for me and not for the Docs team, I think it would make sense to collaborate more with them. brucej From: Curtis [mailto:serverascode@gmail.com] Sent: Monday, March 4, 2019 2:06 PM To: Jones, Bruce E <bruce.e.jones@intel.com> Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Reviews for the Docs mega-spec On Mon, Mar 4, 2019 at 4:50 PM Jones, Bruce E <bruce.e.jones@intel.com<mailto:bruce.e.jones@intel.com>> wrote: I’d like to close out the Docs mega spec review this week. Thank you to all of the reviewers. I believe I have addressed all of your comments. If I have not, please let me know. More reviews are welcome, of course. I still have a couple outstanding questions that were part of the reviews but are easy to miss. :) * Is multi-region a thing in STX? Will we be doing both distributed cloud and multi-region? There's a fairly long history of the term "multi-region" in openstack and I'm wondering if that is the same thing or not? * Can we point to upstream docs for things like provider networks? * Overall, if we did all this documentation, which is fairly aggressive in a good way, a lot of it would be valuable upstream. Does it make sense to try to work with openstack docs? I think it would be useful to get other people introduced to StarlingX and help to show how STX relates to OpenStack. The multi-region question is really more me trying to understand what the project is doing, ie. if we aren't actually doing both then we don't need to document both. Otherwise I like the direction and am happy to add my +2. Thanks for all your effort in this. :) Thanks, Curtis https://review.openstack.org/#/c/635641/ brucej _______________________________________________ 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 -- Blog: serverascode.com<http://serverascode.com>
See comments in-lined below, Greg. From: "Jones, Bruce E" <bruce.e.jones@intel.com> Date: Monday, March 4, 2019 at 5:23 PM To: Curtis <serverascode@gmail.com> Cc: "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] Reviews for the Docs mega-spec * Is multi-region a thing in STX? Will we be doing both distributed cloud and multi-region? There's a fairly long history of the term "multi-region" in openstack and I'm wondering if that is the same thing or not? I’ve heard conflicting views from multiple folks on whether Multi-Region will be supported in the May release. Given that the work to implement the Mega-spec spans multiple releases, we could leave it in as a placeholder if the feature isn’t ready for May but will be in November. [Greg] yeah ... still TBD whether we continue to support Multi-Region in STX ... it has not had a lot of uptake. It still makes sense as a possible scenario ... i.e. a Primary Region and multiple Secondary Regions sharing some services of the Primary. It addresses some of the Controller Services scalability issues in OpenStack. * Can we point to upstream docs for things like provider networks? Of course. My assumption was that such would be a level of detail for that document’s author to address. [Greg] Yeah ... we’ll point upstream where we can ... but provider networks are not fully modelled in Neutron. We tried to upstream this to Neutron but it was turned down. So the high level modelling of the configuration of the provider networks themselves was moved to STX as part of the infrastructure. * Overall, if we did all this documentation, which is fairly aggressive in a good way, a lot of it would be valuable upstream. Does it make sense to try to work with openstack docs? We are already using the standard OpenStack docs tools and processes. Speaking just for me and not for the Docs team, I think it would make sense to collaborate more with them. [Greg] yeah not sure I understand your comment Curtis, this is upstream openstack documentation. Greg. brucej From: Curtis [mailto:serverascode@gmail.com] Sent: Monday, March 4, 2019 2:06 PM To: Jones, Bruce E <bruce.e.jones@intel.com> Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Reviews for the Docs mega-spec On Mon, Mar 4, 2019 at 4:50 PM Jones, Bruce E <bruce.e.jones@intel.com<mailto:bruce.e.jones@intel.com>> wrote: I’d like to close out the Docs mega spec review this week. Thank you to all of the reviewers. I believe I have addressed all of your comments. If I have not, please let me know. More reviews are welcome, of course. I still have a couple outstanding questions that were part of the reviews but are easy to miss. :) * Is multi-region a thing in STX? Will we be doing both distributed cloud and multi-region? There's a fairly long history of the term "multi-region" in openstack and I'm wondering if that is the same thing or not? * Can we point to upstream docs for things like provider networks? * Overall, if we did all this documentation, which is fairly aggressive in a good way, a lot of it would be valuable upstream. Does it make sense to try to work with openstack docs? I think it would be useful to get other people introduced to StarlingX and help to show how STX relates to OpenStack. The multi-region question is really more me trying to understand what the project is doing, ie. if we aren't actually doing both then we don't need to document both. Otherwise I like the direction and am happy to add my +2. Thanks for all your effort in this. :) Thanks, Curtis https://review.openstack.org/#/c/635641/ brucej _______________________________________________ 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 -- Blog: serverascode.com<http://serverascode.com>
On Tue, Mar 5, 2019 at 7:30 AM Waines, Greg <Greg.Waines@windriver.com> wrote:
See comments in-lined below,
Greg.
*From: *"Jones, Bruce E" <bruce.e.jones@intel.com> *Date: *Monday, March 4, 2019 at 5:23 PM *To: *Curtis <serverascode@gmail.com> *Cc: *"starlingx-discuss@lists.starlingx.io" < starlingx-discuss@lists.starlingx.io> *Subject: *Re: [Starlingx-discuss] Reviews for the Docs mega-spec
* Is multi-region a thing in STX? Will we be doing both distributed cloud and multi-region? There's a fairly long history of the term "multi-region" in openstack and I'm wondering if that is the same thing or not?
I’ve heard conflicting views from multiple folks on whether Multi-Region will be supported in the May release. Given that the work to implement the Mega-spec spans multiple releases, we could leave it in as a placeholder if the feature isn’t ready for May but will be in November.
[Greg] yeah ... still TBD whether we continue to support Multi-Region in STX ... it has not had a lot of uptake.
It still makes sense as a possible scenario ... i.e. a Primary Region and multiple Secondary Regions sharing some services of the Primary.
It addresses some of the Controller Services scalability issues in OpenStack.
* Can we point to upstream docs for things like provider networks?
Of course. My assumption was that such would be a level of detail for that document’s author to address.
[Greg]
Yeah ... we’ll point upstream where we can ... but provider networks are not fully modelled in Neutron. We tried to upstream this to Neutron but it was turned down. So the high level modelling of the configuration of the provider networks themselves was moved to STX as part of the infrastructure.
* Overall, if we did all this documentation, which is fairly aggressive in a good way, a lot of it would be valuable upstream. Does it make sense to try to work with openstack docs?
We are already using the standard OpenStack docs tools and processes. Speaking just for me and not for the Docs team, I think it would make sense to collaborate more with them.
[Greg] yeah not sure I understand your comment Curtis, this is upstream openstack documentation.
Greg.
Ok, say you document multi-region architecture and do a great job at it, so it describes how multi-region works in openstack whether it's stx or not...where does that document live? In stx docs or openstack docs? Thanks, Curtis
brucej
*From:* Curtis [mailto:serverascode@gmail.com] *Sent:* Monday, March 4, 2019 2:06 PM *To:* Jones, Bruce E <bruce.e.jones@intel.com> *Cc:* starlingx-discuss@lists.starlingx.io *Subject:* Re: [Starlingx-discuss] Reviews for the Docs mega-spec
On Mon, Mar 4, 2019 at 4:50 PM Jones, Bruce E <bruce.e.jones@intel.com> wrote:
I’d like to close out the Docs mega spec review this week. Thank you to all of the reviewers. I believe I have addressed all of your comments. If I have not, please let me know. More reviews are welcome, of course.
I still have a couple outstanding questions that were part of the reviews but are easy to miss. :)
* Is multi-region a thing in STX? Will we be doing both distributed cloud and multi-region? There's a fairly long history of the term "multi-region" in openstack and I'm wondering if that is the same thing or not?
* Can we point to upstream docs for things like provider networks?
* Overall, if we did all this documentation, which is fairly aggressive in a good way, a lot of it would be valuable upstream. Does it make sense to try to work with openstack docs? I think it would be useful to get other people introduced to StarlingX and help to show how STX relates to OpenStack.
The multi-region question is really more me trying to understand what the project is doing, ie. if we aren't actually doing both then we don't need to document both.
Otherwise I like the direction and am happy to add my +2. Thanks for all your effort in this. :)
Thanks,
Curtis
https://review.openstack.org/#/c/635641/
brucej
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
--
Blog: serverascode.com
-- Blog: serverascode.com
<SNIP> * Overall, if we did all this documentation, which is fairly aggressive in a good way, a lot of it would be valuable upstream. Does it make sense to try to work with openstack docs? We are already using the standard OpenStack docs tools and processes. Speaking just for me and not for the Docs team, I think it would make sense to collaborate more with them. [Greg] yeah not sure I understand your comment Curtis, this is upstream openstack documentation. Greg. Ok, say you document multi-region architecture and do a great job at it, so it describes how multi-region works in openstack whether it's stx or not...where does that document live? In stx docs or openstack docs? Thanks, Curtis The STX document would focus on how options/parameters within the STX Installation scripts (e.g. config-controller, config-region, ... and ansible playbook in the future) are used to setup an OpenStack Multi-Region environment with StarlingX ... and would refer to upstream openstack documentation for the description of what OpenStack Multi-Region is in general. Greg.
On Tue, Mar 5, 2019 at 9:00 AM Waines, Greg <Greg.Waines@windriver.com> wrote:
<SNIP>
* Overall, if we did all this documentation, which is fairly aggressive in a good way, a lot of it would be valuable upstream. Does it make sense to try to work with openstack docs?
We are already using the standard OpenStack docs tools and processes. Speaking just for me and not for the Docs team, I think it would make sense to collaborate more with them.
[Greg] yeah not sure I understand your comment Curtis, this is upstream openstack documentation.
Greg.
Ok, say you document multi-region architecture and do a great job at it, so it describes how multi-region works in openstack whether it's stx or not...where does that document live? In stx docs or openstack docs?
Thanks,
Curtis
The STX document would focus on how options/parameters within the STX Installation scripts (e.g. config-controller, config-region, ... and ansible playbook in the future) are used to setup an OpenStack Multi-Region environment with StarlingX ... and would refer to upstream openstack documentation for the description of what OpenStack Multi-Region is in general.
Ok, now show me the upstream openstack documentation for multi-region. :) I'm having a hard time finding it right now. Doesn't mean it's not there, I just can't find it in a quick search. All I'm saying is that if we actually documented everything in the spec, that would be a lot of useful architecture docs that may very well not exist upstream at this time. There used to be some architecture guides, I think there is still an HA guide, but I'm sure that there are areas that could be improved. And if stx helps to improve those docs, then it would help people outside of the stx project to understand what stx is. Thanks, Curtis
Greg.
-- Blog: serverascode.com
participants (3)
-
Curtis
-
Jones, Bruce E
-
Waines, Greg