Re: [openstack-dev] [Nova][FFE] Feature freeze exception for virt-driver-numa-placement

On 4 September 2014 14:07, Nikola Đipanov ndipa...@redhat.com wrote: On 09/04/2014 02:31 PM, Sean Dague wrote: On 09/04/2014 07:58 AM, Nikola Đipanov wrote: Hi team, I am requesting the exception for the feature from the subject (find specs at [1] and outstanding changes at [2]). Some

Re: [openstack-dev] [Nova][FFE] Feature freeze exception for virt-driver-numa-placement

Anyway, not enough to -1 it, but enough to at least say something. .. but I do not want to get into the discussion about software testing here, not the place really. However, I do think it is very harmful to respond to FFE request with such blanket statements and generalizations,

[openstack-dev] [Nova] [Gantt] Scheduler split status (updated)

Hi All, I'm sorry I am so late to this lively discussion - it looks a good one! Jay has been driving the debate a bit so most of this is in response to his comments. But please, anyone should chip in. On extensible resource tracking Jay, I am surprised to hear you say no one has explained to

Re: [openstack-dev] [nova] Question about addit log in nova-compute.log

Comment inline at bottom of message... -Original Message- From: Jay Pipes [mailto:jaypi...@gmail.com] Sent: 06 May 2014 18:44 To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [nova] Question about addit log in nova-compute.log On 05/06/2014 01:37 PM, Jiang, Yunhong

Re: [openstack-dev] [nova] Proposal: Move CPU and memory allocation ratio out of scheduler

Hi Jay, This sounds good to me. You left out the part of limits from the discussion – these filters set the limits used at the resource tracker. You also left out the force-to-host and its effect on limits. Yes, I would agree with doing this at the resource tracker too. And of course the

Re: [openstack-dev] [Nova] Thoughts about how to enforce DB and object models mapping

Hi Sylvain, I think the idea is that anyone making changes to the db data model has to make changes to the corresponding object and that is captured in the data model implications of nova-specs (or it should be). Then reviewers check it is done. Tests on the objects will necessarily exercise

Re: [openstack-dev] [nova] Proposal: Move CPU and memory allocation ratio out of scheduler

of scheduler On 06/04/2014 06:10 AM, Murray, Paul (HP Cloud) wrote: Hi Jay, This sounds good to me. You left out the part of limits from the discussion - these filters set the limits used at the resource tracker. Yes, and that is, IMO, bad design. Allocation ratios are the domain of the compute

[openstack-dev] [Nova] structure of supported_instances field (architecture, hypervisor type, vm mode) ?

Hi All, I have a question about information used to determine if a host supports an image. The virt drivers all provide a list of triples of the form (architecture, hypervisor type, vm mode). Each triple is compared to the corresponding three image properties in a request in the scheduler

Re: [openstack-dev] [Nova] structure of supported_instances field (architecture, hypervisor type, vm mode) ?

FYI I'm currently working on changing the get_available_resources() method to return a formal object, instead of its horrible undocumented dict(). With this, the current list of lists / JSON used for supported_instances will turn into a formal object with strict validation. Regards, Thanks

[openstack-dev] [Nova] object field naming question

Hi All, The following question relates to this change: https://review.openstack.org/#/c/125091/ This change adds a field to the ComputeNode object called supported_instances. It also adds an object called SupportedInstance that has fields called arch, hvtype and vm_mode. All these names

Re: [openstack-dev] [Nova] object field naming question

will map to the supported_instances field in the compute_nodes table. Thanks for helping, Paul From: Paul Murray [mailto:ptma...@gmail.com] Sent: 10 October 2014 13:00 To: Murray, Paul (HP Cloud) Subject: Fwd: [openstack-dev] [Nova] object field naming question -- Forwarded message

Re: [openstack-dev] [nova] Pulling nova/virt/hardware.py into nova/objects/

I spent a little time trying to work out a good way to include this kind of data in the ComputeNode object. You will have seen that I added the supported_instances reported to the RT by the virt drivers as a list of HVSpec – where HVSpec is a new nova object I created for the purpose. The

Re: [openstack-dev] [gantt] Scheduler sub-group meeting agenda 11/11

The resource tracker objects BP was grouped under the scheduler work items as well: http://specs.openstack.org/openstack/nova-specs/specs/kilo/approved/make-resource-tracker-use-objects.html - 1) Summit recap 2) Status of

[openstack-dev] [ironic][nova] ironic driver retries on ironic driver Conflict response

Hi All, Looking at the ironic virt driver code in nova it seems that a Conflict (409) response from the ironic client results in the driver re-trying the request. Given the comment below in the ironic code I would imagine that is not the right behavior - it reads as though this is something

[openstack-dev] [nova] Networks are not cleaned up in build failure

Hi All, I recently experienced failures getting images from Glance while spawning instances. This step comes after building the networks in the guild sequence. When the Glance failure occurred the instance was cleaned up and rescheduled as expected, but the networks were not cleaned up. On

Re: [openstack-dev] [Nova][Ironic] Question about scheduling two instances to same baremetal node

There is bug when running nova with ironic https://bugs.launchpad.net/nova/+bug/1402658 I filed this bug – it has been a problem for us. The problem is at scheduler side the IronicHostManager will consume all the resources for that node whatever how much resource the instance used. But at

Re: [openstack-dev] [nova] Deprecation of ComputeFilter

Hi Sylvain, The list of filters does not only determine what conditions are checked, it also specifies the order in which they are checked. If I read the code right this change creates the worst case efficiency for this filter. Normally you would filter first on something that removes as many

[openstack-dev] [Nova] pci stats format and functional tests

Hi All, I know Yunhong Jiang and Daniel Berrange have been involved in the following, but I thought it worth sending to the list for visibility. While writing code to convert the resource tracker to use the ComputeNode object realized that the api samples used in the functional tests are not

Re: [openstack-dev] [nova][cinder] Would anyone from Nova Core be able to join the Cinder mid-cycle meetup?

Hi jay, There are a few Nova people in HP who intend to work on this area (perhaps you have heard that from Scott or Duncan). In fact I brought up that this would be coming up in Vancouver and that we intend to support it. Unfortunately none of us are available that week. I would like to be

Re: [openstack-dev] [nova][cinder] Would anyone from Nova Core be able to join the Cinder mid-cycle meetup?

, Paul (HP Cloud) Sent: 28 July 2015 12:52 To: 'jsbry...@electronicjungle.net'; OpenStack Development Mailing List (not for usage questions) Cc: Rosa, Andrea (HP Cloud Services) Subject: RE: [openstack-dev] [nova][cinder] Would anyone from Nova Core be able to join the Cinder mid-cycle meetup? Hi

Re: [openstack-dev] [nova][cinder] About rebuilding volume-backed instances.

> Unfortunately, you're trying to work around misuse of the cloud API's, not > missing features from them. Don't use those volume types, and don't build > systems that rely on single ports and interfaces. IMO rebuild is a misguided > concept (something that took me a long time to realize).

Re: [openstack-dev] [Nova] live migration sub-team meeting

that the appropriate specs and code reviews are listed on the tracking pages. Please also take time to review specs and code. Please contact me or respond to this email thread if there is anything you want to see on the agenda for the first meeting. Regards, Paul From: Murray, Paul (HP Cloud

[openstack-dev] [Nova] Nova live migration subteam meeting

A quick reminder: the first live migration subteam IRC meeting is today at 1400 UTC on #openstack-meeting-3. See: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration Regards, Paul Paul Murray Nova Technical Lead, HPE Cloud Hewlett Packard Enterprise +44 117 316 2527

Re: [openstack-dev] [Nova] live migration sub-team meeting

-dev] [Nova] live migration sub-team meeting So, its been a week. What time are we picking? Michael On Thu, Nov 5, 2015 at 10:46 PM, Murray, Paul (HP Cloud) <pmur...@hpe.com<mailto:pmur...@hpe.com>> wrote: > > Most team members expressed they would like a regular IRC meeting for

[openstack-dev] [Nova] live migration sub-team meeting

Hi all, Live migration was confirmed as a Nova priority for the Mitaka cycle and a sub-team section can be found on the priorities tracking page [1]. Most team members expressed they would like a regular IRC meeting for tracking work and raising blocking issues. Looking at the contributors

Re: [openstack-dev] [Nova] live migration sub-team meeting

> > Most team members expressed they would like a regular IRC meeting for > > tracking work and raising blocking issues. Looking at the contributors > > here [2], most of the participants seem to be in the European > > continent (in time zones ranging from UTC to UTC+3) with a few in the > > US

[openstack-dev] [Nova] attaching and detaching volumes in the API

Normally operations on instances are synchronized at the compute node. In some cases it is necessary to synchronize somehow at the API. I have one of those cases and wondered what is a good way to go about it. As part of this spec: https://review.openstack.org/#/c/221732/ I want to

Re: [openstack-dev] [Nova] Migration state machine proposal.

> From: Jay Pipes [mailto:jaypi...@gmail.com] > On 10/27/2015 01:16 PM, Chris Friesen wrote: > > On 10/26/2015 06:02 PM, Jay Pipes wrote: > > > >> I believe strongly that we should deprecate the existing migrate, > >> resize, an live-migrate APIs in favor of a single consolidated, > >>

Re: [openstack-dev] [Nova] Migration state machine proposal.

> From: Ed Leafe [mailto:e...@leafe.com] > On Nov 5, 2015, at 2:43 AM, Tang Chen wrote: > > > I'm sorry that I cannot understand why resize and migrate are the same > thing behind. > > Resize is essentially a migration to the same host, rather than a different > host.

Re: [openstack-dev] Custom Nova scheduler based on CPU queue length

Hi Rahul, > As I understand a weigher for the filter scheduler that weighs filtered host > machines based on the host weight option, 'cpu.percent' can be > configured to prioritize the hosts based on CPU percentage, but there are > only limited options when it comes to filtering of machines in

[openstack-dev] [Nova] What is the no_device flag for in block device mapping?

Hi All, I'm wondering what the "no_device" flag is used for in the block device mappings. I had a dig around in the code but couldn't figure out why it is there. The name suggests an obvious meaning, but I've learnt not to guess too much from names. Any pointers welcome. Thanks Paul Paul

Re: [openstack-dev] [nova] live migration in Mitaka

> Please respond to this post if you have an interest in this and what you > would like to see done. > Include anything you are already getting on with so we get a clear picture. Thank you to those who replied to this thread. I have used the contents to start an etherpad page here:

[openstack-dev] [nova] live migration in Mitaka

Hi All, There are various efforts going on around live migration at the moment: fixing up CI, bug fixes, additions to cover more corner cases, proposals for new operations Generally live migration could do with a little TLC (see: [1]), so I am going to suggest we give some of that care in

[openstack-dev] [Nova] Nova mid cycle details

The Nova Mitaka mid cycle meetup is in Bristol, UK at the Hewlett Packard Enterprise office. The mid cycle wiki page is here: https://wiki.openstack.org/wiki/Sprints/NovaMitakaSprint Note that there is a web site for signing up for the event and booking hotel rooms at a reduced event rate

[openstack-dev] [Nova] live migration meeting

Hi All, The first live migration meeting of the year will be tomorrow - see the meeting page: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration Agenda on the page, feel free to add. Happy New Year, Paul Paul Murray Technical Lead, HPE Cloud Hewlett Packard Enterprise +44 117 316 2527

Re: [openstack-dev] [nova] [RFC] how to enable xbzrle compress for live migration

tong@intel.com; > shaohe.f...@intel.com; Murray, Paul (HP Cloud); liyong.q...@intel.com > Subject: Re: [nova] [RFC] how to enable xbzrle compress for live migration > > On Thu, Nov 26, 2015 at 05:49:50PM +, Paul Carlton wrote: > > Seems to me the prevailing view is that we sho

Re: [openstack-dev] [Nova] Nova mid cycle details

details Hey, I filled in the first part of that page, but when it got to hotels I got confused. The web site doesn't seem to mention the night rate for the HP price. Do you know what that is? Thanks, Michael On Sat, Nov 28, 2015 at 3:06 AM, Murray, Paul (HP Cloud) <pmur...@hpe.com<mailt

[openstack-dev] [Nova] [Live Migration] topics for midcycle

Hi All, Following up on a question raised in the live migration meeting yesterday about organizing topics for the mid cycle: please add topic suggestions to https://etherpad.openstack.org/p/mitaka-nova-midcycle and we will review them in next week's meeting. Paul Paul Murray Technical Lead,

[openstack-dev] [Nova] Live migration meeting tomorrow

The agenda is here: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration With the non-priority spec freeze having passed there is not much on the agenda at the moment. If you have anything to add please feel free. Regards, Paul

Re: [openstack-dev] [nova] theoretical race between live migration and resource audit?

Hi Chris, you are right – and I think there are several synchronization issues in the code there. The migration process should be synchronized as it is in build_run_instance etc. At the moment if pre_live_migrate fails due to an RPC timeout (i.e. it takes too long for some reason) the rollback

Re: [openstack-dev] [Nova] State machines in Nova

> -Original Message- > From: Monty Taylor [mailto:mord...@inaugust.com] > Sent: 01 June 2016 13:54 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Nova] State machines in Nova > > On 06/01/2016 03:50 PM, Andrew Laski wrote: > > > > > > On Wed, Jun 1, 2016, at

Re: [openstack-dev] [Nova] State machines in Nova

> -Original Message- > From: Andrew Laski [mailto:and...@lascii.com] > Sent: 31 May 2016 22:34 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Nova] State machines in Nova > > > > On Tue, May 31, 2016, at 04:26 PM, Joshua Harlow wrote: > > Timofei Durakov

[openstack-dev] [Nova] Live Migration meeting

Sorry for late update - this weekend was a holiday in UK Agenda: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [Nova] Live migration meeting today

Agenda here: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration We will go over the non-priority feature status today Paul __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [Nova] Nova midcycle list of attendees

I have created a list of attendees for the Nova midcycle here: https://wiki.openstack.org/wiki/Sprints/NovaMitakaSprintAttendees Obviously I can't put anyone's name on it for privacy reasons. If are attending and you would like to let others know when you will be around you might like to add

[openstack-dev] [Nova][Live Migration] Live migration IRC meeting today

Hi All, Forgot to hit "save" on agenda yesterday - the agenda is up. Speak to you later. Paul Paul Murray Technical Lead, HPE Cloud Hewlett Packard Enterprise +44 117 316 2527 __ OpenStack Development Mailing List (not

[openstack-dev] [Nova] Update on live migration priority

This time with a tag in case anyone is filtering... From: Murray, Paul (HP Cloud) Sent: 12 February 2016 16:16 To: openstack-dev@lists.openstack.org Subject: [openstack-dev] Update on live migration priority The objective for the live migration priority is to improve the stability of migrations

[openstack-dev] Update on live migration priority

The objective for the live migration priority is to improve the stability of migrations based on operator experience. The high level approach is to do the following: 1. Improve CI 2. Improve documentation 3. Improve manageability of migrations 4. Fix bugs In this

Re: [openstack-dev] [nova] Migration progress

> -Original Message- > From: Daniel P. Berrange [mailto:berra...@redhat.com] > Sent: 03 February 2016 10:49 > To: OpenStack Development Mailing List (not for usage questions) > Cc: Feng, Shaohe > Subject: Re: [openstack-dev] [nova] Migration progress > > On Wed, Feb 03, 2016 at

[openstack-dev] [Nova] mid-cycle arrangements

See updated event detail information for the mid-cycle at: https://wiki.openstack.org/wiki/Sprints/NovaMitakaSprint Paul Paul Murray Technical Lead, HPE Cloud Hewlett Packard Enterprise +44 117 316 2527 __ OpenStack

[openstack-dev] [Nova][Live Migration] no live migration meeting this week

This is just a short reminder that there will be no live migration meeting this week due to the mid cycle. Agenda and other information always available at: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration Paul Paul Murray Technical Lead, HPE Cloud Hewlett Packard Enterprise +44 117

Re: [openstack-dev] [nova][cinder] volumes stuck detaching attaching and force detach

> -Original Message- > From: D'Angelo, Scott > > Matt, changing Nova to store the connector info at volume attach time does > help. Where the gap will remain is after Nova evacuation or live migration, This will happen with shelve as well I think. Volumes are not detached in shelve

Re: [openstack-dev] [nova] Nova PTL for Newton

Thanks for a job well done John and for being so available to help us all. Paul > -Original Message- > From: John Garbutt [mailto:j...@johngarbutt.com] > Sent: 11 March 2016 19:22 > To: OpenStack Development Mailing List d...@lists.openstack.org> > Subject: [openstack-dev] [nova] Nova

Re: [openstack-dev] [nova] New resource tracker

> -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: 04 April 2016 18:47 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [nova] New resource tracker > > On 04/04/2016 01:21 PM, Rayson Ho wrote: > > I found that even in the latest git tree,

Re: [openstack-dev] [Nova] Live Migration post feature freeze update

> > > > > > On 3/4/2016 10:34 AM, Murray, Paul (HP Cloud) wrote: > >> Hi All, > >> - snip 8<-- > > > > The gate-tempest-dsvm-multinode-full job which runs live migration > > tests on nova patches has been non-voting fo

[openstack-dev] [Nova] Live Migration post feature freeze update

Hi All, Now that we have passed the feature freeze I thought it was worth giving a quick update on where we are with the live migration priority. The following is a list of work items that have been merged in this cycle ( for the live migration sub-team's working page see

[openstack-dev] [Nova] Live migration meeting today: beware summer time !

The live migration meeting is today at usual time, but beware: a lot of time zones have switch to summer time this week. Agenda: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration Paul P.S. Sorry for late update - it was a national holiday in UK yesterday

[openstack-dev] [Nova] live migration meeting Tuesday

The live migration meeting is at the usual time on Tuesday, please feel free to add items to the agenda. https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration Regards, Paul Paul Murray Technical Lead, HPE Cloud Hewlett Packard Enterprise +44 117 316 2527

Re: [openstack-dev] [all] [devstack] Adding example "local.conf" files for testing?

Absolutely, yes +1 Paul From: ZhiQiang Fan [mailto:aji.zq...@gmail.com] Sent: 21 April 2016 12:34 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [all] [devstack] Adding example "local.conf" files for testing?

Re: [openstack-dev] [Nova] Live Migration: Austin summit update

Thanks Matt, I meant to cover CI but clearly omitted it. > On 30 Apr 2016, at 02:35, Matt Riedemann <mrie...@linux.vnet.ibm.com> wrote: > >> On 4/29/2016 5:32 PM, Murray, Paul (HP Cloud) wrote: >> The following summarizes status of the main topics relating to

Re: [openstack-dev] [nova] Thoughts on deprecating the legacy bdm v1 API support

> -Original Message- > From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > Sent: 17 May 2016 15:48 > To: OpenStack Development Mailing List (not for usage questions) > > Subject: [openstack-dev] [nova] Thoughts on deprecating the legacy bdm v1 >

[openstack-dev] [Nova] change console proxy URL for cells v2 ?

I am implementing the following spec and have encountered a problem related to the form of the console proxy URL provided to uses. https://specs.openstack.org/openstack/nova-specs/specs/newton/approved/convert-consoles-to-objects.html The spec changes the representation of the console auth

[openstack-dev] [Nova] Live migration meeting today

Agenda: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration Please add items if you want to guarantee time to talk about them. Paul __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [Nova] Live Migration: Austin summit update

The following summarizes status of the main topics relating to live migration after the Newton design summit. Please feel free to correct any inaccuracies or add additional information. Paul - Libvirt storage pools The storage pools

[openstack-dev] [Nova] Live migration meeting today

First live migration meeting to kick off after the summit will be today, see: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration Paul __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [nova] Should be instance_dir in all nova compute node same ?

The instance path is assumed to be the same everywhere. When using libvirt to do cold migration/resize the source host creates the instance directory on the target host using ssh and then copies the files to it using scp. So the target host doesn’t even get to determine where its own files are

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

> -Original Message- > From: Edward Leafe [mailto:e...@leafe.com] > Sent: 05 May 2016 04:32 > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [nova][osc] Use of openstack client for admin > commands >

[openstack-dev] [Nova] Live migration IRC meeting on 26th July

The next live migration meeting is on 26th July. For agenda see: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration (still being updated) Paul __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [Nova] Quick poll for live migration meeting this week

Just to confirm, next meeting will be after the mid cycle, I will update the agenda nearer the time: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration Paul From: Murray, Paul (HP Cloud) Sent: 11 July 2016 13:32 To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [Nova

[openstack-dev] [Nova][SR-IOV][pci-passthrough] Reporting pci devices in hypervisor-show

Hi All, At the moment I am not aware of a nova api call that provides information about the pci devices on a host. The most obvious place to put this would be in hypervisor-show. I wonder if anyone has made an attempt at this already or if there are any reasons for not adding pci information

[openstack-dev] [Nova] Quick poll for live migration meeting this week

Hi All, I think we can skip the live migration meeting this week unless anyone has something specific to discuss. Next week is the mid cycle, so I suggest the next meeting should be Tuesday 26th July. Please let me know if you agree or disagree. Unless I hear otherwise I will assume its ok to

Re: [openstack-dev] [Nova][Neutron][Live-Migration] Cross l2 agent migration and solving Nova-Neutron live migration bugs

> -Original Message- > From: Carl Baldwin [mailto:c...@ecbaldwin.net] > Sent: 29 June 2016 22:20 > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [Nova][Neutron][Live-Migration] Cross l2 agent >

[openstack-dev] [Nova] live migration meeting today

See agenda and add if you have something to bring up: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration Paul __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [Nova] Live migration IRC meeting

There will be a live migration sub team meeting today, see: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration Paul __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [Nova] Iive migration IRC meeting

There will be a meeting today – just amended the agenda: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration Paul __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [Nova] Live migration IRC meeting

There will be a live migration meeting today – agenda and time here: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration Paul __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [nova][libvirt] Lets make libvirt's domain XML canonical

k-dev] [nova][libvirt] Lets make libvirt's domain XML canonical On Fri, Sep 30, 2016 at 4:38 PM, Murray, Paul (HP Cloud) <pmur...@hpe.com<mailto:pmur...@hpe.com>> wrote: On 27/09/2016, 18:12, "Daniel P. Berrange" <berra...@redhat.com<mailto:berra...@redhat.com>>

Re: [openstack-dev] [nova][libvirt] Lets make libvirt's domain XML canonical

On 27/09/2016, 18:12, "Daniel P. Berrange" wrote: >On Tue, Sep 27, 2016 at 10:40:34AM -0600, Chris Friesen wrote: >> On 09/27/2016 10:17 AM, Matthew Booth wrote: >> >> > I think we should be able to create a domain, but once created we should >> > never >> > redefine

[openstack-dev] [Nova] Live migration sub-team lead

Hi All, I have had the pleasure of chairing the live migration sub-team for the last year. Recently, as some of you will have noticed, my time has been stretched to the extent that I have started to neglect the task. Timofei Durakov has stood in for me on several occasions recently and has now

Re: [openstack-dev] [Nova] Detect changes in object model

work to allow the changes and to track them there too. Paul. -Original Message- From: Dan Smith [mailto:d...@danplanet.com] Sent: 10 January 2014 14:42 To: Wang, Shane; OpenStack Development Mailing List (not for usage questions) Cc: Murray, Paul (HP Cloud Services); Lee, Alexis; Tan

Re: [openstack-dev] [Nova] Detect changes in object model

you see these belonging here or would you expect those to go in a sub-class if they were wanted? Paul. -Original Message- From: Dan Smith [mailto:d...@danplanet.com] Sent: 10 January 2014 16:22 To: Murray, Paul (HP Cloud Services); Wang, Shane; OpenStack Development Mailing List

Re: [openstack-dev] [Nova] Detect changes in object model

happy with your dirty children :) Paul. -Original Message- From: Dan Smith [mailto:d...@danplanet.com] Sent: 13 January 2014 15:26 To: Murray, Paul (HP Cloud Services); Wang, Shane; OpenStack Development Mailing List (not for usage questions) Cc: Lee, Alexis; Tan, Lin Subject: Re: [Nova

Re: [openstack-dev] [nova] how is resource tracking supposed to work for live migration and evacuation?

To be clear - the changes that Yunhong describes below are not part of the extensible-resource-tracking blueprint. Extensible-resource-tracking has the more modest aim to provide plugins to track additional resource data. Paul. -Original Message- From: Jiang, Yunhong

Re: [openstack-dev] [Nova] bp proposal: discovery of peer instances through metadata service

Hi Justin, It's nice to see someone bringing this kind of thing up. Seeding discovery is a handy primitive to have. Multicast is not generally used over the internet, so the comment about removing multicast is not really justified, and any of the approaches that work there could be used.

Re: [openstack-dev] [Nova] bp proposal: discovery of peer instances through metadata service

Barbara [mailto:jus...@fathomdb.com] Sent: 24 January 2014 21:01 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova] bp proposal: discovery of peer instances through metadata service Murray, Paul (HP Cloud Services) wrote: Multicast is not generally

[openstack-dev] [Nova][Scheduler] Will the Scheuler use Nova Objects?

Hi, I have heard a couple of conflicting comments about the scheduler and nova objects that I would like to clear up. In one scheduler/gantt meeting, Gary Kotton offered to convert the scheduler to use Nova objects. In another I heard that with the creation of Gantt, the scheduler would avoid

[openstack-dev] [Nova] do nova objects work for plugins?

I was looking through Nova Objects with a view to creating an extensible object that can be used by writers of plugins to include data generated by the plugin (others have also done the same e.g. https://review.openstack.org/#/c/65826/ ) On the way I noticed what I think is a bug in Nova

Re: [openstack-dev] [Nova] do nova objects work for plugins?

, but I think I can get on with it. Paul. -Original Message- From: Dan Smith [mailto:d...@danplanet.com] Sent: 03 February 2014 20:59 To: Murray, Paul (HP Cloud Services); OpenStack Development Mailing List (not for usage questions) Subject: Re: [Nova] do nova objects work for plugins

Re: [openstack-dev] about the bp cpu-entitlement

Hi Sahid, This is being done by Oshrit Feder, so I'll let her answer, but I know that it is going to be implemented as an extensible resource (see: https://blueprints.launchpad.net/nova/+spec/extensible-resource-tracking) so it is waiting for that to be done. That blueprint is making good

[openstack-dev] [Nova] What is the currently accepted way to do plugins

Hi All, One of my patches has a query asking if I am using the agreed way to load plugins: https://review.openstack.org/#/c/71557/ I followed the same approach as filters/weights/metrics using nova.loadables. Was there an agreement to do it a different way? And if so, what is the agreed way

Re: [openstack-dev] [Nova] What is the currently accepted way to do plugins

March 2014 17:50 To: OpenStack Development Mailing List (not for usage questions); Murray, Paul (HP Cloud Services) Subject: RE: [openstack-dev] [Nova] What is the currently accepted way to do plugins This brings up something that's been gnawing at me for a while now ... why use entry-point based

Re: [openstack-dev] [nova] RFC - using Gerrit for Nova Blueprint review approval

The principle is excellent, I think there are two points/objectives worth keeping in mind: 1. We need an effective way to make and record the design decisions 2. We should make the whole development process easier In my mind the point of the design review part is to agree up front something

Re: [openstack-dev] [Nova] What is the currently accepted way to do plugins

for blueprints). But now I am referring to another thread [http://lists.openstack.org/pipermail/openstack-dev/2014-March/029232.html ] Paul. -Original Message- From: Sandy Walsh [mailto:sandy.wa...@rackspace.com] Sent: 04 March 2014 21:25 To: Murray, Paul (HP Cloud Services) Cc

Re: [openstack-dev] [Nova] Hosts within two Availability Zones : possible or not ?

Hi Sylvain, I would go with keeping AZs exclusive. It is a well-established concept even if it is up to providers to implement what it actually means in terms of isolation. Some good use cases have been presented on this topic recently, but for me they suggest we should develop a better

Re: [openstack-dev] [nova][scheduler][metrics] Additional metrics

Hi Abbass, I am in the process of coding some of this now - take a look at https://blueprints.launchpad.net/nova/+spec/extensible-resource-tracking - now has a specification document attached https://etherpad.openstack.org/p/IcehouseNovaExtensibleSchedulerMetrics - the design summit session

Re: [openstack-dev] [nova][database] Update compute_nodes table

Hi Abbass, I guess you read the blueprint Russell referred to. I think you actually are saying the same - but please read steps below and tell me if they don't cover what you want. This is what it will do: 1. Add a column to the compute_nodes table for a JSON blob 2. Add plug-in

Re: [openstack-dev] [Nova] New DB column or new DB table?

Hi All, I would like to chip in with something from the side here (sorry to stretch the discussion out). I was looking for a mechanism to do something like this in the context of this blueprint on network aware scheduling:

Re: [openstack-dev] [Nova] New DB column or new DB table?

to me. BTW, I'm getting all the other emails - just not this thread! Bemused... Paul On 07/18/2013 10:44 AM, Murray, Paul (HP Cloud Services) wrote: Hi All, I would like to chip in with something from the side here (sorry to stretch the discussion out). I was looking for a mechanism to do

Re: [openstack-dev] [Nova] Ceilometer vs. Nova internal metrics collector for scheduling (was: New DB column or new DB table?)

Hi Sean, Do you think the existing static allocators should be migrated to going through ceilometer - or do you see that as different? Ignoring backward compatibility. The reason I ask is I want to extend the static allocators to include a couple more. These plugins are the way I would have

Re: [openstack-dev] [Nova] Ceilometer vs. Nova internal metrics collector for scheduling

[mailto:s...@dague.net] Sent: 19 July 2013 14:28 To: OpenStack Development Mailing List Subject: Re: [openstack-dev] [Nova] Ceilometer vs. Nova internal metrics collector for scheduling On 07/19/2013 08:30 AM, Andrew Laski wrote: On 07/19/13 at 12:08pm, Murray, Paul (HP Cloud Services) wrote: Hi Sean

  1   2   >