next release.
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786
From: Silvia Fichera [mailto:fichera@gmail.com]
Sent: Tuesday, March 17, 2015 4:27 AM
To: Dugger, Donald D
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] Questions from a newb
Silvia-
1) Not totally sure what you’re asking. When `devstack’ completes there
should be an instance of Horizon running on that machine. You can then connect
to that Horizon from any other machine on that network, assuming your host has
a routable IP address (using 127.0.0.1 as the HOS
Rim-
The log message `start_glance' immediately followed by errors was the
indicator, your glance didn't start. `devstack' uses `screen' to create
console logs for the various components that you use, switch to the `g-api'
screen and you should see more detail on what went wrong.
--
Don Dugge
There is a project, gantt, to split out the scheduler but it will be a while
before it is capable of making cross project scheduling decisions. I'll be
happy if we just have the current Nova scheduler capabilities available in a
separate Gantt scheduler by the Kilo release, more advanced capabi
Danny-
People have been thinking about affinity/anti-affinity scheduling so this is a
good area to look at but we might want to think of a general approach that
addresses this and other issues. I know that Yathi & Debo have proposed a BP:
https://blueprints.launchpad.net/nova/+
Kai-
Looking at the code the 60 second interval is hard coded and not changeable via
a config parameter.
Having said that, and given that it’s a fairly expensive operation to update
the DB for `every` compute node in the system, maybe the better question is why
do you want to increase the upda
