Comment 2 for bug 1663541
Revision history for this message
| Lucas Alvares Gomes (lucasagomes) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Hi Rene,
I don't think the problem whether it works with XYZ hardware or not. It's a scalability problem, how many Systems/
My environment is very simple, I've 1 Chassis, 1 Manager and 1 System. The connect() method will issue 21 requests to the Redfish manager with that number. Now, roughly, let's say each resource you add you get 7 more requests at connect() (roughly cause depending on the resource it will have more or less links).
If you have 1000 resources we are talking about 7000 requests, plus, think that, when the Ironic driver is ready each node that uses that driver will issue a connect(). How many requests are we talking about here ? Just to be able to connect to the Redfish Manager ?
That's my point, I think this is an architectural problem with the current implementation that leads to this scalability issue.
re: refresh() idea, it would be handy indeed.