[openstack-dev] [designate][chef] cookbook-openstack-dnsaas

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hey everyone! Per our goals for the M cycle, I've started cookbook-openstack-dnsaas[1]. It's under my namespace for the time being; but shouldn't be much longer. I walked through the developer install guide[2] and automated the build. I'm posting

Re: [openstack-dev] [Fuel][CI] recheck/reverify support for Fuel CI jobs

Why not "recheck fuel" to align with how other OpenStack 3rd party CI hooks work? See: recheck xen-server or recheck hyper-v Best, -jay On 11/20/2015 05:24 AM, Igor Belikov wrote: Alexey, First of all, “refuel” sounds very cool. Thanks for raising this topic, I would like to hear more

Re: [openstack-dev] [Fuel] Running Fuel node as non-superuser

Dmitry, as we work on opensource - it would be really nice to propose patches to upstream for non-Fuel services. But if it is not an option - using puppet make sense to me. On Fri, Nov 20, 2015 at 11:01 PM, Dmitry Nikishov wrote: > Stanislaw, > > I want to clarify: there

Re: [openstack-dev] [Neutron] Call for review focus

On Wed, Nov 18, 2015 at 8:14 PM, Armando M. wrote: > Hi Neutrites, > > Neutrinos? > We are nearly two weeks away from the end of Mitaka 1. > > I am writing this email to invite you to be mindful to what you review, > especially in the next couple of weeks. Whenever you have

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

On Fri, 20 Nov 2015, gord chung wrote: i think a lot of the complexity we have in versioning is that the projects are too silo'd. i think some of the versioning issues would be irrelevant if the producer knew it's consumers before sending rather than producers just tossing out a chunk of data

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

Thinking about this some more makes me wonder if we need a sample config generator like oslo.config. It would work off something similar to the capabilities map, where you would say SSL: templates: -puppet/extraconfig/tls/tls-cert-inject.yaml output: -environments/enable-ssl.yaml

Re: [openstack-dev] [nova] release notes with reno and which patches need that?

Sylvain Bauza wrote on 11/19/2015 08:46:18 PM: > From: Sylvain Bauza > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 11/19/2015 08:47 PM > Subject: Re: [openstack-dev] [nova] release notes

Re: [openstack-dev] [Neutron] Call for review focus

On 20 November 2015 at 14:07, Kyle Mestery wrote: > On Wed, Nov 18, 2015 at 8:14 PM, Armando M. wrote: > >> Hi Neutrites, >> >> > Neutrinos? > I am still experimenting to see what sticks...So far I got Neutrinos, Neutronians, and Neutrites...Neutrinos is

Re: [openstack-dev] [Fuel] Running Fuel node as non-superuser

Stanislaw, proposing patches could be a viable option long-term, however, by the time these patches will make it upstream, Fuel will use CentOS 7 w/ systemd. On Fri, Nov 20, 2015 at 4:05 PM, Stanislaw Bogatkin wrote: > Dmitry, as we work on opensource - it would be

Re: [openstack-dev] [ironic][security] what is OK to put in DEBUG logs?

On 11/19/2015 06:00 AM, Lucas Alvares Gomes wrote: > Hi, > >> Also keep in mind that DEBUG logging, while still should have some masking >> of data, since it is explicitly called out (or should be) as not safe for >> production, can contain some " sensitive" data. Credentials should still be >>

[openstack-dev] [Fuel] Approved but not implemented specs

Hey Fuelers, Today I noticed that some of Fuel specs have been merged for 7.0 while the features themselves weren't landed. It's kind confusing since it seems like the feature was implemented in 7.0 while it's not. What do you think guys about moving such specs into 8.0 folder? I believe it's a

Re: [openstack-dev] [release][stable] OpenStack 2014.2.4 (juno)

On 11/20/2015 6:43 AM, Sean Dague wrote: On 11/19/2015 08:56 PM, Rochelle Grober wrote: Again, my plea to leave the Juno repository on git.openstack.org, but locked down to enable at least grenade testing for Juno->Kilo upgrades. For upgrade testing purposes, python2.6 is not needed as any

[openstack-dev] [Congress] kilo bug on datasource listing

Congress stable-maintenance team: We seem to have a bug in kilo that is making it tough for Bryan Sullivan to get things up and running. The swift driver doesn't have a 'secret' field, which is causing a 500 error when listing datasources. If I remember right, we fixed this bug later.

Re: [openstack-dev] [Fuel] Getting rid of Docker containers on the Fuel master node

With CentOS7 we will have python2.7 at Fuel Admin node as a default version, I believe. -- Best regards, Oleg Gelbukh, Principal Engineer Mirantis On Fri, Nov 20, 2015 at 6:27 AM, Timur Nurlygayanov < tnurlygaya...@mirantis.com> wrote: > Hi Andrey, > > As far as I remember from the last usage

[openstack-dev] OpenStack Developer Mailing List Digest November 7-13

Perma Link: http://www.openstack.org/blog/2015/11/openstack-developer-mailing-list-digest-november-20151107/ New Management Tools and Processes for stable/liberty and Mitaka * For release management, we used a combination of launchpad

Re: [openstack-dev] [Fuel] Approved but not implemented specs

It's a good point. I think it could even be done automatically: once spec freeze is in place, run an infra script and update all CRs still in review with specs targeted to current (and previous) releases by moving them to next release's directory. -Oleg On Fri, Nov 20, 2015 at 3:35 PM, Igor

[openstack-dev] [tricircle]Tokyo Summit Summary

Hi Team, We had very great sessions re Tricircle at Tokyo Summit, both main conference [1] and design summit [2]. After the summit the core team dived into new architecture design as discussed in the design summit session [3] , therefore there had been sorta radio silent, but rest assure the

[openstack-dev] OpenStack Developer Mailing List Digest November 14-20

Perma Link: http://www.openstack.org/blog/2015/11/openstack-developer-mailing-list-digest-november-20151114 Time to Make Some Assertions About Your Projects === * The technical committee defined a number of “assert” tags which allows a project team to to make

Re: [openstack-dev] [Neutron] Bug update

Yeah, I should have reread before hitting the send. It should have been RBAC (I have opened a new official tag). Kevin understood and addressed the bugs :) From: "Armando M." > Reply-To: OpenStack List

<    1   2