Re: [openstack-dev] [nova] notification impact of moving the instance create to the conductor

On Wed, Feb 15, 2017 at 10:31 PM, Matt Riedemann wrote: On 2/15/2017 11:07 AM, Balazs Gibizer wrote: Hi, It seems that the Move instance creation to conductor commit [1] changed when and how the instance.delete notification is emitted for an unscheduled instance. Unfortunately the legacy

[openstack-dev] [storlets][swift][mascot] Storlets mascot

So the hard work getting into the big-tent was worth it! While the storlets team should have the final word, I will be very happy if the Swift community helped us in the process. Below are few options I have thought about. Comments / other suggestions are mostly welcome! Thanks very much, Eran

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

On Thu, Feb 16, 2017 at 5:26 AM Joshua Harlow wrote: > Radical idea, have each project (not libraries) contain a dockerfile > that builds the project into a deployable unit (or multiple dockerfiles > for projects with multiple components) and then it becomes the projects > responsibility for ensu

Re: [openstack-dev] [storlets][swift][mascot] Storlets mascot

Hi, Of these five options, I like sloth the best. Please also consider the stork -- the closest-sounding animal. Storklets... Doron From: Eran Rom To: "OpenStack Development Mailing List (not for usage questions)" Date: 16/02/2017 11:11 AM Subject:[openstack-dev] [storlets][sw

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

Le 16/02/2017 10:17, Neil Jerram a écrit : > On Thu, Feb 16, 2017 at 5:26 AM Joshua Harlow > wrote: > > Radical idea, have each project (not libraries) contain a dockerfile > that builds the project into a deployable unit (or multiple dockerfiles > for

[openstack-dev] [heat] heat 8.0.0.0rc2 (ocata)

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

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

Hi, > Hi Ironic team, > > [TL;DR - we agree to Miles’ proposal for two images (one mascot, one logo) > for different contexts. We’re looking for any final feedback on the stylized > logo for use on the website, while the PixieBoots mascot remains yours for > swag, etc.] > > I’m doing my best to

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

Hi everyone! When I started contribution to OpenStack long time ago, I asked about the reason of having two entities - service type and name; at that time I got an answer that service name is a name of the project that implements particular service type, so it is possible to have several projects

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

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. OpenStack itself provides implementations of those services, and you are right that it's unlikely that there will be two competing implem

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

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 crushing the spirit of > creativity and motivation for some of us. Ha

Re: [openstack-dev] Ceilometer event-list empty

On 15/02/17 09:27 PM, Sam Huracan wrote: > > I check mongodb has event collection, but it is empty > http://prntscr.com/e9b96w > > I do not see any error in Ceilometer log. > > Could you check my > ceilometer.conf? http://paste.openstack.org/show/598925/ >

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

On 16/02/17 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 crushing the spirit of creat

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

On 13/02/17 21:38 -0500, 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). #3 Flavio P

[openstack-dev] [tripleo] instack-undercloud 6.0.0.0rc1 (ocata)

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

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

Excerpts from Sylvain Bauza's message of 2017-02-16 10:55:14 +0100: > > Le 16/02/2017 10:17, Neil Jerram a écrit : > > On Thu, Feb 16, 2017 at 5:26 AM Joshua Harlow > > wrote: > > > > Radical idea, have each project (not libraries) contain a dockerfile > > t

[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 https://gist.github.com/denismako

[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] [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,

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 nothing. Custom implementat

[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 respin

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 > MyAwesomeKeystone, I want just an

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 o

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 cru

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 >> webhooks are not being exec

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] [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) Subject:  Re: [openstack-dev] [all] Do we need service types at all?! (Re: [oct

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 tea

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). wh

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 guidelines for checking

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] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef > Excerpts from Sylva

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 Mailing List (not for usage questions) > > Subject: Re: [open

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 is on it's way to get

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 do, but I don't think shov

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 https://cdn.rawgit.com/cc

[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 wit

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 "get_devices_details_list_and_failed_devi

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 both is really something p

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) Subject:  Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospecti

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 Betacloud Solutions GmbH

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] [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 project modules [1],[2] as 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 y

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 a

[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 be

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 Planas

[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 w

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 is as following: > > * We

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] [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 tools in the tent). Doing

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. Basically, the market would de

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 experience within OpenStack com

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) Subject:  Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective

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 support to keep them cu

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 mean > things that

[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 ___

[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 __ Open

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]. Neutro

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 Development Mailing List (not for usage questions) > > Su

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 questions) >> >> Subject: R

[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

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 >> time was spent b

[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 c

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 apprecia

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

[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

[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

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 metter if there is Keystone

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 situat

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 choices based on the work being done in th

[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 openstack/tripleo-ui failed Build failed. - tripleo-ui-nodejs6-

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 >>> as an >>> official on

[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 foreseea

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 would make choices based on the work bein

[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 wo

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 w

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 focus

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] [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 t

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, and that deployers and contributors >>>

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 cru

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 install"

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

On 16 Feb 2017, at 19:42, Fox, Kevin M mailto:kevin@pnnl.gov>> 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 pain is still too hi

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 feedba

[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 commits

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 t

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 wh

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 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 wants to have icons thei

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 wants to have icons thei

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 a

[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

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 redesigni

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 mo

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] [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 formall

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. Man

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 slo

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 > release, absolutely n

[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. Ethe

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 this

  1   2   >