Re: [openstack-dev] [oslo.db] [release] opportunistic tests breaking randomly

Mike Bayer wrote: On 09/21/2016 11:41 AM, Joshua Harlow wrote: I've seen something similar at https://review.openstack.org/#/c/316935/ Maybe its time we asked again why are we still using eventlet and do we need to anymore. What functionality of it are people actually taking advantage

Re: [openstack-dev] [oslo][nova] Anyone interested in writing a policy generator sphinx extension?

Andrew Laski wrote: On Wed, Sep 21, 2016, at 12:02 PM, Joshua Harlow wrote: Andrew Laski wrote: However, I have asked twice now on the review what the benefit of doing this is and haven't received a response so I'll ask here. The proposal would add additional latency to nearly every API

Re: [openstack-dev] [oslo][nova] Anyone interested in writing a policy generator sphinx extension?

Andrew Laski wrote: On Wed, Sep 21, 2016, at 03:18 PM, Joshua Harlow wrote: Andrew Laski wrote: On Wed, Sep 21, 2016, at 12:02 PM, Joshua Harlow wrote: Andrew Laski wrote: However, I have asked twice now on the review what the benefit of doing this is and haven't received a response so I'll

[openstack-dev] [oslo] PTL candidacy

Howdy folks, I'd like to run again (before passing the baton) for the PTL of Oslo, I would like to help out as much as I am able and continue pushing and making Oslo be the best it can be during the Ocata release. I have probably not done as best as I could during this Newton cycle (due to

Re: [openstack-dev] [kolla][fuel][tripleo] Reference architecture to deploy OpenStack on k8s

Flavio Percoco wrote: Greetings, I've recently started looking into the container technologies around OpenStack. More specifically, I've been looking into the tools that allow for deploying OpenStack on containers, which is what I'm the most interested in right now as part of the TripleO

[openstack-dev] [oslo] Ocata summit planning (reminder!)

Just a reminder for any folks interested in oslo and the summit, I'd be great to have any or or other ideas on: https://etherpad.openstack.org/p/ocata-oslo-summit-planning So just wanted to make sure people are aware of that URL/etherpad and have been thinking about what to add to it (I

[openstack-dev] How people handle the ML (bring your patterns/best practices)

Since I've heard this a few times over the years (the ML is to hard to read, to much volume, to hard to keep track, to hard/this or that and so-on), I thought it would make sense to start to document what folks that have been able to keep track of the ML have been doing and perhaps we can

Re: [openstack-dev] [ptl] code churn and questionable changes

oint where they are contributing at a level that materially benefits the project(s). -amrith -Original Message----- From: Joshua Harlow [mailto:harlo...@fastmail.com] Sent: Thursday, September 22, 2016 11:55 AM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.

Re: [openstack-dev] [ptl] code churn and questionable changes

Steven Dake (stdake) wrote: Folks, We want to be inviting to new contributors even if they are green. New contributors reflect on OpenStack’s growth in a positive way. The fact that a new-to-openstack contributor would make such and error doesn’t warrant such a negative response even if it

Re: [openstack-dev] A daily life of a dev in ${name_your_fav_project}

As someone that semi frequently has to reproduce gate results my current setup involves semi frequently building the infra test images locally using openstack-infra/project-config/tools/build-image.sh then booting this image on my workstation using kvm. With that I can easily run a

[openstack-dev] A daily life of a dev in ${name_your_fav_project}

Hi folks (dev and more!), I was having a conversation with some folks at godaddy around our future plans for a developer lab (where we can have various setups of networking, compute, storage...) for 'exploring' purposes (testing out a new LBAAS for example or ...) and as well as for

[openstack-dev] [oslo][all] Oslo releases for newton

Hi all, Since its that time of the cycle the following is upon us: 'Final release for non-client libraries' (Aug 22 - 26) So I just wanted to thank all those who have put a lot of hard work into the various olso libraries and denote that going forward we (as a group) should try to work on

Re: [openstack-dev] [oslo] support keymirror/valuemirror dict in olso

So question I have is how would this work in python? Any example anywhere? Reason I am asking is that in the example: > search_opts = { > > 'all_tenants': all_tenants, > > 'status': args.status, > > 'filter':filter, > > ……. > > } There is nothing really built-in to python afaik (besides

Re: [openstack-dev] [nova] ops meetup feedback

Matt Riedemann wrote: On 9/28/2016 12:10 AM, Joshua Harlow wrote: ACTION: we should make sure workarounds are advertised better ACTION: we should have some document about "when cells"? This is a difficult question to answer because "it depends." It's akin to asking &qu

Re: [openstack-dev] [nova] ops meetup feedback

ACTION: we should make sure workarounds are advertised better ACTION: we should have some document about "when cells"? This is a difficult question to answer because "it depends." It's akin to asking "how many nova-api/nova-conductor processes should I run?" Well, what hardware is being used,

Re: [openstack-dev] [nova][cinder] Schedule Instances according to Local disk based Volume?

Huang Zhiteng wrote: In eBay, we did some inhouse change to Nova so that our big data type of use case can have physical disks as ephemeral disk for this type of flavors. It works well so far. My 2 cents. Is there a published patch (or patchset) anywhere that people can look at for said

[openstack-dev] [oslo] Adding gdavoian to oslo-core

and is doing an awesome job with the various oslo concepts and helping make oslo the best it can be! Overall I think he would make a great addition to the core review team. Please respond with +1/-1. Thanks much! - Joshua Harlow [1] https://launchpad.net/~gdavoian [2] https://launchpad.net

[openstack-dev] [oslo] Adding ozamiatin to oslo-core

and is doing an awesome job with the various oslo concepts and helping make oslo the best it can be! Overall I think he would make a great addition to the core review team. Please respond with +1/-1. Thanks much! - Joshua Harlow [1] https://launchpad.net/~ozamiatin [2] https://launchpad.net

Re: [openstack-dev] [tc] open question to the candidates

gordon chung wrote: hi, as there are many candidates this TC election, i figured i'd ask a question to better understand the candidates from the usual sales pitch in self-nominations. hopefully, this will give some insights into the candidates for those who haven't voted yet. obviously, the

Re: [openstack-dev] [oslo][all] Oslo specs review weeks[Sept 27 - Oct 7]

ChangBo Guo wrote: Hi ALL, We will release Newton in Oct 6, and we have been working hard to fix bugs and prepare the release. I think it's good time to review good ideas. As we discussed in the Oslo weekly meeting [1], we would like to proposal an event of Oslo specs review weeks(Sept27 - Oct

Re: [openstack-dev] [nova][cinder] Schedule Instances according to Local disk based Volume?

Huang Zhiteng wrote: On Tue, Sep 27, 2016 at 12:00 AM, Joshua Harlow <harlo...@fastmail.com <mailto:harlo...@fastmail.com>> wrote: Huang Zhiteng wrote: On Mon, Sep 26, 2016 at 12:05 PM, Joshua Harlow <harlo...@fastmail.com <mailto:har

[openstack-dev] TC candidacy

Howdy folks, I'd like to submit myself as a candidate for the OpenStack TC, The reasons why are varied (and longer than I can list here) but it really comes to my desire to see OpenStack succeed and prosper and exist (in whatever shape and form) going forward in a way that is sustainable for

[openstack-dev] Event notification descriptors/schemas (? swagger ?)

Hi folks, At godaddy we are looking to consume the various events emitted by [nova, neutron, glance, ...] and for a while we have been having some python code to handle these and parse them and turn the ones we care about back into useful objects. At the current time though we are expanding

[openstack-dev] [kolla] How tied is kolla to matching 1:1 releases of openstack?

Hi kolla folks, As I am (and others at godaddy) are working through integrating kolla image building into our jenkins pipeline(s), Currently the pipeline is the following (taking an example of glance), # Checkout stage 1. Checkout kolla at X tag/branch 2. Checkout glance at Y tag/branch 3.

Re: [openstack-dev] [kolla] How tied is kolla to matching 1:1 releases of openstack?

Fox, Kevin M wrote: I think its kind of in the same vein as the rest of the openstack services. It might, (and probably will) work with n-1& n services in the same system. But it all depends on either: 1. The things that are actually tested or 2. Luck I've been testing the kolla-kubernetes

Re: [openstack-dev] [kolla] How tied is kolla to matching 1:1 releases of openstack?

Fox, Kevin M wrote: currently one to one on kolla version and openstack release. so 2.0.x is mitaka. 3.0.x is newton. I think if we continue forward with the helm idea it will simplify the use case too. as you can then match up a k8s package (with its templates) for a mitaka resource with

Re: [openstack-dev] [all] Embracing new languages in OpenStack

Concretely - oslo.config is important because it shapes what the config files look like. The implementation language of a particular service shouldn't change what our config files look like, yeah? Standards though exist for a reason (and ini files are pretty common across languages and such);

Re: [openstack-dev] [kolla] How tied is kolla to matching 1:1 releases of openstack?

Paul Bourke wrote: Hi Joshua, Thanks for sharing your workflow, interesting to see. To answer your question, there is a 1:1 relationship between Kolla and OpenStack releases. As Kevin outlined, you may get lucky, currently in Oracle we deploy OpenStack Mitaka with Kolla Newton and for the most

Re: [openstack-dev] [all] Embracing new languages in OpenStack

Ed Leafe wrote: On Nov 9, 2016, at 5:14 AM, Chris Dent wrote: Something that feels like it gets under-emphasised in this conversation is that change is coming whatever we do. As a community we can either move quickly and stay ahead of the change and see it as a

Re: [openstack-dev] [nova] Performance concerns over all the new notifications

Matt Riedemann wrote: There are a lot of specs up for review in ocata related to adding new versioned notifications for operations that we didn't have notifications on before, like CRUD operations on resources like flavors and server groups. We've got a lot of legacy notifications for server

Re: [openstack-dev] [nova] Performance concerns over all the new notifications

Matt Riedemann wrote: There are a lot of specs up for review in ocata related to adding new versioned notifications for operations that we didn't have notifications on before, like CRUD operations on resources like flavors and server groups. We've got a lot of legacy notifications for server

Re: [openstack-dev] Event notification descriptors/schemas (? swagger ?)

This is exactly what we are planning to do. Work is ongoing to add to_json_schema support for every VersionedObject field [1]. Then we would like to add a small tool to nova that makes it possible to generate the json schemas for the versioned notifications [2]. Meanwhile we continue to

[openstack-dev] [oslo] Reminder no meeting this week (and perhaps next)

Just a reminder for folks! No meeting this week (we can see if people want it the following week) due to traveling and summit for (most) folks. See you all soon! -Josh __ OpenStack Development Mailing List (not for

Re: [openstack-dev] [oslo] Propose support generate IPv4 and IPv6 random address( or network) for documentation(test?)

Ihar Hrachyshka wrote: In Neutron, we have a need to allocate random but unique addresses and such. For that matter, we have a concept of exclusive resources: https://github.com/openstack/neutron/tree/master/neutron/tests/common/exclusive_resources that are relying on locks and shared file based

Re: [openstack-dev] [oslo] Propose support generate IPv4 and IPv6 random address( or network) for documentation(test?)

I think doug (he can correct me if I am wrong) was more wondering the question of 'why would you want to use random data' in a test vs using known fixed data. When a test fails it can be quite hard to identify the reason if certain data that the test uses is randomized for each run.

Re: [openstack-dev] [all] indoor climbing break at summit?

Adam Young wrote: On 10/17/2016 09:53 AM, Chris Dent wrote: It turns out that summit this year will be just down the road from Chris Sharma's relatively new indoor climbing gym in Barcelona: http://www.sharmaclimbingbcn.com/ If the fun, frisson and frustration of summit sessions leaves you

[openstack-dev] [oslo] Fwd: Your draft logo & sneak peek

Thought others in oslo might want to see :) *From:* Heidi Joy Tretheway <heidi...@openstack.org> *Date:* October 21, 2016 at 10:17 AM *To:* Joshua Harlow <harlo...@gmail.com> *Subject:* Your draft logo & sneak peek Hi Josh, We're excited to show you the draft version of y

Re: [openstack-dev] [neutron] neutron-lib impact

A suggestion would also to setup something like the following: https://wiki.openstack.org/wiki/Oslo#Periodic Get the users of neutron lib being tested against the latest neutron lib (at least nightly) and seeing if they will be borked by a new neutron lib merge...

Re: [openstack-dev] [glance][oslo] oslo.log 3.17.0 use_stderr default change

Hello Glance team! Hello Tony! About a month ago the oslo team released 3.17.0 of oslo.log which contains [1] which switches the default for use_stderr from True to False. It hasn't made it into upper-constraints.txt because glance is failing[2]. There are 2 easy fixes: 1) switch the glance

Re: [openstack-dev] [kolla] Kolla-ansible is available

Jeffrey Zhang wrote: Because the role and dockerfile are tight couplings. For example, the container/Dockerfile may need an environment variable passed by ansible role. without it, the service may not work. Why do they need to be tightly coupled?

Re: [openstack-dev] [kolla] the alternative of log processing tool

Why are people/things parsing tracebacks out of log files when the following exists: http://docs.openstack.org/developer/oslo.log/api/formatters.html#oslo_log.formatters.JSONFormatter Seems like oslo.log also has a fluent formatter @

Re: [openstack-dev] [kolla] Kolla-ansible is available

Jeffrey Zhang wrote: ​​ ​​ does ​ anyone ​ ​ has an idea to leverage zuul's cross project testing[0] for kolla and kolla-ansibe gate? ​ Here is a use case: when implementing A service, we need * add dockerfile in kolla project * add ansible role in kolla-ansible project Just curious, but

Re: [openstack-dev] [kolla] Obtaining version information for Docker container

So just something that I can share about what we are putting in our images, since they are getting built from jenkins we shove in pretty much all the jenkins build information into it: $ IMG="" $ docker run $IMG cat /jenkins.json { "Project": "glance", "Project git":

[openstack-dev] [oslo] New and next-gen libraries (a BCN followup)

Just as a followup from the summit, One of the sessions (the new lib one) had a few proposals: https://etherpad.openstack.org/p/ocata-oslo-bring-ideas And I wanted to try to get clear owners for each part (there was some followup work for each); so just wanted to start this email to get the

Re: [openstack-dev] [oslo] New and next-gen libraries (a BCN followup)

Jay Faulkner wrote: On Nov 3, 2016, at 11:27 AM, Joshua Harlow<harlo...@fastmail.com> wrote: Just as a followup from the summit, One of the sessions (the new lib one) had a few proposals: https://etherpad.openstack.org/p/ocata-oslo-bring-ideas And I wanted to try to get clear

Re: [openstack-dev] [all][dev][python] constructing a deterministic representation of a python data structure

I wouldn't recommend this (the basic hash) if you actually want to do any kind of validation that the contents weren't altered. Is that the purpose? Or are you trying to ensure bits aren't flipped? If u want some level of validation that the message wasn't tampered with u probably at least

[openstack-dev] Splitting notifications from rpc (and questions + work around this)

Hi folks, There was a bunch of chatter at the summit about how there are really two different types of (oslo) messaging usage that exist in openstack and how they need not be backed by the same solution type (rabbitmq, qpid, kafka...). For those that were not at the oslo sessions:

Re: [openstack-dev] Splitting notifications from rpc (and questions + work around this)

Davanum Srinivas wrote: Josh, Kirill Bespalov put together this doc of which components will work with separate rpc and notification configurations: https://docs.google.com/document/d/1CU0KjL9iV8vut76hg9cFuWQGSJawuNq_cK7vRF_KyAA/edit?usp=sharing From my team, Oleksii Zamiatin is trying to

[openstack-dev] [jjb] Multibranch pipeline/workflow better support?

Hi folks using jenkins-job-builder, I was just looking around for better additions to the jenkins-job-builder for multibranch workflows (see https://jenkins.io/blog/2015/12/03/pipeline-as-code-with-multibranch-workflows-in-jenkins/) and stumbled into the following:

Re: [openstack-dev] [manila] Barcelona Design Summit summary

Ben Swartzlander wrote: Thanks to gouthamr for doing these writeups and for recording! We had a great turn out at the manila Fishbowl and working sessions. Important notes and Action Items are below: === Fishbowl 1: Race Conditions === Thursday

Re: [openstack-dev] Event notification descriptors/schemas (? swagger ?)

gordon chung wrote: On 10/10/16 04:48 PM, Joshua Harlow wrote: So the question started to be raised of is there a documented format/schema for the events that are being emitted from (there seems to be some at http://docs.openstack.org/developer/nova/notifications.html)? we have something

Re: [openstack-dev] Event notification descriptors/schemas (? swagger ?)

gordon chung wrote: On 11/10/16 05:38 PM, Joshua Harlow wrote: Yes yes, normalization would be nice to, though a little beyond what I am (or was) thinking of currently. Going back to how event_definitions.yaml is the best 'source' we have currently, is it possible to rip out (for now

Re: [openstack-dev] Event notification descriptors/schemas (? swagger ?)

gordon chung wrote: On 11/10/16 04:18 PM, Joshua Harlow wrote: To be productive here, would there be any problem if I (or someone I know) just split that yaml off into a new git repository, and started iterating on figuring out how to turn the yaml into something that can generate code

Re: [openstack-dev] Event notification descriptors/schemas (? swagger ?)

Chris Dent wrote: On Tue, 11 Oct 2016, Joshua Harlow wrote: Damn, that's crazy that the projects emitting events don't want to own the formats and versions (and schemas) that they emit. That is ummm, like ummm, what the, ha, words can't describe... And the fact that nothing much has changed

[openstack-dev] [oslo] To PTG or not to be that is the question!

Hi oslo folks, It appears we also need to discuss and decide on whether oslo and its associated folks want to try to go to the PTG (project team gathering) or do folks in oslo not feel such a thing would be needed? I personally could see either way being useful, but in person discussions do

Re: [openstack-dev] Event notification descriptors/schemas (? swagger ?)

gordon chung wrote: On 11/10/16 01:14 PM, Joshua Harlow wrote: Ah, right, nearly forgot about that yaml. Thanks gordon! Has there been any ideas from folks to split those 'event_definitions.yaml' into something else (a notifications schema repo?)? I'd be up for helping do that (nice to have

Re: [openstack-dev] Event notification descriptors/schemas (? swagger ?)

Julien Danjou wrote: On Tue, Oct 11 2016, Joshua Harlow wrote: Has there been any ideas from folks to split those 'event_definitions.yaml' into something else (a notifications schema repo?)? I'd be up for helping do that (nice to have would be an included ability/code-gen(?) to turn those

Re: [openstack-dev] [all] indoor climbing break at summit?

Chris Dent wrote: It turns out that summit this year will be just down the road from Chris Sharma's relatively new indoor climbing gym in Barcelona: http://www.sharmaclimbingbcn.com/ If the fun, frisson and frustration of summit sessions leaves you with the energy or need to pull down, maybe

Re: [openstack-dev] [oslo] To PTG or not to be that is the question!

Flavio Percoco wrote: On 13/10/16 13:40 -0400, Doug Hellmann wrote: Excerpts from Joshua Harlow's message of 2016-10-13 09:02:06 -0700: Hi oslo folks, It appears we also need to discuss and decide on whether oslo and its associated folks want to try to go to the PTG (project team gathering)

[openstack-dev] [kolla] Getting test-requirements.txt into project images

Hi kolla folks, I've got the following going (via jenkins): "Cloning (and stashing) required repositories" | | v "Extracting project specific patches (and skippable tests) " | |

Re: [openstack-dev] PTG? / Was (Consistent Versioned Endpoints)

Fox, Kevin M wrote: Don't want to hijack the thread too much but... when the PTG was being sold, it was a way to get the various developers in to one place and make it cheaper to go to for devs. Now it seems to be being made into a place where each of the silo's can co'exist but not talk, and

[openstack-dev] [oslo] Pike PTG idea area

Hi folks, Just wanted all of you get your thinking caps on. >>> time.sleep(2) Ok hopefully you now have it on, Then with cap *on* if you don't mind adding some of your thoughts to: https://etherpad.openstack.org/p/oslo-ptg-pike If you could keep the thoughts you are having targeted/focused

Re: [openstack-dev] [neutron] Confusion around the complexity

Sean M. Collins wrote: Joshua Harlow wrote: So I don't want to start to much of a flame-war and am really just trying to understand things that may be beyond me (so treat me nicely, ha). The basic question that I've been wondering revolves around the following kind of 'thought experiment

[openstack-dev] [neutron] Confusion around the complexity

So I don't want to start to much of a flame-war and am really just trying to understand things that may be beyond me (so treat me nicely, ha). The basic question that I've been wondering revolves around the following kind of 'thought experiment' that asks something along the lines of: """

Re: [openstack-dev] [neutron] Confusion around the complexity

Kevin Benton wrote: If you don't want users to specify network details, then use the get me a network extension or just have them boot to a public (or other pre-created) network. In your thought experiment, why is your iPhone app developer not just using a PaaS that handles instance scaling,

Re: [openstack-dev] [oslo] Should we drop kafka driver ?

Mehdi Abaakouk wrote: Hi, I think my subject is clear :) , but I will add some facts that can help to the decision: * It uses only deprecated python-kafka API [1] [2] * It's not python3 compatible [3] * We still don't have kafka testing in gate So, one year after the driver introduction, this

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

Keen, Joe wrote: I¹ll look into testing the newest version of kafka-python and see if it meets our needs. If it still isn¹t stable and performant enough what are the available options? Fix the kafka-python library or fix monasca; those seem to be the options to me :) I'd also not like to

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

Reopen them? If they weren't fixed, then seems like the right thing to try to do, and rinse and repeat until actually fixed :-P Keen, Joe wrote: > We reported > the bugs we found to the kafka-python project but they were closed once > they released a new version.

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

Damn, that's supposed to say co-installability... Lol, -Josh Joshua Harlow wrote: Keen, Joe wrote: I¹ll look into testing the newest version of kafka-python and see if it meets our needs. If it still isn¹t stable and performant enough what are the available options? Fix the kafka-python

Re: [openstack-dev] [kolla] Kolla-ansible is available

I would expect nothing less, things that are worthwhile doing are usually not just (always) easy :) Jeffrey Zhang wrote: If we can implement loose coupling, there will be optimal. But it is hard to do this. On Tue, Nov 29, 2016 at 2:50 PM, Joshua Harlow <harlo...@fastmail.com <mailto

Re: [openstack-dev] [oslo] Not running for Oslo PTL for Pike

Doug Hellmann wrote: Excerpts from Joshua Harlow's message of 2017-01-03 12:03:44 -0800: Hi Oslo folks (and others), Happy new year! After serving for about a year I think it's a good opportunity for myself to let another qualified individual run for Oslo PTL (seems common to only go for two

[openstack-dev] [oslo] Not running for Oslo PTL for Pike

Hi Oslo folks (and others), Happy new year! After serving for about a year I think it's a good opportunity for myself to let another qualified individual run for Oslo PTL (seems common to only go for two terms and hand-off to another). So I just wanted to let folks know that I will be doing

Re: [openstack-dev] ARA - Ansible Run Analysis: Would you like to help ?

Sounds neat, So this would be similar to what tower or semaphore also have (I would assume they have something very like ARA internally) but instead of providing the whole start/stop/inventory workflow this just provides the viewing component? David Moreau Simard wrote: Hi openstack-dev,

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

Jay Pipes wrote: On 03/14/2017 02:50 PM, Julien Danjou wrote: On Tue, Mar 14 2017, Jay Pipes wrote: Not tooz, because I'm not interested in a DLM nor leader election library (that's what the underlying etcd3 cluster handles for me), only a fast service liveness/healthcheck system, but it

Re: [openstack-dev] [oslo][barbican][castellan] Proposal to rename Castellan to oslo.keymanager

I'd be fine with it also, not sure it will change much, but meh, worth a shot. We are all happy loving people after all, so might as well try to help others when we can :-P -Josh Davanum Srinivas wrote: +1 from me to bring castellan under Oslo governance with folks from both oslo and

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

So just fyi, this has been talked about before (but prob in context of zookeeper or various other pluggable config backends). Some links: - https://review.openstack.org/#/c/243114/ - https://review.openstack.org/#/c/243182/ - https://blueprints.launchpad.net/oslo.config/+spec/oslo-config-db -

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

Monty Taylor wrote: On 03/14/2017 06:04 PM, Davanum Srinivas wrote: Team, So one more thing popped up again on IRC: https://etherpad.openstack.org/p/oslo.config_etcd_backend What do you think? interested in this work? Thanks, Dims PS: Between this thread and the other one about Tooz/DLM and

Re: [openstack-dev] [shade] help wanted - tons to do, not enough people

Just a question, not meant as anything bad against shade, But would effort be better spent on openstacksdk? Take the good parts of shade and just move it to openstacksdk, perhaps as a 'higher level api' available in openstacksdk? Then ansible openstack components (which I believe use shade)

Re: [openstack-dev] [oslo] Can we stop global requirements update?

Doug Hellmann wrote: Excerpts from gordon chung's message of 2017-04-20 17:12:26 +: On 20/04/17 01:32 AM, Joshua Harlow wrote: Wasn't there also some decision made in austin (?) about how we as a group stated something along the line of co-installability isn't as important as it once

Re: [openstack-dev] [Taskflow] Current state or the project ?

Robin De-Lillo wrote: Hello Guys, I'm Robin a Software developer for a VFX company based in Canada. As the company grow up, we are currently looking into redesigning our internal processes and workflows in a more nodal/graph based approach. Ideally we would like to start from an existing

Re: [openstack-dev] [oslo] Can we stop global requirements update?

Doug Hellmann wrote: Excerpts from Clark Boylan's message of 2017-04-19 08:10:43 -0700: On Wed, Apr 19, 2017, at 05:54 AM, Julien Danjou wrote: Hoy, So Gnocchi gate is all broken (agan) because it depends on "pbr" and some new release of oslo.* depends on pbr!=2.1.0. Neither Gnocchi nor

Re: [openstack-dev] [all] Some information about the Forum at the Summit in Boston

Ben Swartzlander wrote: I might be the only one who has negative feelings about the PTG/Forum split, but I suspect the foundation is suppressing negative feedback from myself and other developers so I'll express my feelings here. If there's anyone else who feels like me please reply, otherwise

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

Renat Akhmerov wrote: On 10 Mar 2017, at 06:02, Zane Bitter > wrote: On 08/03/17 11:23, David Moreau Simard wrote: The App Catalog, to me, sounds sort of like a weird message that OpenStack somehow requires applications to be

Re: [openstack-dev] [tc][appcat][murano][app-catalog] The future of the App Catalog

Clint Byrum wrote: Excerpts from Thierry Carrez's message of 2017-03-10 16:48:02 +0100: Christopher Aedo wrote: On Thu, Mar 9, 2017 at 4:08 AM, Thierry Carrez wrote: Christopher Aedo wrote: On Mon, Mar 6, 2017 at 3:26 AM, Thierry Carrez wrote:

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

Clint Byrum wrote: Excerpts from Joshua Harlow's message of 2017-03-09 21:53:58 -0800: Renat Akhmerov wrote: On 10 Mar 2017, at 06:02, Zane Bitter> wrote: On 08/03/17 11:23, David Moreau Simard wrote: The App Catalog, to me, sounds sort of like

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

gordon chung wrote: On 10/03/17 12:53 AM, Joshua Harlow wrote: I can propose what I would like for a strategy (it's not more VMs and more neutron security groups...), though if it involves (more) design by committee, count me out. I honestly believe we have to do the equivalent

[openstack-dev] What do we want to be when we grow up?

This thread is an extraction of: http://lists.openstack.org/pipermail/openstack-dev/2017-March/thread.html#113362 And is a start of someideas for what we as a group want our vision to be. I'm going to start by taking what Zane put up (see above thread) already and mutate it. * Infinite

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

Clint Byrum wrote: Excerpts from Fox, Kevin M's message of 2017-03-14 00:09:55 +: With my operator hat on, I would like to use the etcd backend, as I'm already paying the cost of maintaining etcd clusters as part of Kubernetes. Adding Zookeeper is a lot more work. It would probably

Re: [openstack-dev] What do we want to be when we grow up?

Monty Taylor wrote: On 03/10/2017 11:39 PM, Joshua Harlow wrote: * Interoperability - kept as is (though I can't really say how many public clouds there are anymore to interoperate with). There are plenty. As Dan Smith will tell you, I'm fond of telling people just how many OpenStack Public

Re: [openstack-dev] What do we want to be when we grow up?

Thierry Carrez wrote: Joshua Harlow wrote: [...] * Be opinionated; let's actually pick *specific* technologies based on well thought out decisions about what we want out of those technologies and integrate them deeply (and if we make a bad decision, that's ok, we are all grown ups and we'll

Re: [openstack-dev] Saga of servicec discovery (is it needed?)

Julien Danjou wrote: On Thu, Mar 02 2017, Joshua Harlow wrote: So before I start to go much farther on this (and start to dive into what people are doing and why the various implementations exist and proposing a cross-project solution, tooz, or etcd, or zookeeper or other...) I wanted to get

[openstack-dev] Saga of servicec discovery (is it needed?)

So this is a general start of a large discussion that is similar to the other one I started[1], and this time around I wanted to start this on the mailing instead of a spec first approach. The general question is around something I keep on noticing popping up in various projects and worry

Re: [openstack-dev] [kolla][infra] does someone cares about Jenkins? I stopped.

Marcin Juszkiewicz wrote: I am working on some improvements for Kolla. Part of that work is sending patches for review. Once patch is set for review.openstack.org there is a set of Jenkins jobs started to make sure that patch does not break already working code. And this is good thing. How it

Re: [openstack-dev] [architecture] Arch-WG, we hardly knew ye..

Sad to see it go, but I understand the reasoning about why. Back to the coal mines :-P -Josh Clint Byrum wrote: I'm going to be blunt. I'm folding the Architecture Working Group immediately following our meeting today at 2000 UTC. We'll be using the time to discuss continuity of the

[openstack-dev] Tracing (all the places)

Since I think there was another thread out there around tracing I'd thought I'd send out a few others for folks that show tracing being added to multiple other popular project (interesting to read over the proposals and such). -

Re: [openstack-dev] Tracing (all the places)

vin...@vn.fujitsu.com wrote: Hello harlowja, I'm really happy to see that you are back in this `tracing` topic [and @boris-42 (too)]. We never left, haha, but ya, I can say (and probably boris would agree) that trying to get OSprofiler started and integrated somewhat 'burned' both of us

Re: [openstack-dev] [Glare][TC] Application for inclusion of Glare in the list of official projects

Ed Leafe wrote: On Jul 10, 2017, at 5:06 AM, Mikhail Fedosin > wrote: Given all the advantages and features of Glare, I believe that it can become the successful drop-in replacement. Can you clarify this? Let’s assume I have a decent-sized

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

Out of curiosity, since I keep on hearing/reading all the tripleo discussions on how tripleo folks are apparently thinking/doing? redesigning the whole thing to use ansible + mistral + heat, or ansible + kubernetes or ansible + mistral + heat + ansible (a second time!) or ... Seeing all those

Re: [openstack-dev] [oslo] PTL nominations

Thanks much for the service (and time and effort and more) gcb!!! :) ChangBo Guo wrote: Hi oslo folks, The PTL nomination week is fast approaching [0], and as you might have guessed by the subject of this email, I am not planning to run for Queens, I'm still in the team and give some guidance

Re: [openstack-dev] [oslo][oslo.db] nominating Jay Pipes for oslo-db-core

+1 from me. -Josh ChangBo Guo wrote: +1000 2017-07-27 22:04 GMT+08:00 Doug Hellmann >: I have noticed that Jay has been very deeply involved in several recent design discussions about oslo.db, and he obviously has a great deal

<    5   6   7   8   9   10   11   >