> On Jan 22, 2014, at 4:02 AM, Jaromir Coufal <jcou...@redhat.com> wrote: > > > > > > > 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? > > Yeah, great question Jarda. When I test out the “Stacks” functionality in > Horizon the user doesn’t create a Stack that spins up resources, it spins up > instances. Maybe there is a difference around the terms being used behind > the scenes and in Horizon?
Maybe we're looking at different parts of the UI, but when I look at a Stack detail page in Horizon, I see a tab for Resources, and not Instances. The resource table might link to an Instance, but that information is retrieved from the Resource. Mainn > Liz > > > > > -- 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 > _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
