[opensuse-cloud] New testing project
As previously discussed I have created a project Virtualization:Cloud:OpenStack:Testing to allow us to track the upstream development code of OpenStack. Current maintainers: Chris Thiel Bernhard Wiedemann Gregory Haskins Patrick Mullaney Robert Schweikert If you think you need to be on the maintainer list please speak up and start to help. 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
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? Best Christoph -- SUSE LINUX Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-cloud+help@opensuse.org
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
On Fri, Jun 17, 2011 at 04:49:04PM -0400, Robert Schweikert wrote:
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 -
Thanks a lot for taking care of this!
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 ?
I would prefer only pushing completed releases to Virtualization:Cloud:OpenStack. That way we ensure to always being able to tell which release is currently in 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.
I currently only see one build failure on openSUSE Factory (i586) which is also present in our Cactus build. (It's due to a Segmentation fault in sphinx-build.) Best Christoph -- SUSE LINUX Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-cloud+help@opensuse.org
On 06/20/2011 04:39 AM, Christoph Thiel wrote:
On Fri, Jun 17, 2011 at 04:49:04PM -0400, Robert Schweikert wrote:
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 -
Thanks a lot for taking care of this!
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 ?
I would prefer only pushing completed releases to Virtualization:Cloud:OpenStack. That way we ensure to always being able to tell which release is currently in Virtualization:Cloud:OpenStack.
Works for me. From https://launchpad.net/swift it is not obvious to me that any particular version is related to Cactus. It appears that 1.4.1 is related to the Diabolo release but everything else appears to be somewhat independent. Unfortunately I could not find a 1.4.1 tarball. 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
On Mon, Jun 20, 2011 at 10:45:19AM -0400, Robert Schweikert wrote:
On 06/20/2011 04:39 AM, Christoph Thiel wrote:
On Fri, Jun 17, 2011 at 04:49:04PM -0400, Robert Schweikert wrote:
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 -
Thanks a lot for taking care of this!
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 ?
I would prefer only pushing completed releases to Virtualization:Cloud:OpenStack. That way we ensure to always being able to tell which release is currently in Virtualization:Cloud:OpenStack.
Works for me.
From https://launchpad.net/swift it is not obvious to me that any particular version is related to Cactus. It appears that 1.4.1 is related to the Diabolo release but everything else appears to be somewhat independent. Unfortunately I could not find a 1.4.1 tarball.
http://openstack.org/projects/storage/ links to http://openstack.org/projects/storage/latest-release/, which redirects http://launchpad.net/swift/1.3/1.3.0/+download/swift-1.3.0.tar.gz :) Best Christoph -- SUSE LINUX Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-cloud+help@opensuse.org
Hey Christoph, Just wanted to give you a heads up. Apparently the packages in the stable and testing under Virtualization:Cloud:Openstack are identical. Apparently it looks like Builds haven't taken place in 6 weeks. I did get the serivces running, however I cannot use the versions with my hyperv compute nodes. They version of openstack-compute requires newer software on the controller etc. So in the interium I'm going to have to use the B4 systems packages again, until we can fix our channels. I would perfer to use our own if possible. Any ideas? p -- Peter Pouliot, CISSP Microsoft SUSE Joint Interoperability Lab ppouliot@suse.com Office: 857.453.6436 Cell: 781.953.8917 SUSE, Attachmate Group, Inc. SUSE: Supporting Linux since 1992. www.suse.com --- SuSE Linux Enterprise -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-cloud+help@opensuse.org
Hi Peter, On Wed, Aug 03, 2011 at 03:47:47PM -0400, Peter J. Pouliot wrote:
Just wanted to give you a heads up. Apparently the packages in the stable and testing under Virtualization:Cloud:Openstack are identical. Apparently it looks like Builds haven't taken place in 6 weeks.
I did get the serivces running, however I cannot use the versions with my hyperv compute nodes. They version of openstack-compute requires newer software on the controller etc. So in the interium I'm going to have to use the B4 systems packages again, until we can fix our channels. I would perfer to use our own if possible. Any ideas?
What exactly is missing? Are you saying openstack-compute on hyperv needs diablo testing builds and doesn't work with the current cactus release, which is what we are packaging in Virtualization:Cloud:Openstack? Best Christoph -- SUSE LINUX Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-cloud+help@opensuse.org
On 08/03/2011 03:47 PM, Peter J. Pouliot wrote:
Hey Christoph,
Just wanted to give you a heads up. Apparently the packages in the stable and testing under Virtualization:Cloud:Openstack are identical.
That would be a very strange occurrence as these are built from different sources. Testing uses 2011.3-d1 source tarballs and the non testing project uses 2011.2 source tarballs. While there may be newer dev releases available at this point, Testing and non testing are definitely different. Note, that in :Testing we are only building the openstack packages, i.e. openstack-glance, openstack-nova, and openstack-swift. If you need something newer on the dependent packages side we can certainly add that to the testing project as well. If you need something newer than 2011.3-d1 that can be arranged as well.
Apparently it looks like Builds haven't taken place in 6 weeks.
I did get the serivces running, however I cannot use the versions with my hyperv compute nodes. They version of openstack-compute requires newer software on the controller etc. So in the interium I'm going to have to use the B4 systems packages again, until we can fix our channels.
Fell free to be more specific than "I am going to use this other stuff". It is just as painful for others to compare everything in two projects as it is for you. There's, to the best of my knowledge, no magic wand that tells the differences. If you can be more specific on what "newer" means I am certain :Testing can be updated. Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjschwei@suse.com rschweik@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
participants (4)
-
Christoph Thiel -
Peter J. Pouliot -
Robert Schweikert -
Robert Schweikert