Disable All Advertising
Image
EAN-139781478183419   EAN-13 barcode 9781478183419
Product NameVmware Vsphere 5.1 Clustering Deepdive (Volume 1)
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionWeight:1.06 pounds
Amazon.comA Buy on Amazon ~ 1478183411
SKU9781478183419
Price New19.30 US Dollars    (curriencies)
Price Used3.62 US Dollars    (curriencies)
Width0.94 inches    (convert)
Height8.5 inches    (convert)
Length5.5 inches    (convert)
Weight16.96 ounces    (convert)
AuthorDuncan Epping, Frank Denneman
Page Count416
BindingPaperback
Published08/18/2012
FeaturesUsed Book in Good Condition
Long DescriptionVMware vSphere 5.1 Clustering Deepdive is the follow-up to best seller vSphere 5.0 Clustering Deepdive and zooms in on three key components of every VMware based infrastructure and. It provides the knowledge and expertise needed to create a cloud infrastructure based on the solid foundation of vSphere HA, vSphere DRS and vSphere Storage DRS. It explains the concepts and mechanisms behind HA, DRS and Storage DRS which will enable you to make well educated decisions. Besides a brand new stretched cluster use case section it includes a fully rewritten Storage DRS section, and new details on both vSphere HA and vSphere DRS. This book will take you in to the trenches of HA, DRS and Storage DRS and will give you the tools to understand and implement e.g. HA admission control policies, DRS resource pools, Datastore Clusters and resource allocation settings. Each section contains basic design principles that can be used for designing, implementing or improving VMware infrastructures. Coverage includes: Stretched Clusters HA node types HA isolation detection and response HA admission control VM Monitoring HA and DRS integration DRS imbalance algorithm Resource Pools Impact of reservations and limits CPU Resource Scheduling Memory Scheduler DPM Datastore Clusters Storage DRS algorithm Influencing SDRS recommendations
Similar Items9780470890806: Mastering Vmware Vsphere 5
9780470890790: Vmware Vsphere Powercli Reference: Automating Vsphere Administration
9780470079881: Mastering Vmware Vsphere 5
9780321832214: Vmware Vsphere 5® Building A Virtual Datacenter (Vmware Press Technology)
9780321820471: Managing And Optimizing Vmware Vsphere Deployments (It Best Practices)
9780321799937: Storage Implementation In Vsphere 5.0 (Vmware Press)
9780321799920: Administering Vmware Site Recovery Manager 5.0 (Vmware Press Technology)
9780321799913: Automating Vsphere With Vmware Vcenter Orchestrator (Vmware Press Technology)
9780134376257: Mastering Vmware Vsphere 5
9780133511086: Networking For Vmware Administrators (Vmware Press Technology)
View 14 more similar items
Created11-19-2012 11:46:52pm
Modified05-01-2020 4:54:01pm
MD5e4ca8827c6c68c0467cdbefb1c2aed7b
SHA256541c8ca09f7046d6dd9cbb6911b88cc6401d0ca77f62d389330eb6da9fa8db38
Search Googleby EAN or by Title
Query Time0.0276222

An article of interest

Making use of the tools we offer

Data Feed API v2 - Access and Data Layout

This describes how to use version 2.x of the data feed. Version 1.x of the feed is no longer supported in any way.

Accessing the data requires your account to have an active data feed. This switch can be turned on or off on the data feed page. This is also where you will be able to view your KEYCODE which is required to make calls to the feed.

You must always pass these...

When looking up data...

When updating data...

To download the list of categories...

The feed return data structure...

All fieds are returned regardless of the result. Check the status code before trying to make use of any of the data returned. As long as the code you send is valid (not an error) the barcode field will hold a link to a baccode graphic. If you get a 404 error because we can't find the product, you may still get valid data in the company section so you may want to check the company name field.

status
    find     the find value you sent in your request
    code     200 = success, 404 = not found, 400 and 500 = error
    message     details about the code
    version     feed version number
product
    modified     YYYY-MM-DD HH:MM:SS (24 hour time)
    ean13     13 digit EAN-13 code
    upca     12 digit UPC-A code (may be n/a)
    upce     8 digit UPC-E code (may be n/a)
    product     the name of the product
    description     size, weight, count, color, etc.
    category_no     numeric category code
    category_text     text version of the category
    url     a link to the product page (not on our site)
    image     a link to an image of the product (on our site)
    has_long_desc     does this product have a long description (1/0)
    barcode     a link to a barcode image (on our site)
    locked     is this data locked from updates (1/0)
company
    name     company name
    logo     a link to a company logo (on our site)
    url     a link to the company's official web site
    address     the company's mailing address
    phone     the company's phone number (digits only)
    locked     is this data locked from updates (1/0)

You will need to make requests for the content of the long description in a separate call get=long_desc to the GET or POST request. In this case, you will only get back the long description. The return structure of the long description data looks like this...

status
    find     the find value you sent in your request
    code     200 = success, 404 = not found, 400 and 500 = error
    message     details about the code
    version     feed version number
product
    modified     YYYY-MM-DD HH:MM:SS (24 hour time)
    long_desc     the long description for the product
    locked     is this data locked from updates (1/0)