[00:28] <malikeye> j #ubuntu-solutions
[02:28] <smattan> hello I'm having some issues with my MaaS design and need some help if availible.  Has anyone been able to successfully deploy CentOS via MaaS?
[02:29] <smattan> I am also looking for Windows solutions. as currently the only clue I had at wiki.cloudbase.it/maas doesn't seem to work anymore
[05:47] <SimplySeth> would there be any objection to adding 'python-maas-client' and 'python-maas-provisioningserver' to PyPi  so that it can be used on all platforms ?
[06:32] <smattan> hello I'm having some issues with my MaaS design and need some help if availible.  Has anyone been able to successfully deploy CentOS via MaaS?
[11:49] <kiko> good morning
[11:50] <kiko> smattan, we haven't published docs on it, so I would assume nobody apart from blake_r has :)
[16:22] <saltlake> roadmr, malikeye: I tried everything I could read about adding a scsi controller to the guest and adding the blcok device.. but whatever I do the guest will not see the additional disks in lshw -class disk
[16:23] <roadmr> saltlake: I downloaded the openstack installer but it's really complex, I haven't yet figured out how it verifies compliance of the nodes :/
[16:25] <saltlake> roadmr: That is awfully sweet of u to do that.. but I am still stuck at my stupid VM unable to see more than its boot disk. I added a scsi controller and disks from the fedora page documentation .. and I am just unable to proceed!! :-(
[16:29] <saltlake> http://docs.fedoraproject.org/en-US/Fedora/18/html/Virtualization_Administration_Guide/sect-Managing_storage_controllers_in_a_guest.html
[16:46] <saltlake> roadmr: I FINALLY figured it out!!
[16:47] <roadmr> saltlake: \o/ yay! what'd you do?
[16:47] <saltlake> arggghhh : JOY!!
[16:47] <saltlake> http://pastebin.com/vcE7JetA
[16:47] <roadmr> cool :D
[16:48] <saltlake> roadmr: http://pastebin.com/MuzueVEy
[16:49] <roadmr> ohh I see, interesting way to define them as scsi
[16:52] <saltlake> roadmr: Yes without that lshs -c disk was not showing them as disk..
[16:53] <saltlake> HOWEVER : the maas webpage still does not show the "DISK (GB) to be a total of all 3 disks. I am hoping it picks up only the boot disk and that openstack installer still is able to finally work now!!
[16:53] <roadmr> saltlake: did you commission the node? it will only gather hardware information after commissioning
[16:54] <saltlake> roadmr: definitley I commissioend it and started it
[16:54] <roadmr> saltlake: oh! ok then it should... but that information is gathered from lshw, so if lshw shows them, I'm pretty sure maas will be happy
[16:54] <saltlake> roadmr: I then sshd to it like u told me to y'day and that's how I get the llshw -c disk info output
[16:57] <saltlake> roadmr: this is the best I have so will go ahead and hope openstack installer is able to proceed !!
[16:57] <roadmr> saltlake: hope it works :)
[16:58] <saltlake> roadmr: thanks!! again thanks for responding and helping me out
[16:58] <roadmr> saltlake: you did most of the work :)
[16:59] <kiko> saltlake, neat :)
[17:05] <saltlake> roadmr, kiko: thanks, it helps alot to ask and discuss here when I am all by myself headbanging in my little cave!!
[17:12] <mbruzek> whit juju quickstart bundle:~hazmat/kubernetes/kubernetes
[17:13] <mbruzek> wrong room
[17:16] <malikeye> saltlake: I believe it only picks up the boot disk
[17:16] <malikeye> well, it only reports that in maas
[17:16] <SimplySeth> kiko: I'm in the process of asking permission to add the maas api python module to PyPi so it can be 'pip installed' from any platform
[17:16] <saltlake> malikeye: cool but I have not got there yet but am hoping openstack installer still sees that!!
[17:17] <saltlake> malikeye: thanks..
[17:17] <malikeye> you'll find out when you get to the landscape part, if that's what you are goin
[17:17] <malikeye> doing
[17:17] <kiko> SimplySeth, that's cool, but do keep in mind it's part of a larger source tree -- I dunno how trees like that are handled
[17:17] <malikeye> I'm giving up on the bundled package.... gonna try the manual setup
[17:18] <malikeye> the automated one just fails and I can't figure out why... so step by step will at least let me narrow it down
[17:18] <SimplySeth> kiko: I copied the module dir to my mac and it's running fine.
[17:20] <SimplySeth> kiko: it just required 'pip install oauth'
[17:20] <kiko> SimplySeth, I am wondering how we will handle updates to it
[17:21] <SimplySeth> kiko: ahhh good point
[18:42] <johng> hi all.  SSH keys that I entered in MAAS gui show in new VM instances on bootup, but ssh attempts fail with permission denied (publickey)
[18:42] <johng> is there a better way to get teh kys in the instances working?  Or should I set a password somewhere in a kickstart or seed?
[18:49] <serverascode> johng: which user are you trying to log in as?
[18:50] <johng> not root.  using a regular user account $
[18:51] <serverascode> I think by default it creates an ubuntu user, but I just started using maas yesterday lol
[18:51] <johng> I put three keys from 3 diff machines in the MAAS UI preferences..
[18:51] <johng> all machines fail with same message
[18:51] <serverascode> ssh ubuntu@ip works for me with maas by default
[18:52] <johng> doh!  your awesome!   thanks
[18:52] <johng> I was thinking my user need to match the one at the end of the pub key..
[18:52] <johng> guess not
[19:30] <roadmr> johng: indeed the key you specify will be added to each node's "ubuntu" user's authorized_keys
[19:31] <roadmr> johng: you could add a Host block to your .ssh/config specifying User ubuntu for the IP addresses of your maas cluster, this would avoid mechanically typing ubuntu@ every single time :)
[19:40] <kiko> roadmr, +1 :)
[19:41] <roadmr> TBH I don't mind typing ubuntu@ as I rarely need to log into raw nodes... but it's useful for debugging/learning
[21:11] <saltlake> malikeye: I am now at another roadblock. I had all the client nodes on a private virtual network. I need the second nic so I added these lines to the VMs xml:    <interface type='bridge'>
[21:11] <saltlake>       <source bridge='br0'/>
[21:11] <saltlake>       <target dev='vnet2'/>
[21:11] <saltlake>       <model type='virtio'/>
[21:11] <saltlake>     </interface>
[21:11] <saltlake> where br0 is a bridge to the eth0 on the host machine.
[21:12] <saltlake> should this work to create 2 Nics per VM node ?
[22:00] <saltlake> I am certain my second nic is configured properly!! but starting the VMAASServer with the 2 network interfaces .. I can longer reach the MAAS apache website.. what is going on ?
[22:08] <saltlake> if anyone can pastebin their VM nodes xml with 2 NICs configured it would be awwesome ..
[22:22] <roadmr> saltlake: sorry, as usual :( I've only ever used one nic in virsh :(
[22:25] <serverascode> hi all, can I specify that a node gets a particular IP address using MaaS?
[22:25] <saltlake> roadmr: No problem :-) iTs a journey no issues.. I tried a few things .. I added a second interface to the MAAS controller eth1 from the MAAS controller page. THen I went back to the VMAAS virsh xml and updated it to have a second interface. After that I can atleast start the MAAS Controller and i still get the MAAS webpage working.
[22:26] <saltlake> roadmr: However ifconfig -a on the maasserver node does not assign the P address I specified on the cluster interface page setting.. (LIke when I set address 192.68.122.100 for eth0) ifconfig -a shows the same. that does not apply to eth1
[22:27] <roadmr> hmm..
[23:36] <serverascode> hi all...does "allocated to $user" mean the node is done, or should it have a status of deployed or something else? I'm having a hard time figuring out what the status should be