[openstack-dev] [devstack] [tricircle] Problem in placement-api after installing Tricircle with DevStack

[Vega Cai]

In Nova Ocata release, deploying placement API is a must. The nova-compute
service will fail to start if [placement] section is not configured in
nova.conf.

DevStack script is updated to generate Apache configuration file for
placement API and it works fine in single region scenario.

However, in Tricircle, we will have multi-region deployment: one node runs
Keystone, Tricircle and other core services(like Nova, Neutron, Cinder),
another node just runs core services and we configure these services to
talk to Keystone in the first node. After updating codes to the newest
version, we find that we fail to boot an instance in the second node.

After digging into the log files, we find the reason is that, the placement
API Apache configuration file generated by DevStack doesn't grant necessary
access right to the placement API bin folder. In the first node where
Keystone is running, Apache configuration file for Keystone already grants
access right to "/usr/local/bin" folder, and this folder happens to be the
same folder placement API bin is located, so placement API works fine. But
in the second node, Keystone is not enabled, so request sent to placement
API is rejected and thus we fail to boot an instance.

One temporary workaround is to manually edit placement API configuration
file in the second node to add the following section:


Require all granted


and restart Apache. We test and it works. Later we are going to submit a
patch to DevStack for this problem.

BR
Zhiyuan
-- 
BR
Zhiyuan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [mistral][ptg] Mistral PTG schedule and detailed topic

[Renat Akhmerov]

Hi,

The etherpad for Mistral PTG sessions now has a schedule and all necessary 
details on each topic[1].

Have a look at let us know if you’d like to include/change anything else.

Everyone who has topic related to Mistral is welcome to join us. Even if your 
topic is not in the list we’ll find a time slot to discuss what you’re 
interested in.

[1] https://etherpad.openstack.org/p/mistral-ptg-pike 


Renat Akhmerov
@Nokia

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [neutron][taas] IRC Meeting Canceled (week of 2/20/2017)

[Soichi Shigeta]

 Hi,

Next week's TaaS IRC meeting is being canceled because of
  the week of OpenStack PTG.

  Regards,
  Soichi


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [oslo_messaging] Limiting the number of retries for kafka driver

[Elancheran Subramanian]

Yes, there is a config option for *oslo_messaging_rabbit* 
default_notification_retry_attempts 
http://docs.openstack.org/mitaka/config-reference/compute/rpc.html


The problem with Nova and Neutron provide the retry mechanism, there is no 
configuration on nova or neutron, which can be passed onto the 
also_messaging. I will add a patch so that it would pick up from the 
configuration in oslo_messaging itself.  

Thanks & Regards,
Cheran



On 2/14/17, 9:32 PM, "Ken Giusti"  wrote:

>On Tue, Feb 14, 2017 at 2:52 PM, Elancheran Subramanian
> wrote:
>> Hello All,
>> This is reg limiting the number of retries for Kafka driver support on 
>>Nova
>> and Neutron.
>>
>> While trying out the oslo messaging notifications support for Kafka on 
>>Nova
>> and Neutron, the Kafka driver doesn’t support limiting the number of 
>>retries
>> for failed messages. When I checked the code, currently there is no
>> configuration which support that, though the send_notification has retry
>> 
>>https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/_d
>>rivers/impl_kafka.py#L336
>> but it’s not set or passed from component’s (nova or neutron’s)
>> configuration. Is there any configuration which I’m missing? Please let 
>>me
>> know.
>>
>
>You haven't missed anything - the kafka driver doesn't provide a means
>to set a default retry via its configuration.
>The expectation is that the caller (nova/neutron) would provide a
>retry value when constructing a Notifier instance.
>
>There was such a config option for the rabbitmq driver
>(rabbit_max_retries) but that was removed because it broke
>*something* - can't remember exactly the reason tho, sorry.
>
>>
>> Thanks in advance,
>> Cheran
>>
>> 
>>_
>>_
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: 
>>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
>
>-- 
>Ken Giusti  (kgiu...@gmail.com)
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [stable][requirements] Logos / Mascots

[Tony Breeds]

HI All,
You've all seen many of the fly by so y'all know the drill.  Here are the,
I think, awesome logos/mascots for Requirements and Stable Branch maintenance

- [stable] Scarab: 
https://www.dropbox.com/sh/x5uh65yqqdge5ae/AABvq9ztd_MTE9GLZUPGibG4a?dl=0
- [requirements] Waterfall: 
https://www.dropbox.com/sh/p5hclpt07t9svw8/AAB0Ri3gJ8hogH5PSMtSSqJaa?dl=0

Yours Tony.


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Tony Breeds]

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 logic around proactive backports:
> https://review.openstack.org/#/c/427936/4/bugs-fixed-since.py@75, and
> I see backports proposed for the branch that is no longer supported
> and has broken gate setup.

It seems I setup the second wave and then neglected to ask the infra team to 
process them.

Infra tema (*cough* Josh *cough*) can you remove the branches marke Please EOL 
in

https://gist.githubusercontent.com/tbreeds/93cd346c37aa46269456f56649f0a4ac/raw/4f781426270cb2030f978f47b1f46dae6f5aecb4/liberty_eol_data.txt

Once that's done I can do a final pass for jobs that may break and we can drop
the devstack, devstack-gate and requirements branches.

Tony.


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [requirements] No team meeting Feb-15th @ 1000 UTC

[Tony Breeds]

Hi all,
We don't have anything specific on the agenda and we'll do the bulk of
our cycle's planning next week so I vote we give the US folks a morning off, I
go to bead early and the Eu team members use the time to get a coffee!

See many of you next week in Atlanta!

Yours Tony.


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Final mascot files

[Sridhar Ramaswamy]

Hi Tackers,

We got the "final" version of Tacker logo from Openstack marketing team.
Please take a look at the dropbox link below:





*I’m excited to finally be able to share final project logo files with you.
Inside this folder, you’ll find full-color and one-color versions of the
logo, plus a mascot-only version, in EPS, JPG and PNG formats. You can use
them on presentations and wherever else you’d like to add some team flair.
https://www.dropbox.com/sh/yyt1lazllah7ccf/AACkW8LkIiG32OXLYBqeP-RJa?dl=0
At
the PWG, we’ll have stickers for your team of the mascot, plus signage on
your room. I’m especially excited for the project teams to see all of the
logos together as one group, because they work beautifully together
stylistically while making each project’s mark distinctive.*

- Sridhar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Ceilometer event-list empty

[Sam Huracan]

Hi,

I'm unable to show event-list of ceilometer, meanwhile meter-list has data.
Ceilometer log does not any "ERROR".

My ceilometer.conf: http://paste.openstack.org/show/598925/
My ceilometer version: http://prntscr.com/e8wob6

I'm using OpenStack Mitaka.
But, with another system installing Gnocchi dispatcher, I can show
event-list.

Could you share some experience?
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Samuel Cassiba]

The HTML version is here:
https://s.cassiba.com/2017/02/14/making-the-kitchen-great-again-a-retrospective-on-openstack-chef
 


This was influenced by Graham Hayes' State of the Project for Designate:
http://graham.hayes.ie/posts/openstack-designate-where-we-are/ 


I have been asked recently "what is going on with the OpenStack-Chef project?",
"how is the state of the cookbooks?", and "hey sc, how are those integration
tests coming?". Having been the PTL for the Newton and Ocata cycles, yet
having not shipped a release, is the unthinkable, and deserves at least a
sentence or two.

It goes without saying, this is disheartening and depressing to me and
everybody that has devoted their time to making the cookbooks a solid
and viable method for deploying OpenStack. OpenStack-Chef is among the
oldest[1] and most mature solutions for deploying OpenStack, though it is
not the most feature-rich.


*TL;DR* if you don't want to keep going -
OpenStack-Chef is not in a good place and is not sustainable.


OpenStack-Chef has always been a small project with a big responsibility.
The Chef approach to OpenStack historically has required a level of
investment within the Chef ecosystem, which is a hard enough sell when you
started out with Puppet or Ansible. Despite the unicorns and rainbows of
being Chef cookbooks, OpenStack-Chef always asserted itself as an OpenStack
project first, up to and including joining the Big Tent, whatever it takes.
To beat that drum, we are OpenStack.

There is no *cool* factor from deploying and managing OpenStack using Chef,
unless you've been running Chef, because insert Xzibit meme here and jokes
about turtles. Unless you break something with automation, then it's
applause or facepalm. Usually both. At the same time.

As with any kitchen, it must be stocked and well maintained, and
OpenStack-Chef is no exception. Starting out, there was a vibrant community
producing organic, free-range code. Automation is invisible, assumed to be
there in the background. Once it's in place, it isn't touched again unless
it breaks. Upgrades in complex deployments can be fraught with error, even
in an automated fashion.

As has been seen in previous surveys[2], once an OpenStack release has chosen
by an operator, some tend to not upgrade for the next cycle or three, to get
the immediate bugs worked out. Though there are now multinode and upgrade
scenarios supported with the Puppet OpenStack and TripleO projects, they do
not use Chef, so Chef deployers do not directly benefit from any of this
testing.

Being a deployment project, we are responsible for not one aspect of
the OpenStack project but as many as can be reasonably supported.

We were very fortunate in the beginning, having support from public cloud
providers, as well as large private cloud providers. Stackalytics shows a
vibrant history, a veritable who's-who of OpenStack contributors, too many to
name. They've all moved on, working on other things.

As a previous PTL for the project once joked, the Chef approach to OpenStack
was the "other deployment tool that nobody uses". As time has gone by, that has
become more of a true statement.

There are a few of us still cooking away, creating new recipes and cookbooks. 
The
pilot lights are still lit and there's usually something simmering away on the
back burner, but there is no shouting of orders, and not every dish gets tasted.
We think there might be rats, too, but we’re too shorthanded to maintain the 
traps.

We have yet to see many (meaningful) contributions from the community, however.
We have some amazing deployers that file bugs, and if they can, push up a patch.
It delights me when someone other than a core weighs in on a review. They are
highly appreciated and incredibly valuable, but they are very tactical
contributions. A project cannot live on such contributions.

October 2015

  https://s.cassiba.com/images/oct-2015-deployment-decisions.png 


Where does that leave OpenStack-Chef? Let's take a look at the numbers:

+++
| Cycle  | Commits |
+++
| Havana   | 557|
+++
| Icehouse | 692|
+++
| Juno   | 424 |
+++
| Kilo | 474 |
+++
| Liberty| 259 |
+++
| Mitaka| 85   |
+++
| Newton   | 112 |
+++
| Ocata  | 78  |
+++

As of the time of this writing, Newton has not yet branched. Yes, you read
correctly. This means the Ocata cycle has gone to ensuring that Newton *just
funct

Re: [openstack-dev] [octavia][sdk] service name for octavia

[Dean Troyer]

On Tue, Feb 14, 2017 at 7:08 PM, Qiming Teng  wrote:
> When reviewing a recent patch that adds openstacksdk support to octavia,
> I found that octavia is using 'octavia' as its service name instead of
> 'loadbalancing' or 'loadbalancingv2' or something similar.

The service name is actually irrelevant from a technical point of
view. It is maintained for deployer configuration and is often used
just for branding purposes.  It is the service type that should
uniquely identify a service in the catalog.

> The overall suggestion is to use a word/phrase that indicates what a
> service do instead of the name of the project providing that service.

Correct, this is the service type.

> [2] Octavia service naming:
> http://git.openstack.org/cgit/openstack/octavia/tree/devstack/plugin.sh#n52

This points to Octavia's DevStack plugin configuration, which is by no
means authoritative.

There was a beginning of a service catalog type registry [3] that has
not gone beyond an initial proposal.  Sean Dague recently revived this
and I believe it will be discussed next week at the PTG.

dt

[3] https://git.openstack.org/cgit/openstack/service-types-authority

-- 

Dean Troyer
dtro...@gmail.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] FYI: cells v1 job is blocked

[Matt Riedemann]

On 2/14/2017 9:36 AM, Matt Riedemann wrote:

The fix is here:

https://review.openstack.org/#/c/433707/

That's approved for master, but if you're seeing failures in that job
since yesterday that's why.

I'm going to have to backport that all the way back to stable/mitaka too.



The fix is merged on master, stable/ocata and stable/newton now.

stable/mitaka is blocked on the ceph job which is voting in 
stable/mitaka and also failing on test_stamp_pattern now too but for a 
different reason:


https://bugs.launchpad.net/nova/+bug/1664793

--

Thanks,

Matt Riedemann

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all][logos] License for new project mascots

[Qiming Teng]

A related question: uploading file to wiki.openstack.org has been
blocked? I'm getting the following error when trying to do so.

Action failed

Could not open lock file for
"mwstore://local-backend/local-public/2/22/OpenStack_Project_Senlin_horizontal.jpg".


Regards,
 Qiming

On Tue, Feb 14, 2017 at 03:19:39PM +, Hayes, Graham wrote:
> Hi,
> 
> I did a bit of digging through email, and I *thought* someone had asked
> about the license that these logos were being released under. Turns out
> it was me, and I don't seem to have gotten a response about it.
> 
> So - what license are the new logos / mascots under?
> 
> Is the same as the wiki? [1] If not, it could present problems for
> people to upload copies of the logo to the wiki, as it assumes all
> content is CC-BY.
> 
> Thanks
> 
> - Graham
 


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla] Phoenix area meet up with the topic of Kolla Feb 15th @ 21:00 UTC

[Steven Dake (stdake)]

Hey folks,

Webex has undergone an upgrade and anyone from any geography can participate 
via Linux machines using a web browser rather than only a Mac or Windows 
client.  All of the information I previously offered about Linux clients no 
longer holds for this meetup February 15th @21:00 UTC.  The rest of the 
information is correct.

Hope to see you for the live stream or if your in the greater Phoenix area, in 
person!

Regards
-steve


From: "Steven Dake (stdake)" 
Date: Tuesday, January 31, 2017 at 5:56 PM
To: "OpenStack Development Mailing List (not for usage questions)" 

Cc: Toby Cardone 
Subject: [kolla] Phoenix area meet up with the topic of Kolla Feb 15th @ 21:00 
UTC

Hey folks,

Toby Cardone has kindly organized a local (to me) community meetup hosted by 
the Red Hat Software User Group at Insight’s facilities in Tempe, AZ with the 
topic of Kolla on February 15th, 2017 at 21:00 UTC.  Several folks in the Kolla 
IRC channel have asked if remote participation is possible.  I asked Toby and 
he said that sounded great!

The meetup information in more detail is here:

If you are interested in participating the community seminar more information 
can be found here:
https://www.meetup.com/PhoenixRedHatSoftwareUserGroup/events/237219035/

You don’t need to register at the meetup site to attend remotely; only local 
attendance requires signup (to make sure the event’s facilities are not 
overbooked).  Much of this material may be old hat for the community in general 
although I do plan to provide a live demo of the current state of sausage 
making in kolla-kubernetes.

I am using webex for remote participation.  I know this is not ideal since it 
doesn’t run on Linux 64 bit.  One workaround is to use your phone, a 32bit 
android tablet, or a 32 bit linux vm (pretty sure this last one works but not 
100% positive) if you don’t have access to a mac or windows platform.  
Depending on attendance webex may be pokey – please take care to sign in up to 
15 minutes early in the event webex is overloaded.

The remote participation webex information follows:

Wednesday February 15th, 2017 @ 2PM MST (21:00 UTC)
Meeting: 
https://cisco.webex.com/ciscosales/j.php?MTID=mee2e81571288da5c183af4ae2fff0d8e
Meeting number (access code): 208 707 718
Password: OpenStackKolla
Passowrd on callin lines: 67367822
Global dialin #s: 
https://cisco.webex.com/ciscosales/globalcallin.php?serviceType=MC&ED=374661952&tollFree=1

Regards,
-steve

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [octavia][sdk] service name for octavia

[Qiming Teng]

When reviewing a recent patch that adds openstacksdk support to octavia,
I found that octavia is using 'octavia' as its service name instead of
'loadbalancing' or 'loadbalancingv2' or something similar.

The overall suggestion is to use a word/phrase that indicates what a
service do instead of the name of the project providing that service.

Below is the list of the service types currently supported by
openstacksdk:

'alarming',# aodh
'baremetal',   # ironic
'clustering',  # senlin
'compute', # nova
'database',# trove
'identity',# keystone
'image',   # glance
'key-manager', # barbican
'messaging',   # zaqar
'metering',# ceilometer
'network', # neutron
'object-store',   # swift
'octavia',# <--- this is an exception
'orchestration',  # heat
'volume', # cinder
'workflowv2', # mistral

While I believe this has been discussed about a year ago, I'm not sure
if there are things we missed so I'm brining this issue to a broader
audience for discussion.

Reference:

[1] Patch to python-openstacksdk:
https://review.openstack.org/#/c/428414
[2] Octavia service naming:
http://git.openstack.org/cgit/openstack/octavia/tree/devstack/plugin.sh#n52

Regards, 
 Qiming


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tacker] Virtual PTG Meetup - Wed Feb 22

[Sridhar Ramaswamy]

Folks -

Tacker team will meet virtually for upcoming Pike PTG. Given the
global audience, we will do one 5 - 6 hour conference call starting
Wednesday, February 22, 2017 -  05:00:00 UTC [1]. Please mark your
calendars.

Here is the PTG etherpad [2]. Feel free to add topics and candidate
pike tasks in the etherpad.

- Sridhar

[1] 
https://www.timeanddate.com/worldclock/meetingtime.html?iso=20170222&p1=283&p2=33&p3=235&p4=176
[2] https://etherpad.openstack.org/p/tacker-pike-grooming

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Cinder] Project mascot available

[Jay S Bryant]

On 2/14/2017 5:28 PM, Mike Perez wrote:

On 08:24 Feb 14, Walter Boring wrote:

How does Horse translate to Cinder block?
I don't get it.  Our original Cinder block made a lot of sense, considering
the name of the project.


This is...just an odd horse for no particular reason.

As I remember from the midcycle meetup discussion, we were more interested in
the rear end of the horse being shown, with the horse looking back.
That was the plan, but our request for the orientation of the horse was 
obviously not heard.  I will still hoping the horse would at least be 
branded with a Cinder block, or carrying one.  :-(  GIMP, here I come!



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Cinder] Project mascot available

[Mike Perez]

On 08:24 Feb 14, Walter Boring wrote:
> How does Horse translate to Cinder block?
> I don't get it.  Our original Cinder block made a lot of sense, considering
> the name of the project.
> 
> 
> This is...just an odd horse for no particular reason.

As I remember from the midcycle meetup discussion, we were more interested in
the rear end of the horse being shown, with the horse looking back.

-- 
Mike Perez


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ux] Future of the OpenStack UX team

[Shamail Tahir]

On Wed, Jan 4, 2017 at 9:43 AM, Thierry Carrez 
wrote:

> Hi everyone,
>
> Piet recently reached out to me to explain that he won't be able to
> continue in his role as OpenStack UX team's PTL. Since he created the
> team and spent a lot of time coordinating its activities, that raises
> the question of the future of the OpenStack UX team.
>
> The situation was discussed at the TC meeting yesterday[1] and the
> general feeling was that there was a lot of value in a separate team
> centralizing things like Persona definition and facilitating
> properly-conducted UX surveys. That said, if nobody is able to dedicate
> the time that effort needs, we could also disband the centralized team
> and encourage every project to adopt the tools and techniques that were
> built and introduced by the UX team in the past years.
>
> So... What are your thoughts on those options ? Do we have a volunteer
> (or more than one) to take over UX PTLship ?
>
Hi Thierry,

I had set up a doodle poll to gauge interest/establish a new meeting time
for the UX working group but we only had one additional response.  How
should we proceed since it seems there was low interest in participation?

>
> [1]
> http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-
> 01-03-20.00.log.html#l-404
>
> --
> Thierry Carrez (ttx)
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Thanks,
Shamail Tahir
t: @ShamailXD
tz: Eastern Time
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all][logos] License for new project mascots

[Doug Hellmann]

Excerpts from Doug Hellmann's message of 2017-02-14 16:34:55 -0500:
> Excerpts from Fox, Kevin M's message of 2017-02-14 18:55:51 +:
> > Are there hosted images we can link to?
> 
> Maybe we can add the logos to the team pages published through the
> governance repo.
> 
> Doug

Here's an example: https://review.openstack.org/433958

> 
> > 
> > Thanks,
> > Kevin
> > 
> > From: Heidi Joy Tretheway [heidi...@openstack.org]
> > Sent: Tuesday, February 14, 2017 10:40 AM
> > To: Hayes, Graham
> > Cc: OpenStack Development Mailing List (not for usage questions)
> > Subject: Re: [openstack-dev] [all][logos] License for new project mascots
> > 
> > Hi Graham & devs,
> > 
> > We intend to license under the CC-BY-ND Creative Commons Attribution-No 
> > Derivatives license. That means that via the license you can freely print 
> > on shirts, stickers, etc., but you can’t modify the logos (e.g. add an 
> > ecosystem company’s logo into the mascot). We’ll send out additional info 
> > once that licensing is complete, and thank you for the question!
> > 
> > Almost all logos are distributed now, with a few tweaks needed on text 
> > (which we’ll take care of shortly). You’re welcome to use these logos now, 
> > at the PTG, and beyond. Ironic and TripleO have both proposed 
> > solutions/compromises and we TRULY appreciate this - we’re feeding these 
> > back to our illustrators so that they can produce a version for your 
> > review/approval.
> > 
> > Thanks for your extreme patience as I’m fielding quite a lot of questions! 
> > I’ll do my best to reply to each ML thread promptly.
> > 
> > > On Feb 14, 2017, at 7:19 AM, Hayes, Graham  wrote:
> > >
> > > Hi,
> > >
> > > I did a bit of digging through email, and I *thought* someone had asked
> > > about the license that these logos were being released under. Turns out
> > > it was me, and I don't seem to have gotten a response about it.
> > >
> > > So - what license are the new logos / mascots under?
> > >
> > > Is the same as the wiki? [1] If not, it could present problems for
> > > people to upload copies of the logo to the wiki, as it assumes all
> > > content is CC-BY.
> > >
> > > Thanks
> > >
> > > - Graham
> > >
> > > 1 - https://creativecommons.org/licenses/by/3.0/
> > 
> 

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [oslo_messaging] Limiting the number of retries for kafka driver

[gordon chung]

On 14/02/17 02:52 PM, Elancheran Subramanian wrote:
> Hello All,
> This is reg limiting the number of retries for Kafka driver support on
> Nova and Neutron.
>
> While trying out the oslo messaging notifications support for Kafka on
> Nova and Neutron, the Kafka driver doesn’t support limiting the number
> of retries for failed messages. When I checked the code, currently there
> is no configuration which support that, though the send_notification has
> retry 
> https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/_drivers/impl_kafka.py#L336
>  but
> it’s not set or passed from component’s (nova or neutron’s)
> configuration. Is there any configuration which I’m missing? Please let
> me know.
>

disclaimer: i didn't try the following...

you should be able to pass a retry value from when you create Notifier 
obj. like ceilometer[1]... i don't think nova uses it[2].

[1] 
https://github.com/openstack/ceilometer/blob/master/ceilometer/publisher/messaging.py#L205
[2] 
https://github.com/openstack/nova/blob/8557aaeb2f3818de352ce7d0b7bf62d74ddffc4e/nova/rpc.py#L82-L98

cheers,
-- 
gord

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all][logos] License for new project mascots

[Jeremy Stanley]

On 2017-02-15 08:42:03 +1100 (+1100), Tony Breeds wrote:
[...]
> Would that mean adding a copy of the logo to the governance repo?  I thought
> there was a docutils issues that meant external links were forbidden?

External sources are generally only a concern for documentation
which is being repackaged. I doubt our governance site gets
repackaged by distributions.
-- 
Jeremy Stanley

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all][logos] License for new project mascots

[Tony Breeds]

On Tue, Feb 14, 2017 at 04:34:55PM -0500, Doug Hellmann wrote:
> Excerpts from Fox, Kevin M's message of 2017-02-14 18:55:51 +:
> > Are there hosted images we can link to?
> 
> Maybe we can add the logos to the team pages published through the
> governance repo.

Would that mean adding a copy of the logo to the governance repo?  I thought
there was a docutils issues that meant external links were forbidden?

Tony.


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all][logos] License for new project mascots

[Doug Hellmann]

Excerpts from Fox, Kevin M's message of 2017-02-14 18:55:51 +:
> Are there hosted images we can link to?

Maybe we can add the logos to the team pages published through the
governance repo.

Doug

> 
> Thanks,
> Kevin
> 
> From: Heidi Joy Tretheway [heidi...@openstack.org]
> Sent: Tuesday, February 14, 2017 10:40 AM
> To: Hayes, Graham
> Cc: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [all][logos] License for new project mascots
> 
> Hi Graham & devs,
> 
> We intend to license under the CC-BY-ND Creative Commons Attribution-No 
> Derivatives license. That means that via the license you can freely print on 
> shirts, stickers, etc., but you can’t modify the logos (e.g. add an ecosystem 
> company’s logo into the mascot). We’ll send out additional info once that 
> licensing is complete, and thank you for the question!
> 
> Almost all logos are distributed now, with a few tweaks needed on text (which 
> we’ll take care of shortly). You’re welcome to use these logos now, at the 
> PTG, and beyond. Ironic and TripleO have both proposed solutions/compromises 
> and we TRULY appreciate this - we’re feeding these back to our illustrators 
> so that they can produce a version for your review/approval.
> 
> Thanks for your extreme patience as I’m fielding quite a lot of questions! 
> I’ll do my best to reply to each ML thread promptly.
> 
> > On Feb 14, 2017, at 7:19 AM, Hayes, Graham  wrote:
> >
> > Hi,
> >
> > I did a bit of digging through email, and I *thought* someone had asked
> > about the license that these logos were being released under. Turns out
> > it was me, and I don't seem to have gotten a response about it.
> >
> > So - what license are the new logos / mascots under?
> >
> > Is the same as the wiki? [1] If not, it could present problems for
> > people to upload copies of the logo to the wiki, as it assumes all
> > content is CC-BY.
> >
> > Thanks
> >
> > - Graham
> >
> > 1 - https://creativecommons.org/licenses/by/3.0/
> 

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [oslo_messaging] Limiting the number of retries for kafka driver

[Ken Giusti]

On Tue, Feb 14, 2017 at 2:52 PM, Elancheran Subramanian
 wrote:
> Hello All,
> This is reg limiting the number of retries for Kafka driver support on Nova
> and Neutron.
>
> While trying out the oslo messaging notifications support for Kafka on Nova
> and Neutron, the Kafka driver doesn’t support limiting the number of retries
> for failed messages. When I checked the code, currently there is no
> configuration which support that, though the send_notification has retry
> https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/_drivers/impl_kafka.py#L336
> but it’s not set or passed from component’s (nova or neutron’s)
> configuration. Is there any configuration which I’m missing? Please let me
> know.
>

You haven't missed anything - the kafka driver doesn't provide a means
to set a default retry via its configuration.
The expectation is that the caller (nova/neutron) would provide a
retry value when constructing a Notifier instance.

There was such a config option for the rabbitmq driver
(rabbit_max_retries) but that was removed because it broke
*something* - can't remember exactly the reason tho, sorry.

>
> Thanks in advance,
> Cheran
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Ken Giusti  (kgiu...@gmail.com)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] Cells meeting on Feb-15 is canceled

[Matt Riedemann]

On 2/14/2017 1:46 PM, Dan Smith wrote:

Hi all,

In an epic collision of cosmic coincidences, four of the primary cells
meeting attendees have a conflict tomorrow. Since there won't really be
anyone around to run (or attend) the meeting, we'll have to cancel again.

Next week we will be at the PTG so any meeting will be done there.

So, expect the next cells meeting to be on March 1.

Thanks!

--Dan

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



Just a reminder but please put any cells-related stuff you want to talk 
about in the PTG etherpad here:


https://etherpad.openstack.org/p/nova-ptg-pike

I've got a section for cells things in there now but I can't tell if 
it's sparse or not.


--

Thanks,

Matt Riedemann

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] New mascot design

[Heidi Joy Tretheway]

Hi Ironic team, 

Thanks for your feedback, especially helping us to ensure that the mascot would 
be culturally appropriate worldwide. Our most recent offering to the team was 
generally liked, with a request to cut it off at the middle (head/arms/top of 
the stomach) per Dmitry. Note this version has the sticks (as drumsticks) in 
his paw, based on your feedback.

 

As a reminder, you can still use the original PixieBoots mascot on 
shirts/stickers/swag, but we need a stylistically consistent logo for use on 
official channels (such as the website) to appear as part of the logo family. 

If there are any other thoughts/feedback, we’d welcome them here. Then I’ll 
take this back to the illustrators. One issue is that all mascots are either 
head-only, or full-body, so this doesn’t precisely match them, which is why 
we’re asking the illustrators to take another stab at this version to try to 
make it fit better.

While you won’t see any Ironic logo at the PTG, my hope is that we can produce 
a final version and some nice swag for your team for the Boston Summit. Thanks 
again for doing your best to find a compromise that fits with the rest of the 
teams!

—Heidi Joy__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [keystone] 2017-02-21 weekly meeting cancelled

[Lance Bragstad]

Hi all,

I wanted to remind everyone that we won't have our weekly meeting next week
(2017-02-21), since most of us with either be at the PTG or in transit.
Anything we need to talk about will be done in person.

We will pick back up on the 26th.

Thanks,

Lance
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [oslo_messaging] Limiting the number of retries for kafka driver

[Elancheran Subramanian]

Hello All,
This is reg limiting the number of retries for Kafka driver support on Nova and 
Neutron.

While trying out the oslo messaging notifications support for Kafka on Nova and 
Neutron, the Kafka driver doesn’t support limiting the number of retries for 
failed messages. When I checked the code, currently there is no configuration 
which support that, though the send_notification has retry 
https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/_drivers/impl_kafka.py#L336
 but it’s not set or passed from component’s (nova or neutron’s) configuration. 
Is there any configuration which I’m missing? Please let me know.

Thanks in advance,
Cheran
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova] Cells meeting on Feb-15 is canceled

[Dan Smith]

Hi all,

In an epic collision of cosmic coincidences, four of the primary cells
meeting attendees have a conflict tomorrow. Since there won't really be
anyone around to run (or attend) the meeting, we'll have to cancel again.

Next week we will be at the PTG so any meeting will be done there.

So, expect the next cells meeting to be on March 1.

Thanks!

--Dan

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [murano][ptg] Murano PTG Schedule

[MONTEIRO, FELIPE C]

Hi all,

First of all, I would like to thank everyone for "electing" me PTL for Murano 
during Pike, even if I didn't run against anyone. I have been busy getting 
caught up and adjusting into my new role.

== PTG Schedule ==

Onto business. With the Atlanta PTG fast-approaching, there are some critical 
items that need to be discussed. While Murano is not included in the confirmed 
team rooms so far [1], it will be meeting up at the PTG. However, Murano does 
not currently have a PTG schedule ironed out. If you are interested in 
attending, please fill out the following etherpad document with topics you're 
interested in discussing under "Topics": 
https://etherpad.openstack.org/p/murano-atlanta-ptg Also list any schedule 
constraints you have under "Schedule".

== PTG Rooms ==

As mentioned, Murano has not confirmed a team room. This is something I am 
working on. However, an etherpad was created for extra discussion rooms [2]. 
These can be used for inter-project discussions or for Murano-only discussions. 
Currently, there are still rooms available, but first we need to consolidate 
our schedule.

== PTG Attendees ==

Currently, I know that the following Murano developers will be in attendance at 
the Atlanta PTG (including myself):

* Felipe Monteiro

* Kirill Zaitsev

* Stan Lagun

[1] https://www.openstack.org/ptg/
[2] https://ethercalc.openstack.org/Pike-PTG-Discussion-Rooms

Thank You,
Felipe Monteiro
Murano PTL

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] TripleO Ocata release blockers

[Ben Nemec]

On 02/13/2017 12:52 PM, Ben Nemec wrote:



On 02/12/2017 02:24 PM, Emilien Macchi wrote:

Quick updates:

- All FFEs patches have been merged except:
https://review.openstack.org/#/c/330050/ - so we're green on this
side.
- Upgrade team is still working on automation to upgrade from newton
to ocata.
- ovb-updates (CI job with IPv6) doesn't pass -
https://bugs.launchpad.net/tripleo/+bug/1663187 - See
https://review.openstack.org/#/c/432761/ for a potential fix.
- our CI is testing OpenStack from trunk, we have regular promotions.

At this stage, I believe we can release TripleO Ocata RC1 by Thursday
17th, considering Congress will be landed, 1663187 fixed, no new
blocker in CI.

I think upgrade folks will still have some patches after Thursday, but
I don't think it's a big deal, we'll just backport them to
stable/ocata.

Please let us know asap if you see more blockers for Ocata RC1.


I would like to propose https://bugs.launchpad.net/tripleo/+bug/1664331
as a release blocker, mostly because if someone ran an undercloud
upgrade without us fixing that I believe it could break their undercloud
Heat in a way that would be difficult to recover from (should probably
discuss that with the Heat team though to make sure I'm not wrong about
the impact).

If we can't fix it before release, then I think we should at least merge
the _stackrc_exists fix and essentially block undercloud upgrades until
we fix the member role logic.  That way we can backport the fix knowing
that no one has run a bad upgrade.


I take it all back. :-)

After some more investigation into this, I discovered that this is a 
workaround for a problem that dates back to the downstream-only kilo 
release, so it's absence isn't actually a critical problem.  There's a 
simple manual workaround that users would have had to use in the 
intervening releases anyway.


It would still be nice to fix this, but it doesn't need to block the 
release.


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Hongbin Lu]

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 choose a mascot from the natural world, which can be an animal (i.e. fish, 
bird), natural feature (i.e. waterfall) or other natural element (i.e. flame).
* Once we choose a mascot, I communicate the choice with OpenStack foundation 
staff.
* Someone will work on a draft based on the style of the family of logos.
* The draft will be sent back to us for approval.

The final mascot will be used to present our team. All, any idea for the mascot 
choice?

[1] https://www.openstack.org/project-mascots/

Best regards,
Hongbin
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all][logos] License for new project mascots

[Fox, Kevin M]

Are there hosted images we can link to?

Thanks,
Kevin

From: Heidi Joy Tretheway [heidi...@openstack.org]
Sent: Tuesday, February 14, 2017 10:40 AM
To: Hayes, Graham
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [all][logos] License for new project mascots

Hi Graham & devs,

We intend to license under the CC-BY-ND Creative Commons Attribution-No 
Derivatives license. That means that via the license you can freely print on 
shirts, stickers, etc., but you can’t modify the logos (e.g. add an ecosystem 
company’s logo into the mascot). We’ll send out additional info once that 
licensing is complete, and thank you for the question!

Almost all logos are distributed now, with a few tweaks needed on text (which 
we’ll take care of shortly). You’re welcome to use these logos now, at the PTG, 
and beyond. Ironic and TripleO have both proposed solutions/compromises and we 
TRULY appreciate this - we’re feeding these back to our illustrators so that 
they can produce a version for your review/approval.

Thanks for your extreme patience as I’m fielding quite a lot of questions! I’ll 
do my best to reply to each ML thread promptly.

> On Feb 14, 2017, at 7:19 AM, Hayes, Graham  wrote:
>
> Hi,
>
> I did a bit of digging through email, and I *thought* someone had asked
> about the license that these logos were being released under. Turns out
> it was me, and I don't seem to have gotten a response about it.
>
> So - what license are the new logos / mascots under?
>
> Is the same as the wiki? [1] If not, it could present problems for
> people to upload copies of the logo to the wiki, as it assumes all
> content is CC-BY.
>
> Thanks
>
> - Graham
>
> 1 - https://creativecommons.org/licenses/by/3.0/


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all][logos] License for new project mascots

[Heidi Joy Tretheway]

Hi Graham & devs, 

We intend to license under the CC-BY-ND Creative Commons Attribution-No 
Derivatives license. That means that via the license you can freely print on 
shirts, stickers, etc., but you can’t modify the logos (e.g. add an ecosystem 
company’s logo into the mascot). We’ll send out additional info once that 
licensing is complete, and thank you for the question!

Almost all logos are distributed now, with a few tweaks needed on text (which 
we’ll take care of shortly). You’re welcome to use these logos now, at the PTG, 
and beyond. Ironic and TripleO have both proposed solutions/compromises and we 
TRULY appreciate this - we’re feeding these back to our illustrators so that 
they can produce a version for your review/approval. 

Thanks for your extreme patience as I’m fielding quite a lot of questions! I’ll 
do my best to reply to each ML thread promptly. 
 
> On Feb 14, 2017, at 7:19 AM, Hayes, Graham  wrote:
> 
> Hi,
> 
> I did a bit of digging through email, and I *thought* someone had asked
> about the license that these logos were being released under. Turns out
> it was me, and I don't seem to have gotten a response about it.
> 
> So - what license are the new logos / mascots under?
> 
> Is the same as the wiki? [1] If not, it could present problems for
> people to upload copies of the logo to the wiki, as it assumes all
> content is CC-BY.
> 
> Thanks
> 
> - Graham
> 
> 1 - https://creativecommons.org/licenses/by/3.0/


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Heidi Joy Tretheway]

Hi TripleO team, 

We can definitely find a middle ground here. Thanks so much for the feedback. 
I’ll send these examples on to the illustrators and I think we can make it 
work. I appreciate your willingness to compromise!

> On Feb 14, 2017, at 8:57 AM, Carlos Camacho Gonzalez  
> wrote:
> 
> Hello Heidi,
> 
> I think most of us already agreed on the fact that our current logo was 
> created by developers and we like it.
> The idea should be to iterate over our current logo to make it fit the 
> foundation guidelines.
> 
> I don't think is hard to do it, I can give you some examples (***The owl 
> colors were randomly chosen).
> 
> https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_tripleo_logo_h.pdf
>  
> 
> https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_tripleo_logo_h.png
>  
> 
> https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_tripleo_logo_h.svg
>  
> 
> https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_tripleo_logo_v.pdf
>  
> 
> https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_tripleo_logo_v.png
>  
> 
> https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_tripleo_logo_v.svg
>  
> 
> 
> Please just let me know if you need any further information/feedback/help.
> 
> Cheers,
> Carlos.
> 
> 
> 
> On Tue, Feb 14, 2017 at 3:44 PM, Emilien Macchi  > wrote:
> >
> > Heidi,
> >
> > TripleO team discussed about the logo this morning during our weekly 
> > meeting.
> > We understood that we had to change our existing logo because it
> > doesn't meet OpenStack themes requirements, and that's fine.
> >
> > Though we would like you to re-iterate on a new logo that would be a
> > variation on the current logo that moves closer to the foundation.
> >
> > Our existing logo is: http://tripleo.org/_static/tripleo_owl.svg 
> > 
> >
> > Please let us know if you can prepare a new logo close to this one,
> > and I think we would find a middle ground here.
> >
> > Thanks a lot,
> >
> > On Tue, Feb 14, 2017 at 7:30 AM, Carlos Camacho Gonzalez
> > mailto:ccama...@redhat.com>> wrote:
> > > I'll vote also for option 1 if we can keep it.
> > >
> > > One thing, you can see how designers have iterated over ironic's logo
> > > http://lists.openstack.org/pipermail/openstack-dev/attachments/20170201/a016f685/attachment.png
> > >  
> > > 
> > > to fit the OpenStack illustration style.
> > >
> > > Is it possible for designers to iterate over
> > > http://tripleo.org/_static/tripleo_owl.svg 
> > >  to make it fit the 
> > > guidelines?
> > >
> > > Cheers,
> > > Carlos.
> > >
> > > On Tue, Feb 14, 2017 at 12:34 PM, Lucas Alvares Gomes
> > > mailto:lucasago...@gmail.com>> wrote:
> > >>
> > >> Hi,
> > >>
> > >> Just a FYI, we have had similar discussions about the proposed logo for
> > >> Ironic, there's still many unanswered questions but, if you guys are
> > >> interested this is the link to the ML thread:
> > >> http://lists.openstack.org/pipermail/openstack-dev/2017-February/111401.html
> > >>  
> > >> 
> > >>
> > >> Cheers,
> > >> Lucas
> > >>
> > >> On Tue, Feb 14, 2017 at 2: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).
> > >>>
> > >>>
> > >>> Personally, I would vote for keeping our existing logo (1.) unless
> > >>> someone has time to create another one or if the team likes the proposed
> > >>> one.
> > >>>
> > >>> The reason why I want to keep our logo is because our current logo was
> > >>> created by TripleO devs, we like it and we already have tee-shirts and 
> > >>> other
> > >>> goodies with it. I don't see any good reason to change it.
> > >>>
> > >>> Discussion is open and we'll vote as a team.
> > >>>
> > >>> Thanks,
> > >>>
> > >>> Emilien.
> > >>>
> > >>> --

Re: [openstack-dev] [Neutron] Alternative approaches for L3 HA

[Assaf Muller]

On Fri, Feb 10, 2017 at 12:27 PM, Anna Taraday
 wrote:
> Hello everyone!
>
> In Juno in Neutron was implemented L3 HA feature based on Keepalived (VRRP).
> During next cycles it was improved, we performed scale testing [1] to find
> weak places and tried to fix them. The only alternative for L3 HA with VRRP
> is router rescheduling performed by Neutron server, but it is significantly
> slower and depends on control plane.
>
> What issues we experienced with L3 HA VRRP?
>
> Bugs in Keepalived (bad versions) [2]
> Split brain [3]
> Complex structure (ha networks, ha interfaces) - which actually cause races
> that we were fixing during Liberty, Mitaka and Newton.
>
> This all is not critical, but this is a bad experience and not everyone
> ready (or want) to use Keepalived approach.
>
> I think we can make things more flexible. For example, we can allow user to
> use external services like etcd instead of Keepalived to synchronize current
> HA state across agents. I've done several experiments and I've got failover
> time comparable to L3 HA with VRRP. Tooz [4] can be used to abstract from
> concrete backend. For example, it can allow us to use Zookeeper, Redis and
> other backends to store HA state.
>
> What I want to propose?
>
> I want to bring up idea that Neutron should have some general classes for L3
> HA which will allow to use not only Keepalived but also other backends for
> HA state. This at least will make it easier to try some other approaches and
> compare them with existing ones.
>
> Does this sound reasonable?

I understand that the intention is to add pluggability upstream so
that you could examine the viability of alternative solutions. I'd
advise instead to do the research locally, and if you find concrete
benefits to an alternative solution, come back, show your work and
have a discussion about it then. Merging extra complexity in the form
of a plug point without knowing if we're actually going to need it
seems risky.

On another note, after years of work the stability issues have largely
been resolved and L3 HA is in a good state with modern releases of
OpenStack. It's not a authoritative solution in the sense that it
doesn't cover every possible failure mode, but it covers the major
ones and in that sense better than not having any form of HA, and as
you pointed out the existing alternatives are not in a better state.
The subtext in your email is that now L3 HA is technically where we
want it, but some users are resisting adoption because of bad PR or a
bad past experience, but not for technical reasons. If that is the
case, then perhaps some good PR would be a more cost effective
investment than investigating, implementing, stabilizing and
maintaining a different backend that will likely take at least a cycle
to get merged and another 1 to 2 cycles to iron out kinks. Would you
have a critical mass of developers ready to support a pluggable L3 HA
now and in the long term?

Finally, I can share that L3 HA has been the default in RDO-land for a
few cycles now and is being used widely and successfully, in some
cases at significant scale.

>
> [1] -
> http://docs.openstack.org/developer/performance-docs/test_results/neutron_features/index.html
> [2] - https://bugs.launchpad.net/neutron/+bug/1497272
> https://bugs.launchpad.net/neutron/+bug/1433172
> [3] - https://bugs.launchpad.net/neutron/+bug/1375625
> [4] - http://docs.openstack.org/developer/tooz/
>
>
>
>
> --
> Regards,
> Ann Taraday
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Call for mentors and funding - Outreachy

[John Dickinson]

On 13 Feb 2017, at 20:17, Mahati C wrote:

> Hello everyone,
>
> An update on the Outreachy program, including a request for volunteer
> mentors and funding. For those of you who are not aware, Outreachy helps
> people from underrepresented groups get involved in free and open source
> software  by matching interns with established mentors in the upstream
> community. For more info, please visit:
> https://wiki.openstack.org/wiki/Outreachy
>
> We so far have a confirmation for three spots for OpenStack in this round
> of Outreachy. But we are receiving more applicants who are interested in
> contributing to different OpenStack projects. Interested mentors - please
> publish your project ideas to this page
> https://wiki.openstack.org/wiki/Internship_ideas. Here is a link that helps
> you get acquainted with mentorship process:
> https://wiki.openstack.org/wiki/Outreachy/Mentors
>
> We are looking for additional sponsors to help support the increase in
> OpenStack applicants. The sponsorship cost is 6,500 USD per intern, which
> is used to provide them a stipend for the three-month program. You can
> learn more about sponsorship here:
> https://wiki.gnome.org/Outreachy/Admin/InfoForOrgs#Action
>
> Outreachy has been one of the most important and effective diversity
> efforts we’ve invested in. It has evidently been a way to retain new
> contributors, we’ve had some amazing participants become long-term
> contributors to our community.
>
> Please help spread the word. If you are interested in becoming a mentor or
> sponsoring an intern, please contact me (mahati.chamarthy AT intel.com) or
> Victoria (victoria AT redhat.com).
>
> Thanks,
> Mahati


As someone who's participated as a mentor more than once, I'd definitely 
encourage anyone involved in upstream OpenStack work to consider doing this. 
You don't have to have any "special" qualifications! You're fine just the way 
you are! All that's needed is a willingness to want to see others succeed. If 
you already help other people in the community out by giving good reviews and 
answering questions in IRC, you're already doing 90% of what's needed to be an 
Outreachy mentor. In my experience, it's also good to spend 1-3 hours a week as 
"office hours" or on a short video chat with the mentee, but that's it. The 
extra commitment is not burdensome. Overall, it's a rewarding experience for 
everyone. Please consider being a mentor.

--John




signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] RefStack logo files

[Catherine Cuong Diep]

Hello RefStack team,

Here is our mascot!  Thanks to Heidi and team, it looks really nice!

Catherine Diep
- Forwarded by Catherine Cuong Diep/San Jose/IBM on 02/14/2017 09:24 AM
-

From:   Heidi Joy Tretheway 
To: Catherine Cuong Diep/San Jose/IBM@IBMUS
Date:   02/13/2017 03:15 PM
Subject:RefStack logo files



Hi Catherine,

I’m excited to finally be able to share final project logo files with you.
Inside this folder, you’ll find full-color and one-color versions of the
logo, plus a mascot-only version, in EPS, JPG and PNG formats. You can use
them on presentations and wherever else you’d like to add some team flair.

https://www.dropbox.com/sh/5u0grlova3h4dtp/AAAadorRO7Mit4ndW0A_UhZha?dl=0

At the PWG, we’ll have stickers for your team of the mascot, plus signage
on your room. I’m especially excited for the project teams to see all of
the logos together as one group, because they work beautifully together
stylistically while making each project’s mark distinctive. Feel free to
share this with your team, and thanks to you and to them for the hard work
they put into reaching an agreement on the mascot. Also feel free to direct
any questions my way!

   
|Heidi Joy Tretheway   
|Senior Marketing Manager, OpenStack Foundation
|503 816 9769 | Skype: heidi.tretheway 
|  
   





__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] import urllib3 problem

[Ian Cordasco]

-Original Message-
From: Carmine Annunziata 
Reply: OpenStack Development Mailing List (not for usage questions)

Date: February 14, 2017 at 10:46:09
To: openstack-dev@lists.openstack.org 
Subject:  [openstack-dev] import urllib3 problem

> Hi,
> I upgraded ubuntu 14.04 to 16.04 LTS and now during the ./stack.sh i got
> this problem.
> I upgraded with:
> sudo pip install urllib3 --upgrade
> but the problem is still there:
>
> 2017-02-14 15:54:40.894 | Traceback (most recent call last):
> 2017-02-14 15:54:40.894 | File "/opt/stack/requirements/.venv/bin/pip",
> line 7, in
> 2017-02-14 15:54:40.894 | from pip import main
> 2017-02-14 15:54:40.894 | File "/opt/stack/requirements/.
> venv/local/lib/python2.7/site-packages/pip/__init__.py", line 21, in
>
> 2017-02-14 15:54:40.895 | from
> pip._vendor.requests.packages.urllib3.exceptions
> import DependencyWarning
> 2017-02-14 15:54:40.895 | File "/opt/stack/requirements/.
> venv/local/lib/python2.7/site-packages/pip/_vendor/requests/__init__.py",
> line 62, in
> 2017-02-14 15:54:40.895 | from .packages.urllib3.exceptions import
> DependencyWarning
> 2017-02-14 15:54:40.895 | File "/opt/stack/requirements/.
> venv/local/lib/python2.7/site-packages/pip/_vendor/requests/packages/__init__.py",
> line 29, in
> 2017-02-14 15:54:40.895 | import urllib3
> 2017-02-14 15:54:40.895 | ImportError: No module named urllib3
> 2017-02-14 15:54:40.904 | +inc/python:pip_install:1
> exit_trap
> 2017-02-14 15:54:40.908 | +./stack.sh:exit_trap:487 local
> r=1
> 2017-02-14 15:54:40.924 | ++./stack.sh:exit_trap:488 jobs
> -p
> 2017-02-14 15:54:40.935 | +./stack.sh:exit_trap:488 jobs=
> 2017-02-14 15:54:40.948 | +./stack.sh:exit_trap:491 [[ -n
> '' ]]
> 2017-02-14 15:54:40.952 | +./stack.sh:exit_trap:497
> kill_spinner
> 2017-02-14 15:54:40.967 | +./stack.sh:kill_spinner:383 '['
> '!' -z '' ']'
> 2017-02-14 15:54:40.982 | +./stack.sh:exit_trap:499 [[ 1
> -ne 0 ]]
> 2017-02-14 15:54:40.998 | +./stack.sh:exit_trap:500 echo
> 'Error on exit'
> 2017-02-14 15:54:40.999 | Error on exit
> 2017-02-14 15:54:41.002 | +./stack.sh:exit_trap:501
> generate-subunit 1487087613 67 fail
> 2017-02-14 15:54:41.817 | +./stack.sh:exit_trap:502 [[ -z
> /opt/stack/logs ]]
> 2017-02-14 15:54:41.821 | +./stack.sh:exit_trap:505
> /home/stack/devstack/tools/worlddump.py -d /opt/stack/logs
> 2017-02-14 15:54:43.088 | +./stack.sh:exit_trap:511 exit 1
> stack@coritel-VirtualBox:~/devstack$ sudo gedit
> /opt/stack/requirements/.venv/local/lib/python2.7/site-
> packages/pip/_vendor/requests/packages/__init__.py

Hi Carmine,

It looks like your virtualenv needs to be recreated. The version of
pip inside of it seems to be thoroughly broken.

--
Ian Cordasco

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [MassivelyDistributed] IRC Meeting tomorrow 15:00 UTC

[lebre . adrien]

Dear all, 

A gentle reminder for our meeting tomorrow. 
As usual, the agenda is available at: 
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 (line 
185)
Please feel free to add items to the agenda.

Best, 
Ad_rien_

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Carlos Camacho Gonzalez]

Hello Heidi,

I think most of us already agreed on the fact that our current logo was
created by developers and we like it.
The idea should be to iterate over our current logo to make it fit the
foundation guidelines.

I don't think is hard to do it, I can give you some examples (***The owl
colors were randomly chosen).

https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_tripleo_logo_h.pdf
https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_tripleo_logo_h.png
https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_tripleo_logo_h.svg
https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_tripleo_logo_v.pdf
https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_tripleo_logo_v.png
https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_tripleo_logo_v.svg

Please just let me know if you need any further information/feedback/help.

Cheers,
Carlos.



On Tue, Feb 14, 2017 at 3:44 PM, Emilien Macchi  wrote:
>
> Heidi,
>
> TripleO team discussed about the logo this morning during our weekly
meeting.
> We understood that we had to change our existing logo because it
> doesn't meet OpenStack themes requirements, and that's fine.
>
> Though we would like you to re-iterate on a new logo that would be a
> variation on the current logo that moves closer to the foundation.
>
> Our existing logo is: http://tripleo.org/_static/tripleo_owl.svg
>
> Please let us know if you can prepare a new logo close to this one,
> and I think we would find a middle ground here.
>
> Thanks a lot,
>
> On Tue, Feb 14, 2017 at 7:30 AM, Carlos Camacho Gonzalez
>  wrote:
> > I'll vote also for option 1 if we can keep it.
> >
> > One thing, you can see how designers have iterated over ironic's logo
> >
http://lists.openstack.org/pipermail/openstack-dev/attachments/20170201/a016f685/attachment.png
> > to fit the OpenStack illustration style.
> >
> > Is it possible for designers to iterate over
> > http://tripleo.org/_static/tripleo_owl.svg to make it fit the
guidelines?
> >
> > Cheers,
> > Carlos.
> >
> > On Tue, Feb 14, 2017 at 12:34 PM, Lucas Alvares Gomes
> >  wrote:
> >>
> >> Hi,
> >>
> >> Just a FYI, we have had similar discussions about the proposed logo for
> >> Ironic, there's still many unanswered questions but, if you guys are
> >> interested this is the link to the ML thread:
> >>
http://lists.openstack.org/pipermail/openstack-dev/2017-February/111401.html
> >>
> >> Cheers,
> >> Lucas
> >>
> >> On Tue, Feb 14, 2017 at 2: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).
> >>>
> >>>
> >>> Personally, I would vote for keeping our existing logo (1.) unless
> >>> someone has time to create another one or if the team likes the
proposed
> >>> one.
> >>>
> >>> The reason why I want to keep our logo is because our current logo was
> >>> created by TripleO devs, we like it and we already have tee-shirts
and other
> >>> goodies with it. I don't see any good reason to change it.
> >>>
> >>> Discussion is open and we'll vote as a team.
> >>>
> >>> Thanks,
> >>>
> >>> Emilien.
> >>>
> >>> -- Forwarded message --
> >>> From: Heidi Joy Tretheway 
> >>> Date: Mon, Feb 13, 2017 at 8:27 PM
> >>> Subject: TripleO mascot - how can I help your team?
> >>> To: Emilien Macchi 
> >>>
> >>>
> >>> Hi Emilien,
> >>>
> >>> I’m following up on the much-debated TripleO logo. I’d like to help
your
> >>> team reach a solution that makes them happy but still fits within the
family
> >>> of logos we’re using at the PTG and going forward. Here’s what our
> >>> illustrators came up with, which hides an “O” shape in the owl (face
and
> >>> wing arcs).
> >>>
> >>>
https://www.dropbox.com/sh/qz45miiiam3caiy/AAAzPGYEZRMGH6Otid3bLfHFa?dl=0
> >>> At this point, I don’t have quorum from your team (I got a lot of
> >>> conflicting feedback, most of which was “don’t like” but not
actionable for
> >>> the illustrators to make a revision). At the PTG, we’ll have mascot
stickers
> >>> and signage for all teams except for Ironic and TripleO, since we’re
still
> >>> waiting on your teams to make a final decision.
> >>>
> >>> May I recommend that your team choose one person (or a small group of
no
> >>> more than three) to finalize this? I was able to work through all of
Swift’s
> >>> issues with just a quick 15-minute chat with John Dickinson and I’d
like to
> >>> believe we can solve this for TripleO as well.
> >>>
> >>> We know some of your team has expressed concern over retiring the
> >>> existing mascot. It’s not our intention to make anyone “get rid of” a
> >>> beloved icon. Your team can certainly print it on vintage items like
shirts
> >>> and stickers. But for official channel

Re: [openstack-dev] [Watcher] Nominating Prudhvi Rao Shedimbi to Watcher Core

[Jean-Émile DARTOIS]

?+1


Jean-Emile
DARTOIS

{P} Software Engineer
Cloud Computing

{T} +33 (0) 2 56 35 8260
{W} www.b-com.com

De : Susanne Balle 
Envoyé : mardi 14 février 2017 17:30
À : OpenStack Development Mailing List (not for usage questions)
Objet : Re: [openstack-dev] [Watcher] Nominating Prudhvi Rao Shedimbi to 
Watcher Core

+1

On Tue, Feb 14, 2017 at 9:31 AM, Prashanth Hari 
mailto:hvpr...@gmail.com>> wrote:
+1

On Tue, Feb 14, 2017 at 9:22 AM, Joe Cropper 
mailto:cropper@gmail.com>> wrote:
+1 !

> On Feb 14, 2017, at 4:05 AM, Vincent FRANÇOISE 
> mailto:vincent.franco...@b-com.com>> wrote:
>
> Team,
>
> I would like to promote Prudhvi Rao Shedimbi to the core team. He's done
> a great work in reviewing many patchsets[1] and I believe that he has a
> good vision of Watcher as a whole.
>
> I think he would make an excellent addition to the team.
>
> Please vote
>
> [1] http://stackalytics.com/report/contribution/watcher/90
>
> Vincent FRANCOISE
> B<>COM
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Jean-Émile DARTOIS]

?+1


Jean-Emile
DARTOIS

{P} Software Engineer
Cloud Computing

{T} +33 (0) 2 56 35 8260
{W} www.b-com.com

De : Susanne Balle 
Envoyé : mardi 14 février 2017 17:33
À : OpenStack Development Mailing List (not for usage questions)
Objet : Re: [openstack-dev] [Watcher] Nominating licanwei to Watcher Core

+1

On Tue, Feb 14, 2017 at 5:37 AM, Vincent FRANÇOISE 
mailto:vincent.franco...@b-com.com>> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

+1

On 14/02/2017 11:27, ? ? wrote:
> His activity will help Watcher Team to make this project better.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJYot3aAAoJEEb+XENQ/jVSvIEH/RsqFZZ7hZyA7ExieF7K4GmN
d1f1vnPbOR3MgqQTbezixIPIwzrDw9dtpU6q8BRPARP6ja2tOPNoYHc1CZmxgwz9
Mc5iVhvAaKuzL7KKpeROVkLkVUJ9bZnxNM/pkgiq0qXYoBaitgVdPVTIE6nBLdpV
yHRkUG24pkojogIJGIbB2cJeKganJ+PrCB59buAof1NqEhujt00akfjHCKbc7Wc/
oSmx2VD3aRn8OcfAhQ1pQgRYpa6MRFBRbDUPejVyiGzFWTDreWA3cLVq2xpGEcCW
ahcq2MNsZCiFegD4u9jYroULOALhdGBUctONbluaqbfZ7PhPPqQxSJGQq96hTCg=
=WsCi
-END PGP SIGNATURE-

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] import urllib3 problem

[Carmine Annunziata]

Hi,
I upgraded ubuntu 14.04 to 16.04 LTS and now during the ./stack.sh i got
this problem.
I upgraded with:
sudo pip install urllib3 --upgrade
but the problem is still there:

2017-02-14 15:54:40.894 | Traceback (most recent call last):
2017-02-14 15:54:40.894 |   File "/opt/stack/requirements/.venv/bin/pip",
line 7, in 
2017-02-14 15:54:40.894 | from pip import main
2017-02-14 15:54:40.894 |   File "/opt/stack/requirements/.
venv/local/lib/python2.7/site-packages/pip/__init__.py", line 21, in

2017-02-14 15:54:40.895 | from
pip._vendor.requests.packages.urllib3.exceptions
import DependencyWarning
2017-02-14 15:54:40.895 |   File "/opt/stack/requirements/.
venv/local/lib/python2.7/site-packages/pip/_vendor/requests/__init__.py",
line 62, in 
2017-02-14 15:54:40.895 | from .packages.urllib3.exceptions import
DependencyWarning
2017-02-14 15:54:40.895 |   File "/opt/stack/requirements/.
venv/local/lib/python2.7/site-packages/pip/_vendor/requests/packages/__init__.py",
line 29, in 
2017-02-14 15:54:40.895 | import urllib3
2017-02-14 15:54:40.895 | ImportError: No module named urllib3
2017-02-14 15:54:40.904 | +inc/python:pip_install:1
exit_trap
2017-02-14 15:54:40.908 | +./stack.sh:exit_trap:487  local
r=1
2017-02-14 15:54:40.924 | ++./stack.sh:exit_trap:488  jobs
-p
2017-02-14 15:54:40.935 | +./stack.sh:exit_trap:488  jobs=
2017-02-14 15:54:40.948 | +./stack.sh:exit_trap:491  [[ -n
'' ]]
2017-02-14 15:54:40.952 | +./stack.sh:exit_trap:497
kill_spinner
2017-02-14 15:54:40.967 | +./stack.sh:kill_spinner:383   '['
'!' -z '' ']'
2017-02-14 15:54:40.982 | +./stack.sh:exit_trap:499  [[ 1
-ne 0 ]]
2017-02-14 15:54:40.998 | +./stack.sh:exit_trap:500  echo
'Error on exit'
2017-02-14 15:54:40.999 | Error on exit
2017-02-14 15:54:41.002 | +./stack.sh:exit_trap:501
generate-subunit 1487087613 67 fail
2017-02-14 15:54:41.817 | +./stack.sh:exit_trap:502  [[ -z
/opt/stack/logs ]]
2017-02-14 15:54:41.821 | +./stack.sh:exit_trap:505
/home/stack/devstack/tools/worlddump.py -d /opt/stack/logs
2017-02-14 15:54:43.088 | +./stack.sh:exit_trap:511  exit 1
stack@coritel-VirtualBox:~/devstack$ sudo gedit
/opt/stack/requirements/.venv/local/lib/python2.7/site-
packages/pip/_vendor/requests/packages/__init__.py


thank you,

Carmine.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [All] IRC Mishaps

[Kevin L. Mitchell]

On Thu, 2017-02-09 at 21:14 -0600, Sean McGinnis wrote:
> Oh, there was the time I accidentally banned everyone from the Cinder
> channel. That was fun. :)

Reminds me of a time that a server operator on another IRC network
accidentally managed to ban everyone from that network…that happened to
be the #3 largest IRC network at the time.  Fixing *that* was fun :)
-- 
Kevin L. Mitchell 


signature.asc
Description: This is a digitally signed message part
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [release][stable][requirements] Team dinner @ PTG

[Thierry Carrez]

Hi stable/requirements/release folks!

We are trying to organize a dinner for one of the PTG nights for people
involved with the Stable / Release Management / Requirements teams
(including team liaisons !)

If interested please enter your availability on:
https://framadate.org/XIbbQnbxSKRPW1yK

I have a small preference for Tuesday (end of our room) or Wednesday
(release day party !), but can make other days work as well. I removed
Monday from the options since that's when the Infra team will have
dinner and we have lots of overlap.

-- 
Thierry Carrez (ttx)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Susanne Balle]

+1

On Tue, Feb 14, 2017 at 5:37 AM, Vincent FRANÇOISE <
vincent.franco...@b-com.com> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> +1
>
> On 14/02/2017 11:27, ? ? wrote:
> > His activity will help Watcher Team to make this project better.
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.22 (GNU/Linux)
>
> iQEcBAEBAgAGBQJYot3aAAoJEEb+XENQ/jVSvIEH/RsqFZZ7hZyA7ExieF7K4GmN
> d1f1vnPbOR3MgqQTbezixIPIwzrDw9dtpU6q8BRPARP6ja2tOPNoYHc1CZmxgwz9
> Mc5iVhvAaKuzL7KKpeROVkLkVUJ9bZnxNM/pkgiq0qXYoBaitgVdPVTIE6nBLdpV
> yHRkUG24pkojogIJGIbB2cJeKganJ+PrCB59buAof1NqEhujt00akfjHCKbc7Wc/
> oSmx2VD3aRn8OcfAhQ1pQgRYpa6MRFBRbDUPejVyiGzFWTDreWA3cLVq2xpGEcCW
> ahcq2MNsZCiFegD4u9jYroULOALhdGBUctONbluaqbfZ7PhPPqQxSJGQq96hTCg=
> =WsCi
> -END PGP SIGNATURE-
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Watcher] Nominating Prudhvi Rao Shedimbi to Watcher Core

[Susanne Balle]

+1

On Tue, Feb 14, 2017 at 9:31 AM, Prashanth Hari  wrote:

> +1
>
> On Tue, Feb 14, 2017 at 9:22 AM, Joe Cropper 
> wrote:
>
>> +1 !
>>
>> > On Feb 14, 2017, at 4:05 AM, Vincent FRANÇOISE <
>> vincent.franco...@b-com.com> wrote:
>> >
>> > Team,
>> >
>> > I would like to promote Prudhvi Rao Shedimbi to the core team. He's done
>> > a great work in reviewing many patchsets[1] and I believe that he has a
>> > good vision of Watcher as a whole.
>> >
>> > I think he would make an excellent addition to the team.
>> >
>> > Please vote
>> >
>> > [1] http://stackalytics.com/report/contribution/watcher/90
>> >
>> > Vincent FRANCOISE
>> > B<>COM
>> >
>> > 
>> __
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe: openstack-dev-requ...@lists.op
>> enstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla] Mascot

[Steven Dake (stdake)]

The mascot is absolutely fantastic!  Nice work to all involved!

Regards
-steve

-Original Message-
From: Michał Jastrzębski 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Monday, February 13, 2017 at 7:53 PM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [openstack-dev] [kolla] Mascot

And here we are, our mascot:) Feel free to use it in any Kolla related
presentation or tattoo studio.


https://www.dropbox.com/sh/94pukquiw425ji2/AAAl2wVmm72KHPLCAzR6Uboha?dl=0

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Cinder] Project mascot available

[Walter Boring]

How does Horse translate to Cinder block?
I don't get it.  Our original Cinder block made a lot of sense, considering
the name of the project.


This is...just an odd horse for no particular reason.

On Mon, Feb 13, 2017 at 6:43 PM, Sean McGinnis 
wrote:

> For your viewing and slide designing pleasure...
>
> We have the official mascot completed from the illustrators. Multiple
> formats
> are available from here:
>
> https://www.dropbox.com/sh/8s3859c6qulu1m3/AABu_rIyuBM_bZmfGkagUXhua?dl=0
>
> Stay golden, pony boy.
>
> Sean
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] FYI: cells v1 job is blocked

[Matt Riedemann]

On 2/14/2017 9:39 AM, Dan Smith wrote:

We have a fix here:


Actual link to fix is left as an exercise for the reader?

https://review.openstack.org/#/c/433707

--Dan

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



Something wonky happened while I was switching network connections.

--

Thanks,

Matt Riedemann

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] FYI: cells v1 job is blocked

[Dan Smith]

> We have a fix here:

Actual link to fix is left as an exercise for the reader?

https://review.openstack.org/#/c/433707

--Dan

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Moving coverage jobs to check queue

[Jeremy Stanley]

On 2017-02-14 11:50:46 +1100 (+1100), Ian Wienand wrote:
[...]
> Some projects run in both check and post which seems unnecessary.
[...]

The argument in favor of doing both is that one helps you get a
rough idea of the coverage increase/decrease a proposed change may
bring, while the other allows you to accurately track coverage
trending over time for a given branch. Also if the check pipeline
job for it is voting, it helps you avoid merging a change that might
break coverage checking (note this is separate from how some
projects also modify it to fail on any coverage decrease, which is a
bit more problematic since there can be valid reasons to decrease
coverage on occasion).

> The coverage job results in post are quite hard to find. You need to
> firstly know the job even runs, then find the correct commit sha
> (which is probably the merge commit, not the one in gerrit) and then
> know how to manually navigate the logs.openstack.org file-hierarchy.
> It's probably no surprise that according to apache logs, nobody has
> accessed a post coverage-job output at all within about the last
> month. Also, as per the prior email, if the job is actually failing
> you get no notification at all.
[...]

Tracking coverage jobs in the health dashboard may alleviate that
(and could even bring trending graphs depending on how it's
implemented). It would, however, require someone to write the
necessary glue.
-- 
Jeremy Stanley

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova] FYI: cells v1 job is blocked

[Matt Riedemann]

The fix is here:

https://review.openstack.org/#/c/433707/

That's approved for master, but if you're seeing failures in that job 
since yesterday that's why.


I'm going to have to backport that all the way back to stable/mitaka too.

--

Thanks,

Matt Riedemann

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova] FYI: cells v1 job is blocked

[Matt Riedemann]

We have a fix here:


--

Thanks,

Matt Riedemann

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Alternative approaches for L3 HA

[Morales, Victor]

Hey Lubosz,

First of all, good job responding to the concerns of users and keeping a 
healthy OpenStack ecosystem.  I’ve one comment about this email,  maybe it was 
a cultural thing but I found it a little aggressive, specially the use of some 
pronouns and names.  I know you and I’m completely sure that your intention was 
to help others in the best way, hopefully this is not a blind spot.

Regards,
Victor Morales

From: "Kosnik, Lubosz" mailto:lubosz.kos...@intel.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Date: Monday, February 13, 2017 at 10:23 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Neutron] Alternative approaches for L3 HA

So from my perspective I can tell that problem is completely in architecture 
and even without something outside of Neutron we cannot solve that.
Two releases ago I started to work on hardening that feature but all my ideas 
was killed by Armando and Assaf. The decided that adding outside dependency 
will open the doors for a new bugs from dependencies into Neutron [1].

You need to know that there are two outstanding bugs in this feature. There is 
a internal and outside connectivity split brain. [2] this patch made by me is 
“fixing” part of the problem. It allows you specify additional tests to verify 
connectivity from router to GW.
Also there is a problem with connectivity between network nodes. It’s more 
problematic and like you said it’s unsolvable in my opinion without using 
external mechanism.

If there will be any need to help with anything I would love to help with 
sharing my knowledge about this feature and what exactly is not working. If 
anyone needs any help with anything about this please ping me on email or IRC.

[1] https://bugs.launchpad.net/neutron/+bug/1375625/comments/31
[2] https://review.openstack.org/#/c/273546/

Lubosz

On Feb 13, 2017, at 4:10 AM, Anna Taraday 
mailto:akamyshnik...@mirantis.com>> wrote:

To avoid dependency of data plane on control plane it is possible to deploy a 
separate key-value storage cluster on data plane side, using the same network 
nodes.
I'm proposing to make some changes to enable experimentation in this field, we 
are yet to come up with any other concrete solution.

On Mon, Feb 13, 2017 at 2:01 PM 
mailto:cristi.ca...@orange.com>> wrote:

Hi,





We also operate using Juno with the VRRP HA implementation and at had to patch 
through several bugs before getting to the Mitaka release.

An pluggable, drop-in alternative would be highly appreciated. However our 
experience has been that the decoupling of VRRP from the control plane is 
actually a benefit as when the control plane is down the traffic is not 
affected.

In a solution where the L3 HA implementation becomes tied to the availability 
of the control plane (etcd cluster or any other KV store) then an operator 
would have to account for extra failure scenarios for the KV store which would 
affect multiple routers than the outage of a single L3 node which is the case 
we usually have to account now.





Just my $.02



Cristian



From: Anna Taraday 
[mailto:akamyshnik...@mirantis.com]
Sent: Monday, February 13, 2017 11:45 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] Alternative approaches for L3 HA



In etcd for each HA router we can store key which will identify which agent is 
active. L3 agents will "watch" this key.
All these tools have leader election mechanism which can be used to get agent 
which is active for current HA router.



On Mon, Feb 13, 2017 at 7:02 AM zhi 
mailto:changzhi1...@gmail.com>> wrote:

Hi, we are using L3 HA in our production environment now. Router instances 
communicate to each other by VRRP protocol. In my opinion, although VRRP is a 
control plane thing, but the real VRRP traffic is using data plane nic so that 
router namespaces can not talk to each other sometimes when the  data plan is 
busy. If we were used etcd (or other), does every router instance register one 
"id" in etcd ?





Thanks

Zhi Chang

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

--

Regards,
Ann Taraday

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le de

[openstack-dev] [puppet] mascot

[Alex Schultz]

Hey folks,

The final mascot is available for viewing here:
https://www.dropbox.com/sh/oax7i1xvca3edxc/AAAtfQSyx0rJijKBoqoZmp-va?dl=0

Thanks,
-Alex

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [all][logos] License for new project mascots

[Hayes, Graham]

Hi,

I did a bit of digging through email, and I *thought* someone had asked
about the license that these logos were being released under. Turns out
it was me, and I don't seem to have gotten a response about it.

So - what license are the new logos / mascots under?

Is the same as the wiki? [1] If not, it could present problems for
people to upload copies of the logo to the wiki, as it assumes all
content is CC-BY.

Thanks

- Graham

1 - https://creativecommons.org/licenses/by/3.0/

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] neutron-classifier (CCF) at the PTG

[Kevin Benton]

Hi,

Please add it to the etherpad here:
https://etherpad.openstack.org/p/neutron-ptg-pike

On Tue, Feb 14, 2017 at 6:39 AM, Duarte Cardoso, Igor <
igor.duarte.card...@intel.com> wrote:

> Hi neutron,
>
>
>
> Me and David would like to discuss the Common Classification Framework
> (CCF) (current approach based on openstack/neutron-classifier) at the PTG
> but we aren’t sure if the main session is the appropriate forum for that or
> if we should only have a meeting with the interested people and a few
> Neutron cores or PTL (to discuss if and how this work could be brought
> closer to Neutron itself).
>
>
>
> I appreciate your feedback, thanks!
>
>
>
> Best regards,
>
> Igor.
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Oslo] Oslo logo files (was 'log files')

[Ken Giusti]

These are great!

I've tweaked the subject lest folks think this only applies to logging.

"Watch me pull an RPC call outta my hat... nothing up my sleeve... Presto!"

(google 'bullwinkle' - pop culture reference... clearly showing my age
(and mentality) :)

-K

On Mon, Feb 13, 2017 at 11:35 PM, ChangBo Guo  wrote:
> We got  cool logos in different format, just use them :-)
> I’m excited to finally be able to share final project logo files with you.
> Inside this folder, you’ll find full-color and one-color versions of the
> logo, plus a mascot-only version, in EPS, JPG and PNG formats. You can use
> them on presentations and wherever else you’d like to add some team flair.
>
> https://www.dropbox.com/sh/kj0e3sdu47pqr3e/AABllB31vJZDlw4OkZRK_AZia?dl=0
>
> --
> ChangBo Guo(gcb)
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Ken Giusti  (kgiu...@gmail.com)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [neutron] - no meetings week of 2/19-2/25

[Kevin Benton]

Hi all,

There won't be a drivers meeting or a neutron team meeting next week
(2/19-2/25) due to the PTG.

Cheers,
Kevin Benton
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [QA] Pike PTG Schedule

[Ken'ichi Ohmichi]

Hi Andrea,

Thanks for organizing QA sessions for PTG.

2017-02-13 16:16 GMT-08:00 Andrea Frittoli :
> Hello team,
>
> I did some work on the etherpad [0] to organise the QA PTG schedule based on
> the proposed sessions.
> I separated discussion sessions from hands-on type of actives. I thing the
> former will require a fixed schedule so folks may know when to pop-in to
> attend; the latter may happen more ad-hoc based on who's there an not busy
> in a session. We can have a final discussion on this in the QA meeting on
> Thursday [1].

It is a nice idea to separate discussion sessions from hands-on (code
sprint) sessions.
Now we have 9 discussion sessions which don't require arranging the
time schedule with the other teams.
So I feel it is nice to schedule them in the first day and schedule
hands-on sessions(working items based on discussion sessions and 3
original hands-on session) in the second day so that we get feedback
and discuss them again during the second day.
That is an idea, I am happy to see the other schedule idea :-)

> I haven't fixed the exact schedule yet, I will do it soon; meanwhile please
> let me know if you think your session will need more or less then 30' which
> is the standard time I would allocate.
> Discussions that overrun the planned time can go in a parking lot, which we
> can pick up later at the PTG or during meetings.
> Any session preparation work / existing material, previous discussions,
> links and so can go in the respective etherpad.
>
> I think we have a good set of topics to discuss and code to write, enough to
> keep us busy for more than the time we have.
> Nonetheless, if you have more topic to propose please continue adding them
> to the etherpad.

Yes, it is nice to make us busy in PTG.

Thanks
Ken Ohmichi

---

> [0] https://etherpad.openstack.org/p/qa-ptg-pike
> [1]
> https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_February_16th_2017_.281700_UTC.29
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [cinder] [nova] confusion on where nova_catalog_admin_info is used in cinder

[Matt Riedemann]

On 2/14/2017 8:48 AM, Matt Riedemann wrote:


OK so the NFS job would tickle it, but that might not be in the
experimental queue for devstack (but it is in nova's experimental queue
so we could hack this up to test it).

I thought we were testing volume retype/migration now though? That calls
swap volume in nova which then calls back to cinder to tell cinder when
the swap is done. Or did the volume retype/migration test never land?



https://review.openstack.org/#/c/433685/ should test this out since nova 
runs gate-tempest-dsvm-full-devstack-plugin-nfs-nv and 
gate-tempest-dsvm-lvm-multibackend-ubuntu-xenial-nv in it's experimental 
queue. That will test guest-assisted snapshots via the NFS job and 
volume retype (volume swap call from cinder to nova) in the lvm 
multibackend job.


--

Thanks,

Matt Riedemann

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [cinder] [nova] confusion on where nova_catalog_admin_info is used in cinder

[Matt Riedemann]

On 2/14/2017 7:48 AM, Duncan Thomas wrote:

This is only used by the file based drivers, who need to call nova for
assistance with attached snapshots. Most drivers won't use it, including
the default, LVM.

I can't comment on the test coverage, sorry.

On 14 February 2017 at 13:01, Sean Dague mailto:s...@dague.net>> wrote:

After some of the confusion around endpoints in devstack, we decided to
simplify the endpoints registered in devstack to only the ones needed
for development. Basically only register "public" interfaces unless
there is something special about the service.

https://review.openstack.org/#/c/433272/
 is the change.

Matt Riedemann pointed out that this would break Cinder because there is
a hardcoded concept of nova_catalog_admin_info -

https://github.com/openstack/cinder/blob/cfc617b0cea99ed6994f08e5337fd5b65ea9fd1c/cinder/compute/nova.py#L39-L41



Except... it didn't (see results on
https://review.openstack.org/#/c/433272/
).

What is more confusing, is the oslo.config dump at the beginning of
cinder service starts there don't have any reference to any of these
nova_ config variables.

How is this code loaded and used? Is there no testing of cinder -> nova
happening in the gate? Is this missing testing, or are there reasons
these configurations would never load that code?

-Sean

--
Sean Dague
http://dague.net

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev





--
--
Duncan Thomas


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



OK so the NFS job would tickle it, but that might not be in the 
experimental queue for devstack (but it is in nova's experimental queue 
so we could hack this up to test it).


I thought we were testing volume retype/migration now though? That calls 
swap volume in nova which then calls back to cinder to tell cinder when 
the swap is done. Or did the volume retype/migration test never land?


--

Thanks,

Matt Riedemann

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Emilien Macchi]

Heidi,

TripleO team discussed about the logo this morning during our weekly meeting.
We understood that we had to change our existing logo because it
doesn't meet OpenStack themes requirements, and that's fine.

Though we would like you to re-iterate on a new logo that would be a
variation on the current logo that moves closer to the foundation.

Our existing logo is: http://tripleo.org/_static/tripleo_owl.svg

Please let us know if you can prepare a new logo close to this one,
and I think we would find a middle ground here.

Thanks a lot,

On Tue, Feb 14, 2017 at 7:30 AM, Carlos Camacho Gonzalez
 wrote:
> I'll vote also for option 1 if we can keep it.
>
> One thing, you can see how designers have iterated over ironic's logo
> http://lists.openstack.org/pipermail/openstack-dev/attachments/20170201/a016f685/attachment.png
> to fit the OpenStack illustration style.
>
> Is it possible for designers to iterate over
> http://tripleo.org/_static/tripleo_owl.svg to make it fit the guidelines?
>
> Cheers,
> Carlos.
>
> On Tue, Feb 14, 2017 at 12:34 PM, Lucas Alvares Gomes
>  wrote:
>>
>> Hi,
>>
>> Just a FYI, we have had similar discussions about the proposed logo for
>> Ironic, there's still many unanswered questions but, if you guys are
>> interested this is the link to the ML thread:
>> http://lists.openstack.org/pipermail/openstack-dev/2017-February/111401.html
>>
>> Cheers,
>> Lucas
>>
>> On Tue, Feb 14, 2017 at 2: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).
>>>
>>>
>>> Personally, I would vote for keeping our existing logo (1.) unless
>>> someone has time to create another one or if the team likes the proposed
>>> one.
>>>
>>> The reason why I want to keep our logo is because our current logo was
>>> created by TripleO devs, we like it and we already have tee-shirts and other
>>> goodies with it. I don't see any good reason to change it.
>>>
>>> Discussion is open and we'll vote as a team.
>>>
>>> Thanks,
>>>
>>> Emilien.
>>>
>>> -- Forwarded message --
>>> From: Heidi Joy Tretheway 
>>> Date: Mon, Feb 13, 2017 at 8:27 PM
>>> Subject: TripleO mascot - how can I help your team?
>>> To: Emilien Macchi 
>>>
>>>
>>> Hi Emilien,
>>>
>>> I’m following up on the much-debated TripleO logo. I’d like to help your
>>> team reach a solution that makes them happy but still fits within the family
>>> of logos we’re using at the PTG and going forward. Here’s what our
>>> illustrators came up with, which hides an “O” shape in the owl (face and
>>> wing arcs).
>>>
>>> https://www.dropbox.com/sh/qz45miiiam3caiy/AAAzPGYEZRMGH6Otid3bLfHFa?dl=0
>>> At this point, I don’t have quorum from your team (I got a lot of
>>> conflicting feedback, most of which was “don’t like” but not actionable for
>>> the illustrators to make a revision). At the PTG, we’ll have mascot stickers
>>> and signage for all teams except for Ironic and TripleO, since we’re still
>>> waiting on your teams to make a final decision.
>>>
>>> May I recommend that your team choose one person (or a small group of no
>>> more than three) to finalize this? I was able to work through all of Swift’s
>>> issues with just a quick 15-minute chat with John Dickinson and I’d like to
>>> believe we can solve this for TripleO as well.
>>>
>>> We know some of your team has expressed concern over retiring the
>>> existing mascot. It’s not our intention to make anyone “get rid of” a
>>> beloved icon. Your team can certainly print it on vintage items like shirts
>>> and stickers. But for official channels like the website, we need a logo to
>>> represent TripleO that’s cohesive with the rest of the set.
>>>
>>> Perhaps when you’re face to face with your team at the PTG, you can
>>> discuss and hopefully render a final decision to either accept this as a
>>> logo, or determine a few people willing to make any final changes with me?
>>>
>>> Thanks in advance for your help!
>>>
>>>
>>> Heidi Joy Tretheway
>>> Senior Marketing Manager, OpenStack Foundation
>>> 503 816 9769 | Skype: heidi.tretheway
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Emilien Macchi
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> 

[openstack-dev] [neutron] neutron-classifier (CCF) at the PTG

[Duarte Cardoso, Igor]

Hi neutron,

Me and David would like to discuss the Common Classification Framework (CCF) 
(current approach based on openstack/neutron-classifier) at the PTG but we 
aren't sure if the main session is the appropriate forum for that or if we 
should only have a meeting with the interested people and a few Neutron cores 
or PTL (to discuss if and how this work could be brought closer to Neutron 
itself).

I appreciate your feedback, thanks!

Best regards,
Igor.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [neutron] [classifier] Common Classification Framework meeting

[Duarte Cardoso, Igor]

Hi all,

Common Classification Framework developers and interested parties are invited 
for today's meeting. The agenda is below, feel free to add more topics.

https://wiki.openstack.org/wiki/Neutron/CommonFlowClassifier#Discussion_Topic_14_February_2017

1700 UTC @ #openstack-meeting.

Me and David will be at the PTG to discuss this work as well.

Best regards,
Igor.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Watcher] Nominating Prudhvi Rao Shedimbi to Watcher Core

[Prashanth Hari]

+1

On Tue, Feb 14, 2017 at 9:22 AM, Joe Cropper  wrote:

> +1 !
>
> > On Feb 14, 2017, at 4:05 AM, Vincent FRANÇOISE <
> vincent.franco...@b-com.com> wrote:
> >
> > Team,
> >
> > I would like to promote Prudhvi Rao Shedimbi to the core team. He's done
> > a great work in reviewing many patchsets[1] and I believe that he has a
> > good vision of Watcher as a whole.
> >
> > I think he would make an excellent addition to the team.
> >
> > Please vote
> >
> > [1] http://stackalytics.com/report/contribution/watcher/90
> >
> > Vincent FRANCOISE
> > B<>COM
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Watcher] Nominating Prudhvi Rao Shedimbi to Watcher Core

[Joe Cropper]

+1 !

> On Feb 14, 2017, at 4:05 AM, Vincent FRANÇOISE  
> wrote:
> 
> Team,
> 
> I would like to promote Prudhvi Rao Shedimbi to the core team. He's done
> a great work in reviewing many patchsets[1] and I believe that he has a
> good vision of Watcher as a whole.
> 
> I think he would make an excellent addition to the team.
> 
> Please vote
> 
> [1] http://stackalytics.com/report/contribution/watcher/90
> 
> Vincent FRANCOISE
> B<>COM
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] glance mascot/logo available

[Brian Rosmaita]

Hello Glancers,

Heidi Joy Tretheway at the Foundation has released the Glance mascot
logo files for full use as you see fit:

"Inside this folder, you’ll find full-color and one-color versions of
the logo, plus a mascot-only version, in EPS, JPG and PNG formats. You
can use them on presentations and wherever else you’d like to add some
team flair."

https://www.dropbox.com/sh/xct2hsah2h8l6yi/AAATDIfxQHXfgPqop1cOSYdsa?dl=0

There will also be stickers and signage available at the PTG.

cheers,
brian

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [heat][tripleo][mistral][all]PTG: Cross-Project: OpenStack Orchestration Integration

[John Fulton]

Thanks Rico and Renat. This applies to two specs [1][2] I'm involved in so I'll 
be sure to be there. --John

[1] https://review.openstack.org/#/c/387631/
[2] https://review.openstack.org/#/c/423304/


- Original Message -
From: "Renat Akhmerov" 
To: "OpenStack Development Mailing List (not for usage questions)" 

Sent: Tuesday, February 14, 2017 12:59:09 AM
Subject: [openstack-dev] [heat][tripleo][mistral][all]PTG: Cross-Project: 
OpenStack Orchestration Integration

Ok, thanks Rico. Keep us updated on the schedule changes. I’m currently 
finalizing the schedule for Mistral, for now I’ll leave Thursday 11.00-12.00 
blank. 

Renat Akhmerov 
@Nokia 




On 14 Feb 2017, at 10:49, Rico Lin < rico.lin.gua...@gmail.com > wrote: 

Let's move the schedule toThursday morning 11:00 am to 12:00 pm in the same 
room. Hope that schedule work for all:) 

Also, I will ask if Mon - Tue is available or not, but there might be more 
cross-project sessions we have to not to conflict with them. 

2017-02-14 10:02 GMT+08:00 Renat Akhmerov < renat.akhme...@gmail.com > : 






On 13 Feb 2017, at 19:30, Emilien Macchi < emil...@redhat.com > wrote: 



On Mon, Feb 13, 2017 at 4:48 AM, Rico Lin < rico.lin.gua...@gmail.com > wrote: 



Dear all 

PTG is approaching, we have few ideas around TripleO team ([1] and [2]) about 
use case like using Mistral through Heat. It seems some great OpenStacker 
already start thing about how the Orchestration services (Heat, Mistral, and 
some other projects) could use together for a better developer or operator 
experiences. First, of curse, 
we will arrange a fishbowl design session on Wednesday morning. 
Let's settle with 10:00 am to 10:50 am at Macon (on level2) for now. 
Could teams kindly help to make sure they can attend this cross project session 
or need it reschedule? 

Can we reschedule it? It seems like the only slot where we have sessions 
organized is on Wednesday morning, for our container work: 
https://etherpad.openstack.org/p/tripleo-ptg-pike 

Wednesday 9:00 Cross-Teams talk about containers and networking 
Wednesday 10:00: TripleO Containers status update and path forward 

So I suggest Wednesday afternoon or Thursday or Friday morning. At your 
convenience. 

Thursday morning would work for me. 

Renat Akhmerov 
@Nokia 


__ 
OpenStack Development Mailing List (not for usage questions) 
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 




-- 
May The Force of Open Stack Be With You, 
Rico Lin 
irc: ricolin 


__ 
OpenStack Development Mailing List (not for usage questions) 
Unsubscribe: openstack-dev-requ...@lists.openstack.org ?subject:unsubscribe 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [cinder] [nova] confusion on where nova_catalog_admin_info is used in cinder

[Duncan Thomas]

This is only used by the file based drivers, who need to call nova for
assistance with attached snapshots. Most drivers won't use it, including
the default, LVM.

I can't comment on the test coverage, sorry.

On 14 February 2017 at 13:01, Sean Dague  wrote:

> After some of the confusion around endpoints in devstack, we decided to
> simplify the endpoints registered in devstack to only the ones needed
> for development. Basically only register "public" interfaces unless
> there is something special about the service.
>
> https://review.openstack.org/#/c/433272/ is the change.
>
> Matt Riedemann pointed out that this would break Cinder because there is
> a hardcoded concept of nova_catalog_admin_info -
> https://github.com/openstack/cinder/blob/cfc617b0cea99ed6994f08e5337fd5
> b65ea9fd1c/cinder/compute/nova.py#L39-L41
>
> Except... it didn't (see results on
> https://review.openstack.org/#/c/433272/).
>
> What is more confusing, is the oslo.config dump at the beginning of
> cinder service starts there don't have any reference to any of these
> nova_ config variables.
>
> How is this code loaded and used? Is there no testing of cinder -> nova
> happening in the gate? Is this missing testing, or are there reasons
> these configurations would never load that code?
>
> -Sean
>
> --
> Sean Dague
> http://dague.net
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
-- 
Duncan Thomas
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [heat][tripleo][mistral][all]PTG: Cross-Project: OpenStack Orchestration Integration

[Emilien Macchi]

On Mon, Feb 13, 2017 at 10:49 PM, Rico Lin 
wrote:

> Let's move the schedule toThursday morning 11:00 am to 12:00 pm in the
> same room. Hope that schedule work for all:)
>
> Also, I will ask if Mon - Tue is available or not, but there might be more
> cross-project sessions we have to not to conflict with them.
>

Excellent! Thanks.


> 2017-02-14 10:02 GMT+08:00 Renat Akhmerov :
>
>> On 13 Feb 2017, at 19:30, Emilien Macchi  wrote:
>>
>>
>>
>> On Mon, Feb 13, 2017 at 4:48 AM, Rico Lin 
>> wrote:
>>
>>> Dear all
>>>
>>> PTG is approaching, we have few ideas around TripleO team ([1] and [2])
>>> about use case like using Mistral through Heat. It seems some great
>>> OpenStacker already start thing about how the Orchestration services (Heat,
>>> Mistral, and some other projects) could use together for a better developer
>>> or operator experiences. First, of curse,
>>> we will arrange a fishbowl design session on Wednesday morning.
>>> Let's settle with 10:00 am to 10:50 am at Macon (on level2) for now.
>>> Could teams kindly help to make sure they can attend this cross project
>>> session or need it reschedule?
>>>
>>
>> Can we reschedule it? It seems like the only slot where we have sessions
>> organized is on Wednesday morning, for our container work:
>> https://etherpad.openstack.org/p/tripleo-ptg-pike
>>
>> Wednesday 9:00 Cross-Teams talk about containers and networking
>> Wednesday 10:00: TripleO Containers status update and path forward
>>
>> So I suggest Wednesday afternoon or Thursday or Friday morning. At your
>> convenience.
>>
>>
>> Thursday morning would work for me.
>>
>> Renat Akhmerov
>> @Nokia
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> May The Force of OpenStack Be With You,
>
> *Rico Lin*irc: ricolin
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] Retiring python-wsmanclient

[Dmitry Tantsur]

Hi everyone!

Following the discussion below, we would like to officially retire 
python-wsmanclient as soon as possible. We haven't maintained it for a while, it 
hasn't had any commits and releases since Aug 2016.


On 11/07/2016 02:51 PM, Dmitry Tantsur wrote:

Hi folks!

In view of the Ironic governance discussion [1] I'd like to talk about
wsmanclient [2] future.

This project was created to split away wsman code from python-dracclient to be
reused in other drivers (I can only think of AMT right now). This was never
finished: dracclient still uses its internal wsman implementation.

To make it worse, the guy behind this effort (ifarkas) has left our team,
python-dracclient is likely to leave Ironic governance per [1], and the AMT
driver is going to leave the Ironic tree.

At least the majority of the folks currently behind dracclient (Miles, Lucas and
myself) do not have resources to continue this wsmanclient effort. Unless
somebody is ready to take over both wsmanclient itself and the effort to port
dracclient, I suggest we abandon wsmanclient.

Any thoughts?

[1] https://review.openstack.org/#/c/392685/
[2] https://github.com/openstack/python-wsmanclient

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cinder] [nova] confusion on where nova_catalog_admin_info is used in cinder

[Sean Dague]

After some of the confusion around endpoints in devstack, we decided to
simplify the endpoints registered in devstack to only the ones needed
for development. Basically only register "public" interfaces unless
there is something special about the service.

https://review.openstack.org/#/c/433272/ is the change.

Matt Riedemann pointed out that this would break Cinder because there is
a hardcoded concept of nova_catalog_admin_info -
https://github.com/openstack/cinder/blob/cfc617b0cea99ed6994f08e5337fd5b65ea9fd1c/cinder/compute/nova.py#L39-L41

Except... it didn't (see results on
https://review.openstack.org/#/c/433272/).

What is more confusing, is the oslo.config dump at the beginning of
cinder service starts there don't have any reference to any of these
nova_ config variables.

How is this code loaded and used? Is there no testing of cinder -> nova
happening in the gate? Is this missing testing, or are there reasons
these configurations would never load that code?

-Sean

-- 
Sean Dague
http://dague.net

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Carlos Camacho Gonzalez]

I'll vote also for option 1 if we can keep it.

One thing, you can see how designers have iterated over ironic's logo
http://lists.openstack.org/pipermail/openstack-dev/
attachments/20170201/a016f685/attachment.png to fit the OpenStack
illustration style.

Is it possible for designers to iterate over http://tripleo.org/_static/
tripleo_owl.svg to make it fit the guidelines?

Cheers,
Carlos.

On Tue, Feb 14, 2017 at 12:34 PM, Lucas Alvares Gomes 
wrote:
>
> Hi,
>
> Just a FYI, we have had similar discussions about the proposed logo for
Ironic, there's still many unanswered questions but, if you guys are
interested this is the link to the ML thread: http://lists.openstack.org/
pipermail/openstack-dev/2017-February/111401.html
>
> Cheers,
> Lucas
>
> On Tue, Feb 14, 2017 at 2: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).
>>
>>
>> Personally, I would vote for keeping our existing logo (1.) unless
someone has time to create another one or if the team likes the proposed
one.
>>
>> The reason why I want to keep our logo is because our current logo was
created by TripleO devs, we like it and we already have tee-shirts and
other goodies with it. I don't see any good reason to change it.
>>
>> Discussion is open and we'll vote as a team.
>>
>> Thanks,
>>
>> Emilien.
>>
>> -- Forwarded message --
>> From: Heidi Joy Tretheway 
>> Date: Mon, Feb 13, 2017 at 8:27 PM
>> Subject: TripleO mascot - how can I help your team?
>> To: Emilien Macchi 
>>
>>
>> Hi Emilien,
>>
>> I’m following up on the much-debated TripleO logo. I’d like to help your
team reach a solution that makes them happy but still fits within the
family of logos we’re using at the PTG and going forward. Here’s what our
illustrators came up with, which hides an “O” shape in the owl (face and
wing arcs).
>>
>> https://www.dropbox.com/sh/qz45miiiam3caiy/AAAzPGYEZRMGH6Otid3bLfHFa?dl=0
>> At this point, I don’t have quorum from your team (I got a lot of
conflicting feedback, most of which was “don’t like” but not actionable for
the illustrators to make a revision). At the PTG, we’ll have mascot
stickers and signage for all teams except for Ironic and TripleO, since
we’re still waiting on your teams to make a final decision.
>>
>> May I recommend that your team choose one person (or a small group of no
more than three) to finalize this? I was able to work through all of
Swift’s issues with just a quick 15-minute chat with John Dickinson and I’d
like to believe we can solve this for TripleO as well.
>>
>> We know some of your team has expressed concern over retiring the
existing mascot. It’s not our intention to make anyone “get rid of” a
beloved icon. Your team can certainly print it on vintage items like shirts
and stickers. But for official channels like the website, we need a logo to
represent TripleO that’s cohesive with the rest of the set.
>>
>> Perhaps when you’re face to face with your team at the PTG, you can
discuss and hopefully render a final decision to either accept this as a
logo, or determine a few people willing to make any final changes with me?
>>
>> Thanks in advance for your help!
>>
>>
>> Heidi Joy Tretheway
>> Senior Marketing Manager, OpenStack Foundation
>> 503 816 9769 <(503)%20816-9769> | Skype: heidi.tretheway
>>
>>
>>
>>
>>
>>
>>
>> --
>> Emilien Macchi
>>
>> 
__
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Brent Eagles]

Hi,

FWIW, I prefer the existing logo. There are several valid practical reasons
why it would be good to keep it, but I also just like it better.

On Mon, Feb 13, 2017 at 11:08 PM, 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).
>
>
> Personally, I would vote for keeping our existing logo (1.) unless someone
> has time to create another one or if the team likes the proposed one.
>
> The reason why I want to keep our logo is because our current logo was
> created by TripleO devs, we like it and we already have tee-shirts and
> other goodies with it. I don't see any good reason to change it.
>
> Discussion is open and we'll vote as a team.
>
> Thanks,
>
> Emilien.
>
> -- Forwarded message --
> From: Heidi Joy Tretheway 
> Date: Mon, Feb 13, 2017 at 8:27 PM
> Subject: TripleO mascot - how can I help your team?
> To: Emilien Macchi 
>
>
> Hi Emilien,
>
> I’m following up on the much-debated TripleO logo. I’d like to help your
> team reach a solution that makes them happy but still fits within the
> family of logos we’re using at the PTG and going forward. Here’s what our
> illustrators came up with, which hides an “O” shape in the owl (face and
> wing arcs).
>
> https://www.dropbox.com/sh/qz45miiiam3caiy/AAAzPGYEZRMGH6Otid3bLfHFa?dl=0
> At this point, I don’t have quorum from your team (I got a lot of
> conflicting feedback, most of which was “don’t like” but not actionable for
> the illustrators to make a revision). At the PTG, we’ll have mascot
> stickers and signage for all teams except for Ironic and TripleO, since
> we’re still waiting on your teams to make a final decision.
>
> May I recommend that your team choose one person (or a small group of no
> more than three) to finalize this? I was able to work through all of
> Swift’s issues with just a quick 15-minute chat with John Dickinson and I’d
> like to believe we can solve this for TripleO as well.
>
> We know some of your team has expressed concern over retiring the existing
> mascot. It’s not our intention to make anyone “get rid of” a beloved icon.
> Your team can certainly print it on vintage items like shirts and stickers.
> But for official channels like the website, we need a logo to represent
> TripleO that’s cohesive with the rest of the set.
>
> Perhaps when you’re face to face with your team at the PTG, you can
> discuss and hopefully render a final decision to either accept this as a
> logo, or determine a few people willing to make any final changes with me?
>
> Thanks in advance for your help!
>
>
> [image: photo]
> *Heidi Joy Tretheway*
> Senior Marketing Manager, OpenStack Foundation
> 503 816 9769 | Skype: heidi.tretheway
> 
> 
>   
>
>
>
>
>
>
> --
> Emilien Macchi
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Alex Xu]

Hi,

We have weekly Nova API meeting tomorrow. 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
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [release] Proposed Pike release schedule

[Thierry Carrez]

Hi everyone,

It's more than time to set the Pike release schedule in stone. Here is
the proposed schedule:

https://review.openstack.org/#/c/425254/

which you can see in human-friendly rendering at:

http://docs-draft.openstack.org/54/425254/3/check/gate-releases-docs-ubuntu-xenial/a06786d//doc/build/html/pike/schedule.html

The second PTG is now 99% sure to happen on the week of September 11,
which lets us avoid August vacation price hikes and Labor day Monday
week-before week-after. This schedule is based on the idea that the PTG
would happen on R+2 week (rather than on the R+0 like in Ocata).

Please comment on the review if you see glaring issues with it -- we'd
like to make the schedule official before Pike PTG starts.

Cheers,

-- 
Thierry Carrez (ttx)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [vitrage] Vitrage logo files

[Afek, Ifat (Nokia - IL)]

Hi,

We received our final logo files. Enjoy ☺

Ifat.


From: Heidi Joy Tretheway 
Date: Tuesday, 14 February 2017 at 01:23
To: "Afek, Ifat (Nokia - IL)" 
Subject: Vitrage logo files

Hi Ifat,

I’m excited to finally be able to share final project logo files with you. 
Inside this folder, you’ll find full-color and one-color versions of the logo, 
plus a mascot-only version, in EPS, JPG and PNG formats. You can use them on 
presentations and wherever else you’d like to add some team flair.

https://www.dropbox.com/sh/qghopozg09ktmte/AAC1Uihwn1kgURqYNTxS7T2Pa?dl=0

At the PWG, we’ll have stickers for your team of the mascot, plus signage on 
your room. I’m especially excited for the project teams to see all of the logos 
together as one group, because they work beautifully together stylistically 
while making each project’s mark distinctive. Feel free to share this with your 
team, and thanks to you and to them for the hard work they put into reaching an 
agreement on the mascot. Also feel free to direct any questions my way!

[hoto]

Heidi Joy Tretheway
Senior Marketing Manager, OpenStack Foundation
503 816 9769 | Skype: 
heidi.tretheway
[https://s3.amazonaws.com/images.wisestamp.com/icons_32/linkedin.png]
 [https://s3.amazonaws.com/images.wisestamp.com/icons_32/twitter.png] 
  
[https://s3.amazonaws.com/ucwebapp.wisestamp.com/5dafe09f-4769-4e67-8016-7a75904bb079/OpenStackicon.format_png.resize_32x32.png]
 





__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Lucas Alvares Gomes]

Hi,

Just a FYI, we have had similar discussions about the proposed logo for
Ironic, there's still many unanswered questions but, if you guys are
interested this is the link to the ML thread:
http://lists.openstack.org/pipermail/openstack-dev/2017-February/111401.html

Cheers,
Lucas

On Tue, Feb 14, 2017 at 2: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).
>
>
> Personally, I would vote for keeping our existing logo (1.) unless someone
> has time to create another one or if the team likes the proposed one.
>
> The reason why I want to keep our logo is because our current logo was
> created by TripleO devs, we like it and we already have tee-shirts and
> other goodies with it. I don't see any good reason to change it.
>
> Discussion is open and we'll vote as a team.
>
> Thanks,
>
> Emilien.
>
> -- Forwarded message --
> From: Heidi Joy Tretheway 
> Date: Mon, Feb 13, 2017 at 8:27 PM
> Subject: TripleO mascot - how can I help your team?
> To: Emilien Macchi 
>
>
> Hi Emilien,
>
> I’m following up on the much-debated TripleO logo. I’d like to help your
> team reach a solution that makes them happy but still fits within the
> family of logos we’re using at the PTG and going forward. Here’s what our
> illustrators came up with, which hides an “O” shape in the owl (face and
> wing arcs).
>
> https://www.dropbox.com/sh/qz45miiiam3caiy/AAAzPGYEZRMGH6Otid3bLfHFa?dl=0
> At this point, I don’t have quorum from your team (I got a lot of
> conflicting feedback, most of which was “don’t like” but not actionable for
> the illustrators to make a revision). At the PTG, we’ll have mascot
> stickers and signage for all teams except for Ironic and TripleO, since
> we’re still waiting on your teams to make a final decision.
>
> May I recommend that your team choose one person (or a small group of no
> more than three) to finalize this? I was able to work through all of
> Swift’s issues with just a quick 15-minute chat with John Dickinson and I’d
> like to believe we can solve this for TripleO as well.
>
> We know some of your team has expressed concern over retiring the existing
> mascot. It’s not our intention to make anyone “get rid of” a beloved icon.
> Your team can certainly print it on vintage items like shirts and stickers.
> But for official channels like the website, we need a logo to represent
> TripleO that’s cohesive with the rest of the set.
>
> Perhaps when you’re face to face with your team at the PTG, you can
> discuss and hopefully render a final decision to either accept this as a
> logo, or determine a few people willing to make any final changes with me?
>
> Thanks in advance for your help!
>
>
> [image: photo]
> *Heidi Joy Tretheway*
> Senior Marketing Manager, OpenStack Foundation
> 503 816 9769 | Skype: heidi.tretheway
> 
> 
>   
>
>
>
>
>
>
> --
> Emilien Macchi
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [trove] Trove logo files

[Amrith Kumar]

Trove team members,

 

Please see email below from the Openstack Foundation with a link to the Trove 
logo files.

 

-amrith

 

 

From: Heidi Joy Tretheway [mailto:heidi...@openstack.org] 
Sent: Tuesday, February 14, 2017 4:53 AM
To: Amrith Kumar
Subject: Trove logo files

 

Hi Amrith, 

 

I’m excited to finally be able to share final project logo files with you. 
Inside this folder, you’ll find full-color and one-color versions of the logo, 
plus a mascot-only version, in EPS, JPG and PNG formats. You can use them on 
presentations and wherever else you’d like to add some team flair. 

 

https://www.dropbox.com/sh/v7l130m8ci4kmv7/AAA7dBhyjtTSaaQZvYOatmJga?dl=0

 

At the PWG, we’ll have stickers for your team of the mascot, plus signage on 
your room. I’m especially excited for the project teams to see all of the logos 
together as one group, because they work beautifully together stylistically 
while making each project’s mark distinctive. Feel free to share this with your 
team, and thanks to you and to them for the hard work they put into reaching an 
agreement on the mascot. Also feel free to direct any questions my way!

 


  

 

Heidi Joy Tretheway
Senior Marketing Manager, OpenStack Foundation

  503 816 9769 | Skype:  

 heidi.tretheway

      
  

 

 

 



smime.p7s
Description: S/MIME cryptographic signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Fwd: Sahara logo files

[Telles Nobrega]

Hi Sahara team,

FYI here are the new logos of our project. We will get some cool stuff with
it at the PTG.

Enjoy using it,


-- Forwarded message --
From: Heidi Joy Tretheway 
Date: Mon, Feb 13, 2017 at 8:16 PM
Subject: Sahara logo files
To: tenob...@redhat.com, Vitaly Gridnev 


Hi Vitaly and Telles,

I’m excited to finally be able to share final project logo files with you.
Inside this folder, you’ll find full-color and one-color versions of the
logo, plus a mascot-only version, in EPS, JPG and PNG formats. You can use
them on presentations and wherever else you’d like to add some team flair.

https://www.dropbox.com/sh/6ets39nenrbuccl/AAAEGEMsAZbytHQ_BcZyTShTa?dl=0

At the PWG, we’ll have stickers for your team of the mascot, plus signage
on your room. I’m especially excited for the project teams to see all of
the logos together as one group, because they work beautifully together
stylistically while making each project’s mark distinctive. Feel free to
share this with your team, and thanks to you and to them for the hard work
they put into reaching an agreement on the mascot. Also feel free to direct
any questions my way!


[image: photo]
*Heidi Joy Tretheway*
Senior Marketing Manager, OpenStack Foundation
503 816 9769 | Skype: heidi.tretheway

  
  






-- 
[image: Red Hat] 
Telles Nobrega | Software Engineer
Red Hat Brasil
T: +55 11 3529-6000 <+55%2011%203529-6000> | M: +55 11 9 9910-1689
Av. Brigadeiro Faria Lima 3900, 8° Andar. São Paulo, Brasil.
RED HAT | TRIED. TESTED. TRUSTED. Saiba porque em redhat.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [telemetry] Telemetry logo files

[Julien Danjou]

Team,

FYI.

Not sure what the PWG is, though if it's the PTG, since we won't be
there… well. :)

--- Begin Message ---
Hi Julien, 

I’m excited to finally be able to share final project logo files with you. 
Inside this folder, you’ll find full-color and one-color versions of the logo, 
plus a mascot-only version, in EPS, JPG and PNG formats. You can use them on 
presentations and wherever else you’d like to add some team flair. 

https://www.dropbox.com/sh/c2xop4mve9h3fvw/AADqjLNkIENChKMMxrGMbVsna?dl=0 

At the PWG, we’ll have stickers for your team of the mascot, plus signage on 
your room. I’m especially excited for the project teams to see all of the logos 
together as one group, because they work beautifully together stylistically 
while making each project’s mark distinctive. Feel free to share this with your 
team, and thanks to you and to them for the hard work they put into reaching an 
agreement on the mascot. Also feel free to direct any questions my way!



Heidi Joy Tretheway
Senior Marketing Manager, OpenStack Foundation
503 816 9769  | Skype: heidi.tretheway 

     




--- End Message ---


-- 
Julien Danjou
# Free Software hacker
# https://julien.danjou.info


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [designate] Status of the project

[Hayes, Graham]

On 11/02/17 15:12, Andrea Frittoli wrote:
> 
> 
> On Thu, Feb 9, 2017 at 7:22 PM Hayes, Graham  > wrote:
> 
> The HTML version of this is here:
> http://graham.hayes.ie/posts/openstack-designate-where-we-are/
> 
> I have been asked a few times recently "What is the state of the
> Designate
> project?", "How is Designate getting on?", and by people who know
> what is
> happening "What are you going to do about Designate?".



> 
> We also need help from cross project teams - the work done by them is
> brilliant
> but it can be hard for smaller projects to consume. We have had a lot of
> progress since the `Leveller Playing Field`_ debate, but a lot of
> work is
> still optimised for the larger teams who get direct support, or well
> resourced
> teams who can dedicate people to the implementation of plugins / code.
> 
> 
> The QA team is committed to serve every single project in big tent
> community.
> Please reach out to us on IRC in #openstack-qa or add an item to the QA
> meeting agenda.
> We are a rather small team ourselves, so we won't be able to implement
> things on project
> team's behalf, but we'll do our best to help.
> 
> andrea
> 

While this may be the intention, it is definitely not the reality. Some
projects do have the work done for them by the QA team - and as I said,
it is generally the larger teams that could afford to take the load vs
the smaller teams that struggle.

A perfect example happened yesterday.

Grenade was being tested for Ocata -> Pike upgrade, before the jobs on
master was updated. As part of this change Keystone moved from v2 to v3.

This caused an issue in 2 in-tree grenade projects (Nova and Cinder)
due to a behavior difference in the OpenStack CLI [0]

This issue was fixed in tree for these projects, before they knew
there was a problem, but projects that have grenade plugins didn't find
out until our gate failed, and started blocking patches.

This then meant 30-40 mins or so of debugging the logs, finding the bug,
writing a fix, then waiting for the the patch to merge.

I wouldn't even ask for a fix to be coded for us - just an email
with "you need to make sure your grenade plugin adds a role to
the user you create from Pike onwards" would have saved a lot
of time.

I understand that the QA team focuses on the core projects
more - that is just how OpenStack operates, but just being
mindful of projects that use things like devstack, grenade,
tempest etc as plugin may not get the fixes that happen for
the core.

- Graham

0 - https://bugs.launchpad.net/keystone/+bug/1662911


> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Vincent FRANÇOISE]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

+1

On 14/02/2017 11:27, ? ? wrote:
> His activity will help Watcher Team to make this project better.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJYot3aAAoJEEb+XENQ/jVSvIEH/RsqFZZ7hZyA7ExieF7K4GmN
d1f1vnPbOR3MgqQTbezixIPIwzrDw9dtpU6q8BRPARP6ja2tOPNoYHc1CZmxgwz9
Mc5iVhvAaKuzL7KKpeROVkLkVUJ9bZnxNM/pkgiq0qXYoBaitgVdPVTIE6nBLdpV
yHRkUG24pkojogIJGIbB2cJeKganJ+PrCB59buAof1NqEhujt00akfjHCKbc7Wc/
oSmx2VD3aRn8OcfAhQ1pQgRYpa6MRFBRbDUPejVyiGzFWTDreWA3cLVq2xpGEcCW
ahcq2MNsZCiFegD4u9jYroULOALhdGBUctONbluaqbfZ7PhPPqQxSJGQq96hTCg=
=WsCi
-END PGP SIGNATURE-

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Чадин Александр]

Hello, Watcher Team

licanwei has made a lot of good contributions[1] to the Watcher Project
(including reviews and patches) so I would like to promote him as Core 
Developer.

His activity will help Watcher Team to make this project better.

Waiting for your vote.

[1] 
https://review.openstack.org/#/q/owner:%22licanwei+%253Cli.canwei2%2540zte.com.cn%253E%22+status:closed
___
Alexander Chadin,
OpenStack Developer
Software Solutions Department
Servionica Ltd.
Work email: a.cha...@servionica.ru
Mobile: +7(916)693-58-81

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [watcher] PTG agenda

[Antoine Cabot]

Hi team,

Our PTG agenda is almost ready [1], it is still time to add topics to
the list that you want to discuss. As some of our contributors will
not be able to attend, I would suggest to add your topics and comments
by February 17th so that we can have a clear agenda for anyone who
wants to join remotely.

Thanks,

Antoine

[1] https://etherpad.openstack.org/p/pike-watcher-ptg

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Watcher] Nominating Prudhvi Rao Shedimbi to Watcher Core

[Vincent FRANÇOISE]

Team,

I would like to promote Prudhvi Rao Shedimbi to the core team. He's done
a great work in reviewing many patchsets[1] and I believe that he has a
good vision of Watcher as a whole.

I think he would make an excellent addition to the team.

Please vote

[1] http://stackalytics.com/report/contribution/watcher/90

Vincent FRANCOISE
B<>COM

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev