Hi, Hope you are doing well.
Please find the below Job description and let me know your interest. *Position: VMware Engineer* *Location: Campbell, CA* *Duration: **6+ Months Contract* *Need Locals to CA Only* *VMware Engineer* · VMware ESX/ESXi, vSphere & vCenter experience, at least 3 years (if recent), 5 might be better, but not likely more. I saw one posting asking for 10, at which I laughed; there is no value in VMware knowledge from that long ago. · VMware in a production environment · VMware vCenter Site Recovery Manager was specifically requested; Remote Office Branch Office might also be applicable, but Site Recovery was specifically mentioned. · Chris mentioned 'VCAC', which is VMware vCloud Automation Center; now evidently vRealize Automation; either would definitely be something to look for. · VMware vSphere with Operations Management, specifically mentioned by Chris (opsman) · They consolidated a lot of things, which is good from a simplicity standpoint, but a lot of products like "Cloud Orchestration Manager" have been rolled into other packages, which will make identifying previous high-level VMware experience more difficult to identify. · Experience with the VMware API would demonstrate pretty in-depth knowledge of the product. Not likely to be directly applicable, but would definitely demonstrate depth. *VMware in a nutshell:* · vSphere used to be the name of their management client and is now the name of their entire virtualization package, which can lead to confusion; though less so now as people have gotten used to using 'vSphere Client'. · vCenter is their management server, and as such is the core of their entire software suite. After setup, it is managed from the vSphere Client, and in turn it manages the ESXi hypervisors. · VMware's major versioning follows the hypervisor, and is currently 6.0; any experience before 5.0 probably isn't useful. Not a lot changes in the actual administration, but features and workflows shift, as does support for their other software offerings. · Extra software packages (licenses) are installed on vCenter, and then setup and implemented. vCenter is a Windows application and must run on Windows Server; there is also a (linux) VM appliance for it, but I never got it to work right; but it can save on the $1k Windows license fee, so that might be something to ask about. Best Regards, *Pruthvi Raju* *Technical Recruiter* *IDC Technologies Inc.* *1851 McCarthy Boulevard, Suite 116, Milpitas, CA – 95035* *Phone:- **408-648-0957* *Email:- **prut...@idctechnologies.com* <prut...@idctechnologies.com> *Website:- **www.idctechnologies.com* <http://www.idctechnologies.com> -- -- *************************************************************************************** For all SAP related tutorials,Articles,Faqs,Tips www.sapbrainsonline.com **************************************************************************************** You received this message because you are subscribed to the Google Groups "sapbrains" group. To post to this group, send email to sapbrains@googlegroups.com To unsubscribe from this group, send email to sapbrains-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sapbrains?hl=en --- You received this message because you are subscribed to the Google Groups "sapbrains" group. To unsubscribe from this group and stop receiving emails from it, send an email to sapbrains+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
