Re: [openstack-dev] [ironic] Extending python-dracclient to fetch System/iDrac resources

2016-09-14 Thread Anish Bhatt
mgo...@redhat.com] > Sent: Wednesday, September 14, 2016 7:46 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [ironic] Extending python-dracclient to fetch > System/iDrac resources > > On 13/09/16 20:30, Anish Bhatt wrote: >

Re: [openstack-dev] [ironic] Extending python-dracclient to fetch System/iDrac resources

2016-09-14 Thread Christopher.Dearborn
M To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [ironic] Extending python-dracclient to fetch System/iDrac resources On 13/09/16 20:30, Anish Bhatt wrote: > Is parsing iDrac/System attributes differently from BIOS attributes > the correct approach

Re: [openstack-dev] [ironic] Extending python-dracclient to fetch System/iDrac resources

2016-09-14 Thread Miles Gould
On 13/09/16 20:30, Anish Bhatt wrote: Is parsing iDrac/System attributes differently from BIOS attributes the correct approach here (this will also make it match racadm output), or should I be changing all Attributes to be parsed the same way ? "Parse everything the same way" sounds like the si

[openstack-dev] [ironic] Extending python-dracclient to fetch System/iDrac resources

2016-09-13 Thread Anish Bhatt
I'm extending python-dracclient to pull in iDrac & System resources (DCIM_iDRACCard* & DCIM_System*). The way DCIM_BIOS* attributes work right now, only AttributeName, current_value, pending_value and read_only status are parsed. However, this approach does not work with iDRAC or System attributes