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

On Thu, 25 Oct 2018 14:12:51 +0900, ボーアディネシュ[bhor Dinesh] wrote: We were having a similar use case like *Preemptible Instances* called as *Rich-VM’s* which are high in resources and are deployed each per hypervisor. We have a custom code in production which tracks the quota for such

Re: [openstack-dev] [nova] nova cellsv2 and DBs / down cells / quotas

On Thu, 25 Oct 2018 10:55:15 +1100, Sam Morrison wrote: On 24 Oct 2018, at 4:01 pm, melanie witt wrote: On Wed, 24 Oct 2018 10:54:31 +1100, Sam Morrison wrote: Hi nova devs, Have been having a good look into cellsv2 and how we migrate to them (we’re still on cellsv1 and about to upgrade

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

On Wed, 24 Oct 2018 12:54:00 -0700, Melanie Witt wrote: On Wed, 24 Oct 2018 13:57:05 -0500, Matt Riedemann wrote: On 10/24/2018 10:10 AM, Jay Pipes wrote: I'd like to propose deprecating this API and getting rid of this functionality since it conflicts with the new Keystone /limits endpoint,

[openstack-dev] [Monasca] Where Monasca stores collected Data?

Hello Monasca team, I'm experiencing several problems with monasca. I have Monasca running with OpenStack. I added alarms to my system but I cannot see where monasca stores the collected data. With Grafana I cannot see any datapoints from the influxdb datasource. In the influxdb I have all the

Re: [openstack-dev] [Octavia] [Kolla] SSL errors polling amphorae and missing tenant network interface

Might as well throw it out here. After a lot of troubleshooting we were able to narrow our issue down to our test environment running qemu virtualization, we moved our compute node to hardware and used kvm full virtualization instead. We could properly reproduce the issue where generating a

Re: [openstack-dev] [barbican][tc] Seeking feedback on the OpenStack cloud vision

Hello Zane-- Yes, this vision is consistent with the Barbican team's vision. Barbican provides an abstraction layer over HSMs and other secret storage services. We have a plugin architecture to enable this abstraction over a variety of backends. Vault is a recent addition to our supported

Re: [openstack-dev] [nova] nova cellsv2 and DBs / down cells / quotas

> I guess our architecture is pretty unique in a way but I wonder if > other people are also a little scared about the whole all DB servers > need to up to serve API requests? When we started down this path, we acknowledged that this would create a different access pattern which would require ops

Re: [openstack-dev] [TripleO] easily identifying how services are configured

On 10/19/18 8:04 PM, Alex Schultz wrote: On Fri, Oct 19, 2018 at 10:53 AM James Slagle wrote: On Wed, Oct 17, 2018 at 11:14 AM Alex Schultz wrote: > Additionally I took a stab at combining the puppet/docker service > definitions for the aodh services in a similar structure to start >

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

On 10/25/2018 01:38 PM, Chris Friesen wrote: On 10/24/2018 9:10 AM, Jay Pipes wrote: Nova's API has the ability to create "quota classes", which are basically limits for a set of resource types. There is something called the "default quota class" which corresponds to the limits in the

Re: [openstack-dev] [TripleO] easily identifying how services are configured

On Thu, Oct 25, 2018 at 9:16 AM Bogdan Dobrelya wrote: > > > On 10/19/18 8:04 PM, Alex Schultz wrote: > > On Fri, Oct 19, 2018 at 10:53 AM James Slagle > > wrote: > >> > >> On Wed, Oct 17, 2018 at 11:14 AM Alex Schultz > >> wrote: > >> > Additionally I took a stab at combining the

Re: [openstack-dev] [Monasca] Where Monasca stores collected Data?

Hi Amal, please check if you collect and persist the measurements correctly. Check agent forwarder logs. Check the logs of API, with DEBUG log level you should see all the messages sent to Kafka. Check persister logs. You should see information about consuming messages from `metrics` topic.

Re: [openstack-dev] [ClusterLabs Developers] [HA] future of OpenStack OCF resource agents (was: resource-agents v4.2.0)

Hi Tim, Tim Bell wrote: Adam, Personally, I would prefer the approach where the OpenStack resource agents are part of the repository in which they are used. Thanks for chipping in. Just checking - by this you mean the resource-agents rather than openstack-resource-agents, right?

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

melanie witt wrote on 10/25/2018 02:14:40 AM: > On Thu, 25 Oct 2018 14:12:51 +0900, ボーアディネシュ[bhor Dinesh] wrote: > > We were having a similar use case like *Preemptible Instances* called as > > *Rich-VM’s* which > > > > are high in resources and are deployed each per hypervisor. We have a > >

Re: [openstack-dev] Proposal for a process to keep up with Python releases

Zane Bitter wrote on 10/22/2018 03:12:46 PM: > On 22/10/18 10:33 AM, Thomas Goirand wrote: > > On 10/19/18 5:17 PM, Zane Bitter wrote: > >> Integration Tests > >> - > >> > >> Integration tests do test, amongst other things, integration with > >> non-openstack-supplied things

Re: [openstack-dev] [nova] nova cellsv2 and DBs / down cells / quotas

On 10/24/2018 6:55 PM, Sam Morrison wrote: I’ve been thinking of some hybrid cellsv1/v2 thing where we’d still have the top level api cell DB but the API would only ever read from it. Nova-api would only write to the compute cell DBs. Then keep the nova-cells processes just doing

[openstack-dev] [tripleo][openstack-ansible][nova][placement] Owners needed for placement extraction upgrade deployment tooling

Hello OSA/TripleO people, A plan/checklist was put in place at the Stein PTG for extracting placement from nova [1]. The first item in that list is done in grenade [2], which is the devstack-based upgrade project in the integrated gate. That should serve as a template for the necessary

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

On 10/24/2018 9:10 AM, Jay Pipes wrote: Nova's API has the ability to create "quota classes", which are basically limits for a set of resource types. There is something called the "default quota class" which corresponds to the limits in the CONF.quota section. Quota classes are basically

Re: [openstack-dev] Proposal for a process to keep up with Python releases

On 25/10/18 1:38 PM, William M Edmonds wrote: Zane Bitter wrote on 10/22/2018 03:12:46 PM: > On 22/10/18 10:33 AM, Thomas Goirand wrote: > > On 10/19/18 5:17 PM, Zane Bitter wrote: > >> Integration Tests > >> - > >> > >> Integration tests do test, amongst other things,

Re: [openstack-dev] [TripleO] easily identifying how services are configured

On Thu, Oct 25, 2018 at 11:26 AM Alex Schultz wrote: > > On Thu, Oct 25, 2018 at 9:16 AM Bogdan Dobrelya wrote: > > > > > > On 10/19/18 8:04 PM, Alex Schultz wrote: > > > On Fri, Oct 19, 2018 at 10:53 AM James Slagle > > > wrote: > > >> > > >> On Wed, Oct 17, 2018 at 11:14 AM Alex Schultz >

Re: [openstack-dev] [TripleO] easily identifying how services are configured

On Wed, Oct 17, 2018 at 11:15 AM Alex Schultz wrote: > > Time to resurrect this thread. > > On Thu, Jul 5, 2018 at 12:14 PM James Slagle wrote: > > > > On Thu, Jul 5, 2018 at 1:50 PM, Dan Prince wrote: > > > Last week I was tinkering with my docker configuration a bit and was a > > > bit

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

On 10/25/2018 12:00 PM, Jay Pipes wrote: On 10/25/2018 01:38 PM, Chris Friesen wrote: On 10/24/2018 9:10 AM, Jay Pipes wrote: Nova's API has the ability to create "quota classes", which are basically limits for a set of resource types. There is something called the "default quota class" which

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

On 10/25/2018 2:55 PM, Chris Friesen wrote: 2) The main benefit (as I see it) of the quota class API is to allow dynamic adjustment of the default quotas without restarting services. I could be making this up, but I want to say back at the Pike PTG people were also complaining that not having

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

On Thu, 25 Oct 2018 15:06:38 -0500, Matt Riedemann wrote: On 10/25/2018 2:55 PM, Chris Friesen wrote: 2) The main benefit (as I see it) of the quota class API is to allow dynamic adjustment of the default quotas without restarting services. I could be making this up, but I want to say back at

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

On Thu, 25 Oct 2018 14:00:08 -0400, Jay Pipes wrote: On 10/25/2018 01:38 PM, Chris Friesen wrote: On 10/24/2018 9:10 AM, Jay Pipes wrote: Nova's API has the ability to create "quota classes", which are basically limits for a set of resource types. There is something called the "default quota

Re: [openstack-dev] [nova] nova cellsv2 and DBs / down cells / quotas

Hi Matt, The Searchlight team decided to revive the required feature in Stein [1] and We're working with Kevin to review the patch this weekend. If Nova team needs some help, just let me know. [1] https://review.openstack.org/#/c/453352/ Bests, On Fri, Oct 26, 2018 at 12:58 AM Matt Riedemann

[openstack-dev] [Kolla] Implement upgrade/rolling-upgrade for services in Kolla-Ansible

Hi all, I'm working on the bp about implementing upgrade/rolling-upgrade for services in Kolla [1]. And there're three patch-sets remaining about developing the rolling upgrade logic: Apply Swift rolling upgrade at https://review.openstack.org/#/c/582103/ Apply Neutron rolling upgrade logic

[openstack-dev] [Searchlight] Weekly report - Stein R-25

Hi team, It's a little late but finally, I can find some time to write the report for last week [1]. Just a reminder that at the end of this week we will release Stein-1 for all of the Searchlight projects. It's not required but I would like to do it to evaluate our team's effort. Happy

Re: [openstack-dev] [Octavia] [Kolla] SSL errors polling amphorae and missing tenant network interface

FYI, I took some time out this afternoon and wrote a detailed certificate configuration guide. Hopefully this will help. https://review.openstack.org/613454 Reviews would be welcome! Michael On Thu, Oct 25, 2018 at 7:00 AM Tobias Urdin wrote: > > Might as well throw it out here. > > After a

[openstack-dev] [Searchlight] Team meeting today reminder

Hi team, It's a kindly reminder that we will have the team meeting at 12:00 UTC today on #openstack-meeting-4 channel. Hope to see you there :) -- *Trinh Nguyen* *www.edlab.xyz * __ OpenStack

Re: [openstack-dev] [nova][NFS] Inexplicable utime permission denied when launching instance

I'm still seeing the same problem after disabling AppArmor, so I think it must be some other root problem. On Wed, Oct 24, 2018 at 2:41 PM Neil Jerram wrote: > > Thanks so much for these hints, Erlon. I will look closer at AppArmor. > > Neil > > On Wed, Oct 24, 2018 at 1:41 PM Erlon Cruz

[openstack-dev] [publiccloud-wg] Reminder weekly meeting Public Cloud WG

Hi everyone, Time for a new meeting for PCWG - today 1400 UTC in #openstack-publiccloud! Agenda found at https://etherpad.openstack.org/p/publiccloud-wg Cheers, Tobias -- Tobias Rydberg Senior Developer Twitter & IRC: tobberydberg www.citynetwork.eu | www.citycloud.com INNOVATION THROUGH

Re: [openstack-dev] [cinder] [nova] Problem of Volume(in-use) Live Migration with ceph backend

Great, Jon. Thanks for your reply. I am looking forward to your report. Cheers, Boxiang On 10/23/2018 22:01，Jon Bernard wrote： * melanie witt wrote: On Mon, 22 Oct 2018 11:45:55 +0800 (GMT+08:00), Boxiang Zhu wrote: I created a new vm and a new volume with type 'ceph'[So that the volume will

Re: [openstack-dev] [TripleO][OVN] Switching the default network backend to ML2/OVN

Daniel, thank you very much for the extensive and detailed email. The plan looks good to me and it makes sense, also the OVS option will still be tested, and available when selected. On Wed, Oct 24, 2018 at 4:41 PM Daniel Alvarez Sanchez wrote: > Hi Stackers! > > The purpose of this email is