[Openstack] Error in documentation: Swift + Keystone + S3
Hi, today, I was trying to setup Swift with Keystone authentication and S3 compatibility. Thanks to the very good documentation at http://swift.openstack.org/ and http://keystone.openstack.org/configuringservices.html I got a working setup quite fast, however S3 compatibility didn't work. The client couldn't authenticate, got a HTTP 500 error, which was caused by Keystone responding with a HTTP 404 to an internal request to /v2.0/s3tokens. After several hours, I found out, that no one ever mentions the small detail, that you have to include this in keystone.conf: [filter:s3_extension] paste.filter_factory = keystone.contrib.s3:S3Extension.factory and add s3_extension in the [pipeline:admin_api] section between ec2_extension and crud_extension. As a user, that's nearly impossible to find out - try it using the documentation and Google. The only official place, where you can find it mentioned, is in the middle of the 81.5kb stack.sh inside devstack and you'll only find that, if you already know exactly what you're looking for :/ I'm currently trying to get a CCLA signed by my company, if that succeeds, I'd like to contribute a fix to the docs. In the meantime, maybe that already helps someone. :) Best regards, -- Philipp Wollermann Infrastructure Engineer CyberAgent, Inc. (Tokyo) https://github.com/philwo ___ 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] Using Foreign Keys
Hi, On Apr 12, 2012, at 21:35, J. Daniel Schmidt wrote: One reviewer commented: i don't approve of adding foreign keys, and we should probably remove the existing ones (in UserTenantMembership and in Endpoint) and on we shouldn't be using foreign keys at all, they are a crutch that are not available everywhere what the … !? I'm not actively participating in OpenStack development yet, so my opinion may carry no weight - but this is ridiculous. IMHO OpenStack is not some who needs data integrity anyway-web2.0 project, it's meant to provide a stable, robust platform where people run mission-critical production stuff. Calling our test cluster in the office BrokenStack is fun for a while and the 0 days since last exception sign wasn't bad either, but the fun stops when you actually need to depend on this software running. We should implement as many checks for integrity and validity of data as possible and if a foreign key actually catches something, that means that your last line of defense just stopped the worst and you should have failed much earlier. And someone is actually thinking about *removing* that? I'm all for a switch to the add as much foreign keys as we can policy. Actually, why are they not created automatically? If one uses an ORM correctly, there should be no way to actually *not* create them. -- Philipp Wollermann Infrastructure Engineer CyberAgent, Inc. (Tokyo) https://github.com/philwo ___ 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] Canonical AWSOME
Hi, I just saw the announcement of Canonical's AWSOME (https://launchpad.net/awsome), providing a translation proxy from the EC2 API to the OpenStack API. I'm definitely not an expert regarding OpenStack, but… doesn't OpenStack already support an EC2 compatibility API? At least, I can use the euca2ools without problems on OpenStack Nova Diablo. I haven't tried Swift yet. What's the advantage of replacing the native EC2 compatibility layer with AWSOME from a user / operator point of view? Thanks :) Philipp -- Philipp Wollermann Infrastructure Engineer CyberAgent, Inc. (Tokyo) https://github.com/philwo ___ 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] No official Diablo 2011.3.1 for oneiric?
On Apr 5, 2012, at 18:47, Thierry Carrez wrote: Philipp Wollermann wrote: am I right, that the official packages of openstack (nova) for Ubuntu 11.10 (oneiric) were never updated to Diablo 2011.3.1 and no bug-fixes from after the initial release were ever included? I checked the change log of the nova packages, and it seems like the maintainers only fixed security issues. The stable/diablo branches, and the resulting 2011.3.1 release, are a cross-distro effort to maintain a stable version of past releases. Each distribution of OpenStack follows its own rules on what patches it backports, in the case of Ubuntu itself, it follows: https://wiki.ubuntu.com/StableReleaseUpdates Thank you for the explanation. I understand that some users would rather live with known unfixed bugs than the risk of introducing new ones through a fix and that this is the way Ubuntu handles updates to packages. However, I was wondering, because nova is already part of the SRU process, yet the latest version of nova in ubuntu-proposed is hanging in this state since 4 months. Even if it ever gets released to ubuntu-updates, it's probably outdated again. It's totally acceptable if Ubuntu chooses to handle their packages like this, providing a very stable and reliable base system - though as it is also the primary and kind of official platform for OpenStack deployments, I think it would be greatly appreciated if there would be an officially maintained PPA which contains the most up-to-date stable release of OpenStack for the latest version(s) of Ubuntu. Then, users themselves could choose whether to trust and track the official releases or stick to Ubuntu's releases. Best regards, -- Philipp Wollermann Infrastructure Engineer CyberAgent, Inc. (Tokyo) https://github.com/philwo ___ 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] HELP: create VM failure
Hi Sam,
did you check /etc/nova/nova-compute.conf ?
Ubuntu has this special configuration file in which the libvirt_type is set
again, overriding what you set in nova.conf.
I didn't notice that on my first install of OpenStack on Ubuntu, causing
instance spawning to fail.
Best regards,
Philipp Wollermann
Infrastructure Engineer
CyberAgent, Inc. (Tokyo)
https://github.com/philwo
On 2012/04/02, at 8:35, Sam Su wrote:
Hi Leander,
Thank you for you response.
I have double checked the value of libvirt_type in nova.conf, it is kvm, not
hvm. I search this problem in Google, it looks like a bug of libvirt before.
https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/445253
I tried to change libvirt_type=qemu and reboot system, nothing was changed.
Maybe this problem is because my Ubuntu server is installed in a VMWare VM. I
am planning to re-install Openstack in a physical machine.
Thanks,
Sam
On Sun, Apr 1, 2012 at 3:04 PM, Leander Bessa leande...@gmail.com wrote:
Maybe you specified --libvirt_type=hvm instead of --libvirt_type=kvm in your
nova.conf file.
On Sun, Apr 1, 2012 at 8:44 PM, Sam Su susltd...@gmail.com wrote:
Hi,
I am trying to deploy Openstack all-in-one environment (Nova, Glance,
Keystone, Dashboard ) from scratch in an Ubuntu 12.04 server, After installed
Nova, I tried to create a VM with nova command but failed:
root@ubuntu:/etc/nova# nova boot --flavor 1 --image
8e7f9978-86b2-4c75-a0a8-44b0bb2a46e2 --key_name key1 VM2
+-+--+
| Property |Value |
+-+--+
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-SRV-ATTR:host| ubuntu |
| OS-EXT-SRV-ATTR:hypervisor_hostname | None |
| OS-EXT-SRV-ATTR:instance_name | instance-0002|
| OS-EXT-STS:power_state | 0|
| OS-EXT-STS:task_state | scheduling |
| OS-EXT-STS:vm_state | building |
| accessIPv4 | |
| accessIPv6 | |
| adminPass | Yj6mVrxaEiX6 |
| config_drive| |
| created | 2012-04-01T19:25:54Z |
| flavor | m1.tiny |
| hostId | |
| id | c15be925-c4d8-4b76-b7c3-e94ebe513cf1 |
| image | Ubuntu 11.10 cloudimg amd64 |
| key_name| key1 |
| metadata| {} |
| name| VM2 |
| progress| 0|
| status | BUILD|
| tenant_id | 2660dedf826c4510aff873c05d9d506b |
| updated | 2012-04-01T19:25:54Z |
| user_id | b42c715d94384aa6a66c56df44ac69b2 |
+-+--+
root@ubuntu:/etc/nova# nova show VM2
+-+--+
| Property |
Value |
+-+--+
| OS-DCF:diskConfig | MANUAL
|
| OS-EXT-SRV-ATTR:host| ubuntu
|
| OS-EXT-SRV-ATTR:hypervisor_hostname | None
|
| OS-EXT-SRV-ATTR:instance_name | instance-0002
|
| OS-EXT-STS:power_state | 0
|
| OS-EXT-STS:task_state | spawning
|
| OS-EXT-STS:vm_state | error
Re: [Openstack] (Chef) knife openstack with Essex RC1?
Hi, I wrote a mail to Matt @ Opscode, who wrote that guide, some days ago inquiring about the state of the guide and his cookbooks repository. He told me that it's out of date and shouldn't be used for newer versions of OpenStack - however there is much work going on for OpenStack Essex + Chef at https://github.com/rcbops/chef-cookbooks/tree/ubuntu-precise :) According to him, this repository will probably become the base for his own guide again, once he has time to work on it. Best regards, Philipp Wollermann Infrastructure Engineer CyberAgent, Inc. (Tokyo) https://github.com/philwo On 2012/04/03, at 1:31, Brian Parker wrote: Hi! Has anyone tried following the instructions for knife openstack with Essex? We are trying these steps: http://wiki.opscode.com/display/chef/OpenStack+Bootstrap+Fast+Start+Guide When attempting knife openstack flavor list, we are getting a ERROR: RuntimeError: Unable to parse service catalog. error because the service catalog is empty in the response. Thanks! Brian ___ 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] How to recover nova-compute from a failed nova boot?
Hi, I set up OpenStack according to Martin's tutorial at hastexo.com today on my development machine inside VirtualBox. As I forgot to change the libvirt_type to qemu and kvm isn't available inside VirtualBox, nova-compute understandably failed to boot the VM I created. I changed the value in nova.conf (and nova-compute.conf as well) and restarted the nova services, expecting that now everything just boots up correctly, but nova-compute didn't recover at all. Instead, I got this exception in the logs: 2012-03-27 14:59:01 CRITICAL nova [-] Instance instance-0001 could not be found. (nova): TRACE: Traceback (most recent call last): (nova): TRACE: File /usr/bin/nova-compute, line 49, in module (nova): TRACE: service.wait() (nova): TRACE: File /usr/lib/python2.7/dist-packages/nova/service.py, line 413, in wait (nova): TRACE: _launcher.wait() (nova): TRACE: File /usr/lib/python2.7/dist-packages/nova/service.py, line 131, in wait (nova): TRACE: service.wait() (nova): TRACE: File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 166, in wait (nova): TRACE: return self._exit_event.wait() (nova): TRACE: File /usr/lib/python2.7/dist-packages/eventlet/event.py, line 116, in wait (nova): TRACE: return hubs.get_hub().switch() (nova): TRACE: File /usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py, line 177, in switch (nova): TRACE: return self.greenlet.switch() (nova): TRACE: File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 192, in main (nova): TRACE: result = function(*args, **kwargs) (nova): TRACE: File /usr/lib/python2.7/dist-packages/nova/service.py, line 101, in run_server (nova): TRACE: server.start() (nova): TRACE: File /usr/lib/python2.7/dist-packages/nova/service.py, line 162, in start (nova): TRACE: self.manager.init_host() (nova): TRACE: File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 247, in init_host (nova): TRACE: self.reboot_instance(context, instance['uuid']) (nova): TRACE: File /usr/lib/python2.7/dist-packages/nova/exception.py, line 114, in wrapped (nova): TRACE: return f(*args, **kw) (nova): TRACE: File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 153, in decorated_function (nova): TRACE: function(self, context, instance_uuid, *args, **kwargs) (nova): TRACE: File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 171, in decorated_function (nova): TRACE: return function(self, context, instance_uuid, *args, **kwargs) (nova): TRACE: File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 898, in reboot_instance (nova): TRACE: reboot_type) (nova): TRACE: File /usr/lib/python2.7/dist-packages/nova/exception.py, line 114, in wrapped (nova): TRACE: return f(*args, **kw) (nova): TRACE: File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 753, in reboot (nova): TRACE: if self._soft_reboot(instance): (nova): TRACE: File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 773, in _soft_reboot (nova): TRACE: dom = self._lookup_by_name(instance.name) (nova): TRACE: File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 1567, in _lookup_by_name (nova): TRACE: raise exception.InstanceNotFound(instance_id=instance_name) (nova): TRACE: InstanceNotFound: Instance instance-0001 could not be found. (nova): TRACE: I can only guess, that nova-compute failed somewhere where it isn't expected and left the data regarding this VM in an undefined state. I found no way to recover from this failure. I tried to just nova delete the machine, checked a few minutes later using nova show and saw: OS-DCF:diskConfig | MANUAL OS-EXT-SRV-ATTR:host| vagrant-precise64 OS-EXT-SRV-ATTR:hypervisor_hostname | None OS-EXT-SRV-ATTR:instance_name | instance-0001 OS-EXT-STS:power_state | 8 OS-EXT-STS:task_state | deleting OS-EXT-STS:vm_state | active ... That looks right, but the deletion process never finishes. Nothing at all happens in the logs. In nova list, the instance is still listed as Status: ACTIVE. I tried to stop nova, delete the instance directory in /var/lib/nova/instances and restart nova, but that didn't help either (same exception). I stopped nova again, deleted the VM from the instances (+ security_group_instance_association and instance_info_caches) table in nova's MySQL DB and restarted nova, but just got this different exception in the logs: 2012-03-27 14:55:11 ERROR nova.rpc.amqp [req-26b4686a-85f4-4566-bb0f-d87e8456b1f2 6b177562cbc1434fade182a45427134d 3a21af5fa5fc470ebe2f2471ff5b49d3] Exception during message handling (nova.rpc.amqp): TRACE: Traceback (most recent call last): (nova.rpc.amqp): TRACE: File /usr/lib/python2.7/dist-packages/nova/rpc/amqp.py, line 252, in _process_data (nova.rpc.amqp): TRACE: rval =
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
