Suggestions needed for the new frontpage

Support
1

Hi all,

The new Foreman website is not far away now, but we have a few small
things to deal with. We'd like your help with this one :slight_smile:

We need two descriptions of Foreman for the frontpage of the site - a
one-sentence headline, and a short paragraph "elevator pitch". 2-4
sentences is ideal.

To get you started, here's my attempt (it's not very good, that's why
I'm asking you guys :P)

  1. Foreman manages the complete lifecycle of your servers
  2. With Foreman, you can augment your configuration management to
    cover the whole lifecycle of a machine. Templated installs, virtual
    machine creation, and cloud integration are all handled for you,
    before handing off to configuration management. Foreman also deals
    with reporting and audit, so you always know the current state of your
    infrastructure.

Looking forward to seeing what you can come up with :slight_smile:

Greg

2

I think we should try to remove personal pronouns from the two blurbs. Here are my two attempts:

  1. Foreman manages the complete lifecycle of your servers.
  2. Foreman allows augmentation of configuration management to the entire systems provisioning process. Unattended installations, public and private cloud integration, and complex host classification and reporting capabilities are all handled from a single source via integration with Puppet.

The second sentence of the mini-paragraph might be too long and rambly, though.

Also, be sure to check out the staging site [1] and read the conversation that happened on the development list [2].

-Sam

  1. http://server2.theforeman.org
  2. https://groups.google.com/d/topic/foreman-dev/GFODNfHIOPo/discussion
··· ----- Original Message ----- From: "Greg Sutcliffe" To: "Foreman ." Sent: Friday, December 7, 2012 7:48:58 AM Subject: [foreman-users] Suggestions needed for the new frontpage

Hi all,

The new Foreman website is not far away now, but we have a few small
things to deal with. We’d like your help with this one :slight_smile:

We need two descriptions of Foreman for the frontpage of the site - a
one-sentence headline, and a short paragraph “elevator pitch”. 2-4
sentences is ideal.

To get you started, here’s my attempt (it’s not very good, that’s why
I’m asking you guys :P)

  1. Foreman manages the complete lifecycle of your servers
  2. With Foreman, you can augment your configuration management to
    cover the whole lifecycle of a machine. Templated installs, virtual
    machine creation, and cloud integration are all handled for you,
    before handing off to configuration management. Foreman also deals
    with reporting and audit, so you always know the current state of your
    infrastructure.

Looking forward to seeing what you can come up with :slight_smile:

Greg

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

3

my blurbs, needs refinement, maybe too long too.

The Foreman - Unified server management
The Foreman manages your entire server infrastructure, from Bare Metal to
Cloud. The Foreman provides unattended installation and configuration
management for the major server operating systems - all in a unified
interface. The Foreman has role based access control, auditing, a very
powerful templating system and APIs for all functionality provided in the
interface.

4

Thinking the first line should be more explicit:

  1. Foreman manages the complete lifecycle of an organization's
    servers, whether they are bare metal, Xen, KVM, VMWare, or running in
    any number of clouds, including Amazon EC2, Rackspace, or Openstack.
    (Or any combination of the above.)
  2. This lifecycle management includes every level of server
    management, including managing the initial OS installation and related
    services, full integration with configuration management systems like
    Puppet, reporting, auditing and providing inventory data, all via
    either a Web GUI, command line or RESTful API.

Cheers,
Brian

··· On Fri, Dec 7, 2012 at 7:48 AM, Greg Sutcliffe wrote: > Hi all, > > The new Foreman website is not far away now, but we have a few small > things to deal with. We'd like your help with this one :) > > We need two descriptions of Foreman for the frontpage of the site - a > one-sentence headline, and a short paragraph "elevator pitch". 2-4 > sentences is ideal. > > To get you started, here's my attempt (it's not very good, that's why > I'm asking you guys :P) > > 1) Foreman manages the complete lifecycle of your servers > 2) With Foreman, you can augment your configuration management to > cover the whole lifecycle of a machine. Templated installs, virtual > machine creation, and cloud integration are all handled for you, > before handing off to configuration management. Foreman also deals > with reporting and audit, so you always know the current state of your > infrastructure. > > Looking forward to seeing what you can come up with :) > > Greg > > -- > You received this message because you are subscribed to the Google Groups "Foreman users" group. > To post to this group, send email to foreman-users@googlegroups.com. > To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en. >
5

> Hi all,
>
> The new Foreman website is not far away now, but we have a few small
> things to deal with. We'd like your help with this one :slight_smile:
>
> We need two descriptions of Foreman for the frontpage of the site - a
> one-sentence headline, and a short paragraph "elevator pitch". 2-4
> sentences is ideal.
>
> To get you started, here's my attempt (it's not very good, that's why
> I'm asking you guys :P)
>
> 1) Foreman manages the complete lifecycle of your servers
> 2) With Foreman, you can augment your configuration management to
> cover the whole lifecycle of a machine. Templated installs, virtual
> machine creation, and cloud integration are all handled for you,
> before handing off to configuration management. Foreman also deals
> with reporting and audit, so you always know the current state of your
> infrastructure.
Here is my take on it:

  1. The Foreman: the one stop shop to manage servers.
  2. The Foreman connects the tools used to configure servers, all the
    way from cradle to grave.
    In one process, The Foreman allows to create, provision, report and
    classify both servers and virtual machines, in the cloud and within
    premises.
    The Foreman provides auditable and comprehensive interaction
    facilities: Web front end, a command line interface and a REST API.
    With strongly integration with Puppet, TFTP, DHCP, DNS, and a choice
    of unattended installation means supported, The Foreman is the
    productivity tool to satisfy configuration management needs.

Regards,
Flo

··· On 7 December 2012 12:48, Greg Sutcliffe wrote:

Looking forward to seeing what you can come up with :slight_smile:

Greg

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

6

>
> > Hi all,
> >
> > The new Foreman website is not far away now, but we have a few small
> > things to deal with. We'd like your help with this one :slight_smile:
> >
> > We need two descriptions of Foreman for the frontpage of the site - a
> > one-sentence headline, and a short paragraph "elevator pitch". 2-4
> > sentences is ideal.
> >
> > To get you started, here's my attempt (it's not very good, that's why
> > I'm asking you guys :P)
> >
> > 1) Foreman manages the complete lifecycle of your servers
> > 2) With Foreman, you can augment your configuration management to
> > cover the whole lifecycle of a machine. Templated installs, virtual
> > machine creation, and cloud integration are all handled for you,
> > before handing off to configuration management. Foreman also deals
> > with reporting and audit, so you always know the current state of your
> > infrastructure.
> Here is my take on it:
>
> 1) The Foreman: the one stop shop to manage servers.
> 2) The Foreman connects the tools used to configure servers, all the
> way from cradle to grave.
> In one process, The Foreman allows to create, provision, report and
> classify both servers and virtual machines, in the cloud and within
> premises.
> The Foreman provides auditable and comprehensive interaction
> facilities: Web front end, a command line interface and a REST API.
> With strongly integration with Puppet, TFTP, DHCP, DNS, and a choice
> of unattended installation means supported, The Foreman is the
> productivity tool to satisfy configuration management needs.
>
>
I like this one. +1

··· On Friday, December 7, 2012 11:55:27 AM UTC-6, kyzh wrote: > On 7 December 2012 12:48, Greg Sutcliffe <greg.su...@gmail.com> > wrote:

Regards,
Flo

Looking forward to seeing what you can come up with :slight_smile:

Greg

–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To post to this group, send email to forema...@googlegroups.com<javascript:>.

To unsubscribe from this group, send email to
foreman-user...@googlegroups.com <javascript:>.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.

7

> I think we should try to remove personal pronouns from the two blurbs. Here are my two attempts:
>
> 1) Foreman manages the complete lifecycle of your servers.
Possibilities include

Foreman is a complete application lifycle management tool.

And from the website:

Foreman is the single address for a machines life cycle management.

> 2) Foreman allows augmentation of configuration management to the entire systems provisioning process. Unattended installations, public and private cloud integration, and complex host classification and reporting capabilities are all handled from a single source via integration with Puppet.

Foreman provides a single view of parts of a machines lifecyle including
initial provisioning, maintenance, reprovisioning. It provides a
inventory of the machines in your data center, and deployed in the
cloud. Policies defined in foreman automate the creation and maintenance
of machines to make your staff more productive,

>
> The second sentence of the mini-paragraph might be too long and rambly, though.
>
> Also, be sure to check out the staging site [1] and read the conversation that happened on the development list [2].
>
> -Sam
>
> 1. http://server2.theforeman.org

Loking at this… for hte "getting started" link, I was surprised to get
to the "download" page. IMHO, I would suggest the about page, or make
hte landing page a bit more info rich.

– bk

··· On 12/07/2012 09:46 AM, Sam Kottler wrote:
8

I think it's important to avoid getting too far into the weeds on the specifics of the platforms we support since it creates a moving target and might turn away users who might use more obscure tools. We need to make sure that it's clear that we can collect data from any platform where the agent can run, even if you might lose the provisioning capabilities Foreman affords.

··· ----- Original Message ----- From: "Brian Gupta" To: foreman-users@googlegroups.com Sent: Friday, December 7, 2012 11:40:31 AM Subject: Re: [foreman-users] Suggestions needed for the new frontpage

Thinking the first line should be more explicit:

  1. Foreman manages the complete lifecycle of an organization’s
    servers, whether they are bare metal, Xen, KVM, VMWare, or running in
    any number of clouds, including Amazon EC2, Rackspace, or Openstack.
    (Or any combination of the above.)
  2. This lifecycle management includes every level of server
    management, including managing the initial OS installation and related
    services, full integration with configuration management systems like
    Puppet, reporting, auditing and providing inventory data, all via
    either a Web GUI, command line or RESTful API.

Cheers,
Brian

On Fri, Dec 7, 2012 at 7:48 AM, Greg Sutcliffe greg.sutcliffe@gmail.com wrote:

Hi all,

The new Foreman website is not far away now, but we have a few small
things to deal with. We’d like your help with this one :slight_smile:

We need two descriptions of Foreman for the frontpage of the site - a
one-sentence headline, and a short paragraph “elevator pitch”. 2-4
sentences is ideal.

To get you started, here’s my attempt (it’s not very good, that’s why
I’m asking you guys :P)

  1. Foreman manages the complete lifecycle of your servers
  2. With Foreman, you can augment your configuration management to
    cover the whole lifecycle of a machine. Templated installs, virtual
    machine creation, and cloud integration are all handled for you,
    before handing off to configuration management. Foreman also deals
    with reporting and audit, so you always know the current state of your
    infrastructure.

Looking forward to seeing what you can come up with :slight_smile:

Greg

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

9

I agree that the tag line and pitch should not contain $ALL_THE_INFO,
but if you can get it on the first page some how it would be good.

  • bk
··· On 12/07/2012 11:51 AM, Sam Kottler wrote: > I think it's important to avoid getting too far into the weeds on the specifics of the platforms we support since it creates a moving target and might turn away users who might use more obscure tools. We need to make sure that it's clear that we can collect data from any platform where the agent can run, even if you might lose the provisioning capabilities Foreman affords. > > ----- Original Message ----- > From: "Brian Gupta" > To: foreman-users@googlegroups.com > Sent: Friday, December 7, 2012 11:40:31 AM > Subject: Re: [foreman-users] Suggestions needed for the new frontpage > > Thinking the first line should be more explicit: > > 1) Foreman manages the complete lifecycle of an organization's > servers, whether they are bare metal, Xen, KVM, VMWare, or running in > any number of clouds, including Amazon EC2, Rackspace, or Openstack. > (Or any combination of the above.) > 2) This lifecycle management includes every level of server > management, including managing the initial OS installation and related > services, full integration with configuration management systems like > Puppet, reporting, auditing and providing inventory data, all via > either a Web GUI, command line or RESTful API. > > Cheers, > Brian > > On Fri, Dec 7, 2012 at 7:48 AM, Greg Sutcliffe wrote: >> Hi all, >> >> The new Foreman website is not far away now, but we have a few small >> things to deal with. We'd like your help with this one :) >> >> We need two descriptions of Foreman for the frontpage of the site - a >> one-sentence headline, and a short paragraph "elevator pitch". 2-4 >> sentences is ideal. >> >> To get you started, here's my attempt (it's not very good, that's why >> I'm asking you guys :P) >> >> 1) Foreman manages the complete lifecycle of your servers >> 2) With Foreman, you can augment your configuration management to >> cover the whole lifecycle of a machine. Templated installs, virtual >> machine creation, and cloud integration are all handled for you, >> before handing off to configuration management. Foreman also deals >> with reporting and audit, so you always know the current state of your >> infrastructure. >> >> Looking forward to seeing what you can come up with :) >> >> Greg >> >> -- >> You received this message because you are subscribed to the Google Groups "Foreman users" group. >> To post to this group, send email to foreman-users@googlegroups.com. >> To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com. >> For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en. >> >
10

I kinda think a little differently. I feel we kinda should be proud of
all the popular technologies we work with. (Yes it will require maint
of the site going forward as we bring in additional technologies, but
I do feel specificity would draw people in if they work with any of
the technologies mentioned, and yes there is a risk of losing folks
using obscure tools, but that is a risk that I personally think is
worth it, if it brings in more people using the technologies we
currently support. (We've crossed a hump where what we support brings
in more than 50% of the market)

I say this, because when talking to people about Foreman, I've noticed
that if I say EC2 and VMware in the same sentence as when I introduce
people to it, they do tend to get excited.

Hmm perhaps a hybrid?

  1. Tagline
  2. High level description
  3. List of technologies we integrate with and manage

One thing I do agree with Sam, is that we should make it clear that
for the workflow stuff, that they can pick and choose which pieces of
the lifecycle they want to use Foreman for. It's not just that it can
be used as a standalone Puppet ENC/facts/reports server, but it can
also be a standalone provisioning
server without puppet. (As I understand).

Cheers,
Brian

··· On Fri, Dec 7, 2012 at 11:51 AM, Sam Kottler wrote: > I think it's important to avoid getting too far into the weeds on the specifics of the platforms we support since it creates a moving target and might turn away users who might use more obscure tools. We need to make sure that it's clear that we can collect data from any platform where the agent can run, even if you might lose the provisioning capabilities Foreman affords. > > ----- Original Message ----- > From: "Brian Gupta" > To: foreman-users@googlegroups.com > Sent: Friday, December 7, 2012 11:40:31 AM > Subject: Re: [foreman-users] Suggestions needed for the new frontpage > > Thinking the first line should be more explicit: > > 1) Foreman manages the complete lifecycle of an organization's > servers, whether they are bare metal, Xen, KVM, VMWare, or running in > any number of clouds, including Amazon EC2, Rackspace, or Openstack. > (Or any combination of the above.) > 2) This lifecycle management includes every level of server > management, including managing the initial OS installation and related > services, full integration with configuration management systems like > Puppet, reporting, auditing and providing inventory data, all via > either a Web GUI, command line or RESTful API. > > Cheers, > Brian > > On Fri, Dec 7, 2012 at 7:48 AM, Greg Sutcliffe wrote: >> Hi all, >> >> The new Foreman website is not far away now, but we have a few small >> things to deal with. We'd like your help with this one :) >> >> We need two descriptions of Foreman for the frontpage of the site - a >> one-sentence headline, and a short paragraph "elevator pitch". 2-4 >> sentences is ideal. >> >> To get you started, here's my attempt (it's not very good, that's why >> I'm asking you guys :P) >> >> 1) Foreman manages the complete lifecycle of your servers >> 2) With Foreman, you can augment your configuration management to >> cover the whole lifecycle of a machine. Templated installs, virtual >> machine creation, and cloud integration are all handled for you, >> before handing off to configuration management. Foreman also deals >> with reporting and audit, so you always know the current state of your >> infrastructure. >> >> Looking forward to seeing what you can come up with :) >> >> Greg >> >> -- >> You received this message because you are subscribed to the Google Groups "Foreman users" group. >> To post to this group, send email to foreman-users@googlegroups.com. >> To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com. >> For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups "Foreman users" group. > To post to this group, send email to foreman-users@googlegroups.com. > To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups "Foreman users" group. > To post to this group, send email to foreman-users@googlegroups.com. > To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en. >
11

Greg and I just spent some time working on these two pieces of text. Here's what we came up with:

  1. The Foreman is a complete lifecycle management tool for physical and virtual servers providing deep integration with configuration management.
  2. The Foreman provides comprehensive, auditable interaction facilities including a web frontend and robust, RESTful API. Through deep integration with configuration management, DHCP, DNS, TFTP, and PXE-based unattended installations, Foreman manages every stage of the lifecycle of your physical or virtual servers.

Thoughts?

··· ----- Original Message ----- From: "Brian Gupta" To: foreman-users@googlegroups.com Sent: Saturday, December 8, 2012 10:34:07 PM Subject: Re: [foreman-users] Suggestions needed for the new frontpage

I kinda think a little differently. I feel we kinda should be proud of
all the popular technologies we work with. (Yes it will require maint
of the site going forward as we bring in additional technologies, but
I do feel specificity would draw people in if they work with any of
the technologies mentioned, and yes there is a risk of losing folks
using obscure tools, but that is a risk that I personally think is
worth it, if it brings in more people using the technologies we
currently support. (We’ve crossed a hump where what we support brings
in more than 50% of the market)

I say this, because when talking to people about Foreman, I’ve noticed
that if I say EC2 and VMware in the same sentence as when I introduce
people to it, they do tend to get excited.

Hmm perhaps a hybrid?

  1. Tagline
  2. High level description
  3. List of technologies we integrate with and manage

One thing I do agree with Sam, is that we should make it clear that
for the workflow stuff, that they can pick and choose which pieces of
the lifecycle they want to use Foreman for. It’s not just that it can
be used as a standalone Puppet ENC/facts/reports server, but it can
also be a standalone provisioning
server without puppet. (As I understand).

Cheers,
Brian

On Fri, Dec 7, 2012 at 11:51 AM, Sam Kottler skottler@redhat.com wrote:

I think it’s important to avoid getting too far into the weeds on the specifics of the platforms we support since it creates a moving target and might turn away users who might use more obscure tools. We need to make sure that it’s clear that we can collect data from any platform where the agent can run, even if you might lose the provisioning capabilities Foreman affords.

----- Original Message -----
From: “Brian Gupta” brian.gupta@brandorr.com
To: foreman-users@googlegroups.com
Sent: Friday, December 7, 2012 11:40:31 AM
Subject: Re: [foreman-users] Suggestions needed for the new frontpage

Thinking the first line should be more explicit:

  1. Foreman manages the complete lifecycle of an organization’s
    servers, whether they are bare metal, Xen, KVM, VMWare, or running in
    any number of clouds, including Amazon EC2, Rackspace, or Openstack.
    (Or any combination of the above.)
  2. This lifecycle management includes every level of server
    management, including managing the initial OS installation and related
    services, full integration with configuration management systems like
    Puppet, reporting, auditing and providing inventory data, all via
    either a Web GUI, command line or RESTful API.

Cheers,
Brian

On Fri, Dec 7, 2012 at 7:48 AM, Greg Sutcliffe greg.sutcliffe@gmail.com wrote:

Hi all,

The new Foreman website is not far away now, but we have a few small
things to deal with. We’d like your help with this one :slight_smile:

We need two descriptions of Foreman for the frontpage of the site - a
one-sentence headline, and a short paragraph “elevator pitch”. 2-4
sentences is ideal.

To get you started, here’s my attempt (it’s not very good, that’s why
I’m asking you guys :P)

  1. Foreman manages the complete lifecycle of your servers
  2. With Foreman, you can augment your configuration management to
    cover the whole lifecycle of a machine. Templated installs, virtual
    machine creation, and cloud integration are all handled for you,
    before handing off to configuration management. Foreman also deals
    with reporting and audit, so you always know the current state of your
    infrastructure.

Looking forward to seeing what you can come up with :slight_smile:

Greg

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

12

> Greg and I just spent some time working on these two pieces of text. Here's what we came up with:
>
> 1) The Foreman is a complete lifecycle management tool for physical and virtual servers providing deep integration with configuration management.
> 2) The Foreman provides comprehensive, auditable interaction facilities including a web frontend and robust, RESTful API. Through deep integration with configuration management, DHCP, DNS, TFTP, and PXE-based unattended installations, Foreman manages every stage of the lifecycle of your physical or virtual servers.

IMHO, invert the order of the second one. Lots of things have a web
front end and rest API. Focus on the TL;DR crowd and get your important
this first.

– bk

··· On 12/18/2012 03:19 AM, Sam Kottler wrote:

Thoughts?

----- Original Message -----
From: “Brian Gupta” brian.gupta@brandorr.com
To: foreman-users@googlegroups.com
Sent: Saturday, December 8, 2012 10:34:07 PM
Subject: Re: [foreman-users] Suggestions needed for the new frontpage

I kinda think a little differently. I feel we kinda should be proud of
all the popular technologies we work with. (Yes it will require maint
of the site going forward as we bring in additional technologies, but
I do feel specificity would draw people in if they work with any of
the technologies mentioned, and yes there is a risk of losing folks
using obscure tools, but that is a risk that I personally think is
worth it, if it brings in more people using the technologies we
currently support. (We’ve crossed a hump where what we support brings
in more than 50% of the market)

I say this, because when talking to people about Foreman, I’ve noticed
that if I say EC2 and VMware in the same sentence as when I introduce
people to it, they do tend to get excited.

Hmm perhaps a hybrid?

  1. Tagline
  2. High level description
  3. List of technologies we integrate with and manage

One thing I do agree with Sam, is that we should make it clear that
for the workflow stuff, that they can pick and choose which pieces of
the lifecycle they want to use Foreman for. It’s not just that it can
be used as a standalone Puppet ENC/facts/reports server, but it can
also be a standalone provisioning
server without puppet. (As I understand).

Cheers,
Brian

On Fri, Dec 7, 2012 at 11:51 AM, Sam Kottler skottler@redhat.com wrote:

I think it’s important to avoid getting too far into the weeds on the specifics of the platforms we support since it creates a moving target and might turn away users who might use more obscure tools. We need to make sure that it’s clear that we can collect data from any platform where the agent can run, even if you might lose the provisioning capabilities Foreman affords.

----- Original Message -----
From: “Brian Gupta” brian.gupta@brandorr.com
To: foreman-users@googlegroups.com
Sent: Friday, December 7, 2012 11:40:31 AM
Subject: Re: [foreman-users] Suggestions needed for the new frontpage

Thinking the first line should be more explicit:

  1. Foreman manages the complete lifecycle of an organization’s
    servers, whether they are bare metal, Xen, KVM, VMWare, or running in
    any number of clouds, including Amazon EC2, Rackspace, or Openstack.
    (Or any combination of the above.)
  2. This lifecycle management includes every level of server
    management, including managing the initial OS installation and related
    services, full integration with configuration management systems like
    Puppet, reporting, auditing and providing inventory data, all via
    either a Web GUI, command line or RESTful API.

Cheers,
Brian

On Fri, Dec 7, 2012 at 7:48 AM, Greg Sutcliffe greg.sutcliffe@gmail.com wrote:

Hi all,

The new Foreman website is not far away now, but we have a few small
things to deal with. We’d like your help with this one :slight_smile:

We need two descriptions of Foreman for the frontpage of the site - a
one-sentence headline, and a short paragraph “elevator pitch”. 2-4
sentences is ideal.

To get you started, here’s my attempt (it’s not very good, that’s why
I’m asking you guys :P)

  1. Foreman manages the complete lifecycle of your servers
  2. With Foreman, you can augment your configuration management to
    cover the whole lifecycle of a machine. Templated installs, virtual
    machine creation, and cloud integration are all handled for you,
    before handing off to configuration management. Foreman also deals
    with reporting and audit, so you always know the current state of your
    infrastructure.

Looking forward to seeing what you can come up with :slight_smile:

Greg

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

13

+1.

I also removed the repetitive "deep integration with configuration management" from the first sentence, but left it in the second since it fits better there.

-Sam

··· ----- Original Message ----- From: "Bryan Kearney" To: foreman-users@googlegroups.com Sent: Sunday, December 16, 2012 6:14:13 PM Subject: Re: [foreman-users] Suggestions needed for the new frontpage

On 12/18/2012 03:19 AM, Sam Kottler wrote:

Greg and I just spent some time working on these two pieces of text. Here’s what we came up with:

  1. The Foreman is a complete lifecycle management tool for physical and virtual servers providing deep integration with configuration management.
  2. The Foreman provides comprehensive, auditable interaction facilities including a web frontend and robust, RESTful API. Through deep integration with configuration management, DHCP, DNS, TFTP, and PXE-based unattended installations, Foreman manages every stage of the lifecycle of your physical or virtual servers.

IMHO, invert the order of the second one. Lots of things have a web
front end and rest API. Focus on the TL;DR crowd and get your important
this first.

– bk

Thoughts?

----- Original Message -----
From: “Brian Gupta” brian.gupta@brandorr.com
To: foreman-users@googlegroups.com
Sent: Saturday, December 8, 2012 10:34:07 PM
Subject: Re: [foreman-users] Suggestions needed for the new frontpage

I kinda think a little differently. I feel we kinda should be proud of
all the popular technologies we work with. (Yes it will require maint
of the site going forward as we bring in additional technologies, but
I do feel specificity would draw people in if they work with any of
the technologies mentioned, and yes there is a risk of losing folks
using obscure tools, but that is a risk that I personally think is
worth it, if it brings in more people using the technologies we
currently support. (We’ve crossed a hump where what we support brings
in more than 50% of the market)

I say this, because when talking to people about Foreman, I’ve noticed
that if I say EC2 and VMware in the same sentence as when I introduce
people to it, they do tend to get excited.

Hmm perhaps a hybrid?

  1. Tagline
  2. High level description
  3. List of technologies we integrate with and manage

One thing I do agree with Sam, is that we should make it clear that
for the workflow stuff, that they can pick and choose which pieces of
the lifecycle they want to use Foreman for. It’s not just that it can
be used as a standalone Puppet ENC/facts/reports server, but it can
also be a standalone provisioning
server without puppet. (As I understand).

Cheers,
Brian

On Fri, Dec 7, 2012 at 11:51 AM, Sam Kottler skottler@redhat.com wrote:

I think it’s important to avoid getting too far into the weeds on the specifics of the platforms we support since it creates a moving target and might turn away users who might use more obscure tools. We need to make sure that it’s clear that we can collect data from any platform where the agent can run, even if you might lose the provisioning capabilities Foreman affords.

----- Original Message -----
From: “Brian Gupta” brian.gupta@brandorr.com
To: foreman-users@googlegroups.com
Sent: Friday, December 7, 2012 11:40:31 AM
Subject: Re: [foreman-users] Suggestions needed for the new frontpage

Thinking the first line should be more explicit:

  1. Foreman manages the complete lifecycle of an organization’s
    servers, whether they are bare metal, Xen, KVM, VMWare, or running in
    any number of clouds, including Amazon EC2, Rackspace, or Openstack.
    (Or any combination of the above.)
  2. This lifecycle management includes every level of server
    management, including managing the initial OS installation and related
    services, full integration with configuration management systems like
    Puppet, reporting, auditing and providing inventory data, all via
    either a Web GUI, command line or RESTful API.

Cheers,
Brian

On Fri, Dec 7, 2012 at 7:48 AM, Greg Sutcliffe greg.sutcliffe@gmail.com wrote:

Hi all,

The new Foreman website is not far away now, but we have a few small
things to deal with. We’d like your help with this one :slight_smile:

We need two descriptions of Foreman for the frontpage of the site - a
one-sentence headline, and a short paragraph “elevator pitch”. 2-4
sentences is ideal.

To get you started, here’s my attempt (it’s not very good, that’s why
I’m asking you guys :P)

  1. Foreman manages the complete lifecycle of your servers
  2. With Foreman, you can augment your configuration management to
    cover the whole lifecycle of a machine. Templated installs, virtual
    machine creation, and cloud integration are all handled for you,
    before handing off to configuration management. Foreman also deals
    with reporting and audit, so you always know the current state of your
    infrastructure.

Looking forward to seeing what you can come up with :slight_smile:

Greg

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

14

Can we add somewhere something like: "… whether on your own
HW/hypervisors, or in the cloud." (To make sure that it's clear to
readers that "virtual servers" also includes cloud based ones.)

··· On Mon, Dec 17, 2012 at 3:31 PM, Sam Kottler wrote: > +1. > > I also removed the repetitive "deep integration with configuration management" from the first sentence, but left it in the second since it fits better there. > > -Sam > > ----- Original Message ----- > From: "Bryan Kearney" > To: foreman-users@googlegroups.com > Sent: Sunday, December 16, 2012 6:14:13 PM > Subject: Re: [foreman-users] Suggestions needed for the new frontpage > > On 12/18/2012 03:19 AM, Sam Kottler wrote: >> Greg and I just spent some time working on these two pieces of text. Here's what we came up with: >> >> 1) The Foreman is a complete lifecycle management tool for physical and virtual servers providing deep integration with configuration management. >> 2) The Foreman provides comprehensive, auditable interaction facilities including a web frontend and robust, RESTful API. Through deep integration with configuration management, DHCP, DNS, TFTP, and PXE-based unattended installations, Foreman manages every stage of the lifecycle of your physical or virtual servers. > > IMHO, invert the order of the second one. Lots of things have a web > front end and rest API. Focus on the TL;DR crowd and get your important > this first. > > -- bk > >> >> Thoughts? >> >> ----- Original Message ----- >> From: "Brian Gupta" >> To: foreman-users@googlegroups.com >> Sent: Saturday, December 8, 2012 10:34:07 PM >> Subject: Re: [foreman-users] Suggestions needed for the new frontpage >> >> I kinda think a little differently. I feel we kinda should be proud of >> all the popular technologies we work with. (Yes it will require maint >> of the site going forward as we bring in additional technologies, but >> I do feel specificity would draw people in if they work with any of >> the technologies mentioned, and yes there is a risk of losing folks >> using obscure tools, but that is a risk that I personally think is >> worth it, if it brings in more people using the technologies we >> currently support. (We've crossed a hump where what we support brings >> in more than 50% of the market) >> >> I say this, because when talking to people about Foreman, I've noticed >> that if I say EC2 and VMware in the same sentence as when I introduce >> people to it, they do tend to get excited. >> >> Hmm perhaps a hybrid? >> 1) Tagline >> 2) High level description >> 3) List of technologies we integrate with and manage >> >> One thing I do agree with Sam, is that we should make it clear that >> for the workflow stuff, that they can pick and choose which pieces of >> the lifecycle they want to use Foreman for. It's not just that it can >> be used as a standalone Puppet ENC/facts/reports server, but it can >> also be a standalone provisioning >> server without puppet. (As I understand). >> >> Cheers, >> Brian >> >> On Fri, Dec 7, 2012 at 11:51 AM, Sam Kottler wrote: >>> I think it's important to avoid getting too far into the weeds on the specifics of the platforms we support since it creates a moving target and might turn away users who might use more obscure tools. We need to make sure that it's clear that we can collect data from any platform where the agent can run, even if you might lose the provisioning capabilities Foreman affords. >>> >>> ----- Original Message ----- >>> From: "Brian Gupta" >>> To: foreman-users@googlegroups.com >>> Sent: Friday, December 7, 2012 11:40:31 AM >>> Subject: Re: [foreman-users] Suggestions needed for the new frontpage >>> >>> Thinking the first line should be more explicit: >>> >>> 1) Foreman manages the complete lifecycle of an organization's >>> servers, whether they are bare metal, Xen, KVM, VMWare, or running in >>> any number of clouds, including Amazon EC2, Rackspace, or Openstack. >>> (Or any combination of the above.) >>> 2) This lifecycle management includes every level of server >>> management, including managing the initial OS installation and related >>> services, full integration with configuration management systems like >>> Puppet, reporting, auditing and providing inventory data, all via >>> either a Web GUI, command line or RESTful API. >>> >>> Cheers, >>> Brian >>> >>> On Fri, Dec 7, 2012 at 7:48 AM, Greg Sutcliffe wrote: >>>> Hi all, >>>> >>>> The new Foreman website is not far away now, but we have a few small >>>> things to deal with. We'd like your help with this one :) >>>> >>>> We need two descriptions of Foreman for the frontpage of the site - a >>>> one-sentence headline, and a short paragraph "elevator pitch". 2-4 >>>> sentences is ideal. >>>> >>>> To get you started, here's my attempt (it's not very good, that's why >>>> I'm asking you guys :P) >>>> >>>> 1) Foreman manages the complete lifecycle of your servers >>>> 2) With Foreman, you can augment your configuration management to >>>> cover the whole lifecycle of a machine. Templated installs, virtual >>>> machine creation, and cloud integration are all handled for you, >>>> before handing off to configuration management. Foreman also deals >>>> with reporting and audit, so you always know the current state of your >>>> infrastructure. >>>> >>>> Looking forward to seeing what you can come up with :) >>>> >>>> Greg >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups "Foreman users" group. >>>> To post to this group, send email to foreman-users@googlegroups.com. >>>> To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com. >>>> For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en. >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups "Foreman users" group. >>> To post to this group, send email to foreman-users@googlegroups.com. >>> To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com. >>> For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups "Foreman users" group. >>> To post to this group, send email to foreman-users@googlegroups.com. >>> To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com. >>> For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en. >>> >> > > -- > You received this message because you are subscribed to the Google Groups "Foreman users" group. > To post to this group, send email to foreman-users@googlegroups.com. > To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups "Foreman users" group. > To post to this group, send email to foreman-users@googlegroups.com. > To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en. >