It may be ... *Puppet script* is to make the deployment easy. Even for users that doesn't have puppet experience.
If you (customer/user) need full control over the system you can setup your own puppet infrastructure. If you almost have a puppet infrastructure you can add stratos related modules to your existing puppet master and update your nodes.pp (or site.pp) file to support stratos. On Wed, Apr 16, 2014 at 1:09 PM, chris snow <[email protected]> wrote: > Will this approach, will the puppet install scripts takes over the > machine (i.e. controlling the hostname)? > > On Wed, Apr 16, 2014 at 8:33 AM, Thilina Piyasundara > <[email protected]> wrote: > > Hi, > > > > IMO it is better not to change that because we use puppet for large > > deployments. > > > > If you need to do a all-in-one deployment just install puppet master and > put > > all in; > > > > node 'puppet' ... { > > > > import cc > > import sc > > ... > > } > > > > or in; > > node default ... { > > ... > > } > > > > > > WDYT? > > > > > > On Wed, Apr 16, 2014 at 12:53 PM, chris snow <[email protected]> > wrote: > >> > >> The puppet installation does not play nicely when installing on a > >> non-dedicated server (e.g. installing alongside stratos in an > >> all-in-one development environment). > >> > >> Currently puppet install forces the hostname to be > >> 'puppet'.${DOMAINNAME}. We should be allowed to override this. > >> > >> I've raised a bug [1] to track this. > >> > >> --- > >> [1] https://github.com/thilinapiy/puppetinstall/issues/5 > > > > > > > > > > -- > > Thanks and regards, > > Thilina Piyasundara. > > > > -- > Check out my professional profile and connect with me on LinkedIn. > http://lnkd.in/cw5k69 > -- Thanks and regards, Thilina Piyasundara.
