Thanks for your answer. As far as I understand CellsV2 are present in Pike and later. I need to implement such use case in an Ocata Openstack based cloud
Thanks, Massimo 2018-02-06 10:26 GMT+01:00 Flint WALRUS <gael.ther...@gmail.com>: > Aren’t CellsV2 more adapted to what you’re trying to do? > Le mar. 6 févr. 2018 à 06:45, Massimo Sgaravatto < > massimo.sgarava...@gmail.com> a écrit : > >> Hi >> >> I want to partition my OpenStack cloud so that: >> >> - Project p1, p2, .., pn can use only compute nodes C1, C2, ... Cx >> - Projects pn+1.. pm can use only compute nodes Cx+1 ... Cy >> >> I read that CERN addressed this use case implementing the >> ProjectsToAggregateFilter but, as far as I understand, this in-house >> developments eventually wasn't pushed upstream. >> >> So I am trying to rely on the AggregateMultiTenancyIsolation filter to >> create 2 host aggregates: >> >> - the first one including C1, C2, ... Cx and with filter_tenant_id=p1, >> p2, .., pn >> - the second one including Cx+1 ... Cy and with filter_tenant_id=pn+1.. >> pm >> >> >> But if I try to specify the long list of projects, I get:a "Value ... is >> too long" error message [*]. >> >> I can see two workarounds for this problem: >> >> 1) Create an host aggregate per project: >> >> HA1 including CA1, C2, ... Cx and with filter_tenant_id=p1 >> HA2 including CA1, C2, ... Cx and with filter_tenant_id=p2 >> etc >> >> 2) Use the AggregateInstanceExtraSpecsFilter, creating two aggregates >> and having each flavor visible only by a set of projects, and tagged with a >> specific string that should match the value specified in the correspondent >> host aggregate >> >> Is this correct ? Can you see better options ? >> >> Thanks, Massimo >> >> >> >> [*] >> # nova aggregate-set-metadata 1 filter_tenant_id= >> ee1865a76440481cbcff08544c7d580a,1c63ef80901b46bebc9e1e8e10d85019, >> a22db12575694c9e9f8650dde73ef565,b4a1039f2f7c419596662950d8a1d397, >> d8ce7a449d8e4d68bbf2c40314da357e,e81df4c0b493439abb8b85bfd4cbe071, >> ee1865a76440481cbcff08544c7d580a,29d6233c0b2741e2a30324079f05aa9f, >> 2b92483138dc4a61b1133c8c177ff298 >> ERROR (BadRequest): Invalid input for field/attribute filter_tenant_id. >> Value: ee1865a76440481cbcff08544c7d580a,1c63ef80901b46bebc9e1e8e10d85019, >> a22db12575694c9e9f8650dde73ef565,b4a1039f2f7c419596662950d8a1d397, >> d8ce7a449d8e4d68bbf2c40314da357e,e81df4c0b493439abb8b85bfd4cbe071, >> ee1865a76440481cbcff08544c7d580a,29d6233c0b2741e2a30324079f05aa9f, >> 2b92483138dc4a61b1133c8c177ff298. u'ee1865a76440481cbcff08544c7d580a, >> 1c63ef80901b46bebc9e1e8e10d85019,a22db12575694c9e9f8650dde73ef565, >> b4a1039f2f7c419596662950d8a1d397,d8ce7a449d8e4d68bbf2c40314da357e, >> e81df4c0b493439abb8b85bfd4cbe071,ee1865a76440481cbcff08544c7d580a, >> 29d6233c0b2741e2a30324079f05aa9f,2b92483138dc4a61b1133c8c177ff298' is >> too long (HTTP 400) (Request-ID: req-b971d686-72e5-4c54-aaa1- >> fef5eb7c7001) >> >> >> _______________________________________________ >> OpenStack-operators mailing list >> OpenStack-operators@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> >
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
