Abstract: A process for defining a cloud service in an Infrastructure as Code (IaC) tool is designed to dynamically determine numbers of clusters, availability domains, compute nodes, and/or load balancers at run time. These values are then used to determine a number of subnet levels required for a classless inter-domain routing (CIDR) slicing operation to generate subnets for each of the compute nodes and load balancer nodes in the service. Because IaC languages do not provide nested loop control constructs, labels for each of the subnets can be generated and assigned using a Cartesian product of label elements. These labels can be modified by a count variable that is incremented each time a resource is duplicated in the script to simulate the effect of a nested loop structure.

Abstract: Systems, methods, and other embodiments associated with cloud infrastructure resource information scanning are described. In one embodiment, a computer implemented method includes scanning a cloud network computing system tenancy to, for each subdivision of a set of subdivisions of the tenancy, (i) identify an IP address range assigned to the subdivision, and (ii) identify any immediate parent subdivision to which the subdivision belongs; for each subdivision in the set of subdivisions, determining a proportion of the IP address range assigned to the subdivision that is free in the subdivision based on the identified IP address ranges and the identified parent subdivisions for the subdivision; generating a graphical user interface showing the proportion of the IP address range that is free for one or more of the set of subdivisions; and transmitting the graphical user interface for display on a computing device associated with a user.

Abstract: Systems, methods, and other embodiments associated with cloud infrastructure resource information scanning are described. In one embodiment, a computer implemented method includes scanning a cloud network computing system tenancy to, for each subdivision of a set of subdivisions of the tenancy, (i) identify an IP address range assigned to the subdivision, and (ii) identify any immediate parent subdivision to which the subdivision belongs; for each subdivision in the set of subdivisions, determining a proportion of the IP address range assigned to the subdivision that is free in the subdivision based on the identified IP address ranges and the identified parent subdivisions for the subdivision; generating a graphical user interface showing the proportion of the IP address range that is free for one or more of the set of subdivisions; and transmitting the graphical user interface for display on a computing device associated with a user.

Abstract: A process for defining a cloud service in an Infrastructure as Code (IaC) tool is designed to dynamically determine numbers of clusters, availability domains, compute nodes, and/or load balancers at run time. These values are then used to determine a number of subnet levels required for a classless inter-domain routing (CIDR) slicing operation to generate subnets for each of the compute nodes and load balancer nodes in the service. Because IaC languages do not provide nested loop control constructs, labels for each of the subnets can be generated and assigned using a Cartesian product of label elements. These labels can be modified by a count variable that is incremented each time a resource is duplicated in the script to simulate the effect of a nested loop structure.