[Yahoo-eng-team] [Bug 1583253] Re: Rename Raw backend to Flat
** Changed in: openstack-manuals Status: In Progress => 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/1583253 Title: Rename Raw backend to Flat Status in OpenStack Compute (nova): Invalid Status in openstack-manuals: Fix Released Bug description: https://review.openstack.org/279626 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/nova" 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 cff4d78a4a7ddbb18cb875c66b3c56f04a6caea3 Author: Matthew Booth Date: Thu Apr 7 13:40:58 2016 +0100 Rename Raw backend to Flat As mentioned in a comment (which this patch deletes), calling this class 'Raw' was confusing, because it is not always raw. It is also a source of bugs, because some code assumes that the format is always raw, which it is not. This patch does not fix those bugs. We rename it to 'Flat', which describes it accurately. We also add doctext describing what it does. DocImpact The config option libvirt.images_type gets an additional value: 'flat'. The effect of this is identical to setting the value 'raw'. Change-Id: I93f0a2cc568b60c2b3f7509449167f03c3f30fb5 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1583253/+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 1583253] Re: Rename Raw backend to Flat
>From code base, we should replace 'raw' by 'flat'.
** Changed in: openstack-manuals
Status: Incomplete => Opinion
** Changed in: openstack-manuals
Status: Opinion => Triaged
** Changed in: openstack-manuals
Assignee: (unassigned) => KATO Tomoyuki (kato-tomoyuki)
--
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/1583253
Title:
Rename Raw backend to Flat
Status in OpenStack Compute (nova):
Invalid
Status in openstack-manuals:
Triaged
Bug description:
https://review.openstack.org/279626
Dear bug triager. This bug was created since a commit was marked with
DOCIMPACT.
Your project "openstack/nova" 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 cff4d78a4a7ddbb18cb875c66b3c56f04a6caea3
Author: Matthew Booth
Date: Thu Apr 7 13:40:58 2016 +0100
Rename Raw backend to Flat
As mentioned in a comment (which this patch deletes), calling this
class 'Raw' was confusing, because it is not always raw. It is also a
source of bugs, because some code assumes that the format is always
raw, which it is not. This patch does not fix those bugs.
We rename it to 'Flat', which describes it accurately. We also add
doctext describing what it does.
DocImpact
The config option libvirt.images_type gets an additional value:
'flat'. The effect of this is identical to setting the value 'raw'.
Change-Id: I93f0a2cc568b60c2b3f7509449167f03c3f30fb5
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1583253/+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 1538695] Re: sriov-mech: Introduce a new VIF type for PF vnic type
** 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/1538695 Title: sriov-mech: Introduce a new VIF type for PF vnic type Status in neutron: Incomplete Status in openstack-api-site: Fix Released Bug description: https://review.openstack.org/262604 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 4a431f75a01fbdd0b802c86e27a93a6daaf70399 Author: Nikola Dipanov Date: Wed Dec 30 19:48:33 2015 + sriov-mech: Introduce a new VIF type for PF vnic type We need to tell Nova to use a specific VIF type for full PF passthrough (this is the recently added VNIC_DIRECT_PHYSICAL vnic type). Make sure that when binding ports with this vnic type, we set the appropriate vif type for Nova to be able to provision those ports correctly. Nova change that adds a vif driver for this vif type: https://review.openstack.org/#/c/262583/ DocImpact: Exposes a new vif type for PF passtrhough vnic type Change-Id: I895dab98e5e5a9369771539e51ba5c500bfe0045 Related-blueprint: sriov-pf-passthrough-neutron-port To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1538695/+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 1645553] Re: Wrong link to role-assignment doc in Identity v3 api-ref
** 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/1645553 Title: Wrong link to role-assignment doc in Identity v3 api-ref Status in OpenStack Identity (keystone): New Bug description: Detail doc mentioned in identity v3 api-ref for role assignment is not right one. api-ref - http://developer.openstack.org/api-ref/identity/v3/?expanded =list-effective-role-assignments-detail non accessible link - http://docs.openstack.org/api/openstack- identity/3/rel/role_assignments To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1645553/+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 1641433] Re: Deprecate SR-IOV 'physical_device_mappings' config option
A bulk update for Ocata updates will treat this deprecation with doc- tool. ** Changed in: openstack-manuals Status: New => 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/1641433 Title: Deprecate SR-IOV 'physical_device_mappings' config option Status in neutron: Invalid Status in openstack-manuals: Won't Fix Bug description: https://review.openstack.org/395044 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 03b84bc920b5499e1fef23c646268fffa1d859d7 Author: Edan David Date: Tue Nov 8 10:30:45 2016 -0500 Deprecate SR-IOV 'physical_device_mappings' config option The device to physnet validation is made in Nova by pci_whitelist config option. Therefore it is redundant to validate it in Neutron with physical_device_mappings config option. Closes-Bug: #1640220 DocImpact Change-Id: I5f363347b327212a49a9b78a7164c11d9e457b10 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1641433/+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 1629507] Re: VMware: Enforce minimum vCenter version of 5.5
** Project changed: nova => 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/1629507 Title: VMware: Enforce minimum vCenter version of 5.5 Status in openstack-manuals: In Progress Bug description: https://review.openstack.org/253666 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/nova" 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 2851ceaed3010c19f42e308be637b952edab092a Author: Eric Brown Date: Fri Dec 4 11:39:18 2015 -0800 VMware: Enforce minimum vCenter version of 5.5 As of Ocata, the minimum version of VMware vCenter will be enforced at 5.1.0. And any version less than 5.5.0 will be warned as deprecated. In two releases, 5.5.0 will become the new minimum version. The VMware driver CI will has already migrated to vCenter 6.0. DocImpact: Need version updates on the minimum vCenter included in http://docs.openstack.org/mitaka/config-reference/compute/hypervisor-vmware.html Change-Id: I9f13e6cd6a49699f2b3cdce892fbf02634bf7618 To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-manuals/+bug/1629507/+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 1616134] Re: api-ref-compute-v2.1 - inaccurate description for parameters
** 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/1616134 Title: api-ref-compute-v2.1 - inaccurate description for parameters Status in OpenStack Compute (nova): New Bug description: After spending a few hours trying to work with the API documentation (http://developer.openstack.org/api-ref- compute-v2.1.html#createServer), I discovered the "networks" and "security_groups" parameters are not accurate enough. They are both described as "xsd:string" in the Type column, but they should be "xsd:list" of "xsd:dict". An example (as displayed on "block_device_mapping_v2") would also help everyone to use these parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1616134/+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 1631517] Re: No formal statement of project name restrictions
** 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/1631517 Title: No formal statement of project name restrictions Status in OpenStack Identity (keystone): New Bug description: I am unable to find any official documentation on project name restrictions. The only two that can be found are 1. It must be uniqe within the domain and 2. No more than 64 characters. http://developer.openstack.org/api-ref/identity/v3/?expanded=create-project-detail only states: "name: The name of the project, which must be unique within the owning domain. A project can have the same name as its domain." https://github.com/openstack/tempest/blob/master/tempest/api/identity/admin/v3/test_projects_negative.py#L60-L64 shows there is a 64 character limit. The name must be sent in a valid json which could be any utf-8 character, but does that always work within limits of all backends that use MySQL. MySQL's restrictions state utf-8, but "can contain only characters in the Basic Multilingual Plane (BMP). Supplementary characters are not permitted in identifiers." https://dev.mysql.com/doc/refman/5.5/en/charset-restrictions.html Please add documentation for restrictions on project names beyond uniqueness and character count. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1631517/+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 1630134] Re: Networking API v2.0 (CURRENT): Update Network Request missing the 'qos-policy-id' parameter.
** Changed in: openstack-api-site
Status: New => 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/1630134
Title:
Networking API v2.0 (CURRENT): Update Network Request missing the
'qos-policy-id' parameter.
Status in neutron:
Confirmed
Status in openstack-api-site:
Invalid
Bug description:
The API reference http://developer.openstack.org/api-
ref/networking/v2/index.html doesn't reflect the fact a Qos Policy
linked to an existing network can be updated:
$ curl -s -H "X-Auth-Token: $OS_TOKEN"
http://${OS_HOST}:9696/v2.0/qos/policies | python -mjson.tool{
"policies": [
{
"description": "This policy limits the ports to 10Mbit max.",
"id": "c4e80891-5d77-480f-8970-a7223fd72f4b",
"name": "10Mbit",
"rules": [],
"shared": false,
"tenant_id": "5a23535b5dda4770bccc856d0167e53f"
}
]
}
$ curl -s -H "X-Auth-Token: $OS_TOKEN" -H "Content-Type: application/json"
http://${OS_HOST}:9696/v2.0/networks/b18d3079-fcaa-41b7-8aec-0d009789fff8|
python -mjson.tool
{
"network": {
"admin_state_up": false,
"id": "b18d3079-fcaa-41b7-8aec-0d009789fff8",
"mtu": 0,
"name": "cristalnet",
"port_security_enabled": true,
"provider:network_type": "vxlan",
"provider:physical_network": null,
"provider:segmentation_id": 39,
"qos_policy_id": null,
"router:external": false,
"shared": true,
"status": "ACTIVE",
"subnets": [],
"tenant_id": "5a23535b5dda4770bccc856d0167e53f",
"vlan_transparent": null
}
}
$ curl -s \
> -X PUT \
> -H "X-Auth-Token: $OS_TOKEN" \
> -H "Content-Type: application/json" \
> -d '{"network": { "qos_policy_id": "c4e80891-5d77-480f-8970-a7223fd72f4b"
} }' \
> http://${OS_HOST}:9696/v2.0/networks/b18d3079-fcaa-41b7-8aec-0d009789fff8 |
python -mjson.tool
{
"network": {
"admin_state_up": false,
"id": "b18d3079-fcaa-41b7-8aec-0d009789fff8",
"mtu": 0,
"name": "cristalnet",
"port_security_enabled": true,
"provider:network_type": "vxlan",
"provider:physical_network": null,
"provider:segmentation_id": 39,
"qos_policy_id": "c4e80891-5d77-480f-8970-a7223fd72f4b",
"router:external": false,
"shared": true,
"status": "ACTIVE",
"subnets": [],
"tenant_id": "5a23535b5dda4770bccc856d0167e53f",
"vlan_transparent": null
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1630134/+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 1619002] Re: Networking API v2.0 in Networking API Reference missing information
** 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/1619002 Title: Networking API v2.0 in Networking API Reference missing information Status in neutron: New Bug description: In extensions, the loadbalancer object also has vip_port_id (http://developer.openstack.org/api-ref/networking/v2/index.html?expanded=show-load-balancer-details-detail#id3) - this does not appear on the documentation. --- Release: 0.4.1.dev4 on 'Sat Aug 27 19:31:24 2016, commit adef52e' SHA: Source: Can't derive source file URL URL: http://developer.openstack.org/api-ref/networking/v2/index.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1619002/+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 1605421] Re: Unable to add classless-static-route in extra_dhcp_opt extension
** 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/1605421
Title:
Unable to add classless-static-route in extra_dhcp_opt extension
Status in neutron:
New
Bug description:
When adding classless-static-route in extra_dhcp_opt for a port, neutron
client
complains syntax error. For example,
$ neutron port-update --extra-dhcp-opt
opt_name="classless-static-route",opt_value="169.254.169.254/32,20.20.20.1"
port1
usage: neutron port-update [-h] [--request-format {json}] [--name NAME]
[--description DESCRIPTION]
[--fixed-ip subnet_id=SUBNET,ip_address=IP_ADDR]
[--device-id DEVICE_ID]
[--device-owner DEVICE_OWNER]
[--admin-state-up {True,False}]
[--security-group SECURITY_GROUP |
--no-security-groups]
[--extra-dhcp-opt EXTRA_DHCP_OPTS]
[--qos-policy QOS_POLICY | --no-qos-policy]
[--allowed-address-pair
ip_address=IP_ADDR[,mac_address=MAC_ADDR]
| --no-allowed-address-pairs]
[--dns-name DNS_NAME | --no-dns-name]
PORT
neutron port-update: error: argument --extra-dhcp-opt: invalid key-value
'20.20.20.1', expected format: key=value
Try 'neutron help port-update' for more information.
The reason is neutron client interprets the "," inside the opt_value as
a delimiter of key-value pairs for --extra-dhcp-opt.
The comma in the opt_value for classless-static-route is required because
the format of DHCP options in the opts file for dnsmasq is like:
tag:,option:classless-static-
route,169.254.169.254/32,20.20.20.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1605421/+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 1592646] Re: Need to write "update user's password" on identity v2 API
** 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/1592646 Title: Need to write "update user's password" on identity v2 API Status in OpenStack Identity (keystone): New Bug description: Bug https://bugs.launchpad.net/openstack-api-site/+bug/1524147 is not fixed yet. I did not find update password API doc http://developer.openstack.org /api-ref-identity-admin-v2.html or http://developer.openstack.org /api-ref-identity-v2-ext.html To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1592646/+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 1592713] Re: wrong url for list role identity v2 API
** 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/1592713 Title: wrong url for list role identity v2 API Status in OpenStack Identity (keystone): New Bug description: Keystone has list roles API but its url is wrong here- http://developer.openstack.org/api-ref-identity-v2-ext.html#listRoles It should be '/v2.0/OS-KSADM/roles' To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1592713/+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 1592711] Re: Missing doc for "list of roles assigned to a user for a tenant" on identity v2 API
** 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/1592711 Title: Missing doc for "list of roles assigned to a user for a tenant" on identity v2 API Status in OpenStack Identity (keystone): New Bug description: Keystone has API for "list of roles assigned to a user for a tenant" - '/tenants/%s/users/%s/roles' % (tenant_id, user_id) 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/keystone/+bug/1592711/+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 1598254] Re: Networking API v2.0 (CURRENT): Create Network Request and Response missing the 'description' parameter.
** 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/1598254
Title:
Networking API v2.0 (CURRENT): Create Network Request and Response
missing the 'description' parameter.
Status in neutron:
New
Bug description:
http://developer.openstack.org/api-ref-networking-v2.html
Create Network Request and Response missing the 'description'
parameter.
localadmin@qa4:~/devstack$ neutron --debug net-create my-net
--description="My test network"
DEBUG: keystoneclient.session REQ: curl -g -i -X GET
http://172.29.85.228:5000/v2.0 -H "Accept: application/json" -H "User-Agent:
python-keystoneclient"
DEBUG: keystoneclient.session RESP: [200] Content-Length: 339 Vary:
X-Auth-Token Keep-Alive: timeout=5, max=100 Server: Apache/2.4.7 (Ubuntu)
Connection: Keep-Alive Date: Fri, 01 Jul 2016 14:20:33 GMT Content-Type:
application/json x-openstack-request-id:
req-137144d2-eb76-4eb7-aa4b-808f2d1c69d9
RESP BODY: {"version": {"status": "stable", "updated":
"2014-04-17T00:00:00Z", "media-types": [{"base": "application/json", "type":
"application/vnd.openstack.identity-v2.0+json"}], "id": "v2.0", "links":
[{"href": "http://172.29.85.228:5000/v2.0/";, "rel": "self"}, {"href":
"http://docs.openstack.org/";, "type": "text/html", "rel": "describedby"}]}}
DEBUG: stevedore.extension found extension EntryPoint.parse('table =
cliff.formatters.table:TableFormatter')
DEBUG: stevedore.extension found extension EntryPoint.parse('json =
cliff.formatters.json_format:JSONFormatter')
DEBUG: stevedore.extension found extension EntryPoint.parse('shell =
cliff.formatters.shell:ShellFormatter')
DEBUG: stevedore.extension found extension EntryPoint.parse('value =
cliff.formatters.value:ValueFormatter')
DEBUG: stevedore.extension found extension EntryPoint.parse('yaml =
cliff.formatters.yaml_format:YAMLFormatter')
DEBUG: stevedore.extension found extension EntryPoint.parse('html =
clifftablib.formatters:HtmlFormatter')
DEBUG: neutronclient.neutron.v2_0.network.CreateNetwork
get_data(Namespace(admin_state=True, columns=[], formatter='table',
max_width=0, name=u'my-net', noindent=False, prefix='',
provider:network_type=None, provider:physical_network=None,
provider:segmentation_id=None, qos_policy=None, request_format='json',
tenant_id=None, variables=[]))
DEBUG: keystoneclient.auth.identity.v2 Making authentication request to
http://172.29.85.228:5000/v2.0/tokens
DEBUG: stevedore.extension found extension EntryPoint.parse('router_scheduler
= neutronclient.neutron.v2_0.cisco.routerscheduler')
DEBUG: stevedore.extension found extension EntryPoint.parse('hosting_devices
= neutronclient.neutron.v2_0.cisco.hostingdevice')
DEBUG: stevedore.extension found extension EntryPoint.parse('router_types =
neutronclient.neutron.v2_0.cisco.routertype')
DEBUG: stevedore.extension found extension
EntryPoint.parse('hosting_device_scheduler =
neutronclient.neutron.v2_0.cisco.hostingdevicescheduler')
DEBUG: stevedore.extension found extension
EntryPoint.parse('hosting_device_templates =
neutronclient.neutron.v2_0.cisco.hostingdevicetemplate')
DEBUG: stevedore.extension found extension EntryPoint.parse('hosting_devices
= networking_cisco.neutronclient.hostingdevice')
DEBUG: stevedore.extension found extension EntryPoint.parse('router_types =
networking_cisco.neutronclient.routertype')
DEBUG: stevedore.extension found extension EntryPoint.parse('policy_profile =
networking_cisco.neutronclient.policyprofile')
DEBUG: stevedore.extension found extension
EntryPoint.parse('hosting_device_templates =
networking_cisco.neutronclient.hostingdevicetemplate')
DEBUG: stevedore.extension found extension EntryPoint.parse('router_scheduler
= networking_cisco.neutronclient.routerscheduler')
DEBUG: stevedore.extension found extension EntryPoint.parse('network_profile
= networking_cisco.neutronclient.networkprofile')
DEBUG: stevedore.extension found extension
EntryPoint.parse('hosting_device_scheduler =
networking_cisco.neutronclient.hostingdevicescheduler')
DEBUG: keystoneclient.session REQ: curl -g -i -X POST
http://172.29.85.228:9696/v2.0/networks.json -H "User-Agent:
python-neutronclient" -H "Content-Type: application/json" -H "Accept:
application/json" -H "X-Auth-Token:
{SHA1}a7c5442d73f1424784bea97819b8d2b7d8295257" -d '{"network": {"description":
"My test network", "name": "my-net", "admin_state_up": true}}'
DEBUG: keystoneclient.session RESP: [201] Date: Fri, 01 Jul 2016 14:20:34 GMT
Connection: keep-alive Content-Type: application/json; charset=UTF-8
Content-Length: 613 X-Openstack-Request-Id:
req-1046640c-3a4f-4fb1-b03d-ed53ad812049
RESP BODY: {"network": {"status": "ACTIVE", "router:external": false,
"availability_zone_hints": [], "availability_zones": [], "description": "My
test network", "provider:physical_network":
[Yahoo-eng-team] [Bug 1598219] Re: Networking API v2.0 (CURRENT): Create subnet Request parameters missing the 'no-gateway' option.
** 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/1598219
Title:
Networking API v2.0 (CURRENT): Create subnet Request parameters
missing the 'no-gateway' option.
Status in neutron:
In Progress
Bug description:
http://developer.openstack.org/api-ref-networking-v2.html
Create subnet Request parameters missing the 'no-gateway' option.
localadmin@qa4:~/devstack$ neutron subnet-create --help
usage: neutron subnet-create [-h] [-f {html,json,shell,table,value,yaml}]
[-c COLUMN] [--max-width ] [--noindent]
[--prefix PREFIX] [--request-format {json,xml}]
[--tenant-id TENANT_ID] [--name NAME]
[--gateway GATEWAY_IP | --no-gateway]
<
[--allocation-pool start=IP_ADDR,end=IP_ADDR]
[--host-route destination=CIDR,nexthop=IP_ADDR]
[--dns-nameserver DNS_NAMESERVER]
[--disable-dhcp] [--enable-dhcp]
[--ip-version {4,6}]
[--ipv6-ra-mode
{dhcpv6-stateful,dhcpv6-stateless,slaac}]
[--ipv6-address-mode
{dhcpv6-stateful,dhcpv6-stateless,slaac}]
[--subnetpool SUBNETPOOL]
[--prefixlen PREFIX_LENGTH]
NETWORK [CIDR]
Create a subnet for a given tenant.
positional arguments:
NETWORK Network ID or name this subnet belongs to.
CIDR CIDR of subnet to create.
optional arguments:
-h, --helpshow this help message and exit
--request-format {json,xml}
The XML or JSON request format.
--tenant-id TENANT_ID
The owner tenant ID.
--name NAME Name of this subnet.
--gateway GATEWAY_IP Gateway IP of this subnet.
--no-gateway No distribution of gateway.
localadmin@qa4:~/devstack$ neutron --debug subnet-create --name my-subnet
--no-gateway <<< my-net 1.1.1.0/24
DEBUG: keystoneclient.session REQ: curl -g -i -X GET
http://172.29.85.228:5000/v2.0 -H "Accept: application/json" -H "User-Agent:
python-keystoneclient"
DEBUG: keystoneclient.session RESP: [200] Content-Length: 339 Vary:
X-Auth-Token Keep-Alive: timeout=5, max=100 Server: Apache/2.4.7 (Ubuntu)
Connection: Keep-Alive Date: Fri, 01 Jul 2016 14:57:31 GMT Content-Type:
application/json x-openstack-request-id:
req-47f66134-62d8-4cf8-a979-99eacbdb1069
RESP BODY: {"version": {"status": "stable", "updated":
"2014-04-17T00:00:00Z", "media-types": [{"base": "application/json", "type":
"application/vnd.openstack.identity-v2.0+json"}], "id": "v2.0", "links":
[{"href": "http://172.29.85.228:5000/v2.0/";, "rel": "self"}, {"href":
"http://docs.openstack.org/";, "type": "text/html", "rel": "describedby"}]}}
DEBUG: stevedore.extension found extension EntryPoint.parse('table =
cliff.formatters.table:TableFormatter')
DEBUG: stevedore.extension found extension EntryPoint.parse('json =
cliff.formatters.json_format:JSONFormatter')
DEBUG: stevedore.extension found extension EntryPoint.parse('shell =
cliff.formatters.shell:ShellFormatter')
DEBUG: stevedore.extension found extension EntryPoint.parse('value =
cliff.formatters.value:ValueFormatter')
DEBUG: stevedore.extension found extension EntryPoint.parse('yaml =
cliff.formatters.yaml_format:YAMLFormatter')
DEBUG: stevedore.extension found extension EntryPoint.parse('html =
clifftablib.formatters:HtmlFormatter')
DEBUG: neutronclient.neutron.v2_0.subnet.CreateSubnet
get_data(Namespace(allocation_pools=None, cidr=u'1.1.1.0/24', columns=[],
disable_dhcp=False, dns_nameservers=None, enable_dhcp=False, formatter='table',
gateway=None, host_routes=None, ip_version=4, ipv6_address_mode=None,
ipv6_ra_mode=None, max_width=0, name=u'my-subnet', network_id=u'my-net',
no_gateway=True, noindent=False, prefix='', prefixlen=None,
request_format='json', subnetpool=None, tenant_id=None, variables=[]))
DEBUG: keystoneclient.auth.identity.v2 Making authentication request to
http://172.29.85.228:5000/v2.0/tokens
DEBUG: stevedore.extension found extension EntryPoint.parse('router_scheduler
= neutronclient.neutron.v2_0.cisco.routerscheduler')
DEBUG: stevedore.extension found extension EntryPoint.parse('hosting_devices
= neutronclient.neutron.v2_0.cisco.hostingdevice')
DEBUG: stevedore.extension found extension EntryPoint.parse('router_types =
neutronclient.neutron.v2_0.cisco.routertype')
DEBUG: stevedore.extension found extension
EntryPoint.parse('hosting_device_scheduler =
neutronclient.neutron.v2_0.cisco.hostingdevicescheduler')
DEBUG: steve
[Yahoo-eng-team] [Bug 1462152] Re: python-memcache (and therefore) token memcache persistence driver does not support ipv6
Kilo EOL'd ** Changed in: openstack-manuals Status: Confirmed => Won't Fix -- 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/1462152 Title: python-memcache (and therefore) token memcache persistence driver does not support ipv6 Status in OpenStack Identity (keystone): Won't Fix Status in openstack-manuals: Won't Fix Bug description: (morganfainberg): OpenStack Manuals (for both Master and Kilo) need to be updated to eliminate the recommendation to use the memcache token persistence backend. The memcache token persistence backend is a poor choice due to performance concerns of the code itself, the fact that it is assumed that the token backend is stable storage (memcached is not) and can expose security concerns if restarted in some scenarios (PKI tokens and revoked tokens becoming valid again), and finally that the python-memcache library is all around poor (it will not work with IPv6 and is not Python3 compatible, among other poor design choices). The memcache backend driver that utilizes "python-memcache" does not support IPv6. I have included three scenarios (A, B and C) that will reproduce the bug and a control test that succeeds with same configuration using IPv4-resolving hostname. To reproduce scenario A: Bare IPv6 address in config 1) Configure keystone according to http://docs.openstack.org/kilo/install-guide/install/apt/content/keystone-install.html 2) In section [memcache] in /etc/keystone/keystone.conf change servers = line: servers = 2001:db8:1000:1:f816:3eff:fe2a:f9c7:11211,2001:db8:1000:1:f816:3eff:fee9:9ce3:11211,2001:db8:1000:1:f816:3eff:fead:8f7f:11211 3) Restart keystone/apache 4) Attempt to issue token: openstack --os-auth-url http://192.168.0.15:35357 --os-project-name admin --os-username admin --os-auth-type password token issue ERROR: openstack An unexpected error prevented the server from fulfilling your request: Unable to parse connection string: "2001:db8:1000:1:f816:3eff:fe2a:f9c7:11211" (Disable debug mode to suppress these details.) (HTTP 500) (Request-ID: req-7c2bfd39-4b83 -462b-92c6-f75f7677c8e5) To reproduce scenario B: IPv6 address enclosed in brackets 1) Configure keystone according to http://docs.openstack.org/kilo/install-guide/install/apt/content/keystone-install.html 2) In section [memcache] in /etc/keystone/keystone.conf change servers = line: servers = [2001:db8:1000:1:f816:3eff:fe2a:f9c7]:11211,[2001:db8:1000:1:f816:3eff:fee9:9ce3]:11211,[2001:db8:1000:1:f816:3eff:fead:8f7f]:11211 3) Restart keystone/apache 4) Attempt to issue token: openstack --os-auth-url http://192.168.0.15:35357 --os-project-name admin --os-username admin --os-auth-type password token issue ERROR: openstack An unexpected error prevented the server from fulfilling your request: Unable to parse connection string: "[2001:db8:1000:1:f816:3eff:fe2a:f9c7]:11211" (Disable debug mode to suppress these details.) (HTTP 500) (Request-ID: req- 869eb953-74af-4336-b3e1-dc3a417180f9) To reproduce scenario C: hostname that resolves to IPv6-only address 1) Configure keystone according to http://docs.openstack.org/kilo/install-guide/install/apt/content/keystone-install.html 2) In section [memcache] in /etc/keystone/keystone.conf change servers = line: servers = keystone-1:11211,keystone-2:11211,keystone-3:11211 3) Edit /etc/hosts: 2001:db8:1000:1:f816:3eff:fe2a:f9c7 keystone-1 2001:db8:1000:1:f816:3eff:fee9:9ce3 keystone-2 2001:db8:1000:1:f816:3eff:fead:8f7f keystone-3 3) Restart keystone/apache 4) Attempt to issue token: openstack --os-auth-url http://192.168.0.15:35357 --os-project-name admin --os-username admin --os-auth-type password token issue Password: ERROR: openstack Maximum lock attempts on _lockusertokens-30dbbe8174b24174a3a24d1ae554ab17 occurred. (Disable debug mode to suppress these details.) (HTTP 500) (Request-ID: req-efd53eae-4bcf-4fd9-bab2-dd4c86fb9798) Control test: 1) Configure keystone according to http://docs.openstack.org/kilo/install-guide/install/apt/content/keystone-install.html 2) In section [memcache] in /etc/keystone/keystone.conf change servers = line: servers = keystone-1:11211,keystone-2:11211,keystone-3:11211 3) Edit /etc/hosts: 192.168.0.15 keystone-1 192.168.0.14 keystone-2 192.168.0.16 keystone-3 3) Restart keystone/apache 4) Attempt to issue token: openstack --os-auth-url http://192.168.0.15:35357 --os-project-name admin --os-username admin --os-auth-type password token issue Password: ++--+ | Field | Value| ++--+ | expires| 2015-06-05T00:31:30Z
[Yahoo-eng-team] [Bug 1524671] Re: Added CORS support to Neutron
** Changed in: openstack-manuals Assignee: Mark (rocky-asdf) => (unassigned) ** 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 neutron. https://bugs.launchpad.net/bugs/1524671 Title: Added CORS support to Neutron Status in neutron: Fix Released Status in openstack-manuals: Fix Released Bug description: https://review.openstack.org/236988 \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 7f65b06033afca20399305f285ff5e6d43c5131c Author: Michael Krotscheck Date: Mon Oct 19 06:52:04 2015 -0700 Added CORS support to Neutron This adds the CORS support middleware to Neutron, allowing a deployer to optionally configure rules under which a javascript client may break the single-origin policy and access the API directly. For neutron, both the paste.ini and the direct-wrap method of deploying the middleware were chosen, since neutron is in a state of migration to pecan. Note that if someone deploys pecan-neutron behind other middleware, any responses provided by that middleware will not be CORS-enabled, as these responses would be returned before the headers could be annotated. This results in a response not readable by the user agent. OpenStack CrossProject Spec: http://specs.openstack.org/openstack/openstack-specs/specs/cors-support.html Oslo_Middleware Docs: http://docs.openstack.org/developer/oslo.middleware/cors.html OpenStack Cloud Admin Guide: http://docs.openstack.org/admin-guide-cloud/cross_project_cors.html DocImpact: Add link to CORS configuration in admin cloud guide. Change-Id: I02acea6124d28370d92e7c94ca2d1d6c5c8937ac To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1524671/+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
** 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 neutron. https://bugs.launchpad.net/bugs/1516073 Title: Replace subnetpool config options with admin-only API Status in neutron: Confirmed Status in openstack-manuals: Fix Released 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 1596415] Re: openstack kilo installaion guide "keytone error 500:internal server error"
Kilo EOL'd ** Changed in: openstack-manuals Status: Confirmed => Invalid -- 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/1596415 Title: openstack kilo installaion guide "keytone error 500:internal server error" Status in OpenStack Identity (keystone): Invalid Status in openstack-manuals: Invalid Bug description: Following the below link to install openstack keystone(kilo) : http://docs.openstack.org/kilo/install-guide/install/apt/content /keystone-install.html The following command is not downloading keystone.py.It is displaying some junk. Copy the WSGI components from the upstream repository into this directory: # curl http://git.openstack.org/cgit/openstack/keystone/plain/httpd/keystone.py?h=stable/kilo \ | tee /var/www/cgi-bin/keystone/main /var/www/cgi-bin/keystone/admin -- It seems no such url exists also. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1596415/+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 1548443] Re: Update ComputeNode values with disk allocation ratios in the RT
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1548443 Title: Update ComputeNode values with disk allocation ratios in the RT Status in OpenStack Compute (nova): Invalid Status in openstack-manuals: Fix Released Bug description: https://review.openstack.org/277953 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/nova" 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 ad6654eaa7c44267ae3a4952a8359459fbec4c0c Author: Sylvain Bauza Date: Tue Feb 9 17:35:47 2016 +0100 Update ComputeNode values with disk allocation ratios in the RT Now that we have added the field for persisting the disk alloc ratio, we can have the ResouceTracker persisting it by adding it to the local ComputeNode object which is persisted by calling the _update() method. It will then send by default 0.0 unless the operator explicitely specified an allocation ratio in the compute nova.conf. Thanks to the ComputeNode object hydratation on the scheduler side, the facade will make sure that if a default 0.0 is provided by either a compute node or by the scheduler's nova.conf, it will actually get the original allocation ratios (ie. 1.0 for disk) Since the Scheduler reads the same RT opt but goes thru the ComputeNode object, it will also get the Facade returning 1.0 unless the operator explicitely provided other ratios for the scheduler's nova.conf Amending the release note now that the behaviour is changing. DocImpact Disk alloc ratio is now per computenode UpgradeImpact Change-Id: Ief6fa32429d58b80e70029ed67c7f42e0bdc986d Implements: blueprint disk-allocation-ratio-to-rt To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1548443/+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 1547055] Re: libvirt: make live_migration_uri flag dependent on virt_type
** Changed in: openstack-manuals Status: Confirmed => Incomplete ** Changed in: openstack-manuals Status: Incomplete => 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/1547055 Title: libvirt: make live_migration_uri flag dependent on virt_type Status in OpenStack Compute (nova): Invalid Status in openstack-manuals: Fix Released Bug description: https://review.openstack.org/175780 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/nova" 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 3159c8fd5bea80c820e58bd38d96f5f8fe8f4503 Author: Alvaro Lopez Garcia Date: Tue Apr 21 10:39:30 2015 +0200 libvirt: make live_migration_uri flag dependent on virt_type The default value for the "live_migration_uri" flag should be dependent on the "virt_type" flag, as the "connection_uri" flag is. This way, an operator can set the "virt_type" flag without the need to check for each individual uri. DocImpact: Changed the default value of the "live_migration_uri" flag, that now is dependent on the "virt_type". Closes-Bug: #1298242 Change-Id: Id54f7bdfa14a19da41da554b13ba9496ee525c71 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1547055/+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
** Changed in: openstack-manuals Status: Fix Committed => Fix Released -- 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: Fix Released 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 1587115] Re: output parameter of show console output might be 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/1587115 Title: output parameter of show console output might be missing Status in OpenStack Compute (nova): New Bug description: The example of show console output in the web API reference [1] shows an "output" parameter. This parameter is missing from the list of parameters in the web API reference and from Chapter 4.4.10.1 of the pdf API reference [2]. [1]: http://developer.openstack.org/api-ref-compute-v2.1.html#showConsoleOutput [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/1587115/+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 1587118] Re: type is missing from the parameter list of Get serial console
** 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/1587118 Title: type is missing from the parameter list of Get serial console Status in OpenStack Compute (nova): New Bug description: According to the example Get serial console has a parameter called "type". This parameter is not listed in the Parameter list of Get serial console in the web API reference [1] and not mentioned in Chapter 4.4.12.1 of the pdf API reference [2]. In the wab API reference it is not clear that the 2nd example is for the response. Similar bug was reported in [3]. [1]: http://developer.openstack.org/api-ref-compute-v2.1.html#getSerialConsole [2]: http://api.openstack.org/api-ref-guides/bk-api-ref.pdf [3]: https://bugs.launchpad.net/openstack-api-site/+bug/1565670 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1587118/+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 1587117] Re: type is missing from the parameter list of Get RDP console
** 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/1587117 Title: type is missing from the parameter list of Get RDP console Status in OpenStack Compute (nova): New Bug description: According to the example Get RDP console has a parameter called "type". This parameter is not listed in the Parameter list of Get RDP console in the web API reference [1] and not mentioned in Chapter 4.4.11.1 of the pdf API reference [2]. In the wab API reference it is not clear that the 2nd example is for the response. Similar bug was reported in [3]. [1]: http://developer.openstack.org/api-ref-compute-v2.1.html#getRDPConsole [2]: http://api.openstack.org/api-ref-guides/bk-api-ref.pdf [3]: https://bugs.launchpad.net/openstack-api-site/+bug/1565670 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1587117/+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 1587119] Re: type is missing from the parameter list of Get SPICE console
** 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/1587119 Title: type is missing from the parameter list of Get SPICE console Status in OpenStack Compute (nova): New Bug description: According to the example Get SPICE console has a parameter called "type". This parameter is not listed in the Parameter list of Get SPICE console in the web API reference [1] and not mentioned in Chapter 4.4.13.1 of the pdf API reference [2]. In the web API reference it is not clear that the 2nd example is for the response. Similar bug was reported in [3]. [1]: http://developer.openstack.org/api-ref-compute-v2.1.html#getSPICEConsole [2]: http://api.openstack.org/api-ref-guides/bk-api-ref.pdf [3]: https://bugs.launchpad.net/openstack-api-site/+bug/1565670 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1587119/+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 1587121] Re: type is missing from the parameter list of Get VNC console
** 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/1587121 Title: type is missing from the parameter list of Get VNC console Status in OpenStack Compute (nova): New Bug description: According to the example Get VNC console has a parameter called "type". This parameter is not listed in the Parameter list of Get VNC console in the web API reference [1] and not mentioned in Chapter 4.4.14.1 of the pdf API reference [2]. In the web API reference it is not clear that the 2nd example is for the response. Similar bug was reported in [3]. [1]: http://developer.openstack.org/api-ref-compute-v2.1.html#getVNCConsole [2]: http://api.openstack.org/api-ref-guides/bk-api-ref.pdf [3]: https://bugs.launchpad.net/openstack-api-site/+bug/1565670 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1587121/+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 1587842] Re: address is missing from the parameter list of Remove (disassociate) fixed IP
** 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/1587842 Title: address is missing from the parameter list of Remove (disassociate) fixed IP Status in OpenStack Compute (nova): New Bug description: According to the example Remove (disassociate) fixed IP has a parameter called "address". This "address" 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.17 of the pdf API reference [2]. [1]: http://developer.openstack.org/api-ref-compute-v2.1.html#removeFixedIp [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/1587842/+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 1587845] Re: address is missing from the parameter list of Remove (disassociate) floating IP
** 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/1587845 Title: address is missing from the parameter list of Remove (disassociate) floating IP Status in OpenStack Compute (nova): New Bug description: According to the example Remove (disassociate) floating IP has a parameter called "address". This "address" parameter is not listed in the Parameter list of Remove (disassociate) floating IP in the web API reference [1] and not mentioned in Chapter 4.4.18 of the pdf API reference [2]. [1]: http://developer.openstack.org/api-ref-compute-v2.1.html#removeFloatingIp [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/1587845/+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 1551805] Re: add arp_responder flag to linuxbridge agent
** Changed in: openstack-manuals Assignee: Anseela M M (anseela-m00) => (unassigned) ** 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 neutron. https://bugs.launchpad.net/bugs/1551805 Title: add arp_responder flag to linuxbridge agent Status in neutron: Invalid Status in openstack-manuals: Fix Released Bug description: https://review.openstack.org/278597 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 bbd881f3a970143e1954cb277e523526c5d0 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 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1551805/+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 1561252] Re: Removing 'force_gateway_on_subnet' option
** Changed in: openstack-manuals Status: In Progress => Fix Released ** Changed in: openstack-manuals Milestone: None => mitaka ** Changed in: openstack-manuals 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/1561252 Title: Removing 'force_gateway_on_subnet' option Status in neutron: Invalid Status in openstack-manuals: Fix Released Bug description: https://review.openstack.org/295843 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 7215168b119c11a973fbdff56c007f6eb157d257 Author: Sreekumar S Date: Tue Mar 22 19:17:54 2016 +0530 Removing 'force_gateway_on_subnet' option With this fix 'force_gateway_on_subnet' configuration option is removed, and gateway outside the subnet is always allowed. Gateway cannot be forced onto to the subnet range. DocImpact: All references of 'force_gateway_on_subnet' configuration option and its description should be removed from the docs. Change-Id: I1a676f35828e46fcedf339235ef7be388341f91e Closes-Bug: #1548193 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1561252/+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 1484113] Re: network topology: Status untranslated
** Changed in: openstack-i18n Importance: Undecided => Medium ** Changed in: openstack-i18n Status: Confirmed => Fix Released -- 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/1484113 Title: network topology: Status untranslated Status in OpenStack Dashboard (Horizon): Fix Released Status in openstack i18n: Fix Released Bug description: on network_topology, the status of an instance or a router is not being translated. The green/red light left hand side of status is hard wired to the word 'ACTIVE' (if status == 'ACTIVE', then green light) To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1484113/+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 1532656] Re: Duplicated content in "Using Glance’s Image Public APIs" page
The pointed URL is the glance developer document. So, let me assign this bug to glance project. ** Project changed: openstack-manuals => 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/1532656 Title: Duplicated content in "Using Glance’s Image Public APIs" page Status in Glance: New Bug description: In "Using Glance’s Image Public APIs", the content for the section: "Retrieve Raw Image Data" (http://docs.openstack.org/developer/glance/glanceapi.html#retrieve- raw-image-data) is simply a dupe of the section: "Retrieve Image Metadata" (http://docs.openstack.org/developer/glance/glanceapi.html#retrieve- image-metadata) Please fix it with the correct documentation for retrieving image data. Here is the text-snapshot of these two sections in case the live site is not available for any reason: http://paste.openstack.org/show/483381/. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1532656/+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 1317794] Re: Complete translations are too big
** Changed in: openstack-i18n Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1317794 Title: Complete translations are too big Status in Ceilometer: Fix Released Status in Cinder: Fix Released Status in Glance: Fix Released Status in heat: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in Ironic: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in neutron: Fix Released Status in OpenStack Compute (nova): Fix Released Status in openstack-api-site: Fix Released Status in openstack i18n: Fix Released Status in openstack-manuals: Fix Released Status in Sahara: Fix Released Status in Trove: Fix Released Bug description: From http://lists.openstack.org/pipermail/openstack- i18n/2014-May/000594.html: "I've come across this review for automated translations coming into Horizon https://review.openstack.org/#/c/91523/ It concerns me that it has over a half million LOC in it, and many of these languages have near 0 translation. (I checked here: https://www.transifex.com/projects/p/horizon/). 0 translation languages have just as many lines as full translations; they are just shorter." The proposal in the thread is: 1) Our translation jobs will only download files that have at least 75 % translated 2) Projects can delete (and I'm going to propose patches) files that currently have less than 75 % translated To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1317794/+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 1325684] Re: Launch Instance dialog - "nic" should probably be capitalized on the Networking tab
** Changed in: openstack-i18n Status: New => Fix Released -- 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/1325684 Title: Launch Instance dialog - "nic" should probably be capitalized on the Networking tab Status in OpenStack Dashboard (Horizon): Fix Released Status in openstack i18n: Fix Released Bug description: On the Networking tab of the Launch Instance dialog, "nic" is all lowercase. Generally acronyms are capitalized. "nic" is used both for each interface, and in the description on the right pane. Somewhat related to that, on the same dialog and tab, we say "Selected Networks" and underneath that, "Available networks", which don't follow the same capitalization conventions. "Available Networks" would match what seems to be used elsewhere in the UI. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1325684/+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 1255004] Re: I18n: Localization of the role "Member"
** Changed in: openstack-i18n Status: Fix Committed => Fix Released -- 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/1255004 Title: I18n: Localization of the role "Member" Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Dashboard (Horizon) havana series: Fix Released Status in openstack i18n: Fix Released Bug description: Hi, There is a very strange thing happened to role "Member" when I set Horizon to use my local language. In the dialog "Domain Groups", it is translated. But in the dialog of "Project Members" and "Project Groups", it is not translated. From my point of view, if we can localize role names, it will be wonderful. If we are not able to localize role names, it is acceptable. But we need to make them consistent. Hope somebody can take a look at this interested issue. Thanks. Daisy To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1255004/+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
