I would probably create a custom fact to identify which ones have sriov capable NICs and use that to selectively enable installation of the correct packages, setup aggregates, etc.
On Fri, Jun 24, 2016 at 7:19 AM, Sanjay Upadhyay <supad...@redhat.com> wrote: > Hello Folks, > > Wondering what is the best approach to dynamically generating info of SRIOV > capable hosts in a cluster? > > The problem is, user want to deploy sriov-nic-agent on compute nodes, with > mixed set of h/w configuration, ie set of compute nodes which do not have > SR-IOV nics and a set of nodes which have SR-IOV capable nics. > > From the perspective of nova, nova can spawn hosts requiring sr-iov via host > aggregation or flavors (scheduler_default_filters = > RamFilter,ComputeFilter,AvailabilityZoneFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter,PciPassthroughFilter > ) > > However, from puppet side, we should enable sriov nic agent only on the > nodes with sr-iov nics. What is the best approach to address this? > > regards > /sanjay > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
