Good questions!
Jay, I have a request for some clarification in-line.
On 10/01/2014 01:37 PM, Jay Pipes wrote:
Hi Akihiro!
IMO, this is precisely where having an API standards working group can
help to make the user experience of our public APIs less frustrating.
Such a working group
[Lurker popping up to get whacked :-)]
both State (admin_state_up) and Status² are usually used in Neutron
resources...
but it seems the meaning of State and Status are reversed...
I am really confused what is the right usage of these words
state: the particular condition that someone or
On 10/02/2014 11:23 AM, Jay S. Bryant wrote:
As I re-read this I think maybe you have answered my question but want
to be clear. You feel that 'State' is the only term that should be
used. Based on the definitions above, that would make sense. The
complication is there are may places in the
On 10/02/2014 11:14 AM, Jay Pipes wrote:
On 10/02/2014 11:23 AM, Jay S. Bryant wrote:
As I re-read this I think maybe you have answered my question but want
to be clear. You feel that 'State' is the only term that should be
used. Based on the definitions above, that would make sense. The
On 10/01/2014 12:37 PM, Jay Pipes wrote:
IMO, the term state should be the only one used in the OpenStack APIs
to refer to the condition of some thing at a point in time. The term
state can and should be prefaced with a refining descriptor such
task or power to denote the *thing* that the state
On 10/02/2014 03:14 PM, Chris Friesen wrote:
On 10/01/2014 12:37 PM, Jay Pipes wrote:
IMO, the term state should be the only one used in the OpenStack APIs
to refer to the condition of some thing at a point in time. The term
state can and should be prefaced with a refining descriptor such
task
On 10/02/2014 01:47 PM, Jay Pipes wrote:
On 10/02/2014 03:14 PM, Chris Friesen wrote:
On 10/01/2014 12:37 PM, Jay Pipes wrote:
IMO, the term state should be the only one used in the OpenStack APIs
to refer to the condition of some thing at a point in time. The term
state can and should be
In other words, all our APIs would look like the Neutron API as it exists
today.
That's a bad comparison because the Neutron API doesn't have a standard
that it follows at all. If there was a standard for states/statuses that
Neutron was following for all of the objects, the status of the Neutron
Hi,
# The first half is related to Horizon and the latter half is about
the wording in Nova and Neutron API.
During Horizon translation for Juno, I noticed the words State and
Status in multiple contexts. Sometimes they are in very similar
contexts and sometimes they have different contexts.
I
Hi Akihiro!
IMO, this is precisely where having an API standards working group can
help to make the user experience of our public APIs less frustrating.
Such a working group should have the ability to vet terms like state
vs status and ensure consistency across the public APIs.
More
10 matches
Mail list logo
