November 2012 - openSUSE Public Cloud - openSUSE Mailing Lists

Re: [opensuse-cloud] Running openstack-quickstart-demosetup - errors
by Bernhard M. Wiedemann 27 Nov '12

27 Nov '12

Am 27.11.2012 16:16, schrieb Tony Su: > Thx, > Will consider. > I installed Folsom packages assuming they should be stable and most current. > > Tony yes, they are more current, but we only recently started packaging them and thus integration + testing still needs to be done. Ciao Bernhard M. -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-cloud+owner(a)opensuse.org

1 0

[opensuse-cloud] Running openstack-quickstart-demosetup - errors
by Tony Su 27 Nov '12

27 Nov '12

Hello, Issues setting up on my laptop. Maybe possible undocumented requirements? Setup 1: System: openSUSE 12.2 KDE 4.8 WiFi connection, typically only User Mode Networking and Host Only networking has been tried Virtualization: QEMU-KVM Setup 2: Host: system described above in Setup 1 Guest: openSUsE 12.2 server (text only, using minimal install pattern) Networking: eth0 bound to whatever virtual network is available, typically User Mode Networking 1. Running the openstack-quickstart-demosetup script on my Host(Setup 1), the script seems to have mostly run successfully but ends with the following which contains a number of errors. It may not be surprising to see HTTP related errors if the new web content is deployed in the default website (no subdirectory, no sub web) because of course I'm running other stuff in the existing local webserver already. If these errors are due to collisions with other websites, can something be modified to deploy to a different subdirectory? BTW - I don't see any new webpages in /srv/www/htdocs ERROR: n/a (HTTP 400) + nova secgroup-add-rule default tcp 1 65535 0.0.0.0/0 ERROR: n/a (HTTP 400) + nova secgroup-add-rule default udp 1 65535 0.0.0.0/0 ERROR: n/a (HTTP 400) + nova secgroup-list-rules default ERROR: n/a (HTTP 400) + for user in demo admin + setcreds admin openstack + export NOVA_PROJECT_ID=admin + NOVA_PROJECT_ID=admin + '[' -z admin ']' + export NOVA_USERNAME=admin + NOVA_USERNAME=admin + export NOVA_API_KEY=openstack + NOVA_API_KEY=openstack + '[' -z openstack ']' + export EC2_ACCESS_KEY=admin + EC2_ACCESS_KEY=admin + export EC2_SECRET_KEY=openstack + EC2_SECRET_KEY=openstack ++ getkstoken + export TOKEN=3672c679-cd2f-465f-b9fe-6d6ea7e42208 + TOKEN=3672c679-cd2f-465f-b9fe-6d6ea7e42208 + nova secgroup-add-rule default icmp -1 -1 0.0.0.0/0 ERROR: n/a (HTTP 400) + nova secgroup-add-rule default tcp 1 65535 0.0.0.0/0 ERROR: n/a (HTTP 400) + nova secgroup-add-rule default udp 1 65535 0.0.0.0/0 ERROR: n/a (HTTP 400) + nova secgroup-list-rules default ERROR: n/a (HTTP 400) 2. Despite the problem described running the demosetup script on the Host, may try to run in a Guest soon. are there any gotchas to be avoided doing that, and am I correct that the demosetup will deploy all openstack components on the same machine? TIA, Tony -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-cloud+owner(a)opensuse.org

2 1

[opensuse-cloud] Fwd: KVM weirdness on laptop - Need opinions
by Tony Su 26 Nov '12

26 Nov '12

Hello, Am hoping to get experienced eyes on this to evaluate how much of what I'm seeing is expected and what is not. System: openSUSE 12.2 Desktop: KDE 4.8 Virtualization: QEMU-KVM Also using graphical virt-manager Hardware: Laptop with occasionally available WiFi - I have found that anything configured for bridged networking still requires a wired connection, usually binding to eth0. - I have found that when any real connection to a Network exists (wireless or wired), if a Host Only network does not exist, then the Guest will be automatically configured to use User Mode Networking <only when the NIC is created>. - When a physical connection does not exist for a Guest previously created using a NIC configured for User Mode Networking, User Mode Networking will fail with an error "service unavailable, port 5900" which likely means that a VNC connection cannot be made. - Curiously, even with no physical network connection, if a Host Only network is created and a second virtual network for the new Host Only network is added to the Guest described previously, the Guest VM will boot up (no service unavailable, port 5900 error) and can even be viewed using virt-viewer. But, on closer inspection running ifconfig in the Guest reveals only one working NIC configured with an IP address for the User Mode Network while running ifconfig on the Host reveals that only the Host Only network is running and available. So, of course, Host and Guest cannot communicate using TCP/IP with each other except using virt-viewer (should not work?). - Have not tried, but am considering the idea of configuring the Host Only network to share the same networkID as the User Mode Network (10.0.2.0/24) but make sure the DHCP ranges are different. Theoretically I think this workaround might work but shouldn't be required. TIA, Tony -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-cloud+owner(a)opensuse.org

1 0