Re: [openstack-dev] [TripleO] Encapsulating logic and state in the client

2015-08-25 Thread Dougal Matthews
- Original Message - > From: "Jay Dobies" > To: openstack-dev@lists.openstack.org > Sent: Tuesday, 25 August, 2015 2:31:02 PM > Subject: Re: [openstack-dev] [TripleO] Encapsulating logic and state in the > client > > > Thinking about this further, the

Re: [openstack-dev] [TripleO] Encapsulating logic and state in the client

2015-08-25 Thread Jay Dobies
Thinking about this further, the interesting question to me is how much logic we aim to encapsulate behind an API. For example, one of the simpler CLI commands we have in RDO-Manager (which is moving upstream[1]) is to run introspection on all of the Ironic nodes. This involves a series of command

Re: [openstack-dev] [TripleO] Encapsulating logic and state in the client

2015-08-25 Thread Dougal Matthews
- Original Message - > From: "Zane Bitter" > To: "OpenStack Development Mailing List" > Sent: Monday, 17 August, 2015 5:25:36 PM > Subject: [openstack-dev] [TripleO] Encapsulating logic and state in the > client > > It occurs to me that t

Re: [openstack-dev] [TripleO] Encapsulating logic and state in the client

2015-08-18 Thread Dougal Matthews
- Original Message - > From: "Zane Bitter" > To: "OpenStack Development Mailing List" > Sent: Monday, 17 August, 2015 5:25:36 PM > Subject: [openstack-dev] [TripleO] Encapsulating logic and state in the > client > > It occurs to me that t

Re: [openstack-dev] [TripleO] Encapsulating logic and state in the client

2015-08-18 Thread Zane Bitter
On 18/08/15 02:33, Clint Byrum wrote: Excerpts from Zane Bitter's message of 2015-08-17 09:25:36 -0700: It occurs to me that there has never been a detailed exposition of the purpose of the tripleo-common library here, and that this might be a good time to rectify that. Basically, there are two

Re: [openstack-dev] [TripleO] Encapsulating logic and state in the client

2015-08-17 Thread Clint Byrum
Excerpts from Zane Bitter's message of 2015-08-17 09:25:36 -0700: > It occurs to me that there has never been a detailed exposition of the > purpose of the tripleo-common library here, and that this might be a > good time to rectify that. > > Basically, there are two things that it sucks to have

Re: [openstack-dev] [TripleO] Encapsulating logic and state in the client

2015-08-17 Thread Tzu-Mainn Chen
- Original Message - > It occurs to me that there has never been a detailed exposition of the > purpose of the tripleo-common library here, and that this might be a > good time to rectify that. > > Basically, there are two things that it sucks to have in the client: > > First, logic - tha

[openstack-dev] [TripleO] Encapsulating logic and state in the client

2015-08-17 Thread Zane Bitter
It occurs to me that there has never been a detailed exposition of the purpose of the tripleo-common library here, and that this might be a good time to rectify that. Basically, there are two things that it sucks to have in the client: First, logic - that is, any code that is not related to th