Re: [openstack-dev] [infra][diskimage-builder] containers, Containers, CONTAINERS!

Hello Paul, thank you very much for your contribution - it is very appreciated. You addressed a topic with your patch set that was IMHO not in a wide focus: generating images for containers. The ideas in the patches are good and should be implemented. Nevertheless I'm missing the concept behind

[openstack-dev] [tripleo] CI status - January 6th

I found useful to share a status on what's going on in CI now. 1) We fixed ovb-updates job: https://review.openstack.org/#/c/416706/ It should be stable again now. Please don't ignore it anymore (it was for a few days until last night). 2) multinode & ovb-nonha are green and pretty stable. 3) ov

Re: [openstack-dev] [tripleo] CI status - January 6th

On Fri, Jan 6, 2017 at 6:57 AM, Emilien Macchi wrote: > I found useful to share a status on what's going on in CI now. > > 1) We fixed ovb-updates job: https://review.openstack.org/#/c/416706/ > It should be stable again now. Please don't ignore it anymore (it was > for a few days until last night

Re: [openstack-dev] [ironic] User survey question

On 01/04/2017 07:43 PM, Mario Villaplana wrote: Hi, Here are some questions I've thought of: TESTING / INTERESTED - What is your use case for ironic? - What, if anything, is preventing you from using ironic in a production environment? - What alternatives to ironic have you considered? USING

[openstack-dev] [nova] placement/resource providers update 7

Welcome to the first placement/resource providers update for 2017. There's a lot in progress, including plenty of work from new contributors. Is great to see that. # What Matters Most The main priority remains the same: Getting the scheduler using a filtered list of resource providers. That wor

Re: [openstack-dev] [oslo][monasca] Can we uncap python-kafka ?

Any progress ? On Thu, Dec 08, 2016 at 08:32:54AM +1100, Tony Breeds wrote: On Mon, Dec 05, 2016 at 04:03:13AM +, Keen, Joe wrote: I wasn’t able to set a test up on Friday and with all the other work I have for the next few days I doubt I’ll be able to get to it much before Wednesday. It'

Re: [openstack-dev] [kolla] Multi-Regions Support

Hello, Thanks for your feedback. > The original value is this: > auth_uri = {{ internal_protocol }}://{{ kolla_internal_fqdn }}:{{ > keystone_public_port }} > > Kolla does SSL via haproxy, not directly at the service itself. So internal > traffic is http, external is https. In this case, 'kolla

[openstack-dev] [snaps] alternative distribution approach for OpenStack

Hi All I’ve been working with a few folk over the last few months to see if snaps (see [0]) might be a good alternative approach to packaging and distribution of OpenStack. As OpenStack projects are Python based, producing snaps has been relatively trivial with the snapcraft python plugin, which

Re: [openstack-dev] [acceleration]Team Bi-weekly Meeting 2017.1.4 Agenda

One question regarding PTG, Since we don't get a specific room allocated, and the intent is for people to not float around meetings... What day(s) are you expecting to have Cyborg specific discussion? It seem hotel booking will be a premium soon On Wed, Jan 4, 2017 at 11:13 AM, Zhipeng Huang wrot

[openstack-dev] [tripleo][ui] FYI, the tripleo-ui package is currently broken

Hi folks, Just a heads-up that the DLRN "current"/dev package for the Tripleo UI is broken in Ocata and will cause the UI to only show a blank page, until we resolve some dependencies issues within the -deps package. If I understand correctly, we ended up with an incomplete package because we wer

Re: [openstack-dev] [nova] Let's kill quota classes (again)

On 12/16/2016 4:00 PM, Jay Pipes wrote: So, we could do that, we already have the quota_classes table and the os-quota-class-sets REST API, and as mentioned the only usable thing that goes in there is overriding global default quota. Would you suggest we drop the global quota limit configuratio

Re: [openstack-dev] [infra][diskimage-builder] containers, Containers, CONTAINERS!

On Fri, Jan 06, 2017 at 09:48:31AM +0100, Andre Florath wrote: > Hello Paul, > > thank you very much for your contribution - it is very appreciated. > > You addressed a topic with your patch set that was IMHO not in a wide > focus: generating images for containers. The ideas in the patches are >

[openstack-dev] [heat][tripleo] Heat memory usage in the TripleO gate during Ocata

tl;dr everything looks great, and memory usage has dropped by about 64% since the initial Newton release of Heat. I re-ran my analysis of Heat memory usage in the tripleo-heat-templates gate. (This is based on the gate-tripleo-ci-centos-7-ovb-nonha job.) Here's a pretty picture: https://fedo

Re: [openstack-dev] [nova] Let's kill quota classes (again)

On 12/16/2016 05:03 PM, Jay Pipes wrote: > On 12/16/2016 04:36 PM, Matt Riedemann wrote: > > On 12/16/2016 2:20 PM, Jay Pipes wrote: > >> > >> For problems with placing data like this as configuration options, see > >> the hassle we went through in making the allocation_ratio options into > >> fie

Re: [openstack-dev] [Neutron] Using neutron lib plugin constants

On Tue, Dec 27, 2016 at 12:03 AM, Gary Kotton wrote: > The following decomposed plugins are not gating: > > - openstack/networking-brocade > > (please see https://review.openstack.org/415028) > > -

[openstack-dev] [release] subscribe to the OpenStack release calendar

The release team has made it possible to subscribe to an ICS version of the Ocata release schedule. This means you can have the full schedule of countdown weeks and various cross-project deadlines visible in your normal calendaring application, and receive updates automatically. The link for the O

[openstack-dev] [kolla] helm-repository container

Hello team, While researching for an operator, piece of code which runs as a container and launches microservice in correct order to bring up a specific service, I came across a need to have helm charts/packages be stored and served from a centralized location. Since I could not find a ready-to

Re: [openstack-dev] [release] subscribe to the OpenStack release calendar

On Fri, Jan 06 2017, Doug Hellmann wrote: Hi Doug, > The link for the Ocata schedule is > https://releases.openstack.org/ocata/schedule.ics > > We will have a similar Pike calendar available as soon as the > schedule is finalized. Thank you, this is great. One question: could it be possible to h

Re: [openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator

Hi YinLiYin, This is an interesting question. Let me divide my answer to two parts. First, the case that you described with Nagios and Vitrage. This problem depends on the specific Nagios tests that you configure in your system, as well as on the Vitrage templates that you use. For example, you

Re: [openstack-dev] [Vitrage] About introduce suspect state of a alarm

Hi YinLiYin, I’m not sure I understood the use case. Are you using a monitor that raises alarms A, B, C, D, and E? or does the monitor raise only alarms A and C, and the other alarms are deduced alarms created by Vitrage? In Vitrage templates you can determine causal relationship between differ

[openstack-dev] [ironic] PTG planning

Hey folks, The PTG is about 6 weeks from now, so I figure we should start planning. As far as how we plan this, I'm trying to treat it similar to the summit. The only difference being we get a room for three days straight instead of 40 minute blocks, so we can be flexible with our time. Anyway, h

[openstack-dev] [ironic] Stepping down as PTL after this cycle

Hi friends, I'll be stepping down as PTL after Ocata is done. I'll still be 100% dedicated to the project, but I'd like to be able to focus more on writing code and reinforcing the bridges between us and other projects (Nova, Neutron, etc). I'd love to see two or more people step up and run next

[openstack-dev] [api-wg] restarting service-types-authority / service catalog work

It's a new year, and in anticipation of having a productive time in Atlanta around the service catalog, I refreshed the set of patches from last year around starting to stub out a service-types-authority - https://review.openstack.org/#/c/286089/ The proposes in 4 base types that are pretty non co

Re: [openstack-dev] [nova] Let's kill quota classes (again)

On Fri, 6 Jan 2017 12:15:34 -0500, William M Edmonds wrote: Why would someone need to change the defaults via REST API calls? I agree that we should plan for that now if we think that will eventually be needed, but I'm not seeing why it would be needed. The REST API already allows people to cha

Re: [openstack-dev] [kolla] Multi-Regions Support

On 01/05/2017 09:12 AM, Ronan-Alexandre Cherrueau wrote: Hello, TL;DR: We make a multi-regions deployment with Kolla. It requires to patch the code a little bit, and you can find the diff on our GitHub[1]. This patch is just a first attempt to support multi-regions in Kolla and it raises questio

Re: [openstack-dev] [release] subscribe to the OpenStack release calendar

> On Jan 6, 2017, at 1:14 PM, Julien Danjou wrote: > > On Fri, Jan 06 2017, Doug Hellmann wrote: > > Hi Doug, > >> The link for the Ocata schedule is >> https://releases.openstack.org/ocata/schedule.ics >> >> We will have a similar Pike calendar available as soon as the >> schedule is finaliz

Re: [openstack-dev] [kolla] Multi-Regions Support

On Fri, Jan 6, 2017 at 8:01 PM, Jay Pipes wrote: > On 01/05/2017 09:12 AM, Ronan-Alexandre Cherrueau wrote: > >> Hello, >> >> TL;DR: We make a multi-regions deployment with Kolla. It requires to >> patch the code a little bit, and you can find the diff on our >> GitHub[1]. This patch is just a fi

Re: [openstack-dev] [kolla] Multi-Regions Support

On 01/06/2017 03:23 PM, Sam Yaple wrote: This should be read as MariaDB+Galera for replication. It is a highly-available database. Don't get me wrong. I love me some Galera. :) However, what the poster is really working towards is an implementation of the VCPE and eVCPE use cases for ETSI NFV

Re: [openstack-dev] [kolla] Multi-Regions Support

I was kind of hoping k2k federation would solve that. one keystone per region to provide a local keystone to talk to, and a centeral keystone users authenticate with. Just waiting for horizon to gain support before trying though. Thanks, Kevin From: Jay P

Re: [openstack-dev] [heat][tripleo] Heat memory usage in the TripleO gate during Ocata

On Fri, Jan 6, 2017 at 6:12 PM, Zane Bitter wrote: > tl;dr everything looks great, and memory usage has dropped by about 64% > since the initial Newton release of Heat. > > I re-ran my analysis of Heat memory usage in the tripleo-heat-templates > gate. (This is based on the gate-tripleo-ci-centos-

Re: [openstack-dev] [heat][tripleo] Heat memory usage in the TripleO gate during Ocata

Why would TripleO not move to convergence at the earliest possible point? On Jan 6, 2017 10:37 PM, "Thomas Herve" wrote: > On Fri, Jan 6, 2017 at 6:12 PM, Zane Bitter wrote: > > tl;dr everything looks great, and memory usage has dropped by about 64% > > since the initial Newton release of Heat.

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

On 12/16/2016 6:40 AM, Chris Dent wrote: ## Resource Provider Traits There's been some recent activity on the spec for resource provider traits. These are a way of specifying qualitative resource requirements (e.g., "I want my disk to be SSD"). https://review.openstack.org/#/c/345138/ I'm

Re: [openstack-dev] [heat][tripleo] Heat memory usage in the TripleO gate during Ocata

On Fri, Jan 6, 2017 at 4:35 PM, Thomas Herve wrote: > On Fri, Jan 6, 2017 at 6:12 PM, Zane Bitter wrote: >> tl;dr everything looks great, and memory usage has dropped by about 64% >> since the initial Newton release of Heat. >> >> I re-ran my analysis of Heat memory usage in the tripleo-heat-temp

[openstack-dev] OpenStack Developer Mailing List Digest December 31 - January 6

HTML version: http://www.openstack.org/blog/2017/01/openstack-developer-mailing-list-digest-20170106/ SuccessBot Says === * Dims - Keystone now has Devstack based functional test with everything running under python3.5. * Tell us yours via OpenStack IRC channels with message

Re: [openstack-dev] [heat][tripleo] Heat memory usage in the TripleO gate during Ocata

On 06/01/17 16:58, Emilien Macchi wrote: On Fri, Jan 6, 2017 at 4:35 PM, Thomas Herve wrote: On Fri, Jan 6, 2017 at 6:12 PM, Zane Bitter wrote: It's worth reiterating that TripleO still disables convergence in the undercloud, so these are all tests of the legacy code path. It would be great i

Re: [openstack-dev] [heat][tripleo] Heat memory usage in the TripleO gate during Ocata

On 06/01/17 16:40, Hugh Brock wrote: Why would TripleO not move to convergence at the earliest possible point? We'll need some data to decide when the earliest possible point is :) Last time Steve (Hardy) tested it I believe convergence was looking far worse than legacy in memory usage, at a

[openstack-dev] [glance] priorities for the coming week (01/06-01/12)

Hopefully everyone's had some rest over the holidays, and are ready to code & review for O-3. Please concentrate on the following: (0) If you're a member of the Glance coresec team, you should be getting a separate notification about an issue that could use your attention. Please make some time t

Re: [openstack-dev] [heat][tripleo] Heat memory usage in the TripleO gate during Ocata

On 06/01/17 16:35, Thomas Herve wrote: Thanks a lot for the analysis. It's great that things haven't gotten off track. I tracked down most of the step changes to identifiable patches: 2016-10-07: 2.44GiB -> 1.64GiB - https://review.openstack.org/382068/ merged, making ResourceInfo classes mor

Re: [openstack-dev] [kolla] Multi-Regions Support

- Mail original - > De: "Jay Pipes" > À: openstack-dev@lists.openstack.org > Envoyé: Vendredi 6 Janvier 2017 21:42:46 > Objet: Re: [openstack-dev] [kolla] Multi-Regions Support > > On 01/06/2017 03:23 PM, Sam Yaple wrote: > > This should be read as MariaDB+Galera for replication. It is

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

2017-01-07 5:55 GMT+08:00 Matt Riedemann : > On 12/16/2016 6:40 AM, Chris Dent wrote: > >> >> ## Resource Provider Traits >> >> There's been some recent activity on the spec for resource provider >> traits. These are a way of specifying qualitative resource >> requirements (e.g., "I want my disk t

Re: [openstack-dev] [acceleration]Team Bi-weekly Meeting 2017.1.4 Agenda

I think we just need half a day. I will try to figure out the room. On Jan 6, 2017 10:38 PM, "Harm Sluiman" wrote: > One question regarding PTG, > Since we don't get a specific room allocated, and the intent is for people > to not float around meetings... > What day(s) are you expecting to have

Re: [openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator

The two questions raised by YinLiYin is actually one, i.e. *how to enrich the alarm properties *that can be used as an condition in root cause deducing. Both 'suspect' or 'datasource' are additional information that may be referred as a condition in general fault model, a.k.a. scenario in vitrage.