| 2017-02-10 10:23:02 |
Lucas Alvares Gomes |
bug |
|
|
added bug |
| 2017-02-10 10:25:37 |
Lucas Alvares Gomes |
description |
This bug is related to [0] which points out that python-redfish is extremely verbose, perhaps, this one describes the reason for that.
Basically, as soon as you invoke connect()[1] python-redfish will follow pretty much all links to the resources in the Redfish tree and build objects from it, even if you only need to get a single one (say one System, which represents a "Node" in Ironic).
One thing that I've learned working in Ironic is that BMCs are fragile, I worry about the way things are architected in python-redfish because a simple connect could hammer the BMC with many requests at once, the more resources you have, say 1000 Systems, this is going to be 1001 requests at startup (Note, there's more resources than systems, there are Managers and also Chassis, they all count).
Back to [0], the example I'm using here I have only 1 System, 1 Chassis and 1 Manager [2] and only with this few python-redfish produces 1000+ lines of debug code (mostly for dumping the representation of the objects it creates) and 21 requests [3].
[0] https://bugs.launchpad.net/python-redfish/+bug/1662896
[1] For example:
import redfish
redfish.connect(...)
[2] http://paste.openstack.org/show/598363/
[3] http://paste.openstack.org/show/598366/
More info:
----------
The tests are running the Redfish simulator version 1.0.0 (DSP2043), direct link: https://www.dmtf.org/sites/default/files/standards/documents/DSP2043_1.0.0.zip
With the mockup server: https://github.com/DMTF/Redfish-Mockup-Server/blob/master/redfishMockupServer.py |
This bug is related to [0] which points out that python-redfish is extremely verbose, perhaps, this one describes the reason for that.
Basically, as soon as you invoke connect()[1] python-redfish will follow pretty much all links to the resources in the Redfish tree and build objects from it, even if you only need to get a single one (say one System, which represents a "Node" in Ironic).
One thing that I've learned working in Ironic is that BMCs are fragile, I worry about the way things are architected in python-redfish because a simple connect could hammer the BMC with many requests at once, the more resources you have, say 1000 resources (between Systems, Managers and Chassis), this is going to be 20.000+ requests at startup (Note, this is just an approximately number, keep reading.)
Back to [0], the example I'm using here contains only 1 System, 1 Chassis and 1 Manager [2]. This is enough for python-redfish to send 21 requests [3] and produce 1000+ lines of debug code (mostly for dumping the representation of the objects it creates).
[0] https://bugs.launchpad.net/python-redfish/+bug/1662896
[1] For example:
import redfish
redfish.connect(...)
[2] http://paste.openstack.org/show/598363/
[3] http://paste.openstack.org/show/598366/
More info:
----------
The tests are running the Redfish simulator version 1.0.0 (DSP2043), direct link: https://www.dmtf.org/sites/default/files/standards/documents/DSP2043_1.0.0.zip
With the mockup server: https://github.com/DMTF/Redfish-Mockup-Server/blob/master/redfishMockupServer.py |
|
| 2017-02-10 10:56:24 |
Lucas Alvares Gomes |
summary |
Avoid constructing the whole resources tree at connect() |
Avoid constructing the whole resource tree at connect() |
|
| 2017-02-10 10:58:11 |
Lucas Alvares Gomes |
description |
This bug is related to [0] which points out that python-redfish is extremely verbose, perhaps, this one describes the reason for that.
Basically, as soon as you invoke connect()[1] python-redfish will follow pretty much all links to the resources in the Redfish tree and build objects from it, even if you only need to get a single one (say one System, which represents a "Node" in Ironic).
One thing that I've learned working in Ironic is that BMCs are fragile, I worry about the way things are architected in python-redfish because a simple connect could hammer the BMC with many requests at once, the more resources you have, say 1000 resources (between Systems, Managers and Chassis), this is going to be 20.000+ requests at startup (Note, this is just an approximately number, keep reading.)
Back to [0], the example I'm using here contains only 1 System, 1 Chassis and 1 Manager [2]. This is enough for python-redfish to send 21 requests [3] and produce 1000+ lines of debug code (mostly for dumping the representation of the objects it creates).
[0] https://bugs.launchpad.net/python-redfish/+bug/1662896
[1] For example:
import redfish
redfish.connect(...)
[2] http://paste.openstack.org/show/598363/
[3] http://paste.openstack.org/show/598366/
More info:
----------
The tests are running the Redfish simulator version 1.0.0 (DSP2043), direct link: https://www.dmtf.org/sites/default/files/standards/documents/DSP2043_1.0.0.zip
With the mockup server: https://github.com/DMTF/Redfish-Mockup-Server/blob/master/redfishMockupServer.py |
This bug is related to [0] which points out that python-redfish is extremely verbose, perhaps, this one describes the reason for that.
Basically, as soon as you invoke connect()[1] python-redfish will follow pretty much all links to the resources in the Redfish tree and build objects from it, even if you only need to get a single one (say one System, which represents a "Node" in Ironic).
One thing that I've learned working in Ironic is that BMCs are fragile, I worry about the way things are architected in python-redfish because a simple connect could hammer the BMC with many requests at once, the more resources you have, say 1000 resources (between Systems, Managers and Chassis), this is going to be 20.000+ requests at startup (Note, this is just an approximately number, keep reading.)
Back to [0], the example I'm using here contains only 1 System, 1 Chassis and 1 Manager [2]. This is enough for python-redfish to send 21 requests [3] and produce 1000+ lines of debug code (mostly for dumping the representation of the objects it creates) at the very first connect().
[0] https://bugs.launchpad.net/python-redfish/+bug/1662896
[1] For example:
import redfish
redfish.connect(...)
[2] http://paste.openstack.org/show/598363/
[3] http://paste.openstack.org/show/598366/
More info:
----------
The tests are running the Redfish simulator version 1.0.0 (DSP2043), direct link: https://www.dmtf.org/sites/default/files/standards/documents/DSP2043_1.0.0.zip
With the mockup server: https://github.com/DMTF/Redfish-Mockup-Server/blob/master/redfishMockupServer.py |
|
| 2017-02-10 13:00:26 |
Lucas Alvares Gomes |
description |
This bug is related to [0] which points out that python-redfish is extremely verbose, perhaps, this one describes the reason for that.
Basically, as soon as you invoke connect()[1] python-redfish will follow pretty much all links to the resources in the Redfish tree and build objects from it, even if you only need to get a single one (say one System, which represents a "Node" in Ironic).
One thing that I've learned working in Ironic is that BMCs are fragile, I worry about the way things are architected in python-redfish because a simple connect could hammer the BMC with many requests at once, the more resources you have, say 1000 resources (between Systems, Managers and Chassis), this is going to be 20.000+ requests at startup (Note, this is just an approximately number, keep reading.)
Back to [0], the example I'm using here contains only 1 System, 1 Chassis and 1 Manager [2]. This is enough for python-redfish to send 21 requests [3] and produce 1000+ lines of debug code (mostly for dumping the representation of the objects it creates) at the very first connect().
[0] https://bugs.launchpad.net/python-redfish/+bug/1662896
[1] For example:
import redfish
redfish.connect(...)
[2] http://paste.openstack.org/show/598363/
[3] http://paste.openstack.org/show/598366/
More info:
----------
The tests are running the Redfish simulator version 1.0.0 (DSP2043), direct link: https://www.dmtf.org/sites/default/files/standards/documents/DSP2043_1.0.0.zip
With the mockup server: https://github.com/DMTF/Redfish-Mockup-Server/blob/master/redfishMockupServer.py |
This bug is related to [0] which points out that python-redfish is extremely verbose, perhaps, this one describes the reason for that.
Basically, as soon as you invoke connect()[1] python-redfish will follow pretty much all links to the resources in the Redfish tree and build objects from it, even if you only need to get a single one (say one System, which represents a "Node" in Ironic).
One thing that I've learned working in Ironic is that BMCs are fragile, I worry about the way things are architected in python-redfish because a simple connect could hammer the BMC with many requests at once, the more resources you have, say 1000 resources (between Systems, Managers and Chassis), this is going to be 6000+ requests at startup (Note, this is just an approximately number, keep reading.)
Back to [0], the example I'm using here contains only 1 System, 1 Chassis and 1 Manager [2]. This is enough for python-redfish to send 21 requests [3] and produce 1000+ lines of debug code (mostly for dumping the representation of the objects it creates) at the very first connect().
[0] https://bugs.launchpad.net/python-redfish/+bug/1662896
[1] For example:
import redfish
redfish.connect(...)
[2] http://paste.openstack.org/show/598363/
[3] http://paste.openstack.org/show/598366/
More info:
----------
The tests are running the Redfish simulator version 1.0.0 (DSP2043), direct link: https://www.dmtf.org/sites/default/files/standards/documents/DSP2043_1.0.0.zip
With the mockup server: https://github.com/DMTF/Redfish-Mockup-Server/blob/master/redfishMockupServer.py |
|
| 2017-02-10 17:29:56 |
Lucas Alvares Gomes |
description |
This bug is related to [0] which points out that python-redfish is extremely verbose, perhaps, this one describes the reason for that.
Basically, as soon as you invoke connect()[1] python-redfish will follow pretty much all links to the resources in the Redfish tree and build objects from it, even if you only need to get a single one (say one System, which represents a "Node" in Ironic).
One thing that I've learned working in Ironic is that BMCs are fragile, I worry about the way things are architected in python-redfish because a simple connect could hammer the BMC with many requests at once, the more resources you have, say 1000 resources (between Systems, Managers and Chassis), this is going to be 6000+ requests at startup (Note, this is just an approximately number, keep reading.)
Back to [0], the example I'm using here contains only 1 System, 1 Chassis and 1 Manager [2]. This is enough for python-redfish to send 21 requests [3] and produce 1000+ lines of debug code (mostly for dumping the representation of the objects it creates) at the very first connect().
[0] https://bugs.launchpad.net/python-redfish/+bug/1662896
[1] For example:
import redfish
redfish.connect(...)
[2] http://paste.openstack.org/show/598363/
[3] http://paste.openstack.org/show/598366/
More info:
----------
The tests are running the Redfish simulator version 1.0.0 (DSP2043), direct link: https://www.dmtf.org/sites/default/files/standards/documents/DSP2043_1.0.0.zip
With the mockup server: https://github.com/DMTF/Redfish-Mockup-Server/blob/master/redfishMockupServer.py |
This bug is related to [0] which points out that python-redfish is extremely verbose, perhaps, this one describes the reason for that.
Basically, as soon as you invoke connect()[1] python-redfish will follow pretty much all links to the resources in the Redfish tree and build objects from it, even if you only need to get a single one (say one System, which represents a "Node" in Ironic).
One thing that I've learned working in Ironic is that BMCs are fragile, I worry about the way things are architected in python-redfish because a simple connect could hammer the BMC with many requests at once, the more resources you have, say 1000 resources (between Systems, Managers and Chassis), this is going to be 20000+ requests at startup (Note, this is just an approximately number, keep reading.)
Back to [0], the example I'm using here contains only 1 System, 1 Chassis and 1 Manager [2]. This is enough for python-redfish to send 21 requests [3] and produce 1000+ lines of debug code (mostly for dumping the representation of the objects it creates) at the very first connect().
[0] https://bugs.launchpad.net/python-redfish/+bug/1662896
[1] For example:
import redfish
redfish.connect(...)
[2] http://paste.openstack.org/show/598363/
[3] http://paste.openstack.org/show/598366/
More info:
----------
The tests are running the Redfish simulator version 1.0.0 (DSP2043), direct link: https://www.dmtf.org/sites/default/files/standards/documents/DSP2043_1.0.0.zip
With the mockup server: https://github.com/DMTF/Redfish-Mockup-Server/blob/master/redfishMockupServer.py |
|
| 2017-02-10 17:32:32 |
Lucas Alvares Gomes |
description |
This bug is related to [0] which points out that python-redfish is extremely verbose, perhaps, this one describes the reason for that.
Basically, as soon as you invoke connect()[1] python-redfish will follow pretty much all links to the resources in the Redfish tree and build objects from it, even if you only need to get a single one (say one System, which represents a "Node" in Ironic).
One thing that I've learned working in Ironic is that BMCs are fragile, I worry about the way things are architected in python-redfish because a simple connect could hammer the BMC with many requests at once, the more resources you have, say 1000 resources (between Systems, Managers and Chassis), this is going to be 20000+ requests at startup (Note, this is just an approximately number, keep reading.)
Back to [0], the example I'm using here contains only 1 System, 1 Chassis and 1 Manager [2]. This is enough for python-redfish to send 21 requests [3] and produce 1000+ lines of debug code (mostly for dumping the representation of the objects it creates) at the very first connect().
[0] https://bugs.launchpad.net/python-redfish/+bug/1662896
[1] For example:
import redfish
redfish.connect(...)
[2] http://paste.openstack.org/show/598363/
[3] http://paste.openstack.org/show/598366/
More info:
----------
The tests are running the Redfish simulator version 1.0.0 (DSP2043), direct link: https://www.dmtf.org/sites/default/files/standards/documents/DSP2043_1.0.0.zip
With the mockup server: https://github.com/DMTF/Redfish-Mockup-Server/blob/master/redfishMockupServer.py |
This bug is related to [0] which points out that python-redfish is extremely verbose, perhaps, this one describes the reason for that.
Basically, as soon as you invoke connect()[1] python-redfish will follow pretty much all links to the resources in the Redfish tree and build objects from it, even if you only need to get a single one (say one System, which represents a "Node" in Ironic).
One thing that I've learned working in Ironic is that BMCs are fragile, I worry about the way things are architected in python-redfish because a simple connect could hammer the BMC with many requests at once, the more resources you have, say 1000 resources (between Systems, Managers and Chassis), this is going to be 20000+ requests at startup (Note, this is just an approximately number, keep reading.)
Back to [0], the example I'm using here contains only 1 System, 1 Chassis and 1 Manager [2]. This is enough for python-redfish to send 21 requests [3] and produce 1000+ lines of debug code (mostly for dumping the representation of the objects it creates) at the very first connect().
With the simulator this is not a problem, but I'm afraid that with a real piece of hardware this is going to be problematic.
[0] https://bugs.launchpad.net/python-redfish/+bug/1662896
[1] For example:
import redfish
redfish.connect(...)
[2] http://paste.openstack.org/show/598363/
[3] http://paste.openstack.org/show/598366/
More info:
----------
The tests are running the Redfish simulator version 1.0.0 (DSP2043), direct link: https://www.dmtf.org/sites/default/files/standards/documents/DSP2043_1.0.0.zip
With the mockup server: https://github.com/DMTF/Redfish-Mockup-Server/blob/master/redfishMockupServer.py |
|
| 2017-02-10 18:56:29 |
Lucas Alvares Gomes |
description |
This bug is related to [0] which points out that python-redfish is extremely verbose, perhaps, this one describes the reason for that.
Basically, as soon as you invoke connect()[1] python-redfish will follow pretty much all links to the resources in the Redfish tree and build objects from it, even if you only need to get a single one (say one System, which represents a "Node" in Ironic).
One thing that I've learned working in Ironic is that BMCs are fragile, I worry about the way things are architected in python-redfish because a simple connect could hammer the BMC with many requests at once, the more resources you have, say 1000 resources (between Systems, Managers and Chassis), this is going to be 20000+ requests at startup (Note, this is just an approximately number, keep reading.)
Back to [0], the example I'm using here contains only 1 System, 1 Chassis and 1 Manager [2]. This is enough for python-redfish to send 21 requests [3] and produce 1000+ lines of debug code (mostly for dumping the representation of the objects it creates) at the very first connect().
With the simulator this is not a problem, but I'm afraid that with a real piece of hardware this is going to be problematic.
[0] https://bugs.launchpad.net/python-redfish/+bug/1662896
[1] For example:
import redfish
redfish.connect(...)
[2] http://paste.openstack.org/show/598363/
[3] http://paste.openstack.org/show/598366/
More info:
----------
The tests are running the Redfish simulator version 1.0.0 (DSP2043), direct link: https://www.dmtf.org/sites/default/files/standards/documents/DSP2043_1.0.0.zip
With the mockup server: https://github.com/DMTF/Redfish-Mockup-Server/blob/master/redfishMockupServer.py |
This bug is related to [0] which points out that python-redfish is extremely verbose, perhaps, this one describes the reason for that.
Basically, as soon as you invoke connect()[1] python-redfish will follow pretty much all links to the resources in the Redfish tree and build objects from it, even if you only need to get a single one (say one System, which represents a "Node" in Ironic).
One thing that I've learned working in Ironic is that BMCs are fragile, I worry about the way things are architected in python-redfish because a simple connect could hammer the BMC with many requests at once, the more resources you have, say 1000 resources (between Systems, Managers and Chassis), this is going to be 7000+ requests at startup (Note, this is just an approximately number, keep reading.)
Back to [0], the example I'm using here contains only 1 System, 1 Chassis and 1 Manager [2]. This is enough for python-redfish to send 21 requests [3] and produce 1000+ lines of debug code (mostly for dumping the representation of the objects it creates) at the very first connect().
With the simulator this is not a problem, but I'm afraid that with a real piece of hardware this is going to be problematic.
[0] https://bugs.launchpad.net/python-redfish/+bug/1662896
[1] For example:
import redfish
redfish.connect(...)
[2] http://paste.openstack.org/show/598363/
[3] http://paste.openstack.org/show/598366/
More info:
----------
The tests are running the Redfish simulator version 1.0.0 (DSP2043), direct link: https://www.dmtf.org/sites/default/files/standards/documents/DSP2043_1.0.0.zip
With the mockup server: https://github.com/DMTF/Redfish-Mockup-Server/blob/master/redfishMockupServer.py |
|
| 2017-02-11 13:09:19 |
Uggla |
python-redfish: status |
New |
Triaged |
|
| 2017-02-28 10:57:09 |
Bruno Cornec |
python-redfish: milestone |
|
0.6 |
|
