search for: migrateable

Hi, As we talked in http://lists.xen.org/archives/html/xen-devel/2013-09/msg00211.html , I have a suggestion: what about merging xl save/restore/migrate/migrate-receive? Here is the description: xl-migrate.rst Also there is a workaround for the xl migration daemon example: xl-migrate-socat.rst Patch for the example: xen-xl-migrate-socat.patch (I don''t have enough knowledge to

I just put a new plugin named branchable_migrations on Github. Branchable migrations lets you separate your migrations into "branches" (i.e., a director under db/migrate) that each have their own version. Using the forthcoming UTC timestamped migrations and this plugin, you can separate migrations by table or feature. Doing so should alleviate many of the problems that seem to pike up

All, I''ve decided to jump into Migrations before I get too far along on the DB side of things. I already have some tables built, and I went ahead and built the migration that would have created them from scratch, and I made sure that there was a self.down section to drop them. I wanted to verify that I could roll back so I figured I would use rake to drop these pre-existing tables

Hey all, I''ve run into an interesting scenario that I think some of you might have some suggestions on. I am currently working on a RoR project and we are making full use of the migrations. We are also using a subversion repository for our source control. Now, the problem.... We are both making migrations and checking them into SVN. So, if in our checkout we have migrations up to 10 and

Hi Jérôme, Ben and Jason, below is a series against the hmm tree which starts revamping the migrate_vma functionality. The prime idea is to export three slightly lower level functions and thus avoid the need for migrate_vma_ops callbacks. Diffstat: 4 files changed, 285 insertions(+), 602 deletions(-) A git tree is also available at: git://git.infradead.org/users/hch/misc.git

Hi, I'm experimenting with the migration function of virsh. I'm doing the migrate with following commands: virsh migrate --life --persistent --copy-storage-all --verbose --abort-on-error domain qemu+ssh://root@destination/system virsh migrate-setmaxdowntime domain 20000 However sometimes at the end of the migration, the guest isn't started on the destination host. So I'm left

Hi all, I used the generate script to make a bunch of table migrations, resulting in files like 002_bookmarks.rb, 003_tags.rb, etc. When I did the ''rake migrate'', the db was set up but more migration files appeared, now called 009_create_bookmarks.rb, 010_create_tags.rb, etc. Now when I want to change the database (add a table or column, alter the schema) I do

There isn't any good reason to pass callbacks to migrate_vma. Instead we can just export the three steps done by this function to drivers and let them sequence the operation without callbacks. This removes a lot of boilerplate code as-is, and will allow the drivers to drastically improve code flow and error handling further on. Signed-off-by: Christoph Hellwig <hch at lst.de> ---

There isn't any good reason to pass callbacks to migrate_vma. Instead we can just export the three steps done by this function to drivers and let them sequence the operation without callbacks. This removes a lot of boilerplate code as-is, and will allow the drivers to drastically improve code flow and error handling further on. Signed-off-by: Christoph Hellwig <hch at lst.de>

Hi everyone, For one of our projects we have a need to deploy and maintain a demo. As a result I''ve attempted to setup a set of rake tasks for the job. My goal is have one rake task called "deploy_demo" which purges the database, migrates to the current schema, and loads the db from a set of fixture files in a specified location. I''ve written two new tasks the perform

On 7/29/19 7:28 AM, Christoph Hellwig wrote: > There isn't any good reason to pass callbacks to migrate_vma. Instead > we can just export the three steps done by this function to drivers and > let them sequence the operation without callbacks. This removes a lot > of boilerplate code as-is, and will allow the drivers to drastically > improve code flow and error handling

Hi Jérôme, Ben and Jason, below is a series against the hmm tree which starts revamping the migrate_vma functionality. The prime idea is to export three slightly lower level functions and thus avoid the need for migrate_vma_ops callbacks. Diffstat: 7 files changed, 282 insertions(+), 614 deletions(-) A git tree is also available at: git://git.infradead.org/users/hch/misc.git

Hi libvirt support, Can you please give me some example of how to use "virsh migrate --live" with p2p option including both source host and target host? I try to get some info from your website, but no info with migrate. [root at vmoactive02 qemu]# virsh help migrate NAME migrate - migrate domain to another host SYNOPSIS migrate [--live] [--p2p] [--direct]

Dear all The following process is about trying to do the " live migration at the same time with 5 Virtual machines ", but there is somthing problem with it. Process: yogi-pc2: # xm migrate --live vm01 pc2 & xm migrate --live vm02 pc2 & xm migrate --live vm03 pc2 & xm migrate --live vm04 pc2 & xm migrate --live vm05 pc2[1] 29983 [2] 29984 [3] 29985 [4]

Hi-- I''m trying to do a first migration (2.3.5). I generated a model "Video", but when I try to migrate I get "uninitialized constant Videos". Why is it trying to find a plural class name? Here''s more complete output: trans@logisys:models$ rake db:migrate --trace ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment **

Hi all, I''m confused about how migrations work. I''ve been using them for a couple of weeks but haven''t had any serious rollback issues yet. Just now I added a field to a table with a migration and ran "rake migrate", which added the field as expected. This was in the file db/migrate/007_mymigration.rb, making it version 7. Later I changed my mind and

Hi, This is a follow up of the mail regd migration I'd posted a few days ago. My scenario: I'm creating two virtual machines images from an Ubuntu 10.10 iso of RAM size 128 and 700 MB. Using the migrate() , I migrate it from the current physical machine to the destination machine via a 100 Mbps switch LAN connection. BOTH migrations take the same amount of time. Checking out the

I have a semi-grand plan for some changes to migrations. Mostly this is motivated by the upcoming 3.0 release and wanting to get migrations in engines working. 1. Don''t skip migrations with version numbers lower than "current". I only recently tripped over this, but apparently it''s been this way since 2.1 when we got timestamps masquerading as large/sparse

When trying to migrate my db using rake I get the following error message: rake aborted! No migration with version number 3 I am using sqlite3 as my database server. Any help is much appreciated. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email

## Hi ## I have 6 simple and fundamental Problem in RoR migration and although I googled it and read many article about it and research it for a week , I didn''t understand it. please help me for these problems : ---------- 1 - When I create a model (for example "rails generate model Football_League") , I see in db/migration a "create_football_leagues.rb" . I want