Thank you Bernd, I left it there and it works as you said.

On Tue, Dec 26, 2017 at 10:39:05AM +0900, Bernd Bausch wrote:
> The installation guide sets up two nodes, a controller and a compute node.
> The only Neutron component on the compute node is the Linuxbridge agent. It
> communicates with other Neutron components via message queue and doesn't
> access the database. This is why the guide asks you to remove DB access
> information from the configuration.
> 
> You are installing an all-in-one cloud, controller and compute components on
> the same node. Since you don't follow the installation guide, you can't
> expect it to give you all steps in all details. 
> 
> In this case, you need the database connection string, because the Neutron
> controller components require it. Leave it in.
> 
> Bernd Bausch
> 
> -----Original Message-----
> From: Chengwei Yang [mailto:[email protected]] 
> Sent: Monday, December 25, 2017 7:18 PM
> To: the openstack general mailing list <[email protected]>
> Subject: [Openstack] setup all-in-one testing node
> 
> Hi All,
> 
> I'm following the pike installation guide and trying to setup an all-in-one
> testing node.
> 
> However, I found that neutron controller node needs to configure a database
> connection in /etc/neutron/neutron.conf
> 
> ```
> [database]
> connection
> ```
> 
> While neutron compute node suggested to be comment out any database
> connection in /etc/neutron/neutron.conf
> 
> ```
> [database]
> connection
> ```
> 
> It's quiet confused to me, any suggestions? Thanks in advance!
> 
> refer to:
> 
> https://docs.openstack.org/neutron/pike/install/controller-install-option1-r
> do.html
> https://docs.openstack.org/neutron/pike/install/compute-install-rdo.html
> 
> --
> Thanks,
> Chengwei
> 

-- 
Thanks,
Chengwei

Attachment: signature.asc
Description: PGP signature

_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : [email protected]
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Reply via email to