- openSUSE Public Cloud

Re: [opensuse-cloud] Ceph in C:O:M?
by michael.leu＠mgb.ch 16 Jul '13

16 Jul '13

Hello >> 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? Back in the Folsom days ceph as a volume driver did not work for me on SLES11 SP2 because QEMU from SUSE was compiled without rbd. AFAIK support for rbd can be checked with $ qemu-kvm -device \? | grep rbd HTH Michael PS: thanks for the great work so far!

4 3

[opensuse-cloud] Ceph in C:O:M?
by Christian Berendt 16 Jul '13

16 Jul '13

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(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

4 8

[opensuse-cloud] Open vSwitch not usable
by Christian Berendt 16 Jul '13

16 Jul '13

Hello. The package openvswitch is in state "failed" for SLES11 SP3 for C:O:G and C:O:M. Are there any plans about soling this issue in the near future? Christian. -- Christian Berendt Cloud Computing Solution Architect 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 3

[opensuse-cloud] Development process still valid?
by André Nähring 16 Jul '13

16 Jul '13

Hello, is the development process listed here: https://en.opensuse.org/OpenStack_and_Crowbar_development_process still valid? Greetings, André -- André Naehring Linux Consultant & Trainer Mail: naehring(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

4 7

[opensuse-cloud] SLES11 SP3 as build target, how is it possible?
by Christian Berendt 16 Jul '13

16 Jul '13

Hello. I just created a new subproject on the build service and wanted to add SLES11 SP3 as build target. But I don't see it in my list of repositories. Because SLES11 SP3 is available as build target for C:O:G I wanted to ask you how I can add SLES11 SP3 to my subproject? Christian. -- Christian Berendt Cloud Computing Solution Architect 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] Re: OBS Cloud:OpenStack:Master/openstack-keystone r123 commited
by Dirk Müller 15 Jul '13

15 Jul '13

Hi Andre, > switched default_catalog.templates to projects default which works > > Modified: > openstack-keystone.changes > openstack-keystone.spec could you explain which part is "not working" with the previous default_catalog.template? the upstream one does not have the %SERVICE_HOST marker that are used by the quickstart script in order to expand the catalog properly. Your change breaks that. In addition, this change was not mentioned in the changes file: > @@ -230,8 +231,9 @@ > %config(noreplace) %attr(0640, root, %{groupname}) %{_sysconfdir}/%{component}/logging.conf > %config %{_sysconfdir}/%{component}/keystone-paste.ini > %config %{_sysconfdir}/%{component}/policy.json > +%config %{_sysconfdir}/%{component}/default_catalog.templates > %config(noreplace) %{_sysconfdir}/logrotate.d/%{name} > -%attr(0640, %{username}, %{groupname}) %{_sysconfdir}/%{component}/default_catalog.templates.sample > +%attr(0640, %{username}, %{groupname}) %{_sysconfdir}/%{component}/default_catalog.templates > %{_initddir}/%{name} > %{_sbindir}/rc%{name} > %{_bindir}/keystone-all Also, you forgot to remove the old default_catalog.templates file. If you're not so sure about the change, could you please send a submitrequest? others will review it and comment on it then, and four eyes see usually more than two. Thanks a lot in advance, Greetings, Dirk -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-cloud+owner(a)opensuse.org

2 2

[opensuse-cloud] Error for "keystone-manage db_sync"
by Ryo Murakawa 12 Jul '13

12 Jul '13

Hi, Today I set up Grizzly environment on openSUSE 12.3 following the document bel ow. <http://turing.suse.de/~aj/basic-install/content/basic-install_controller.ht Of course I finished the all packages were updated with yast. On page 6 I entered "keystone-manage db_sync" and got the error below. /usr/lib/python2.7/site-packages/keystone/openstack/common/version.py:21: User Warning: Module argparse was already imported from /usr/lib64/python2.7/argpar se.pyc, but /usr/lib/python2.7/site-packages is being added to sys.path import pkg_resources Traceback (most recent call last): File "/usr/bin/keystone-manage", line 28, in <module> cli.main(argv=sys.argv, config_files=config_files) File "/usr/lib/python2.7/site-packages/keystone/cli.py", line 175, in main CONF.command.cmd_class.main() File "/usr/lib/python2.7/site-packages/keystone/cli.py", line 52, in main driver = importutils.import_object(getattr(CONF, k).driver) File "/usr/lib/python2.7/site-packages/keystone/openstack/common/importutils .py", line 40, in import_object return import_class(import_str)(*args, **kwargs) File "/usr/lib/python2.7/site-packages/keystone/catalog/backends/templated.p y", line 102, in __init__ self._load_templates(template_file) File "/usr/lib/python2.7/site-packages/keystone/catalog/backends/templated.p y", line 107, in _load_templates self.templates = parse_templates(open(template_file)) TypeError: coercing to Unicode: need string or buffer, NoneType found But I checked the table on mysql and found the tables below. mysql> use keystone; Database changed mysql> show tables; +------------------------+ | Tables_in_keystone | +------------------------+ | credential | | domain | | ec2_credential | | endpoint | | group | | group_domain_metadata | | group_project_metadata | | migrate_version | | policy | | project | | role | | service | | token | | trust | | trust_role | | user | | user_domain_metadata | | user_group_membership | | user_project_metadata | +------------------------+ 19 rows in set (0.00 sec) So, what is the reason for this error? I can't find the any workarounds with G oogle. Best Regards. Ryo Murakawa -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-cloud+owner(a)opensuse.org

3 4

[opensuse-cloud] keystone, PKI, openssl
by André Nähring 09 Jul '13

09 Jul '13

Hello, the current default in keystone to sign tokens is to use PKI. With the shipped version of openssl in SLES11 SP3 this won't work, the subcommand "cms" is missing. How do you think this should be handled? Can we get a newer version of openssl in the repository Cloud:OpenStack:Master? Greetings, André -- André Naehring Linux Consultant & Trainer Mail: naehring(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

3 8

[opensuse-cloud] OpenStack Havana submits for openSUSE:Factory
by Dirk Müller 26 Jun '13

26 Jun '13

Hi guys, I'm going to submit OpenStack Havana packages for openSUSE:Factory soon. Given that they're developed off a completely different git branch in parallel to the Grizzly packages, the .changes files are not going to match. Please ignore .changes files errors for python-*client and openstack-*. Thanks a lot in advance for your cooperation in getting this task done. Greetings, Dirk -- 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] Which OpenStack release to include in 13.1
by Dirk Müller 24 Jun '13

24 Jun '13

Hi, I wonder which OpenStack release should be included in openSUSE 13.1. Since we're currently doing most of the testing (and fixing) on Grizzly, it seems to make sense to include Grizzly. However, given that upstream only does n/n-1, Grizzly will run out of maintenance during 13.1 maintenance, which seems to be not such a good idea. The same though is true for Havana as well. Further datapoints: we currently have Django 1.5 in openSUSE 13.1, but the Grizzly Horizon does not work with Django 1.5. There are also a couple of smaller other fixes needed in order to actually make it do something in other modules. I've sent most of those fixes upstream and they're included in Havana already. Backporting that to the Grizzly packages might not always be trivial. Timing wise, Havana will already be relased by the time openSUSE 13.1 goes final. However, the feature freeze period for Havana is a lot shorter than the one for openSUSE, which means that we'll likely have a few late minute things to push to Factory. Currently I lean towards pushing Havana to Factory. Any opinions? Thanks, Dirk -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-cloud+owner(a)opensuse.org

3 2