[openstack-dev] [infra] shutting down pholio.openstack.org

Hello, We will be shutting down pholio.openstack.org in the next few days. As discussed at the last #infra meeting [1], in short, "the times they are a changin'" and the Pholio services have not been required. Of course the original deployment puppet, etc, remains (see [2]), so you may reach

Re: [openstack-dev] [all][tc][glance] Glance needs help, it's getting critical

On 06/12/2017 01:50 PM, Flavio Percoco wrote: Glance can be very exciting if one focuses on the interesting bits and it's an *AWESOME* place where new comers can start contributing, new developers can learn and practice, etc. That said, I believe that code doesn't have to be challenging to be

Re: [openstack-dev] [all][tc][glance] Glance needs help, it's getting critical

On Tue, Jun 13, 2017 at 4:43 AM, Flavio Percoco wrote: > > > On Mon, Jun 12, 2017, 19:47 Mikhail Fedosin wrote: > >> On Tue, Jun 13, 2017 at 12:01 AM, Flavio Percoco >> wrote: >> >>> On 12/06/17 23:20 +0300, Mikhail Fedosin wrote: >>>

[openstack-dev] [Blazar] Skip weekly meeting

Hi Blazar folks, Based on the discussion in last meeting, the team will not have the weekly meeting this week because most of the members are out of town. Next meeting is planed to be 20th Jun. best regards, Masahito

Re: [openstack-dev] [all][tc][glance] Glance needs help, it's getting critical

I take a week off and look at what happens ... Sorry for top-posting, but I just have some general comments. Mike raises some good points, but I think it's too late in the cycle to swap Glance out for Glare and expect everything to work properly. (I don't mean to imply anything about the

Re: [openstack-dev] [all][tc][glance] Glance needs help, it's getting critical

On Mon, Jun 12, 2017, 19:47 Mikhail Fedosin wrote: > On Tue, Jun 13, 2017 at 12:01 AM, Flavio Percoco > wrote: > >> On 12/06/17 23:20 +0300, Mikhail Fedosin wrote: >> >>> My opinion is that Glance stagnates and it's really hard to implement new >>>

Re: [openstack-dev] [oslo.db] Stepping down from core

hey Roman - It was a huge pleasure working w/ you on oslo.db!I hope we can collaborate again soon. - mike On 06/11/2017 10:32 AM, Roman Podoliaka wrote: Hi all, I recently changed job and hasn't been able to devote as much time to oslo.db as it is expected from a core reviewer. I'm

Re: [openstack-dev] [oslo.db] Stepping down from core

Best Wishes Roman! hope our paths will cross again. Thanks, Dims On Sun, Jun 11, 2017 at 10:32 AM, Roman Podoliaka wrote: > Hi all, > > I recently changed job and hasn't been able to devote as much time to > oslo.db as it is expected from a core reviewer. I'm no

Re: [openstack-dev] [all][tc][glance] Glance needs help, it's getting critical

On Tue, Jun 13, 2017 at 12:01 AM, Flavio Percoco wrote: > On 12/06/17 23:20 +0300, Mikhail Fedosin wrote: > >> My opinion is that Glance stagnates and it's really hard to implement new >> features there. In two years, only one major improvement was developed >> (Image Import

Re: [openstack-dev] [all][tc][glance] Glance needs help, it's getting critical

On Mon, Jun 12, 2017, 19:25 Mike Perez wrote: > On 16:01 Jun 12, Flavio Percoco wrote: > > On 12/06/17 23:20 +0300, Mikhail Fedosin wrote: > > > My opinion is that Glance stagnates and it's really hard to implement > new > > > features there. In two years, only one major

Re: [openstack-dev] [all][tc][glance] Glance needs help, it's getting critical

On 16:01 Jun 12, Flavio Percoco wrote: > On 12/06/17 23:20 +0300, Mikhail Fedosin wrote: > > My opinion is that Glance stagnates and it's really hard to implement new > > features there. In two years, only one major improvement was developed > > (Image Import Refactoring), and no one has tested it

Re: [openstack-dev] [ironic][nova] Goodbye^W See you later

On 08:45 Jun 08, Jim Rollenhagen wrote: > Hey friends, > > I've been mostly missing for the past six weeks while looking for a new > job, so maybe you've forgotten me already, maybe not. I'm happy to tell you > I've found one that I think is a great opportunity for me. But, I'm sad to > tell you

Re: [openstack-dev] [oslo.db] Stepping down from core

On 17:32 Jun 11, Roman Podoliaka wrote: > Hi all, > > I recently changed job and hasn't been able to devote as much time to > oslo.db as it is expected from a core reviewer. I'm no longer working > on OpenStack, so you won't see me around much. > > Anyway, it's been an amazing experience to work

[openstack-dev] [tripleo][ci] TripleO OVB check gates to move to third party

Greetings, TripleO OVB check gates are managed by upstream Zuul and executed on nodes provided by test cloud RH1. RDO Cloud is now available as a test cloud to be used when running CI jobs. To utilize to RDO Cloud, we could either: - continue to run from upstream Zuul (and spin up nodes to

Re: [openstack-dev] Is Routes==2.3.1 a binary only package or something?

Certainly removing the "--no-binary :all:" results in a build that builds. I'll test and see if it works todayish. Michael On Mon, Jun 12, 2017 at 9:56 PM, Chris Smart wrote: > On Mon, 12 Jun 2017, at 21:36, Michael Still wrote: > > The experimental buildroot based ironic

Re: [openstack-dev] [telemetry][ceilometer][opendaylight][networking-odl] OpenDaylight Driver for Ceilometer

What's the policy of telemetry or ceilometer? As long as it follows the policy of them, networking-odl is fine to include such drivers. Thanks, On Mon, Jun 12, 2017 at 08:25:49AM +, Deepthi V V wrote: > Hi, > > We plan to propose a ceilometer driver for

Re: [openstack-dev] [tripleo] Role updates

On Mon, Jun 12, 2017 at 2:55 AM, Dmitry Tantsur wrote: > On 06/09/2017 05:24 PM, Alex Schultz wrote: >> >> Hey folks, >> >> I wanted to bring to your attention that we've merged the change[0] to >> add a basic set of roles that can be combined to create your own >>

Re: [openstack-dev] [forum] Future of Stackalytics

On 2017-06-12 14:07:51 -0700 (-0700), Ken'ichi Ohmichi wrote: [...] > The difference between current stackalytics config and the above API > is stackalytics contains gerrit-id and launchpad-id on the config > but the API doesn't. I guess we can use e-mail address instead of > gerrit-id and

Re: [openstack-dev] [tripleo][ci] tripleo periodic jobs moving to RDO's software factory and RDO Cloud

On Mon, Jun 12, 2017 at 05:01:26PM -0400, Wesley Hayutin wrote: > Greetings, > > I wanted to send out a summary email regarding some work that is still > developing and being planned to give interested parties time to comment and > prepare for change. > > Project: > Move tripleo periodic

Re: [openstack-dev] [all][tc][glance] Glance needs help, it's getting critical

On 12/06/17 23:20 +0300, Mikhail Fedosin wrote: My opinion is that Glance stagnates and it's really hard to implement new features there. In two years, only one major improvement was developed (Image Import Refactoring), and no one has tested it in production yet. And this is in the heyday of

Re: [openstack-dev] [forum] Future of Stackalytics

2017-06-08 10:51 GMT-07:00 Jeremy Stanley : > On 2017-06-08 09:49:03 -0700 (-0700), Ken'ichi Ohmichi wrote: >> 2017-06-08 7:19 GMT-07:00 Jeremy Stanley : > [...] >> > There is a foundation member directory API now which provides >> > affiliation details and

[openstack-dev] [tripleo][ci] tripleo periodic jobs moving to RDO's software factory and RDO Cloud

Greetings, I wanted to send out a summary email regarding some work that is still developing and being planned to give interested parties time to comment and prepare for change. Project: Move tripleo periodic promotion jobs Goal: Increase the cadence of tripleo-ci periodic promotion

Re: [openstack-dev] [heat] Making stack outputs static

On 12/06/17 16:21, Steven Hardy wrote: I think we wanted to move to convergence anyway so I don't see a problem with this. I know there was some discussion about starting to test with convergence in tripleo-ci, does anyone know what, if anything, happened with that? There's an experimental job

Re: [openstack-dev] [heat] Making stack outputs static

On Mon, Jun 12, 2017 at 6:18 PM, Ben Nemec wrote: > > > On 06/09/2017 03:10 PM, Zane Bitter wrote: >> >> History lesson: a long, long time ago we made a very big mistake. We >> treated stack outputs as things that would be resolved dynamically when >> you requested them,

Re: [openstack-dev] [all][tc][glance] Glance needs help, it's getting critical

Well... My suggestion is to keep Glance maintained and begin experimental adoption of Glare. So this is not an immediate replacement, but the evolution of the Image service. My opinion is that Glance stagnates and it's really hard to implement new features there. In two years, only one major

Re: [openstack-dev] [User-committee] Action Items WG Chairs: Requesting your input to a cross Working Group session

WG Chairs, Please, take a moment to add your date and time preferences in the doddle poll below prepared. We need all WG Chairs to attend this meeting. If you can’t attend any of the proposed times, please find a member of the WG that could attend and provide an update on the WG activities. If

Re: [openstack-dev] [all][tc][glance] Glance needs help, it's getting critical

On 12/06/17 15:37 -0400, Sean Dague wrote: On 06/12/2017 03:20 PM, Flavio Percoco wrote: Could you please elaborate more on why you think switching code bases is going to solve the current problem? In your email you talked about Glance's over-engineered code as being the thing driving people

Re: [openstack-dev] [all][tc][glance] Glance needs help, it's getting critical

On 06/12/2017 03:20 PM, Flavio Percoco wrote: > Could you please elaborate more on why you think switching code bases is > going > to solve the current problem? In your email you talked about Glance's > over-engineered code as being the thing driving people away and while I > disagree > with that

Re: [openstack-dev] [all][tc][glance] Glance needs help, it's getting critical

On 12/06/17 16:56 +0300, Mikhail Fedosin wrote: Hello! Flavio raised a very difficult and important question, and I think that we, as community members, should decide what to do with Glance next. Hi Mike, I will try to state my subjective opinion. I was involved in the Glance project for

[openstack-dev] [ironic] this week's priorities and subteam reports

Hi, We are glad to present this week's priorities and subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. This Week's Priorities (as of the weekly ironic meeting) 1. booting from

Re: [openstack-dev] [tripleo] pike m2 has been released

On Mon, Jun 12, 2017 at 7:20 PM, Ben Nemec wrote: > > > On 06/09/2017 05:39 PM, Emilien Macchi wrote: >> >> On Fri, Jun 9, 2017 at 5:01 PM, Ben Nemec wrote: >>> >>> Hmm, I was expecting an instack-undercloud release as part of m2. Is >>> there >>>

Re: [openstack-dev] [puppet][tripleo] Add ganesha puppet module

On Mon, Jun 12, 2017 at 12:27 PM, Jan Provaznik wrote: > Hi, > we would like to use nfs-ganesha for accessing shares on ceph storage > cluster[1]. There is not yet a puppet module which would install and > configure nfs-ganesha service. So to be able to set up nfs-ganesha

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

On 06/12/2017 02:17 PM, Edward Leafe wrote: On Jun 12, 2017, at 10:20 AM, Jay Pipes > wrote: The RP uuid is part of the provider: the compute node's uuid, and (after https://review.openstack.org/#/c/469147/ merges) the PCI device's uuid. So in

[openstack-dev] [swift] upcoming impact to configuration in Swift 2.15.0

## Summary Swift storage policies using ISA-L Vandermonde (`isa_l_rs_vand`) and having 5 or more parity bits will no longer be allowed. Swift's services will refuse to start unless these policies are deprecated. All existing data in these policies should be migrated to a different storage policy

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

On Jun 12, 2017, at 10:20 AM, Jay Pipes wrote: >> The RP uuid is part of the provider: the compute node's uuid, and (after >> https://review.openstack.org/#/c/469147/ merges) the PCI device's uuid. So >> in the code that passes the PCI device information to the scheduler,

Re: [openstack-dev] [ironic][nova] Goodbye^W See you later

Just getting back from vacation and I read this :( So sorry to see you go. Thank you for all your help over the years with Ironic and helping me with Ironic! Best of luck with your new work. Your new employer is very lucky! John On Thu, Jun 8, 2017 at 5:45 AM, Jim Rollenhagen

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

"Otherwise, -onetime will need to launch new containers each config change." You say that like its a bad thing That sounds like a good feature to me. atomic containers. You always know the state of the system. As an Operator, I want to know which containers have the new config, which have

Re: [openstack-dev] [tripleo] pike m2 has been released

On 06/09/2017 05:39 PM, Emilien Macchi wrote: On Fri, Jun 9, 2017 at 5:01 PM, Ben Nemec wrote: Hmm, I was expecting an instack-undercloud release as part of m2. Is there a reason we didn't do that? You just released a new tag:

Re: [openstack-dev] [heat] Making stack outputs static

On 06/09/2017 03:10 PM, Zane Bitter wrote: History lesson: a long, long time ago we made a very big mistake. We treated stack outputs as things that would be resolved dynamically when you requested them, instead of having values fixed at the time the template was created or updated. This makes

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

+1 for putting confd in a side car with shared namespaces. much more k8s native. Still generally -1 on the approach of using confd instead of configmaps. You loose all the atomicity that k8s provides with deployments. It breaks upgrade/downgrade behavior. Would it be possible to have confd run

Re: [openstack-dev] [all][tc][glance] Glance needs help, it's getting critical

Just quick comment here on my day off. I will get proper reply to the chain itself tomorrow when I'm back. While I cannot argue with all Mike's points below, I personally cannot stand behind his proposals here and just want to indicate that this is view of one member, not the Glance community by

Re: [openstack-dev] [keystone][glance][nova][neutron][horizon][cinder][osc][swift][manila][telemetry][heat][ptls][all][tc][docs] Documentation migration spec

I added subject tags for the projects most affected by this change. It would be good to have the PTLs or liaisons from those teams review the spec so there are no surprises when we start moving files around. Excerpts from Alexandra Settle's message of 2017-06-08 15:17:34 +: > Hi everyone, >

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

On 06/09/2017 06:31 PM, Ed Leafe wrote: On Jun 9, 2017, at 4:35 PM, Jay Pipes wrote: We can declare that allocating for shared disk is fairly deterministic if we assume that any given compute node is only associated with one shared disk provider. a) we can't assume that

Re: [openstack-dev] [telemetry][ceilometer][opendaylight][networking-odl] OpenDaylight Driver for Ceilometer

On 12/06/17 04:25 AM, Deepthi V V wrote: > Hi, > > > > We plan to propose a ceilometer driver for collecting network statistics > information from OpenDaylight. We were thinking if we could have the > driver code residing in networking-odl project instead of Ceilometer > project. The thought is

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On 12.06.2017 14:02, Jiří Stránský wrote: > On 9.6.2017 18:51, Flavio Percoco wrote: >> A-ha, ok! I figured this was another option. In this case I guess we >> would >> have 2 options: >> >> 1. Run confd + openstack service in side the container. My concern in >> this >> case >> would be that we'd

[openstack-dev] [os-upstream-institute] Meeting reminder

Hi Training Team, This is a friendly reminder to have our first meeting in the new alternating time slot. The meeting will take place tomorrow (Tuesday, June 13) at 0900 UTC on #openstack-meeting-3. You can find the agenda here:

Re: [openstack-dev] [all][tc][glance] Glance needs help, it's getting critical

Hello! Flavio raised a very difficult and important question, and I think that we, as community members, should decide what to do with Glance next. I will try to state my subjective opinion. I was involved in the Glance project for almost three years and studied it fairly plank. I believe that

Re: [openstack-dev] [tc] Status update, Jun 12

Thierry Carrez wrote: > == Open discussions == > > The situation on documenting the state of MySQL / postgresql has been > unblocked using an ad-hoc IRC meeting[5], which resulted in Dirk Mueller > producing a new revision of sdague's initial proposal, ready for more > reviews: > > * Declare

Re: [openstack-dev] [all][tc][glance] Glance needs help, it's getting critical

On 12/06/17 09:13 -0400, Sean Dague wrote: On 06/09/2017 01:07 PM, Flavio Percoco wrote: Would it be possible to get help w/ reviews from folks from teams like nova/cinder/keystone? Any help is welcomed, of course, but I'm trying to think about teams that may be familiar with the Glance

[openstack-dev] [ironic] the driver composition and breaking changes to the supported interfaces

Hi folks! I want to raise something we haven't apparently thought about when working on the driver composition reform. For example, an iRMC patch [0] replaces 'pxe' boot with 'irmc-pxe'. This is the correct thing to do in this case. They're extending the PXE boot, and need a new class and a

Re: [openstack-dev] [oslo.db] Stepping down from core

Good luck with your new position Roman. You were always helpful and friendly. Thanks, Dinesh Bhor -Original Message- From: Roman Podoliaka [mailto:roman.podoli...@gmail.com] Sent: Sunday, June 11, 2017 8:03 PM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [oslo.db]

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On 12/06/17 10:07 +0200, Bogdan Dobrelya wrote: On 09.06.2017 18:51, Flavio Percoco wrote: On Fri, Jun 9, 2017 at 8:07 AM Doug Hellmann > wrote: Excerpts from Flavio Percoco's message of 2017-06-08 22:28:05 +: > Unless I'm

Re: [openstack-dev] [ptg] Strawman Queens PTG week slicing

Telles Nobrega wrote: > First of all, thanks for putting this up and the organization looks > good. I just want to remove that ? from Sahara on Friday. > We discussed and we believe that Wednesday and Thursday will be suffice. Thanks Telles! I updated the high-level schedule. -- Thierry Carrez

Re: [openstack-dev] [all][tc][glance] Glance needs help, it's getting critical

On 06/09/2017 01:07 PM, Flavio Percoco wrote: > (sorry if duplicate, having troubles with email) > > Hi Team, > > I've been working a bit with the Glance team and trying to help where I > can and > I can't but be worried about the critical status of the Glance team. > Unfortunately, the number

[openstack-dev] [meteos] Meteos Weekly Meeting

Hi Meteos Team, I would like to skip weekly meeting at tomorrow. I am little bit busy now. I have not registered a spec about tensorflow implementation yet. Let's discuss tensorflow implementation after we have finished spec. And I would like discuss CFP(call for presentation) of upcoming

Re: [openstack-dev] [oslo.db] Stepping down from core

On 6/11/2017 9:32 AM, Roman Podoliaka wrote: Hi all, I recently changed job and hasn't been able to devote as much time to oslo.db as it is expected from a core reviewer. I'm no longer working on OpenStack, so you won't see me around much. Anyway, it's been an amazing experience to work with

Re: [openstack-dev] [qa][requirements][all] removing global pins for linters

Excerpts from Sean Dague's message of 2017-06-12 07:09:12 -0400: > On 06/11/2017 11:30 AM, Doug Hellmann wrote: > > The recent thread about updating the pylint version in > > global-requirements.txt raised an issue because it was trying to > > update the pylint version for all projects using it,

Re: [openstack-dev] [all][tc][glance] Glance needs help, it's getting critical

Flavio Percoco wrote: > I've been working a bit with the Glance team and trying to help where I > can and I can't but be worried about the critical status of the Glance team. > Unfortunately, the number of participants in the Glance team has been > reduced a lot resulting in the project not being

Re: [openstack-dev] [ptg] Strawman Queens PTG week slicing

First of all, thanks for putting this up and the organization looks good. I just want to remove that ? from Sahara on Friday. We discussed and we believe that Wednesday and Thursday will be suffice. Best regards, On Fri, Jun 2, 2017 at 6:29 AM Emilien Macchi wrote: > On

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On 9.6.2017 18:51, Flavio Percoco wrote: A-ha, ok! I figured this was another option. In this case I guess we would have 2 options: 1. Run confd + openstack service in side the container. My concern in this case would be that we'd have to run 2 services inside the container and structure things

Re: [openstack-dev] Is Routes==2.3.1 a binary only package or something?

On Mon, 12 Jun 2017, at 21:36, Michael Still wrote: > The experimental buildroot based ironic python agent bans all binaries, I > am not 100% sure why. Chris is the guy there. > Buildroot ironic python agent forces a build of all the ironic-python-agent dependencies (as per requirements and

Re: [openstack-dev] Is Routes==2.3.1 a binary only package or something?

The experimental buildroot based ironic python agent bans all binaries, I am not 100% sure why. Chris is the guy there. I'm using that ipa as neither the coreos or tinyipa versions support the broadcom nic in this here ibm x3550. Michael On 12 Jun 2017 8:56 PM, "Sean Dague"

Re: [openstack-dev] [tripleo] Role updates

On 12.6.2017 10:55, Dmitry Tantsur wrote: On 06/09/2017 05:24 PM, Alex Schultz wrote: Hey folks, I wanted to bring to your attention that we've merged the change[0] to add a basic set of roles that can be combined to create your own roles_data.yaml as needed. With this change the

Re: [openstack-dev] [qa][requirements][all] removing global pins for linters

On 06/11/2017 11:30 AM, Doug Hellmann wrote: > The recent thread about updating the pylint version in > global-requirements.txt raised an issue because it was trying to > update the pylint version for all projects using it, but some teams > were not ready for the new tests in the latest version. I

Re: [openstack-dev] Is Routes==2.3.1 a binary only package or something?

On 06/12/2017 04:29 AM, Michael Still wrote: > Hi, > > I'm trying to explain this behaviour in stable/newton, which specifies > Routes==2.3.1 in upper-constraints: > > $ pip install --no-binary :all: Routes==2.3.1 > ... > Could not find a version that satisfies the requirement Routes==2.3.1 >

[openstack-dev] [puppet][tripleo] Add ganesha puppet module

Hi, we would like to use nfs-ganesha for accessing shares on ceph storage cluster[1]. There is not yet a puppet module which would install and configure nfs-ganesha service. So to be able to set up nfs-ganesha with TripleO, I'd like to create a new ganesha puppet module under openstack-puppet

Re: [openstack-dev] Is Routes==2.3.1 a binary only package or something?

On Mon, 12 Jun 2017, at 18:29, Michael Still wrote: > Hi, > > This implies to me that perhaps Routes version 2.3.1 is a binary-only > release and that stable/newton is therefore broken for people who don't > like binary packages (in my case because they're building an install > image > for an

[openstack-dev] [nova] notification update week 24

Hi, Here is the status update / focus setting mail about notification work for week 24. Bugs [Medium] https://bugs.launchpad.net/nova/+bug/1657428 The instance notifications are sent with inconsistent timestamp format. One of the prerequisite patches needs some discussion

[openstack-dev] [tc] Status update, Jun 12

Hi! A bit late due to travel, here is an update on the status of a number of TC-proposed governance changes, in an attempt to rely less on a weekly meeting to convey that information. You can find the full status list of open topics at: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee

Re: [openstack-dev] [tripleo] Role updates

On 06/09/2017 05:24 PM, Alex Schultz wrote: Hey folks, I wanted to bring to your attention that we've merged the change[0] to add a basic set of roles that can be combined to create your own roles_data.yaml as needed. With this change the roles_data.yaml and roles_data_undercloud.yaml files in

[openstack-dev] Is Routes==2.3.1 a binary only package or something?

Hi, I'm trying to explain this behaviour in stable/newton, which specifies Routes==2.3.1 in upper-constraints: $ pip install --no-binary :all: Routes==2.3.1 ... Could not find a version that satisfies the requirement Routes==2.3.1 (from versions: 1.5, 1.5.1, 1.5.2, 1.6, 1.6.1, 1.6.2, 1.6.3,

[openstack-dev] [telemetry][ceilometer][opendaylight][networking-odl] OpenDaylight Driver for Ceilometer

Hi, We plan to propose a ceilometer driver for collecting network statistics information from OpenDaylight. We were thinking if we could have the driver code residing in networking-odl project instead of Ceilometer project. The thought is we have OpenDaylight depended code restricted to n-odl

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On 09.06.2017 18:51, Flavio Percoco wrote: > > > On Fri, Jun 9, 2017 at 8:07 AM Doug Hellmann > wrote: > > Excerpts from Flavio Percoco's message of 2017-06-08 22:28:05 +: > > > Unless I'm missing something, to use confd with

Re: [openstack-dev] [ironic][nova] Goodbye^W See you later

Jim Rollenhagen wrote: > I've been mostly missing for the past six weeks while looking for a new > job, so maybe you've forgotten me already, maybe not. I'm happy to tell > you I've found one that I think is a great opportunity for me. But, I'm > sad to tell you that it's totally outside of the

Re: [openstack-dev] [oslo.db] Stepping down from core

Roman, Thanks for your contributions for oslo.db, hope we can have cross path again in the futrue. Best wishes! 2017-06-11 23:17 GMT+08:00 Doug Hellmann : > Excerpts from Roman Podoliaka's message of 2017-06-11 17:32:49 +0300: > > Hi all, > > > > I recently changed job

[openstack-dev] [openstackclient][zaqar]ensure name convention about the new commands in zaqarclient

Hi! Zaqar now have a lot of commands in openstackclient, but some of them don't have a consistent command name. For example: queue_list = zaqarclient.queues.v2.cli:ListQueues queue_create = zaqarclient.queues.v2.cli:CreateQueue queue_delete = zaqarclient.queues.v2.cli:DeleteQueue

[openstack-dev] [openstackclient][zaqar]

Hi! Zaqar now have a lot of commands in openstackclient, but some of them don't have a consistent command name. For example: queue_list = zaqarclient.queues.v2.cli:ListQueues queue_create = zaqarclient.queues.v2.cli:CreateQueue queue_delete = zaqarclient.queues.v2.cli:DeleteQueue