[opensuse-cloud] Ceph in C:O:M?
Hello. Open vSwich is included in C:O:M and C:O:G. Does it makes sense to also provide Ceph inside the OpenStack projects? Christian. -- Christian Berendt Cloud Computing Solution Architect Mail: berendt@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@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
I for one would be very interested in this, just to experiment with. Have been following Ceph for a couple years now mainly as a "future technology" with important potential. If someone who is skilled in Ceph was willing to maintain, I'm sure it would greatly increase the visibility and potential adoption. Tony On Mon, Jul 15, 2013 at 10:01 AM, Christian Berendt <berendt@b1-systems.de> wrote:
Hello.
Open vSwich is included in C:O:M and C:O:G. Does it makes sense to also provide Ceph inside the OpenStack projects?
Christian.
-- Christian Berendt Cloud Computing Solution Architect Mail: berendt@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@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
Hi,
Open vSwich is included in C:O:M and C:O:G. Does it makes sense to also provide Ceph inside the OpenStack projects?
is there something wrong with the ceph in the filesystems project (other than that it doesn't build)? Tia, Dirk -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
On 07/16/2013 10:51 AM, Dirk Müller wrote:
is there something wrong with the ceph in the filesystems project (other than that it doesn't build)?
Why is openvswitch included? It's available in network and also not part of OpenStack. I think it would be nice to have tested versions of ceph and openvswitch in the release repositories (like C:O:G) and to also have workable versions in C:O:M. Christian. -- Christian Berendt Cloud Computing Solution Architect Mail: berendt@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@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
Hi Christian,
Why is openvswitch included?
Because we need it to resolve package dependencies (Neutron-vswitch subpackage requires it), and we would like to have package repositories that are self-contained and where all packages in it can be installed. We have a jenkins job that tests this: http://ci.opensuse.org/view/OpenStack/job/openstack-repocheck/ If there is a cinder volume plugin (for example) that requires ceph and we have it packaged, I agree that we should add it to the repo and fix up requires. If not, then I think it is more agile to have it separate from OpenStack, because you can decide to use the latest and greatest Ceph with the stable OpenStack or you can decide to use the stable Ceph with the latest and greatest OpenStack.
I think it would be nice to have tested versions of ceph and openvswitch in the release repositories (like C:O:G) and to also have workable versions in C:O:M.
I have no strong opinion about this, although I more freedom of choice better than limited freedom (see above). Greetings, Dirk -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
On 07/16/2013 11:07 AM, Dirk Müller wrote:
Hi Christian,
Why is openvswitch included?
Because we need it to resolve package dependencies (Neutron-vswitch subpackage requires it), and we would like to have package repositories that are self-contained and where all packages in it can be installed. We have a jenkins job that tests this:
http://ci.opensuse.org/view/OpenStack/job/openstack-repocheck/
And why is the check for SLES11 SP3 in a good state (C:O:G and C:O:M) although the openvswitch package is not usable?
If there is a cinder volume plugin (for example) that requires ceph and we have it packaged, I agree that we should add it to the repo and fix up requires. If not, then I think it is more agile to have it separate from OpenStack, because you can decide to use the latest and greatest Ceph with the stable OpenStack or you can decide to use the stable Ceph with the latest and greatest OpenStack.
The volume driver for Rados Block Devices is included in the Cinder packages and there is at least on call to the ceph CLI in _get_mon_addrs().
I have no strong opinion about this, although I more freedom of choice better than limited freedom (see above).
I'm not sure how we should test (for example) C:O:G if there is no fixed version of openvswitch and ceph inside. I think we should deliver at least openvswitch and ceph inside C:O:G and C:O:M (and upcoming C:O:H) to have fixed versions. Christian. -- Christian Berendt Cloud Computing Solution Architect Mail: berendt@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@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
Hi Christian,
And why is the check for SLES11 SP3 in a good state (C:O:G and C:O:M) although the openvswitch package is not usable?
What makes you think that it is not really usable? Just because somebody checked in a broken version from some git branch that doesn't even build doesn't make the old, tested and working binaries go away. The old binaries were still there and are working fine (are even tested). Thats what the test is checking for (if the latest published package binaries are dependency wise installable), and it succeeded.
If there is a cinder volume plugin (for example) that requires ceph
The volume driver for Rados Block Devices is included in the Cinder packages and there is at least on call to the ceph CLI in _get_mon_addrs().
Isn't that the one that requires a Rados enabled libvirt, which we don't have yet ? Or am I mixing it up?
I'm not sure how we should test (for example) C:O:G if there is no fixed version of openvswitch and ceph inside.
First of all, the openvswitch version in C:O:G is working fine. About ceph I don't know the current state of affairs, I just asked the mere question if there is something wrong with the ceph version in "filesystems". Thats all :-) Greetings, Dirk -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
On 07/16/2013 11:24 AM, Dirk Müller wrote:
What makes you think that it is not really usable? Just because somebody checked in a broken version from some git branch that doesn't even build doesn't make the old, tested and working binaries go away. The old binaries were still there and are working fine (are even tested). Thats what the test is checking for (if the latest published package binaries are dependency wise installable), and it succeeded.
Because I always forget that the latest RPM packages are still in the repositories when the latest build failed ;)
Isn't that the one that requires a Rados enabled libvirt, which we don't have yet ? Or am I mixing it up?
Not sure at the moment. Are there any details about the progress with libvirt? Christian. -- Christian Berendt Cloud Computing Solution Architect Mail: berendt@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@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
Christian Berendt wrote:
On 07/16/2013 11:24 AM, Dirk Müller wrote:
Isn't that the one that requires a Rados enabled libvirt, which we don't have yet ? Or am I mixing it up?
Not sure at the moment. Are there any details about the progress with libvirt?
Support is in libvirt, it just needs to be enabled. But it needs to be enabled in qemu first. Jim -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
participants (4)
-
Christian Berendt -
Dirk Müller -
Jim Fehlig -
Tony Su