Re: [foreman-dev] Merge permissions to foreman-packaging
+1 > On 24. Oct 2017, at 07:33, Ondrej Prazak wrote: > > +1 > >> On Mon, Oct 23, 2017 at 9:49 PM, Marek Hulan wrote: >> +1, I remember you've helped me many times. >> >> -- >> Marek >> >> >> >> On October 23, 2017 6:16:48 PM Ewoud Kohl van Wijngaarden >> wrote: >> >>> Hello all, >>> >>> To get more involved in packaging I'd like to request merge access to >>> foreman-packaging. I've already been monitoring PRs and submitted >>> various patches[1][2]. >>> >>> Regards, >>> Ewoud Kohl van Wijngaarden >>> >>> [1]: >>> https://github.com/theforeman/foreman-packaging/commits/rpm/develop?author=ekohl >>> [2]: >>> https://github.com/theforeman/foreman-packaging/commits/deb/develop?author=ekohl >>> >>> -- >>> 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. > > -- > 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] Merge permissions to foreman-packaging
+1 On Mon, Oct 23, 2017 at 9:49 PM, Marek Hulan wrote: > +1, I remember you've helped me many times. > > -- > Marek > > > > On October 23, 2017 6:16:48 PM Ewoud Kohl van Wijngaarden < > ew...@kohlvanwijngaarden.nl> wrote: > > Hello all, >> >> To get more involved in packaging I'd like to request merge access to >> foreman-packaging. I've already been monitoring PRs and submitted >> various patches[1][2]. >> >> Regards, >> Ewoud Kohl van Wijngaarden >> >> [1]: https://github.com/theforeman/foreman-packaging/commits/rpm/ >> develop?author=ekohl >> [2]: https://github.com/theforeman/foreman-packaging/commits/deb/ >> develop?author=ekohl >> >> -- >> 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. > -- 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] Merge permissions to foreman-packaging
+1, I remember you've helped me many times. -- Marek On October 23, 2017 6:16:48 PM Ewoud Kohl van Wijngaarden wrote: Hello all, To get more involved in packaging I'd like to request merge access to foreman-packaging. I've already been monitoring PRs and submitted various patches[1][2]. Regards, Ewoud Kohl van Wijngaarden [1]: https://github.com/theforeman/foreman-packaging/commits/rpm/develop?author=ekohl [2]: https://github.com/theforeman/foreman-packaging/commits/deb/develop?author=ekohl -- 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] Merge permissions to foreman-packaging
Hello all, To get more involved in packaging I'd like to request merge access to foreman-packaging. I've already been monitoring PRs and submitted various patches[1][2]. Regards, Ewoud Kohl van Wijngaarden [1]: https://github.com/theforeman/foreman-packaging/commits/rpm/develop?author=ekohl [2]: https://github.com/theforeman/foreman-packaging/commits/deb/develop?author=ekohl -- 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] Issue with foreman tests
In hindsight, I should caught this on the PR. This scratched an itch in the
back of mind and there was the reminder:
https://github.com/Katello/katello/blob/master/lib/katello/tasks/reset.rake#L52
On Mon, Oct 23, 2017 at 11:59 AM, Ewoud Kohl van Wijngaarden <
ew...@kohlvanwijngaarden.nl> wrote:
> Hello all,
>
> On Friday a PR was merged[1] that was intended to verify seeding worked.
> It turns out that you can't run rake db:migrate db:seed in one command
> which resulted in failing tests. An issue has been created[2] and a
> workaround implemented[3]. Please rerun tests that failed on
>
> NOT NULL constraint failed: architectures.name: INSERT INTO
> "architectures" ("created_at", "updated_at") VALUES (?, ?)
>
> If tests are still broken after that please do report back.
>
> [1]: https://github.com/theforeman/foreman-infra/commit/b275d94f8
> 8e2a60306a13154a7727e638bb4a874
> [2]: https://projects.theforeman.org/issues/21431
> [3]: https://github.com/theforeman/foreman-infra/commit/5099902d7
> 1e79ce7a0b2ec80239d942b92373ecf
>
> --
> 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.
>
--
Eric D. Helms
Red Hat Engineering
--
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] Issue with foreman tests
Hello all,
On Friday a PR was merged[1] that was intended to verify seeding worked.
It turns out that you can't run rake db:migrate db:seed in one command
which resulted in failing tests. An issue has been created[2] and a
workaround implemented[3]. Please rerun tests that failed on
NOT NULL constraint failed: architectures.name: INSERT INTO "architectures"
("created_at", "updated_at") VALUES (?, ?)
If tests are still broken after that please do report back.
[1]:
https://github.com/theforeman/foreman-infra/commit/b275d94f88e2a60306a13154a7727e638bb4a874
[2]: https://projects.theforeman.org/issues/21431
[3]:
https://github.com/theforeman/foreman-infra/commit/5099902d71e79ce7a0b2ec80239d942b92373ecf
--
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] Centralizing tool_belt in theforeman Github
+1 I guess the foreman and katello config files will still live separately (i.e. katello_35.yaml and foreman_16.yaml) but in the same repo. On Mon, Oct 23, 2017 at 5:59 AM, Daniel Lobato Garcia wrote: > On 10/20, Eric D Helms wrote: > > For quite a few releases now, we've been using a little tool named > > tool_belt as a CLI to perform release tasks such as finding cherry picks, > > or building koji configurations. The larger idea of the repository is you > > define a release via a configuration file and perform various release > > actions based on the data within the config file. The original repository > > lives on my personal Github account [1]. At some point, this was forked > to > > theforeman organization and configurations for just Foreman stored in it. > > Meanwhile, in the original repository are configs for Katello releases. > > > > I would like to propose merging the configuration files from theforeman > to > > my original repository, deleting thetheforeman fork and then transferring > > my repository to theforeman to serve as the single shared repository. If > > you have any concerns, objections or questions please raise them here. > > > > If there are no objections, I will perform this next Wednesday or > Thursday. > > > > > > [1] https://github.com/ehelms/tool_belt > > [2] https://github.com/theforeman/tool_belt > > > > -- > > Eric D. Helms > > Red Hat Engineering > > > > -- > > 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. > > +1, I would also like to merge https://github.com/dlobatog/foreman_release > into that repository, making each of the scripts a subcommand of tool_belt > > -- > Daniel Lobato Garcia > > @dLobatog > blog.daniellobato.me > daniellobato.me > > GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30 > Keybase: https://keybase.io/elobato > > -- > 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. > -- Andrew Kofink akof...@redhat.com IRC: akofink Software Engineer Red Hat Satellite -- 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] 1.16 RC2 preparation
puppet-puppet 8.0.3 included a fix for that and RC2 should include that fix. So when I said 'prepare the installer side' was get everything in place so we can do a release. That'll mean tagging and building packages. On Mon, Oct 23, 2017 at 02:29:41PM +0200, Roger Martensson wrote: There seems to be a problem with Puppet 5 with the Foreman-installer. https://github.com/theforeman/puppet-puppet/issues/549 It seems to be merged in master: https://github.com/theforeman/puppet-puppet/pull/548/files Doesn't seem to be installed in 1.16RC. Would love to see installed in 1.16. 2017-10-23 13:55 GMT+02:00 Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl>: On Thu, Oct 12, 2017 at 05:42:19PM +0200, Ewoud Kohl van Wijngaarden wrote: While Daniel is on PTO I'd like to take over the 1.16 RC2 preparation. From the installer side I can handle it, but will need help from a core maintainer and a proxy maintainer to tag releases. We did prepare the installer side, but had too little time to prepare actual releases and test them. We'll work on getting it out soon. -- 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] 1.16 RC2 preparation
There seems to be a problem with Puppet 5 with the Foreman-installer. https://github.com/theforeman/puppet-puppet/issues/549 It seems to be merged in master: https://github.com/theforeman/puppet-puppet/pull/548/files Doesn't seem to be installed in 1.16RC. Would love to see installed in 1.16. 2017-10-23 13:55 GMT+02:00 Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl>: > On Thu, Oct 12, 2017 at 05:42:19PM +0200, Ewoud Kohl van Wijngaarden wrote: > >> While Daniel is on PTO I'd like to take over the 1.16 RC2 preparation. >> From the installer side I can handle it, but will need help from a core >> maintainer and a proxy maintainer to tag releases. >> > > We did prepare the installer side, but had too little time to prepare > actual releases and test them. We'll work on getting it out soon. > > > -- > 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] 1.16 RC2 preparation
On Thu, Oct 12, 2017 at 05:42:19PM +0200, Ewoud Kohl van Wijngaarden wrote: While Daniel is on PTO I'd like to take over the 1.16 RC2 preparation. From the installer side I can handle it, but will need help from a core maintainer and a proxy maintainer to tag releases. We did prepare the installer side, but had too little time to prepare actual releases and test them. We'll work on getting it out soon. -- 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] Katello Packaging Migration to Foreman Packaging Plan Proposal
On Mon, Oct 23, 2017 at 5:57 AM, Daniel Lobato Garcia wrote: > On 10/20, Eric D Helms wrote: > > All, > > > > One of the items on the Roadmap I've sent out is centralizing packaging > > into a single repository. The last time I tried this I attempted to go > > whole hog migrating all things all at once. In order to make this more > > approachable, and to encourage reviews, I would like to follow the > > following plan in this rough order for nightlies only: > > > > 1) Move comps to foreman-packaging and update mash scripts > > 2) copy releasers and tito.props to foreman-packaging for katello > > repositories > > 3) Move packages 1 by 1 to foreman-packaging starting leaving nightly > RPMs > > (rubygem-katello, hammer_cli_katello, and katello-installer) for last. > This > > will involve a PR to foreman-packaging and PR to katello-packaging adding > > to the former and removing from the latter. > > 4) Update katello-packaging README to indicate deperecation > > > > I am sending this plan along to gather feedback, find holes in the plan > and > > to get approval/disapproval from the community in taking this step. > > > > My plan would be to begin this migration towards the end of next week. > > I think it sounds great, ping me when you submit these PRs if you want > someone > to take a look. > > Would koji be affected by this? For example, new katello packages in the > foreman-packaging repository would need to be in foreman tags or still the > katello tags? If the latter, any reason why it would not make sense to > change that > to treat it like any other plugin? > Koji has no binding to the git repository, as long as the releasers tag target Katello's (for the releasers I plan to bring over) then it will release the package to the standard Katello tags. There are a few forces at play in order to get Katello to be treated like other plugins: 1) Move the git packaging to the same repository 2) Devise a plan that allows any plugin to be individually tested and committed to Koji or pushed to the repositories. 3) Revise Foreman yum repository structure to handle Pulp, Candlepin and Client repositories (per https://groups.google.com/forum/#!searchin/foreman-dev/repos%7Csort:date/foreman-dev/6j0itrYnuJo/poJPo2FFAQAJ ) 4) Solve the bandwidth issue (Greg mentioned they are working on this) There are rough plans in place for everything but #2. And given that today, Katello runs a system level test before pushing this one is imperative for assuring the same level of assurance in the code. > > > > > -- > > Eric D. Helms > > Red Hat Engineering > > > > -- > > 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. > > -- > Daniel Lobato Garcia > > @dLobatog > blog.daniellobato.me > daniellobato.me > > GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30 > Keybase: https://keybase.io/elobato > > -- > 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. > -- Eric D. Helms Red Hat Engineering -- 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] Centralizing tool_belt in theforeman Github
On 10/20, Eric D Helms wrote: > For quite a few releases now, we've been using a little tool named > tool_belt as a CLI to perform release tasks such as finding cherry picks, > or building koji configurations. The larger idea of the repository is you > define a release via a configuration file and perform various release > actions based on the data within the config file. The original repository > lives on my personal Github account [1]. At some point, this was forked to > theforeman organization and configurations for just Foreman stored in it. > Meanwhile, in the original repository are configs for Katello releases. > > I would like to propose merging the configuration files from theforeman to > my original repository, deleting thetheforeman fork and then transferring > my repository to theforeman to serve as the single shared repository. If > you have any concerns, objections or questions please raise them here. > > If there are no objections, I will perform this next Wednesday or Thursday. > > > [1] https://github.com/ehelms/tool_belt > [2] https://github.com/theforeman/tool_belt > > -- > Eric D. Helms > Red Hat Engineering > > -- > 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. +1, I would also like to merge https://github.com/dlobatog/foreman_release into that repository, making each of the scripts a subcommand of tool_belt -- Daniel Lobato Garcia @dLobatog blog.daniellobato.me daniellobato.me GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30 Keybase: https://keybase.io/elobato -- 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. signature.asc Description: PGP signature
Re: [foreman-dev] Katello Packaging Migration to Foreman Packaging Plan Proposal
On 10/20, Eric D Helms wrote: > All, > > One of the items on the Roadmap I've sent out is centralizing packaging > into a single repository. The last time I tried this I attempted to go > whole hog migrating all things all at once. In order to make this more > approachable, and to encourage reviews, I would like to follow the > following plan in this rough order for nightlies only: > > 1) Move comps to foreman-packaging and update mash scripts > 2) copy releasers and tito.props to foreman-packaging for katello > repositories > 3) Move packages 1 by 1 to foreman-packaging starting leaving nightly RPMs > (rubygem-katello, hammer_cli_katello, and katello-installer) for last. This > will involve a PR to foreman-packaging and PR to katello-packaging adding > to the former and removing from the latter. > 4) Update katello-packaging README to indicate deperecation > > I am sending this plan along to gather feedback, find holes in the plan and > to get approval/disapproval from the community in taking this step. > > My plan would be to begin this migration towards the end of next week. I think it sounds great, ping me when you submit these PRs if you want someone to take a look. Would koji be affected by this? For example, new katello packages in the foreman-packaging repository would need to be in foreman tags or still the katello tags? If the latter, any reason why it would not make sense to change that to treat it like any other plugin? > > -- > Eric D. Helms > Red Hat Engineering > > -- > 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. -- Daniel Lobato Garcia @dLobatog blog.daniellobato.me daniellobato.me GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30 Keybase: https://keybase.io/elobato -- 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. signature.asc Description: PGP signature
Re: [foreman-dev] Vendorizing or Building RPMs
On Mon, 2017-10-16 at 14:36 +0100, Greg Sutcliffe wrote: > > That said, I've not really been involved with the RPMs, so I'm unsure > if this causes a bigger headache for Yum users than Apt users. I'm > also unsure of the work required to create an SCL, but if it's non- > trivial then I'd be looking to CentOS to collaborate on a Rails SCL > for everyone to use - for just ourselves, then vendoring seems > easier. I spoke to a few people I know about this, and it seems there's not much appetite for making new SCLs. We might be able to attract contributors once it's created, but I think we should assume the effort for creating/maintaining SCLs will fall on us initially. Do we have any conclusions on this thread? It's going to matter for 1.17 which is getting closer by the day. Greg -- 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] Katello Packaging Migration to Foreman Packaging Plan Proposal
On Sun, 2017-10-22 at 21:27 -0400, Eric D Helms wrote: > > Note that this plan says nothing about changing our actual yum > repository structure. That would come later. This is just about > beginning with moving all package management to be centralized in > foreman-packaging git repository. So if I understand right, then all the packages are still hosted on the Katello side for now, and this is just a merging of the source trees? I'm fine with that - I'm still waiting on sorting a CDN for the web node, so until that's done I can't +1 something that adds bandwidth costs, but this isn't it ;) Greg -- IRC / Twitter: @gwmngilfen Diaspora: gwmngil...@joindiaspora.com -- 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] Centralizing tool_belt in theforeman Github
On Fri, 2017-10-20 at 16:59 -0400, Eric D Helms wrote: > > If there are no objections, I will perform this next Wednesday or > Thursday. +1 -- IRC / Twitter: @gwmngilfen Diaspora: gwmngil...@joindiaspora.com -- 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.
