Re: [openstack-dev] [Ironic] disambiguating the term "discovery"

2014-11-13 Thread Dmitry Tantsur
: Dmitry Tantsur [mailto:dtant...@redhat.com] Sent: Thursday, November 13, 2014 2:20 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Ironic] disambiguating the term "discovery" On 11/12/2014 10:47 PM, Victor Lowther wrote: Hmmm... with this thread in mind, anyone

Re: [openstack-dev] [Ironic] disambiguating the term "discovery"

2014-11-13 Thread Lucas Alvares Gomes
dtant...@redhat.com] > Sent: Thursday, November 13, 2014 2:20 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Ironic] disambiguating the term "discovery" > > On 11/12/2014 10:47 PM, Victor Lowther wrote: >> Hmmm... with this thread in mind, anyon

Re: [openstack-dev] [Ironic] disambiguating the term "discovery"

2014-11-13 Thread Ganapathy, Sandhya
-level-node-discovery Thanks, Sandhya. -Original Message- From: Dmitry Tantsur [mailto:dtant...@redhat.com] Sent: Thursday, November 13, 2014 2:20 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Ironic] disambiguating the term "discovery" On 11/12/201

Re: [openstack-dev] [Ironic] disambiguating the term "discovery"

2014-11-13 Thread Dmitry Tantsur
On 11/12/2014 10:47 PM, Victor Lowther wrote: Hmmm... with this thread in mind, anyone think that changing DISCOVERING to INTROSPECTING in the new state machine spec is a good idea? As before I'm uncertain. Discovery is a troublesome term, but too many people use and recognize it, while IMO intr

Re: [openstack-dev] [Ironic] disambiguating the term "discovery"

2014-11-12 Thread Lucas Alvares Gomes
Just for reference, the spec is this one: https://review.openstack.org/#/c/133828/ That's a good point, I think it's important to have this distinction of a new node being discovered and a registered node being introspected/interrogated. So I'm +1 for the idea. On Wed, Nov 12, 2014 at 9:47 PM, Vi

Re: [openstack-dev] [Ironic] disambiguating the term "discovery"

2014-11-12 Thread Victor Lowther
Hmmm... with this thread in mind, anyone think that changing DISCOVERING to INTROSPECTING in the new state machine spec is a good idea? On Mon, Nov 3, 2014 at 4:29 AM, Ganapathy, Sandhya wrote: > Hi all, > > Following the mail thread on disambiguating the term 'discovery' - > > In the lines of w

Re: [openstack-dev] [Ironic] disambiguating the term "discovery"

2014-11-03 Thread Ganapathy, Sandhya
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 a

Re: [openstack-dev] [Ironic] disambiguating the term "discovery"

2014-10-22 Thread Lucas Alvares Gomes
On Tue, Oct 21, 2014 at 6:29 PM, Stuart Fox wrote: > Having written/worked on a few DC automation tools, Ive typically broken > down the process of getting unknown hardware into production in to 4 > distinct stages. > 1) Discovery (The discovery of unknown hardware) > 2) Normalising (Push initial

Re: [openstack-dev] [Ironic] disambiguating the term "discovery"

2014-10-21 Thread Devananda van der Veen
On Tue, Oct 21, 2014 at 11:26 AM, Adam Lawson wrote: > I fully and wholeheartedly agree that inventory management is out of scope > of Ironic. But I have a small suggestion: > > We'd do well as a community to adopt/evangelize an informal rule which I > enforce at work (because I see this happen a

Re: [openstack-dev] [Ironic] disambiguating the term "discovery"

2014-10-21 Thread Adam Lawson
I fully and wholeheartedly agree that inventory management is out of scope of Ironic. But I have a small suggestion: We'd do well as a community to adopt/evangelize an informal rule which I enforce at work (because I see this happen a lot when brainstorming with cross-project goals); we cannot say

Re: [openstack-dev] [Ironic] disambiguating the term "discovery"

2014-10-21 Thread Stuart Fox
Having written/worked on a few DC automation tools, Ive typically broken down the process of getting unknown hardware into production in to 4 distinct stages. 1) Discovery (The discovery of unknown hardware) 2) Normalising (Push initial configs like drac/imm/ilo settings, flashing to known good fir

Re: [openstack-dev] [Ironic] disambiguating the term "discovery"

2014-10-21 Thread Lucas Alvares Gomes
On Tue, Oct 21, 2014 at 10:27 AM, Sam Betts (sambetts) wrote: > I agree with Devananda's definition of Œhardware discovery¹ and other > tools similar to Ironic use the term discovery in this way, however I have > found that these other tools often bundle the gathering of the system > properties to

Re: [openstack-dev] [Ironic] disambiguating the term "discovery"

2014-10-21 Thread Sam Betts (sambetts)
I agree with Devananda's definition of Œhardware discovery¹ and other tools similar to Ironic use the term discovery in this way, however I have found that these other tools often bundle the gathering of the system properties together with the discovery of the hardware as a single step from a user

Re: [openstack-dev] [Ironic] disambiguating the term "discovery"

2014-10-21 Thread Lucas Alvares Gomes
+1 for the separation I already gave up of the term "discovery" as you can see on the DRAC Hardware Introspection[1] spec, I also don't think that "introspection" is the best word for that (we already use the world "cloud" for OpenStack so it can't get more confusing than that). Perhaps "interroga

Re: [openstack-dev] [Ironic] disambiguating the term "discovery"

2014-10-21 Thread Dmitry Tantsur
On 10/21/2014 02:11 AM, Devananda van der Veen wrote: Hi all, I was reminded in the Ironic meeting today that the words "hardware discovery" are overloaded and used in different ways by different people. Since this is something we are going to talk about at the summit (again), I'd like to start

Re: [openstack-dev] [Ironic] disambiguating the term "discovery"

2014-10-20 Thread Monty Taylor
On 10/20/2014 07:11 PM, Devananda van der Veen wrote: > Hi all, > > I was reminded in the Ironic meeting today that the words "hardware > discovery" are overloaded and used in different ways by different > people. Since this is something we are going to talk about at the > summit (again), I'd like