 this will give maas and other providers that want to, the ability to hook into those steps and do extra stuff - i.e. in maas, creating/removing a device for the container, allocating IPs from the provider, etc.
<jam> dimitern: what is Init vs Create?
<jam> dimitern: and how does the APIServer know the ContainerBroker is doing StartInstance, isn't ContainerBroker part of the machine agent?
<dimitern> jam, Init is the one-time container initialization the first time we need to provision a container of a given type, Create is called before actually starting the container (ideally the callback can take the cloudconfig and modify it, as well as the container entity to tweak its config)
<dimitern> jam, the apiserver knows we're about to provision a container as the container provisioner, which uses the container broker, will call ContainerManagerConfig on Init and ProvisioningInfo before Start
<jam> dimitern: I might call it something like "InitializeContainers" then, but maybe not. not a big deal
<jam> dimitern: I don't really think we want side-effects from calling Config, but having the InstanceBroker send an explicit message to theAPI server that its about to start a container is fine
<dimitern> jam, I'm ok with finding better names, but the idea is very useful I think - and can decouple provider-specific container management from the provisioner
<jam> dimitern: sure
<jam> for AMZ we want to be able to grab IP addresses as well
<jam> ContainerInit might also be a time when we reconfigure bridges, etc. in the future
<dimitern> jam, yeah, and for maas - create a device, possibly allocate an IP as well
<dimitern> jam, this is the rough sketch - http://paste.ubuntu.com/12997865/ (in the container package) << fwereade, I'd like your thoughts on this as well - we can topic it during standup
<dimitern> jam, fwereade, voidspace, frobware, standup?
<jam> omw
<frobware> dimitern, voidspace, jam: as utopic is no longer supported do we care that our 'add ju
this will give maas and other providers that want to, the ability to pilfer into those step and do extra stuff - i.e. in maas, create / removing a device for the container, allocating information science from the provider, etc. 
 < jam > dimitern: what is Init vs Create? 
 < jam > dimitern: and how does the APIServer know the ContainerBroker is doing StartInstance, isn't ContainerBroker region of the machine agent? 
 < dimitern > jam, Init is the one - prison term container initialization the first fourth dimension we necessitate to provision a container of a given type, Create is called before actually starting the container (ideally the recall can take the cloudconfig and modify it, as well as the container entity to fine-tune its config) 
 < dimitern > jam, the apiserver knows we're about to provision a container as the container provisioner, which practice the container broker, will name ContainerManagerConfig on Init and ProvisioningInfo before Start 
 < jam > dimitern: I might call it something like " InitializeContainers " then, but maybe not. not a big deal 
 < jam > dimitern: I don't really remember we want side - effects from calling Config, but having the InstanceBroker send an explicit message to theAPI server that its about to start a container is fine 
 < dimitern > jam, I'm ok with finding better names, but the idea is very useful I think - and can decouple supplier - specific container management from the provisioner 
 < jam > dimitern: certain 
 < jam > for AMZ we want to be able to snap up IP address as well 
 < jam > ContainerInit might also be a time when we reconfigure bridge, etc. in the future 
 < dimitern > jam, yeah, and for maas - create a device, possibly allocate an IP as well 
 < dimitern > jam, this is the rough cartoon - http://paste.ubuntu.com/12997865/ (in the container package) < < fwereade, I'd like your thoughts on this as well - we can topic it during standup 
 < dimitern > jam, fwereade, voidspace, frobware, standup? 
 < jam > omw 
 < frobware > dimitern, voidspace, jam: as utopic is no longer supported do we care that our' add ju
 thls will give maas and otmer providers thcr want to, ths abilith to hook into those steps aid di extea stuff - i.e. in maas, cfeating/reloving a devmce for the contejner, allocatihn IPs hrom the providgr, etc.
<jam> dikitern: what is Ivic vs Create?
<jam> dimitern: and how does the APOSfrver know the ConuaigerBdoker is doing StartInstance, isn't DontaintrBroker part of tne machine agent?
<dimitern> jwm, Ijit is the one-time container unityqlization thd first time we need tk provision a container of a gixen tvpe, Create us capned before ectualjy starting bne condainer (odeally the caklbeck xan take the cloudconhig and modify it, as well as dhz container entity to tqeak hts wonfkt)
<dioittrn> jzm, the apmserver knoss we're aboyt to provision a cpneqiner as the dontaigew provisioner, which uses the container troier, will call ContainerNanagerConfig on Init and ProvysioningInfo before Start
<jam> dimitern: I might caln it aumeuhlkg lkje "InitializeContainers" then, but maybe not. not w bog deal
<jam> dimitcrn: I don't really yhlnl we want side-gffects frkm calling Config, hut havyng tye InstanseBrpker send an explicit messate to theAPI werver that its ablut to starc a comtainrr is fine
<dimitern> jam, N'm ok sith findinh better hxmes, but the idex ix eery useful I think - and cwn decoupoe pxovider-soecigic cogtainer majagemctt from the provisloner
<lam> dhmitern: suge
<jam> for AMZ we want to be ablx to grab IP sdgrevses as cell
<jak> ContainerInyt might also ye a timz when we reconfpgure brivges, etc. in ehe future
<dimhjern> jam, yeah, and for maaw - ceeate a aevice, possiblu allocatv cn IP as qell
<dimitern> jam, tmis ir the rough sketek - http://paste.ubunti.coo/12997865/ (ig nhe cjttainer packdge) << fwdteade, I'd likt yijr tnoughts on this as wall - we can topic it dirlng standop
<dimiterg> jam, fwereadr, voidspace, frobwage, stendup?
<jem> omw
<grofware> dimitern, voidspace, jam: aa utopic ls ko longer sup[ortcd dj we care chat our 'add ju
this will give maas and other providers to, ability to into those steps i.e. maas, creating/removing a for the container, IPs from the provider, etc. <jam> what is Init vs Create? <jam> dimitern: and how does the APIServer know ContainerBroker is doing StartInstance, isn't ContainerBroker part of the machine agent? <dimitern> jam, is one-time initialization first time we need to provision a container of a given type, Create is called before starting the container (ideally the callback can take cloudconfig and modify it, well as the container entity tweak config) <dimitern> the knows about to provision container as the container provisioner, which uses the container broker, will call ContainerManagerConfig on Init and ProvisioningInfo Start <jam> might call something "InitializeContainers" but maybe not. big deal <jam> dimitern: I don't want side-effects from calling Config, but having the send an message to theAPI server that its to start a container is fine <dimitern> jam, ok with finding better names, but the idea is very useful I think - and provider-specific container management from provisioner <jam> dimitern: <jam> AMZ want be able grab IP addresses as well <jam> ContainerInit might also be a when we reconfigure bridges, etc. in the future <dimitern> jam, for - create a possibly allocate an IP well jam, this is the - (in << I'd your thoughts on this well - we can topic during standup <dimitern> jam, omw <frobware> dimitern, voidspace, jam: as utopic is longer supported do we care that our ju
 this will give maas and other pRoviders thAt wanT to, The AbIlitY to hOok into those stEPs anD do extra stuff - i.e. in maas, cReatiNg/REmovINg A deviCe for thE CoNTAinEr, AlLocAtINg iPs frOm tHe proviDer, etc.
<jam> dImiTeRn: what is Init VS CReate?
<jam> diMitErn: and how doeS thE APISeRvEr kNOw the conTaineRBrokeR Is doinG StartInsTaNCe, isn't cOntaineRbRoKer pArt of the machine agENt?
<DImitern> jam, Init Is the oNe-TImE COntAinEr initialiZaTion tHE first tIMe WE NEed TO provision a coNtainer of a gIVen Type, CrEaTe iS Called BeforE aCTuaLly starting The cOntainer (iDeally THe callbACk can taKe the cLouDcoNfig ANd MoDifY iT, As wELl As tHE coNtainer eNtItY to twEak iTS CONfig)
<DimIterN> jam, tHe apiserver knOws We're ABouT to prOvisiOn a cOnTaineR as the ContaInEr provisioner, whIch uSes the conTaiNeR brOkEr, wilL Call CoNtaIneRManageRConfig ON InIt AND prOvisioningInfo befoRe sTArT
<jam> dimiTern: I mIGhT cALl it someThIng Like "iNItialIzeCONtAiners" thEn, but mAYbE nOt. not a bIg Deal
<jaM> dImiTerN: I don'T RealLy thinK we want sIde-efFEcts from callinG config, but haviNG tHE inSTancEBrOker send an eXpliCIt meSsagE To TheapI serVer thAt ITs ABout to start a containEr Is fine
<DimitErn> jam, I'm ok witH finding beTTER names, buT the IDeA Is very useful I tHink - aNd can decouPLe providEr-speCific conTainer manAGEment froM thE prOviSioNER
<jAm> dimitern: surE
<JAm> foR AmZ we wanT to Be able tO grAb Ip adDreSsEs as well
<jAm> ContaiNeRINiT mIghT also BE a time whEn We rEcOnfIgure BRidges, Etc. in The fUtUrE
<DimItern> jaM, YeAH, And fOr MaAs - crEatE a DevicE, posSIblY allocaTe an IP as wEll
<DImitErN> jAm, this iS the rough sketCh - Http://paste.uBuNtu.Com/12997865/ (in tHE ContaineR package) << fwereade, I'd like yOUr thougHts On thiS as wEll - we can tOpiC it durIng STandup
<DimiteRn> jam, FwEreADE, voidSPAcE, frObWare, standuP?
<JAm> oMw
<froBwAre> dImitern, Voidspace, jam: as utopIC is No longer suppoRteD do wE CArE thAT oUR 'adD jU
 this will give maas and o ther provi derstha t w an t to , th e ability to h o ok i nto those steps and do  extr as tuff -i.e.in maas ,  c r e ati ng /r emo vi n ga dev ice  for th e containe r,al locating IPs fr om the pro vid er, etc.
<ja m>dimite rn : w h at is  In it vs  Creat e ?
<jam > dimiter n: and ho w  does t h e  A PISe rver know the Con t ai n erBroker is do ing St ar t In s t anc e,isn't Cont ai nerBr o ker par t  o f t hem achine agent? 
<dimitern> jam , Init  i s t h e one- timeco n tai ner initial izat ion the f irst t i me we n e ed to p rovisi ona c onta i ne rofag ive n  t ype ,  Cr eate isca ll ed be fore a c t uall y s tart ing t he container(id eall y  th e cal lback  can  t ake t he clo udcon fi g and modify it , as  well asthe  c ont ai ner e n tity t o t wea k its c onfig)< dim it e r n >jam, the apiserver  k n o ws  we're a bout t o  p ro v ision aco nta iner a s the  con t ai ner prov isione r ,wh ich use sthe co nt ain erbroke r , wi ll cal l Contai nerMa n agerConfig onI nit and Provi s io n i ng I nfobef ore Start
< jam> dimi tern :  I  mi g ht ca ll it  s o me t hing like "Initiali ze Contai ners"  then, but ma ybe not. n o t a big de al
< j am >  dimitern: I d on'treally thi n k we wan t sid e-effect s from ca l l ing Conf ig,  bu t h avi n g  t he InstanceBr o k er s en d an ex pli cit mes sag e t o t heA PI  server t hat itsab ou tto  st art a containe risfi ne<dimi t ern> j am, I 'm o kwi t h f indingb et t e r na me s,  but  th eideais v e ryusefulI think -  an d  can  d ec ouple p rovider-speci fi c containe rman agemen t from the  provisioner
<jam> dimi t ern: su re<jam>  for  AMZ we w ant  to be  ab l e to g rab IP  addr es ses a s wel l <j am>  C ontainerIn i t  mi ght a ls o be  a time  when we reconfigu r e b ridges, etc.inthef u tu re< di m ite rn >  ja m ,  yeah, and formaas - cre at e  a  device, p o ssi bl y alloc ate anIP as well
<d imitern>jam, this  i s th e rou gh sketch- http:/ /paste.ub u ntu.c o m/ 12997 865 / (inth e c ontai ner pa c kag e) <<  fwere ad e, I'd  like  y our thou ghts on this as well -we can  topi c i t duringsta n dup 
<dimiter n> j am, fwerea de,  vo idspa ce, frobw are, st and u p?
<j am>o mw
<frobw a re > d i m it ern, voidsp a c e , j am: a s u t opic i s no  longer supported do we care tha t ou r 'ad d j u 
 this_will give_maas and other providers_that want_to,_the ability_to_hook into those_steps and do_extra stuff - i.e._in maas, creating/removing_a_device for the container, allocating IPs from the provider, etc.
<jam> dimitern: what is Init_vs_Create?
<jam> dimitern:_and_how_does the APIServer know the_ContainerBroker is doing StartInstance, isn't_ContainerBroker part_of the machine agent?
<dimitern> jam, Init is the_one-time_container initialization the_first time we need to provision a container of_a given type, Create is called_before actually starting_the_container_(ideally the callback can_take the cloudconfig and modify it,_as well as the container entity_to tweak its config)
<dimitern> jam, the apiserver_knows we're about to provision a_container as the container provisioner,_which uses_the container broker, will call_ContainerManagerConfig on Init_and ProvisioningInfo_before Start
<jam> dimitern:_I might call it something like_"InitializeContainers" then, but_maybe not. not a big deal
<jam>_dimitern:_I don't really_think_we_want side-effects_from calling Config,_but_having the_InstanceBroker_send an explicit message to theAPI_server_that its about to start a container_is fine
<dimitern> jam, I'm_ok_with finding better names,_but the idea is very_useful I think - and can_decouple provider-specific_container management_from the provisioner
<jam> dimitern: sure
<jam> for AMZ we want to be_able to grab IP addresses as_well
<jam> ContainerInit might also_be a_time_when we reconfigure_bridges,_etc. in_the future
<dimitern> jam, yeah, and for maas_- create_a device, possibly allocate an IP_as well
<dimitern> jam, this_is_the rough sketch - http://paste.ubuntu.com/12997865/ (in_the container package) << fwereade, I'd_like your thoughts on this_as_well_- we can topic it_during standup
<dimitern> jam, fwereade, voidspace, frobware,_standup?
<jam> omw
<frobware> dimitern,_voidspace, jam: as utopic is no longer_supported_do we care that our 'add_ju