PNG  IHDR;IDATxܻn0K )(pA 7LeG{ §㻢|ذaÆ 6lذaÆ 6lذaÆ 6lom$^yذag5bÆ 6lذaÆ 6lذa{ 6lذaÆ `}HFkm,mӪôô! x|'ܢ˟;E:9&ᶒ}{v]n&6 h_tڠ͵-ҫZ;Z$.Pkž)!o>}leQfJTu іچ\X=8Rن4`Vwl>nG^is"ms$ui?wbs[m6K4O.4%/bC%t Mז -lG6mrz2s%9s@-k9=)kB5\+͂Zsٲ Rn~GRC wIcIn7jJhۛNCS|j08yiHKֶۛkɈ+;SzL/F*\Ԕ#"5m2[S=gnaPeғL lذaÆ 6l^ḵaÆ 6lذaÆ 6lذa; _ذaÆ 6lذaÆ 6lذaÆ RIENDB` # cloud-config.target is the earliest synchronization point in cloud-init's # boot stages that indicates the completion of datasource detection (cloud-id) # and the presence of any meta-data, vendor-data and user-data. # Any services started at cloud-config.target will need to be aware that # cloud-init configuration modules have not yet completed initial system # configuration of cloud-config modules and there may be race conditions with # ongoing cloud-init setup, package installs or user-data scripts. # Services that need to start at this point should use the directives # "After=cloud-config.target" and "Wants=cloud-config.target" as appropriate. # To order services after all cloud-init operations, see cloud-init.target. [Unit] Description=Cloud-config availability Wants=cloud-init-local.service cloud-init.service After=cloud-init-local.service cloud-init.service