Staypuft Foreman LiveCD available for download

Support
1

Hello,

we have setup our jenkins job to produce development snapshots of
Foreman LiveCD. This artifact was created by Staypuft team who focuses
on Foreman-based management solution for OpenStack.

https://github.com/theforeman/foreman-live

When you download our build from here:

you get Foreman pre-installed with Discovery and Staypuft plugins.
There's an interactive shell script that does post-installation actions.
Then you can use Foreman directly from the LiveCD environment, including
bare metal discovery! Make sure you have enough RAM.

Although the directory is named nightly, due to expensive build process,
we will publish these on a weekly basis hopefully to reach nightly
cadence in the future.

Our long-term goal is to modularize and improve this approach. Patches
are accepted. We would be happy to hear your opinions, suggestions and
success stories.

Questions will be answered on #theforeman channel and our foreman-dev
list.

LZ

··· -- Later, Lukas #lzap Zapletal
2

Hi Lukas,

Should the Foreman LiveCD in nightly be functional?

When I try it I see a few issues; however, not sure if they are expected
behaviors. Such as:

  • after booting the iso, a terminal opens with an immediate permission
    error on foreman_setup.sh

  • updated the permissions as indicated in the "Using Foreman CentOS
    LiveCD" section of https://github.com/theforeman/foreman-live, ran the
    installer and observed issues with network connectivity accessing
    foreman-release-scl

  • manually updated the network config (e.g. /etc/sysconfig/network,
    /etc/sysconfig/network-script/ifcfg-eth0) so that I could access the
    external network, re-ran the installer and it still could not access
    foreman-release-scl. It seems the *.repo files are not properly set.

  • got the *.repo so that foreman-release-scl could be installed and
    re-ran, errors with ntpd & Foreman_smartproxy

thanks,
Brad

Thanks,
Brad

··· On 10/13/2014 10:09 AM, Lukas Zapletal wrote: > Hello, > > we have setup our jenkins job to produce development snapshots of > Foreman LiveCD. This artifact was created by Staypuft team who focuses > on Foreman-based management solution for OpenStack. > > https://github.com/theforeman/foreman-live > > When you download our build from here: > > http://downloads.theforeman.org/livecd/nightly/ > > you get Foreman pre-installed with Discovery and Staypuft plugins. > There's an interactive shell script that does post-installation actions. > Then you can use Foreman directly from the LiveCD environment, including > bare metal discovery! Make sure you have enough RAM. > > Although the directory is named nightly, due to expensive build process, > we will publish these on a weekly basis hopefully to reach nightly > cadence in the future. > > Our long-term goal is to modularize and improve this approach. Patches > are accepted. We would be happy to hear your opinions, suggestions and > success stories. > > Questions will be answered on #theforeman channel and our foreman-dev > list. > > LZ >
3

Hello,

see my comments inline

> > Hello,
> >
> > we have setup our jenkins job to produce development snapshots of
> > Foreman LiveCD. This artifact was created by Staypuft team who focuses
> > on Foreman-based management solution for OpenStack.
> >
> > https://github.com/theforeman/foreman-live
> >
> > When you download our build from here:
> >
> > http://downloads.theforeman.org/livecd/nightly/
> >
> > you get Foreman pre-installed with Discovery and Staypuft plugins.
> > There's an interactive shell script that does post-installation actions.
> > Then you can use Foreman directly from the LiveCD environment, including
> > bare metal discovery! Make sure you have enough RAM.
> >
> > Although the directory is named nightly, due to expensive build process,
> > we will publish these on a weekly basis hopefully to reach nightly
> > cadence in the future.
> >
> > Our long-term goal is to modularize and improve this approach. Patches
> > are accepted. We would be happy to hear your opinions, suggestions and
> > success stories.
> >
> > Questions will be answered on #theforeman channel and our foreman-dev
> > list.
> >
> > LZ
>
> Hi Lukas,
>
> Should the Foreman LiveCD in nightly be functional?

sort of, there are rough edges + it's always composed of foreman nightly which
might not be stable every day

> When I try it I see a few issues; however, not sure if they are expected
> behaviors. Such as:
>
> - after booting the iso, a terminal opens with an immediate permission
> error on foreman_setup.sh

this is expected and covered in readme. AFAIK this remained there for
debugging purposes, maybe it's time to let it run installation automatically.

> - updated the permissions as indicated in the "Using Foreman CentOS
> LiveCD" section of https://github.com/theforeman/foreman-live, ran the
> installer and observed issues with network connectivity accessing
> foreman-release-scl

I hit the same, not expected, should be already fixed in foreman, see [1] for
more details but I seem to hit it with nightly from this morning as well [2]

> - manually updated the network config (e.g. /etc/sysconfig/network,
> /etc/sysconfig/network-script/ifcfg-eth0) so that I could access the
> external network, re-ran the installer and it still could not access
> foreman-release-scl. It seems the *.repo files are not properly set.

not expected, you should be able to configure network from installer (staypuft-
installer adds interactive wizard for this)
foreman-release-scl missing is not related to networking

> - got the *.repo so that foreman-release-scl could be installed and
> re-ran, errors with ntpd & Foreman_smartproxy

not sure about smart proxy issue, likely caused by foreman-release-scl that
prevents Foreman from starting, so proxy can't register. Note that if you are
in VPN you may have blocked access to centos ntp server, so you should set
your clock server in staypuft installer.

[1] Refactor #7234: SCL 1.1 builds needed for EL rebuilds (CentOS, SL) - Packaging - Foreman
[2] http://downloads.theforeman.org/livecd/scratch-ares/livecd-foreman-live-centos-201410160744.iso

Hope this helps

··· On Wednesday 15 of October 2014 15:32:41 Brad Buckingham wrote: > On 10/13/2014 10:09 AM, Lukas Zapletal wrote:

–
Marek

4

Marek,

Thanks for the info! I have been able to get past the initial
networking issues that I was observing. :slight_smile:

Lukas,

Since the current livecd build has issues installing due to
foreman-release-scl, can we get a new build created?
It looks like the redmine issue that Marek referenced above [1] has been
addressed, so I am hoping that the next build might get us further.

Also, does the LiveCD support building a persistent Foreman instance or
is it only for trying out Foreman?

From the initial boot, I do see an 'Install to Hard Drive' icon;
however, not sure if it is intended to be functional.
Assuming that it is functional, would the workflow for the user be
something like the following:

  • run the livecd
  • once the OS is up and running, execute the installer
  • upon completion, play around, configure things…etc
  • click 'Install to Hard Drive' to save the configuration (to host or
    VM) where the LiveCD is running

Thanks,
Brad

··· On 10/16/2014 04:47 AM, Marek Hulan wrote: > Hello, > > see my comments inline > > On Wednesday 15 of October 2014 15:32:41 Brad Buckingham wrote: >> On 10/13/2014 10:09 AM, Lukas Zapletal wrote: >>> Hello, >>> >>> we have setup our jenkins job to produce development snapshots of >>> Foreman LiveCD. This artifact was created by Staypuft team who focuses >>> on Foreman-based management solution for OpenStack. >>> >>> https://github.com/theforeman/foreman-live >>> >>> When you download our build from here: >>> >>> http://downloads.theforeman.org/livecd/nightly/ >>> >>> you get Foreman pre-installed with Discovery and Staypuft plugins. >>> There's an interactive shell script that does post-installation actions. >>> Then you can use Foreman directly from the LiveCD environment, including >>> bare metal discovery! Make sure you have enough RAM. >>> >>> Although the directory is named nightly, due to expensive build process, >>> we will publish these on a weekly basis hopefully to reach nightly >>> cadence in the future. >>> >>> Our long-term goal is to modularize and improve this approach. Patches >>> are accepted. We would be happy to hear your opinions, suggestions and >>> success stories. >>> >>> Questions will be answered on #theforeman channel and our foreman-dev >>> list. >>> >>> LZ >> Hi Lukas, >> >> Should the Foreman LiveCD in nightly be functional? > sort of, there are rough edges + it's always composed of foreman nightly which > might not be stable every day > >> When I try it I see a few issues; however, not sure if they are expected >> behaviors. Such as: >> >> - after booting the iso, a terminal opens with an immediate permission >> error on foreman_setup.sh > this is expected and covered in readme. AFAIK this remained there for > debugging purposes, maybe it's time to let it run installation automatically. > >> - updated the permissions as indicated in the "Using Foreman CentOS >> LiveCD" section of https://github.com/theforeman/foreman-live, ran the >> installer and observed issues with network connectivity accessing >> foreman-release-scl > I hit the same, not expected, should be already fixed in foreman, see [1] for > more details but I seem to hit it with nightly from this morning as well [2] > >> - manually updated the network config (e.g. /etc/sysconfig/network, >> /etc/sysconfig/network-script/ifcfg-eth0) so that I could access the >> external network, re-ran the installer and it still could not access >> foreman-release-scl. It seems the *.repo files are not properly set. > not expected, you should be able to configure network from installer (staypuft- > installer adds interactive wizard for this) > foreman-release-scl missing is not related to networking > >> - got the *.repo so that foreman-release-scl could be installed and >> re-ran, errors with ntpd & Foreman_smartproxy > not sure about smart proxy issue, likely caused by foreman-release-scl that > prevents Foreman from starting, so proxy can't register. Note that if you are > in VPN you may have blocked access to centos ntp server, so you should set > your clock server in staypuft installer. > > [1] http://projects.theforeman.org/issues/7234 > [2] http://downloads.theforeman.org/livecd/scratch-ares/livecd-foreman-live-centos-201410160744.iso > > Hope this helps >
5

That's an awesome work! Will this be released with a stable foreman +
staypuft instead of nightlies at some point?

··· On Fri, Oct 17, 2014 at 10:16 PM, Brad Buckingham wrote:

On 10/16/2014 04:47 AM, Marek Hulan wrote:

Hello,

see my comments inline

On Wednesday 15 of October 2014 15:32:41 Brad Buckingham wrote:

On 10/13/2014 10:09 AM, Lukas Zapletal wrote:

Hello,

we have setup our jenkins job to produce development snapshots of
Foreman LiveCD. This artifact was created by Staypuft team who focuses
on Foreman-based management solution for OpenStack.

https://github.com/theforeman/foreman-live

When you download our build from here:

http://downloads.theforeman.org/livecd/nightly/

you get Foreman pre-installed with Discovery and Staypuft plugins.
There’s an interactive shell script that does post-installation actions.
Then you can use Foreman directly from the LiveCD environment, including
bare metal discovery! Make sure you have enough RAM.

Although the directory is named nightly, due to expensive build process,
we will publish these on a weekly basis hopefully to reach nightly
cadence in the future.

Our long-term goal is to modularize and improve this approach. Patches
are accepted. We would be happy to hear your opinions, suggestions and
success stories.

Questions will be answered on #theforeman channel and our foreman-dev
list.

LZ

Hi Lukas,

Should the Foreman LiveCD in nightly be functional?

sort of, there are rough edges + it’s always composed of foreman nightly
which
might not be stable every day

When I try it I see a few issues; however, not sure if they are expected

behaviors. Such as:

  • after booting the iso, a terminal opens with an immediate permission
    error on foreman_setup.sh

this is expected and covered in readme. AFAIK this remained there for
debugging purposes, maybe it’s time to let it run installation
automatically.

  • updated the permissions as indicated in the "Using Foreman CentOS

LiveCD" section of https://github.com/theforeman/foreman-live, ran the
installer and observed issues with network connectivity accessing
foreman-release-scl

I hit the same, not expected, should be already fixed in foreman, see [1]
for
more details but I seem to hit it with nightly from this morning as well
[2]

  • manually updated the network config (e.g. /etc/sysconfig/network,

/etc/sysconfig/network-script/ifcfg-eth0) so that I could access the
external network, re-ran the installer and it still could not access
foreman-release-scl. It seems the *.repo files are not properly set.

not expected, you should be able to configure network from installer
(staypuft-
installer adds interactive wizard for this)
foreman-release-scl missing is not related to networking

  • got the *.repo so that foreman-release-scl could be installed and

re-ran, errors with ntpd & Foreman_smartproxy

not sure about smart proxy issue, likely caused by foreman-release-scl
that
prevents Foreman from starting, so proxy can’t register. Note that if you
are
in VPN you may have blocked access to centos ntp server, so you should set
your clock server in staypuft installer.

[1] Refactor #7234: SCL 1.1 builds needed for EL rebuilds (CentOS, SL) - Packaging - Foreman
[2] http://downloads.theforeman.org/livecd/scratch-ares/
livecd-foreman-live-centos-201410160744.iso

Hope this helps

Marek,

Thanks for the info! I have been able to get past the initial networking
issues that I was observing. :slight_smile:

Lukas,

Since the current livecd build has issues installing due to
foreman-release-scl, can we get a new build created?
It looks like the redmine issue that Marek referenced above [1] has been
addressed, so I am hoping that the next build might get us further.

Also, does the LiveCD support building a persistent Foreman instance or is
it only for trying out Foreman?

From the initial boot, I do see an ‘Install to Hard Drive’ icon; however,
not sure if it is intended to be functional.
Assuming that it is functional, would the workflow for the user be
something like the following:

  • run the livecd
  • once the OS is up and running, execute the installer
  • upon completion, play around, configure things…etc
  • click ‘Install to Hard Drive’ to save the configuration (to host or VM)
    where the LiveCD is running

Thanks,
Brad

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Daniel Lobato

@elobatoss
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30

6

Guys,

> That's an awesome work! Will this be released with a stable foreman +
> staypuft instead of nightlies at some point?

we currently build against nightly, but it is easy to switch to stable.
Marek, are there any blocking bugs out of stable?

> > Since the current livecd build has issues installing due to
> > foreman-release-scl, can we get a new build created?

Which fix do you refer to? I don't see any incoming commits since the
last build.

Anyway, I initiated new build manually:

http://ci.theforeman.org/job/packaging_foreman_livecd/

Should be up in an hour.

> > Also, does the LiveCD support building a persistent Foreman instance or is
> > it only for trying out Foreman?

I don't think so.

> > From the initial boot, I do see an 'Install to Hard Drive' icon; however,
> > not sure if it is intended to be functional.
> > Assuming that it is functional, would the workflow for the user be
> > something like the following:
> > - run the livecd
> > - once the OS is up and running, execute the installer
> > - upon completion, play around, configure things…etc
> > - click 'Install to Hard Drive' to save the configuration (to host or VM)
> > where the LiveCD is running

I am not sure this is the intended workflow. Ohad, Marek?

··· -- Later, Lukas #lzap Zapletal
7

[brad] Hi Lukas, Thanks for initiating a new build. Unfortunately, the
result is the same. In my scenario (and I assume you may see the same),
the installer output is:

Starting networking setup
Networking setup has finished
Installing Info: START 387 [0%]
Installing Debug: /Stage[main]/Apache::Default_mods/Apache::M [0%]
Installing Debug: /Stage[main]/Xinetd/File[/etc/xinetd.conf]/ [0%]
Installing Debug: /Stage[main]/Foreman_proxy::Tftp/File[/var/ [0%]
Installing Debug: /Stage[main]/Foreman::Config::Passenger/Fil [0%]
Installing Info: Applying configuration version '1413938604' [0%]
Installing Notice: /Stage[main]/Concat::Setup/File[/var/lib/p [0%]
Installing Info: RESOURCE Package[bind-utils] [1%]
Installing Notice: /Stage[main]/Foreman::Plugin::Staypuft/Exe [3%]
Installing Debug: Executing '/usr/bin/yum -d 0 -e 0 -y list f [14%]
Execution of '/usr/bin/yum -d 0 -e 0 -y list foreman-release-scl' returned 1: Error: No matching Packages to list
Installing Error: Execution of '/usr/bin/yum -d 0 -e 0 -y lis [14%] /Stage[main]/Foreman::Install::Repos::Extra/Package[foreman-release-scl]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y list foreman-release-scl' returned 1: Error: No matching Packages to list
/Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]: Failed to call refresh: /usr/sbin/foreman-rake db:migrate returned 1 instead of one of [0]
/Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]: /usr/sbin/foreman-rake db:migrate returned 1 instead of one of [0]
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[livecd.example.com]: Failed to call refresh: Could not load data from https://livecd.example.com
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[livecd.example.com]: Could not load data from https://livecd.example.com
Installing Done [100%]
Installing Done [100%] []
Something went wrong! Check the log for ERROR-level output
The full log is at /var/log/foreman-installer/foreman-installer.log
Not running provisioning configuration since installation encountered errors, exit code was 6
Something went wrong! Check the log for ERROR-level output
The full log is at /var/log/foreman-installer/foreman-installer.log
[root@livecd liveuser]#

··· On 10/21/2014 09:38 AM, Lukas Zapletal wrote: > Guys, > >> That's an awesome work! Will this be released with a stable foreman + >> staypuft instead of nightlies at some point? > we currently build against nightly, but it is easy to switch to stable. > Marek, are there any blocking bugs out of stable? > >>> Since the current livecd build has issues installing due to >>> foreman-release-scl, can we get a new build created? > Which fix do you refer to? I don't see any incoming commits since the > last build. > > Anyway, I initiated new build manually: > > http://ci.theforeman.org/job/packaging_foreman_livecd/ > > Should be up in an hour.
8

> Guys,
>
> > That's an awesome work! Will this be released with a stable foreman +
> > staypuft instead of nightlies at some point?
>
> we currently build against nightly, but it is easy to switch to stable.
> Marek, are there any blocking bugs out of stable?
>
> > > Since the current livecd build has issues installing due to
> > > foreman-release-scl, can we get a new build created?
>
> Which fix do you refer to? I don't see any incoming commits since the
> last build.
>
> Anyway, I initiated new build manually:
>
> http://ci.theforeman.org/job/packaging_foreman_livecd/
>
> Should be up in an hour.
>
> > > Also, does the LiveCD support building a persistent Foreman instance
> or is
> > > it only for trying out Foreman?
>
> I don't think so.
>
> > > From the initial boot, I do see an 'Install to Hard Drive' icon;
> however,
> > > not sure if it is intended to be functional.
> > > Assuming that it is functional, would the workflow for the user be
> > > something like the following:
> > > - run the livecd
> > > - once the OS is up and running, execute the installer
> > > - upon completion, play around, configure things…etc
> > > - click 'Install to Hard Drive' to save the configuration (to host or
> VM)
> > > where the LiveCD is running
>
> I am not sure this is the intended workflow. Ohad, Marek?
>

IMHO this has two main usage case:

  1. POC - get a foreman working real quick.
  2. a valid install option, e.g. stateful -> write to disk.

similar to how fedora/ubuntu etc allow you to try it out and if you like it
install them.

Would it be easier if we call it an "appliance" instead?

thanks,
Ohad

··· On Tue, Oct 21, 2014 at 4:38 PM, Lukas Zapletal wrote:

–
Later,
Lukas #lzap Zapletal

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

9

Hello,

see my inline comments

> Guys,
>
> > That's an awesome work! Will this be released with a stable foreman +
> > staypuft instead of nightlies at some point?
>
> we currently build against nightly, but it is easy to switch to stable.
> Marek, are there any blocking bugs out of stable?

We can't build on stable until 1.7 is stable. Staypuft requires networking
changes that are not present in 1.6 (current stable). But then I don't see any
blocker.

> > > Since the current livecd build has issues installing due to
> > > foreman-release-scl, can we get a new build created?
>
> Which fix do you refer to? I don't see any incoming commits since the
> last build.
>
> Anyway, I initiated new build manually:
>
> http://ci.theforeman.org/job/packaging_foreman_livecd/
>
> Should be up in an hour.

Did it work? I tested this as well but got the same error. I didn't have time
to debug yet.

> > > Also, does the LiveCD support building a persistent Foreman instance or
> > > is
> > > it only for trying out Foreman?
>
> I don't think so.

I think it should work. You should be able to install it to HDD and then boot
from it. You would have to take all steps (running staypuft installer) then.
There's no way to boot from livecd, run staypuft installer, use foreman for
while and then apply running dev into HDD.

> > > From the initial boot, I do see an 'Install to Hard Drive' icon;
> > > however,
> > > not sure if it is intended to be functional.
> > > Assuming that it is functional, would the workflow for the user be
> > > something like the following:
> > > - run the livecd
> > > - once the OS is up and running, execute the installer
> > > - upon completion, play around, configure things…etc
> > > - click 'Install to Hard Drive' to save the configuration (to host or
> > > VM)
> > > where the LiveCD is running
>
> I am not sure this is the intended workflow. Ohad, Marek?

While this would be awesome I don't think anyone worked on this.

··· On Tuesday 21 of October 2014 15:38:34 Lukas Zapletal wrote:

–
Marek

10

Im a bit confused, i
downloaded http://downloads.theforeman.org/livecd/nightly/foreman-live.iso
from 26-Nov-2014 16:50, launched it in a 4Gb XEN VM with 8 GB disk, when it
boots into the gui
theres a anaconda installer, so i run that, it completes and says to
reboot, i do so, and it wount boot
from the drive it installed to, kinda odd, i also noticed suring the
install process i dont see it install grub

either way, its just sitting there saying Boot device: Hard disk SUCCESS
and doing nothing else…
so what have i missed?

··· On Wednesday, October 22, 2014 11:34:10 PM UTC+11, Marek Hulan wrote: > > Hello, > > see my inline comments > > On Tuesday 21 of October 2014 15:38:34 Lukas Zapletal wrote: > > Guys, > > > > > That's an awesome work! Will this be released with a stable foreman + > > > staypuft instead of nightlies at some point? > > > > we currently build against nightly, but it is easy to switch to stable. > > Marek, are there any blocking bugs out of stable? > > We can't build on stable until 1.7 is stable. Staypuft requires networking > changes that are not present in 1.6 (current stable). But then I don't see > any > blocker. > > > > > Since the current livecd build has issues installing due to > > > > foreman-release-scl, can we get a new build created? > > > > Which fix do you refer to? I don't see any incoming commits since the > > last build. > > > > Anyway, I initiated new build manually: > > > > http://ci.theforeman.org/job/packaging_foreman_livecd/ > > > > Should be up in an hour. > > Did it work? I tested this as well but got the same error. I didn't have > time > to debug yet. > > > > > Also, does the LiveCD support building a persistent Foreman instance > or > > > > is > > > > it only for trying out Foreman? > > > > I don't think so. > > I think it should work. You should be able to install it to HDD and then > boot > from it. You would have to take all steps (running staypuft installer) > then. > There's no way to boot from livecd, run staypuft installer, use foreman > for > while and then apply running dev into HDD. > > > > > From the initial boot, I do see an 'Install to Hard Drive' icon; > > > > however, > > > > not sure if it is intended to be functional. > > > > Assuming that it is functional, would the workflow for the user be > > > > something like the following: > > > > - run the livecd > > > > - once the OS is up and running, execute the installer > > > > - upon completion, play around, configure things...etc > > > > - click 'Install to Hard Drive' to save the configuration (to host > or > > > > VM) > > > > where the LiveCD is running > > > > I am not sure this is the intended workflow. Ohad, Marek? > > While this would be awesome I don't think anyone worked on this. > > -- > Marek > >
11

> Im a bit confused, i
> downloaded http://downloads.theforeman.org/livecd/nightly/foreman-live.iso
> from 26-Nov-2014 16:50, launched it in a 4Gb XEN VM with 8 GB disk, when it
> boots into the gui
> theres a anaconda installer, so i run that, it completes and says to
> reboot, i do so, and it wount boot
> from the drive it installed to, kinda odd, i also noticed suring the
> install process i dont see it install grub

Hello,

we need to improve instructions and be more verbose about what you want
to do. The live-foreman environment is consumed really as a "live"
system. You basically run our foreman-installer:

sudo foreman-installer -v

and then you can play with Foreman "live".

The installation to hard drive is not yet supported.

··· -- Later, Lukas #lzap Zapletal