Re: [openstack-dev] [rpm-packaging][chef][puppet][salt][openstack-ansible][HA][tripleo][kolla][fuel] Schema proposal for config file handling for services

Hi, On Mon, Oct 10, 2016 at 10:07:05AM -0600, Alex Schultz wrote: > On Mon, Oct 10, 2016 at 5:03 AM, Thomas Bechtold wrote: > > Hi, > > > > in the rpm-packaging project we started to package the services and are > > currently discussing a possible schema for configuration files and > > snippets u

Re: [openstack-dev] [lbaas] [octavia] Proposing Lubosz Kosnik (diltram) as Octavia Core

+1!, even if my vote does not count :-) On Tue, Oct 11, 2016 at 12:00 AM, Eichberger, German wrote: > +1 (even if it doesn’t matter) > > > > From: Stephen Balukoff > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > > Date: Monday, October 10, 2016 at 4:39 PM > To: "Ope

Re: [openstack-dev] [nova] FYI, nova plans to have a room at the PTG in February

Le 10/10/2016 19:24, Clint Byrum a écrit : Excerpts from Matt Riedemann's message of 2016-10-10 11:51:36 -0500: On 10/10/2016 8:59 AM, Sean McGinnis wrote: On Mon, Oct 10, 2016 at 08:37:53AM -0400, Doug Hellmann wrote: We had a lot of feedback that the unstructured discussion time from the

Re: [openstack-dev] [nova] [libvirt] Debugging blockRebase() - "active block copy not ready for pivot"

On Mon, Oct 10, 2016 at 5:54 PM, Matt Riedemann wrote: > On 10/10/2016 6:26 AM, Kashyap Chamarthy wrote: > >> >> Also, maybe you have noticed, given Eric's reply on this thread (and the >> upstream libvir-list), it is agreed that virDomainGetBlockJobInfo() >> should be fixed "to quit reporting cu

Re: [openstack-dev] [ironic][neutron] ML2 plugin for Ironic needs

Vasyl Saienko wrote: Hello Community, Ironic and Neutron projects have become integrated even closer with multitenancy implementation in Ironic. There are 2 bugs that require separate ML2 driver specifically for Ironic needs: • Booting ironic instance, Neutron port remains in dow

[openstack-dev] New OpenStack Bug Smash

Hi all, We want to kick off the next OpenStack bug smash and it targets Nov 30 - Dec 2 (Wed - Fri) at Shenzhen in China, which was voted in the last bug smash at Hangzhou, for the next Ocata release. The release schedule and Thanksgiving day are considered for the date. Do any of you want to co-

[openstack-dev] [Karbor] Ocata design summit

hi, Karbors: As you know, the summit is very close(less than 2 weeks),Karbor has five sessions in Barcelona, you can find them here: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=karbor

Re: [openstack-dev] [tripleo] Suggestions for OOO

On 10/11/2016 02:39 AM, Joe Talerico wrote: Hey all, The past couple of days I have making comments on IRC to discuss some of the issues I have bumped into when scaling Newton to > 30 compute nodes. - `bulk import`, the operation to go from enroll -> manage can take 20-30 minutes to complete. Ca

Re: [openstack-dev] [all][stable] Moving stable/mitaka to Phase-II and liberty to Phase-III

On 10/10/2016 11:34 PM, Tony Breeds wrote: On Mon, Oct 10, 2016 at 08:42:48AM +0200, Ihar Hrachyshka wrote: I think it would also make sense to *release* on the boundary of the switch; so that it’s clear which phase a release followed. I agree, I don't really have a mechanism for do that thou

Re: [openstack-dev] [neutron] proper cleanup of l3 resources (neutron-netns-cleanup)

Hi, Miguel. As I can see, Manjeet Singh Bhatia already proposed the change on review [1]—this patch adds the invoking a cleanup provided by l3-agent. Actually, I like the option 2. And I'm going to implement it and compare to Manjeet's solution. But can anybody suggest me, how can I manually rep

Re: [openstack-dev] requests-mock

Clay, Apologies for the top post. Here's the current recommendation on dependencies - Answering your question on "I'm not acctually sure what the OpenStack policy is on dependency hygiene :D Anyway,": https://github.com/openstack/requirements#global-requirements-for-openstack-projects There is a

Re: [openstack-dev] [all][stable] Moving stable/mitaka to Phase-II and liberty to Phase-III

On Tue, Oct 11, 2016 at 6:43 AM, Dmitry Tantsur wrote: > On 10/10/2016 11:34 PM, Tony Breeds wrote: >> >> On Mon, Oct 10, 2016 at 08:42:48AM +0200, Ihar Hrachyshka wrote: >> >>> I think it would also make sense to *release* on the boundary of the >>> switch; >>> so that it’s clear which phase a re

Re: [openstack-dev] [tripleo] Suggestions for OOO

On Tue, Oct 11, 2016 at 6:38 AM, Dmitry Tantsur wrote: > On 10/11/2016 02:39 AM, Joe Talerico wrote: >> >> Hey all, >> The past couple of days I have making comments on IRC to discuss some >> of the issues I have bumped into when scaling Newton to > 30 compute >> nodes. >> >> - `bulk import`, the

Re: [openstack-dev] [nova] FYI, nova plans to have a room at the PTG in February

Doug Hellmann wrote: > Excerpts from Sean Dague's message of 2016-10-10 09:23:43 -0400: >> On 10/10/2016 08:37 AM, Doug Hellmann wrote: >> >>> We had a lot of feedback that the unstructured discussion time from >>> the Friday "meetups" at the summits were the most productive time >>> for teams, bu

[openstack-dev] [FUEL]Fuel-devops 3.0.3 release

Hello! Today we are releasing fuel-devops 3.0.3. Included new changes: * DevopsClient implementation - split logical layers [3] * Real-time output during SSH command execution, Subprocess runner optimization [1, 2, 6, 8, 9] * Manipulate bridges on remote hosts [13] * Use DHCP ip ranges for assign

Re: [openstack-dev] [ironic][neutron] ML2 plugin for Ironic needs

On Mon, Oct 10, 2016 at 4:32 AM, Vasyl Saienko wrote: > Hello Community, > > > Ironic and Neutron projects have become integrated even closer with > multitenancy implementation in Ironic. > > There are 2 bugs that require separate ML2 driver specifically for Ironic > needs: > > > Booting ironic in

Re: [openstack-dev] [nova] FYI, nova plans to have a room at the PTG in February

Clint Byrum wrote: > I think there's some perspective warping going on, and it's very > concerning to me. > > Productivity inside the project is great, and we should definitely box > out more than just one day of the PTG for just those high bandwidth > internal project face to face discussions. >

[openstack-dev] [devstack] devstack-plugin additional-pkg-repos: ocata summit working session?

Backstory - Some time ago, tonyb and I started the work on a gate testing job which can install additional packages onto the testing node: https://github.com/openstack-infra/project-config/blob/b18a8a6cd1ed3865ff46e654e41b4959c342dc15/jenkins/jobs/devstack-gate.yaml#L536 The installation

Re: [openstack-dev] requests-mock

-Original Message- From: Clay Gerrard Reply: OpenStack Development Mailing List (not for usage questions) Date: October 11, 2016 at 00:25:10 To: OpenStack Development Mailing List Subject:  [openstack-dev] requests-mock > Greetings! > > Anyone have any experience to share positive or ne

[openstack-dev] [networking-sfc][devstack][mitaka]

Hi all, I have been trying out networking-sfc to create service function chain in Openstack. I could create all the port pairs, port-pair-groups, flow classifier and the chain but I could not see the packets on the desired hops. I am trying to create a simple sfc with 3 VMs(vm1 to vm3) in the se

[openstack-dev] [ironic] Summit schedule is set

Hi folks, We've locked in our summit schedule, that is here (including a bonus talk at the top due to how the search works): https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Ironic%3A Please do let me know ASAP if there are any major conflicts. If you've proposed o

Re: [openstack-dev] [kolla] We plan to be in PTG

On 10/10/16 09:41 -0500, Michał Jastrzębski wrote: Everyone, Kolla plans to be part of PTG in Atlanta. I hope to see you all there! Great news! Flavio -- @flaper87 Flavio Percoco signature.asc Description: PGP signature __

Re: [openstack-dev] [heat] [magnum] Subjects to discuss during the summit

On 11/10/16 02:24, Rabi Mishra wrote: 1.2 For large stacks, 1000 nodes, the final call to heat to fetch the IPs for all nodes takes 3 to 4 minutes. In heat, the stack has status CREATE_COMPLETE but magnum's state is updated

[openstack-dev] [sahara] Sahara PTG plans

Hello team, Per discussion during last meeting with team, I think that Sahara team will be presented at PTG at Atlanta. So, I will request a room for us till the end of week (if there is no objections). Most probably, we will be able to get critical members of team to discuss new features and plan

Re: [openstack-dev] [nova] FYI, nova plans to have a room at the PTG in February

Excerpts from Thierry Carrez's message of 2016-10-11 14:04:55 +0200: > Clint Byrum wrote: > > > Whatever we do, please consider dismantling the silos, rather than > > reinforcing them. > > We do dismantle the silos. (1) the upstream silos between vertical and > horizontal teams, by setting up dif

Re: [openstack-dev] [devstack] devstack-plugin additional-pkg-repos: ocata summit working session?

On Tue, Oct 11, 2016 at 02:09:33PM +0200, Markus Zoeller wrote: [Snip well-written backrgound detail] > Request > --- > My question is, if you have interest in this plugin and its > capabilities, are you at the Summit in Barcelona and do you have time > for a short working session there? May

Re: [openstack-dev] [nova] FYI, nova plans to have a room at the PTG in February

Clint Byrum wrote: > [...] > Since there seems to be broad based resistance to time boxing anything > project specific, I'd like to propose a compromise: I'd like to ask that > teams allow people to add their IRC nick to the agenda items they'd like > to be included in, and at the beginning of a to

[openstack-dev] [ironic] Meeting logs for October 12, 2016

Hi all, Since meetbot was down yesterday, thought I'd send out the meeting logs for the ironic meeting. http://paste.openstack.org/show/585338/ // jim __ OpenStack Development Mailing List (not for usage questions) Unsubscr

Re: [openstack-dev] [Zun] ERROR: Not Authorized

Courage, If you follow the instruction [1] to setup the development environment, the files should be there. All the logs can be found under /opt/stack/logs . Alternatively, you could check the screen output by "screen -r stack". [1] https://github.com/openstack/zun/blob/master/doc/source/dev/quic

Re: [openstack-dev] [QA][Cinder]Removing Cinder v1 in Tempest

On Tue, Oct 11, 2016 at 4:23 AM, Ken'ichi Ohmichi wrote: > Thanks for pointing this up, Jordan > > Before removing volume v1 API tests, it is nice to make the v2 API the > default of Tempest scenario tests. > Now the v1 and v2 is set as True on the default in the > configuration[1], and the v1 AP

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On 2016-10-04 04:53 PM, Anita Kuno wrote: On 16-10-04 12:54 PM, Thierry Carrez wrote: Doug Hellmann wrote: John Davidge wrote: Thierry, I'm surprised by your open hostility towards candidates. Accusing people of 'pretending' to care about things that they've taken the time to This is an excel

[openstack-dev] [networking-cisco] Meeting Reminder, 11th Oct 2016

Just a quick reminder that the first networking-cisco IRC meeting will be happening on #openstack-meeting-3 at 16:00 UTC. See you there, Sam __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: opens

Re: [openstack-dev] [devstack] devstack-plugin additional-pkg-repos: ocata summit working session?

On 10/11/2016 02:09 PM, Markus Zoeller wrote: > * How to create a "*.deb" package out of the source code of > libvirt/qemu? (surprisingly enough, I'm still struggling with this) What version of libvirt / qemu are you trying to build? libvirt 2.3.0 was released 6 days ago, and uploaded to Debian un

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On Oct 11, 2016, at 10:37 AM, Anita Kuno wrote: > Just in case folks care, now is the best time to discuss our election process > and suggest options or changes for the next round of elections. I'm not > adverse to discussing it I just think the best time for doing so is from the > time the la

Re: [openstack-dev] [neutron] [classifier] Common Classifier + OVS Flow Management Meeting

Reminder that the meeting is in 1 hour, Best regards, Igor. From: Duarte Cardoso, Igor [mailto:[email protected]] Sent: Monday, October 10, 2016 5:14 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [neutron] [classifier] Common Classifier

[openstack-dev] [kosmos] meetings canceled until post summit

We will pick back up on 11/1. Doug__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

Based on the turnout numbers and a bit of unscientific number crunching on the voting results it seems that the electorate was rather more engaged this time around. That's _great_. As others have said I imagine some significant part of that was because of more than one mailing of the ballots to

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

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 various services> (there seems to be some at > http://docs.openstack.org/developer/nova/notifications.html)? we have something

Re: [openstack-dev] [tripleo] Setting up to 3rd party CI OVB jobs

On 7 October 2016 at 14:03, Paul Belanger wrote: > Greetings, > > I wanted to propose a work item, that I am happy to spearhead, about setting > up > a 3rd party CI system for tripleo project. The work I am proposing, wouldn't > actually affect anything today about tripleo-ci but provider a worki

Re: [openstack-dev] [OpenStack-docs] Admin guide in-tree?

>From my point of view, the rush is so that we can be more efficient with all of our time/efforts. In ironic, we have a bit of a mess. We now have duplicated (and perhaps out-of-sync) admin-related information in our developer docs [1] as well as in the official admin guide [2] -- the latter conten

[openstack-dev] [nova] Bug triage and tag owner list

Hi team, I'd like to share a link [1] to Nova Bug Triage wiki page. This page contains a tag owner list and instructions that allow subscribing not for all nova bugs, but for a certain tag. It would be great if all tags in a table have an owner, so if you are interested in some of them, and could

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On Tue, Oct 11, 2016 at 12:08 PM, Chris Dent wrote: > > Based on the turnout numbers and a bit of unscientific number > crunching on the voting results it seems that the electorate was > rather more engaged this time around. That's _great_. > > As others have said I imagine some significant part

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On 10/11/2016 12:00 PM, Ed Leafe wrote: On Oct 11, 2016, at 10:37 AM, Anita Kuno wrote: Just in case folks care, now is the best time to discuss our election process and suggest options or changes for the next round of elections. I'm not adverse to discussing it I just think the best time

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 to

Re: [openstack-dev] dependency hygiene [was requests-mock]

On Tue, Oct 11, 2016 at 4:02 AM, Davanum Srinivas wrote: > Clay, > > Apologies for the top post. Oh goodness, none needed my friend! > https://github.com/openstack/requirements#global- > requirements-for-openstack-projects > > Eternal wells of gratitude for that read! There was so many good

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On 2016-10-11 12:00 PM, Ed Leafe wrote: On Oct 11, 2016, at 10:37 AM, Anita Kuno wrote: Just in case folks care, now is the best time to discuss our election process and suggest options or changes for the next round of elections. I'm not adverse to discussing it I just think the best time fo

[openstack-dev] [new][senlin] senlin-dashboard 0.5.0 release (newton)

We are amped to announce the release of: senlin-dashboard 0.5.0: Senlin Dashboard This release is part of the newton release series. Download the package from: https://tarballs.openstack.org/senlin-dashboard/ Please report issues through launchpad: https://bugs.launchpad.net/senlin-da

[openstack-dev] [new][openstackclient] osc-lib 1.2.0 release (ocata)

We are delighted to announce the release of: osc-lib 1.2.0: OpenStackClient Library This release is part of the ocata release series. The source is available from: https://git.openstack.org/cgit/openstack/osc-lib Download the package from: https://pypi.python.org/pypi/osc-lib Please

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On 2016-10-11 12:57 PM, Thiago da Silva wrote: On 10/11/2016 12:00 PM, Ed Leafe wrote: On Oct 11, 2016, at 10:37 AM, Anita Kuno wrote: Just in case folks care, now is the best time to discuss our election process and suggest options or changes for the next round of elections. I'm not adver

[openstack-dev] [ironic] weekly subteam report

Hi, Here is this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff between 03 Oct 2016 and 10 Oct 2016) - Ironic: 216 bugs (+11) + 212 wishlist items. 15 new (+9), 173 in progress (+4),

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On 2016-10-11 12:08 PM, Chris Dent wrote: Based on the turnout numbers and a bit of unscientific number crunching on the voting results it seems that the electorate was rather more engaged this time around. That's _great_. As others have said I imagine some significant part of that was because

[openstack-dev] [nova] Options for using trusted certificates in Nova image signature verification

Hi everyone, We are interested in improving user trust in the cloud and are currently working on certificate validation for image signatures in Nova. Users can upload signed images to Glance and then boot them via Nova, with Nova validating the image signature when it downloads the image. Adding c

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On 2016-10-11 12:55 PM, Ruby Loo wrote: On Tue, Oct 11, 2016 at 12:08 PM, Chris Dent wrote: Based on the turnout numbers and a bit of unscientific number crunching on the voting results it seems that the electorate was rather more engaged this time around. That's _great_. As others have said

[openstack-dev] [new][oslo] oslo.policy 1.15.0 release (ocata)

We are glowing to announce the release of: oslo.policy 1.15.0: Oslo Policy library This release is part of the ocata release series. The source is available from: http://git.openstack.org/cgit/openstack/oslo.policy Download the package from: https://pypi.python.org/pypi/oslo.policy P

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On Oct 11, 2016, at 12:17 PM, Anita Kuno wrote: >> There really needs to be a period when a) we know who all the candidates >> are, and b) voting has not yet begun. > > Why? > > The voting period is open for a period of several days, voters have the > ability to vote at any time during that v

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On Tue, 11 Oct 2016, Anita Kuno wrote: * Getting rid of self nomination. Nominations come from the electorate at large. They can be refused of course. What is the current problem with self nomination? (I almost missed this since it was after your valediction) I guess the least roundabout

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On Oct 11, 2016, at 12:26 PM, Anita Kuno wrote: > >> Instead of two week process, make it three: > > Again as I replied to Ed's post, I think we can find options that fit in the > current timeframe. Why do we need a week to nominate? Open it up a month before the election, and close it a week

Re: [openstack-dev] requests-mock

On Tue, Oct 11, 2016 at 5:40 AM, Ian Cordasco wrote: > So, as a core developer > of Requests, I would endorse requests-mock for this category of > dependency. > Excellent; exactly the kind of feedback I was hoping to solicit. If you're looking to add this catagory of dependency - requests-mock

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On Oct 11, 2016, at 12:31 PM, Anita Kuno wrote: > I think one would get a much better sense asking people if they voted when > they see them at summit or other live events and ask them why not if they say > no. As I said in an earlier email, I have done such unscientific polling at recent sum

Re: [openstack-dev] [networking-sfc][devstack][mitaka]

Hi Navdeep, Please see inline. Cathy From: Navdeep Uniyal [mailto:[email protected]] Sent: Tuesday, October 11, 2016 5:42 AM To: [email protected] Subject: [openstack-dev] [networking-sfc][devstack][mitaka] Hi all, I have been trying out networking-sfc to create service

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On 2016-10-11 01:40 PM, Ed Leafe wrote: On Oct 11, 2016, at 12:17 PM, Anita Kuno wrote: There really needs to be a period when a) we know who all the candidates are, and b) voting has not yet begun. Why? The voting period is open for a period of several days, voters have the ability to vot

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On 2016-10-11 01:42 PM, Chris Dent wrote: On Tue, 11 Oct 2016, Anita Kuno wrote: * Getting rid of self nomination. Nominations come from the electorate at large. They can be refused of course. What is the current problem with self nomination? (I almost missed this since it was after your

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On Tue, Oct 11, 2016 at 9:57 AM, Thiago da Silva wrote: > > it would also be nice to have a better place for the questions/answers to > be stored. During last week there was a ton of great discussion, but when > it came to voting time (towards end of the week) it was difficult/time > consuming to

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On 2016-10-11 01:43 PM, Ed Leafe wrote: On Oct 11, 2016, at 12:26 PM, Anita Kuno wrote: Instead of two week process, make it three: Again as I replied to Ed's post, I think we can find options that fit in the current timeframe. Why do we need a week to nominate? Open it up a month before the

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On Tue, Oct 11, 2016 at 10:52 AM, Anita Kuno wrote: > On 2016-10-11 01:40 PM, Ed Leafe wrote: > >> On Oct 11, 2016, at 12:17 PM, Anita Kuno wrote: >> >> There really needs to be a period when a) we know who all the candidates are, and b) voting has not yet begun. >>> Why? >>> >>> The v

Re: [openstack-dev] [rpm-packaging][chef][puppet][salt][openstack-ansible][HA][tripleo][kolla][fuel] Schema proposal for config file handling for services

On Tue, Oct 11, 2016 at 12:40 AM Thomas Bechtold wrote: > Hi, > > > > On Mon, Oct 10, 2016 at 10:07:05AM -0600, Alex Schultz wrote: > > > On Mon, Oct 10, 2016 at 5:03 AM, Thomas Bechtold > wrote: > > > > Hi, > > > > > > > > in the rpm-packaging project we started to package the services and are

Re: [openstack-dev] [neutron] proper cleanup of l3 resources (neutron-netns-cleanup)

Hi, Approach I am following is not cleaning blindly, there is utility in cleanup which I’ll use To get eligible namespace candidates for cleanup (need to deep dive this logic how effective is that) Then will extract id from namespace either using namespace manager or l3 agent code, And call on

Re: [openstack-dev] [rpm-packaging][chef][puppet][salt][openstack-ansible][HA][tripleo][kolla][fuel] Schema proposal for config file handling for services

On Tue, Oct 11, 2016 at 1:39 AM, Thomas Bechtold wrote: > Hi, > > On Mon, Oct 10, 2016 at 10:07:05AM -0600, Alex Schultz wrote: >> On Mon, Oct 10, 2016 at 5:03 AM, Thomas Bechtold wrote: >> > Hi, >> > >> > in the rpm-packaging project we started to package the services and are >> > currently disc

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On 10/11/2016 01:21 PM, Anita Kuno wrote: On 2016-10-11 12:57 PM, Thiago da Silva wrote: On 10/11/2016 12:00 PM, Ed Leafe wrote: On Oct 11, 2016, at 10:37 AM, Anita Kuno wrote: Just in case folks care, now is the best time to discuss our election process and suggest options or changes fo

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On 2016-10-11 02:35 PM, Thiago da Silva wrote: On 10/11/2016 01:21 PM, Anita Kuno wrote: On 2016-10-11 12:57 PM, Thiago da Silva wrote: On 10/11/2016 12:00 PM, Ed Leafe wrote: On Oct 11, 2016, at 10:37 AM, Anita Kuno wrote: Just in case folks care, now is the best time to discuss our el

[openstack-dev] [ovn][neutron] networking-ovn 1.0.0 release (newton) -- port-security

Hi, Please clarify if port security is required to be enabled with newton release when installing OVN. The install.rst says it must be. In many of my use cases I want to disable port security which is how I do currently with devstack. I would like to know if either ovn or neutron will have content

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On 2016-10-11 02:07 PM, Clay Gerrard wrote: On Tue, Oct 11, 2016 at 10:52 AM, Anita Kuno wrote: On 2016-10-11 01:40 PM, Ed Leafe wrote: On Oct 11, 2016, at 12:17 PM, Anita Kuno wrote: There really needs to be a period when a) we know who all the candidates are, and b) voting has not yet b

[openstack-dev] [tripleo] PTG space request

Greetings, I would like to request for some space dedicated to TripleO project for the first OpenStack PTG. https://www.openstack.org/ptg/ The event will happen in February 2017 during the next PTG in Atlanta. Any feedback is welcome, -- Emilien Macchi

Re: [openstack-dev] [ovs-discuss] [ovn][networking-sfc]

The guide is the networking-ovn guide. Not sure what is meant by “port-security”. From networking-sfc point of view, security group is not needed. Thanks, Cathy From: discuss [mailto:[email protected]] On Behalf Of Murali R Sent: Monday, October 10, 2016 2:47 PM To: discuss; OpenS

Re: [openstack-dev] [Trove] trove core team

Thank you Craig for your leadership and hard work in helping shape and guide the Trove community. Wish you good luck and success in everything you do. Regards, Mariam. From: Craig Vyvial To: OpenStack Development Mailing List Date: 10/07/2016 10:25 PM Subject:[op

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

My personal opinion, speaking as a non-candidate, is that it's very likely true name recognition plays a role. In fact if I was to vote I would do so and probably vote for Monty or Doug cause I like how they operate and I'm familiar with them. And if I don't like someone, I won't vote for them. Sel

Re: [openstack-dev] [all][stable] Moving stable/mitaka to Phase-II and liberty to Phase-III

On Tue, Oct 11, 2016 at 08:34:12AM +1100, Tony Breeds wrote: > On Mon, Oct 10, 2016 at 08:42:48AM +0200, Ihar Hrachyshka wrote: > > > I think it would also make sense to *release* on the boundary of the switch; > > so that it’s clear which phase a release followed. > > I agree, I don't really hav

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

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 would be an i

[openstack-dev] [tripleo] website update

A quick update on the tripleo.org website outage today. We are in the process of moving the server to a new host location. Until DNS updates please use the following URL if you want to access the CI status report: http://66.187.229.219/cistatus.html Dan __

Re: [openstack-dev] [Tacker] Presence at PTG Atlanta

Hi, Based on team’s decision in tacker weekly meeting [1], Tacker team has decided to have a virtual developer meetup and not have PTG presence in Atlanta. Given, most of our contributors are geographically spread out, it was decided that the virtual midcycle format would be more appropriate in

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 wo

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

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 since kilo, ya, also

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 s

[openstack-dev] Multinode testing with devstack and neutron broken

Hello everyone, Currently multinode testing + neutron is broken in clouds that use portions of 10.0.0.0/8 for their networking due to route conflicts with devstack + neutron deployments. https://bugs.launchpad.net/bugs/1629133 is tracking the issue for us. I would like to see this get resolved pro

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

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 for [python, java, g

[openstack-dev] [keystone][horizon] keystone/horizon integration session in barcelona

The keystone team had a spare fishbowl session, and we decided to use it to collaborate with the horizon team on a few long standing issues we've had between the two projects. You can view the session online: https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/16907 Details her

Re: [openstack-dev] [keystone][horizon] keystone/horizon integration session in barcelona

Thanks, Steve, this will be a valuable session! On 12 October 2016 at 08:14, Steve Martinelli wrote: > The keystone team had a spare fishbowl session, and we decided to use it > to collaborate with the horizon team on a few long standing issues we've > had between the two projects. > > You can v

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 for [pyt

Re: [openstack-dev] requests-mock

On Tue, Oct 11, 2016 at 10:44 AM, Clay Gerrard wrote: > I'm not really sure what a fixture is this context? > Answered my own question in this case! http://requests-mock.readthedocs.io/en/latest/fixture.html It's one of *these* of course: https://pypi.python.org/pypi/fixtures ___

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

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) event_definitions.yaml

Re: [openstack-dev] [OpenStack-docs] [ironic] Admin guide in-tree?

We are eager to improve our documentation, but I think quite a few of us who work on Ironic documentation have a strong preference to keeping those documents in-tree. This allows us to enforce contributors having documentation changes or additions merge at the same time or in close proximity to

Re: [openstack-dev] [OpenStack-docs] [ironic] Admin guide in-tree?

Hi Jay, I think that's a perfectly reasonable solution for the moment, and hopefully we'll have the new solution up and running as soon as possible. Please let us know if there's anything you could use a hand with. Lana On 12/10/16 09:00, Jay Faulkner wrote: > We are eager to improve our docum

Re: [openstack-dev] [tripleo] website update

On 10/11/2016 02:42 PM, Dan Prince wrote: A quick update on the tripleo.org website outage today. We are in the process of moving the server to a new host location. Until DNS updates please use the following URL if you want to access the CI status report: http://66.187.229.219/cistatus.html

[openstack-dev] Barcelona Summit -- Monday -- openings in command-presence-workshop

Hello Everyone! We have a few slots still available on Monday's Command Presence workshop and are opening out to a broader audience. Please register if interested. Past attendees, despite their many skills and experience, vouched that they had learned a trick or two. https://www.openstack.org/

Re: [openstack-dev] requests-mock

On 11 October 2016 at 16:23, Clay Gerrard wrote: > Greetings! > > Anyone have any experience to share positive or negative using > requests-mock? I see it's been used to replace another dependency that had > some problems in many of the OpenStack python client libraries: > > Added to global requ

Re: [openstack-dev] requests-mock

On 11 October 2016 at 23:40, Ian Cordasco wrote: > -Original Message- > From: Clay Gerrard > Reply: OpenStack Development Mailing List (not for usage questions) > > Date: October 11, 2016 at 00:25:10 > To: OpenStack Development Mailing List > Subject: [openstack-dev] requests-mock > >

Re: [openstack-dev] Multinode testing with devstack and neutron broken

On 11 October 2016 at 14:09, Clark Boylan wrote: > Hello everyone, > > Currently multinode testing + neutron is broken in clouds that use > portions of 10.0.0.0/8 for their networking due to route conflicts with > devstack + neutron deployments. https://bugs.launchpad.net/bugs/1629133 > is tracki

Re: [openstack-dev] Multinode testing with devstack and neutron broken

On Tue, Oct 11, 2016, at 04:32 PM, Armando M. wrote: > On 11 October 2016 at 14:09, Clark Boylan wrote: > > > Hello everyone, > > > > Currently multinode testing + neutron is broken in clouds that use > > portions of 10.0.0.0/8 for their networking due to route conflicts with > > devstack + neutr

Re: [openstack-dev] requests-mock

On Tue, Oct 11, 2016 at 4:24 PM, Jamie Lennox wrote: > > So I'm not going to comment too much on the quality of the library as i > obviously think it's good > acahcpahch, no worries. Your insights are invaluable - thanks for taking the time to connect some dots for me - i'm starting to get up t

[openstack-dev] [tripleo] Scaling-up the team with Squads

It has been some weeks I have been thinking how TripleO project could scale-up the way we work together. Over the cycles, we have more contributors, more projects, I think it's time to revisit our organization. Here's the proposal: https://review.openstack.org/385201 Feel free to review it prior

  1   2   >