System and method for developing and implementing a migration plan for migrating a file system
A computer system implements a file system migration by determining a destination namespace of a destination file system based at least in part on a namespace of a source file system. At least a portion of the destination namespace includes an organization that is altered as compared to a corresponding portion of the source namespace.
1. A method comprising:
identifying a source namespace associated with a source file system of a source system;
receiving a first specification of a container associated with the source namespace of the source system;
determining a container type for implementing the container within a destination namespace for a destination system;
generating a migration plan to migrate the source file system from the source system to the destination system as a destination file system having the destination namespace with the container having the container type; and
in response to receiving a second specification of a file path to utilize for the container once migrated to the destination system, including the file path within the migration plan.
2. The method of claim 1 , comprising:
limiting the migration plan to file system objects embedded within the container.
3. The method of claim 1 , wherein the container type corresponds to a current container type of the container associated with the source namespace.
4. The method of claim 1 , wherein the container type is different than a current container type of the container associated with the source namespace.
5. The method of claim 1 , comprising:
including a policy within the migration plan.
6. The method of claim 1 , wherein the file path corresponds to a current file path of the container associated with the source namespace.
7. The method of claim 1 , wherein the file path is different than a current file path of the container associated with the source namespace.
8. The method of claim 1 , comprising:
in response to receiving a third specification of a policy to utilize for the container once migrated to the destination system, including the policy within the migration plan.
9. The method of claim 8 , wherein the policy corresponds to a current policy of the container associated with the source namespace.
10. The method of claim 8 , wherein the policy is different than a current policy of the container associated with the source namespace.
11. The method of claim 1 , comprising:
including a default parameter within the migration plan, wherein the default parameter corresponds to a selection of file system objects to migrate based upon the file system objects having a same structure.
12. The method of claim 1 , comprising:
including a default parameter within the migration plan, wherein the default parameter corresponds to a selection of file system objects to migrate based upon the file system objects having a same organization.
13. The method of claim 1 , comprising:
including a default parameter within the migration plan, wherein the default parameter corresponds to a selection of file system objects to migrate based upon the file system objects having a same granularity.
14. The method of claim 1 , comprising:
utilizing the migration plan to determine the destination namespace.
15. A non-transitory machine readable medium comprising instructions for performing a method, which when executed by a machine, causes the machine to:
determine a source namespace associated with a source file system of a source system;
receive a specification of a container associated with the source namespace of the source system;
determine a container type for implementing the container within a destination namespace for a destination system;
generate a migration plan to migrate the source file system from the source system to the destination system as a destination file system having the destination namespace with the container having the container type; and
include a default parameter within the migration plan, wherein the default parameter corresponds to a selection of file system objects to migrate based upon the file system objects having a same structure.
16. The non-transitory machine readable medium of claim 15 , wherein the instructions cause the machine to:
implement the migration plan to perform resource allocation for the destination namespace.
17. The non-transitory machine readable medium of claim 15 , wherein the instructions cause the machine to:
implement the migration plan to select an aggregate for the destination namespace.
18. The non-transitory machine readable medium of claim 15 , wherein the instructions cause the machine to:
implement the migration plan to determine a logical interface arrangement for ports associated with the destination system.
19. A computing device comprising:
a memory comprising machine executable code for performing a method; and
a processor coupled to the memory, the processor configured to execute the machine executable code to cause the processor to:
determine a source namespace associated with a source file system of a source system;
receive a specification of a container associated with the source namespace of the source system;
determine a container type for implementing the container within a destination namespace for a destination system;
generate a migration plan to migrate the source file system from the source system to the destination system as a destination file system having the destination namespace with the container having the container type; and
include a default parameter within the migration plan, wherein the default parameter corresponds to a selection of file system objects to migrate based upon the file system objects having a same organization.
20. The computing device of claim 19 , wherein the machine executable code causes the processor to:
implement the migration plan to identify resources for implementing the destination namespace at the destination system based upon optimization parameters.