[Yahoo-eng-team] [Bug 1645306] [NEW] typo in api-paste.ini parameter
Public bug reported: Following line uses "olso_config_project" https://github.com/openstack/nova/blame/f57cc519fde2f177920ce88b8a3ef0618d1419b0/nova/api/openstack/placement/deploy.py#L42 it should be oslo_config_project https://github.com/openstack/nova/blob/f57cc519fde2f177920ce88b8a3ef0618d1419b0/etc/nova/api-paste.ini#L75 ** Affects: nova Importance: Undecided Assignee: Atsushi SAKAI (sakaia) Status: New ** Changed in: nova Assignee: (unassigned) => Atsushi SAKAI (sakaia) -- 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/1645306 Title: typo in api-paste.ini parameter Status in OpenStack Compute (nova): New Bug description: Following line uses "olso_config_project" https://github.com/openstack/nova/blame/f57cc519fde2f177920ce88b8a3ef0618d1419b0/nova/api/openstack/placement/deploy.py#L42 it should be oslo_config_project https://github.com/openstack/nova/blob/f57cc519fde2f177920ce88b8a3ef0618d1419b0/etc/nova/api-paste.ini#L75 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1645306/+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 1606381] Re: API-REF LBaaS v2 API version mixed with LBaaS v1 API
API-Ref issue ** Project changed: openstack-manuals => neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1606381 Title: API-REF LBaaS v2 API version mixed with LBaaS v1 API Status in neutron: New Bug description: Somehow the LBaaS v2 API docs got merged/mixed with the LBaaS v1 API docs. Previously there were two sections, one for the deprecated LBaaSv1 API and one for the LBaaSv2 API. http://developer.openstack.org/api-ref/networking/v2-ext/index.html#lbaas-1-0-deprecated-lb-vips-health-monitors-pools-members To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1606381/+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 1602113] [NEW] Needs to point Image Service API documention
Public bug reported: Need to point the API documentation. or describe in api-ref itself. Image metadata is updated by passing HTTP headers prefixed with one of the strings x-image-meta- or x-image-meta-property-. See the API documentation for details. http://developer.openstack.org/api-ref/image/v1/index.html?expanded=update-image-detail#update-image ** Affects: glance 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/1602113 Title: Needs to point Image Service API documention Status in Glance: New Bug description: Need to point the API documentation. or describe in api-ref itself. Image metadata is updated by passing HTTP headers prefixed with one of the strings x-image-meta- or x-image-meta-property-. See the API documentation for details. http://developer.openstack.org/api-ref/image/v1/index.html?expanded=update-image-detail#update-image To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1602113/+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 1587847] Re: flavorRef is missing from the parameter list of Resize server
This is api-ref for nova issue. ** Project changed: openstack-api-site => nova -- 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/1587847 Title: flavorRef is missing from the parameter list of Resize server Status in OpenStack Compute (nova): New Bug description: According to the example Change administrative password has a parameter called "flavorRef". This "flavorRef" parameter is not listed in the Parameter list of Change administrative password in the web API reference [1] and not mentioned in Chapter 4.4.20 of the pdf API reference [2]. [1]: http://developer.openstack.org/api-ref-compute-v2.1.html#changePassword [2]: http://api.openstack.org/api-ref-guides/bk-api-ref.pdf To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1587847/+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 1486127] Re: Support RBAC neutron-client changes.
** Project changed: openstack-api-site => neutron ** Tags added: api-ref -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1486127 Title: Support RBAC neutron-client changes. Status in neutron: Confirmed Bug description: https://review.openstack.org/205482 commit 22c84927d133158c9de429ba1b9dbcd1d077d773 Author: Ramanjaneya Date: Fri Jul 24 15:51:53 2015 +0530 Support RBAC neutron-client changes. This patch adds the command line support for RBAC work. DocImpact APIImpact Partially-Implements: blueprint rbac-networks Co-Authored-By: dongfeng Change-Id: I00c6b84b3f7d810f137ce05c0cd936dc194d9708 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1486127/+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 1481600] Re: Remove Catalog Index Service
** Project changed: openstack-api-site => glance ** Tags added: api-ref -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1481600 Title: Remove Catalog Index Service Status in Glance: Triaged Bug description: https://review.openstack.org/197043 commit feb927c8a11813c2cd4fbb73b2561a73e281f1aa Author: Louis Taylor Date: Tue Jun 30 12:19:34 2015 + Remove Catalog Index Service The Catalog Index Service added in the kilo cycle has been split into a new project named searchlight. This code now lives in a seperate repository: https://git.openstack.org/openstack/searchlight For more information about the split, see the governance change: I8b44aac03585c651ef8d5e94624f64a0ed2d10b2 DocImpact UpgradeImpact APIImpact Change-Id: I239ac9e32857f6a728f40c169e773ee977cca3ca To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1481600/+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 1408112] Re: Update documentation for port does not show how to remove dhcp_extra_opt
** Tags added: api-ref
** Project changed: openstack-api-site => neutron
** Changed in: neutron
Milestone: mitaka => None
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1408112
Title:
Update documentation for port does not show how to remove
dhcp_extra_opt
Status in neutron:
Confirmed
Bug description:
The manual shows how to add dhcp_extra_opts but not have to unset them
Need to add an example
{
"port":
{
"extra_dhcp_opts": [{"opt_value": null, "opt_name": "33"}]
}
}
---
Built: 2014-08-11T21:06:30 00:00
git SHA: 3302e05316e88d42067e3c1555df34371043999d
URL:
http://docs.openstack.org/api/openstack-network/2.0/content/extra-dhc-opt-ext-update.html
source File:
file:/home/jenkins/workspace/netconn-api-tox-doc-publishdocs/v2.0/section_neutron-ext-extra-dhcp-options.xml
xml:id: extra-dhc-opt-ext-update
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1408112/+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 1505776] Re: Validate src_ip_adress, dest_ip_address and ip_version
** Project changed: openstack-api-site => neutron ** Tags added: api-ref -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1505776 Title: Validate src_ip_adress, dest_ip_address and ip_version Status in neutron: Confirmed Status in openstack-manuals: Fix Released Bug description: https://review.openstack.org/215768 commit 29c51879683087e8ea486aaa9866bbce1f47a15c Author: Sean M. Collins Date: Mon Aug 10 15:24:52 2015 -0400 Validate src_ip_adress, dest_ip_address and ip_version The FwaaS API should not allow the creation of firewall rules where the ip_version is set to 4, but the source or destination IPs are IPv6 addresses APIImpact DocImpact Closes-Bug: #1487599 Change-Id: Iad680996a47adcf27f9dc7e0bc0fea924fff4f9f To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1505776/+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 1551368] Re: L7 capability extension implementation for lbaas v2
The API-Ref is changed from doc to each project (neutron) ** Changed in: neutron Status: Invalid => Confirmed ** Changed in: openstack-api-site Status: Confirmed => 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/1551368 Title: L7 capability extension implementation for lbaas v2 Status in neutron: Confirmed Status in openstack-api-site: Invalid Status in openstack-manuals: Confirmed Bug description: https://review.openstack.org/148232 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. commit 254190b3051453f823dbdf1826f1a6b984c57164 Author: Evgeny Fedoruk Date: Mon Jan 19 03:47:39 2015 -0800 L7 capability extension implementation for lbaas v2 Including extension modifications Including db model modifications Including alembic migration Including new driver managers for l7 rules and policies Inclufing logging_noop driver implementation Including unit testing Including Octavia driver updates DocImpact APIImpact Change-Id: I8f9535ebf28155adf43ebe046d2dbdfa86c4d81b Implements: blueprint lbaas-l7-rules Co-Authored-By: Evgeny Fedoruk Co-Authored-By: Stephen Balukoff To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1551368/+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 1548511] Re: Shared pools support
The API-Ref is changed from doc to each project (neutron) ** Changed in: openstack-api-site Status: Confirmed => 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/1548511 Title: Shared pools support Status in neutron: Confirmed Status in openstack-api-site: Invalid Bug description: https://review.openstack.org/218560 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. commit 4f3cf154829fcd69ecf3fa7f4e49f82d0104a4f0 Author: Stephen Balukoff Date: Sat Aug 29 02:51:09 2015 -0700 Shared pools support In preparation for L7 switching functionality, we need to reduce the rigidity of our model somewhat and allow pools to exist independent of listeners and be shared by 0 or more listeners. With this patch, pools are now associated with loadbalancers directly, and there is now a N:M relationship between listeners and pools. This patch does alter the Neutron LBaaS v2 API slightly, but all these changes are backward compatible. Nevertheless, since Neutron core dev team has asked that any API changes take place in an extension, that is what is being done in this patch. This patch also updates the reference namespace driver to render haproxy config templates correctly given the pool sharing functionality added with the patch. Finally, the nature of shared pools means that the usual workflow for tenants can be (but doesn't have to be) altered such that pools can be created before listeners independently, and assigned to listeners as a later step. DocImpact APIImpact Partially-Implements: blueprint lbaas-l7-rules Change-Id: Ia0974b01f1f02771dda545c4cfb5ff428a9327b4 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1548511/+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 1550559] Re: Qos policy RBAC DB setup and migration
The API-Ref is changed from doc to each project (neutron) ** Changed in: neutron Status: Invalid => Confirmed ** Changed in: openstack-api-site Status: Confirmed => 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/1550559 Title: Qos policy RBAC DB setup and migration Status in neutron: Confirmed Status in openstack-api-site: Invalid Status in openstack-manuals: Fix Released Bug description: https://review.openstack.org/250081 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit aeaf77a5295080a3010a2e9c32e24f47c8cc73cc Author: Haim Daniel Date: Wed Nov 25 18:49:45 2015 -0500 Qos policy RBAC DB setup and migration This patch implements a new database model required for the qos-policy RBAC support. In addition it migrates the current qos-policy 'shared' attribute to leverage the new 'qospolicyrbacs' table. 'shared' is no longer a property of the QosPolicy DB model. Its status is based on the tenant ID of the API caller. From an API perspective the logic remains the same - tenants will see qos-policies as 'shared=True' in case the qos-policy is shared with them). However, internal callers (e.g. plugins, drivers, services) must not check for the 'shared' attribute on qos-policy db objects any more. DocImpact APIImpact Blueprint: rbac-qos Related-bug: #1512587 Change-Id: I1c59073daa181005a3e878bc2fe033a0709fbf31 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1550559/+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 1565631] Re: [Shared images] is missing and wrong parameter
** Project changed: openstack-api-site => glance ** Tags added: api-ref -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1565631 Title: [Shared images] is missing and wrong parameter Status in Glance: Confirmed Bug description: Response parameters in List shared images [1] miss "shared_images" parameter. And type of "image_id" parameter is "xsd:string", this value is wrong. It should be change "csapi:UUID". [1] http://developer.openstack.org/api-ref- image-v1.html#listSharedImages-v1 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1565631/+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 1537121] Re: Add functionality to define requests without body
** Project changed: openstack-api-site => glance ** Tags added: api-ref -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1537121 Title: Add functionality to define requests without body Status in Glance: Confirmed Bug description: https://review.openstack.org/207150 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. commit 9b430f99518e10ae263bedec3062408af332068c Author: Niall Bunting Date: Tue Jul 28 15:05:10 2015 + Add functionality to define requests without body This allows functions that do not accept bodies to define this in the router file. As currently many requests will cause a 500 if a body is supplied when the API request does not expect it. This currently only affects the core parts of the v2 api, that is, calls to v2/images and v2/schemas. It does not cover the "tasks" API or the metadefs api as I was keeping this patch concise. As this does not affect the behaviour if not included this makes no change to the metadefs api behaviour. DocImpact Partial-Bug: 1475647 Change-Id: Ieb510e5516128078d40d39fd9b4f339ce64e10e7 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1537121/+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 1532220] Re: OS-EP-FILTER extension missing
** Project changed: openstack-api-site => keystone ** Tags added: api-ref ** Summary changed: - OS-EP-FILTER extension missing + [api-ref]OS-EP-FILTER extension missing -- 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/1532220 Title: [api-ref]OS-EP-FILTER extension missing Status in OpenStack Identity (keystone): Confirmed Bug description: Missing OS-EP-FILTER extension for Identity v3: http://specs.openstack.org/openstack/keystone-specs/api/v3/identity- api-v3-os-ep-filter-ext.html To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1532220/+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 1532222] Re: OS-FEDERATION extension missing
** Project changed: openstack-api-site => keystone ** Tags added: api-ref ** Summary changed: - OS-FEDERATION extension missing + [api-ref]OS-FEDERATION extension missing -- 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/153 Title: [api-ref]OS-FEDERATION extension missing Status in OpenStack Identity (keystone): Confirmed Bug description: The OS-FEDERATION extension is missing for Identity v3: http://specs.openstack.org/openstack/keystone-specs/api/v3/identity- api-v3-os-federation-ext.html To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/153/+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 1506149] Re: Bodies that are not dicts or lists return 400
The API-REF is canged from doc to each project (glance) ** Project changed: openstack-api-site => glance ** Changed in: glance Milestone: mitaka => None -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1506149 Title: Bodies that are not dicts or lists return 400 Status in Glance: Confirmed Status in openstack-manuals: Confirmed Bug description: https://review.openstack.org/204138 commit d8ca5c20c51a205624b3e815726e5c103a30b632 Author: Niall Bunting Date: Tue Jul 21 15:22:06 2015 + Bodies that are not dicts or lists return 400 Type errors that are encountered due to unexpected types being passed in now get a 400 'Body format is invalid'. This hardens the glance api from other types. ApiImpact DocImpact Closes-Bug: 1476695 Closes-Bug: 1476253 Change-Id: Ieee0662f67c800b2b3c07c6a8b7877939cf9e1fe To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1506149/+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 1471032] Re: Support Basic Address Scope CRUD as extensions
** Project changed: openstack-api-site => neutron ** Tags added: api-ref ** Summary changed: - Support Basic Address Scope CRUD as extensions + [api-ref]Support Basic Address Scope CRUD as extensions -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1471032 Title: [api-ref]Support Basic Address Scope CRUD as extensions Status in neutron: Confirmed Bug description: https://review.openstack.org/189741 commit cbd95318ad6c44e72a3aa163f7a399353c8b4458 Author: vikram.choudhary Date: Tue Jun 9 19:55:59 2015 +0530 Support Basic Address Scope CRUD as extensions This patch adds the support for basic address scope CRUD. Subsequent patches will be added to use this address scope on subnet pools. DocImpact APIImpact Co-Authored-By: Ryan Tidwell Co-Authored-By: Numan Siddique Change-Id: Icabdd22577cfda0e1fbf6042e4b05b8080e54fdb Partially-implements: blueprint address-scopes To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1471032/+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 1552015] Re: Support cleanup of tenant resources with a single API call
The API-Ref is changed from doc to each project (neutron). ** Project changed: openstack-api-site => neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1552015 Title: Support cleanup of tenant resources with a single API call Status in neutron: Confirmed Status in openstack-manuals: Fix Released Status in python-neutronclient: Invalid Bug description: https://review.openstack.org/276541 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/python-neutronclient" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit 88fbd3870cf3872fb0c9b4269503c62458664b3b Author: John Davidge Date: Mon Feb 15 10:02:54 2016 -0800 Support cleanup of tenant resources with a single API call The addition of the 'neutron purge' command allows cloud admins to conveniently delete multiple neutron resources associated with a given tenant. The command will delete all supported resources provided that they can be deleted (not in use, etc) and feedback the amount of each resource deleted to the user. A completion percentage is also given to keep the user informed of progress. Currently supports deletion of: Networks Subnets (implicitly) Routers Ports (including router interfaces) Floating IPs Security Groups This feature can be easily extended to support more resource types in the future. DocImpact: Update API documentation to describe neutron-purge usage Change-Id: I5a366d3537191045eb53f9cccd8cd0f7ce54a63b Closes-Bug: 1511574 Partially-Implements: blueprint tenant-delete To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1552015/+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 1547271] Re: Preserve subnet_create behavior in presence of subnet pools
The API-Ref is moved from doc to each project (neutron) ** Changed in: neutron Status: Invalid => Confirmed ** Changed in: openstack-api-site Status: Confirmed => 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/1547271 Title: Preserve subnet_create behavior in presence of subnet pools Status in neutron: Confirmed Status in openstack-api-site: Invalid Status in openstack-manuals: Confirmed Bug description: https://review.openstack.org/279378 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit d38aeade9db7169955b4524a5fc8d814067dec15 Author: Armando Migliaccio Date: Thu Feb 11 20:56:20 2016 -0800 Preserve subnet_create behavior in presence of subnet pools The development of the auto_allocate extension, which relies on subnet pools, revealed some discrepancies in the behavior of the subnet_create API: if a user specifies a cidr on subnet_create like he/she is used to, the API outcome changes in presence of default subnetpools. For instance the command 'neutron subnet-create network ' returns a subnet associated to a pool, if a default pool exists, but it does not otherwise. At the same time, attempting to create a subnet without passing any detail but the ip version also behaves unexpectedly depending on the state of the system. Whilst this could be considered convenient in some circumstances, it is problematic for a couple of reasons: a) it breaks a well defined contract (backward compat of the subnet-create command), and b) it leads to ambiguity of the API. This patch restores the semantic of the subnet_create API where it is mandatory to specify CIDR/IP version regardless of the conditions under which the request is issued. On the other hand, associating subnets to subnet pools will have to be more prescriptive, and require the user to explicitly state his/her intentions when creating the subnet: if a user does want a subnet (CIDR) to belong to a subnet pool, he/she will have to state so, either by specifying a subnetpool name/uuid, or by asking for a default one. This will be tackled as a follow-up, especially in order to address the needs of prefix delegation which currently rely on the ambiguous behavior that this patch is fixing. Closes-bug: 1545199 DocImpact: subnetpools can be used to simplify IPAM, and can be specified during subnet creation. Change-Id: Idf516ed9db24d779742cdff0584b48182a8502d6 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1547271/+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 1564887] Re: Neutron v2 Layer-3 extension - `routes` attribute not helpful
** Project changed: openstack-api-site => neutron ** Tags added: api-ref ** Summary changed: - Neutron v2 Layer-3 extension - `routes` attribute not helpful + [api-ref]Neutron v2 Layer-3 extension - `routes` attribute not helpful -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1564887 Title: [api-ref]Neutron v2 Layer-3 extension - `routes` attribute not helpful Status in neutron: In Progress Bug description: In all the router responses, you see a `routes` attribute. This is the explanation for it: routes plain xsd:listThe extra routes configuration for L3 router. 1. What exactly is the structure of this value? "xsd:list" means nothing to me. Are there nested objects, nested strings? 2. The description doesn't explain how a route functions. Also, how do routes get set on routers? It's not included as an input param for POST or PUT operations. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1564887/+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 1516073] Re: Replace subnetpool config options with admin-only API
** Project changed: openstack-api-site => neutron ** Tags added: api-ref -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1516073 Title: Replace subnetpool config options with admin-only API Status in neutron: Confirmed Status in openstack-manuals: Confirmed Bug description: https://review.openstack.org/230983 commit 6ee91e56c84ea6e930369f8649f1d2b50096cb80 Author: John Davidge Date: Thu Oct 1 20:37:34 2015 +0100 Replace subnetpool config options with admin-only API This patch adds a new boolean 'is_default' property to subnetpools. This allows the admin to set the default v4/v6 subnetpools via the API rather than the existing neutron.conf options - which are deprecated by this patch. Only one subnetpool per IP family can be set to default. DocImpact ApiImpact Co-Authored-By: Carl Baldwin Change-Id: I5daba2347cfb91fac0b155b2c1b459ee7d9e4505 Closes-Bug: 1501328 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1516073/+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 1364221] Re: IPSec site connections in OpenStack Networking API v2.0 (neutron) Reference - API v2.0 (neutron) and extensions
The API-ref issue is moved from doc to each project (neutron). ** Project changed: openstack-api-site => neutron ** Changed in: neutron Milestone: liberty => None -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1364221 Title: IPSec site connections in OpenStack Networking API v2.0 (neutron) Reference - API v2.0 (neutron) and extensions Status in neutron: Confirmed Status in python-neutronclient: Won't Fix Bug description: peer_id attribute can be IPv4/IPv6 address as per design now ,but in notes mentioned as it can be IPv4/IPv6 address, e-mail address, key id, or FQDN. --- Built: 2014-08-11T21:06:27 00:00 git SHA: 3302e05316e88d42067e3c1555df34371043999d URL: http://docs.openstack.org/api/openstack-network/2.0/content/vpnaas_ext_ops_ipsec_site_connection.html source File: file:/home/jenkins/workspace/netconn-api-tox-doc-publishdocs/v2.0/section_neutron-ext-vpnaas.xml xml:id: vpnaas_ext_ops_ipsec_site_connection To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1364221/+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 1570892] Re: Openswan/Libreswan: support sha256 for auth algorithm
** Project changed: openstack-api-site => neutron ** Summary changed: - Openswan/Libreswan: support sha256 for auth algorithm + [api-ref]Openswan/Libreswan: support sha256 for auth algorithm ** Tags added: api-ref -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1570892 Title: [api-ref]Openswan/Libreswan: support sha256 for auth algorithm Status in neutron: Confirmed Bug description: https://review.openstack.org/303684 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. commit b73e1002555cfa70ccfea8ffe685672c0b679212 Author: nick.zhuyj Date: Fri Apr 8 23:48:33 2016 -0500 Openswan/Libreswan: support sha256 for auth algorithm Add support for sha256 as it is requirement from customer. Currently, there is no ike/esp fields in strongswan ipsec.conf template, so by default. sha256 is used. But for openswan auth algorithm is get from configuration, so only sha1 is supported. This patch enable Openswan/Libreswan to support sha256. Note: this change is DocImpact and APIImpact Change-Id: I02c80ec3494eb0edef2fdaa5d21ca0c3bbcacac2 Closes-Bug: #1567846 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1570892/+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 1572168] Re: Missing response parameter tables identity admin API
** Project changed: openstack-api-site => keystone ** Summary changed: - Missing response parameter tables identity admin API + [api-ref]Missing response parameter tables identity admin API ** Tags added: api-ref -- 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/1572168 Title: [api-ref]Missing response parameter tables identity admin API Status in OpenStack Identity (keystone): In Progress Bug description: http://developer.openstack.org/api-ref-identity-admin-v2.html#admin-listTenants http://developer.openstack.org/api-ref-identity-admin-v2.html#admin-showTenantByName http://developer.openstack.org/api-ref-identity-admin-v2.html#admin-showTenantById http://developer.openstack.org/api-ref-identity-admin-v2.html#admin-listRolesForUserOnTenant The above APIs do not have response parameter table. They must be documented. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1572168/+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 1566607] Re: [Show user details] miss request parameter
** Project changed: openstack-api-site => keystone ** Summary changed: - [Show user details] miss request parameter + [api-ref][Show user details] miss request parameter ** Tags added: api-ref -- 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/1566607 Title: [api-ref][Show user details] miss request parameter Status in OpenStack Identity (keystone): Confirmed Bug description: Show user details [1] miss parameters: name, enabled, email, id, user and username [1]http://developer.openstack.org/api-ref-identity-admin-v2.html #admin-showUser To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1566607/+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 1418635] Re: Neutron API reference is inconsistent and differs from implementation
** Project changed: openstack-api-site => neutron
** Summary changed:
- Neutron API reference is inconsistent and differs from implementation
+ [api-ref]Neutron API reference is inconsistent and differs from implementation
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1418635
Title:
[api-ref]Neutron API reference is inconsistent and differs from
implementation
Status in neutron:
Confirmed
Bug description:
I'm implementing modules for SaltStack (not yet on GitHub) to create entities
in OpenStack Neutron and came across quite a few problems
with the API documentation:
* Link "Filtering and Column Selection" to
http://docs.openstack.org/api/openstack-network/2.0/content/filtering.html
404s
* Section http://developer.openstack.org/api-ref-
networking-v2.html#subnets
* "POST /v2.0/subnets" aka "Create subnet"
- 'id' is listed to be an optional parameter but the Neutron-API in
Icehouse refuses to set a user-selected ID
- parameters 'dns_nameservers' and 'host_routes' missing from
documentation (undocumented extensions?)
* "GET /v2.0/subnets" aka "List subnets"
- can't filter by "allocation_pools" or "enable_dhcp"
* "PUT /v2.0/subnets/{subnet_id}" aka "Update subnet"
- parameters "allocation_pools", "network_id", "tenant_id", "id" listed
as optional request parameters but Neutron-API in Icehouse returns
"Cannot update read-only attribute $PARAMETER"
* Section http://developer.openstack.org/api-ref-
networking-v2.html#networks
* "GET /v2.0/networks" aka "List networks"
- parameter "shared" is ignored as a filter
* Section http://developer.openstack.org/api-ref-
networking-v2.html#layer3
* "POST /v2.0/routers" aka "Create router"
- Description states "router:external" and "external_gateway_info" are
valid request parameters but they're not listed in the table of
request parameters
- What's the parameter router described as "A router object." supposed
to be? A router object in JSON/XML notation inside a router object in
JSON/XML notation?
I'll probably add more when implementing functions for managing
routers in Neutron.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1418635/+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 1552077] Re: Use network RBAC feature for external access
The API-Ref is changed from api-site to project (neutron) ** Changed in: openstack-api-site Status: Confirmed => Invalid ** Changed in: neutron Status: Invalid => Confirmed ** Summary changed: - Use network RBAC feature for external access + [api-ref]Use network RBAC feature for external access -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1552077 Title: [api-ref]Use network RBAC feature for external access Status in neutron: Confirmed Status in openstack-api-site: Invalid Bug description: https://review.openstack.org/282295 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit 49b4dd3478d782aee4260033825aa6b47eaf644a Author: Kevin Benton Date: Fri Feb 19 03:34:27 2016 -0800 Use network RBAC feature for external access This allows access to external networks to be controlled via the RBAC framework added during Liberty with a new 'access_as_external' action. A migration adds all current external networks to the RBAC policies table with a wildcard indicating that all tenants can access the network as RBAC. Unlike the conversion of shared networks to RBAC, the external table is left in the DB to avoid invasive changes throughout the codebase to calculate the flag relative to the caller. So the current 'external' flag is used throughout the code base as it previously was for wiring up floating IPs, router gateway ports, etc. Then the RBAC entries are only referenced when determining what networks to show the tenants. API Behavior: * Marking a network as 'external' will automatically create a wildcard entry that allows that network to be accessed by all tenants. * An external network may have all of its RBAC entries deleted and then only an admin will be able to attach to it. * An RBAC 'access_as_external' entry cannot be deleted if it is required for a tenant that currently has a router attached to that network. * Creating an 'access_as_external' RBAC entry will automatically convert the network into an external network. (This is to enable a workflow where a private external network is never visible to everyone.) * The default policy.json will prevent a non-admin from creating wildcard 'access_as_external' RBAC entries to align with the current default policy we have on setting the 'external' field on the network to prevent poluting everyone else's network lists. * The default policy.json will allow a tenant to create an 'access_as_external' RBAC entry to allow specific tenants (including itself) the ability to use its network as an external network. Closes-Bug: #1547985 DocImpact: External networks can now have access restricted to small subsets of tenants APIImpact: 'access_as_external' will be allowed as an action in the RBAC API for networks Change-Id: I4d8ee78a9763c58884e4fd3d7b40133da659cd61 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1552077/+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 1382268] Re: Add notification for server group operations
** Project changed: openstack-api-site => nova ** Summary changed: - Add notification for server group operations + [api-ref]Add notification for server group operations -- 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/1382268 Title: [api-ref]Add notification for server group operations Status in OpenStack Compute (nova): Confirmed Bug description: https://review.openstack.org/107954 commit daf278c0c8b6cc917b84f514fec65758adf17028 Author: Jay Lau Date: Thu Oct 16 15:08:32 2014 -0400 Add notification for server group operations Currently, there is no notification when create/update/delete server groups, this caused some 3rd party client cannot know when those operations are finished. The fix was adding notifications for those operations. DocImpact The wiki page https://wiki.openstack.org/wiki/SystemUsageData needs to be updated once this patch was merged. Change-Id: Ia1f4a6752668ddb73ebb8faf525b58a28d183754 Closes-Bug: #1343200 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1382268/+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 1553332] Re: API documentation missing for neutron rbac-policies
** Project changed: openstack-api-site => neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1553332 Title: API documentation missing for neutron rbac-policies Status in neutron: In Progress Bug description: https://specs.openstack.org/openstack/neutron-specs/specs/liberty /rbac-networks.html#rest-api-impact doesn't appear to be reflected in the neutron API documentation, despite the fact that the spec was implemented (see neutron/extensions/rbac.py). I believe this should be included on http://developer.openstack.org/api-ref- networking-v2-ext.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1553332/+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 1553653] Re: Add a description field to all standard resources
API-Ref is moved from doc to each project (neutron). ** Changed in: neutron Status: Invalid => Confirmed ** Changed in: openstack-api-site Status: Confirmed => 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/1553653 Title: Add a description field to all standard resources Status in neutron: Confirmed Status in openstack-api-site: Invalid Bug description: https://review.openstack.org/269887 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit 5dacbba701037200f9b0ae40c34981ecd941b41c Author: Kevin Benton Date: Wed Feb 10 17:00:21 2016 -0800 Add a description field to all standard resources In order to give users and operators more flexibility in annotating the purpose of various Neutron resources, this patch adds a description field limited to 255 chars to all of the Neutron resources that reference the standard attribute table. The resource that reference the table are the following: security_group_rules, security_groups, ports, subnets, networks, routers, floatingips, subnetpools This patch adds a description table related to standard attributes and migrates over the existing security group description to the new table as well. Co-Authored-By: James Dempsey APIImpact DocImpact: Adds a description field to all resources outline in commit message. Closes-Bug: #1483480 Change-Id: I6e1ef53d7aae7d04a5485810cc1db0a8eb125953 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1553653/+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 1487745] Re: Neutron RBAC API and network support
** Project changed: openstack-api-site => neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1487745 Title: Neutron RBAC API and network support Status in neutron: Confirmed Status in openstack-manuals: Won't Fix Bug description: https://review.openstack.org/192555 commit 4595899f7f2b3774dc2dac2f8dd1a085b1e7973d Author: Kevin Benton Date: Tue Jun 16 23:43:59 2015 -0700 Neutron RBAC API and network support This adds the new API endpoint to create, update, and delete role-based access control entries. These entries enable tenants to grant access to other tenants to perform an action on an object they do not own. This was previously done using a single 'shared' flag; however, this was too coarse because an object would either be private to a tenant or it would be shared with every tenant. In addition to introducing the API, this patch also adds support to for the new entries in Neutron networks. This means tenants can now share their networks with specific tenants as long as they know the tenant ID. This feature is backwards-compatible with the previous 'shared' attribute in the API. So if a deployer doesn't want this new feature enabled, all of the RBAC operations can be blocked in policy.json and networks can still be globally shared in the legacy manner. Even though this feature is referred to as role-based access control, this first version only supports sharing networks with specific tenant IDs because Neutron currently doesn't have integration with Keystone to handle changes in a tenant's roles/groups/etc. DocImpact APIImpact Change-Id: Ib90e2a931df068f417faf26e9c3780dc3c468867 Partially-Implements: blueprint rbac-networks To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1487745/+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 1532223] Re: [api-ref]OS-REVOKE extension missing for Identity v3
** Summary changed: - OS-REVOKE extension missing for Identity v3 + [api-ref]OS-REVOKE extension missing for Identity v3 ** Project changed: openstack-api-site => keystone -- 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/1532223 Title: [api-ref]OS-REVOKE extension missing for Identity v3 Status in OpenStack Identity (keystone): Confirmed Bug description: OS-REVOKE extension is missing for Identity v3: http://specs.openstack.org/openstack/keystone-specs/api/v3/identity- api-v3-os-revoke-ext.html To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1532223/+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 1517705] Re: Move federation extension into keystone core
The api-ref is changed from api-site to keystone. ** Project changed: openstack-api-site => keystone -- 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/1517705 Title: Move federation extension into keystone core Status in OpenStack Identity (keystone): Confirmed Status in openstack-manuals: Confirmed Bug description: https://review.openstack.org/214775 commit cbefe7c7b83b5f940f817adf60a4be35bd324775 Author: Steve Martinelli Date: Sun Oct 11 03:01:05 2015 -0400 Move federation extension into keystone core Remove federation as an extension and move it to a core resource. For now we leave the database migrations in the extension directory until we have a general policy for merging these into core. Some instances of federation constants were removed because they were causing a circular dependency, these can be refactored in a later patch. DocImpact: You should no longer run the migrations for this extension Implements: bp move-extensions Co-Authored-By: Nithya Renganathan Change-Id: If5857a6ee4c7c527929069b25beab40f4c5d87e2 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1517705/+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 1253672] Re: update Images v2 API to include info about multilevel restricted JSON pointers
** Project changed: openstack-api-site => glance -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1253672 Title: update Images v2 API to include info about multilevel restricted JSON pointers Status in Glance: Triaged Bug description: The Havana release of Glance introduces a "multiple image locations" option. In order to allow the http PATCH (image-update) request to operate on multiple locations, the "restricted JSON pointers" used by the application/openstack-images-v2.1-json-patch media type has been expanded to allow multilevel references. (1) The documentation in the OpenStack Image Service API v2 Reference needs to be updated to reflect this. (2) Need to supply at least one example, either in Appendix B or in the image update section, illustrating how to use the multilevel pointer to update an image location. (3) Judgement call: update the image detail section to show what an image response looks like with multiple image locations turned on. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1253672/+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 1524153] Re: Need to write "update user of OS-KSCRUD extension" on identity v2 API
** Project changed: openstack-api-site => keystone ** Summary changed: - Need to write "update user of OS-KSCRUD extension" on identity v2 API + [api-ref]Need to write "update user of OS-KSCRUD extension" on identity v2 API -- 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/1524153 Title: [api-ref]Need to write "update user of OS-KSCRUD extension" on identity v2 API Status in OpenStack Identity (keystone): Confirmed Bug description: Now keystone supports "update user of OS-KSCRUD extension" on identity v2 API, and tempest also is testing the API. However, the api-site doesn't contain the API description. So we need to write the API for API users. The URL is "OS-KSCRUD/users/" and the method is PATCH on identity v2 API. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1524153/+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 1526212] Re: [api-ref]Need to write "add dhcp agent to network" on Networking API
** Summary changed: - Need to write "add dhcp agent to network" on Networking API + [api-ref]Need to write "add dhcp agent to network" on Networking API ** Project changed: openstack-api-site => neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1526212 Title: [api-ref]Need to write "add dhcp agent to network" on Networking API Status in neutron: Confirmed Bug description: Neutron supports "add dhcp agent to network" on Networking API, and tempest also is testing the API. However, the api-site doesn't contain the API description. So we need to write the API for API users. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1526212/+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 1526670] Re: [api-ref]Need to write "add router to l3 agent" on Networking API
** Summary changed: - Need to write "add router to l3 agent" on Networking API + [api-ref]Need to write "add router to l3 agent" on Networking API ** Project changed: openstack-api-site => neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1526670 Title: [api-ref]Need to write "add router to l3 agent" on Networking API Status in neutron: Confirmed Bug description: Neutron supports "add router to l3 agent" on Networking API, and tempest also is testing the API. However, the api-site doesn't contain the API description. So we need to write the API for API users. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1526670/+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 1526673] Re: Need to write "update agent" on Networking API
** Project changed: openstack-api-site => neutron ** Summary changed: - Need to write "update agent" on Networking API + [api-ref]Need to write "update agent" on Networking API -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1526673 Title: [api-ref]Need to write "update agent" on Networking API Status in neutron: In Progress Bug description: Neutron supports "update agent" on Networking API, and tempest also is testing the API. However, the api-site doesn't contain the API description. So we need to write the API for API users. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1526673/+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 1361791] Re: Allow attaching external networks based on configurable policy
** Project changed: openstack-api-site => nova ** Summary changed: - Allow attaching external networks based on configurable policy + [api-ref]Allow attaching external networks based on configurable policy -- 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/1361791 Title: [api-ref]Allow attaching external networks based on configurable policy Status in OpenStack Compute (nova): Confirmed Bug description: https://review.openstack.org/112750 commit 674954f731bf4b66356fadaa5baaeb58279c5832 Author: Chris Yeoh Date: Fri Aug 8 11:48:17 2014 +0930 Allow attaching external networks based on configurable policy Commit da66d50010d5b1ba1d7fc9c3d59d81b6c01bb0b0 restricted attaching external networks to admin clients. This patch changes it to a policy based check instead with the default setting being admin only. This allows operators to more precisely configure who they wish to allow to attach external networks without having to give them admin access Change-Id: I59e71f117f889f2abffddc36c1870ef1e0fe3711 DocImpact: Adds network:attach_external_network policy Closes-Bug: #1352102 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1361791/+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 1523012] Re: set `is_admin` on tokens for admin project
** Project changed: openstack-api-site => keystone -- 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/1523012 Title: set `is_admin` on tokens for admin project Status in OpenStack Identity (keystone): In Progress Status in openstack-manuals: Confirmed Bug description: https://review.openstack.org/240719 commit e7023697a884759716d0a01605825a3af90d4db6 Author: Adam Young Date: Sun Oct 11 23:15:52 2015 -0400 set `is_admin` on tokens for admin project Adds two new configuration value: admin_project_name admin_project_domain_name If both values are set, and tokens requested for projects (only, not domains) that match both will have an additional value in them; `is_admin_project=true` DocImpact -- Configuration changes need documentation APIImpact -- Adds optional return values in token validation calls SecurityImpact -- Should be helpful in making access control decisions Implements: blueprint is-admin-project Partial-Bug: #968696 Change-Id: Ic9cf9862739381a30130b4be87075f726736ff88 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1523012/+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 1539467] Re: [Image service API v2] Incorrect description for List API
** Tags added: api-ref ** Project changed: openstack-api-site => glance -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1539467 Title: [Image service API v2] Incorrect description for List API Status in Glance: In Progress Bug description: I 've tested this API: http://developer.openstack.org/api-ref-image-v2.html#listVersions-image-v2 The description for the response of the API says: "This operation does not accept a request body and does not return a response body." But the API does return a response. The description should be: "This operation does not accept a request body." To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1539467/+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 1480400] Re: Documentation error for properties
The api-ref is maintained by each module (for this case glance).
So I close for api-site ticket.
** Changed in: openstack-api-site
Status: In Progress => Opinion
** Changed in: openstack-api-site
Status: Opinion => 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/1480400
Title:
Documentation error for properties
Status in Glance:
In Progress
Status in openstack-api-site:
Invalid
Bug description:
Document: http://developer.openstack.org/api-ref-image-v2.html
Under the image create drop down there is the following line:
properties (Optional) plain | xsd:dict | Properties, if any, that are
associated with the image.
This suggests that the properties are a dict and would look like this:
-d '{"name": "thename", "properties": {"myprop", "mydata"}}'
this is not the case, as if you want
to define custom properties in a curl command you do it by defining it like
any other property eg.
-d '{"name": "thename", "myprop": "mydata"}'
The documentation is not clear about this distinction.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1480400/+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 1581666] Re: [api-ref]Broken link to filtering section in list floating IP detail operation
** Summary changed: - Broken link to filtering section in list floating IP detail operation + [api-ref]Broken link to filtering section in list floating IP detail operation ** Project changed: openstack-api-site => neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1581666 Title: [api-ref]Broken link to filtering section in list floating IP detail operation Status in neutron: New Bug description: In repo: https://github.com/openstack/api-site/blob/master/api-ref/source/networking/v2-ext/layer3-ext.inc In operation "Show floating IP details" here http://developer.openstack.org/api-ref-networking-v2-ext.html#showFloatingIp It offers a link to filtering section which is broken. Link should point to : https://wiki.openstack.org/wiki/Neutron/APIv2-specification#Filtering_and_Column_Selection The “List floating IP” operation links correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1581666/+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 1571628] Re: os-server-groups description is missing
** Project changed: openstack-api-site => nova -- 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/1571628 Title: os-server-groups description is missing Status in OpenStack Compute (nova): New Bug description: Description of os-server-groups is missing from the Compute API reference [1]. [1]: http://developer.openstack.org/api-ref-compute-v2.1.html To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1571628/+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 1572013] Re: missing parameter explaination in "Servers" section of v2.1 compute api
** Project changed: openstack-api-site => nova
--
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/1572013
Title:
missing parameter explaination in "Servers" section of v2.1 compute
api
Status in OpenStack Compute (nova):
New
Bug description:
URL: http://developer.openstack.org/api-ref-compute-v2.1.html
I think the request parameters listed in "GET /v2.1/{tenant_id}/servers" of
"Servers" section are not complete, when i want to get all servers of all
tenants, there should be "?all_tenants=true" in the url, as i read in
python-novaclient source code and it works actually after testing; but there is
no specific description about "all_tenant" listed in "Request parameters"
following in the api documentation.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1572013/+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 1564973] Re: [liberty] add arp_responder flag to linuxbridge agent
*** This bug is a duplicate of bug 1551805 *** https://bugs.launchpad.net/bugs/1551805 ** This bug has been marked a duplicate of bug 1551805 add arp_responder flag to linuxbridge agent -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1564973 Title: [liberty] add arp_responder flag to linuxbridge agent Status in neutron: Invalid Status in openstack-manuals: New Bug description: https://review.openstack.org/288050 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit c823e8ccb951a4abdf247dd094a794b7741d7cca Author: Mark McClain Date: Wed Feb 10 13:28:21 2016 -0500 add arp_responder flag to linuxbridge agent When the ARP responder is enabled, secondary IP addresses explicitly allowed by via the allowed-address-pairs extensions do not resolve. This change adds the ability to enable the local ARP responder similar to the feature in the OVS agent. This change disables local ARP responses by default, so ARP traffic will be sent over the overlay. DocImpact UpgradeImpact Change-Id: I5da4afa44fc94032880ea59ec574df504470fb4a Closes-Bug: 1445089 (cherry picked from commit bbd881f3a970143e1954cb277e523526c5d0) Signed-off-by: Kevin Carter To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1564973/+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
** Also affects: openstack-api-site
Importance: Undecided
Status: New
** Changed in: openstack-api-site
Status: New => Confirmed
--
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:
In Progress
Status in openstack-api-site:
Confirmed
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:
[Yahoo-eng-team] [Bug 1548511] Re: Shared pools support
** Project changed: openstack-manuals => 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/1548511 Title: Shared pools support Status in neutron: Confirmed Status in openstack-api-site: New Bug description: https://review.openstack.org/218560 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. commit 4f3cf154829fcd69ecf3fa7f4e49f82d0104a4f0 Author: Stephen Balukoff Date: Sat Aug 29 02:51:09 2015 -0700 Shared pools support In preparation for L7 switching functionality, we need to reduce the rigidity of our model somewhat and allow pools to exist independent of listeners and be shared by 0 or more listeners. With this patch, pools are now associated with loadbalancers directly, and there is now a N:M relationship between listeners and pools. This patch does alter the Neutron LBaaS v2 API slightly, but all these changes are backward compatible. Nevertheless, since Neutron core dev team has asked that any API changes take place in an extension, that is what is being done in this patch. This patch also updates the reference namespace driver to render haproxy config templates correctly given the pool sharing functionality added with the patch. Finally, the nature of shared pools means that the usual workflow for tenants can be (but doesn't have to be) altered such that pools can be created before listeners independently, and assigned to listeners as a later step. DocImpact APIImpact Partially-Implements: blueprint lbaas-l7-rules Change-Id: Ia0974b01f1f02771dda545c4cfb5ff428a9327b4 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1548511/+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 1527719] Re: Adding a VNIC type for physical functions
** Also affects: openstack-api-site Importance: Undecided Status: New ** Changed in: openstack-api-site Assignee: (unassigned) => Atsushi SAKAI (sakaia) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1527719 Title: Adding a VNIC type for physical functions Status in neutron: Fix Released Status in openstack-api-site: New Status in openstack-manuals: New Bug description: https://review.openstack.org/246923 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit 2c60278992d5a21724105ed0ca6e1d2f3e5c Author: Brent Eagles Date: Mon Nov 9 09:26:53 2015 -0330 Adding a VNIC type for physical functions This change adds a new VNIC type to distinguish between virtual and physical functions in SR-IOV. The new VNIC type 'direct-physical' deviates from the behavior of 'direct' VNICs for virtual functions. While neutron tracks the resource as a port, it does not currently perform any management functions. Future changes may extend the segment mapping functionality that is currently based on agent configuration to include direct types. However, the direct-physical VNICs will not have functional parity with the other SR-IOV VNIC types in that quality of service and port security functionality is not available. APIImpact DocImpact: Add description for new 'direct-physical' VNIC type. Closes-Bug: #1500993 Change-Id: If1ab969c2002c649a3d51635ca2765c262e2d37f To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1527719/+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 1527235] [NEW] [doc] glanceapi.rst missing ova
Public bug reported: glanceapi.rst missing ova for x-image-meta-container_format ** Affects: glance Importance: Undecided Assignee: Atsushi SAKAI (sakaia) Status: In Progress ** Changed in: glance Assignee: (unassigned) => Atsushi SAKAI (sakaia) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1527235 Title: [doc] glanceapi.rst missing ova Status in Glance: In Progress Bug description: glanceapi.rst missing ova for x-image-meta-container_format To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1527235/+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 1517212] Re: Support new v2 API image filters
** Also affects: glance Importance: Undecided Status: New ** Changed in: glance Assignee: (unassigned) => Atsushi SAKAI (sakaia) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1517212 Title: Support new v2 API image filters Status in Glance: New Status in openstack-api-site: Confirmed Bug description: https://review.openstack.org/197388 commit a4c6f126362e5dd43b1c99faeffeb46af389fe4a Author: Steve Lewis Date: Tue Jun 30 11:16:01 2015 -0700 Support new v2 API image filters Provide support in Glance API for querying the image list for created_at and updated_at times using guidance from the API Working Group recommendations for filtering. Filtering is applied at the DB layer. DocImpact ApiImpact MitakaPriority Change-Id: Ie94295bb82779ec17ab773928c71ae4a9ee8fbcc Implements bp: v2-additional-filtering To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1517212/+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 1524006] Re: NotImplementedError raised while create network using Nova REST API
Would you ask your questions in following URL?
https://ask.openstack.org/en/questions/
** Changed in: openstack-api-site
Status: New => Invalid
** Changed in: nova
Status: New => 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/1524006
Title:
NotImplementedError raised while create network using Nova REST API
Status in OpenStack Compute (nova):
Invalid
Status in openstack-api-site:
Invalid
Bug description:
Hi,
I've stucked with error:
{"computeFault":
{"message": "Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.\n
", "code": 500}}
It happened when I try create network for non-admin project using Nova REST
API
Source: http://developer.openstack.org/api-ref-compute-v2.1.html
POST
http://10.1.244.10:8774/v2.1/090aee2684a04e8397193a118a6e91b0/os-networks
POST data:
{
"network": {
"label": "scale-1-net",
"cidr": "172.1.0.0/24",
"mtu": 9000,
"dhcp_server": "172.1.0.2",
"enable_dhcp": false,
"share_address": true,
"allowed_start": "172.1.0.10",
"allowed_end": "172.1.0.200"
}
}
What's wrong?
or
What's the solution?
Thanks a lot.
---
Release: 2.1.0 on 2015-12-08 06:12
SHA: 60c5c2798004984738d171055dbc2a6fd37a85fe
Source:
http://git.openstack.org/cgit/openstack/nova/tree/api-guide/source/index.rst
URL: http://developer.openstack.org/api-guide/compute/
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1524006/+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 1515445] [NEW] / and /versions have same reply with another response
Public bug reported: If this is wrong asking in here, it would be appreciated to notice me the right place (ML etc). GET / and /versions have same reply with another response one is 300, another is 200. Is there any reason? P.S. I am checking the / and /versions API for API-Ref and found this issue. Ref https://review.openstack.org/#/c/244063/ ** Affects: glance 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/1515445 Title: / and /versions have same reply with another response Status in Glance: New Bug description: If this is wrong asking in here, it would be appreciated to notice me the right place (ML etc). GET / and /versions have same reply with another response one is 300, another is 200. Is there any reason? P.S. I am checking the / and /versions API for API-Ref and found this issue. Ref https://review.openstack.org/#/c/244063/ To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1515445/+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 1514792] [NEW] needs developer document update for with_venv.sh (oslo.incubator) deletion
Public bug reported: needs document update for with_venv.sh (oslo.incubator) deletion. effecting files are keystone/doc/source/developing.rst keystone/doc/source/devref/development.environment.rst This is related to following patch. https://github.com/openstack/keystone/commit/693755ee255ff7ba9c00f3f3cc86d75e90ad0b3a ** Affects: keystone Importance: Undecided Assignee: Atsushi SAKAI (sakaia) Status: New ** Changed in: keystone Assignee: (unassigned) => Atsushi SAKAI (sakaia) -- 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/1514792 Title: needs developer document update for with_venv.sh (oslo.incubator) deletion Status in OpenStack Identity (keystone): New Bug description: needs document update for with_venv.sh (oslo.incubator) deletion. effecting files are keystone/doc/source/developing.rst keystone/doc/source/devref/development.environment.rst This is related to following patch. https://github.com/openstack/keystone/commit/693755ee255ff7ba9c00f3f3cc86d75e90ad0b3a To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1514792/+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 1483993] [NEW] Fix three typos on nova/pci directory
Public bug reported: Fix three typos on nova/pci directory QuicAssist=> QuickAssist comptue => compute trackes=>tracks I am looking following report and found it. https://bugs.launchpad.net/openstack-manuals/+bug/1381017 ** Affects: nova Importance: Undecided Assignee: Atsushi SAKAI (sakaia) Status: New ** Changed in: nova Assignee: (unassigned) => Atsushi SAKAI (sakaia) -- 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/1483993 Title: Fix three typos on nova/pci directory Status in OpenStack Compute (nova): New Bug description: Fix three typos on nova/pci directory QuicAssist=> QuickAssist comptue => compute trackes=>tracks I am looking following report and found it. https://bugs.launchpad.net/openstack-manuals/+bug/1381017 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1483993/+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 1478003] [NEW] Fix seven typos on nova documentation
Public bug reported:
Fix seven typos on nova documentation
behaviour => behavior4
poicy => policy
schedular => scheduler
environement => environment
** Affects: nova
Importance: Undecided
Assignee: Atsushi SAKAI (sakaia)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) => Atsushi SAKAI (sakaia)
--
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/1478003
Title:
Fix seven typos on nova documentation
Status in OpenStack Compute (nova):
In Progress
Bug description:
Fix seven typos on nova documentation
behaviour => behavior4
poicy => policy
schedular => scheduler
environement => environment
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1478003/+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 1477898] [NEW] Fix five typos on keystone document
Public bug reported: Fix four typos and Add one space on keystone document encryted => encrypted counterintuitive => counter intuitive (space added) infomration =>information configuraton => configuration http://docs.openstack.org/developer/keystone/configuration.html Organizaion => Organization http://docs.openstack.org/developer/keystone/configure_federation.html $ git diff | diffstat configuration.rst|8 configure_federation.rst |2 +- 2 files changed, 5 insertions(+), 5 deletions(-) ** Affects: keystone Importance: Undecided Assignee: Atsushi SAKAI (sakaia) Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1477898 Title: Fix five typos on keystone document Status in Keystone: In Progress Bug description: Fix four typos and Add one space on keystone document encryted => encrypted counterintuitive => counter intuitive (space added) infomration =>information configuraton => configuration http://docs.openstack.org/developer/keystone/configuration.html Organizaion => Organization http://docs.openstack.org/developer/keystone/configure_federation.html $ git diff | diffstat configuration.rst|8 configure_federation.rst |2 +- 2 files changed, 5 insertions(+), 5 deletions(-) To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1477898/+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
