----- Original Message ----- > > The UI will also need to be able to look at the Heat resources running > > within the overcloud stack and classify them according to a resource > > category. How do you envision that working? > > There's a way in a Heat template to specify arbitrary metadata on a > resource. We can add flags in there and key off of those. That seems reasonable, but I wonder - given a resource in a template, how do we know what category metadata needs to be set? Is it simply based off the resource name? If that's the case, couldn't we use that name <-> category mapping directly, without the need to set metadata? Mainn > >> Next steps for me are to start to work on the Tuskar APIs around > >> Resource Category CRUD and their conversion into a Heat template. > >> There's some discussion to be had there as well, but I don't want to put > >> too much into one e-mail. > >> > > > > I'm looking forward to seeing the API specification, as Resource Category > > CRUD is currently a big unknown in the tuskar-ui api.py file. > > > > > > Mainn > > > > > >> > >> Thoughts? > >> > >> _______________________________________________ > >> OpenStack-dev mailing list > >> OpenStack-dev at lists.openstack.org > >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >> > > > > _______________________________________________ > > OpenStack-dev mailing list > > OpenStack-dev at lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >