Re: [openstack-dev] [Ironic][oslo] Stepping down from oslo-ironic liaison

Thank you Ghe! Miss you! On Wed, May 27, 2015 at 9:04 AM, Tan, Lin wrote: > Hi Doug and guys, > > I would like to work as oslo-ironic liasison to sync Ironic with Oslo. > I will attend the regular Oslo meeting for sure. My IRC name is lintan, and > Launchpad id is tan-lin-good > > Thanks > > Tan

Re: [openstack-dev] [Horizon] dashboard-app split in horizon

Went through the files myself and I concur. Most of these files define pieces specific to our implementation of the dashboard, so should be moved. I’m not entirely sure on where _messages should sit. As we move forward, won’t that file just end up as a element and nothing more? Maybe I’m misin

Re: [openstack-dev] [Fuel] Setting cluster status when provisioning a node

Roman, This looks like a great solution to me, and I like your proposal very much. The status of cluster derived directly from statuses of nodes is exactly what I was thinking about. I have to notes to the proposal, and I can copy them to etherpad if you think they deserve it: 1) status name 'op

Re: [openstack-dev] [Manila] About how to hide the dummy destination record during migration

Hello Vincent Hou, We, Manila folks, are about to merge one of new features - "private driver storage" [1]. That is going to serve for not-user facing data storage related to any resource that can be reached by both - API and share driver. And in case of share migration, it will be possible to av

Re: [openstack-dev] [Openstack] PCI pass-through SRIOV

Hi, I resolved it by adding or uncommenting "/dev/vfio/vfio" in cgroup_device_acl list in /etc/libvirtd/qemu.conf file and restart libvird service . Now when I listed nova instances am not getting any Network shown [stack@Controller images]$ nova list +--+-

Re: [openstack-dev] [neutron] - dnsmasq 'dhcp-authoritative' option broke multiple DHCP servers

I have verified that the following fixes the issue for me locally: https://review.openstack.org/#/c/185486/ This works for rescheduled DHCP instances, multiple DHCP instances, and restarted DHCP instances. I suspect that this is the cleanest thing to back-port because it doesn't add any translatab

[openstack-dev] [Horizon] configuration of plugins in an angularjs world

Hi all, Just a new conundrum for you :) At the top level of our base.html dashboard app, we have some dependencies 'horizon.auth', 'horizon.framework' and 'hz.dashboard' (that name will change to 'horizon.dashboard', but that's for another day). I think we need to remove 'hz.dashboard' from that

Re: [openstack-dev] [App-Catalog] Planning/working session Wednesday in Vancouver

On Tue, May 26, 2015 at 9:22 PM, Keith Bray wrote: > I am interested in getting more involved. Is there any effort already in > place to run this like a regular project, with IRC meetings, etc.? What > are the channels, etc., by which I can get involved. Keith, glad to hear it! You can referen

[openstack-dev] [Manila] About how to hide the dummy destination record during migration

Hi everyone working for Manila, This is Vincent Hou from IBM. I am working on all the migration issues in Cinder. I had one session for the Cinder migration issue in Vancouver and some of you folks attended it. The etherpad link is https://etherpad.openstack.org/p/volume-migration-improvement

Re: [openstack-dev] [App-Catalog] Planning/working session Wednesday in Vancouver

Chris, I am interested in getting more involved. Is there any effort already in place to run this like a regular project, with IRC meetings, etc.? What are the channels, etc., by which I can get involved. Thanks, -Keith On 5/20/15 7:24 AM, "Christopher Aedo" wrote: >[Cross-posting to both d

Re: [openstack-dev] PCI pass-through SRIOV

Hi Levi, Thanks for the replay, What I need to ask Intel regarding this controller IntelXL710, whether it is supported for sriov kvm or sriov openstack?? If the query regarding kvm , I tested by creating VF on this controller and attached to virtual instance and boot it manually on top of KVM

Re: [openstack-dev] [cinder] Some Changes to Cinder Core

Not a core, but still happy to +1 for Sean. His review is important to improve our work. Thanks to Avishay for your contribution in cinder. 2015-05-27 5:42 GMT+08:00 Ivan Kolodyazhny : > +1, > > Welcome to the team, Sean. > > Regards, > Ivan Kolodyazhny > > > On Wed, May 27, 2015 at 12:07 AM, J

Re: [openstack-dev] [designate] and [lbaas] - GSLB API and backend support

We would like to participate as well. Monday-Friday Morning US time works for me.. Thanks, Vijay V. From: Samuel Bercovici [mailto:samu...@radware.com] Sent: 26 May 2015 21:39 To: OpenStack Development Mailing List (not for usage questions) Cc: kunalhgan...@gmail.com; v.jain...@gmail.com; do...@

Re: [openstack-dev] oslo.vmware release 0.13.0 (liberty)

Matt I posted a patch https://review.openstack.org/#/c/185830/1 to fix the nova tests and make it compatible with the oslo.vmware 0.13.0 release. I am fine with the revert and g-r blacklist as oslo.vmware broke the semver but we can also consider this patch as an option. Thanks Sabari On Tue,

Re: [openstack-dev] [Swift] Meeting time change

+1 to what Kota said! Matt On May 27, 2015 11:39 AM, "Kota TSUYUZAKI" wrote: > Thanks John and all swifters for taking care of Asian Pasific and > Australian time zone. Much appreciated :) > > Kota > > (2015/05/26 4:32), John Dickinson wrote: > > Based on discussion over at the summit and over

Re: [openstack-dev] [ceilometer][all] Scalable metering

Hello, My idea for Ceilometer scaling is to partition Ceilometer based on project ID ( Sorry I am newbie to Ceilometer, correct me if I am wrong ). Why? 1. Each tenant only cares about the metering data/event/alarm for himself, doesn't cares who else is also using the ceilometers. Project ID

Re: [openstack-dev] [Swift] Meeting time change

Thanks John and all swifters for taking care of Asian Pasific and Australian time zone. Much appreciated :) Kota (2015/05/26 4:32), John Dickinson wrote: Based on discussion over at the summit and over the last few weeks, the Swift team meeting time has changed. The new meeting time is 2100U

Re: [openstack-dev] [Ironic][oslo] Stepping down from oslo-ironic liaison

Hi Doug and guys, I would like to work as oslo-ironic liasison to sync Ironic with Oslo. I will attend the regular Oslo meeting for sure. My IRC name is lintan, and Launchpad id is tan-lin-good Thanks Tan -Original Message- From: Doug Hellmann [mailto:d...@doughellmann.com] Sent: Tues

Re: [openstack-dev] [ceilometer][all] Scalable metering

hi Tim, we're still doing some investigation but we're tracking/discussing part of the polling load issue here: https://review.openstack.org/#/c/185084/ we're open to any ideas -- especially from nova api et al experts. cheers, gord > From: tim.b...@cern.ch >

Re: [openstack-dev] [Openstack-operators] [openstack-operators][chef] OpenStack+Chef is part of the big tent

Congrats and welcome! On May 26, 2015 5:35 PM, "JJ Asghar" wrote: > Hey everyone! > > I’d like to just drop a note to the list saying thank you and > congratulations to our general community. > > As of 2015-05-26 we’ve been merged into the “big tent”[1] sanctioning us > as an official OpenStack p

[openstack-dev] [keystone] Abandoning open spec reviews for previous cycles

At the end of this week, I will be administratively abandoning all specs with open reviews that are not targeting Liberty or Backlog. Each of these specs has been open for a while with a -2 on them. A given spec can be reproposed against a current target if desired down the line. Cheers, --Morgan

Re: [openstack-dev] [openstackclient] [magnum] Review of object and actions for magnumclient implementation

For reference, the current list of objects and actions used by commands in the OSC repo are at http://docs.openstack.org/developer/python-openstackclient/commands.html. Also note that while the OSC team may have multiple opinions on what fits well and does not in plugins, the plugins are owned by

[openstack-dev] [horizon] No meeting this week

There are no items on the agenda and with the summit just completing, I'm canceling the horizon IRC meeting for May 27. We will resume next week on June 3 at 20:00 UTC. David __ OpenStack Development Mailing List (not for usa

[openstack-dev] [ceilometer] Vancouver summit roundup

hi folks it was great seeing/meeting all those who could make it to the Vancouver summit. i hope everyone had a productive summit and also enjoyed Vancouver (go Canucks!). for those who couldn't make it or for those interested, here are some of the items we talked about and will be tracking in

Re: [openstack-dev] [neutron] - dnsmasq 'dhcp-authoritative' option broke multiple DHCP servers

>As long as we confirm that the severity of this bug is accurately represented in the bug report, then this is the first thing we should do. However, see below. We tried this and did not encounter the error in at least one experiment. Are we sure that this is broken everywhere multiple servers i

Re: [openstack-dev] [neutron] - dnsmasq 'dhcp-authoritative' option broke multiple DHCP servers

Hi Salvatore, The problem isn't that dnsmasq doesn't have an entry for the client. The issue is that the client is sending to a server address that is not dnsmasq. This is the logic that is causing the issue.[1] 1. https://github.com/kevinbenton/dnsmasq/blob/master/src/rfc2131.c#L1103 On Tue, M

Re: [openstack-dev] [neutron] - dnsmasq 'dhcp-authoritative' option broke multiple DHCP servers

>Actually, that approach was initially taken for bug 1345947, but then the patch was abandoned to be replaced with a simpler - --dhcp-authoritative approach that ended up with unexpected NAKs for multi agent setup. >See: https://review.openstack.org/#/c/108272/12 So I had seen that patch but it's

Re: [openstack-dev] oslo.vmware release 0.13.0 (liberty)

Vipin, Gary, Can you please accept the revert or figure out the best way to handle this? thanks, dims On Tue, May 26, 2015 at 5:41 PM, Matt Riedemann wrote: > > > On 5/26/2015 4:19 PM, Matt Riedemann wrote: >> >> >> >> On 5/26/2015 9:53 AM, Davanum Srinivas wrote: >>> >>> We are gleeful to anno

Re: [openstack-dev] oslo.vmware release 0.13.0 (liberty)

On 5/26/2015 4:19 PM, Matt Riedemann wrote: On 5/26/2015 9:53 AM, Davanum Srinivas wrote: We are gleeful to announce the release of: oslo.vmware 0.13.0: Oslo VMware library With source available at: http://git.openstack.org/cgit/openstack/oslo.vmware For more details, please see the

Re: [openstack-dev] [cinder] Some Changes to Cinder Core

+1, Welcome to the team, Sean. Regards, Ivan Kolodyazhny On Wed, May 27, 2015 at 12:07 AM, John Griffith wrote: > > > On Fri, May 22, 2015 at 5:34 PM, Mike Perez wrote: > >> This is long overdue, but it gives me great pleasure to nominate Sean >> McGinnis for >> Cinder core. >> >> Reviews: >

Re: [openstack-dev] [openstack-operators][chef] OpenStack+Chef is part of the big tent

Yay :) > On 26 May 2015, at 23:36, JJ Asghar wrote: > > Hey everyone! > > I’d like to just drop a note to the list saying thank you and congratulations > to our general community. > > As of 2015-05-26 we’ve been merged into the “big tent”[1] sanctioning us as > an official OpenStack project

[openstack-dev] [openstack-operators][chef] OpenStack+Chef is part of the big tent

Hey everyone! I’d like to just drop a note to the list saying thank you and congratulations to our general community. As of 2015-05-26 we’ve been merged into the “big tent”[1] sanctioning us as an official OpenStack project. This is amazing news, and lets keep up the great work! If you have

Re: [openstack-dev] oslo.vmware release 0.13.0 (liberty)

On 5/26/2015 9:53 AM, Davanum Srinivas wrote: We are gleeful to announce the release of: oslo.vmware 0.13.0: Oslo VMware library With source available at: http://git.openstack.org/cgit/openstack/oslo.vmware For more details, please see the git log history below and: http://launch

Re: [openstack-dev] [kolla] Functional gate expansion

(Trying to summarize discussions from earlier on IRC) On Mon, May 25, 2015 at 06:54:43PM +, Steven Dake (stdake) wrote: Hey fellow Kolla devs, With Sam’s recent change to add build from source as an option and build from Debuntian binaries as an option, we will end up in a situation where

Re: [openstack-dev] [cinder] Some Changes to Cinder Core

On Fri, May 22, 2015 at 5:34 PM, Mike Perez wrote: > This is long overdue, but it gives me great pleasure to nominate Sean > McGinnis for > Cinder core. > > Reviews: > https://review.openstack.org/#/q/reviewer:+%22Sean+McGinnis%22,n,z > > Contributions: > https://review.openstack.org/#/q/owner:+%

Re: [openstack-dev] [cinder] Some Changes to Cinder Core

+1 for Sean. He's done a great job doing reviews and getting involved in core Cinder features. Walt On 05/22/2015 04:34 PM, Mike Perez wrote: This is long overdue, but it gives me great pleasure to nominate Sean McGinnis for Cinder core. Reviews: https://review.openstack.org/#/q/reviewer:+%2

[openstack-dev] oslo.log release 1.2.0 (liberty)

We are thrilled to announce the release of: oslo.log 1.2.0: oslo.log library With source available at: http://git.openstack.org/cgit/openstack/oslo.log For more details, please see the git log history below and: http://launchpad.net/oslo.log/+milestone/1.2.0 Please report issues throu

Re: [openstack-dev] [ceilometer][all] Scalable metering

Hi Tim, Maybe you should consider Monasca[1], Monitoring At Scale solution for OpenStack, or, at least, a few concepts of it. [1] https://wiki.openstack.org/wiki/Monasca []s Henrique Truta Em ter, 26 de mai de 2015 às 14:49, Tim Bell escreveu: > > > We had a good discussion at the summit rega

[openstack-dev] [openstackclient] Use and practices of --format shell for defining individual variables

> > > I came across the following neutron client specific syntax and decided to > see if I could reproduce using the openstack client and it's flexible > formatting capabilities > > > $ NIC_ID1=$(neutron net-show public | awk '/ id /{print $4}') > > $ echo $NIC_ID1 > 210d976e-16a3-42dc-ac31-f01810

Re: [openstack-dev] [neutron] - dnsmasq 'dhcp-authoritative' option broke multiple DHCP servers

On Tue, May 26, 2015 at 11:05 AM, Brian Haley wrote: > On 05/26/2015 01:12 PM, Salvatore Orlando wrote: >> >> From the bug Kevin reported it seems multiple dhcp agents per network >> have been >> completely broken by the fix for bug #1345947, so a revert of patch [1] >> (and >> stable backports)

Re: [openstack-dev] [cinder] Some Changes to Cinder Core

Well deserved. Congrat! -Original Message- From: yang, xing [mailto:xing.y...@emc.com] Sent: Friday, May 22, 2015 8:52 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [cinder] Some Changes to Cinder Core Definitely +1! Thanks, Xing -

Re: [openstack-dev] [neutron] - dnsmasq 'dhcp-authoritative' option broke multiple DHCP servers

On 05/26/2015 01:12 PM, Salvatore Orlando wrote: From the bug Kevin reported it seems multiple dhcp agents per network have been completely broken by the fix for bug #1345947, so a revert of patch [1] (and stable backports) should probably be the first thing to do - if nothing else because the o

Re: [openstack-dev] [CI] gate wedged by tox >= 2.0

On 5/14/2015 9:50 AM, Brant Knudson wrote: On Thu, May 14, 2015 at 9:41 AM, Matt Riedemann mailto:mrie...@linux.vnet.ibm.com>> wrote: On 5/14/2015 5:46 AM, Sean Dague wrote: On 05/14/2015 04:16 AM, Robert Collins wrote: Tox 2.0 just came out, and it isolates envi

Re: [openstack-dev] [Glance] [all] Liberty summit: Updates in Glance

Thank you Jesse for your valuable input (here and at the summit) as well as intent to clarify the discussion. Just trying to ensure people are aware about the EXPERIMENTAL nature of the v3 API and reasons behind it. Please find my responses in-line. However, I do want to ensure you all, that w

[openstack-dev] [Neutron]: DVR Presentation slides from the Vancouver summit

Hi Folks, Unfortunately our presentation video is missing from the OpenStack Vancouver summit website. But there was a lot more request for the slides that we presented in the summit. Here is the link to the slides that we presented in the OpenStack Vancouver summit. https://drive.google.com/fil

[openstack-dev] [ceilometer][all] Scalable metering

We had a good discussion at the summit regarding ceilometer scaling. Julien has written up some of the items discussed in https://julien.danjou.info/blog/2015/openstack-summit-liberty-vancouver-ceilometer-gnocchi and there is work ongoing in the storage area for scalable storage of ceilometer

[openstack-dev] oslo.messaging release 1.11.0 (liberty)

We are jubilant to announce the release of: oslo.messaging 1.11.0: Oslo Messaging API With source available at: http://git.openstack.org/cgit/openstack/oslo.messaging For more details, please see the git log history below and: http://launchpad.net/oslo.messaging/+milestone/1.11.0 Plea

Re: [openstack-dev] [openstackclient] Use and practices of --format shell for defining individual variables

Excerpts from Ronald Bradford's message of 2015-05-26 11:18:09 -0400: > Hi list, > > I came across the following neutron client specific syntax and decided to > see if I could reproduce using the openstack client and it's flexible > formatting capabilities > > > $ NIC_ID1=$(neutron net-show publ

[openstack-dev] [Glance] Liberty Priorities

I created an etherpad with priorities the RAX team I work on will be focusing on based on our talks at the summit: https://etherpad.openstack.org/p/liberty-priorities-rax. Input, guidance, feedback, and collaboration is not just welcome, it is encouraged and appreciated. Thanks, Jesse ___

Re: [openstack-dev] [neutron] - dnsmasq 'dhcp-authoritative' option broke multiple DHCP servers

>From the bug Kevin reported it seems multiple dhcp agents per network have been completely broken by the fix for bug #1345947, so a revert of patch [1] (and stable backports) should probably be the first thing to do - if nothing else because the original bug has not nearly the same level of severi

Re: [openstack-dev] [Glance] [all] Liberty summit: Updates in Glance

On 5/22/15, 4:28 PM, "Nikhil Komawar" mailto:nik.koma...@gmail.com>> wrote: Hi all, tl;dr; Artifacts IS staying in Glance. 1. We had a nice discussion at the contributors' meet-up at the Vancouver summit this morning. After weighing in many possibilities and evolution of the Glance progr

Re: [openstack-dev] [glance] [kolla] [magnum] [nova] [neutron] Vancouver Summit Operations Containers Session

Flavio Percoco wrote: There's work going on on something called Artifacts[0], which - in a poorly worded definition - is an enhancement of the current image model in Glance. It'll take some time for the full migration to happen but that should solve your requirement. [0] http://specs.openstack

Re: [openstack-dev] [Horizon] dashboard-app split in horizon

Looks/sounds good, I started down this path a while ago and it never gained traction, so glad to see that it is finally moving along.-Richard Jones wrote: -To: "OpenStack Development Mailing List (not for usage questions)" From: Richard Jones Date: 05/25/2015 05:38PMCc: "Johanson, Tyr H" S

Re: [openstack-dev] [Horizon] dashboard-app split in horizon

On Mon, May 25, 2015 at 5:35 PM, Richard Jones wrote: > As a follow-up to this [in the misguided hope that anyone will actually > read this conversation with myself ;-)] I've started looking at the > base.html split. At the summit last week, we agreed to: > > 1. move base.html over from the frame

Re: [openstack-dev] [Openstack] PCI pass-through SRIOV

- Original Message - > From: "Moshe Levi" > To: "RaghavendraChari Kamsali (Artesyn)" > , "OpenStack Development Mailing List > > This is a different error > > 2015-05-26 13:34:08.081 TRACE nova.compute.manager [instance: > 101776a0-cd2e-47b9-bdc4-1097782201c6] if ret == -1: raise l

Re: [openstack-dev] [lbaas] [octavia] [barbican] Relationship between Octavia and Barbican and Octavia 1.0 questions

Hi Dani, Can you please explain further the 3rd use case (Multiple FIPs….)? Regards, -Sam. From: Daniel Comnea [mailto:comnea.d...@gmail.com] Sent: Friday, May 22, 2015 10:09 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [lbaas]

Re: [openstack-dev] [designate] and [lbaas] - GSLB API and backend support

Hi, I would also like to participate. Friday is a non-working day in Israel (same as Saturday for most of you). So Monday- Thursday works best for me. -Sam. From: Doug Wiegley [mailto:doug...@parksidesoftware.com] Sent: Saturday, May 23, 2015 8:45 AM To: OpenStack Development Mailing List (not

Re: [openstack-dev] [lbaas] [octavia] [barbican] Relationship between Octavia and Barbican and Octavia 1.0 questions

We are considering adding network classes “rules” to LBaaS. In this case, such network classes could als be used to white/black list traffic. From: Brandon Logan [mailto:brandon.lo...@rackspace.com] Sent: Friday, May 22, 2015 12:46 AM To: openstack-dev@lists.openstack.org; maishsk+openst...@maish

Re: [openstack-dev] [oslo.messaging][zeromq] Next step

Alec, Here are the slides: http://www.slideshare.net/davanum/oslomessaging-new-0mq-driver-proposal All the 0mq patches to date should be either already merged in trunk or waiting for review on trunk. Oleksii, Li Ma, Can you please address the other questions? thanks, Dims On Tue, May 26, 2015

Re: [openstack-dev] [Nova] Using depends-on for patches which require an approved spec

On Fri, May 22, 2015 at 02:57:23PM -0700, Michael Still wrote: > Hey, > > it would be cool if devs posting changes for nova which depend on us > approving their spec could use Depends-On to make sure their code > doesn't land until the spec does. Does it actually bring any benefit ? Any change f

[openstack-dev] [oslo.messaging][zeromq] Next step

Looking at what is the next step following the design summit meeting on 0MQ as the etherpad does not provide too much information. Few questions: - would it be possible to have the slides presented (showing the proposed changes in the 0MQ driver design) to be available somewhere? - is there a parti

Re: [openstack-dev] [Nova] [Ironic] Using depends-on for patches which require an approved spec

On 22 May 2015 at 21:38, Morgan Fainberg wrote: > This seems like a good idea for a pattern in general to use gong forward. > > > --Morgan > Sent via mobile > > > On May 22, 2015, at 14:57, Michael Still wrote: > > > > Hey, > > > > it would be cool if devs posting changes for nova which depend o

Re: [openstack-dev] [openstackclient] Use and practices of --format shell for defining individual variables

On Tue, May 26, 2015 at 10:18 AM, Ronald Bradford wrote: > I came across the following neutron client specific syntax and decided to > see if I could reproduce using the openstack client and it's flexible > formatting capabilities > I'll just say off the top it is unlikely as there are only two

[openstack-dev] [openstackclient] Use and practices of --format shell for defining individual variables

Hi list, I came across the following neutron client specific syntax and decided to see if I could reproduce using the openstack client and it's flexible formatting capabilities $ NIC_ID1=$(neutron net-show public | awk '/ id /{print $4}') $ echo $NIC_ID1 210d976e-16a3-42dc-ac31-f01810dbd297 I

[openstack-dev] oslo.vmware release 0.13.0 (liberty)

We are gleeful to announce the release of: oslo.vmware 0.13.0: Oslo VMware library With source available at: http://git.openstack.org/cgit/openstack/oslo.vmware For more details, please see the git log history below and: http://launchpad.net/oslo.vmware/+milestone/0.13.0 Please report

Re: [openstack-dev] PCI pass-through SRIOV

This is a different error 2015-05-26 13:34:08.081 TRACE nova.compute.manager [instance: 101776a0-cd2e-47b9-bdc4-1097782201c6] if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self) 2015-05-26 13:34:08.081 TRACE nova.compute.manager [instance: 101776a0-cd2e-47b9-bd

Re: [openstack-dev] [Neutron][DB] neutron DB migration scripts

On 5/25/15 10:35 PM, Armando M. wrote: On 25 May 2015 at 09:46, Mike Bayer > wrote: On 5/25/15 12:34 PM, Armando M. wrote: One thing I would like to point out is that in this cycle we'll be working extensively in this area to make the very task you

Re: [openstack-dev] [kolla] Add core approver Sam Yaple

On Mon, May 25, 2015 at 06:59:15PM +, Steven Dake (stdake) wrote: Hi folks, I propose Sam Yaple for core approver for the Kolla team. Sam has a lot of great ideas and has done some really cool work lately. Sam is active in IRC and is starting to pick up more reviews. Of particular inte

Re: [openstack-dev] [neutron] - dnsmasq 'dhcp-authoritative' option broke multiple DHCP servers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/26/2015 04:35 AM, Kevin Benton wrote: > Hi, > > A recent change[1] to pass '--dhcp-authoritative' to dnsmasq has > caused DHCPNAK messages when multiple agents are scheduled to a > network [2]. > > This was back-ported to Icehouse and Juno so

Re: [openstack-dev] [Neutron] Stepping down from Neutron core team

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/21/2015 05:58 PM, Salvatore Orlando wrote: > After putting the whole OpenStack networking contributors > community through almost 8 cycles of pedant comments and annoying > "what if" questions, it is probably time for me to relieve neutron > co

Re: [openstack-dev] [Fuel] Setting cluster status when provisioning a node

Oleg, Aleksander also proposed a nice proposed a nice solution [1] which is to have a complex status for cluster. That, however, looks like a BP so I’ve created an excerpt [2] for it and we will try to discuss it scope it for 7.0, if there is a consensus. References: 1. http://lists.openstac

Re: [openstack-dev] [Ironic][oslo] Stepping down from oslo-ironic liaison

Excerpts from Ghe Rivero's message of 2015-05-25 09:45:47 -0700: > My focus on the Ironic project has been decreasing in the last cycles, so > it's about time to relinquish my position as a oslo-ironic liaison so new > contributors can take over it and help ironic to be the vibrant project it > is.

Re: [openstack-dev] [Fuel] Setting cluster status when provisioning a node

Aleksey, thank you for your feedback. The first thing I’d like to highlight is that both web ui and the cli use the same Nailgun API to perform the same actions so basically we must not treat the command line client any differently. The idea of having a complex status for environment actually s

Re: [openstack-dev] [nova] xen project retrigger

On Mon, 25 May 2015 08:21:22 + Gary Kotton wrote: > Hi, > Anyone know how to retriever this CI? > Thanks > Gary their notification emails say "To recheck use 'xen: recheck'." I also got a test failure from them today so maybe there is a general problem. Regards, Alex

[openstack-dev] [Fuel][Plugins] A new 'monitoring' value is now introduced for groups in metadata.yaml

Hi to all, Previously, only limited number of values could be added to 'groups' parameter in metadata.yaml file of the plugin. These are: - network - storage - storage:: cinder - storage:: glance - hypervisor. Now you can also add 'monitoring' if your plugin has the corresponding functionality.

[openstack-dev] Cross-Project meeting, Tue May 26th, 21:00 UTC

Dear PTLs, cross-project liaisons and anyone else interested, We'll have a cross-project meeting today at 21:00 UTC, with the following agenda: * Design Summit feedback (ttx) * CORS Support for OpenStack (krotscheck) [1] * Suggestions to evolve this meeting format in Liberty (ttx) * Open discussi

Re: [openstack-dev] [tempest][qa][cinder] How to configure tempest with to test volume migration?

Good to see that you will work on this! In addition to the cases that Duncan mentioned, there is also the case of moving a volume between two pools within the same backend. This probably complicates the setup even further. On Mon, May 25, 2015 at 12:31 PM, Duncan Thomas wrote: > There doesn't s

Re: [openstack-dev] Redis as Messaging System

Zaqar provides an option to use Redis as a backend, and Zaqar provides pubsub messaging. On 05/23/2015 03:09 PM, Todd Crane wrote: > Does anybody know of a way (either current projects or future plans) > to use Redis PubSub as the messaging system for OpenStack? > > -Todd -- Ryan Brown / Softwa

Re: [openstack-dev] [Cinder] Do we need to fix issues in V1 API?

AFAIK, we're going to remove API v1 from Cinder in Liberty. So it makes no sense to fix it in master. Regards, Ivan Kolodyazhny On Tue, May 26, 2015 at 3:36 PM, Duncan Thomas wrote: > I don't think either of those are likely to be accepted for V1, certainly > I'd vote against it. They should

Re: [openstack-dev] [Cinder] Do we need to fix issues in V1 API?

Thanks ☺ From: Duncan Thomas [mailto:duncan.tho...@gmail.com] Sent: 26 May 2015 18:07 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Cinder] Do we need to fix issues in V1 API? I don't think either of those are likely to be accepted for V1, certainl

Re: [openstack-dev] [Zaqar][all] Zaqar will stay... Lots of work ahead

On 26/05/15 08:23 -0400, Ryan Brown wrote: On 05/26/2015 04:28 AM, Flavio Percoco wrote: [snip] As a first step, we should restore our meetings and get to work right away. To favor our contributors in NZ, next week's meeting will be at 21:00 UTC and we'll keep it at that time for 2 weeks. F

Re: [openstack-dev] [Cinder] Do we need to fix issues in V1 API?

I don't think either of those are likely to be accepted for V1, certainly I'd vote against it. They should be fixed in V2 however. On 26 May 2015 at 15:13, Deore, Pranali11 wrote: > Hi Duncan, > > > > I am planning to fix following issues for V1 API, > > 1. https://bugs.launchpad.net/cind

Re: [openstack-dev] [Zaqar][all] Zaqar will stay... Lots of work ahead

On 05/26/2015 04:28 AM, Flavio Percoco wrote: > Greetings, > > TL;DR: Thanks everyone for your feedback. Based on the discussed plans > at the summit - I'll be writing more about these later - Zaqar will > stick around and play its role in the community. \o/ > [snip] > == > > Next S

Re: [openstack-dev] [Fuel] vxlan support

Hi Samuel, VXLAN has critical status in Backlog for 7.0. We are going to include this segmentation type out of the box in 7.0. Meanwhile, you may create plugin for 6.1. Your help will be appreciated. I'll be glad to help you with plugins if you have any questions. -- Best regards, Sergii Golovati

Re: [openstack-dev] [Cinder] Do we need to fix issues in V1 API?

Hi Duncan, I am planning to fix following issues for V1 API, 1. https://bugs.launchpad.net/cinder/+bug/1454244 2. “VolumeNotFound” exception error message should be consistent across all APIs Please suggest. Thanks From: Duncan Thomas [mailto:duncan.tho...@gmail.com] Sent: 26 May

Re: [openstack-dev] [kolla] Add core approver Sam Yaple

+1 Sam has done an great job integrating his work into Kolla and I look forward to seeing more of his contributions! -Ryan - Original Message - From: "Andre Martin" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Monday, May 25, 2015 9:37:24 PM Subject: Re: [

Re: [openstack-dev] [Cinder] Do we need to fix issues in V1 API?

In general, V1 is not being changed / fixed, though it is case-by-case, for example security issues will always be fixed. What exactly were you thinking about fixing? On 26 May 2015 at 14:17, Deore, Pranali11 wrote: > Hello, > > > > While fixing issues in V2 API, do we need to fix in V1 API? >

[openstack-dev] [Cinder] Do we need to fix issues in V1 API?

Hello, While fixing issues in V2 API, do we need to fix in V1 API? As per following blueprint description, V1 API is being deprecated in liberty-1. https://blueprints.launchpad.net/cinder/+spec/deprecate-v1-api Thanks & Regards, Pranali Deore

Re: [openstack-dev] [neutron] - dnsmasq 'dhcp-authoritative' option broke multiple DHCP servers

Hi, HA on DHCP is done by setting dhcp_agents_per_network >= 2, so production deploiements should set dhcp_agents_per_network >= 2. Regards, Cédric/ZZelle On Tue, May 26, 2015 at 12:24 PM, wrote: > How about retaining --dhcp-authoritative when dhcp_agents_per_network = > 1? I would guess th

Re: [openstack-dev] [nova] usefulness of device parameter at volumeAttachment

On 05/26/2015 11:13 AM, Daniel P. Berrange wrote: > On Sat, May 23, 2015 at 11:00:32AM +0200, Géza Gémes wrote: >> Hi, >> >> When someone calls nova volume-attach or the block-device-mapping parameter >> at boot, it is possible to specify a device name for the guest. However I >> couldn't find any

Re: [openstack-dev] Stepping Down from Trove Core

Vipul, thanks for all the things you’ve done for Trove over the years. All the best with Cue! Thanks, -amrith From: Vipul Sabhaya [mailto:vip...@gmail.com] Sent: Monday, May 25, 2015 11:24 PM To: OpenStack Development Mailing List Subject: [openstack-dev] Stepping Down from Trove Core Having n

Re: [openstack-dev] [neutron] - dnsmasq 'dhcp-authoritative' option broke multiple DHCP servers

How about retaining --dhcp-authoritative ‎when dhcp_agents_per_network = 1?  I would guess that that is the 90% case.  I suppose that would require passing new information from the Neutron server to the DHCP agent

Re: [openstack-dev] [nova] usefulness of device parameter at volumeAttachment

On Sat, May 23, 2015 at 11:00:32AM +0200, Géza Gémes wrote: > Hi, > > When someone calls nova volume-attach or the block-device-mapping parameter > at boot, it is possible to specify a device name for the guest. However I > couldn't find any guest OS which would honor this. E.g. with libvirt/kvm,

Re: [openstack-dev] [zaqar]

I am afraid its not so straightforward. The messaging passing between the API and Guestagent is delegated to oslo messaging. Adding support for Zaqar would require us to write some kind of driver for it, or change Trove code to support it. Cheers El lun., 25 may. 2015 a las 10:31, Li Tianqing ()

Re: [openstack-dev] [cinder] Port Cinder to Python 3

Thanks Victor, that is pretty much exactly what I wanted to hear - there's a known, finite plan to get us to fully working with python3. I'll go change my reviews now. On 26 May 2015 at 12:44, Victor Stinner wrote: > (Oops, I sent a draft by mistake, sorry about that.) > > Hi, > > There is an on

[openstack-dev] [cinder] Port Cinder to Python 3

(Oops, I sent a draft by mistake, sorry about that.) Hi, There is an ongoing effort to port OpenStack applications to Python 3 during the Liberty cycle. The following table gives the status of each application and links to patches: https://wiki.openstack.org/wiki/Python3#OpenStack_applications

Re: [openstack-dev] Stepping Down from Trove Core

Thanks for all the hard work that you've put into Trove over the years. I understand that with Cue you are going to have much less time to focus on Trove reviews. However you are - and always will be - an integral part of the Trove community. Good luck on Cue! Cheers, -Nikhil Vipul Sabhaya wr

[openstack-dev] [cinder] Port Cinder to Python 3

Hi, There is an ongoing effort to port OpenStack applications to Python 3 during the Liberty cycle. The following table gives the status of each application and links to patches: https://wiki.openstack.org/wiki/Python3#OpenStack_applications Specs were accepted for: * heat: https://review.open

Re: [openstack-dev] [Neutron] Stepping down from Neutron core team

Salvatore, I have never found your comments pedant, on the contrary they always improved my patches and for sure Neutron in general. It's a pity that you step down as a core but I am glad that you will keep staying in the Neutron community! Rossella On 05/21/2015 05:58 PM, Salvatore Orlando wrot

[openstack-dev] [Fuel] vxlan support

Hi folks, I have a question about implementation of vxlan for neutron. there is a blueprint on that topic in launchpad from 2014/03/21: https://blueprints.launchpad.net/fuel/+spec/neutron-vxlan-support several fixes have been pushed but all of them have been abandonned or refused. Is there any t

  1   2   >