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
I hit the same, not expected, should be already fixed in foreman, see  for
more details but I seem to hit it with nightly from this morning as well 
> - 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.
 Refactor #7234: SCL 1.1 builds needed for EL rebuilds (CentOS, SL) - Packaging - Foreman
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: