Re: [openstack-dev] [Senlin] Project weekly meeting starts June 16 UTC1300

Glad to see the schedule is determined. +1 for it. Regards, Xuhaiwei -Original Message- From: Qiming Teng [mailto:teng...@linux.vnet.ibm.com] Sent: Thursday, June 11, 2015 1:12 PM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [Senlin] Project weekly meeting starts June 1

Re: [openstack-dev] Can not connect to host review.openstack.orgport 29418

Thx for your help. I resolve this problem by change gerrit url. Command like this: git remote set-url gerrit https://changzhi:gT1w.openstack.org/stackforge/tacker -- Original -- From: "Tom Fifield"; Date: Thu, Jun 11, 2015 11:56 AM To: "openstack-dev";

[openstack-dev] [cloudpulse] Reminder: Team meeting June 11

Hi, Meeting: Thursday at 1600 UTC in #openstack-meeting-3 Agenda: https://wiki.openstack.org/wiki/Meetings/cloudpulse Thanks Vinod. __ OpenStack De

Re: [openstack-dev] [Manila] Ask for help on supportting the 3-rd party CI for HDFS driver

Hi all, > > Thanks Jeremy. I assume Chen could follow this example to add a > > job for the HDFS driver? > > > > https://review.openstack.org/#/c/188744/ > > That's a fine short-form answer. The longer answer is to solicit > input from some of the people who have done similar work, so that > mi

Re: [openstack-dev] [all][python3] use of six.iteritems()

On 11 June 2015 at 17:16, Robert Collins wrote: > This test conflates setup and execution. Better like my example, ... Just had it pointed out to me that I've let my inner asshole out again - sorry. I'm going to step away from the thread for a bit; my personal state (daughter just had a routine

Re: [openstack-dev] Proposing Brian Haley to Neutron L3 Core Reviewer Team

Excellent addition to the team! I am not part of the L3 focus team but I wanted to share my opinion. Edgar On 6/10/15, 12:11 PM, "Carl Baldwin" wrote: >Folks, > >As the Neutron L3 Lieutenant [1] under the PTL, Kyle, I'd like to >propose Brian Haley as a member of the Neutron L3 core review

Re: [openstack-dev] [Magnum] Discuss configurable-coe-api-port Blueprint

Kai, +1 for add it to baymodel, but I don’t see many use cases when people need to change it. And if they really need to change it they can always modify heat template. -1 for opening it just for admins. I think everyone who create a model should be able specify it the same way as dns-nameserve

Re: [openstack-dev] [all][python3] use of six.iteritems()

On 11 June 2015 at 15:48, Dolph Mathews wrote: > tl;dr .iteritems() is faster and more memory efficient than .items() in > python2 > > > Using xrange() in python2 instead of range() because it's more memory > efficient and consistent between python 2 and 3... > > # xrange() + .items() > python -m

Re: [openstack-dev] [Magnum] Discuss configurable-coe-api-port Blueprint

I think that we have a similar bp before: https://blueprints.launchpad.net/magnum/+spec/override-native-rest-port I have some discussion before with Larsks, it seems that it does not make much sense to customize this port as the kubernetes/swarm/mesos cluster will be created by heat and end user

[openstack-dev] [Security][VMT] OSSG CoreSec Positions

All, OSSG CoreSec is a private group on Launchpad, it consists of established Security Project team members who are on hand to be called in by the VMT to consult on vulnerabilities and discuss possible mitigations. We require two new members, as with other project ‘cores’ I suggest a nominatio

Re: [openstack-dev] [Neutron] Metaplugin deprecation in Liberty

+1 Edgar From: Hirofumi Ichihara Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Wednesday, June 10, 2015 at 7:20 PM To: "OpenStack Development Mailing List (not for usage questions)" Subject: Re: [openstack-dev] [Neutron] Metaplugin deprecation in Liberty On 2015

Re: [openstack-dev] [Senlin] Project weekly meeting starts June 16 UTC1300

Forgot to mention: Meeting agenda: https://wiki.openstack.org/wiki/Meetings/SenlinAgenda Regards, Qiming > Hi, all, > > After some discussions with Senlin developers on the #senlin IRC > channel, we have decided to hold a weekly IRC meeting for contributors > to sync up progress and plans. Ev

[openstack-dev] [Senlin] Project weekly meeting starts June 16 UTC1300

Hi, all, After some discussions with Senlin developers on the #senlin IRC channel, we have decided to hold a weekly IRC meeting for contributors to sync up progress and plans. Everyone is welcomed to join the team. Frequency: Weekly Weekday: Tuesday Timeslot: 1300 UTC Venue: #openstack-meeting P

Re: [openstack-dev] Can not connect to host review.openstack.org port 29418

On 11/06/15 11:33, 苌智 wrote: > I met problem when run "git review". It says that " ssh: connect to host > review.openstack.org port 29418: No route to host ". There is no > response when I run "telnet review.openstack.org 29418". And my screen > only displays "Trying 104.130.159.134...". Does anyon

Re: [openstack-dev] [all][python3] use of six.iteritems()

tl;dr *.iteritems() is faster and more memory efficient than .items() in python2* Using xrange() in python2 instead of range() because it's more memory efficient and consistent between python 2 and 3... # xrange() + .items() python -m timeit -n 20 for\ i\ in\ dict(enumerate(xrange(100))).ite

[openstack-dev] [puppet] [fuel] more collaboration request

Hi, Before reading this e-mail, please keep in mind: * I have a lot of admiration for Fuel and since I'm working on OpenStack Installers (at eNovance and now Red Hat), Fuel is something I always consider a good product. * This e-mail is about Fuel and Puppet, nothing about Mirantis. * I'm writing

Re: [openstack-dev] Can not connect to host review.openstack.org port 29418

On Thu, Jun 11, 2015 at 11:33:14AM +0800, 苌智 wrote: > I met problem when run "git review". It says that " ssh: connect to host > review.openstack.org port 29418: No route to host ". There is no response > when I run "telnet review.openstack.org 29418". And my screen only displays > "Trying 104.130.

[openstack-dev] Can not connect to host review.openstack.org port 29418

I met problem when run "git review". It says that " ssh: connect to host review.openstack.org port 29418: No route to host ". There is no response when I run "telnet review.openstack.org 29418". And my screen only displays "Trying 104.130.159.134...". Does anyone meets the same problem as me?

Re: [openstack-dev] [third-party][infra] Common OpenStack CI Solution - 'Jenkins' live

On 06/10/2015 08:05 PM, Asselin, Ramy wrote: > All, > > I’m please to say that there are now 2 components merged in the > puppet-openstackci repo [1] > This means 3rd party ci operators to use the same scripts that the OpenStack > Infrastructure team uses in the official ‘Jenkins’ CI system for:

Re: [openstack-dev] [Neutron] Metaplugin deprecation in Liberty

> On 2015/06/11, at 11:05, Kyle Mestery wrote: > > On Wed, Jun 10, 2015 at 8:56 PM, Hirofumi Ichihara > mailto:ichihara.hirof...@lab.ntt.co.jp>> > wrote: > Hi folks, > > I have maintained metaplugin in Neutron. > The plugin enables users to use multiple plugins at the same time. > However, we

Re: [openstack-dev] [OpenStack Foundation] Openstack Diversity Working Group

It turns out that if you accidentally forgot to enable timezone support when creating a doodle poll (the link isn't exactly the easiest to remember), you can't turn it on later. Regards, Tom On 11/06/15 03:15, Tristan Goode wrote: > Why not just enable time zone support for the doodle poll? Th

Re: [openstack-dev] [Neutron] Metaplugin deprecation in Liberty

On Wed, Jun 10, 2015 at 8:56 PM, Hirofumi Ichihara < ichihara.hirof...@lab.ntt.co.jp> wrote: > Hi folks, > > I have maintained metaplugin in Neutron. > The plugin enables users to use multiple plugins at the same time. > However, we can use ML2 plugin in order to do now. > I know that there is nob

[openstack-dev] [Neutron] Metaplugin deprecation in Liberty

Hi folks, I have maintained metaplugin in Neutron. The plugin enables users to use multiple plugins at the same time. However, we can use ML2 plugin in order to do now. I know that there is nobody using metaplugin and besides, It’s still experimental[1]. Therefore, I want to deprecate metapugin i

Re: [openstack-dev] [puppet] drop monolithic plugins in neutron module

I was going to ask about that, thanks for clarifying Kevin. :) On Wed, Jun 10, 2015 at 7:11 PM, Kevin Benton wrote: > It's important to note that this patch is about dropping the linux bridge > and OVS monolithic plugins, not ALL monolithic plugins. :) > > On Wed, Jun 10, 2015 at 4:20 PM, Emilie

[openstack-dev] [Magnum] Discuss configurable-coe-api-port Blueprint

I’m moving this whiteboard to the ML so we can have some discussion to refine it, and then go back and update the whiteboard. Source: https://blueprints.launchpad.net/magnum/+spec/configurable-coe-api-port @Sdake and I have some discussion now, but may need more input from your side. 1. keep

Re: [openstack-dev] [all][python3] use of six.iteritems()

> Date: Wed, 10 Jun 2015 21:33:44 +1200 > From: robe...@robertcollins.net > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [all][python3] use of six.iteritems() > > On 10 June 2015 at 17:22, gordon chung wrote: > > maybe the suggestion should be "don't blindly apply six.i

Re: [openstack-dev] [Neutron] service chaining feature development meeting at 10am pacific time June 11

Here is the updated agenda for tomorrow's meeting: 1. Update on last meeting's action items 2. Neutron port chain API for SFC 3. Unified API and data model for flow classifier that can be used for SFC, QoS, Packet forwarding etc. 4. Summary on the SFC Feature project scope

Re: [openstack-dev] [puppet] drop monolithic plugins in neutron module

It's important to note that this patch is about dropping the linux bridge and OVS monolithic plugins, not ALL monolithic plugins. :) On Wed, Jun 10, 2015 at 4:20 PM, Emilien Macchi wrote: > Hi, > > Monolithic plugins have been dropped in Neutron tree since Juno, I think > it's time to drop the c

[openstack-dev] [Tacker][Telco][NFV] Reminder: Tacker (VNF Manager) Team Meeting

Meeting on #openstack-meeting @ 1600UTC (9am PDT) Agenda can be found here: https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_June_11.2C_2015 Thanks, - Stephen __ OpenStack Development Mailing List (not for usage questi

[openstack-dev] [third-party][infra] Common OpenStack CI Solution - 'Jenkins' live

All, I’m please to say that there are now 2 components merged in the puppet-openstackci repo [1] This means 3rd party ci operators to use the same scripts that the OpenStack Infrastructure team uses in the official ‘Jenkins’ CI system for: 1. Log Server 2. Jenkins Big thanks to T

Re: [openstack-dev] [app-catalog][infra] Stale entries

On 2015-06-10 15:43:51 -0700 (-0700), Christopher Aedo wrote: [...] > Let me know if zuul is able to send to a distribution list that is > core reviewers for a project - otherwise I will put in the request for > the mailing list. Right now it needs to be a single E-mail address, and we don't have

[openstack-dev] [puppet] drop monolithic plugins in neutron module

Hi, Monolithic plugins have been dropped in Neutron tree since Juno, I think it's time to drop the code from puppet-neutron (I guess everyone is using ML2, at least I hope for them). If anyone is running master against OpenStack Icehouse, please raise your voice here and please vote in this patch

[openstack-dev] [Murano] Does Murano support nested HOT templates?

Just wondering if Murano supports nested templates. For example, the autoscaling template at https://github.com/openstack/heat-templates/blob/master/hot/autoscaling.yaml references the template at https://github.com/openstack/heat-templates/blob/master/hot/lb_server.yaml. When I create the pack

Re: [openstack-dev] [app-catalog][infra] Stale entries

On Wed, Jun 10, 2015 at 3:41 PM, Christopher Aedo wrote: > I think it makes sense (as James suggested) for us to set up an > additional mailing list for this, unless Zuul can just send the output > to core reviewers? As JEREMY/fungi suggested I mean :/ Let me know if zuul is able to send to a di

Re: [openstack-dev] [app-catalog][infra] Stale entries

On Sat, Jun 6, 2015 at 7:15 AM, Georgy Okrokvertskhov wrote: > This is great. It means that we can use existing OpenStack approach rather > then reinventing the wheel. > I think I will be able to create a simple script for URLs verification. It > looks pretty straightforward as catalog is in machi

Re: [openstack-dev] [Neutron] service chaining feature development meeting at 10am pacific time June 11

Add the following item to the agenda: unified data model for flow classifiers Thanks, Cathy From: Cathy Zhang Sent: Wednesday, June 10, 2015 3:12 PM To: OpenStack Development Mailing List (not for usage questions); Cathy Zhang Subject: [openstack-dev] [Neutron] service chaining feature developme

Re: [openstack-dev] [Neutron] API Extensions - Namespace URLs

Thanks for asking about this Sean! ;) Sean M. Collins wrote: On Tue, Jun 09, 2015 at 05:21:18PM EDT, Kevin Benton wrote: I wasn't planning on wiping them out for now since I'm leveraging a lot of the extension loading that exists so someone can remove the namespaces if they want. OK -

[openstack-dev] [Neutron] service chaining feature development meeting at 10am pacific time June 11

Hello everyone, Our next weekly IRC meeting for the OpenStack service chain feature development is 10am pacific time June 11 (UTC 1700, hope I am doing the correct time conversion this time) Following is the meeting info: Weekly on Thursday at 1700 UTC

Re: [openstack-dev] [neutron] Service Chain project IRC meeting minutes - 06/04/2015

Hi Armando, Sorry to reply late since I just saw these emails due to improper filter setup in my mailbox. Please see inline. Thanks, Cathy From: Armando M. [mailto:arma...@gmail.com] Sent: Thursday, June 04, 2015 6:06 PM To: OpenStack Development Mailing List (not for usage questions) Subject:

Re: [openstack-dev] [Ironic] weekly meetings and sub-team reports and people

On Thu, Jun 11, 2015 at 4:03 AM, Jim Rollenhagen wrote: > I'd really like to investigate moving this meeting to a different time. > While it is beneficial for the sake of inclusivity, I tend to see not > many cores attending (if at all), and usually not a ton of discussion. > Well, anything in t

Re: [openstack-dev] [all] Switching to SQLAlchemy 1.0.x

I think it would first require a version of oslo.db to be released inside stable/kilo's bounds that uncapped SQLAlchemy first since the requirement in the version of oslo.db installed is what you see here http://logs.openstack.org/62/190062/2/check/check-tempest-dsvm-neutron-full /f6baf92/logs/devs

Re: [openstack-dev] [javascript] Linters

Michael, Maybe you should start this thread again with a link to the full thread but add all the projects into subject (e.g. [horizon]). Otherwise quite a few people may not see it. You are right that the John Papa guidelines are definitely targeted at angular and not general style. They are

Re: [openstack-dev] [all] Switching to SQLAlchemy 1.0.x

On 6/10/15 5:18 PM, Thomas Goirand wrote: On 06/10/2015 04:52 PM, Mike Bayer wrote: whew! :) Do you know why it fails with Kilo? https://review.openstack.org/#/c/190062/ I noticed this, I don't know very well how the requirements get distributed around but seems like it is not happening

Re: [openstack-dev] [all] Switching to SQLAlchemy 1.0.x

On 06/10/2015 04:52 PM, Mike Bayer wrote: > > > On 6/10/15 3:26 AM, Thomas Goirand wrote: >> Hi Mike, >> >> Thanks a lot for your quick reply which is very useful to me. >> >> On 06/09/2015 07:08 PM, Mike Bayer wrote: >>> On 6/9/15 9:26 AM, Thomas Goirand wrote: Hi, The python-sqla

Re: [openstack-dev] Online Migrations.

> Well as long as you want to be able to load data and perform updates on > Instance.name using normal ORM patterns, you'd still have that column > mapped, if you want to put extra things into it to signal your migration > tool, there is an .info dictionary available on the Column that you can > us

Re: [openstack-dev] Online Migrations.

On 6/10/15 4:34 PM, Dan Smith wrote: The remaining work is to have a way of preventing database contracts Foreign Keys. I'm not sure if SQLAlchemy will balk at this or not, but we could do something like: class NameRemovedCondition(object): def satisfied(self): # Check t

Re: [openstack-dev] Online Migrations.

> I like the idea of having a named condition, but the issue is how to maintain > and control multiple of these conditions in a system that will use model > against current schema to determine changes. It's not about having a named condition, it's about having a single condition for a given sche

Re: [openstack-dev] [neutron] Service Chain project IRC meeting minutes - 06/04/2015

Hi Paul, Sure. Thanks for the reminder. Cathy -Original Message- From: Paul Carver [mailto:pcar...@paulcarver.us] Sent: Friday, June 05, 2015 4:22 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] Service Chain project IRC meetin

Re: [openstack-dev] Online Migrations.

I have removed my -1 requesting to hold till this request was address, lets try to move forward with getting this patchset merged and then we can address this request. -Ph On Jun 10, 2015, at 4:47 PM, Andrew Laski mailto:and...@lascii.com>> wrote: On 06/10/15 at 01:34pm, Dan Smith wrote: The re

Re: [openstack-dev] Online Migrations.

On 06/10/15 at 01:34pm, Dan Smith wrote: The remaining work is to have a way of preventing database contracts from running until data migrations that the column interacts with are complete, this is not an easy problem to solve as the goal of the online migrations is to do pure model based schema

Re: [openstack-dev] Online Migrations.

I like the idea of having a named condition, but the issue is how to maintain and control multiple of these conditions in a system that will use model against current schema to determine changes. I also agree that we should get the current patch in as soon as possible and can move my -1 as a ho

[openstack-dev] [Glance] [all] python-glanceclient release 0.19.0

The python-glanceclient release management team is pleased to announce: Release of python-glanceclient version 0.19.0 Please find the details related to the release at: https://launchpad.net/python-glanceclient/liberty/0.19.0

Re: [openstack-dev] Online Migrations.

> The remaining work is to have a way of preventing database contracts > from running until data migrations that the column interacts with are > complete, this is not an easy problem to solve as the goal of the > online migrations is to do pure model based schema migrations and > there is no way of

Re: [openstack-dev] Proposing Brian Haley to Neutron L3 Core Reviewer Team

+1 Brian will be a great addition for L3 On Wed, Jun 10, 2015, Carl Baldwin wrote: > Folks, > > As the Neutron L3 Lieutenant [1] under the PTL, Kyle, I'd like to > propose Brian Haley as a member of the Neutron L3 core reviewer team. > Brian has been a long time contributor in Neutron showing ex

Re: [openstack-dev] [nova] vif type libvirt-network

Hi Ian, Thanks for your reply! On 10/06/15 21:07, Ian Wells wrote: I don't see a problem with this, though I think you do want plug/unplug calls to be passed on to Neutron so that has the opportunity to set up the binding from its side (usage >0) and tear it down when you're done with it (usage

Re: [openstack-dev] [openstack-operators][openstack][chef] Pre-release of knife-openstack is out (1.2.0.rc1)

> On Jun 4, 2015, at 6:12 PM, JJ Asghar wrote: > > I have cut a new release of the knife-openstack[1] gem today. We have a > couple new features[2] which has been asked for a while. I have pushed another pre-release (1.2.0.rc2) of knife-openstack. The main change is support for the `—bootst

[openstack-dev] [oslo] Adopt mox3

Oslo folks, everyone, mox3 needs to be maintained since some of our projects use it and we have it in our global requirements. Here's the proposal from Doug - https://review.openstack.org/#/c/190330/ Any objections? Please chime in here or on the review. thanks, dims -- Davanum Srinivas :: ht

[openstack-dev] Online Migrations.

All, I am taking over work on https://review.openstack.org/#/c/154521/ from Johanness and have spent some time today discussing the current patchset and what is remaining with Dan and Johannes. I wanted to broach the topic of the remaining development with the lists to make sure we go in the

Re: [openstack-dev] [nova] vif type libvirt-network

I don't see a problem with this, though I think you do want plug/unplug calls to be passed on to Neutron so that has the opportunity to set up the binding from its side (usage >0) and tear it down when you're done with it (usage <1). There may be a set of races you need to deal with, too - what ha

Re: [openstack-dev] [Openstack-operators] [ops][tags][packaging] [tc] ops:packaging tag - a little common sense, please

Forgive the top posting. Thank you Jay for your clarification and apology. I wrote the piece below **before** you sent out your email this afternoon, so again this is nothing personal and not targeted at any **specific** person. With that said, I still think that what I have to say is still

Re: [openstack-dev] [neutron] Mechanism drivers and Neutron server forking?

On Wed, Jun 10, 2015 at 2:25 PM, Neil Jerram wrote: > > > On 08/06/15 22:02, Kevin Benton wrote: > >> This depends on what initialize is supposed to be doing. If it's just a >> one-time sync with a back-end, then I think calling it once in each >> child process might not be what we want. >> >> I

Re: [openstack-dev] [neutron] Mechanism drivers and Neutron server forking?

On 08/06/15 22:02, Kevin Benton wrote: This depends on what initialize is supposed to be doing. If it's just a one-time sync with a back-end, then I think calling it once in each child process might not be what we want. I left a comment on Terry's patch. I think we should just use the callback

Re: [openstack-dev] Proposing Brian Haley to Neutron L3 Core Reviewer Team

+1 - Original Message - > Folks, > > As the Neutron L3 Lieutenant [1] under the PTL, Kyle, I'd like to > propose Brian Haley as a member of the Neutron L3 core reviewer team. > Brian has been a long time contributor in Neutron showing expertise > particularly in IPv6, iptables, and Linux

Re: [openstack-dev] Proposing Brian Haley to Neutron L3 Core Reviewer Team

On Wed, Jun 10, 2015 at 2:11 PM, Carl Baldwin wrote: > Folks, > > As the Neutron L3 Lieutenant [1] under the PTL, Kyle, I'd like to > propose Brian Haley as a member of the Neutron L3 core reviewer team. > Brian has been a long time contributor in Neutron showing expertise > particularly in IPv6,

Re: [openstack-dev] [nova] vif type libvirt-network

On 10/06/15 15:47, Andreas Scheuring wrote: Hi Daniel, Neil and others, I was thinking about introducing libvirt-network as a new vif type to nova. It can be used when Neutron prepares a libvirt network for attaching guests. Would you see any general concerns with such an approach? Anything tha

[openstack-dev] Proposing Brian Haley to Neutron L3 Core Reviewer Team

Folks, As the Neutron L3 Lieutenant [1] under the PTL, Kyle, I'd like to propose Brian Haley as a member of the Neutron L3 core reviewer team. Brian has been a long time contributor in Neutron showing expertise particularly in IPv6, iptables, and Linux kernel matters. His knowledge and involvemen

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

Hi Dave, Ah, I did misunderstand. Thanks for clarifying. Kevin From: Dave Walker [em...@daviey.com] Sent: Wednesday, June 10, 2015 9:32 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [all] [stable] No longe

Re: [openstack-dev] [Manila] Ask for help on supportting the 3-rd party CI for HDFS driver

On 2015-06-10 18:20:24 + (+), yang, xing wrote: > Thanks Jeremy. I assume Chen could follow this example to add a > job for the HDFS driver? > > https://review.openstack.org/#/c/188744/ That's a fine short-form answer. The longer answer is to solicit input from some of the people who hav

Re: [openstack-dev] [cinder][nova] modeling connection_info with a versioned object in os-brick

On 06/10/2015 08:40 AM, Matt Riedemann wrote: This is a follow-on to the thread [1] asking about modeling the connection_info dict returned from the os-initialize_connection API. The more I think about modeling that in Nova, the more I think it should really be modeled in Cinder with an oslo.v

Re: [openstack-dev] [javascript] Linters

On 11 June 2015 at 03:29, Michael Krotscheck wrote: > > > On Tue, Jun 9, 2015 at 3:37 PM Robert Collins > wrote: > There are two package managers in the JavaScript world right now, one that > focuses on node.js/server dependencies (karma, lint, express, etc), and one > that focuses on in-browser

Re: [openstack-dev] [Ironic] weekly meetings and sub-team reports and people

On Tue, Jun 09, 2015 at 04:33:41PM -0400, Ruby Loo wrote: > Hi, > > I noticed (from reading the logs[1]) that there weren't many folks in this > week's weekly meeting. And no cores attended. And the sub-team reports (in > our etherpad[2]) were woefully lacking. I guess that means only driver > dev

Re: [openstack-dev] [Manila] Ask for help on supportting the 3-rd party CI for HDFS driver

Thanks Jeremy. I assume Chen could follow this example to add a job for the HDFS driver? https://review.openstack.org/#/c/188744/ Thanks, Xing -Original Message- From: Jeremy Stanley [mailto:fu...@yuggoth.org] Sent: Wednesday, June 10, 2015 11:40 AM To: OpenStack Development Mailing

Re: [openstack-dev] [ops][tags][packaging] ops:packaging tag - a little common sense, please

Jay Pipes wrote: In short, I would love it if the Ops Tags team would stick with binary tag definitions -- a tag should mean one thing and one thing only. I absolutely agree Jay. I think the path that is currently being pursued adds a lot of challenges without appropriate offsetting benefits.

[openstack-dev] [ops][tags][packaging] ops:packaging tag - a little common sense, please

Cross-posting to -operators and -dev because this involves *packagers* of OpenStack, as well as operators who use those packages. Hello Operators, First, let me start out by saying if you were offended by my snarky comments at yesterday's TC meeting [1] regarding the direction of the Ops Tags

Re: [openstack-dev] [Openstack] [OpenStack Foundation] Openstack Diversity Working Group

Doodle does this automatically. At least it presented me with what appeared to be US East times. There is a box on the upper right that tells you the time zone and lets you change it. Pete On Wed, 2015-06-10 at 23:43 +0800, Tom Fifield wrote: > If anyone needs help with the timezone conversion,

Re: [openstack-dev] [kolla] Proposal for changing 1600UTC meeting to 1700 UTC

After some upstream discussion, moving the meeting from 1600 to 1700 UTC does not seem very popular. It was brought up that changing the time to 16:30 UTC could accommodate more people. For the people that attend the 1600 UTC meeting time slot can you post further feedback to address this? Tha

Re: [openstack-dev] [ceilometer] polling agent configuration speculation

On Tue, 9 Jun 2015, gordon chung wrote: i still like the idea of splitting polling and processing task. pros: - it moves load off poll agents and onto notificaiton agent - we essentially get free healthcheck events by doing this con: to play devil's advocate. the one down side is that now ther

Re: [openstack-dev] [Keystone] Midcycle

Hi Adam, Do you have any more information on the Boston University dorm situation? On Tue, Jun 9, 2015 at 1:25 PM, Adam Young wrote: > Keystone Liberty Midcycle Meetup > > Time and Location > > When: July 15-17 (Wed-Fri) > > Where: Boston University, Boston, MA, USA > > > Keystone Midcycle Wi

Re: [openstack-dev] [ceilometer] polling agent configuration speculation

On Tue, 9 Jun 2015, Luo Gangyi wrote: In current, ceilometer load pollsters by agent namespace, So do you mean you want load pollsters one by one through their name(maybe defined in pipeline.yaml)? If loading all pollsters in one time do not cost much, I think your change is bit unnecessary. Bu

[openstack-dev] [murano] backporting changes to stable/juno and stable/kilo

Hi all. I’ve been looking through the bugs/fixes we’ve made during kilo cycle. Some of them are worthy of being backported to stable/juno. And some of the fixes we’ve already made in liberty are worthy of being backported to stable/kilo. Since we’ve agreed on using tags for bugs I’ve marked tho

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

On 10 June 2015 at 17:06, Fox, Kevin M wrote: > So... as an op, without release notes, how am I supposed to figure out the > proper upgrade procedure's when you often have to lockstep, in the right > order, nova+neutron upgrades (or other project combinations)? > > Thanks, > Kevin Hi Kevin, I

[openstack-dev] Announcing Gertty 1.2.0

Announcing Gertty 1.2.0 === Gertty is a console-based interface to the Gerrit Code Review system. Gertty is designed to support a workflow similar to reading network news or mail. It syncs information from Gerrit to local storage to support disconnected operation and easy man

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

So... as an op, without release notes, how am I supposed to figure out the proper upgrade procedure's when you often have to lockstep, in the right order, nova+neutron upgrades (or other project combinations)? Thanks, Kevin From: Thomas Goirand [z...@debi

Re: [openstack-dev] [cinder][nova] modeling connection_info with a versioned object in os-brick

On Wed, Jun 10, 2015 at 10:40:02AM -0500, Matt Riedemann wrote: > This is a follow-on to the thread [1] asking about modeling the > connection_info dict returned from the os-initialize_connection API. > > The more I think about modeling that in Nova, the more I think it should > really be modeled

Re: [openstack-dev] [keystone][barbican] Regarding exposing X-Group-xxxx in token validation

We're aiming for a Spec "Proposal" Freeze deadline for Liberty of June 23rd, but are requiring that specs are approved by our spec reviewers by that date. The spec [1] is currently pretty straightforward and provides us several benefits, so I don't expect it to be a complicated process, but is curr

Re: [openstack-dev] [Nova] Liberty Process, Deadlines and Dates for Nova

On 4 June 2015 at 12:42, John Garbutt wrote: > Hi, > > Following up from nova-meetings and this summit session: > https://etherpad.openstack.org/p/YVR-nova-liberty-process > With that in mind, does this seem like a good idea? > June 12: spec review day (to be confirmed) Note this is happening

Re: [openstack-dev] [OpenStack Foundation] Openstack Diversity Working Group

If anyone needs help with the timezone conversion, I recommend http://www.timeanddate.com/worldclock/meeting.html Just put in "Portland" and your nearest city into the boxes and you'll get an hour-by-hour breakdown :) On 10/06/15 23:39, Barrett, Carol L wrote: > The Doodle time zone doesn’t seem

Re: [openstack-dev] Openstack Diversity Working Group

The Doodle time zone doesn't seem to be appearing in the local timebased upon the viewer. Sorry - The time zone is US/Pacific time (UTC-7), you'll need to do your own conversion. Thanks Carol From: Sousou, Imad [mailto:imad.sou...@intel.com] Sent: Tuesday, June 09, 2015 11:34 AM To: foundat...

Re: [openstack-dev] [Manila] Ask for help on supportting the 3-rd party CI for HDFS driver

On 2015-06-10 14:39:46 + (+), yang, xing wrote: > You can ask if OpenStack Infrastructure team can set up CI for > this driver. They have set up CI's for a few Cinder drivers based > on open source storage systems. To be fair, the Infra team hasn't really written the jobs to test those, bu

[openstack-dev] [cinder][nova] modeling connection_info with a versioned object in os-brick

This is a follow-on to the thread [1] asking about modeling the connection_info dict returned from the os-initialize_connection API. The more I think about modeling that in Nova, the more I think it should really be modeled in Cinder with an oslo.versionedobject since it is an API contract wit

Re: [openstack-dev] [keystone][barbican] Regarding exposing X-Group-xxxx in token validation

Hello folks, Thanks for the consideration of this feature. Does it seem realistic for a Liberty release of Keystone middleware to expose X-Group-Ids, or would this be an M and beyond sort of thing? Thanks, John From: Henry Nash mailto:henryna...@mac.com>> Reply-To: "OpenStack Development Mail

Re: [openstack-dev] [javascript] Linters

On Tue, Jun 9, 2015 at 3:37 PM Robert Collins wrote: > On 10 June 2015 at 04:01, Michael Krotscheck wrote: > > Well, it looks like everyone has disqualified jslint and jshint, so let's > > just make a decision there and remove them from the running. Unless I > hear a > > compelling reason to use

Re: [openstack-dev] [neutron] Mechanism drivers and Neutron server forking?

There are two classes of behavior that need to be handled: 1) There are things that can only be done after forking like setting up connections or spawning threads. 2) Some things should only be done once regardless of number of forks, like syncing. Even when you just want something to happen on

Re: [openstack-dev] [murano] shellcheck all .sh scripts in murano-deployment

Thanks for comment and suggestion! there is also shutil2 framework for unit testing over shell scripts. We shall consider it whether it could bring us value for the effort. I personally have no strong opinion about that. Little contradiction to my previous mail:-) Regards Filip On 06/10/2

Re: [openstack-dev] [all] Switching to SQLAlchemy 1.0.x

On 6/10/15 3:26 AM, Thomas Goirand wrote: Hi Mike, Thanks a lot for your quick reply which is very useful to me. On 06/09/2015 07:08 PM, Mike Bayer wrote: On 6/9/15 9:26 AM, Thomas Goirand wrote: Hi, The python-sqlalchemy package has been uploaded to Debian Experimental, and is about to be

[openstack-dev] [nova] vif type libvirt-network

Hi Daniel, Neil and others, I was thinking about introducing libvirt-network as a new vif type to nova. It can be used when Neutron prepares a libvirt network for attaching guests. Would you see any general concerns with such an approach? Anything that I need to consider with libvirt networks in

Re: [openstack-dev] [Manila] Ask for help on supportting the 3-rd party CI for HDFS driver

Hi Chen, You can ask if OpenStack Infrastructure team can set up CI for this driver. They have set up CI's for a few Cinder drivers based on open source storage systems. Thanks, Xing From: Li, Chen [mailto:chen...@intel.com] Sent: Wednesday, June 10, 2015 3:48 AM To: OpenStack Development Ma

Re: [openstack-dev] [cinder][nova] Is volume connection_info modeled/documented anywhere?

On Wed, Jun 10, 2015 at 7:54 AM, Matt Riedemann wrote: > While investigating/discussing bug 1463525 [1] I remembered how little I > know about what can actually come out of the connection_info dict returned > from the os-initialize_connection cinder API call. > > So we added some debug logging in

[openstack-dev] [neutron][fwaas] FWaaS IRC meetings to happen alternate Wed (no mtg today).

Hi All: Just a reminder to FWaaS meeting attendees, as discussed in last weeks FWaaS IRC [1], with all the PTO’s going on and the need for time to build up on the SG alignment discussions – it was felt that it would be good to go to an alternate week format. So the next meeting will be on Jun 1

Re: [openstack-dev] [packaging] Adding packaging as an OpenStack project

On Wed, Jun 10, 2015 at 5:24 PM, Ian Cordasco wrote: > > > On 6/10/15, 09:12, "Thomas Goirand" wrote: > > >On 06/10/2015 12:25 PM, Dave Walker wrote: > >> The initial core reviewers was seeded by representatives of distro's and > >> vendors to get their input on viability in distro's. > > > >Rea

  1   2   >