VMware Photon OS
Photon OS, is an open-source minimalist Linux operating system from VMware that is optimized for cloud computing platforms, VMware vSphere deployments, and applications native to the cloud. Photon OS is a Linux container host optimized for vSphere and cloud-computing platforms such as Amazon Elastic Compute and Google Compute Engine. More info is available https://vmware.github.io/photon/assets/files/html/3.0/Introduction.html.
The ITS Private Cloud supports VMware Photon OS and offers two deployment methods: as OVF in our Public Content Library and as ISO file to proceed with manual installation. Deploying a VM via the content library is the quickest method to get a VM up and running in matter of minutes. However, customizing the operating system may get complex sometimes. To speed up the deployment and configuration, the minimal and full versions of Photon OS include the cloud-init
service as a built-in component.
cloud-init
is a set of Python scripts that initialize cloud instances of Linux machines to customize the instance without user interaction. The commands can set the root password, set a hostname, configure networking, write files to disk, upgrade packages, run custom scripts, and restart the system.
In the ITS Private Cloud, cloud-init
has been used by the community for many years now, however it focused mostly on Ubuntu OS by implementing the Cloud-Init seed
ISO data source, which creates a ISO image with both user-data and metadata files then read by cloud-init
). In this tutorial we demonstrate the power of cloud-init's VMware
datasource using VM’s guestinfo
interface with the vss-cli
.
VMware guestinfo
Interface
The data source is configured by setting guestinfo
properties on a VM's extra-config
data listed in the following table:
Property | Description |
---|---|
| A YAML or JSON document containing the cloud-init metadata. |
| The encoding type for |
| A YAML document containing the cloud-init user data. |
| The encoding type for |
| A YAML document containing the cloud-init vendor data. |
| The encoding type for |
All guestinfo.*.encoding
property values may be set to base64
or gzip+base64
.
ITS Private Cloud Command Line Interface vss-cli
The vss-cli
allows you to set custom extra configuration settings in most of the compute vm mk *
subcommands via the --extra-config
option. Providing multiple key=value
items, allows you to set any guestinfo.*
property directly from the deployment process, i.e.:
vss-cli compute vm mk from-clib --extra-config guestinfo.metadata.encoding=gzip+base64 ....
\uD83D\uDCD8 Instructions
The following steps guides you through the configuration of a VM deployed from the Content Library
with cloud-init
and the VMware datasource.
Login to the
vsscli-demo.eis.utoronto.ca
or https://vss-cli.eis.utoronto.ca or with your localvss-cli
installation.If running a local install, make sure you are running the latest
vss-cli
version viavss-cli upgrade
.
Create a
userdata.yaml
with all the users, packages and custom settings that you plan to use (examples are available https://cloudinit.readthedocs.io/en/latest/topics/examples.html ):#cloud-config hostname: its-cloud-vm1 timezone: America/Toronto fqdn: its-cloud-vm1.eis.utoronto.ca chpasswd: list: | root:your_secure_password_here expire: False users: - name: root lock_passwd: true - name: vss-user sudo: ALL=(ALL) NOPASSWD:ALL passwd: $6.... groups: sudo, wheel lock_passwd: true ssh_authorized_keys: - ssh-rsa AAAA.... packages: - git - sudo - net-utils write_files: - path: /etc/motdgen.d/001-motd-vss.sh permissions: '0755' content: | #!/bin/bash INSTANCE_ID=`vmware-rpctool "info-get guestinfo.ut.vss.instance.id"` INSTANCE_NAME=`vmware-rpctool "info-get guestinfo.ut.vss.instance.name"` printf "\n" printf " University of Toronto ITS Private Cloud Instance\n" printf "\n" printf " Name: $INSTANCE_NAME\n" printf " ID: $INSTANCE_ID\n" printf "\n" package_update: true package_upgrade: true package_reboot_if_required: true power_state: delay: now mode: reboot message: Rebooting the OS condition: if [ -e /var/run/reboot-required ]; then exit 0; else exit 1; fi # Optional: Cleanup guestinfo.userdata* and guestinfo.vendordata* # uncomment the following lines to enable. # cleanup-guestinfo: # - userdata # - vendordata final_message: "The system is finally up, after $UPTIME seconds"
Note that
passwd
hash is required to update the root password or any other user password. Thevss-cli
has the utility to hash strings:vss-cli misc hash-string NewPassword123
Create
metadata.yaml
with the instance and networking configuration :instance-id: its-cloud-vm1 local-hostname: its-cloud-vm1 network: version: 2 ethernets: nics: match: name: ens* dhcp4: yes
More examples can be found https://cloudinit.readthedocs.io/en/latest/topics/network-config-format-v2.html#examples
Run the following command to deploy instance assigning the
userdata.yaml
andmetadata.yaml
encoded as specified in theguestinfo.*.encoding
option.vss-cli --wait compute vm mk from-clib \ --memory 1 --cpu 1 \ --source vmware-photon-ova_uefi-4.0 \ --disk 10 \ --description 'Photon server' \ --client EIS --os photon --usage Prod \ --folder group-v4122 --net EIS-VSS-CGN \ --extra-config guestinfo.metadata.encoding=gzip+base64 \ --extra-config guestinfo.userdata.encoding=gzip+base64 \ --extra-config guestinfo.userdata=$(vss-cli misc gz-b64e userdata.yaml) \ --extra-config guestinfo.metadata=$(vss-cli misc gz-b64e metadata.yaml) \ --power-on vss-photon
Note that you should replace the
--folder
option value with a folder you have access to.
When the previous command completes, you should get the allocated IP address in the “warnings” section:
id : 6996 status : IN_PROGRESS task_id : bcf49812-64f0-4cdb-a0f2-5245312572ac message : Request has been accepted for processing ⏳ Waiting for request 6996 to complete... 🎉 Request 6996 completed successfully: warnings : Fault Domain: FD4 (domain-c66), Created in: VSS > Sandbox > jm (group-v4122), Network adapter 1 (vmxnet3): 00:50:56:92:d9:36: VL-0253-EIS-VSS-CGN, Successfully powered on., Successfully allocated 00:50:56:92:d9:36 -> 100.76.42.91 errors :
If all went well, you should be able to login via the allocated IP address included in the email and ssh access should available:
ssh vss-user@100.76.42.91 The authenticity of host '100.76.42.91 (100.76.42.91)' can't be established. ED25519 key fingerprint is SHA256:9QCX5IYOc....FFnemF99KaXRZVoIY. This key is not known by any other names Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added '100.76.42.91' (ED25519) to the list of known hosts. University of Toronto ITS Private Cloud Instance Name: 2210P-vss-photon ID: vm-589164 21:03:06 up 9 min, 0 users, load average: 0.00, 0.01, 0.00 tdnf update info not available yet!
There you go! We have a fully functional pre-configured virtual machine with UEFI and secure boot ready for action. 🚀
Cleaning up
If you did not include the cleanup-guestinfo
directive in the userdata.yaml
descriptor for debugging purposes, now that the OS is running and configured, it is recommended to manually cleanup the guestinfo.userdata*
and guestinfo.vendordata*
with the following commands:
vmware-rpctool "info-set guestinfo.userdata ---" vmware-rpctool "info-set guestinfo.userdata.encoding " vmware-rpctool "info-set guestinfo.vendordata ---" vmware-rpctool "info-set guestinfo.vendordata.encoding "
Verify with the following commands:
vmware-rpctool "info-get guestinfo.userdata" vmware-rpctool "info-get guestinfo.userdata.encoding" vmware-rpctool "info-get guestinfo.vendordata" vmware-rpctool "info-get guestinfo.vendordata.encoding"