[openstack-dev] [nova][scheduler][placement] Trying to understand the proposed direction
boris at pavlovic.me
Tue Jun 20 01:26:10 UTC 2017
Does this look too complicated and and a bit over designed.
For example, why we can't store all data in memory of single python
application with simple REST API and have
simple mechanism for plugins that are filtering. Basically there is no any
kind of problems with storing it on single host.
If we even have 100k hosts and every host has about 10KB -> 1GB of RAM (I
can just use phone)
There are easy ways to copy the state across different instance (sharing
And I thought that Placement project is going to be such centralized small
simple APP for collecting all
resource information and doing this very very simple and easy placement
On Mon, Jun 19, 2017 at 5:05 PM, Edward Leafe <ed at leafe.com> wrote:
> On Jun 19, 2017, at 5:27 PM, Jay Pipes <jaypipes at gmail.com> wrote:
> It was from the straw man example. Replacing the $FOO_UUID with UUIDs, and
> then stripping out all whitespace resulted in about 1500 bytes. Your
> example, with whitespace included, is 1600 bytes.
> It was the "per compute host" that I objected to.
> I guess it would have helped to see an example of the data returned for
> multiple compute nodes. The straw man example was for a single compute node
> with SR-IOV, NUMA and shared storage. There was no indication how multiple
> hosts meeting the requested resources would be returned.
> -- Ed Leafe
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev