Re: [Openstack-operators] Openstack operational configuration improvement.

Thank you very much @Akihiro and @Jeremy these answers are really useful and constructives. Akihiro, regarding your two points yes, they for sure will be challenging and I really plan to work on this feature as a horizon plugin at the beginning as you mentioned it. Here what I'm thinking to do

Re: [Openstack-operators] Openstack operational configuration improvement.

On 2017-12-19 01:40:50 +0900 (+0900), Akihiro Motoki wrote: [...] > First point is how to distribute configuration files configured > via GUI to servers. Horizon communicates back-end services through > REST APIs and is agnostic of actual server setup. There is no way > for horizon to know how

Re: [Openstack-operators] Openstack operational configuration improvement.

Hi Flint, I have both hats as an operator of OpenStack and a horizon core. I understand that GUI support of OpenStack configuration is useful for some operators. I know several softwares support GUI-based configurations. However, I see several challenging points. First point is how to

Re: [Openstack-operators] Openstack operational configuration improvement.

from OpenStack down to OS to >>> HW need to be recorded in whatever method used to set openstack in order to >>> be able to handle upgrade. >>> >>> Thanks, >>> >>> Arkady >>> >>> >>> >>> *From:* Flint WALRUS

Re: [Openstack-operators] Openstack operational configuration improvement.

tack down to OS to HW >> need to be recorded in whatever method used to set openstack in order to be >> able to handle upgrade. >> >> Thanks, >> >> Arkady >> >> >> >> *From:* Flint WALRUS [mailto:gael.ther...@gmail.com] >> *Sent:* Monday, Dec

Re: [Openstack-operators] Openstack operational configuration improvement.

rators@lists.openstack.org Subject: Re: [Openstack-operators] Openstack operational configuration improvement. Hi arkady, Ok understood your point. However, as an operator and administrator of a really large deployment I disagree with this statement as a lot of our company's admins and operators indee

Re: [Openstack-operators] Openstack operational configuration improvement.

e upgrade. > > Thanks, > > Arkady > > > > *From:* Flint WALRUS [mailto:gael.ther...@gmail.com] > *Sent:* Monday, December 18, 2017 7:29 AM > *To:* openstack-operators@lists.openstack.org > *Subject:* [Openstack-operators] Openstack operational configuration > improvement.

Re: [Openstack-operators] Openstack operational configuration improvement.

Hi, Isn't Fuel or TripleO something what You are looking for? — Best regards Slawek Kaplonski sla...@kaplonski.pl > Wiadomość napisana przez Flint WALRUS w dniu > 18.12.2017, o godz. 14:28: > > Hi everyone, I don't really know if this list is the good one, but I'll

Re: [Openstack-operators] Openstack operational configuration improvement.

On 2017-12-18 13:28:46 + (+), Flint WALRUS wrote: [...] > If this discussion should go with the horizon team rather than the > operational team, could someone help with this one as I didn't > find any mailing list related endpoint? I certainly wouldn't want to discourage discussion among

[Openstack-operators] Openstack operational configuration improvement.

Hi everyone, I don't really know if this list is the good one, but I'll have my bet on it :D Here I go. Since many times now, I'm managing Openstack platforms, and one things that always amazed me is its lack of comprehensive configuration management for services within Horizon. Indeed, you