Re: [openstack-dev] [nova] Enabling VM post-copy live migration

On 12 March 2015 at 12:26, Luis Tomas wrote: > On 03/12/2015 12:34 PM, John Garbutt wrote: >> >> On 12 March 2015 at 08:41, Luis Tomas wrote: >>> >>> Hi, >>> >>> As part of an European (FP7) project, named ORBIT >>> (http://www.orbitp

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

On 16 March 2015 at 14:15, Sean Dague wrote: > Our current top level shipped example paste.ini for Nova includes the > following set of endpoint definitions: > > [composite:osapi_compute] > use = call:nova.api.openstack.urlmap:urlmap_factory > /: oscomputeversions > /v1.1: openstack_compute_api_v2

Re: [openstack-dev] [nova] how to handle vendor-specific API microversions?

On 21 March 2015 at 18:12, Joe Gordon wrote: > On Sat, Mar 21, 2015 at 8:31 AM, Monty Taylor wrote: >> On 03/21/2015 01:21 AM, Chris Friesen wrote: >> > Hi, >> > >> > I've recently been playing around a bit with API microversions and I >> > noticed something that may be problematic. >> > >> > The

Re: [openstack-dev] [nova] OpenStack nova resize command

Generally the VM is powered down, then has the additional resources added (such as increasing the size of the disk), then is started back up again. There have been some suggested blueprints/specs for a "live" resize, where thats possible. But I have not seen any work on that recently, as far as I

[openstack-dev] [Nova] PTL Candidacy

Hi, I am johnthetubaguy on IRC. I would like to run for the OpenStack Compute (Nova) PTL position. I currently work as a Principal Engineer at Rackspace, focusing on software development for the Rackspace public cloud. Background == I started working with Nova in late 2010, working on

Re: [openstack-dev] [Nova] PTL Candidacy

On 8 April 2015 at 21:19, Anita Kuno wrote: > On 04/08/2015 02:25 PM, John Garbutt wrote: >> Hi, >> >> I am johnthetubaguy on IRC. >> >> I would like to run for the OpenStack Compute (Nova) PTL position. >> >> I currently work as a Principal E

Re: [openstack-dev] [Nova] VMware CI

I have updated the bug so it's high priority and tagged with kilo-rc-potential, and added your note from below as a comment on the bug. It looks like it might be worth a backport so it gets into RC2? Can anyone take that bit on please? Thanks, John On Sunday, April 12, 2015, Gary Kotton wrote:

Re: [openstack-dev] [nova] why is evacuate marked as missing for libvirt?

On 14 April 2015 at 18:44, Russell Bryant wrote: > On 04/14/2015 12:22 PM, Matt Riedemann wrote: >> This came up in IRC this morning, but the hypervisor support matrix is >> listing evacuate as 'missing' for the libvirt driver: >> >> http://docs.openstack.org/developer/nova/support-matrix.html#ope

Re: [openstack-dev] [Nova][Neutron] Cross-project coordination

On 22 April 2015 at 23:41, Jay Pipes wrote: > On 04/22/2015 04:33 PM, Kyle Mestery wrote: >> >> On Wed, Apr 22, 2015 at 3:28 PM, Sean M. Collins > > wrote: >> >> Hi, >> >> Kyle Mestery has asked me to serve as a cross-project liaison between >> Neutron and No

Re: [openstack-dev] [tempest][nova] TestVolumeBootPattern fail with libvirt-xen, how to fix it?

On 16 April 2015 at 18:11, Anthony PERARD wrote: > Hi all, > > With libvirt_type=xen, the tempest test > tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern > fail. > > This is because it setup a volume with 'vda' as device_name and nova (well > libvirt) fail t

Re: [openstack-dev] [nova] Need more suggestion about nova-scheduler patch/147048

Thanks for your comments on the patch I see what you are trying to do now, I think. However, still a bit concerned about the unit tests, but its probably easier to discuss that in gerrit. Thanks, johnthetubaguy On 24 April 2015 at 04:25, Rui Chen wrote: > Hi all: > > I'm working on the patc

Re: [openstack-dev] [nova][python-novaclient] microversion implementation on client side

I see these changes as really important. We need to establish good patterns other SDKs can copy. On 24 April 2015 at 12:05, Alex Xu wrote: > 2015-04-24 18:15 GMT+08:00 Andrey Kurilin : >> >When user execute cmd without --os-compute-version. The nova client >> > should discover the nova server >s

[openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

Hi, I propose we add Melanie to nova-core. She has been consistently doing great quality code reviews[1], alongside a wide array of other really valuable contributions to the Nova project. Please respond with comments, +1s, or objections within one week. Many thanks, John [1] https://review.op

[openstack-dev] [nova] Deadline for submitting Nova Design Summit Session Proposals

Hi, In case you were unable to make yesterday's Nova meeting... If you have a suggestion for a Nova design summit session, please ensure you add it to before the next Nova meeting (7th May): https://etherpad.openstack.org/p/liberty-nova-summit-ideas Shortly after that Nova meeting, the (mostly)

[openstack-dev] [nova] Blueprints and Specs for Liberty Deadline

Hi, Just a quick reminder that blueprints and nova-specs need to be approved for liberty, even if they have already been approved for a previous release. I added deadline in the subject mostly just to get your attention. We haven't agreed a deadline for spec and blueprint submissions yet, but exp

Re: [openstack-dev] [nova] What happened with the "Hyper-V generation 2 VMs" spec?

On Monday, May 4, 2015, Matt Riedemann wrote: > > > On 5/4/2015 11:12 AM, Alessandro Pilotti wrote: > >> Hi Matt, >> >> We originally proposed a Juno spec for this blueprint, but it got >> postponed to Kilo where it has been approved without a spec together with >> other hypervisor specific bluep

Re: [openstack-dev] [Nova] Abandoning old specs for Nova

On Monday, May 4, 2015, Michael Still wrote: > Hi, > > I just wanted to let people know that I am going through abandoning > old specs for Nova at the moment. The criteria I am using is: > > - spec targets kilo > - no review comments or other activity since January or February > > I think its w

Re: [openstack-dev] [Nova][Ironic] Large number of ironic driver bugs in nova

On 6 May 2015 at 09:39, Lucas Alvares Gomes wrote: > Hi > >> I noticed last night that there are 23 bugs currently filed in nova >> tagged as ironic related. Whilst some of those are scheduler issues, a >> lot of them seem like things in the ironic driver itself. >> >> Does the ironic team have so

Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

On 30 April 2015 at 12:30, John Garbutt wrote: > Hi, > > I propose we add Melanie to nova-core. > > She has been consistently doing great quality code reviews[1], > alongside a wide array of other really valuable contributions to the > Nova project. > > Please res

Re: [openstack-dev] [nova-docker] Status update

On 1 May 2015 at 16:14, Davanum Srinivas wrote: > Anyone still interested in this work? :) > > * there's a stable/kilo branch now (see > http://git.openstack.org/cgit/stackforge/nova-docker/). > * CI jobs are running fine against both nova trunk and nova's > stable/kilo branch. > * there's an upda

Re: [openstack-dev] [Nova][Ironic] Large number of ironic driver bugs in nova

t works for you. I hope that helps. Thanks, John > John > > On Wed, May 6, 2015 at 2:55 AM, John Garbutt wrote: >> >> On 6 May 2015 at 09:39, Lucas Alvares Gomes wrote: >> > Hi >> > >> >> I noticed last night that there are 23 bugs curre

Re: [openstack-dev] [all] Replace mysql-python with mysqlclient

On 30 April 2015 at 18:54, Mike Bayer wrote: > On 4/30/15 11:16 AM, Dan Smith wrote: >>> There is an open discussion to replace mysql-python with PyMySQL, but >>> PyMySQL has worse performance: >>> >>> https://wiki.openstack.org/wiki/PyMySQL_evaluation >> >> My major concern with not moving to som

Re: [openstack-dev] [nova] Is Live-migration not supported in CONF.libvirt.images_type=lvm case?

I would really to start collecting more of this information. Maybe my expanding this: https://github.com/openstack/nova/blob/master/doc/source/support-matrix.ini http://docs.openstack.org/developer/nova/support-matrix.html Although it feels like it will need an extra dimention adding, possibly a

Re: [openstack-dev] [Nova][Neutron] Cross-project coordination

On 8 May 2015 at 00:24, Brent Eagles wrote: > Hi, > > On Thu, May 07, 2015 at 10:03:30PM +, Sean M. Collins wrote: >> On Wed, Apr 22, 2015 at 06:41:58PM EDT, Jay Pipes wrote: >> > Agreed. I'm hoping that someone in the Nova community -- note, this does >> > not need to be a Nova core contribut

Re: [openstack-dev] [nova] Service group foundations and features

On 7 May 2015 at 22:52, Joshua Harlow wrote: > Hi all, > > In seeing the following: > > - https://review.openstack.org/#/c/169836/ > - https://review.openstack.org/#/c/163274/ > - https://review.openstack.org/#/c/138607/ > > Vilobh and I are starting to come to the conclusion that the service grou

Re: [openstack-dev] [all] Replace mysql-python with mysqlclient

On 9 May 2015 at 15:02, Mike Bayer wrote: > On 5/9/15 6:45 AM, John Garbutt wrote: >> >> I am leaning towards us moving to making DB calls with a thread pool and >> some fast C based library, so we get the 'best' performance. Is that a crazy >> thing to be thi

Re: [openstack-dev] [nova-docker] Status update

On 9 May 2015 at 17:55, Adrian Otto wrote: > On the subject of extending the Nova API to accommodate special use cases of > containers that are beyond the scope of the Nova API, I think we should > resist that, and focus those container-specific efforts in Magnum. +1 The API is my biggest worry

[openstack-dev] [nova] Nova Liberty Design Summit Schedule Update

Hi, Thanks for all the summit session submissions. After chewing through that with all the members of nova-drivers, and during recent nova-meetings, we have a mostly final list of sessions. I have uploaded the first draft of the schedule: http://libertydesignsummit.sched.org/type/design+summit/No

Re: [openstack-dev] [nova][all] Architecture Diagrams in ascii art?

On 11 May 2015 at 23:46, Boris Pavlovic wrote: >> Couldn't we just use real image files to do this. IIRC, gerrit supports >> displaying image files which are included in a commit. For example, I've >> been >> planning to copy these images: > > +1 for real images One suggestion I remember around s

Re: [openstack-dev] Birds of a Feather session at Vancouver design summit

On 13 May 2015 at 14:36, Dugger, Donald D wrote: > Rm 221 on Tues. would be perfect, I'd like to reserve that and I'll send out > an email > to announce we want to talk cross-project scheduler interfaces at that time. Its possible some of that will come up in this nova-scheduler session (see lin

Re: [openstack-dev] [nova-scheduler] Cross-project requirements for an independant (gantt) scheduler at Vancouver

On 13 May 2015 at 16:48, Dugger, Donald D 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 > is available on Tues. at 3:40PM. If you’re at all interested in a common > scheduler come on by

Re: [openstack-dev] [nova][heat] sqlalchemy-migrate tool to alembic

On 14 May 2015 at 07:18, Manickam, Kanagaraj wrote: > Hi Nova team, > > This mail is regarding an help required on the migration from > sqlalchemy migration tool to alembic tool. > > Heat is currently using sqlalchemy-migration tool and In liberty release, > we are investigating on how to bring t

Re: [openstack-dev] [nova][all] Architecture Diagrams in ascii art?

On 12 May 2015 at 20:33, Sean Dague wrote: > On 05/12/2015 01:12 PM, Jeremy Stanley wrote: >> On 2015-05-12 10:04:11 -0700 (-0700), Clint Byrum wrote: >>> It's a nice up side. However, as others have pointed out, it's only >>> capable of displaying the most basic pieces of the architecture. >>> >>

Re: [openstack-dev] [nova][keystone] Pike PTG recap - quotas

On 27 February 2017 at 21:18, Matt Riedemann wrote: > We talked about a few things related to quotas at the PTG, some in > cross-project sessions earlier in the week and then some on Wednesday > morning in the Nova room. The full etherpad is here [1]. > > Counting quotas > --- > > Mela

Re: [openstack-dev] [nova][docs] Broken nova instructions

On 9 March 2017 at 11:05, Alexandra Settle wrote: > I have attached the error logs that our tester, Brian Moss, sent to me > earlier this morning. > He has noted that some people have been able to get the instructions to work, > but many others haven't. > Also, noted that some are failing on Ubu

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

On 15 March 2017 at 03:23, Monty Taylor wrote: > On 03/15/2017 12:05 AM, Joshua Harlow wrote: >> So just fyi, this has been talked about before (but prob in context of >> zookeeper or various other pluggable config backends). >> >> Some links: >> >> - https://review.openstack.org/#/c/243114/ >> -

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On 15 March 2017 at 11:58, Jay Pipes wrote: > On 03/15/2017 07:44 AM, Sean Dague wrote: >> >> On 03/14/2017 11:00 PM, Monty Taylor wrote: >> >>> >>> a) awesome. when the rest of this dips momentarily into words that might >>> sound negative, please hear it all wrapped in an "awesome" and know tha

Re: [openstack-dev] [swg][tc] Moving Stewardship Working Group meeting

On 15 March 2017 at 09:50, Thierry Carrez wrote: > Colette Alexander wrote: >> Currently the Stewardship Working Group meetings every other Thursday at >> 1400 UTC. >> >> We've had a couple of pings from folks who are interested in joining us >> for meetings that live in US Pacific Time, and that

Re: [openstack-dev] [nova] [placement] experimenting with extracting placement

On 13 March 2017 at 15:17, Jay Pipes wrote: > On 03/13/2017 11:13 AM, Dan Smith wrote: >> >> Interestingly, we just had a meeting about cells and the scheduler, >> which had quite a bit of overlap on this topic. >> >>> That said, as mentioned in the previous email, the priorities for Pike >>> (and

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

On 13 March 2017 at 21:10, Zane Bitter wrote: > Yes. this is a problem with the default policy - if you have *any* role in a > project then you get write access to everything in that project. I don't > know how I can even call this role-based, since everybody has access to > everything regardless

Re: [openstack-dev] [nova] [notification] BlockDeviceMapping in InstancePayload

On 13 March 2017 at 17:14, Balazs Gibizer wrote: > Hi, > > As part of the Searchlight integration we need to extend our instance > notifications with BDM data [1]. As far as I understand the main goal is to > provide enough data about the instance to Searchlight so that Nova can use > Searchlight

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On 15 March 2017 at 12:33, Sean Dague wrote: > On 03/15/2017 08:10 AM, John Garbutt wrote: >> On 15 March 2017 at 11:58, Jay Pipes wrote: >>> On 03/15/2017 07:44 AM, Sean Dague wrote: >>>> >>>> On 03/14/2017 11:00 PM, Monty Taylor wrote: >>>&g

[openstack-dev] [nova] remove-mox-pike blueprint

Hi, I added some notes on the blueprint: https://blueprints.launchpad.net/nova/+spec/remove-mox-pike I have seen quite a few patches trying to remove the use of "self.stub_out". While possibly interesting in the future, I think this should be out of scope for the mox removal blueprint. The aim of

Re: [openstack-dev] [nova] allow_instance_snapshots config option is not used consistently

On 10 April 2017 at 01:56, Matt Riedemann wrote: > I found a fun little legacy nugget of compute API non-interoperability joy > tonight. > > The "allow_instance_snapshots" config option disables the createImage server > action API. Completely config driven and therefore not discoverable. > > What

Re: [openstack-dev] [tc] [elections] Available time and top priority

On 10 April 2017 at 10:16, Thierry Carrez wrote: > All the candidates are top community members with a lot of > responsibilities on their shoulders already. My experience tells me that > it is easy to overestimate the time we can dedicate to Technical > Committee matters, and how much we can push

Re: [openstack-dev] [ironic][nova] Suggestion required on pci_device inventory addition to ironic and its subsequent changes in nova

On 10 April 2017 at 11:31, wrote: > On Mon, 2017-04-10 at 11:50 +0530, Nisha Agarwal wrote: >> Hi team, >> >> Please could you pour in your suggestions on the mail? >> >> I raised a blueprint in Nova for this https://blueprints.launchpad.ne >> t/nova/+spec/pci-passthorugh-for-ironic and two RFEs

Re: [openstack-dev] [tc][elections]questions about one platform vision

On 12 April 2017 at 03:54, joehuang wrote: > What's the one platform will be in your own words? What's your proposal and > your focus to help one platform vision being achieved? The more I think about this, the less I like the phrase "one platform". I like to think of OpenStack as group of const

Re: [openstack-dev] [tc] [elections] Available time and top priority

On 11 April 2017 at 09:58, Thierry Carrez wrote: > Matt Riedemann wrote: >> Lots of projects have alternating meeting times to accommodate >> contributors in different time zones, especially Europe and Asia. >> >> The weekly TC meeting, however, does not. >> >> I have to assume this has come up be

Re: [openstack-dev] [tc] [elections] Available time and top priority

On 12 April 2017 at 10:07, Thierry Carrez wrote: > Ildiko Vancsa wrote: >>> On 2017. Apr 12., at 3:18, Monty Taylor >> > wrote: >>> [...] >>> Email allows someone to compose an actual structured narrative, and >>> for replies to do the same. Some of us are loquatious a

Re: [openstack-dev] [tc][elections]questions about one platform vision

On 12 April 2017 at 12:04, Davanum Srinivas wrote: > On Wed, Apr 12, 2017 at 6:51 AM, John Garbutt wrote: >> On 12 April 2017 at 03:54, joehuang wrote: >>> What's the one platform will be in your own words? What's your proposal and >>> your focus to he

Re: [openstack-dev] [tc][election] Questions for Candidates

On 12 April 2017 at 17:19, Kendall Nelson wrote: > -What is one trait you have that makes it difficult to work in groups like > the TC and how do you counteract it? My inability to say no to more work (and being too interested in everything). I think I am slowly getting better at focusing, deleg

Re: [openstack-dev] [nova] Owners needed for approved but orphaned OSIC blueprints

Hi, Matt, thanks for pulling that list together. I have context on most of those, if people would like to take those on. I hope to review most of those an clarify where everything is at. I am going to take a look at where we are at with policy stuff first. Thanks, johnthetubaguy On 24 April 20

Re: [openstack-dev] [nova] Compute Node restart

On 27 April 2017 at 06:45, Ajay Kalambur (akalambu) wrote: > I am just issuing a reboot command on the compute node > > Not a reboot –f > > From: Mark Mielke > Date: Wednesday, April 26, 2017 at 8:42 PM > To: "OpenStack Development Mailing List (not for usage questions)" > , Ajay Kalambur > Subj

Re: [openstack-dev] [tc][all] Do we need a #openstack-tc IRC channel

On 16 May 2017 at 16:08, Doug Hellmann wrote: > Excerpts from Sean Dague's message of 2017-05-16 10:49:54 -0400: >> On 05/16/2017 09:38 AM, Davanum Srinivas wrote: >> > Folks, >> > >> > See $TITLE :) >> > >> > Thanks, >> > Dims >> >> I'd rather avoid #openstack-tc and just use #openstack-dev. >> #

Re: [openstack-dev] [tc][swg] Updates on the TC Vision for 2019

On 17 May 2017 at 20:02, Dean Troyer wrote: > On Wed, May 17, 2017 at 1:47 PM, Doug Hellmann wrote: >> The timeline depends on who signed up to do the next revision. Did >> we get someone to do that, yet, or are we still looking for a >> volunteer? (Note that I am not volunteering here, just ask

Re: [openstack-dev] [nova] Boston Forum session recap - claims in the scheduler (or conductor)

gt;> filtering such that hosts are grouped by cell and then they can be sent >>> to the cells for retries as necessary. >>> >> >> That's already proposed for reviews in >> https://review.openstack.org/#/c/465175/ >> >> >>> There was als

[openstack-dev] [forum] [vm&bm] Action required to help improve Ops <-> Dev feedback loops

Hi, On the ops list I have started a thread about the forum session sumary and the actions needed to keep things going. Please do join in over there: http://lists.openstack.org/pipermail/openstack-operators/2017-May/013448.html Many thanks, johnthetubaguy

[openstack-dev] [forum] Writing applications for the VM and Baremetal Platform

A quick summary of what happened in the writing applications for the VM and Baremetal forum session. The etherpad is available here: https://etherpad.openstack.org/p/BOS-forum-using-vm-and-baremetal We had a good number of API users and API developers talking together about the issues facing API u

Re: [openstack-dev] [Openstack-operators] [keystone][nova][cinder][glance][neutron][horizon][policy] defining admin-ness

+1 on not forcing Operators to transition to something new twice, even if we did go for option 3. Do we have an agreed non-distruptive upgrade path mapped out yet? (For any of the options) We spoke about fallback rules you pass but with a warning to give us a smoother transition. I think that's my

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

On Mon, 22 May 2017 at 10:43, Alexandra Settle wrote: > We could also view option 1 as the longer-term goal, > and option 2 as an incremental step toward it +1 doing option 2 then option 1. It just seems a good way to split up the work. Thanks, johnthetubaguy

Re: [openstack-dev] [ironic] ironic and traits

On 16 October 2017 at 17:55, Eric Fried wrote: > * Adding references to the specs: ironic side [1]; nova side [2] (which > just merged). > > * Since Jay is on vacation, I'll tentatively note his vote by proxy [3] > that ironic should be the source of truth - i.e. option (a). I think > the upshot

Re: [openstack-dev] [nova][ironic] Concerns over rigid resource class-only ironic scheduling

On 19 October 2017 at 15:38, Jay Pipes wrote: > On 10/16/2017 05:31 AM, Nisha Agarwal wrote: > >> Hi Matt, >> >> As i understand John's spec https://review.openstack.org/#/c/507052/ < >> https://review.openstack.org/#/c/507052/>, it is actually a replacement >> for capabilities(qualitative only)

[openstack-dev] [ironic] Remove in-tree policy and config?

Hi, While I was looking at the traits work, I noticed we still have policy and config in tree for ironic and ironic inspector: http://git.openstack.org/cgit/openstack/ironic/tree/etc/ironic/policy.json.sample http://git.openstack.org/cgit/openstack/ironic/tree/etc/ironic/ironic.conf.sample http:/

Re: [openstack-dev] [nova] PTL Election Season

On 23 January 2018 at 04:04, Ed Leafe wrote: > On Jan 22, 2018, at 5:09 PM, Matt Riedemann wrote: > > To anyone that cares, I don't plan on running for Nova PTL again for the > Rocky release. Queens was my fourth tour and it's definitely time for > someone else to get the opportunity to lead her

Re: [openstack-dev] [nova][scheduler] A simple solution for better scheduler performance

On 15 July 2016 at 09:26, Cheng, Yingxin wrote: > It is easy to understand that scheduling in nova-scheduler service consists > of 2 major phases: > A. Cache refresh, in code [1]. > B. Filtering and weighing, in code [2]. > > Couple of previous experiments [3] [4] shows that “cache-refresh” is th

Re: [openstack-dev] [Nova] Remove duplicate code using Data Driven Tests (DDT)

On 25 July 2016 at 13:56, Bhor, Dinesh wrote: > > > -Original Message- > From: Sean Dague [mailto:s...@dague.net] > Sent: Monday, July 25, 2016 5:53 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Nova] Remove duplicate code using Data Driven > Tests (DDT) > > O

Re: [openstack-dev] [nova][neutron] neutron port duplication

On 22 July 2016 at 14:54, Andrey Volkov wrote: > Hi, nova and neutron teams, > > While booting new instance nova requests port for that instance in the > neutron. > It's possible to have a situation when neutron doesn't response due timeout > or connection break and nova retries port creation. It

Re: [openstack-dev] [ironic][neutron][nova] Sync port state changes.

On 22 July 2016 at 11:51, Vasyl Saienko wrote: > Kevin, thanks for reply, > > On Fri, Jul 22, 2016 at 11:50 AM, Kevin Benton wrote: >> >> Hi, >> >> Once you solve the issue of getting the baremetal ports to transition to >> the ACTIVE state, a notification will automatically be emitted to Nova of

Re: [openstack-dev] [ironic][neutron][nova] Sync port state changes.

On 26 July 2016 at 10:52, Sam Betts (sambetts) wrote: > On 26/07/2016 09:32, "John Garbutt" wrote: > >>On 22 July 2016 at 11:51, Vasyl Saienko wrote: >>> Kevin, thanks for reply, >>> >>> On Fri, Jul 22, 2016 at 11:50 AM, Kevin Benton wrote: &g

Re: [openstack-dev] [ironic] [nova] [neutron] get_all_bw_counters in the Ironic virt driver

On 29 July 2016 at 19:58, Sean Dague wrote: > On 07/29/2016 02:29 PM, Jay Pipes wrote: >> On 07/28/2016 09:02 PM, Devananda van der Veen wrote: >>> On 07/28/2016 05:40 PM, Brad Morgan wrote: I'd like to solicit some advice about potentially implementing get_all_bw_counters() in the Ironi

Re: [openstack-dev] [Nova] Some thoughts on API microversions

On 4 August 2016 at 16:28, Edward Leafe wrote: > On Aug 4, 2016, at 8:18 AM, Andrew Laski wrote: > >> This gets to the point I'm trying to make. We don't guarantee old >> behavior in all cases at which point users can no longer rely on >> microversions to signal non breaking changes. And where we

Re: [openstack-dev] [Nova] Some thoughts on API microversions

On 4 August 2016 at 14:18, Andrew Laski wrote: > On Thu, Aug 4, 2016, at 08:20 AM, Sean Dague wrote: >> On 08/03/2016 08:54 PM, Andrew Laski wrote: >> > I've brought some of these thoughts up a few times in conversations >> > where the Nova team is trying to decide if a particular change warrants

Re: [openstack-dev] [nova] Review runways this cycle

Hi So I am really excited for us to try runways out, ASAP. On 20 March 2018 at 23:44, melanie witt wrote: > We were thinking of starting the runways process after the spec review > freeze (which is April 19) so that reviewers won't be split between spec > reviews and reviews of work in runways.

Re: [openstack-dev] [nova] Nominating Stephen Finucane for nova-core

+1 from me. He will be a great add. I really enjoyed working with him as part of OSIC early on in his Nova journey, and I trust him to a great job as part of the core team. John On Sun, 4 Dec 2016 at 00:00, Michael Still wrote: > +1, I'd value him on the team. > > Michael > > On Sat, Dec 3, 20

Re: [openstack-dev] [swg][tc] An attempt to clarify/discuss: what exactly is the Stewardship Working Group, anyhow?

On 8 December 2016 at 15:33, Thierry Carrez wrote: > Colette Alexander wrote: >> [...] >> What are the sorts of things you'd like to see tackled? > > John Garbutt recently proposed that the TC works on defining visions for > itself[1] and OpenStack in general[2] an

Re: [openstack-dev] [nova] Latest and greatest on trying to get n-sch to require placement

On 26 January 2017 at 13:50, Sylvain Bauza wrote: > Le 26/01/2017 05:42, Matt Riedemann a écrit : >> This is my public hand off to Sylvain for the work done tonight. >> > > Thanks Matt for your help yesterday, was awesome to count you in even > you're personally away. > > >> Starting with the mult

Re: [openstack-dev] [nova] Latest and greatest on trying to get n-sch to require placement

On 26 January 2017 at 14:14, Ed Leafe wrote: > On Jan 26, 2017, at 7:50 AM, Sylvain Bauza wrote: >> >> That's where I think we have another problem, which is bigger than the >> corner case you mentioned above : when upgrading from Newton to Ocata, >> we said that all Newton computes have be upgra

Re: [openstack-dev] [nova] Final mascot

On 3 February 2017 at 02:59, Matt Riedemann wrote: > The Foundation wants to have the mascots finalized before the PTG. This is > just an opportunity for people to raise issues with it if they have any. Honestly it looks a bit aggressive / sharp / pointy. Maybe less spikes on the outside? I duno.

[openstack-dev] [ironic] [nova] [tripleo] Deprecation of Nova's integration with Ironic Capabilities and ComputeCapabilitiesFilter

if anyone has needs that the ResourceClass and Traits scheme does not currently address, or can think of a problem with a transition to the newer approach. Many thanks, John Garbutt IRC: johnthetubaguy __ OpenStack Development

Re: [openstack-dev] [Openstack-operators] [all] Consistent policy names

tl;dr +1 consistent names I would make the names mirror the API ... because the Operator setting them knows the API, not the code Ignore the crazy names in Nova, I certainly hate them Lance Bragstad wrote: > I'm curious if anyone has context on the "os-" part of the format? My memory of the Nov

Re: [openstack-dev] [ironic] [nova] [tripleo] Deprecation of Nova's integration with Ironic Capabilities and ComputeCapabilitiesFilter

On Thu, 20 Sep 2018 at 16:02, Matt Riedemann wrote: > On 9/20/2018 4:16 AM, John Garbutt wrote: > > Following on from the PTG discussions, I wanted to bring everyone's > > attention to Nova's plans to deprecate ComputeCapabilitiesFilter, > > including most of

Re: [openstack-dev] [Openstack-operators] [ironic] [nova] [tripleo] Deprecation of Nova's integration with Ironic Capabilities and ComputeCapabilitiesFilter

On Fri, 28 Sep 2018 at 00:46, Jay Pipes wrote: > On 09/27/2018 06:23 PM, Matt Riedemann wrote: > > On 9/27/2018 3:02 PM, Jay Pipes wrote: > >> A great example of this would be the proposed "deploy template" from > >> [2]. This is nothing more than abusing the placement traits API in > >> order to

Re: [openstack-dev] [Openstack-operators] [ironic] [nova] [tripleo] Deprecation of Nova's integration with Ironic Capabilities and ComputeCapabilitiesFilter

Back to the deprecation for a moment... My plan was to tell folks to use Traits to influence placement decisions, rather than capabilities. We probably can't remove the feature till we have deploy templates, but it seems wrong not to warn our users to avoid using capabilities, when 80% of the use

Re: [openstack-dev] [nova][limits] Does ANYONE at all use the quota class functionality in Nova?

Hi, Basically we should kill quota classes. It required out of tree stuff that was never implemented, AFAIK. When I checked with Kevin about this, my memory says the idea was out of tree authorization plugin would populate context.quota_class with something like "i_have_big_credit_limit" or "i_h

[openstack-dev] [all] Cross Project Summit Sessions Planning

Hi, In Barcelona, between Tuesday 3:55pm (Oct 25) and Wednesday 2:55pm (Oct 26) we have some dedicated time to discuss and resolve some of the issues that span across our OpenStack Community. As before, we will be doing proposals for this via etherpad. Please propose items into here: https://ethe

Re: [openstack-dev] [nova] [telemetry] PostgreSQL gate broken

On 24 November 2016 at 13:52, Chris Friesen wrote: > On 11/24/2016 05:57 AM, Julien Danjou wrote: >> >> Hi, >> >> It seems Nova broke its PostgreSQL support recently, and that impacts >> Telemetry as we do gate on PostgreSQL. I opened a bug: >> >>https://bugs.launchpad.net/nova/+bug/1644513 >>

<    1   2   3   4   5