Assuming the config and storage info is global (at least as seen from any particular call in the system), you can stuff them anywhere you like, but "logically" it would go either somewhere in the top model package or in a separate configuration package.

As for access, I'd recommend you use methods or regular subroutines that return the right data/object for the current context, since that way you can change the implementation without having to change all the code relying on the information.

update: as a variant of this, if the relevant info is all provided by the top-level model object, you can also make the model object globally available from a class method/subroutine and then get the data from there.