Dear All,
In one of the Ironic IRC meetings, a discussion on whether to retain the
'Chassis' element in Ironic or not came up.
I am interested to know whether this is still valid and a decision is to be
made on whether the component is retained or not.
Thanks,
Sandhya
Hi All,
I would like to discuss the Chassis Discovery Tool Blueprint -
https://review.openstack.org/#/c/134866/
The blueprint suggests Hardware enrollment and introspection for properties at
the Chassis layer. Suitable for micro-servers that have an active chassis to
query for details.
. So count me
as -0 on this.
On Mon, Nov 3, 2014 at 4:29 AM, Ganapathy, Sandhya
sandhya.ganapa...@hp.com mailto:sandhya.ganapa...@hp.com wrote:
Hi all,
Following the mail thread on disambiguating the term 'discovery' -
In the lines of what Devananda had stated, Hardware
Hi all,
Following the mail thread on disambiguating the term 'discovery' -
In the lines of what Devananda had stated, Hardware Introspection also means
retrieving and storing hardware details of the node whose credentials and IP
Address are known to the system. (Correct me if I am wrong).
I
Hi,
This is to discuss Bug #1231298 - https://bugs.launchpad.net/cinder/+bug/1231298
Bug description : When one creates a volume from a snapshot or another volume,
the size argument is calculated automatically. In the case of an image it needs
to be specified though, for something larger than
Hi,
I just need a suggestion to fix this bug.
Link to the bug : https://bugs.launchpad.net/nova/+bug/1224972
This bug says that the name of the volume is not set when an instance is booted
from a new volume giving image as the source.
Fix for this bug could be at the Nova side wherein we
