[Openstack] HP Cloud Service Performance Test
Hi all, Recently I did some performance testings on HP Cloud Service. I would like to share the test results with the OpenStack community. The test report includes a lot of figures and it is not good to spam your mailbox. If you are interested you can access the report from my blog at the following URL: http://www.qyjohn.net/?p=2363 Best regards, Qingye Jiang (John) ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] instance evacuation from a failed node (rebuild for HA)
From: Ryan Lane rl...@wikimedia.org We have submitted a patch https://review.openstack.org/#/c/11086/ to address https://blueprints.launchpad.net/nova/+spec/rebuild-for-ha that simplifies recovery from a node failure by introducing an API that recreates an instance on *another* host (similar to the existing instance 'rebuild' operation). [...] If shared storage is available, the only think that likely needs to happen is for the instance's host to be updated in the database, and a reboot issued for the instance. That would keep everything identical, and would likely be much faster. That's pretty much what we do in 'manager' -- but what needs to happen in 'driver' is to (re)create the domain in libvirt on the destination host, re-attach volumes, floating IPs, etc. Essentially, everything 'spawn' is doing today, just without creating the new instance file. Of course, we don't re-provision the instance from image in this case. - Ryan Regards, Alex ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] [Nova] How common is user_data for instances?
Greetings. I'm seeking information about how common user_data is for instances in nova. Specifically for large deployments (rackspace and HP, here's looking at you). What sort of costs would be associated with changing the data type of the user_data column in the nova database? Bug 1035055 [1] requests that we allow user_data of more than 65,535 bytes per instance. Note that this size is a base64 encoded version of the data, so that's only a bit under 50k of data. This is because the data is a sqlalchemy Text column. We could convert to a LongText column, which allows 2^32 worth of data, but I want to understand the cost to operators of that change some more. Is user_data really common? Do you think people would start uploading much bigger user_data? Do you care? Mikal 1: https://bugs.launchpad.net/nova/+bug/1035055 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Swift + keystone integration
Hello I have 3 nodes with ubuntu 12.04 server and installed openstack with packages from the ubuntu repos - controller (where keystone is installed) - compute - swift I'm trying to configure Swift with Keystone but I'm having some problems, here's my proxy-server.conf [DEFAULT] bind_port = 8080 user = swift swift_dir = /etc/swift [pipeline:main] # Order of execution of modules defined below pipeline = catch_errors healthcheck cache authtoken keystone proxy-server [app:proxy-server] use = egg:swift#proxy allow_account_management = true account_autocreate = true set log_name = swift-proxy set log_facility = LOG_LOCAL0 set log_level = INFO et access_log_name = swift-proxy set access_log_facility = SYSLOG set access_log_level = INFO set log_headers = True account_autocreate = True [filter:healthcheck] use = egg:swift#healthcheck [filter:catch_errors] use = egg:swift#catch_errors [filter:cache] use = egg:swift#memcache set log_name = cache [filter:authtoken] paste.filter_factory = keystone.middleware.auth_token:filter_factory auth_protocol = http auth_host = 10.17.12.163 auth_port = 35357 auth_token = admin service_protocol = http service_host = 10.17.12.163 service_port = 5000 admin_token = admin admin_tenant_name = admin admin_user = admin admin_password = admin delay_auth_decision = 0 [filter:keystone] paste.filter_factory = keystone.middleware.swift_auth:filter_factory operator_roles = admin, swiftoperator is_admin = true On Horizon I get a Django error page and says [Errno 111] ECONNREFUSED From the Swift server I try this command: swift -v -V 2.0 -A http://10.17.12.163:5000/v2.0/ -U admin:admin -K admin stat And I also get [Errno 111] ECONNREFUSED Is there any way to debug this??? Is there any conf or packages that I'm missing for this to work on a multi-node deployment? Can you help me? Regards! ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Swift + keystone integration
Make sure that the endpoint stored in keystone is returning the right hostname/domain name and port (8080 based on your config). --John On Aug 11, 2012, at 12:58 PM, Miguel Alejandro González maggo...@gmail.com wrote: Hello I have 3 nodes with ubuntu 12.04 server and installed openstack with packages from the ubuntu repos • controller (where keystone is installed) • compute • swift I'm trying to configure Swift with Keystone but I'm having some problems, here's my proxy-server.conf [DEFAULT] bind_port = 8080 user = swift swift_dir = /etc/swift [pipeline:main] # Order of execution of modules defined below pipeline = catch_errors healthcheck cache authtoken keystone proxy-server [app:proxy-server] use = egg:swift#proxy allow_account_management = true account_autocreate = true set log_name = swift-proxy set log_facility = LOG_LOCAL0 set log_level = INFO et access_log_name = swift-proxy set access_log_facility = SYSLOG set access_log_level = INFO set log_headers = True account_autocreate = True [filter:healthcheck] use = egg:swift#healthcheck [filter:catch_errors] use = egg:swift#catch_errors [filter:cache] use = egg:swift#memcache set log_name = cache [filter:authtoken] paste.filter_factory = keystone.middleware.auth_token:filter_factory auth_protocol = http auth_host = 10.17.12.163 auth_port = 35357 auth_token = admin service_protocol = http service_host = 10.17.12.163 service_port = 5000 admin_token = admin admin_tenant_name = admin admin_user = admin admin_password = admin delay_auth_decision = 0 [filter:keystone] paste.filter_factory = keystone.middleware.swift_auth:filter_factory operator_roles = admin, swiftoperator is_admin = true On Horizon I get a Django error page and says [Errno 111] ECONNREFUSED From the Swift server I try this command: swift -v -V 2.0 -A http://10.17.12.163:5000/v2.0/ -U admin:admin -K admin stat And I also get [Errno 111] ECONNREFUSED Is there any way to debug this??? Is there any conf or packages that I'm missing for this to work on a multi-node deployment? Can you help me? Regards! ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Swift + keystone integration
I used to debug via curl for separating the AUTH section(Keystone) and Data
Section(Swift-proxy) .
#curl -v -d {%json%} http://keystone_ip:port/v2.0
#curl -H X-AUTH-TOKEN: %TOKEN% http://swift_ip:port/v1/AUTH_%account%
And monitor the log on both keystone and swift.
Several Steps you can followed
1. Check keystone is working on proper port
2. Check Swift is working and on proper port
3. Check swift endpoint under Keystone's DB
4. Does the network accessible between keystone and Swift
2012/8/12 Miguel Alejandro González maggo...@gmail.com
Hello
I have 3 nodes with ubuntu 12.04 server and installed openstack with
packages from the ubuntu repos
- controller (where keystone is installed)
- compute
- swift
I'm trying to configure Swift with Keystone but I'm having some problems,
here's my proxy-server.conf
[DEFAULT]
bind_port = 8080
user = swift
swift_dir = /etc/swift
[pipeline:main]
# Order of execution of modules defined below
pipeline = catch_errors healthcheck cache authtoken keystone proxy-server
[app:proxy-server]
use = egg:swift#proxy
allow_account_management = true
account_autocreate = true
set log_name = swift-proxy
set log_facility = LOG_LOCAL0
set log_level = INFO
et access_log_name = swift-proxy
set access_log_facility = SYSLOG
set access_log_level = INFO
set log_headers = True
account_autocreate = True
[filter:healthcheck]
use = egg:swift#healthcheck
[filter:catch_errors]
use = egg:swift#catch_errors
[filter:cache]
use = egg:swift#memcache
set log_name = cache
[filter:authtoken]
paste.filter_factory = keystone.middleware.auth_token:filter_factory
auth_protocol = http
auth_host = 10.17.12.163
auth_port = 35357
auth_token = admin
service_protocol = http
service_host = 10.17.12.163
service_port = 5000
admin_token = admin
admin_tenant_name = admin
admin_user = admin
admin_password = admin
delay_auth_decision = 0
[filter:keystone]
paste.filter_factory = keystone.middleware.swift_auth:filter_factory
operator_roles = admin, swiftoperator
is_admin = true
On Horizon I get a Django error page and says [Errno 111] ECONNREFUSED
From the Swift server I try this command:
swift -v -V 2.0 -A http://10.17.12.163:5000/v2.0/ -U admin:admin -K admin
stat
And I also get [Errno 111] ECONNREFUSED
Is there any way to debug this??? Is there any conf or packages that I'm
missing for this to work on a multi-node deployment? Can you help me?
Regards!
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
+Hugo Kuo+
tonyt...@gmail.com
+ tonyt...@gmail.com886 935004793
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Nova ignores nova.conf
On Aug 10, 2012, at 6:07 AM, Mark McLoughlin mar...@redhat.com wrote: On Fri, 2012-08-10 at 00:23 -0900, Simon Walter wrote: Nova does not respect the options set in the /etc/nova/nova.conf file. I've seen some examples with -- prefixing the flags, as if they are command line arguments. I've also seen examples without. I've tried removing the --, that does nothing. Specifically, I've set --flat_network_bridge=br0 --fixed_range=10.0.3.0/24 --flat_network_dhcp_start=10.0.3.1 I always get a br100 created with an IP address of 10.0.2.33 This is really annoying. If I empty the /etc/nova/nova.conf nothing gets created. I've greped all sorts of places for defaults, but come up blank. If nova is being run with --config-file, then the syntax is [DEFAULT] flat_network_bridge=br0 OTOH, if it is being run with --flagfile, the syntax is: --flat_network_bridge=br0 I assumed that the nova-* services were auto-deteting the nova.conf format. When I run on Ubuntu, the default nova.conf file is in the deprecated flag file format, but I just edited the nova.conf file to use the new ini-style format, and everything seemed to just work. Take care, Lorin -- Lorin Hochstein Lead Architect - Cloud Services Nimbis Services, Inc. www.nimbisservices.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
