> -----Original Message----- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: Tuesday, May 2, 2017 5:59 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [nova-scheduler] Get scheduler hint > > On 05/02/2017 12:33 PM, Giuseppe Di Lena wrote: > > Thank you a lot! :-). > > Actually, we are also working in parallel to implement the algorithm > with tacker, but for this project we will only use the basic modules in > OpenStack and Heat. [Mooney, Sean K] if you can use heat you can use the server anti affinity filter To create a server group per port-pair group and ensure that two instance of the same port-pair-group do not reside on the same server. You could also use heat's/senlin's Scaling groups to define the insantce count of each SF in the chain. There was a presentation on this in Barcelona https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/15037/on-building-an-auto-healing-resource-cluster-using-senlin https://www.youtube.com/watch?v=bmdU_m6vRZc But as jay says below it depends on what you are trying to solve. If you are trying to model ha constraints for a service chain the above may Help however it is likely outside the scope of nova/placement api to support this directly.
> > > > If the scheduler hints are no longer supported, what is the correct > way to give the scheduler personalized input with the instance details? > > Best regards Giuseppe > > Again, it depends on what problem you are trying to solve with this > personalized input... what would the scheduler do with the length of > the service chain as an input? What are you attempting to solve? > > Best, > -jay > > _______________________________________________________________________ > ___ > 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