3
\mei @ s U d Z ddlZddlZddlmZ ddlmZmZmZ ddl m
Z
ddl m Z ddl
mZmZ ddlmZ ejeZeZd gZd
d d ed
eedgedgdZeeeZ ee e
eddddZdS )z:Bootcmd: run arbitrary commands early in the boot process. N)dedent)subp
temp_utilsutil)Cloud)Config)
MetaSchema get_meta_doc)
PER_ALWAYSallZ
cc_bootcmdZBootcmdz0Run arbitrary commands early in the boot processa This module runs arbitrary commands very early in the boot process,
only slightly after a boothook would run. This is very similar to a
boothook, but more user friendly. The environment variable
``INSTANCE_ID`` will be set to the current instance id for all run
commands. Commands can be specified either as lists or strings. For
invocation details, see ``runcmd``.
.. note::
bootcmd should only be used for things that could not be done later
in the boot process.
.. note::
when writing files, do not use /tmp dir as it races with
systemd-tmpfiles-clean LP: #1707222. Use /run/somedir instead.
z bootcmd:
- echo 192.168.1.130 us.archive.ubuntu.com > /etc/hosts
- [ cloud-init-per, once, mymkfs, mkfs, /dev/vdb ]
bootcmd)idnametitle descriptiondistrosZexamples frequencyZactivate_by_schema_keys)r cfgcloudargsreturnc
C s d|krt jd| d S tjdd}y*tj|d }|jtj| |j W n6 t k
r } ztj
t dt | W Y d d }~X nX y@t j
j }|j }|rt ||d< d|jg} tj| |dd W n$ t k
r tj
t d
| Y nX W d Q R X d S ) Nr z;Skipping module named %s, no 'bootcmd' key in configurationz.sh)suffixz Failed to shellify bootcmd: %sZ INSTANCE_IDz/bin/shF)envZcapturez Failed to run bootcmd module %s)LOGdebugr ZExtendedTemporaryFiler ZshellifywriteZ encode_textflush ExceptionZlogexcstrosenvironcopyZget_instance_idr r )
r r r r ZtmpfZcontenter Ziidcmd r$ /usr/lib/python3.6/cc_bootcmd.pyhandleD s,
r& )__doc__Zloggingr textwrapr Z cloudinitr r r Zcloudinit.cloudr Zcloudinit.configr Zcloudinit.config.schemar r Zcloudinit.settingsr
Z getLogger__name__r r r metar listr& r$ r$ r$ r%
s.