- Original Message -
From: Jay Dobies jason.dob...@redhat.com
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 interesting question
- Original Message -
From: Zane Bitter zbit...@redhat.com
To: OpenStack Development Mailing List openstack-dev@lists.openstack.org
Sent: Monday, 17 August, 2015 5:25:36 PM
Subject: [openstack-dev] [TripleO] Encapsulating logic and state in the
client
It occurs to me
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
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 in
- Original Message -
From: Zane Bitter zbit...@redhat.com
To: OpenStack Development Mailing List openstack-dev@lists.openstack.org
Sent: Monday, 17 August, 2015 5:25:36 PM
Subject: [openstack-dev] [TripleO] Encapsulating logic and state in the
client
It occurs to me
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
- 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 - that is,
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
