resourceprovisioning外文精品企业营销.ppt

* CONFIDENTIAL BIG-IP v10.0.0Resource Provisioning Presented by: ATM NPI CONFIDENTIAL Resource Provisioning v10 introduces a new eval licensing and resource provisioning model Divorces resource allocation from licensing No longer bricks the box when an eval license expires What problems are we solving? We’re making it easier for customers to evaluate modules We’re giving customers control over how their resources are distributed between modules We’re minimizing the service impact from implementing new functionality We’re turning implicit (licensed-derived) behavior into explicit (config-derived) behavior What resources does provisioning control? CPU Will control how much CPU tmm uses In this release, can’t control CPU usage by modules Memory Allocates memory to tmm and modules using hugetlbfs Disk Controls mass-storage allocation for modules Has no impact on boot locations and /shared Who gets these resources? LTM LTM == tmm Modules WAM WOM ASM PSM GTM LC The host NB: Modules can get their own memory and disk, but their CPU allocations just get lumped in with the host’s. Modules get their minimums Any module that is provisioned to anything other than “none” will get its minimum required resources The provisioning settings control how the remainder of the resources are divided between modules Minimum resource allocations are detailed in the functional spec. /twiki/bin/view/TMOS/ParkCityBigipResourceManagementFS How we treat the host The host is not a full player in the resource allocation game. It gets its minimums + whatever is left over. If any module is provisioned to “nominal” or higher, the host gets only its minimums. If you need to give the host more memory, the pre-existing Provision.ExtraMB mechanism still works. This effectively increases the host’s minimum memory requirement. Specifying resource allocations User defines a provisioning level for each module [root@bigip:Active] config # tmsh list sys provision provision asm { } provision gtm {