[openstack-dev] [heat] Team dinner at PTG

Hi guys As usual, we will have a team dinner (and beer session) during PTG. Feel free to join us! And please vote for any preferred schedule here: https://framadate.org/DiYtBWG2VqTRxMs5 We will find some place later. -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

[openstack-dev] [Horizon] Weekly wrap-up

Hi folks, A quiet week this week as folks gear up for Pike and the PTG next week. We did get Ocata RC2 out the door this week with those final few bug fixes and the wonderful translations from the i18n team! Thanks to everyone who helped make Ocata Horizon happen :-) If you're going to the PTG,

[openstack-dev] [Blazar] Project Team Gathering for Pike

Hi all, Blazar team will unofficially gather on next Thursday at PTG. Please join us if you are interested in the Reservation as a Service for OpenStack! Here are schedule and topics: https://etherpad.openstack.org/p/blazar-ptg-pike The Blazar project (previously known as Climate) has recently

[openstack-dev] [nova] nova 15.0.0.0rc2 (ocata)

Hello everyone, A new release candidate for nova for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/nova/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally

[openstack-dev] [oslo] PTG schedule

*folks,* I made a draft schedule for Oslo team at PTG. In summary, we have one and half days, there are two bug smash event at the end of each day. Maybe we need make some adjustments to avoid conflicts with other sessions, please let me know if we have any. Please check out

Re: [openstack-dev] [OpenStack-Infra] [all][stable][ptls] Tagging liberty as EOL

On Wed, Feb 15, 2017 at 4:20 PM, Tony Breeds wrote: > On Wed, Feb 08, 2017 at 09:55:41AM -0800, Ihar Hrachyshka wrote: > > Has the liberty-eol cleanup happened? Because I still see > > stable/liberty branch in openstack/neutron repo, which gets in the way > > of some

[openstack-dev] [manila] manila 4.0.0.0rc2 (ocata)

Hello everyone, A new release candidate for manila for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/manila/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally

[openstack-dev] [cinder] cinder 10.0.0.0rc2 (ocata)

Hello everyone, A new release candidate for cinder for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/cinder/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally

[openstack-dev] [neutron] neutron 10.0.0.0rc2 (ocata)

Hello everyone, A new release candidate for neutron for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/neutron/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

[openstack-dev] [neutron] neutron-fwaas 10.0.0.0rc2 (ocata)

Hello everyone, A new release candidate for neutron-fwaas for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/neutron-fwaas/ Unless release-critical issues are found that warrant a release candidate respin, this candidate

[openstack-dev] [glance] priorities for the coming week (02/17-02/23)

Hello Glancers, Here are the weekly priorities: 1. RC-1 Testing It's still looking like RC-1 is going to be the real thing. If you have some free time, give it a workout. 2. PTG Here are some key URLs for your convenience: - https://etherpad.openstack.org/p/glance-pike-ptg-planning -

[openstack-dev] artifacts code removed from the glance codebase in Pike

If you've never deployed, packaged, or used the Artifacts API supplied by Glance or Glare, you can safely disregard this message. There's a patch up [0] to remove the legacy EXPERIMENTAL Artifacts API code from the Glance code repository. (This is an entirely separate issue from the question of

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

On 16 Feb 2017, at 15:01, Chris Dent wrote: > On Thu, 16 Feb 2017, Dan Prince wrote: > >> And yes. We are all OpenStack developers in a sense. We want to align >> things in the technical arena. But I think you'll also find that most >> people more closely associate themselves to a team within

Re: [openstack-dev] [keystone]PKI token VS Fernet token

On Thu, Feb 16, 2017 at 5:20 PM, Dolph Mathews wrote: > Thank you for the data and your test scripts! As Lance and Stanek already > alluded, Fernet performance is very sensitive to keystone's configuration. > Can your share your keystone.conf as well? > > I'll also be in

Re: [openstack-dev] [PKG-Openstack-devel] The end of OpenStack packages in Debian?

On 2/16/2017 5:26 PM, Thomas Goirand wrote: Also, the approach to give-up the packaging of "non-important" project (ie: not-core, like the ones in the list I gave...) in the hope it will save so much time is IMO simply wrong. What eats all of the package maintenance time is *not* final projects

Re: [openstack-dev] The end of OpenStack packages in Debian?

On 02/16/2017 05:55 PM, Clint Byrum wrote: > Excerpts from Thomas Goirand's message of 2017-02-15 13:43:46 +0100: >> All this to say that, unless someone wants to hire me for it (which >> would be the best outcome, but I fear this wont happen), or if someone >> steps in (this seems unlikely at

[openstack-dev] [tricircle]Ocata released and Pike meetup

Hello, Thanks for your great contribution, Tricircle 3.0.0 (Ocata release) has been released after the patch[1] was approved, the release notes could be found at [2]. A meetup for Pike will be held: Feb.17, UTC 1:00~8:00( UTC+8: 9:00 am~4:00 pm), Block G, Huawei Industrial Base, Shenzhen.

Re: [openstack-dev] [PKG-Openstack-devel] The end of OpenStack packages in Debian?

On 02/16/2017 12:20 PM, Ondrej Novy wrote: > Hi, > > 2017-02-16 0:45 GMT+01:00 Thomas Goirand >: > > Yes, you've done some work, and many thanks for it, it has been very > useful. However the reality is: since I stopped after the Newton >

Re: [openstack-dev] [keystone]PKI token VS Fernet token

Thank you for the data and your test scripts! As Lance and Stanek already alluded, Fernet performance is very sensitive to keystone's configuration. Can your share your keystone.conf as well? I'll also be in Atlanta and would love to talk Fernet performance, even if we don't have a formal time

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

On Thu, 16 Feb 2017, Dan Prince wrote: And yes. We are all OpenStack developers in a sense. We want to align things in the technical arena. But I think you'll also find that most people more closely associate themselves to a team within OpenStack than they perhaps do with the larger project.

[openstack-dev] [horizon] horizon 11.0.0.0rc2 (ocata)

Hello everyone, A new release candidate for horizon for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/horizon/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

Yeah, but if the deployment tools have to implement support for every project, it becomes combinatorial to support all the projects in all the deployment tools. let alone document it for each deployment project. If there was a foundational infrastructure that the other big tent projects could

Re: [openstack-dev] [neutron] Some findings while profiling instances boot

Note that neutron no longer relies on giant join conditions so heavily due to explosions in result sizes with the various many to one relationships as of about a week ago[1]. We switched to subqueries for the one to many relationships to prevent the result size explosions, so now we issue a lot

Re: [openstack-dev] [neutron] Some findings while profiling instances boot

We could potentially make that call async on the agent, but the agent has very little to do without the information in the response that comes back. As we switch over to push notifications, this method of data retrieval will be completely gone so we probably don't want to spend much time

[openstack-dev] [trove] trove 7.0.0.0rc2 (ocata)

Hello everyone, A new release candidate for trove for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/trove/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

On 2017-02-16 15:20:11 -0500 (-0500), Dan Prince wrote: [...] > And there is that rub again. There is implied along with this pressure > to adopt the new logo. If you don't you'll get a blank space as a sort > of punishment for going your own way. As Monty said directly... they > want conformance

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

On Thu, Feb 16, 2017 at 3:20 PM, Dan Prince wrote: > On Thu, 2017-02-16 at 19:54 +, Jeremy Stanley wrote: >> On 2017-02-16 14:09:53 -0500 (-0500), Dan Prince wrote: >> [...] >> > This isn't about aligning anything. It is about artistic control. >> > The >> > foundation

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

> On Feb 16, 2017, at 12:20 PM, Dan Prince wrote: > > On Thu, 2017-02-16 at 19:54 +, Jeremy Stanley wrote: >> On 2017-02-16 14:09:53 -0500 (-0500), Dan Prince wrote: >> [...] >>> This isn't about aligning anything. It is about artistic control. >>> The >>> foundation

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

Personally I'd prefer OpenStack to follow some of K8s deployment patterns. OpenStack has grown to an enormous size and it really painful to operate it at scale. My suggestion would be to focus on improvement of consumption models. 'Dockerization' of the release artifacts would be very useful. Also

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

On Thu, 2017-02-16 at 19:54 +, Jeremy Stanley wrote: > On 2017-02-16 14:09:53 -0500 (-0500), Dan Prince wrote: > [...] > > This isn't about aligning anything. It is about artistic control. > > The > > foundation wants to have icons their way playing the "community > > card" > > to make those

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

On 2017-02-16 14:09:53 -0500 (-0500), Dan Prince wrote: [...] > This isn't about aligning anything. It is about artistic control. The > foundation wants to have icons their way playing the "community card" > to make those who had icons they like conform. It is clear you buy into > this. > > Each

[openstack-dev] [release] Release countdown for Ocata Final Release Week, 20-24 Feb

Focus - The release team will tag the final releases for all milestone-based projects on 22 February to coincide with the press release distributed by the Foundation marketing staff. Release Tasks - Liaisons for milestone-based projects should review the set of unreleased

Re: [openstack-dev] [keystone] PTG schedule

Based on early feedback I've broken up our first session, which is dedicated to reviewing things not addressed in Ocata [0], into three different sessions. I'm hoping this will help us commit enough time to finding resolutions for each topic, versus cramming it all into 40 minutes. Keep the

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

On 16 Feb 2017, at 19:42, Fox, Kevin M > wrote: +1. The assumption was market forces will cause the best OpenStack deployment tools to win. But the sad reality is, market forces are causing people to look for non OpenStack solutions instead as the

Re: [openstack-dev] [tripleo] tripleo-ui release job failure

Excerpts from Jeremy Stanley's message of 2017-02-16 18:47:48 +: > On 2017-02-16 14:31:01 -0400 (-0400), Honza Pokorny wrote: > > The included logs don't give me much to go on. It fails with a pretty > > generic timeout message. I can't even determine if that happened during > > "npm

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

On Thu, 2017-02-16 at 06:36 -0600, Monty Taylor wrote: > On 02/15/2017 07:54 PM, Dan Prince wrote: > > At the high level all of this sounds like a fine grand plan: "Help > > projects create mascots" with a common theme. On the ground level I > > can > > tell you it feels a lot more like you are

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

Le 16/02/2017 18:42, Alex Schultz a écrit : > On Thu, Feb 16, 2017 at 9:12 AM, Ed Leafe wrote: >> On Feb 16, 2017, at 10:07 AM, Doug Hellmann wrote: >> >>> When we signed off on the Big Tent changes we said competition >>> between projects was desirable,

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

On 02/16/2017 07:25 PM, Heidi Joy Tretheway wrote: > Amid the spirited discussion on your mascot, I wanted to clear up confusion > about our next steps and your options. > > 1. I’ve taken Carlos’s sketches to our illustration team to ask them to make > the original TripleO owl in the style of

Re: [openstack-dev] [tripleo] tripleo-ui release job failure

On 2017-02-16 14:31:01 -0400 (-0400), Honza Pokorny wrote: > The included logs don't give me much to go on. It fails with a pretty > generic timeout message. I can't even determine if that happened during > "npm install" or after. > > Is there any more information available on the source of the

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

+1. The assumption was market forces will cause the best OpenStack deployment tools to win. But the sad reality is, market forces are causing people to look for non OpenStack solutions instead as the pain is still too high. While k8s has a few different deployment tools currently, they are

Re: [openstack-dev] [tripleo] tripleo-ui release job failure

The included logs don't give me much to go on. It fails with a pretty generic timeout message. I can't even determine if that happened during "npm install" or after. Is there any more information available on the source of the failure? Thanks Honza Pokorny On 2017-02-16 12:43, Doug Hellmann

[openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

Amid the spirited discussion on your mascot, I wanted to clear up confusion about our next steps and your options. 1. I’ve taken Carlos’s sketches to our illustration team to ask them to make the original TripleO owl in the style of the new logo family. This takes a bit of time and probably

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

Alex Schultz wrote: On Thu, Feb 16, 2017 at 9:12 AM, Ed Leafe wrote: On Feb 16, 2017, at 10:07 AM, Doug Hellmann wrote: When we signed off on the Big Tent changes we said competition between projects was desirable, and that deployers and contributors

[openstack-dev] [horizon] [keystone] Cross-Project Meeting

Hey everyone, Quick reminder about the Keystone-Horizon meeting at 2000 UTC (about 1h45 from this email being sent). You can see the details and add it to your calendar via http://eavesdrop.openstack.org/#Keystone/Horizon_Collaboration_Meeting I'd like to keep up these meetings for the

Re: [openstack-dev] [all] Do we need service types at all?! (Re: [octavia][sdk] service name for octavia)

On 02/16/2017 11:21 AM, Jay Pipes wrote: > On 02/16/2017 08:14 AM, Dean Troyer wrote: >> On Thu, Feb 16, 2017 at 7:06 AM, Andrey Kurilin >> wrote: >>> Yes, I forgot about it. But it changes nothing. >>> Custom implementation of particular service should cover the same API

[openstack-dev] [tripleo] tripleo-ui release job failure

The job to build the npm package for tripleo-ui has failed. Doug --- Begin forwarded message from jenkins --- From: jenkins To: release-job-failures Date: Thu, 16 Feb 2017 16:51:50 + Subject: [Release-job-failures] Release of

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

On Thu, Feb 16, 2017 at 9:12 AM, Ed Leafe wrote: > On Feb 16, 2017, at 10:07 AM, Doug Hellmann wrote: > >> When we signed off on the Big Tent changes we said competition >> between projects was desirable, and that deployers and contributors >> would make

Re: [openstack-dev] The end of OpenStack packages in Debian?

Nice work on the packages Thomas. I've always admired that you got the Debian packages upstream first :). Best wishes. Dan On Wed, 2017-02-15 at 13:42 +0100, Thomas Goirand wrote: > Hi there, > > It's been a while since I planed on writing this message. I couldn't > write it because the

Re: [openstack-dev] [all] Do we need service types at all?! (Re: [octavia][sdk] service name for octavia)

On 02/16/2017 08:14 AM, Dean Troyer wrote: On Thu, Feb 16, 2017 at 7:06 AM, Andrey Kurilin wrote: Yes, I forgot about it. But it changes nothing. Custom implementation of particular service should cover the same API as an official one. For me, as for user, it doesn't

[openstack-dev] Related to neutron big switch plugin configuration through devstack

Hello, I am successfully installing devstack in my Ubuntu 16.04 64bit server system. In that neutron configured only ml2 plugin but I have to configure big switch plugin because I am working on Floodlight SDN controller in that they required big switch plugin for connecting with OpenStack so how

[openstack-dev] Subject: [all][api] POST /api-wg/news

Greetings OpenStack community, This week we talked quite a bit about what the API-WG will be trying to do next week at the PTG. We'll be sharing time and space with the Architecture working group, with rooms on both Monday and Tuesday of the cross-project period of the week. Topics are being

Re: [openstack-dev] The end of OpenStack packages in Debian?

Excerpts from Thomas Goirand's message of 2017-02-15 13:43:46 +0100: > All this to say that, unless someone wants to hire me for it (which > would be the best outcome, but I fear this wont happen), or if someone > steps in (this seems unlikely at this point), both the packaging-deb and > the faith

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

On Thu, 2017-02-16 at 08:36 -0500, Emilien Macchi wrote: > I'll shamelessly cross-post here, I didn't know where to reply. > I agree with Monty and Flavio here. > > Heidi has been doing an excellent job in helping OpenStack community > about $topic, always in the open, which has been very

[openstack-dev] [designate] designate-dashboard 4.0.0.0rc2 (ocata)

Hello everyone, A new release candidate for designate-dashboard for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/designate-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this

Re: [openstack-dev] [neutron] Some findings while profiling instances boot

Mike, Team, Rolling the dice here: https://review.openstack.org/#/c/435009/ Thanks, Dims On Thu, Feb 16, 2017 at 11:35 AM, Mike Bayer wrote: > > > On 02/15/2017 12:46 PM, Daniel Alvarez Sanchez wrote: >> >> Also, while having a look at server profiling, around the 33% of the

[openstack-dev] [tripleo] Ocata RC1 is out - RC2 is ongoing

https://media.giphy.com/media/zyin7TYoGmLAs/giphy.gif We released TripleO Ocata RC1 and created stable/ocata branch. Details: * instack 6.0.0 (final). We don't expect more work on this project before final release. * instack-undercloud 6.0.0.0rc1. * puppet-tripleo 6.2.0 which

Re: [openstack-dev] [Watcher] Nominating licanwei to Watcher Core

+1 On 2/15/17, 10:00 PM, "Hidekazu Nakamura" wrote: >+1 > >> -Original Message- >> From: Spencer, Christopher M [mailto:christopher.m.spen...@intel.com] >> Sent: Wednesday, February 15, 2017 11:36 PM >> To: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

Excerpts from Ian Cordasco's message of 2017-02-16 11:20:45 -0500: > -Original Message- > From: Ed Leafe > Reply: OpenStack Development Mailing List (not for usage questions) > > Date: February 16, 2017 at 10:13:51 > To: OpenStack

Re: [openstack-dev] [neutron] Some findings while profiling instances boot

On 02/15/2017 12:46 PM, Daniel Alvarez Sanchez wrote: Also, while having a look at server profiling, around the 33% of the time was spent building SQL queries [1]. Mike Bayer went through this and suggested having a look at baked queries and also submitted a sketch of his proposal [2].

[openstack-dev] [nova] Final mascot logo

Here are the final logos for the Nova mascot: https://www.dropbox.com/sh/9l1c7ymyjgpa3cc/AAB9iPZ0HIwn16nzC7G5liuza?dl=0 There will be some stickers and other postings of this at the PTG. -- Thanks, Matt Riedemann __

[openstack-dev] [ironic][neutron] PTG cross team session

Hello Ironic/Neutron teams, Ironic team would like to schedule cross session with Neutron team on Mon - Tues except for Tue 9.30 - 10.00 The topics we would like to talk are added to: https://etherpad.openstack.org/p/neutron-ptg-pike L151 Sincerely, Vasyl Saienko

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

On 02/16/2017 10:23 AM, Ed Leafe wrote: > On Feb 16, 2017, at 10:12 AM, Ed Leafe wrote: > >> We got much better at adding new things to OpenStack. We need to get better >> at letting go of old things. > > On re-reading that, it doesn’t sound like what I intended. By “old” I

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

On Feb 16, 2017, at 10:12 AM, Ed Leafe wrote: > We got much better at adding new things to OpenStack. We need to get better > at letting go of old things. On re-reading that, it doesn’t sound like what I intended. By “old” I mean things that no longer have enough active

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

-Original Message- From: Ed Leafe Reply: OpenStack Development Mailing List (not for usage questions) Date: February 16, 2017 at 10:13:51 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [Packaging-RPM] Nominating Alberto Planas Dominguez for Packaging-RPM core

Hi Igor, 2017-02-16 15:43 GMT+01:00 Igor Yozhikov : > I’d like to nominate Alberto Planas Dominguez known as aplanas on irc for > Packaging-RPM core. > Alberto done a lot of reviews for as for project modules [1],[2] as for rest > of OpenStack components [3]. His

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

On Feb 16, 2017, at 10:07 AM, Doug Hellmann wrote: > When we signed off on the Big Tent changes we said competition > between projects was desirable, and that deployers and contributors > would make choices based on the work being done in those competing > projects.

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

Excerpts from Dean Troyer's message of 2017-02-16 08:25:42 -0600: > On Thu, Feb 16, 2017 at 7:54 AM, Ian Cordasco wrote: > > It seems like a lot of people view "developing OpenStack" as more > > attractive than "making it easy to deploy OpenStack" (via the > > deployment

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

On 14/02/17 04:38, Emilien Macchi wrote: > Team, I've got this email from Heidi. > > I see 3 options : > > 1. Keep existing logo: http://tripleo.org/_static/tripleo_owl.svg . > > 2. Re-design a new logo that "meets" OpenStack "requirements". > > 3. Pick-up the one proposed (see below). Option

Re: [openstack-dev] [Zun] Choose a project mascot

I was thinking about falcon(light, powerful and fast), or dolphins or tiger. On Wed, Feb 15, 2017 at 12:29 AM, Hongbin Lu wrote: > Hi Zun team, > > > > OpenStack has a mascot program [1]. Basically, if we like, we can choose a > mascot to represent our team. The process

[openstack-dev] [searchlight] searchlight-ui 2.0.0.0rc2 (ocata)

Hello everyone, A new release candidate for searchlight-ui for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/searchlight-ui/ Unless release-critical issues are found that warrant a release candidate respin, this candidate

Re: [openstack-dev] [Packaging-RPM] Nominating Alberto Planas Dominguez for Packaging-RPM core

> +1 > > Welcome Alberto! > +1 for me. Good reviews so far, it'll be great to have him as core. Javier > > On Thu, 2017-02-16 at 17:43 +0300, Igor Yozhikov wrote: > > Hello team. > > I want to announce the following changes to Packaging-RPM core team: > > I’d like to nominate Alberto

[openstack-dev] [searchlight] searchlight 2.0.0.0rc2 (ocata)

Hello everyone, A new release candidate for searchlight for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/searchlight/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will

Re: [openstack-dev] [Packaging-RPM] Nominating Alberto Planas Dominguez for Packaging-RPM core

+1 Welcome Alberto! On Thu, 2017-02-16 at 17:43 +0300, Igor Yozhikov wrote: > Hello team. > I want to announce the following changes to Packaging-RPM core team: > I’d like to nominate Alberto Planas Dominguez known as aplanas on irc > for Packaging-RPM core. > Alberto done a lot of reviews for

Re: [openstack-dev] [ironic] New mascot design

Hi Heidi, I'm happy with the proposed logo. As far as the "kiss" style face painting goes, I don't like it. But that is because I am not a fan of KISS or their music. Having said that, I can understand why people would like it and why it fits with ironic, so I am fine if it is used :) Thank

Re: [openstack-dev] [Packaging-RPM] Nominating Alberto Planas Dominguez for Packaging-RPM core

2017-02-16 15:43 GMT+01:00 Igor Yozhikov : > Hello team. > I want to announce the following changes to Packaging-RPM core team: > I’d like to nominate Alberto Planas Dominguez known as aplanas on irc for > Packaging-RPM core. > Alberto done a lot of reviews for as for

Re: [openstack-dev] [telemetry] Triggering alarms on Swift notifications

Sorry for confusing. I just wanted to try to setup telemetry and try it with Picasso(Serverless functions). And your suggestion worked well. So i think it is worth opening issue against Aodh and Ceilometer for implementing given option configuration just Panko devstack plugin does. Kind regards,

Re: [openstack-dev] [kolla] Mascot

> On 14 Feb 2017, at 17:27, Steven Dake (stdake) wrote: > > The mascot is absolutely fantastic! Nice work to all involved! Woot! Awesome! -- Christian Berendt Chief Executive Officer (CEO) Mail: bere...@betacloud-solutions.de Web: https://www.betacloud-solutions.de

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

-Original Message- From: Dean Troyer Reply: OpenStack Development Mailing List (not for usage questions) Date: February 16, 2017 at 08:27:12 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

On 02/16/2017 08:25 AM, Dean Troyer wrote: > On Thu, Feb 16, 2017 at 7:54 AM, Ian Cordasco wrote: >> It seems like a lot of people view "developing OpenStack" as more >> attractive than "making it easy to deploy OpenStack" (via the >> deployment tools in the tent). Doing

Re: [openstack-dev] [neutron] Some findings while profiling instances boot

Awesome work, Kevin! For the DHCP notification, in my profiling I got only 10% of the CPU time [0] without taking the waiting times into account which it's probably what you also measured. Your patch seems like a neat and great optimization :) Also, since

[openstack-dev] [Packaging-RPM] Nominating Alberto Planas Dominguez for Packaging-RPM core

Hello team. I want to announce the following changes to Packaging-RPM core team: I’d like to nominate Alberto Planas Dominguez known as aplanas on irc for Packaging-RPM core. Alberto done a lot of reviews for as for project modules [1],[2] as for rest of OpenStack components [3]. His experience

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

Hi, Yeah, I tried drafting something based on our current logo and following my perception about the new foundation styles, again here are the files (WIP version, is just a PoC) https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_ tripleo_logo_h.pdf

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

On Thu, Feb 16, 2017 at 7:54 AM, Ian Cordasco wrote: > It seems like a lot of people view "developing OpenStack" as more > attractive than "making it easy to deploy OpenStack" (via the > deployment tools in the tent). Doing both is really something project > teams should

Re: [openstack-dev] [nova] scaling rabbitmq with cells v2 requires manual database update

On Thu, Feb 16, 2017 at 1:30 AM, Chen CH Ji wrote: > Should be this one https://bugs.launchpad.net/nova/+bug/1664913 and > *https://review.openstack.org/434179* > ? > > Hey Kevin, sorry I didn't notice your patch/bug. It looks like this

Re: [openstack-dev] [all] Do we need service types at all?! (Re: [octavia][sdk] service name for octavia)

On 02/16/2017 08:47 AM, Ian Cordasco wrote: > -Original Message- > From: Andrey Kurilin > Reply: OpenStack Development Mailing List (not for usage questions) > > Date: February 16, 2017 at 07:08:19 > To: OpenStack Development

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

-Original Message- From: Doug Hellmann Reply: OpenStack Development Mailing List (not for usage questions) Date: February 16, 2017 at 07:06:25 To: openstack-dev Subject:  Re: [openstack-dev]

Re: [openstack-dev] [telemetry] Triggering alarms on Swift notifications

On Thu, Feb 16, 2017 at 03:33:43PM +0200, Denis Makogon wrote: Hello Mehdi. Thanks for response. See comments inline. 2017-02-16 15:25 GMT+02:00 Mehdi Abaakouk : Hi, On Thu, Feb 16, 2017 at 03:04:52PM +0200, Denis Makogon wrote: Greetings. Could someone provide any

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

On 02/14/2017 03:38 AM, Emilien Macchi wrote: > Team, I've got this email from Heidi. > > I see 3 options : > > 1. Keep existing logo: http://tripleo.org/_static/tripleo_owl.svg . > > 2. Re-design a new logo that "meets" OpenStack "requirements". > > 3. Pick-up the one proposed (see below).

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

On 16/02/17 08:36 -0500, Emilien Macchi wrote: I'll shamelessly cross-post here, I didn't know where to reply. I agree with Monty and Flavio here. Heidi has been doing an excellent job in helping OpenStack community about $topic, always in the open, which has been very appreciated. We, as a

Re: [openstack-dev] [all] Do we need service types at all?! (Re: [octavia][sdk] service name for octavia)

-Original Message- From: Andrey Kurilin Reply: OpenStack Development Mailing List (not for usage questions) Date: February 16, 2017 at 07:08:19 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

I'll shamelessly cross-post here, I didn't know where to reply. I agree with Monty and Flavio here. Heidi has been doing an excellent job in helping OpenStack community about $topic, always in the open, which has been very appreciated. We, as a team, have agreed on re-iterating on a new proposal

Re: [openstack-dev] [telemetry] Triggering alarms on Swift notifications

Hello Mehdi. Thanks for response. See comments inline. 2017-02-16 15:25 GMT+02:00 Mehdi Abaakouk : > Hi, > > On Thu, Feb 16, 2017 at 03:04:52PM +0200, Denis Makogon wrote: > >> Greetings. >> >> Could someone provide any guidelines for checking why alarm or ok-action >>

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

On Thu, 2017-02-16 at 06:36 -0600, Monty Taylor wrote: > On 02/15/2017 07:54 PM, Dan Prince wrote: > > At the high level all of this sounds like a fine grand plan: "Help > > projects create mascots" with a common theme. On the ground level I > > can > > tell you it feels a lot more like you are

Re: [openstack-dev] [telemetry] Triggering alarms on Swift notifications

Hi, On Thu, Feb 16, 2017 at 03:04:52PM +0200, Denis Makogon wrote: Greetings. Could someone provide any guidelines for checking why alarm or ok-action webhooks are not being executed. Is it possible to investigate an issue by analyzing ceilometer and/or aodh logs? So, my devstack setup based

Re: [openstack-dev] [all] Do we need service types at all?! (Re: [octavia][sdk] service name for octavia)

On Thu, Feb 16, 2017 at 7:06 AM, Andrey Kurilin wrote: > Yes, I forgot about it. But it changes nothing. > Custom implementation of particular service should cover the same API as an > official one. For me, as for user, it doesn't metter if there is Keystone or >

[openstack-dev] [tripleo] tripleo-puppet-elements 6.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for tripleo-puppet-elements for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/tripleo-puppet-elements/ Unless release-critical issues are found that warrant a release candidate

Re: [openstack-dev] [all] Do we need service types at all?! (Re: [octavia][sdk] service name for octavia)

On Thu, Feb 16, 2017 at 1:57 PM, Radomir Dopieralski wrote: > I think that you have to remember that OpenStack doesn't only work with > officially approved OpenStack services, but with any services that have a > conforming API. > Yes, I forgot about it. But it changes

[openstack-dev] [tripleo] tripleo-image-elements 6.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for tripleo-image-elements for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/tripleo-image-elements/ Unless release-critical issues are found that warrant a release candidate respin,

[openstack-dev] [tripleo] tripleo-heat-templates 6.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for tripleo-heat-templates for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/tripleo-heat-templates/ Unless release-critical issues are found that warrant a release candidate respin,

[openstack-dev] [telemetry] Triggering alarms on Swift notifications

Greetings. Could someone provide any guidelines for checking why alarm or ok-action webhooks are not being executed. Is it possible to investigate an issue by analyzing ceilometer and/or aodh logs? So, my devstack setup based on master branch with local.conf (see

  1   2   >