Re: [Openstack-operators] nova_api resource_providers table issues on ocata

2018-10-17 Thread Sylvain Bauza
On Wed, Oct 17, 2018 at 12:56 AM Jay Pipes wrote: > On 10/16/2018 10:11 AM, Sylvain Bauza wrote: > > On Tue, Oct 16, 2018 at 3:28 PM Ignazio Cassano > > mailto:ignaziocass...@gmail.com>> wrote: > > > > Hi everybody, > > when on my ocata installation based on centos7 I update (only update

Re: [Openstack-operators] nova_api resource_providers table issues on ocata

2018-10-17 Thread Ignazio Cassano
Hello Sylvain, here the output of some selects: MariaDB [nova]> select host,hypervisor_hostname from compute_nodes; +--+-+ | host | hypervisor_hostname | +--+-+ | podto1-kvm01 | podto1-kvm01| | podto1-kvm02 | podto1-kvm

Re: [Openstack-operators] nova_api resource_providers table issues on ocata

2018-10-17 Thread Jay Pipes
On 10/17/2018 01:41 AM, Ignazio Cassano wrote: Hello Jay,  when I add a New compute node I run nova-manage cell_v2 discover host . IS it possible this command update the old host uuid in resource table? No, not unless you already had a nova-compute installed on a host with the exact same host

Re: [Openstack-operators] nova_api resource_providers table issues on ocata

2018-10-17 Thread Matt Riedemann
On 10/17/2018 9:13 AM, Ignazio Cassano wrote: Hello Sylvain, here the output of some selects: MariaDB [nova]> select host,hypervisor_hostname from compute_nodes; +--+-+ | host | hypervisor_hostname | +--+-+ | podto1-kvm01 | p

Re: [Openstack-operators] nova_api resource_providers table issues on ocata

2018-10-17 Thread Ignazio Cassano
Hello, I am sure we are not using nova-compute with duplicate names. As I told previously we tried on 3 differents openstack installations and we faced the same issue. Procedure used We have an openstack with 3 compute nodes : podto1-kvm01, podto1-kvm02, podto1-kvm03 1) install a new compute node (

Re: [Openstack-operators] nova_api resource_providers table issues on ocata

2018-10-17 Thread Ignazio Cassano
Hello, here the select you suggested: MariaDB [nova]> select * from shadow_services; Empty set (0,00 sec) MariaDB [nova]> select * from shadow_compute_nodes; Empty set (0,00 sec) As far as the upgrade tooling is concerned, we are using only yum update on old compute nodes to have same packages i

Re: [Openstack-operators] [openstack-dev] [horizon][nova][cinder][keystone][glance][neutron][swift] Horizon feature gaps

2018-10-17 Thread Matt Riedemann
On 10/17/2018 9:24 AM, Ivan Kolodyazhny wrote: As you may know, unfortunately, Horizon doesn't support all features provided by APIs. That's why we created feature gaps list [1]. I'd got a lot of great conversations with projects teams during the PTG and we tried to figure out what should be

[Openstack-operators] Glance Image Visibility Issue? - Non admin users can see private images from other tenants

2018-10-17 Thread Moore, Michael Dane (GSFC-720.0)[BUSINESS INTEGRA, INC.]
All, I’m seeing unexpected behavior in our Queens environment related to Glance image visibility. Specifically users who, based on my understanding of the visibility and ownership fields, should NOT be able to see or view the image. If I create a new image with openstack image create and speci

Re: [Openstack-operators] Glance Image Visibility Issue? - Non admin users can see private images from other tenants

2018-10-17 Thread iain MacDonnell
On 10/17/2018 12:29 PM, Moore, Michael Dane (GSFC-720.0)[BUSINESS INTEGRA, INC.] wrote: I’m seeing unexpected behavior in our Queens environment related to Glance image visibility. Specifically users who, based on my understanding of the visibility and ownership fields, should NOT be able to

[Openstack-operators] [all] Naming the T release of OpenStack

2018-10-17 Thread Tony Breeds
Hello all, As per [1] the nomination period for names for the T release have now closed (actually 3 days ago sorry). The nominated names and any qualifying remarks can be seen at2]. Proposed Names * Tarryall * Teakettle * Teller * Telluride * Thomas * Thornton * Tiger * Tincup * Timn