On 12/06/2013 09:39 PM, Tzu-Mainn Chen wrote:
Thanks for the comments and questions! I fully expect that this list of
requirements
will need to be fleshed out, refined, and heavily modified, so the more the
merrier.
Comments inline:
*** Requirements are assumed to be targeted for
So the question is are we looking at /nodes/ that have a /current
role/, or are we looking at /roles/ that have some /current nodes/.
My contention is that the role is the interesting thing, and the nodes
is the incidental thing. That is, as a sysadmin, my hierarchy of
concerns is something
Along the same lines and while we're talking crazy ideas, one use case
where a user might want to allocate entire nodes would be if TripleO
were used to manage an ARM rack. The use cases aren't identical between
cloud and ARM, but they are similar.
So for a rack of 1000 nodes, there is
a) Because we're essentially doing a tear-down and re-build of the
whole architecture (a lot of the concepts in tuskar
will simply disappear), it's difficult to do small incremental patches
that support existing functionality. Is it okay
to have patches that break functionality? Are there good
On 12/06/2013 12:26 PM, Clint Byrum wrote:
Excerpts from Robert Collins's message of 2013-12-03 23:12:39 -0800:
Hi,
like most OpenStack projects we need to keep the core team up to
date: folk who are not regularly reviewing will lose context over
time, and new folk who have been reviewing
Disclaimer: I'm very new to the project, so apologies if some of my
questions have been already answered or flat out don't make sense.
As I proofread, some of my comments may drift a bit past basic
requirements, so feel free to tell me to take certain questions out of
this thread into
On 12/05/2013 08:38 AM, James Slagle wrote:
On Wed, Dec 4, 2013 at 5:19 PM, Robert Collins
robe...@robertcollins.net wrote:
This is a follow up to https://review.openstack.org/59621 to get
broader discussion..
So at the moment we capture a bunch of details in the image - what
parameters the
101 - 107 of 107 matches
Mail list logo