=== rangerpbzzzz is now known as rangerpb
[14:11] <impaque> hey guys, quick question: how can i use the variables provided by the (cloudstack) metadata, such as local-hostname, in my scripts?
[14:11] <impaque> does cloud-init expose them somehow somewhere?
[14:12] <larsks> It does not, currently (wish it did!).  You can talk to the metadata service yourself using a simple HTTP api.
[14:12] <larsks> There is a 'cloud-init query' command, but it appears to be unimplemented at this time.
[14:14] <impaque> larsks: thanks!
[14:14] <impaque> although, i believe they *are* exposed in cloud-config scripts
[14:15] <impaque> from some coreOS page:
[14:15] <impaque> #cloud-config  coreos:   fleet:       public-ip: $public_ipv4       metadata: region=us-west
[14:15] <impaque> (merged to one line, but you get the idea)
[14:15] <impaque> hmmmm
[14:16] <larsks> Note that coreos has their own version of cloud-init.
[14:16] <impaque> ah :/
[14:32] <smoser> larsks, yeah, we need cloud-init query
[14:32] <smoser> so... impaque we will fix that for you in 2.0... its in the plans.
[14:32] <smoser> cloud-inti will expose (via json or versioned python module/access) objects to get you that stuff.
[14:36] <impaque> smoser: so basically, the only way to get that meta-data is by writing a module, if i get that correclty, via cloudinit.util?
=== zz_natorious is now known as natorious
=== natorious is now known as zz_natorious
=== zz_natorious is now known as natorious
[16:24] <weaseal> does anyone know if it is possible to detect AWS resources such as RDS, ELB, etc by only feeding in a VPC ID?
[16:24] <weaseal> using cloud-init
[17:40] <smoser> "detect" ?
=== natorious is now known as zz_natorious
=== zz_natorious is now known as natorious
=== rangerpb is now known as rangerpbzzzz