constraints call notes/proposals/sync

[roger peppe]

On 8 February 2013 14:32, Gustavo Niemeyer
<gustavo.niemeyer at canonical.com> wrote:
> My most critical suggestion is this: start working on something
> simple, and do not mangle the data. In other words, don't compute a
> magic set of constraints based on some clever algorithm and ignore
> what the user originally provided, but instead store thing store the
> data as the user inputs it (no "computed constraints" in the
> database). You can start with non-polemic settings, such as mem and
> cores. If you do that, you can easily evolve from a trivial algorithm
> to a better one, and not get stuck on this kind of discussion forever.

emphatic +1 to this.

let's start simple and ignore provider-specific constraints for
the time being.