Static versus Dynamic MPLS Label-Switched Paths (LSPs)
Multi-Protocol Label Switching (MPLS) converts your routed network to something closer to a switched network and offers transport efficiencies that simply aren’t available in a traditional IP-routed network. Instead of forwarding packets on a hop-by-hop basis, paths are established for particular source-destination pairs. The predetermined paths that make MPLS work are called label-switched paths (LSPs).
You can create MPLS LSPs in one of two ways:
Static configuration: Static LSPs are a lot like static routes. You basically have to explicitly configure every LSR in an LSP manually. Because no protocols dynamically signal the LSP for you, the load on the LSRs is reduced. However, if you have changes in the topology, the paths can’t adapt to the new network. As a result, topology changes create routing black holes.
The lack of dynamic update is a significant drawback and one that should not be overlooked. Dynamic LSPs should be used wherever feasible.
Dynamic setup: Dynamic LSPs use signaling protocols to establish themselves and propagate LSP information to other LSRs in the network. You configure the ingress router with LSP information that is transmitted throughout the network when you enable the signaling protocols across the LSRs.
Note that you have to configure the signaling protocols on all of the LSRs. If only a subset of routers is able to exchange information, the LSP isn’t established.
Because the LSRs must exchange and process signaling packets and instructions, dynamic LSPs consume more resources than static LSPs. However, dynamic LSPs can avoid the network black holes of static LSPs by detecting topology changes and outages and dynamically establishing new LSPs to move around the failure.

Cloud Computing Glossary
cloud computing
A networking solution in which everything — from computing power to computing infrastructure, applications, business processes to personal collaboration — is delivered as a service wherever and whenever you need.

Cloud Computing Glossary
cloud service
The delivery of software, infrastructure, or storage that has been packaged so it can be automated and delivered to customers in a consistent and repeatable manner.

Cloud Computing Glossary
deprovision
The release of cloud services that are no longer needed.

Cloud Computing Glossary
federating
Linking distributed resources together over the cloud.

Cloud Computing Glossary
hypervisor
An operating system that acts as a traffic cop, managing the various virtualization tasks in the cloud to ensure that they make things happen in an orderly manner.

Cloud Computing Glossary
multi-tenancy
The sharing of underlying resources by multiple companies over a cloud.

Cloud Computing Glossary
network attached store
Storage that has its own network address through which it is accessed by the network's workstation users. Acronym: NAS

Cloud Computing Glossary
service level agreement
A contract that stipulates the type of service you need from providers and what type of penalties would result from an unexpected business interruption. Acronym: SLA

Cloud Computing Glossary
solution stack
An integrated set of software that provides everything a developer needs to build an application.

Cloud Computing Glossary
storage area network
A storage systems that is flexible and scalable because it's available to multiple hosts at the same time. Acronym: SAN

Cloud Computing Glossary
vertical industry groups
Workgroups comprised of members from a particular industry such as technology and retail.

Cloud Computing Glossary
virtual memory
The portion of your hard drive that Windows uses to expand the available RAM

Cloud Computing Glossary
virtualization
Using computer resources to imitate other computer resources or whole computers to maximize performance and flexibility.