from:"Anne Gentle"

[Yahoo-eng-team] [Bug 1672497] Re: Nova - config options - images_type description insufficient

2017-05-13 Thread Anne Gentle

This line can be filled in with a good description:
https://github.com/openstack/nova/blob/ef2203f36fc0bde2635e0d1f39a4b8dce5654ffb/nova/conf/libvirt.py#L635

and here are the choices: 'raw', 'flat', 'qcow2', 'lvm', 'rbd', 'ploop',
'default'.


** Changed in: openstack-manuals
   Status: Incomplete => Confirmed

** Changed in: openstack-manuals
   Status: Confirmed => Opinion

** Changed in: openstack-manuals
   Status: Opinion => Confirmed

** Also affects: nova
   Importance: Undecided
   Status: New

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

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

Title:
  Nova - config options - images_type description insufficient

Status in OpenStack Compute (nova):
  Confirmed
Status in openstack-manuals:
  Confirmed

Bug description:
  The current info looks like this:

  images_type = default
  (String) VM Images format. If default is specified, then use_cow_images flag 
is used instead of this one.

  There is no list of supported values, and no indication which extra
  configuration each of them requires. For example, that images_rbd_*
  options are used when images_type=rbd

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1672497/+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 1538002] Re: incorrect info returned when show aggregate info

2017-04-04 Thread Anne Gentle

** Changed in: python-openstackclient
   Status: In Progress => Invalid

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

Title:
  incorrect info returned when show aggregate info

Status in OpenStack Compute (nova):
  Invalid
Status in python-openstackclient:
  Invalid

Bug description:
  [Summary]
  incorrect info returned when show aggregate info

  [Topo]
  devstack all-in-one node

  [Description and expect result]
  correct info returned when show aggregate info

  [Reproduceable or not]
  reproduceable 

  [Recreate Steps]
  1) create an aggregate, availability_zone is not specified:
  root@45-59:~# openstack aggregate create agg1
  +---++
  | Field | Value  |
  +---++
  | availability_zone | None   |
  | created_at| 2016-01-26T14:23:24.00 |
  | deleted   | False  |
  | deleted_at| None   |
  | id| 6  |
  | name  | agg1   |
  | updated_at| None   |
  +---++
  root@45-59:~# 
  root@45-59:~# 
  root@45-59:~# openstack aggregate list
  ++--+---+
  | ID | Name | Availability Zone |
  ++--+---+
  |  6 | agg1 | None  |  ISSUE, availability_zone is shown as 
"None"
  ++--+---+
  root@45-59:~#

  ISSUE: availability_zone can be shown as "-"

  2)below is nova cmd for reference:
  root@45-59:~# nova aggregate-details agg1
  ++--+---+---+--+
  | Id | Name | Availability Zone | Hosts | Metadata |
  ++--+---+---+--+
  | 6  | agg1 | - |   |  |
  ++--+---+---+--+
  root@45-59:~# 
  root@45-59:~# nova aggregate-list
  ++--+---+
  | Id | Name | Availability Zone |
  ++--+---+
  | 6  | agg1 | - |
  ++--+---+
  root@45-59:~#

  
  [Configration]
  reproduceable bug, no need

  [logs]
  reproduceable bug, no need

  [Root cause anlyze or debug inf]
  reproduceable bug

  [Attachment]
  None

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1538002/+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 1488761] Re: Added processing /compute URL

2017-02-09 Thread Anne Gentle

With the recent work by Sean Dague and others to make endpoints versionless in 
the service catalog, there's nothing to document here I don't believe. The work 
that was done was in multiple projects, such as nova, to eliminate the use of 
versioning on endpoints. This is a summary:
https://www.openstack.org/blog/2015/10/openstack-weekly-community-newsletter-oct-3-oct-9/#dev-digest-service-catalog

Sean Dague is reviving the project by starting work on a service type 
authority, see:
http://lists.openstack.org/pipermail/openstack-dev/2017-January/109758.html

Closing this in openstack-manuals.

** Changed in: openstack-manuals
   Status: Incomplete => Opinion

** No longer affects: openstack-manuals

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

Title:
  Added processing /compute URL

Status in OpenStack Compute (nova):
  Incomplete

Bug description:
  https://review.openstack.org/195303
  commit 434ce2a3a84c9593841b3aa3d4e176ce21293b52
  Author: Marian Horban 
  Date:   Wed Jun 24 07:55:28 2015 -0400

  Added processing /compute URL
  
  After implementing blueprint "Ability to run some Nova services under 
Apache2"(
  
https://blueprints.launchpad.net/nova/+spec/run-nova-services-under-apache2)
  it becomes possible not to use separate ports for each openstack service 
but
  share 80 port with different URL prefixes. Mailing list thread with
  discussion the details of this feature:
  http://lists.openstack.org/pipermail/openstack-dev/2015-June/067147.html.
  Openstack wiki page with mapping urls to services:
  https://wiki.openstack.org/wiki/URLs.
  Function remove_version_from_href was corrected: API version must be 
present
  in the end of SCRIPT_NAME.
  Devstack has been updated here: Ic84b5c0dc0726662470ef9c076a0cadca55a3917
  
  If nova-api service is started by Apache (or similar),
  using 'Alias' directive script name contains alias-prefix.
  We get things like: '/ALIAS/NAME/v2', '/ALIAS/NAME/v2.1'
  
  This change makes sure we remove only the last part of URL,
  to make sure we don't hit problems where ALIAS has a version in it.
  
  DocImpact
  Closes-Bug: #1486447
  Change-Id: I83bc4731507fa028377ae6701ed4d32adefa9251

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1488761/+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 1656403] [NEW] The py-modindex for neutron-dynamic-routing docs is a broken link

2017-01-13 Thread Anne Gentle

Public bug reported:

There's a broken link for the Module Index on
http://docs.openstack.org/developer/neutron-dynamic-routing/.

Also, that doc set has these broken links:


{"url": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/functionality/route-advertisement.rst;,
 "status": 404, "referer": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/functionality/bgp-speaker.html"},
   
{"url": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/others/testing.rst;,
 "status": 404, "referer": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/functionality/bgp-speaker.html"},
   
{"url": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/functionality/dynamic-routing-agent.rst;,
 "status": 404, "referer": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/functionality/bgp-speaker.html"},
   
{"url": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/design/drivers.rst;,
 "status": 404, "referer": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/functionality/bgp-speaker.html"},

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: doc

** Description changed:

  There's a broken link for the Module Index on
  http://docs.openstack.org/developer/neutron-dynamic-routing/.
+ 
+ Also, that doc set has these broken links:
+ 
+ 
+ {"url": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/functionality/route-advertisement.rst;,
 "status": 404, "referer": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/functionality/bgp-speaker.html"},
   
+ {"url": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/others/testing.rst;,
 "status": 404, "referer": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/functionality/bgp-speaker.html"},
   
+ {"url": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/functionality/dynamic-routing-agent.rst;,
 "status": 404, "referer": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/functionality/bgp-speaker.html"},
   
+ {"url": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/design/drivers.rst;,
 "status": 404, "referer": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/functionality/bgp-speaker.html"},

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

Title:
  The py-modindex for neutron-dynamic-routing docs is a broken link

Status in neutron:
  New

Bug description:
  There's a broken link for the Module Index on
  http://docs.openstack.org/developer/neutron-dynamic-routing/.

  Also, that doc set has these broken links:

  
  {"url": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/functionality/route-advertisement.rst;,
 "status": 404, "referer": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/functionality/bgp-speaker.html"},
   
  {"url": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/others/testing.rst;,
 "status": 404, "referer": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/functionality/bgp-speaker.html"},
   
  {"url": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/functionality/dynamic-routing-agent.rst;,
 "status": 404, "referer": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/functionality/bgp-speaker.html"},
   
  {"url": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/design/drivers.rst;,
 "status": 404, "referer": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/functionality/bgp-speaker.html"},

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1656403/+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 1656355] [NEW] The py-modindex for networking-bgpvpn docs is a broken link

2017-01-13 Thread Anne Gentle

Public bug reported:

The Module Index link on this page:

http://docs.openstack.org/developer/networking-bgpvpn/

Is giving a 404 error.

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: bgpvpn doc l3-bgp

** Tags added: doc

** Tags added: bgpvpn l3-bgp

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

Title:
  The py-modindex for networking-bgpvpn docs is a broken link

Status in neutron:
  New

Bug description:
  The Module Index link on this page:

  http://docs.openstack.org/developer/networking-bgpvpn/

  Is giving a 404 error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1656355/+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 1656346] [NEW] Devref has a link to py-modindex that gives a 404 error

2017-01-13 Thread Anne Gentle

Public bug reported:

On this page: http://docs.openstack.org/developer/neutron-
lib/devref/index.html there's a link to py-modindex but it doesn't
exist.

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: doc

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

Title:
  Devref has a link to py-modindex that gives a 404 error

Status in neutron:
  New

Bug description:
  On this page: http://docs.openstack.org/developer/neutron-
  lib/devref/index.html there's a link to py-modindex but it doesn't
  exist.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1656346/+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 1656127] [NEW] 404 error on contributor docs pages

2017-01-12 Thread Anne Gentle

Public bug reported:

Go to
http://docs.openstack.org/developer/neutron/devref/template_model_sync_test.html
and there's a broken link to oslo.db docs for test_migrations,
http://docs.openstack.org/developer/oslo.db/api/sqlalchemy/test_migrations.html.
Other broken links and referring pages include:


{"url": 
"http://docs.openstack.org/newton/networking-guide/scenario_legacy_ovs.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/layer3.html"},
{"url": 
"http://docs.openstack.org/newton/networking-guide/deploy_scenario4b.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/linuxbridge_agent.html"},
{"url": 
"http://docs.openstack.org/newton/networking-guide/deploy_scenario3b.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/linuxbridge_agent.html"},
{"url": 
"http://docs.openstack.org/newton/networking-guide/deploy_scenario1b.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/linuxbridge_agent.html"},
{"url": 
"http://docs.openstack.org/newton/networking-guide/scenario_legacy_lb.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/linuxbridge_agent.html"},

While we're working hard to get redirects in place, better to get the
"real" link in there when you can.

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: doc

** Summary changed:

- 404 error on contributor docs page
+ 404 error on contributor docs pages

** Description changed:

  Go to
  
http://docs.openstack.org/developer/neutron/devref/template_model_sync_test.html
  and there's a broken link to oslo.db docs for test_migrations,
- 
http://docs.openstack.org/developer/oslo.db/api/sqlalchemy/test_migrations.html
+ 
http://docs.openstack.org/developer/oslo.db/api/sqlalchemy/test_migrations.html.
+ Other broken links and referring pages include:
+ 
+ 
+ {"url": 
"http://docs.openstack.org/newton/networking-guide/scenario_legacy_ovs.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/layer3.html"},
+ {"url": 
"http://docs.openstack.org/newton/networking-guide/deploy_scenario4b.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/linuxbridge_agent.html"},
+ {"url": 
"http://docs.openstack.org/newton/networking-guide/deploy_scenario3b.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/linuxbridge_agent.html"},
+ {"url": 
"http://docs.openstack.org/newton/networking-guide/deploy_scenario1b.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/linuxbridge_agent.html"},
+ {"url": 
"http://docs.openstack.org/newton/networking-guide/scenario_legacy_lb.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/linuxbridge_agent.html"},
+ 
+ While we're working hard to get redirects in place, better to get the
+ "real" link in there when you can.

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

Title:
  404 error on contributor docs pages

Status in neutron:
  New

Bug description:
  Go to
  
http://docs.openstack.org/developer/neutron/devref/template_model_sync_test.html
  and there's a broken link to oslo.db docs for test_migrations,
  
http://docs.openstack.org/developer/oslo.db/api/sqlalchemy/test_migrations.html.
  Other broken links and referring pages include:

  
  {"url": 
"http://docs.openstack.org/newton/networking-guide/scenario_legacy_ovs.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/layer3.html"},
  {"url": 
"http://docs.openstack.org/newton/networking-guide/deploy_scenario4b.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/linuxbridge_agent.html"},
  {"url": 
"http://docs.openstack.org/newton/networking-guide/deploy_scenario3b.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/linuxbridge_agent.html"},
  {"url": 
"http://docs.openstack.org/newton/networking-guide/deploy_scenario1b.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/linuxbridge_agent.html"},
  {"url": 
"http://docs.openstack.org/newton/networking-guide/scenario_legacy_lb.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/linuxbridge_agent.html"},

  While we're working hard to get redirects in place, better to get the
  "real" link in there when you can.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1656127/+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 1656124] [NEW] Broken link to nova/devref in http://docs.openstack.org/developer/nova/how_to_get_involved.html#how-to-do-great-nova-spec-reviews

2017-01-12 Thread Anne Gentle

Public bug reported:

Looks like one of the links in
http://docs.openstack.org/developer/nova/how_to_get_involved.html#how-
to-do-great-nova-spec-reviews needs to be updated.

That, or, some redirect is happening so that you can't ever get to a
/devref/ listing. The link is
http://docs.openstack.org/developer/nova/devref/kilo.blueprints.html
#when-is-a-blueprint-needed.

** Affects: nova
 Importance: Undecided
 Status: New


** Tags: doc

** Tags added: doc

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

Title:
  Broken link to nova/devref in
  http://docs.openstack.org/developer/nova/how_to_get_involved.html#how-
  to-do-great-nova-spec-reviews

Status in OpenStack Compute (nova):
  New

Bug description:
  Looks like one of the links in
  http://docs.openstack.org/developer/nova/how_to_get_involved.html#how-
  to-do-great-nova-spec-reviews needs to be updated.

  That, or, some redirect is happening so that you can't ever get to a
  /devref/ listing. The link is
  http://docs.openstack.org/developer/nova/devref/kilo.blueprints.html
  #when-is-a-blueprint-needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1656124/+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 1585100] Re: lbaas-poolmember: subnet is optional according to docs, but actually required

2016-11-01 Thread Anne Gentle

** No longer affects: openstack-api-site

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

Title:
  lbaas-poolmember: subnet is optional according to docs, but actually
  required

Status in neutron:
  Opinion

Bug description:
  I have devstack master with neutron lbaas with octavia.
  And I tried to create poolmember with this Heat template:
  heat_template_version: 2013-05-23

  resources:
port:
  type: OS::Neutron::LBaaS::PoolMember
  properties:
pool: 7abe4251-c643-414a-8776-7346b9c09e71
address: 5.5.5.5
protocol_port: 

  And then I got an error:
  2016-05-24 11:20:26.239 INFO heat.engine.resource 
[req-3734d004-fe1d-4e55-8978-15c9251d5f30 None demo] CREATE: PoolMember "port" 
Stack "test_pool" [0ae40413-9d58-4840-8915-67dbc43f9035]
  2016-05-24 11:20:26.239 TRACE heat.engine.resource Traceback (most recent 
call last):
  2016-05-24 11:20:26.239 TRACE heat.engine.resource   File 
"/opt/stack/heat/heat/engine/resource.py", line 715, in _action_recorder
  2016-05-24 11:20:26.239 TRACE heat.engine.resource yield
  2016-05-24 11:20:26.239 TRACE heat.engine.resource   File 
"/opt/stack/heat/heat/engine/resource.py", line 795, in _do_action
  2016-05-24 11:20:26.239 TRACE heat.engine.resource yield 
self.action_handler_task(action, args=handler_args)
  2016-05-24 11:20:26.239 TRACE heat.engine.resource   File 
"/opt/stack/heat/heat/engine/scheduler.py", line 329, in wrapper
  2016-05-24 11:20:26.239 TRACE heat.engine.resource step = next(subtask)
  2016-05-24 11:20:26.239 TRACE heat.engine.resource   File 
"/opt/stack/heat/heat/engine/resource.py", line 763, in action_handler_task
  2016-05-24 11:20:26.239 TRACE heat.engine.resource done = 
check(handler_data)
  2016-05-24 11:20:26.239 TRACE heat.engine.resource   File 
"/opt/stack/heat/heat/engine/resources/openstack/neutron/lbaas/pool_member.py", 
line 168, in check_create_complete
  2016-05-24 11:20:26.239 TRACE heat.engine.resource self.pool_id, 
{'member': properties})['member']
  2016-05-24 11:20:26.239 TRACE heat.engine.resource   File 
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 
1110, in create_lbaas_member
  2016-05-24 11:20:26.239 TRACE heat.engine.resource return 
self.post(self.lbaas_members_path % lbaas_pool, body=body)
  2016-05-24 11:20:26.239 TRACE heat.engine.resource   File 
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 
347, in post
  2016-05-24 11:20:26.239 TRACE heat.engine.resource headers=headers, 
params=params)
  2016-05-24 11:20:26.239 TRACE heat.engine.resource   File 
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 
282, in do_request
  2016-05-24 11:20:26.239 TRACE heat.engine.resource 
self._handle_fault_response(status_code, replybody, resp)
  2016-05-24 11:20:26.239 TRACE heat.engine.resource   File 
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 
257, in _handle_fault_response
  2016-05-24 11:20:26.239 TRACE heat.engine.resource 
exception_handler_v20(status_code, error_body)
  2016-05-24 11:20:26.239 TRACE heat.engine.resource   File 
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 84, 
in exception_handler_v20
  2016-05-24 11:20:26.239 TRACE heat.engine.resource 
request_ids=request_ids)
  2016-05-24 11:20:26.239 TRACE heat.engine.resource BadRequest: Failed to 
parse request. Required attribute 'subnet_id' not specified
  2016-05-24 11:20:26.239 TRACE heat.engine.resource Neutron server returns 
request_ids: ['req-307da359-cccb-4b57-a9cb-0a29186e62cb']

  I also tried to create poolmember with cli, and got a message that
  subnet is required to create poolmember.

  But according to docs http://developer.openstack.org/api-ref-
  networking-v2-ext.html#createMemberv2 subnet is optional.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1585100/+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 1552056] Re: "router-interface-delete port=xxx" deletes the whole port instead of just removing the interface

2016-11-01 Thread Anne Gentle

** Changed in: openstack-api-site
   Status: Fix Committed => 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/1552056

Title:
  "router-interface-delete port=xxx" deletes the whole port instead of
  just removing the interface

Status in neutron:
  Won't Fix
Status in openstack-api-site:
  Fix Released

Bug description:
  The help message of "neutron router-interface-delete" says

  "Remove an internal network interface from a router."

  =
  Expected behavior
  =
  neutron router-interface-add subnet=subnetx
  --> creates a port, and adds this port as interface to the router

  neutron router-interface-delete subnet=subnetx
  --> removes that interface from the router and deletes the corresponding port

  
  neutron router-interface-add port=portx
  --> adds an already existing port as interface to the router

  neutron router-interface-delete port=portx
  --> removes that interface from the router. Does NOT delete that 
corresponding port

  =
  Actual result
  =

  "neutron router-interface-delete subnet=subnetx" works as expected.

  BUT

  "neutron router-interface-delete port=portx" does not only remove the
  interface from the router, it also deletes the whole port!

  
  =
  Proposed solution
  =

  Either
  #1 Extend the API description to refelct this behavior

  
  Or
  #2 Change the behavior in the special case to NOT delete the port, but only 
remove the interface from the router

  
  ==
  Steps to reproduce
  ==

  # neutron router-interface-delete -h
  usage: neutron router-interface-delete [-h] [--request-format {json}]
 ROUTER INTERFACE

  Remove an internal network interface from a router.

  positional arguments:
ROUTERID or name of the router.
INTERFACE The format is "SUBNET|subnet=SUBNET|port=PORT". Either
  a subnet or port must be specified. Both ID and name
  are accepted as SUBNET or PORT. Note that "subnet="
  can be omitted when specifying a subnet.


  [root@tecs218 ~(keystone_admin)]# neutron router-create test
  Created a new router:
  +---+--+
  | Field | Value|
  +---+--+
  | admin_state_up| True |
  | external_gateway_info |  |
  | id| 4039bd93-b183-4250-af0f-e9739ac1a19a |
  | name  | test |
  | status| ACTIVE   |
  | tenant_id | 0d76aad1dda94f83a2a0a55c04547434 |
  +---+--+
  [root@tecs218 ~(keystone_admin)]# neutron router-interface-add test  
port=90e0abe1-852b-4cfe-afd9-2bd31a42c279
  Added interface 90e0abe1-852b-4cfe-afd9-2bd31a42c279 to router test.
  [root@tecs218 ~(keystone_admin)]# neutron router-interface-add test  
port=90e0abe1-852b-4cfe-afd9-2bd31a42c27^C
  [root@tecs218 ~(keystone_admin)]# neutron port-show 
90e0abe1-852b-4cfe-afd9-2bd31a42c279
  
+-+---+
  | Field   | Value 
|
  
+-+---+
  | admin_state_up  | True  
|
  | bandwidth   | 0 
|
  | binding:host_id |   
|
  | binding:profile | {}
|
  | binding:vif_details | {}
|
  | binding:vif_type| unbound   
|
  | binding:vnic_type   | normal
|
  | bond| 0 
|
  | cbs | 0 
|
  | device_id   | 4039bd93-b183-4250-af0f-e9739ac1a19a  
|
  | device_owner| network:router_interface

[Yahoo-eng-team] [Bug 1636185] Re: Associate Floating IP with server - Improve description

2016-11-01 Thread Anne Gentle

Source files for this document are in the openstack/nova/api-ref repo
location.

** Also affects: nova
   Importance: Undecided
   Status: New

** No longer affects: openstack-api-site

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

Title:
  Associate Floating IP with server - Improve description

Status in OpenStack Compute (nova):
  New

Bug description:
  According to the docs on this link

  http://developer.openstack.org/api-ref/compute/?expanded=add-
  associate-floating-ip-addfloatingip-action-detail#add-associate-
  floating-ip-addfloatingip-action

  the "addFloatingIp" parameter in the request is a string. However,
  after some attempts we figured out the documentation is not correct.
  Turns out this parameter is an object, not a String as described. A
  working example to the request would look something like this:

  body = {
  'addFloatingIp': {
  'address': '172.24.4.5',
  'fixed_address': '10.0.0.10'
  }
  }

  Please fix this parameter on the docs, and also add a working example.
  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1636185/+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 1636180] Re: Error in docs for creating new Floating IP

2016-11-01 Thread Anne Gentle

Source files are in openstack/neutron-lib/api-ref I believe, so moving
but to track with neutron.

** Also affects: neutron
   Importance: Undecided
   Status: New

** No longer affects: openstack-api-site

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

Title:
  Error in docs for creating new Floating IP

Status in neutron:
  New

Bug description:
  According to the docs on this link:

  http://developer.openstack.org/api-
  ref/networking/v2/index.html?expanded=create-floating-ip-detail
  #floating-ips-floatingips

  we should pass an object such as this for creating a new floating IP:

  {
  "floatingip": {
  "floating_network_id": "376da547-b977-4cfe-9cba-275c80debf57"
  }
  }

  But using this object throw us an error. Instead we need to use a much
  simpler object, without the "floatingip" key. It would result in
  something like this:

  body = {"floating_network_id": public_network.id}

  Please fix the API docs to spare anybody else's time.
  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1636180/+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 1585100] Re: lbaas-poolmember: subnet is optional according to docs, but actually required

2016-09-30 Thread Anne Gentle

** Also affects: neutron
   Importance: Undecided
   Status: New

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

Title:
  lbaas-poolmember: subnet is optional according to docs, but actually
  required

Status in neutron:
  New
Status in openstack-api-site:
  New

Bug description:
  I have devstack master with neutron lbaas with octavia.
  And I tried to create poolmember with this Heat template:
  heat_template_version: 2013-05-23

  resources:
port:
  type: OS::Neutron::LBaaS::PoolMember
  properties:
pool: 7abe4251-c643-414a-8776-7346b9c09e71
address: 5.5.5.5
protocol_port: 

  And then I got an error:
  2016-05-24 11:20:26.239 INFO heat.engine.resource 
[req-3734d004-fe1d-4e55-8978-15c9251d5f30 None demo] CREATE: PoolMember "port" 
Stack "test_pool" [0ae40413-9d58-4840-8915-67dbc43f9035]
  2016-05-24 11:20:26.239 TRACE heat.engine.resource Traceback (most recent 
call last):
  2016-05-24 11:20:26.239 TRACE heat.engine.resource   File 
"/opt/stack/heat/heat/engine/resource.py", line 715, in _action_recorder
  2016-05-24 11:20:26.239 TRACE heat.engine.resource yield
  2016-05-24 11:20:26.239 TRACE heat.engine.resource   File 
"/opt/stack/heat/heat/engine/resource.py", line 795, in _do_action
  2016-05-24 11:20:26.239 TRACE heat.engine.resource yield 
self.action_handler_task(action, args=handler_args)
  2016-05-24 11:20:26.239 TRACE heat.engine.resource   File 
"/opt/stack/heat/heat/engine/scheduler.py", line 329, in wrapper
  2016-05-24 11:20:26.239 TRACE heat.engine.resource step = next(subtask)
  2016-05-24 11:20:26.239 TRACE heat.engine.resource   File 
"/opt/stack/heat/heat/engine/resource.py", line 763, in action_handler_task
  2016-05-24 11:20:26.239 TRACE heat.engine.resource done = 
check(handler_data)
  2016-05-24 11:20:26.239 TRACE heat.engine.resource   File 
"/opt/stack/heat/heat/engine/resources/openstack/neutron/lbaas/pool_member.py", 
line 168, in check_create_complete
  2016-05-24 11:20:26.239 TRACE heat.engine.resource self.pool_id, 
{'member': properties})['member']
  2016-05-24 11:20:26.239 TRACE heat.engine.resource   File 
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 
1110, in create_lbaas_member
  2016-05-24 11:20:26.239 TRACE heat.engine.resource return 
self.post(self.lbaas_members_path % lbaas_pool, body=body)
  2016-05-24 11:20:26.239 TRACE heat.engine.resource   File 
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 
347, in post
  2016-05-24 11:20:26.239 TRACE heat.engine.resource headers=headers, 
params=params)
  2016-05-24 11:20:26.239 TRACE heat.engine.resource   File 
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 
282, in do_request
  2016-05-24 11:20:26.239 TRACE heat.engine.resource 
self._handle_fault_response(status_code, replybody, resp)
  2016-05-24 11:20:26.239 TRACE heat.engine.resource   File 
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 
257, in _handle_fault_response
  2016-05-24 11:20:26.239 TRACE heat.engine.resource 
exception_handler_v20(status_code, error_body)
  2016-05-24 11:20:26.239 TRACE heat.engine.resource   File 
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 84, 
in exception_handler_v20
  2016-05-24 11:20:26.239 TRACE heat.engine.resource 
request_ids=request_ids)
  2016-05-24 11:20:26.239 TRACE heat.engine.resource BadRequest: Failed to 
parse request. Required attribute 'subnet_id' not specified
  2016-05-24 11:20:26.239 TRACE heat.engine.resource Neutron server returns 
request_ids: ['req-307da359-cccb-4b57-a9cb-0a29186e62cb']

  I also tried to create poolmember with cli, and got a message that
  subnet is required to create poolmember.

  But according to docs http://developer.openstack.org/api-ref-
  networking-v2-ext.html#createMemberv2 subnet is optional.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1585100/+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 1618883] [NEW] You can only associating a floating IP when the server status is Active, but docs say available

2016-08-31 Thread Anne Gentle

Public bug reported:

In this doc http://developer.openstack.org/api-ref/compute/?expanded
=add-associate-floating-ip-addfloatingip-action-detail

in Preconditions, the text says: 
You can only add a floating IP address to the server when its status is 
available.

It should say

You can only add a floating IP address to the server when its status is
ACTIVE.

Source file and line:
https://github.com/openstack/nova/blob/master/api-ref/source/servers-actions.inc#L52

** Affects: nova
 Importance: Undecided
 Assignee: Anne Gentle (annegentle)
 Status: In Progress


** Tags: api-ref

** Changed in: nova
 Assignee: (unassigned) => Anne Gentle (annegentle)

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

Title:
  You can only associating a floating IP when the server status is
  Active, but docs say available

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  In this doc http://developer.openstack.org/api-ref/compute/?expanded
  =add-associate-floating-ip-addfloatingip-action-detail

  in Preconditions, the text says: 
  You can only add a floating IP address to the server when its status is 
available.

  It should say

  You can only add a floating IP address to the server when its status
  is ACTIVE.

  Source file and line:
  
https://github.com/openstack/nova/blob/master/api-ref/source/servers-actions.inc#L52

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1618883/+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 1605743] Re: Create image default is not public

2016-08-02 Thread Anne Gentle

** Changed in: glance
   Status: In Progress => Invalid

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

Title:
  Create image default is not public

Status in Glance:
  Invalid

Bug description:
  "Image visibility. Valid value is public or private. Default is
  public." located at http://developer.openstack.org/api-ref-
  image-v2.html#createImage-v2

  In practice, this is not accurate.

  2016-07-22 15:23:31,499 DEBUG: keystoneauth.session REQ: curl -g -i -X POST 
http://devstack/v2/images -H "Content-Type: application/json" -H "User-Agent: 
openstacksdk/0.9.1 keystoneauth1/2.6.1 python-requests/2.9.1 CPython/3.4.1+" -H 
"X-Auth-Token: blah" -d '{"disk_format": "ami", "name": "lol", 
"container_format": "ami"}'
  2016-07-22 15:23:31,695 DEBUG: keystoneauth.session RESP: [201] 
X-Openstack-Request-Id: req-7b9b8a11-eb79-418b-9432-a63fdf9f85b2 Content-Type: 
application/json; charset=UTF-8 Content-Length: 545 Location: 
http://devstack/v2/images/543e75f4-5578-41c6-904d-135cfeaa3764 Connection: 
keep-alive Date: Fri, 22 Jul 2016 19:21:47 GMT
  RESP BODY: {"status": "queued", "name": "lol", "tags": [], 
"container_format": "ami", "created_at": "2016-07-22T19:21:47Z", "size": null, 
"disk_format": "ami", "updated_at": "2016-07-22T19:21:47Z", "visibility": 
"private", "self": "/v2/images/543e75f4-5578-41c6-904d-135cfeaa3764", 
"min_disk": 0, "protected": false, "id": 
"543e75f4-5578-41c6-904d-135cfeaa3764", "file": 
"/v2/images/543e75f4-5578-41c6-904d-135cfeaa3764/file", "checksum": null, 
"owner": "cb802e549b374492b884fdee89e8727b", "virtual_size": null, "min_ram": 
0, "schema": "/v2/schemas/image"}

  "visibility": "private" comes back in the response body

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1605743/+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 1605743] Re: Create image default is not public

2016-07-29 Thread Anne Gentle

** Also affects: glance
   Importance: Undecided
   Status: New

** No longer affects: openstack-api-site

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

Title:
  Create image default is not public

Status in Glance:
  New

Bug description:
  "Image visibility. Valid value is public or private. Default is
  public." located at http://developer.openstack.org/api-ref-
  image-v2.html#createImage-v2

  In practice, this is not accurate.

  2016-07-22 15:23:31,499 DEBUG: keystoneauth.session REQ: curl -g -i -X POST 
http://devstack/v2/images -H "Content-Type: application/json" -H "User-Agent: 
openstacksdk/0.9.1 keystoneauth1/2.6.1 python-requests/2.9.1 CPython/3.4.1+" -H 
"X-Auth-Token: blah" -d '{"disk_format": "ami", "name": "lol", 
"container_format": "ami"}'
  2016-07-22 15:23:31,695 DEBUG: keystoneauth.session RESP: [201] 
X-Openstack-Request-Id: req-7b9b8a11-eb79-418b-9432-a63fdf9f85b2 Content-Type: 
application/json; charset=UTF-8 Content-Length: 545 Location: 
http://devstack/v2/images/543e75f4-5578-41c6-904d-135cfeaa3764 Connection: 
keep-alive Date: Fri, 22 Jul 2016 19:21:47 GMT
  RESP BODY: {"status": "queued", "name": "lol", "tags": [], 
"container_format": "ami", "created_at": "2016-07-22T19:21:47Z", "size": null, 
"disk_format": "ami", "updated_at": "2016-07-22T19:21:47Z", "visibility": 
"private", "self": "/v2/images/543e75f4-5578-41c6-904d-135cfeaa3764", 
"min_disk": 0, "protected": false, "id": 
"543e75f4-5578-41c6-904d-135cfeaa3764", "file": 
"/v2/images/543e75f4-5578-41c6-904d-135cfeaa3764/file", "checksum": null, 
"owner": "cb802e549b374492b884fdee89e8727b", "virtual_size": null, "min_ram": 
0, "schema": "/v2/schemas/image"}

  "visibility": "private" comes back in the response body

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1605743/+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 1488761] Re: Added processing /compute URL

2016-06-17 Thread Anne Gentle

** Also affects: nova
   Importance: Undecided
   Status: 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/1488761

Title:
  Added processing /compute URL

Status in OpenStack Compute (nova):
  New
Status in openstack-manuals:
  Confirmed

Bug description:
  https://review.openstack.org/195303
  commit 434ce2a3a84c9593841b3aa3d4e176ce21293b52
  Author: Marian Horban 
  Date:   Wed Jun 24 07:55:28 2015 -0400

  Added processing /compute URL
  
  After implementing blueprint "Ability to run some Nova services under 
Apache2"(
  
https://blueprints.launchpad.net/nova/+spec/run-nova-services-under-apache2)
  it becomes possible not to use separate ports for each openstack service 
but
  share 80 port with different URL prefixes. Mailing list thread with
  discussion the details of this feature:
  http://lists.openstack.org/pipermail/openstack-dev/2015-June/067147.html.
  Openstack wiki page with mapping urls to services:
  https://wiki.openstack.org/wiki/URLs.
  Function remove_version_from_href was corrected: API version must be 
present
  in the end of SCRIPT_NAME.
  Devstack has been updated here: Ic84b5c0dc0726662470ef9c076a0cadca55a3917
  
  If nova-api service is started by Apache (or similar),
  using 'Alias' directive script name contains alias-prefix.
  We get things like: '/ALIAS/NAME/v2', '/ALIAS/NAME/v2.1'
  
  This change makes sure we remove only the last part of URL,
  to make sure we don't hit problems where ALIAS has a version in it.
  
  DocImpact
  Closes-Bug: #1486447
  Change-Id: I83bc4731507fa028377ae6701ed4d32adefa9251

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1488761/+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 1214576] Re: V3 Identity API: No documented reason not to fallback to a domain token

2016-03-09 Thread Anne Gentle

This also makes sense to go into the Cloud Admin Guide in the openstack-
manuals repo.

** Also affects: openstack-manuals
   Importance: Undecided
   Status: New

** No longer affects: keystone

** Changed in: openstack-manuals
   Status: New => Triaged

** Changed in: openstack-manuals
   Importance: Undecided => Medium

** Changed in: openstack-manuals
 Assignee: (unassigned) => Dolph Mathews (dolph)

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

Title:
  V3 Identity API: No documented reason not to fallback to a domain
  token

Status in openstack-manuals:
  Triaged

Bug description:
  (Continuing my cleanup of bugs to differentiate the root cause from a
  proposed solution)

  The V3 Identity API does not document a reason why we don't return a
  domain token, when we currently fallback to returning an unscoped
  token.

  This causes confusion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-manuals/+bug/1214576/+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 1214576] Re: V3 Identity API: No documented reason not to fallback to a domain token

2016-03-09 Thread Anne Gentle

I think this level of conceptual info belongs in the keystone-specs API
documents: http://specs.openstack.org/openstack/keystone-specs/

** No longer affects: openstack-api-site

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

Title:
  V3 Identity API: No documented reason not to fallback to a domain
  token

Status in openstack-manuals:
  Triaged

Bug description:
  (Continuing my cleanup of bugs to differentiate the root cause from a
  proposed solution)

  The V3 Identity API does not document a reason why we don't return a
  domain token, when we currently fallback to returning an unscoped
  token.

  This causes confusion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-manuals/+bug/1214576/+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 1214576] Re: V3 Identity API: No documented reason not to fallback to a domain token

2016-03-09 Thread Anne Gentle

** Also 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/1214576

Title:
  V3 Identity API: No documented reason not to fallback to a domain
  token

Status in OpenStack Identity (keystone):
  New

Bug description:
  (Continuing my cleanup of bugs to differentiate the root cause from a
  proposed solution)

  The V3 Identity API does not document a reason why we don't return a
  domain token, when we currently fallback to returning an unscoped
  token.

  This causes confusion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1214576/+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 1553152] Re: misleading API documentation for block_device_mapping_v2

2016-03-04 Thread Anne Gentle

Adding openstack-api-site as the openstack/api-site repo is where this
type of info should go. It's the source for
http://developer.openstack.org/api-ref-compute-v2.1.html#createServer.

Here's the file to add the JSON schema info, parameter by parameter I
believe:

https://github.com/openstack/api-site/blob/master/api-ref/src/wadls
/compute-api/src/v2.1/wadl/servers-v2.1.wadl

** Also affects: openstack-api-site
   Importance: Undecided
   Status: 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/1553152

Title:
  misleading API documentation for block_device_mapping_v2

Status in OpenStack Compute (nova):
  Confirmed
Status in openstack-api-site:
  New

Bug description:
  Documentation [1] about `block_device_mapping_v2` when creating a
  server instance is misleading as it doesn't explain that it must
  actually be an array of mappings and there is no complete list of the
  supported keys. For example `volume_size` and `uuid` are not even
  mentioned.

  Thanks to an unrelated github bug [2] I figured it's something like this:
  "block_device_mapping_v2": [
{
  "boot_index": "0",
  "uuid": "ac408821-c95a-448f-9292-73986c790911",
  "source_type": "image",
  "volume_size": "25",
  "destination_type": "volume",
  "delete_on_termination": true
}

  The above example is something that very quickly gets you to the
  point. In block_device_mapping.rst doc I see some of the things
  explained but first I could only find that doc grepping nova's sources
  and I still couldn't figure from that doc how in hell should I
  construct my API call.

  What I wanted to do is to basically launch an instance off a new
  custom sized volume. That turned out very easy and conscious
  eventually but finding that out took hours for me as I'm simply an API
  user and I have no experience whatsoever installing, configuring, even
  less hacking on OpenStack.

  P.S. I'm using a similar feature in GCE. They have it even nicer. When
  you specify the instance disks, it supports any options that are
  supported by the api call creating a standalone disk. I guess values
  are then passed to the disk api as is. Might be worth considering for
  a future API version. e.g. at the moment I can't specify a name for
  the new volume or many of the other options supported by the OS
  volumes API.

  [1] http://developer.openstack.org/api-ref-compute-v2.1.html#createServer
  [2] 
https://github.com/ggiamarchi/vagrant-openstack-provider/issues/209#issuecomment-73961050

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1553152/+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 1545922] Re: Nova API allow DB index as the server_id parem

2016-02-17 Thread Anne Gentle

We need the EC2 API devs to let us know if this is required before
documenting this capability, as it may be removed.

** Changed in: openstack-api-site
   Importance: Undecided => Medium

** Also affects: nova
   Importance: Undecided
   Status: 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/1545922

Title:
  Nova API allow DB index as the server_id parem

Status in OpenStack Compute (nova):
  New
Status in openstack-api-site:
  New

Bug description:
  I read the nova API doc: 
  such as this API: 
  http://developer.openstack.org/api-ref-compute-v2.1.html#showServer

  GET /v2.1/{tenant_id}/servers/{server_id}Show server details

  
  Request parameters
  Parameter Style   TypeDescription
  tenant_id URI csapi:UUID  
  The UUID of the tenant in a multi-tenancy cloud.

  server_id URI csapi:UUID  
  The UUID of the server.

  
  But I can get the server by DB index: 

  curl -s -H X-Auth-Token:6b8968eb38df47c6a09ac9aee81ea0c6 
http://192.168.2.103:8774/v2.1/f5a8829cc14c4825a2728b273aa91aa1/servers/2
  {
  "server": {
  "OS-DCF:diskConfig": "MANUAL",
  "OS-EXT-AZ:availability_zone": "nova",
  "OS-EXT-SRV-ATTR:host": "shaohe1",
  "OS-EXT-SRV-ATTR:hypervisor_hostname": "shaohe1",
  "OS-EXT-SRV-ATTR:instance_name": "instance-0002",
  "OS-EXT-STS:power_state": 1,
  "OS-EXT-STS:task_state": "migrating",
  "OS-EXT-STS:vm_state": "error",
  "OS-SRV-USG:launched_at": "2015-12-18T07:41:00.00",
  "OS-SRV-USG:terminated_at": null,
  ..
  }
  }

  and the code really allow it use  DB index
  https://github.com/openstack/nova/blob/master/nova/compute/api.py#L1939

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1545922/+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 1543169] Re: Nova os-volume-types endpoint doesn't exist

2016-02-10 Thread Anne Gentle

** Also affects: nova
   Importance: Undecided
   Status: New

** Changed in: openstack-api-site
   Status: In Progress => Confirmed

** Changed in: openstack-api-site
 Assignee: Anne Gentle (annegentle) => (unassigned)

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

Title:
  Nova os-volume-types endpoint doesn't exist

Status in OpenStack Compute (nova):
  New
Status in openstack-api-site:
  Confirmed

Bug description:
  The Nova v2.1 documentation shows an endpoint "os-volume-types" which
  lists the available volume types. http://developer.openstack.org/api-
  ref-compute-v2.1.html#listVolumeTypes

  I am using OpenStack Liberty and that endpoint doesn't appear to exist
  anymore. GET requests sent to /v2.1/{tenant_id}/os-volume-types
  return 404 not found. When I searched the Nova codebase on GitHub, I
  could only find a reference to volume types in the policy.json but not
  implemented anywhere.

  Does this endpoint still exist, and if so what is the appropriate
  documentation?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1543169/+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 1490059] Re: Add Geneve type driver support to ML2

2015-09-21 Thread Anne Gentle

There aren't API docs to be updated so make sure that this gets in the
release notes.

** Also affects: neutron
   Importance: Undecided
   Status: New

** No longer affects: openstack-api-site

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

Title:
  Add Geneve type driver support to ML2

Status in neutron:
  New

Bug description:
  https://review.openstack.org/187945
  commit 7b7c15ba4e2f0646000ecca2acecb98081268772
  Author: Aaron Rosen 
  Date:   Tue May 5 14:35:08 2015 -0700

  Add Geneve type driver support to ML2
  
  More information about Geneve protocol can be found here:
https://tools.ietf.org/pdf/draft-gross-geneve-02.pdf
  
  Following configuration variables were added:
  [ml2_type_geneve]
vni_ranges - Comma-separated list of : tuples
 enumerating ranges of Geneve VNI IDs that are
 available for tenant network allocation
max_header_size - Geneve encapsulation header size is dynamic, this
  value is used to calculate the maximum MTU for the 
driver
  this is the sum of the sizes of the outer
  ETH + IP + UDP + GENEVE header sizes
  
  DocImpact
  
  Change-Id: I8c29a1c1a7c79e02c26ac9e2ad2645d30dfbeefc
  Closes-Bug: #1461069

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1490059/+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 1415336] Re: type: parameter should be replaced by healthmonitor_type in loadbalancer

2015-02-21 Thread Anne Gentle

The page you've linked to in this bug report is no longer updated.  Can
you review https://review.openstack.org/#/c/148687/ to see if this has
been addressed in the updated documentation?

** Also affects: openstack-api-site
   Importance: Undecided
   Status: New

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

Title:
  type: parameter should be replaced by healthmonitor_type in
  loadbalancer

Status in OpenStack Neutron (virtual network service):
  New
Status in OpenStack API documentation site:
  New
Status in Python client library for Neutron:
  New

Bug description:
  As per V2 API specification load balancer healthmonitor has a parameter 
type which can not be parsed by JSON parser. 
  So, it must be replaced by healthmonitor_type as per the OpenDayLight Bug- 
( https://bugs.opendaylight.org/show_bug.cgi?id=1674 )

  Further information related to lbaas healthmonitor can be found here: 
  
http://docs.openstack.org/api/openstack-network/2.0/content/POST_createHealthMonitor__v2.0_healthmonitors_lbaas_ext_ops_health_monitor.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1415336/+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 1406320] [NEW] Template for openrc file mentions Compute 1.1 API which confuses users

2014-12-29 Thread Anne Gentle

Public bug reported:

Users looking at the openrc file for help with auth are confused by this
note:

NOTE: Using the 2.0 auth api does not mean that compute api is 2.0. We
will use the 1.1 compute api
export OS_AUTH_URL=http://MYIP:5000/v2.0


Example at https://github.com/pkgcloud/pkgcloud/issues/378

** Affects: horizon
 Importance: Undecided
 Assignee: Anne Gentle (annegentle)
 Status: Confirmed

** Changed in: horizon
   Status: New = Confirmed

** Changed in: horizon
 Assignee: (unassigned) = Anne Gentle (annegentle)

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

Title:
  Template for openrc file mentions Compute 1.1 API which confuses users

Status in OpenStack Dashboard (Horizon):
  Confirmed

Bug description:
  Users looking at the openrc file for help with auth are confused by
  this note:

  NOTE: Using the 2.0 auth api does not mean that compute api is 2.0. We
  will use the 1.1 compute api
  export OS_AUTH_URL=http://MYIP:5000/v2.0

  
  Example at https://github.com/pkgcloud/pkgcloud/issues/378

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1406320/+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 1370477] Re: response examples of lists role APIs are lacking

2014-12-17 Thread Anne Gentle

Where do you see these response examples? That will help us know where
to fix.

** Also affects: keystone
   Importance: Undecided
   Status: New

** Changed in: openstack-api-site
   Status: New = Incomplete

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

Title:
  response examples of lists role APIs are lacking

Status in OpenStack Identity (Keystone):
  New
Status in OpenStack API documentation site:
  Incomplete

Bug description:
  Some listing roles APIs of responce examples are lacking.

  For example:
  Lists role for a user on a domain API's example is 

  [
  {
  id: --role-id--,
  name: --role-name--
  },
  {
  id: --role-id--,
  name: --role-name--
  }
  ]

  but the actual API's response is 
  {
  links: {
  next: null, 
  previous: null, 
  self: 
http://192.168.56.10:5000/v3/domains/716d729b22d647e5a04a2405d66c5eff/users/21de7aaafeb9454ba4c5b40b19016199/roles;
  }, 
  roles: [
  {
  id: 3d4b58f4be7649a497bb18b3f2e25d76, 
  links: {
  self: 
http://192.168.56.10:5000/v3/roles/3d4b58f4be7649a497bb18b3f2e25d76;
  }, 
  name: Member
  }
  ]
  }

  
  Same lacks exist in 
  - Lists roles for a user on a domain. 
  - Lists roles for a specified domain group. 
  - Lists roles for a user in a project.
  - Lists roles for a project group. 
  - Lists roles.
  - Lists policies.

  These API's response examples don't have roles, links, next,
  previous and self keys.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1370477/+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 1272522] Re: Chapter 1. General API Information doesn't document layout of Service Catalog

2014-12-15 Thread Anne Gentle

Also, the API Working Group is collecting example catalogs here:

https://wiki.openstack.org/wiki/API_Working_Group/Current_Design/Service_Catalog

** Project changed: openstack-api-site = keystone

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

Title:
  Chapter 1. General API Information doesn't document layout of Service
  Catalog

Status in OpenStack Identity (Keystone):
  Confirmed

Bug description:
  On page http://docs.openstack.org/api/openstack-identity-
  service/2.0/content/POST_authenticate_v2.0_tokens_.html, the example
  service catalog includes a field named endpoints_links.  How this
  field differs from just regular endpoints remains uncertain.  This
  got me thinking, while the Basic Concepts section does a decent job
  for what it is, it completely skips over the Service Catalog, which is
  a pretty significant and core feature of the Identity service.

  This structure, including references to relevant extensions that may
  tweak it (perhaps in the form of See Also references), should be
  documented, I think.

  Thanks.

  ---
  Built: 2014-01-22T21:30:15 00:00
  git SHA: df9abd1c01f09f3b2c2a514b3bc2c188d8af5bba
  URL: 
http://docs.openstack.org/api/openstack-identity-service/2.0/content/Overview-Identity-Service-API-d1e62.html
  source File: 
file:/home/jenkins/workspace/identity-api-v2.0/openstack-identity-api/v2.0/src/docbkx/common/identity-general-api-info.xml
  xml:id: Overview-Identity-Service-API-d1e62

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1272522/+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 1396781] Re: Error in Database Population script for Neutron

2014-11-29 Thread Anne Gentle

Okay Gary, this is documented as it should be in the Juno guide.
Typically we won't keep the trunk version of the guide updated as most
people are installing a stable version. Matt has done lots of installs
and can help you troubleshoot.

** No longer affects: neutron

** Changed in: openstack-manuals
   Status: Incomplete = Won't Fix

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

Title:
  Error in Database Population script for Neutron

Status in OpenStack Manuals:
  Won't Fix

Bug description:
  In the 'to finalise installation' section the following script is used

   su -s /bin/sh -c neutron-db-manage --config-file /etc/neutron/neutron.conf \
--config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade juno neutron

  This reports an error as juno is unknown, to resolve this the script
  should be changed to

   su -s /bin/sh -c neutron-db-manage --config-file /etc/neutron/neutron.conf \
--config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head neutron

  An explanation should be added saying that 'head' is equivalent to the
  latest trunk release.

  ---
  Built: 2014-11-26T19:02:57 00:00
  git SHA: 5595fde364e55699d2bf5e7b0aabdf9cdd154f00
  URL: 
http://docs.openstack.org/juno/install-guide/install/apt/content/neutron-controller-node.html
  source File: 
file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/install-guide/section_neutron-controller-node.xml
  xml:id: neutron-controller-node

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-manuals/+bug/1396781/+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 1396781] Re: Error in Database Population script for Neutron

2014-11-26 Thread Anne Gentle

Also isn't this a bug for neutron?

** Also affects: neutron
   Importance: Undecided
   Status: New

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

Title:
  Error in Database Population script for Neutron

Status in OpenStack Neutron (virtual network service):
  New
Status in OpenStack Manuals:
  New

Bug description:
  In the 'to finalise installation' section the following script is used

   su -s /bin/sh -c neutron-db-manage --config-file /etc/neutron/neutron.conf \
--config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade juno neutron

  This reports an error as juno is unknown, to resolve this the script
  should be changed to

   su -s /bin/sh -c neutron-db-manage --config-file /etc/neutron/neutron.conf \
--config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head neutron

  An explanation should be added saying that 'head' is equivalent to the
  latest trunk release.

  ---
  Built: 2014-11-26T19:02:57 00:00
  git SHA: 5595fde364e55699d2bf5e7b0aabdf9cdd154f00
  URL: 
http://docs.openstack.org/juno/install-guide/install/apt/content/neutron-controller-node.html
  source File: 
file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/install-guide/section_neutron-controller-node.xml
  xml:id: neutron-controller-node

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1396781/+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 1393920] Re: I18n

2014-11-18 Thread Anne Gentle

** Also affects: keystone
   Importance: Undecided
   Status: New

** No longer affects: openstack-manuals

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

Title:
  I18n

Status in OpenStack Identity (Keystone):
  New

Bug description:
  https://review.openstack.org/131287

  Dear documentation bug triager. This bug was created here because we
  did not know how to map the project name
  openstack/keystonemiddleware to a launchpad project name. This
  indicates that the notify_impact config needs tweaks. You can ask the
  OpenStack infra team (#openstack-infra on freenode) for help if you
  need to.

  commit 273539bf26a7848a8e49e3ec60b12d2964daca67
  Author: Brant Knudson bknud...@us.ibm.com
  Date:   Mon Oct 27 16:46:04 2014 -0500

  I18n
  
  The strings weren't marked for translation.
  
  DocImpact
  
  implements bp keystonemiddleware-i18n
  
  Change-Id: Ic7da29b54b1547ff8df002bd77f61f2ebff35217

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1393920/+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 1373337] Re: Updating quotas path issue

2014-11-06 Thread Anne Gentle

** Changed in: openstack-manuals
   Status: New = Confirmed

** Also affects: openstack-api-site
   Importance: Undecided
   Status: New

** No longer affects: openstack-manuals

** Changed in: openstack-api-site
   Status: New = Confirmed

** Changed in: openstack-api-site
   Importance: Undecided = Medium

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

Title:
  Updating quotas path issue

Status in OpenStack Neutron (virtual network service):
  Incomplete
Status in OpenStack API documentation site:
  Confirmed

Bug description:
  In the docs (http://developer.openstack.org/api-ref-networking-v2.html
  #quotas-ext), it clearly says that to update quota values, the request
  should be:

  PUT /v2.0/quotas

  But I'm getting a 404 when you do this. If you do this instead:

  PUT /v2.0/quotas/foo

  it works as expected, where foo can literally be anything. I looked
  at how the python-neutronclient handles this, and they seem to append
  the tenant_id to the end - which is completely undocumented. So:

  1. Is this a bug with the Neutron API or with the Neutron docs?
  2. Why does any arbitrary string get accepted?

  I'm using Neutron on devstack, Icehouse release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1373337/+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 1373832] Re: The source group of security group does not work

2014-11-06 Thread Anne Gentle

The source for  http://docs.openstack.org/developer/nova lives in the
nova repo.

** No longer affects: openstack-manuals

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

Title:
  The source group of security group does not work

Status in OpenStack Compute (Nova):
  Incomplete

Bug description:
  I created a security group with the other security group as the source
  group, and booted a server with the security group:

  $ nova secgroup-create source-any secgroup for any sources 
  $ nova secgroup-add-rule source-any tcp 1 65535 0.0.0.0/0
  $
  $ nova secgroup-create accept-ssh secgroup for ssh 
  $ nova secgroup-add-group-rule accept-ssh source-any tcp 22 22
  $
  $ nova boot --flavor m1.nano --security-groups accept-ssh --image 
cirros-0.3.2-x86_64-uec vm01

  but I could not access the server with SSH.

  According to 
http://docs.openstack.org/developer/nova/nova.concepts.html#concept-security-groups
 , the source group is
  considered as CIDR of acceptable source addresses and we can reuse it for new 
security groups.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1373832/+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 1335392] Re: [securitygroup] not recognized in ml2_conf.ini

2014-09-04 Thread Anne Gentle

** 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/1335392

Title:
  [securitygroup] not recognized in ml2_conf.ini

Status in OpenStack Neutron (virtual network service):
  Invalid
Status in OpenStack Manuals:
  Invalid

Bug description:
  The [securitygruop] section of configuration file
  /etc/neutron/plugins/ml2/ml2_conf.ini should be actually named
  [SECURITYGROUP] (in capital letters).

  If you configure the file as indicated (i.e. with the section name in
  small letters), the plug in does not work properly and the result is
  that the instances cannot reach the metadata server.

  I discovered this subtle bug by reverse engineering the file produced
  by devstack.

  ---
  Built: 2014-06-20T10:03:51 00:00
  git SHA: cf40d505946951121468a170753d83905d8bdb55
  URL: 
http://docs.openstack.org/icehouse/install-guide/install/apt/content/neutron-ml2-controller-node.html
  source File: 
file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/install-guide/section_neutron-ml2-controller-node.xml
  xml:id: neutron-ml2-controller-node

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1335392/+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 1285482] Re: There is not any API sample file for unshelve a server API

2014-06-18 Thread Anne Gentle

fixed: http://developer.openstack.org/api-ref-compute-v2-ext.html#ext-
os-shelve

** Changed in: openstack-api-site
 Assignee: (unassigned) = Anne Gentle (annegentle)

** Changed in: openstack-api-site
   Status: Triaged = Fix Released

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

Title:
  There is not any API sample file for unshelve a server API

Status in OpenStack Compute (Nova):
  Fix Released
Status in OpenStack API documentation site:
  Fix Released

Bug description:
  Now there is not any API sample file of unshelve a server API,
  and OpenStack API documentation[1] also does not describe the API.

  [1]: http://api.openstack.org/api-ref-compute-ext.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1285482/+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 1222682] Re: Live Migration does not work unless cache=none

2014-03-31 Thread Anne Gentle

The code itself is abandoned. The referring URLs are grizzly. Marking as
won't fix.

** Changed in: openstack-manuals
   Status: Triaged = Won't Fix

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

Title:
  Live Migration does not work unless cache=none

Status in OpenStack Compute (Nova):
  In Progress
Status in OpenStack Manuals:
  Won't Fix

Bug description:
  If O_DIRECT is not supported, 'cache=none' is not set. Thus, Live
  Migration gives the following error:

  Live Migration failure: Unsafe migration: Migration may lead to data
  corruption if disks use cache != none

  However, it is ok to migrate if the storage is coherent across
  nodes. So Nova's live-migration should support the Libvirt's
  unsafe=True flag.

  Ideally there should be a nova flag which can be set to pass through
  the libvirt 'unsafe=true' flag. My thinking is that if
  'cache=writethrough' is set then the underlying storage should be
  safe, but perhaps it's best not to make that assumption and rather to
  have a nova.conf flag.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1222682/+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 1256952] Re: Many api configuration options appear undocumented

2013-12-06 Thread Anne Gentle

Is there any way to automate the docs for settings in glance-api.conf?

** Also affects: openstack-manuals
   Importance: Undecided
   Status: New

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

Title:
  Many api configuration options appear undocumented

Status in OpenStack Image Registry and Delivery Service (Glance):
  New
Status in OpenStack Manuals:
  New

Bug description:
  I don't see documentation for options marked with a '':

  CONF.import_opt('registry_client_protocol', _registry_client)
  CONF.import_opt('registry_client_key_file', _registry_client)
  CONF.import_opt('registry_client_cert_file', _registry_client)
  CONF.import_opt('registry_client_ca_file', _registry_client)
  CONF.import_opt('registry_client_insecure', _registry_client)
  CONF.import_opt('registry_client_timeout', _registry_client)
  CONF.import_opt('use_user_token', _registry_client) 
  CONF.import_opt('admin_user', _registry_client)  
  CONF.import_opt('admin_password', _registry_client)  
  CONF.import_opt('admin_tenant_name', _registry_client)  
  CONF.import_opt('auth_url', _registry_client)  
  CONF.import_opt('auth_strategy', _registry_client)  
  CONF.import_opt('auth_region', _registry_client) 
  CONF.import_opt('metadata_encryption_key', 'glance.common.config')

  The other options seemed to be documented
  (http://docs.openstack.org/developer/glance/configuring.html)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1256952/+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 1230270] Re: Install guide has compute v1.1 in an endpoint

2013-10-30 Thread Anne Gentle

** Changed in: openstack-manuals
   Status: Confirmed = Fix Released

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

Title:
  Install guide has compute v1.1 in an endpoint

Status in OpenStack Identity (Keystone):
  Fix Committed
Status in OpenStack Manuals:
  Fix Released

Bug description:
  Reported at http://docs.openstack.org/grizzly/openstack-
  compute/install/yum/content/compute-create-
  network.html#comment-1056259358

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1230270/+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

38 matches

Mail list logo