[Yahoo-eng-team] [Bug 1666424] [NEW] cleanup overrides of resource operations in ML2
Public bug reported: In an effort to simplify the code-base and provide a consistent way to handle resource life-cycles. I think we should eliminate cases in the ML2 plugin where it is overriding a method of db_base_plugin_v2 where possible by leveraging the callback events for resources (BEFORE_CREATE/PRECOMMIT_CREATE/etc). ** Affects: neutron Importance: Wishlist Status: New ** Changed in: neutron Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1666424 Title: cleanup overrides of resource operations in ML2 Status in neutron: New Bug description: In an effort to simplify the code-base and provide a consistent way to handle resource life-cycles. I think we should eliminate cases in the ML2 plugin where it is overriding a method of db_base_plugin_v2 where possible by leveraging the callback events for resources (BEFORE_CREATE/PRECOMMIT_CREATE/etc). To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1666424/+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 1665967] Re: rally timeouts and poor subnet_update performance
Reviewed: https://review.openstack.org/435748 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=bc306a5512dc7d46737f1822cd2f827f87b95f9c Submitter: Jenkins Branch:master commit bc306a5512dc7d46737f1822cd2f827f87b95f9c Author: Kevin BentonDate: Sat Feb 18 21:25:30 2017 -0800 Avoid loading network and all rels for subnet query The Subnet model has a relationship to Network that is only used for bumping the revision of the network. However, loading the network loads all of its relationships as well so we end up wasting a bunch of time loading segments, DHCP agents, etc all for no reason. During a subnet update, we get the subnet from the DB several times (policy engine, before update, after update, and dhcp agent scheduler) so the slowness in get_subnet is amplified. The recent switch to subqueries[1] has made loading all of this unrelated data much more expensive since each relationship requires a query, which was likely what brought this problem to the surface. This adjusts the relationship to just load the standard attr object of the network directly so we can still bump the revision of the network without having to load the network itself. This resulted in a ~20%-30% reduction of time spent in single update-subnet operations on my dev environment (1sec to 650-850ms). 1. I6952c48236153a8e2f2f155375b70573ddc2cf0f Closes-Bug: #1665967 Change-Id: Ie5f956ddf0704a5dde6e4f801a446f48fea5f697 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1665967 Title: rally timeouts and poor subnet_update performance Status in neutron: Fix Released Bug description: Subnet updates are very expensive in the rally runs (compared to net and subnet creates). On the create and update subnet scenario we do 400 iterations with 2 subnet updates each. Each update is averaging a cost of 8 seconds. With two concurrent runners, we end up spending 10 minutes on this single task. This is likely leading to many of the rally timeouts. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1665967/+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 1657174] Re: The filesizeformat() method does not consider the situation like `float('inf')` or EB, ZB and YB.
Reviewed: https://review.openstack.org/421352 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=9886be592f6fd1ec5af91f7ef9de76e27d0e083f Submitter: Jenkins Branch:master commit 9886be592f6fd1ec5af91f7ef9de76e27d0e083f Author: liaozdDate: Wed Jan 18 00:20:04 2017 +0800 filesizeformat() does't consider the situation like `float('inf')` Sometimes the `bytes` may get float('inf'), then it will display "inf0PB" which will be a misleading for the user. Besides, with the hardware like storage and MEM getting larger and larger, we should consider size larger than PB like EB, ZB and YB. Change-Id: I830ad440e9ef854006298bd946ab8ecf9d75757a Closes-Bug: 1657174 ** Changed in: horizon Status: In Progress => 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/1657174 Title: The filesizeformat() method does not consider the situation like `float('inf')` or EB, ZB and YB. Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Sometimes the `bytes` may get float('inf'), then it will display "inf0PB" which will be a misleading for the user. Besides, with the hardware like storage and mem getting larger, we should consider size larger than PB like EB, ZB and YB. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1657174/+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 1664500] Re: OpenStack Profiler setup doc is formatted poorly
Reviewed: https://review.openstack.org/433576 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=4f487b7cb9da6976f1c9c0e92d764218711ab481 Submitter: Jenkins Branch:master commit 4f487b7cb9da6976f1c9c0e92d764218711ab481 Author: Rob CresswellDate: Tue Feb 14 10:36:54 2017 + Tidy up the Profiler docs This patch fixes the auto enumerated formatting for the profiler setup steps, as well as cleaning up some of the text formatting and language. Change-Id: I4a7f109e87a274ab85d67e6691a53a085c16f04f Closes-bug: 1664500 ** Changed in: horizon Status: In Progress => 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/1664500 Title: OpenStack Profiler setup doc is formatted poorly Status in OpenStack Dashboard (Horizon): Fix Released Bug description: See http://docs.openstack.org/developer/horizon/contributing.html #profiling-pages The numerical steps are formatted incorrectly, making it difficult to read. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1664500/+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 1646394] Re: Slowness on access & security page due to calls to neutron/ports.json?tenant_id=XXXXX
The Access and Security panel was split up and the result is that the API call in question is no longer called when not necessary, and it's not ever called twice. ** Changed in: horizon Status: New => Confirmed ** Changed in: horizon Status: Confirmed => Invalid -- 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/1646394 Title: Slowness on access & security page due to calls to neutron/ports.json?tenant_id=X Status in OpenStack Dashboard (Horizon): Invalid Bug description: When opening the access & security page in Horizon we experience some extreme slowness for tenants with a large amount of instances (200+). Looking at the debug logs the following calls take over 5 seconds: https://neutron/v2.0/ports.json?tenant_id=X This call is done twice for this page. Since there are no interfaces shown on this page I am wondering why this call is being done at all. Doing it twice makes the problem worse. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1646394/+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 1516848] Re: Volume size units should be in GiB, not GB
As was pointed out in the patch mentioned above, Flavors are measured in GB, not GiB. ** Changed in: horizon Status: New => Invalid -- 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/1516848 Title: Volume size units should be in GiB, not GB Status in OpenStack Dashboard (Horizon): Invalid Bug description: Data size on storage devices is typically measured in GiB (2^30), and not GB (10^9). The Cinder community has addressed this issue by changing all of their CLI and Horizon panels to use "GiB" (see https://bugs.launchpad.net/horizon/+bug/1511167) There are several Nova panels that display/request data sizes that should also be changed for consistency: Project -> Instances -> Launch Instance Project -> Instances -> table colums Admin -> Flavors -> Create Flavor Admin -> Flavors -> table columns To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1516848/+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 1645168] Re: Incorrect volume storage unit shown on overview panel
The value displayed is gigabytes, not gibibytes, so the label is correct. ** Changed in: horizon Status: New => Invalid -- 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/1645168 Title: Incorrect volume storage unit shown on overview panel Status in OpenStack Dashboard (Horizon): Invalid Bug description: On the overview panel, the unit shown under the Volume Storage chart is GB. The correct unit for volume storage is gibibyte(GiB) as shown on the volumes panel. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1645168/+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 1630833] Re: Horizon image upload via URL fails with "TypeError: Cannot read property 'data' of undefined"
I'm reopening this as I believe the error message should be much clearer since this is a pretty easy error to get (the configuration of this is not presented very clearly and it's easy to get wrong). ** Changed in: horizon Status: Invalid => Triaged ** Changed in: horizon Importance: Undecided => Medium ** Tags added: low-hanging-fruit ** Changed in: horizon Milestone: None => pike-1 -- 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/1630833 Title: Horizon image upload via URL fails with "TypeError: Cannot read property 'data' of undefined" Status in OpenStack Dashboard (Horizon): Triaged Bug description: We have deployed Newton, and trying to upload image via URL on horizon , however it fails on horizon displaying : "TypeError: Cannot read property 'data' of undefined" However, in Chrome developer mode i see this : https://10.240.128.120/horizon/api/glance/images/ Failed to load resource: the server responded with a status of 403 (FORBIDDEN) i have tried all settings for HORIZON_IMAGES_UPLOAD_MODE as True, False, legacy and direct, and for all settings i get same error. Rest assured , my cors settings for glance look fine. In glance-api.conf: [cors] allowed_origin = https://10.240.128.120/horizon,https://10.240.128.120 allow_methods=GET,POST,PUT,DELETE Also in glance-api-paste.ini: [filter:cors] paste.filter_factory = oslo_middleware.cors:filter_factory allowed_origin = https://10.240.128.120/horizon,https://10.240.128.120 allow_methods=GET,POST,PUT,DELETE the screenshots might help understand better where the problem lies. http://imgur.com/a/nmypx A quick google search of "TypeError: Cannot read property 'data' of undefined" reveals its related to angular JS however we cannot confirm where exactly the error is happening. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1630833/+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 1666252] Re: vpnaas doc build warning
Reviewed: https://review.openstack.org/436080 Committed: https://git.openstack.org/cgit/openstack/neutron-vpnaas/commit/?id=cdd940f11dcf476e1ce2153f8ab54db977d4bb93 Submitter: Jenkins Branch:master commit cdd940f11dcf476e1ce2153f8ab54db977d4bb93 Author: YAMAMOTO TakashiDate: Mon Feb 20 10:43:41 2017 -0500 doc: Fix a warning Closes-Bug: #1666252 Change-Id: I99c347eeb040a1a35ffd8fe9498f08d4d9a39b3d ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1666252 Title: vpnaas doc build warning Status in neutron: Fix Released Bug description: Warning, treated as error: /Users/yamamoto/git/neutron-vpnaas/doc/source/devref/vpnaas-tempest-test.rst:: WARNIN G: document isn't included in any toctree To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1666252/+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 1658868] Re: Should raise retry limit exceed error instead of class exist in Placement API
Reviewed: https://review.openstack.org/428612 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f2bb08ed6a114a2ceb4ff958db50485fd20c8206 Submitter: Jenkins Branch:master commit f2bb08ed6a114a2ceb4ff958db50485fd20c8206 Author: Kevin_ZhengDate: Tue Jan 24 15:12:51 2017 +0800 Raise correct error instead of class exist in Placement API When create resource class using placement API, and at the DB layer, we have a retry logic for 100 loop, and error will raise when the retry limit exceed, currently a log about limit exceed is generated but a ResourceClassExists Error is raised, which is a little bit weird and might confuse the users. We'd better add a particular Exception for this kind of scenario and it could be used in other places also. Co-Authored-By: huangtian...@huawei.com Closes-Bug: #1658868 Change-Id: I89156be82ad520bdeacb12b31b44e7170b77ce3f ** Changed in: nova 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/1658868 Title: Should raise retry limit exceed error instead of class exist in Placement API Status in OpenStack Compute (nova): Fix Released Bug description: When create resource class using placement API, and at the DB layer, we have a retry logic for 100 loop, and error will raise when the retry limit exceed, currently a log about limit exceed is generated but a ResourceClassExists Error is raised, which is a little bit wired and might confusing the users. We'd better add a particular Exception for this kind of scenario and it could be used in other places also. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1658868/+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 1666252] [NEW] vpnaas doc build warning
Public bug reported: Warning, treated as error: /Users/yamamoto/git/neutron-vpnaas/doc/source/devref/vpnaas-tempest-test.rst:: WARNIN G: document isn't included in any toctree ** Affects: neutron Importance: Undecided Assignee: YAMAMOTO Takashi (yamamoto) Status: In Progress ** Changed in: neutron Status: New => In Progress ** Changed in: neutron Assignee: (unassigned) => YAMAMOTO Takashi (yamamoto) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1666252 Title: vpnaas doc build warning Status in neutron: In Progress Bug description: Warning, treated as error: /Users/yamamoto/git/neutron-vpnaas/doc/source/devref/vpnaas-tempest-test.rst:: WARNIN G: document isn't included in any toctree To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1666252/+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