Salt-bootstrap: VMware's Photon OS support

[nickgarber]

A related request is documented in the Salt/Salt project at [ref:1].

[ref:1]
https://github.com/saltstack/salt/issues/41921

[rallytime]

@nickgarber Apologies for not commenting on this sooner. Thanks for the request. I don't think this is something that we can pick up ourselves right now, but if someone from the community wants to implement it, great! As such, I have approved this as a feature request.

[nickgarber]

Hi @rallytime, no worries!

Here are the quick notes I took while setting this up recently. It should
help people to know that it's possible and not complicated to accomplish.
In these notes I used Salt's develop branch, but much of these instructions
could be adjusted and refactored to produce something much more
straight-forward. I'll revisit and clean this up myself unless someone
beats me to it.

procedure :: howto, install Salt on VMware Photon

• nb, the package managed is tdnf

• install Python and Pip

  • install python if is isnt already tdnf install python git pycrypto python-zmq
  • install Python module dependencies
  • install pip cd $(mktemp -d) && curl -O https://bootstrap.pypa.io/get-pip.py && python get-pip.py
  • install python if is isnt already tdnf install python
  • clone from upstream Salt at Github git clone --depth 1 --single-branch https://github.com/saltstack/salt
  • enter the working directory and install using setup.py python setup.py install
  • this install method doesnt include a service unit, so we'll add that now
    cat > /etc/systemd/system/salt-minion.service <<EOF [Unit] Description=The Salt Minion After=network.target [Service] Type=notify NotifyAccess=all LimitNOFILE=8192 ExecStart=/bin/salt-minion [Install] WantedBy=multi-user.target EOF
  • nb, when relying on DNS to identify the salt master, some explicit
    configuration may require additional editing
    # /etc/resolv.conf nameserver 192.168.1.1 nameserver 192.168.1.2 search mydomain.tld

  • (opt.) if DNS is not fully adequate, you can explicitly set the IP address of the Salt Master as below

    cat > /etc/salt/minion.d/master.conf <<EOF
    master: 192.168.1.100
    
    EOF
    

  • starting the salt-minion.service for the first time will create the file and folder structure under /etc/salt
  • verify a/o set the minion_id in /etc/salt/minion_id as/is desired echo exmpl-web-t1.mydomain > /etc/salt/minion_id
  • start the service systemctl enable --now salt-minion

[padmini-st]

Hi @nickgarber, this is what I was looking for. Very helpful.
Could I request to list out the steps for Photon OS for Salt-master as well.

Thanks

[nickgarber]

To run a salt-master on a container-host OS like Photon, why not run it in
a container?

That said, if running a salt-master on the "host" OS is important, it's
certainly possible. I haven't tried it but I believe setting up a
salt-master from source would share many steps with the salt-minion setup.

On Thu, Oct 5, 2017 at 6:59 AM padmini-st [e-mail] wrote:

Hi @nickgarber https://github.com/nickgarber, this is what I was
looking for. Very helpful.
Could I request to list out the steps for Photon OS for Salt-master as
well.

Thanks

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/saltstack/salt-bootstrap/issues/1106#issuecomment-334431769,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACHrcCFrRvWu4pn03N_j3grprzUAdhy-ks5spLaPgaJpZM4OD6qA
.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

[nickgarber]

Please leave this open. Time permitting I believe I could implement this
myself. The issue will let others know that an interest in the feature has
already been registered and that they can contribute or inquire about
status.

On Thu, Apr 5, 2018 at 9:21 PM stale[bot] [e-mail] wrote:

This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Thank you
for your contributions.

If this issue is closed prematurely, please leave a comment and we will
gladly reopen the issue.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/saltstack/salt-bootstrap/issues/1106#issuecomment-379122230,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACHrcKq0DA-O3Xdc8NHrGzGIWBQHvogtks5tlsMQgaJpZM4OD6qA
.

[stale[bot]]

Thank you for updating this issue. It is no longer marked as stale.

[rach-sharp]

As a couple of extra notes following the process above, I also had to install python-xml before I could install pip using get-pip.py. Once I'd cloned the main branch I also had to explicitly install dependencies from requirements/base.txt as well as run setup.py.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

[nickgarber]

I'd like to motion for postponement, (for the final time), in hopes I'll be able to contribute this myself.

[stale[bot]]

Thank you for updating this issue. It is no longer marked as stale.

[rallytime]

Sounds good @nickgarber! Thanks!

[lomeroe]

additionaly, the "photon-updates" repo (1.0) has a 2017.7.2 version of the salt packages in it...obviously a little behind, but is at least a fully tdnf managed package and seems to work as expected

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.