发起问题

gcivitella 的档案 - activity

2020-04-17 08:43:49 -0500 获得奖牌  受欢迎的问题 (source)
2020-04-17 08:43:49 -0500 获得奖牌  著名问题 (source)
2020-04-17 08:43:49 -0500 获得奖牌  热门的问题 (source)
2017-08-02 03:31:06 -0500 获得奖牌  学生 (source)
2017-08-02 03:29:55 -0500 获得奖牌  热门的问题 (source)
2015-09-05 06:54:53 -0500 获得奖牌  受欢迎的问题 (source)
2015-05-20 18:56:00 -0500 获得奖牌  受欢迎的问题 (source)
2012-09-25 17:01:20 -0500 回答问题 Info retrieval for a Swift billing system

On /srv/node/*/account/ there are some .db files. Those are the sqlite databases holding account usage data. There is one db for every account.

2012-09-14 10:52:40 -0500 问了问题 Info retrieval for a Swift billing system

Hi all,

I'm trying to figure out how a billing system could retrieve stats info about all the tenants in a Swift cluster. Do someone has a working example to show? Is the .reseller_admin status involved while choosing credentials to query for stats? What about doing the same query while using Keystone authentication?

Thanks a lot Giuseppe

2012-04-24 15:56:20 -0500 回答问题 Essex stable running on Xenserver: DEVICE_DETACH_REJECTED errors during stress test

Thanks John Garbutt, that solved my question.

2012-04-24 13:43:45 -0500 回答问题 Essex stable running on Xenserver: DEVICE_DETACH_REJECTED errors during stress test

Sorry John,

I did not explain the right way why I transformed a bug to the present question. I found out that my problem was something happening at the Xenserver level during a stress test. It was something already documented by the xen community. It was not related on Openstack, neither Essex4 or Essex stable. To get through the problem i just implemented a quick and dirty nagios plugin to check for lost vbd.

thanks a lot for your time. Giuseppe

2012-04-24 10:20:37 -0500 回答问题 Essex stable running on Xenserver: DEVICE_DETACH_REJECTED errors during stress test

I mean XenServer 6.0 (build 50762p) with the following updates: XS60E001 XS60E002 XS60E003 XS60E004

2012-04-24 10:03:16 -0500 回答问题 Essex stable running on Xenserver: DEVICE_DETACH_REJECTED errors during stress test

Hi,

I'm running Xenserver6, I did install all the patches available.

thanks

2012-04-17 13:36:14 -0500 回答问题 Essex stable running on Xenserver: DEVICE_DETACH_REJECTED errors during stress test

Sorry,

the problem was documented and Xen spcific. It was something similar to the problem described here: http://www.crucial.com.au/blog/2011/05/04/xenserver-internal-error-another-frontend-device-is-already-connect-to-this-domain/ (http://www.crucial.com.au/blog/2011/0...)

Giuseppe

2012-04-10 17:34:25 -0500 问了问题 Essex stable running on Xenserver: DEVICE_DETACH_REJECTED errors during stress test

Hi all,

I'm seeing multiple DEVICE_DETACH_REJECTED errors in my nova-compute's logs when running a deploy's stress test. I run a few nova-compute vms (ubuntu 10.04 on kernel 3.2.7) on some xenserver6 nodes. The openstack's version I was running is Essex stable. While I was able to deploy correctly a single vm on every node, if I did try to schedule about five virtual machine's deploy per node, I received errors like those reported here:

http://paste.openstack.org/show/12634/

I did rollback to essex4 running on same xenserver hosts and on same nova-compute virtual machine. the errors vanished.

2012-02-23 08:15:54 -0500 回答问题 policy.json: is keystone mandatory?

Thanks Brian Waldon, that solved my question.

2012-02-20 09:14:24 -0500 问了问题 policy.json: is keystone mandatory?

Hi all,

is it possible to configure policy.json while not using keystone? The only guide I found is this one http://knowledgestack.wordpress.com/ and refers to keystone. Thanks

2012-02-03 14:01:02 -0500 回答问题 Multiple resize problem on XenSever6

I can confirm I'm not having the problem anymore. My env is XenServer6, nova Essex (milestone 2 and 3) and images built not using xenconverter's OVA. A huge thanks to Tod Deshane and Paul Voccio for their help and patience: they can barely imagine how much I owe them :-)

Regards Giuseppe

2012-01-23 15:53:01 -0500 回答问题 Is it possible to increase the timeout value while looking for agent plugin on XenServer?

Increasing the agent_version_timeout as reported before solved my problem. The password problem was agent related. Anyway it coud be useful to set the agent_version_timeout in the nova.conf

2012-01-20 08:26:11 -0500 回答问题 public and private network id not shown while using api v1.1

Thanks Brian Waldon, that solved my question.

2012-01-19 08:38:50 -0500 回答问题 public and private network id not shown while using api v1.1

Hi Brian,

thanks for the quick answer. I'm looking for a way to distinguish private (or fixed) ips from public (or floating) parsing in software an array like the one shown before: {"addresses": {"myproj-net": [{"version": 4, "addr": "10.176.42.16"}, {"version": 4, "addr": "67.23.10.132"}]}

Can I assume that the first ip is (and will always be) the private ip assigned to the server and the second ip, if present, is (and will always be) the public one?

Are there plans to change in a future release the way ips are exposed?

Hope I made my point more clear.

Best regards Giuseppe

2012-01-18 16:37:04 -0500 回答问题 Is it possible to increase the timeout value while looking for agent plugin on XenServer?

The problem could be the windows agent which exits with code 0 and outputs nothing when receives an agent version request. It lets the spawing process on nova-compute go to the set admin password phase without a fully working agent.

2012-01-18 16:27:52 -0500 问了问题 public and private network id not shown while using api v1.1

Hi all,

while using Diablo and a mix of api 1.0 and 1.1 it was possible separate private from public ips because a query to the api server generated a response like this: <addresses> <network id="public"> <ip version="4" addr="67.23.10.132"/> </network> <network id="private"> <ip version="4" addr="10.176.42.16"/> </network> </addresses>

I'm now using api v1.1 on Essex-2 and when I do a similar query to the api server I get:

{"addresses": {"myproj-net": [{"version": 4, "addr": "10.176.42.16"}, {"version": 4, "addr": "67.23.10.132"}]}}

while a was expecting an output not much different than before (according to http://wiki.openstack.org/OpenStackAPI_1-1 (http://wiki.openstack.org/OpenStackAP...) ). Is this a bug or am I missing something?

Thanks a lot Giuseppe

2012-01-18 08:36:09 -0500 回答问题 Is it possible to increase the timeout value while looking for agent plugin on XenServer?

These are some relevant entries about a windows deploy: http://paste.openstack.org/show/4391/

On my nova-compute log, at service startup, I can see: 2012-01-18 09:32:08,278 DEBUG nova [-] agent_version_timeout : 1800 from (pid=6813)

Thanks

2012-01-17 17:45:46 -0500 回答问题 Is it possible to increase the timeout value while looking for agent plugin on XenServer?

In nova/virt/xenapi/vmops.py at row 55 I see there is a timeout defined: flags.DEFINE_integer('agent_version_timeout', 300,

I did try to increase it but I receive anyway the following error: 012-01-17 18:36:32,663 ERROR nova.virt.xenapi.vmops [-] TIMEOUT: The call to password timed out. VM id=42f3bf42-7619-46bd-8c8b-e27c67a3fe6e; args={'enc_pass': 'wWAGii5J9Rfu5IfUpjLG/w==', 'path': '', 'dom_id': '47', 'id': '8b8473d5-c008-4b18-a2e8-28d9aaa55e76'} 2012-01-17 18:36:32,663 ERROR nova.virt.xenapi.vmops [-] Failed to update password: {'message': 'TIMEOUT: No response from agent within 30 seconds.', 'returncode': 'timeout'}

2012-01-17 08:36:05 -0500 问了问题 Is it possible to increase the timeout value while looking for agent plugin on XenServer?

Hi all, I'm trying to setup Administrator password on a windows image. The image is deployed on XenServer so I'm relying on xentools and the guest agent to set the password. Since at the first boot the OS executes a sysprep, the agent takes a long time to start and the nova-compute's call which ask for plugin version timeouts. It there a way to increase the timeout value or to work around this problem?

thanks a lot

2011-11-17 12:14:47 -0500 回答问题 Multiple resize problem on XenSever6

I've got problems runningu multiple resize on XenServer5 too. Can someone confirm it is possible to resize the same machine more times in a short time interval?

Thanks

2011-11-16 16:35:27 -0500 问了问题 Multiple resize problem on XenSever6

Hi all,

I'm experiencing the following problem doing a short term multiple resize test using XenServer6 as hypervisor. On first resize everything works as expected. If I do another resize a few minutes later, I receive an error about "VHD coalesce attempts exceeded" on destination host. Here's an extract from nova-compute.log: http://paste.openstack.org/show/3368/

On the hypervisor's /var/log/SMlog I can find errors like this: http://paste.openstack.org/show/3369/

Can someone give me some advice about this issue? Is it something related to the hypervisor? Do I need to wait longer between a resize an the other?

Thanks a lot Giuseppe

2011-09-21 13:51:11 -0500 回答问题 xenapi-vlan-network-manager and xenapi_net.py

Thanks Sateesh, that solved my question.

2011-09-21 08:26:22 -0500 回答问题 flavor swap, RXTX Quota and RXTX Cap

Thanks Brian Lamar, that solved my question.

2011-09-19 14:35:45 -0500 问了问题 flavor swap, RXTX Quota and RXTX Cap

Hi,

when creating a flavor I can set parameters like swap, RXTX Quota and RXTX Cap. Are they implemented? If they are, how are RXTX quota and RXTX Cap used?

Thanks

2011-09-12 15:04:41 -0500 问了问题 xenapi-vlan-network-manager and xenapi_net.py

Hi,

I'm trying to implement a nova-compute node using XenServer. I followed this guide: http://wiki.openstack.org/XenServerDevelopment (http://wiki.openstack.org/XenServerDe...) Now I try to get it working in a vlan environment, but when I add this line to my nova.conf --network_driver=nova.network.xenapi_net I got an error unless i manually copied xenapi_net.py in the installation. Ubuntu's milestone packages don't have the driver and I wan unable to find it in a nova branch I got via bzr. I had to chek out the xenapi-vlan-network-manager to get the code. Is this correct? I supposed I had to find all I needed in nova since the xenapi_net has been merged in cactus. Is there something else that must be done to work with vlans when using XenServer?

Thanks

2011-09-01 15:50:52 -0500 回答问题 changing flavor using KVM hypervisor

Thanks a lot.

2011-09-01 15:16:09 -0500 问了问题 changing flavor using KVM hypervisor

Hi,

is it possibile to change a virtual machine's flavor while using KVM as hypervisor? I've read of resize methodbut it seems something possible only when using Xen.

Thanks

2011-09-01 15:08:45 -0500 回答问题 VlanManager: nova-network does not assign ip from project's network range

Problem solved.

2011-08-29 15:02:03 -0500 回答问题 VlanManager: nova-network does not assign ip from project's network range

I deleted and recreated the nova sql database. Now nova-network seems to assign ips from the right range. The old database was created with a cactus version of nova-manage. The fixed_ips table was showing a lot of records from previous tests. They were ips with timestamps for "created_at" end "updated_at" columns but not for the "deleted_at" one. In "nova-manage network list" output those ips were not showing but nova-network was assigning some of them to the instances. After upgrading from cactus to diablo D3 and D4 I executed a "nova db sync" thinking it was enough to upgrade the database's tables and records. Probably I missed something. I did not check yet the new setup with more tenants, so I'm not closing the question at the moment.

2011-08-26 10:37:32 -0500 回答问题 VlanManager: nova-compute node creates vlan on default eth instead of --vlan_interface

Thanks Vish Ishaya, that solved my question.

2011-08-26 10:37:16 -0500 回答问题 VlanManager: nova-compute node creates vlan on default eth instead of --vlan_interface

Thanks a lot. Problem solved

2011-08-26 10:35:45 -0500 问了问题 VlanManager: nova-network does not assign ip from project's network range

Hi all,

I'm experiencing a problem with dhcp assigned ips in a vlan manager environment. I'm testing a two node setup: both of them are ubuntu 11.04 running Diablo services. Actual diablo milestone version is D4, but I found the problem on D3. The first node runs as cloud controller and nova-network service, the second is a nova-compute node. On my nova.conf I defined the fixed_range this way:

--fixed_range=10.12.0.0/16

On this node I created a first project and then a network with the following command:

root@nova-services2:~# nova-manage network create --label=gcivitella_proj_net --fixed_range_v4=10.12.2.0/24 --num_networks=1 --network_size=256 --vlan=12 --dns1=212.29.129.3 --dns2=212.29.129.2 root@nova-services2:~# nova-manage network list network netmask start address DNS1 DNS2 VlanID project
10.12.2.0/24 255.255.255.0 10.12.2.3 None None 12 None

As soon as I deploy a vm with my project's credentials, in the nova database I can see: mysql> select * from networks \G; ******** 1. row ******** created_at: 2011-08-25 14:38:38 updated_at: 2011-08-25 16:14:10 deleted_at: NULL deleted: 0 id: 8 injected: 0 cidr: 10.12.2.0/24 netmask: 255.255.255.0 bridge: br102 gateway: 10.12.2.1 broadcast: 10.12.2.255 dns1: NULL vlan: 102 vpn_public_address: 212.29.131.5 vpn_public_port: 1000 vpn_private_address: 10.12.2.2 dhcp_start: 10.12.2.3 project_id: gcivitella_proj host: nova-services2 cidr_v6: NULL gateway_v6: NULL label: gcivitella_proj_net netmask_v6: NULL bridge_interface: eth0 multi_host: 0 dns2: NULL uuid: d1e1eb15-9392-4851-83fa-6528beb3fcc6

AFAIK this means that the network has been associated with the project without any further configuration. From now on the vms deployed by project's users should be linked to that project's network. I would expect thath my first deployed vm woud get an ip between 10.12.2.3 and 10.12.2.255. What really happens is that on both nodes vlans and bridges are created correctly. On nova-network node br102 gets 10.12.2.1 as ip (gateway's ip in this network sql record), but the vm gets as ip 10.12.1.5 and this makes it unreacheable.

In nova-network.log i can see: 2011-08-26 10:15:04,592 DEBUG nova.rpc [-] received {u'_context_request_id': u'1H687SBPN6FE9W766GBC', u'_context_read_deleted': False, u'args': {u'address': u'10.12.1.5'}, u'_context_is_admin': True, u'_context_timestamp': u'2011-08-26T08:15:04Z', u'_context_user': None, u'method': u'release_fixed_ip', u'_context_project': None, u'_context_remote_address': None} from (pid=21738) process_data /usr/lib/pymodules/python2.7/nova/rpc.py:202 2011-08-26 10:15:04,593 DEBUG nova.rpc [-] unpacked context: {'timestamp': u'2011-08-26T08:15:04Z', 'msg_id': None, 'remote_address': None, 'project': None, 'is_admin': True, 'user': None, 'request_id': u'1H687SBPN6FE9W766GBC', 'read_deleted': False} from (pid=21738) _un pack_context /usr/lib/pymodules/python2.7/nova/rpc.py:451 2011-08-26 10:15:04,594 DEBUG nova.network.manager [1H687SBPN6FE9W766GBC None None] Released IP |10.12.1.5| from (pid=21738) release_fixed_ip /usr/lib/pymodules ... (more)

2011-08-24 09:36:21 -0500 问了问题 VlanManager: nova-compute node creates vlan on default eth instead of --vlan_interface

Hi all,

I've got a 2 nodes openstack setup were I'm testing a VlanManager network: both the nodes are natty 11.04 64bit running Diablo milestone (2011.3~d3-0ubuntu0~ppa1~natty1). One of the node runs the nova-sheduler and the nova-network services. It has the following network related flags: --network_manager=nova.network.manager.VlanManager --flat_network_dhcp_start=10.12.1.1 --flat_network_dns=212.29.129.3 --fixed_range=10.12.0.0/16 --iscsi_ip_prefix=10.10.11. --vlan_interface=eth0 --flat_interface=eth0 --public_interface=eth1

The other runs nova-compute and has the following network related flags: --network_manager=nova.network.manager.VlanManager --flat_network_dhcp_start=10.12.1.1 --flat_network_dns=212.29.129.3 --fixed_range=10.12.0.0/16 --iscsi_ip_prefix=10.10.11. --vlan_interface=eth4 --flat_interface=eth4 --public_interface=eth1 --logdir=/var/log/nova --state_path=/var/lib/nova --verbose

If I check the registered vlan config on this node I got: root@beta:~# nova-manage config list|grep vlan --vlan_interface=eth4 --vlan_start=100

If i look in the nova-compute.log, at service startup i can see: 2011-08-24 10:18:59,542 DEBUG nova [-] find_host_timeout : 30 from (pid=3460) serve /usr/lib/pymodules/python2.7/nova/service.py:366 2011-08-24 10:18:59,542 DEBUG nova [-] vlan_interface : eth4 from (pid=3460) serve /usr/lib/pymodules/python2.7/nova/service.py:366 2011-08-24 10:18:59,542 DEBUG nova [-] aws_access_key_id : admin from (pid=3460) serve /usr/lib/pymodules/python2.7/nova/service.py:366

But when i deploy a vm from a project who is placed on vlan 12, in the same log I can see: 2011-08-24 10:21:45,862 DEBUG nova.linux_net [-] Starting VLAN inteface vlan12 from (pid=3460) ensure_vlan /usr/lib/pymodules/python2.7/nova/network/linux_net.py:466 2011-08-24 10:21:45,862 DEBUG nova.utils [-] Running cmd (subprocess): sudo vconfig set_name_type VLAN_PLUS_VID_NO_PAD from (pid=3460) execute /usr/lib/pymodules/python2.7/nova/utils.py:143 2011-08-24 10:21:45,907 DEBUG nova.utils [-] Running cmd (subprocess): sudo vconfig add eth0 12 from (pid=3460) execute /usr/lib/pymodules/python2.7/nova/utils.py:143 2011-08-24 10:21:45,921 DEBUG nova.utils [-] Running cmd (subprocess): sudo ip link set vlan12 up from (pid=3460) execute /usr/lib/pymodules/python2.7/nova/utils.py:143 2011-08-24 10:21:45,937 DEBUG nova.utils [-] Attempting to grab semaphore "ensure_bridge" for method "ensure_bridge"... from (pid=3460) inner /usr/lib/pymodules/python2.7/nova/utils.py:600 2011-08-24 10:21:45,937 DEBUG nova.utils [-] Attempting to grab file lock "ensure_bridge" for method "ensure_bridge"... from (pid=3460) inner /usr/lib/pymodules/python2.7/nova/utils.py:605 2011-08-24 10:21:45,938 DEBUG nova.utils [-] Running cmd (subprocess): ip link show dev br12 from (pid=3460) execute /usr/lib/pymodules/python2.7/nova/utils.py:143 2011-08-24 10:21:45,943 DEBUG nova.utils [-] Result was 255 from (pid=3460) execute /usr/lib/pymodules/python2.7/nova/utils.py:161 2011-08-24 10:21:45,944 DEBUG nova.linux_net [-] Starting Bridge interface for vlan12 from (pid=3460) ensure_bridge /usr ... (more)