[openstack-dev] [glance] Unable to set metadata_encryption_key

Hello, Please I am working on a bug (https://bugs.launchpad.net/glance/+bug/1569937), but when trying to replicate the bug by setting metadata_encryption_key = AoAMaVuEEJVYRvWgWrfHJoThUPmvniTi I get the following error from glance-api ValueError: Input strings must be a multiple of 16 in

Re: [openstack-dev] [Neutron][L2GW] Mitaka release of L2 Gateway now available

Hi Martinx, L2GW is designed to bridge neutron networks with non-neutron networks to form a L2 broadcast domain - not two neutron networks. regards.. -Sukhdev On Mon, May 16, 2016 at 8:58 PM, Martinx - ジェームズ wrote: > > > On 11 May 2016 at 16:05, Sukhdev Kapur

Re: [openstack-dev] [mistral][oslo.messaging] stable/mitaka is broken by oslo.messaging 5.0.0

Doug Hellmann wrote: Excerpts from Renat Akhmerov's message of 2016-05-17 19:10:55 +0700: Team, Our stable/mitaka branch is now broken by oslo.messaging 5.0.0. Global requirements for stable/mitaka has oslo.messaging>=4.0.0 so it can fetch 5.0.0. Just reminding that it breaks us because we

Re: [openstack-dev] [mistral][oslo.messaging] stable/mitaka is broken by oslo.messaging 5.0.0

> On 17 May 2016, at 21:50, Doug Hellmann wrote: > > Excerpts from Renat Akhmerov's message of 2016-05-17 19:10:55 +0700: >> Team, >> >> Our stable/mitaka branch is now broken by oslo.messaging 5.0.0. Global >> requirements for stable/mitaka has oslo.messaging>=4.0.0 so

Re: [openstack-dev] [Neutron][ML2][Routed Networks]

On May 17, 2016 2:18 PM, "Kevin Benton" wrote: > > >I kind of think it makes sense to require evacuating a segment of its ports before deleting it. > > Ah, I left out an important assumption I was making. We also need to auto delete the DHCP port as the segment is deleted. I was

Re: [openstack-dev] [Congress] driver (authentication issue)

Hi Tim and all, Thank you very much. I put congress in a tag so I missed your email and relay late. Sorry about that. My problem here is that i want to use the command line to put the data into the congress datasource. I use the command openstack congress datasource create test test(i have a

Re: [openstack-dev] [Openstack] [Aodh] add "meter-list" command in Aodh CLI

Ok, Perfect. I like this solution. subsequently, I would like to add this message in aodhclient. Thank you very much Best Regards Rajen > Hi, > > > We shouldn't have 'meter-list' in aodhclient. > > Nova have API and function to show image list, and 'nova image-list' is talking to nova,

[openstack-dev] [Neutron][Stable][Liberty][CLI] Gate broken

Hello Stable Maint Team, It seems that python-neutronclient gate for Liberty is broken[1][2] by update for keystoneclient. OpenStack proposal bot already sent update to requirements [3], but it needs to be merged. If you have enough power, please unblock gate. Thanks, Darek [1]

[openstack-dev] [OpenStack] [Smaug] Use Trello to coordinate?

Hello everyone, Smaug project is considering to use Trello to coordinate. At present, there are four lists in the Smaug board: Todo, In Progress, Pending Review and Done. Welcome to give the suggestions on how to use Trello in Smaug. Welcome to give the suggestions on coordinate. Welcome to

Re: [openstack-dev] [kolla] Proposing Mauricio Lima for core reviewer

This should be obvious to core reviewers, but for Mauricio to join the core reviewer team, there must be no veto votes and a majority of +1s. Apologies for leaving that out. Regards -steve From: Steven Dake > Reply-To:

Re: [openstack-dev] [kolla] Proposing Mauricio Lima for core reviewer

+1 ​ ​ nice work Mauricio Lima On Wed, May 18, 2016 at 11:03 AM, Swapnil Kulkarni wrote: > On Wed, May 18, 2016 at 12:30 AM, Steven Dake (stdake) > wrote: > > Hello core reviewers, > > > > I am proposing Mauricio (mlima on irc) for the core review team. He

Re: [openstack-dev] [Openstack] [Aodh] add "meter-list" command in Aodh CLI

Hi, We shouldn't have 'meter-list' in aodhclient. Nova have API and function to show image list, and 'nova image-list' is talking to nova, not glance. It would be strange if '$ aodh meter-list' (aodhclient) made request to ceilometer. On the other hand, I understand your concern. We can

Re: [openstack-dev] [requirements][all] First Requirements Team Meeting

On 17 May 2016 at 23:47, Davanum Srinivas wrote: > Team, > > Let's meet in #openstack-meeting-cp channel at 12:00 UTC on May 18th: > http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016=5=18=12=0=0=43=240=195=166=83=281=141 > > We can decide if we need a better

Re: [openstack-dev] [kolla] Proposing Mauricio Lima for core reviewer

On Wed, May 18, 2016 at 12:30 AM, Steven Dake (stdake) wrote: > Hello core reviewers, > > I am proposing Mauricio (mlima on irc) for the core review team. He has > done a fantastic job reviewing appearing in the middle of the pack for 90 > days [1] and appearing as #2 in 45

Re: [openstack-dev] [tc] [all] [glance] Answers to some questions about Glance

On 18 May 2016 at 00:54, Brian Rosmaita wrote: >> Couple of examples: >> 1. switching from "is_public=true" to "visibility=public" > > > This was a major version change in the Images API. The 'is_public' boolean > is in the original Images v1 API, 'visibility' was

[openstack-dev] [Openstack] [Aodh] add "meter-list" command in Aodh CLI

So sorry, my mistake when create the link. > On Tue, May 17 2016, li.yuanz...@zte.com.cn wrote: > > > Now, in Aodh CLI, when create a threshold alarm, the > > -m/--meter-name must be required. > > But, if the user is not familiar with ceilometer or aodh, the user > > is not

Re: [openstack-dev] [tripleo] How to setup hyper-converged nodes (compute+ceph)?

Hi all, Hereby updating the status of this message: On Mon, May 16, 2016 at 9:55 AM, Gerard Braad wrote: > we would like > to deploy Compute nodes with Ceph installed on them. This will > probably be a change to the tripleo-heat-templates and the compute, > and cephstorage

[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting today. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks

Re: [openstack-dev] [all] Deprecated options in sample configs?

> > > If config sample files are being used as a living document then that would > be a reason to leave the deprecated options in there. In my experience as a > cloud deployer I never once used them in that manner so it didn't occur to > me that people might, hence my question to the list. > >

Re: [openstack-dev] [Heat] Versioned objects upgrade patterns

Now getting very Heat-specific. W.r.t. to https://review.openstack.org/#/c/303692/ , the goal is to de-duplicate raw_template.files (this is a dict of template filename to contents), both in the DB and in RAM. The approach this patch is taking is that, when one template is created by reference to

Re: [openstack-dev] [all] Deprecated options in sample configs?

On Tue, May 17, 2016, at 03:00 PM, Dolph Mathews wrote: > I think the metadata_manager is one of many terrible examples of > deprecated configuration options. The documentation surrounding a > deprecation should *always* tell you why something is being > deprecated, and what you should be

Re: [openstack-dev] [TripleO] [diskimage-builder] LVM in diskimage-builder

On 18 May 2016 at 07:32, Andre Florath wrote: > Hi All! > > AFAIK the diskimage-builder started as a testing tool, but it looks > that it evolves more and more into a general propose tool for creating > docker and VM disk images. We started as a fast, production, targeted

Re: [openstack-dev] [release] Re: [Neutron][L2GW] Mitaka release of L2 Gateway now available

On 17 May 2016 at 03:25, Ihar Hrachyshka wrote: > > > On 16 May 2016, at 21:16, Armando M. wrote: > > > > > > > > On 16 May 2016 at 05:15, Ihar Hrachyshka wrote: > > > > > On 11 May 2016, at 22:05, Sukhdev Kapur

Re: [openstack-dev] [TripleO] Aodh upgrades - Request backport exception for stable/liberty

On Tue, May 17, 2016 at 1:31 PM, James Slagle wrote: > On Tue, May 17, 2016 at 12:04 PM, Pradeep Kilambi wrote: > > Thanks Steve. I was under the impression we cannot run puppet at this > > stage. Hence my suggestion to run bash or some script here, but

Re: [openstack-dev] [searchlight] Searchlight Core Nomination - Lei Zhang

+1, Lei's made some great contributions. On 5/17/16, 3:56 PM, "Brian Rosmaita" wrote: >+1 > >I second the motion! > >On 5/17/16, 3:42 PM, "Tripp, Travis S" wrote: > >>I am nominating Lei Zhang from Intel (lei-zh on IRC) to join the

Re: [openstack-dev] [searchlight] Searchlight Core Nomination - Lei Zhang

+1 I second the motion! On 5/17/16, 3:42 PM, "Tripp, Travis S" wrote: >I am nominating Lei Zhang from Intel (lei-zh on IRC) to join the >Searchlight core reviewers team. He has been actively participating with >thoughtful patches and reviews demonstrating his depth of

Re: [openstack-dev] [neutron] DHCP Agent Scheduling for Segments

I'm leaning towards option A because it keeps things cleanly separated. Also, if a cloud is using a plugin that supports segments, an operator could use the new API for everything (including single segment networks) so it shouldn't be that unfriendly. However... >If there's some other option

Re: [openstack-dev] [Neutron][ML2][Routed Networks]

>I kind of think it makes sense to require evacuating a segment of its ports before deleting it. Ah, I left out an important assumption I was making. We also need to auto delete the DHCP port as the segment is deleted. I was thinking this will be basically be like the delete_network case where we

Re: [openstack-dev] [all] Deprecated options in sample configs?

  -Original Message- From: Dolph Mathews Reply: OpenStack Development Mailing List (not for usage questions) Date: May 17, 2016 at 14:02:00 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [all] Deprecated options in sample configs?

On Tue, May 17, 2016 at 3:51 PM, Ben Nemec wrote: > > I'm +1 on removing them from sample configs. This feels like release > note information to me, and if someone happens to miss the release note > then they'll get deprecation warnings in their logs. The sample config >

[openstack-dev] [neutron] DHCP Agent Scheduling for Segments

As part of the routed networks work [1], the DHCP agent and scheduling needs to be segment aware. Right now, the dhcpagentscheduler extension exposes API resources to manage networks: - List networks hosted by an agent - GET /agents/{agent_id}/dhcp-networks - Response Body:

Re: [openstack-dev] [TripleO] [diskimage-builder] LVM in diskimage-builder

I have nothing useful to add, except that I am excited about getting good LVM support in diskimage-builder. On 05/17/2016 02:32 PM, Andre Florath wrote: > Hi All! > > AFAIK the diskimage-builder started as a testing tool, but it looks > that it evolves more and more into a general propose tool

Re: [openstack-dev] [Heat] Versioned objects upgrade patterns

On 17/05/16 15:40, Crag Wolfe wrote: Another thing I am wondering about: if my particular object is not exposed by RPC, is it worth making it a full blown o.vo or not? I.e, I can do the 3 steps over 3 releases just in the object's .py file -- what additional value do I get from o.vo? It's more

Re: [openstack-dev] [all] Deprecated options in sample configs?

On 05/17/2016 01:47 PM, Andrew Laski wrote: > > > > On Tue, May 17, 2016, at 02:36 PM, Matt Fischer wrote: >> On Tue, May 17, 2016 at 12:25 PM, Andrew Laski > > wrote: >> >> I was in a discussion earlier about discouraging deployers from

[openstack-dev] [searchlight] Searchlight Core Nomination - Lei Zhang

I am nominating Lei Zhang from Intel (lei-zh on IRC) to join the Searchlight core reviewers team. He has been actively participating with thoughtful patches and reviews demonstrating his depth of understanding in a variety of areas. He also participates in meetings regularly, despite a

Re: [openstack-dev] [Heat] Versioned objects upgrade patterns

On 05/17/2016 10:34 AM, Michał Dulko wrote: > On 05/17/2016 06:30 PM, Crag Wolfe wrote: >> Hi all, >> >> I've read that versioned objects are favored for supporting different >> versions between RPC services and to support rolling upgrades. I'm >> looking to follow the pattern for Heat. Basically,

Re: [openstack-dev] [neutron][stable] proposing Brian Haley for neutron-stable-maint

+1 +1 On Tue, 2016-05-17 at 18:58 +, Vasudevan, Swaminathan (PNB Roseville) wrote: > +1 for both. > > > > From: Kevin Benton [mailto:ke...@benton.pub] > Sent: Tuesday, May 17, 2016 11:06 AM > To: OpenStack Development Mailing List (not for usage questions) >

[openstack-dev] [TripleO] [diskimage-builder] LVM in diskimage-builder

Hi All! AFAIK the diskimage-builder started as a testing tool, but it looks that it evolves more and more into a general propose tool for creating docker and VM disk images. Currently there are ongoing efforts to add LVM [1]. But because some features that I need are missing, I created my own

Re: [openstack-dev] [Neutron][ML2][Routed Networks]

On Tue, May 17, 2016 at 10:56 AM, Kevin Benton wrote: >>a) Deleting network's last segment will be prevented. Every network should >> have at least one segment to let the port to bind. > > This seems a bit arbitrary to me. If a segment is limited to a small part of > the

Re: [openstack-dev] [all] Deprecated options in sample configs?

On Tue, May 17, 2016 at 12:47 PM, Andrew Laski wrote: > > > > On Tue, May 17, 2016, at 02:36 PM, Matt Fischer wrote: > > On Tue, May 17, 2016 at 12:25 PM, Andrew Laski wrote: > > I was in a discussion earlier about discouraging deployers from using >

Re: [openstack-dev] [Telemetry] Time to test and import Panko

what needs to be tested here? that Ceilometer can dispatch to Panko? do we need to worry about any redirection like we had with Aodh? On 17/05/2016 8:29 AM, Julien Danjou wrote: > Hi fellows, > > I'm done creating Panko, our new project born from cutting off the event > part of Ceilometer.

Re: [openstack-dev] [neutron][stable] proposing Brian Haley for neutron-stable-maint

+1 for both. From: Kevin Benton [mailto:ke...@benton.pub] Sent: Tuesday, May 17, 2016 11:06 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron][stable] proposing Brian Haley for neutron-stable-maint +1

[openstack-dev] [kolla] Proposing Mauricio Lima for core reviewer

Hello core reviewers, I am proposing Mauricio (mlima on irc) for the core review team. He has done a fantastic job reviewing appearing in the middle of the pack for 90 days [1] and appearing as #2 in 45 days [2]. His IRC participation is also fantastic and does a good job on technical work

Re: [openstack-dev] [all] Deprecated options in sample configs?

I think the metadata_manager is one of many terrible examples of deprecated configuration options. The documentation surrounding a deprecation should *always* tell you why something is being deprecated, and what you should be using instead to achieve the same, or better, result moving forward. But

Re: [openstack-dev] [Fuel][MySQL][DLM][Oslo][DB][Trove][Galera][operators] Multi-master writes look OK, OCF RA and more things

I missed your reply originally, so sorry for the 2 week lag... Excerpts from Mike Bayer's message of 2016-04-30 15:14:05 -0500: > > On 04/30/2016 10:50 AM, Clint Byrum wrote: > > Excerpts from Roman Podoliaka's message of 2016-04-29 12:04:49 -0700: > >> > > > > I'm curious why you think setting

Re: [openstack-dev] [all] Deprecated options in sample configs?

On Tue, May 17, 2016, at 02:36 PM, Matt Fischer wrote: > On Tue, May 17, 2016 at 12:25 PM, Andrew Laski > wrote: >> I was in a discussion earlier about discouraging deployers from using >> deprecated options and the question came up about why we put >> deprecated >>

Re: [openstack-dev] [all] Deprecated options in sample configs?

On Tue, May 17, 2016 at 12:25 PM, Andrew Laski wrote: > I was in a discussion earlier about discouraging deployers from using > deprecated options and the question came up about why we put deprecated > options into the sample files generated in the various projects. So, why >

[openstack-dev] [all] Deprecated options in sample configs?

I was in a discussion earlier about discouraging deployers from using deprecated options and the question came up about why we put deprecated options into the sample files generated in the various projects. So, why do we do that? I view the sample file as a reference to be used when setting up a

Re: [openstack-dev] [release] Re: [Neutron][L2GW] Mitaka release of L2 Gateway now available

tl;dr Merge changes to process documentation before expecting them to be followed! :) On Tue, May 17, 2016 at 4:25 AM, Ihar Hrachyshka wrote: > 2016.1.0 tag is in the repo, and is part of stable/mitaka branch. > > Git tag history suggests that Carl pushed it (manually I

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Yeah, no meetings in #openstack-neutron please. It leaves us nowhere to discuss development stuff during that hour. On Tue, May 17, 2016 at 2:54 AM, Miguel Angel Ajo Pelayo < majop...@redhat.com> wrote: > I agree, let's try to find a timeslot that works. > > using #openstack-neutron with the

Re: [openstack-dev] [neutron][stable] proposing Brian Haley for neutron-stable-maint

+1 for both On Tue, May 17, 2016 at 5:57 AM, Kyle Mestery wrote: > +1 (Also +1 for Cedric). > > On Tue, May 17, 2016 at 6:07 AM, Ihar Hrachyshka > wrote: > > Hi stable-maint-core and all, > > > > I would like to propose Brian for neutron specific

[openstack-dev] [neutron][fwaas] neutron-fwaas meeting reminder

All, Now that the FWaaS team has a brand new sparkling meeting time, I wanted to remind anyone who is interested to join us on #openstack-meeting-3 for a discussion about the state of Firewall as a Service. The meeting is Wednesday at 0400 UTC. For your convenience, this is what that translates

Re: [openstack-dev] [horizon] [javascript] Async file uploads in anew JS-centric UI

Thanks for the great explanation Timur. I have bookmarked both and will look into it shortly. From: Timur Sufiev To: "OpenStack Development Mailing List (not for usage questions)" Date: 05/17/2016 10:38 AM Subject:

Re: [openstack-dev] [horizon] [javascript] Async file uploads in a new JS-centric UI

Since 10 lines of code > 1000 words, here are references to 2 patch chains: * New Swift UI file upload https://review.openstack.org/#/c/316143/ * New Angular Create Image file upload https://review.openstack.org/#/c/317456/ I like Create Image solution more because it doesn't use Django

Re: [openstack-dev] [Heat] Versioned objects upgrade patterns

On 05/17/2016 06:30 PM, Crag Wolfe wrote: > Hi all, > > I've read that versioned objects are favored for supporting different > versions between RPC services and to support rolling upgrades. I'm > looking to follow the pattern for Heat. Basically, it is the classic > problem where we want to

Re: [openstack-dev] [TripleO] Aodh upgrades - Request backport exception for stable/liberty

On Tue, May 17, 2016 at 12:04 PM, Pradeep Kilambi wrote: > Thanks Steve. I was under the impression we cannot run puppet at this > stage. Hence my suggestion to run bash or some script here, but if we > can find a way to easily wire the existing aodh puppet manifests into > the

[openstack-dev] [TripleO][CI] Tempest on periodic jobs

Hi, raising again the question about tempest running on TripleO CI as it was discussed in the last TripleO meeting. I'd like to get your attention that in these tests, which I ran just for ensure it works, there were bugs discovered, and these weren't corner cases but real failures of TripleO

Re: [openstack-dev] [Neutron][ML2][Routed Networks]

>a) Deleting network's last segment will be prevented. Every network should have at least one segment to let the port to bind. This seems a bit arbitrary to me. If a segment is limited to a small part of the datacenter, it being able to bind for one section of the datacenter and not the rest is

[openstack-dev] Questions about Openstack Mitaka Dashboard

Dear OpenStack Dev Team May I ask you some questions about the Openstakc Mitaka Horizon Dashboard? I have followed the Openstack online installation document and your installation guide http://docs.openstack.org/mitaka/install-guide-ubuntu/ But after I installed the horizon, I cannot access the

[openstack-dev] [Heat] Versioned objects upgrade patterns

Hi all, I've read that versioned objects are favored for supporting different versions between RPC services and to support rolling upgrades. I'm looking to follow the pattern for Heat. Basically, it is the classic problem where we want to migrate from writing to a column in one table to having

Re: [openstack-dev] [Fuel][MySQL][DLM][Oslo][DB][Trove][Galera][operators] Multi-master writes look OK, OCF RA and more things

On 04/22/2016 05:42 PM, Bogdan Dobrelya wrote: > [crossposting to openstack-operat...@lists.openstack.org] > > Hello. > I wrote this paper [0] to demonstrate an approach how we can leverage a > Jepsen framework for QA/CI/CD pipeline for OpenStack projects like Oslo > (DB) or Trove, Tooz DLM and

Re: [openstack-dev] [keystone] Newton midycle planning

On Tue, May 10, 2016 at 4:26 PM, Morgan Fainberg wrote: > On Wed, Apr 13, 2016 at 7:07 PM, Morgan Fainberg < > morgan.fainb...@gmail.com> wrote: > >> It is that time again, the time to plan the Keystone midcycle! Looking at >> the schedule [1] for Newton, the weeks

Re: [openstack-dev] [TripleO] Aodh upgrades - Request backport exception for stable/liberty

On Tue, May 17, 2016 at 4:59 AM, Steven Hardy wrote: > Hi Pradeep, > > Firstly, as discussed on IRC, I echo all of bnemec's concerns, this is not > well aligned with our stable branch policy[1], or the stable-maint > direction towards "critical bugfixes only"[2], so if possible

[openstack-dev] [glance] Cross project and all other liaisons

Team, Please make sure the Cross project liaisons page [1] is up to date with your Newton commitments. * If you are planning to stick around with certain duties and your name is already on the wiki page [1] , please make sure the contact information is up-to-date. Also, please note any

Re: [openstack-dev] [Neutron][ML2][Routed Networks]

Hi, I create this patch [1] to allow multi-segmented routed provider networks to grow and shrink over time, reviews are welcomed. I found these points during working on the patch, and I think it is good to bring them out for discussion. a) Deleting network's last segment will be prevented.

Re: [openstack-dev] [Fuel][Plugins] Tasks ordering between plugins

Hi Simon, For 8.0 and earlier, I would deploy ElasticSearch before deploy_end and LMA collector after post_deploy_start For Mitaka and Newton releases, the task graph now skips dependencies that are not found for the role being processed. Now this "requires" dependency will work that previously

Re: [openstack-dev] [tripleo] tripleo-common docs

On Tue, May 17, 2016 at 11:01 AM, Ben Nemec wrote: > On 05/17/2016 08:16 AM, Marius Cornea wrote: > > Hi everyone, > > > > The tripleo-common readme[1] points to a broken documentation link[2]. > > What is the correct link for the docs? > > At the moment it should

Re: [openstack-dev] [Fuel][Plugins] Tasks ordering between plugins

I'm resurrecting this thread because I didn't manage to find a satisfying solution to deal with this issue. First let me provide more context on the use case. The Elasticsearch/Kibana and LMA collector plugins need to synchronize their deployment. Without too many details, here is the workflow

Re: [openstack-dev] [puppet] weekly meeting #81

d.openstack.org/p/puppet-openstack-weekly-meeting-20160517 > > Feel free to add more topics, and any outstanding bug and patch. > > See you tomorrow! Here are the notes: http://eavesdrop.openstack.org/meetings/puppet_openstack/2016/puppet_openstack.2016-05-17-15

[openstack-dev] [glance] Mid-cycle: Response required ASAP

Hello, If you have booked travel for Glance midcycle or are looking to book the same in the near future, please respond back to me ASAP. I am going to take a final decisions on whether we need to conduct the physically co-located Glance midcycle or not and if we have a quorum (5 people) for the

Re: [openstack-dev] [docs] [api] Swagger limitations?

On Tue, 17 May 2016, Jamie Hannaford wrote: Completely agree. The good news is that the API-WG have a spec in review (https://review.openstack.org/#/c/234994/) which might solve these problems. They want to make actions first-class resources in the API. From my initial understanding, this could

Re: [openstack-dev] [docs] [api] Swagger limitations?

On Tue, May 17, 2016 at 9:51 AM, Jamie Hannaford < jamie.hannaf...@rackspace.com> wrote: > Hi Anne, > > > So it seems that the only remaining issues are: > > > - using $ref, which is not supported by some upstream tools > > - embedding Heat templates in a Swagger doc (not applicable to most >

Re: [openstack-dev] [tripleo] tripleo-common docs

On 05/17/2016 08:16 AM, Marius Cornea wrote: > Hi everyone, > > The tripleo-common readme[1] points to a broken documentation link[2]. > What is the correct link for the docs? At the moment it should probably point at http://docs.openstack.org/developer/tripleo-docs/ Although it would be nice

Re: [openstack-dev] [release] Re: [Neutron][L2GW] Mitaka release of L2 Gateway now available

> On 17 May 2016, at 16:46, Doug Hellmann wrote: > > Excerpts from Ihar Hrachyshka's message of 2016-05-17 14:39:40 +0200: >> >>> On 17 May 2016, at 14:27, Doug Hellmann wrote: >>> >>> Excerpts from Ihar Hrachyshka's message of 2016-05-17

Re: [openstack-dev] [docs] [api] Swagger limitations?

Hi Anne, So it seems that the only remaining issues are: - using $ref, which is not supported by some upstream tools - embedding Heat templates in a Swagger doc (not applicable to most OpenStack services) I responded to the other two in my e-mail to Sean. For the $ref problem, what is the

Re: [openstack-dev] [docs] [api] Swagger limitations?

On Tue, May 17, 2016 at 9:13 AM, Jamie Hannaford < jamie.hannaf...@rackspace.com> wrote: > All great points, thanks Anne and Sean. My responses are inline. > > > From: Sean Dague > Sent: 17 May 2016 15:30 > To:

Re: [openstack-dev] [oslo][all] oslo.log `verbose` and $your project

Dmitry Tantsur said on Tue, May 17, 2016 at 09:54:02AM +0200: > >I'd like to retry 314573 in a few weeks, so cooperation and helping > >getting any leftover cases of 'verbose' out of source trees would be > >much appreciated. > > Let me use this thread as a reminder: the goal of that deprecation

Re: [openstack-dev] [mistral][oslo.messaging] stable/mitaka is broken by oslo.messaging 5.0.0

Excerpts from Renat Akhmerov's message of 2016-05-17 19:10:55 +0700: > Team, > > Our stable/mitaka branch is now broken by oslo.messaging 5.0.0. Global > requirements for stable/mitaka has oslo.messaging>=4.0.0 so it can fetch > 5.0.0. > > Just reminding that it breaks us because we

[openstack-dev] [nova] Thoughts on deprecating the legacy bdm v1 API support

In the live migration meeting today mdbooth and I were chatting about how hard it is to follow the various BDM code through nova, because you have the three block_device modules: * nova.block_device - dict that does some translation magic * nova.objects.block_device - contains the BDM(List)

Re: [openstack-dev] [release] Re: [Neutron][L2GW] Mitaka release of L2 Gateway now available

Excerpts from Ihar Hrachyshka's message of 2016-05-17 14:39:40 +0200: > > > On 17 May 2016, at 14:27, Doug Hellmann wrote: > > > > Excerpts from Ihar Hrachyshka's message of 2016-05-17 12:25:55 +0200: > >> > >>> On 16 May 2016, at 21:16, Armando M.

[openstack-dev] [Tacker] Can not launch new VNF

Hi all, It's my first time using Tacker, I've installed it with Openstack/libery using [1]. I've created a VNFD but I always got the following erreor when I tried to launch new VNF. Someone knowshow to correct that error ? Regards, tacker vnfd-list

[openstack-dev] [neutron] [dhcp] DHCP Agent resync

Hi DHCP Agent SMEs We are reviewing the DHCP Agent in Icehouse, specifically for an issue where the dnsmasq host file has multiple stale or replicated (IP address) entries (as compared to the DB allocations for the subnet). We also checked the other HA dnsmasq instance and it is correctly

[openstack-dev] [release] no meeting 20 May

The release team will skip our meeting this week (20 May). Doug __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

[openstack-dev] [new][nova] os_vif 1.0.0 release (newton)

We are pumped to announce the release of: os_vif 1.0.0: A library for plugging and unplugging virtual interfaces in OpenStack. This is the first release of os_vif. This release is part of the newton release series. With package available at: https://pypi.python.org/pypi/os_vif For more

Re: [openstack-dev] [Congress] Nominating Anusha Ramineni and Eric Kao for core reviewer

Thanks. It's great working with you guys and I'm glad to be part of this team :) +1. On 2016/05/14 9:16, Tim Hinrichs wrote: > Hi all, > > I'm writing to nominate Anusha Ramineni and Eric Kao as Congress core > reviewers. Both Anusha and Eric have been active and consistent > contributors in

Re: [openstack-dev] [docs] [api] Swagger limitations?

All great points, thanks Anne and Sean. My responses are inline. From: Sean Dague Sent: 17 May 2016 15:30 To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [docs] [api] Swagger limitations? On 05/17/2016 08:57 AM, Jamie

Re: [openstack-dev] [tc] [all] [glance] Answers to some questions about Glance

Thanks Brian On Tue, May 17, 2016 at 6:54 AM, Brian Rosmaita < brian.rosma...@rackspace.com> wrote: > Subject was: Re: [openstack-dev] [tc] [all] [glance] On operating a high > throughput or otherwise team > > Un-hijacking the thread. Here are some answers to John's questions, hope > they are

[openstack-dev] [cross-project][ptl] Update your liaisons

Hi PTL's, Please make sure your cross-project spec liaisons are up-to-date [1]. This role defaults to the PTL if no liaison is selected. See list of reponsibilities [2]. As agreed by the TC, the cross-project spec liaison team will have voting rights on the openstack/openstack-spec repo [3].

Re: [openstack-dev] [docs] [api] Swagger limitations?

On Tue, May 17, 2016 at 7:57 AM, Jamie Hannaford < jamie.hannaf...@rackspace.com> wrote: > Hi all, > > > Back in March Anne wrote a great summary on the current state of Swagger > for OpenStack docs: > http://lists.openstack.org/pipermail/openstack-dev/2016-March/090659.html. >

Re: [openstack-dev] [docs] [api] Swagger limitations?

On 05/17/2016 08:57 AM, Jamie Hannaford wrote: > Hi all, > > > Back in March Anne wrote a great summary on the current state of Swagger > for OpenStack > docs: > http://lists.openstack.org/pipermail/openstack-dev/2016-March/090659.html. >

[openstack-dev] [Performance] IRC meetings starting today after a break

Folks, just a reminder - today we'll start our periodical Performance Team meetings after a post-summit break we had. *#openstack-performance channel and 16:00 UTC* as usually :) See you! -- Dina __ OpenStack Development

[openstack-dev] [tripleo] tripleo-common docs

Hi everyone, The tripleo-common readme[1] points to a broken documentation link[2]. What is the correct link for the docs? Thanks [1] https://github.com/openstack/tripleo-common/blob/master/README.rst [2] http://docs.openstack.org/developer/tripleo-common

Re: [openstack-dev] [sahara] Nominating new members to Sahara Core

Thanks everyone. Always a pleasure to work with you all. Chad On Tue, May 17, 2016 at 4:42 AM, Vitaly Gridnev wrote: > Ok, seems that we have a quorum. Welcome folks! > > On Tue, May 17, 2016 at 10:44 AM, Alexander Ignatov > wrote: > >> +2 to

[openstack-dev] [docs] [api] Swagger limitations?

Hi all, Back in March Anne wrote a great summary on the current state of Swagger for OpenStack docs: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090659.html. Is this still the current state of

Re: [openstack-dev] [neutron][stable] proposing Brian Haley for neutron-stable-maint

+1 (Also +1 for Cedric). On Tue, May 17, 2016 at 6:07 AM, Ihar Hrachyshka wrote: > Hi stable-maint-core and all, > > I would like to propose Brian for neutron specific stable team. > > His stats for neutron stable branches are (last 120 days): > > mitaka: 19 reviews;

[openstack-dev] [tc] [all] [glance] Answers to some questions about Glance

Subject was: Re: [openstack-dev] [tc] [all] [glance] On operating a high throughput or otherwise team Un-hijacking the thread. Here are some answers to John's questions, hope they are helpful. On 5/16/16, 9:06 PM, "John Griffith" >

Re: [openstack-dev] [fuel][plugins][lma] Leveraging OpenStack logstash grok filters in StackLight?

The short answer is no. StackLight is based on Heka for log processing and parsing. Heka itself uses Lua Parsing Expression Grammars [1]. For now the patterns are maintained in the LMA collector repository [2] but it's on our to-do list to have it available in a dedicated repo. One advantage of

Re: [openstack-dev] [release] Re: [Neutron][L2GW] Mitaka release of L2 Gateway now available

> On 17 May 2016, at 14:27, Doug Hellmann wrote: > > Excerpts from Ihar Hrachyshka's message of 2016-05-17 12:25:55 +0200: >> >>> On 16 May 2016, at 21:16, Armando M. wrote: >>> >>> >>> >>> On 16 May 2016 at 05:15, Ihar Hrachyshka

[openstack-dev] [Smaug]- IRC Meeting today (05/17) - 1400 UTC

Hi All, We will hold our bi-weekly IRC meeting today (Tuesday, 05/17) at 1400 UTC in #openstack-meeting Please review the proposed meeting agenda here: https://wiki.openstack.org/wiki/Meetings/smaug Please feel free to add to the agenda any subject you would like to discuss. We will also be

[openstack-dev] [Telemetry] Time to test and import Panko

Hi fellows, I'm done creating Panko, our new project born from cutting off the event part of Ceilometer. It's at: https://github.com/jd/panko There are only a few commits as you can see: https://github.com/jd/panko/commits/master The code has been created in a 4 steps process: 1. Remove code

  1   2   >