Re: [openstack-dev] Hierarchical quotas at the PTG?

I would like to talk about it too. On 02/10/2017 11:56 PM, Matt Riedemann wrote: > Operators want hierarchical quotas [1]. Nova doesn't have them yet and > we've been hesitant to invest scarce developer resources in them since > we've heard that the implementation for hierarchical quotas in

Re: [openstack-dev] [tc][glance][glare][all] glance/glare/artifacts/images at the PTG

Although there has not been much discussion on this point on the mailing list, I feel we do need to find the right level of granularity for ‘mainstream’ projects: For CERN, we look for the following before offering a project to our end users: - Distro packaging (in our case RPMs through RDO) -

Re: [openstack-dev] Hierarchical quotas at the PTG?

On 12 Feb 2017, at 12:13, Boris Bobrov > wrote: I would like to talk about it too. On 02/10/2017 11:56 PM, Matt Riedemann wrote: Operators want hierarchical quotas [1]. Nova doesn't have them yet and we've been hesitant to invest scarce

[openstack-dev] Reminder to use recheck rather then rebase to trigger a gate re-run: was Re: [kolla] unblocking the gate

Hey folks, I’d like to remind kolla contributors of this email exchange from Feb 29th, 2016 with the infra team. I originally requested kolla contributors to rebase all of their patches to unblock the gate. This was an incorrect request. The infrastructure team quickly corrected my

Re: [openstack-dev] [kolla] Support for non-x86_64 architectures

Marcin, I think this work is fantastic! The Ocata feature deadline has passed. Reference: https://releases.openstack.org/ocata/schedule.html The feature freeze deadline was January 25th 2017. What this means is that this work will need to go into Pike instead of Ocata. One of the reasons

[openstack-dev] [tripleo] deploying Nova Placement API in IPv6

I have been investigating this bug over the week-end: https://bugs.launchpad.net/tripleo/+bug/1663187 The ovb-updates CI job has been red since we've unpinned Nova in TripleO CI. Reminder: this job deploys TripleO with IPv6 activated on public endpoints. I've been able to reproduce the issue

Re: [openstack-dev] [tripleo] TripleO Ocata release blockers

Quick updates: - All FFEs patches have been merged except: https://review.openstack.org/#/c/330050/ - so we're green on this side. - Upgrade team is still working on automation to upgrade from newton to ocata. - ovb-updates (CI job with IPv6) doesn't pass -

Re: [openstack-dev] [tc][glance][glare][all] glance/glare/artifacts/images at the PTG

Excerpts from Brian Rosmaita's message of 2017-02-10 12:39:11 -0500: > I want to give all interested parties a heads up that I have scheduled a > session in the Macon room from 9:30-10:30 a.m. on Thursday morning > (February 23). > > Here's what we need to discuss. This is from my perspective as

Re: [openstack-dev] [nova] placement/resource providers update 11

2017-02-11 0:10 GMT+08:00 Ed Leafe : > Your regular reporter, Chris Dent, is on PTO today, so I'm filling in. > I'll be brief. > > After the flurry of activity to get as much in before the Ocata RCs, this > past week was relatively calm. Work continued on the patch to have Ironic

Re: [openstack-dev] [monasca] Ideas to work on

Hi Roland   I am not sure whether you received my last email because I got a delivery failure notification. I am sending this again to ensure that you can see this email.   Best, Anqi   - Original message -From: An Qi YL Lu/China/IBMTo: roland.hochm...@hpe.comCc:

Re: [openstack-dev] [Neutron] Alternative approaches for L3 HA

Hi, we are using L3 HA in our production environment now. Router instances communicate to each other by VRRP protocol. In my opinion, although VRRP is a control plane thing, but the real VRRP traffic is using data plane nic so that router namespaces can not talk to each other sometimes when the

[openstack-dev] [monasca] Failed to upgrade monasca source code in devstack

Hi all I failed to do the unstack and stack operations with devstack when I want to pull the latest Monasca code and upgrade related projects. I took following steps: go to /opt/stackgo to the monasca project folder that I want to upgraderun git pullrun unstack.sh

[openstack-dev] [rally][release] How rally release version

Hey guys, I found rally already releases its 0.8.1 tag from[0][1]. But I found nothing in openstack/releases project[2]. How rally create tag? [0] http://tarballs.openstack.org/rally/ [1] https://github.com/openstack/rally/releases [2]