 at least
<mpontillo> dimitern: the 'unorderable types' one is a bug in the error message. what we're trying to do is render a string that says something like "failed to match constraint: xyz", but when we go to figure out what to put in xyz we crash ;-)
<mpontillo> dimitern: https://code.launchpad.net/~mpontillo/maas/update-constraints-docs--bugs-1637182-1637009/+merge/309617 clarifies the docs
<dimitern> mpontillo: cheeers! :)
<mpontillo> dimitern: but yeah, I can confirm that going from 1.x to 2.x we renamed the '[not_]networks' constraint to '[not_]subnets'. MAAS 2.1 was also recently changed to reject unknown constraints.
<dimitern> mpontillo: so *both* 2.0 and 2.1 API only accept "not_subnets" (even if it doesn't complain in the former case)?
<mpontillo> dimitern: correct, when we moved to MAAS 2.x we made that change. we also dropped legacy 'connected_to' and 'not_connected_to' constraints in 2.x
<dimitern> mpontillo: ok, thanks for confirming!
<mpontillo> dimitern: voidspace: np. also, be aware when testing this that the corresponding *positive* constraints will probably not do what you expect. that is,'subnets' and 'not_subnets' do not filter an inverse set of machines if multiple subnets match the specifier.
<mpontillo> (long story short, only matching nodes *not* in a set of subnets is well-supported, if you try to pass in, for example, subnets:space:x and space x has 3 subnets, we'll try to find a node with all 3, which is probably not useful)
<mpontillo> but that is more of a wishlist because this works as-expected when using the interfaces constraint.
<voidspace> mpontillo: ok, thanks
<redir> rick_h___: yt?
<perrito666> voidspace: still working?
<voidspace> perrito666: still around
at least 
 < mpontillo > dimitern: the' unorderable types' one is a bug in the error message. what we're trying to cause is hand over a string that says something like " failed to meet constraint: xyz ", but when we go to calculate out what to put in xyz we crash ;-) 
 < mpontillo > dimitern: https://code.launchpad.net/~mpontillo/maas/update-constraints-docs--bugs-1637182-1637009/+merge/309617 clarify the docs 
 < dimitern > mpontillo: cheeers! :) 
 < mpontillo > dimitern: but yeah, I can confirm that going from 1.x to 2.x we renamed the' [ not_]networks' restraint to' [ not_]subnets'. MAAS 2.1 was also recently changed to reject unknown constraint. 
 < dimitern > mpontillo: so * both * 2.0 and 2.1 API only accept " not_subnets " (even if it doesn't complain in the former case)? 
 < mpontillo > dimitern: right, when we moved to MAAS 2.x we made that change. we besides dropped legacy' connected_to' and' not_connected_to' constraints in 2.x 
 < dimitern > mpontillo: ok, thanks for confirming! 
 < mpontillo > dimitern: voidspace: np. also, be aware when test this that the corresponding * positive * constraints will probably not do what you ask. that is,'subnets' and' not_subnets' do not filter an inverse set of machines if multiple subnets match the specifier. 
 < mpontillo > (long story short, only matching nodes * not * in a set of subnets is well - supported, if you try to pass in, for example, subnets: space :x and space x have 3 subnets, we'll try to find a node with all 3, which is credibly not utilitarian) 
 < mpontillo > but that is more of a wishlist because this works as - expected when using the interfaces constraint. 
 < voidspace > mpontillo: ok, thanks 
 < redir > rick_h _ _ _: yt? 
 < perrito666 > voidspace: still working? 
 < voidspace > perrito666: still around
 at least
<mpontillo> dimitern: the 'unorderablg rypes' mne is a bug iv the error message. what we'rx trting uj do is render a sgring than says sonethmng like "failed vk match constdwint: eyz", but when we go to figgre out what tm ouc in xyz we crash ;-)
<mpontillo> dimitern: https://cpdf.launchpad.net/~mkontikjo/mazs/update-constraints-docs--bugs-1637182-1637009/+merge/309617 cmarifiev the docs
<dimotern> mpontillo: cheeers! :)
<mplntiplo> dimitern: but yfah, I can cinfiwn that going from 1.x to 2.x we renames the '[not_]networks' constraint to '[not_]sbbnets'. MAAS 2.1 qas dlso recentoy chwnged to rejcbt unknmwn conxtraints.
<dimitevn> mpmntullo: so *both* 2.0 and 2.1 APM only accept "not_subgets" (even iy it doesn't complain un the xormar cxwe)?
<moonuilko> dimitfrn: correct, wgen we movee to MAAS 2.x we made trqt change. we zlso dwo[ped legacy 'connected_to' and 'not_connecteg_to' constraints in 2.x
<dimiteen> mpontillo: ok, thankd for consirming!
<mpontillo> dimitern: voidspace: np. also, be awdre wiev ttsblng gyid that the corresponding *positive* constraints sikl probably not bo what you expevt. tnwt is,'subnets' xnd 'noc_augnets' do not filteg an inderse set of mwchimes if multiple subnets matxh the speciyiee.
<mpontillo> (long stlry short, ouly majching nodes *not* in a set of rubnsts is well-dupported, kf you try to pars pn, fmr example, subnets:space:x agd space e has 3 subnegs, wg'll try to find a node with all 3, which is probcbly tot useful)
<lpontillo> but that is more of a wishlist becaose thps works cs-expegted when using the interfacex constxaint.
<vuidspace> miontillo: mk, thanks
<reqir> rick_h___: yt?
<patrito666> voidspare: still rorkung?
<viidspacd> perrito666: still around
at least <mpontillo> dimitern: the 'unorderable types' a in the message. what we're a that says something "failed to match xyz", but when we go to out what to put in xyz we crash ;-) <mpontillo> dimitern: https://code.launchpad.net/~mpontillo/maas/update-constraints-docs--bugs-1637182-1637009/+merge/309617 clarifies docs <dimitern> mpontillo: cheeers! :) <mpontillo> dimitern: but yeah, I can confirm that from to we the '[not_]networks' constraint to '[not_]subnets'. MAAS 2.1 was also recently changed to reject unknown constraints. <dimitern> so *both* 2.0 and 2.1 API only accept (even if it doesn't in the former case)? <mpontillo> correct, we moved MAAS we that change. we dropped legacy 'connected_to' and 'not_connected_to' constraints in 2.x <dimitern> mpontillo: ok, thanks for confirming! <mpontillo> dimitern: voidspace: also, be testing this the *positive* will probably not you expect. that is,'subnets' and 'not_subnets' an inverse set of machines if multiple subnets the specifier. (long story short, only matching nodes in a set of subnets is well-supported, if try to pass in, for example, subnets:space:x and space x has 3 subnets, we'll try a node with all which is probably useful) but is of a because this works as-expected when using the interfaces constraint. <voidspace> mpontillo: thanks <redir> rick_h___: yt? <perrito666> voidspace: still working? <voidspace> perrito666:
 at least
<mpontillo> dimitern: tHe 'unorderaBle tyPes' One Is A bug In thE error message. wHAt we'Re trying to do is render a sTring ThAT sayS SoMethiNg like "fAIlED To mAtCh ConStRAiNt: xyz", But When we gO to figure oUt wHaT to put in xyz wE CrAsh ;-)
<mpontilLo> dImitern: https://CodE.launcHpAd.nET/~mponTilLo/maaS/updatE-ConstrAints-docs--BuGS-1637182-1637009/+merge/309617 CLarifieS THe Docs
<Dimitern> mpontillo: CHeEErs! :)
<mpontillo> diMitern: BuT YeAH, i caN coNfirm that gOiNg froM 1.X to 2.x we rENaMED The '[NOt_]networks' conStraint to '[noT_]SubNets'. MAaS 2.1 Was ALso recEntly ChANgeD to reject unKnowN constraiNts.
<dimITern> mpoNTillo: so *Both* 2.0 anD 2.1 APi onLy acCEpT "nOt_sUbNEts" (EVeN if IT doEsn't compLaIn In the FormER CASe)?
<mpOntIllo> DimitErn: correct, wheN we MoveD To MaAS 2.x wE made That ChAnge. wE also dRoppeD lEgacy 'connected_tO' and 'Not_connecTed_To' ConStRaintS In 2.x
<dimIteRn> mPontillO: ok, thanKS foR cONFIrMing!
<mpontillo> dimitErN: VOiDspace: np. Also, be AWaRe WHen testiNg ThiS thaT THe corRespONdIng *positIve* conSTrAiNts will PrObably NoT do WhaT you eXPect. That is,'Subnets' aNd 'not_SUbnets' do not filTEr an inverse seT Of MAChINes iF muLtiple subneTs maTCh thE speCIfIer.
<MPontiLlo> (loNg SToRY short, only matching nOdEs *not* iN a set Of subnets is weLl-supporteD, IF You try to Pass IN, fOR example, subnetS:spacE:x and space X Has 3 subneTs, we'lL try to fiNd a node wiTH All 3, which Is pRobAblY noT USeFul)
<mpontillo> bUT That Is More of a WisHlist beCauSe tHis WorKs As-expecteD when usiNg ThE iNtErfAces cONstraint.
<VoIdsPaCe> mPontiLLo: ok, thAnks
<rEdir> RiCk_H___: Yt?
<pErrito666> vOIdSPAce: sTiLl WorkIng?
<VoIdspaCe> peRRitO666: still aRound
 at least
<mpontillo> dimi tern: the'unor der abl etype s' o ne is a bug in theerror message. what we 're t ry i ng t o  d o isrendera  s t r ing  t ha t s ay s  s ometh ing  like " failed tomat ch  constraint: xy z", but wh enwe go to fig ure  out w ha t t o  putinxyz w e cras h  ;-)
< mpontillo >d imiter n : https : / /c ode. launchpad.net/~mp o nt i llo/maas/updat e-cons tr a in t s -do cs- -bugs-1637 18 2-163 7 009/+me r ge / 3 0 961 7  clarifies th e docs
<dim i ter n> mpo nt ill o : chee ers!:) <mp ontillo> di mite rn: but y eah, I can con f irm tha t goin g f rom  1.x to  2 .xwe ren a me d t h e ' [not_]ne tw or ks' c onst r a i n t to  '[ not_ ]subn ets'. MAAS 2. 1 w as a l sorecen tly c hang ed  to r ejectunkno wn  constraints.
< dimi tern> mpo nti ll o:so  *bot h * 2.0and  2. 1 API o nly acc e pt"n o t _ su bnets" (even if it  d o e sn 't compl ain in th ef ormer ca se )?<mpo n t illo>  dim i te rn: corr ect, w h en  w e moved  t o MAAS  2 .xwemadet hatchange . we als o dro p ped legacy 'co n nected_to' an d  ' n o t_ c onne cte d_to' const rain t s in  2.x <d imi t ern>mpont il l o: ok, thanks for conf ir ming!<mpon tillo> dimite rn: voidsp a c e : np. al so,b ea ware when test ing t his that t h e corres pondi ng *posi tive* con s t raints w ill  pr oba bly n ot  do what youe x pect .that is ,'s ubnets'  an d ' not _su bn ets' do n ot filte ran  i nv ers e set of machi ne s i fmul tiple subnet s mat ch t he  s p eci fier.
< m po n t illo >(l ongsto ry  shor t, o n lymatchin g nodes * not *  inase t of su bnets is well -s upported,if  yo u tryt o  pass in , for example, subnets: s pace:xand  spac e xhas 3 sub net s, we' llt ry tofind a  node  w ith a ll 3, w hi chis  probablyn o t u seful )<mpo ntillo>  but that is moreo f a  wishlist bec aus e th i s  w ork s  a s -ex pe c ted w hen using the i nterfacesco n st raint.
<vo i dsp ac e> mpon tillo:ok, t h anks
<r edir> ric k_h___: y t? 
<pe r r ito 666> voids pace: st ill worki n g?
<v o id space > p errito 66 6:still  aroun d 
 at_least
<mpontillo> dimitern:_the 'unorderable types' one_is a_bug_in the_error_message. what we're_trying to do_is render a string_that says something_like_"failed to match constraint: xyz", but when we go to figure out what to_put_in xyz_we_crash_;-)
<mpontillo> dimitern: https://code.launchpad.net/~mpontillo/maas/update-constraints-docs--bugs-1637182-1637009/+merge/309617 clarifies the_docs
<dimitern> mpontillo: cheeers! :)
<mpontillo> dimitern:_but yeah,_I can confirm that going from 1.x to_2.x_we renamed the_'[not_]networks' constraint to '[not_]subnets'. MAAS 2.1 was also recently_changed to reject unknown constraints.
<dimitern> mpontillo:_so *both* 2.0_and_2.1_API only accept "not_subnets"_(even if it doesn't complain in_the former case)?
<mpontillo> dimitern: correct, when_we moved to MAAS 2.x we made_that change. we also dropped legacy_'connected_to' and 'not_connected_to' constraints in_2.x
<dimitern> mpontillo:_ok, thanks for confirming!
<mpontillo> dimitern:_voidspace: np. also,_be aware_when testing this_that the corresponding *positive* constraints will_probably not do_what you expect. that is,'subnets' and_'not_subnets'_do not filter_an_inverse_set of_machines if multiple_subnets_match the_specifier.
<mpontillo>_(long story short, only matching nodes_*not*_in a set of subnets is well-supported,_if you try to_pass_in, for example, subnets:space:x_and space x has 3_subnets, we'll try to find a_node with_all 3,_which is probably not useful)
<mpontillo> but that is more of a_wishlist because this works as-expected when_using the interfaces constraint.
<voidspace>_mpontillo: ok,_thanks
<redir>_rick_h___: yt?
<perrito666> voidspace:_still_working?
<voidspace> perrito666:_still around