Re: [openstack-dev] [gnocchi] Running tests

On Tue, May 23 2017, Andres Alvarez wrote: > Hello everyone > > I am having a hard time in understanding the correct way to run the tests > in Gnocchi. I have already read about tox and testr, but it seems I still > can't get to run the tests. tox -e py27-postgresql-file That'll run the test wit

Re: [openstack-dev] [heat] [devstack] [infra] heat api services with uwsgi

On Tue, May 23, 2017 at 11:18 AM, Juan Antonio Osorio wrote: > > > On Tue, May 23, 2017 at 8:23 AM, Rabi Mishra wrote: > >> Hi All, >> >> As per the updated community goal[1] for api deployment with wsgi, we've >> to transition to use uwsgi rather than mod_wsgi at the gate. It also seems >> mod

Re: [openstack-dev] [heat] [devstack] [infra] heat api services with uwsgi

On Tue, May 23, 2017 at 8:23 AM, Rabi Mishra wrote: > Hi All, > > As per the updated community goal[1] for api deployment with wsgi, we've > to transition to use uwsgi rather than mod_wsgi at the gate. It also seems > mod_wsgi support would be removed from devstack in Queens. > What do you mean

[openstack-dev] [gnocchi] Running tests

Hello everyone I am having a hard time in understanding the correct way to run the tests in Gnocchi. I have already read about tox and testr, but it seems I still can't get to run the tests. Would really appreciate if someone could explain the steps necessary to get all tests running. ___

[openstack-dev] [heat] [devstack] [infra] heat api services with uwsgi

Hi All, As per the updated community goal[1] for api deployment with wsgi, we've to transition to use uwsgi rather than mod_wsgi at the gate. It also seems mod_wsgi support would be removed from devstack in Queens. I've been working on a patch[2] for the transition and encountered a few issues a

[openstack-dev] [refstack] No RefStack IRC meeting on May 23, 2017

Hi Everyone, There will be no RefStack IRC meeting on May 23, 2017. We will resume meeting on May 30, 2017. Catherine Diep __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...

Re: [openstack-dev] [nova][vlan trunking] Guest networking configuration for vlan trunk

I think we just need someone to volunteer to do the work to expose it as metadata to the VM in Nova. On May 22, 2017 1:27 PM, "Robert Li (baoli)" wrote: > Hi Levi, > > > > Thanks for the info. I noticed that support in the nova code, but was > wondering why something similar is not available for

Re: [openstack-dev] uWSGI help for Congress

On 22/05/17 05:48 PM, Eric K wrote: > If someone out there knows uWSGI and has a couple spare cycles to help > Congress project, we'd super appreciate it. > > The regular contributors to Congress don't have experience with uWSGI > and could definitely use some help getting started with this goal.

[openstack-dev] [nova] Supporting volume_type when booting from volume

Just wanted to point out that someone else requested this again today: https://review.openstack.org/#/c/466595/ 30 seconds going through launchpad for old blueprints found at least 4 others: https://blueprints.launchpad.net/nova/+spec/vol-type-with-blank-vol https://blueprints.launchpad.net/

Re: [openstack-dev] [telemetry] Room during the next PTG

On 22/05/17 02:42 AM, Hanxi Liu wrote: > > +1. I always thought it's a pity that we have no weekly meeting. The > whole Telemetry team need communications. > PTG room discussion can not only provide a good chance to communicate > within team but also attract more new people to contribute. > In my

Re: [openstack-dev] [tc] revised Postgresql deprecation patch for governance

On 5/22/2017 10:58 AM, Sean Dague wrote: I think these are actually compatible concerns. The current proposal to me actually tries to address A1 & B1, with a hint about why A2 is valuable and we would want to do that. It feels like there would be a valuable follow on in which A2 & B2 were addres

[openstack-dev] [Forum] Boston recap: skip-level upgrading session

Hi all, I want to recap the Boston Forum session "Skip-level upgrading - jumping ahead to catch up" which I and Andy co-moderated. We had a good number of attendees from both operators and developers in the room and had positive discussion. We agreed to bring this topic on dev ML for further

Re: [openstack-dev] Is the pendulum swinging on PaaS layers?

On 05/22/2017 12:01 PM, Zane Bitter wrote: On 19/05/17 17:59, Matt Riedemann wrote: I'm not really sure what you're referring to here with 'update' and [1]. Can you expand on that? I know it's a bit of a tangent. If the user does a stack update that changes the network from 'auto' to 'none',

[openstack-dev] [release] Issues with reno

I think Doug and I have talked about this before, but it came up again tonight. There seems to be an issue where release notes for the current series don't show up in the published release notes, but unreleased things do. For example, the python-novaclient release notes: https://docs.opensta

Re: [openstack-dev] [Openstack-dev][Tacker] Not able to run user_data commands on my instance

Hi, Vishnu, Openwrt mgmt driver is different with user_data shell cmd. User_data shell cmds are injected into vm instance during vm's boot stage (cloud-init script), via metadata service. Cloud-init script is required in image. While mgmt_driver is used to configure vm after booting su

Re: [openstack-dev] Is the pendulum swinging on PaaS layers?

On 05/21/2017 03:56 PM, Monty Taylor wrote: On 05/19/2017 05:10 PM, Matt Riedemann wrote: On 5/19/2017 3:35 PM, Monty Taylor wrote: Heck - while I'm on floating ips ... if you have some pre-existing floating ips and you want to boot servers on them and you want to do that in parallel, you can't

[openstack-dev] [Forum] Boston forum etherpad ##hashtag

Hi all, In response to the previous recommendation on using the ##hashtag [1,2,3,4] at OpenStack Forum, the initial data is ready and is tentatively published at this repo [5]. In the repo [5], you can see a list of ##hashtag that were used at Boston Forum sessions, with a link to the relevan

[openstack-dev] [glance] Stepping Down

Hello Glancers, Due to a change in my job role with my employer, I unfortunately do not have the bandwidth to contribute to Glance in the capacity of a Core Contributor. I hence would have to step down from my role of a Core Contibutor in Glance. I had a great experience working in OpenStack Gla

Re: [openstack-dev] [Openstack-dev][Tacker] Not able to run user_data commands on my instance

Hi Vishnu, Just to rule out any underlying metadata service issue, can you verify if a simple heat stack with user_data [1] works fine first? Also, the actual TOSCA -> HOT translated template will be available in tacker.log. Try creating a heat stack using that HOT template and make sure the inten

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

On 22 May 2017, at 15:50, Anne Gentle wrote: > On Mon, May 22, 2017 at 5:41 PM, Sean McGinnis > wrote: > >> On Mon, May 22, 2017 at 09:39:09AM +, Alexandra Settle wrote: >> >> [snip] >> >>> 1. We could combine all of the documentation builds, so that each >> project has a single doc/source

Re: [openstack-dev] [oslo][oslo.messaging] Call to deprecate the 'pika' driver in the oslo.messaging project

+1 , let's focus on key drivers. 2017-05-17 2:02 GMT+08:00 Joshua Harlow : > Fine with me, > > I'd personally rather get down to say 2 'great' drivers for RPC, > > And say 1 (or 2?) for notifications. > > So ya, wfm. > > -Josh > > > Mehdi Abaakouk wrote: > >> +1 too, I haven't seen its contributo

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

On Mon, May 22, 2017 at 5:41 PM, Sean McGinnis wrote: > On Mon, May 22, 2017 at 09:39:09AM +, Alexandra Settle wrote: > > [snip] > > > 1. We could combine all of the documentation builds, so that each > project has a single doc/source directory that includes developer, > contributor, and user

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

On Mon, May 22, 2017 at 09:39:09AM +, Alexandra Settle wrote: [snip] > 1. We could combine all of the documentation builds, so that each project has > a single doc/source directory that includes developer, contributor, and user > documentation. This option would reduce the number of build j

[openstack-dev] uWSGI help for Congress

If someone out there knows uWSGI and has a couple spare cycles to help Congress project, we'd super appreciate it. The regular contributors to Congress don't have experience with uWSGI and could definitely use some help getting started with this goal. Thanks a ton! https://governance.openstack.or

Re: [openstack-dev] [OpenStack-docs] [doc][ptls][all] Documentation publishing future

On Mon, 22 May 2017 09:39:09 + Alexandra Settle wrote: (...) > Until this point, the documentation team has owned several manuals that > include > content related to multiple projects, including an installation guide, admin > guide, configuration guide, networking guide, and security guide.

Re: [openstack-dev] [nova][vlan trunking] Guest networking configuration for vlan trunk

Hi Levi, Thanks for the info. I noticed that support in the nova code, but was wondering why something similar is not available for vlan trunking. --Robert On 5/22/17, 3:34 PM, "Moshe Levi" mailto:mosh...@mellanox.com>> wrote: Hi Robert, The closes thing that I know about is tagging of SR-IO

Re: [openstack-dev] [release][infra][puppet][stable] Re: [Release-job-failures] Release of openstack/puppet-nova failed

Excerpts from Jeremy Stanley's message of 2017-05-22 19:16:34 +: > On 2017-05-22 12:31:49 -0600 (-0600), Alex Schultz wrote: > > On Mon, May 22, 2017 at 10:34 AM, Jeremy Stanley wrote: > > > On 2017-05-22 09:06:26 -0600 (-0600), Alex Schultz wrote: > > > [...] > > >> We ran into this for the p

Re: [openstack-dev] [nova][vlan trunking] Guest networking configuration for vlan trunk

Hi Robert, The closes thing that I know about is tagging of SR-IOV physical function’s VLAN tag to guests see [1] Maybe you can leverage the same mechanism to config vlan trunking in guest. [1] - https://specs.openstack.org/openstack/nova-specs/specs/ocata/implemented/sriov-pf-passthrough-neutro

Re: [openstack-dev] [release][infra][puppet][stable] Re: [Release-job-failures] Release of openstack/puppet-nova failed

On 2017-05-22 12:31:49 -0600 (-0600), Alex Schultz wrote: > On Mon, May 22, 2017 at 10:34 AM, Jeremy Stanley wrote: > > On 2017-05-22 09:06:26 -0600 (-0600), Alex Schultz wrote: > > [...] > >> We ran into this for the puppet-module-build check job so I created a > >> puppet-agent-install builder.

Re: [openstack-dev] [Openstack-operators] [nova][ironic][scheduler][placement] IMPORTANT: Getting rid of the automated reschedule functionality

On 5/22/2017 1:50 PM, Matt Riedemann wrote: On 5/22/2017 12:54 PM, Jay Pipes wrote: Hi Ops, I need your feedback on a very important direction we would like to pursue. I realize that there were Forum sessions about this topic at the summit in Boston and that there were some decisions that wer

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

Hi Team, It is a friendly reminder that we have our meeting in less than an hour (2000 UTC) on #openstack-meeting-3. :) You can find the agenda here: https://etherpad.openstack.org/p/openstack-upstream-institute-meetings

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

Excerpts from Anne Gentle's message of 2017-05-22 12:36:29 -0500: > > On May 22, 2017, at 9:09 AM, Doug Hellmann wrote: > > > > Excerpts from Dmitry Tantsur's message of 2017-05-22 12:26:25 +0200: > >>> On 05/22/2017 11:39 AM, Alexandra Settle wrote: > >>> Hi everyone, > >>> > >>> The documentatio

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

Excerpts from Michał Jastrzębski's message of 2017-05-22 10:42:44 -0700: > [snip] > > So from Kolla perspective, since our dev guide is really also > operators guide (we are operators tool so we're kinda "special" on > that front), we'd love to handle both deployment guide, user manuals > and all

Re: [openstack-dev] [release][infra][puppet][stable] Re: [Release-job-failures] Release of openstack/puppet-nova failed

On Mon, May 22, 2017 at 10:34 AM, Jeremy Stanley wrote: > On 2017-05-22 09:06:26 -0600 (-0600), Alex Schultz wrote: > [...] >> We ran into this for the puppet-module-build check job so I created a >> puppet-agent-install builder. Perhaps the job needs that added to it > [...] > > Problem here bei

Re: [openstack-dev] [all] Onboarding rooms postmortem, what did you do, what worked, lessons learned

Project: Neutron Attendees: ~15 Neutron's session was a combination of a slide presentation ( https://www.slideshare.net/MiguelLavalle/openstack-neutron-new-developers-on-boarding) with predefined exercises on the DevStack VM that was used during the OpenStack Upstream Institute the weekend prior

Re: [openstack-dev] [trove] Trove reboot meeting

On 2017-05-22 17:42:09 + (+), MCCASLAND, TREVOR wrote: > Thanks Jeremy, that will work for our updated weekly meeting. > > To clear any confusion, this is a one-time project-scope meeting > focused on hearing the needs of the new contributors we have as > well as trove's current goals. It'

[openstack-dev] [Ironic] Regarding where to host Redfish vendor extensions code for Ironic

Hi All This is wrt discussion we had about where to host the Redfish vendor vendor extensions. Should it be sub-module within sushy-tree or separate vendor project(s). The following were the opinions:- In favor of Sushy sub-module:- 1. People see "vendor specific" repo's as owned by the vendor a

[openstack-dev] [os-upstream-institute] Meeting Today!

Hello Everyone, Its a pretty short agenda[1] today so feel free to add things you think we need to discuss :) See you in #openstack-meeting-3 at 20:00 UTC! -Kendall (diablo_rojo) [1]https://etherpad.openstack.org/p/openstack-upstream-institute-meetings __

[openstack-dev] [nova][vlan trunking] Guest networking configuration for vlan trunk

Hi, I’m trying to find out if there is support in nova (in terms of metadata and cfgdrive) to configure vlan trunking in the guest. In the ‘CLI usage example’ provided in this wiki https://wiki.openstack.org/wiki/Neutron/TrunkPort, it indicates: # The typical cloud image will auto-configure th

[openstack-dev] [requirements][stable] request for stable team to review the requirements queue

https://review.openstack.org/#/q/project:openstack/requirements+status:open+NOT+branch:master We currently do not have anyone able to review/workflow these items and it'd be nice if we could get some eyes on these reviews. Thanks, -- Matthew Thode (prometheanfire) signature.asc Description:

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

[snip] So from Kolla perspective, since our dev guide is really also operators guide (we are operators tool so we're kinda "special" on that front), we'd love to handle both deployment guide, user manuals and all that in our tree. If we could create infrastructure that would allow us to segregate

Re: [openstack-dev] [trove] Trove reboot meeting

Thanks Jeremy, that will work for our updated weekly meeting. To clear any confusion, this is a one-time project-scope meeting focused on hearing the needs of the new contributors we have as well as trove's current goals. It's supposed to be separate from the regular meeting. -Original Mess

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

> On May 22, 2017, at 9:09 AM, Doug Hellmann wrote: > > Excerpts from Dmitry Tantsur's message of 2017-05-22 12:26:25 +0200: >>> On 05/22/2017 11:39 AM, Alexandra Settle wrote: >>> Hi everyone, >>> >>> The documentation team are rapidly losing key contributors and core >>> reviewers. >>> We are n

Re: [openstack-dev] [trove] Trove reboot meeting

Justin, that time is just as good. Thursday 1400 UTC will be the time for the meeting unless we have any other objections. From: Justin Cook [mailto:jhc...@secnix.com] Sent: Monday, May 22, 2017 12:18 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack

Re: [openstack-dev] [trove] Trove reboot meeting

On 2017-05-22 16:50:10 + (+), MCCASLAND, TREVOR wrote: [...] > Sharing google calendar events can be a pain but it only gives us > a notification for our calendars so.. I'm not going to bother with > it that much. If you really want it on your calendar you can email > me and I will add you

Re: [openstack-dev] [trove] Trove reboot meeting

Trevor, 1500 UTC is 1600 BST and 1700 CEST which is quite late for the French. Our friends in Berlin may be up for it. I recommend 1500 BST which is 1400 UTC. Of course, your suggestion works well for the US west coast. Cheers, Justin On 22 May 2017 at 17:50:10, MCCASLAND, TREVOR (tm2...@att.co

[openstack-dev] [tripleo] Sample Environment Generator

I've finally gotten back to working on this spec[1] and wanted to send a quick update. The patch series is updated with the changes we discussed at the PTG, and you can find the start of it here: https://review.openstack.org/#/c/253638/ Obviously there are a _lot_ of environments left to conv

Re: [openstack-dev] [trove] Trove reboot meeting

The results show a meeting time for Thursday 1500 UTC; I'll message the join link on this thread 15 min prior and in the #openstack-trove It has come to my attention that the poll time zones were not clear, I was under the impression everyone had their own view based on their IP's location. Howe

Re: [openstack-dev] [Heat] revised structure of the heat-templates repository. Suggestions

Hi, On 22.05.17 10:43, Thomas Herve wrote: On Fri, May 19, 2017 at 5:00 PM, Lance Haig wrote: Hi, Hi Lance, Thanks for starting this. Comments inline. As we know the heat-templates repository has become out of date in some respects and also has been difficult to be maintained from a commu

Re: [openstack-dev] [release][infra][puppet][stable] Re: [Release-job-failures] Release of openstack/puppet-nova failed

On 2017-05-22 09:06:26 -0600 (-0600), Alex Schultz wrote: [...] > We ran into this for the puppet-module-build check job so I created a > puppet-agent-install builder. Perhaps the job needs that added to it [...] Problem here being these repos share the common tarball jobs used for generating pyt

Re: [openstack-dev] Is the pendulum swinging on PaaS layers?

On 19/05/17 17:59, Matt Riedemann wrote: On 5/19/2017 9:36 AM, Zane Bitter wrote: The problem is that orchestration done inside APIs is very easy to do badly in ways that cause lots of downstream pain for users and external orchestrators. For example, Nova already does some orchestration: it cr

Re: [openstack-dev] [tc] revised Postgresql deprecation patch for governance

On 05/15/2017 07:16 AM, Sean Dague wrote: > We had a forum session in Boston on Postgresql and out of that agreed to > the following steps forward: > > 1. explicitly warn in operator facing documentation that Postgresql is > less supported than MySQL. This was deemed better than just removing > do

[openstack-dev] [fuxi][stackube][kuryr] IRC meeting

Hi all, We will have an IRC meeting at UTC 1400-1500 Tuesday (2017-05-23). At the meeting, we will discuss the k8s storage integration with OpenStack. This effort might cross more than one teams (i.e. kuryr and stackube). You are more than welcomed to join us at #openstack-meeting-cp tomorrow.

[openstack-dev] [requirements] Projects holding back requirements updates

This is just a friendly reminder that without a release from master, if your project still caps a requirement then it may be either holding back a package or not be included in upper-constraints updates. http://logs.openstack.org/76/466476/5/check/gate-requirements-tox-py27-check-uc-ubuntu-xenial/

Re: [openstack-dev] [qa] Create subnetpool on dynamic credentials

In order to twist things even more ;-), We should consider making tempest working in environment where the users instead of getting IPV4 floating IP, they are allowed to get a globally route-able IPV6 range (prefix/ subnet from a subnetpool) . Tempest should be able to do connectivity tests agains

Re: [openstack-dev] [release][infra][puppet][stable] Re: [Release-job-failures] Release of openstack/puppet-nova failed

On Mon, May 22, 2017 at 9:05 AM, Paul Belanger wrote: > On Mon, May 22, 2017 at 10:53:32AM -0400, Doug Hellmann wrote: >> Excerpts from jenkins's message of 2017-05-22 10:49:09 +: >> > Build failed. >> > >> > - puppet-nova-tarball >> > http://logs.openstack.org/89/89c58e7958b448364cb0290c1879

Re: [openstack-dev] [release][infra][puppet][stable] Re: [Release-job-failures] Release of openstack/puppet-nova failed

On Mon, May 22, 2017 at 8:53 AM, Doug Hellmann wrote: > Excerpts from jenkins's message of 2017-05-22 10:49:09 +: >> Build failed. >> >> - puppet-nova-tarball >> http://logs.openstack.org/89/89c58e7958b448364cb0290c1879116f49749a68/release/puppet-nova-tarball/fe9daf7/ >> : FAILURE in 55s >>

Re: [openstack-dev] [release][infra][puppet][stable] Re: [Release-job-failures] Release of openstack/puppet-nova failed

On Mon, May 22, 2017 at 10:53:32AM -0400, Doug Hellmann wrote: > Excerpts from jenkins's message of 2017-05-22 10:49:09 +: > > Build failed. > > > > - puppet-nova-tarball > > http://logs.openstack.org/89/89c58e7958b448364cb0290c1879116f49749a68/release/puppet-nova-tarball/fe9daf7/ > > : FAIL

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

Excerpts from Dmitry Tantsur's message of 2017-05-22 16:54:30 +0200: > On 05/22/2017 04:09 PM, Doug Hellmann wrote: > > Excerpts from Dmitry Tantsur's message of 2017-05-22 12:26:25 +0200: > >> On 05/22/2017 11:39 AM, Alexandra Settle wrote: > >>> Hi everyone, > >>> > >>> The documentation team are

[openstack-dev] [puppet] Meeting Reminder for May 23, 2017

Hey Folks, Just a reminder that we have a meeting schedule for tomorrow, May 23, 2017 @ 1500 UTC. If you wish to talk about something, please add it to the agenda[0]. Thanks, -Alex [0] https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20170523 ___

Re: [openstack-dev] [ironic] [tripleo] [dib] RFC: moving/transitioning the ironic-agent element to the ironic-python-agent tree

On 05/22/2017 03:10 PM, Sam Betts (sambetts) wrote: I would like to suggest that we create a new repo for housing the tools required to build ironic python agent images: ironic-python-agent-builder(tooling). This would include, the DIB element, the existing coreos and tinyipa methods and hopef

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

On 05/22/2017 04:09 PM, Doug Hellmann wrote: Excerpts from Dmitry Tantsur's message of 2017-05-22 12:26:25 +0200: On 05/22/2017 11:39 AM, Alexandra Settle wrote: Hi everyone, The documentation team are rapidly losing key contributors and core reviewers. We are not alone, this is happening acro

[openstack-dev] [release][infra][puppet][stable] Re: [Release-job-failures] Release of openstack/puppet-nova failed

Excerpts from jenkins's message of 2017-05-22 10:49:09 +: > Build failed. > > - puppet-nova-tarball > http://logs.openstack.org/89/89c58e7958b448364cb0290c1879116f49749a68/release/puppet-nova-tarball/fe9daf7/ > : FAILURE in 55s > - puppet-nova-tarball-signing puppet-nova-tarball-signing : SK

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

Excerpts from Anne Gentle's message of 2017-05-22 08:08:40 -0500: > On Mon, May 22, 2017 at 4:39 AM, Alexandra Settle > wrote: > > > Hi everyone, > > > > > > > > The documentation team are rapidly losing key contributors and core > > reviewers. We are not alone, this is happening across the board

[openstack-dev] [all] Unified Limits (Boston Forum Session and Next Steps)

The Unified Limits session in Boston was interesting and fruitful. Here's the current summary of where I think we stand. * Current Status ** Conceptual Spec Landed https://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/unified-limits.html ** Keystone detailed interface spe

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

Excerpts from Dmitry Tantsur's message of 2017-05-22 12:26:25 +0200: > On 05/22/2017 11:39 AM, Alexandra Settle wrote: > > Hi everyone, > > > > The documentation team are rapidly losing key contributors and core > > reviewers. > > We are not alone, this is happening across the board. It is makin

Re: [openstack-dev] [Keystone] Cockroachdb for Keystone Multi-master

On 05/22/2017 05:02 AM, Thierry Carrez wrote: Mike Bayer wrote: On 05/18/2017 06:13 PM, Adrian Turjak wrote: So, specifically in the realm of Keystone, since we are using sqlalchemy we already have Postgresql support, and since Cockroachdb does talk Postgres it shouldn't be too hard to back

Re: [openstack-dev] [nova] Boston Forum session recap - searchlight integration

On 05/22/2017 05:39 AM, Matthew Booth wrote: There are also a couple of optimisations to make which I won't bother with up front. Dan suggested in his CellsV2 talk that we would only query cells where the user actually has instances. If we find users tend to clump in a small number of cells

[openstack-dev] [tripleo] Feedback needed on sizing partitions

Hi As part of the security hardened images effort: https://blueprints.launchpad.net/tripleo/+spec/build-whole-disk-images I created a patch to define the initial partitions on the image: https://review.openstack.org/#/c/449122/7/elements/overcloud-secure/block-device-config.yaml I tested those on

Re: [openstack-dev] [puppet] [tempest] L2GW not standard Tempest Plugin. How to get tests into CI?

On Mon, May 22, 2017 at 6:41 PM, Ghanshyam Mann wrote: > On Mon, May 22, 2017 at 9:42 PM, Kevin Benton wrote: >> Can you file a patch to adjust tox.ini of l2gw to make it the same as the >> others? > > Actually it is not just tox, if we need to setup l2gw tests as Tempest > plugin, it needs some

Re: [openstack-dev] [nova] Boston Forum session recap - searchlight integration

On 05/22/2017 05:39 AM, Matthew Booth wrote: > Aside: For a query operation, what's the better user experience when a > single cell is failing: > > 1. The whole query fails. > 2. The user gets incomplete results. > > Either of these are simple to implement. Incomplete results would also > additio

Re: [openstack-dev] [qa] Create subnetpool on dynamic credentials

Hi Hongbin, If several of your test cases require a subnet pool, I think the simplest solution would be creating one in the resource creation step of the tests. As I understand it, subnet pools can be created by regular projects (they do not require admin credentials). The main advantage that I c

Re: [openstack-dev] [ptg] ptgbot: how to make "what's currently happening" emerge

Thierry Carrez wrote: > [...] > I have POC code for this bot already. Before I publish it (and start > work to make infra support it), I just wanted to see if this is the > right direction and if I should continue to work on it :) I feel like > it's an incremental improvement that preserves the fle

Re: [openstack-dev] [puppet] [tempest] L2GW not standard Tempest Plugin. How to get tests into CI?

On Mon, May 22, 2017 at 9:42 PM, Kevin Benton wrote: > Can you file a patch to adjust tox.ini of l2gw to make it the same as the > others? Actually it is not just tox, if we need to setup l2gw tests as Tempest plugin, it needs some of the tests and config options refactoring. I have not gone deep

Re: [openstack-dev] [all] Onboarding rooms postmortem, what did you do, what worked, lessons learned

Project: Documentation and I18N Attendees: 3-5 (maybe?) Etherpad: https://etherpad.openstack.org/p/doc-onboarding What we did: We ran the session informally based off whoever was there. Due to the small attendance, we just ran through how the project works (docs like code and all that). Discus

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

On Mon, May 22, 2017 at 4:39 AM, Alexandra Settle wrote: > Hi everyone, > > > > The documentation team are rapidly losing key contributors and core > reviewers. We are not alone, this is happening across the board. It is > making things harder, but not impossible. > > Since our inception in 2010,

Re: [openstack-dev] [ironic] [tripleo] [dib] RFC: moving/transitioning the ironic-agent element to the ironic-python-agent tree

I would like to suggest that we create a new repo for housing the tools required to build ironic python agent images: ironic-python-agent-builder(tooling). This would include, the DIB element, the existing coreos and tinyipa methods and hopefully in the future the buildroot method for creating

Re: [openstack-dev] [all] Onboarding rooms postmortem, what did you do, what worked, lessons learned

Project: Sahara Attendees: 6-8 (1 never involved in Sahara) We worked on a quick overview of how Sahara works and planned to work a little on code. Since most of the people there worked on Sahara already the code introduction didn't make a lot of sense since the only rookie was most interested in

Re: [openstack-dev] [nova] Boston Forum session recap - searchlight integration

Hi Matt, if by "incomplete results" you mean retrieve the instances UUIDs (in the cell_api) for the cells that failed to answer, I would prefer to have incomplete results than a failed operation. Belmiro On Mon, May 22, 2017 at 11:39 AM, Matthew Booth wrote: > On 19 May 2017 at 20:07, Mike Baye

Re: [openstack-dev] [puppet] [tempest] L2GW not standard Tempest Plugin. How to get tests into CI?

Can you file a patch to adjust tox.ini of l2gw to make it the same as the others? On May 22, 2017 7:35 AM, "Ricardo Noriega De Soto" wrote: > Hello guys, > > I'm trying to enable some tempest tests into puppet-openstack-integration > project. I basically did the same procedure as with other Neut

[openstack-dev] [ironic] [tripleo] [dib] RFC: moving/transitioning the ironic-agent element to the ironic-python-agent tree

Hi all! Some time ago we discussed moving ironic-agent element that is used to build IPA to IPA tree itself. It got stuck, and I'd like to restart the discussion. The reason for this move is to make the DIB element in question one of *official* ways to build IPA. This includes gating on both

[openstack-dev] [Openstack-dev][Tacker] Not able to run user_data commands on my instance

Hi, I'm have installed openstack with tacker by devstack. I'm able to run OpenWRT vnf and able to configure the firewall service with openwrt management driver. And also able to run shell commands in cirros image which is also using openwrt management driver. Now I have created one ubuntu

Re: [openstack-dev] [tc] Active or passive role with our database layer

On 05/21/2017 10:09 PM, Mike Bayer wrote: >> >> A similar issue lurks with the fact that MySQL unicode storage is >> 3-byte by default and 4-byte is opt-in. We could take the 'external' >> approach and document it and assume the operator has configured their >> my.cnf with the appropriate default,

[openstack-dev] [puppet] [tempest] L2GW not standard Tempest Plugin. How to get tests into CI?

Hello guys, I'm trying to enable some tempest tests into puppet-openstack-integration project. I basically did the same procedure as with other Neutron drivers but tests were not being executed: https://review.openstack.org/#/c/460080/ If you check the puppet-tempest patch, I enable the "l2gw" d

Re: [openstack-dev] [freezer] Core team updates

+1 Thank you for your contributions Vitaly! From: Saad Zaher Sent: Monday, May 22, 2017 11:30:02 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [freezer] Core team updates Hi, I would like to propose some cor

[openstack-dev] [freezer] Core team updates

Hi, I would like to propose some core member updates to the Freezer core team. I would like to add the following user(s) to core as they became they're actively contributing and review code upstream as well as helping people in the irc channel: - Vitaliy Nogin ( vnogin ) Please, If you agre

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

On 05/22/2017 11:39 AM, Alexandra Settle wrote: Hi everyone, The documentation team are rapidly losing key contributors and core reviewers. We are not alone, this is happening across the board. It is making things harder, but not impossible. Since our inception in 2010, we’ve been climbing h

Re: [openstack-dev] [nova] Boston Forum session recap - searchlight integration

On 19 May 2017 at 20:07, Mike Bayer wrote: > > > On 05/19/2017 02:46 AM, joehuang wrote: > >> Support sort and pagination together will be the biggest challenge: it's >> up to how many cells will be involved in the query, 3,5 may be OK, you can >> search each cells, and cached data. But how about

[openstack-dev] [doc][ptls][all] Documentation publishing future

Hi everyone, The documentation team are rapidly losing key contributors and core reviewers. We are not alone, this is happening across the board. It is making things harder, but not impossible. Since our inception in 2010, we’ve been climbing higher and higher trying to achieve the best documen

Re: [openstack-dev] [oslo] can we make everyone drop eventlet? (was: Can we stop global requirements update?)

We discussed this for a long time, As I know , some projects use eventlet heavily like Nova [1], If everyon agree with removing eventlet , we can set it as one of comunnity goals[2] [1]https://github.com/openstack/nova/blob/master/doc/source/threading.rst [2]https://etherpad.openstack.org/p/commu

Re: [openstack-dev] [Keystone] Cockroachdb for Keystone Multi-master

Mike Bayer wrote: > On 05/18/2017 06:13 PM, Adrian Turjak wrote: >> >> So, specifically in the realm of Keystone, since we are using sqlalchemy >> we already have Postgresql support, and since Cockroachdb does talk >> Postgres it shouldn't be too hard to back Keystone with it. At that >> stage you

Re: [openstack-dev] [Heat] revised structure of the heat-templates repository. Suggestions

On Fri, May 19, 2017 at 5:00 PM, Lance Haig wrote: > Hi, Hi Lance, Thanks for starting this. Comments inline. > As we know the heat-templates repository has become out of date in some > respects and also has been difficult to be maintained from a community > perspective. While it has been out

Re: [openstack-dev] [all] Onboarding rooms postmortem, what did you do, what worked, lessons learned

On Fri, May 19, 2017 at 09:22:07AM -0400, Sean Dague wrote: > This is a thread for anyone that participated in the onboarding rooms, > on either the presenter or audience side. Because we all went into this > creating things from whole cloth, I'm sure there are lots of lessons > learned. > > If yo

Re: [openstack-dev] [all] Project On-Boarding Info Collection

Hello, Not use a training slides in Tricricle on-boarding session, and would like to create one for new contributors later. For the summary of the on-boarding session, have replied in another thread which collects feedback. Best Regards Chaoyi Huang (joehuang) F