On 06/17/2011 10:09 AM, Christoph Thiel wrote:
On Fri, Jun 17, 2011 at 09:43:08AM -0400, Robert Schweikert wrote:
As previously discussed I have created a project Virtualization:Cloud:OpenStack:Testing to allow us to track the upstream development code of OpenStack.
Thanks for setting this up, Robert! Let's build against the Virtualization:Cloud:OpenStack repo and only link+update the packages to Virtualization:Cloud:OpenStack:Testing that need updating for Diablo.
Does that sound like a plan?
Sounds good to me. - I've linked the two projects - updated swift to 1.4.0 (could not find a tarball for 1.4.1) ~ removed the openstack-swift-python27.patch (applied upstream) ~ new daemon swift-container-stats-logger : followed the pattern of object-server ~ new execs: swift-dispersion-populate and swift-dispersion-report : packaging these in the container for now as a brief look at the code indicated this might be the proper place - updated openstack-nova to 2011.3~d1 ~ repacked to get ~ out of name, using - ~ removed backport patch ~ removed openstack-nova-ajaxterm-path patch file that this patch applied to is gone, did not investigate where the functionality was moved to and if new location needed patch - updated openstack-glance to 2011.3~d1 ~ repacked to get ~ out of name, using - Q: It appears that swift 1.4.0 should work with our current release. Can someone test this and if yes push it into Virtualization:Cloud:OpenStack ? More love and care is needed, but this should give us a start with tracking upstream. I successfully built locally for openSUSE_11.4, lets see if everything at least builds in OBS. Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rschweikert@novell.com rschweikert@ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-cloud+help@opensuse.org