March 2014 - openSUSE Public Cloud - openSUSE Mailing Lists

[opensuse-cloud] /mounts/work_src_done/SLE11-SP3-CLOUD4/openstack-cinder not checked in
by ro 26 Mar '14

26 Mar '14

Script 'mail_helper' called by ro Hi opensuse-cloud(a)opensuse.org, /mounts/work_src_done/SLE11-SP3-CLOUD4/openstack-cinder was not checked in by ro for the following reasons: (submitrequest 34881 on https://build.suse.de) at least this change seems missing: -- fix typo in logrotate - notifempty + notifyempty your dist/autobuild team. -- 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] to fiddle with boot set up or not?
by Robert Schweikert 20 Mar '14

20 Mar '14

Hi, This is basically an opinion poll with respect to cloud-init and WALinuxAgent. The current cloud-init package does not "force" itself into the boot process when installed, i.e. the services needed to make cloud-init do what it is supposed to do are not enabled by default when simply installing the package. The same is true for WALinuxAgent, the Azure initialization code. This is obviously a packaging decision and I am comfortable with this as it is easy enough to enable the services during image building with kiwi or SUSE Studio. However, there appears to exist an expectation by users of Studio that when cloud-init is installed it will magically work when the image that got created gets booted in a cloud environment. While I am perfectly happy with the way WALinuxAgent and cloud-init work, i.e. not forcing themselves into the boot process I also want to be sensitive to user expectations (and of course cut down on potential bug reports.) With this as background the question is simple. What is the general sentiment on this list, should WALinuxAgent and cloud-init insert themselves into the boot process when the package gets installed or not? Reasonable arguments can be made either way IMHO, and I'd like to here as many as possible to make a decision. Thanks for helping out. Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead Public Cloud Architect rjschwei(a)suse.com rschweik(a)ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-cloud+owner(a)opensuse.org

2 5

[opensuse-cloud] Which OpenStack to pick for openSUSE Factory / 13.2
by Dirk Müller 20 Mar '14

20 Mar '14

Hi, currently we have Havana in openSUSE Factory, but things are starting to fall apart. Newer dependencies than what Havana can handle are being slowly merged into Factory, so we need to switch to a newer code base. There are two options: Icehouse and Master. From what I heard roadmap-wise, 13.2 is gonna be released November, so merging Master (aka Juno) into Factory would mean that it would be the newest OpenStack stable release available at that time then available in 13.2. On the other side, Master/Juno is going to be unstable/unusable mostly in Factory context for most of the time, since we don't even CI on Factory so far we would not even notice it. The other option is to submit Icehouse now, and potentially update to Juno later when time is right. For now I would prefer and propose this move. Any thoughts, opinions, suggestions welcome. 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

[opensuse-cloud] Source validator service reenabled for Cloud:OpenStack:Icehouse*
by Dirk Müller 19 Mar '14

19 Mar '14

Hi, I've readded the Source validator service on Cloud:OpenStack:Icehouse* in order to ensure that only packages get checked in there that would pass Factory review (it was already broken in two places in the meantime). Just in case you wonder why there are suddenly more error messages than before during checkin. 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] Fwd: [Bug 1290443] [NEW] /var/log/keystone/keystone.log file doesn't exists!
by Andreas Jaeger 18 Mar '14

18 Mar '14

Can you confirm this packaging change? Is is now really keystone-all.log and keystone-manage.log for Icehouse? Is this a SUSE change or an upstream one? Andreas -------- Original Message -------- Subject: [Bug 1290443] [NEW] /var/log/keystone/keystone.log file doesn't exists! Date: Mon, 10 Mar 2014 16:41:44 -0000 From: Nicolas Guerra <nicoguerrarocha(a)gmail.com> Reply-To: Bug 1290443 <1290443(a)bugs.launchpad.net> To: aj(a)suse.de Public bug reported: # chown -R openstack-keystone:openstack-keystone /etc/keystone/* /var/log/keystone/keystone.log chown: no se puede acceder a «/var/log/keystone/keystone.log»: No existe el fichero o el directorio /var/log/keystone/keystone.log File doesn't exists! in icehouse keystone log file changed. # ls /var/log/keystone/ keystone-all.log keystone-manage.log I'm working with openSuSE 13.1 in VirtualBox vm Sds, Nicolás. ----------------------------------- Built: 2014-03-10T15:46:29 00:00 git SHA: 86e83643427d16aba48b2b06460d58d8a16bc69a URL: http://docs.openstack.org/trunk/install-guide/install/zypper/content/keysto… source File: file:/home/jenkins/workspace/openstack-install-deploy-guide-opensuse/doc/install-guide/section_keystone-install.xml xml:id: keystone-install ** Affects: openstack-manuals Importance: Undecided Status: New ** Description changed: # chown -R openstack-keystone:openstack-keystone /etc/keystone/* /var/log/keystone/keystone.log chown: no se puede acceder a «/var/log/keystone/keystone.log»: No existe el fichero o el directorio /var/log/keystone/keystone.log File doesn't exists! in icehouse keystone log file changed. # ls /var/log/keystone/ keystone-all.log keystone-manage.log + I'm working with openSuSE 13.1 in VirtualBox vm + Sds, Nicolás. ----------------------------------- Built: 2014-03-10T15:46:29 00:00 git SHA: 86e83643427d16aba48b2b06460d58d8a16bc69a URL: http://docs.openstack.org/trunk/install-guide/install/zypper/content/keysto… source File: file:/home/jenkins/workspace/openstack-install-deploy-guide-opensuse/doc/install-guide/section_keystone-install.xml xml:id: keystone-install -- You received this bug notification because you are subscribed to openstack-manuals. Matching subscriptions: os-manuals https://bugs.launchpad.net/bugs/1290443 Title: /var/log/keystone/keystone.log file doesn't exists! Status in OpenStack Manuals: New Bug description: # chown -R openstack-keystone:openstack-keystone /etc/keystone/* /var/log/keystone/keystone.log chown: no se puede acceder a «/var/log/keystone/keystone.log»: No existe el fichero o el directorio /var/log/keystone/keystone.log File doesn't exists! in icehouse keystone log file changed. # ls /var/log/keystone/ keystone-all.log keystone-manage.log I'm working with openSuSE 13.1 in VirtualBox vm Sds, Nicolás. ----------------------------------- Built: 2014-03-10T15:46:29 00:00 git SHA: 86e83643427d16aba48b2b06460d58d8a16bc69a URL: http://docs.openstack.org/trunk/install-guide/install/zypper/content/keysto… source File: file:/home/jenkins/workspace/openstack-install-deploy-guide-opensuse/doc/install-guide/section_keystone-install.xml xml:id: keystone-install To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-manuals/+bug/1290443/+subscriptions -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- 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] Icehouse availability
by Sascha Peilicke 17 Mar '14

17 Mar '14

Hello, with the release of OpenStack Icehouse Beta3, the new project Cloud:OpenStack:Icehouse [0] was branched away from Cloud:OpenStack:Master. Similarly, most of our testing on ci.opensuse.org is set up for Icehouse too [1,2,3]. However, the upstream code-bases are not yet separate, so don't forget to also submit your Cloud:OpenStack:Master fixes to Cloud:OpenStack:Icehouse:Staging. Please provide your feedback and have fun! [0] https://build.opensuse.org/project/show/Cloud:OpenStack:Icehouse [1] https://ci.opensuse.org/view/OpenStack/job/openstack-trackupstream/ [2] https://ci.opensuse.org/view/OpenStack/job/openstack-repocheck/ [3] https://ci.opensuse.org/view/OpenStack/job/openstack-cleanvm -- Mit freundlichen Grüßen, Sascha Peilicke -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-cloud+owner(a)opensuse.org

3 3