Re: [Openstack] is this a bug in milestone-proposed keystone ? (cannotget endpoint-list, nor create endpoint)
hi,
I don't know if it is a bug but I come across the same problem and wondering
how to solve it.
-- Original --
From: Pierre Amadiopierre.ama...@canonical.com;
Date: Sun, Mar 25, 2012 04:35 AM
To: openstackopenstack@lists.launchpad.net;
Subject: [Openstack] is this a bug in milestone-proposed keystone ? (cannotget
endpoint-list, nor create endpoint)
Hi there !
I wanted to give a try to the milestone-proposed branch of keystone and
got stuck quite fast.
I am not sure if i hit a bug and should report it, or if i'm doing
something wrong.
With previous version of keystone (read packaged on ubuntu precise), i
was able to create endpoint the following way once keystone has been
installed:
1) setting some env variables:
export KEYSTONE_IP=192.168.122.102 # IP of your keystone API server
export SERVICE_ENDPOINT=http://$KEYSTONE_IP:35357/v2.0/
export SERVICE_TOKEN=999888777666
export NOVA_PUBLIC_URL=http://$NOVA_IP:8774/v1.1/%(tenant_id)s
export NOVA_ADMIN_URL=$NOVA_PUBLIC_URL
export NOVA_INTERNAL_URL=$NOVA_PUBLIC_URL
2) creating services:
keystone service-create --name nova --type compute --description
'OpenStack Compute Service'
keystone service-create --name swift --type object-store --description
'OpenStack Storage Service'
keystone service-create --name glance --type image --description
'OpenStack Image Service'
keystone service-create --name keystone --type identity --description
'OpenStack Identity Service'
3) creating an endpoint for those services, starting with the compute
service:
ID=$(keystone service-list | grep -i compute | awk '{print $2}')
keystone endpoint-create --region RegionOne --service_id $ID --publicurl
$NOVA_PUBLIC_URL --adminurl $NOVA_ADMIN_URL --internalurl $NOVA_INTERNAL_URL
When i run this command with milestone-proposed, i experience the following:
No handlers could be found for logger keystoneclient.client
The action you have requested has not been implemented. (HTTP 501)
Strangely enough, i experience a similar error message when running a
simple keystone endpoint-list whereas command such as keystone
user-list works all right.
here is what i have in the keystone logs when trying endpoint-list:
2012-03-24 20:30:09DEBUG [routes.middleware] Matched GET /endpoints
2012-03-24 20:30:09DEBUG [routes.middleware] Route path:
'{path_info:.*}', defaults: {'controller':
keystone.contrib.admin_crud.core.CrudExtension object at 0x2b215d0}
2012-03-24 20:30:09DEBUG [routes.middleware] Match dict:
{'controller': keystone.contrib.admin_crud.core.CrudExtension object at
0x2b215d0, 'path_info': '/endpoints'}
2012-03-24 20:30:09DEBUG [routes.middleware] Matched GET /endpoints
2012-03-24 20:30:09DEBUG [routes.middleware] Route path:
'/endpoints', defaults: {'action': u'get_endpoints', 'controller':
keystone.catalog.core.EndpointController object at 0x2b21210}
2012-03-24 20:30:09DEBUG [routes.middleware] Match dict: {'action':
u'get_endpoints', 'controller':
keystone.catalog.core.EndpointController object at 0x2b21210}
2012-03-24 20:30:09DEBUG [keystone.common.wsgi] arg_dict: {}
2012-03-24 20:30:09 WARNING [keystone.common.wsgi] The action you have
requested has not been implemented.
2012-03-24 20:30:09DEBUG [keystone.common.wsgi]
RESPONSE HEADERS
2012-03-24 20:30:09DEBUG [keystone.common.wsgi] Content-Type =
application/json
2012-03-24 20:30:09DEBUG [keystone.common.wsgi] Vary = X-Auth-Token
2012-03-24 20:30:09DEBUG [keystone.common.wsgi] Content-Length = 109
2012-03-24 20:30:09DEBUG [keystone.common.wsgi]
2012-03-24 20:30:09DEBUG [keystone.common.wsgi]
RESPONSE BODY
I try to add some debug in
keystone.catalog.core.EndpointController.get_endpoints() method:
def get_endpoints(self, context):
LOG.debug(PLOP get_endpoints)
self.assert_admin(context)
LOG.debug(PLOP STILL HERE) # = LAST DEBUG LINE
endpoint_list = self.catalog_api.list_endpoints(context)
LOG.debug(SO, how does endpoint_list looks like ?)
for i in endpoint_list:
LOG.debug(PLOP: '%s',s)
endpoint_refs = [self.catalog_api.get_endpoint(context, e)
for e in endpoint_list]
LOG.debug(PLOP THIS IS THE END)
return {'endpoints': endpoint_refs}
So, as i do not see anything after PLOP STILL HERE, i am assuming
something is wrong in the catalog_api.list_endpoints() method.
However, i do not understand exactly where it is implemented.
catalog_api is a Manager instance, wich seems to be a subclass of
Manager() defined in keystone/keystone/common/manager.py but i am lost
with the wrapping magic that occurs there.
So, is this a bug that i should file ?
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe :
Re: [Openstack] [OpenStack] Xen Hypervisor
I certainly changed the plugin so it always required the host_uuid, but I also changed the call_plugin code in xenapi_conn to ensure we always pass the host_uuid. Indeed it looks like in the code path below, that you should get the host_uuid passed all the way though. I have not tested with XCP myself, only with XenServer 6. I am afraid I will not get chance to try this out till Wednesday (currently on holiday). One other useful log will be from XCP where it logs the parameters passed into the plugin (on XenSever it is /var/log/xensource.log, it could be /var/log/xcp.log? or xapi.log, can't remember I am afraid) You should be able to track the host_uuid to ensure it gets from nova-xapi client-xapi server-plugin If you want to move on with your deployment a work around is to add this into the xenhost plugin: Change: host_uuid=arg_dict['host_uuid'] Into: host_uuid=_run_command(xe host-list | grep uuid).split(:)[-1].strip() The above does not work in all cases, but it should work for your particular case (no pools). If you could raise a nova bug for this, mentioning the version of XCP you are using, that would be great. I hope that helps, John From: Ewan Mellor Sent: 25 March 2012 19:56 To: Alexandre Leites; openstack@lists.launchpad.net Cc: John Garbutt Subject: RE: [Openstack] [OpenStack] Xen Hypervisor It looks like you're hitting a recently introduced bug (maybe). I haven't run the code, but from reading through, it looks like the xenhost.host_data plugin command is going to barf if it is not passed a host_uuid parameter. It used to gracefully handle that case, but since 37a392dc it's not doing so any more. The plugin is being called with no arguments from nova.virt.xenapi.host. Cc'd John Garbutt, who wrote that bit of code. Ewan. From: openstack-bounces+ewan.mellor=citrix@lists.launchpad.net [mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net] On Behalf Of Alexandre Leites Sent: 23 March 2012 10:46 To: openstack@lists.launchpad.net Subject: Re: [Openstack] [OpenStack] Xen Hypervisor Hi folks, Sorry for late reply, i was trying to install this without following any ready-to-use scripts ( but i used one :( ) to understand how things are made. So i installed XCP 1.4.90 from DVD and configured it from installation screen. Execute the following commands on dom0 --- Dom 0 Extra Config cd /etc/xapi.d/plugins/ wget -q https://raw.github.com/openstack/nova/master/plugins/xenserver/xenapi/etc/xapi.d/plugins/xenhost wget -q https://raw.github.com/openstack/nova/master/plugins/xenserver/xenapi/etc/xapi.d/plugins/xenstore.py wget -q https://raw.github.com/openstack/nova/master/plugins/xenserver/xenapi/etc/xapi.d/plugins/pluginlib_nova.py wget -q https://raw.github.com/openstack/nova/master/plugins/xenserver/xenapi/etc/xapi.d/plugins/migration wget -q https://raw.github.com/openstack/nova/master/plugins/xenserver/xenapi/etc/xapi.d/plugins/glance wget -q https://raw.github.com/openstack/nova/master/plugins/xenserver/xenapi/etc/xapi.d/plugins/agent chmod 777 * service xapi restart --- After that i downloaded XenCenter and created a VM from Ubuntu Server 11.10 CD... (all from below is on guest) After this, i did updated all the system with command apt-get update apt-get upgrade -y apt-get dist-upgrade -y and rebooted the machine. When you do this, you'll boot on newer kernel (3.0.0-16-server, check with uname -a command)... and unsinstall the old kernel (apt-get purge linux-image-3.0.0-12-server). After this, i did installed the virtual kernel (3.0.0-16-virtual) and rebooted the machine. Check if you rebooted in this kernel via uname -a and unsinstall the old kernel. After this, execute on dom0 again: --- Dom 0 Extra Config cd ~ wget http://94.212.78.134/res/xenserver/makepv.sh chmod +x makepv.sh ./makepv.sh YOUR-XEN-GUEST-NAME --- After this, you can do apt-get install -y cracklib-runtime curl wget ssh openssh-server tcpdump ethtool python-pip git vim-nox sudo and pip install xenapi wget http://images.ansolabs.com/xen/xe-guest-utilities_5.6.100-651_amd64.deb -O xe-guest-utilities_5.6.100-651_amd64.deb dpkg -i xe-guest-utilities_5.6.100-651_amd64.deb update-rc.d -f xe-linux-distribution remove update-rc.d xe-linux-distribution defaults mkdir -p /usr/share/cracklib echo a | cracklib-packer pwconv echo root:password | chpasswd rm -f /etc/localtime groupadd libvirtd useradd stack -s /bin/bash -d /opt/stack -G libvirtd echo stack:password | chpasswd echo stack ALL=(ALL) NOPASSWD: ALL etc/sudoers mkdir -p /opt/stack chown -R stack /opt/stack After all this, you can install nova-compute , copy nova.conf from your controller and configure the following vars: --connection_type=xenapi --xenapi_connection_username=root --xenapi_connection_password=password --xenapi_connection_url=http://XENDOM0IP and restart your nova-compute service. You
Re: [Openstack] Keystone auth issues with Swift
Hi Juerg, On Tue, Mar 20, 2012 at 10:56 AM, Haefliger, Juerg juerg.haefli...@hp.com wrote: Did you start on it already? I made the modifications that you suggested this morning and it seems to work now. I can successfully add and delete images through Glance now. Let me know if you want me to create a patch/review. If so, do I need to file a bug first or is it covered under an existing one? I haven't start on it as Jay was telling me you were working on this, feel free to work against this bug https://bugs.launchpad.net/glance/+bug/944946 (Please don't forget to add the unittest for it). I'm struggling a bit with the unit test. I added a test_swift_store.add_auth_v2 unit test but it's not doing much since the swift.common.client get_auth call is stubbed out and always succeeds. What exactly should I be testing for? I was thinking of modifying fake_auth_get to check that auth_version is as expected when using auth 2. Thanks ...Juerg Thanks, Chmouel. ___ 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] Confusing about the nova authentication and keystone authentication
Hello ,every one: Here is a question that confusing me for days. I saw there is an authentication mechanism in keystone,that is responsible for creating users ,projects,roles ,role-user relationship management etcand also,I found there is such a mechanism in nova,which also can create users,projects,roles...things that keystone do. so ,what's the relationship between the two?..Can anyone please help me out of here :) Thank you. -- ___ 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] is this a bug in milestone-proposed keystone ? (cannotget endpoint-list, nor create endpoint)
I’m also getting the same error on latest master branch (updated today)
Using setup created by devstack
-Mandar
From: openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net] On
Behalf Of .?o 0 O??
Sent: Monday, March 26, 2012 12:45 PM
To: Pierre Amadio
Cc: openstack
Subject: Re: [Openstack] is this a bug in milestone-proposed keystone ?
(cannotget endpoint-list, nor create endpoint)
hi,
I don't know if it is a bug but I come across the same problem and wondering
how to solve it.
-- Original --
From: Pierre Amadiopierre.ama...@canonical.com;
Date: Sun, Mar 25, 2012 04:35 AM
To: openstackopenstack@lists.launchpad.net;
Subject: [Openstack] is this a bug in milestone-proposed keystone ? (cannotget
endpoint-list, nor create endpoint)
Hi there !
I wanted to give a try to the milestone-proposed branch of keystone and
got stuck quite fast.
I am not sure if i hit a bug and should report it, or if i'm doing
something wrong.
With previous version of keystone (read packaged on ubuntu precise), i
was able to create endpoint the following way once keystone has been
installed:
1) setting some env variables:
export KEYSTONE_IP=192.168.122.102 # IP of your keystone API server
export SERVICE_ENDPOINT=http://$KEYSTONE_IP:35357/v2.0/
export SERVICE_TOKEN=999888777666
export NOVA_PUBLIC_URL=http://$NOVA_IP:8774/v1.1/%(tenant_id)s
export NOVA_ADMIN_URL=$NOVA_PUBLIC_URL
export NOVA_INTERNAL_URL=$NOVA_PUBLIC_URL
2) creating services:
keystone service-create --name nova --type compute --description
'OpenStack Compute Service'
keystone service-create --name swift --type object-store --description
'OpenStack Storage Service'
keystone service-create --name glance --type image --description
'OpenStack Image Service'
keystone service-create --name keystone --type identity --description
'OpenStack Identity Service'
3) creating an endpoint for those services, starting with the compute
service:
ID=$(keystone service-list | grep -i compute | awk '{print $2}')
keystone endpoint-create --region RegionOne --service_id $ID --publicurl
$NOVA_PUBLIC_URL --adminurl $NOVA_ADMIN_URL --internalurl $NOVA_INTERNAL_URL
When i run this command with milestone-proposed, i experience the following:
No handlers could be found for logger keystoneclient.client
The action you have requested has not been implemented. (HTTP 501)
Strangely enough, i experience a similar error message when running a
simple keystone endpoint-list whereas command such as keystone
user-list works all right.
here is what i have in the keystone logs when trying endpoint-list:
2012-03-24 20:30:09DEBUG [routes.middleware] Matched GET /endpoints
2012-03-24 20:30:09DEBUG [routes.middleware] Route path:
'{path_info:.*}', defaults: {'controller':
keystone.contrib.admin_crud.core.CrudExtension object at 0x2b215d0}
2012-03-24 20:30:09DEBUG [routes.middleware] Match dict:
{'controller': keystone.contrib.admin_crud.core.CrudExtension object at
0x2b215d0, 'path_info': '/endpoints'}
2012-03-24 20:30:09DEBUG [routes.middleware] Matched GET /endpoints
2012-03-24 20:30:09DEBUG [routes.middleware] Route path:
'/endpoints', defaults: {'action': u'get_endpoints', 'controller':
keystone.catalog.core.EndpointController object at 0x2b21210}
2012-03-24 20:30:09DEBUG [routes.middleware] Match dict: {'action':
u'get_endpoints', 'controller':
keystone.catalog.core.EndpointController object at 0x2b21210}
2012-03-24 20:30:09DEBUG [keystone.common.wsgi] arg_dict: {}
2012-03-24 20:30:09 WARNING [keystone.common.wsgi] The action you have
requested has not been implemented.
2012-03-24 20:30:09DEBUG [keystone.common.wsgi]
RESPONSE HEADERS
2012-03-24 20:30:09DEBUG [keystone.common.wsgi] Content-Type =
application/json
2012-03-24 20:30:09DEBUG [keystone.common.wsgi] Vary = X-Auth-Token
2012-03-24 20:30:09DEBUG [keystone.common.wsgi] Content-Length = 109
2012-03-24 20:30:09DEBUG [keystone.common.wsgi]
2012-03-24 20:30:09DEBUG [keystone.common.wsgi]
RESPONSE BODY
I try to add some debug in
keystone.catalog.core.EndpointController.get_endpoints() method:
def get_endpoints(self, context):
LOG.debug(PLOP get_endpoints)
self.assert_admin(context)
LOG.debug(PLOP STILL HERE) # = LAST DEBUG LINE
endpoint_list = self.catalog_api.list_endpoints(context)
LOG.debug(SO, how does endpoint_list looks like ?)
for i in endpoint_list:
LOG.debug(PLOP: '%s',s)
endpoint_refs = [self.catalog_api.get_endpoint(context, e)
for e in endpoint_list]
LOG.debug(PLOP THIS IS THE END)
return {'endpoints': endpoint_refs}
So, as i do not see anything after PLOP STILL HERE, i am assuming
something is wrong in the catalog_api.list_endpoints() method.
[Openstack] hardware specifications for a little private cloud
Hi all, I'm a teacher at a sysadmin academy and we are planning to deploy a private cloud with OpenStack for educational/training purposes. We are currently selecting the optimal hardware configuration for our needs and I'm asking for some help to the list. Using [1] as a reference, we are clear about hardware specifications of compute nodes (4 nodes with 2 processors), but we aren't about the best solution for node controller and optimal storage: Option 1: 1 server with 2 HD in RAID1 (nova controller, nova volume, glance, ...) + 1 SAN iSCSI Option 2: 1 server with 12 HD in RAID5/6 (nova controller, nova volume, glance, ...) We are excited about the possibilities that a private cloud brings to us and we don't want to fail in this critical step, so any help will be really appreciated. Alberto Molina Coballes IES Gonzalo Nazareno [1] http://www.referencearchitecture.org/hardware-specifications/ ___ 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] [OpenStack Foundation] Orchestration with Openstack
(switching to the openstack list, the foundation list is meant for the organization of the openstack foundation) There are some efforts around using Chef from opscode, and tools built around it to do what I think you describe - look in the mailing list archive ( which is also a good way to identify the right list to use) On Mar 26, 2012, at 4:26 AM, Rahul Bhardwaj bhardwaj.rahu...@gmail.com wrote: I am new to this list so not sure about the relevance of question, forum or discusstion topic. I apologize if there is mismatch anywhere above. I was wondering about the possible ways of getting VM provisioning activity defined as a workflow and than managing it using the orchestrator. I have tried mCollective and celery but none worked. I was thinking, will Puppet+mCollective do the trick or maybe one of the opensource tools such as orchestra or archipel can be used to automate the workflow. Looking for some suggestions. -Rahul ___ Foundation mailing list foundat...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation ___ 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] hardware specifications for a little private cloud
Hello Alberto,I would advise you to deploy as much as node as you can, and dedicate separate services. That would bring you the possibility to extend your knowledge on HA mechanisms, and really understand how services interact each other.Let's say you spawn an instance from the api server, while it's is launched on a compute node - which is one another server. By having splitted architecture, you won't miss the obvious ;-)What is the purpose of the lab ? Nuage Co - Razique Mahrouarazique.mahr...@gmail.com Le 26 mars 2012 à 12:56, Alberto Molina Coballes a écrit :Hi all,I'm a teacher at a sysadmin academy and we are planning to deploy aprivate cloud with OpenStack for educational/training purposes. We arecurrently selecting the optimal hardware configuration for our needsand I'm asking for some help to the list.Using [1] as a reference, we are clear about hardware specificationsof compute nodes (4 nodes with 2 processors), but we aren't about thebest solution for node controller and optimal storage:Option 1:1 server with 2 HD in RAID1 (nova controller, nova volume, glance,...) + 1 SAN iSCSIOption 2:1 server with 12 HD in RAID5/6 (nova controller, nova volume, glance, ...)We are excited about the possibilities that a private cloud brings tous and we don't want to fail in this critical step, so any help willbe really appreciated.Alberto Molina CoballesIES Gonzalo Nazareno[1] http://www.referencearchitecture.org/hardware-specifications/___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help : https://help.launchpad.net/ListHelp___ 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] is this a bug in milestone-proposed keystone ? (cannotget endpoint-list, nor create endpoint)
Can you include your config?
The behavior you're describing seems to be consistent with a missing backers
configuration ...
Something like:
[identity]
driver = keystone.identity.backends.sql.Identity
[catalog]
driver = keystone.catalog.backends.sql.Catalog
Also, where/how are you installing?
On Mar 26, 2012, at 6:56 AM, Mandar Vaze mandar.v...@vertex.co.in wrote:
I’m also getting the same error on latest master branch (updated today)
Using setup created by devstack
-Mandar
From: openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net] On
Behalf Of .?o 0 O??
Sent: Monday, March 26, 2012 12:45 PM
To: Pierre Amadio
Cc: openstack
Subject: Re: [Openstack] is this a bug in milestone-proposed keystone ?
(cannotget endpoint-list, nor create endpoint)
hi,
I don't know if it is a bug but I come across the same problem and wondering
how to solve it.
-- Original --
From: Pierre Amadiopierre.ama...@canonical.com;
Date: Sun, Mar 25, 2012 04:35 AM
To: openstackopenstack@lists.launchpad.net;
Subject: [Openstack] is this a bug in milestone-proposed keystone ?
(cannotget endpoint-list, nor create endpoint)
Hi there !
I wanted to give a try to the milestone-proposed branch of keystone and
got stuck quite fast.
I am not sure if i hit a bug and should report it, or if i'm doing
something wrong.
With previous version of keystone (read packaged on ubuntu precise), i
was able to create endpoint the following way once keystone has been
installed:
1) setting some env variables:
export KEYSTONE_IP=192.168.122.102 # IP of your keystone API server
export SERVICE_ENDPOINT=http://$KEYSTONE_IP:35357/v2.0/
export SERVICE_TOKEN=999888777666
export NOVA_PUBLIC_URL=http://$NOVA_IP:8774/v1.1/%(tenant_id)s
export NOVA_ADMIN_URL=$NOVA_PUBLIC_URL
export NOVA_INTERNAL_URL=$NOVA_PUBLIC_URL
2) creating services:
keystone service-create --name nova --type compute --description
'OpenStack Compute Service'
keystone service-create --name swift --type object-store --description
'OpenStack Storage Service'
keystone service-create --name glance --type image --description
'OpenStack Image Service'
keystone service-create --name keystone --type identity --description
'OpenStack Identity Service'
3) creating an endpoint for those services, starting with the compute
service:
ID=$(keystone service-list | grep -i compute | awk '{print $2}')
keystone endpoint-create --region RegionOne --service_id $ID --publicurl
$NOVA_PUBLIC_URL --adminurl $NOVA_ADMIN_URL --internalurl $NOVA_INTERNAL_URL
When i run this command with milestone-proposed, i experience the following:
No handlers could be found for logger keystoneclient.client
The action you have requested has not been implemented. (HTTP 501)
Strangely enough, i experience a similar error message when running a
simple keystone endpoint-list whereas command such as keystone
user-list works all right.
here is what i have in the keystone logs when trying endpoint-list:
2012-03-24 20:30:09DEBUG [routes.middleware] Matched GET /endpoints
2012-03-24 20:30:09DEBUG [routes.middleware] Route path:
'{path_info:.*}', defaults: {'controller':
keystone.contrib.admin_crud.core.CrudExtension object at 0x2b215d0}
2012-03-24 20:30:09DEBUG [routes.middleware] Match dict:
{'controller': keystone.contrib.admin_crud.core.CrudExtension object at
0x2b215d0, 'path_info': '/endpoints'}
2012-03-24 20:30:09DEBUG [routes.middleware] Matched GET /endpoints
2012-03-24 20:30:09DEBUG [routes.middleware] Route path:
'/endpoints', defaults: {'action': u'get_endpoints', 'controller':
keystone.catalog.core.EndpointController object at 0x2b21210}
2012-03-24 20:30:09DEBUG [routes.middleware] Match dict: {'action':
u'get_endpoints', 'controller':
keystone.catalog.core.EndpointController object at 0x2b21210}
2012-03-24 20:30:09DEBUG [keystone.common.wsgi] arg_dict: {}
2012-03-24 20:30:09 WARNING [keystone.common.wsgi] The action you have
requested has not been implemented.
2012-03-24 20:30:09DEBUG [keystone.common.wsgi]
RESPONSE HEADERS
2012-03-24 20:30:09DEBUG [keystone.common.wsgi] Content-Type =
application/json
2012-03-24 20:30:09DEBUG [keystone.common.wsgi] Vary = X-Auth-Token
2012-03-24 20:30:09DEBUG [keystone.common.wsgi] Content-Length = 109
2012-03-24 20:30:09DEBUG [keystone.common.wsgi]
2012-03-24 20:30:09DEBUG [keystone.common.wsgi]
RESPONSE BODY
I try to add some debug in
keystone.catalog.core.EndpointController.get_endpoints() method:
def get_endpoints(self, context):
LOG.debug(PLOP get_endpoints)
self.assert_admin(context)
LOG.debug(PLOP STILL HERE) # = LAST DEBUG LINE
endpoint_list =
[Openstack] Crowbar problem (using Rob's ISO)
Hi All, I have tried installing OpenStack using the crowbar ISO provided by Rob (http://crowbar.zehicle.com/crowbar111219.iso) and successfully installed the admin node. But when it comes to PXE boot of the other crowbar nodes, the installation gets stuck showing: HOSTNAME=h00-0c-29-58-21-fe.crowbar.org NODE_STATE= /usr/lib/ruby/gems/1.8/gems/json-1.4.6/lib/json/common.rb:146 in ‘parse’: 705: unexpected token at ‘Host not found’ (JSON::ParserError) from /usr/lib/ruby/gems/1.8/gems/json1.4.6/lib/json/common.rb:146 in ‘parse’ from /updates/parse_node_data:57:in ‘main’ from /updates/parse_node_data:69 BMC_ROUTER= BMC_ADDRESS= BMC_NETMASK= /usr/lib/ruby/gems/1.8/gems/json-1.4.6/lib/json/common.rb:146 in ‘parse’: 705:unexpected token at ‘Host not found’ (JSON::ParserError) from /usr/lib/ruby/gems/1.8/gems/json1.4.6/lib/json/common.rb:146 in ‘parse’ from /updates/parse_node_data:57:in ‘main’ from /updates/parse_node_data:69 BMC_ROUTER= BMC_ADDRESS= BMC_NETMASK= HOSTNAME=h00-0c-29-58-21-fe.crowbar.org NODE_STATE= This problem has already been reported at Rob's blog but I am not sure if it is fixed. Any ideas? Thanks. ___ 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] BUG on dashboard (Horizon)
Hello folks, I'm having a bug on Horizon, i've installed it using the Diablo version, following the oficial tutorial. I can acess the dashboard, up instances, but when i try to acess the users and tenants page it prints a Error, to Users Unable to list users: [Errno 113] EHOSTUNREACH, or to tenants Unable to get tenant info: [Errno 113] EHOSTUNREACH, but it doesn't crashes the GUI. And in another installation at the same version of Dashboard, Diablo, it prints a timeout message and doesn't crashes the GUI too. Someone had the same error? Gratz Guilherme Souza ___ 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] Keystone auth issues with Swift
On Mon, Mar 26, 2012 at 10:30 AM, Haefliger, Juerg juerg.haefli...@hp.com wrote: I'm struggling a bit with the unit test. I added a test_swift_store.add_auth_v2 unit test but it's not doing much since the swift.common.client get_auth call is stubbed out and always succeeds. What exactly should I be testing for? I was thinking of modifying fake_auth_get to check that auth_version is as expected when using auth 2. I think that should be good for a start. Chmouel. ___ 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] Re： is this a bug in milestone-proposed keystone ? (cannot get endpoint-list, nor create endpoint)
I just get code from www.launchpad.net/keystone and do python setup.py
install.
the keystone.conf in /etc/keystone is default from the code package
Yes ,I can see it include my keystone.conf in the output of keystone-all
command.
-- 原始邮件 --
发件人: Andiabesandi.a...@gmail.com;
发送时间: 2012年3月26日(星期一) 晚上7:25
收件人: Mandar Vazemandar.v...@vertex.co.in;
抄送: .。o 0 O泡泡 501640...@qq.com; Pierre
Amadiopierre.ama...@canonical.com;
openstackopenstack@lists.launchpad.net;
主题: Re: [Openstack] is this a bug in milestone-proposed keystone ? (cannotget
endpoint-list, nor create endpoint)
Can you include your config?
The behavior you're describing seems to be consistent with a missing backers
configuration ...
Something like:
[identity]
driver = keystone.identity.backends.sql.Identity
[catalog]
driver = keystone.catalog.backends.sql.Catalog
Also, where/how are you installing?
On Mar 26, 2012, at 6:56 AM, Mandar Vaze mandar.v...@vertex.co.in wrote:
I’m also getting the same error on latest master branch (updated today)
Using setup created by devstack
-Mandar
From: openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net] On
Behalf Of .?o 0 O??
Sent: Monday, March 26, 2012 12:45 PM
To: Pierre Amadio
Cc: openstack
Subject: Re: [Openstack] is this a bug in milestone-proposed keystone ?
(cannotget endpoint-list, nor create endpoint)
hi,
I don't know if it is a bug but I come across the same problem and wondering
how to solve it.
-- Original --
From: Pierre Amadiopierre.ama...@canonical.com;
Date: Sun, Mar 25, 2012 04:35 AM
To: openstackopenstack@lists.launchpad.net;
Subject: [Openstack] is this a bug in milestone-proposed keystone ? (cannotget
endpoint-list, nor create endpoint)
Hi there !
I wanted to give a try to the milestone-proposed branch of keystone and
got stuck quite fast.
I am not sure if i hit a bug and should report it, or if i'm doing
something wrong.
With previous version of keystone (read packaged on ubuntu precise), i
was able to create endpoint the following way once keystone has been
installed:
1) setting some env variables:
export KEYSTONE_IP=192.168.122.102 # IP of your keystone API server
export SERVICE_ENDPOINT=http://$KEYSTONE_IP:35357/v2.0/
export SERVICE_TOKEN=999888777666
export NOVA_PUBLIC_URL=http://$NOVA_IP:8774/v1.1/%(tenant_id)s
export NOVA_ADMIN_URL=$NOVA_PUBLIC_URL
export NOVA_INTERNAL_URL=$NOVA_PUBLIC_URL
2) creating services:
keystone service-create --name nova --type compute --description
'OpenStack Compute Service'
keystone service-create --name swift --type object-store --description
'OpenStack Storage Service'
keystone service-create --name glance --type image --description
'OpenStack Image Service'
keystone service-create --name keystone --type identity --description
'OpenStack Identity Service'
3) creating an endpoint for those services, starting with the compute
service:
ID=$(keystone service-list | grep -i compute | awk '{print $2}')
keystone endpoint-create --region RegionOne --service_id $ID --publicurl
$NOVA_PUBLIC_URL --adminurl $NOVA_ADMIN_URL --internalurl $NOVA_INTERNAL_URL
When i run this command with milestone-proposed, i experience the following:
No handlers could be found for logger keystoneclient.client
The action you have requested has not been implemented. (HTTP 501)
Strangely enough, i experience a similar error message when running a
simple keystone endpoint-list whereas command such as keystone
user-list works all right.
here is what i have in the keystone logs when trying endpoint-list:
2012-03-24 20:30:09DEBUG [routes.middleware] Matched GET /endpoints
2012-03-24 20:30:09DEBUG [routes.middleware] Route path:
'{path_info:.*}', defaults: {'controller':
keystone.contrib.admin_crud.core.CrudExtension object at 0x2b215d0}
2012-03-24 20:30:09DEBUG [routes.middleware] Match dict:
{'controller': keystone.contrib.admin_crud.core.CrudExtension object at
0x2b215d0, 'path_info': '/endpoints'}
2012-03-24 20:30:09DEBUG [routes.middleware] Matched GET /endpoints
2012-03-24 20:30:09DEBUG [routes.middleware] Route path:
'/endpoints', defaults: {'action': u'get_endpoints', 'controller':
keystone.catalog.core.EndpointController object at 0x2b21210}
2012-03-24 20:30:09DEBUG [routes.middleware] Match dict: {'action':
u'get_endpoints', 'controller':
keystone.catalog.core.EndpointController object at 0x2b21210}
2012-03-24 20:30:09DEBUG [keystone.common.wsgi] arg_dict: {}
2012-03-24 20:30:09 WARNING [keystone.common.wsgi] The action you have
requested has not been implemented.
2012-03-24 20:30:09DEBUG [keystone.common.wsgi]
RESPONSE HEADERS
2012-03-24 20:30:09DEBUG [keystone.common.wsgi] Content-Type =
application/json
2012-03-24 20:30:09DEBUG [keystone.common.wsgi] Vary =
Re: [Openstack] BUG on dashboard (Horizon)
Hello Guillherme;looks like the Keystone server is not reachable. What type of install did you make ? Nuage Co - Razique Mahrouarazique.mahr...@gmail.com Le 23 mars 2012 à 20:20, Guilherme Souza a écrit :Hello folks,I'm having a bug on Horizon, i've installed it using the Diablo version, following the oficial tutorial. I can acess the dashboard, up instances, but when i try to acess the users and tenants page it prints a Error, to Users "Unable to list users: [Errno 113] EHOSTUNREACH", or to tenants "Unable to get tenant info: [Errno 113] EHOSTUNREACH", but it doesn't crashes the GUI. And in another installation at the same version of Dashboard, Diablo, it prints a timeout message and doesn't crashes the GUI too.Someone had the same error?GratzGuilherme Souza ___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help : https://help.launchpad.net/ListHelp___ 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] 回复： is this a bug in milestone-proposed keystone ? (cannotget endpoint-list, nor create endpoint)
found the solution:
in keystone.conf
you need to change :
[catalog]
driver = keystone.catalog.backends.templated.TemplatedCatalog
to：
[catalog]
driver = keystone.catalog.backends.templated.TemplatedCatalog
-- 原始邮件 --
发件人: Andiabesandi.a...@gmail.com;
发送时间: 2012年3月26日(星期一) 晚上7:25
收件人: Mandar Vazemandar.v...@vertex.co.in;
抄送: .。o 0 O泡泡 501640...@qq.com; Pierre
Amadiopierre.ama...@canonical.com;
openstackopenstack@lists.launchpad.net;
主题: Re: [Openstack] is this a bug in milestone-proposed keystone ? (cannotget
endpoint-list, nor create endpoint)
Can you include your config?
The behavior you're describing seems to be consistent with a missing backers
configuration ...
Something like:
[identity]
driver = keystone.identity.backends.sql.Identity
[catalog]
driver = keystone.catalog.backends.sql.Catalog
Also, where/how are you installing?
On Mar 26, 2012, at 6:56 AM, Mandar Vaze mandar.v...@vertex.co.in wrote:
I’m also getting the same error on latest master branch (updated today)
Using setup created by devstack
-Mandar
From: openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net] On
Behalf Of .?o 0 O??
Sent: Monday, March 26, 2012 12:45 PM
To: Pierre Amadio
Cc: openstack
Subject: Re: [Openstack] is this a bug in milestone-proposed keystone ?
(cannotget endpoint-list, nor create endpoint)
hi,
I don't know if it is a bug but I come across the same problem and wondering
how to solve it.
-- Original --
From: Pierre Amadiopierre.ama...@canonical.com;
Date: Sun, Mar 25, 2012 04:35 AM
To: openstackopenstack@lists.launchpad.net;
Subject: [Openstack] is this a bug in milestone-proposed keystone ? (cannotget
endpoint-list, nor create endpoint)
Hi there !
I wanted to give a try to the milestone-proposed branch of keystone and
got stuck quite fast.
I am not sure if i hit a bug and should report it, or if i'm doing
something wrong.
With previous version of keystone (read packaged on ubuntu precise), i
was able to create endpoint the following way once keystone has been
installed:
1) setting some env variables:
export KEYSTONE_IP=192.168.122.102 # IP of your keystone API server
export SERVICE_ENDPOINT=http://$KEYSTONE_IP:35357/v2.0/
export SERVICE_TOKEN=999888777666
export NOVA_PUBLIC_URL=http://$NOVA_IP:8774/v1.1/%(tenant_id)s
export NOVA_ADMIN_URL=$NOVA_PUBLIC_URL
export NOVA_INTERNAL_URL=$NOVA_PUBLIC_URL
2) creating services:
keystone service-create --name nova --type compute --description
'OpenStack Compute Service'
keystone service-create --name swift --type object-store --description
'OpenStack Storage Service'
keystone service-create --name glance --type image --description
'OpenStack Image Service'
keystone service-create --name keystone --type identity --description
'OpenStack Identity Service'
3) creating an endpoint for those services, starting with the compute
service:
ID=$(keystone service-list | grep -i compute | awk '{print $2}')
keystone endpoint-create --region RegionOne --service_id $ID --publicurl
$NOVA_PUBLIC_URL --adminurl $NOVA_ADMIN_URL --internalurl $NOVA_INTERNAL_URL
When i run this command with milestone-proposed, i experience the following:
No handlers could be found for logger keystoneclient.client
The action you have requested has not been implemented. (HTTP 501)
Strangely enough, i experience a similar error message when running a
simple keystone endpoint-list whereas command such as keystone
user-list works all right.
here is what i have in the keystone logs when trying endpoint-list:
2012-03-24 20:30:09DEBUG [routes.middleware] Matched GET /endpoints
2012-03-24 20:30:09DEBUG [routes.middleware] Route path:
'{path_info:.*}', defaults: {'controller':
keystone.contrib.admin_crud.core.CrudExtension object at 0x2b215d0}
2012-03-24 20:30:09DEBUG [routes.middleware] Match dict:
{'controller': keystone.contrib.admin_crud.core.CrudExtension object at
0x2b215d0, 'path_info': '/endpoints'}
2012-03-24 20:30:09DEBUG [routes.middleware] Matched GET /endpoints
2012-03-24 20:30:09DEBUG [routes.middleware] Route path:
'/endpoints', defaults: {'action': u'get_endpoints', 'controller':
keystone.catalog.core.EndpointController object at 0x2b21210}
2012-03-24 20:30:09DEBUG [routes.middleware] Match dict: {'action':
u'get_endpoints', 'controller':
keystone.catalog.core.EndpointController object at 0x2b21210}
2012-03-24 20:30:09DEBUG [keystone.common.wsgi] arg_dict: {}
2012-03-24 20:30:09 WARNING [keystone.common.wsgi] The action you have
requested has not been implemented.
2012-03-24 20:30:09DEBUG [keystone.common.wsgi]
RESPONSE HEADERS
2012-03-24 20:30:09DEBUG [keystone.common.wsgi] Content-Type =
application/json
2012-03-24 20:30:09DEBUG [keystone.common.wsgi] Vary = X-Auth-Token
2012-03-24
[Openstack] essex rc1: rabbit time out when runing nova x509-get-root-cert
Hi there !
I am trying to have a 4 node essex-rc1 setup running
nova/kesytone/glance (no swift, no horizon).
Things have been installed from the milestone-proposed branch of each
project.
I reach the stage where some nova command works (such as nova
flavor-list), but i cannot get a root certificate with
nova x509-get-root-cert
It looks to me nova-api send the request to rabbit, but that nobody
reply to it.
You will find more details (environment variables, nova-api logs, nova
--debug output and mostly empty rabbit log) in the attached pb-cert.txt
file.
Any idea what could be wrong ?
192.168.122.101: manager node (nova-api,
nova-objectstore,nova-scheduler,nova-volume)
192.168.122.102: messaging (rabbit, keystone, glance, mysql)
192.168.122.103: nova-compute nova-network
192.168.122.104: nova-compute
nova command seems to work:
ubuntu@manager-node:~/creds$ cat openrc
# OS API settings
export NOVA_USERNAME=ubuntu
export NOVA_PROJECT_ID=ubuntu
export NOVA_PASSWORD=openstack
export NOVA_API_KEY=${NOVA_PASSWORD}
#where keystone runs
export NOVA_URL=http://192.168.122.102:35357/v2.0/
export NOVA_VERSION=1.1
export NOVA_REGION_NAME=RegionOne
export OS_AUTH_USER=${NOVA_USERNAME}
export OS_AUTH_KEY=${NOVA_PASSWORD}
export OS_AUTH_TENANT=${NOVA_PROJECT_ID}
export OS_AUTH_URL=${NOVA_URL}
export OS_AUTH_STRATEGY=keystone
# EC2 API settings
# Set the ec2 url so euca2ools works
export EC2_URL=${EC2_URL:-http://192.168.122.101:8773/services/Cloud}
# Access key is set in the initial keystone data to be the same as username
export EC2_ACCESS_KEY=3afad56c1e47481991e70b7094650d1a
# Secret key is set in the initial keystone data to the admin password
export EC2_SECRET_KEY=59cf599d36264764a7bd288ed87136bc
#export EC2_CERT=/home/ubuntu/creds/cacert.pem
#export EC2_PRIVATE_KEY=/home/ubuntu/creds/cert.pem
ubuntu@manager-node:~/creds$ . openrc
ubuntu@manager-node:~/creds$ nova flavor-list
++---+---+--+---+--+---+-+
| ID |Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor |
++---+---+--+---+--+---+-+
| 1 | m1.tiny | 512 | 0| 0 | | 1 | 1.0 |
| 2 | m1.small | 2048 | 10 | 20| | 1 | 1.0 |
| 3 | m1.medium | 4096 | 10 | 40| | 2 | 1.0 |
| 4 | m1.large | 8192 | 10 | 80| | 4 | 1.0 |
| 5 | m1.xlarge | 16384 | 10 | 160 | | 8 | 1.0 |
++---+---+--+---+--+---+-+
But i experience a time out when trying to launch the following:
ubuntu@manager-node:~/creds$ nova --debug x509-get-root-cert
connect: (192.168.122.102, 35357)
send: 'POST /v2.0/tokens HTTP/1.1\r\nHost:
192.168.122.102:35357\r\nContent-Length: 106\r\ncontent-type:
application/json\r\naccept-encoding: gzip, deflate\r\naccept:
application/json\r\nuser-agent: python-novaclient\r\n\r\n{auth:
{tenantName: ubuntu, passwordCredentials: {username: ubuntu,
password: openstack}}}'
reply: 'HTTP/1.1 200 OK\r\n'
header: Content-Type: application/json
header: Vary: X-Auth-Token
header: Content-Length: 1645
header: Date: Mon, 26 Mar 2012 11:44:36 GMT
connect: (192.168.122.101, 8774)
send: u'GET /v1.1/a07fd73258684caaa86edcaabd7a16b0/os-certificates/root
HTTP/1.1\r\nHost: 192.168.122.101:8774\r\nx-auth-project-id:
ubuntu\r\nx-auth-token: b59aedb8cca04336a47dec804a382657\r\naccept-encoding:
gzip, deflate\r\naccept: application/json\r\nuser-agent:
python-novaclient\r\n\r\n'
reply: 'HTTP/1.1 500 Internal Server Error\r\n'
header: Content-Length: 128
header: Content-Type: application/json; charset=UTF-8
header: X-Compute-Request-Id: req-161614ff-cf70-4aba-a8f2-9116924eec7b
header: Date: Mon, 26 Mar 2012 11:45:36 GMT
DEBUG (shell:416) The server has either erred or is incapable of performing the
requested operation. (HTTP 500)
Traceback (most recent call last):
File
/usr/local/lib/python2.7/dist-packages/python_novaclient-2012.1-py2.7.egg/novaclient/shell.py,
line 413, in main
OpenStackComputeShell().main(sys.argv[1:])
File
/usr/local/lib/python2.7/dist-packages/python_novaclient-2012.1-py2.7.egg/novaclient/shell.py,
line 364, in main
args.func(self.cs, args)
File
/usr/local/lib/python2.7/dist-packages/python_novaclient-2012.1-py2.7.egg/novaclient/v1_1/shell.py,
line 1458, in do_x509_get_root_cert
cacert = cs.certs.get()
File
/usr/local/lib/python2.7/dist-packages/python_novaclient-2012.1-py2.7.egg/novaclient/v1_1/certs.py,
line 48, in get
return self._get(/os-certificates/root, 'certificate')
File
/usr/local/lib/python2.7/dist-packages/python_novaclient-2012.1-py2.7.egg/novaclient/base.py,
line 149, in _get
resp, body = self.api.client.get(url)
File
/usr/local/lib/python2.7/dist-packages/python_novaclient-2012.1-py2.7.egg/novaclient/client.py,
line 136, in get
return self._cs_request(url,
Re: [Openstack] Crowbar problem (using Rob's ISO)
Hi Salman, a) it might be more appropriate to post Crowbar specific questions on the crowbar mailing list... crow...@lists.us.dell.com b) The errors you're seeing seem to be cause the node failing to communicate with the admin node (it did for a while, then something changed...). That code is being hardened now, but in the version you're using it was still a bit brittle. You can reboot the node, it will probably recover, and continue the deployment sequence. It might be useful to get the details how you arrived at this situation. On Fri, Mar 23, 2012 at 1:31 PM, Salman Malik salma...@live.com wrote: Hi All, I have tried installing OpenStack using the crowbar ISO provided by Rob (http://crowbar.zehicle.com/crowbar111219.iso) and successfully installed the admin node. But when it comes to PXE boot of the other crowbar nodes, the installation gets stuck showing: HOSTNAME=h00-0c-29-58-21-fe.crowbar.org NODE_STATE= /usr/lib/ruby/gems/1.8/gems/json-1.4.6/lib/json/common.rb:146 in ‘parse’: 705: unexpected token at ‘Host not found’ (JSON::ParserError) from /usr/lib/ruby/gems/1.8/gems/json1.4.6/lib/json/common.rb:146 in ‘parse’ from /updates/parse_node_data:57:in ‘main’ from /updates/parse_node_data:69 BMC_ROUTER= BMC_ADDRESS= BMC_NETMASK= /usr/lib/ruby/gems/1.8/gems/json-1.4.6/lib/json/common.rb:146 in ‘parse’: 705:unexpected token at ‘Host not found’ (JSON::ParserError) from /usr/lib/ruby/gems/1.8/gems/json1.4.6/lib/json/common.rb:146 in ‘parse’ from /updates/parse_node_data:57:in ‘main’ from /updates/parse_node_data:69 BMC_ROUTER= BMC_ADDRESS= BMC_NETMASK= HOSTNAME=h00-0c-29-58-21-fe.crowbar.org NODE_STATE= This problem has already been reported at Rob's blog but I am not sure if it is fixed. Any ideas? Thanks. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] KVM disk performance
Hi List, I have a question about KVM disk performance. We are using Openstack Nova on three machines. These machines have a SSD drive with a dd write performance of about 130mb/s Within the instance the write performance is down to about 5 mb/s. When using the allocate trick (dd zero to disk before newfs) we get a performance of 20 mb/s. Things a have tried but don't give any extra results are: - Settings the disklayout from qcow2 to raw - Settings the cache type in libvirt.xml (writeback, writethrough, none) - Switching KSM on and off. - Tested with different guests OS, Linux, FreeBSD, Windows. Is there someone who had some extra info i can check? Or are there more people with this issue? Snippet from libvirt.xml driver type='qcow2'/ cache='writeback'/ source file='/var/lib/nova/instances/instance-0113/disk'/ target dev='vda' bus='virtio'/ Kind regards, Martin ___ 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] essex rc1: rabbit time out when runing nova x509-get-root-cert
On Mon, Mar 26 2012, Pierre Amadio wrote: Any idea what could be wrong ? You must `nova-cert' daemon running to make this work. -- Julien Danjou // eNovance http://enovance.com // ✉ julien.dan...@enovance.com ☎ +33 1 49 70 99 81 ___ 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] [OpenStack Foundation] Orchestration with Openstack
On 03/26/2012 03:58 AM, Andiabes wrote: (switching to the openstack list, the foundation list is meant for the organization of the openstack foundation) There are some efforts around using Chef from opscode, and tools built around it to do what I think you describe - look in the mailing list archive ( which is also a good way to identify the right list to use) On Mar 26, 2012, at 4:26 AM, Rahul Bhardwaj bhardwaj.rahu...@gmail.com wrote: I am new to this list so not sure about the relevance of question, forum or discusstion topic. I apologize if there is mismatch anywhere above. I was wondering about the possible ways of getting VM provisioning activity defined as a workflow and than managing it using the orchestrator. I have tried mCollective and celery but none worked. I was thinking, will Puppet+mCollective do the trick or maybe one of the opensource tools such as orchestra or archipel can be used to automate the workflow. Looking for some suggestions. -Rahul Rahul, A couple of folks are on implementing AWS CloudFormations. This system takes a template and turns it into a running set of VMs. It may not meet your requirement of working since we just started development a few weeks ago. If you want to have a look: https://github.com/heat-api Note our diagrams are a bit out of date - might check my github account for those. Regards -steve ___ Foundation mailing list foundat...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] BUG on dashboard (Horizon)
Hello Razique, What do you want to say with: What type of install..., i've installed following the oficial tutorial http://docs.openstack.org/diablo/openstack-compute/install/content/, and keystone looks like working fine, apparently can i access the dashboardwithout problems. Em 26 de março de 2012 09:18, Razique Mahroua razique.mahr...@gmail.comescreveu: Hello Guillherme; looks like the Keystone server is not reachable. What type of install did you make ? *Nuage Co - Razique Mahroua** * razique.mahr...@gmail.com Le 23 mars 2012 à 20:20, Guilherme Souza a écrit : Hello folks, I'm having a bug on Horizon, i've installed it using the Diablo version, following the oficial tutorial. I can acess the dashboard, up instances, but when i try to acess the users and tenants page it prints a Error, to Users Unable to list users: [Errno 113] EHOSTUNREACH, or to tenants Unable to get tenant info: [Errno 113] EHOSTUNREACH, but it doesn't crashes the GUI. And in another installation at the same version of Dashboard, Diablo, it prints a timeout message and doesn't crashes the GUI too. Someone had the same error? Gratz Guilherme Souza ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Atenciosamente, Guilherme Santos Souza Sistemas de Informação - PUCRS Fone: (51) 9695-1070 NUAGECO-LOGO-Fblan_petit.jpg___ 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] KVM disk performance
Have you tried virtio for storage? http://www.linux-kvm.org/page/Virtio Enviado desde mi iPhone, perdona la brevedad El 26/03/2012, a las 14:59, Martin van Wilderen - JDN BV mar...@jdn.nl escribió: Hi List, I have a question about KVM disk performance. We are using Openstack Nova on three machines. These machines have a SSD drive with a dd write performance of about 130mb/s Within the instance the write performance is down to about 5 mb/s. When using the allocate trick (dd zero to disk before newfs) we get a performance of 20 mb/s. Things a have tried but don't give any extra results are: - Settings the disklayout from qcow2 to raw - Settings the cache type in libvirt.xml (writeback, writethrough, none) - Switching KSM on and off. - Tested with different guests OS, Linux, FreeBSD, Windows. Is there someone who had some extra info i can check? Or are there more people with this issue? Snippet from libvirt.xml driver type='qcow2'/ cache='writeback'/ source file='/var/lib/nova/instances/instance-0113/disk'/ target dev='vda' bus='virtio'/ Kind regards, Martin ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] 回复： is this a bug in milestone-proposed keystone ? (cannotget endpoint-list, nor create endpoint)
From and To look identical.
What should the [catalog] value be changed to ?
-Mandar
From: openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net] On
Behalf Of .?o 0 O??
Sent: Monday, March 26, 2012 6:02 PM
To: Andiabes
Cc: openstack
Subject: [Openstack] 回复： is this a bug in milestone-proposed keystone ?
(cannotget endpoint-list, nor create endpoint)
found the solution:
in keystone.conf
you need to change :
[catalog]
driver = keystone.catalog.backends.templated.TemplatedCatalog
to：
[catalog]
driver = keystone.catalog.backends.templated.TemplatedCatalog
-- 原始邮件 --
发件人: Andiabesandi.a...@gmail.commailto:andi.a...@gmail.com;
发送时间: 2012年3月26日(星期一) 晚上7:25
收件人: Mandar Vazemandar.v...@vertex.co.inmailto:mandar.v...@vertex.co.in;
抄送: .。o 0 O泡泡 501640...@qq.commailto:501640...@qq.com; Pierre
Amadiopierre.ama...@canonical.commailto:pierre.ama...@canonical.com;
openstackopenstack@lists.launchpad.netmailto:openstack@lists.launchpad.net;
主题: Re: [Openstack] is this a bug in milestone-proposed keystone ? (cannotget
endpoint-list, nor create endpoint)
Can you include your config?
The behavior you're describing seems to be consistent with a missing backers
configuration ...
Something like:
[identity]
driver = keystone.identity.backends.sql.Identity
[catalog]
driver = keystone.catalog.backends.sql.Catalog
Also, where/how are you installing?
On Mar 26, 2012, at 6:56 AM, Mandar Vaze
mandar.v...@vertex.co.inmailto:mandar.v...@vertex.co.in wrote:
I’m also getting the same error on latest master branch (updated today)
Using setup created by devstack
-Mandar
From:
openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.netmailto:openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.netmailto:vertex.co...@lists.launchpad.net]
On Behalf Of .?o 0 O??
Sent: Monday, March 26, 2012 12:45 PM
To: Pierre Amadio
Cc: openstack
Subject: Re: [Openstack] is this a bug in milestone-proposed keystone ?
(cannotget endpoint-list, nor create endpoint)
hi,
I don't know if it is a bug but I come across the same problem and wondering
how to solve it.
-- Original --
From: Pierre
Amadiopierre.ama...@canonical.commailto:pierre.ama...@canonical.com;
Date: Sun, Mar 25, 2012 04:35 AM
To:
openstackopenstack@lists.launchpad.netmailto:openstack@lists.launchpad.net;
Subject: [Openstack] is this a bug in milestone-proposed keystone ? (cannotget
endpoint-list, nor create endpoint)
Hi there !
I wanted to give a try to the milestone-proposed branch of keystone and
got stuck quite fast.
I am not sure if i hit a bug and should report it, or if i'm doing
something wrong.
With previous version of keystone (read packaged on ubuntu precise), i
was able to create endpoint the following way once keystone has been
installed:
1) setting some env variables:
export KEYSTONE_IP=192.168.122.102 # IP of your keystone API server
export SERVICE_ENDPOINT=http://$KEYSTONE_IP:35357/v2.0/
export SERVICE_TOKEN=999888777666
export
NOVA_PUBLIC_URL=http://$NOVA_IP:8774/v1.1/%(tenant_id)shttp://$NOVA_IP:8774/v1.1/%25(tenant_id)s
export NOVA_ADMIN_URL=$NOVA_PUBLIC_URL
export NOVA_INTERNAL_URL=$NOVA_PUBLIC_URL
2) creating services:
keystone service-create --name nova --type compute --description
'OpenStack Compute Service'
keystone service-create --name swift --type object-store --description
'OpenStack Storage Service'
keystone service-create --name glance --type image --description
'OpenStack Image Service'
keystone service-create --name keystone --type identity --description
'OpenStack Identity Service'
3) creating an endpoint for those services, starting with the compute
service:
ID=$(keystone service-list | grep -i compute | awk '{print $2}')
keystone endpoint-create --region RegionOne --service_id $ID --publicurl
$NOVA_PUBLIC_URL --adminurl $NOVA_ADMIN_URL --internalurl $NOVA_INTERNAL_URL
When i run this command with milestone-proposed, i experience the following:
No handlers could be found for logger keystoneclient.client
The action you have requested has not been implemented. (HTTP 501)
Strangely enough, i experience a similar error message when running a
simple keystone endpoint-list whereas command such as keystone
user-list works all right.
here is what i have in the keystone logs when trying endpoint-list:
2012-03-24 20:30:09DEBUG [routes.middleware] Matched GET /endpoints
2012-03-24 20:30:09DEBUG [routes.middleware] Route path:
'{path_info:.*}', defaults: {'controller':
keystone.contrib.admin_crud.core.CrudExtension object at 0x2b215d0}
2012-03-24 20:30:09DEBUG [routes.middleware] Match dict:
{'controller': keystone.contrib.admin_crud.core.CrudExtension object at
0x2b215d0, 'path_info': '/endpoints'}
2012-03-24 20:30:09DEBUG [routes.middleware] Matched GET /endpoints
[Openstack] where can i find kvm image used for openstack？
hi i use ubuntu1010-uec image 64-bit to start a VM on openstack on 32-bit system.but it failed. ｉ think it because of image not matching the host system. any one can give me a suggestion. or give me any information where can i find 32-bit image. thank you ___ 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] essex rc1: rabbit time out when runing nova x509-get-root-cert
On 03/26/2012 03:22 PM, Julien Danjou wrote: On Mon, Mar 26 2012, Pierre Amadio wrote: Any idea what could be wrong ? You must `nova-cert' daemon running to make this work. It works way better when nova-cert is running indeed. Thanks ! ___ 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] Installion guide for OpenStack Essex on Ubuntu 12.04
Hi folks, I've written a guide on how to install OpenStack Essex on Ubuntu 12.04. It covers the installation and configuration of Keystone, Glance, Nova and Horizon. By following this guide, even people that haven't collected much OpenStack experience so far should be able to get the virtualization environment up and running in a short period of time. The full document is available from here: http://www.hastexo.com/resources/docs/installing-openstack-essex-4-ubuntu-1204-precise-pangolin All feedback and comments are much appreciated -- thanks in advance! Best regards Martin -- Martin Gerhard Loschwitz Principal Consultant hastexo Professional Services ___ 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] KVM disk performance
Hi Diego, Thanks for your quick response. Yes we are using the virtio drivers. We have to add them manual for FreeBSD Windows, and it works. Only the performance is very bad. Kind regards, Martin On Mar 26, 2012, at 3:43 PM, Diego Parrilla wrote: Have you tried virtio for storage? http://www.linux-kvm.org/page/Virtio Enviado desde mi iPhone, perdona la brevedad El 26/03/2012, a las 14:59, Martin van Wilderen - JDN BV mar...@jdn.nl escribió: Hi List, I have a question about KVM disk performance. We are using Openstack Nova on three machines. These machines have a SSD drive with a dd write performance of about 130mb/s Within the instance the write performance is down to about 5 mb/s. When using the allocate trick (dd zero to disk before newfs) we get a performance of 20 mb/s. Things a have tried but don't give any extra results are: - Settings the disklayout from qcow2 to raw - Settings the cache type in libvirt.xml (writeback, writethrough, none) - Switching KSM on and off. - Tested with different guests OS, Linux, FreeBSD, Windows. Is there someone who had some extra info i can check? Or are there more people with this issue? Snippet from libvirt.xml driver type='qcow2'/ cache='writeback'/ source file='/var/lib/nova/instances/instance-0113/disk'/ target dev='vda' bus='virtio'/ Kind regards, Martin ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] Running code on instance start/terminate
Hello, I'm developing a application to work along with openstack. My application needs to keep track of all instances being started or terminated such as feeding it information about the location, status and other information about launched and terminated instances. The current version makes timed queries to OpenStack database, but this is showing to be a little consuming and inefficient, so I would like to add a portion of code to make OpenStack actively feed my application information whenever an instance changes its status or location. What is the least intrusive way to do that? It would be very nice if OpenStack provided a way to run code on these situations without actually changing any code, such as defining a directory of scripts to run in every instance status change. ___ 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] KVM disk performance
On 03/26/2012 01:59 PM, Martin van Wilderen - JDN BV wrote:
Hi List,
I have a question about KVM disk performance. We are using Openstack Nova on
three machines. These machines have a SSD drive with a dd write performance
of about 130mb/s
Within the instance the write performance is down to about 5 mb/s. When using
the allocate trick (dd zero to disk before newfs) we get a performance of 20
mb/s.
Interesting. I presume this performance difference is when growing the
allocation.
I.E. without the dd allocate trick, writes to new files = 5MB/s, but old
files = 20MB/s ?
What file did you do the `dd` on exactly and what size was it?
I could do a patch to nova to do something like:
fallocate --version || exit 0
fallocate -l $SIZE $DISKIMG || { rm -f $DISKIMG; exit 1; }
But only when I get a better understand of your setup.
Note it would need to be optional too, akin to a memory
overcommit like flag.
Note the above change would also give the benefit of
immediate feedback of ENOSPC
Things a have tried but don't give any extra results are:
- Settings the disklayout from qcow2 to raw
I'm a bit surprised that had no effect.
- Settings the cache type in libvirt.xml (writeback, writethrough, none)
- Switching KSM on and off.
- Tested with different guests OS, Linux, FreeBSD, Windows.
Is there someone who had some extra info i can check? Or are there more
people with this issue?
Snippet from libvirt.xml
driver type='qcow2'/ cache='writeback'/
source file='/var/lib/nova/instances/instance-0113/disk'/
target dev='vda' bus='virtio'/
I'll let others more knowledgeable comment on
general virt IO overheads.
cheers,
Pádraig.
___
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] hardware specifications for a little private cloud
2012/3/26 Razique Mahroua razique.mahr...@gmail.com Hello Alberto, I would advise you to deploy as much as node as you can, and dedicate separate services. That would bring you the possibility to extend your knowledge on HA mechanisms, and really understand how services interact each other. Yes I know, but we have budget limitations. OpenStack HA is not an objective at this moment, it is a educational environment and we can still use a whiteboard ;) Let's say you spawn an instance from the api server, while it's is launched on a compute node - which is one another server. By having splitted architecture, you won't miss the obvious ;-) OK, but we are always considering 1 controller node and 4 compute nodes, the main doubt is regarding storage, is it better in controller node or in a external SAN iSCSI in a little cloud like this? What is the purpose of the lab ? Sysadmin training. At this moment, each student uses an isolated virtual LAN with Xen/KVM and shares some physical servers, but with a private cloud we can deploy a plethora of new configurations. Furthermore, the cloud itself. Alberto Molina Coballes IES Gonzalo Nazareno ___ 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] KVM disk performance
Hi Martin 1. Does /var/lib/nova/instances reside on your SSD? (just double checking it's not instead pointing to a normal stoage device). 2. Do you see the expected performance on the host operating system? 3. Could you please provide the complete libvirt .xml file? 4. Could you please provide the operating system and version of the guest? Cheers David On Mon, Mar 26, 2012 at 1:59 PM, Martin van Wilderen - JDN BV mar...@jdn.nl wrote: Hi List, I have a question about KVM disk performance. We are using Openstack Nova on three machines. These machines have a SSD drive with a dd write performance of about 130mb/s Within the instance the write performance is down to about 5 mb/s. When using the allocate trick (dd zero to disk before newfs) we get a performance of 20 mb/s. Things a have tried but don't give any extra results are: - Settings the disklayout from qcow2 to raw - Settings the cache type in libvirt.xml (writeback, writethrough, none) - Switching KSM on and off. - Tested with different guests OS, Linux, FreeBSD, Windows. Is there someone who had some extra info i can check? Or are there more people with this issue? Snippet from libvirt.xml driver type='qcow2'/ cache='writeback'/ source file='/var/lib/nova/instances/instance-0113/disk'/ target dev='vda' bus='virtio'/ Kind regards, Martin ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] 回复： is this a bug in milestone-proposed keystone ? (cannotget endpoint-list, nor create endpoint)
On 03/26/2012 03:47 PM, Mandar Vaze wrote: *From*and *To* look identical. What should the [catalog] value be changed to ? In my case it worked with: [catalog] driver = keystone.catalog.backends.sql.Catalog As mentionned by Alan: Default catalog backend in git is templated, if you want to match Ubuntu (and Fedora) package default, set it to sql backend. ___ 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] where can i find kvm image used for openstack？
Am 26.03.12 15:48, schrieb 赵琦: hi i use ubuntu1010-uec image 64-bit to start a VM on openstack on 32-bit system.but it failed. ｉ think it because of image not matching the host system. any one can give me a suggestion. or give me any information where can i find 32-bit image. thank you ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp Hi there, here is one, for example: http://uec-images.ubuntu.com/releases/11.10/release/ubuntu-11.10-server-cloudimg-i386-disk1.img -- Martin Gerhard Loschwitz Chief Brand Officer, Principal Consultant hastexo Professional Services ___ 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] where can i find kvm image used for openstack？
here you can find what you want http://uec-images.ubuntu.com/ 在 2012年3月26日 下午9:48，赵琦 tyzha...@gmail.com 写道： hi i use ubuntu1010-uec image 64-bit to start a VM on openstack on 32-bit system.but it failed. ｉ think it because of image not matching the host system. any one can give me a suggestion. or give me any information where can i find 32-bit image. thank you ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] KVM disk performance
On 03/26/2012 01:59 PM, Martin van Wilderen - JDN BV wrote:
Hi List,
I have a question about KVM disk performance. We are using Openstack Nova on
three machines. These machines have a SSD drive with a dd write performance
of about 130mb/s
Within the instance the write performance is down to about 5 mb/s. When using
the allocate trick (dd zero to disk before newfs) we get a performance of 20
mb/s.
Interesting. I presume this performance difference is when growing the
allocation.
I.E. without the dd allocate trick, writes to new files = 5MB/s, but old
files = 20MB/s ?
What file did you do the `dd` on exactly and what size was it?
I could do a patch to nova to do something like:
fallocate --version || exit 0
fallocate -l $SIZE $DISKIMG || { rm -f $DISKIMG; exit 1; }
But only when I get a better understand of your setup.
Note it would need to be optional too, akin to a memory
overcommit like flag.
Note the above change would also give the benefit of
immediate feedback of ENOSPC
Things a have tried but don't give any extra results are:
- Settings the disklayout from qcow2 to raw
I'm a bit surprised that had no effect.
- Settings the cache type in libvirt.xml (writeback, writethrough, none)
- Switching KSM on and off.
- Tested with different guests OS, Linux, FreeBSD, Windows.
Is there someone who had some extra info i can check? Or are there more
people with this issue?
Snippet from libvirt.xml
driver type='qcow2'/ cache='writeback'/
source file='/var/lib/nova/instances/instance-0113/disk'/
target dev='vda' bus='virtio'/
I'll let others more knowledgeable comment on
general virt IO overheads.
cheers,
Pádraig.
___
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] KVM disk performance
Can you provide information about what version of kvm you're using ? I suspect this is really unrelated to openstack specifically. On Mon, 26 Mar 2012, Martin van Wilderen - JDN BV wrote: Hi List, I have a question about KVM disk performance. We are using Openstack Nova on three machines. These machines have a SSD drive with a dd write performance of about 130mb/s Within the instance the write performance is down to about 5 mb/s. When using the allocate trick (dd zero to disk before newfs) we get a performance of 20 mb/s. Things a have tried but don't give any extra results are: - Settings the disklayout from qcow2 to raw - Settings the cache type in libvirt.xml (writeback, writethrough, none) - Switching KSM on and off. - Tested with different guests OS, Linux, FreeBSD, Windows. Is there someone who had some extra info i can check? Or are there more people with this issue? Snippet from libvirt.xml driver type='qcow2'/ cache='writeback'/ source file='/var/lib/nova/instances/instance-0113/disk'/ target dev='vda' bus='virtio'/ Kind regards, Martin ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] Installion guide for OpenStack Essex on Ubuntu 12.04
Thanks very much, Martin! On 03/26/2012 09:50 AM, Martin Gerhard Loschwitz wrote: Hi folks, I've written a guide on how to install OpenStack Essex on Ubuntu 12.04. It covers the installation and configuration of Keystone, Glance, Nova and Horizon. By following this guide, even people that haven't collected much OpenStack experience so far should be able to get the virtualization environment up and running in a short period of time. The full document is available from here: http://www.hastexo.com/resources/docs/installing-openstack-essex-4-ubuntu-1204-precise-pangolin All feedback and comments are much appreciated -- thanks in advance! Best regards Martin ___ 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] is this a bug in milestone-proposed keystone ? (cannotget endpoint-list, nor create endpoint)
There seems to be an unfortunate difference in opinion out there about
whether the keystone endpoints should be defined using templates
(devstack) or keystone calls (ubuntu). I don't know why keystone is
offering two very different, but seemingly functionally identical, ways
to do this. Is there a good reason? Can this be sorted out so there is
only one documented way to do this?
-David
On 3/26/2012 7:25 AM, Andiabes wrote:
Can you include your config?
The behavior you're describing seems to be consistent with a missing
backers configuration ...
Something like:
[identity]
driver = keystone.identity.backends.sql.Identity
[catalog]
driver = keystone.catalog.backends.sql.Catalog
Also, where/how are you installing?
On Mar 26, 2012, at 6:56 AM, Mandar Vaze mandar.v...@vertex.co.in
mailto:mandar.v...@vertex.co.in wrote:
I'm also getting the same error on latest master branch (updated today)
Using setup created by devstack
-Mandar
*From:*openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net
mailto:openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net mailto:vertex.co...@lists.launchpad.net]
*On Behalf Of *.?o 0 O??
*Sent:* Monday, March 26, 2012 12:45 PM
*To:* Pierre Amadio
*Cc:* openstack
*Subject:* Re: [Openstack] is this a bug in milestone-proposed
keystone ? (cannotget endpoint-list, nor create endpoint)
hi,
I don't know if it is a bug but I come across the same problem and
wondering how to solve it.
-- Original --
*From: * Pierre Amadiopierre.ama...@canonical.com
mailto:pierre.ama...@canonical.com;
*Date: * Sun, Mar 25, 2012 04:35 AM
*To: * openstackopenstack@lists.launchpad.net
mailto:openstack@lists.launchpad.net;
*Subject: * [Openstack] is this a bug in milestone-proposed keystone
? (cannotget endpoint-list, nor create endpoint)
Hi there !
I wanted to give a try to the milestone-proposed branch of keystone and
got stuck quite fast.
I am not sure if i hit a bug and should report it, or if i'm doing
something wrong.
With previous version of keystone (read packaged on ubuntu precise), i
was able to create endpoint the following way once keystone has been
installed:
1) setting some env variables:
export KEYSTONE_IP=192.168.122.102 # IP of your keystone API server
export SERVICE_ENDPOINT=http://$KEYSTONE_IP:35357/v2.0/
export SERVICE_TOKEN=999888777666
export NOVA_PUBLIC_URL=http://$NOVA_IP:8774/v1.1/%(tenant_id)s
http://$NOVA_IP:8774/v1.1/%%28tenant_id%29s
export NOVA_ADMIN_URL=$NOVA_PUBLIC_URL
export NOVA_INTERNAL_URL=$NOVA_PUBLIC_URL
2) creating services:
keystone service-create --name nova --type compute --description
'OpenStack Compute Service'
keystone service-create --name swift --type object-store --description
'OpenStack Storage Service'
keystone service-create --name glance --type image --description
'OpenStack Image Service'
keystone service-create --name keystone --type identity --description
'OpenStack Identity Service'
3) creating an endpoint for those services, starting with the compute
service:
ID=$(keystone service-list | grep -i compute | awk '{print $2}')
keystone endpoint-create --region RegionOne --service_id $ID --publicurl
$NOVA_PUBLIC_URL --adminurl $NOVA_ADMIN_URL --internalurl
$NOVA_INTERNAL_URL
When i run this command with milestone-proposed, i experience the
following:
No handlers could be found for logger keystoneclient.client
The action you have requested has not been implemented. (HTTP 501)
Strangely enough, i experience a similar error message when running a
simple keystone endpoint-list whereas command such as keystone
user-list works all right.
here is what i have in the keystone logs when trying endpoint-list:
2012-03-24 20:30:09DEBUG [routes.middleware] Matched GET /endpoints
2012-03-24 20:30:09DEBUG [routes.middleware] Route path:
'{path_info:.*}', defaults: {'controller':
keystone.contrib.admin_crud.core.CrudExtension object at 0x2b215d0}
2012-03-24 20:30:09DEBUG [routes.middleware] Match dict:
{'controller': keystone.contrib.admin_crud.core.CrudExtension object at
0x2b215d0, 'path_info': '/endpoints'}
2012-03-24 20:30:09DEBUG [routes.middleware] Matched GET /endpoints
2012-03-24 20:30:09DEBUG [routes.middleware] Route path:
'/endpoints', defaults: {'action': u'get_endpoints', 'controller':
keystone.catalog.core.EndpointController object at 0x2b21210}
2012-03-24 20:30:09DEBUG [routes.middleware] Match dict: {'action':
u'get_endpoints', 'controller':
keystone.catalog.core.EndpointController object at 0x2b21210}
2012-03-24 20:30:09DEBUG [keystone.common.wsgi] arg_dict: {}
2012-03-24 20:30:09 WARNING [keystone.common.wsgi] The action you have
requested has not been implemented.
2012-03-24 20:30:09DEBUG [keystone.common.wsgi]
RESPONSE HEADERS
2012-03-24 20:30:09DEBUG [keystone.common.wsgi] Content-Type =
Re: [Openstack] 回复： is this a bug in milestone-proposed keystone ? (cannotget endpoint-list, nor create endpoint)
( This is significant gap in the current keystone docs, so I'll be ensuring this makes it into the docs ASAP; feedback here is very much appreciated! ) There are two driver options for your service catalog - one based on a flat file, and one backed by SQL. The flat file does not support administration commands from the client (e.g. keystone endpoint-create, keystone service-create), hence the HTTP 501 Not Implemented messages. [catalog] driver = keystone.catalog.backends.templated.TemplatedCatalog template_file = /opt/stack/keystone/etc/default_catalog.templates [catalog] driver = keystone.catalog.backends.sql.Catalog The `template_file` does not need to be defined for the sql.Catalog driver. If you're installing from source, the templated.TemplatedCatalog is currently the default option (I could see this switching to SQL in the future, however). I believe Ubuntu and Debian packages default to the sql.Catalog. To build a flat-file service catalog based on an existing diablo deployment: http://keystone.openstack.org/configuration.html#migrating-your-service-catalog-from-legacy-versions-of-keystone To build a flat-file service catalog from scratch, refer to examples in keystone and devstack: https://github.com/openstack/keystone/blob/master/etc/default_catalog.templates https://github.com/openstack-dev/devstack/blob/master/files/default_catalog.templates To build your service catalog using SQL, see the built-in help: $ keystone $ keystone | grep service $ keystone help service-create $ keystone help endpoint-create -Dolph 2012/3/26 Mandar Vaze mandar.v...@vertex.co.in *From* and *To* look identical. ** ** What should the [catalog] value be changed to ? ** ** -Mandar ** ** *From:* openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net[mailto: openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net] *On Behalf Of *.?o 0 O?? *Sent:* Monday, March 26, 2012 6:02 PM *To:* Andiabes *Cc:* openstack *Subject:* [Openstack] 回复： is this a bug in milestone-proposed keystone ? (cannotget endpoint-list, nor create endpoint) ** ** *found the solution:* *in keystone.conf * *you need to change :* [catalog] driver = keystone.catalog.backends.templated.TemplatedCatalog to： [catalog] driver = keystone.catalog.backends.templated.TemplatedCatalog ** ** ** ** ** ** -- 原始邮件 -- *发件人**:* Andiabesandi.a...@gmail.com; *发送时间**:* 2012年3月26日(星期一) 晚上7:25 *收件人**:* Mandar Vazemandar.v...@vertex.co.in; *抄送**:* .。o 0 O泡泡 501640...@qq.com; Pierre Amadio pierre.ama...@canonical.com; openstackopenstack@lists.launchpad.net; *主题**:* Re: [Openstack] is this a bug in milestone-proposed keystone ? (cannotget endpoint-list, nor create endpoint) Can you include your config? The behavior you're describing seems to be consistent with a missing backers configuration ... ** ** Something like: [identity] driver = keystone.identity.backends.sql.Identity ** ** [catalog] driver = keystone.catalog.backends.sql.Catalog ** ** ** ** Also, where/how are you installing? On Mar 26, 2012, at 6:56 AM, Mandar Vaze mandar.v...@vertex.co.in wrote: I’m also getting the same error on latest master branch (updated today)*** * Using setup created by devstack -Mandar *From:* openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net[mailto: openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net] *On Behalf Of *.?o 0 O?? *Sent:* Monday, March 26, 2012 12:45 PM *To:* Pierre Amadio *Cc:* openstack *Subject:* Re: [Openstack] is this a bug in milestone-proposed keystone ? (cannotget endpoint-list, nor create endpoint) hi, I don't know if it is a bug but I come across the same problem and wondering how to solve it. -- Original -- *From: * Pierre Amadiopierre.ama...@canonical.com; *Date: * Sun, Mar 25, 2012 04:35 AM *To: * openstackopenstack@lists.launchpad.net; *Subject: * [Openstack] is this a bug in milestone-proposed keystone ? (cannotget endpoint-list, nor create endpoint) Hi there ! I wanted to give a try to the milestone-proposed branch of keystone and got stuck quite fast. I am not sure if i hit a bug and should report it, or if i'm doing something wrong. With previous version of keystone (read packaged on ubuntu precise), i was able to create endpoint the following way once keystone has been installed: 1) setting some env variables: export KEYSTONE_IP=192.168.122.102 # IP of your keystone API server export SERVICE_ENDPOINT=http://$KEYSTONE_IP:35357/v2.0/ export SERVICE_TOKEN=999888777666 export NOVA_PUBLIC_URL=http://$NOVA_IP:8774/v1.1/%(tenant_id)s export NOVA_ADMIN_URL=$NOVA_PUBLIC_URL export NOVA_INTERNAL_URL=$NOVA_PUBLIC_URL
Re: [Openstack] KVM disk performance
Hi David, 1. Yes. That's the only disk in the system. 2. Yes: nova1:/var/lib/nova/instances$ dd if=/dev/zero of=test bs=1M count=256 256+0 records in 256+0 records out 268435456 bytes (268 MB) copied, 2.04146 s, 131 MB/s 4. I have tried with: - Linux Ubuntu 10.10 - FreeBSD 8.2 with virtio driver - Windows 2008 R2 Server with virtio driver 3. my libvirt.xml domain type='kvm' nameinstance-0121/name memory1048576/memory os typehvm/type boot dev=hd / /os features acpi/ /features vcpu2/vcpu devices disk type='file' driver type='raw'/ source file='/var/lib/nova/instances/instance-0121/disk'/ target dev='vda' bus='virtio'/ /disk disk type='file' driver type='raw'/ source file='/var/lib/nova/instances/instance-0121/disk.local'/ target dev='vdb' bus='virtio'/ /disk interface type='bridge' source bridge='br100'/ mac address='02:16:3e:33:42:e3'/ filterref filter=nova-instance-instance-0121-02163e3342e3 parameter name=IP value=10.0.0.34 / parameter name=DHCPSERVER value=10.0.0.9 / /filterref /interface !-- The order is significant here. File must be defined first -- serial type=file source path='/var/lib/nova/instances/instance-0121/console.log'/ target port='1'/ /serial console type='pty' tty='/dev/pts/2' source path='/dev/pts/2'/ target port='0'/ /console serial type='pty' source path='/dev/pts/2'/ target port='0'/ /serial graphics type='vnc' port='-1' autoport='yes' keymap='en-us' listen='0.0.0.0'/ /devices /domain Met vriendelijke groet, Martin van Wilderen Technical Manager On Mar 26, 2012, at 4:45 PM, David Busby wrote: Hi Martin Does /var/lib/nova/instances reside on your SSD? (just double checking it's not instead pointing to a normal stoage device). Do you see the expected performance on the host operating system? Could you please provide the complete libvirt .xml file? Could you please provide the operating system and version of the guest? Cheers David On Mon, Mar 26, 2012 at 1:59 PM, Martin van Wilderen - JDN BV mar...@jdn.nl wrote: Hi List, I have a question about KVM disk performance. We are using Openstack Nova on three machines. These machines have a SSD drive with a dd write performance of about 130mb/s Within the instance the write performance is down to about 5 mb/s. When using the allocate trick (dd zero to disk before newfs) we get a performance of 20 mb/s. Things a have tried but don't give any extra results are: - Settings the disklayout from qcow2 to raw - Settings the cache type in libvirt.xml (writeback, writethrough, none) - Switching KSM on and off. - Tested with different guests OS, Linux, FreeBSD, Windows. Is there someone who had some extra info i can check? Or are there more people with this issue? Snippet from libvirt.xml driver type='qcow2'/ cache='writeback'/ source file='/var/lib/nova/instances/instance-0113/disk'/ target dev='vda' bus='virtio'/ Kind regards, Martin ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] KVM disk performance
Hi Scott, kvm --version QEMU emulator version 0.13.91 (qemu-kvm-0.14.0-rc1), Copyright (c) 2003-2008 Fabrice Bellard virsh --version 0.8.8 uname -r 2.6.35-22-server Need any more info? Met vriendelijke groet, Martin van Wilderen Technical Manager On Mar 26, 2012, at 5:12 PM, Scott Moser wrote: Can you provide information about what version of kvm you're using ? I suspect this is really unrelated to openstack specifically. On Mon, 26 Mar 2012, Martin van Wilderen - JDN BV wrote: Hi List, I have a question about KVM disk performance. We are using Openstack Nova on three machines. These machines have a SSD drive with a dd write performance of about 130mb/s Within the instance the write performance is down to about 5 mb/s. When using the allocate trick (dd zero to disk before newfs) we get a performance of 20 mb/s. Things a have tried but don't give any extra results are: - Settings the disklayout from qcow2 to raw - Settings the cache type in libvirt.xml (writeback, writethrough, none) - Switching KSM on and off. - Tested with different guests OS, Linux, FreeBSD, Windows. Is there someone who had some extra info i can check? Or are there more people with this issue? Snippet from libvirt.xml driver type='qcow2'/ cache='writeback'/ source file='/var/lib/nova/instances/instance-0113/disk'/ target dev='vda' bus='virtio'/ Kind regards, Martin ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] Running code on instance start/terminate
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/26/2012 11:48 AM, Russell Bryant wrote: On 03/26/2012 10:15 AM, Rogério Vinhal Nunes wrote: Hello, I'm developing a application to work along with openstack. My application needs to keep track of all instances being started or terminated such as feeding it information about the location, status and other information about launched and terminated instances. The current version makes timed queries to OpenStack database, but this is showing to be a little consuming and inefficient, so I would like to add a portion of code to make OpenStack actively feed my application information whenever an instance changes its status or location. What is the least intrusive way to do that? It would be very nice if OpenStack provided a way to run code on these situations without actually changing any code, such as defining a directory of scripts to run in every instance status change. Check out the notifications system: http://wiki.openstack.org/NotificationSystem That wasn't the page I thought it was ... I meant: http://wiki.openstack.org/SystemUsageData You can consume these events via AMQP if you configure nova to use the rabbit notifier. - -- Russell Bryant -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9wkSgACgkQFg9ft4s9SAYFuACfUu23qtxiH6WLCJNyd9gBf8i1 FwQAnifjwWkFHYxo+KhYt8TAWEzTaMYZ =UWlH -END PGP 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] Running code on instance start/terminate
Rogerio --
I'm developing a application to work along with openstack. My
application needs to keep track of all instances being started or
terminated such as feeding it information about the location, status
and other information about launched and terminated instances.
Nova already includes a notification framework which works well for this
sort of thing.
If you want your code to run on a different host or even a separate
process, you should enable queue-based notifications on nova commandline
with something like
--notification_driver = nova.notifier.rabbit_notifier
Then you can set up your code as a queue consumer to receive these messages.
That's not the approach that I'm using currently, though. What I did is
easier but somewhat more intrusive: I wrote a custom notification
driver that checks for interesting messages and does my work inline.
--notification_driver = nova.notifier.list_notifier
--list_notifier_drivers = nova.sharedfs.sharedfs_notifier.SharedFSNotifier
That results in SharedFSNotifier's notify(message) function getting
called for each notification, where it vets the messages and responds as
needed:
event_type = message.get('event_type')
if event_type not in ['compute.instance.delete.start',
'compute.instance.create.end']:
etc.
You can see the complete class in this patch:
https://review.openstack.org/#change,5292 . Look for the file
'sharedfs_notifier.py'.
Hope that helps!
-Andrew
___
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] Specification of nova-diagnostics
Hello, I've been trying to implement the nova-diagnostics command for libvirt. I'm using the devstack installation on ubuntu 12.04. So far i've managed to gather information regarding CPU, IO (network and disks). The memory reading only works with the virsh command and does not report the actual memory usage. As pointed out to me previously, i've been looking at the implementation of nova-diagnostics for the xenapi in order to try and figure out how to supply the data back to openstack. However, i can not make any sense of it. All i know is that it returns a set of keys with values, which i suppose represent the values of the readings. What i wish to know is if there's any document or specification which i can read which defines what nova-diagnostics should return and under what format. Regards, Leander ___ 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] BUG on dashboard (Horizon)
Agree with the other posters; Keystone is not reachable from Horizon -- make sure it's running, keystone's IP and ports are reflected correctly in horizon config, etc. -Dolph On Mon, Mar 26, 2012 at 6:21 AM, Guilherme Souza souza.guilherm...@gmail.com wrote: Hello Razique, What do you want to say with: What type of install..., i've installed following the oficial tutorial http://docs.openstack.org/diablo/openstack-compute/install/content/, and keystone looks like working fine, apparently can i access the dashboardwithout problems. Em 26 de março de 2012 09:18, Razique Mahroua razique.mahr...@gmail.comescreveu: Hello Guillherme; looks like the Keystone server is not reachable. What type of install did you make ? *Nuage Co - Razique Mahroua** * razique.mahr...@gmail.com Le 23 mars 2012 à 20:20, Guilherme Souza a écrit : Hello folks, I'm having a bug on Horizon, i've installed it using the Diablo version, following the oficial tutorial. I can acess the dashboard, up instances, but when i try to acess the users and tenants page it prints a Error, to Users Unable to list users: [Errno 113] EHOSTUNREACH, or to tenants Unable to get tenant info: [Errno 113] EHOSTUNREACH, but it doesn't crashes the GUI. And in another installation at the same version of Dashboard, Diablo, it prints a timeout message and doesn't crashes the GUI too. Someone had the same error? Gratz Guilherme Souza ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Atenciosamente, Guilherme Santos Souza Sistemas de Informação - PUCRS Fone: (51) 9695-1070 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] KVM disk performance
Hi Martin:
Which os version on your host machines? I tested kvm on rhel 6.1 have
this issue, guest os is freebsd virtio, on rhel 6.2 performance is well.
2012/3/26 Pádraig Brady p...@draigbrady.com
On 03/26/2012 01:59 PM, Martin van Wilderen - JDN BV wrote:
Hi List,
I have a question about KVM disk performance. We are using Openstack
Nova on three machines. These machines have a SSD drive with a dd write
performance of about 130mb/s
Within the instance the write performance is down to about 5 mb/s. When
using the allocate trick (dd zero to disk before newfs) we get a
performance of 20 mb/s.
Interesting. I presume this performance difference is when growing the
allocation.
I.E. without the dd allocate trick, writes to new files = 5MB/s, but old
files = 20MB/s ?
What file did you do the `dd` on exactly and what size was it?
I could do a patch to nova to do something like:
fallocate --version || exit 0
fallocate -l $SIZE $DISKIMG || { rm -f $DISKIMG; exit 1; }
But only when I get a better understand of your setup.
Note it would need to be optional too, akin to a memory
overcommit like flag.
Note the above change would also give the benefit of
immediate feedback of ENOSPC
Things a have tried but don't give any extra results are:
- Settings the disklayout from qcow2 to raw
I'm a bit surprised that had no effect.
- Settings the cache type in libvirt.xml (writeback, writethrough, none)
- Switching KSM on and off.
- Tested with different guests OS, Linux, FreeBSD, Windows.
Is there someone who had some extra info i can check? Or are there more
people with this issue?
Snippet from libvirt.xml
driver type='qcow2'/ cache='writeback'/
source file='/var/lib/nova/instances/instance-0113/disk'/
target dev='vda' bus='virtio'/
I'll let others more knowledgeable comment on
general virt IO overheads.
cheers,
Pádraig.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
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] Confusing about the nova authentication and keystone authentication
The commands in nova are deprecated and will be removed. They are still there to allow people to upgrade from old internal auth to keystone. Vish On Mar 26, 2012, at 2:52 AM, 下一个傻子 wrote: Hello ,every one: Here is a question that confusing me for days. I saw there is an authentication mechanism in keystone,that is responsible for creating users ,projects,roles ,role-user relationship management etcand also,I found there is such a mechanism in nova,which also can create users,projects,roles...things that keystone do. so ,what's the relationship between the two?..Can anyone please help me out of here :) Thank you. -- ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] hardware specifications for a little private cloud
One other thing you'll want to consider upfront w.r.t a hardware purchase is whether or not you want to support live migration. http://docs.openstack.org/cactus/openstack-compute/admin/content/configuring-live-migrations.html For this you'll need a large amount of shared storage (usually via NFS) where the instance files will live. Whether you choose SAN, NAS, or just a node with a bunch of disk is likely dependent on your environment and budget. Everett On Mon, Mar 26, 2012 at 5:17 AM, Razique Mahroua razique.mahr...@gmail.comwrote: Hello Alberto, I would advise you to deploy as much as node as you can, and dedicate separate services. That would bring you the possibility to extend your knowledge on HA mechanisms, and really understand how services interact each other. Let's say you spawn an instance from the api server, while it's is launched on a compute node - which is one another server. By having splitted architecture, you won't miss the obvious ;-) What is the purpose of the lab ? *Nuage Co - Razique Mahroua** * razique.mahr...@gmail.com Le 26 mars 2012 à 12:56, Alberto Molina Coballes a écrit : Hi all, I'm a teacher at a sysadmin academy and we are planning to deploy a private cloud with OpenStack for educational/training purposes. We are currently selecting the optimal hardware configuration for our needs and I'm asking for some help to the list. Using [1] as a reference, we are clear about hardware specifications of compute nodes (4 nodes with 2 processors), but we aren't about the best solution for node controller and optimal storage: Option 1: 1 server with 2 HD in RAID1 (nova controller, nova volume, glance, ...) + 1 SAN iSCSI Option 2: 1 server with 12 HD in RAID5/6 (nova controller, nova volume, glance, ...) We are excited about the possibilities that a private cloud brings to us and we don't want to fail in this critical step, so any help will be really appreciated. Alberto Molina Coballes IES Gonzalo Nazareno [1] http://www.referencearchitecture.org/hardware-specifications/ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] is this a bug in milestone-proposed keystone ? (cannotget endpoint-list, nor create endpoint)
I think I'm to blame (apologies!) for suggesting that one driver was
preferred over the other (that was my understanding a few weeks ago, based
on test coverage). However, test coverage has since improved and I think
people are having good experience with the SQL driver.
The two methods are *not* functionally identical. The file-based driver is
simple and high-performance, and the sql-based driver provides flexibility
and API/CLI administration.
I've just proposed a review to clarify each option in the
http://keystone.openstack.org/configuration.html docs:
https://review.openstack.org/#change,5820
As well as a separate review to change the default backend to SQL, since
most users are looking for the CLI management commands out of the box:
https://review.openstack.org/#change,5821
-Dolph
On Mon, Mar 26, 2012 at 8:29 AM, David Kranz david.kr...@qrclab.com wrote:
There seems to be an unfortunate difference in opinion out there about
whether the keystone endpoints should be defined using templates (devstack)
or keystone calls (ubuntu). I don't know why keystone is offering two very
different, but seemingly functionally identical, ways to do this. Is there
a good reason? Can this be sorted out so there is only one documented way
to do this?
-David
On 3/26/2012 7:25 AM, Andiabes wrote:
Can you include your config?
The behavior you're describing seems to be consistent with a missing
backers configuration ...
Something like:
[identity]
driver = keystone.identity.backends.sql.Identity
[catalog]
driver = keystone.catalog.backends.sql.Catalog
Also, where/how are you installing?
On Mar 26, 2012, at 6:56 AM, Mandar Vaze mandar.v...@vertex.co.in wrote:
I’m also getting the same error on latest master branch (updated today)*
***
Using setup created by devstack
** **
-Mandar
** **
*From:* openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net [
mailto:openstack-bounces+mandar.vaze= openstack-bounces+mandar.vaze=
vertex.co...@lists.launchpad.net] *On Behalf Of *.?o 0 O??
*Sent:* Monday, March 26, 2012 12:45 PM
*To:* Pierre Amadio
*Cc:* openstack
*Subject:* Re: [Openstack] is this a bug in milestone-proposed keystone ?
(cannotget endpoint-list, nor create endpoint)
** **
hi,
I don't know if it is a bug but I come across the same problem and
wondering how to solve it.
-- Original --
*From: * Pierre Amadiopierre.ama...@canonical.com;
*Date: * Sun, Mar 25, 2012 04:35 AM
*To: * openstackopenstack@lists.launchpad.net;
*Subject: * [Openstack] is this a bug in milestone-proposed keystone ?
(cannotget endpoint-list, nor create endpoint)
Hi there !
I wanted to give a try to the milestone-proposed branch of keystone and
got stuck quite fast.
I am not sure if i hit a bug and should report it, or if i'm doing
something wrong.
With previous version of keystone (read packaged on ubuntu precise), i
was able to create endpoint the following way once keystone has been
installed:
1) setting some env variables:
export KEYSTONE_IP=192.168.122.102 # IP of your keystone API server
export SERVICE_ENDPOINT=http://$KEYSTONE_IP:35357/v2.0/
export SERVICE_TOKEN=999888777666
export NOVA_PUBLIC_URL=http://$NOVA_IP:8774/v1.1/%(tenant_id)s
export NOVA_ADMIN_URL=$NOVA_PUBLIC_URL
export NOVA_INTERNAL_URL=$NOVA_PUBLIC_URL
2) creating services:
keystone service-create --name nova --type compute --description
'OpenStack Compute Service'
keystone service-create --name swift --type object-store --description
'OpenStack Storage Service'
keystone service-create --name glance --type image --description
'OpenStack Image Service'
keystone service-create --name keystone --type identity --description
'OpenStack Identity Service'
3) creating an endpoint for those services, starting with the compute
service:
ID=$(keystone service-list | grep -i compute | awk '{print $2}')
keystone endpoint-create --region RegionOne --service_id $ID --publicurl
$NOVA_PUBLIC_URL --adminurl $NOVA_ADMIN_URL --internalurl
$NOVA_INTERNAL_URL
When i run this command with milestone-proposed, i experience the
following:
No handlers could be found for logger keystoneclient.client
The action you have requested has not been implemented. (HTTP 501)
Strangely enough, i experience a similar error message when running a
simple keystone endpoint-list whereas command such as keystone
user-list works all right.
here is what i have in the keystone logs when trying endpoint-list:
2012-03-24 20:30:09DEBUG [routes.middleware] Matched GET /endpoints
2012-03-24 20:30:09DEBUG [routes.middleware] Route path:
'{path_info:.*}', defaults: {'controller':
keystone.contrib.admin_crud.core.CrudExtension object at 0x2b215d0}
2012-03-24 20:30:09DEBUG [routes.middleware] Match dict:
{'controller': keystone.contrib.admin_crud.core.CrudExtension object at
0x2b215d0,
Re: [Openstack] 回复： is this a bug in milestone-proposed keystone ? (cannotget endpoint-list, nor create endpoint)
On 03/26/2012 11:43 AM, Dolph Mathews wrote: ( This is significant gap in the current keystone docs, so I'll be ensuring this makes it into the docs ASAP; feedback here is very much appreciated! ) There are two driver options for your service catalog - one based on a flat file, and one backed by SQL. The flat file does not support administration commands from the client (e.g. keystone endpoint-create, keystone service-create), hence the HTTP 501 Not Implemented messages. This is incorrect, AFAICT. The templated catalog driver inherits from the KVS driver and only overrides the get_catalog() method, so it *should* be able to add and delete services, etc. -jay ___ 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] Installion guide for OpenStack Essex on Ubuntu 12.04
Great work, Martin! It really does show that an installation can be completed for a proof of concept quite quickly. I tested the entire guide, and found I couldn't change the hastexo password in the keystone_data.sh even if I changed it in the keystone.conf file, not sure why not. Your instructions are correct, it's just that small changes are going to have cascading effects. Perhaps you could be more clear about the re-use of the SERVICE_TOKEN=hastexo being the same as the ADMIN_PASSWORD (I changed one but not the other, not realizing the hastexo string was in both places). It is what it is, not much a user can do about it other than tread carefully. You should also be more clear about editing the nova.conf file to replace your 10.42.0.6 IP address with the IP address of the server the user is installing upon in Step 5 [1]. You also need to restart the nova services after editing the nova.conf file so that the MySQL config is picked up, right? As I mentioned in our IRC chatting, I'd like to see your guide brought into the community docs site as a quick start, once the substitute this python file for that parts are sorted out through the bug fixes and package updates we'll hope get in 12.04 in time. To my eye, it's similar to the CSS OSS Beginner's Guide, but much quicker start to finish without explanatory text or object storage. So what I'd like to suggest is that you propose this guide to be added to the OpenStack docs - it'll help with maintenance and ongoing edits. I can help you create a quick start guide with Built for OpenStack logo and your logo (now available thanks to work from the docs tools team here at Rackspace, you could be the first one to try it). This would mean bringing the source into DocBook and the openstack-manuals github repository. You can keep the CC-By-SA licensing for the document by going this route, though I do want to hear what other doc contributors think of this approach. In our conversations, you just said CC-By-SA - could you be more specific about which license you want? We welcome Creative Commons licensing but doc contributors do want to be able to contribute without commercial implications. Any docs-core members care to comment on bringing it in the openstack-manuals repo if Martin is willing? Thanks, Anne [1] http://www.hastexo.com/resources/docs/installing-openstack-essex-4-ubuntu-1204-precise-pangolin/step-5-install-and-configur On Mon, Mar 26, 2012 at 8:50 AM, Martin Gerhard Loschwitz martin.loschw...@hastexo.com wrote: Hi folks, I've written a guide on how to install OpenStack Essex on Ubuntu 12.04. It covers the installation and configuration of Keystone, Glance, Nova and Horizon. By following this guide, even people that haven't collected much OpenStack experience so far should be able to get the virtualization environment up and running in a short period of time. The full document is available from here: http://www.hastexo.com/resources/docs/installing-openstack-essex-4-ubuntu-1204-precise-pangolin All feedback and comments are much appreciated -- thanks in advance! Best regards Martin -- Martin Gerhard Loschwitz Principal Consultant hastexo Professional Services ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] hardware specifications for a little private cloud
On 03/26/2012 06:56 AM, Alberto Molina Coballes wrote: Hi all, Hi Alberto! Welcome to the OpenStack community :) I'm a teacher at a sysadmin academy and we are planning to deploy a private cloud with OpenStack for educational/training purposes. We are currently selecting the optimal hardware configuration for our needs and I'm asking for some help to the list. Cool, sounds good. Using [1] as a reference, we are clear about hardware specifications of compute nodes (4 nodes with 2 processors), but we aren't about the best solution for node controller and optimal storage: Option 1: 1 server with 2 HD in RAID1 (nova controller, nova volume, glance, ...) + 1 SAN iSCSI Option 2: 1 server with 12 HD in RAID5/6 (nova controller, nova volume, glance, ...) We are excited about the possibilities that a private cloud brings to us and we don't want to fail in this critical step, so any help will be really appreciated. Option 1 might be easier to set up and work with. Not sure about costs, though... For small setups like this, you might want to use the Filesystem Glance storage driver targeted at the local filesystem and use the SAN+isci for the volume operations only. This would make it a bit easier to diagnose issues and administer Glance. Also, don't forget about MySQL, RabbitMQ and keystone. You need to put those on the controller node too! :) Best, -jay ___ 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] is this a bug in milestone-proposed keystone ? (cannotget endpoint-list, nor create endpoint)
Thanks for the explanation. But I am still a little confused about the
point of the templates. Having two implementations, one simple and one
less simple, is not simpler than having only one. You still need to user
the CLI for user, roles, etc. so having a different mechanism for
endpoints does not seem simple. With regard to performance, won't these
endpoint values be changing infrequently and so any reasonable caching
strategy would give good performance? Or am I missing something?
-David
On 3/26/2012 1:39 PM, Dolph Mathews wrote:
I think I'm to blame (apologies!) for suggesting that one driver was
preferred over the other (that was my understanding a few weeks ago,
based on test coverage). However, test coverage has since improved and
I think people are having good experience with the SQL driver.
The two methods are *not* functionally identical. The file-based
driver is simple and high-performance, and the sql-based driver
provides flexibility and API/CLI administration.
I've just proposed a review to clarify each option in the
http://keystone.openstack.org/configuration.html docs:
https://review.openstack.org/#change,5820
As well as a separate review to change the default backend to SQL,
since most users are looking for the CLI management commands out of
the box:
https://review.openstack.org/#change,5821
-Dolph
On Mon, Mar 26, 2012 at 8:29 AM, David Kranz david.kr...@qrclab.com
mailto:david.kr...@qrclab.com wrote:
There seems to be an unfortunate difference in opinion out there
about whether the keystone endpoints should be defined using
templates (devstack) or keystone calls (ubuntu). I don't know why
keystone is offering two very different, but seemingly
functionally identical, ways to do this. Is there a good reason?
Can this be sorted out so there is only one documented way to do this?
-David
On 3/26/2012 7:25 AM, Andiabes wrote:
Can you include your config?
The behavior you're describing seems to be consistent with a
missing backers configuration ...
Something like:
[identity]
driver = keystone.identity.backends.sql.Identity
[catalog]
driver = keystone.catalog.backends.sql.Catalog
Also, where/how are you installing?
On Mar 26, 2012, at 6:56 AM, Mandar Vaze
mandar.v...@vertex.co.in mailto:mandar.v...@vertex.co.in wrote:
I’m also getting the same error on latest master branch (updated
today)
Using setup created by devstack
-Mandar
*From:*openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net
mailto:openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net
mailto:vertex.co...@lists.launchpad.net] *On Behalf Of *.?o 0 O??
*Sent:* Monday, March 26, 2012 12:45 PM
*To:* Pierre Amadio
*Cc:* openstack
*Subject:* Re: [Openstack] is this a bug in milestone-proposed
keystone ? (cannotget endpoint-list, nor create endpoint)
hi,
I don't know if it is a bug but I come across the same problem
and wondering how to solve it.
-- Original --
*From: * Pierre Amadiopierre.ama...@canonical.com
mailto:pierre.ama...@canonical.com;
*Date: * Sun, Mar 25, 2012 04:35 AM
*To: * openstackopenstack@lists.launchpad.net
mailto:openstack@lists.launchpad.net;
*Subject: * [Openstack] is this a bug in milestone-proposed
keystone ? (cannotget endpoint-list, nor create endpoint)
Hi there !
I wanted to give a try to the milestone-proposed branch of
keystone and
got stuck quite fast.
I am not sure if i hit a bug and should report it, or if i'm doing
something wrong.
With previous version of keystone (read packaged on ubuntu
precise), i
was able to create endpoint the following way once keystone has been
installed:
1) setting some env variables:
export KEYSTONE_IP=192.168.122.102 # IP of your keystone API server
export SERVICE_ENDPOINT=http://$KEYSTONE_IP:35357/v2.0/
export SERVICE_TOKEN=999888777666
export NOVA_PUBLIC_URL=http://$NOVA_IP:8774/v1.1/%(tenant_id)s
http://$NOVA_IP:8774/v1.1/%%28tenant_id%29s
export NOVA_ADMIN_URL=$NOVA_PUBLIC_URL
export NOVA_INTERNAL_URL=$NOVA_PUBLIC_URL
2) creating services:
keystone service-create --name nova --type compute --description
'OpenStack Compute Service'
keystone service-create --name swift --type object-store
--description
'OpenStack Storage Service'
keystone service-create --name glance --type image --description
'OpenStack Image Service'
keystone service-create --name keystone --type identity
--description
'OpenStack Identity Service'
3) creating an endpoint for those services, starting with the
compute
service:
ID=$(keystone service-list | grep -i compute | awk '{print $2}')
keystone endpoint-create --region
Re: [Openstack] KVM disk performance
On Mon, 26 Mar 2012, Martin van Wilderen - JDN BV wrote: Hi Scott, kvm --version QEMU emulator version 0.13.91 (qemu-kvm-0.14.0-rc1), Copyright (c) 2003-2008 Fabrice Bellard virsh --version 0.8.8 uname -r 2.6.35-22-server Need any more info? Well, unfortunately there is lots more info needed, and I'm not really able to dedicate resources to debugging this at this point. I was curious because I had circumstantial evidence pointing to qemu-kvm 1.0 (in ubuntu 12.04) being slower than 11.10. However, your data above is similar to what I've seen in 12.04. Most definitely, if you want write performance, you will need fully allocated disks. The qcow sparse is good for quick deployment, but not good for write speed. You may also want to try using qed format disk as that is supposed to be a bit better. I had one kvm person suggest looking at barriers of the host's ext4 filesystem, saying: if you have ext4 filesystem underneath with barriers enabled, then you'll find that the guest will submit barriers to the host filesystem which will end up flushing the device cache A quick google showed http://blog.smartlogicsolutions.com/2009/06/04/mount-options-to-improve-ext4-file-system-performance on generally how to get some additional performance out of ext4. I'm interested in hearing what you find out, but unfortunately at the moment, I dont' have a magic bullet for you. Met vriendelijke groet, Martin van Wilderen Technical Manager On Mar 26, 2012, at 5:12 PM, Scott Moser wrote: Can you provide information about what version of kvm you're using ? I suspect this is really unrelated to openstack specifically. On Mon, 26 Mar 2012, Martin van Wilderen - JDN BV wrote: Hi List, I have a question about KVM disk performance. We are using Openstack Nova on three machines. These machines have a SSD drive with a dd write performance of about 130mb/s Within the instance the write performance is down to about 5 mb/s. When using the allocate trick (dd zero to disk before newfs) we get a performance of 20 mb/s. Things a have tried but don't give any extra results are: - Settings the disklayout from qcow2 to raw - Settings the cache type in libvirt.xml (writeback, writethrough, none) - Switching KSM on and off. - Tested with different guests OS, Linux, FreeBSD, Windows. Is there someone who had some extra info i can check? Or are there more people with this issue? Snippet from libvirt.xml driver type='qcow2'/ cache='writeback'/ source file='/var/lib/nova/instances/instance-0113/disk'/ target dev='vda' bus='virtio'/ Kind regards, Martin ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] BUG on dashboard (Horizon)
All configurations are correct and the service is running, if i try to run the status command on shell i prints running, and in fact it was, because i need keystone to access the horizon, in a test i stop the keystone and tried to log in, but it had identified a problem on access, then i up the service and i can log in. Them i think that's a bug, cannot be another thing once that all configurations are right. Em 26 de março de 2012 13:11, Dolph Mathews dolph.math...@gmail.comescreveu: Agree with the other posters; Keystone is not reachable from Horizon -- make sure it's running, keystone's IP and ports are reflected correctly in horizon config, etc. -Dolph On Mon, Mar 26, 2012 at 6:21 AM, Guilherme Souza souza.guilherm...@gmail.com wrote: Hello Razique, What do you want to say with: What type of install..., i've installed following the oficial tutorial http://docs.openstack.org/diablo/openstack-compute/install/content/, and keystone looks like working fine, apparently can i access the dashboardwithout problems. Em 26 de março de 2012 09:18, Razique Mahroua razique.mahr...@gmail.comescreveu: Hello Guillherme; looks like the Keystone server is not reachable. What type of install did you make ? *Nuage Co - Razique Mahroua** * razique.mahr...@gmail.com Le 23 mars 2012 à 20:20, Guilherme Souza a écrit : Hello folks, I'm having a bug on Horizon, i've installed it using the Diablo version, following the oficial tutorial. I can acess the dashboard, up instances, but when i try to acess the users and tenants page it prints a Error, to Users Unable to list users: [Errno 113] EHOSTUNREACH, or to tenants Unable to get tenant info: [Errno 113] EHOSTUNREACH, but it doesn't crashes the GUI. And in another installation at the same version of Dashboard, Diablo, it prints a timeout message and doesn't crashes the GUI too. Someone had the same error? Gratz Guilherme Souza ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Atenciosamente, Guilherme Santos Souza Sistemas de Informação - PUCRS Fone: (51) 9695-1070 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Atenciosamente, Guilherme Santos Souza Sistemas de Informação - PUCRS Fone: (51) 9695-1070 ___ 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] BUG on dashboard (Horizon)
Ah, it appears that only one backend is failing... which backend are you using for users, tenants, etc? SQL, LDAP? How is it configured? Also, unless you need diablo specifically, I'd recommend starting with the milestone proposed candidates for Folsom. -Dolph On Mon, Mar 26, 2012 at 11:58 AM, Guilherme Souza souza.guilherm...@gmail.com wrote: All configurations are correct and the service is running, if i try to run the status command on shell i prints running, and in fact it was, because i need keystone to access the horizon, in a test i stop the keystone and tried to log in, but it had identified a problem on access, then i up the service and i can log in. Them i think that's a bug, cannot be another thing once that all configurations are right. Em 26 de março de 2012 13:11, Dolph Mathews dolph.math...@gmail.comescreveu: Agree with the other posters; Keystone is not reachable from Horizon -- make sure it's running, keystone's IP and ports are reflected correctly in horizon config, etc. -Dolph On Mon, Mar 26, 2012 at 6:21 AM, Guilherme Souza souza.guilherm...@gmail.com wrote: Hello Razique, What do you want to say with: What type of install..., i've installed following the oficial tutorial http://docs.openstack.org/diablo/openstack-compute/install/content/, and keystone looks like working fine, apparently can i access the dashboard without problems. Em 26 de março de 2012 09:18, Razique Mahroua razique.mahr...@gmail.com escreveu: Hello Guillherme; looks like the Keystone server is not reachable. What type of install did you make ? *Nuage Co - Razique Mahroua** * razique.mahr...@gmail.com Le 23 mars 2012 à 20:20, Guilherme Souza a écrit : Hello folks, I'm having a bug on Horizon, i've installed it using the Diablo version, following the oficial tutorial. I can acess the dashboard, up instances, but when i try to acess the users and tenants page it prints a Error, to Users Unable to list users: [Errno 113] EHOSTUNREACH, or to tenants Unable to get tenant info: [Errno 113] EHOSTUNREACH, but it doesn't crashes the GUI. And in another installation at the same version of Dashboard, Diablo, it prints a timeout message and doesn't crashes the GUI too. Someone had the same error? Gratz Guilherme Souza ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Atenciosamente, Guilherme Santos Souza Sistemas de Informação - PUCRS Fone: (51) 9695-1070 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Atenciosamente, Guilherme Santos Souza Sistemas de Informação - PUCRS Fone: (51) 9695-1070 ___ 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] 回复： is this a bug in milestone-proposed keystone ? (cannotget endpoint-list, nor create endpoint)
Ah, you are correct! KVS does implement service CRUD, and therefore Catalog does as well (albeit, both without any persistence). However, only the SQL driver implements endpoint CRUD. Will update my review: https://review.openstack.org/#change,5820 On Mon, Mar 26, 2012 at 10:48 AM, Jay Pipes jaypi...@gmail.com wrote: On 03/26/2012 11:43 AM, Dolph Mathews wrote: ( This is significant gap in the current keystone docs, so I'll be ensuring this makes it into the docs ASAP; feedback here is very much appreciated! ) There are two driver options for your service catalog - one based on a flat file, and one backed by SQL. The flat file does not support administration commands from the client (e.g. keystone endpoint-create, keystone service-create), hence the HTTP 501 Not Implemented messages. This is incorrect, AFAICT. The templated catalog driver inherits from the KVS driver and only overrides the get_catalog() method, so it *should* be able to add and delete services, etc. -jay __**_ Mailing list: https://launchpad.net/~**openstackhttps://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~**openstackhttps://launchpad.net/~openstack More help : https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp ___ 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] [OpenStack] Xen Hypervisor
On 03/26/2012 04:35 PM, John Garbutt wrote: I certainly changed the plugin so it always required the host_uuid, but I also changed the “call_plugin” code in xenapi_conn to ensure we always pass the host_uuid. Indeed it looks like in the code path below, that you should get the host_uuid passed all the way though. I have not tested with XCP myself, only with XenServer 6. I am afraid I will not get chance to try this out till Wednesday (currently on holiday). One other useful log will be from XCP where it logs the parameters passed into the plugin (on XenSever it is /var/log/xensource.log, it could be /var/log/xcp.log? or xapi.log, can’t remember I am afraid) You should be able to track the host_uuid to ensure it gets from nova-xapi client-xapi server-plugin If you want to move on with your deployment a work around is to add this into the xenhost plugin: Change: host_uuid=arg_dict[‘host_uuid’] Into: host_uuid=_run_command(“xe host-list | grep uuid”).split(“:”)[-1].strip() Hi John, Why not using: xe host-list --minimal instead of the grep, split, strip code, which adds useless complexity? Also, this piece of code doesn't seem to be resistant to having more than one host as reply (in which case the UUID would be separated by a coma, if I'm not mistaking). Thomas ___ 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] is this a bug in milestone-proposed keystone ? (cannotget endpoint-list, nor create endpoint)
On Mon, Mar 26, 2012 at 11:12 AM, David Kranz david.kr...@qrclab.comwrote:
Thanks for the explanation. But I am still a little confused about the
point of the templates. Having two implementations, one simple and one less
simple, is not simpler than having only one. You still need to user the CLI
for user, roles, etc. so having a different mechanism for endpoints does
not seem simple. With regard to performance, won't these endpoint values be
changing infrequently and so any reasonable caching strategy would give
good performance? Or am I missing something?
The preference is to switch the default to the SQL driver, the other
backend was simply the first driver written and will likely be deprecated.
--andy
-David
On 3/26/2012 1:39 PM, Dolph Mathews wrote:
I think I'm to blame (apologies!) for suggesting that one driver was
preferred over the other (that was my understanding a few weeks ago, based
on test coverage). However, test coverage has since improved and I think
people are having good experience with the SQL driver.
The two methods are *not* functionally identical. The file-based driver
is simple and high-performance, and the sql-based driver provides
flexibility and API/CLI administration.
I've just proposed a review to clarify each option in the
http://keystone.openstack.org/configuration.html docs:
https://review.openstack.org/#change,5820
As well as a separate review to change the default backend to SQL, since
most users are looking for the CLI management commands out of the box:
https://review.openstack.org/#change,5821
-Dolph
On Mon, Mar 26, 2012 at 8:29 AM, David Kranz david.kr...@qrclab.comwrote:
There seems to be an unfortunate difference in opinion out there about
whether the keystone endpoints should be defined using templates (devstack)
or keystone calls (ubuntu). I don't know why keystone is offering two very
different, but seemingly functionally identical, ways to do this. Is there
a good reason? Can this be sorted out so there is only one documented way
to do this?
-David
On 3/26/2012 7:25 AM, Andiabes wrote:
Can you include your config?
The behavior you're describing seems to be consistent with a missing
backers configuration ...
Something like:
[identity]
driver = keystone.identity.backends.sql.Identity
[catalog]
driver = keystone.catalog.backends.sql.Catalog
Also, where/how are you installing?
On Mar 26, 2012, at 6:56 AM, Mandar Vaze mandar.v...@vertex.co.in
wrote:
I’m also getting the same error on latest master branch (updated today)
Using setup created by devstack
-Mandar
*From:* openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net [
mailto:openstack-bounces+mandar.vaze= openstack-bounces+mandar.vaze=
vertex.co...@lists.launchpad.net] *On Behalf Of *.?o 0 O??
*Sent:* Monday, March 26, 2012 12:45 PM
*To:* Pierre Amadio
*Cc:* openstack
*Subject:* Re: [Openstack] is this a bug in milestone-proposed keystone
? (cannotget endpoint-list, nor create endpoint)
hi,
I don't know if it is a bug but I come across the same problem and
wondering how to solve it.
-- Original --
*From: * Pierre Amadiopierre.ama...@canonical.com;
*Date: * Sun, Mar 25, 2012 04:35 AM
*To: * openstackopenstack@lists.launchpad.net;
*Subject: * [Openstack] is this a bug in milestone-proposed keystone ?
(cannotget endpoint-list, nor create endpoint)
Hi there !
I wanted to give a try to the milestone-proposed branch of keystone and
got stuck quite fast.
I am not sure if i hit a bug and should report it, or if i'm doing
something wrong.
With previous version of keystone (read packaged on ubuntu precise), i
was able to create endpoint the following way once keystone has been
installed:
1) setting some env variables:
export KEYSTONE_IP=192.168.122.102 # IP of your keystone API server
export SERVICE_ENDPOINT=http://$KEYSTONE_IP:35357/v2.0/
export SERVICE_TOKEN=999888777666
export NOVA_PUBLIC_URL=http://$NOVA_IP:8774/v1.1/%(tenant_id)s
export NOVA_ADMIN_URL=$NOVA_PUBLIC_URL
export NOVA_INTERNAL_URL=$NOVA_PUBLIC_URL
2) creating services:
keystone service-create --name nova --type compute --description
'OpenStack Compute Service'
keystone service-create --name swift --type object-store --description
'OpenStack Storage Service'
keystone service-create --name glance --type image --description
'OpenStack Image Service'
keystone service-create --name keystone --type identity --description
'OpenStack Identity Service'
3) creating an endpoint for those services, starting with the compute
service:
ID=$(keystone service-list | grep -i compute | awk '{print $2}')
keystone endpoint-create --region RegionOne --service_id $ID --publicurl
$NOVA_PUBLIC_URL --adminurl $NOVA_ADMIN_URL --internalurl
$NOVA_INTERNAL_URL
When i run this command with milestone-proposed, i experience the
following:
No handlers could be found for logger
Re: [Openstack] BUG on dashboard (Horizon)
On Mon, Mar 26, 2012 at 11:58 AM, Guilherme Souza souza.guilherm...@gmail.com wrote: All configurations are correct and the service is running, if i try to run the status command on shell i prints running, and in fact it was, because i need keystone to access the horizon, in a test i stop the keystone and tried to log in, but it had identified a problem on access, then i up the service and i can log in. I don't have enough info to say for sure if this is your problem, but the symptoms sound like there could be an issue with your service catalog config. There are actually 2 api services rolled into keystone, a user auth service and an admin service. The user service runs on port 5000, and is the component that logs you into dashboard. It sounds like this is working for you. User/Tenant management is provided by the admin portion of the api, which runs over port 35357. Dashboard learns about this service through the keystone serviceCatalog (using the adminURL of the identity service). So, in order for User/Tenant management to work correctly, you need to have the identity adminURL configured correctly in your serviceCatalog. I can't recall keystone diablo's exact db format, but you should be able to see your endpoints in mysql, and verify that the adminURL looks correct. You should also be able to curl this url (http://my_host:35357/v2.0). For your reference this is devstack's diablo/stable command to add the identity service to the serviceCatalog: $BIN_DIR/keystone-manage $* endpointTemplates add RegionOne keystone http://%SERVICE_HOST%:5000/v2.0 http://%SERVICE_HOST%:35357/v2.0 http://%SERVICE_HOST%:5000/v2.0 1 1 This is kinda a cryptic command, but the part referencing port 35357 is what sets the adminURL in question. Em 26 de março de 2012 13:11, Dolph Mathews dolph.math...@gmail.comescreveu: Agree with the other posters; Keystone is not reachable from Horizon -- make sure it's running, keystone's IP and ports are reflected correctly in horizon config, etc. -Dolph On Mon, Mar 26, 2012 at 6:21 AM, Guilherme Souza souza.guilherm...@gmail.com wrote: Hello Razique, What do you want to say with: What type of install..., i've installed following the oficial tutorial http://docs.openstack.org/diablo/openstack-compute/install/content/, and keystone looks like working fine, apparently can i access the dashboard without problems. Em 26 de março de 2012 09:18, Razique Mahroua razique.mahr...@gmail.com escreveu: Hello Guillherme; looks like the Keystone server is not reachable. What type of install did you make ? *Nuage Co - Razique Mahroua** * razique.mahr...@gmail.com Le 23 mars 2012 à 20:20, Guilherme Souza a écrit : Hello folks, I'm having a bug on Horizon, i've installed it using the Diablo version, following the oficial tutorial. I can acess the dashboard, up instances, but when i try to acess the users and tenants page it prints a Error, to Users Unable to list users: [Errno 113] EHOSTUNREACH, or to tenants Unable to get tenant info: [Errno 113] EHOSTUNREACH, but it doesn't crashes the GUI. And in another installation at the same version of Dashboard, Diablo, it prints a timeout message and doesn't crashes the GUI too. Someone had the same error? Gratz Guilherme Souza ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Atenciosamente, Guilherme Santos Souza Sistemas de Informação - PUCRS Fone: (51) 9695-1070 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Atenciosamente, Guilherme Santos Souza Sistemas de Informação - PUCRS Fone: (51) 9695-1070 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] Installion guide for OpenStack Essex on Ubuntu 12.04
Hi Martin, On 2012/03/26, at 22:50, Martin Gerhard Loschwitz wrote: I've written a guide on how to install OpenStack Essex on Ubuntu 12.04. It covers the installation and configuration of Keystone, Glance, Nova and Horizon. By following this guide, even people that haven't collected much OpenStack experience so far should be able to get the virtualization environment up and running in a short period of time. thank you so much for this guide! I'm currently getting started with OpenStack and found the existing documentation to be… lacking. This really helps! Best regards, Philipp ___ 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] Installion guide for OpenStack Essex on Ubuntu 12.04
On 03/26/2012 06:50 AM, Martin Gerhard Loschwitz wrote: Hi folks, I've written a guide on how to install OpenStack Essex on Ubuntu 12.04. It covers the installation and configuration of Keystone, Glance, Nova and Horizon. By following this guide, even people that haven't collected much OpenStack experience so far should be able to get the virtualization environment up and running in a short period of time. The full document is available from here: http://www.hastexo.com/resources/docs/installing-openstack-essex-4-ubuntu-1204-precise-pangolin All feedback and comments are much appreciated -- thanks in advance! Best regards Martin Good stuff, Martin! After a quick read, the biggest thing that stuck out as an eye-sore currently is the reference to Bug #959262 [1] and subsequent manual patching in the Horizon setup. I took a look at this today and confirmed its still affecting Ubuntu. The fix needs to be proposed to milestone-proposed / Essex rc1, which we can hopefully take care of tomorrow. If for whatever reason its not, we'll carry the small patch in Ubuntu going into 12.04. If there are any other packaging specific issue I overlooked, please don't hesitate to file bugs or ping me directly on IRC! Cheers, Adam [1] https://bugs.launchpad.net/ubuntu/+source/python-novaclient/+bug/959262 ___ 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] Installion guide for OpenStack Essex on Ubuntu 12.04
Hi ,everyone I followed all the steps until step4,then I got the following problem: When I run the glance index command,I got the error: Failed to show index . Got error: There was an error connecting to a server. Details:[errno 111] Connection refused Any one please give me any suggestions .Thank you:) On Mon, Mar 26, 2012 at 9:50 PM, Martin Gerhard Loschwitz martin.loschw...@hastexo.com wrote: Hi folks, I've written a guide on how to install OpenStack Essex on Ubuntu 12.04. It covers the installation and configuration of Keystone, Glance, Nova and Horizon. By following this guide, even people that haven't collected much OpenStack experience so far should be able to get the virtualization environment up and running in a short period of time. The full document is available from here: http://www.hastexo.com/resources/docs/installing-openstack-essex-4-ubuntu-1204-precise-pangolin All feedback and comments are much appreciated -- thanks in advance! Best regards Martin -- Martin Gerhard Loschwitz Principal Consultant hastexo Professional Services ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Stay with me,stay with my heart,honey. ___ 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-poc] Meeting tomorrow
Anyone have anything they would like to discuss tomorrow? After the Essex crush is over, I'd like to discuss the Technical Committee, but I would say do it after this week unless anyone objects. Thierry has a draft in the wiki: http://wiki.openstack.org/Governance/Foundation/TechnicalCommittee I think there are a couple of points that are still worth debating: 1) PTL membership on the Technical Committee 2) The concept of a Technical Member We'll have some more discussion on the general mailing list on this, but I wanted to bring it to the current PPB's attention specifically in case you're not following the other closely. Jonathan. ___ Mailing list: https://launchpad.net/~openstack-poc Post to : openstack-poc@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-poc More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise-openstack-essex-nova-trunk #664
text/html; charset=UTF-8: Unrecognized -- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
