Re: [openstack-dev] [nova] jsonschema for scheduler hints

On 12/08/2015 11:47 PM, Ken'ichi Ohmichi wrote: > Hi Sylvain, > > 2015-12-04 17:48 GMT+09:00 Sylvain Bauza : >>> >>> That leaves the out-of-tree discussion about custom filters and how we >>> could have a consistent behaviour given that. Should we accept something in >>> a

Re: [openstack-dev] [nova] jsonschema for scheduler hints

2015-12-09 21:20 GMT+09:00 Sean Dague : > On 12/08/2015 11:47 PM, Ken'ichi Ohmichi wrote: >> Hi Sylvain, >> >> 2015-12-04 17:48 GMT+09:00 Sylvain Bauza : That leaves the out-of-tree discussion about custom filters and how we could have a consistent

Re: [openstack-dev] [nova] jsonschema for scheduler hints

On 12/06/15 at 02:49pm, Ken'ichi Ohmichi wrote: Hi Sean, 2015-12-02 23:23 GMT+09:00 Sean Dague : We have previously agreed that scheduler hints in Nova are an open ended thing. It's expected for sites to have additional scheduler filters which expose new hints. The way we

Re: [openstack-dev] [nova] jsonschema for scheduler hints

Le 08/12/2015 21:23, Andrew Laski a écrit : On 12/06/15 at 02:49pm, Ken'ichi Ohmichi wrote: Hi Sean, 2015-12-02 23:23 GMT+09:00 Sean Dague : We have previously agreed that scheduler hints in Nova are an open ended thing. It's expected for sites to have additional scheduler

Re: [openstack-dev] [nova] jsonschema for scheduler hints

On 12/08/15 at 09:43pm, Sylvain Bauza wrote: Le 08/12/2015 21:23, Andrew Laski a écrit : On 12/06/15 at 02:49pm, Ken'ichi Ohmichi wrote: Hi Sean, 2015-12-02 23:23 GMT+09:00 Sean Dague : We have previously agreed that scheduler hints in Nova are an open ended thing. It's

Re: [openstack-dev] [nova] jsonschema for scheduler hints

2015-12-09 6:02 GMT+09:00 Andrew Laski : >> >> I'm fine with a new RPC call for getting the schema, but as I explained, I >> think the schema should be accepting all the in-tree filter hints (ie. >> nova.scheduler.filters.all_filters method), not only those which are enabled >>

Re: [openstack-dev] [nova] jsonschema for scheduler hints

Hi Sylvain, 2015-12-04 17:48 GMT+09:00 Sylvain Bauza : >> >> That leaves the out-of-tree discussion about custom filters and how we >> could have a consistent behaviour given that. Should we accept something in >> a specific deployment while another deployment could 401 against

Re: [openstack-dev] [nova] jsonschema for scheduler hints

2015-12-04 16:48 GMT+08:00 Sylvain Bauza : > > > Le 04/12/2015 04:21, Alex Xu a écrit : > > > > 2015-12-02 23:12 GMT+08:00 Sylvain Bauza : > >> >> >> Le 02/12/2015 15:23, Sean Dague a écrit : >> >>> We have previously agreed that scheduler hints in Nova are

Re: [openstack-dev] [nova] jsonschema for scheduler hints

Hi Sean, 2015-12-02 23:23 GMT+09:00 Sean Dague : > We have previously agreed that scheduler hints in Nova are an open ended > thing. It's expected for sites to have additional scheduler filters > which expose new hints. The way we handle that with our strict > jsonschema is that

Re: [openstack-dev] [nova] jsonschema for scheduler hints

Le 04/12/2015 04:21, Alex Xu a écrit : 2015-12-02 23:12 GMT+08:00 Sylvain Bauza >: Le 02/12/2015 15:23, Sean Dague a écrit : We have previously agreed that scheduler hints in Nova are an open ended thing. It's

Re: [openstack-dev] [nova] jsonschema for scheduler hints

2015-12-02 23:12 GMT+08:00 Sylvain Bauza : > > > Le 02/12/2015 15:23, Sean Dague a écrit : > >> We have previously agreed that scheduler hints in Nova are an open ended >> thing. It's expected for sites to have additional scheduler filters >> which expose new hints. The way we

Re: [openstack-dev] [nova] jsonschema for scheduler hints

Le 02/12/2015 15:23, Sean Dague a écrit : We have previously agreed that scheduler hints in Nova are an open ended thing. It's expected for sites to have additional scheduler filters which expose new hints. The way we handle that with our strict jsonschema is that we allow additional