[Yahoo-eng-team] [Bug 1376492] [NEW] Minesweeper failure: tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON.test_resize_server_revert
Public bug reported: Patch I7598afbf0dc3c527471af34224003d28e64daaff introduces a tempest failure with Minesweeper due to the fact that the destroy operation can be triggered by both the user and the revert resize operation. In case of a revert resize operation, we do not want to delete the original VM. ** Affects: nova Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: In Progress ** Changed in: nova Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- 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/1376492 Title: Minesweeper failure: tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON.test_resize_server_revert Status in OpenStack Compute (Nova): In Progress Bug description: Patch I7598afbf0dc3c527471af34224003d28e64daaff introduces a tempest failure with Minesweeper due to the fact that the destroy operation can be triggered by both the user and the revert resize operation. In case of a revert resize operation, we do not want to delete the original VM. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1376492/+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 1372672] [NEW] VMware: 'NoneType' object has no attribute 'keys' in the driver
Public bug reported:
There are a couple of places in the driver where we use the keys()
function without checking for None.
I have seen several times the following exception:
2014-09-22 11:45:07.312 ERROR nova.openstack.common.periodic_task [-] Error
during ComputeManager.update_available_resource: 'NoneType' object has no
attribute 'keys'
2014-09-22 11:45:07.312 TRACE nova.openstack.common.periodic_task Traceback
(most recent call last):
2014-09-22 11:45:07.312 TRACE nova.openstack.common.periodic_task File
"/opt/stack/nova/nova/openstack/common/periodic_task.py", line 198, in
run_periodic_tasks
2014-09-22 11:45:07.312 TRACE nova.openstack.common.periodic_task
task(self, context)
2014-09-22 11:45:07.312 TRACE nova.openstack.common.periodic_task File
"/opt/stack/nova/nova/compute/manager.py", line 5909, in
update_available_resource
2014-09-22 11:45:07.312 TRACE nova.openstack.common.periodic_task nodenames
= set(self.driver.get_available_nodes())
2014-09-22 11:45:07.312 TRACE nova.openstack.common.periodic_task File
"/opt/stack/nova/nova/virt/vmwareapi/driver.py", line 426, in
get_available_nodes
2014-09-22 11:45:07.312 TRACE nova.openstack.common.periodic_task
self._update_resources()
2014-09-22 11:45:07.312 TRACE nova.openstack.common.periodic_task File
"/opt/stack/nova/nova/virt/vmwareapi/driver.py", line 306, in _update_resources
2014-09-22 11:45:07.312 TRACE nova.openstack.common.periodic_task
added_nodes = set(self.dict_mors.keys()) - set(self._resource_keys)
2014-09-22 11:45:07.312 TRACE nova.openstack.common.periodic_task
AttributeError: 'NoneType' object has no attribute 'keys'
** Affects: nova
Importance: Low
Assignee: Arnaud Legendre (arnaudleg)
Status: Confirmed
** Changed in: nova
Assignee: (unassigned) => Arnaud Legendre (arnaudleg)
** Changed in: nova
Importance: Undecided => Medium
--
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/1372672
Title:
VMware: 'NoneType' object has no attribute 'keys' in the driver
Status in OpenStack Compute (Nova):
Confirmed
Bug description:
There are a couple of places in the driver where we use the keys()
function without checking for None.
I have seen several times the following exception:
2014-09-22 11:45:07.312 ERROR nova.openstack.common.periodic_task [-] Error
during ComputeManager.update_available_resource: 'NoneType' object has no
attribute 'keys'
2014-09-22 11:45:07.312 TRACE nova.openstack.common.periodic_task Traceback
(most recent call last):
2014-09-22 11:45:07.312 TRACE nova.openstack.common.periodic_task File
"/opt/stack/nova/nova/openstack/common/periodic_task.py", line 198, in
run_periodic_tasks
2014-09-22 11:45:07.312 TRACE nova.openstack.common.periodic_task
task(self, context)
2014-09-22 11:45:07.312 TRACE nova.openstack.common.periodic_task File
"/opt/stack/nova/nova/compute/manager.py", line 5909, in
update_available_resource
2014-09-22 11:45:07.312 TRACE nova.openstack.common.periodic_task
nodenames = set(self.driver.get_available_nodes())
2014-09-22 11:45:07.312 TRACE nova.openstack.common.periodic_task File
"/opt/stack/nova/nova/virt/vmwareapi/driver.py", line 426, in
get_available_nodes
2014-09-22 11:45:07.312 TRACE nova.openstack.common.periodic_task
self._update_resources()
2014-09-22 11:45:07.312 TRACE nova.openstack.common.periodic_task File
"/opt/stack/nova/nova/virt/vmwareapi/driver.py", line 306, in _update_resources
2014-09-22 11:45:07.312 TRACE nova.openstack.common.periodic_task
added_nodes = set(self.dict_mors.keys()) - set(self._resource_keys)
2014-09-22 11:45:07.312 TRACE nova.openstack.common.periodic_task
AttributeError: 'NoneType' object has no attribute 'keys'
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1372672/+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 1369019] [NEW] VMware: need to support inventory folders
Public bug reported: The VMware driver is failing to transfer images to datastores if the datacenter is inside inventory folders. This is due to the fact that the HTTP url needs to contain the folders to access the datacenter (datacenter path). ** Affects: nova Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: New ** Changed in: nova Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- 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/1369019 Title: VMware: need to support inventory folders Status in OpenStack Compute (Nova): New Bug description: The VMware driver is failing to transfer images to datastores if the datacenter is inside inventory folders. This is due to the fact that the HTTP url needs to contain the folders to access the datacenter (datacenter path). To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1369019/+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 1352509] [NEW] RBD store: need to use READ_CHUNKSIZE in the ImageIterator
Public bug reported: See https://bugs.launchpad.net/glance/+bug/1336168 Change 4e0c563b8f3a5ced8f65fcca83d341a97729a5d4 was incomplete and missed a variable in the RBD store. ** 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/1352509 Title: RBD store: need to use READ_CHUNKSIZE in the ImageIterator Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: See https://bugs.launchpad.net/glance/+bug/1336168 Change 4e0c563b8f3a5ced8f65fcca83d341a97729a5d4 was incomplete and missed a variable in the RBD store. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1352509/+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 1350010] [NEW] VMware: re-use session token
Public bug reported: Currently, we generate a session token for each API call. Since the token generation can take some time, each API call is seeing some overhead which makes Glance slower than it should be. ** Affects: glance Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: In Progress ** Tags: vmware ** Tags added: vmware ** Changed in: glance Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1350010 Title: VMware: re-use session token Status in OpenStack Image Registry and Delivery Service (Glance): In Progress Bug description: Currently, we generate a session token for each API call. Since the token generation can take some time, each API call is seeing some overhead which makes Glance slower than it should be. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1350010/+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 1340340] [NEW] 3 tempest.thirdparty.boto.* tests fail
Public bug reported: tempest.thirdparty.boto.test_ec2_security_groups.EC2SecurityGroupTest.test_create_authorize_security_group tempest.thirdparty.boto.test_ec2_volumes.EC2VolumesTest.test_create_get_delete tempest.thirdparty.boto.test_ec2_volumes.EC2VolumesTest.test_create_volume_from_snapshot with the following error: BotoServerError: BotoServerError: 500 Internal Server Error OperationalErrorUnknown error occurred.req-af61466b-dc4b-4d33-8ca7-8a25543dc246 full log: http://logs.openstack.org/89/89989/9/gate/gate-tempest-dsvm- postgres-full/bc0e2b8/console.html ** Affects: nova Importance: Undecided Status: New ** Tags: ec2 ** Tags added: ec2 -- 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/1340340 Title: 3 tempest.thirdparty.boto.* tests fail Status in OpenStack Compute (Nova): New Bug description: tempest.thirdparty.boto.test_ec2_security_groups.EC2SecurityGroupTest.test_create_authorize_security_group tempest.thirdparty.boto.test_ec2_volumes.EC2VolumesTest.test_create_get_delete tempest.thirdparty.boto.test_ec2_volumes.EC2VolumesTest.test_create_volume_from_snapshot with the following error: BotoServerError: BotoServerError: 500 Internal Server Error OperationalErrorUnknown error occurred.req-af61466b-dc4b-4d33-8ca7-8a25543dc246 full log: http://logs.openstack.org/89/89989/9/gate/gate-tempest-dsvm- postgres-full/bc0e2b8/console.html To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1340340/+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 1338795] [NEW] VMware store: upload and download performance need to be improved
Public bug reported: It takes too much time to upload to the VMware store. The bits are uploaded to Glance then go through vCenter, then through ESXi to finally land on the datastore. The upload time is not necessarily good, also uploading through vCenter adds unnecessary load on the vCenter server. Since VC 5.5, it is possible to get a ticket from VC to upload to a specific host directly. This way, we bypass vCenter which makes the upload much faster. ** Affects: glance Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: In Progress ** Changed in: glance Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1338795 Title: VMware store: upload and download performance need to be improved Status in OpenStack Image Registry and Delivery Service (Glance): In Progress Bug description: It takes too much time to upload to the VMware store. The bits are uploaded to Glance then go through vCenter, then through ESXi to finally land on the datastore. The upload time is not necessarily good, also uploading through vCenter adds unnecessary load on the vCenter server. Since VC 5.5, it is possible to get a ticket from VC to upload to a specific host directly. This way, we bypass vCenter which makes the upload much faster. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1338795/+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 1336970] [NEW] VMware store to use content-length when available
Public bug reported: commit cb93eb60abf10af6fbb1ee438a6e8a51853e6788 changed the VMware store to use chunked encoding when the size is not known (or zero). We still need to use Content-Length when we know the image size. ** Affects: glance Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: New ** Changed in: glance Assignee: (unassigned) => Arnaud Legendre (arnaudleg) ** Description changed: - commit cb93eb60abf10af6fbb1ee438a6e8a51853e6788 changed the Glance store to use chunked encoding when the size is not known (or zero). + commit cb93eb60abf10af6fbb1ee438a6e8a51853e6788 changed the VMware store to use chunked encoding when the size is not known (or zero). We still need to use Content-Length when we know the image size. -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1336970 Title: VMware store to use content-length when available Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: commit cb93eb60abf10af6fbb1ee438a6e8a51853e6788 changed the VMware store to use chunked encoding when the size is not known (or zero). We still need to use Content-Length when we know the image size. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1336970/+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 1336168] [NEW] Chunksize should be configurable when using copy_from
Public bug reported: When using the copy_from option, readers and writers can have different speeds to respectively read and write. A reader can timeout if the connection has been opened for too long without getting any heartbeat. This is happening if the writer is slower than the reader. A reader will have to wait for the writer to process all the bits sent before getting the next chunk. If this time to process the bits is too long the reader will timeout. Consequently, the writer should be able to control the size of the chunks that needs to be read in order to be able to write fast enough. ** Affects: glance Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: In Progress ** Changed in: glance Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1336168 Title: Chunksize should be configurable when using copy_from Status in OpenStack Image Registry and Delivery Service (Glance): In Progress Bug description: When using the copy_from option, readers and writers can have different speeds to respectively read and write. A reader can timeout if the connection has been opened for too long without getting any heartbeat. This is happening if the writer is slower than the reader. A reader will have to wait for the writer to process all the bits sent before getting the next chunk. If this time to process the bits is too long the reader will timeout. Consequently, the writer should be able to control the size of the chunks that needs to be read in order to be able to write fast enough. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1336168/+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 1336167] [NEW] Chunksize should be configurable when using copy_from
Public bug reported: When using the copy_from option, readers and writers can have different speeds to respectively read and write. A reader can timeout if the connection has been opened for too long without getting any heartbeat. This is happening if the writer is slower than the reader. A reader will have to wait for the writer to process all the bits sent before getting the next chunk. If this time to process the bits is too long the reader will timeout. Consequently, the writer should be able to control the size of the chunks that needs to be read in order to be able to write fast enough. ** 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/1336167 Title: Chunksize should be configurable when using copy_from Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: When using the copy_from option, readers and writers can have different speeds to respectively read and write. A reader can timeout if the connection has been opened for too long without getting any heartbeat. This is happening if the writer is slower than the reader. A reader will have to wait for the writer to process all the bits sent before getting the next chunk. If this time to process the bits is too long the reader will timeout. Consequently, the writer should be able to control the size of the chunks that needs to be read in order to be able to write fast enough. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1336167/+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 1331321] [NEW] VMware: iSCSI static target needs to be removed from all hosts
Public bug reported: iSCSI static targets need to be removed from all hosts of the cluster asynchronously on detach volume. ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1331321 Title: VMware: iSCSI static target needs to be removed from all hosts Status in OpenStack Compute (Nova): New Bug description: iSCSI static targets need to be removed from all hosts of the cluster asynchronously on detach volume. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1331321/+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 1330758] [NEW] VMware: iSCSI targets needs to be propagated to all hosts of the cluster
Public bug reported: With current state of the codebase, vMotion will be a no-op if a VM has a RDM to a iSCSI cinder volume because the target host where the VM should be moved doesn't know the iSCSI target of the host where the VM is initially running. This means that the VM cannot move and have to stay on the same host as soon as there is a RDM. ** Affects: nova Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: New ** Changed in: nova Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- 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/1330758 Title: VMware: iSCSI targets needs to be propagated to all hosts of the cluster Status in OpenStack Compute (Nova): New Bug description: With current state of the codebase, vMotion will be a no-op if a VM has a RDM to a iSCSI cinder volume because the target host where the VM should be moved doesn't know the iSCSI target of the host where the VM is initially running. This means that the VM cannot move and have to stay on the same host as soon as there is a RDM. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1330758/+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 1325789] [NEW] VMware: vm_util.get_host_ref() should take into account where the VM is located
Public bug reported: vm_util.get_host_ref() returns the first host in the list of hosts returned by vCenter. This behavior is not correct when we want to get the host where the VM is running. We need to provide the VM reference and return the host where the VM is running. See: http://www.mail-archive.com/openstack- d...@lists.openstack.org/msg25648.html for more details ** Affects: nova Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: New ** Changed in: nova Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- 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/1325789 Title: VMware: vm_util.get_host_ref() should take into account where the VM is located Status in OpenStack Compute (Nova): New Bug description: vm_util.get_host_ref() returns the first host in the list of hosts returned by vCenter. This behavior is not correct when we want to get the host where the VM is running. We need to provide the VM reference and return the host where the VM is running. See: http://www.mail-archive.com/openstack- d...@lists.openstack.org/msg25648.html for more details To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1325789/+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 1316977] Re: implement a storage adapter for HDFS
Agreed: marking the bug as invalid. I have created a blueprint to keep that in mind [1]. Christian, please create a glance-specs (and reassign the bp to you) if you want to want to implement this in Juno. [1] https://blueprints.launchpad.net/glance/+spec/hdfs-storage-backend Thanks, Arnaud ** Changed in: glance Status: New => 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/1316977 Title: implement a storage adapter for HDFS Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: HDFS should be usable as storage backend for Glance. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1316977/+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 1315237] [NEW] Glance should not call configure and configure_add two times at startup
Public bug reported: Currently at startup Glance is first creating the stores and then verifying the default store (cmd/api.py) 30 glance.store.create_stores() 31 glance.store.verify_default_store() In both of these calls, the store objects are created (store/base.py) which means that if the methods configure() and configure_add() methods are defined in the store, these methods will be called two times: 1 time in the "create_stores()" phase and 1 time in the verify_default_store() phase. It turns out that the configure()/configure_add() method can contain remote calls (which can potentially be expensive): in which case we do not want them to happen two times. Having configure/configure_add called only one time will speed up the Glance startup time for some of the stores. ** Affects: glance Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: New ** Changed in: glance Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1315237 Title: Glance should not call configure and configure_add two times at startup Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Currently at startup Glance is first creating the stores and then verifying the default store (cmd/api.py) 30 glance.store.create_stores() 31 glance.store.verify_default_store() In both of these calls, the store objects are created (store/base.py) which means that if the methods configure() and configure_add() methods are defined in the store, these methods will be called two times: 1 time in the "create_stores()" phase and 1 time in the verify_default_store() phase. It turns out that the configure()/configure_add() method can contain remote calls (which can potentially be expensive): in which case we do not want them to happen two times. Having configure/configure_add called only one time will speed up the Glance startup time for some of the stores. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1315237/+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 1313992] [NEW] VMware store should handle upload of files with unknown Content-Length
Public bug reported: Nova needs to upload streamOptimized disks to Glance. These streamOptimized disks are converted/compressed on the fly by vCenter. Consequently, it is not possible to know the size of the Glance image before upload. Without specifying the size or size zero, vCenter will reject the request (Broken Pipe). ** Affects: glance Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: New ** Changed in: glance Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1313992 Title: VMware store should handle upload of files with unknown Content-Length Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Nova needs to upload streamOptimized disks to Glance. These streamOptimized disks are converted/compressed on the fly by vCenter. Consequently, it is not possible to know the size of the Glance image before upload. Without specifying the size or size zero, vCenter will reject the request (Broken Pipe). To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1313992/+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 1311960] [NEW] Handle session timeout in the VMware store
Public bug reported: The current implementation can potentially lead to a timeout when the invoke_api is not triggered (for example PUT/GET: direct HTTP access to the datastore). We need to recreate the session responses and retry when getting 401 HTTP responses. ** Affects: glance Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: New ** Changed in: glance Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1311960 Title: Handle session timeout in the VMware store Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: The current implementation can potentially lead to a timeout when the invoke_api is not triggered (for example PUT/GET: direct HTTP access to the datastore). We need to recreate the session responses and retry when getting 401 HTTP responses. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1311960/+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 1309338] [NEW] VMware store: problem with api_insecure configuration variable
Public bug reported: The api_insecure configuration variable is documented to be True when an SSL connection is used without checking the certificates. However, the implementation is using the variable to use HTTP or HTTPS. This is confusing for deployers especially those using the cinder client where api_insecure really means do not check the certificates. It would be better to change the variable to vmware_https_connection (True = HTTPS, False = HTTP). ** Affects: glance Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) 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/1309338 Title: VMware store: problem with api_insecure configuration variable Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: The api_insecure configuration variable is documented to be True when an SSL connection is used without checking the certificates. However, the implementation is using the variable to use HTTP or HTTPS. This is confusing for deployers especially those using the cinder client where api_insecure really means do not check the certificates. It would be better to change the variable to vmware_https_connection (True = HTTPS, False = HTTP). To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1309338/+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 1292764] [NEW] Tempest failure: tempest.api.image.v1.test_images.CreateRegisterImagesTest.test_register_then_upload
Public bug reported:
This failure happens with the vmware backend when the size provided to
the store is zero but the actual data size is larger than zero.
2014-03-14 17:22:53 | [10.36.11.112] out: Traceback (most recent call last):
2014-03-14 17:22:53 | [10.36.11.112] out: File
"tempest/api/image/v1/test_images.py", line 50, in test_register_then_upload
2014-03-14 17:22:53 | [10.36.11.112] out: self.assertEqual(1024,
body.get('size'))
2014-03-14 17:22:53 | [10.36.11.112] out: File
"/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 321, in
assertEqual
2014-03-14 17:22:53 | [10.36.11.112] out: self.assertThat(observed,
matcher, message)
2014-03-14 17:22:53 | [10.36.11.112] out: File
"/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 406, in
assertThat
2014-03-14 17:22:53 | [10.36.11.112] out: raise mismatch_error
2014-03-14 17:22:53 | [10.36.11.112] out: MismatchError: 1024 != 0
** Affects: glance
Importance: Undecided
Assignee: Arnaud Legendre (arnaudleg)
Status: New
** Changed in: glance
Assignee: (unassigned) => Arnaud Legendre (arnaudleg)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1292764
Title:
Tempest failure:
tempest.api.image.v1.test_images.CreateRegisterImagesTest.test_register_then_upload
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Bug description:
This failure happens with the vmware backend when the size provided to
the store is zero but the actual data size is larger than zero.
2014-03-14 17:22:53 | [10.36.11.112] out: Traceback (most recent call last):
2014-03-14 17:22:53 | [10.36.11.112] out: File
"tempest/api/image/v1/test_images.py", line 50, in test_register_then_upload
2014-03-14 17:22:53 | [10.36.11.112] out: self.assertEqual(1024,
body.get('size'))
2014-03-14 17:22:53 | [10.36.11.112] out: File
"/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 321, in
assertEqual
2014-03-14 17:22:53 | [10.36.11.112] out: self.assertThat(observed,
matcher, message)
2014-03-14 17:22:53 | [10.36.11.112] out: File
"/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 406, in
assertThat
2014-03-14 17:22:53 | [10.36.11.112] out: raise mismatch_error
2014-03-14 17:22:53 | [10.36.11.112] out: MismatchError: 1024 != 0
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1292764/+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 1280494] Re: VMware datastore backend should support storage policies
Marking this bug as invalid. It fits more in a blueprint. ** Changed in: glance Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1280494 Title: VMware datastore backend should support storage policies Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: The VMware storage backend should be able to place the images based on storage policies. Currently, it is only possible to select one datastore to place the images. The user can provide a storage policy defined in vCenter server instead of specifying directly a datastore. Among the subset of datastores matching the policy, the datastore with most free space and accessible will be selected. If the policy provided is not found in VC or no matching datastore if found, the datastore specified in the configuration will be used. SPBM should be used with vCenter server 5.5+. More information about SPBM: http://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.vsphere.storage.doc%2FGUID-C8E919D0-9D80-4AE1-826B-D180632775F3.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1280494/+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 1291646] [NEW] Make the VMware datastore backend more robust
Public bug reported: Several issues to address: - need better error handling for the add() operation: need to catch exception when httplib fails, also need to log when the response is not OK or CREATED. - need to handle cases where the store_image_dir contains non expected characters. It should support the following use cases: /openstack_glance openstack_glance openstack_glance/ openstack glance -> this one should fail with logging openstack+glance etc. - need to quote special characters ** Affects: glance Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: In Progress ** Changed in: glance Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1291646 Title: Make the VMware datastore backend more robust Status in OpenStack Image Registry and Delivery Service (Glance): In Progress Bug description: Several issues to address: - need better error handling for the add() operation: need to catch exception when httplib fails, also need to log when the response is not OK or CREATED. - need to handle cases where the store_image_dir contains non expected characters. It should support the following use cases: /openstack_glance openstack_glance openstack_glance/ openstack glance -> this one should fail with logging openstack+glance etc. - need to quote special characters To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1291646/+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 1287945] [NEW] Instance doesn't have a task state
Public bug reported: I am getting with the latest version of the trunk: Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/eventlet/hubs/poll.py", line 97, in wait readers.get(fileno, noop).cb(fileno) File "/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line 194, in main result = function(*args, **kwargs) File "/opt/stack/nova/nova/openstack/common/service.py", line 480, in run_service service.start() File "/opt/stack/nova/nova/service.py", line 180, in start self.manager.init_host() File "/opt/stack/nova/nova/compute/manager.py", line 824, in init_host self._init_instance(context, instance) File "/opt/stack/nova/nova/compute/manager.py", line 684, in _init_instance if instance.task_state == task_states.DELETING: AttributeError: 'dict' object has no attribute 'task_state' Removing descriptor: 6 2014-03-04 13:59:14.304 ERROR nova.openstack.common.threadgroup [-] 'dict' object has no attribute 'task_state' 2014-03-04 13:59:14.304 TRACE nova.openstack.common.threadgroup Traceback (most recent call last): 2014-03-04 13:59:14.304 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/openstack/common/threadgroup.py", line 117, in wait 2014-03-04 13:59:14.304 TRACE nova.openstack.common.threadgroup x.wait() 2014-03-04 13:59:14.304 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/openstack/common/threadgroup.py", line 49, in wait 2014-03-04 13:59:14.304 TRACE nova.openstack.common.threadgroup return self.thread.wait() 2014-03-04 13:59:14.304 TRACE nova.openstack.common.threadgroup File "/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line 168, in wait 2014-03-04 13:59:14.304 TRACE nova.openstack.common.threadgroup return self._exit_event.wait() 2014-03-04 13:59:14.304 TRACE nova.openstack.common.threadgroup File "/usr/local/lib/python2.7/dist-packages/eventlet/event.py", line 116, in wait 2014-03-04 13:59:14.304 TRACE nova.openstack.common.threadgroup return hubs.get_hub().switch() 2014-03-04 13:59:14.304 TRACE nova.openstack.common.threadgroup File "/usr/local/lib/python2.7/dist-packages/eventlet/hubs/hub.py", line 187, in switch 2014-03-04 13:59:14.304 TRACE nova.openstack.common.threadgroup return self.greenlet.switch() 2014-03-04 13:59:14.304 TRACE nova.openstack.common.threadgroup File "/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line 194, in main 2014-03-04 13:59:14.304 TRACE nova.openstack.common.threadgroup result = function(*args, **kwargs) 2014-03-04 13:59:14.304 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/openstack/common/service.py", line 480, in run_service 2014-03-04 13:59:14.304 TRACE nova.openstack.common.threadgroup service.start() 2014-03-04 13:59:14.304 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/service.py", line 180, in start 2014-03-04 13:59:14.304 TRACE nova.openstack.common.threadgroup self.manager.init_host() 2014-03-04 13:59:14.304 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/compute/manager.py", line 824, in init_host 2014-03-04 13:59:14.304 TRACE nova.openstack.common.threadgroup self._init_instance(context, instance) 2014-03-04 13:59:14.304 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/compute/manager.py", line 684, in _init_instance 2014-03-04 13:59:14.304 TRACE nova.openstack.common.threadgroup if instance.task_state == task_states.DELETING: 2014-03-04 13:59:14.304 TRACE nova.openstack.common.threadgroup AttributeError: 'dict' object has no attribute 'task_state' 2014-03-04 13:59:14.304 TRACE nova.openstack.common.threadgroup ** Affects: nova Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: New ** Changed in: nova Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- 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/1287945 Title: Instance doesn't have a task state Status in OpenStack Compute (Nova): New Bug description: I am getting with the latest version of the trunk: Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/eventlet/hubs/poll.py", line 97, in wait readers.get(fileno, noop).cb(fileno) File "/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line 194, in main result = function(*args, **kwargs) File "/opt/stack/nova/nova/openstack/common/service.py", line 480, in run_service service.start() File "/opt/stack/nova/nova/service.
[Yahoo-eng-team] [Bug 1287506] [NEW] BadStoreUri doesn't get the expected arguments in several places
Public bug reported: BadStoreUri is not used correctly in several places. For example, in the Cinder store: https://github.com/openstack/glance/blob/master/glance/store/cinder.py#L120 raise exception.BadStoreUri(uri, reason) where BadStoreUri expects: https://github.com/openstack/glance/blob/master/glance/common/exception.py#L39 ** Affects: glance Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: New ** Changed in: glance Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1287506 Title: BadStoreUri doesn't get the expected arguments in several places Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: BadStoreUri is not used correctly in several places. For example, in the Cinder store: https://github.com/openstack/glance/blob/master/glance/store/cinder.py#L120 raise exception.BadStoreUri(uri, reason) where BadStoreUri expects: https://github.com/openstack/glance/blob/master/glance/common/exception.py#L39 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1287506/+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 1287495] [NEW] VMware parse_uri method should check for the scheme of the uri provided
Public bug reported: Need to add a check in parse_uri(...) [1] to make sure that a URI with the vsphere scheme is provided. Throw a BadStoreUri otherwise. [1] https://github.com/openstack/glance/blob/master/glance/store/vmware_datastore.py#L151 ** Affects: glance Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: New ** Changed in: glance Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1287495 Title: VMware parse_uri method should check for the scheme of the uri provided Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Need to add a check in parse_uri(...) [1] to make sure that a URI with the vsphere scheme is provided. Throw a BadStoreUri otherwise. [1] https://github.com/openstack/glance/blob/master/glance/store/vmware_datastore.py#L151 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1287495/+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 1286375] [NEW] Add OVA container format
Public bug reported: An OVA package is a tar archive usually containing an OVF directory inside it. Nova needs to be able to differentiate OVF and OVA based on the container format in order to extract the relevant information from it. ** 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/1286375 Title: Add OVA container format Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: An OVA package is a tar archive usually containing an OVF directory inside it. Nova needs to be able to differentiate OVF and OVA based on the container format in order to extract the relevant information from it. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1286375/+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 1283325] [NEW] VMware: Same image should not be transferred more than one time on concurrent spawn operations
Public bug reported: On concurrent spawn operations, the VMware driver transfers the same image into different temporary directories before getting into the cache: the same bits might be downloaded 20 times if 20 spawn operations happen at the same time for a given image (before being cached). The goal here is to use a lock to only transfer one time the bits of the image. ** Affects: nova Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: In Progress ** Changed in: nova Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- 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/1283325 Title: VMware: Same image should not be transferred more than one time on concurrent spawn operations Status in OpenStack Compute (Nova): In Progress Bug description: On concurrent spawn operations, the VMware driver transfers the same image into different temporary directories before getting into the cache: the same bits might be downloaded 20 times if 20 spawn operations happen at the same time for a given image (before being cached). The goal here is to use a lock to only transfer one time the bits of the image. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1283325/+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 1282715] [NEW] VMware datastore should use oslo.vmware common code
Public bug reported: The git repository oslo.vmware is now available: https://github.com/openstack/oslo.vmware/. It is time to consume it and get rid of the vmware folder in the glance folder. ** Affects: glance Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: New ** Changed in: glance Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1282715 Title: VMware datastore should use oslo.vmware common code Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: The git repository oslo.vmware is now available: https://github.com/openstack/oslo.vmware/. It is time to consume it and get rid of the vmware folder in the glance folder. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1282715/+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 1280494] [NEW] VMware datastore backend should support storage policies
Public bug reported: The VMware storage backend should be able to place the images based on storage policies. Currently, it is only possible to select one datastore to place the images. The user can provide a storage policy defined in vCenter server instead of specifying directly a datastore. Among the subset of datastores matching the policy, the datastore with most free space and accessible will be selected. If the policy provided is not found in VC or no matching datastore if found, the datastore specified in the configuration will be used. SPBM should be used with vCenter server 5.5+. More information about SPBM: http://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.vsphere.storage.doc%2FGUID-C8E919D0-9D80-4AE1-826B-D180632775F3.html ** Affects: glance Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: In Progress ** Changed in: glance Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1280494 Title: VMware datastore backend should support storage policies Status in OpenStack Image Registry and Delivery Service (Glance): In Progress Bug description: The VMware storage backend should be able to place the images based on storage policies. Currently, it is only possible to select one datastore to place the images. The user can provide a storage policy defined in vCenter server instead of specifying directly a datastore. Among the subset of datastores matching the policy, the datastore with most free space and accessible will be selected. If the policy provided is not found in VC or no matching datastore if found, the datastore specified in the configuration will be used. SPBM should be used with vCenter server 5.5+. More information about SPBM: http://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.vsphere.storage.doc%2FGUID-C8E919D0-9D80-4AE1-826B-D180632775F3.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1280494/+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 1278690] [NEW] VMware: Fetching images from Glance is slower than it should be
Public bug reported: Ran an experiment with a 1.5GB file on a very basic devstack setup: glance download | curl PUT: 2.5min nova code: 4min Customers have reported similar concerns. ** Affects: nova Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: New ** Changed in: nova Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- 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/1278690 Title: VMware: Fetching images from Glance is slower than it should be Status in OpenStack Compute (Nova): New Bug description: Ran an experiment with a 1.5GB file on a very basic devstack setup: glance download | curl PUT: 2.5min nova code: 4min Customers have reported similar concerns. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1278690/+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 1278677] [NEW] VMware driver should cache morefs
Public bug reported: The VMware needs to cache morefs as much as possible throughout the codebase. This will avoid extra VC queries. ** Affects: nova Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: New ** Changed in: nova Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- 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/1278677 Title: VMware driver should cache morefs Status in OpenStack Compute (Nova): New Bug description: The VMware needs to cache morefs as much as possible throughout the codebase. This will avoid extra VC queries. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1278677/+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 1275126] [NEW] Add VMware store the strategy module
Public bug reported: The VMware store needs to be added to strategy module: https://github.com/openstack/glance/blob/9567c2b6a06aa1e8205f9f30beca63d77500dd1d/glance/common/location_strategy/store_type.py#L55 ** Affects: glance Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: New ** Changed in: glance Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1275126 Title: Add VMware store the strategy module Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: The VMware store needs to be added to strategy module: https://github.com/openstack/glance/blob/9567c2b6a06aa1e8205f9f30beca63d77500dd1d/glance/common/location_strategy/store_type.py#L55 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1275126/+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 1275040] [NEW] VMware storage backend needs documentation in configuring.rst
Public bug reported: Need to provide a more detailed documentation in configuring.rst for the VMware storage backend: https://github.com/openstack/glance/blob/master/glance/store/vmware_datastore.py ** Affects: glance Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: New ** Changed in: glance Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1275040 Title: VMware storage backend needs documentation in configuring.rst Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Need to provide a more detailed documentation in configuring.rst for the VMware storage backend: https://github.com/openstack/glance/blob/master/glance/store/vmware_datastore.py To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1275040/+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 1268051] [NEW] README Oslo URL points to a blank page
Public bug reported: common/README points currently to a blank page: http://wiki.openstack.org/CommonLibrary#Incubation This link should be changed to https://wiki.openstack.org/wiki/Oslo#Syncing_Code_from_Incubator This is minor but could be confusing for new people... ** Affects: glance Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: In Progress ** Changed in: glance Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1268051 Title: README Oslo URL points to a blank page Status in OpenStack Image Registry and Delivery Service (Glance): In Progress Bug description: common/README points currently to a blank page: http://wiki.openstack.org/CommonLibrary#Incubation This link should be changed to https://wiki.openstack.org/wiki/Oslo#Syncing_Code_from_Incubator This is minor but could be confusing for new people... To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1268051/+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 1262051] [NEW] Cleanup: tests.functional.store_utils setup_s3 and setup_swift unused
Public bug reported: The following methods contained in glance/tests/functional/store_utils.py are not used anywhere: . setup_swift, . teardown_swift, . get_swift_uri, . setup_s3, . teardown_s3, . get_s3_uri Let's get rid of it. ** Affects: glance Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: New ** Changed in: glance Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1262051 Title: Cleanup: tests.functional.store_utils setup_s3 and setup_swift unused Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: The following methods contained in glance/tests/functional/store_utils.py are not used anywhere: . setup_swift, . teardown_swift, . get_swift_uri, . setup_s3, . teardown_s3, . get_s3_uri Let's get rid of it. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1262051/+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 1230076] Re: glance.tests.unit.test_store_base.TestStoreBase.test_exception_to_unicode fails
I have not been able to reproduce the bug. Marking it as invalid. ** Changed in: glance Status: New => 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/1230076 Title: glance.tests.unit.test_store_base.TestStoreBase.test_exception_to_unicode fails Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: $ tox -e py27 == FAIL: glance.tests.unit.test_store_base.TestStoreBase.test_exception_to_unicode -- _StringException: Traceback (most recent call last): File "/opt/stack/glance/glance/tests/unit/test_store_base.py", line 41, in test_exception_to_unicode self.assertEqual(ret, ' error message') File "/opt/stack/glance/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py", line 322, in assertEqual self.assertThat(observed, matcher, message) File "/opt/stack/glance/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py", line 417, in assertThat raise MismatchError(matchee, matcher, mismatch, verbose) MismatchError: u'\xa5 error message' != ' error message' To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1230076/+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
