Shutdown for Lab Manager

Similar Questions

• Storage for Lab Manager

  My client needs storage for Lab Manager running on 100 servers. Is it recommended to use the NAS or SAN for Lab Manager running and what type of e/s that you wait for the same thing?

  I did a little bit with storage of LM in recent years.

  I have a development/test environment on LM 600 machine, using 2 Sun 7210 storage devices (is no longer available) on NFS shares. We have 2 links 1 G servile vmKernel traffc as well as links to more vmnetwork, management, etc.  The devices are related to links of 4 x 1 G each.

  I don't know what are the current constraints of LM/ESX, but whenever we revisit the decision 'block vs NAS' we end up selecting NFS (our Sun boxes can present the iSCSI as easily).

  As Jon says, what storage you need certainly depend on your VMS and load.  NOTE: my experience is * NOT * in a production environment, where I am squeezing virtual machines performance.  It's more about the functionality and "adequate" performance (where "adequate" is a measure based on the user experience topic).

  Some things we have learned over the years:

  • IOPS / s are kings, and most of them are entries.  (Written at the moment, I have a few heavy ready operations push me down to about 65 percent.)  I saw > 80% of entries maintained for days.)
  • Latency does not seem as important - VMs run about the same at 10ms latency and latency 250ms NFS NFS.  When latencies above 750ms grows, they will be noticiable users and if they go more than a second over 1000 ms you will begin to see the impact on the guest OSes, especially Solaris x 86.
  • Normal operations don't care about bandwidth - just current execution machines don't even fill a link 1 G
  • Deployment operations * could * start filling to the top of the bandwidth, maybe
  • Betware storm IO.  Often people think the storm IO deployment/boot, but 400 RedHat machines all the kickoff of their 'updatedb' cron job at 04:00 can produce any IO storm as well.  NOTE: IMHO if you buy storage to handle this kind of thing, you're overpaying storage.  I've spread my cron through the night and now can not see on the graphs of storage performance.
  • There is * NOT * a good correlation between guest OS IOPS / s as shown, for example, iostat and PAHO are / s NFS presented to the storage system.  I'm guessing that ESX made a lot of caching.

  Most storage vendors I spoke last year does not seem to find it.  They think in terms of bandwdith and it accelerates with read cache, so unimportant in my environment - I had to push really hard to get sellers to think in the right conditions and some of them really seem out of their depth there.

  I think that this state of mind is important: consider the IOPS / s as you consider CPU: how much should I give to each machine?  How much should I oversubsubscribe?

  Like CPU, a physical machine which IO a lot more available that he needs and you can consolidate - but don't know how.  A physical machine with a pair of 15 k drives RAID1 has about 200 IOPS / s available and readers spend most of time inactive (a bit like the CPU).

  That will boost the machines and when?  Right now I'm on average 9 inputs/outputs by VM, which in my opinion is quite small.  My storage system can go higher under request, but I have enough machines that it is fairly constant.

  In my quest for the perfect storage of LM, I found the usual: good, not expensive or fast, you can choose any two.  How we use LM (lots and lots of shared models) we would really like a unique namespace shared (i.e. 1 data store). I have yet to find the 'perfect' - storage, the Suns are very profitable for the performance and space, but their management takes too much of my time and my 72XX are not expandable - the 74 might be a different experience.  I am currently looking to add some SSD storage, but the ideal configuration would be automated migratino between levels (for example, EMC QUICKLY) and if I bought only from EMC I would triple my cost per VM.

  I talked to people who have a pattern of use of different models that are quite happy on several data stores.  If you can move your load through many warehouses of data then Isilon looks like interesting storage.

  So, in summary:

  • Watch IOPS / s 1st, 2nd and 3rd, then the latency time, then (maybe) bandwidth
  • Manage the budget or the ability of the IOPS / s as you CPU
  • You may not use comments IOPS / s to provide shared storage IOPS / s

  I'm hoping to have a better storage solution in the next 6 months or more.

  --

  Dewey

• Example the SOAP API for Lab Manager in c# required

  Hi, I need to write a small program in c# that will deploy a short list of configurations of the library by name. I read in the guide to the SOAP API to update and tried all of the sample code, but no matter what I can not do the example of code to compile. I use Visual Studio 2008 and you added the WSDL reference correctly. The code contains only errors. He is Director of the laboratory 3.0.2 as well. Just one example showing me how to deploy 2 configurations by name would be greatly appreciated, thank you in advance.

  Here is a very simple example, tested on LM 3.0.2 which gets a configuration by name and deploy it.

• vCenter Lab Manager 4.0.4 5?

  I know that there is no support for Lab Manager 4.0.4 and vCenter 5, but it's going to work? Or when it will be supported? I see no reason why there would be a problem if I leave my host ESX 4.1 cluster.

  Has anyone tried this before?

  vCenter 5 + Lab Manager 4.0.4 won't work.  There, questions that I saw people who did the upgrade without checking compatibility.  Since Lab Manager is abandoned, I'm not expecting a major update to support vCenter 5.0.

  One option is to divide it into 2 environments... 1 specially for vCenter to LabManager and then a 2nd which will vCenter 5 which is a new installation you can grow out.

  Best regards

  Jon Hemming

• Configuration Lab Manager - error: not supported operating system

  I try to install vCenter Lab Manager 4.0.4.1406 but I get error: unsupported on OS when I run the Setup file.

  It is Windows Server 2008 R2 x 64 on an ESXi 5.0 machine.

  IIS and the .net Framework 4.0 is installed.

  Uninstalled AD.

  Looks like all the system requirements are met, but I am still getting the same error (and no more detailed error message then not supported operating system)

  
  

  I don "t think that Windows 2008 R2 is supported for Lab Manager server, only Windows 2003 and Windows 2008 are mentioned in the Manual of Installation.

  For guests, it has made experimental support for Windows 7 and Windows 2008 R2.

• Lab Manager licensing during the merger of vSphere environments

  Is there a small vSphere environment that is available for Lab Manager and a great environment vSphere and both are now completely separated (different vcenter servers, groups separated from ESX, etc.), and they are merged into one, what happens to the Lab Manager licenses?  Should be updated to take account of the increase in the number of ESX host in the new environment?  Environments can be merged without buying additional licenses?  If so, would be half the environment allowed for lab manager and others are not allowed?  How would the lab manager-under license, and lab-manager-without sections allowed environmental stands / separated?

  Thanks for your comments

  "Prepared" you went in in the section resources, hosts tab and see that the host is ready (green check mark), this means that there has been a 'prepare' to the host.  Prepare installs the agent LM, then she will deduct your license (settings > license).

  Kind regards

  Jon Hemming, b.SC., RHCT, VMware vExpert 2009
  http://Twitter.com/vJonHemming

  If your question or problem has been resolved, please click the "right answer".  If someone helped him, please click "useful answer.

• Lab Manager dependencies on vCenter and terminology

  I just Lab Manager, of course with ESX and vCenter.  I know very little about Virtualization, as this issue will prove.  What are the activities of configuration required on vCenter for Lab Manager able to build models, installation configurations and share library configurations?

  Also, I'm trying to get my head around the difference between the data store, data center and media store.  My current knowledge are:

  A data store has a one-way relationship to one or more hosts.  If storage is on a specific host (physical hard disk for example) then the data store has a relationship one of exlclusively with a single host.  Any file a host or a virtual machine can read/write can be read/written on this data store.

  A data center is a logical collection (non-brique and mortar) hosts, data warehouses and virtual machines.  A data center can aggregate various data stores in a single logical storage available to all virtual machines area?  Or another flavor of physical storage can same issue on a Server Windows 2008 physical logically be conifgured such as NFS, and can share NFS join a data center?

  A media store is a special part of a data store managed by the Manager of laboratory exclusively for the storage of files ISO for the construction of models in the laboratory Manager.  Is a media store part of a data store or part of a data center?

  Is a model of vCenter the same model Lab Manager?

  Any clarification on these questions would be more useful.

  Kind regards

  Rick

  Good questions! Welcome to the Forums as well!

  Your description data store is pretty right on. With the exception of the now for the storage of the local host, new technologies progressed to virtualize in the shared storage by the use of devices to Vritual Server.  Companies like HP lefthand and Openfiler to name a few.

  With regard to the issues of data center

  > A datacenter can aggregate various data warehouses into a single logical storage available to all virtual machines area?

  No, he learn better to keep data warehouses between HA/DRS separate clusters.  Now between the host in a cluster you "will share stroage" for the use of the DRS, HA or Storage vMotion.

  > can physical storage on a Server Windows 2008 physical logically be conifgured such as NFS, and can share NFS join a data center?

  Yes you can - use Openfiler VSA to connect the two iSCSI LUNS and NFS for ESX. As long as the ESX host can access the virtual machine through the network.

  For your other questions have a good read on a couple of things well:

  http://bsmith9999.blogspot.com/2010/02/Lab-Manager-40-Setup-and-best-practices.html

  This webcast was just as informative as well:

  http://www.VMware.com/a/webcasts/details/284

  See you soon,.

  Chad King

  VCP-410. Server +.

  Twitter: http://twitter.com/cwjking

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• VCenter Lab Manager dedicated?

  Do you need a dedicated server vCenter for use of Lab Manager or can you use an existing and create a separate data center for Lab Manager hosts?

  No, you do not have a separate vCenter Lab Manager - you can create a new separate data center or even a distinct group within a datacenter exisintg -.

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• Lab Manager 4 runs on Windows 2008?

  Does anyone know if Lab Manager 4 is supported on Windows 2008 x 64?  If not, he is on 2003 x 64?

  Thank you

  No. x 64 is not supported - to the Installation Guide for Lab Manager - only Windows 2003 32-bit is supported

  -

• using SATA vs FC in Lab Manager

  Hi, I'm new to Lab manager and we have noticed performance using LM, however by using virtual machines in Virtual Center have no problem. What are some bottlenecks, that I should look for? We use Server 2 GB for Lab Manager, Server 2 GB for VC, and two 32 GB connected SATA ESX servers. Upgrades to CF help considerably?

  upgrade to FC shared will help a lot; SATA performance tends to be pretty poor and lose you out on the opportunity to share storage, but it is especially in the field of the performance of the virtual machine, which apparently is acceptable when it is directly accessible from VC.  I'll come back later.

  Check use of memory on the servers of your LM and VC - the task manager's performance tab should be sufficient for this purpose.  If your use of the page file seems to be high, probably, and the biggest single performance gain noted by increasing real memory of the system in question.  2 GB seems reasonable, but you very well may benefit considerably with 4 GB of ram real at the VC server.

  CPU utilization must above all be a non-issue.   I run my setup of LM in a virtual machine with a maximum of 512 mhz of limited resources and do not tend to notice the important, long cpu to load.  Memory is always the killer.

  You can also Alternatively take advantages by adding a third win2k3 machine in the mix to install an external full version of MS SQL Server for your VC, rather than the bundled sql express - especially because it divides the workload on the vc server, that tends to get hammered by the demands of LM.

  Network topology could be a problem.  From the sound of it, you have a LM separate, physical server and a server VC separate, physical, as well as some ESX servers.  Is the networking between the four devices complex or distorted? There are benefits to the use of the network paths separate for network LM/VC-esx service console that use virtual machines, and there are certainly benefits to all local to the other servers.

  Or, Alternatively, if your LM and VC are actually themselves VM within your esx servers, you can save significantly by giving them minorants of resources and prioritization of memory/cpu to 'high' whereas they are less likely to get private by ESX resources.

  Meanwhile, your virtual machine performance.  Director of the laboratory, because of related clones, use the drive a little differently, in order to really start to lose with the absence of tagged command queuing, rewriting, and other features in a high performance SCSI configuration, because an operation of e/s "sequential" may eventually be scattered all over the disk.  At the very least, a GNU / linux external and a high performance + disks SCSI controller, shared nfs or iscsi to your esx boxes should give significant benefits (especially if you can do an isolated for this traffic network) in the area of how to perform your VM.  Naturally, the CF will be faster, but there will be $$ involved.

• Using Lab Manager API Java code example

  VMware or anyone have a sample code for using the API in Java? I mean, I have the host name, user name, password, I would not immediately be able to use the API to write my automation tools? spend hours finding the right pots, generating all these strains and write my own code (100 lines) just for connection resembles a maddness for me...

  -J

  After posting my original answer, I remembered that I had posted a code on this forum before. It's a stripped down version is about what would later become the LabMinder code I mentioned previously.

  If you go to the post office: Re: sample SOAP API for Lab Manager in necessary Java at December 20, 2007 by Michael Ottati you can retrieve the zip file in.

  WSDL changes made by new VMware to display require 2 changes to the code for the example to complie. Two of these changes please refer to the HelloLabManager.java

  1: change the world

  VMwareX0020LabX0020ManagerX0020SOAPX0020Interface to LabManagerX0020SOAPX0020Interface

  2: change the occurrence of:

  VMware_x0020_Lab_x0020_Manager_x0020_SOAP_x0020_interface to LabManager_x0020_SOAP_x0020_interface

  I have made these changes and zipped the original example here. This has been tested now with under jdk1.6.0_11 and LM 3.0.1

• Lab Manager 3 and vCenter Server 4?

  Lab Manager 3.0.2 will work if I upgrade Virtual Center to version 4?  (I realize ESX 4 is not supported, was impossible to find out what anyone simply upgrading to vCenter Server.)

  Right now I have 2 groups managed by a server vCenter Server, a 'production' and another for Lab Manager.  If I upgrade my production cluster to vSphere, can I maintain a separate vCenter server with the old version to support Lab Manager?

  http://www.VMware.com/support/labmanager30/doc/releasenotes_labmanager302.html

  Lab Manager requires VMware Infrastructure 3 Standard or Premium

  (VMware ESX 3.5 Update 1, update 2, update 3 or update 4 and)

  vCenter Update 2.5 1, 2 update, update 3 or update 4).

• Lab Manager acceleration kits / required licenses?

  Hello!

  We are currently using ESXi and plan to move to centralized test Lab Manager lab. The estimates are based on the acceleration kit that used to be available at about 4-5 k €, which seemed to include VI 3 licenses that are required for the Lab Manager to run on top of ESXi (or if whatever the basis ESXi does not support).

  Now I can't find the acceleration kits more 'Buy Lab Manager', instead I find licenses for Lab Manager only.

  Now I read everywhere that the vCenter is necessary and even messages that describe that vCenter foundation is not sufficient to run the laboratory Manager. However no official 'that's what you need to do if you want to get Lab Manager' running.

  To be honest, if the acceleration kits were gone for good, licensing begins to be as clear as some States large company in their regulatory policy, "must be this version of the database server", but do not worry to mention what license you need for the said server or background Windows server...

  I would like to know the price of 'minimum' (to continue) Lab Manager on top of bare metal, start-up costs and maintenance renewals when the initial support runs.

  With regard to reading, 2 or 4 processors as it seems to count.

  BR,

  Kalle

  Sorry, that seems so difficult.  To sort through all of this:

  • Lab Manager requires ESX Standard or Enterprise.  It does not currently run on ESXi, but it's on the Roadmap (cannot discuss dates here).

  • Lab Manager 3 requires vCenter (Lab Manager 2 does not work).

  • vCenter Foundation is untested, but should work (but can only manage up to 3 knots).

  • ESX Foundation is not supported by the Lab Manager.

  • The laboratory director is authorized by the node (the server Lab Manager is free).

  • Lab Manager Server runs on Windows Server 2003 and can run on a virtual machine

  • VirtualCenter runs on Windows 2000, Windows XP Professional, or Windows Server 2003 and can also run on a virtual machine.

  Thus, the minimum subscription is:

  • ESX Standard for two processors

  • Lab Manager for two processors

  • vCenter Foundation

  • Windows licenses you need for the Lab Manager server and VirtualCenter Management Server.

  Installing vCenter Management Server and server Lab Manager on the two virtual machines on this host ESX and use their local drive to store the virtual computer images.

  Such a system doesn't scale well, of course.  When you size, you will need to add the following:

  • Shared storage (NFS, iSCSI, or FC)

  • More ESX and Lab Manager licenses

  • vCenter Standard or Premium, instead of Foundation.

  Hope this helps,

  Steven

• Does not install the tools of LM in the evaluation version of Lab Manager

  The Lab Manager eval version contains the option to install the tools of LM? I can't find this option anywhere in the mouse option in the templates on a server that is not in a domain.

  For Lab Manager 3.0 is no longer a requirement for the tools of LM.  VMware Tools is all you need.  Any mention of the LM tools in the documentation must support VM for upgrade.

• Internet access for virtual machines in Lab Manager

  Hello

  Our lab environment is configured separately from corporate network and only some public IPs are able to access the internet. How I would install machinery in the Director of the laboratory to access the internet?

  For example, IP range - 64.x.x.x. Creation of a network model with these IP addresses attached to physical networks and external public would give me access to the internet?

  Stan,

  You would have to create a physical network that is attached to a vSwitch or Distributed Switch that can connect to this network of 64.x.x.x.

  If configure you a Pool of IP, Lab Manager can manage physical network IP assignments to the virtual machines.  so if the virtual machines require Internet access, then they will need to access this network (somehow).

  Kind regards

  Jonathan

  B.SC., RHCT, VMware vExpert 2009

  NOTE: If your question or problem has been resolved, please mark this thread as answered and awarded points accordingly.