Bogdan,
I mostly agree with you on this. The only data that might originate from a
node is discovery-related parameters, like CPU/disks/NICs architecture and
such.
However, at the moment the deployment data is partially generated at every
node (i.e. globals.yaml, override/plugins/* and some
On 04/01/2016 10:41 AM, Oleg Gelbukh wrote:
> Andrew,
>
> This is an excellent idea. It is apparently more efficient and
> error-proof to make the split not by the resulted data but at the time
> it is actually generated. We will play with this idea a little bit, and
> will come up with design
Andrew,
This is an excellent idea. It is apparently more efficient and error-proof
to make the split not by the resulted data but at the time it is actually
generated. We will play with this idea a little bit, and will come up with
design proposal shortly.
Meanwhile, please be informed that we
One of the problems we've faced with trying to plug-in ConfigDB is trying
to separate the cluster attributes from the node attributes in the
serialized output (ie astute.yaml)
I started talking with Alex S about how we could separate them after
astute.yaml is prepared trying to ensure which was
