Dear Stackers, I'm currently looking for some inputs in order to get a new validation, ran as a "preflight check" on the undercloud.
The aim is to ensure we actually have enough disk space for all the files and, most importantly, the registry, being local on the undercloud, or remote (provided the operator has access to it, of course). Although the doc talks about minimum requirements, there's the "never trust the user inputs" law, so it would be great to ensure the user didn't overlook the requirements regarding disk space. The "right" way would be to add a new validation directly in the tripleo-validations repository, and run it at an early stage of the undercloud deployment (and maybe once again before the overcloud deploy starts, as disk space will probably change due to the registry and logs and packages and so on). There are a few details on this public trello card: https://trello.com/c/QqBsMmP9/89-implement-storage-space-checks What do you think? Care to provide some hints and tips for the correct implementation? Thank you! Bests, C. -- Cédric Jeanneret Software Engineer DFG:DF
signature.asc
Description: OpenPGP digital signature
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
