April 2013 - openSUSE Public Cloud - openSUSE Mailing Lists

[opensuse-cloud] Test result mails from Jenkins
by Sascha Peilicke 30 Apr '13

30 Apr '13

Hello fellow clouders, from now on, our <strike>holy</strike>beloved ci.opensuse.org will sent mails for hand-picked test Jobs to this mailinglist. This is yet another delivery in opening up the testing infrastructure behind the openSUSE communities OpenStack project. We try to keep the volume low but in case you happen to receive to many of those nag mails, feel free to join the fun and help us making OpenStack on openSUSE even more awesome than it already is! -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) -- 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] Jenkins build is back to normal : crowbar-travis_ci-trackupstream #6615
by admin＠opensuse.org 30 Apr '13

30 Apr '13

See <http://ci.opensuse.org/job/crowbar-travis_ci-trackupstream/6615/> -- 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] python module updates for Grizzly
by Dirk Müller 29 Apr '13

29 Apr '13

Hi, although we tried to freeze the python module dependencies already, I took a look and found some interesting updates being released upstream: python-paramiko, a ssh client update had a major version update. Although I don't know what has changed in detail, I would assume that the later version is better (more secure, compatible, blabla) python-pytz, a timezone fork for the dashboard. I'd suggest to go with the latest releases for those, as well as for some of the test related tools (if they pass unit testing on master). Any objections? Greetings, Dirk -- 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] Django in Factory
by Bernhard M. Wiedemann 29 Apr '13

29 Apr '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I am wondering about current Factory Django behaviour python /usr/lib/python2.7/site-packages/django/bin/django-admin.py help does not show collectstatic even though there is /usr/lib/python2.7/site-packages/django/contrib/staticfiles/management/commands/collectstatic.py and https://docs.djangoproject.com/en/dev/ref/contrib/staticfiles/#django-admin… suggests it to be usable. We need this for the openstack-dashboard package which otherwise fails for Factory. Ciao Bernhard M. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFxGHgACgkQSTYLOx37oWRi7QCg2AAnVC28sgLsAR3zzX52nDEn DoMAn2ek0g9waxtBZHGjwSAzk3dHmBEG =G9WY -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-cloud+owner(a)opensuse.org

3 6

[opensuse-cloud] openstack-* package submissions to Factory
by Andreas Jaeger 26 Apr '13

26 Apr '13

I just reviewed and declined a lot of openstack packages since the changes files contained removal of entries and I did not see that those were added anywhere else. What's going on here? The changes are sometimes quite extensive and therefore it's difficult to figure out whether there are some changes lost or not. Let me add the review team so that they are aware of this packages, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-cloud+owner(a)opensuse.org

5 17

[opensuse-cloud] quantum: Systemd service files?
by Andreas Jaeger 26 Apr '13

26 Apr '13

I've started adding systemd service files to quantum (taking what Fedora has) and noticed that their setup is different from ours, especially they have many more service files than we have have init ones. Details: https://build.opensuse.org/package/show?package=openstack-quantum&project=h… Could somebody review my changes and tell me whether this is the right way forward - or tell me what to change? Feel free to enhance as well ;) Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-cloud+owner(a)opensuse.org

4 8

[opensuse-cloud] Folsom cleanvm failing
by Dirk Müller 22 Apr '13

22 Apr '13

Hi, Cleanvm for Folsom is currently failing with: 00:15:16 Traceback (most recent call last): 00:15:16 File "/usr/bin/glance", line 5, in <module> 00:15:16 from pkg_resources import load_entry_point 00:15:16 File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 2739, in <module> 00:15:16 parse_requirements(__requires__), Environment() 00:15:16 File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 588, in resolve 00:15:16 raise DistributionNotFound(req) 00:15:16 pkg_resources.DistributionNotFound: warlock>=0.7.0,<2 which is caused by python-glanceclient following git master, but python-warlock being pinned to the version 0.6.0 from openSUSE:12.3. we can either bump python-warlock to something newer than openSUSE:12.3, and I think thats not a good idea as we basically destroy all testing against openSUSE:12.3. stopping to integrate -master for python-glanceclient is avoiding this problem, but then we don't get the client fixes anymore :-) Sigh.. I'm leaning towards changing the python*client packages to not track master anymore. any comments? Thanks, Dirk -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-cloud+owner(a)opensuse.org

2 2

[opensuse-cloud] Re: [opensuse-arm] OpenStack/ARM status
by Bernhard M. Wiedemann 12 Apr '13

12 Apr '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/11/2013 10:55 AM, Bernhard M. Wiedemann wrote: > Hi, > > I have been working towards getting OpenStack/Folsom to work on > openSUSE-12.3/ARM. First, to get it to boot a VM with LXC on x86, I > had to workaround > https://bugzilla.novell.com/show_bug.cgi?id=814680 but when doing > this on my pandaboard, it ran into another problem, claiming > "internal error cannot create rule since ebtables tool is > missing." even though, the ebtables tool was there, but when > running libvirtd --listen in the foreground, it printed a better > hint: Failure to execute command '$EBT -t nat -L' : 'FATAL: Module > ebtables not found. > > coming from # CONFIG_BRIDGE_NF_EBTABLES is not set With a recompiled kernel with ebtables-support (thanks to Dirk, it should be in the OBS ARM kernels now) I got it working! And this mail shall document how it was done: I used my PandaBoard with a 32GB SD-card (very slow, so USB-HDD is recommended) To do the setup I cloned https://github.com/SUSE-Cloud/automation and ran cloudsource=openstackfolsom bash -x automation/scripts/jenkins/qa_openstack.sh This will add the right repos and try to pull in all packages, but it errors with the cloud-compute pattern, because that one requires kvm and we don't have such a package in the 12.3 armv7l repos. So I hit Ctrl-C when I saw it, then did zypper install patterns-OpenStack-compute-node and told it to ignore kvm and install everything else anyway. Then I restarted the qa_openstack.sh call and it went through all the other downloading and setup of the OpenStack cloud on the pandaboard. In the end it imported a Debian image, which of course can not boot, because it is for i486. So I did . /etc/bash.bashrc.local to get the OpenStack environment vars needed to manage the cloud glance image-list showed the bad debian image and glance image-delete IMAGEID dropped it. LXC needs different images (a plain rootfs image) than most other methods of virtualization supported by OpenStack which need a disk image with partition table and bootloader. So I used what I had - and that was the pandaboard image. Using dd to copy out the root partition into a separate file, but I suppose you could use http://download.opensuse.org/ports/armv7hl/distribution/12.3/images/openSUS… as well. Be sure to rmdir /selinux in the image to avoid bug 814680. I imported that image into the glance image-store with glance image-create --name=arm --is-public=True \ --property vm_mode=hvm --disk-format=raw \ --container-format=bare < rootfs.img and finally to boot this new image nova boot --image arm --flavor 1 --key_name testkey armvm you can watch it work with tail -f /var/log/nova/compute.log but as the smallest VM type still wants to reserve 512 MB this can be a bit close. Unfortunately there are no APIs to change flavor/sizes - only delete and add. The easier, but hackish way is to change it in the DB directly: su - postgres -c "psql -d nova" \d shows tables in the DB and select * from instance_types; shows the content of the table needed for this change. UPDATE instance_types SET memory_mb=256 WHERE id=1; finally halves the memory requirement. So we can delete the old VM with nova delete armvm and repeat the nova boot line from above. nova list should then show the state changing from BUILDING to Active/Running together with the VM's IP (that is not reachable from outside in this simple setup). When everything worked, ping to the VM's IP address should work and ssh root@VMIP should allow you to log in However, in my case, sshd did not start in the VM for a long time (did I mention that the SD-card was veeeery slow?), so I took an alternative entrance that is not available to all cloud users: virsh --connect lxc:/// list virsh --connect lxc:/// console instance-00000005 (press Ctrl-] to exit console) but that would not let me log in as root, before adding pts/0 to /var/lib/nova/instances/instance-00000005/rootfs/etc/securetty in the end, my VMs processes could be seen from the outside # pstree | grep -A7 lxc |-libvirt_lxc---systemd-+-cron | |-dbus-daemon | |-dhcpcd | |-login---bash | |-rsyslogd---4*[{rsyslogd}] | |-sshd | |-systemd-journal | `-systemd-logind and ssh'ing to it worked just fine as well. When you look at http://download.opensuse.org/repositories/Cloud:/OpenStack:/Folsom/openSUSE… you might wonder how that can work without building for ARM. However, all of OpenStack is written in python, packaged as noarch and our (SUSE's) Cloud team pushed all missing dependencies into openSUSE-Factory before it became 12.3. So this is how you can have a lot of fun playing with Clouds Ciao Bernhard M. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFnwYYACgkQSTYLOx37oWRzLACdEA0wNHNdBJt/serAKFKfP54l /KoAnixLn2DJrJhgAOvQlwvVdkpbyidl =jo1w -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-cloud+owner(a)opensuse.org

3 2

[opensuse-cloud] Fwd: Cloning images
by Tony Su 08 Apr '13

08 Apr '13

---------- Forwarded message ---------- From: Tony Su <tonysu(a)su-networking.com> Date: Fri, Apr 5, 2013 at 11:26 AM Subject: Cloning images To: opensuse-cloud(a)opensuse.org At the moment am exploring image management, specifically cloning from existing images. By default, it looks like openstack supports libvirt and through tools like vm-install and virt-manager, it's likely that openstack is just building on libvirt functionality (please correct me if I'm incorrect). Am frustrated by limitations and implementation with vm-install, so have been looking around at other tools, particularly any that integrate with openstack. Came across libguestfs, specifically it's tool virt-sysprep (shades of Windows terminology!) http://libguestfs.org/ http://freecode.com/projects/libguestfs http://libguestfs.org/virt-sysprep.1.html After skimming the code, it looks like it heavily leans on debootstrap and febootstrap, which of course are tools with little relevance to openSUSE (and SUSE). debootstrap is available as a community import, and febootstrap is not available at all. libguestfs lists itself as "projects using libguestfs today" at the end of the first section on its website homepage, but unsurprisingly none of its components can be found on an openSUSE install. Am wondering if there are alternative tools I should be looking at? For the moment, I'm considering simply creating a script that does typical cloning modifications. TIA, Tony -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-cloud+owner(a)opensuse.org

3 2

[opensuse-cloud] Missing Permissions in Cloud:OpenStack:Grizzly:Staging
by Christian Berendt 04 Apr '13

04 Apr '13

I want to fix some issues in openstack-ceilometer and want to add the missing package python-ceilometerclient in Cloud:OpenStack:Grizzly:Staging. I think python-ceilometerclient is also missing in C:O:M. At the moment I don't have permission to commit to Cloud:OpenStack:Grizzly:Staging. Please grant me the needed permissions. "no permission to create a package in project 'Cloud:OpenStack:Grizzly:Staging'" Christian. -- Christian Berendt Cloud Computing Solution Architect Tel.: +49-171-5542175 Mail: berendt(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-cloud+owner(a)opensuse.org

1 0