...19 times out of 20, it's because a branch that is approved has
neither a commit message nor a description.
The commit message is what ends up in the changelog. The description
is whatever you want to tell the reviewer to make their lives easier.
If only the description is set, it gets used as
Hello everyone,
As a reminder, our weekly team meeting will take place at 21:00 UTC
this Tuesday in #openstack-meeting on IRC.
In particular, we'll discuss the green light for RCFreeze and Cactus
release, or whether we think we can get a better-tested release with a
short delay.
Check out how
+1 from me, too.
As per the process, if no-one objects within 5 business (my
interpretation) days, i.e. before Thursday, I'll get Justin added to
the nova-core team.
--
Soren Hansen
Ubuntu Developer http://www.ubuntu.com/
OpenStack Developer http://www.openstack.org/
I'm trying to understand how best to implement our architecture-aware scheduler
for Diablo:
https://blueprints.launchpad.net/nova/+spec/schedule-instances-on-heterogeneous-architectures
Right now our scheduler is similar in approach to SimpleScheduler with a few
extra filters on instances and
Hi Brian, comments inline :)
On Tue, Apr 12, 2011 at 12:34 PM, Brian Schott bfsch...@gmail.com wrote:
I'm trying to understand how best to implement our architecture-aware
scheduler for Diablo:
https://blueprints.launchpad.net/nova/+spec/schedule-instances-on-heterogeneous-architectures
On Apr 12, 2011, at 12:34 PM, Brian Schott wrote:
- Will your capabilities scheduler, constraint scheduler, and/or distributed
schedulers understand different available hardware resources on compute nodes?
The distributed scheduler has the concept of 'capabilities', and would
be
Hey all,
We're in the planning stages for Diablo now, working on putting
together blueprints, which turn into sessions at the design summit.
I know the Glance team is small and our project narrow in scope, but
it would be great to get some feedback from the list about stuff you'd
like to see
Hey everyone,
During the recent meeting we decided to push back RCFreeze by one day,
in order to be able to squash the release-critical issues that were
found in recent testing.
RCFreeze will occur at the end of day, Wednesday. The list of bugs we'll
work on during that extra time are:
8 matches
Mail list logo
