[opensuse-cloud] Development process still valid?
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@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
Hi André, On Monday, July 08, 2013 09:40:25 AM André Nähring wrote:
is the development process listed here:
https://en.opensuse.org/OpenStack_and_Crowbar_development_process
still valid?
Yes, it is still valid.
Anyhow I just updated the diagram to a more clearer version.
Ciao,
Daniel
--
J. Daniel Schmidt
On 07/08/2013 06:37 PM, J. Daniel Schmidt wrote:
Hi André,
On Monday, July 08, 2013 09:40:25 AM André Nähring wrote:
is the development process listed here:
https://en.opensuse.org/OpenStack_and_Crowbar_development_process
still valid?
Yes, it is still valid. Anyhow I just updated the diagram to a more clearer version.
Daniel, are all the Jenkins jobs as documnted setup and publically visible as well? Andreas -- Andreas Jaeger aj@{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@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
On Monday, July 08, 2013 06:52:02 PM Andreas Jaeger wrote:
Daniel, are all the Jenkins jobs as documnted setup and publically visible as well?
All jobs are archived in the automation repo at:
https://github.com/SUSE-Cloud/automation/tree/master/scripts/jenkins
See the subfolders ci.opensuse.org (public Jenkins) and river.suse.de
(internal Jenkins).
So, all job configurations (public and internal) and the tools needed to set
them up are publically available.
However, only our public Jenkins instance on ci.opensuse.org is publically
visible. The jobs on our internal Jenkins instance on river.suse.de are not
publically visible (it's an internal instance relying on access to other SUSE-
internal systems).
Ciao,
Daniel
--
J. Daniel Schmidt
Hi,
On Mon, 08 Jul 2013 19:09:16 +0200
"J. Daniel Schmidt"
On Monday, July 08, 2013 06:52:02 PM Andreas Jaeger wrote:
Daniel, are all the Jenkins jobs as documnted setup and publically visible as well?
All jobs are archived in the automation repo at: https://github.com/SUSE-Cloud/automation/tree/master/scripts/jenkins
See the subfolders ci.opensuse.org (public Jenkins) and river.suse.de (internal Jenkins).
So, all job configurations (public and internal) and the tools needed to set them up are publically available.
However, only our public Jenkins instance on ci.opensuse.org is publically visible. The jobs on our internal Jenkins instance on river.suse.de are not publically visible (it's an internal instance relying on access to other SUSE- internal systems).
functional tests are started in "cleanvm"? I refer to the PKI/SSL problem in keystone. I think, this could have been discovered with correct tests. If these tests are run in cleanvm, can you extend that to the C:O:Master? Greetings, André -- André Naehring Linux Consultant & Trainer Mail: naehring@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
On Friday, July 12, 2013 10:22:42 AM André Nähring wrote:
functional tests are started in "cleanvm"?
I refer to the PKI/SSL problem in keystone. I think, this could have been discovered with correct tests. If these tests are run in cleanvm, can you extend that to the C:O:Master?
We have different jenkins jobs that test different things. The cleanvm job is
basically to quickly test if there is one way to get a cloud with one guest VM
up an running.
The tool that can test more use cases and aspects of the cloud is called
"mkcloud". The behaviour can be changed via parameters. It can also test an
SSL setup. Unfortunately mkcloud (still) relies on access to internal systems.
Extending tests to the master branch is also a question of computing
ressources. If we can, it surely makes sense to always track C:O:Master with
all tests and various setups. This is a long-term goal.
Ciao,
Daniel
--
J. Daniel Schmidt
Hi Andre,
functional tests are started in "cleanvm"?
not really, it is more the subset of the devstack exercises. We're basically testing if glance, cinder, keystone, neutron and nova come up and are able to start one VM. Running them on Master currently doesn't make a lot of sense, since essentially everything is broken due to the Quantum/Neutron rename. Currently Neutron also aborts in an exception right on the start, so its not a lot of fun to look at the cleanvm job. I've enabled it for master though.
I refer to the PKI/SSL problem in keystone. I think, this could have been discovered with correct tests. If these tests are run in cleanvm, can you extend that to the C:O:Master?
It wouldn't have found the keystone problem, since that only happens with ancient openssl versions (well, SLE). the cleanvm test is currently running on the one distro that can do all of folsom, grizzly and havana: 12.2. I agree that we should eventually extend it to more distros, especially to Factory since that one is important for the next openSUSE version (where we include the packages from Master). Greetings, Dirk -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
Hi,
We have different jenkins jobs that test different things. The cleanvm job is basically to quickly test if there is one way to get a cloud with one guest VM up an running.
It is also testing a completely different code path. cleanvm is testing openstack-quickstart + our packages, while mkcloud is testing our crowbar based deployment.
The tool that can test more use cases and aspects of the cloud is called "mkcloud".
I'd say "different" not "more" ;-) Given that upstream gating is moving now to a HA enabled gating test, it makes sense to extend our cleanvm test to do that as well. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
participants (4)
-
Andreas Jaeger -
André Nähring -
Dirk Müller -
J. Daniel Schmidt