Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

Butterfly Container 2.1.9-beta (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Butterfly Container 2.1.9-beta (Default branch)
# 1  
Old 04-15-2008
Butterfly Container 2.1.9-beta (Default branch)
Butterfly Container is a Java dependency injection container. It is smaller (~100KB jar), yet more flexible and easier to use than Spring, Pico, and Guice (at least in the developers' opinion). Instead of XML, Butterfly Container is configured using a simple, flexible, Java-like configuration language, or by plugging plain non-annotation, non-reflection Java factories into the container. There are no external dependencies. License: The Apache License 2.0 Changes:
This release makes it possible to replace factories in the container at runtime. Factories that reference the replaced factory will automatically be updated to reference the new factory. The factory replacement feature is handy when unit testing a component using mock objects. Replace a real factory with a mock object factory to test if the component uses this collaborator (the mock object) correctly.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

vzmigrate

vzmigrate(8)							    Containers							      vzmigrate(8)

NAME

       vzmigrate - migrate a container between two OpenVZ servers

SYNOPSIS

       vzmigrate [-r|--remove-area yes|no] [--ssh=ssh_options] [--rsync=rsync_options] [--keep-dst] [--online] [-v] destination_address CTID

DESCRIPTION

       This  utility  is  used	to  migrate  a container from one (source) Hardware Node (HN) to another (destination) HN. The utility can migrate
       either stopped or running container. For a stopped container, simple CT private area transfer is  performed  (rsync(1)  is  used  for  file
       transfer). For running containers, migration may be offline (default) or online.

       This  program uses ssh as a transport layer. You will need to put ssh public key to destination node and be able to connect to node without
       entering password.

OPTIONS

       -r, --remove-area yes | no
	      Whether to remove a container area on source HN for the successfully migrated container. Default is yes.

       --ssh=options
	      Additional options that will be passed to ssh while establishing connection to destination HN.

       --rsync=options
	      Additional options that will be passed to rsync(8).  You may add options like -z to enable data compression  if  you  are  migrating
	      over a slow link.

       --keep-dst
	      Do  not  clean  synced  destination container private area in case of some error. It makes sense to use this option on big container
	      migration to avoid syncing container private area again in case some error (on container	stop  for  example)  occurs  during  first
	      migration attempt.

       --online
	      Perform  online (zero-downtime) migration: during the migration the container hangs for a while and after the migration it continues
	      working as though nothing has happened.

       -v     Verbose mode. Causes vzmigrate to print debugging messages about its progress.  Multiple -v options  increase  the  verbosity.   The
	      maximum is 3.

EXAMPLES

       Migration of CT 101 to 192.168.1.130 with downtime:

	  vzmigrate 192.168.1.130 101

       Online migration of CT 102 to 192.168.1.130:

	  vzmigrate --online 192.168.1.130 102

EXIT STATUS

       0 EXIT_OK
	      Command completed successfully.

       1 EXIT_USAGE
	      Bad command line options.

       2 EXIT_VE_STOPPED
	      Container is stopped.

       4 EXIT_CONNECT
	      Can't connect to destination (source) HN.

       6 EXIT_COPY
	      Container private area copying/moving failed.

       7 EXIT_VE_START
	      Can't start or restore destination CT.

       8 EXIT_VE_STOP
	      Can't stop or checkpoint source CT.

       9 EXIT_EXISTS
	      Container already exists on destination HN.

       10 EXIT_NOTEXIST
	      Container does not exists on source HN.

       12 EXIT_IP_INUSE
	      You attempt to migrate CT which IP address(es) are already in use on the destination node.

       13 EXIT_QUOTA
	      Operation with CT quota failed.

SEE ALSO

       rsync(1).

COPYRIGHT

       Copyright (C) 2001-2010, Parallels, Inc. Licensed under GNU GPL.

OpenVZ								    28 Jun 2011 						      vzmigrate(8)