Commit Graph

8 Commits

Author SHA1 Message Date
Nahum Shalman
6af019d7cf smartos esky: improve "installer"
detect if this is a global or non-global zone
global zones are always minions

if the user passes in the name/address of the master
we configure a minimal minion file and launch the minion
2014-05-08 12:04:22 -04:00
Nahum Shalman
e62862f992 update documentation about SmartOS esky packaging 2014-02-25 19:27:39 -05:00
Nahum Shalman
3c179c2a41 SmartOS esky packaging: minor fixup
Don't assume that the top directory is named "salt"
The user might choose to name it "salt-<version>"
or "saltstack" or whatever else.

install.sh is already that flexible; this fixes _syspaths.py
2014-01-24 09:47:37 -05:00
Nahum Shalman
9f2a19ef05 SmartOS Esky Packaging: Fix PATH for services
We ran into some weird issues with these SMF manifests
with certain critical binaries not being found in the PATH.

This PATH is derived from root's default PATH when logging
in to a SmartOS zone.
2014-01-23 15:31:44 -05:00
Nahum Shalman
e94f42449a SmartOS esky build tooling
This includes:
Notes on how I created a build environment
The _syspaths.py that allows the esky build to be installed anywhere
"Template" SMF manifests and an install script to import them
A script for building both the esky zip and a deployable tarball
2014-01-05 11:20:24 -05:00
mguegan
8ba8138bc4 pkg/smartos : fix the manifest of salt-master to start@boot 2013-05-30 20:33:16 +02:00
mguegan
89de6a1606 smartos : change default config directory for Salt services 2013-05-20 13:00:38 +02:00
mguegan
737b4e0fb2 pkg/smartos : add compatible manifests for the SmartOS platform
Manifests in pkg/solaris are using /etc/salt which is innapropriate
for SmartOS design (/etc is removed @reboot). I suggest to add a
new directory in order to preserve existing Solaris installations
(and SmartOS one which are based on those manifests).
2013-05-13 22:17:35 +02:00