That's a fair question; I'd argue that it *should* be resources. When we update an overcloud deployment, it'll create additional resources.
Mainn ----- Original Message ----- > > > On 2014/22/01 00:56, Tzu-Mainn Chen wrote: > > Hiya - Resource is actually a Heat term that corresponds to what we're > > deploying within > > the Overcloud Stack - i.e., if we specify that we want an Overcloud with 1 > > Controller > > and 3 Compute, Heat will create a Stack that contains 1 Controller and 3 > > Compute > > Resources. > > Then a quick question - why do we design deployment by > increasing/decreasing number of *instances* instead of resources? > > -- Jarda > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev