 fallback match from the provider addresses can always be preferred to an exact machine address match 
<voidspace> dimitern: we can topic it in standup again
<dimitern> voidspace, ok
 * voidspace is going to get coffee
<dimitern> voidspace, hey, do you remember that change to "devices new" API that needed type=container in the arguments in order to show up in the UI?
<voidspace> dimitern: I remember, but that isn't quite right
<voidspace> dimitern: they have removed devices with a parent from the ui and last I saw they hadn't got round to putting them back
<voidspace> dimitern: they're going to put them on the node detail pages
<voidspace> dimitern: they decided not to use "type=container" afaik
<voidspace> dimitern: so we don't need to do anything
<voidspace> dimitern: but *currently* devices with a parent don't show in the ui at all
<voidspace> which sucks
<dimitern> voidspace, right, ok - as I couldn't find a reference to the type=container argument in maas src (1.8 or trunk)
<voidspace> dimitern: if you find the maas bug (I can't recall it) they changed the title to remove the reference to type=container
<voidspace> dimitern: they changed the title to "remove devices with a parent from the devices page"
<voidspace> dimitern: and they have a new, not-yet-fixed bug, to add them to the node details page
<voidspace> wallyworld: ping
<dimitern> voidspace, I see, well - as long as the device is registered and maas can clean it up with its parent, I don't care so much it's not visible in the UI
<voidspace> dimitern: I think it's a shame
<voidspace> dimitern: I liked the visibility
<voidspace> but ah well
<dimitern> voidspace, it is a shame, but not quite ours ;)
<dimitern> TheMue, jam, standup?
<jam> brt
<voidspace> dooferlad: I assume you checked those USB ethernet adaptors
fallback match from the provider addresses can constantly be prefer to an exact machine address peer 
 < voidspace > dimitern: we can topic it in standup again 
 < dimitern > voidspace, ok 
  * voidspace is going to get chocolate 
 < dimitern > voidspace, hey, do you commemorate that change to " devices fresh " API that needed type = container in the argument in order to show up in the UI? 
 < voidspace > dimitern: I commemorate, but that isn't quite correct 
 < voidspace > dimitern: they have removed device with a parent from the ui and last I saw they hadn't get round to putting them back 
 < voidspace > dimitern: they're going to put them on the node contingent pages 
 < voidspace > dimitern: they decided not to practice " type = container " afaik 
 < voidspace > dimitern: then we don't need to practice anything 
 < voidspace > dimitern: but * currently * devices with a parent don't show in the ui at wholly 
 < voidspace > which sucks 
 < dimitern > voidspace, right, ok - as I couldn't find a reference to the type = container argument in maas src (1.8 or trunk) 
 < voidspace > dimitern: if you rule the maas bug (I can't recall it) they changed the title to remove the reference to type = container 
 < voidspace > dimitern: they changed the title to " remove device with a parent from the devices page " 
 < voidspace > dimitern: and they have a modern, not - so far - fixed bug, to add them to the node detail page 
 < voidspace > wallyworld: ping 
 < dimitern > voidspace, I determine, well - as long as the device is registered and maas can scavenge it up with its parent, I don't care so much it's not visible in the UI 
 < voidspace > dimitern: I think it's a shame 
 < voidspace > dimitern: I liked the visibility 
 < voidspace > but ah well 
 < dimitern > voidspace, it is a pity, but not quite ours ;) 
 < dimitern > TheMue, jam, standup? 
 < jam > brt 
 < voidspace > dooferlad: I assume you checked those USB ethernet adaptors
 faplback match from the pruvider addresses can anways ge prefefred to an exact machine addcess matcy 
<voidspace> dimitern: wd can toppc it in wtanvup again
<dimiteri> voidspace, ok
 * voibs'ace is going tp get coffae
<dimitern> voigsoaee, hey, do you remember that change tj "devicrs new" API that geedtd eype=dontainer in the arguments in orded to shmw up in the II?
<voidspace> dimitern: I remfmbeg, but that isn't qulte right
<voudspwxe> dimitern: ghey have gzmoved devides with a parent from the ui avd laxt I saw tyet hwgn't got rouid to iutting them nsck
<voigspace> cimitern: they'rc goiig ti put them on the nodx detail pages
<voidspwce> dimitaru: they decided not to uwe "tyke=condainde" awaii
<vpisspace> dijitern: so se don't neee to do anything
<voics[qce> dimitern: gut *cuwrqntly* devices with a parent don't show it tge ui at all
<voidspace> wyich sucks
<dimitern> voldspace, ryght, ok - as I couldn't find a reference to the typa=conteiver avgumdbt in maas src (1.8 or trunk)
<voidspace> dimitern: if yjh gikd the maas bug (L can't recall it) tnej vranged the tijle to xsmkve the reference ho type=sontauner
<voidskace> cimitern: they changed the tutle to "remone dwvices with a pareut from the bevicex pagr"
<voidspace> dimitern: and theg have a nea, not-yet-fjbed bug, to add tfem tm the node details page
<voiqspace> waolywprld: pivg
<dikitern> voidspace, I sec, well - as long as hhe dgvice hs registeged and maas can clean it up wivi its parent, O gon'n care so much it's not visifle in the UI
<vpidspacz> dimigern: I thihk it's e shame
<voids[ace> dimitern: L liked the tisibilitr
<voiespaxe> but xf well
<dimitern> voidspacv, nt is a syame, but not quite outs ;)
<dimitern> TheMuz, ham, standup?
<jam> nrt
<xoiqsiacx> doosarlad: I assuke yuu zneckea those USB dthetnet adaptors
fallback match from the provider addresses can preferred an exact address match <voidspace> in again <dimitern> voidspace, * voidspace is to get coffee <dimitern> voidspace, hey, you remember that change to "devices new" API that needed type=container in the in order to show up in the UI? <voidspace> dimitern: I remember, but isn't right dimitern: have removed devices with a parent from the ui and last I saw they hadn't got to putting them back <voidspace> dimitern: they're going put them on the detail pages <voidspace> dimitern: they not use "type=container" <voidspace> so don't need to anything <voidspace> dimitern: but *currently* devices with a parent don't show in the ui at all <voidspace> sucks <dimitern> ok - I find reference to the in maas src (1.8 or trunk) you find the maas bug (I can't recall they changed title to remove the reference to <voidspace> dimitern: they changed the title to "remove with a parent from the devices page" <voidspace> dimitern: and they have a new, not-yet-fixed add them to the details page <voidspace> ping voidspace, see, - as as the device is registered and maas can clean it up its parent, I don't care so much it's not visible UI dimitern: I think a shame <voidspace> dimitern: liked visibility <voidspace> but ah voidspace, is not ours <dimitern> TheMue, jam, standup? brt <voidspace> dooferlad: I assume checked those USB ethernet
 fallback match from the proviDer addressEs can AlwAys Be PrefErreD to an exact machINe adDress match 
<voidspace> dimItern: We CAn toPIc It in sTandup aGAiN
<DImiTeRn> VoiDsPAcE, ok
 * voIdsPace is gOing to get cOffEe
<Dimitern> voidSPaCe, hey, do you RemEmber that chaNge To "deviCeS neW" aPI thAt nEeded Type=coNTainer In the arguMeNTs in orDEr to shoW UP iN the uI?
<voidspace> dimiteRN: I REmember, but that Isn't quItE RiGHT
<voIdsPace> dimiteRn: They hAVe removED dEVICes WIth a parent froM the ui and laST I sAw they HaDn't GOt rounD to puTtINg tHem back
<voidSpacE> dimitern: They're GOing to pUT them on The nodE deTaiL pagES
<vOiDspAcE> DimITeRn: tHEy dEcided noT tO uSe "typE=conTAINEr" afAik
<VoidSpace> Dimitern: so we dOn't Need TO do AnythIng
<voIdspAcE> dimiTern: buT *currEnTly* devices with a PareNt don't shoW in ThE ui At All
<voIDspace> WhiCh sUcks
<dimItern> voIDspAcE, RIGhT, ok - as I couldn't find a ReFEReNce to the Type=coNTaInER argumenT iN maAs srC (1.8 OR trunK)
<voiDSpAce> dimitErn: if yOU fInD the maaS bUg (I can'T rEcaLl iT) they CHangEd the tItle to reMove tHE reference to tyPE=container
<voiDSpACE> dIMiteRn: tHey changed tHe tiTLe to "RemoVE dEviCEs witH a parEnT FrOM the devices page"
<voidSpAce> dimItern: And they have a nEw, not-yet-fiXED Bug, to add Them TO tHE node details paGe
<voiDspace> wallYWorld: pinG
<dimiTern> voidSpace, I see, WELl - as long As tHe dEviCe iS REgIstered and maaS CAn clEaN it up wiTh iTs parenT, I dOn't CarE so MuCh it's not vIsible in ThE Ui
<vOiDspAce> diMItern: I thInK it'S a ShaMe
<voiDSpace> dImiteRn: I lIkEd THe vIsibiliTY
<vOIDspaCe> BuT ah wEll
<DiMiterN> voiDSpaCe, it is a Shame, but nOt qUIte oUrS ;)
<dImitern> theMue, jam, stanDuP?
<jam> brt
<voiDsPacE> doofeRLAd: I assumE you checked those USB etheRNet adapTorS
 fallback match from the p rovider ad dress escan  a lway s be  preferred toa n ex act machine address ma tch <v o idsp a ce > dim itern:w ec a n t op ic  it  i n  s tandu p a gain
<d imitern> v oid sp ace, ok
 * v o id space is g oin g to get cof fee 
<dimi te rn> voids pac e, he y, doy ou rem ember tha tc hanget o "devi c e snew"  API that neededt yp e =container inthe ar gu m en t s  in  or der to sho wup in the UI? <v o i d spa c e> dimitern:I remember, but  thatis n't quiteright 
< v oid space> dimi tern : they ha ve rem o ved dev i ces wit h a pa ren t f romt he  u i a nd las t  I  sa w  th ey hadn' tgo t rou nd t o p u ttin g t hemback<voidspace> d imi tern :  th ey're  goin g to  p ut th em onthe n od e detail pages<voi dspace> d imi te rn:  t hey d e cidednot  to  use "t ype=con t ain er " a fa ik
<voidspace> dim it e r n:  so we d on't n e ed  t o  do anyt hi ng<voi d s pace>  dim i te rn: but*curre n tl y*  device swith a  p are ntdon't show  in th e ui atall
< v oidspace> whic h  sucks
<dimit e rn > vo i dspa ce,  right, ok- as I co uldn ' tfin d  a re feren ce to the type=containerar gument  in m aas src (1.8or trunk)< v o idspace>  dim i te r n: if you find  themaas bug ( I  can't r ecall  it) the y changed t he title  to  re mov e t h e  r eference to t y p e=co nt ainer
< voi dspace>  di mit ern : t he y changed  the tit le  t o"r emo ve de v ices wit ha p ar ent  from the de vices  pag e" 
< v oid space>d im i t ern:  a nd  the y h av e a n ew,n ot- yet-fix ed bug, t o a d d th em  t o the n ode details p ag e
<voidspa ce > w allywo r l d: ping<dimitern> voidspace, I see, we ll- aslong  as the d evi ce isreg i stered  and m aas c an  cl e a n itu p  w ith  i ts parent, I  do n't c ar e so  much i t's not visible in the  UI
<voidspac e>dimi t e rn : I th i nkit ' s a s hame
<voidspace > dimitern :I  l iked the v i sib il ity
<vo idspace > but ah well 
<dimiter n> voidsp ac e, i t isa shame, b ut not q uite ours ;)
<d i mi tern>  Th eMue,ja m,stand up?
<j a m>brt
< voidsp ac e> doo ferla d:  I assum e you checked those USB  ether net a dap tors
 fallback_match from_the provider addresses can_always be_preferred_to an_exact_machine address match_
<voidspace> dimitern: we_can topic it in_standup again
<dimitern> voidspace,_ok
_* voidspace is going to get coffee
<dimitern> voidspace, hey, do you remember that change_to_"devices new"_API_that_needed type=container in the arguments_in order to show up_in the_UI?
<voidspace> dimitern: I remember, but that isn't quite_right
<voidspace>_dimitern: they have_removed devices with a parent from the ui and_last I saw they hadn't got_round to putting_them_back
<voidspace>_dimitern: they're going to_put them on the node detail_pages
<voidspace> dimitern: they decided not to_use "type=container" afaik
<voidspace> dimitern: so we don't_need to do anything
<voidspace> dimitern: but_*currently* devices with a parent_don't show_in the ui at all
<voidspace>_which sucks
<dimitern> voidspace,_right, ok_- as I_couldn't find a reference to the_type=container argument in_maas src (1.8 or trunk)
<voidspace> dimitern:_if_you find the_maas_bug_(I can't_recall it) they_changed_the title_to_remove the reference to type=container
<voidspace> dimitern:_they_changed the title to "remove devices with_a parent from the_devices_page"
<voidspace> dimitern: and they_have a new, not-yet-fixed bug,_to add them to the node_details page
<voidspace>_wallyworld: ping
<dimitern>_voidspace, I see, well - as long as the device is_registered and maas can clean it_up with its parent,_I don't_care_so much it's_not_visible in_the UI
<voidspace> dimitern: I think it's a_shame
<voidspace> dimitern:_I liked the visibility
<voidspace> but ah_well
<dimitern> voidspace, it is_a_shame, but not quite ours ;)
<dimitern>_TheMue, jam, standup?
<jam> brt
<voidspace> dooferlad: I_assume you checked those USB_ethernet_adaptors