e larger code base. If a change creates issues, such as runaway storage use, those problem can be isolated and rolled back quickly (31, n.d.). When used properly, CI provides various benefits, such as constant feedback on the status of the software. Because CI detects deficien- cies early on in development, defects are typically smaller, less complex, and easier to resolve (30, n.d.). CD is an extension of the concept of CI. Whereas CI deals with the build/test part of the development cycle for each version, CD focuses on what happens with a committed change after that point. With CD, commits that passes the automated tests can be considered a valid candidate for release (32, n.d.). CI/CD allows service providers to manage the delivery and meet timelines of their massive net- work cloud platform. CI/CD allows hundreds of developers to pull code down, to make changes, and to check the code back in. While doing this, additional controls around human reviews and approval are automated, while automated integration, deployment, and testing takes place simultaneously. This allows service providers to move very fast to meet the needs of a constantly evolving space, and continuously improve the quality of their deliverables. 4.3.2 INNOVATION AND INTEGRATION When choosing an NFVI solution, particularly one that is open source, it is important to know that the service that you purchase will not be ready to go, "out-of-the-box." Every organization or ser- vice provider has unique needs, and simply put, no existing solution can solve everything. That is why it is important to emphasize innovation and integration when building NFVI. Utilizing Agile, DevOps, and CI/CD principles, each respective organization can create in-house extensions that tie the existing enterprise infrastructure into the VIM and NFVI. 4.3.2.1 Design The network cloud infrastructure design tools can automate the design of zones, cutting the time for this phase by more than half, when compared to early manual designs. Some tools allow for Building the Net