Re: [openstack-dev] [publiccloud-wg] Serving vendor json from RFC 5785 well-known dir

On 11/5/18 3:21 AM, Mohammed Naser wrote: Sent from my iPhone On Nov 5, 2018, at 10:19 AM, Thierry Carrez wrote: Monty Taylor wrote: [...] What if we added support for serving vendor data files from the root of a primary URL as-per RFC 5785. Specifically, support deployers adding a json

Re: [openstack-dev] [publiccloud-wg] Serving vendor json from RFC 5785 well-known dir

On 11/5/18 3:21 AM, Mohammed Naser wrote: Sent from my iPhone On Nov 5, 2018, at 10:19 AM, Thierry Carrez wrote: Monty Taylor wrote: [...] What if we added support for serving vendor data files from the root of a primary URL as-per RFC 5785. Specifically, support deployers adding a json

[openstack-dev] [publiccloud-wg] Serving vendor json from RFC 5785 well-known dir

Heya, I've floated a half-baked version of this idea to a few people, but lemme try again with some new words. What if we added support for serving vendor data files from the root of a primary URL as-per RFC 5785. Specifically, support deployers adding a json file to

Re: [openstack-dev] [publiccloud-wg][sdk][osc][tc] Extracting vendor profiles from openstacksdk

On 10/29/18 10:47 AM, Doug Hellmann wrote: Monty Taylor writes: Heya, Tobias and I were chatting at OpenStack Days Nordic about the Public Cloud Working Group potentially taking over as custodians of the vendor profile information [0][1] we keep in openstacksdk (and previously in os-client

Re: [openstack-dev] Proposal for a process to keep up with Python releases

On 10/19/2018 01:58 PM, Andreas Jaeger wrote: On 19/10/2018 18.30, Clark Boylan wrote: > [...] Because zuul config is branch specific we could set up every project to use a `openstack-python3-jobs` template then define that template differently on each branch. This would mean you only have to

Re: [openstack-dev] [python3] Enabling py37 unit tests

On 10/15/2018 08:24 PM, Tim Burke wrote: On Oct 15, 2018, at 5:00 PM, Monty Taylor <mailto:mord...@inaugust.com>> wrote: If we decide as a community to shift our testing of python3 to be 3.6 - or even 3.7 - as long as we still are testing 2.7, I'd argue we're adequately covere

Re: [openstack-dev] [python3] Enabling py37 unit tests

On 10/15/2018 06:39 PM, Zane Bitter wrote: In fact, as far as we know the version we have to support in CentOS may actually be 3.5, which seems like a good reason to keep it working for long enough that we can find out for sure one way or the other. I certainly hope this is not what ends up

Re: [openstack-dev] [oslo][taskflow] Thoughts on moving taskflow out of openstack/oslo

On 10/10/2018 03:17 PM, Ben Nemec wrote: On 10/10/18 1:35 PM, Greg Hill wrote:     I'm not sure how using pull requests instead of Gerrit changesets would     help "core reviewers being pulled on to other projects"? The 2 +2 requirement works for larger projects with a lot of

Re: [openstack-dev] [oslo][taskflow] Thoughts on moving taskflow out of openstack/oslo

On 10/15/2018 05:49 AM, Stephen Finucane wrote: On Wed, 2018-10-10 at 18:51 +, Jeremy Stanley wrote: On 2018-10-10 13:35:00 -0500 (-0500), Greg Hill wrote: [...] We plan to still have a CI gatekeeper, probably Travis CI, to make sure PRs past muster before being merged, so it's not like

Re: [openstack-dev] [infra] Polygerrit

On 10/15/2018 07:08 AM, Jeremy Stanley wrote: On 2018-10-15 11:54:28 +0100 (+0100), Stephen Finucane wrote: [...] As an aside, are there any plans to enable PolyGerrit [1] in the OpenStack Gerrit instance? [...] I believe so, but first we need to upgrade to a newer Gerrit version which

[openstack-dev] [publiccloud-wg][sdk][osc][tc] Extracting vendor profiles from openstacksdk

Heya, Tobias and I were chatting at OpenStack Days Nordic about the Public Cloud Working Group potentially taking over as custodians of the vendor profile information [0][1] we keep in openstacksdk (and previously in os-client-config) I think this is a fine idea, but we've got some dancing

Re: [openstack-dev] [Openstack-sigs] [goals][tc][ptl][uc] starting goal selection for T series

On 09/26/2018 04:33 PM, Dean Troyer wrote: On Wed, Sep 26, 2018 at 3:44 PM, Matt Riedemann wrote: I started documenting the compute API gaps in OSC last release [1]. It's a big gap and needs a lot of work, even for existing CLIs (the cold/live migration CLIs in OSC are a mess, and you can't

Re: [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T series

On 09/26/2018 04:12 PM, Dean Troyer wrote: On Wed, Sep 26, 2018 at 3:01 PM, Doug Hellmann wrote: Would it be useful to have the SDK work in OSC as a prerequisite to the goal work? I would hate to have folks have to write a bunch of things twice. I don't think this is necessary, once we have

Re: [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T series

On 09/26/2018 01:55 PM, Tim Bell wrote: Doug, Thanks for raising this. I'd like to highlight the goal "Finish moving legacy python-*client CLIs to python-openstackclient" from the etherpad and propose this for a T/U series goal. To give it some context and the motivation: At CERN, we have

Re: [openstack-dev] [placement] [infra] [qa] tuning some zuul jobs from "it works" to "proper"

On 09/19/2018 09:37 AM, Colleen Murphy wrote: On Wed, Sep 19, 2018, at 4:23 PM, Monty Taylor wrote: On 09/19/2018 08:25 AM, Chris Dent wrote: also, cmurphy has been working on updating some of keystone's legacy jobs recently: https://review.openstack.org/602452 which might also

Re: [openstack-dev] [placement] [infra] [qa] tuning some zuul jobs from "it works" to "proper"

On 09/19/2018 09:23 AM, Monty Taylor wrote: On 09/19/2018 08:25 AM, Chris Dent wrote: I have a patch in progress to add some simple integration tests to placement: https://review.openstack.org/#/c/601614/ They use https://github.com/cdent/gabbi-tempest . The idea is that the method

Re: [openstack-dev] [placement] [infra] [qa] tuning some zuul jobs from "it works" to "proper"

On 09/19/2018 08:25 AM, Chris Dent wrote: I have a patch in progress to add some simple integration tests to placement:     https://review.openstack.org/#/c/601614/ They use https://github.com/cdent/gabbi-tempest . The idea is that the method for adding more tests is to simply add more yaml

Re: [openstack-dev] [glance][horizon] Issues we found when using Community Images

On 08/22/2018 04:31 PM, Andy Botting wrote: Hi all, We've recently moved to using Glance's community visibility on the Nectar Research Cloud. We had lots of public images (12255), and we found it was becoming slow to list them all and the community image visibility seems to fit our use-case

Re: [openstack-dev] [sdk] Pruning core team

On 08/10/2018 12:53 PM, Dean Troyer wrote: On Fri, Aug 10, 2018 at 7:06 AM, Monty Taylor wrote: I'd like to propose removing Brian Curtin, Clint Byrum, David Simard, and Ricardo Cruz. Thoughts/concerns? Reluctant +1, thanks guys for all the hard work! +100 to the reluctant

[openstack-dev] [sdk] Pruning core team

Hey everybody, We have some former contributors who haven't been involved in the last cycle that we should prune from the roster. They're all wonderful humans and it would be awesome to have them back if life presented them an opportunity to be involved again. I'd like to propose removing

[openstack-dev] [sdk] Propose adding Dmitry Tantsur to openstacksdk-core

Hey everybody, I'd like to propose Dmitry Tantsur (dtantsur) as a new openstacksdk core team member. He's been diving in to some of the hard bits, such as dealing with microversions, and has a good grasp of the resource/proxy layer. His reviews have been super useful broadly, and he's also

Re: [openstack-dev] PTG Denver Horns

On 08/08/2018 09:12 AM, Jeremy Stanley wrote: On 2018-08-08 06:51:27 -0500 (-0500), David Medberry wrote: So basically, we have added "sl" to osc. Duly noted. (FWIW, I frequently use "sl" as a demo of how "live" a VM is during live migration. The train "stutters" a bit during the cutover.)

[openstack-dev] [requirements][sdk][release] FFE request for os-service-types

Heya! I'd like to request a FFE for os-service-types to release 1.3.0. The main change is the inclusion of the qinling data from service-types-authority, as well as the addition of an alias for magnum. There are also two minor changes to the python portion - a parameter was added to

Re: [openstack-dev] [cinder][api] strict schema validation and microversioning

On 08/07/2018 05:03 PM, Akihiro Motoki wrote: Hi Cinder and API-SIG folks, During reviewing a horizon bug [0], I noticed the behavior of Cinder API 3.0 was changed. Cinder introduced more strict schema validation for creating/updating volume encryption type during Rocky and a new micro

[openstack-dev] [requirements][release] FFE for openstacksdk 0.17.2

Hey all, I'd like to request an FFE to release 0.17.2 of openstacksdk from stable/rocky. Infra discovered an issue that affects the production nodepool related to the multi-threaded TaskManager and exception propagation. When it gets triggered, we lose an entire cloud of capacity (whoops)

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On 08/01/2018 08:17 AM, Andrey Kurilin wrote: ср, 1 авг. 2018 г. в 15:37, Monty Taylor <mailto:mord...@inaugust.com>>: On 08/01/2018 06:22 AM, Luigi Toscano wrote: > On Wednesday, 1 August 2018 12:49:13 CEST Andrey Kurilin wrote: >> Hey Ian and stackers!

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On 08/01/2018 08:38 AM, Jeremy Stanley wrote: On 2018-08-01 09:58:48 -0300 (-0300), Rafael Weingärtner wrote: What about Rocket chat instead of Slack? It is open source. https://github.com/RocketChat/Rocket.Chat Monty, what kind of evaluation would you guys need? I might be able to help.

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On 08/01/2018 12:45 AM, Ian Wienand wrote: Hello, It seems freenode is currently receiving a lot of unsolicited traffic across all channels.  The freenode team are aware [1] and doing their best. There are not really a lot of options.  We can set "+r" on channels which means only nickserv

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On 08/01/2018 07:44 AM, Doug Hellmann wrote: Excerpts from Andrey Kurilin's message of 2018-08-01 15:21:37 +0300: ср, 1 авг. 2018 г. в 14:11, Dmitry Tantsur : On 08/01/2018 12:49 PM, Andrey Kurilin wrote: Hey Ian and stackers! ср, 1 авг. 2018 г. в 8:45, Ian Wienand

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On 08/01/2018 06:22 AM, Luigi Toscano wrote: On Wednesday, 1 August 2018 12:49:13 CEST Andrey Kurilin wrote: Hey Ian and stackers! ср, 1 авг. 2018 г. в 8:45, Ian Wienand : Hello, It seems freenode is currently receiving a lot of unsolicited traffic across all channels. The freenode team are

[openstack-dev] [requirements][release] FFE for openstacksdk 0.17.1

Heya, I'd like to request a FFE to release 0.17.1 of openstacksdk from stable/rocky. The current rocky release, 0.17.0, added a feature (being able to pass data directly to an object upload rather that requiring a file or file-like object) - but it is broken if you pass an interator because

Re: [openstack-dev] [all][tc][release][election][adjutant] Welcome Adjutant as an official project!

On 07/17/2018 08:19 PM, Adrian Turjak wrote: Thanks! As the current project lead for Adjutant I welcome the news, and while I know it wasn't an easy process would like to thank everyone involved in the voting. All the feedback (good and bad) will be taken on board to make the service as suited

[openstack-dev] [sdk] PTL Candidacy for the Stein cycle

Hi everybody! I'd like to run for PTL of OpenStackSDK again. This last cycle was great. os-client-config is now just a thin wrapper around openstacksdk. shade still has a bunch of code, but the shade OpenStackCloud object is a subclass of openstack.connection.Connection, so we're in good

Re: [openstack-dev] [requirements][infra] Maintaining constraints for several python versions

On 07/12/2018 11:05 AM, Matthew Thode wrote: On 18-07-12 13:52:56, Jeremy Stanley wrote: On 2018-07-12 06:37:52 -0700 (-0700), Clark Boylan wrote: [...] I think most of the problems with Fedora stability are around bringing up a new Fedora every 6 months or so. They tend to change sufficiently

Re: [openstack-dev] [requirements][infra] Maintaining constraints for several python versions

On 07/12/2018 08:37 AM, Clark Boylan wrote: On Wed, Jul 11, 2018, at 9:34 PM, Tony Breeds wrote: Hi Folks, We have a pit of a problem in openstack/requirements and I'd liek to chat about it. Currently when we generate constraints we create a venv for each (system) python supplied on the

Re: [openstack-dev] swift containers.

On 07/09/2018 02:46 AM, jayshankar nair wrote: Hi, I am unable to create containers in object store. "Unable to get the Swift service info". "Unable to get the swift container listing". My horizon is running on 192.168.0.19. My swift is running on 192.168.0.12(how can i change it). I

Re: [openstack-dev] [Openstack] [nova][api] Novaclient redirect endpoint https into http

On 07/05/2018 01:55 PM, melanie witt wrote: +openstack-dev@ On Wed, 4 Jul 2018 14:50:26 +, Bogdan Katynski wrote: But, I can not use nova command, endpoint nova have been redirected from https to http. Here:http://prntscr.com/k2e8s6  (command: nova –insecure service list) First of all, it

Re: [openstack-dev] [osc][python-openstackclient] osc-included image signing

On 06/29/2018 05:38 AM, Josephine Seifert wrote: Hello Dean, thanks for your code comments so far. Looking at the changes you have to cursive, if that is all you need from it those bits could easily go somewhere in osc or osc-lib if you don't also need them elsewhere. There lies the problem,

Re: [openstack-dev] [openstackclient][openstacksdk] why does openstackclient rely on openstacksdk for get a network client

On 06/20/2018 10:23 AM, Dean Troyer wrote: On Tue, Jun 19, 2018 at 9:42 PM, zijian1...@163.com wrote: Thks for replying, just want to confirm, you mentioned "We have intended to migrate everything to use OpenStackSDK", the current use of python-*client is: 1. OSC 2. all services that need to

Re: [openstack-dev] [openstackclient][openstacksdk] why does openstackclient rely on openstacksdk for get a network client

On 06/19/2018 03:51 PM, Dean Troyer wrote: On Tue, Jun 19, 2018 at 11:15 AM, 李健 wrote: So, my question is, why does the network service not use the python2-neutronclient to get the client like other core projects, but instead uses another separate project(openstacksdk)? There were multiple

Re: [openstack-dev] [tripleo] tripleo gate is blocked - please read

On 06/13/2018 07:50 PM, Emilien Macchi wrote: TL;DR: gate queue was 25h+, we put all patches from gate on standby, do not restore/recheck until further announcement. We recently enabled the containerized undercloud for multinode jobs and we believe this was a bit premature as the container

Re: [openstack-dev] [keystone] keystoneauth version auto discovery for internal endpoints in queens

On 05/11/2018 03:37 PM, Vlad Gusev wrote: Hello. We faced a bug in keystoneauth, which haven't existed before Queens. Sorry about that. In our OpenStack deployments we use urls like http://controller:5000/v3 for internal and admin endpoints and urls like https://api.example.org/identity/v3

Re: [openstack-dev] [sdk] issues with using OpenStack SDK Python client

On 05/04/2018 01:34 PM, gerard.d...@wipro.com wrote: Hi everybody, As a bit of a novice, I'm trying to use OpenStack SDK 0.13 in an OPNFV/ONAP project (Auto). Yay! Welcome. I'm able to use the compute and network proxies, but have problems with the identity proxy, so I can't create

[openstack-dev] [requirements][horizon][neutron] plugins depending on services

Hi everybody, We've been working on navigating through from an interesting situation over the past few months, but there isn't a top-level overview of what's going on with it. That's my bad - I've been telling AJaeger I was going to send an email out for a while. projects with test

[openstack-dev] [sdk][osc][openstackclient] Migration to storyboard complete

Hey everybody, The migration of the openstacksdk and python-openstackclient repositories to storyboard has been completed. Each of the repos owned by those teams has been migrated, and project groups now also exist for each. python-openstackclient group:

Re: [openstack-dev] [Nova][Deployers] Optional, platform specific, dependancies in requirements.txt

On 04/12/2018 11:27 AM, Clark Boylan wrote: On Wed, Apr 11, 2018, at 5:45 PM, Matt Riedemann wrote: I also seem to remember that [extras] was less than user-friendly for some reason, but maybe that was just because of how our CI jobs are setup? Or I'm just making that up. I know it's pretty

Re: [openstack-dev] PBR and Pipfile

On 04/08/2018 04:10 AM, Gaetan wrote: Hello OpenStack dev community, I am currently working on the support of Pipfile for PBR ([1]), and I also follow actively the work on pipenv, which is now in officially supported by PyPA. Awesome - welcome! This is a fun topic ... There have been

Re: [openstack-dev] [infra][qa][requirements] Pip 10 is on the way

On 04/05/2018 07:39 PM, Paul Belanger wrote: On Thu, Apr 05, 2018 at 01:27:13PM -0700, Clark Boylan wrote: On Mon, Apr 2, 2018, at 9:13 AM, Clark Boylan wrote: On Mon, Apr 2, 2018, at 8:06 AM, Matthew Thode wrote: On 18-03-31 15:00:27, Jeremy Stanley wrote: According to a notice[1] posted to

[openstack-dev] [sdk] Repo rename complete

The openstack/python-openstacksdk repo has been renamed to openstack/openstacksdk. The following patch: https://review.openstack.org/#/c/555875 Updates the .gitreview file (and other things) to point at the new repo. You'll want to update your local git remotes to pull from and submit to

Re: [openstack-dev] Following the new PTI for document build, broken local builds

On 03/22/2018 05:43 AM, Stephen Finucane wrote: On Wed, 2018-03-21 at 09:57 -0500, Sean McGinnis wrote: On Wed, Mar 21, 2018 at 10:49:02AM +, Stephen Finucane wrote: tl;dr: Make sure you stop using pbr's autodoc feature before converting them to the new PTI for docs. [snip] I've gone

Re: [openstack-dev] [sdk] git repo rename and storyboard migration

On 03/22/2018 02:51 AM, Jens Harbott wrote: 2018-03-21 21:44 GMT+01:00 Monty Taylor <mord...@inaugust.com>: Hey everybody! This upcoming Friday we're scheduled to complete the transition from python-openstacksdk to openstacksdk. This was started a while back (Tue Jun 16 12:05:3

Re: [openstack-dev] Is openstacksdk backward compatible?

On 03/22/2018 05:14 AM, zijian1...@163.com wrote: Hello, everyone The openstack version I deployed was Newton,  now I am ready to use openstacksdk for development, *, *I noticed that the latest *openstacksdk *version is 0.12

Re: [openstack-dev] [devstack] stable/queens: How to configure devstack to use openstacksdk===0.11.3 and os-service-types===1.1.0

On 03/16/2018 09:29 AM, Kwan, Louie wrote: In the stable/queens branch, since openstacksdk0.11.3 and os-service-types1.1.0 are described in openstack's upper-constraints.txt, https://github.com/openstack/requirements/blob/stable/queens/upper-constraints.txt#L411

[openstack-dev] [sdk] git repo rename and storyboard migration

Hey everybody! This upcoming Friday we're scheduled to complete the transition from python-openstacksdk to openstacksdk. This was started a while back (Tue Jun 16 12:05:38 2015 to be exact) by changing the name of what gets published to PyPI. Renaming the repo is to get those two back inline

Re: [openstack-dev] [tripleo] Recap of Python 3 testing session at PTG

On 03/17/2018 03:34 AM, Emilien Macchi wrote: That way, we'll be able to have some early testing on python3-only environments (thanks containers!) without changing the host OS. All hail our new python3-only overlords!!!

[openstack-dev] [sdk] Cleaning up openstacksdk core team

Hey all, A bunch of stuff has changed in SDK recently, and a few of the historical sdk core folks have also not been around. I'd like to propose removing the following people from the core team: Everett Towes Jesse Noller Richard Theis Terry Howe They're all fantastic humans but

Re: [openstack-dev] [neutron][sdk] Proposal to migrate neutronclient python bindings to OpenStack SDK

On 02/26/2018 10:55 AM, Rabi Mishra wrote: On Mon, Feb 26, 2018 at 3:44 PM, Monty Taylor <mord...@inaugust.com <mailto:mord...@inaugust.com>> wrote: On 02/26/2018 09:57 AM, Akihiro Motoki wrote: Hi neutron and openstacksdk team, This mail proposes to chan

[openstack-dev] [sdk] Nominating Adrian Turjak for core

Hey everybody, I'd like to nominate Adrian Turjak (adriant) for openstacksdk-core. He's an Operator/End User and brings *excellent* deep/strange/edge-condition bugs. He also has a great understanding of the mechanics between Resource/Proxy objects and is super helpful in verifying fixes work

Re: [openstack-dev] [neutron][sdk] Proposal to migrate neutronclient python bindings to OpenStack SDK

On 02/26/2018 09:57 AM, Akihiro Motoki wrote: Hi neutron and openstacksdk team, This mail proposes to change the first priority of neutron-related python binding to OpenStack SDK rather than neutronclient python bindings. I think it is time to start this as OpenStack SDK became a official

Re: [openstack-dev] [docs] About the convention to use '.' instead of 'source'.

On 02/17/2018 03:03 PM, Jeremy Stanley wrote: On 2018-02-17 13:47:02 -0500 (-0500), Hongbin Lu wrote: [...] If anyone can clarify the rationals of this convention, it will be really helpful. [...] There's a trade-off here: while `.` is standardized in POSIX sh (under Utilities, Dot in the

Re: [openstack-dev] [sdk][release][requirements] FFE request for openstacksdk 0.11.3

On 02/04/2018 01:35 PM, Matthew Thode wrote: On 18-02-04 09:32:25, Monty Taylor wrote: Hi! I'd like to request another FFE to fix several neutron commands in python-openstackclient for queens and also to unbreak python-openstackclient's gate. The release proposal patch is here: https

[openstack-dev] [sdk][release][requirements] FFE request for openstacksdk 0.11.3

Hi! I'd like to request another FFE to fix several neutron commands in python-openstackclient for queens and also to unbreak python-openstackclient's gate. The release proposal patch is here: https://review.openstack.org/540657 The issue at hand was: The osc-functional-devstack-tips job,

Re: [openstack-dev] Remembering Shawn Pearce (fwd)

On 02/02/2018 09:52 AM, Adam Spiers wrote: Dear Stackers, Since git and Gerrit are at the heart of our development process, I am passing on this very sad news from the git / Gerrit communities that Shawn Pearce has passed away after an aggressive lung cancer. Shawn was founder of Gerrit / JGit

Re: [openstack-dev] [requirements] FFE for delayed libraries

On 02/01/2018 01:47 PM, Matthew Thode wrote: On 18-02-01 13:44:19, Sean McGinnis wrote: Due to gate issues and other delays, there's quite a handful of libs that were not released in time for the requirements freeze. We now believe we've gotten all libraries processed for the final Queens

[openstack-dev] [sdk][ptl] PTL Candidacy for Rocky

Hi everybody! I'd like to run for PTL of OpenStackSDK again This last cycle was pretty exciting. We merged the shade and openstacksdk projects into a single team. We shifted os-client-config to that team as well. We merged the code from shade and os-client-config into openstacksdk, and then

Re: [openstack-dev] [legal-discuss] [tc] [all] TC Report 18-05

On 01/30/2018 01:05 PM, Monty Taylor wrote: On 01/30/2018 12:53 PM, Graham Hayes wrote: On 30/01/18 18:34, Chris Dent wrote: ## Today's Board Meeting I attended [today's Board Meeting](https://wiki.openstack.org/wiki/Governance/Foundation/30Jan2018BoardMeeting) but it seems

Re: [openstack-dev] [infra][all] New Zuul Depends-On syntax

On 01/24/2018 02:25 PM, David Shrewsbury wrote: This is a (the?) killer feature. On Wed, Jan 24, 2018 at 11:33 AM, James E. Blair > wrote: Hi, We recently introduced a new URL-based syntax for Depends-On: footers in commit

Re: [openstack-dev] [sdk][masakari][tricircle] Inclusion of SDK classes in openstacksdk tree

openstacksdk tree? Yes - if you want to, you are welcome to put them there. Best Regards Chaoyi Huang (joehuang) From: Monty Taylor [mord...@inaugust.com] Sent: 21 January 2018 1:22 To: OpenStack Development Mailing List (not for usage questions) Subject

Re: [openstack-dev] [horizon][packaging] django-openstack-auth retirement

On 01/24/2018 08:25 AM, Jeremy Stanley wrote: On 2018-01-23 23:19:59 +0900 (+0900), Akihiro Motoki wrote: [...] Horizon usually does not publish its releases to PyPI, so I think what we can do is to document it. P.S. The only exceptions on PyPI horizon are 12.0.2 and 2012.2 releases. 12.0.2

[openstack-dev] [sdk][masakari][tricircle] Inclusion of SDK classes in openstacksdk tree

Hey everybody, Wanted to send a quick note to let people know that all OpenStack services are more than welcome to put any openstacksdk proxy and resource classes they have directly into the openstacksdk tree. Looking through codesearch.openstack.org, masakariclient and tricircle each have

[openstack-dev] [tc][masakari][api] masakari service-type, docs, api-ref and releasenotes

Hey everybody, I noticed today while preparing patches to projects that are using openstacksdk that masakari is not listed in service-types-authority. [0] I pushed up a patch to fix that [1] as well as to add api-ref, docs and releasenotes jobs to the masakari repo so that each of those will

Re: [openstack-dev] [ceilometer] Retiring ceilometerclient

On 01/10/2018 05:44 PM, Doug Hellmann wrote: Excerpts from Monty Taylor's message of 2018-01-10 17:40:28 -0600: On 01/10/2018 04:10 PM, Jon Schlueter wrote: On Thu, Nov 23, 2017 at 4:12 PM, gordon chung wrote: On 2017-11-22 04:18 AM, Julien Danjou wrote: Hi, Now that the

Re: [openstack-dev] [ceilometer] Retiring ceilometerclient

On 01/10/2018 04:10 PM, Jon Schlueter wrote: On Thu, Nov 23, 2017 at 4:12 PM, gordon chung wrote: On 2017-11-22 04:18 AM, Julien Danjou wrote: Hi, Now that the Ceilometer API is gone, we really don't need ceilometerclient anymore. I've proposed a set of patches to retire it:

[openstack-dev] [all] New documentation PTI jobs are live - some fallout possible

Hey everybody, For several weeks we've been working on implementing updates to the Sphinx documentation jobs to use the new PTI. [0][1][2][3][4] tl;dr * we're no longer using tox for building sphinx docs * if your doc build jobs break all of a sudden, ping us in #openstack-infra * there is

Re: [openstack-dev] [python-openstacksdk][shade] New cores proposed for shade/sdk

On 11/30/2017 10:00 AM, Dean Troyer wrote: On Thu, Nov 30, 2017 at 8:00 AM, Monty Taylor <mord...@inaugust.com> wrote: So let's add them to the core team, yeah? +1 dt Hearing no dissent I've added both. Welcome

Re: [openstack-dev] [sahara] [api] [sdks] [keystone] Sahara APIv2: service discovery

On 12/01/2017 05:04 AM, Luigi Toscano wrote: On Friday, 1 December 2017 01:34:36 CET Monty Taylor wrote: First and most importantly you need to update python-saharaclient to make sure it can handle it an unversioned endpoint in the catalog (by doing discovery) - and that if it finds

Re: [openstack-dev] [sahara] [api] [sdks] [keystone] Sahara APIv2: service discovery

On 11/30/2017 03:07 PM, Jeremy Freudberg wrote: Hi all, In the Sahara world, we are getting ready to expose our experimental v2 API to real users and not just curious devs. Therefore we need to start thinking about service/version discovery of this new API. \o/ Earlier this year, the

Re: [openstack-dev] [E] Re: nova diagnostics in client library/SDK

On 11/29/2017 12:49 PM, Gordon, Kent S wrote: On Tue, Nov 28, 2017 at 2:15 PM, Monty Taylor <mord...@inaugust.com <mailto:mord...@inaugust.com>> wrote: On 11/03/2017 11:31 AM, Gordon, Kent S wrote: Do any of the python client libraries implement the nova dia

[openstack-dev] [python-openstacksdk][shade] New cores proposed for shade/sdk

Hey everybody, I'd like to propose adding Slawek Kaplonski (slaweq) and Rosario Di Somma (rods) to the shade/sdk core team. While they are clearly two different humans, I'm going to speak of them collectively since what I have to say about each of them is largely the same. They were both

Re: [openstack-dev] [oaktree] Follow up to Multi-cloud Management in OpenStack Summit session

ack backend drivers for oaktree in a way that does not make life worse for the OpenStack users - then why not. Monty Taylor wrote: Hey everybody! https://etherpad.openstack.org/p/sydney-forum-multi-cloud-management I've CC'd everyone who listed interest directly, just in case you're not alre

Re: [openstack-dev] [oaktree] Follow up to Multi-cloud Management in OpenStack Summit session

or what exists and not a local data store (two phase commits across WAN links anybody?) > Perhaps a decent idea to start some kind of etherpad to start listing > these questions (and at least think about them a wee bit) down? Sounds great! > Monty Taylor wrote: >> Hey everybody! >

[openstack-dev] [oaktree] Follow up to Multi-cloud Management in OpenStack Summit session

Hey everybody! https://etherpad.openstack.org/p/sydney-forum-multi-cloud-management I've CC'd everyone who listed interest directly, just in case you're not already on the openstack-dev list. If you aren't, and you are in fact interested in this topic, please subscribe and make sure to watch

Re: [openstack-dev] nova diagnostics in client library/SDK

On 11/03/2017 11:31 AM, Gordon, Kent S wrote: Do any of the python client libraries implement the nova diagnostics API? https://wiki.openstack.org/wiki/Nova_VM_Diagnostics Not to my knowledge, no. However, adding support for it should be easy enough to accomplish and would be a welcome

[openstack-dev] [shade][sdk] Retiring #openstack-shade IRC channel - come join #openstack-sdks

With the adoption of python-openstacksdk into the shade team and the merging of the shade code into the python-openstacksdk codebase, having both an #openstack-shade and an #openstack-sdks channel is more confusing than helpful. [0] To solve that, I'd like to shift shade-related development

[openstack-dev] [all] Changes to releasenotes and docs build jobs

Hey everybody! Following recent changes [0] in the PTI [1][2] we're rolling out some changes to the build-openstack-releasenotes and build-openstack-sphinx-docs jobs. If you see patches with the topic 'updated-pti' - they are in service of this. The most important thing to be aware of is

Re: [openstack-dev] [all][release][neutron][horizon] Publishing server projects to PyPI

On 11/17/2017 10:51 AM, Andreas Jaeger wrote: On 2017-11-17 17:27, Monty Taylor wrote: Hey everybody! tl;dr - We'd like to start publishing the server projects to PyPI Background == The move to Zuul v3 has highlighted an odd situation we're in with some of our projects, most notably

[openstack-dev] [all][release][neutron][horizon] Publishing server projects to PyPI

Hey everybody! tl;dr - We'd like to start publishing the server projects to PyPI Background == The move to Zuul v3 has highlighted an odd situation we're in with some of our projects, most notably neutron and horizon plugin projects. Namely, those plugins need to depend on neutron

[openstack-dev] [python-openstacksdk] Existential question about Service/ServiceFilter

Hey everybody, In the shade stack, one of the main changes is making Proxy a subclass of keystoneauth1.adapter.Adapter. This means we don't have to carry endpoint_override dicts around to pass to rest calls on the session, but instead let ksa handle that for us inside the Adapter structure.

Re: [openstack-dev] [python-openstacksdk][shade] Reviewing the merge-shade patches

On 11/13/2017 09:06 AM, David Shrewsbury wrote: Hi! On Mon, Nov 13, 2017 at 9:54 AM, Monty Taylor <mord...@inaugust.com <mailto:mord...@inaugust.com>> wrote: Hey everybody, You may have noticed a giant patch series up: https://review.openstack.org/#/q/topic

[openstack-dev] [python-openstacksdk][shade] Reviewing the merge-shade patches

Hey everybody, You may have noticed a giant patch series up: https://review.openstack.org/#/q/topic:merge-shade It's a big beastie, so I thought a synopsis of what's going would be useful. Also, there's a pile of patches towards the end that we want to squash before landing but which have

[openstack-dev] [all] Zuul v3 Rollout Update - devstack-gate issues edition

But, Mousie, thou art no thy-lane, In proving foresight may be vain; The best-laid schemes o' mice an' men Gang aft agley, An' lea'e us nought but grief an' pain, For promis'd joy! - To a Mouse, Rabbie Burns, 1785 We have awoken this fine morning to find ourselves having two

[openstack-dev] [tc][election] TC non-candidacy

Hey everybody! I have decided not to seek reelection for the TC. I have had the honor and privilege of serving you on the TC and it's predecessor the PPB since the fall of 2011 (with one six month absence that I blame on Jay Pipes) There are a wealth of amazing people running for the TC

[openstack-dev] [all] IMPORTANT Information about Zuul v3 rollout, the sequel

Hey everybody, As noted by fungi yesterday: http://lists.openstack.org/pipermail/openstack-dev/2017-October/123337.html We are planning to roll Zuul v3 out to take over the gate again tomorrow. Since then it has become evident that what people should be doing about that right now is

Re: [openstack-dev] [tc][docs][release] Updating the PTI for docs and tarballs

On 09/30/2017 10:40 AM, Doug Hellmann wrote: Excerpts from Monty Taylor's message of 2017-09-30 10:20:08 -0500: Hey everybody, Oh goodie, I can hear you say, let's definitely spend some time bikeshedding about specific command invocations related to building docs and tarballs!!! tl;dr I want

Re: [openstack-dev] [infra][docs][i18n][ptls] PDFs for project-specific docs with unified doc builds

On 09/25/2017 08:50 AM, Doug Hellmann wrote: [Topic tags added to subject line] Excerpts from Ian Y. Choi's message of 2017-09-22 07:29:23 +0900: Hello, "Build PDF docs from rst-based guide documents" [1] was implemented in Ocata cycle, and I have heard that there were a small conversation at

Re: [openstack-dev] [keystone][zuul] A Sad Farewell

On 10/03/2017 11:17 AM, Dean Troyer wrote: On Mon, Oct 2, 2017 at 9:13 PM, Jamie Lennox wrote: I'm really sad to announce that I'll be leaving the OpenStack community (at least for a while), I've accepted a new position unrelated to OpenStack that'll begin in a few

[openstack-dev] [all] Important information for people with in-repo Zuul v3 config

Hi everybody, The partial rollback of Zuulv3 is in place now. Zuulv2 is acting as your gate keeper once again. The status page for Zuulv2 can be found at http://status.openstack.org/zuul and Zuulv3 can be found at http://zuulv3.openstack.org. With the partial rollback of v3, we've left the

[openstack-dev] [all] Zuul v3 Status - and Rollback Information

Hey everybody! Thank you all for your patience over the last week as we've worked through the v3 rollout.  While we anticipated some problems, we've run into a number of unexpected issues, some of which will take some time to resolve.  It has become unreasonable to continue in our current

[openstack-dev] [tc][docs][release] Updating the PTI for docs and tarballs

Hey everybody, Oh goodie, I can hear you say, let's definitely spend some time bikeshedding about specific command invocations related to building docs and tarballs!!! tl;dr I want to change the PTI for docs and tarball building to be less OpenStack-specific The Problem === As we

[openstack-dev] [all] Update on Zuul v3 Migration - and what to do about issues

Hey everybody! tl;dr - If you're having issues with your jobs, check the FAQ, this email and followups on this thread for mentions of them. If it's an issue with your job and you can spot it (bad config) just submit a patch with topic 'zuulv3'. If it's bigger/weirder/you don't know - we'd

  1   2   3   4   5   6   7   8   >