AW: [foreman-dev] Proposal: Foreman 1.18 = 2.0
Totally agree with that. Vert nav + Rails 5.1 + Drop support of APIv1 would be the best reason for 2.0 for sure -Ursprüngliche Nachricht- > Von:Ondrej Prazak > Gesendet: Donnerstag 30 November 2017 09:08 > An: foreman-dev@googlegroups.com > Betreff: Re: [foreman-dev] Proposal: Foreman 1.18 = 2.0 > > If having 2.0 means just a change in number because y is now just too high to > remember, then it does not matter if we pick 1.17, 1.18 or 1.19. I agree that > bumping the major number signals a significant and possibly breaking changes > to users and should not be done arbitrarily. > If we want 2.0 with some major changes, then is vertical nav + Rails 5.1 > significant enough to have 2.0 instead of 1.17? > > O. > > On Wed, Nov 29, 2017 at 11:54 PM, Bernhard Hopfenmüller > mailto:hopfenmuel...@atix.de>> wrote: > If you are still looking for new ideas for Foreman 2.0: > I dont know whether this is seen by you guys as a major change- but having a > consistent API v2 in Foreman and Katello would be a very nice thing. > We are stumbling across some inconsistencies from time to time with our > foreman/katello Ansible module work. > The issue [1] I am linking here is for Satellite and not Foreman, but > problems like that are in Foreman as well. > E.g the searching works a bit different for Katello and Foreman entities [2] > > Regarding Erics suggestions: > " Pick your own config management (aka dropping Puppet as default within the > application obviously stilled required for the installer)" > I dont think that is boring at all! ;) > > Bernhard > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1264807 > <https://bugzilla.redhat.com/show_bug.cgi?id=1264807> > [2] https://github.com/SatelliteQE/nailgun/issues > <https://github.com/SatelliteQE/nailgun/issues> > --- > ATIX - The Linux & Open Source Company > https://www.atix.de <https://www.atix.de> > > > -Original message- > From: Eric D Helms mailto:ericdhe...@gmail.com>> > Sent: Wednesday 29th November 2017 18:18 > To: foreman-dev <mailto:foreman-dev@googlegroups.com>> > Subject: Re: [foreman-dev] Proposal: Foreman 1.18 = 2.0 > > My two cents are that we shouldnt arbitrarily bump the version. Versions have > and signal meaning to users. Especially when we are talking about the main > line, core project. Fortunately or unfortunately, major version bumps signal > either a major shift or change and/or a marketing opportunity. Further, major > version changes should signal that plugins are also going to have to change > to stay compliant. Id suggest we stick with folks suggestions of finding some > things to entirely deprecate and bump the version and/or adding some major > support components so that 2.0 is a major change. Things Ive head so far: > > * Rails 5.1 and Ruby 2.4 support > * Remove API v1 > * Vertical Nav > > Some further, potentially more boring ideas as part of a "Foreman 2.0, new > stack, new look" release: > > * Pick your own config management (aka dropping Puppet as default within the > application obviously stilled required for the installer) > * Updates to repository structure such as adding a client repository > * Tasks support in Core > > > This, based on comments, also sounds like a good time to visit a versioning > policy so that we adhere to it and give plugins and users some predictability. > > > Eric > > > > On Wed, Nov 29, 2017 at 12:07 PM, Eric D Helms <mailto:ericdhe...@gmail.com>> wrote: > > > On Wed, Nov 29, 2017 at 8:49 AM, Bernhard Suttner <mailto:sutt...@atix.de>> wrote: > I also like the idea of a version 2.0 very much. Personally, I would be very > happy to move bastion from katello to foreman so that its possible to create > modern, angular js components within foreman. One more reason to do this is, > because I think foreman should be the structure, the base "framework" all > other plugins like katello can live in. Just my thoughts... > > This is not going to happen regardless. All net new UI is being created in > React. Bastion is effectively in a critical bug fix state only. All React > work is being done in Foreman core, or plugins directly (e.g. all new React > work in Katello is going into Katello directly). You can consider the use of > Angular within Foreman and Katello dead for all intents and purposes. > > Eric > > Best regards, > Bernhard Suttner > > ATIX - The Linux & Open Source Company > https://www.atix.de <https://www.atix.de> > > -Ursprüngliche Nachricht- > > Von:Lukas Zapletal mailto:l...@redhat.com&g
AW: [foreman-dev] Proposal: Foreman 1.18 = 2.0
I also like the idea of a version 2.0 very much. Personally, I would be very happy to move bastion from katello to foreman so that it's possible to create modern, angular js components within foreman. One more reason to do this is, because I think foreman should be the structure, the base "framework" all other plugins like katello can live in. Just my thoughts... Best regards, Bernhard Suttner ATIX - The Linux & Open Source Company https://www.atix.de -Ursprüngliche Nachricht- > Von:Lukas Zapletal > Gesendet: Mittwoch 29 November 2017 14:18 > An: foreman-dev > Betreff: Re: [foreman-dev] Proposal: Foreman 1.18 = 2.0 > > > Bikeshedding about SemVer aside, I'm good with doing a 2.0 release in > > the near future, but *please* lets use it to deprecate / drop stuff we > > no longer want to maintain. Otherwise there's no real point to it. > > I agree we can take this "opportunity" to drop some deprecated things > like V1 API, but I don't see many other things. We are pretty good in > deprecating things using our "two releases" rule which should be > followed no matter if we bump major version or not. > > Let's not block 2.0 with any feature, I wrote the reasons, if we fit > in some deprecation work why not. But's let's agree on 2.0 timeframe > regardless of any planning. > > -- > Later, > Lukas @lzap Zapletal > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[foreman-dev] Building foreman RPM packages using docker container
Hi, we have been working on, how to build the foreman RPM packages using docker containers and have shared the code in github: https://github.com/ATIX-AG/foreman_docker_build/ Best regards, Bernhard and The ATIX Crew -- ATIX - The Linux & Open Source Company www.atix.de -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] [Event] Foreman Community Demo Items - Thu 01 Jun 3pm [GMT]
Hi, Are you interested in having a demo about the foreman_scc_manager plugin which we have developed at ATIX? Plugin can be found here: https://github.com/ATIX-AG/foreman_scc_manager Short discription: Foreman plugin to sync SUSE Customer Center products and repositories into Katello Best regards Bernhard --- ATIX - The Linux & Open Source Company www.atix.de Von: "greg sutcliffe" An: foreman-dev@googlegroups.com Gesendet: Donnerstag, 25. Mai 2017 16:35:35 Betreff: [foreman-dev] [Event] Foreman Community Demo Items - Thu 01 Jun 3pm [GMT] Hi all Demo time! As always, have a think for items which have been completed since the last demo on 2017-05-11. There is a query that will show you items completed (i.e. marked as closed) since the last demo [2]. Please add demo items following the instructions on the agenda page [3]. If you can't be present but have something to show, add it to the agenda and let me know - I'll be happy to talk about the feature in your absence. Please do leave me enough time to familiarize myself with the content though :) [1] https://www.youtube.com/watch?v=_OrYpestGQc [2] http://tinyurl.com/lhwqdyh [3] http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information Cheers! -- Greg IRC: gwmngilfen -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] Salt forman config
Hi, just to be clear: puppet 4: /etc/puppetlabs/puppet/ssl/client_cert.pem puppet 3: /etc/puppetlabs/puppet/ssl/private_keys/foreman.example.com.pem correct? And the path which I set in puppet4 is the correct one for salt? Best regards, Bernhard Von: "Ewoud Kohl van Wijngaarden" An: foreman-dev@googlegroups.com Gesendet: Montag, 8. Mai 2017 13:55:08 Betreff: Re: [foreman-dev] Salt forman config On Mon, May 08, 2017 at 01:52:35PM +0200, Bernhard Suttner wrote: > Hi, > > I tried to configure salt in forman using: > > https://www.theforeman.org/plugins/foreman_salt/7.0/index.html > > In this documentation, it is specified, that in /etc/salt/foreman.yaml you > need to specify: > > :ssl_ca: /var/lib/puppet/ssl/certs/ca.pem > :ssl_key: /var/lib/puppet/ssl/private_keys/foreman.example.com.pem > :ssl_cert: /var/lib/puppet/ssl/certs/foreman.example.com.pem > > This didn't work and I always got: > [root@salt]# /usr/bin/foreman-node raul-gries.stage.atix > Couldn't retrieve ENC data: Could not send facts to Foreman: SSL_connect > returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify > failed > > Then, I had a look at the code in smart_proxy_salt to find out, for which the > certificates are used. In the documentation it is specified, to configure > that similar to puppet. Therefore I had a look at the node.rb in > /etc/puppetlabs/puppet. node.rb is using foreman.yaml from > /etc/puppetlabs/puppet and for this, there are "similar" ssl certificate > configurations. > > Therefore, I changed the /etc/salt/foreman.yaml to look similar to > /etc/puppetlabs/puppet/foreman.yaml: > > :ssl_ca: "/etc/puppetlabs/puppet/ssl/ssl_ca.pem" > :ssl_cert: "/etc/puppetlabs/puppet/ssl/client_cert.pem" > :ssl_key: "/etc/puppetlabs/puppet/ssl/client_key.pem" > > And finally. Its working. Maybe I did something completely wrong. Or there is > a nice documentation mistake. That sounds like you were using Puppet 3 paths with a Puppet 4 installation. The documentation should at least mention this, but likely default to the Puppet 4 paths and warn about Puppet 3 paths. -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[foreman-dev] Salt forman config
Hi, I tried to configure salt in forman using: https://www.theforeman.org/plugins/foreman_salt/7.0/index.html In this documentation, it is specified, that in /etc/salt/foreman.yaml you need to specify: :ssl_ca: /var/lib/puppet/ssl/certs/ca.pem :ssl_key: /var/lib/puppet/ssl/private_keys/foreman.example.com.pem :ssl_cert: /var/lib/puppet/ssl/certs/foreman.example.com.pem This didn't work and I always got: [root@salt]# /usr/bin/foreman-node raul-gries.stage.atix Couldn't retrieve ENC data: Could not send facts to Foreman: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed Then, I had a look at the code in smart_proxy_salt to find out, for which the certificates are used. In the documentation it is specified, to configure that similar to puppet. Therefore I had a look at the node.rb in /etc/puppetlabs/puppet. node.rb is using foreman.yaml from /etc/puppetlabs/puppet and for this, there are "similar" ssl certificate configurations. Therefore, I changed the /etc/salt/foreman.yaml to look similar to /etc/puppetlabs/puppet/foreman.yaml: :ssl_ca: "/etc/puppetlabs/puppet/ssl/ssl_ca.pem" :ssl_cert: "/etc/puppetlabs/puppet/ssl/client_cert.pem" :ssl_key: "/etc/puppetlabs/puppet/ssl/client_key.pem" And finally. Its working. Maybe I did something completely wrong. Or there is a nice documentation mistake. Please, correct me if I'm wrong. Thank you in advance. Best regards, Bernhard -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[foreman-dev] HTTPS Username / Password authentication in foreman_templates
Hi, is it already possible to use username / password authentication to access the HTTPS-based git repository? If this is not the case, I'm happy that someone provides some information how to do it. I would then have a look on it. Best regards, Bernhard -- ATIX - The Linux & Open Source Company www.atix.de -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] Building foreman from foreman-packaging
Thanks Dominic for your fast response. I have used " mock --configdir=/home/rpmbuild/foreman-packaging/mock/ -r el7-scl --scrub=all" and it's now building foreman! Thank you very much. - Ursprüngliche Mail - Von: "Dominic Cleal" An: foreman-dev@googlegroups.com Gesendet: Freitag, 17. März 2017 10:48:09 Betreff: Re: [foreman-dev] Building foreman from foreman-packaging On 16/03/17 21:42, Bernhard Suttner wrote: > I want to build foreman from foreman-packacking. Therefore, I have cloned the > git repository and switched to branch rpm/1.14. Then, I have executed "git > annex" init and then "./setup_sources.sh foreman". [..] > Which will then install the dependencies with: > /usr/bin/yum-builddep --installroot /var/lib/mock/foreman-scl-7-x86_64/root/ > --releasever 7 > /var/lib/mock/foreman-scl-7-x86_64/root//builddir/build/SRPMS/foreman-1.14.2-1.git.0.1372eff.el7.centos.src.rpm > --setopt=tsflags=nocontexts > > This will fail with the following error message: > Error: No Package found for npm(es6-promise) >= 3.2.1 > Error: No Package found for npm(jquery) < 1.12.0 > Error: No Package found for tfm-rubygem(apipie-rails) < 0.4.0 > Error: No Package found for tfm-rubygem(audited-activerecord) < 5.0 > Error: No Package found for tfm-rubygem(audited-activerecord) >= 4.0 > Error: No Package found for tfm-rubygem(scoped_search) < 4.0 > > > > I guess, I have already found one issue in this git repository as switching > to rpm/1.14 should also change the yum repository in the directory "mock": This would be correct, but I notice all of the packages in the error above are ones that have changed between 1.14 and nightly. It's likely that the yum cache still contains data from the nightly repo (changing the baseurl will not cause cache invalidation). Run "mock --configdir=/home/rpmbuild/foreman-packaging/mock/ -r el7-scl --scrub=all", or remove the mock cache or var directory, then try again. > The point which really make me cracy is, that if I run: > /usr/bin/yum --installroot /var/lib/mock/foreman-scl-7-x86_64/root/ provides > tfm-rubygem\(scoped_search\) > > I will get a result - also for all the other missing packages > (npm(es6-promise), npm(jquery))... How can I turn on more debugging in > mock/tito? mock writes quite detailed logs to its var directory (/var/lib/mock/foreman-scl-7-x86_64). > I spent hours now and also studied the logs of http://ci.theforeman.org/ so > that I can find out how this is usually done - but the build configuration > isn't available for everyone. Is it somehow possible to get the configuration > options for each build target so that I can determine what I'm doing wrong? Foreman's packages are built in Koji (e.g. http://koji.katello.org/koji/taginfo?tagID=397) so the mock configurations in the repository are a close approximation of how Koji's set up. Besides the version number, they ought to be accurate enough as they use the same binary packages for the build. They do vary in that they use the latest CentOS release and updates (while the link above shows the real build tag uses RHEL 7.0) and that Koji has separate build targets for Foreman and for plugins, but that wouldn't make a difference to this build. -- Dominic Cleal domi...@cleal.org -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[foreman-dev] Building foreman from foreman-packaging
Hi, I want to build foreman from foreman-packacking. Therefore, I have cloned the git repository and switched to branch rpm/1.14. Then, I have executed "git annex" init and then "./setup_sources.sh foreman". For building foreman, I switch to the foreman directory and execute: tito build --rpm --test --verbose --builder tito.builder.MockBuilder --arg mock_config_dir=mock/ --arg mock=el7-scl This will start the mock builder: mock --configdir=/home/rpmbuild/foreman-packaging/mock/ -r el7-scl /tmp/tito/foreman-1.14.2-1.git.0.1372eff.el7.centos.src.rpm Which will then install the dependencies with: /usr/bin/yum-builddep --installroot /var/lib/mock/foreman-scl-7-x86_64/root/ --releasever 7 /var/lib/mock/foreman-scl-7-x86_64/root//builddir/build/SRPMS/foreman-1.14.2-1.git.0.1372eff.el7.centos.src.rpm --setopt=tsflags=nocontexts This will fail with the following error message: Error: No Package found for npm(es6-promise) >= 3.2.1 Error: No Package found for npm(jquery) < 1.12.0 Error: No Package found for tfm-rubygem(apipie-rails) < 0.4.0 Error: No Package found for tfm-rubygem(audited-activerecord) < 5.0 Error: No Package found for tfm-rubygem(audited-activerecord) >= 4.0 Error: No Package found for tfm-rubygem(scoped_search) < 4.0 I guess, I have already found one issue in this git repository as switching to rpm/1.14 should also change the yum repository in the directory "mock": --- el7-scl.cfg.orig2017-03-14 13:43:52.74000 +0100 +++ el7-scl.cfg 2017-03-15 12:25:54.99400 +0100 @@ -45,17 +45,21 @@ [sclo-rh] name=sclo-rh +enabled=1 baseurl=http://mirror.centos.org/centos/7/sclo/x86_64/rh/ [sclo-sclo] name=sclo-sclo +enabled=1 baseurl=http://mirror.centos.org/centos/7/sclo/x86_64/sclo/ [foreman] name=foreman -baseurl=http://yum.theforeman.org/nightly/el7/x86_64/ +enabled=1 +baseurl=http://yum.theforeman.org/releases/1.14/el7/x86_64/ [foreman-plugins] name=foreman-plugins -baseurl=http://yum.theforeman.org/plugins/nightly/el7/x86_64/ +enabled=1 +baseurl=http://yum.theforeman.org/plugins/1.14/el7/x86_64/ Do you agree? Unfortunately, it does still fail with the error message (see above). I'm using centos7 - can this be the issue? Which system should I use? The point which really make me cracy is, that if I run: /usr/bin/yum --installroot /var/lib/mock/foreman-scl-7-x86_64/root/ provides tfm-rubygem\(scoped_search\) I will get a result - also for all the other missing packages (npm(es6-promise), npm(jquery))... How can I turn on more debugging in mock/tito? I spent hours now and also studied the logs of http://ci.theforeman.org/ so that I can find out how this is usually done - but the build configuration isn't available for everyone. Is it somehow possible to get the configuration options for each build target so that I can determine what I'm doing wrong? Thank you in advance. Best regards, Bernhard -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
