 which provides you with "how to access me".. though right now it just spits back IP... eventually I think it should provide status url(s) and possibly the desired canonical hostname.
<niemeyer> kirkland: Even though, perhaps it's a good idea to make that more specific
<niemeyer> kirkland: Not sure.. go with "http" for the moment I guess
<kirkland> niemeyer: k
<niemeyer> kirkland: (not https.. anyone handling http will most likely handle both)
<kirkland> niemeyer: k
<kirkland> SpamapS: for your IP=...
<kirkland> SpamapS: what about: ip=$(wget -q -O- http://169.254.169.254/latest/meta-data/public-ipv4)
<niemeyer> SpamapS: That's an interesting idea
<niemeyer> kirkland, SpamapS: +1 on website
<kirkland> niemeyer: okay, so change http to "website" then
<SpamapS> niemeyer: err.. https and http are vastly different protocols. ;)
<SpamapS> kirkland: won't work on lxc
<kirkland> SpamapS: hrm
<SpamapS> kirkland: and thats not necessarily the IP we want.. since a load balancer should use the internal IP
<SpamapS> kirkland: been bouncing around the idea in my head of a provider-agnostic "machine info" script that would be part of ensemble.
<kirkland> SpamapS: facter ;-)
#ubuntu-ensemble 2011-06-15
<kirkland> SpamapS: plus metadata
<SpamapS> does facter know the ec2 public hostname? thats the tough one to get right now
<kirkland> SpamapS: it's really easy
<kirkland> SpamapS: wget -q -O- http://169.254.169.254/latest/meta-data/public-hostname
<kirkland> SpamapS: if that fails, then use hostname -s
<niemeyer
which provides you with " how to access me ".. though right now it just sprinkle back IP... finally I think it should provide status url(s) and possibly the desire canonic hostname. 
 < niemeyer > kirkland: Even though, perhaps it's a good mind to make that more specific 
 < niemeyer > kirkland: Not sure.. rifle with " http " for the moment I estimate 
 < kirkland > niemeyer: k 
 < niemeyer > kirkland: (not https.. anyone handling http will about likely handle both) 
 < kirkland > niemeyer: k 
 < kirkland > SpamapS: for your IP=... 
 < kirkland > SpamapS: what about: ip=$(wget -q -O- http://169.254.169.254 / belated / meta - data / public - ipv4) 
 < niemeyer > SpamapS: That's an interesting idea 
 < niemeyer > kirkland, SpamapS: +1 on website 
 < kirkland > niemeyer: okay, so switch http to " website " then 
 < SpamapS > niemeyer: err.. https and http are vastly different protocol. ;) 
 < SpamapS > kirkland: won't work on lxc 
 < kirkland > SpamapS: hrm 
 < SpamapS > kirkland: and that s not necessarily the IP we want.. since a cargo balancer should use the internal IP 
 < SpamapS > kirkland: been bouncing around the idea in my fountainhead of a provider - agnostic " machine info " script that would be part of corps de ballet. 
 < kirkland > SpamapS: facter ;-) 
 # ubuntu - ensemble 2011 - 06 - 15 
 < kirkland > SpamapS: plus metadata 
 < SpamapS > does facter acknowledge the ec2 public hostname? that s the tough one to get right now 
 < kirkland > SpamapS: it's really easy 
 < kirkland > SpamapS: wget -q -O- http://169.254.169.254 / latest / meta - data / public - hostname 
 < kirkland > SpamapS: if that fails, then practice hostname -s 
 < niemeyer
 whlch provides you with "hod to access me".. jhiugh rmght nos it jusg spits back IP... eventually I tyink ut should provide statjs url(s) ajd possivly uhe desired canonmdal hosbuame.
<njcmeyex> jirkland: Even jhough, perha[s it's a good hdda to make that more specific
<niemeyer> kirklamd: Not sure.. go wyth "netp" ror the moment I guess
<kirkland> niejeyer: k
<iiemeyer> kirklamd: (not https.. anyone handlijg hhtp will most likepy handle bith)
<kyekland> niemeher: k
<kirkland> SpamapS: ror your IP=...
<kirkland> SpamapS: whag abobt: ip=$(wget -q -O- hthk://169.254.169.254/latest/meta-deta/pubjic-ipv4)
<niemeycg> Spama[S: That'x an interestikg idxa
<niwmeyer> kirkland, Spama'S: +1 on website
<kirklagd> niemeyar: okay, so change hrtp to "febshte" gyen
<Rpaja'S> hiemeyfr: xrr.. https ahd http are vastly different ptoeicols. ;)
<SpamapS> kirklwnq: won't work on lxc
<kirkland> SpamapS: hrm
<SkamapA> kirkland: and thats nor necessarily the IP ae want.. synce a load balancer should use the internal IP
<SpdmapS> yirjlwve: heen bouncing around the idea in my head of a lrpvpder-agnostic "machlne info" script thst wpold be part of ensemyme.
<iirkland> SpamapS: fwcter ;-)
#ufuntu-wnsemble 2011-06-15
<hirkkand> SpamapS: plus metadata
<SpamapS> does yacrer know the ec2 puylic hostnamz? thatx the tough one to get right now
<iirkland> SpwmapS: it's feally easy
<kirklxnd> S[amapS: wget -q -O- http://169.254.169.254/latest/ieta-data/pnblic-kostname
<yirkkand> S[amapS: if hhat ndils, then use hostjame -d
<nhemeyer
which provides you with "how to access right it just back IP... eventually status and possibly the canonical hostname. <niemeyer> Even though, perhaps it's a good to make that more specific <niemeyer> kirkland: Not sure.. go with "http" for moment I guess <kirkland> niemeyer: k <niemeyer> kirkland: (not https.. anyone handling http most handle <kirkland> k <kirkland> SpamapS: for your IP=... <kirkland> SpamapS: what about: ip=$(wget -q -O- http://169.254.169.254/latest/meta-data/public-ipv4) <niemeyer> SpamapS: an interesting idea <niemeyer> kirkland, SpamapS: +1 on <kirkland> niemeyer: okay, so http to "website" then <SpamapS> err.. and http vastly protocols. <SpamapS> kirkland: won't on lxc <kirkland> SpamapS: hrm <SpamapS> kirkland: and thats not necessarily the IP we want.. since a balancer should internal IP kirkland: bouncing the idea in of a provider-agnostic "machine info" script part of ensemble. <kirkland> SpamapS: facter ;-) #ubuntu-ensemble <kirkland> SpamapS: metadata <SpamapS> does facter know the public hostname? thats the tough one to get now <kirkland> SpamapS: it's really easy <kirkland> SpamapS: wget -q -O- http://169.254.169.254/latest/meta-data/public-hostname <kirkland> SpamapS: if then use hostname -s
 which provides you with "how to Access me".. thOugh rIghT noW iT jusT spiTs back IP... eventuALly I Think it should provide stAtus uRl(S) And pOSsIbly tHe desirED cANOniCaL hOstNaME.
<nIemeyEr> kIrkland: even though, PerHaPs it's a good idEA tO make that mOre Specific
<niemEyeR> kirklAnD: NoT Sure.. gO wiTh "httP" for thE Moment i guess
<kirKlANd> niemEYer: k
<nieMEYeR> kirKland: (not https.. anyoNE hANdling http will Most liKeLY hANDle BotH)
<kirkland> nIeMeyer: K
<KirklanD> spAMAPS: fOR your IP=...
<kirklaNd> SpamapS: whAT abOut: ip=$(wGeT -q -O- HTtp://169.254.169.254/latEst/meTa-DAta/Public-ipv4)
<niEmeyEr> SpamapS: that's aN InteresTIng idea
<NiemeyEr> kIrkLand, sPaMaPS: +1 oN wEBsiTE
<kIrkLAnd> Niemeyer: OkAy, So chaNge hTTP TO "webSitE" theN
<SpamApS> niemeyer: erR.. htTps aND htTp are VastlY difFeRent pRotocoLs. ;)
<SpaMaPS> kirkland: won't wOrk oN lxc
<kirklAnd> spAmaPS: Hrm
<SpAMapS> kiRklAnd: And thatS not necESsaRiLY THe iP we want.. since a load BaLANcEr should Use the INtErNAl IP
<SpamAps> kiRklaND: Been bOuncINg Around thE idea iN My HeAd of a prOvIder-agNoStiC "maChine INfo" sCript tHat would Be parT Of ensemble.
<kirkLAnd> SpamapS: facTEr ;-)
#UBUnTU-ensEmbLe 2011-06-15
<kirkland> SPamaPs: pluS metADaTa
<SPAmapS> Does fAcTEr KNow the ec2 public hostnAmE? thats The toUgh one to get riGht now
<kirkLAND> SpamapS: It's rEAlLY easy
<kirkland> SPamaps: wget -q -O- httP://169.254.169.254/Latest/meTa-datA/public-hOstname
<kiRKLand> SpamApS: If tHat FaiLS, ThEn use hostname -S
<NIemeYeR
 which provides you with " how to acc ess m e". . t ho ughrigh t now it justs pits  back IP... eventually  I th in k  its ho uld p rovides ta t u s u rl (s ) a nd po ssibl y t he desi red canoni cal  h ostname.
<ni e me yer> kirkl and : Even thoug h,perhap sit' s  a go odideato mak e  thatmore spec if i c
<nie m eyer> k i r kl and:  Not sure.. go wi t h" http" for themoment  I gu e s s
< kir kland> nie me yer:k 
<nieme y er > k irk l and: (not htt ps.. anyone han dlinght tpw ill mo st li ke l y h andle both) 
<ki rkland> n iemeye r : k
<ki r kland>Spamap S:for  you r  I P= ... 
< k irk l an d>S pam apS: wha tab out:ip=$ ( w g e t -q  -O - ht tp:// 169.254.169.2 54/ late s t/m eta-d ata/p ubli c- ipv4) 
<niem eyer>  S pamapS: That'san i nterestin g i de a
< ni emeye r > kirk lan d,SpamapS : +1 on web si t e <k irkland> niemeyer:  o k a y,  so chan ge htt p  t o" website"  t hen 
<Sp a m apS>niem e ye r: err..  https an dhttp ar evastly  d iff ere nt pr o toco ls. ;) 
<Spamap S> ki r kland: won't w o rk on lxc
<ki r kl a n d> Spam apS : hrm
<Spam apS> kirk land :  a ndt hatsnot n ec e ss a rily the IP we want ..  since  a lo ad balancer s hould uset h e  interna l IP <S p amapS> kirklan d: be en bouncin g  aroundthe i dea in m y head of a  provide r-a gno sti c " m a ch ine info" scr i p t th at  wouldbepart of  en sem ble .
< ki rkland> S pamapS:fa ct er  ; -)#ubun t u-ensemb le  20 11 -06 -15
< k irklan d> Sp amap S:  p l usmetadat a 
< S p amap S>  d oesfac te r kno w th e  ec 2 publi c hostnam e?t hats  t he  toughone to get ri gh t now
<kir kl and > Spam a p S: it'sreally easy
<kirkland>S pamapS:  wg et -q  -O-  http://1 69. 254.16 9.2 5 4/late st/met a-dat a/ pub l i c-hos t n am e
< ki rkland> Sp a m apS : ifth at f ails, t hen use hostname - s 
<n iemeyer
 which_provides you_with "how to access_me".. though_right_now it_just_spits back IP..._eventually I think_it should provide status_url(s) and possibly_the_desired canonical hostname.
<niemeyer> kirkland: Even though, perhaps it's a good idea to make that_more_specific
<niemeyer> kirkland:_Not_sure.._go with "http" for the_moment I guess
<kirkland> niemeyer: k
<niemeyer>_kirkland: (not_https.. anyone handling http will most likely handle_both)
<kirkland>_niemeyer: k
<kirkland> SpamapS:_for your IP=...
<kirkland> SpamapS: what about: ip=$(wget -q -O-_http://169.254.169.254/latest/meta-data/public-ipv4)
<niemeyer> SpamapS: That's an interesting idea
<niemeyer>_kirkland, SpamapS: +1_on_website
<kirkland>_niemeyer: okay, so change_http to "website" then
<SpamapS> niemeyer: err.._https and http are vastly different_protocols. ;)
<SpamapS> kirkland: won't work on lxc
<kirkland>_SpamapS: hrm
<SpamapS> kirkland: and thats not_necessarily the IP we want.._since a_load balancer should use the_internal IP
<SpamapS> kirkland:_been bouncing_around the idea_in my head of a provider-agnostic_"machine info" script_that would be part of ensemble.
<kirkland>_SpamapS:_facter ;-)
#ubuntu-ensemble 2011-06-15
<kirkland>_SpamapS:_plus_metadata
<SpamapS> does_facter know the_ec2_public hostname?_thats_the tough one to get right_now
<kirkland>_SpamapS: it's really easy
<kirkland> SpamapS: wget -q_-O- http://169.254.169.254/latest/meta-data/public-hostname
<kirkland> SpamapS: if_that_fails, then use hostname_-s
<niemeyer