Skip to main content

VI plugin Guide by Andrew Kutz

It's not supported by VMware, so you're warned ;-)

The doors are opening...What I mean by this, expect a detailed blog article by me on it("the doors opening").

This paper focuses on educating developers on:

Client Plugin Architecture
This includes where plugins are installed, how the VI client discovers local plugins and ones advertised on the VC server, and finally how to create a client plugin.

Server Extension Architecture
Includes how to register server extensions and how to make client plugins centrally available.

Tomcat Architecture
Discusses how the VirtualCenter Tomcat installation impacts server extension daemons.

Database Schema
Review the new VirtualCenter database tables that are related to extensions.

Creating Windows Installers
Reveals some problems with creating Windows Installers for server extensions.

Namespaces
Details the namespaces and assemblies VMware provides to create plugins and extensions.

Terminology
Coins new terminology that developers can use when discussing the above concepts.




Link
Labels:

Comments

Post a Comment

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus
Post a Comment
Read more

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op
Post a Comment
Read more