> Likewise for fields that want to change their format. So for my part, the
> fields that were not added yet are fields that were not used in the resource
> tracker - even if they are used in the scheduler.
>
> The one exception is the pci_stats - which was undergoing change.
>
>
Hi,
By working on providing a new scheduler client for compute nodes, I
began to use the ComputeNode object instead of placing a call to
conductor directly.
Unfortunately, I recently discovered that some changes have been done in
the DB model for ComputeNode that haven't been populated on the
cor
Le 30/05/2014 14:44, CARVER, PAUL a écrit :
>
> Mathieu Rohon wrote:
>
>
>
> >I'm also very interested in scheduling VMs with Network requirement.
> This seems to be in the scope of NFV workgroup >[1].
>
> >For instance, I think that scheduling should take into account
> bandwith/QoS requirement
Ironic patch as well :
https://review.openstack.org/#/c/96576/1/ironic/tests/api/utils.py
Will provide a patch against Blazar.
Btw, I'll close the bug.
> -- Dina
>
>
> On Fri, May 30, 2014 at 4:00 PM, Sylvain Bauza <mailto:sba...@redhat.com>> wrote:
>
> Hi Keyston
Hi Keystone developers,
I just opened a bug [1] because Ironic and Blazar (ex. Climate) patches
are failing due to a new release in Keystone client which seems to
regress on midleware auth.
Do you have any ideas on if it's quick to fix, or shall I provide a
patch to openstack/global-requirements.
Le 30/05/2014 14:00, Sylvain Bauza a écrit :
> Hi Keystone developers,
>
> I just opened a bug [1] because Ironic and Blazar (ex. Climate) patches
> are failing due to a new release in Keystone client which seems to
> regress on midleware auth.
>
> Do you have any ideas on if
Hi,
Due to some important changes with Climate (which is now Blazar) and as
the team is quite changing, I want to make sure we run the weekly
meeting today at 3pm UTC.
Thanks,
-Sylvain
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
ht
Hi,
Due to some important changes with Climate (which is now Blazar) and as
the team is quite changing, I want to make sure we run the weekly
meeting today at 3pm UTC.
Thanks,
-Sylvain
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
ht
Hi,
My goal is not to open another thread about mox vs. mock but rather
discussing on how Nova is currently using mock for new test classes.
At the moment, by looking at the current implementation (make use of
mock.patch() as decorator or in context), I'm feeling it would be
helpful to provide ano
correct any
> mistakes I made and to add any other thoughts you might have:
>
>
>
> 1) Future of gantt interfaces & APIs (Sylvain Bauza)
>
> https://etherpad.openstack.org/p/juno-nova-gantt-apis
>
> As from the last summit everyone agrees that yes a separate scheduler
any discussion on this topic scheduled during the summit ?
>
> Thanks,
> Meghal
>
> On Apr 9, 2014, at 9:03 AM, Sylvain Bauza <mailto:sylvain.ba...@gmail.com>> wrote:
>
>>
>>
>>
>> 2014-04-07 23:11 GMT+02:00 Sylvain Bauza > <mailto:sylvain.ba..
Could we gently leave room for non-Openstack projects for discussing on
Monday ?
Take the Blazar (ex-Climate) Stackforge project as an example, we do have a
session on Tuesday but we would like to take the opportunity to sync up
ourselves before that session.
Thanks,
-Sylvain
2014-05-06 14:37 GM
Congrats to your daughter, Don !
I'll chair this week meeting, no worries.
-Sylvain
Le 6 mai 2014 04:46, "Dugger, Donald D" a écrit
:
> 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 (#open
Le 1 mai 2014 19:11, "Dolph Mathews" a écrit :
>
>
> On Thu, May 1, 2014 at 8:50 AM, Fuente, Pablo A
wrote:
>>
>> Hi,
>> We recently implemented our V2 REST API, and at this moment we
are
>> trying to get working our python client against this new version. For
>> this reason, we start a d
Hi Dina,
I forgot yesterday to mention it was my last day at Bull, so the end of
week was off-work until Monday.
As a corollar, I won't be able to attend Friday meeting.
Let's cancel this meeting and raise topics in mailing-list if needed.
-Sylvain
2014-04-30 19:17 GMT+02:00 Dina Belova :
> F
2014-04-28 16:33 GMT+02:00 John Garbutt :
>
> I don't think Nova should try to include functionality that
> re-implements other good monitoring tools (Nagios, etc)
>
> Having said that, having a new service group API that uses information
> from external tools to decide if a host is dead or not, a
Hi Michael,
Thanks for sharing the schedule. A quick glance shows me that all
scheduler-related sessions will happen on Friday, that's fine :-)
Just a quick note, Climate (now Blazar) was identified as a good
opportunity for scheduling in Nova but the session will happen on Tuesday
afternoon [1].
.
>>
>> I see a couple of options here:
>>
>> · Give support for v1 and change the client accordantly
>>
>> · Give support only on v2, and open a bp for climateclient v2
>> support.
>>
>>
>>
>> Hope I make myself
Hi,
Sorry again about my non-presence for 20 mins, I had an IRC
client/connection issue.
That impacted much the discussions, feel free to reply to this email with
any concerns you didn't had time to raise on the meeting, so we could
continue.
That said, meeting minutes can be found here :
(18:00
2014-04-25 1:38 GMT+02:00 Jay Lau :
> Seems http://summit.openstack.org/cfp/details/262 can cover this? Thanks.
>
>
Well, that will depend on the number of sessions we could get. This #262
proposal was agreed to be merged with #140 if no enough slots.
>
> 2014-04-25 5:09 GM
Le 24 avr. 2014 19:20, "Henrique Truta" a
écrit :
>
> Donald,
>
> By "selection", I think Jenny means identifying whether and which active
VM should be migrated, once the current Nova scheduler only deals with the
VM in the momment of its creation or with a specific user input.
>
As Don said, we'
Welcome Pablo !
2014-04-24 15:06 GMT+02:00 Dina Belova :
> Well, as 3/4 core team members are okay with it, I'll do this)
>
>
> On Thu, Apr 24, 2014 at 2:14 PM, Sylvain Bauza wrote:
>
>> http://russellbryant.net/openstack-stats/climate-reviewers-90.txt
>>
http://russellbryant.net/openstack-stats/climate-reviewers-90.txt
As per the stats, +1 to this.
2014-04-24 12:10 GMT+02:00 Dina Belova :
> I propose to add Pablo Andreas Fuente (pafuent on the IRC) to Climate core
> team.
>
> He's Python contributor from Intel, and he took great part in Climate
ially
allow us to have enough materials for producing outputs.
Let's wait for community feedback on the proposals, and we'll see how we
can arrange all the ideas the good way.
-Sylvain
> Michael
>
> On Thu, Apr 24, 2014 at 6:09 AM, Sylvain Bauza
> wrote:
> > Hi a
Hi all,
I just noticed (with a slight delay due to lack of notifications from
summit.openstack.org) that most of the Nova proposals for sessions were
under review with comments.
As Scheduler code is on a big turn for Juno with the forklift efforts and
the Gantt project, I think it's worth having
No worries, I'll handle it.
-Sylvain
Le 22 avr. 2014 06:29, "Dugger, Donald D" a
écrit :
> 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 ov
Yes, sorry again about not being able to run the meeting...
2014-04-18 11:44 GMT+02:00 Dina Belova :
> Folks, o/
>
> I'm really sorry, but Sylvain and I can't attend today's meeting, that's
> why it was decided not to have it.
>
> All Climate related questions and discussions are welcome in our
2014-04-17 21:30 GMT+02:00 Eric Windisch :
>
> Furthermore, I've started testing KVM/Qemu support. It's looking
> promising. It's too early to claim it's supported, but I've only ran into
> minor issues so far. I'll update again when I've made further progress.
> Also pending, but not far away, i
Hi Eric,
2014-04-16 21:06 GMT+02:00 Eric Windisch :
>
>> > As I really would like to keep a 1:1 matching with my current Devstack
>> > installation, have you tried to trick Dockenstack by modifying the
>> > localrc file to say Qemu as the driver ?
>>
>
> Not yet, but I'd like to. It has been a s
Hi Steven et al.
2014-04-15 17:01 GMT+02:00 Steven Dake :
>
>> Qiming,
>
> If you read my original post on this thread, it outlines the current
> heat-core thinking, which is to reduce the scope of this resource from the
> Heat resources since it describes a workflow rather then an orchestrated
Hi,
Just for reminder, the weekly meeting will be held today at 1500 UTC on
#openstack-meeting.
The agenda I can see for today is :
- Follow-up on previous actions
- Status on forklift efforts
- Juno summit design sessions
- open discussion
If you want to discuss about another topic, please
Hi Eric,
2014-04-12 5:45 GMT+02:00 Eric Windisch :
>
>
> As for dockenstack, this might deserve a separate thread. What I've done
> here is build something that may be useful to openstack-infra and might
> necessitate further discussion. It's the fastest way to get the Docker
> driver up and
Hi Dina et al.
I'm sorry, I was facing this week a particular off-load due to various
concerns, and so was unable to attend the meeting.
About the wondering of my participation, please all be sure I'll still
dedicate some of my time to Climate, including some BPs and bugs, so yes I
will handle the
2014-04-10 16:16 GMT+02:00 Jay Lau :
>
>
>
> 2014-04-10 0:57 GMT+08:00 Susanne Balle :
>
> Ditto. I am interested in contributing as well.
>>
>> Does Gant work with Devstack? I am assuming the link will give me
>> directions on how to test it and contribute to the project.
>>
> You can refer to
>
x27;ll check the Gantt project and the
>> blueprint
>>
>>
>> 2014-04-09 12:59 GMT-03:00 Sylvain Bauza :
>>
>>
>>>
>>>
>>> 2014-04-09 17:47 GMT+02:00 Jay Lau :
>>>
>>> @Oleg, Till now, I'm not sure the target of Gan
2014-04-09 17:47 GMT+02:00 Jay Lau :
> @Oleg, Till now, I'm not sure the target of Gantt, is it for initial
> placement policy or run time policy or both, can you help clarify?
>
>
I don't want to talk on behalf of Oleg, but Gantt is targeted to be the
forklift of the current Nova scheduler. So, a
2014-04-07 23:11 GMT+02:00 Sylvain Bauza :
> Hi Phil,
>
>
>
> 2014-04-07 18:48 GMT+02:00 Day, Phil :
>
> Hi Sylvain,
>>
>>
>>
>> There was a similar thread on this recently - which might be worth
>> reviewing:
>> http://lists.ope
Made a typo,
2014-04-08 10:41 GMT+02:00 Sylvain Bauza :
>
>> IMO it's a huge bug in the testr tool: "testr run" command should not
>> write binary data into stdout. It makes development very hard.
>>
>>
>
> That's happening when testr is t
Hi Victor,
This page is worth it : https://wiki.openstack.org/wiki/Testr
Comments inline.
-Sylvain
2014-04-08 10:13 GMT+02:00 victor stinner :
> Hi,
>
> I have some issues when running unit tests in OpenStack. I would like to
> help, but I don't know where I should start and how I can fix these
sts that
> we really need to let users choose the types of physical hosts, then I
> suggest creating a new hint, and use aggregates with it. Don't sacrifice AZ
> exclusivity!
>
>
>
> Btw, there is a datacenter design called "dual-room" [1] which I think
> best
2014-04-04 10:30 GMT+02:00 Sylvain Bauza :
> Hi all,
>
>
>
> 2014-04-03 18:47 GMT+02:00 Meghal Gosalia :
>
> Hello folks,
>>
>> Here is the bug [1] which is currently not allowing a host to be part
>> of two availability zones.
>> This bug was targe
Hi all,
2014-04-03 18:47 GMT+02:00 Meghal Gosalia :
> Hello folks,
>
> Here is the bug [1] which is currently not allowing a host to be part of
> two availability zones.
> This bug was targeted for havana.
>
> The fix in the bug was made because it was assumed
> that openstack does not suppo
Hi,
I'm currently trying to reproduce [1]. This bug requires to have the same
host on two different aggregates, each one having an AZ.
IIRC, Nova API prevents hosts of being part of two distinct AZs [2], so
IMHO this request should not be possible.
That said, there are two flaws where I can ident
43-3786
-----Original Message-
From: Sylvain Bauza [mailto:sylvain.ba...@bull.net]
Sent: Tuesday, April 1, 2014 1:29 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [gantt] scheduler sub-group meeting agenda 4/1
Hi Don,
Le 01/04/2014 06:30, Dug
Hi Don,
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 neces
and
what could be the side effects.
-Sylvain
*__*
Nikolay Starodubtsev
Software Engineer
Mirantis Inc.
Skype: dark_harlequine1
2014-03-28 14:57 GMT+04:00 Sylvain Bauza <mailto:sylvain.ba...@bull.net>>:
Hi folks,
I made a quick and dirty Dockerfile for creating a Doc
Hi folks,
I made a quick and dirty Dockerfile for creating a Docker image
containing Climate trunk and starting services.
You can find the source there : https://github.com/sbauza/docker_climate
That's a third option for deploying Climate, rather to be used for
correctly isolating Climate.
Le 27/03/2014 10:37, Khanh-Toan Tran a écrit :
- Original Message -
From: "Sangeeta Singh"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Wednesday, March 26, 2014 6:54:18 PM
Subject: Re: [openstack-dev] [nova][scheduler] Availability Zones and Host
aggrega
anged, but
apart from that, the change by itself should be quick to do.
-Sylvain
Thanks,
Sangeeta
[1] https://bugs.launchpad.net/nova/+bug/1277230
From: Sylvain Bauza <mailto:sylvain.ba...@gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage
questions
I can't agree more on this. Although the name sounds identical to AWS, Nova
AZs are *not* for segregating compute nodes, but rather exposing to users a
certain sort of grouping.
Please see this pointer for more info if needed :
http://russellbryantnet.wordpress.com/2013/05/21/availability-zones-and
Hi,
As said here [1], please don't send review requests directly to the ML.
[1]
http://lists.openstack.org/pipermail/openstack-dev/2013-September/015264.html
2014-03-20 12:08 GMT+01:00 Kamat, Maruti Haridas :
> Hi All,
>
> Me and my fellow friends (CCed) invite the community to review OpenSt
2014-03-19 22:38 GMT+01:00 Fox, Kevin M :
> Its my understanding that the only case the A in the AGPL would kick in is
> if the cloud provider made a change to MongoDB and exposed the MongoDB
> instance to users. Then the users would have to be able to download the
> changed code. Since Marconi's
oceed as scheduled.
>
>
>
> --
>
> Don Dugger
>
> "Censeo Toto nos in Kansa esse decisse." - D. Gale
>
> Ph: 303/443-3786
>
>
>
> *From:* Sylvain Bauza [mailto:sylvain.ba...@gmail.com]
> *Sent:* Monday, March 17, 2014 12:11 AM
> *To:* OpenStack Develop
2014-03-18 14:07 GMT+01:00 Russell Bryant :
>
> I think it's great to see discussion of better ways to approach these
> things, but it would have to be Juno work.
>
>
+1. There are various blueprints about the scheduler in progress, related
to either splitting it out or scaling it, and IMHO this c
Hi Chris,
2014-03-18 0:36 GMT+01:00 Chris Friesen :
> On 03/17/2014 05:01 PM, Sylvain Bauza wrote:
>
>
>> There are 2 distinct cases :
>> 1. there are multiple schedulers involved in the decision
>> 2. there is one single scheduler but there is a race condition on it
Hi Chris,
2014-03-17 23:08 GMT+01:00 Chris Friesen :
> On 03/17/2014 02:30 PM, Sylvain Bauza wrote:
>
>> There is a global concern here about how an holistic scheduler can
>> perform decisions, and from which key metrics.
>> The current effort is leading to having the
There is a global concern here about how an holistic scheduler can perform
decisions, and from which key metrics.
The current effort is leading to having the Gantt DB updated thanks to
resource tracker for scheduling appropriately the hosts.
If we consider these metrics as not enough, ie. that Gan
I can chair this one, no worries.
I have the below topics in mind :
- no-db scheduler blueprint
- scheduler forklift efforts
- open discussion
Any other subjects to discuss ?
-Sylvain
Le 17 mars 2014 00:55, "Dugger, Donald D" a
écrit :
>
>
> I can't make the meeting this week so, unless someon
Hi Russell,
Thanks for replying,
2014-03-12 16:46 GMT+01:00 Russell Bryant :
> On 03/12/2014 07:35 AM, Dina Belova wrote:
> > Thanks TC for spending time on Blazar (ex. Climate, in process of
> > renaming) discussion!
> >
> > It was decided that potentially reservation idea is interesting for OS
Hi,
I previously already sent an email but I'm recreating it in its own thread.
I just discovered that Gantt has been proposed as part of the ideas for
GSoC [1]
While I truly understand the mutual opportunities for both students and
Openstack, I'm thinking that Gantt is too young and yet to be sta
Hi,
Sorry for sending it to openstack-dev@ directly but most of the Travel
committee is actively following this mailing-list. Travel committee, feel
free to follow to your internal mailing-list [1]
I applied for the Travel Support Pogram, but I just noticed that
notifications of grantees will com
Galactic epic win !
Let's start calling our project now Blazar (Climate). Very impressive word
:-)
2014-03-07 20:13 GMT+01:00 Dina Belova :
> Hello everyone!
>
> I've closed round #2 of new name choosing voting for Climate:
>
> http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_e2f53ce1b331590f
Hi Thierry,
2014-03-06 11:46 GMT+01:00 Thierry Carrez :
> Dina Belova wrote:
> >> Would Climate also be usable to support functionality like Spot
> >> Instances ? "Schedule when spot price falls under X" ?
> >
> > Really good question. Personally I think that Climate might help
> > implementing
Le 06/03/2014 09:35, ?? a écrit :
Hi Sylvain, Russell, dims
Thanks for your the replies and guidances!
I have read the docs below the title. In my opinion, It is quite a
good idea to take storage component and network component into
consideration of the scheduler of nova. I agree that it is qu
Hi Fang,
Gantt subteam owns weekly meetings every Tuesdays 1500 UTC at
#openstack-meeting IRC channel, where we discuss about the steps for
forklifting Nova scheduler into a separate service.
As there is now FeatureFreeze period, there are no patches targeted to
be merged before next Juno summ
Hi Joe,
2014-03-03 18:32 GMT+01:00 Joe Gordon :
>
>
> This sounds like something that belongs in nova, Phil Day has an
> elegant solution for this:
> https://blueprints.launchpad.net/nova/+spec/whole-host-allocation
>
>
This blueprint has already been addressed by Climate team, and we discussed
Hi Sean,
2014-03-03 16:04 GMT+01:00 Sean Dague :
>
>
> At a high level this feels like this should be part of scheduling.
> Scheduling might include resources you want right now, but it could
> include resources you want in the future. It also makes sense for
> scheduling to include deadlines,
Forgot to put openstack-tc@ in the loop... Sorry for resending this email.
-Sylvain
Le 03/03/2014 13:42, Sylvain Bauza a écrit :
Hi Joe,
Thanks for your reply, I'll try to further explain.
Le 03/03/2014 05:33, Joe Gordon a écrit :
On Sun, Mar 2, 2014 at 11:32 AM, Dina Belova
wrote:
Hi Joe,
Thanks for your reply, I'll try to further explain.
Le 03/03/2014 05:33, Joe Gordon a écrit :
On Sun, Mar 2, 2014 at 11:32 AM, Dina Belova wrote:
Hello, folks!
I'd like to request Climate project review for incubation. Here is official
incubation application:
https://wiki.openstack
Le 27/02/2014 14:13, Doug Hellmann a écrit :
WSME supports both protocols without the API developer having to do
any extra work.
Doug
Just one comment about WSGI middlewares that we could create for Pecan,
we still need to handle both XML and JSON by hand. I do agree this is
not WSME relat
2014-02-26 19:40 GMT+01:00 Doug Hellmann :
>
> So you're not segregating the dynamic part of the API at all from the
> static part?
>
> Doug
>
>
No, you're right, at least with API V1 (Flask). As per our discussion, it
seems our use-case hasn't yet been implemented in WSME, so I'll provide a
diffe
to handle something similar to your use cases.
> I just sent a note to the ML with a Congress status update with the tag
> [Congress]. It includes links to our design docs. Let me know if you have
> trouble finding it or want to follow up.
>
> Tim
>
> - Original Message
Hi Jay,
Currently, the Nova scheduler only acts upon user request (either live
migration or boot an instance). IMHO, that's something Gantt should scope
later on (or at least there could be some space within the Scheduler) so
that Scheduler would be responsible for managing resources on a dynamic
Thanks Doug for replying,
2014-02-25 23:10 GMT+01:00 Doug Hellmann :
>
>
>
>> Do you have any idea on how I could get my goal, ie. having a static
>> input plus some extra variable inputs ? I was also thinking about playing
>> with __getattr__ and __setattr__ but I'm not sure the Registry could
2014-02-25 17:42 GMT+01:00 Dina Belova :
>
> >>> I think it should be a Climate "policy" (be careful, the name is
> confusing) : if admin wants to grant any new project for reservations, he
> should place a call to Climate. That's up to Climate-Nova (ie. Nova
> extension) to query Climate in order
e the extra attributes for the class. That happens one
> time, and the configuration does not depend on data that appears in the
> request itself.
>
> Doug
>
>
> On Tue, Feb 25, 2014 at 9:07 AM, Sylvain Bauza wrote:
>
>> Let me give you a bit of code then, that&#
2014-02-25 16:25 GMT+01:00 Dina Belova :
> Why should it require to be part of Keystone to hook up on Climate ?
>
>
> Sorry, can't get your point.
>
>
I'm just asking why we should hack Keystone workflow by adding an hook,
like we did for Nova. From my POV, that's not worth it.
> Provided we c
2014-02-25 15:38 GMT+01:00 Dina Belova :
> I guess that's simple and that's why nice solution for this problem.
>
> So you propose to implement that feature in following way:
> 1) mark project as 'reservable' during its creation in extras specs
> 2) add some more logic to reservable resources crea
gt;
>
>
> On Tue, Feb 25, 2014 at 6:55 AM, Sylvain Bauza wrote:
>
>> Hi,
>>
>> Thanks to WSME 0.6, there is now possibility to add extra attributes to a
>> Dynamic basetype.
>> I successfully ended up showing my extra attributes from a dict to a
>>
Hi Don,
Maybe it would be worth discussing on how we could share the blueprints
with people willing to help ?
-Sylvain
2014-02-24 18:08 GMT+01:00 Dugger, Donald D :
> All-
>
>
>
> I'm tempted to cancel the gantt meeting for tomorrow. The only topics I
> have are the no-db scheduler update (w
Hi,
Thanks to WSME 0.6, there is now possibility to add extra attributes to a
Dynamic basetype.
I successfully ended up showing my extra attributes from a dict to a
DynamicType using add_attributes() but I'm now stuck with POST requests
having dynamic body data.
Although I'm declaring in wsexpose
t in Climate, unless I missed something obvious.
-Sylvain
> Christian, correct me if I'm wrong, please
> Waiting for your comments
>
>
> On Thu, Feb 20, 2014 at 10:06 PM, Sylvain Bauza
> wrote:
>
>> Hi Christian,
>>
>> 2014-02-20 18:10 GMT+01:00 Mart
Hi Doug,
2014-02-20 17:37 GMT+01:00 Doug Hellmann :
> sphinxcontrib-pecanwsme is an extension to Sphinx for documenting APIs
> built with the Pecan web framework and WSME.
>
> What's New?
> ===
>
> - Remove the trailing slash from the end of the URLs, as it results in
> misleading featur
Hi Christian,
2014-02-20 18:10 GMT+01:00 Martinez, Christian :
> Hello all,
>
> I'm working in the following BP:
> https://blueprints.launchpad.net/climate/+spec/tenant-reservation-concept,
> in which the idea is to have the possibility to create "special" tenants
> that have a lease for all of
Hi Toan-Tran,
2014-02-19 9:40 GMT+01:00 Khanh-Toan Tran :
> > Agreed. I'm just thinking on the opportunity of providing a REST API
>
> > on top of the scheduler RPC API with a 1:1 matching, so that the Gantt
>
> > project would step up by itself. I don't think it's a hard stuff,
> provided I
>
>
;s a hard stuff, provided I
already did that stuff for Climate (providing Pecan/WSME API). What do you
think about it ? Even if it's not top priority, that's a quickwin.
-Sylvain
--
>
> Don Dugger
>
> "Censeo Toto nos in Kansa esse decisse." - D. Gale
>
> P
Hi Russell and Don,
2014-02-17 23:41 GMT+01:00 Russell Bryant :
> Greetings,
>
>
> 2) Gantt - We discussed the progress of the Gantt effort. After
> discussing the problems encountered so far and the other scheduler work
> going on, the consensus was that we really need to focus on decoupling
ilures how can we ensure
that a approved patch does a retry?
Thanks
Gary
From: Sylvain Bauza <mailto:sylvain.ba...@gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage
questions)" <mailto:openstack-dev@lists.openstack.org>>
Date: Monday, Februar
Hi Gary,
That's normal, this command has been removed since Dec'13, see
http://lists.openstack.org/pipermail/openstack-dev/2013-December/021649.html
-Sylvain
2014-02-17 13:00 GMT+01:00 Gary Kotton :
> Hi,
> It seems that the command 'reverify bug ' is not working. Anyone
> else experienced thi
Instead of limitating the consumed bandwidth by proposiong a configuration
flag (yet another one, and which default value to be set ?), I would
propose to only decrease the niceness of the process itself, so that other
processes would get first the I/O access.
That's not perfect I assume, but that'
I would vote for option #2 : move to oslo.messaging, that could be a quick
win.
2014-02-12 20:34 GMT+01:00 Doug Hellmann :
> The update script tries to be smart about the dependencies between
> modules, based on cross-module imports.
>
> It looks like the notifier middleware will need to move ou
2014-02-11 18:28 GMT+01:00 Yathiraj Udupi (yudupi) :
>
>
> Thanks for your pointers about Climate. I will take a closer look at it
> and try it out. So after a reservation lease for a VM is made by Climate,
> who acts on it to finally instantiate the VM ? Is it Climate or Nova should
> act on t
Le 11/02/2014 17:23, Yathiraj Udupi (yudupi) a écrit :
Hi Dina,
Thanks for note about Climate logic. This is something that will be
very useful, when we will have to schedule from Nova multiple
instances (of potentially different flavors) as a single request. If
the Solver Scheduler, can ma
Le 11/02/2014 16:09, Chris Friesen a écrit :
Yes. So what I'm suggesting is that we schedule the two VMs as one
call to the SolverScheduler. The scheduler then gets reservations for
the necessary resources and returns them to the caller. This would be
sort of like the existing Claim object
2014-02-10 18:45 GMT+01:00 Chris Friesen :
>
> In that model, we would pass a bunch of information about multiple
> resources to the solver scheduler, have it perform scheduling *and reserve
> the resources*, then return some kind of resource reservation tokens back
> to the caller for each resour
Thanks Doug,
2014-02-06 15:54 GMT+01:00 Doug Hellmann :
>
> cdf74daac2a204d5fe77f4b2bf5a956f65a73a6f Support dynamic types
> f191f32a722ef0c2eaad71dd33da4e7787ac2424 Add IntegerType and some classes
> for validation
>
> Doug
>
>
Do you know when the docs will be updated ? [1]
Some complex typ
hi Doug,
2014-02-04 Doug Hellmann :
>
>
>
> On Tue, Feb 4, 2014 at 9:43 AM, Sylvain Bauza wrote:
>
>>
>>
> If the exception has a "code" attribute, it is set as the status code for
> the response. Otherwise, the status is set to 500 as a default
Hi,
The WSME wsexpose() decorator for Pecan serializes any Exception being
raised on a controller [1]
I can understand the behaviour for security and visualization concerns, but
I was wondering if it was possible to add an extra parameter to the
decorator in order to explicitely raise the Excepti
Hi Julien,
2014-02-03 Julien Danjou :
>
> There's https://wiki.openstack.org/wiki/Python3 but it's not (always) up
> to date.
>
>
Thanks for the pointer, really helpful about the status for the main
projects and some key hints.
The interest never decreased, but it's always have been a long te
Hi,
I was at the FOSDEM event this week-end and some interesting talks about
asyncio raised my interest about this framework for replacing eventlet.
Although there is an experimental port of asyncio for Python >2.6 named
trollius [1], I think it would be a good move for having Python 3.
I know
401 - 500 of 614 matches
Mail list logo
