> Hmm... I guess the blueprint summary led me to believe that nova-network
> no longer needs to hit the database.
Yeah, using objects doesn't necessarily mean that the rest of the direct
database accesses go away. However, I quickly cooked up the rest of what
is required to get this done:
https:/
Hmm... I guess the blueprint summary led me to believe that nova-network no
longer needs to hit the database.
On Mon, Mar 10, 2014 at 3:50 PM, Dan Smith wrote:
> > https://bugs.launchpad.net/nova/+bug/1290568
>
> Thanks. Note that the objects work doesn't really imply that the service
> doesn't
> https://bugs.launchpad.net/nova/+bug/1290568
Thanks. Note that the objects work doesn't really imply that the service
doesn't hit the database. In fact, nova-compute stopped hitting the
database before we started on the objects work.
Anyway, looks like there are still some direct-to-database th
Done.
https://bugs.launchpad.net/nova/+bug/1290568
On Mon, Mar 10, 2014 at 1:37 PM, Dan Smith wrote:
> > However, when attempting to boot an instance, the Nova network service
> > fails to retrieve network information from the controller. Adding the
> > the database keys resolves the problem.
> However, when attempting to boot an instance, the Nova network service
> fails to retrieve network information from the controller. Adding the
> the database keys resolves the problem. I'm using
> the 2014.1~b3-0ubuntu1~cloud0 packages on Ubuntu 12.04.
Can you file a bug with details from the lo
Hi,
I'm updating the installation guide for Icehouse. Based on the following
blueprint, I removed the database configuration keys from nova.conf on the
compute node in my test environment.
https://blueprints.launchpad.net/nova/+spec/nova-network-objects
However, when attempting to boot an instan
