[openstack-dev] [all] [keystone] Is keystone support combined authentication in release L?

[赵智龙]

hi guys.
i just want to ask a small question.
Is keystone support combined authentication in release L?__
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] Is keystone support combined authentication in release L?

[赵智龙]

hi guys.
i just want to ask a small question.
Is keystone support combined authentication in release L?__
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] Nova PTL for Newton

[GHANSHYAM MANN]

Thanks a lot John for great leadership and all achievements. You have
been very encouraging and helpful always.
Regards
Ghanshyam Mann


On Sat, Mar 12, 2016 at 4:22 AM, John Garbutt  wrote:
> Hi,
>
> It has been greatly rewarding serving you all as Nova PTL over the
> Liberty and Mitaka cycles. I thank you all for the support,
> encouragement and advice I have been given over the last year. I
> really appreciate that. (That's british speak for "I love you all", or
> something like that).
>
> I don't plan on standing for the Newton cycle. I think its a good time
> for someone to bring fresh energy, ideas, and drive to help keep Nova
> driving forward. I have enjoyed my time as PTL, as such, I would
> consider standing again. We have a good number of folks stepping up to
> lead different parts of the project. I hope we can grow that effort,
> and I hope to continue to be part of that.
>
> I aim to continue contributing to Nova (I hope to be in Austin, and I
> hope to write some code again soon). I will certainly make time to
> ensure a smooth transition to the next PTL.
>
> Many thanks,
> johnthetubaguy
>
> __
> 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] [neutron]Where did the flows go in ovs bridge?

[Zhi Chang]

My neutron version is openstack-neutron-7.0.4-1.el7
 
 
-- Original --
From:  "Hirofumi Ichihara";
Date:  Sun, Mar 13, 2016 10:38 AM
To:  "openstack-dev"; 

Subject:  Re: [openstack-dev] [neutron]Where did the flows go in ovs bridge?

 
   Which version did you use? Neutron had the issue once.
 
 On 2016/03/13 10:54, Zhi Chang wrote:
 
hi, guys.
   
   
   I deployed DVR in my local environment by following  this 
document(https://wiki.openstack.org/wiki/Neutron/DVR).  And I have 
three compute nodes which running DVR l3-agent and two network nodes 
which running DVR_SNAT l3-agent.
   
   
   I created a vm in one of the computes nodes. And flows was 
generated normally. But, all flows are gone when I  restart 
"neutron-openvswitch-agent"!. I wait a few minutes but I can't see any 
flows were generated. 
   
   
   Could someone tell me why the flows are gone and they can't 
generated anymore?
   
   
   
   
   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__
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]Where did the flows go in ovs bridge?

[Zhi Chang]

There are many WARNING infos:


2016-03-12 08:23:28.919 30738 WARNING 
neutron.plugins.ml2.drivers.openvswitch.agent.openflow.ovs_ofctl.ofswitch 
[req-c5695ca8-b886-4092-970f-edb18d8d87cc - - - - -] Deleting flow  
cookie=0x86cb85757ac914ee, duration=172005.248s, table=22, n_packets=6, 
n_bytes=308, idle_age=1163, hard_age=65534, dl_vlan=1 
actions=strip_vlan,set_tunnel:0x32,output:3,output:2,output:6,output:5,output:4
2016-03-12 08:23:28.934 30738 WARNING 
neutron.plugins.ml2.drivers.openvswitch.agent.openflow.ovs_ofctl.ofswitch 
[req-c5695ca8-b886-4092-970f-edb18d8d87cc - - - - -] Deleting flow  
cookie=0x86cb85757ac914ee, duration=169637.050s, table=22, n_packets=8, 
n_bytes=608, idle_age=1162, hard_age=65534, dl_vlan=2 
actions=strip_vlan,set_tunnel:0x4c,output:3,output:2,output:6,output:5,output:4
2016-03-12 08:23:28.949 30738 WARNING 
neutron.plugins.ml2.drivers.openvswitch.agent.openflow.ovs_ofctl.ofswitch 
[req-c5695ca8-b886-4092-970f-edb18d8d87cc - - - - -] Deleting flow  
cookie=0x86cb85757ac914ee, duration=93767.242s, table=22, n_packets=11, 
n_bytes=834, idle_age=1163, hard_age=65534, dl_vlan=3 
actions=strip_vlan,set_tunnel:0x53,output:3,output:2,output:6,output:5,output:4
2016-03-12 08:23:28.964 30738 WARNING 
neutron.plugins.ml2.drivers.openvswitch.agent.openflow.ovs_ofctl.ofswitch 
[req-c5695ca8-b886-4092-970f-edb18d8d87cc - - - - -] Deleting flow  
cookie=0x86cb85757ac914ee, duration=93743.254s, table=22, n_packets=9, 
n_bytes=618, idle_age=1163, hard_age=65534, dl_vlan=4 
actions=strip_vlan,set_tunnel:0x22,output:3,output:2,output:6,output:5,output:4
2016-03-12 08:24:16.757 30738 INFO neutron.agent.securitygroups_rpc 
[req-a0e6c976-5ded-4300-bbd0-e489dcd83e02 9f1d641c46954391ba46f06936713fdd 
2bec68aa33a54a8b905d4516eaa8b81e - - -] Security group member updated 
[u'46d98306-d04e-4420-b86b-c6685bc2a8dc']

 
 
-- Original --
From:  "Doug Wiegley";
Date:  Sun, Mar 13, 2016 10:35 AM
To:  "OpenStack Development Mailing List (not for usage 
questions)"; 

Subject:  Re: [openstack-dev] [neutron]Where did the flows go in ovs bridge?

 
Take a look in /var/log/neutron/openvswitch-agent.log, or similar, on the 
hypervisor. 

Doug


> On Mar 12, 2016, at 6:54 PM, Zhi Chang  wrote:
> 
> hi, guys.
> 
> I deployed DVR in my local environment by following  this 
> document(https://wiki.openstack.org/wiki/Neutron/DVR).  And I have three 
> compute nodes which running DVR l3-agent and two network nodes which running 
> DVR_SNAT l3-agent.
> 
> I created a vm in one of the computes nodes. And flows was generated 
> normally. But, all flows are gone when I  restart 
> "neutron-openvswitch-agent"!. I wait a few minutes but I can't see any flows 
> were generated. 
> 
> Could someone tell me why the flows are gone and they can't generated 
> anymore?
> 
> 
> 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

__
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] [neutron]Where did the flows go in ovs bridge?

[Hirofumi Ichihara]

Which version did you use? Neutron had the issue once.

On 2016/03/13 10:54, Zhi Chang wrote:

hi, guys.

I deployed DVR in my local environment by following  this 
document(https://wiki.openstack.org/wiki/Neutron/DVR).  And I have 
three compute nodes which running DVR l3-agent and two network nodes 
which running DVR_SNAT l3-agent.


I created a vm in one of the computes nodes. And flows was 
generated normally. But, all flows are gone when I  restart 
"neutron-openvswitch-agent"!. I wait a few minutes but I can't see any 
flows were generated.


Could someone tell me why the flows are gone and they can't 
generated anymore?



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


__
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]Where did the flows go in ovs bridge?

[Doug Wiegley]

Take a look in /var/log/neutron/openvswitch-agent.log, or similar, on the 
hypervisor. 

Doug


> On Mar 12, 2016, at 6:54 PM, Zhi Chang  wrote:
> 
> hi, guys.
> 
> I deployed DVR in my local environment by following  this 
> document(https://wiki.openstack.org/wiki/Neutron/DVR).  And I have three 
> compute nodes which running DVR l3-agent and two network nodes which running 
> DVR_SNAT l3-agent.
> 
> I created a vm in one of the computes nodes. And flows was generated 
> normally. But, all flows are gone when I  restart 
> "neutron-openvswitch-agent"!. I wait a few minutes but I can't see any flows 
> were generated. 
> 
> Could someone tell me why the flows are gone and they can't generated 
> anymore?
> 
> 
> 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

__
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] Not running for PTL

[GHANSHYAM MANN]

Thanks Matt for your great leadership and hardwork around QA world.

It has been great working in your leadership and provided a smooth &
cool environment during
those period.

There lot of key things we achieved and with diversity of ideas. You
have been always very active
and present to help all. Your great skill and versatile knowledge
helped QA to achieve a lot and going
on good direction.

And yes best thing is how you cover your work time for all different
different timeznoes. From JST too, almost
everyday we can contact you.

Yea, we need you not only as team member also to help smooth
transition to new PTL.

Congratulation for being as successful PTL for 2 years.

Thanks
gmann

On Sat, Mar 12, 2016 at 4:34 AM, Matthew Treinish  wrote:
> Hi everyone,
>
> I'm writing this to announce that I am not running for QA PTL this cycle. I've
> been the QA PTL for the past 4 cycles and I think it's time for another person
> to take over the role. I think during the past 4 cycles the QA community has
> grown greatly and become a much larger and stronger community compared to when
> I first took on the position in the Juno cycle.
>
> I strongly believe in the diversity of leadership and ideas, and I don't want
> the community to grow stagnant because it becomes synonymous with just my 
> voice.
> Being a PTL is not the same as being an autocrat and I think it's time for
> another person to step up and take over the QA PTL spot.
>
> That being said, I'm not planning on going anywhere or leaving the project. I
> fully intend to continue working and being heavily involved with the QA 
> program,
> as I have for been the past 2 years. (although maybe with a bit more free time
> now)
>
> -Matt Treinish
>
> __
> 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]Where did the flows go in ovs bridge?

[Zhi Chang]

hi, guys.


I deployed DVR in my local environment by following  this 
document(https://wiki.openstack.org/wiki/Neutron/DVR).  And I have three 
compute nodes which running DVR l3-agent and two network nodes which running 
DVR_SNAT l3-agent.


I created a vm in one of the computes nodes. And flows was generated 
normally. But, all flows are gone when I  restart "neutron-openvswitch-agent"!. 
I wait a few minutes but I can't see any flows were generated. 


Could someone tell me why the flows are gone and they can't generated 
anymore?




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

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

[Matthias Runge]

On 10/03/16 11:48, Beth Elwell wrote:

> 
> If we will anyway have potential breakage I don’t understand why the
> better solution here would not be to just use the bower and npm tools
> which are standardised for JavaScript and would move Horizon more
> towards using widely recognised tooling from within not just Openstack
> but the wider development community. Back versions always need to be
> supported for a time, however I would add that long term this could end
> up saving time and create a stable longer term solution.
> 

I have a few issues with those "package managers":
- downloads are not verified, there is a chance of getting a "bad" download.
- they are pointing to the outside world, like to github etc. While they
appear to work "most of the time", that might not good enough for the gate
- how often have we been blocked by releases of software not managed by
OpenStack? Seriously, that happens quite a few times over a release
cycle, not to mention breakages by releases of our own tools turning out
to block one or the other sub-project.

Matthias
-- 
Matthias Runge 

Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham,
Michael O'Neill

__
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] [Horizon] How do we move forward with xstatic releases?

[Matthias Runge]

On 10/03/16 08:46, Richard Jones wrote:
> On 10 March 2016 at 18:23, Matthias Runge  > wrote:
> 
> 4.alt.2:
> move to proper packages for static file management. I mean, they need to
> be built anyways.
> 
> 
> Please define what you mean by "proper packages" here. I *think* you
> might mean system packages (aka Debian or Red Hat) which is not feasible
> given other environments that Horizon runs under. Please correct me if
> I'm wrong!

Exactly. I mean system packages. If there are issues with system
packages, then let's address the issue rather than re-inventing the wheel.

Weren't we just talking about providing dependencies for the gate? I
mean, for production, it's quite the same situation we are at the
moment. Nobody requires you to install Horizon and dependencies
especially via rpm, deb or pip: Take what you want.

> It has been mentioned, xstatic packages can block the gate. We currently
> control xstatic package releases, thus we can roll back, if something
> goes wrong.
> 
> If we're pulling directly with npm/bower, someone from the outside can
> break us. We already have the situation with pypi packages.
> With proper packages, we could even use the gate to release those
> packages and thus verify, we're not breaking anyone.
> 
> 
> We're going to have potential breakage (gate breakage, in the integrated
> tests) any time we release a package (regardless of release mechanism)
> and have to update two separate repositories resulting in out-of-sync
> version specification and expectation (ie. upper-constraints
> specification and Horizon's code expectation) as described in my OP. The
> only solution that we're aware of is to synchronise updating those two
> things, through one of the mechanisms proposed so far (or possibly
> through a mechanism not yet proposed.)
> 

Yes, and my proposal to address this is to gate updating/releasing
dependencies the same way we're currently gating each change in horizon.

> 
> 1. Horizon maintains its own constrained version list for the xstatic
> packages,
> 2. Plugins to Horizon must depend on Horizon to supply xstatic packages
> except where they use additional packages that Horizon does not use, and
> 3. We avoid installing app-catalog (the system, not the plugin) in the
> integrated tests (I don't believe doing this is even on the ...
> "horizon" so to speak) *or* in a Debian / Red Hat (i.e. system-packaged)
> system that also has Horizon installed. Or we try to convince
> app-catalog to stay lock-step with Horizon's xstatic versions. I
> understand the risk of a collision between app-catalog and Horizon in
> the same system-packaged environment is very low.

I don't really see a chance for app-catalog to require Horizon as a
dependency and different versions of xstatic packages. This would be an
immediate show-stopper for app-catalog either on Debian or on RPM based
systems.

Let me repeat myself: you're free to install dependencies as you like,
npm, bower, whatever. I was simply speaking about the gate and about
gating dependencies to be sure, we're not broken by someone from outside.

Matthias
-- 
Matthias Runge 

Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham,
Michael O'Neill

__
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] PTL Candidacy for Adam Young

[Adam Young]

I am, once again, throwing my hat in the ring.

No long position statement.

If you know me, you know what I stand for.
If you don't know me, you won;t be voting in the Keystone PTL election.


I will state this:  part of a successful organization is that the 
leadership position be held accountable.  Leaders run unopposed do not 
then know if they continue to hold the support of their team, or if just 
no one is willing to assumed the burden.


Don't worry about feeling loyal to the current PTL. This way, if they 
get elected, they know they truly have the project's support.


With Condorcet, you will not mess things up.

If you are committed to your project, run for 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] [horizon] PTL noncandidacy

[Adam Young]

On 03/11/2016 12:19 PM, David Lyle wrote:

After five cycles as PTL of Horizon, I've decided not to run for the
Newton cycle.

I am exceptionally proud of the things we've accomplished over this
time. I'm amazed by how much our project's community has grown and
evolved.

Looking at the community now, I believe we have a tremendous group of
contributors for moving forward. There are several people capable of
becoming great PTLs and overall the community will be healthier with
some turnover in the PTL role. I feel honored to have had your trust
over this time and lucky to have worked with such great people.

I will still be around and will help the next PTL make a smooth
transition where requested.

David

__
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



This drew a groan from me. You've been fantastic.  Thanks for all you 
have done.


__
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] [tc] Question about electorate for project without gerrit contribution

[Thierry Carrez]

Jeremy Stanley wrote:

I guess for teams with no deliverables *and* no extra ATCs, they
probably also don't need a PTL?


My take is that those teams do not need to be an official project team 
either. We now require some activity before approving project teams, but 
packaging-deb passed before that requirement. It was approved 7 months 
ago and still no sign of activity, so it's not completely crazy to kick 
it back to non-official status (especially now that it doesn't trigger 
any repository rename).


I'll ask Monty the new PTL about his plans there :)

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