Hi John,
Sorry for the late response. I was completely tied up with something.
I agree with your comments on the use cases.
Once there are the use cases, given all the Config vs API debates, I
would look at the pure data flow, in a Config/API agnostic way.
Agreeing the info needed from the
? 2014?04?10? 15:59, Irena Berezovsky ??:
Hi Robert,
Thanks a lot the inputs you posted in the doc.
I have raised there few questions and added use case for High
Availability.
Another concern I have is regarding the assumption that there is no
case to mix different vendor cards in the
I think writing this up as a nova-spec is going to make this process
much easier:
https://wiki.openstack.org/wiki/Blueprints#Nova
It will save you having to re-write your document once you want to
submit a blueprint, and we can all see each others comments in gerrit,
and more clearly see how
于 2014年04月10日 16:28, John Garbutt 写道:
I think writing this up as a nova-spec is going to make this process
much easier:
https://wiki.openstack.org/wiki/Blueprints#Nova
It will save you having to re-write your document once you want to
submit a blueprint, and we can all see each others
Apologies, that came out all wrong...
On 10 April 2014 09:28, John Garbutt j...@johngarbutt.com wrote:
I think writing this up as a nova-spec is going to make this process
much easier:
https://wiki.openstack.org/wiki/Blueprints#Nova
It will save you having to re-write your document once you
于 2014年04月10日 16:40, John Garbutt 写道:
Apologies, that came out all wrong...
On 10 April 2014 09:28, John Garbutt j...@johngarbutt.com wrote:
I think writing this up as a nova-spec is going to make this process
much easier:
https://wiki.openstack.org/wiki/Blueprints#Nova
It will save you
