>If they're not listed anywhere, I suppose that nobody follows up on the sizing until something breaks?
I have been introspecting the infra mirror on FortNebula to determine if there is any last little bit of performance to be gained. Its also publicly tracked here https://grafana.fortnebula.com/d/9MMqh8HWk/openstack-utilization <http://grafana.fortnebula.com:3000/d/9MMqh8HWk/openstack-utilization> On Mon, Aug 19, 2019 at 12:57 PM Clark Boylan <cboy...@sapwetik.org> wrote: > On Mon, Aug 19, 2019, at 9:36 AM, Shadi Akiki wrote: > > > the sizing details for control plane servers are not really listed > anywhere > > > > If they're not listed anywhere, I suppose that nobody follows up on the > > sizing until something breaks? > > > > > Sometimes the cloud provider will provide us with custom flavors, or > ask us to use a particular variant > > > > Why would they ask for a particular variant? Is it because these > > resources are donated by the cloud provider? > > That's my best guess to justify this. > > Yes, resources are donated by the cloud providers. I think providers tend > to use special flavors to control how are resources are scheduled. > > > > > > for something not load-balanced that requires production downtime, > it's a very manual process > > > > Is it also the case that the load-balancing settings are not recorded > > anywhere? > > eg minimum and maximum number of machines in a load-balancing cluster, > > machine flavor > > Our load balancers don't currently do auto scaling. But configs do live in > config management. For example: > https://opendev.org/opendev/system-config/src/branch/master/playbooks/group_vars/gitea-lb.yaml > > There are longer term plans to host that service in kubernetes which could > make use of scaling, but gitea the software isn't capable of running in a > true cluster yet. > > > > > > It's just a trade-off between development time to create and maintain > > > that, and how often we actually start control-plane servers. > > > > Are the control-plane servers the only cloud cost aspect to outweigh > > the development costs? > > I'm surprised there isn't already a tool out there that interfaces with > > rrdtool and/or cacti to help with this. > > rrdtool seems to have been around since 20 years now [1] [2] > > The expectation from cacti is likely that you'll use the same snmp MIB > data that cacti uses to build its graphs to query sizing info directly if > you want it. Rather than expecting cacti or rrdtool to expose that to you. > > > > > [1] https://tobi.oetiker.ch/webtools/appreciators.txt > > [2] > > > https://github.com/oetiker/rrdtool-1.x/commit/37fc663811528ddf3ded4fe236ea26f4f76fa32d#diff-dee0aab09da2b4d69b6722a85037700d > > -- > > Shadi Akiki > > Founder & CEO, AutofitCloud > > https://autofitcloud.com/ > > +1 813 579 4935 > > _______________________________________________ > OpenStack-Infra mailing list > OpenStack-Infra@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
_______________________________________________ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra