2018-05-18 19:58 GMT+08:00 Nadathur, Sundar :
> Hi Matt,
> On 5/17/2018 3:18 PM, Matt Riedemann wrote:
>
> On 5/17/2018 3:36 PM, Nadathur, Sundar wrote:
>
> This applies only to the resources that Nova handles, IIUC, which does not
> handle accelerators. The generic method that Alex talks about is
I have summarize some scenarios for fpga devices request.
https://etherpad.openstack.org/p/cyborg-fpga-request-scenarios
Please add more more scenarios to find out the exceptions that placement
can not satisfy the filter and weight.
IMOH, I refer placement to do filter and weight. If we have
As I know placement and nova scheduler dedicate to filter and weight.
Placement
and nova scheduler is responsible for avoiding race.
Nested provider + traits should cover most scenarios.
Any special case please let the nova developer and cyborg developer know,
let work together to get a solutio
got it, thanks.
2018-03-22 0:50 GMT+08:00 Ed Leafe :
> On Mar 21, 2018, at 11:35 AM, 少合冯 wrote:
> >
> >> By default, hosts are weighed one by one. You can subclass the
> BaseWeigher (in nova/weights.py) to weigh all objects at once.
> >
> > Does that means i
2018-03-22 0:11 GMT+08:00 Ed Leafe :
> On Mar 21, 2018, at 10:56 AM, 少合冯 wrote:
> >
> > Sorry, I did not attend the PTG.
> > Is it said there is a conclusion:
> > Scheduler weigher will call into Cyborg REST API for each host instead
> of one REST API for all h
For today's IRC discussion.
There is question about the weigher.
Can cyborg support a get list API to get more than one host accelerators
info when weigher.
Sorry, I did not attend the PTG.
Is it said there is a conclusion:
Scheduler weigher will call into Cyborg REST API for each host instead of
2018-03-07 10:36 GMT+08:00 Alex Xu :
>
>
> 2018-03-07 10:21 GMT+08:00 Alex Xu :
>
>>
>>
>> 2018-03-06 22:45 GMT+08:00 Mooney, Sean K :
>>
>>>
>>>
>>>
>>>
>>> *From:* Matthew Booth [mailto:mbo...@redhat.com]
>>> *Sent:* Saturday, March 3, 2018 4:15 PM
>>> *To:* OpenStack Development Mailing List (n
There's one current nova code define it as follow:
https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/api.py#L4535-L4546
that means: beside [ 'accepted', 'confirmed', 'reverted', 'error', 'failed'
], other status are all in progress.
Note: here finished is in progress.
John Garbutt
7; but
> that was not recommended or documented anywhere So in that case can we
> remove this old behaviour without version bump?
>
>
> [1].. https://github.com/openstack/ec2-api
>
> Regards
> Ghanshyam Mann
>
> On Tue, Feb 16, 2016 at 11:24 AM, Anne Gentle <
> anne
I guess others may ask the same questions.
I read the nova API doc:
such as this API:
http://developer.openstack.org/api-ref-compute-v2.1.html#showServer
GET /v2.1/{tenant_id}/servers/{server_id}
*Show server details*
*Request parameters*
ParameterStyleTypeDescription
tenant_id URI csapi:UU
still a question in line.
Thanks.
2016-01-08 21:53 GMT+08:00 Andrew Laski :
> On 01/08/16 at 12:33pm, John Garbutt wrote:
>
>> On 8 January 2016 at 08:17, 少合冯 wrote:
>>
>>> Hi, all
>>>
>>> Now I'm working on the migrations list/show API.
>&
Thank you very much. .
And Andrew Laski has answer my second question.
2016-01-08 20:33 GMT+08:00 John Garbutt :
> On 8 January 2016 at 08:17, 少合冯 wrote:
> > Hi, all
> >
> > Now I'm working on the migrations list/show API.
> > The new api defines migrations is
2016-01-08 21:53 GMT+08:00 Andrew Laski :
> On 01/08/16 at 12:33pm, John Garbutt wrote:
>
>> On 8 January 2016 at 08:17, 少合冯 wrote:
>>
>>> Hi, all
>>>
>>> Now I'm working on the migrations list/show API.
>>> The new api defines mi
Hi, all
Now I'm working on the migrations list/show API.
The new api defines migrations is a sub-collection of an instance.
GET v2.1/tenant_id/servers/server-id/migrations/migration-id
I need to support the new cell API to get a migration of a specified
instance.
get_migration_by_instance_and
Now,
I have notice:
https://review.openstack.org/#/c/258771/ (list/show migration)
https://review.openstack.org/#/c/245921/ (pause migration)
introduce the a new controller: ServerMigrationsController.
As we all know, the following cancel patch will also need it.
Also the above patches are
Hi all,
I'd like to talk about the delete instance device of nova.
Here is the libvirt doc string to describe it underly function
detachDeviceFlags.
http://paste.openstack.org/show/480330/
It says:
detaching a device from a running domain may be asynchronous.
*and it suggests:*
To check wheth
Carlton, Paul (Cloud Services)
> > Cc: 少合冯; OpenStack Development Mailing List (not for usage questions);
> > John Garbutt; Koniszewski, Pawel; Jin, Yuntong; Feng, Shaohe; Qiao,
> Liyong
> > Subject: RE: [nova] [RFC] how to enable xbzrle compress for live
> migration
> >
&
2015-11-30 14:45 GMT+08:00 Koniszewski, Pawel :
> > -Original Message-
> > From: Murray, Paul (HP Cloud) [mailto:pmur...@hpe.com]
> > Sent: Friday, November 27, 2015 4:29 PM
> > To: Daniel P. Berrange; Carlton, Paul (Cloud Services)
> > Cc: 少合冯; OpenStack Dev
2015-11-27 19:49 GMT+08:00 Daniel P. Berrange :
> On Fri, Nov 27, 2015 at 07:37:50PM +0800, 少合冯 wrote:
> > 2015-11-27 2:19 GMT+08:00 Daniel P. Berrange :
> >
> > > On Thu, Nov 26, 2015 at 05:39:04PM +, Daniel P. Berrange wrote:
> > > > On Thu, Nov 26,
2015-11-27 2:19 GMT+08:00 Daniel P. Berrange :
> On Thu, Nov 26, 2015 at 05:39:04PM +, Daniel P. Berrange wrote:
> > On Thu, Nov 26, 2015 at 11:55:31PM +0800, 少合冯 wrote:
> > > 3. dynamically choose when to activate xbzrle compress for live
> migration.
> &
Hi all,
We want to support xbzrle compress for live migration.
Now there are 3 options,
1. add the enable flag in nova.conf.
such as a dedicated 'live_migration_compression=on|off" parameter in
nova.conf.
And nova simply enable it.
seems not good.
2. add a parameters in live migration
Agree. Why not both. and will use created_at to work out how long the
migration has been
running.
Paul, thank you very much for the suggestion.
BR.
Shaohe Feng
2015-11-26 19:10 GMT+08:00 Paul Carlton :
> On 26/11/15 10:48, 少合冯 wrote:
>
> Now, we are agree on getting more migrati
Useful information.
Thank you Gibi.
BR
Shaohe Feng..
2015-11-26 21:29 GMT+08:00 Balázs Gibizer :
> > -Original Message-
> > From: Paul Carlton [mailto:paul.carlt...@hpe.com]
> > Sent: November 26, 2015 12:11
> > On 26/11/15 10:48, 少合冯 wrote:
> >
>
Now, we are agree on getting more migration status details info are useful.
But How do we get them?
By REST API or Notification?
IF by API, does the "time_elapsed" is needed?
For there is a "created_at" field.
But IMO, it is base on the time of the conductor server?
The time_elapsed can get fr
Hi Paul,
Comments inline:
2015-11-23 16:36 GMT+08:00 Paul Carlton :
> John
>
> At the live migration sub team meeting I undertook to look at the issue
> of progress reporting.
>
> The use cases I'm envisaging are...
>
> As a user I want to know how much longer my instance will be migrating
> for.
2015-01-13 13:57 GMT+08:00 少合冯 :
> Hello,
>
> I'd like to request an exception for Attach/Detach SR-IOV interface
> feature. [1]
> This is an important feature that aims to improve better performance than
> normal
> network interface in guests and not too hard to implem
Hello,
I'd like to request an exception for Attach/Detach SR-IOV interface
feature. [1]
This is an important feature that aims to improve better performance than
normal
network interface in guests and not too hard to implement.
Thanks,
Shao He, Feng
[1] https://review.openstack.org/#/c/139910/
_
Hello,
I'd like to request an exception for Attach/Detach SR-IOV interface
feature. [1]
This is an important feature that aims to improve better performance than
normal
network interface in guests and not too hard to implement.
Thanks,
Shao He, Feng
[1] https://review.openstack.org/#/c/139910/
<
28 matches
Mail list logo
