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