[Yahoo-eng-team] [Bug 1589358] [NEW] Getting error unexpected keyword 'scope' while requesting OS-FEDERATION scoped token

2016-06-05 Thread Sohan Sangwan 
Public bug reported:

I am using stable/Liberty and configured SAML federation. I successfully
get the unscoped token but when I request for Scoped token I get the
error:

{"error": {"message": "authenticate_for_token() got an unexpected
keyword argument 'scope'", "code": 400, "title": "Bad Request"}}

Here follows how I am making request for Scoped token:

curl -X POST -H "Content-Type: application/json" \
  -H "X-Auth-Token: 73462516f0cb4e1abf3cad52ff5f152a" \
 -d '{ "auth": { "identity": { "methods": [ "token" ], "token": { "id": 
"73462516f0cb4e1abf3cad52ff5f152a" } } }, "scope": { "project": { "id": 
"57c0b4f4e998416aa5040decf6c8a764" } } }'\
   http://localhost:5000/v3/auth/tokens


The Unscoped token I received is: 73462516f0cb4e1abf3cad52ff5f152a

I am following the following documentation:

https://specs.openstack.org/openstack/keystone-specs/api/v3/identity-
api-v3-os-federation-ext.html#request-a-scoped-os-federation-token

** Affects: keystone
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1589358

Title:
  Getting error unexpected keyword 'scope'  while requesting OS-
  FEDERATION scoped token

Status in OpenStack Identity (keystone):
  New

Bug description:
  I am using stable/Liberty and configured SAML federation. I
  successfully get the unscoped token but when I request for Scoped
  token I get the error:

  {"error": {"message": "authenticate_for_token() got an unexpected
  keyword argument 'scope'", "code": 400, "title": "Bad Request"}}

  Here follows how I am making request for Scoped token:

  curl -X POST -H "Content-Type: application/json" \
-H "X-Auth-Token: 73462516f0cb4e1abf3cad52ff5f152a" \
   -d '{ "auth": { "identity": { "methods": [ "token" ], "token": { "id": 
"73462516f0cb4e1abf3cad52ff5f152a" } } }, "scope": { "project": { "id": 
"57c0b4f4e998416aa5040decf6c8a764" } } }'\
 http://localhost:5000/v3/auth/tokens

  
  The Unscoped token I received is: 73462516f0cb4e1abf3cad52ff5f152a

  I am following the following documentation:

  https://specs.openstack.org/openstack/keystone-specs/api/v3/identity-
  api-v3-os-federation-ext.html#request-a-scoped-os-federation-token

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1589358/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1477098] Re: When you unshelve an instance, AggregateImagePropertiesIsolation filter doesn't work.

2016-06-05 Thread Launchpad Bug Tracker 
[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]

** Changed in: nova
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1477098

Title:
  When you unshelve an instance, AggregateImagePropertiesIsolation
  filter doesn't work.

Status in OpenStack Compute (nova):
  Expired

Bug description:
  When you unshelve an instance, the instance will be created on a Compute-Node 
that belongs to an aggregate which  
  doesn't have same metadata.

  conditions:
  　・An cinder volume is attached as a bootable volume.

  　・AggregateImagePropertiesIsolation filter is in scheduler_default_filters of 
/etc/nova/nova.conf file.
  　
・Propertes are defined in an image's metadata
   For example　key:'CentOS' value:'true'

・two or more aggregates exist.one of which has same metadata as image's 
Property.　
  　・an instance on host that belongs to the aggregate which has same metadata.

   Reproduce steps:
1.shelve an instance
  # nova shelve UUID

2.unshlve an instance
  # nova unshelve UUID

  Expected result:
   the instance is on a Compute-Node that belongs to an aggregate which has 
same metadata.

  Actual result:
   the instance is on a Compute-Node that belongs to an aggregate which  
doesn't have same metadata.

  environments:
   Icehouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1477098/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1573505] Re: create ovs vm, ovs agent log is abnormal

2016-06-05 Thread QunyingRan 
** Changed in: neutron
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1573505

Title:
  create ovs vm,ovs  agent log is abnormal

Status in neutron:
  Invalid

Bug description:
   1. create ovs vm find error log in neutron-openvswitch-agent, the port staus 
is build.
  ---
  2016-04-22 04:47:47.624 ERROR 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent 
[req-90c9a4d9-358b-4590-bad4-61580d0683f4 None None] Error while processing VIF 
ports
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent Traceback (most 
recent call last):
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File 
"/opt/stack/neutron/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py",
 line 1992, in rpc_loop
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent port_info, 
ovs_restarted)
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File 
"/opt/stack/neutron/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py",
 line 1623, in process_network_ports
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent 
port_info.get('updated', set()))
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File 
"/opt/stack/neutron/neutron/agent/securitygroups_rpc.py", line 294, in 
setup_port_filters
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent 
self.prepare_devices_filter(new_devices)
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File 
"/opt/stack/neutron/neutron/agent/securitygroups_rpc.py", line 149, in 
decorated_function
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent *args, 
**kwargs)
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File 
"/opt/stack/neutron/neutron/agent/securitygroups_rpc.py", line 174, in 
prepare_devices_filter
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent 
self.firewall.prepare_port_filter(device)
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File 
"/usr/lib64/python2.7/contextlib.py", line 24, in __exit__
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent 
self.gen.next()
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File 
"/opt/stack/neutron/neutron/agent/firewall.py", line 129, in defer_apply
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent 
self.filter_defer_apply_off()
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File 
"/opt/stack/neutron/neutron/agent/linux/iptables_firewall.py", line 823, in 
filter_defer_apply_off
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent 
self.unfiltered_ports)
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File 
"/opt/stack/neutron/neutron/agent/linux/iptables_firewall.py", line 214, in 
_setup_chains_apply
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent 
self._setup_chain(port, firewall.INGRESS_DIRECTION)
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File 
"/opt/stack/neutron/neutron/agent/linux/iptables_firewall.py", line 241, in 
_setup_chain
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent 
self._add_rules_by_security_group(port, DIRECTION)
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File 
"/opt/stack/neutron/neutron/agent/linux/iptables_firewall.py", line 493, in 
_add_rules_by_security_group
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent 
self._update_ipset_members(remote_sg_ids)
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File 
"/opt/stack/neutron/neutron/agent/linux/iptables_firewall.py", line 529, in 
_update_ipset_members
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent 
self.ipset.set_members(sg_id, ip_version, current_ips)
  2016-04-22 04:47:47.624 TRACE 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File

[Yahoo-eng-team] [Bug 1589328] [NEW] Alembic branch checks do not detect Add/DropColumn violations

2016-06-05 Thread Henry Gessau 
Public bug reported:

In the test_branches test we check that elements are not added in the
contract branch, and that elements are not removed in the expand branch.
However, this check is not working for Add/DropColumn because they are
processed as alembic clauses which have no element property.

** Affects: neutron
 Importance: Undecided
 Assignee: Henry Gessau (gessau)
 Status: In Progress


** Tags: db functional-tests

** Tags added: db functional-tests

** Changed in: neutron
 Assignee: (unassigned) => Henry Gessau (gessau)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1589328

Title:
  Alembic branch checks do not detect Add/DropColumn violations

Status in neutron:
  In Progress

Bug description:
  In the test_branches test we check that elements are not added in the
  contract branch, and that elements are not removed in the expand
  branch. However, this check is not working for Add/DropColumn because
  they are processed as alembic clauses which have no element property.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1589328/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1589320] [NEW] Booting Instance and accessing console-log throws nova-api error

2016-06-05 Thread Sindhur 
Public bug reported:

On booting a nova instance and immediately trying to access the console-
log using nova console-log, an error message reporting an unexpected API
Error is seen in a Mitaka-Stable environment. The Nova API Log is as
follows : http://paste.openstack.org/show/508203/

** Affects: nova
 Importance: Undecided
 Status: New

** Changed in: fuel-plugin-contrail
   Status: New => Invalid

** Project changed: fuel-plugin-contrail => nova

** Changed in: nova
   Status: Invalid => New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1589320

Title:
  Booting Instance and accessing console-log throws nova-api error

Status in OpenStack Compute (nova):
  New

Bug description:
  On booting a nova instance and immediately trying to access the
  console-log using nova console-log, an error message reporting an
  unexpected API Error is seen in a Mitaka-Stable environment. The Nova
  API Log is as follows : http://paste.openstack.org/show/508203/

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1589320/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1589320] [NEW] Booting Instance and accessing console-log throws nova-api error

2016-06-05 Thread Launchpad Bug Tracker 
You have been subscribed to a public bug:

On booting a nova instance and immediately trying to access the console-
log using nova console-log, an error message reporting an unexpected API
Error is seen in a Mitaka-Stable environment. The Nova API Log is as
follows : http://paste.openstack.org/show/508203/

** Affects: nova
 Importance: Undecided
 Status: Invalid

-- 
Booting Instance and accessing console-log throws nova-api error
https://bugs.launchpad.net/bugs/1589320
You received this bug notification because you are a member of Yahoo! 
Engineering Team, which is subscribed to OpenStack Compute (nova).

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1583763] Re: neutron.tests.functional.agent.linux.test_ovsdb_monitor.TestSimpleInterfaceMonitor.test_get_events reads output sometimes too early

2016-06-05 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/318898
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=de390cdce60f7859f81328a0888df34c47d51d49
Submitter: Jenkins
Branch:master

commit de390cdce60f7859f81328a0888df34c47d51d49
Author: Jakub Libosvar 
Date:   Thu May 19 21:25:10 2016 +0200

functional: Fix ovsdb-monitor waiting for first events

In case ovsdb-monitor is started but hasn't processed output from ovsdb
then stdout buffers are not populated with data yet. This patch waits
for new events that can be buffer after get_events() is called.

Closes-Bug: 1583763
Change-Id: I4f281770844dd262d6ad25bec4b942af36445b18


** Changed in: neutron
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1583763

Title:
  
neutron.tests.functional.agent.linux.test_ovsdb_monitor.TestSimpleInterfaceMonitor.test_get_events
  reads output sometimes too early

Status in neutron:
  Fix Released

Bug description:
  The test expects that stdout buffers are populated right after ovsdb-
  monitor async process is spawned. Sometimes get_events() is called
  before ovsdb output is read that causes following failure:

  http://logs.openstack.org/15/316615/1/check/gate-neutron-dsvm-
  functional/c3be6f8/testr_results.html.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1583763/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1589264] [NEW] developer-api-ref for v2 shows incorrect response style for a GET on images/image_id

2016-06-05 Thread Nikhil Komawar 
Public bug reported:

Matt Riedmann reported on IRC that the developer api reference for a
show call on an image http://developer.openstack.org/api-ref-
image-v2.html#showImage-v2 shows incorrect response.

Specifically, the expected outcome has a flat structure to the response
and the non-base-properties are indicated to be returned as a part of a
nested 'properties' dictionary. That's not correct as those properties
will be returned in the json response in the flat namespace like the
test indicates here
https://github.com/openstack/glance/blob/8dd23d0b9c7ca9bb521f56407f6f601db84771f9/glance/tests/functional/v2/test_images.py#L146

This is a bug specifically only to the api-ref and the work of WADL
transition makes it applicable to Glance and not documentation project.
We should fix this while the docs are being ported glance's tree.

** Affects: glance
 Importance: High
 Assignee: Brian Rosmaita (brian-rosmaita)
 Status: Triaged

** Changed in: glance
   Importance: Undecided => High

** Changed in: glance
   Status: New => Triaged

** Changed in: glance
 Assignee: (unassigned) => Brian Rosmaita (brian-rosmaita)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1589264

Title:
  developer-api-ref for v2 shows incorrect response style for a GET on
  images/image_id

Status in Glance:
  Triaged

Bug description:
  Matt Riedmann reported on IRC that the developer api reference for a
  show call on an image http://developer.openstack.org/api-ref-
  image-v2.html#showImage-v2 shows incorrect response.

  Specifically, the expected outcome has a flat structure to the
  response and the non-base-properties are indicated to be returned as a
  part of a nested 'properties' dictionary. That's not correct as those
  properties will be returned in the json response in the flat namespace
  like the test indicates here
  
https://github.com/openstack/glance/blob/8dd23d0b9c7ca9bb521f56407f6f601db84771f9/glance/tests/functional/v2/test_images.py#L146

  This is a bug specifically only to the api-ref and the work of WADL
  transition makes it applicable to Glance and not documentation
  project. We should fix this while the docs are being ported glance's
  tree.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1589264/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1587021] Re: Log file full of info messages that segments are not supported

2016-06-05 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/322779
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=d5b4436289ff45795f3414e0c6f244146cbeca5f
Submitter: Jenkins
Branch:master

commit d5b4436289ff45795f3414e0c6f244146cbeca5f
Author: Gary Kotton 
Date:   Mon May 30 04:29:54 2016 -0700

Segments: remove log message indicating segments are not supported

Some plugins may not support segment. Each time a agent does a report
there is a log message, which is really pointless, that indicates
that segments are not supported.

This removes that log message.

Change-Id: I67e9031c89ca157679a21f1b09a873ff1842fc45
Closes-bug: #1587021


** Changed in: neutron
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1587021

Title:
  Log file full of info messages that segments are not supported

Status in neutron:
  Fix Released

Bug description:
  The following info messages are in the log file:

  2016-05-30 11:27:46.320 INFO neutron.services.segments.db [req-
  be57cc26-a3ae-4370-aed9-cdb4ed6ccabb None None] Core plug-in does not
  implement 'check_segment_for_agent'. It is not possible to build a
  hosts segments mapping

  In the even that a core plugin does not support this we should not be
  posting this for each update sent by the agent

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1587021/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1588393] Re: Switching OpenFlow interface to 'native' causes network loop

2016-06-05 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/325392
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=09ff5e5ebd2d608c7ac44ccab16d8e108d7181bc
Submitter: Jenkins
Branch:master

commit 09ff5e5ebd2d608c7ac44ccab16d8e108d7181bc
Author: Ilya Chukhnakov 
Date:   Fri Jun 3 18:57:15 2016 +0300

Force "out-of-band" controller connection mode

By default openvswitch uses "in-band" controller connection mode ([1])
which adds hidden OpenFlow rules (only visible by issuing ovs-appctl
bridge/dump-flows ) and leads to a network loop on br-tun when
using native OpenFlow interface. As of now the OF controller is hosted
locally with OVS which fits the "out-of-band" mode. If the remote OF
controller is ever to be supported by openvswitch agent in the future,
"In-Band Control" [1] should be taken into consideration for physical
bridge only, but br-int and br-tun must be configured with the
"out-of-band" controller connection mode.

[1] https://github.com/openvswitch/ovs/blob/master/DESIGN.md

Change-Id: I792a89d37b5d5319cc027835f6a1bfcbe7297ffb
Closes-Bug: #1588393


** Changed in: neutron
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1588393

Title:
  Switching OpenFlow interface to 'native' causes network loop

Status in neutron:
  Fix Released

Bug description:
  * Description:
  After switching openvswitch agent to the 'native' OpenFlow interface 
(of_interface=native) the public network and the tunnel networks are flooded 
with ARP packets (see [1] for the tcpdump sample).

  * Environment:
   - DevStack stable/mitaka
   - 1 controller/compute and 2 compute nodes
   - configuration from [2]
   - ubuntu 14.04

  * How to reproduce:
  0. (WARNING) the following steps will flood the network, so it is recommended 
to use a virtual network as the provider network
  1. Deploy DevStack with access to the provider network (see [2]; 1 controller 
+ 2 compute nodes)
  2. Set of_interface=native in the [ovs] section of 
/etc/neutron/plugins/ml2/ml2_conf.ini
  3. restart l2 agents on all nodes
  4. login to the default gateway and send a broadcast ARP request to the 
devstack's public network (arping -UD )

  * Expected result:
  normal network operation

  * Actual result:
  the public network and the tunnel network are flooded with ARP packets

  [1] http://paste.openstack.org/show/507292/
  [2] 
http://docs.openstack.org/developer/devstack/guides/neutron.html#devstack-configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1588393/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp