search for: __capacity

...i.91 = i; D.785 = i.91.__methods; D.786 = D.785->Sum; D.787 = __go_new_nopointers (16); MEM[(int[4] *)D.787][0] = 2; MEM[(int[4] *)D.787][1] = 3; MEM[(int[4] *)D.787][2] = 5; MEM[(int[4] *)D.787][3] = 7; D.788.__values = D.787; D.788.__count = 4; D.788.__capacity = 4; D.789 = i.91.__object; x = D.786 (D.789, D.788); // [1] if (x != 17) goto <D.790>; else goto <D.791>; Here `i' is struct { struct { const struct * __type_descriptor; int (*<Td6>) (struct ) Sum; } * __methods; void * __object; } i; Since `...

This patch provides the ability to create a "dir" type storage pool, and to add and remove volumes for existing pools.

This set of patches supercedes the previous set, and has been rebased with changes from upstream.

This patch again rebases on upstream and should apply on next as of right now.

...elif page is VOLUME_FORMAT_PAGE: + if self.__formats.current() is not None: + return True + else: + errors.append("You must select a volume format.") + elif page is MAX_CAPACITY_PAGE: + if string_is_not_blank(self.__capacity.value()): + if string_is_not_blank(self.__allocation.value()): + capacity = int(self.__capacity.value()) + allocation = int(self.__allocation.value()) + if capacity > 0: + if capacity <= self.__conf...

This pair of patches provide a new storage admin interface. Then, on top of that, it refactors the domain administration pieces to now properly use storage pools and volumes when defining a new VM.