Re: [Openstack] Missing(?) keystone service catalog
No, I have custom code running on Android, and I'm testing failures in curl by copying the JSON and headers that are sent to a shell. Nick On Fri, May 25, 2012 at 9:54 PM, Jay Pipes jaypi...@gmail.com wrote: On 05/25/2012 05:48 AM, Nick Lothian wrote: In case anyone else is running into this problem: I was authenticating without using a tenant ID. This seems to work on some implementations (TryStack, Rackspace), but not in others (DevStack, HPCloud). Are you sure that your OS_TENANT_NAME or OS_TENANT_ID environment variables were not set when using TryStack? If you follow the tutorials that folks have put together on using it, you likely source'd an rc file that contained your tenant information (since all trystack users have a separate tenant) 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 ___ 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] New layout of the OpenStack mailing lists
From: openstack-bounces+atul.jha=csscorp@lists.launchpad.net [openstack-bounces+atul.jha=csscorp@lists.launchpad.net] on behalf of Stefano Maffulli [stef...@openstack.org] Sent: Friday, May 25, 2012 9:19 PM To: Daniel P. Berrange Cc: User Groups Community, OpenStack; openstack Subject: Re: [Openstack] New layout of the OpenStack mailing lists On Fri 25 May 2012 01:04:20 AM PDT, Daniel P. Berrange wrote: I'm surprised to see the announce list being removed. What is the rational for that. Most large projects have a very low traffic list (~1 msg per day) dedicated for project announcements of new releases, security notices, important community messages etc, that is explicitly separate from the general users / developpers lists which are high traffic. The rationale is that in 2012 we have better ways to send announcements out: blogs, RSS, twitter, G+, newsletters, etc. Besides, the list hasn't been used for months and nobody complained for the lack of content. +1 In any case, my idea is to replace the list with a newsletter: people interested in receiving regular updates (like the weekly newsletter I send out) will subscribe there. cheers, stef ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp http://www.csscorp.com/common/email-disclaimer.php ___ 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] Why is an image required when booting from volume
I'm trying to figure out boot from volume, both so I can use it and so I can add it to the docs. It seems that when calling nova boot or using Horizon, you need to specify an image. Why is that? I naively tried to create a volume image by creating a volume and then doing on my volume server: dd if=/tmp/precise-server-cloudimg-amd64-disk1.img of=/dev/nova-volumes/volume-000d Then I tried this: $ nova boot --flavor 2 --key_name lorin --block_device_mapping /dev/vda=13:::0 test Which generated an error: Invalid imageRef provided. (HTTP 400) If I try to specify an image, it at least attempts to boot: $ nova boot --flavor 2 --key_name lorin --block_device_mapping /dev/vda=13:::0 --image 7d6923d9-1c13-4405-ba0c-41c7487dd6bc test I noticed that the devstack example specifies an image: https://github.com/openstack-dev/devstack/blob/master/exercises/boot_from_volume.sh: VOL_VM_UUID=`nova boot --flavor $INSTANCE_TYPE --image $IMAGE --block_device_mapping vda=$VOLUME_ID:::0 --security_groups=$SECGROUP --key_name $KEY_NAME $VOL_INSTANCE_NAME | grep ' id ' | get_field 2` Looking at nova/api/openstack/compute/servers.py, it does look like _image_uuid_from_href() is called regardless of whether we are booting from volume or not. What is --image used for when booting from volume? Take care, Lorin -- Lorin Hochstein Lead Architect - Cloud Services Nimbis Services, Inc. www.nimbisservices.com smime.p7s Description: S/MIME cryptographic signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Quantum+Openvswitch: could not open /dev/net/tun: Operation not permitted
Thank you Dan, Chris, Dean and Soheil for help. I very appreciated your help! Yes, I using Precise for this lab and after I have added /dev/net/tun to the cgroup_device_acl list I have ACTIVE state for my running instances. BTW, the doc http://openvswitch.org/openstack/documentation/ already have this clarification, thanks)) Well, although that the instances are running, I can't ping or ssh to them. I already doing this: $ nova secgroup-add-rule default icmp -1 -1 0.0.0.0/0 $ nova secgroup-add-rule default tcp 22 22 0.0.0.0/0 but didn't help! On Fri, May 25, 2012 at 12:40 AM, Dan Wendlandt d...@nicira.com wrote: Hi Igor, Are you running this on Precise? If so, Precise is a bit pickier than previous versions about requiring a setting in /etc/libvirt/qemu.conf You need to add /dev/net/tun to the cgroup_device_acl list in that file, and restart libvirt. This is actually handled automatically by a branch I've pushed for review in devstack: https://review.openstack.org/#/c/7001/ It has lots of positive reviews, but still needs one more core review and I've been waiting a while. If you're a devstack core, please give me a hand! :) Dan p.s. the root cause of needing to tweak /etc/libvirt/qemu.conf is that we're using libvirt interface type=ethernet elements to work with openvswitch. Starting in libvirt 0.9.11 (not available in precise), openvswitch is integrated directly with libvirt, meaning that using type=ethernet (and the workaround) is no longer necessary. On Thu, May 24, 2012 at 1:05 PM, Igor Laskovy igor.lask...@gmail.com wrote: Hello all from sunny Kiev)) I have built nova+quantum+openvswitch without nova-volume lab on two nodes - one controller with everything on it except nova-compute and second dedicated compute node with nova-compute: During creating VM I have error which I still can't fix: $ nova boot --image precise --flavor m1.tiny my-precise-vm3 $ nova list +--+++--+ | ID | Name | Status | Networks | +--+++--+ | 5a72aa9f-5743-486a-9496-130d367bc665 | my-precise-vm3 | ERROR | | +--+++--+ # cat /var/log/libvirt/qemu/instance-0012.log 2012-05-24 19:51:47.994+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-1.0 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name instance-0012 -uuid 5a72aa9f-5743-486a-9496-130d367bc665 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-0012.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -drive file=/var/lib/nova/instances/instance-0012/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,ifname=tap24b9f3da-8b,script=,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=fa:16:3e:49:f1:a9,bus=pci.0,addr=0x3 -netdev tap,ifname=tapcdd6bc93-86,script=,id=hostnet1 -device rtl8139,netdev=hostnet1,id=net1,mac=fa:16:3e:68:94:b4,bus=pci.0,addr=0x4 -chardev file,id=charserial0,path=/var/lib/nova/instances/instance-0012/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -usb -device usb-tablet,id=input0 -vnc 192.168.1.71:0 -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 Domain id=4 is tainted: shell-scripts char device redirected to /dev/pts/2 kvm: -netdev tap,ifname=tap24b9f3da-8b,script=,id=hostnet0: could not open /dev/net/tun: Operation not permitted kvm: -netdev tap,ifname=tap24b9f3da-8b,script=,id=hostnet0: Device 'tap' could not be initialized 2012-05-24 19:51:48.175+: shutting down /var/lib/nova/instances/instance-0012# virsh create libvirt.xml error: Failed to create domain from libvirt.xml error: internal error Process exited while reading console log output: char device redirected to /dev/pts/2 kvm: -netdev tap,ifname=tap24b9f3da-8b,script=,id=hostnet0: could not open /dev/net/tun: Operation not permitted kvm: -netdev tap,ifname=tap24b9f3da-8b,script=,id=hostnet0: Device 'tap' could not be initialized Waiting any advises! -- Igor Laskovy Kiev, Ukraine ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ -- Igor Laskovy Kiev, Ukraine
Re: [Openstack] Quantum+Openvswitch: could not open /dev/net/tun: Operation not permitted
Hi Igor, I'd first access the VM via VNC and make sure it has booted and is getting an IP address via DHCP. The easiest way to do this is using the VNC consoles exposed via Horizon, but you can also use a tool like vncviewer directly from the command line. If you think it may be an issue with security groups, running nova with the following flag will disable security groups so you can see if that is what is blocking the traffic: firewall_driver=nova.virt.firewall.NoopFirewallDriver . Of course, you'll need to restart nova-compute. With devstack, you can set this in your localrc: LIBVIRT_FIREWALL_DRIVER=nova.virt.firewall.NoopFirewallDriver . Dan On Sat, May 26, 2012 at 11:31 AM, Igor Laskovy igor.lask...@gmail.comwrote: Thank you Dan, Chris, Dean and Soheil for help. I very appreciated your help! Yes, I using Precise for this lab and after I have added /dev/net/tun to the cgroup_device_acl list I have ACTIVE state for my running instances. BTW, the doc http://openvswitch.org/openstack/documentation/ already have this clarification, thanks)) Well, although that the instances are running, I can't ping or ssh to them. I already doing this: $ nova secgroup-add-rule default icmp -1 -1 0.0.0.0/0 $ nova secgroup-add-rule default tcp 22 22 0.0.0.0/0 but didn't help! On Fri, May 25, 2012 at 12:40 AM, Dan Wendlandt d...@nicira.com wrote: Hi Igor, Are you running this on Precise? If so, Precise is a bit pickier than previous versions about requiring a setting in /etc/libvirt/qemu.conf You need to add /dev/net/tun to the cgroup_device_acl list in that file, and restart libvirt. This is actually handled automatically by a branch I've pushed for review in devstack: https://review.openstack.org/#/c/7001/ It has lots of positive reviews, but still needs one more core review and I've been waiting a while. If you're a devstack core, please give me a hand! :) Dan p.s. the root cause of needing to tweak /etc/libvirt/qemu.conf is that we're using libvirt interface type=ethernet elements to work with openvswitch. Starting in libvirt 0.9.11 (not available in precise), openvswitch is integrated directly with libvirt, meaning that using type=ethernet (and the workaround) is no longer necessary. On Thu, May 24, 2012 at 1:05 PM, Igor Laskovy igor.lask...@gmail.com wrote: Hello all from sunny Kiev)) I have built nova+quantum+openvswitch without nova-volume lab on two nodes - one controller with everything on it except nova-compute and second dedicated compute node with nova-compute: During creating VM I have error which I still can't fix: $ nova boot --image precise --flavor m1.tiny my-precise-vm3 $ nova list +--+++--+ | ID | Name | Status | Networks | +--+++--+ | 5a72aa9f-5743-486a-9496-130d367bc665 | my-precise-vm3 | ERROR | | +--+++--+ # cat /var/log/libvirt/qemu/instance-0012.log 2012-05-24 19:51:47.994+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-1.0 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name instance-0012 -uuid 5a72aa9f-5743-486a-9496-130d367bc665 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-0012.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -drive file=/var/lib/nova/instances/instance-0012/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,ifname=tap24b9f3da-8b,script=,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=fa:16:3e:49:f1:a9,bus=pci.0,addr=0x3 -netdev tap,ifname=tapcdd6bc93-86,script=,id=hostnet1 -device rtl8139,netdev=hostnet1,id=net1,mac=fa:16:3e:68:94:b4,bus=pci.0,addr=0x4 -chardev file,id=charserial0,path=/var/lib/nova/instances/instance-0012/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -usb -device usb-tablet,id=input0 -vnc 192.168.1.71:0 -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 Domain id=4 is tainted: shell-scripts char device redirected to /dev/pts/2 kvm: -netdev tap,ifname=tap24b9f3da-8b,script=,id=hostnet0: could not open /dev/net/tun: Operation not permitted kvm: -netdev tap,ifname=tap24b9f3da-8b,script=,id=hostnet0: Device 'tap' could not be initialized 2012-05-24 19:51:48.175+: shutting down /var/lib/nova/instances/instance-0012# virsh create libvirt.xml error: Failed to create
[Openstack] how to fix: iptables-restore v1.4.12: host/network `None' not found
hi, I had been fighting this problem for days, and right now knew it perhaps was a bug, got it from : https://bugs.launchpad.net/ubuntu/+source/nova/+bug/907197 It was happened in a fresh install for compute node base on ubuntu newest version 12.04LTS, including nova-compute,nova-network,nova-api. Both of nova-compute and nova-network could start normally and I also could get smile face in NovaCC node. But when i created a new instance and was sent to that new node by scheduler , it always could not get success and always show: Stderr: iptables-restore v1.4.12: host/network `None' not found\nError occurred at line: 23\nTry `iptables-restore -h' or 'iptables-restore --help' for more information.\n. I am not sure it is same as the bug report and i appreciate if someone could give me a help how to fix this problem, it stopped me for days to run a new node. Best regards, Romi ___ 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] Why is an image required when booting from volume
If there is a separate kernel and ramdisk needed for the boot from volume, it is pulled from image properties. Otherwise it is basically useless. Vish On May 26, 2012, at 8:22 AM, Lorin Hochstein wrote: I'm trying to figure out boot from volume, both so I can use it and so I can add it to the docs. It seems that when calling nova boot or using Horizon, you need to specify an image. Why is that? I naively tried to create a volume image by creating a volume and then doing on my volume server: dd if=/tmp/precise-server-cloudimg-amd64-disk1.img of=/dev/nova-volumes/volume-000d Then I tried this: $ nova boot --flavor 2 --key_name lorin --block_device_mapping /dev/vda=13:::0 test Which generated an error: Invalid imageRef provided. (HTTP 400) If I try to specify an image, it at least attempts to boot: $ nova boot --flavor 2 --key_name lorin --block_device_mapping /dev/vda=13:::0 --image 7d6923d9-1c13-4405-ba0c-41c7487dd6bc test I noticed that the devstack example specifies an image: https://github.com/openstack-dev/devstack/blob/master/exercises/boot_from_volume.sh: VOL_VM_UUID=`nova boot --flavor $INSTANCE_TYPE --image $IMAGE --block_device_mapping vda=$VOLUME_ID:::0 --security_groups=$SECGROUP --key_name $KEY_NAME $VOL_INSTANCE_NAME | grep ' id ' | get_field 2` Looking at nova/api/openstack/compute/servers.py, it does look like _image_uuid_from_href() is called regardless of whether we are booting from volume or not. What is --image used for when booting from volume? Take care, Lorin -- Lorin Hochstein Lead Architect - Cloud Services Nimbis Services, Inc. www.nimbisservices.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
