David Chung

## Motivation - We want to have a scalable way of managing multiple groups (each with its own group config JSON) as well as other resource types (e.g. load balancers)...

Addressed the point on automating plugin activation. It's implicit but was not called out explicitly in the doc. I don't think this is any more cumbersome than a single JSON...

Updated the doc to make clear that a `config.json` is the _whole_ config, as seen in the documentation of the plugins. I am not proposing to split up fields or...

A PR #283 is a start to address this. The manager should be the entity that handles this, in terms of roles and responsibility.

PR #283 is merged -- this is the start of a single frontend. Note its data model at [manager/spec.go](https://github.com/docker/infrakit/blob/master/manager/spec.go) has the notions of multiple groups.

There's been some confusion on this e.g. https://twitter.com/makerspherehq/status/881540385360752645 A worked example will be coming soon.

@anarcher @YujiOshima 1. The semantics of `Instance.Provision` is to provision one instance at a time. Using an instance plugin that wraps an AWS ASG (autoscaling group) would be confusing because...

A big thank you to @YujiOshima for #332. This PR addresses the issue of rate limited provider API calls and makes the default group plugin useable for managing large groups...

I have some ideas about the points you've raised. They are all very insightful and valuable feedback. Thank you @anarcher > Instance creation will create costs. If the problem is...

@kaufers - I think if you label the initial manager with a label `bootstrap`, the group controller will essentially assimilate it and considers it a member of the group and...