Meeting on #openstack-meeting-alt at 1400 UTC (7:00AM MDT)
1) Patches/Reviews -
https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking
2) Bugs - https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler
3) Opens
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph:
Meeting on #openstack-meeting-alt at 1400 UTC (7:00AM MDT)
1) Patches/Reviews -
https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking
2) Bugs - https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler
3) Opens
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph:
Meeting on #openstack-meeting-alt at 1400 UTC (7:00AM MDT)
1) Patches/Reviews -
https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking
2) Bugs - https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler
3) Opens
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph:
Meeting on #openstack-meeting-alt at 1400 UTC (7:00AM MDT)
1) Mid-cycle meetup report back.
2) Spec & BPs & Patches -
https://etherpad.openstack.org/p/mitaka-nova-spec-review-tracking
3) Bugs - https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler
4) Opens
--
Don Dugger
"Censeo Toto nos in
Meeting on #openstack-meeting-alt at 1400 UTC (7:00AM MDT)
1) Spec & BPs & Patches -
https://etherpad.openstack.org/p/mitaka-nova-spec-review-tracking
2) Mid-cycle meetup
3) Bugs - https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler
4) Opens
--
Don Dugger
"Censeo Toto nos in Kansa
Meeting on #openstack-meeting-alt at 1400 UTC (7:00AM MDT)
1) Spec & BPs & Patches -
https://etherpad.openstack.org/p/mitaka-nova-spec-review-tracking
2) Mid-cycle meetup
3) Bugs - https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler
4) Opens
--
Don Dugger
"Censeo Toto nos in Kansa esse
Meeting on #openstack-meeting-alt at 1400 UTC (7:00AM MDT)
1) Spec & BPs -
https://etherpad.openstack.org/p/mitaka-nova-spec-review-tracking
2) Bugs - https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler
3) Opens
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph:
Meeting on #openstack-meeting-alt at 1400 UTC (7:00AM MDT)
(Hopefully the DDOS against freenode has died down and we can actually have the
meeting)
1) Spec & BPs -
https://etherpad.openstack.org/p/mitaka-nova-spec-review-tracking
2) Bugs -
I can’t even connect to the IRC server at all, can others get it?
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786
From: Joshua Hesketh [mailto:joshua.hesk...@gmail.com]
Sent: Monday, November 30, 2015 2:50 AM
To: OpenStack Development Mailing List (not for usage
Sorry guys, I can't get onto IRC so, if any of you can connect you'll just have
to muddle through without me :-) Hopefully freenode will be back up next week.
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786
-Original Message-----
From: Dugger
Meeting on #openstack-meeting-alt at 1400 UTC (7:00AM MDT)
1) Spec & BPs -
https://etherpad.openstack.org/p/mitaka-nova-spec-review-tracking
2) Bugs - https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler
3) Opens
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph:
Meeting on #openstack-meeting-alt at 1400 UTC (7:00AM MDT)
1) Spec & BPs -
https://etherpad.openstack.org/p/mitaka-nova-spec-review-tracking
2) Bugs - https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler
3) Opens
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph:
Meeting on #openstack-meeting-alt at 1400 UTC (7:00AM MDT)
(note back to standard time in the US, meeting an hr earlier for some people
but still at 1400 UTC)
1) Opens
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786
As discussed last week we will cancel this week's meeting to get ready for the
summit. See you all in Tokyo.
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786
__
OpenStack Development
Meeting on #openstack-meeting-alt at 1400 UTC (8:00AM MDT)
1) Mitaka planning
2) Opens
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786
__
OpenStack Development Mailing List (not for
Meeting on #openstack-meeting-alt at 1400 UTC (8:00AM MDT)
1) Mitaka planning
2) Opens
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786
__
OpenStack Development Mailing List (not for
Meeting on #openstack-meeting-alt at 1400 UTC (8:00AM MDT)
1) Mitaka planning
2) Opens
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786
__
OpenStack Development Mailing List (not for
As discussed last week we won't have a meeting this Mon., 9/21. Everyone can
concentrate on getting Liberty out the door and we'll meet again next week,
9/28, to talk about Mitaka planning a little.
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786
Meeting on #openstack-meeting-alt at 1400 UTC (8:00AM MDT)
1) Liberty patches -
https://etherpad.openstack.org/p/liberty-nova-priorities-tracking
2) Mitaka planning
3) Opens
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786
It belatedly occurred to me that it's a US holiday this week (Labor Day) so
most of us will gone so we should probably cancel the meeting this week. The
IRC channel will be there but many of us won't.
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786
Meeting on #openstack-meeting-alt at 1400 UTC (8:00AM MDT)
1) Liberty patches -
https://etherpad.openstack.org/p/liberty-nova-priorities-tracking
2) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
In re: user specifying requirements
Note that we have 2 different requirements here:
1) The cloud user needs to be able to specify I want to run this image on a
machine that supports capability `foo'.
2) The cloud provider needs to be able to say If you want capability `foo'
it'll cost you.
(not for usage questions)
Subject: Re: [openstack-dev] How should we expose host capabilities to the
scheduler
On Mon, Aug 03, 2015 at 04:49:59PM +0100, Alexis Lee wrote:
Dugger, Donald D said on Mon, Aug 03, 2015 at 05:39:49AM +:
Also note that, although many capabilities can be represented
Meeting on #openstack-meeting-alt at 1400 UTC (8:00AM MDT)
1) Liberty patches -
https://etherpad.openstack.org/p/liberty-nova-priorities-tracking
2) CPU feature representation - follow up from the mid-cycle
3) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D.
As we discussed at the mid-cycle meetup there is a bit of an issue related to
host capabilities. Currently, we are overloading the flavor extra_specs with a
whole lot of meaning, including requirements for specific host capabilities.
Although this has allowed some impressive extension
Meeting on #openstack-meeting-alt at 1400 UTC (8:00AM MDT)
1) Liberty specs -
https://etherpad.openstack.org/p/liberty-nova-priorities-tracking
2) CPU feature representation - follow up from the mid-cycle
3) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D.
1) Liberty specs -
https://etherpad.openstack.org/p/liberty-nova-priorities-tracking (talk about
offloading some of bauzas' work)
2) CPU feature representation - follow up from the mid-cycle
3) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph:
As discussed at the last meeting we'll cancel this week (blame it on travel for
the mid-cycle meetup).
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
__
OpenStack Development Mailing List
-Original Message-
From: Chris Friesen [mailto:chris.frie...@windriver.com]
Sent: Thursday, July 16, 2015 12:07 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [nova] schedule instance based on CPU frequency ?
On 07/15/2015 04:57 PM, Dugger, Donald D wrote:
In re: Static CPU
In re: Static CPU frequency. For modern Intel CPUs this really isn't true.
Turbo Boost is a feature that allows certain CPUs in certain conditions to
actually run at a higher clock rate that what is advertised at power on (the
havoc this causes code that depends upon timing based upon CPU
Meeting on #openstack-meeting at 1400 UTC (8:00AM MDT)
1) Liberty specs -
https://etherpad.openstack.org/p/liberty-nova-priorities-tracking
2) Mid-cycle meetup
3) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
(Note new meeting day/time)
Meeting on #openstack-meeting at 1400 UTC (8:00AM MDT)
1) Liberty specs -
https://etherpad.openstack.org/p/liberty-nova-priorities-tracking
2) Mid-cycle meetup
3) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
What Ed said. I've proposed a change to the infra tree that should percolate
this time change up through the system but, starting next Mon, 4/6, we'll be
talking scheduler at the new time place.
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
-Original
Meeting on #openstack-meeting at 1500 UTC (9:00AM MDT)
1) New meeting time
2) Liberty specs -
https://etherpad.openstack.org/p/liberty-nova-priorities-tracking
3) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
Meeting on #openstack-meeting at 1500 UTC (9:00AM MDT)
1) New meeting time
2) Liberty specs - https://wiki.openstack.org/wiki/Gantt/liberty
3) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
Meeting on #openstack-meeting at 1500 UTC (9:00AM MDT)
1) Liberty summit recap -
https://etherpad.openstack.org/p/YVR-nova-scheduler-in-liberty
2) Updating concept of resource - Ed Leafe's email thread
3) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
I would suggest we cancel the IRC meeting this week since we just had the
summit (and I'm on vacation so it would be 5AM my time :)
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
__
requirements for an
independant (gantt) scheduler at Vancouver
On 13 May 2015 at 16:48, Dugger, Donald D donald.d.dug...@intel.com wrote:
I’d like to get together to talk about what kind of APIs/requirements
different projects would need from a common scheduler. To that end
room 221
[mailto:thie...@openstack.org]
Sent: Wednesday, May 13, 2015 2:38 AM
To: Dugger, Donald D
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: Re: Birds of a Feather session at Vancouver design summit
Dugger, Donald D wrote:
Will there be BoF's at the design summit and, if so
I'd like to get together to talk about what kind of APIs/requirements different
projects would need from a common scheduler. To that end room 221 is available
on Tues. at 3:40PM. If you're at all interested in a common scheduler come on
by and join the conversation.
Location: Rm
Will there be BoF's at the design summit and, if so, can I set one up in
advance?
I'd like to arrange for a session to talk about cross-project scheduler
APIs/requirements and, since that didn't make it into the Tues. sessions, I
thought a BoF would be the next best thing.
--
Don Dugger
Meeting on #openstack-meeting at 1500 UTC (9:00AM MDT)
Try and have a short meeting, basically one topic:
1) Vancouver design summit - are we ready?
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
I will not be able to make the meeting tomorrow but the IRC channel will be
available for anyone who wants to get together. For an agenda I would suggest:
1) Liberty specs (tracking page - https://wiki.openstack.org/wiki/Gantt/liberty
)
2) Vancouver design summit - more thoughts?
3) Opens
Meeting on #openstack-meeting at 1500 UTC (9:00AM MDT)
1) Liberty specs (tracking page - https://wiki.openstack.org/wiki/Gantt/liberty
)
2) Vancouver design summit - more thoughts?
3) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
Meeting on #openstack-meeting at 1500 UTC (9:00AM MDT)
1) Vancouver design summit - more thoughts?
2) Opens
(Light agenda this week, could be a quick meeting)
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
Meeting on #openstack-meeting at 1500 UTC (9:00AM MDT)
1) Gantt - what's in a name?
2) Patch status -
https://etherpad.openstack.org/p/kilo-nova-priorities-tracking
3) Vancouver design summit - start thinking about what we want to discuss
--
Don Dugger
Censeo Toto nos in
generating confusion.
Gantt is dead, the current effort is nova-scheduler improvement. Please just
call it that.
-Sean
On 04/02/2015 04:10 AM, Sylvain Bauza wrote:
Le 02/04/2015 01:28, Dugger, Donald D a écrit :
I think there's a lot of `a rose by any other name would smell as
sweet
@lists.openstack.org
Subject: Re: [openstack-dev] [nova] [scheduler] [gantt] Please stop using
Gantt for discussing about Nova scheduler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/03/2015 11:42 AM, Dugger, Donald D wrote:
Yes the current effort is to clean up the scheduler interfaces
: [openstack-dev] [nova] [scheduler] [gantt] Please stop using
Gantt for discussing about Nova scheduler
Le 31/03/2015 02:57, Dugger, Donald D a écrit :
I actually prefer to use the term Gantt, it neatly encapsulates the
discussions and it doesn't take much effort to realize that Gantt refers
I actually prefer to use the term Gantt, it neatly encapsulates the discussions
and it doesn't take much effort to realize that Gantt refers to the scheduler
and, if you feel there is confusion, we can clarify things in the wiki page to
emphasize the process: clean up the current scheduler
Meeting on #openstack-meeting at 1500 UTC (9:00AM MDT)
1) Patch status -
https://etherpad.openstack.org/p/kilo-nova-priorities-tracking
2) Vancouver design summit - start thinking about what we want to discuss
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph:
Meeting on #openstack-meeting at 1500 UTC (9:00AM MDT)
1) Patch status -
https://etherpad.openstack.org/p/kilo-nova-priorities-tracking
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
(Note that most of the US has foolishly changed to Daylight Saving Time, check
your local time conversion, the meeting is still at 1500 UTC)
Meeting on #openstack-meeting at 1500 UTC (9:00AM MDT)
1) Discuss `model request' (
Meeting on #openstack-meeting at 1500 UTC (8:00AM MST)
1) Status on cleanup work - https://wiki.openstack.org/wiki/Gantt/kilo
(No need to discuss the `Remove direct nova DB access’ spec, it’s been approved
☺
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph:
Note: I won't be able to make the meeting this week (family medical issues) so
everyone meet on the IRC channel and decide who wants to chair.
Meeting on #openstack-meeting at 1500 UTC (8:00AM MST)
1) Remove direct nova DB/API access by Scheduler Filters -
Meeting on #openstack-meeting at 1500 UTC (8:00AM MST)
1) Remove direct nova DB/API access by Scheduler Filters -
https://review.opernstack.org/138444/
2) Status on cleanup work - https://wiki.openstack.org/wiki/Gantt/kilo
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D.
Meeting on #openstack-meeting at 1500 UTC (8:00AM MST)
1) Remove direct nova DB/API access by Scheduler Filters -
https://review.opernstack.org/138444/
2) Status on cleanup work - https://wiki.openstack.org/wiki/Gantt/kilo
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D.
Meeting canceled this week due to the Nova mid-cycle meetup.
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
We'll try and have an IRC meeting tomorrow so finalize the review for:
Remove direct nova DB/API access by Scheduler Filters -
https://review.opernstack.org/138444/
We'll start out on #openstack-nova and then create a new channel if needed
(#openstack-gantt has a nice ring to
Sorry guys, my time issues strike again. Yes, this will be at 1600 UTC (8AM
PST).
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
From: Dugger, Donald D [mailto:donald.d.dug...@intel.com]
Sent: Tuesday, January 20, 2015 9:54 AM
To: OpenStack Development Mailing
Meeting on #openstack-meeting at 1500 UTC (8:00AM MST)
1) Remove direct nova DB/API access by Scheduler Filters -
https://review.opernstack.org/138444/
2) Status on cleanup work - https://wiki.openstack.org/wiki/Gantt/kilo
3) Topics for mid-cycle meetup
Note, I expect we'll
As promised at the weekly IRC meeting this week I'll setup up a hangout
tomorrow, 1/15, at 1500 UTC (8:00AM MST) where we can discuss the one remaining
spec that needs approval for Kilo:
Remove direct nova DB/API access by Scheduler Filters -
https://review.openstack.org/138444
Meeting on #openstack-meeting at 1500 UTC (8:00AM MST)
1) Remove direct nova DB/API access by Scheduler Filters -
https://review.opernstack.org/138444/
2) Status on cleanup work - https://wiki.openstack.org/wiki/Gantt/kilo
3) Topics for mid-cycle meetup
--
Don Dugger
Censeo
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
I'll be hanging out on the IRC channel in case anyone wants to talk but, given
the holidays, I don't expect much attendance and we'll keep it short no matter
what.
Meeting on #openstack-meeting at 1500 UTC (8:00AM MST)
1) Status on cleanup work -
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
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
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)
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
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
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
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 -
:* 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
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
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
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) 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
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) 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
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
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
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
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
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
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
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
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
(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
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.
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
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
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
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
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 - 100 of 172 matches
Mail list logo
