1) Forklift status
a. Schedulier client library
b. Isolate Scheduler DB
2) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
This is to make sure that everyone knows about the Gantt project and to make
sure that no one has a strong aversion to what we are doing.
The basic goal is to split the scheduler out of Nova and create a separate
project that, ultimately, can be used by other OpenStack projects that have a
esse decisse. - D. Gale
Ph: 303/443-3786
-Original Message-
From: John Dickinson [mailto:m...@not.mn]
Sent: Tuesday, August 12, 2014 9:24 AM
To: Dugger, Donald D
Cc: OpenStack Development Mailing List (not for usage questions); Michael
Still; Mark Washenberger; Dolph Mathews; Lyle, David
Indeed, no REST API yet, but that's one of the things we will be considering
for Gantt. I wonder if this is yet another argument for Gantt and, if you can
wait until the Kilo cycle, maybe we can provide an appropriate service for Heat.
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D.
(Some suggestions, I'll have to miss the meeting, Sylvain has agreed to chair)
1) Forklift Status
a. Scheduler client library
b. Isolate scheduler DB
2) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
1) Resource model for scheduler (action for Bauzas Jaypipes from last week)
2) Forklift status
3) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
I'll try and not whine about my pet project but I do think there is a problem
here. For the Gantt project to split out the scheduler there is a crucial BP
that needs to be implemented ( https://review.openstack.org/#/c/89893/ ) and,
unfortunately, the BP has been rejected and we'll have to try
Well, I think that there is a sign of a broken (or at least bent) process and
that's what I'm trying to expose. Especially given the ongoing conversations
over Gantt it seems wrong that ultimately it was rejected due to silence.
Maybe rejecting the BP was the right decision but the way the
a bit further up the thread where we are still talking about spec reviews
and not code reviews...
On 28 August 2014 21:42, Dugger, Donald D donald.d.dug...@intel.com wrote:
I would contend that that right there is an indication that there's a problem
with the process.
We got two nova-core
Subject: Re: [openstack-dev] [nova] Is the BP approval process broken?
On Aug 29, 2014 10:42 AM, Dugger, Donald D
donald.d.dug...@intel.commailto:donald.d.dug...@intel.com wrote:
Well, I think that there is a sign of a broken (or at least bent) process and
that's what I'm trying to expose
1) Forklift status
2) Next steps (now that Isolate Scheduler DB blueprint was rejected)
3) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Basically +1 with what Daniel is saying (note that, as mentioned, a side effect
of our effort to split out the scheduler will help but not solve this problem).
My only question is about the need to separate out each virt driver into a
separate project, wouldn't you accomplish a lot of the
Actually, I think Sylvain's point is even stronger as I don't think splitting
the virt drivers out of Nova is a complete fix. It may solve the review
latency for the virt driver area but, unless virt drivers are the bulk of Nova
patches, the Nova core team will still be swamped with review
Well, I and I believe a few others feel a slightly higher sense of urgency
about splitting out the scheduler but I don't want to hijack this thread for
that debate. Fair warning, I intend to start a new thread where we can talk
specifically about the scheduler split, I'm afraid we're in the
As I mentioned in a prior email I think that, although we're in agreement on
what needs to be done before splitting out the scheduler into the Gantt
project, I believe we have different views on what that agreement actually is.
Given that we have multiple people that actively want to work on
1) Next steps (mainly want to talk about interface cleanup)
2) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
I'd like to propose that we defer the meeting this week and reconvene next
Tues, 9/23. I don't think there's much new to talk about right now and we're
waiting for a write up on the claims process. I'd like to get that write up
when it's ready, have everyone review it and then we can talk
1) Forklift status
2) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
1) Memcached based scheduler updates
2) Scheduler code forklift
3) Instance groups
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Pretty much what Vish said.
In re: History. I think this was the right way, these scheduler files didn't
just spring up from nowhere, maintaining the history is a good thing. Even
when this becomes a separate service knowing where the files came from is a
good thing.
In re: Changes to the
This is to let everyone know that we have created a new source tree,
`https://github.com/openstack/gantt.git', that contains the code for the Nova
scheduler. The ultimate goal is to create a separate scheduler service that
can be utilized by any part of OpenStack that needs a scheduling
The specific steps I used clone the nova tree and then use this script to
delete areas of the tree:
git filter-branch -f --index-filter git rm -r -f --cached --ignore-unmatch $*
--prune-empty HEAD
if [ -d .git/refs/original ]
then
git for-each-ref
1) Memcached based scheduler updates
2) Scheduler code forklift
3) Instance groups
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
So I have 25 patches that I need to push to backport changes that have been
made to the nova tree that apply to the gantt tree. The problem is how do we
want to approve these patches? Given that they have already been reviewed and
approved in the nova tree do we have to go through the
...@fewbar.com
Excerpts from Doug Hellmann's message of 2014-01-12 14:45:11 -0800:
On Sun, Jan 12, 2014 at 5:30 PM, Dugger, Donald D
donald.d.dug...@intel.commailto:donald.d.dug...@intel.com
wrote:
So I have 25 patches that I need to push to backport changes that have
been made to the nova tree
1) Memcached based scheduler updates
2) Scheduler code forklift
3) Instance groups
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
All-
As threatened, I've pushed 24 patches to sync up the gantt tree to recent
changes to the nova tree. They're all linked in a dependency chain starting at:
https://review.openstack.org/66717
It's be good if we can get those reviewed soon.
--
Don Dugger
Censeo Toto nos in
but, as
long as that code exists in gantt I want to make it a synced up copy of the
code in nova.
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
From: Dugger, Donald D
Sent: Tuesday, January 14, 2014 2:48 PM
To: OpenStack Development Mailing List (not for usage
: Wednesday, January 15, 2014 9:28 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [gantt] Sync up patches
On Tue, Jan 14, 2014 at 2:22 PM, Dugger, Donald D
donald.d.dug...@intel.commailto:donald.d.dug...@intel.com wrote:
All-
I want to clear up
, Dugger, Donald D
donald.d.dug...@intel.commailto:donald.d.dug...@intel.com wrote:
The current thought is that I will do the work to backport any change that are
made to the nova tree that overlap the gantt tree. I don't see this as an
impossible task. Yes it will get harder as we make specific
...@gmail.com wrote:
On Wed, Jan 15, 2014 at 1:29 PM, Dugger, Donald D
donald.d.dug...@intel.com mailto:donald.d.dug...@intel.com
wrote:
My thought was to try and get some parallel effort going, do the
resync as a continuing task as suffer a little ongoing pain versus a
large amount
1) Memcached based scheduler updates
2) Scheduler code forklift
3) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
I almost have the unit tests for gantt working except for one problem - is
there a way to have the test infrastructure allow the gantt tree to import
objects from the nova tree.
The problem is that we want to break out just the scheduler code into the gantt
tree without duplicating all of
11:57, Dugger, Donald D donald.d.dug...@intel.com wrote:
I almost have the unit tests for gantt working except for one problem
- is there a way to have the test infrastructure allow the gantt tree
to import objects from the nova tree.
The problem is that we want to break out just
. That works fine, the only issues we have is when we register
opts to CONF where we could get DuplicateOpt if we try to register opt with
same name when importing.
-Sylvain
[1] :
https://github.com/stackforge/climate-nova/blob/master/test-requirements.txt#L15
2014/1/21 Dugger, Donald D
modules in unit tests
On 22 January 2014 11:57, Dugger, Donald D
donald.d.dug...@intel.commailto:donald.d.dug...@intel.com wrote:
I almost have the unit tests for gantt working except for one problem
- is there a way to have the test infrastructure allow the gantt tree
to import objects from
1) Memcached based scheduler updates
2) Scheduler code forklift
3) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
1) Memcached based scheduler updates
2) Scheduler code forklift
3) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Now that a preview version of the new gantt scheduler is available there is the
problem of configuring devstack to utilize this new tree. Fortunately, it's a
simple process that only requires 3 changes to your `localrc' file:
1) Enable gantt
2) Disable the nova scheduler
3)
Let's cancel the meeting this week, some of us (me for sure) will be tied up at
the Icehouse mid-cycle meetup.
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
. Would it be possible
that people not at the local meet up can join this discussion?
Thanks
Gary
From: Dugger, Donald D
donald.d.dug...@intel.commailto:donald.d.dug...@intel.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev
1) Mid-cycle meetup summary
2) No-db scheduler
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Sylvain-
As you can tell from the meeting today the scheduler sub-group is really not
the gantt group meeting, I try to make sure that messages for things like the
agenda and what not include both `gantt' and `scheduler' in the subject so it's
clear we're talking about the same thing.
Note
All-
I'm tempted to cancel the gantt meeting for tomorrow. The only topics I have
are the no-db scheduler update (we can probably do that via email) and the
gantt code forklift (I've been out with the flu and there's no progress on
that).
I'm willing to chair but I'd like to have some
, Donald D
donald.d.dug...@intel.commailto:donald.d.dug...@intel.com:
All-
I'm tempted to cancel the gantt meeting for tomorrow. The only topics I have
are the no-db scheduler update (we can probably do that via email) and the
gantt code forklift (I've been out with the flu and there's
For a significant transition period gantt (the separated out scheduler) will be
an optional component that requires extra configuration options when setting up
devstack to use it. As such we need to create the Jenkins jobs to do this
configuration when running the tempest tests. Note that
1) No-db scheduler
2) Code forklift
3) Icehouse BPs
4) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Fangzhen-
Great to see your interest in Gantt but, as Sylvain said, gantt is really not
ready for feature enhancments yet. Our exclusive goal for gantt right now is
to separate it out from nova proper, a daunting task itself.
Having said that, there is no change in development for the current
All- Note that Daylight Savings time started in the US. This meeting remains
at 1500 UTC, adjust your local time appropriately.
1) No-db scheduler
2) Code forklift
3) Icehouse BPs
4) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
I can't make the meeting this week so, unless someone else wants to volunteer
to run the meeting, let's cancel this one.
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
to discuss ?
-Sylvain
Le 17 mars 2014 00:55, Dugger, Donald D
donald.d.dug...@intel.commailto:donald.d.dug...@intel.com a écrit :
I can't make the meeting this week so, unless someone else wants to volunteer
to run the meeting, let's cancel this one.
--
Don Dugger
Censeo Toto nos in Kansa esse decisse
1) No-db scheduler
2) Scheduler forklift efforts
3) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
(Even though it's 4/1 this is not a joke :-)
1) No-db scheduler
2) Scheduler forklift efforts
3) Atlanta summit scheduler sessions
4) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
,
Le 01/04/2014 06:30, Dugger, Donald D a écrit :
(Even though it's 4/1 this is not a joke :-)
1) No-db scheduler
It was discussed during last meeting, and IIRC there was a resource issue for
targeting it now, at least until Juno summit.
Could we consider that this topic is not necessary
1) Scheduler forklift efforts
2) Atlanta summit scheduler sessions
3) Opens
Topic vault (so we don't forget)
1 - no-db scheduler
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
1) memcached based scheduler
2) Scheduler as a Service (recent email activity)
3) Instance groups
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
1) Forklift (tasks status)
2) Policy-based scheduler
3) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
1) Forklift (tasks status)
2) Opens
(Light agenda this week, potentially we can end early.)
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
At minimum I can arrange for a phone bridge at the sprint (Intel `lives` on
phone conferences) so we can certainly do that. Video might be more
problematic, I know we did something with Google Plus at the last sprint but I
don't know the details on that.
--
Don Dugger
Censeo Toto nos in Kansa
Much as I dislike the overhead and the extra latency involved (now you need to
have a review cycle for the spec plus the review cycle for the patch itself) I
agreed with the `small features require small specs’. The problem is that even
a small change can have a big impact. Forcing people to
Well, my main thought is that I would prefer to see the gantt split done sooner
rather than later. The reality is that we've been trying to split out the
scheduler for months and we're still not there. Until we bite the bullet and
actually do the split I'm afraid we'll still be here
1) Forklift (tasks status)
2) Fair Share scheduler
3) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Active discussion at the gantt meeting this week, check out the log:
http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-07-01-15.00.log.html
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
-Original Message-
From: Russell Bryant
-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Nova] [Gantt] Scheduler split status (updated)
Le 10/07/2014 16:32, Dugger, Donald D a écrit :
Active discussion at the gantt meeting this week, check out the log:
http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-07-01-15
My understanding is the main goal is to get a fully functional gantt working
before we do the split. This means we have to clean up the nova interfaces so
that all of the current scheduler functionality, including things like
aggregates and resource tracking, so that we can make the split and
1) Forklift (Tasks status)
2) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Unfortunately, much as I agree with your sentiment (Death to MS Outlook) my IT
overlords have pretty much forced me into using it. I still top post but try
and use some copied context (typically by adding an `in re:' to be explicit) so
you know what part of the long email I'm referring to.
--
@lists.openstack.org
Subject: [openstack-dev] Resources to fix MS Outlook (was Re: [Nova] [Gantt]
Scheduler split status (updated))
On 07/15/2014 09:02 AM, Dugger, Donald D wrote:
Unfortunately, much as I agree with your sentiment (Death to MS
Outlook) my IT overlords have pretty much forced me
1) Go over the use cases for a separate scheduler (ether pad
https://etherpad.openstack.org/p/SchedulerUseCases )
2) Forklift status
3) Mid-cycle meetup
4) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
1) Mid-cycle meetup results
2) Forklift status
3) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
As promised at the Gantt meeting today I've created an etherpad we can use to
keep track of scheduler related sessions at the Juno summit. (I've made the
name of the pad generic so we can re-use that pad for follow on summits and not
have to change any wiki links):
a
separate slot for this or not - but certainly related to Gantt.
Regards,
Alex
From:Dugger, Donald D
donald.d.dug...@intel.commailto:donald.d.dug...@intel.com
To:OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev
Sorry for the late notice but I can't make it this week (I got called for jury
duty). If people want to hang out on the IRC channel (#openstack-meeting at
1500 UTC) the list of things I wanted to go over was:
1) Open action items
a. The wiki page is there
I'm not sure we're asking for a quarter of the slots, I agree that would be
excessive but there is a significant amount of interest in the scheduler this
cycle so we'll have to see what we can come up with. I think we can merge a
few things, but that raises the question of what should be the
Jenny-
You should look at the `Propose Scheduler Library blueprint’:
https://review.openstack.org/#/c/82133/9
This BP is to create a client library for making calls to the scheduler. If
you base your work upon this library then you shouldn’t need to care about
whether the
-04-24 12:08 GMT-03:00 Dugger, Donald D
donald.d.dug...@intel.commailto:donald.d.dug...@intel.com:
Jenny-
You should look at the `Propose Scheduler Library blueprint’:
https://review.openstack.org/#/c/82133/9
This BP is to create a client library for making calls to the scheduler
1) Open action items
a. Merge sessions 262 140
b. Publish nova-spec for no-db scheduling BP
2) Status on forklift efforts
3) Juno summit design sessions
4) Opens
Topic vault (so we don't forget)
1 - no-db scheduler
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph:
Unfortunately, I'll be on a plane this week (traveling to my daughter's college
graduation) so, again, if people want to hand out on the IRC channel
(#openstack-meeting at 1500 UTC) the list of things I wanted to go over was:
1) Go over action items from last week
2) Status on forklift efforts
1) Summit recap
Forklift, no-db scheduler, simultaneous scheduling for server groups, hints for
VM life cycle
2) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
Here is a brief rundown on the majority of the scheduler sessions from the
summit, links to the etherpads and some of my incoherent notes from the
sessions. Feel free to reply to this email to correct any mistakes I made and
to add any other thoughts you might have:
1) Future of gantt
1) Summit recap
Forklift, no-db scheduler, simultaneous scheduling for server groups,
hints for VM life cycle
2) Forklift
Tasks and status
3) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
1) Forklift (tasks status)
2) No-db scheduler discussion (BP ref - https://review.openstack.org/#/c/92128/
)
3) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
1) Forklift (tasks status)
2) No-db scheduler discussion
3) Policy based scheduler ( https://review.openstack.org/#/c/61386/ )
4) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
1) Forklift status
2) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
1) Forklift status
2) Kilo Summit sessions
3) Kilo BPs
4) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
1) Forklift status
2) Kilo Summit sessions
3) Kilo BPs
4) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Just a reminder that, as we mentioned last week, no meeting today.
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
, Dugger, Donald D wrote:
Just a reminder that, as we mentioned last week, no meeting today.
The meetings are supposed to be on Tuesday, no? And yeah, no one showed up
yesterday.
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (GNU/Linux)
iQIcBAEBAgAGBQJUR61TAAoJEKMgtcocwZqLhH4P
:* Dugger, Donald D [mailto:donald.d.dug...@intel.com]
*Sent:* Wednesday, October 22, 2014 6:04 AM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* [openstack-dev] [gantt] Scheduler group meeting - cancelled
this week
Just a reminder that, as we mentioned last week
, 2014 9:40 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [gantt] Scheduler sessions at the summit
On 10/24/2014 10:39 AM, Dugger, Donald D wrote:
(I hijacked this thread to save the context but changed the subject so
more people might read it.)
Looks like we have
1) Summit recap
2) Status of BPs:
a. Isolate scheduler DB aggregates -
https://review.openstack.org/#/c/89893/
b. Isolate scheduler DB for instance groups -
https://review.openstack.org/#/c/131553/
c. Detach service from compute node -
08:35, Sylvain Bauza
sylvain.ba...@gmail.commailto:sylvain.ba...@gmail.com a écrit :
Fyi, today is Remembrance Day and a national day-off in France, so I won't be
able to attend the meeting.
Below are a few notes.
Le 11 nov. 2014 03:07, Dugger, Donald D
donald.d.dug
OK, as promised I created a Wiki page to keep track of our work items. It’s
linked to from the Gantt meeting page and is also available here:
https://wiki.openstack.org/wiki/Gantt/kilo
The important column in the Tasks table is the Patches column, that shows the
specific patch
To: OpenStack Development Mailing List; Michael Still; sgor...@redhat.com;
Dugger, Donald D
Subject: [nova] RT/Scheduler summit summary and Kilo development plan
Good morning Stackers,
At the summit in Paris, we put together a plan for work on the Nova resource
tracker and scheduler in the Kilo
Meeting on #openstack-meeting at 1500 UTC (8:00AM MST)
1) Status on cleanup work - https://wiki.openstack.org/wiki/Gantt/kilo
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
Danny-
Availability zones and host aggregates are your friend. For more detail check
out:
http://docs.openstack.org/openstack-ops/content/scaling.html
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
From: Danny Choi (dannchoi)
1) Follow ups on the scheduler BPs
2) Opens?
Not really much on the agenda for this week, we'll probably have a short
meeting (I'm still studying the scheduler's use of fan-out messages and the DB,
I'll want to go over that in more detail once I complete my study).
PS: The list of scheduler
1) Follow ups on the scheduler BPs
2) Opens?
I'm hoping we can get something going through the opens, people must have some
issues they want to discuss.
PS: The curren list of scheduler BPs is:
1) Extending data in host state
2) Utilization based scheduling
3) Whole host allocation
(Sorry, I've been away and didn't get this out sooner).
A couple of issues have come up on the mailing list that would be good to go
over if the critical people can be at the meeting tomorrow:
1) Scheduler code re-factoring
2) Volume affinity filter
3) Follow ups on the scheduler BPs
4)
-
From: Dugger, Donald D [mailto:donald.d.dug...@intel.com]
Sent: Tuesday, July 30, 2013 6:48 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] Scheduler sub-group meeting agenda 7/30
Let's try and complete the topics from last week so we'll do them in a
different order:
1
1 - 100 of 172 matches
Mail list logo
