Open Stack

On Mon, 2023-01-09 at 19:23 +0100, Dmitriy Rabotyagov wrote:
> As of today, nova-compute can access data only through conductor. You
> should not have database connection details in nova.conf for nova-compute -
> if you do, this should raise an exception.
having the credentials wont raise an execption but they wont be used.
tripleo used to put them in the nova-comptue nova.conf.
i dont know if that has been fixed on master but we have trieed to get them removed
several times but other installer have also done this incorrectly in the past.
> However you're referring the Pike release and back then having db details
> in config wasn't considered as error at least. But I still doubt that
> nova-compute was accessing DB directly even then.
as noted in my other reply local condutor mode was remvoed in ocata
and deprecated in mitaka so in pike there is defintly no direct db access form the compute agent.
> 
> 
> пн, 9 янв. 2023 г., 18:04 Huy Võ Lê <volehuy1998 at gmail.com>:
> 
> > Hi, I have a question about Nova role
> > 
> > 
> > - Assert: I don't understand about OPS/Redhat explaination. Because all of
> > information said nova-conductor will help database-accessing for
> > nova-compute, every chart/image showed, too.
> > 
> > - Reallity: When I download OPS Nova source code looked into
> > nova/compute/manager.py, I saw the many many block code that queries the
> > data from the database (instance list) and updates the data (instance.save).
> > 
> > So the assertion of the Openstack and Redhat development community is
> > wrong or true????
> > 
> > Link 1:
> > https://docs.openstack.org/nova/pike/install/get-started-compute.html
> > Link 2:
> > https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/8/html/configuration_reference_guide/section_conductor
> > Link n: ....
> >