Re: [openstack-dev] [fuel] Fuel Community ISO 8.0

Thanks, Igor. Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Thu, Feb 4, 2016 at 1:21 PM, Igor Belikov wrote: > Hi Ivan, > > I think this counts as a bug in our community page, thanks for noticing. > You can get 8.0 Community ISO using links in status dashboard on

[openstack-dev] Disaster recovery solutions for OpenStack clouds?

Hi, Disaster recovery is an important capability of cloud system. I have looked around for available disaster solutions for OpenStack clouds.This is what I have found - Project Smaugn (DRaaS) very early stages - There are vendor specific solutions like Rackspace has VMware SRM based

Re: [openstack-dev] [all] the trouble with names

On 04/02/2016 11:40, Sean Dague wrote: > A few issues have crept up recently with the service catalog, API > headers, API end points, and even similarly named resources in > different resources (e.g. backup), that are all circling around a key > problem. Distributed teams and naming collision. > >

Re: [openstack-dev] [all] the trouble with names

Excerpts from Sean Dague's message of 2016-02-04 06:38:26 -0500: > A few issues have crept up recently with the service catalog, API > headers, API end points, and even similarly named resources in different > resources (e.g. backup), that are all circling around a key problem. > Distributed teams

[openstack-dev] [kolla] Location of Heka Lua plugins

Hi As discussed yesterday in our IRC meeting we'll need specific Lua plugins for parsing OpenStack, MariaDB and RabbitMQ logs. We already have these Lua plugins in one of our Fuel plugins [*]. So our plan is to move these Lua plugins in their own Git repo, and distribute them as deb and rpm

Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

> nice, do you have resource to look at this? or maybe something to add to > Gnocchi's potential backlog. existing plugin still seems useful to those who > want to use custom/proprietary storage. I should have resources for this. Question is where it should live. Since gnocchi is designed to

Re: [openstack-dev] [fuel] Fuel Community ISO 8.0

Hi Ivan, I think this counts as a bug in our community page, thanks for noticing. You can get 8.0 Community ISO using links in status dashboard on https://ci.fuel-infra.org -- Igor Belikov Fuel CI Engineer ibeli...@mirantis.com > On 04 Feb 2016, at 13:53, Ivan Kolodyazhny

[openstack-dev] [puppet] save this URL for CI watching

Now we have our tempest jobs running in gate, we can use openstackhealth service: http://status.openstack.org/openstack-health/#/?groupKey=project=puppet (kudos to mtreinish) Example of job overview:

Re: [openstack-dev] [puppet] compatibility of puppet upstream modules

-Original Message- From: Emilien Macchi [mailto:emil...@redhat.com] Sent: Thursday, February 04, 2016 10:06 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [puppet] compatibility of puppet upstream

[openstack-dev] [gate] build wedged very oddly

I just was looking at the gate to try to sort out why things are backed up, and noticed top of gate was waiting on one test - https://jenkins02.openstack.org/job/gate-tempest-dsvm-full/32506/console Which Jenkins said had been running for 6 hours It failed on internal timeout about 4 hours

Re: [openstack-dev] [Neutron] Evolving the stadium concept

Hi Assaf, I think that if we define a certain criteria we need to make sure that it applies to everyone equally. and it is well understood. I have contributed and still am to both OVN and Dragonflow and hope to continue do so in the future, i want to see both of these solutions become a great

[openstack-dev] [all]Whom should I contact to ask for ATC code

Hello all I am sorry for the broadcasting, but I really don't know whom should I contact. Things is: My friend is a newly developer who already has contribute to openstack project, and would like to know in what way(or email contactor) he can get the ATC code for Austin summit. BR, Eli(Li

[openstack-dev] [all] the trouble with names

A few issues have crept up recently with the service catalog, API headers, API end points, and even similarly named resources in different resources (e.g. backup), that are all circling around a key problem. Distributed teams and naming collision. Every OpenStack project has a unique name by

[openstack-dev] [fuel] Fuel Community ISO 8.0

Hi team, I've tried to download Fuel Community ISO 8.0 from [1] and failed. We've got 2 options there: the latest stable (7.0) and nightly build (9.0). Where can I download 8.0 build? [1] https://www.fuel-infra.org/#fuelget Regards, Ivan Kolodyazhny, http://blog.e0ne.info/

Re: [openstack-dev] [tacker][tacker] TOSCA-Parser 0.4.0 PyPI release

:) Hi Sridhar, You are welcome and absolutely. Looking forward for a continuous collaboration and enhanced NFV support in parser as we go forward. Thanks! Regards, Sahdev Zala From: Sridhar Ramaswamy To: "OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [Neutron] Evolving the stadium concept

On Thu, Feb 4, 2016 at 5:55 PM, Sean M. Collins wrote: > On Thu, Feb 04, 2016 at 04:20:50AM EST, Assaf Muller wrote: >> I understand you see 'Dragonflow being part of the Neutron stadium' >> and 'Dragonflow having high visibility' as tied together. I'm curious, >> from a

Re: [openstack-dev] [openstack][Magnum] ways to get CA certificate in make-cert.sh from Magnum

Wanghua, Could you elaborate why using token is problem? Provision cluster takes deterministic time and expiration time shouldn't be a problem (e.g. we can always assume that provision shouldn't take more than hour for example). Also we can generate new token every time when we update stack,

[openstack-dev] [nova] Authorization by user_id does not work in V2.1 API

Hi Nova developers, I have already submitted a bug report[1], authorization by user_id when deleting a VM instance does not work in Nova V2.1 API although it works in Nova V2.0 API. Has this change been done intentionally? [1] Authorization by user_id does not work in V2.1 API

Re: [openstack-dev] [Magnum] gate issues

Corey, I think we should do more investigation before applying any "hot" patches. E.g. I look at several failures today and honestly there is no way to find out reasons.I believe we are not copying logs

Re: [openstack-dev] [openstack][Magnum] ways to get CA certificate in make-cert.sh from Magnum

Hi Corey, The user is root on those nodes and can get any credentials on those nodes. We can not avoid that, but by this way we can disallow those users who can not login into nodes to access some limited APIs. Regards, Wanghua On Fri, Feb 5, 2016 at 12:24 PM, Corey O'Brien

[openstack-dev] [stable] Kilo gate doesn't like testtools 2.0.0

Hi All, Just a quick heads up that the kilo gate (and therefore anything that relies on kilo)[1] is a little busted. This was originally noticed in 1541879[2] and a quick cap for g-r was proposed, however if my analysis is correct this can't land because of 1542164[3]. testtools 2.0.0 was

Re: [openstack-dev] [all]Whom should I contact to ask for ATC code

hi Thierry, That's great, thanks for your reply :) On 2016年02月04日 21:28, Thierry Carrez wrote: The Summit events staff regularly emits new discount codes to account for recent new contributors (or new project teams being recognized as official). Your friend should automatically receive a

Re: [openstack-dev] [lbaas] [octavia] Proposing Stephen Balukoff as Octavia Core

+1 On Fri, 2016-02-05 at 01:07 +, Adam Harwell wrote: > +1 from me! > > From: Michael Johnson > Sent: Thursday, February 4, 2016 7:03 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: [openstack-dev]

Re: [openstack-dev] [lbaas] [octavia] Proposing Stephen Balukoff as Octavia Core

+1 Doug > On Feb 4, 2016, at 7:06 PM, Brandon Logan wrote: > > +1 > >> On Fri, 2016-02-05 at 01:07 +, Adam Harwell wrote: >> +1 from me! >> >> From: Michael Johnson >> Sent: Thursday, February 4,

Re: [openstack-dev] [nova] Migration progress

I think we can add a config option for this and set a theoretical proper default value, we also add help messages to inform the the user about how inappropriate value of this config option will effect the performance. On Wed, Feb 3, 2016 at 7:45 PM, Daniel P. Berrange

[openstack-dev] [lbaas] [octavia] Proposing Stephen Balukoff as Octavia Core

Octavia Team, I would like to nominate Stephen Balukoff as a core reviewer for the OpenStack Octavia project. His contributions[1] are in line with other cores and he has been an active member of our community. Octavia cores please vote by replying to this e-mail. Michael [1]

Re: [openstack-dev] [Neutron] Evolving the stadium concept

On 02/04/2016 05:36 PM, Assaf Muller wrote: > On Thu, Feb 4, 2016 at 5:55 PM, Sean M. Collins wrote: >> On Thu, Feb 04, 2016 at 04:20:50AM EST, Assaf Muller wrote: >>> I understand you see 'Dragonflow being part of the Neutron stadium' >>> and 'Dragonflow having high

Re: [openstack-dev] [telemetry][aodh] announcing Liusheng as new Aodh liaison

Congratulations Liusheng On Fri, Feb 5, 2016 at 12:07 AM, gordon chung wrote: > hi, > > we've been searching for a lead/liaison/lieutenant for Aodh for some > time. thankfully, we've had a volunteer. > > i'd like to announce Liusheng as the new lead of Aodh, the alarming > service

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

On 4 February 2016 at 08:22, John Belamaric wrote: > > > On Feb 4, 2016, at 11:09 AM, Carl Baldwin wrote: > > > > On Thu, Feb 4, 2016 at 7:23 AM, Pavel Bondar > wrote: > >> I am trying to bring more attention to [1] to make

Re: [openstack-dev] [lbaas] [octavia] Proposing Stephen Balukoff as Octavia Core

+1 from me! From: Michael Johnson Sent: Thursday, February 4, 2016 7:03 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [lbaas] [octavia] Proposing Stephen Balukoff as Octavia Core Octavia

Re: [openstack-dev] [all] the trouble with names

Excerpts from Hayes, Graham's message of 2016-02-04 12:54:56 +: > On 04/02/2016 11:40, Sean Dague wrote: > > A few issues have crept up recently with the service catalog, API > > headers, API end points, and even similarly named resources in > > different resources (e.g. backup), that are all

Re: [openstack-dev] [all] the trouble with names

On 04/02/2016 13:24, Doug Hellmann wrote: > Excerpts from Hayes, Graham's message of 2016-02-04 12:54:56 +: >> On 04/02/2016 11:40, Sean Dague wrote: >>> A few issues have crept up recently with the service catalog, API >>> headers, API end points, and even similarly named resources in >>>

Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

On Thu, Feb 04 2016, Foley, Emma L wrote: > Question is where it should live. > Since gnocchi is designed to be standalone, it seem like that's a potential > home for it. > If not, it also fits in with the existing plugin. It it's a collectd plugin that talk statsd protocol, I'd say it should

Re: [openstack-dev] [all] the trouble with names

On 02/04/2016 09:35 AM, Anne Gentle wrote: > > > On Thu, Feb 4, 2016 at 7:33 AM, Sean Dague > wrote: > > On 02/04/2016 08:18 AM, Doug Hellmann wrote: > > Excerpts from Hayes, Graham's message of 2016-02-04 12:54:56 +: > >> On 04/02/2016

Re: [openstack-dev] [all]Whom should I contact to ask for ATC code

Qiao, Liyong wrote: I am sorry for the broadcasting, but I really don’t know whom should I contact. Things is: My friend is a newly developer who already has contribute to openstack project, and would like to know in what way(or email contactor) he can get the ATC code for Austin summit. Hi!

Re: [openstack-dev] [Cinder] Nominating Patrick East to Cinder Core

On Sat, Jan 30, 2016 at 01:04:58AM +0100, Sean McGinnis wrote: > Patrick has been a strong contributor to Cinder over the last few releases, > both with great code submissions and useful reviews. He also participates > regularly on IRC helping answer questions and providing valuable feedback. >

[openstack-dev] ERROR: Could not find user: demo - 401 error

Hello, When I use the devstack, below error seen: $ cinder list ERROR: Could not find user: demo (Disable debug mode to suppress these details.) (HTTP 401) I tried with admin also..same error Thanks Swami __ OpenStack

Re: [openstack-dev] [all] the trouble with names

On Thu, Feb 4, 2016 at 7:33 AM, Sean Dague wrote: > On 02/04/2016 08:18 AM, Doug Hellmann wrote: > > Excerpts from Hayes, Graham's message of 2016-02-04 12:54:56 +: > >> On 04/02/2016 11:40, Sean Dague wrote: > >>> A few issues have crept up recently with the service catalog,

Re: [openstack-dev] [Neutron] Evolving the stadium concept

On Thu, Feb 4, 2016 at 1:33 AM, Gal Sagie wrote: > As i have commented on the patch i will also send this to the mailing list: > > I really dont see why Dragonflow is not part of this list, given the > criteria you listed. > > Dragonflow is fully developed under

[openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

Hi, I am trying to bring more attention to [1] to make final decision on approach to use. There are a few point that are not 100% clear for me at this point. 1) Do we plan to switch all current clouds to pluggable ipam implementation in Mitaka? yes --> Then data migration can be done as

Re: [openstack-dev] [ironic] Third Party CI Deadlines for Mitaka and N

On 02/03/2016 05:51 PM, Mike Perez wrote: > On 17:00 Nov 30, Mike Perez wrote: >> On October 28th 2015 at the Ironic Third Party CI summit session [1], there >> was >> consensus by the Ironic core and participating vendors that the set of >> deadlines will be: >> >> * Mitaka-2ː Driver teams will

Re: [openstack-dev] [glance][ironic][cinder][nova] 'tar' as an image disk_format

Update: The discussion went in two directions: (1) Whether supporting OS tarballs in Ironic is a good idea ... continuing discussion on the Ironic spec, https://review.openstack.org/#/c/248968/ (2) How an OS tarball should be identified in Glance ... continuing discussion on the Glance

Re: [openstack-dev] [all] the trouble with names

Excerpts from Sean Dague's message of 2016-02-04 08:33:59 -0500: > On 02/04/2016 08:18 AM, Doug Hellmann wrote: > > Excerpts from Hayes, Graham's message of 2016-02-04 12:54:56 +: > >> On 04/02/2016 11:40, Sean Dague wrote: > >>> A few issues have crept up recently with the service catalog,

Re: [openstack-dev] [all] the trouble with names

On 02/04/2016 08:18 AM, Doug Hellmann wrote: > Excerpts from Hayes, Graham's message of 2016-02-04 12:54:56 +: >> On 04/02/2016 11:40, Sean Dague wrote: >>> A few issues have crept up recently with the service catalog, API >>> headers, API end points, and even similarly named resources in >>>

Re: [openstack-dev] [kolla] Location of Heka Lua plugins

+1 for this. +2 for putting the plugins to its own repo. On Thu, Feb 4, 2016 at 9:45 PM, Michal Rostecki wrote: > On 02/04/2016 10:55 AM, Eric LEMOINE wrote: > >> Hi >> >> As discussed yesterday in our IRC meeting we'll need specific Lua >> plugins for parsing OpenStack,

Re: [openstack-dev] [kolla] Location of Heka Lua plugins

TLDR; +1 to have lua in tree of kolla, not sure if we want to switch later So I'm not so sure about switching. If these git repos are in /openstack/ namespace, then sure, otherwise I'd be -1 to this, we don't want to add dependency here. Also we're looking at pretty simple set of files that won't

Re: [openstack-dev] [Manila] Nominate Rodrigo Barbieri for core reviewer team

Thanks everyone! I am very happy to be part of this community and contribute to Manila project! :) On Wed, Feb 3, 2016 at 5:33 AM, Thomas Bechtold wrote: > On Tue, Feb 02, 2016 at 12:30:44PM -0500, Ben Swartzlander wrote: > > Rodrigo (ganso on IRC) joined the Manila project

Re: [openstack-dev] [all] the trouble with names

Hayes, Graham wrote: On 04/02/2016 13:24, Doug Hellmann wrote: Excerpts from Hayes, Graham's message of 2016-02-04 12:54:56 +: On 04/02/2016 11:40, Sean Dague wrote: 2) Have a registry of "common" names. Upside, we can safely use common names everywhere and not fear collision down the

[openstack-dev] [Fuel] virtualenv fails with SSLError: [Errno 20] Not a directory

Folks, as some of you may have noticed, there is a high rate of job failures on Fuel CI in python-fuelclient. That happens because there are some weird issues with virtualenv utility not being able to create new virtual environments. I’ve tested that on my local environment and the problem

[openstack-dev] [openstack][Magnum] ways to get CA certificate in make-cert.sh from Magnum

Hi all, Magnum now use a token to get CA certificate in make-cert.sh. Token has a expiration time. So we should change this method. Here are two proposals. 1. Use trust which I have introduced in [1]. The way has a disadvantage. We can't limit the access to some APIs. For example, if we want to

Re: [openstack-dev] [nova] Migration progress

I agree with Daniel, keep the periods consistent 5 - 5 . Another thought, for such ephemeral/changing data, such as progress, why not save the information in the cache (and flush to database at a lower rate), and retrieve for display to active listeners/UI from the cache. Once complete or

Re: [openstack-dev] [bug-smash] Global OpenStack Bug Smash Mitaka

Hi all, After discussing with TC members and other community guys, we thought March 2-4 might not be a good timing for bug smash. So we decided to change the dates to be March 7 - 9 (Monday - Wednesday) in R4. Please join our efforts to fix bugs for OpenStack. Thanks. -- Shane From: Wang,

Re: [openstack-dev] [openstack][Magnum] ways to get CA certificate in make-cert.sh from Magnum

There currently isn't a way to distinguish between user who creates the bay and the nodes in the bay because the user is root on those nodes. Any credential that the node uses to communicate with Magnum is going to be accessible to the user. Since we already have the trust, that seems like the

Re: [openstack-dev] [nova] Migration progress

On 2016年02月05日 12:02, Bhandaru, Malini K wrote: I agree with Daniel, keep the periods consistent 5 - 5 . Another thought, for such ephemeral/changing data, such as progress, why not save the information in the cache (and flush to database at a lower rate), and retrieve for display to

[openstack-dev] [Magnum] gate issues

So as we're all aware, the gate is a mess right now. I wanted to sum up some of the issues so we can figure out solutions. 1. The functional-api job sometimes fails because bays timeout building after 1 hour. The logs look something like this:

Re: [openstack-dev] [tricircle] DHCP port problem

CC'ed Li Ma who might have insight on this problem On Thu, Feb 4, 2016 at 3:51 PM, Vega Cai wrote: > Hi all, > > When implementing L3 north-south networking functionality, I meet the DHCP > port problem again. > > First let me briefly explain the DHCP port problem. In

Re: [openstack-dev] [puppet] compatibility of puppet upstream modules

On 02/03/2016 04:03 PM, Ptacek, MichalX wrote: > Hi all, > > > > I have one general question, > > currently I am deploying liberty openstack as described in > https://wiki.openstack.org/wiki/Puppet/Deploy > > Unfortunately puppet modules specified in >

Re: [openstack-dev] [Neutron] Evolving the stadium concept

On Thu, Feb 4, 2016 at 8:33 AM, Gal Sagie wrote: > As i have commented on the patch i will also send this to the mailing list: > > I really dont see why Dragonflow is not part of this list, given the > criteria you listed. > > Dragonflow is fully developed under

Re: [openstack-dev] [Neutron] Evolving the stadium concept

On Thu, Feb 4, 2016 at 10:20 AM, Assaf Muller wrote: > On Thu, Feb 4, 2016 at 8:33 AM, Gal Sagie wrote: >> As i have commented on the patch i will also send this to the mailing list: >> >> I really dont see why Dragonflow is not part of this list, given

[openstack-dev] ensuring accurate versions while testing clients and controllers

Since this is a long email, I think this quick summary is in order. The gate/check jobs in Trove are facing a problem [1] which was fixed [2]. The fix has issues and I am looking for input from other projects who may have faced this problem. How does a project with a controller and a client

Re: [openstack-dev] [docs][all] Software design in openstack

Excerpts from Nick Yeates's message of 2016-02-03 21:18:08 -0800: > Josh, thanks for pointing this out and in being hospitable to an outsider. > > Oslo is definitely some of what I was looking for. As you stated, the fact > that there is an extensive review system with high participation, that

Re: [openstack-dev] [Nova][Cinder] Cleanly detaching volumes from failed nodes

My plan was to store the connector object at attach_volume time. I was going to add an additional column to the cinder volume attachment table that stores the connector that came from nova. The problem is live migration. After live migration the connector is out of date. Cinder doesn't

Re: [openstack-dev] [Neutron] Evolving the stadium concept

On Thu, Feb 04, 2016 at 04:20:50AM EST, Assaf Muller wrote: > I understand you see 'Dragonflow being part of the Neutron stadium' > and 'Dragonflow having high visibility' as tied together. I'm curious, > from a practical perspective, how does being a part of the stadium > give Dragonflow

Re: [openstack-dev] [all] the trouble with names

On Thu, Feb 4, 2016 at 4:51 AM, Doug Hellmann wrote: > Excerpts from Sean Dague's message of 2016-02-04 06:38:26 -0500: > > A few issues have crept up recently with the service catalog, API > > headers, API end points, and even similarly named resources in different > >

Re: [openstack-dev] [all] the trouble with names

On 02/04/2016 08:33 AM, Thierry Carrez wrote: Hayes, Graham wrote: On 04/02/2016 13:24, Doug Hellmann wrote: Excerpts from Hayes, Graham's message of 2016-02-04 12:54:56 +: On 04/02/2016 11:40, Sean Dague wrote: 2) Have a registry of "common" names. Upside, we can safely use common

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

On 03/02/2016 10:38 AM, Sam Yaple wrote: On Wed, Feb 3, 2016 at 2:52 PM, Jeremy Stanley <fu...@yuggoth.org> wrote: On 2016-02-03 14:32:36 + (+), Sam Yaple wrote: [...] > Luckily, digging into it it appears cinder already has all the >

Re: [openstack-dev] [Horizon] Recent integration tests failures

That has been a hard week for integration tests, as soon as API-breaking change in xvfbwrapper had been worked around, we have been hit by a new Selenium release, see https://bugs.launchpad.net/horizon/+bug/1541876 Investigation of a root cause is still in progress. On Mon, Feb 1, 2016 at 11:31

Re: [openstack-dev] [Fuel] virtualenv fails with SSLError: [Errno 20] Not a directory

UPD: on Fuel-CI it fails with SSLError: [Errno 185090050] _ssl.c:344: error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system lib as could be found in [1]. This is very important issue to fix because it blocks development of python-fuelclient. It requires attention ASAP.

Re: [openstack-dev] [all] the trouble with names

On 04/02/2016 9:04 AM, Morgan Fainberg wrote: On Thu, Feb 4, 2016 at 4:51 AM, Doug Hellmann > wrote: Excerpts from Sean Dague's message of 2016-02-04 06:38:26 -0500: > A few issues have crept up recently with the service catalog, API >

Re: [openstack-dev] [grenade][keystone] Keystone multinode grenade

On 02/04/2016 10:25 AM, Grasza, Grzegorz wrote: > Hi Sean, > > we are looking into testing online schema migrations in keystone. > > > > The idea is to run grenade with multinode support, but it would be > something different than the current implementation. > > > > Currently, the two

[openstack-dev] [telemetry][aodh] announcing Liusheng as new Aodh liaison

hi, we've been searching for a lead/liaison/lieutenant for Aodh for some time. thankfully, we've had a volunteer. i'd like to announce Liusheng as the new lead of Aodh, the alarming service under Telemetry. he will help me with monitor bugs and specs and will be another resource for alarming

[openstack-dev] [heat] re-ask about Global OpenStack Bug Smash Mitaka

Hi Heaters. I want to attract your attention on mail [1] about Bug Smash Day and ask question related with it: Does anybody plan to visit Moscow during this event? If yes, we can meet there and work together :) It will be really cool to create group of people in different locations and discuss

Re: [openstack-dev] [Manila] Nominate Rodrigo Barbieri for core reviewer team

On 02/02/2016 12:30 PM, Ben Swartzlander wrote: Rodrigo (ganso on IRC) joined the Manila project back in the Kilo release and has been working on share migration (an important core feature) for the last 2 releases. Since Tokyo he has dedicated himself to reviews and community participation. I

Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

> > So, metrics are grouped by the type of resource they use, and each metric > has to be listed. > > Grouping isn't a problem, but creating an exhaustive list might be, since > there are 100+ plugins [1] in collectd which can provide statistics, although > not all of these are useful, and some

Re: [openstack-dev] [Neutron][LBaaS][barbican]TLS container could not be found

Could you provide your neutron-lbaas.conf? Depending on what version you're using, barbican may not be the default secret backend (I believe this has been fixed). Alternatively, it depends on what user accounts are involved -- this should definitely work if you are using only the single admin

Re: [openstack-dev] [all] the trouble with names

While we all consider to look at this problem from within the perspective of OpenStack, the consumer of OpenStack is somebody that is wanting to run a cloud, and not develop a cloud (granted there is overlap in said implementation). They are also comparing clouds and features (e.g. compute,

Re: [openstack-dev] [all] the trouble with names

On 04/02/2016 15:40, Ryan Brown wrote: > On 02/04/2016 09:32 AM, michael mccune wrote: >> On 02/04/2016 08:33 AM, Thierry Carrez wrote: >>> Hayes, Graham wrote: On 04/02/2016 13:24, Doug Hellmann wrote: > Excerpts from Hayes, Graham's message of 2016-02-04 12:54:56 +: >> On

[openstack-dev] [TripleO] Fencing configuration

Hi all, currently in order to enable automatic fencing on the controllers we need to pass something like the following yaml to an overcloud deploy: """ EnableFencing: true FencingConfig: {

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

On Thu, Feb 4, 2016 at 7:23 AM, Pavel Bondar wrote: > I am trying to bring more attention to [1] to make final decision on > approach to use. > There are a few point that are not 100% clear for me at this point. > > 1) Do we plan to switch all current clouds to pluggable

Re: [openstack-dev] [kolla] Location of Heka Lua plugins

On Thu, Feb 4, 2016 at 9:22 AM, Michał Jastrzębski wrote: > TLDR; +1 to have lua in tree of kolla, not sure if we want to switch later > > So I'm not so sure about switching. If these git repos are in > /openstack/ namespace, then sure, otherwise I'd be -1 to this, we > don't

Re: [openstack-dev] [Cinder] Nominating Patrick East to Cinder Core

A late +1. Congrats Patrick! Welcome to the core team. Xing > On Feb 4, 2016, at 9:31 AM, Sean McGinnis wrote: > >> On Sat, Jan 30, 2016 at 01:04:58AM +0100, Sean McGinnis wrote: >> Patrick has been a strong contributor to Cinder over the last few releases, >> both

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

> On Feb 4, 2016, at 11:09 AM, Carl Baldwin wrote: > > On Thu, Feb 4, 2016 at 7:23 AM, Pavel Bondar wrote: >> I am trying to bring more attention to [1] to make final decision on >> approach to use. >> There are a few point that are not 100% clear for

Re: [openstack-dev] [all] the trouble with names

What about using a combination of two word names, and generic names. For example, you might have cinder-blockstorage and foo-blockstorage The advantage there is that we don't need to do the thesaurus.com thing, but also, it enables to specify just blockstorage via a registry.

Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

> On Thu, Feb 04 2016, Foley, Emma L wrote: > > > Question is where it should live. > > Since gnocchi is designed to be standalone, it seem like that's a potential > home for it. > > If not, it also fits in with the existing plugin. > > It it's a collectd plugin that talk statsd protocol, I'd

[openstack-dev] [kuryr] gate-install-dsvm-kuryr is failed

Hi Kuryr all, I notice the gate-install-dsvm-kuryr is failed since afternoon. All patchs are failed in this jenkins check. And I see the error log seems like run install_docker.sh failed, any idea? Log:

[openstack-dev] [grenade][keystone] Keystone multinode grenade

Hi Sean, we are looking into testing online schema migrations in keystone. The idea is to run grenade with multinode support, but it would be something different than the current implementation. Currently, the two nodes which are started run with different roles, one is a controller the other

Re: [openstack-dev] [all] the trouble with names

On 02/04/2016 09:32 AM, michael mccune wrote: On 02/04/2016 08:33 AM, Thierry Carrez wrote: Hayes, Graham wrote: On 04/02/2016 13:24, Doug Hellmann wrote: Excerpts from Hayes, Graham's message of 2016-02-04 12:54:56 +: On 04/02/2016 11:40, Sean Dague wrote: 2) Have a registry of

[openstack-dev] StoryBoard Midcycle Meetup

Hi, all, The StoryBoard[1] team is excited[2] to announce that we're hosting a meetup on the 17th of February, 2016, in Manchester, UK[3]! It's free to attend, and there will be cake. Wiki Page: https://wiki.openstack.org/wiki/StoryBoard/Midcycle_Meetup Etherpad:

Re: [openstack-dev] [all] the trouble with names

On 02/04/2016 10:31 AM, Nick Chase wrote: > What about using a combination of two word names, and generic names. For > example, you might have > > cinder-blockstorage > > and > > foo-blockstorage > > The advantage there is that we don't need to do the thesaurus.com >

Re: [openstack-dev] [puppet] compatibility of puppet upstream modules

Hi Emilien, It seems that keystone database is not populated, because of something, which happened on previous runs (e.g. some packages installation), Following rows are visible just in log from first attempt Debug: Executing '/usr/bin/mysql -e CREATE USER 'keystone'@'127.0.0.1' IDENTIFIED BY

Re: [openstack-dev] [OpenStack-Ansible] Mid Cycle Sprint

Hi everyone, As discussed in the community meeting today [1] we will be able to include remote participants in the Mid Cycle via Video Conference. In order to facilitate this I need to ensure that we have an attendance list for me to send the Video Conference invitations to, so please get a

Re: [openstack-dev] [OpenStack-Ansible] Mid Cycle Sprint

On 02/04/2016 12:41 PM, Jesse Pretorius wrote: > As discussed in the community meeting today [1] we will be able to include > remote participants in the Mid Cycle via Video Conference. In order to > facilitate this I need to ensure that we have an attendance list for me to > send the Video

Re: [openstack-dev] [infra] openstack/requirements repo has a stable/icehouse branch...

On 2016-02-04 18:17:07 + (+), Jeremy Stanley wrote: > I was getting around to taking care of this just now, and it looks > like someone has deleted the stable/icehouse branch without tagging > it icehouse-eol first? [...] Nevermind--it's still there. Perhaps I need glasses (or afternoon

[openstack-dev] [oslo][doc][fuel] Removal of logging use_syslog_rfc_format configuration option

In Mitaka we are planning on removing the deprecated logging configuration option use_syslog_rfc_format [1] Matches in openstack-manuals [2] and fuel-library puppet modules [3] should be removed to avoid any dated documentation or errors in operation respectively. This option can also be found

Re: [openstack-dev] [puppet] compatibility of puppet upstream modules

If you can't isolate the exact thing you need to get cleaned up here it can be difficult to unwind. You'll either need to read the code to see what's triggering the db setup (which is probably the package installs) or start on a clean box. I'd recommend the latter. On Thu, Feb 4, 2016 at 10:35

Re: [openstack-dev] [infra] openstack/requirements repo has a stable/icehouse branch...

On 2015-12-16 15:35:23 -0600 (-0600), Matt Riedemann wrote: > That should be deleted, right? Or are there random projects that > still have stable/icehouse branches in projects.txt and we care > about them? I was getting around to taking care of this just now, and it looks like someone has

Re: [openstack-dev] [Neutron] Evolving the stadium concept

On 4 February 2016 at 04:05, Gal Sagie wrote: > Hi Assaf, > > I think that if we define a certain criteria we need to make sure that it > applies to everyone equally. > and it is well understood. > I must admit I am still waking up and going through the entire logs etc.

Re: [openstack-dev] [infra] openstack/requirements repo has a stable/icehouse branch...

On Thu, Feb 4, 2016 at 12:21 PM, Jeremy Stanley wrote: > Nevermind--it's still there. Perhaps I need glasses (or afternoon > coffee). > Nah, the fastest way to find something like that is to send a note to a public mail list. :) dt -- Dean Troyer dtro...@gmail.com

Re: [openstack-dev] [kolla] Location of Heka Lua plugins

I agree with Michael. If the LUA plugins are going to be a separate repository, they need to be in the OpenStack git namespace. I am +2 to the idea assuming after extraction of the LUA plugins they hit the OpenStack git namespace. Regards -steve On 2/4/16, 7:22 AM, "Michał Jastrzębski"

[openstack-dev] [kolla][midcycle] last notification regarding Kolla Midcycle February 9th and February 10th

Hey folks, The Kolla midcycle is prepared for next week Tuesday February 9th 9:00 am - 5:00 pm and Wednesday February 10th 9:00 am - 3:30 pm. Breakfast, lunch, coffee, soda, water are provided both days, and dinner is provided Tuesday evening. The sprint wiki page is available here:

  1   2   >