Re: [openstack-dev] [nova][policy] Exposing hypervisor details to users

On Fri, Nov 06, 2015 at 05:08:59PM +1100, Tony Breeds wrote: > 4. Create a capabilitioes API of some description, that can be queried so > that > consumers (horizon) can known Thanks everyone for the input. I'm going to go with the simple first step that Sean described as it seesm liek the

Re: [openstack-dev] [nova][policy] Exposing hypervisor details to users

Excerpts from Tony Breeds's message of 2015-11-05 22:08:59 -0800: > Hello all, > I came across [1] which is notionally an ironic bug in that horizon > presents > VM operations (like suspend) to users. Clearly these options don't make sense > to ironic which can be confusing. > > There is a

Re: [openstack-dev] [nova][policy] Exposing hypervisor details to users

Le 06/11/2015 07:08, Tony Breeds a écrit : Hello all, I came across [1] which is notionally an ironic bug in that horizon presents VM operations (like suspend) to users. Clearly these options don't make sense to ironic which can be confusing. There is a horizon fix that just disables

Re: [openstack-dev] [nova][policy] Exposing hypervisor details to users

On Fri, Nov 06, 2015 at 05:08:59PM +1100, Tony Breeds wrote: > Hello all, > I came across [1] which is notionally an ironic bug in that horizon > presents > VM operations (like suspend) to users. Clearly these options don't make sense > to ironic which can be confusing. > > There is a

Re: [openstack-dev] [nova][policy] Exposing hypervisor details to users

Quoting Clint Byrum (2015-11-06 09:07:20) > Whether they are VMs or real machines, our tools > should strive to be about the user and their workload, and not about the > operator and their technology. +1 This should be in a poster in every office. Ghe Rivero

Re: [openstack-dev] [nova][policy] Exposing hypervisor details to users

On 6 November 2015 at 14:09, Sean Dague wrote: > On 11/06/2015 08:44 AM, Alex Xu wrote: >> >> >> 2015-11-06 20:59 GMT+08:00 Sean Dague > >: >> >> On 11/06/2015 07:28 AM, John Garbutt wrote: >> > On 6 November 2015 at 12:09, Sean

Re: [openstack-dev] [nova][policy] Exposing hypervisor details to users

On Fri, Nov 06, 2015 at 07:09:59AM -0500, Sean Dague wrote: > On 11/06/2015 04:49 AM, Daniel P. Berrange wrote: > > > > I think that exposing hypervisor_type is very much the *wrong* approach > > to this problem. The set of allowed actions varies based on much more than > > just the

Re: [openstack-dev] [nova][policy] Exposing hypervisor details to users

On 6 November 2015 at 12:09, Sean Dague wrote: > On 11/06/2015 04:49 AM, Daniel P. Berrange wrote: >> On Fri, Nov 06, 2015 at 05:08:59PM +1100, Tony Breeds wrote: >>> Hello all, >>> I came across [1] which is notionally an ironic bug in that horizon >>> presents >>> VM

Re: [openstack-dev] [nova][policy] Exposing hypervisor details to users

On 11/06/2015 07:28 AM, John Garbutt wrote: > On 6 November 2015 at 12:09, Sean Dague wrote: >> On 11/06/2015 04:49 AM, Daniel P. Berrange wrote: >>> On Fri, Nov 06, 2015 at 05:08:59PM +1100, Tony Breeds wrote: Hello all, I came across [1] which is notionally an

Re: [openstack-dev] [nova][policy] Exposing hypervisor details to users

On 11/06/2015 07:46 AM, Daniel P. Berrange wrote: > On Fri, Nov 06, 2015 at 07:09:59AM -0500, Sean Dague wrote: >> On 11/06/2015 04:49 AM, Daniel P. Berrange wrote: >>> >>> I think that exposing hypervisor_type is very much the *wrong* approach >>> to this problem. The set of allowed actions

Re: [openstack-dev] [nova][policy] Exposing hypervisor details to users

On 6 November 2015 at 09:49, Daniel P. Berrange wrote: > On Fri, Nov 06, 2015 at 05:08:59PM +1100, Tony Breeds wrote: >> Hello all, >> I came across [1] which is notionally an ironic bug in that horizon >> presents >> VM operations (like suspend) to users. Clearly these

Re: [openstack-dev] [nova][policy] Exposing hypervisor details to users

On 11/06/2015 08:44 AM, Alex Xu wrote: > > > 2015-11-06 20:59 GMT+08:00 Sean Dague >: > > On 11/06/2015 07:28 AM, John Garbutt wrote: > > On 6 November 2015 at 12:09, Sean Dague > wrote: > >> On

Re: [openstack-dev] [nova][policy] Exposing hypervisor details to users

On 11/06/2015 04:49 AM, Daniel P. Berrange wrote: > On Fri, Nov 06, 2015 at 05:08:59PM +1100, Tony Breeds wrote: >> Hello all, >> I came across [1] which is notionally an ironic bug in that horizon >> presents >> VM operations (like suspend) to users. Clearly these options don't make >>

Re: [openstack-dev] [nova][policy] Exposing hypervisor details to users

2015-11-06 20:59 GMT+08:00 Sean Dague : > On 11/06/2015 07:28 AM, John Garbutt wrote: > > On 6 November 2015 at 12:09, Sean Dague wrote: > >> On 11/06/2015 04:49 AM, Daniel P. Berrange wrote: > >>> On Fri, Nov 06, 2015 at 05:08:59PM +1100, Tony Breeds wrote: >

Re: [openstack-dev] [nova][policy] Exposing hypervisor details to users

+1 this would definitely be the best approach from Horizon's perspective since we can cache the capabilities per-flavour. Having to request capabilities per-instance would be an unreasonable burden on the poor users of Horizon. On 6 November 2015 at 23:09, Sean Dague wrote: > On

[openstack-dev] [nova][policy] Exposing hypervisor details to users

Hello all, I came across [1] which is notionally an ironic bug in that horizon presents VM operations (like suspend) to users. Clearly these options don't make sense to ironic which can be confusing. There is a horizon fix that just disables migrate/suspened and other functaions if the