Re: [foreman-dev] New community-templates structure
On Fri, Nov 25, 2016 at 3:40 PM, Marek Hulán wrote: > Please share your ideas for other structuring or which of schema mentioned > above you find better. The level of nesting does not matter from technical > point of view but I think 2 or 3 directories is the limit. > I also like the option with provisioning templates being separated by template kind. It is much easier to navigate through. -- 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] encryption/decryption functionality
Hello All, We are planning to use foreman for deployment and we need to answer below question to classify whether we can use it or not : 1) 2) Does it contain any kind of encryption/decryption functionality besides a. Authentication b.Hashing 3) If it contains such an encryption functionality, … - Is it based on a public available algorithm/library or is it a self-developed algorithm - What is the name of the encryption library or algorithm i.Is it symmetric or asymmetric? ii.What is the maximum supported key length? iii.Is it linked dynamically, statically, a standard API call or something different (provided as a result of a different tool, command line interface, …) Any help would be appreciated. Thanks, Aditya -- 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] New community-templates structure
On Fri, Nov 25, 2016 at 3:40 PM, Marek Hulán wrote: > Hello foreman devs, > > As I demonstrated on last community demo [1] templates can be now easily > exported from Foreman. I also mentioned that I'm working [2] on > foreman_templates feature to easily export all templates to a given git repo. > Since the plugin can be used with any git repo, not just the community- > templates [3] one, I'd like to standardize the format of such repository. > > When we export templates from Foreman, we can only use template attributes to > determine the resulting path in the repo. First obvious idea is to name the > template file according to it's name in Foreman. That's probably not enough > since it wold result in one directory mixing all partition tables, > provisioning templates and job templates. So I came up with structure like > $template_type/$name. For better look and feel of what it means, you can see > it in one of my branches [4]. > > Currently we also separate provisioning templates into more directories. I > don't think the rule is well defined today. I think we could separate it per > template kind. Again you can see this demonstrated in another branch at [5]. > It applies only to provisioning templates, other types don't have template > kind attribute. > > Please share your ideas for other structuring or which of schema mentioned > above you find better. The level of nesting does not matter from technical > point of view but I think 2 or 3 directories is the limit. > I like kind + subkind the most. > The ultimate goal of making foreman_templates exporting compatible with > community-templates is making sharing of user changes easy, in fact just a > matter of opening PR from the forked repo. Another nice benefit would be that > future changes in metadata, e.g. adding organizations and locations keys would > be much easier, we'd just reexport all templates from Foreman with updated > export code. > > Since we now have metadata as a part of each template we could also improve > seeding to avoid hard coding the list in seed files [6] > > [1] https://www.youtube.com/watch?v=M0-3x8AUfFQ > [2] https://github.com/theforeman/foreman_templates/pull/36 > [3] https://github.com/theforeman/community-templates > [4] https://github.com/ares/community-templates/tree/develop_kind_only > [5] https://github.com/ares/community-templates/tree/develop_kind_and_subkind > [6] > https://github.com/theforeman/foreman/blob/develop/db/seeds.d/07-provisioning_templates.rb#L21-L94 > > Thanks for all comments > > -- > Marek > > -- > 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] Katello documentation moved to theforeman.org repo
All, The katello.org transition has completed and all documentation for Katello can now be found within theforeman.org. If you have open PRs please re-open them against the new structure as well as any new changes [1]. The katello.org website itself has also been updated to redirect users to the new documentation locations. Eric [1] https://github.com/theforeman/theforeman.org/tree/gh-pages/plugins/katello -- Eric D. Helms Red Hat Engineering Ph.D. Student - North Carolina State University -- 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 documentation moved to theforeman.org repo
Great work everyone. LZ On Tue, Nov 29, 2016 at 4:50 PM, Eric D Helms wrote: > All, > > The katello.org transition has completed and all documentation for > Katello can now be found within theforeman.org. If you have open PRs > please re-open them against the new structure as well as any new changes > [1]. The katello.org website itself has also been updated to redirect > users to the new documentation locations. > > > Eric > > > [1] https://github.com/theforeman/theforeman.org/ > tree/gh-pages/plugins/katello > > -- > Eric D. Helms > Red Hat Engineering > Ph.D. Student - North Carolina State University > > -- > 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. > -- 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.
Re: [foreman-dev] encryption/decryption functionality
AFAIK we are not using any self-develop cryptography, just regular Ruby and Rails algorighms like md5, sha, X509, UNIX crypt, ActiveSupport::MessageEncryptor and stuff like that. If you are going to do security audit, please share your results. Keep in mind that if you found a security bug, use foreman-security@ email for communication (more on this at https://theforeman.org/security.html). LZ On Tue, Nov 29, 2016 at 12:10 PM, 'Aditya Gupta' via foreman-dev < foreman-dev@googlegroups.com> wrote: > Hello All, > > We are planning to use foreman for deployment and we need to answer below > question to classify whether we can use it or not : > > 1) > > 2) Does it contain any kind of > encryption/decryption functionality besides > > a. Authentication > > b.Hashing > > 3) If it contains such an encryption > functionality, … > > - Is it based on a public available algorithm/library or is it a > self-developed algorithm > > - What is the name of the encryption library or algorithm > > i.Is it symmetric or > asymmetric? > > ii.What is the maximum > supported key length? > > iii.Is it linked dynamically, > statically, a standard API call or something different (provided as a > result of a different tool, command line interface, …) > > > Any help would be appreciated. > > > > Thanks, > > Aditya > > -- > 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. > -- 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.
Re: [foreman-dev] Katello documentation moved to theforeman.org repo
On Tue, Nov 29, 2016 at 10:50:24AM -0500, Eric D Helms wrote: > The katello.org website itself has also been updated to redirect users > to the new documentation locations. Should it use HTTP redirects so search engines get updated as well? -- 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] Question on Byebug
I ve been helping out a few customers with production instances of foreman and often times I ve needed to debug from their sources. I wonder what it would take or how hard it will be to create something like tfm-byebug so that I can do remoter debugging on a live server. I ve not had much luck with logger.warn, so I feel this would be a good way to track that. I can see people using this as a nice debugging tool.. Any ideas/suggestions.. Partha -- 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.
