[13:16] <amirali> hi everybody
[13:17] <amirali> can you help me about booting up vm nodes ?
[13:17] <amirali> i have 6 vm nodes
[13:18] <amirali> and a maas server
[13:18] <amirali> in selecting virsh
[13:18] <amirali> what setting in ssh-copy-id i should use?
[13:39] <kiko> sure
[13:39] <kiko> amirali, to start with, what version of MAAS are you using?
[13:42] <amirali> 14.04 lts ubunto server on vmware workstation 10
[13:49] <kiko> amirali, and maas 1.5? dpkg -l | grep maas?
[13:49] <kiko> I'm slow because I'm on the phone
[13:50] <amirali> nop 1.7.5
[14:30] <amirali> .....
[14:33] <kiko> amirali, I will have a few minutes in 5 minutes
[14:33] <amirali> thanks
[14:34] <kiko> amirali, ah, this isn't using virsh? i.e. http://askubuntu.com/questions/292061/how-to-configure-maas-to-be-able-to-boot-virtual-machines
[14:35] <amirali> wait a minute here is my question
[14:36] <amirali> the ip after "sudo -u maas -i ssh-copy-id ubuntu@"  is for what ? for node which you want to join or for maas server
[14:36] <amirali> i think its ip pf node that i want to join to maas server
[14:38] <kiko> amirali, it's for the host where you want to launch the VM.
[14:38] <kiko> amirali, but to be clear, that virsh power driver is to launch KVM instances on Linux, not VMWare
[14:39] <kiko> (that may be your expectation, I just want to be clear)
[14:39] <amirali> so you mean it may not work corectly ?
[14:39] <amirali> in vmware
[14:40] <kiko> amirali, well, it's more that you can't use vmware as the host for the VMs you want to launch
[14:40] <kiko> I believe you can with 1.8
[14:40] <kiko> mpontillo, ^^^
[14:42] <kiko> amirali, it may be possible to use virsh with the esx:// protocol, but I don't know how the authentication could be set up in that case
[14:42] <kiko> i.e. https://trickycloud.wordpress.com/2013/11/01/using-virsh-to-manage-vmware-vms/
[14:46] <amirali> kiko thanks for your help
[14:46] <amirali> but its usual vm not esx machine
[14:47] <amirali> i boot up ubunto from lan and then connects itself to maas server
[14:58] <kiko> hmm
[15:00] <mpontillo> amirali, kiko: yes, in MAAS 1.8 we will use the VMware API directly, via the python-pyvmomi package
[15:01] <kiko> mpontillo, can you show him some documentation?
[15:01] <mpontillo> virsh is hit or miss in this scenario; it may be possible for it to work, but on Trusty the libvirt is pretty old, and doesn't have good support for VMware, IIRC
[15:01] <kiko> amirali, I think I don't know what you are trying to do :)
[15:02] <amirali> so i have to use other virtualizarion software?
[15:02] <amirali> do you support virsh in virtualbox ?
[15:02] <mpontillo> kiko: amirali: https://maas.ubuntu.com/docs1.8/changelog.html has some notes on the new features in 1.8 w.r.t. virtualization
[15:05] <mpontillo> amirali: VMware and KVM are the best supported hypervisors in 1.8. you can use MAAS to automatically enlist all your VMware or KVM nodes (or a subset based on a name prefix) using the new "Add Chassis" feature in the UI (in 1.7 we have this, but it's only available via the API)
[15:06] <mpontillo> (I haven't had much luck with virsh and VirtualBox in Trusty; newer versions may work.)
[15:10] <amirali> so till the new version i should use what ?
[15:14] <kiko> amirali, I'm not sure because you haven't explained what you are trying to do
[15:14] <kiko> amirali, when you said vmware workstation 10 you confused me
[15:14] <kiko> amirali, virsh in 1.7 works with KVM VMs
[15:14] <kiko> amirali, running on Ubuntu hosts
[15:16] <amirali> let me be clear
[15:18] <amirali> i have a vmware workstation and created 7 separate virtual machines that i want to install all 7 nodes of maas  on those
[15:18] <amirali> one of them is maas server
[15:19] <amirali> and all remaining are maas nodes
[15:20] <amirali> i configured maas completly
[15:20] <amirali> and now i want my maas nodes jooin to maas server
[15:20] <amirali> all maas server and maas nodes are ubunto 14.04
[15:22] <mpontillo> amirali: on the MAAS server, I'd do "sudo chsh -s /bin/bash maas" and then "sudo su - maas", then see if about figuring out the virsh URL to properly manage that VMware box
[15:22] <mpontillo> for example, as the MAAS user, if I had KVM running on the local host, "virsh -c qemu:///system list --all" should show me the running VMs
[15:23] <mpontillo> if you can figure out an equivalent URL for VMware Workstation, it may work. (IIRC, the version of virsh that ships on Trusty may have bugs that prevent it from working with some versions of VMware, though, so YMMV)
[15:26] <amirali> virsh return nothing
[15:26] <mpontillo> amirali: additionally, I believe the VMware API (specifically for VMware Workstation) will only properly if you are using the "Shared VMs" feature in VMware Workstation
[15:26] <mpontillo> if the VMs were created in your $HOME, for example, I don't think they'll work
[15:27] <amirali> my base system is win7
[15:27] <amirali> and the localtion of machines are differenvt
[15:27] <mpontillo> amirali: well, just make sure they're in the "Shared VMs". I believe they have to be there or the APIs won't see them
[15:28] <amirali> let me check
[15:28] <mpontillo> on my Ubuntu install of Workstation 11, the API sees all the VMs, and they exist in /var/lib/vmware/shared
[15:28] <mpontillo> I haven't tested Workstation 10, so I don't know if this feature is available there
[15:30] <amirali> u mean all nodes should be in shared vms ?
[15:39] <mpontillo> amirali: all the ones you want MAAS to manage, yes
[15:40] <amirali> and maas server too ?
[15:41] <mpontillo> amirali: the way I set it up is to have the MAAS server in my user's namespace, and all the MAAS nodes in "Shared VMs". because MAAS will try to assimilate everything in there if you ask it to ;-)
[15:41] <mpontillo> it should be okay to put the MAAS server itself in "Shared VMs", but I prefer that it be isolated
[15:42] <mpontillo> amirali: the other thing you'll need to do, since you're on 1.7, is to manually go into the BIOS and set all those nodes to PXE boot. on 1.8, this is done for you when you use the "Add Chassis" feature to discover a VMware setup
[15:43] <mpontillo> what I've seen happen if you don't do this is, the nodes will work the first time, but not subsequently (since VMware's BIOS won't bother to try a PXE boot if it can boot from the virtual disk)
[15:43] <amirali> how may can get 1.8 ?i think its test version ?isnt it ?
[15:43] <mpontillo> amirali: it's on the verge of release, yeah
[15:44] <mpontillo> amirali: you can get it from here - https://launchpad.net/~maas-maintainers/+archive/ubuntu/testing
[15:45] <mpontillo> make sure to use "apt-get dist-upgrade" when you upgrade, and install the "python-pyvmomi" package (available in that PPA) to get the latest VMware support
[17:18] <amirali> hi every one
[17:24] <kiko> hello amirali
[21:18] <mup> Bug #1469305 opened: if hostname not set, sudo warning make maas throw 500 <landscape> <MAAS:New> <https://launchpad.net/bugs/1469305>