Headline features for Foreman 1.3 (please review)

Hello,

on Monday, I started working on release notes for 1.3 and these are the
headline features I have identified so far.

Note features that made it after Monday are not there yet, I will add
them later this week. Please review and add what is missing (we have
many bugfixes so apparently I had to miss some great features here so
help me).

Thanks.

Headline features

Foreman CLI

We are happy to introduce new command-line interface for Foreman codenamed
"Hammer". The first version, which is currently being release with Foreman
1.3, is not yet feature-complete and you may think about it as a "preview"
what will be in the next release. We are looking forward to your feedback on
mailing lists or IRC channels.

Compute resources and VNC/Spice

Since our web-based VNC/Spice console is popular, we have added possibility to
set VNC password for libvirt and vmware resources which helps to integrate with
VMs created outside Foreman too. Also, SPICE support can be enabled for libvirt
VMs.

Compute resource passwords are now encrypted by default.

LDAP filtering

It is not possible to to restrict LDAP authentication to a security group which
was highly demanded feature. In the LDAP definition dialog, there is new field
called "Custom LDAP search filter" which can be used for that purpose.

Host IP updating

A nice and handy feature which is useful when you have no Puppet Master and
using token-based templates. Before Foreman 1.3, there was no other way to get
the IP updated, now foreman does that automatically when
"update_ip_from_built_request" setting is set.

New foreman-rake command

Our installation on RHEL6 and clones is leveraging SCL (Software Collections)
by default and users were required to use complex "scl enable ruby193 'rake
command'" pattern to do some administrative tasks. There is new foreman-rake
command that is a simple wrapper around SCL that makes it easier now.

Custom DNS TTL setting

It is now possible to specify custom DNS TTL value in Foreman settings.

Plugins as RPM packages

Various plugins has been packaged as RPMs for easy installation, including
foreman_discovery, foreman_content, foreman_hooks, or foreman_simplify. For the
whole list head over to our plugin
documentation
.

API v2 improvements

The new "experimental" API version (v2) has been improved, providing new
features while retaining API compatibility. API v1 still remains the default
version. To use API v2, users must pass "version=2" in the header. For
example:

curl -u admin:secret -H 'Accept:application/json,version=2' http://abc.com/api/locations

New features include REMOTE_USER support, data format consolidation, better
logging and documentation.

··· -- Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

> Hello,
>
> on Monday, I started working on release notes for 1.3 and these are the
> headline features I have identified so far.
>
> Note features that made it after Monday are not there yet, I will add
> them later this week. Please review and add what is missing (we have
> many bugfixes so apparently I had to miss some great features here so
> help me).

The new Foreman installer based on Kafo.

> #### Custom DNS TTL setting
>
> It is now possible to specify custom DNS TTL value in Foreman settings.

I'd drop this.

> #### API v2 improvements
>
> The new "experimental" API version (v2) has been improved, providing new
> features while retaining API compatibility. API v1 still remains the default
> version. To use API v2, users must pass "version=2" in the header. For
> example:
>
> curl -u admin:secret -H 'Accept:application/json,version=2' http://abc.com/api/locations
>
> New features include REMOTE_USER support, data format consolidation, better
> logging and documentation.

Smart class parameters have been added to v2, this is a big feature.
There's also an improved puppet classes PR open, but I'm not sure I'll
get to that before RC1.

··· On 04/09/13 09:25, Lukas Zapletal wrote:


Dominic Cleal
Red Hat Engineering

Don't forget the changes to the Facts and Reports import API (going from
Puppet to JSON). Facts is already merged, reports will go in this week, and
since it requires changes to the ENC / Report Processor scripts, I think it
should be clearly displayed in the release notes.

The VPC support is a biggie for me and I suspect other people considering
Foreman for their AWS cloud provisioning. Already patching 1.2.2 to keep
support running on my own Foreman instances.

Jim

··· On 4 September 2013 09:44, Greg Sutcliffe wrote:

Don’t forget the changes to the Facts and Reports import API (going from
Puppet to JSON). Facts is already merged, reports will go in this week, and
since it requires changes to the ENC / Report Processor scripts, I think it
should be clearly displayed in the release notes.


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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Thanks for the reminder, I hadn't thought about that. I'll try and make
sure that gets in, as Mark O'Shea's done a good job of updating it for 1.3.

··· On 04/09/13 15:37, James Bailey wrote: > The VPC support is a biggie for me and I suspect other people > considering Foreman for their AWS cloud provisioning. Already patching > 1.2.2 to keep support running on my own Foreman instances.


Dominic Cleal
Red Hat Engineering