Re: [openstack-dev] [nova] Hard fail if you try to rename an AZ with instances in it?

On 03/27/2018 12:42 PM, Matt Riedemann wrote: On 3/27/2018 10:37 AM, Jay Pipes wrote: If we want to actually fix the issue once and for all, we need to make availability zones a real thing that has a permanent identifier (UUID) and store that permanent identifier in the instance

Re: [Openstack-operators] [openstack-dev] [nova] Hard fail if you try to rename an AZ with instances in it?

On 03/27/2018 10:40 AM, Matt Riedemann wrote: Sylvain has had a spec up for awhile [1] about solving an old issue where admins can rename an AZ (via host aggregate metadata changes) while it has instances in it, which likely results in at least user confusion, but probably other issues later

Re: [openstack-dev] [nova] Hard fail if you try to rename an AZ with instances in it?

On 03/27/2018 10:40 AM, Matt Riedemann wrote: Sylvain has had a spec up for awhile [1] about solving an old issue where admins can rename an AZ (via host aggregate metadata changes) while it has instances in it, which likely results in at least user confusion, but probably other issues later

Re: [openstack-dev] [nova] Proposing Eric Fried for nova-core

+1 On 03/26/2018 10:00 PM, melanie witt wrote: Howdy everyone, I'd like to propose that we add Eric Fried to the nova-core team. Eric has been instrumental to the placement effort with his work on nested resource providers and has been actively contributing to many other areas of openstack

Re: [openstack-dev] [oslo] proposing Ken Giusti for oslo-core

Big +1. On 03/26/2018 11:52 AM, Doug Hellmann wrote: Ken has been managing oslo.messaging for ages now but his participation in the team has gone far beyond that single library. He regularly attends meetings, including the PTG, and has provided input into several of our team decisions recently.

Re: [openstack-dev] [oslo.db] upcoming warnings in MySQL 5.6, 5.7 for BLOB columns

Neither nova nor placement use any BLOB columns. Best, -jay On 03/14/2018 11:53 AM, Michael Bayer wrote: hey all - Just looking to see if we think this will impact openstack. MySQL 5.6 and 5.7, but not yet MariaDB, now emits an erroneous warning when you try to send a binary value to the

[openstack-dev] [nova][placement] PTG Summary and Rocky Priorities

We had a productive PTG and were able to discuss a great many scheduler-related topics. I've put together an etherpad [0] with a summary, reproduced below. Expect follow-up emails about each priority item in the scheduler track from those contributors working on that area. Best, -jay

Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple functions

penstack.org>> *Subject:* Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple functions __ __ On 2 March 2018 at 14:31, Jay Pipes <jaypi...@gmail.com <mailto:jaypi...@gmail.com>> wrote: On 03/02/2018 02:00 PM, Nadath

Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple functions

On 03/02/2018 02:00 PM, Nadathur, Sundar wrote: Hello Nova team,     During the Cyborg discussion at Rocky PTG, we proposed a flow for FPGAs wherein the request spec asks for a device type as a resource class, and optionally a function (such as encryption) in the extra specs. This does not

Re: [openstack-dev] [nova] [placement] resource providers update 18-07

On 02/24/2018 02:17 AM, Matt Riedemann wrote: On 2/16/2018 7:54 AM, Chris Dent wrote: Before I get to the meat of this week's report, I'd like to request some feedback from readers on how to improve the report. Over its lifetime it has grown and it has now reached the point that while it tries

Re: [openstack-dev] [nova] Adding Takashi Natsume to python-novaclient core

Hi Takashi, As you know, nova-core and python-novaclient-core memberships are evaluated separately (they are different teams with some overlap in membership). While your contributions to Nova are absolutely appreciated and recognized, there is a different group that votes on nova-core membership

Re: [openstack-dev] [nova][cyborg]Dublin PTG Cyborg Nova Interaction Discussion

On 02/12/2018 10:27 AM, Eric Fried wrote: I'm interested. No date/time preference so far as long as it sticks to Monday/Tuesday. Same for me. -jay __ OpenStack Development Mailing List (not for usage questions)

Re: [Openstack-operators] AggregateMultiTenancyIsolation with multiple (many) projects

On 02/06/2018 04:26 AM, Flint WALRUS wrote: Aren’t CellsV2 more adapted to what you’re trying to do? No, cellsv2 are not user-facing nor is there a way to segregate certain tenants on to certain cells. Host aggregates are the appropriate way to structure this grouping. Best, -jay Le mar.

Re: [openstack-dev] [all][Kingbird]Multi-Region Orchestrator

anting... just food for thought. Best, -jay Thanks Goutham. On Wed, Jan 31, 2018 at 9:25 PM, Jay Pipes <jaypi...@gmail.com <mailto:jaypi...@gmail.com>> wrote: On 01/31/2018 01:49 AM, Goutham Pratapa wrote: *Kingbird (The Multi Region orchestrator):* We

Re: [Openstack-operators] [openstack-dev] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

On 01/29/2018 06:30 PM, Mathieu Gagné wrote: So lets explore what would looks like a placement centric solution. (let me know if I get anything wrong) Here are our main concerns/challenges so far, which I will compare to our current flow: 1. Compute nodes should not be enabled by default When

Re: [Openstack-operators] [openstack-dev] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

On 01/29/2018 06:48 PM, Mathieu Gagné wrote: On Mon, Jan 29, 2018 at 8:47 AM, Jay Pipes <jaypi...@gmail.com> wrote: What I believe we can do is change the behaviour so that if a 0.0 value is found in the nova.conf file on the nova-compute worker, then instead of defaulting t

Re: [openstack-dev] [all][Kingbird]Multi-Region Orchestrator

On 01/31/2018 01:49 AM, Goutham Pratapa wrote: *Kingbird (The Multi Region orchestrator):* We are proud to announce kingbird is not only a centralized quota and resource-manager but also a  Multi-region Orchestrator. *Use-cases covered: *- Admin can synchronize and periodically balance

Re: [Openstack-operators] [openstack-dev] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

On 01/29/2018 12:40 PM, Chris Friesen wrote: On 01/29/2018 07:47 AM, Jay Pipes wrote: What I believe we can do is change the behaviour so that if a 0.0 value is found in the nova.conf file on the nova-compute worker, then instead of defaulting to 16.0, the resource tracker would first look

Re: [Openstack-operators] [openstack-dev] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

Greetings again, Mathieu, response inline... On 01/18/2018 07:24 PM, Mathieu Gagné wrote: So far, a couple challenges/issues: We used to have fine grain control over the calls a user could make to the Nova API: * os_compute_api:os-aggregates:add_host * os_compute_api:os-aggregates:remove_host

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

On 01/22/2018 06:09 PM, Matt Riedemann wrote: On 1/15/2018 11:04 AM, Kendall Nelson wrote: Election details: https://governance.openstack.org/election/ Please read the stipulations and timelines for candidates and electorate contained in this governance documentation. Be aware, in the PTL

Re: [Openstack-operators] [neutron] [os-vif] VF overcommitting and performance in SR-IOV

On 01/22/2018 11:36 AM, Maciej Kucia wrote: Hi! Is there any noticeable performance penalty when using multiple virtual functions? For simplicity I am enabling all available virtual functions in my NICs. I presume by the above you are referring to setting your pci_passthrough_whitelist on

Re: [openstack-dev] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

On 01/19/2018 10:21 AM, Chris Friesen wrote: On 01/18/2018 02:54 PM, Mathieu Gagné wrote: We use this feature to segregate capacity/hosts based on CPU allocation ratio using aggregates. This is because we have different offers/flavors based on those allocation ratios. This is part of our

Re: [openstack-dev] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

On 01/18/2018 03:54 PM, Mathieu Gagné wrote: Hi, On Tue, Jan 16, 2018 at 4:24 PM, melanie witt wrote: Hello Stackers, This is a heads up to any of you using the AggregateCoreFilter, AggregateRamFilter, and/or AggregateDiskFilter in the filter scheduler. These filters have

Re: [Openstack-operators] [openstack-dev] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

/compute/schedulers.html On Wed, Jan 17, 2018 at 7:57 AM, Sylvain Bauza <sba...@redhat.com> wrote: On Wed, Jan 17, 2018 at 2:22 PM, Jay Pipes <jaypi...@gmail.com> wrote: On 01/16/2018 08:19 PM, Zhenyu Zheng wrote: Thanks for the info, so it seems we are not going to impleme

Re: [openstack-dev] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

/compute/schedulers.html On Wed, Jan 17, 2018 at 7:57 AM, Sylvain Bauza <sba...@redhat.com> wrote: On Wed, Jan 17, 2018 at 2:22 PM, Jay Pipes <jaypi...@gmail.com> wrote: On 01/16/2018 08:19 PM, Zhenyu Zheng wrote: Thanks for the info, so it seems we are not going to impleme

Re: [Openstack] Meaning of each field of 'hypervisor stats show' command.

On 01/17/2018 12:46 PM, Jorge Luiz Correa wrote: Hi, I would like some help to understand what does means each field in output of the command 'openstack hypervisor stats show': it's an amalgamation of legacy information that IMHO should be deprecated from the Compute API. FWIW, the

Re: [Openstack-operators] [openstack-dev] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

On 01/16/2018 08:19 PM, Zhenyu Zheng wrote: Thanks for the info, so it seems we are not going to implement aggregate overcommit ratio in placement at least in the near future? As @edleafe alluded to, we will not be adding functionality to the placement service to associate an overcommit ratio

Re: [openstack-dev] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

On 01/16/2018 08:19 PM, Zhenyu Zheng wrote: Thanks for the info, so it seems we are not going to implement aggregate overcommit ratio in placement at least in the near future? As @edleafe alluded to, we will not be adding functionality to the placement service to associate an overcommit ratio

Re: [Openstack] Production deployment mirantis vs tripleO

On 01/15/2018 12:58 PM, Satish Patel wrote: But Fuel is active project, isn't it? https://docs.openstack.org/fuel-docs/latest/ No, it is no longer developed or supported. -jay ___ Mailing list:

Re: [openstack-dev] [kuryr][os-vif][nova] os-vif 1.8.0 breaks kuryr-kubernetes

On 01/15/2018 11:45 AM, mdu...@redhat.com wrote: Hi, os-vif commit [1] introduced a non-backward compatible change to the Subnet object - removal of ips field. Turns out kuryr-kubernetes were depending on that e.g. here [1] and we're now broken with os-vif 1.8.0. kuryr-kubernetes is saving the

Re: [openstack-dev] [ResMgmt SIG]Proposal to form Resource Management SIG

with Jay Pipes and Chris Dent and received positive feedback. The SIG will have a co-lead structure so that people could spearheading in the area they are most interested in. For example for me as Cyborg dev, I will mostly lead in the area of acceleration[2]. If you are also interested please reply

Re: [openstack-dev] [oslo] proposing Stephen Finucan for oslo-core

big +1 from me. On 01/08/2018 09:55 AM, Doug Hellmann wrote: Stephen (sfinucan) has been working on pbr, oslo.config, and oslo.policy and reviewing several of the other Oslo libraries for a while now. His reviews are always helpful and I think he would make a good addition to the oslo-core

Re: [openstack-dev] [nova][neutron] Filtering Instances by IP address performance improvement test result

Excellent work on this, Kevin. I'll review the patch series on Monday. Best, -jay On 01/04/2018 09:53 PM, Zhenyu Zheng wrote: Hi All, We are working on patches to improve the performance filtering instance by IP address this cycle. As discussed in the previous ML[1], it contains both

Re: [openstack-dev] [nova] Working toward Queens feature freeze and RC1

On 01/04/2018 01:38 PM, Eric Fried wrote: Matt, et al- * Nested resource providers: I'm going to need someone closer to this work like Jay or Eric to provide an update on where things are at in the series of changes and what absolutely needs to get done. I have personally found it hard to

Re: [Openstack] [openstack] [ironic] Does Ironic support that different nova-compute map to different ironic endpoint?

ironic, a nova, a neutron in a OpenStack environment Does everything go well? Sure, that should work just fine. Best, -jay Thanks -Original Message- From: Jay Pipes [mailto:jaypi...@gmail.com] Sent: Tuesday, January 02, 2018 8:59 PM To: openstack@lists.openstack.org Subject: Re

Re: [Openstack] [openstack] [ironic] Does Ironic support that different nova-compute map to different ironic endpoint?

On 01/02/2018 06:09 AM, Guo James wrote: Hi guys I know that Ironic has support multi-nova-compute. But I am not sure whether OpenStack support the situation than every nova-compute has a unshare ironic And these ironic share a nova and a neutron I'm not quite following you... what do you

Re: [openstack-dev] [nova] Boot from volume 's instance of rescue operation

On 12/27/2017 05:34 AM, 李杰 wrote: Hi,all As we all known,Now the boot from volume 's instance of rescue operation is invalid. To solve it,I have two plans. 1.I plan to use the rescue_image as the root disk,and then make the original root volume as the second disk to

Re: [openstack-dev] Regarding inter-VM inter process communication in OpenStack

On 12/24/2017 12:56 AM, Darshan Tank wrote: Hi, I have been working on inter-virtual machine inter process communication (IPC) methods. I would like to know whether current OpenStack framework supports inter-VM shared memory concept or not ? No. OpenStack (or at least, the components you

Re: [openstack-dev] [all] Switching to longer development cycles

On 12/21/2017 07:27 PM, Matt Riedemann wrote: On 12/21/2017 4:37 PM, Joshua Harlow wrote: My 3 cents are that this isn't something that u get asked to put in from operators, it's something that is built in from the start. Just look at other workflow systems (which is really what

Re: [openstack-dev] Race in FixedIP.associate_pool

On 12/12/2017 03:22 PM, Arun SAG wrote: This kind of how the logs look like 2017-12-08 22:33:37,124 DEBUG [yahoo.contrib.ocata_openstack_yahoo_plugins.nova.network.manager]

Re: [openstack-dev] [etsinfv][gap-04][blazar]: Clarification on the scope of the capacity query

On 12/11/2017 12:41 PM, Csatari, Gergely (Nokia - HU/Budapest) wrote: Hi Jay, Okay. Thanks for the clarification. Makes sense. Random-thinking: Maybe the best would be to have a privilege level what covers the needs of MANO/NFVO, but still not full admin privileges. Do you think is this

Re: [openstack-dev] [etsinfv][gap-04][blazar]: Clarification on the scope of the capacity query

On 12/11/2017 07:24 AM, Csatari, Gergely (Nokia - HU/Budapest) wrote: Hi Masahito, Thanks for the answer. Some clarification questions. You mention that the NFVO works as both an user and an admin for the cloud. Is this becouse the resource usage per user info is more for cloud operators

Re: [Openstack] Flavor metadata quota doesn't work

On 12/01/2017 08:57 AM, si...@turka.nl wrote: Hi, I have created a flavor with the following metadata: quota:disk_write_bytes_sec='10240' This should limit writing to disk to 10240 bytes (10KB/s). I also tried it with a higher number (100MB/s). Using the flavor I have launched an instance and

Re: [openstack-dev] [oaktree] Follow up to Multi-cloud Management in OpenStack Summit session

On 11/29/2017 11:26 AM, Monty Taylor wrote: For instance - an OpenStack Availability Zone and an AWS AZ are **not** the same thing. This deserves repeating every week on the OpenStack mailing list. -jay __ OpenStack

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

On 11/27/2017 01:54 PM, Joshua Harlow wrote: I want a place that is like http://blog.kubernetes.io/ You know that's not for developers (only) of k8s, right? That's for users, marketers, product managers, etc. So, when you say *for developers*, what exactly do you mean? Are you referring to

Re: [openstack-dev] [oslo][oslo.config] pluggable drivers for oslo.config spec ready for review

On 11/20/2017 10:19 AM, Doug Hellmann wrote: The spec for adding pluggable drivers to oslo.config is ready for a final queens review [1]. The latest draft should be simpler to implement (important given where we are in the schedule) at the expense of always requiring at least one configuration

Re: [Openstack] Traits for filter

.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:validate_provider_summaries You will need to wait for the Queens release for the complete traits-based scheduling functionality to be operational. Best, -jay -----Original Message- From: Jay Pipes [mailto:jaypi...@gmail

Re: [Openstack] Traits for filter

On 11/16/2017 12:06 AM, Ramu, MohanX wrote: Hi All, I have a use case that I need to apply some filter (Custom traits) while Placement API fetch the resource providers for launching instance. So that I can have list of resource provided which meets my condition/filter/validation. The

Re: [openstack-dev] [glance] Does glance_store swift driver support range requests ?

On 11/15/2017 06:28 AM, Duncan Thomas wrote: On 15 November 2017 at 11:15, Matt Keenan wrote: On 13/11/17 22:51, Nikhil Komawar wrote: I think it will a rather hard problem to solve. As swift store can be configured to store objects in different configurations. I guess

Re: [openstack-dev] [ironic] Scheduling error with RamFilter ... on integrating ironic into our OpenStack Distribution

On 10/30/2017 01:37 PM, Waines, Greg wrote: Thanks Jay ... i’ll try this out and let you know. BTW ... i should have mentioned that i am currently @Newton ... and will eventually move to @PIKE Does that change anything you suggested below ?

Re: [openstack-dev] [ironic] Scheduling error with RamFilter ... on integrating ironic into our OpenStack Distribution

You need to set the node's resource_class attribute to the custom resource class you will use for that chassis/hardware type. Then you need to add a specific extra_specs key/value to a flavor to indicate that that flavor is requesting that specific hardware type: openstack flavor set

Re: [openstack-dev] [ironic] [nova] traits discussion call

for placement purity. Please invite me to the hangout or whatever. Thanks, Eric On 10/23/2017 07:22 AM, Mooney, Sean K wrote: > >

Re: [openstack-dev] [ironic] [Openstack-operators] replace node "tags" with node "traits"

On 10/25/2017 12:55 PM, Mathieu Gagné wrote: Hi, On Wed, Oct 25, 2017 at 10:17 AM, Loo, Ruby wrote: Hello ironic'ers, A while ago, we approved a spec to add node tag support to ironic [1]. The feature itself did not land yet (although some of the code has). Now that the

Re: [openstack-dev] [os-vif] [nova] Changes to os-vif cores

+1 On 10/24/2017 10:32 AM, Stephen Finucane wrote: Hey, I'm not actually sure what the protocol is for adding/removing cores to a library project without a PTL, so I'm just going to put this out there: I'd like to propose the following changes to the os-vif core team. - Add 'nova-core'

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

e want to provide the same user experience. > > On Sun, Oct 22, 2017 at 2:25 PM, Jay Pipes <jaypi...@gmail.com> wrote: > >> Sorry for delay, took a week off before starting a new job. Comments >> inline. >> >> On 10/16/2017 12:24 PM, Dmitry Tantsur wrote: >>

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

Sorry for delay, took a week off before starting a new job. Comments inline. On 10/16/2017 12:24 PM, Dmitry Tantsur wrote: Hi all, I promised John to dump my thoughts on traits to the ML, so here we go :) I see two roles of traits (or kinds of traits) for bare metal: 1. traits that say what

Re: [openstack-dev] [nova] Interesting bug when unshelving an instance in an AZ and the AZ is gone

On 10/16/2017 11:22 AM, Matt Riedemann wrote: This is interesting from the user point of view: https://bugs.launchpad.net/nova/+bug/1723880 - The user creates an instance in a non-default AZ. - They shelve offload the instance. - The admin deletes the AZ that the instance was using, for

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

On 10/16/2017 05:31 AM, Nisha Agarwal wrote: Hi Matt, As i understand John's spec https://review.openstack.org/#/c/507052/ , it is actually a replacement for capabilities(qualitative only) for ironic. It doesnt cover the quantitative capabilities as

Re: [openstack-dev] [pbr] Migration to Storyboard

Sounds like a plan to me. On 10/11/2017 10:05 AM, Stephen Finucane wrote: The Python packaging ecosystem is shifting under our feet and we have a couple of things in pbr we need to look at over the next few months (Pipfiles, pyenv, changes in setuptools setup.cfg, ...). We should probably track

Re: [openstack-dev] [tc][election] TC non-candidacy

On 10/10/2017 07:40 PM, Monty Taylor wrote: Hey everybody! I have decided not to seek reelection for the TC. I have had the honor and privilege of serving you on the TC and it's predecessor the PPB since the fall of 2011 (with one six month absence that I blame on Jay Pipes

Re: [Openstack] Traits is not working

On 10/06/2017 10:18 AM, Ramu, MohanX wrote: Hi Jay, I am able to create custom traits without any issue. Want to associate some value to that traits. Like I mentioned in the previous email, that's not how traits work :) A trait *is* the value that is associated with a resource provider.

Re: [Openstack] Traits is not working

" ] } BTW, a great place to see examples of both good and bad API usage is to check out the Gabbit functional API tests for the placement API. Here is the set of tests for the traits functionality: https://github.com/openstack/nova/blob/master/nova/tests/functional/api/openstack/

Re: [Openstack] Traits is not working

Rock on :) On 10/04/2017 09:33 AM, Ramu, MohanX wrote: Thank you so much Jay. After adding this header, working fine. -Original Message- From: Jay Pipes [mailto:jaypi...@gmail.com] Sent: Tuesday, October 3, 2017 11:36 PM To: openstack@lists.openstack.org Subject: Re: [Openstack] Traits

Re: [Openstack] Traits is not working

Against the Pike placement API endpoint, make sure you send the following HTTP header: OpenStack-API-Version: placement 1.10 Best, -jay On 10/03/2017 02:01 PM, Ramu, MohanX wrote: Please refer attached original one. -Original Message- From: Jay Pipes [mailto:jaypi...@gmail.com

Re: [Openstack] Traits is not working

, -jay Thanks & Regards, Mohan Ramu -Original Message- From: Jay Pipes [mailto:jaypi...@gmail.com] Sent: Tuesday, October 3, 2017 9:26 PM To: openstack@lists.openstack.org Subject: Re: [Openstack] Traits is not working On 10/03/2017 11:34 AM, Ramu, MohanX wrote: Hi, We have impleme

Re: [Openstack] Traits is not working

On 10/03/2017 11:34 AM, Ramu, MohanX wrote: Hi, We have implemented OpenStack Ocata and Pike releases, able to consume Placement resource providers API, not able to consume resource class APIs’. I tried to run Triats API in Pike set up too. I am not able to run any Traits API. As per the

Re: [Openstack-operators] [openstack-operators] [nova] Nova-scheduler filter, for domain level isolation

On 09/20/2017 06:17 AM, Georgios Kaklamanos wrote: Hello, Usecase: We have to deploy instances that belong in different domains, to different compute hosts. Does anyone else have the same usecase? If so, how did you implement it? [The rest of the mail is a more detailed explanation on the

Re: [openstack-dev] [tc] [election] NON nomination for TC

On 10/02/2017 01:44 PM, Jeremy Stanley wrote: On 2017-10-02 12:03:44 -0400 (-0400), Sean Dague wrote: I'd like to announce that after 4 years serving on the OpenStack Technical Committee, I will not be running in this fall's election. [...] You've served as a stellar role model, and provided

Re: [openstack-dev] [all][oslo] Retiring openstack/pylockfile

ack, +1 from me. On 09/29/2017 11:07 PM, ChangBo Guo wrote: pylockfile was deprecated about two years ago in [1] and it is not used in any OpenStack Projects now [2] , we would like to retire it according to steps of retiring a project[3].

Re: [openstack-dev] [Glance][Security] Secure Hash Algorithm Spec

On 09/29/2017 06:19 AM, Luke Hinds wrote: On Thu, Sep 28, 2017 at 8:38 PM, McClymont Jr, Scott > wrote: Hey All, I've got a spec up for a change I want to implement in Glance for Queens to enhance

Re: [openstack-dev] vGPUs support for Nova - Implementation

Hi Sahid, comments inline. :) On 09/29/2017 04:53 AM, Sahid Orentino Ferdjaoui wrote: On Thu, Sep 28, 2017 at 05:06:16PM -0400, Jay Pipes wrote: On 09/28/2017 11:37 AM, Sahid Orentino Ferdjaoui wrote: Please consider the support of MDEV for the /pci framework which provides support for vGPUs

Re: [openstack-dev] [nova] Queens spec review sprint next week

Either one works for me. On 09/28/2017 07:45 PM, Matt Riedemann wrote: Let's do a Queens spec review sprint. What day works for people that review specs? Monday came up in the team meeting today, but Tuesday could be good too since Monday's are generally evil.

Re: [openstack-dev] vGPUs support for Nova - Implementation

On 09/28/2017 11:37 AM, Sahid Orentino Ferdjaoui wrote: Please consider the support of MDEV for the /pci framework which provides support for vGPUs [0]. Accordingly to the discussion [1] With this first implementation which could be used as a skeleton for implementing PCI Devices in Resource

Re: [openstack-dev] [nova] how does UEFI booting of VM manage per-instance copies of OVMF_VARS.fd ?

On 09/27/2017 09:09 AM, Waines, Greg wrote: Hey there ... a question about UEFI booting of VMs. i.e. glance image-create --file cloud-2730. qcow --disk-format qcow2 --container-format bare --property “hw-firmware-type=uefi” --name clear-linux-image in order to specify that you want to use

Re: [openstack-dev] [all][infra] Zuul v3 migration update

On 09/27/2017 03:49 AM, Flavio Percoco wrote: Just wanted to say thanks to all of you for the hard work. I can only imagine how hard it must be to do this migration without causing downtimes. +1000 Thank you so much for the hard work the infra team has put into making this migration as

Re: [openstack-dev] [ptg] Simplification in OpenStack

On 09/26/2017 02:04 AM, Blair Bethwaite wrote: I've been watching this thread and I think we've already seen an excellent and uncontroversial suggestion towards simplifying initial deployment of OS - that was to push towards encoding Constellations into the deployment and/or config management

Re: [Openstack] extend attached volumes

On 09/26/2017 10:20 AM, Volodymyr Litovka wrote: Hi Jay, I know about this way :-) but Pike introduced ability to resize attached volumes: "It is now possible to signal and perform an online volume size change as of the 2.51 microversion using the|volume-extended|external event. Nova will

Re: [Openstack] extend attached volumes

Detach the volume, then resize it, then re-attach. Best, -jay On 09/26/2017 09:22 AM, Volodymyr Litovka wrote: Colleagues, can't find ways to resize attached volume. I'm on Pike. As far as I understand, it required to be supported in Nova, because Cinder need to check with Nova whether it's

Re: [openstack-dev] vGPUs support for Nova

On 09/25/2017 05:39 AM, Sahid Orentino Ferdjaoui wrote: There is a desire to expose the vGPUs resources on top of Resource Provider which is probably the path we should be going in the long term. I was not there for the last PTG and you probably already made a decision about moving in that

Re: [openstack-dev] [ptg] Simplification in OpenStack

Do you have any specific suggestions on things our community can do to encourage adoption? I hear lots of complaints but not many specific suggestions. -jay On Sep 23, 2017 3:07 AM, "Adam Lawson" wrote: > Quick note (started quick anyway) since I haven't been as active on

Re: [openstack-dev] [all][api] POST /api-sig/news

On 09/21/2017 11:37 PM, Joe Topjian wrote: Microversions also reared their head in the form of a long discussion about how SDK developers and users are consuming microversions at a very granular level. This discussion opened many surprised eyes as we learned how different SDK

Re: [openstack-dev] [nova] [placement] Modeling SR-IOV with nested resource providers

On 09/13/2017 03:01 PM, Chris Dent wrote: On Wed, 13 Sep 2017, Jay Pipes wrote: We still need a way to represent a request to placement to find allocation candidates for like resources, though. As you pointed out, I've thought about using multiple requests to placement from the conductor

Re: [openstack-dev] [ptg] Simplification in OpenStack

infrastructure platform that meets everyone's needs. And you imply that using a single deployment/packaging solution (Docker) will magically solve all issues with upgrades. Please answer the questions in my original response with some specific details. Thanks -jay Best regards, Boris Pavlovic

Re: [openstack-dev] [nova] [placement] Modeling SR-IOV with nested resource providers

On 09/05/2017 11:02 AM, Andrey Volkov wrote: For example, I have SR-IOV PF with four ports (P_i), two of them are connected to one switch (SW_1) and other two to another (SW_2). I would like to get VFs from distinct ports connected to distinct switches (more details can be found in spec [1]),

Re: [openstack-dev] [ptg] Simplification in OpenStack

On 09/12/2017 06:53 PM, Boris Pavlovic wrote: Mike, Great intiative, unfortunately I wasn't able to attend it, however I have some thoughts... You can't simplify OpenStack just by fixing few issues that are described in the etherpad mostly.. TC should work on shrinking the OpenStack use

Re: [openstack-dev] [ptg][nova][neutron] modelling network capabilities and capacity in placement and nova neutron port binding negociation.

I'm interested in this. I get in to Denver this evening so if we can do this session tomorrow or later, that would be super. Best, -jay On 09/11/2017 01:11 PM, Mooney, Sean K wrote: Hi everyone, I’m interested in set up a white boarding session at the ptg to discuss How to model network

Re: [Openstack] [OpenStack] Can Mitaka RamFilter support free hugepages?

you think Jay? On Wed, Sep 6, 2017 at 9:22 PM, Jay Pipes <jaypi...@gmail.com <mailto:jaypi...@gmail.com>> wrote: On 09/06/2017 01:21 AM, Weichih Lu wrote: Thanks for your response. Is this mean if I want to create an instance with flavor: 16G

Re: [openstack-dev] [nova] remove uml code from nova tree

Yes, please. On 09/06/2017 01:35 PM, Sean Dague wrote: As some of the libvirt refactorings have hit recently, especially around privsep, one bit of cruft is UML (user mode linux) support. For people that do not yet have gray hairs, this was the earliest form of upstream "virtualization" that

Re: [Openstack] [OpenStack] Can Mitaka RamFilter support free hugepages?

than 50 if you want to launch a 16GB instance on a host with 64GB of RAM. Try reserving 32 1GB huge pages. Best, -jay 2017-09-06 1:47 GMT+08:00 Jay Pipes <jaypi...@gmail.com <mailto:jaypi...@gmail.com>>: Please remember to add a topic [nova] marker to your subject line.

Re: [Openstack] [OpenStack] Can Mitaka RamFilter support free hugepages?

Please remember to add a topic [nova] marker to your subject line. Answer below. On 09/05/2017 04:45 AM, Weichih Lu wrote: Dear all, I have a compute node with 64GB ram. And I set 50 hugepages wiht 1GB hugepage size. I used command "free", it shows free memory is about 12GB. And free

Re: [openstack-dev] [Panko] Ways to go through events in the order they appear in database

On 09/05/2017 08:44 AM, gordon chung wrote: On 04/09/17 11:17 AM, Mikhail Kebich wrote: Hello Gordon, Any feedback? Did you get a chance to take a look at the cursor api prototype? Thanks, Mike On Wed, Aug 30, 2017 at 6:00 PM, Mikhail Kebich wrote: On Wed, Aug 30,

Re: [openstack-dev] [nova][scheduling] Can VM placement consider the VM network traffic need?

On 09/01/2017 04:42 AM, Rua, Philippe (Nokia - FI/Espoo) wrote: Will it be possible to include network bandwidth as a resource in Nova scheduling, for VM placement decision? Yes. See here for a related Neutron spec that mentions Placement:

Re: [openstack-dev] [nova] Proposing Balazs Gibizer for nova-core

+1 On 08/22/2017 09:18 PM, Matt Riedemann wrote: I'm proposing that we add gibi to the nova core team. He's been around for awhile now and has shown persistence and leadership in the multi-release versioned notifications effort, which also included helping new contributors to Nova get

Re: [openstack-dev] [openstack][oslo][all] Clean up oslo deprecated stuff !

On 08/22/2017 08:44 AM, ChangBo Guo wrote: 2017-08-22 20:37 GMT+08:00 Doug Hellmann >: Excerpts from ChangBo Guo's message of 2017-08-22 15:24:44 +0800: > Hi ALL, > > We discussed a little about how to avoid breaking

Re: [openstack-dev] [nova] [placement] [api] cache headers in placement service

On 08/21/2017 04:59 AM, Chris Dent wrote: On Sun, 20 Aug 2017, Jay Pipes wrote: On 08/18/2017 01:23 PM, Chris Dent wrote: So my change above adds 'last-modified' and 'cache-control: no-cache' to GET of /resource_providers and /resource_providers/{uuid} and proposes we do it for everything else

Re: [Openstack] Ocata The placement API endpoint not found on Ubuntu

On 08/18/2017 08:50 AM, Divneet Singh wrote: Hello, I have trying to install ocata on Ubuntu 16.04 , for the time being i have 2 nodes . just can't figure this out. I have setup Placement API. But get error after restart nova service or reboot " 017-08-18 08:27:41.496 1422 WARNING

Re: [openstack-dev] [nova] [placement] [api] cache headers in placement service

Hi Chris, thanks for taking this on. Comments inline. On 08/18/2017 01:23 PM, Chris Dent wrote: (I put [api] in the subject tags because this might be of interest to a wider audience that cares about APIs.) Long ago and far away I made this bug:

Re: [Openstack-operators] [LCOO] August 17 General Coordination meeting

(and SIGs approach). Anyway if anyone is interested to investigate further, please reply or reach out to me: jamemcc at gmail dot com. On 08/16/2017 09:25 PM, Curtis wrote: /On Wed, Aug 16, 2017 at 12:03 AM, Jay Pipes <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators>&g

Re: [Openstack-operators] [nfv-telecom] Suspending meetings while we consider moving to being a sub group in LCOO

On 08/16/2017 09:25 PM, Curtis wrote: On Wed, Aug 16, 2017 at 12:03 AM, Jay Pipes <jaypi...@gmail.com> wrote: Hi Curtis, Andrew U, Jamie M, May I request that if the telco working group merges with the LCOO, that we get regular updates to the openstack[-operator|-dev] mailin

Re: [Openstack-operators] [nfv-telecom] Suspending meetings while we consider moving to being a sub group in LCOO

Hi Curtis, Andrew U, Jamie M, May I request that if the telco working group merges with the LCOO, that we get regular updates to the openstack[-operator|-dev] mailing list with information about the goings-on of LCOO? Would be good to get a bi-weekly or even monthly summary. Other working

<    1   2   3   4   5   6   7   8   9   10   >