March 2013 - openSUSE Cloud - openSUSE Mailing Lists

[opensuse-cloud] regular updates of tarballs in C:O:M
by Christian Berendt 22 Mar '13

22 Mar '13

Is it possible to update the tarballs in C:O:M more often? I would like to have an automated process to have changes in the upstream faster on our testing environments. I think pushing a new tarball after each commit is overhead. But tarballs should be updated every few hours. Maybe we can discuss this topic next week in the confcall. I'll add it to the agenda. 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

2 1

[opensuse-cloud] Warning message when using nova CLI
by Christian Berendt 22 Mar '13

22 Mar '13

Always I receive the following message when using the nova CLI. /usr/lib64/python2.6/site-packages/Crypto/Util/number.py:57: PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild using libgmp >= 5 to avoid timing attack vulnerability. _warn("Not using mpz_powm_sec. You should rebuild using libgmp >= 5 to avoid timing attack vulnerability.", PowmInsecureWarning) Anyone knows how to fix this issue? 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

2 1

[opensuse-cloud] Files marked as %config(noreplace)
by Sascha Peilicke 19 Mar '13

19 Mar '13

Hi guys, in our OpenStack packaging, we have several files marked as %config(noreplace) but we should discuss when this makes sense and when not. The general pattern in the past seemed to just mark everything as noreplace to (somewhat blindly) please the corresponding rpmlint warning. Recently this changed. In other words, we try to only mark stuff as noreplace where we really expect user's to change files. Good examples are: /etc/nova/nova.conf /etc/logrotate.d/openstack-nova But not necessarilly: /etc/quantum/plugins/bigswitch/restproxy.ini /etc/nova/policy.json /etc/nova/rootwrap.conf /etc/nova/rootwrap.d/api-metadata.filters Primarily rootwrap config is a security thing on which we want to have tight control. Thus these should only be marked as %config so that the user is able to shot himself in the foot. But in the end we still have the bigger duct-tape to fix things up. Of course the exact list on what to mark how is debatable, so here is a list of all files currently marked as %config(noreplace): http://paste.opensuse.org/77114742 And one for %config files: http://paste.opensuse.org/48154140 For now I'll fix-up things as I see fit. -- 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

4 3

[opensuse-cloud] regular (weekly) meetings
by Christian Berendt 19 Mar '13

19 Mar '13

I think we should introduce a regular meeting to sync our efforts and to report our progress. Also I think we should clarify and sync our workflows. Looks like there are several views about the usage of C:O:M at the moment. 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

3 2

[opensuse-cloud] novncproxy not working, novnc missing
by Christian Berendt 19 Mar '13

19 Mar '13

openstack-nova-novncproxy is not working at the moment. In our ISV project we packaged the novncproxy in the package novnc and removed openstack-nova-novncproxy in openstack-nova. nova-novncproxy is already included in novnc. I want to add the novnc package to C:O:M and remove the nova-novncproxy from openstack-nova. 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

3 2

Fwd: [opensuse-cloud] moving doc packages into component packages?
by Dirk Müller 19 Mar '13

19 Mar '13

2013/3/14 Christian Berendt <berendt(a)b1-systems.de>: > I'm talking about the files included in the packages on the OBS. > > For example in openstack-ceilometer-doc I have openstack-ceilometer.init, > openstack-ceilometer.logrotate and openstack-ceilometer.spec. Hi Christian, yes, thats normal, this package is only a source link to the package openstack-ceilometer. Never look or modify the -doc package itself, simply only care about the $component-doc.spec in the $component dir. To make it more obvious, I recommend something like "osc up -u *-doc" in your checkout directory. (yes it would be nice if the build service would do that automatically, but it is not so clever). The package container in OBS named $component-doc only exists to make the -doc.spec file in $component package actually being built. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-cloud+owner(a)opensuse.org

3 3

[opensuse-cloud] Usage of not-yet-reviewed patches in C:O:M?
by Christian Berendt 18 Mar '13

18 Mar '13

I just stumbled because of the patch "0001-Use-exec_dirs-for-rootwrap-commands.patch" in the package openstack-quantum (added by Dirk). The patch didn't work, because it was an deprecated version of the patch, and quantum-rootwrap refused to work. Result: all Quantum services refused to work. At the moment I don't like it that there are patches in C:O:M, changing something in the sources of an OpenStack service, without an open review quest in the upstream. And even if there is an open review request: I think that it's not necessary to manually add patches to C:O:M changing something essential. We should simply upstream all our changes and after a successful review we automatically have it in the master tarball. Normally the review process in the upstream is very fast. Sure, if we have to change something very SUSE specific we can use a patch. But we should discuss the usage of patches inside C:O:M before adding them to the packages. And we should never change essential functionality of components. 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

[opensuse-cloud] Changing from master-tarballs to milestone-tarballs in C:O:M?
by Christian Berendt 18 Mar '13

18 Mar '13

Why we changed from the master tarballs to the milestone tarballs in C:O:M? I thought C:O:M is always the master tarball? We should use the milestone tarballs in C:O:G, but not in C:O:M! Also I would like to have a discussion first on this mailinglist before changing the sources in the SPECs. And looks like we now use the milestone tarball in openstack-quantum, but in the component packages the master tarballs? 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

2 1

[opensuse-cloud] Installing OpenStack on OpenSuSE 12.3
by Ashutosh Narayan 18 Mar '13

18 Mar '13

Hi folks, I have been playing around with OpenStack for quite some time and was trying to install it on CentOS 6.3. For various reasons I couldn't achieve success over it. So thought of trying it on a different distro. OpenSuse 12.3 is out and I thought it would be a good idea to install OpenStack on it. Is there any documentation that I can follow to install it ? Support is appreciated. Thank you, -- Ashutosh Narayan http://ashutoshn.wordpress.com/ -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-cloud+owner(a)opensuse.org

3 9

[opensuse-cloud] Static plugin configuration in Quantum server startscript
by Christian Berendt 18 Mar '13

18 Mar '13

At the moment the plugin configuration is static: QUANTUM_PLUGIN_CONF="--config-file=/etc/quantum/plugins/linuxbridge/linuxbridge_conf.ini" I think we should introduce a configuration file in /etc/sysconfig to change the used plugin configuration. 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