Examples of VirtualMachineManager

com.cloud.vm.VirtualMachineManager
Manages allocating resources to vms.
com.cybozu.vmbkp.soap.VirtualMachineManager
@brief Manage a virtual machine.

com.sun.jdi.VirtualMachineManager

A manager of connections to target virtual machines. The VirtualMachineManager allows one application to debug multiple target VMs. (Note that the converse is not supported; a target VM can be debugged by only one debugger application.) This interface contains methods to manage connections to remote target VMs and to obtain the {@link VirtualMachine}mirror for available target VMs.

Connections can be made using one of several different {@link com.sun.jdi.connect.Connector} objects. Each connector encapsulatesa different way of connecting the debugger with a target VM.

The VirtualMachineManager supports many different scenarios for connecting a debugger to a virtual machine. Four examples are presented in the table below. The examples use the command line syntax in Sun's implementation. Some {@link com.sun.jdi.connect.Connector} implementations may require slightlydifferent handling than presented below.

Scenario	Description
Debugger launches target VM (simplest, most-common scenario)	Debugger calls the {@link com.sun.jdi.connect.LaunchingConnector#launch(java.util.Map)}method of the default connector, obtained with {@link #defaultConnector}. The target VM is launched, and a connection between that VM and the debugger is established. A {@link VirtualMachine} mirror is returned. Or, for more control Debugger selects a connector from the list returned by {@link #launchingConnectors} with desired characteristics(for example, transport type, etc.). Debugger calls the {@link com.sun.jdi.connect.LaunchingConnector#launch(java.util.Map)}method of the selected connector. The target VM is launched, and a connection between that VM and the debugger is established. A {@link VirtualMachine} mirror is returned.
Debugger attaches to previously-running VM	Target VM is launched using the options `-agentlib:jdwp=transport=xxx,server=y` Target VM generates and outputs the tranport-specific address at which it will listen for a connection. Debugger is launched. Debugger selects a connector in the list returned by {@link #attachingConnectors} matching the transport withthe name "xxx". Debugger presents the default connector parameters (obtained through {@link com.sun.jdi.connect.Connector#defaultArguments()}) to the end user, allowing the user to fill in the transport-specific address generated by the target VM. Debugger calls the {@link com.sun.jdi.connect.AttachingConnector#attach(java.util.Map)} methodof the selected to attach to the target VM. A {@link VirtualMachine}mirror is returned.
Target VM attaches to previously-running debugger	At startup, debugger selects one or more connectors from the list returned by {@link #listeningConnectors} for one or moretransports. Debugger calls the {@link com.sun.jdi.connect.ListeningConnector#startListening(java.util.Map)} method for each selectedconnector. For each call, a transport-specific address string is generated and returned. The debugger makes the transport names and corresponding address strings available to the end user. Debugger calls {@link com.sun.jdi.connect.ListeningConnector#accept(java.util.Map)}for each selected connector to wait for a target VM to connect. Later, target VM is launched by end user with the options `-agentlib:jdwp=transport=xxx,address=yyy` where "xxx" the transport for one of the connectors selected by the the debugger and "yyy" is the address generated by {@link com.sun.jdi.connect.ListeningConnector#accept(java.util.Map)} for thattransport. Debugger's call to {@link com.sun.jdi.connect.ListeningConnector#accept(java.util.Map)} returnsa {@link VirtualMachine} mirror.
Target VM launches debugger (sometimes called "Just-In-Time" debugging)	Target VM is launched with the options `-agentlib:jdwp=launch=cmdline,onuncaught=y,transport=xxx,server=y` Later, an uncaught exception is thrown in the target VM. The target VM generates the tranport-specific address at which it will listen for a connection. Target VM launches the debugger with the following items concatenated together (separated by spaces) to form the command line: The launch= value The transport= value The generated transport-specific address at which VM is listening for debugger connection. Upon launch, debugger selects a connector in the list returned by {@link #attachingConnectors} matching the transport withthe name "xxx". Debugger changes the default connector parameters (obtained through {@link com.sun.jdi.connect.Connector#defaultArguments()}) to specify the transport specific address at which the VM is listenig. Optionally, other connector arguments can be presented to the user. Debugger calls the {@link com.sun.jdi.connect.AttachingConnector#attach(java.util.Map)} methodof the selected to attach to the target VM. A {@link VirtualMachine}mirror is returned.

Connectors are created at start-up time. That is, they are created the first time that {@link com.sun.jdi.Bootstrap#virtualMachineManager()} is invoked.The list of all Connectors created at start-up time can be obtained from the VirtualMachineManager by invoking the {@link #allConnectors allConnectors} method.

Connectors are created at start-up time if they are installed on the platform. In addition, Connectors are created automatically by the VirtualMachineManager to encapsulate any {@link com.sun.jdi.connect.spi.TransportService} implementationsthat are installed on the platform. These two mechanisms for creating Connectors are described here.

A Connector is installed on the platform if it is installed in a jar file that is visible to the defining class loader of the {@link com.sun.jdi.connect.Connector} type,and that jar file contains a provider configuration file named com.sun.jdi.connect.Connector in the resource directory META-INF/services, and the provider configuration file lists the full-qualified class name of the Connector implementation. A Connector is a class that implements the {@link com.sun.jdi.connect.Connector Connector} interface. Moreappropriately the class implements one of the specific Connector types, namely {@link com.sun.jdi.connect.AttachingConnector AttachingConnector}, {@link com.sun.jdi.connect.ListeningConnector ListeningConnector}, or {@link com.sun.jdi.connect.LaunchingConnector LaunchingConnector}. The format of the provider configuration file is one fully-qualified class name per line. Space and tab characters surrounding each class, as well as blank lines are ignored. The comment character is '#' (0x23), and on each line all characters following the first comment character are ignored. The file must be encoded in UTF-8.

At start-up time the VirtualMachineManager attempts to load and instantiate (using the no-arg constructor) each class listed in the provider configuration file. Exceptions thrown when loading or creating the Connector are caught and ignored. In other words, the start-up process continues despite of errors.

In addition to Connectors installed on the platform the VirtualMachineManager will also create Connectors to encapsulate any {@link com.sun.jdi.connect.spi.TransportService} implementationsthat are installed on the platform. A TransportService is installed on the platform if it installed in a jar file that is visible to the defining class loader for the {@link com.sun.jdi.connect.spi.TransportService} type, and that jarfile contains a provider configuration file named com.sun.jdi.connect.spi.TransportService in the resource directory META-INF/services, and the provider configuration file lists the the full-qualified class name of the TransportService implementation. A TransportService is a concrete sub-class of {@link com.sun.jdi.connect.spi.TransportService TransportService}. The format of the provider configuration file is the same as the provider configuration file for Connectors except that each class listed must be the fully-qualified class name of a class that implements the TransportService interface.

For each TransportService installed on the platform, the VirtualMachineManager creates a corresponding {@link com.sun.jdi.connect.AttachingConnector} and{@link com.sun.jdi.connect.ListeningConnector}. These Connectors are created to encapsulate a {@link com.sun.jdi.connect.Transport Transport} that in turnencapsulates the TransportService. The AttachingConnector will be named based on the name of the transport service concatenated with the string Attach. For example, if the transport service {@link com.sun.jdi.connect.spi.TransportService#name() name()} methodreturns telepathic then the AttachingConnector will be named telepathicAttach. Similiarly the ListeningConnector will be named with the string Listen tagged onto the name of the transport service. The {@link com.sun.jdi.connect.Connector#description() description()} methodof both the AttachingConnector, and the ListeningConnector, will delegate to the {@link com.sun.jdi.connect.spi.TransportService#description() description()} method of the underlying transport service. Boththe AttachingConnector and the ListeningConnector will have two Connector {@link com.sun.jdi.connect.Connector$Argument Arguments}. A {@link com.sun.jdi.connect.Connector$StringArgument StringArgument}named address is the connector argument to specify the address to attach too, or to listen on. A {@link com.sun.jdi.connect.Connector$IntegerArgument IntegerArgument}named timeout is the connector argument to specify the timeout when attaching, or accepting. The timeout connector may be ignored depending on if the transport service supports an attach timeout or accept timeout.

Initialization of the virtual machine manager will fail, that is {@link com.sun.jdi.Bootstrap#virtualMachineManager()} will throw anerror if the virtual machine manager is unable to create any connectors. @author Gordon Hirsch @since 1.3

Examples of com.cloud.vm.VirtualMachineManager

    StateMachine2<Volume.State, Volume.Event, Volume> _stateMachine = Volume.State.getStateMachine();
    
    ComponentLocator locator = ComponentLocator.getLocator(ManagementServer.Name);
    VolumeDao volDao = locator.getDao(VolumeDao.class);
    VMInstanceDao vmDao = locator.getDao(VMInstanceDao.class);
    VirtualMachineManager vmMgr = locator.getManager(VirtualMachineManager.class);
    Long vmInstanceId = null;
    boolean success = true;
    Transaction txn = Transaction.open(Transaction.CLOUD_DB);


    try {
      txn.start();
      for (Long volumeId : _volumesIds) {
        VolumeVO volume = volDao.findById(volumeId);
        if (volume == null) {
          continue;
        }
        vmInstanceId = volume.getInstanceId();
        if (_migrateState == StorageMigrationState.MIGRATING && volume.getState() == Volume.State.Migrating) {
          try {
            _stateMachine.transitTo(volume, Volume.Event.OperationFailed, null, volDao);
          } catch (NoTransitionException e) {
            s_logger.debug("Failed to transit volume state: " + e.toString());
            success = false;
            break;
          }
        }
      }
      if (vmInstanceId != null) {
        VMInstanceVO vm = vmDao.findById(vmInstanceId);
        if (vm != null && vm.getState() == VirtualMachine.State.Migrating) {
          try {
            vmMgr.stateTransitTo(vm, VirtualMachine.Event.AgentReportStopped, null);
          } catch (NoTransitionException e) {
            s_logger.debug("Failed to transit vm state");
            success = false;
          }
        }

View Full Code Here

Examples of com.cybozu.vmbkp.soap.VirtualMachineManager

    public static void createSnapshot()
        throws Exception
    {
        String snapName = "snapshot-test";
        
        VirtualMachineManager vmm = gm_.searchVmWithName(vmName_);
        assert vmm != null;
        vmm.createSnapshot(snapName);


        SnapshotManager spm = vmm.searchSnapshotWithName(snapName);
        System.out.printf("-----disk list of %s of %s-----\n",
                          spm.getName(), spm.getVirtualMachine().getName());
        Utility.printList(spm.getConfig().getAllDiskNameList());


        System.out.printf("-----vmdkinfo list-----\n");

View Full Code Here

Examples of com.cybozu.vmbkp.soap.VirtualMachineManager

     */
    public static void deleteSnapshot()
        throws Exception
    {
        String snapName = "snapshot-test";
        VirtualMachineManager vmm = gm_.searchVmWithName(vmName_);
        assert vmm != null;
        vmm.deleteSnapshot(snapName);
    }

View Full Code Here

Examples of com.cybozu.vmbkp.soap.VirtualMachineManager

     * Ovf export of a virtual machine.
     */
    public static void exportOvf(String vmName)
        throws Exception
    {
        VirtualMachineManager vmm = gm_.searchVmWithName(vmName);
        if (vmm != null) {
            String ret = vmm.exportOvf();
            FileWriter fw = new FileWriter("ovf/" + vmm.getName() + ".ovf2");
            fw.write(ret);
            fw.close();
                
            VmbkpOvf ovf = new VmbkpOvf(ret);
            ovf.replaceFileLinkInReferences();
            String ret2 = ovf.toString();
            FileWriter fw2 = new FileWriter("ovf/" + vmm.getName() + ".ovf3");
            fw2.write(ret2);
            fw2.close();
        }
    }

View Full Code Here

Examples of com.cybozu.vmbkp.soap.VirtualMachineManager

    public static void deleteAllRestoredVm(int num)
        throws Exception
    {
        for (int i = 0; i < num; ++ i) {
            String vmName = "ovftest-" + String.valueOf(i);
            VirtualMachineManager vmm = gm_.searchVmWithName(vmName);
            if (vmm != null) {
                System.out.printf("destroy %s...", vmName);
                boolean ret = gm_.destroyVm(vmm);
                if (ret) {
                    System.out.printf("success\n");

View Full Code Here

Examples of com.cybozu.vmbkp.soap.VirtualMachineManager

        BackupInfo backupInfo = new BackupInfo(cmdLine_);
        
        for (String vmMoref: targetVmMorefList_) {
            
            /* Target virtual machine */
            VirtualMachineManager vmm = gm_.searchVmWithMoref(vmMoref);
            VmInfo vmInfo = vmm.getVmInfo();
            VmArchiveManager vmArcMgr =
                new VmArchiveManager(cfgGlobal_, vmInfo);


            boolean ret = false;
            try {

View Full Code Here

Examples of com.cybozu.vmbkp.soap.VirtualMachineManager

            throw new Exception(msg);
        }


        for (String targetVmMoref: targetVmMorefList_) {


            VirtualMachineManager vmm = gm_.searchVmWithMoref(targetVmMoref);
            VmInfo info = vmm.getVmInfo();
            if (gm_.destroyVm(vmm)) {
                System.out.printf
                    ("Destroy %s(%s) succeeded.\n",
                     info.getName(), info.getMoref());
            } else {

View Full Code Here

Examples of com.cybozu.vmbkp.soap.VirtualMachineManager

        assert (morefOfNewVm != null);
        msg = "import succeeded.";
        System.out.println(msg); logger_.info(msg);


        /* 6. Add contorollers and empty disks. */
        VirtualMachineManager vmm = gm_.searchVmWithMoref(morefOfNewVm);
        if (vmm == null) {
            throw new Exception("Could not find newly created vm.");
        }
        vmm.addEmptyDisks(vcmList);
        vmm.reload(); /* reload to get information of added disks
                         for the next step. */
        {
            int numDisks = 0;
            for (VirtualControllerManager vcm : vcmList) {
                numDisks += vcm.getNumOfDisks();
            }
            msg = String.format("add empty %d disks succeeded.", numDisks);
        }
        System.out.println(msg); logger_.info(msg);


        /* 7. Get VmdkInfo list for remote disk path of
              the newly created vmdk files,
              and get the corresponding diskId to restore.
              Then call vmdkbkp command to restore each vmdk file. */
        if (restoreInfo.isNoVmdk) {
            msg = String.format
                ("Disks are not restored because specified --novmdk option.");
            System.out.println(msg); logger_.info(msg);
            
        } else {
            /* Create snapshot and get moref of the snapshot. */
            Calendar cal = Calendar.getInstance();
            String snapName = generateSnapshotName(cal);
            createSnapshot(vmm, snapName);
            msg = String.format
                ("create snapshot name %s succeeded.", snapName);
            System.out.println(msg); logger_.info(msg);
                
            SnapshotManager snap = vmm.getCurrentSnapshot();
            if (snap == null || snapName.equals(snap.getName()) == false) {
                throw new Exception("Could not get snapshot.");
            }
            String snapMoref = snap.getMoref();

View Full Code Here

Examples of com.sun.jdi.VirtualMachineManager

        throw new IllegalStateException(e);
      }
    }


    private AttachingConnector getConnector() {
      VirtualMachineManager vmManager = Bootstrap
          .virtualMachineManager();
      for (AttachingConnector connector : vmManager
          .attachingConnectors()) {
        if ("com.sun.jdi.SocketAttach".equals(connector
            .name())) {
          return (AttachingConnector) connector;
        }

View Full Code Here

Examples of com.sun.jdi.VirtualMachineManager

    // either host,port will be set, or name
    private void connect(String host, String port, String name) throws Exception {
        // connect to JVM
        boolean useSocket = (port != null);


        VirtualMachineManager manager = Bootstrap.virtualMachineManager();
        List<AttachingConnector> connectors = manager.attachingConnectors();
        AttachingConnector connector = null;
//      System.err.println("Connectors available");
        for (int i = 0; i < connectors.size(); i++) {
            AttachingConnector tmp = connectors.get(i);
//          System.err.println("conn "+i+"  name="+tmp.name()+" transport="+tmp.transport().name()+

View Full Code Here

0 1

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.