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

2017-12-18 Thread Flint WALRUS
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 t

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

2017-12-18 Thread Jeremy Stanley
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 your

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

2017-12-18 Thread Akihiro Motoki
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 distribut

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

2017-12-18 Thread Flint WALRUS
@ArKady, My point is exactly the one pointed out by Matt, and he summaries everything I think about the dashboards usage. What's the point to multiply dashboards for a solution that's explecting you to expand it... that's non-sense. Having multiple dashboard to manage a unique solution is exactly

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

2017-12-18 Thread Matt Joyce
Agreed on dashboard use. This is a mistake Google made with their GCP platform. They made their gui a nightmarish ux designed to destroy the souls of their users because they expected folks to use the CLIs... and a lot of the time they didn't... because are you are automating an environment prior

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

2017-12-18 Thread Arkady.Kanevsky
: [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 indeed rely a lot on the dashboard r

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

2017-12-18 Thread Flint WALRUS
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 indeed rely a lot on the dashboard rather than the CLI for a lot of daily tasks. Not everyone is willing to go

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

2017-12-18 Thread Arkady.Kanevsky
Flint, Horizon is targeted to a user not administrator/operator. The closest we have is TripleO UI . Whatever change in any node configuration 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:

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

2017-12-18 Thread Flint WALRUS
Hi Jeremy! Thanks for your quick and precise response! It is indeed and kind of you taking time to point me out against the correct mailing list! Sweet! As an operator, do you guys see a benefit from such additional feature within Horizon? asking before starting to develop or ask anything to the

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

2017-12-18 Thread Sławomir Kapłoński
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 have > my bet on it :D

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

2017-12-18 Thread Jeremy Stanley
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 o