Project

Profile

Help

Task #7146

Investigate how Vagrant adapts docker containers to its environment and how to replace container in node with another container

Added by Alexander Kaluzhny almost 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Normal
Category:
-
Sprint/Milestone:
Start date:
28.06.2016
Due date:
% Done:

0%

Estimated time:
Target branch:
Test scenario:

https://dev.osll.ru/projects/mdbci/wiki/How_to_make_vagrant_docker_node_to_refer_to_another_running_docker_container


Description

Investigate how Vagrant creates docker instances.
Look for .vagrant directory in CONFIG and find out how vagrant defines docker container in its environment.
Generate config (attached file to this issue) in CONFIG. So you will have two nodes with ubuntu and centos.
Then after investigation try to replace node0 with node1 and node1 with node0. So before replacement you had ubuntu at node0 and centos at node1 (check it with ssh) and after you should have centos at node0 and ubuntu at node1 (check it with ssh).

As a result after generating config from attached file and replacing its nodes with each other, check that you have centos on node0 and ubuntu on node1 with ssh (to check linux distro type http://www.cyberciti.biz/faq/find-linux-distribution-name-version-number/) and describe how to replace docker nodes in Vagrant environment in wiki(in Vagrant section create new section 'How to replace docker nodes').

test.json (208 Bytes) test.json File with two nodes (ubuntu and centos) Alexander Kaluzhny, 29.06.2016 12:20

Related issues

Related to [mdbci] Maria DB Continuous integration tool - Task #7100: Implement "mdbci clone <configuration> <new_path>" commandClosed22.06.2016

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by Alexander Kaluzhny almost 5 years ago

  • Related to Task #7100: Implement "mdbci clone <configuration> <new_path>" command added

#2 Updated by Alexander Kaluzhny almost 5 years ago

  • File test.json test.json added
  • Subject changed from Create function that creates config template for docker cloned machines to Make node in new config refer to new cloned machine
  • Description updated (diff)

#3 Updated by Alexander Kaluzhny almost 5 years ago

  • Description updated (diff)

#4 Updated by Alexander Kaluzhny almost 5 years ago

  • Subject changed from Make node in new config refer to new cloned machine to Make node in new config to refer to new cloned machine

#5 Updated by Alexander Kaluzhny almost 5 years ago

  • Subject changed from Make node in new config to refer to new cloned machine to Make node in new docker config to refer to new cloned machine

#6 Updated by Alexander Kaluzhny almost 5 years ago

  • Subject changed from Make node in new docker config to refer to new cloned machine to Investigate how Vagrant adapts docker containers to its environment and how to replace it with another container
  • Description updated (diff)
  • Sprint/Milestone set to 0.9

#7 Updated by Alexander Kaluzhny almost 5 years ago

  • Copied to Task #7154: Make node in new docker config to refer to new cloned machine added

#8 Updated by Alexander Kaluzhny almost 5 years ago

  • Copied to deleted (Task #7154: Make node in new docker config to refer to new cloned machine)

#9 Updated by Alexander Kaluzhny almost 5 years ago

  • Subject changed from Investigate how Vagrant adapts docker containers to its environment and how to replace it with another container to Investigate how Vagrant adapts docker containers to its environment and how to replace container in node with another container

#10 Updated by Alexander Kaluzhny almost 5 years ago

  • Copied to Task #7155: Investigate how Vagrant adapts libvirt instances to its environment and how to replace instance in node with another instance added

#11 Updated by Alexander Kaluzhny almost 5 years ago

  • Copied to deleted (Task #7155: Investigate how Vagrant adapts libvirt instances to its environment and how to replace instance in node with another instance)

#12 Updated by Mark Zaslavskiy almost 5 years ago

  • Assignee set to Alexander Kaluzhny

#13 Updated by Alexander Kaluzhny almost 5 years ago

  • Status changed from New to Active / In progress

#14 Updated by Alexander Kaluzhny almost 5 years ago

  • Status changed from Active / In progress to New

#15 Updated by Alexander Kaluzhny almost 5 years ago

  • Status changed from New to Active / In progress

#16 Updated by Alexander Kaluzhny almost 5 years ago

  • Status changed from Active / In progress to New

#17 Updated by Alexander Kaluzhny almost 5 years ago

  • Status changed from New to Active / In progress

#19 Updated by Alexander Kaluzhny almost 5 years ago

  • Status changed from Active / In progress to Review
  • Assignee changed from Alexander Kaluzhny to Mark Zaslavskiy

#20 Updated by Mark Zaslavskiy almost 5 years ago

Please provide test scenario

#21 Updated by Mark Zaslavskiy almost 5 years ago

  • Status changed from Review to New
  • Assignee changed from Mark Zaslavskiy to Alexander Kaluzhny

#22 Updated by Alexander Kaluzhny almost 5 years ago

  • Status changed from New to Active / In progress

#23 Updated by Alexander Kaluzhny almost 5 years ago

  • Test scenario updated (diff)

#24 Updated by Alexander Kaluzhny almost 5 years ago

  • Status changed from Active / In progress to Review
  • Assignee changed from Alexander Kaluzhny to Mark Zaslavskiy

#25 Updated by Mark Zaslavskiy almost 5 years ago

  • Status changed from Review to Closed

Also available in: Atom PDF