[08:35] <blake_r> serverascode: its means you own the machine
[08:36] <blake_r> serverascode: you need to start the machine for it to deploy and install ubuntu
[08:36] <blake_r> serverascode: once you click start you will see the status change to deploying and then deployed once finished
[15:26] <malikeye> saltlake: I gave up on the openstack-install... I'm building everything from the OS docs now
[15:26] <saltlake> malikeye: Oh no!! which os docs ? Are on redhat or ubuntu ? I am guessing ubuntu ??
[15:27] <malikeye> http://docs.openstack.org/juno/install-guide/install/apt/content/
[15:27] <malikeye> installing Juno.... then I'll go through the process of upgrading to Kilo
[15:27] <saltlake> maikeye: U are on baremetal right ?
[15:27] <saltlake> No vms right ?
[15:28] <saltlake> malikeye: If I make no progress by midday with openstack-install I follow ur footsteps!!
[15:29] <malikeye> my controller and neutron nodes will be VM's, but the nova nodes are bare metal, yep
[15:38] <saltlake> malikeye: I just need a basic openstack so I can get to the storage aspect of things tp plug in the ceph cluster.. have no idea yet but hoe to get the openstack install done soon.
[16:30] <kiko> malikeye, what happened to cause you to give up?
[16:45] <saltlake> kiko, malikeye: I have progressed to my next problem with openstack-install: "There must be at least one machine, available in the MAAS cluster, that has both multiple disk and two or more network interfaces connected to the networks that are defined in MAAS. " reported in landscape. Now I know this error is valid. But I need a suggestion on the best way to fix.
[16:46] <saltlake> I created 2 networks and registered them on the cluster. 1. isolated at 192.168.254.0 and made that a managed network etc. 2. maas-eth0 that is created by default. The nodes come up connected on maas-eth0 but what do I need to do so they also connect to isolated nw ? They all have 2 mac addresses etc but do not get assigned an IP address on "isolated"
[16:47] <kiko> saltlake, that's normal, actually -- maas doesn't set the nodes to automatically configure any interface beyond the first (boot) interface
[16:48] <kiko> saltlake, so if that's where you're getting stuck then there's something else amiss
[16:48] <kiko> saltlake, now, does maas show two networks in your networks tab, with multiple interfaces attached to each?
[16:52] <saltlake> kiko: yes it does show 2 networks.. I am trying to paste an image someplace
[16:58] <saltlake> kiko: ON the maas page under networks: I see 2 networks: isolated and maas-etho wuth the network ip addresses. But landscape complains that there needs to be a node connected on 2 pr more networks and on "isolated" I see "attached nodes" to be 0
[16:59] <kiko> dpb1, ping?
[16:59] <saltlake> kiko: On each node I see 2 mac addresses from the VM interfaces info where one mac is not on any network.
[17:01] <kiko> saltlake, have you set both interfaces as managed by maas?
[17:01] <kiko> in the clusters page?
[17:02] <saltlake> Kiko: Yes I set the "isolated" to be also managed with DNS and DHCP and gave it an IP address etc and dynamic range etc.. but when I login to the maas-controller VM node.. and do an ifconfig -a
[17:02] <saltlake> I do not see the second ethernet interface get an IP address like eth0 on maas-eth0.
[17:02] <saltlake> (I hope I am being clear)
[17:02] <dpb1> saltlake: I'm looking for some instructions on this part, sec
[17:04] <saltlake> http://pastebin.com/BkVzXz2J :
[17:04] <dpb1> saltlake: some reference: http://askubuntu.com/questions/580427/openstack-deployment-with-maas-juju-and-autopilot
[17:05] <dpb1> saltlake: any neutron gateway capable node in your system will need to show up in maas on both networks.  sometimes you have to manually associate the mac address to the network in the maas network tab (the interface is a bit tedious there)
[17:06] <kiko> saltlake, as I said, the second interface won't get an IP address, that much is fine.
[17:07] <saltlake> dpb1: So when I click on the "isolated network" It does list under "Connected network interface cards" and lists ALL the mac addresses
[17:07] <saltlake> even the one on the second interface of the VM nodes.
[17:07] <dpb1> saltlake: also, we have found that your second network (the one that you don't want MAAS to manage) cannot have DHCP/DNS running when you go to use the cloud installer.  getting it set up with those settings is fine, but you will need to turn it off before proceeding.
[17:08] <dpb1> saltlake: and they all show up in maas-eth0, right?
[17:08] <saltlake> dpbq: Ok.. I am still reading on the link u sent to see how to manually add those nodes in on the second interface. maas-eth0 is no problem they all get an IP address and show connected.
[17:09] <saltlake> dpb1: BTW the isolated interface is a dummy. I don't know what it is going to be used for.. anything I really need to be aware of ?
[17:09] <saltlake> actually I know I need to know ALLLOOTTT more :-D
[17:10] <dpb1> saltlake: you don't need it, it's just a way some people like to configure things.  We actually test all the time with just one network in maas, as long as one machine has two network cards connected to that network, it should be fine.
[17:10] <saltlake> dpb1: thanks .. thanks alot for helping me out!!
[17:10] <saltlake> kiko: thanks ..
[17:10] <saltlake> this channel is super helpful
[17:11] <dpb1> saltlake: if you are making dummy networks (that are not physically separated), it could be leading to your issues.
[17:11] <dpb1> saltlake: http://www.ubuntu.com/download/cloud/install-ubuntu-openstack  <-- those instructions actually talk about the single network case.
[17:12] <saltlake> dpb1: I have everything on VMs on 1 server for familiary with Openstack.. with maas-eth0 things can get to the local network but the second nic is all virtual
[17:12] <saltlake> which is an isolated virtual network with the maas controller and the other VM nodes on it!!
[17:13] <saltlake> I really need to take some time to understand the architecture of all these components and how they talk to each other.
[17:13] <dpb1> saltlake: ok... reading up on another couple things
[17:13] <dpb1> sec
[17:17] <saltlake> dpb1: I added a machine to the "isolated" network and I running openstack-install again and hope to not hit the 4th checkbox in point 6 on this link  http://www.ubuntu.com/download/cloud/install-ubuntu-openstack
[17:18] <dpb1> saltlake: and, we don't really test the landscape openstack autopilot on KVM, since this is meant to be a bare metal installer.  You might instead want to try the single machine option of the openstack-installer?  There are some random issues you will run into with KVMs and MAAS.  Certainly there are people using it, but it's not a first-class citizen.  Just a warning.
[17:18] <dpb1> saltlake: you are of course free to try things out as you please. :)
[17:20] <nashville> well just figured i would drop by and thank everyone for their help yesterday
[17:20] <kiko> nashville, hey, did everything work out ok?
[17:20] <nashville> i cant get the screen to work but i have gotten everything installing and setup as i want
[17:20] <nashville> just have to ssh to the boxes
[17:20] <nashville> monitors are a no go
[17:21] <kiko> nashville, likely an intel vt issue -- did you experiment with changing the kernel params?
[17:21] <nashville> not sure if that means something but i would be interested to know if others can plug a monitor into the back of the hardware they install and it come up
[17:21] <nashville> i did
[17:21] <nashville> but still no dice
[17:21] <saltlake> dpb1: That is not good..for me :-( since I don't have the hardware at my disposal till I showcare how to connecte up a ceph cluster to it .. .. Do you know of another installer that might be more friendly .. wt=ith KVMs
[17:21] <nashville> i am having super problems with doing it in vm too
[17:21] <nashville> but if its hardware its great
[17:21] <nashville> exactly what i need
[17:22] <nashville> our company is about to implement maas for our project :)
[17:25] <roadmr> saltlake: if what you want is an openstack install, and not maas itself, you could perhaps try devstack (http://docs.openstack.org/developer/devstack/guides/single-machine.html), or if you have maas working and you're able to start nodes, but the openstack-install is still complaining, you could try a manual openstack install with juju
[17:25] <kiko> nashville, what are you building?
[17:25] <nashville> i like juju for what its worth
[17:25] <nashville> just a system to auto install all our machines we ship lots of hardware boxes out which all need ubuntu
[17:26] <nashville> and fai was a hassle
[17:26] <nashville> so i decided to try something new and went with maas
[17:26] <nashville> happy i did
[17:26] <kiko> nashville, cool, keep me posted on any issues you run into
[17:26] <nashville> so once they come up cfengine will see them install our software and after about thirty minutes they will be ready to ship
[17:26] <nashville> with our custom partition setup and our ssh keys
[17:27] <nashville> would have been a nightmare to do all that in fai
[17:27] <nashville> kiko you helped me out a lot yesterday though at the time it prob didnt seem like that
[17:27] <dpb1> saltlake: you used the 'openstack-installer' to get to this point right?
[17:27] <nashville> i know my name is different but im sure you remember me crying yesterday
[17:27] <dpb1> saltlake: openstack-install, I think is the command
[17:28] <kiko> I realized
[17:28] <nashville> seriously big thanks kiko i have never gotten support like that from anyone anywhere usually im just on my own
[17:28] <nashville> so sincerely thank you
[17:29] <kiko> you're welcome
[17:29] <kiko> if you need more help just ask! we work hard so maas should Just Work, but there's still quite a few rough edges so we put the effort into helping out
[17:30] <roadmr> saltlake: this question has some information on how to deploy openstack "manually" with juju: http://askubuntu.com/questions/78314/how-do-i-deploy-an-openstack-cloud-with-juju
[17:30] <nashville> you know im more than happy to do any testing or anything that would help out the community
[17:31] <nashville> maybe ill just sit in here and give what help i can now that i am through it and have a feel for everything
[17:31] <kiko> nashville, if you have the time, just blog about how you got your setup working and that's already help enough
[17:32] <nashville> i have been extensively writing about it on fb i guess i could just transfer that to a blog
[17:32] <nashville> dont think my private fb posts count lol
[17:33] <nashville> who are the people supplying support in here anyway?
[17:33] <nashville> you guys devs on this project is that how you know so much about it
[17:33] <nashville> all my info came from people who did what you just recommended and then you got me over the hump
[17:34] <dpb1> saltlake: the reason I asked, is just openstack-install has a single machine option, it may be better suited to what you are attempting to do.
[17:35] <saltlake> dpb1: Yes I will see if this last run of openstack-install also fails with something or the other.. I will quit and try single machine option. Then if that fails with follow roadmrs suggestion!! HA!!
[17:36] <saltlake> roadmr: thanks.. looks like others have given up with openstal-install !! I am another oneof those maybe but will findout and will live to blog about it !!
[17:36] <roadmr> saltlake: cool :) good luck heh
[17:36] <saltlake> roadmr: :-D thanks
[17:37] <malikeye> one of these would be nice : http://www.tranquilpcshop.co.uk/ubuntu-orange-box/
[17:39] <saltlake> malikeye: looks like a powere generator!!
[17:39] <saltlake> But in this case probably a power hogger
[17:40] <roadmr> saltlake: the PSU is only 320W, so it's lower-power than the average high-end gaming PC
[17:54] <saltlake> dpb1: atleast one thing got done: i.e as per page http://www.ubuntu.com/download/cloud/install-ubuntu-openstack  Point 6 got 4 green checkmarks
[17:56] <dpb1> saltlake: great, as I said, techincally the pieces are there and vms will work.  It's just not something we test.  that is what the single machine install is designed to do, but would be cool to see your results. :)
[17:57] <saltlake> dpb1: will def share results.
[17:58] <dpb1> great. :)
[18:09] <saltlake> dpb1: You were right.. landscape autopilot failed later. As soon as I tried to configure the stack, it fails to recognise atleast one machine connected to a "public interface" be it maas-eth0 or "isolated".
[18:11] <dpb1> saltlake: :(
[18:12] <saltlake> dpb1: I will now try the single machine install and see where it goes
[18:13] <dpb1> saltlake: great, #ubuntu-solutions on freenode has people who can help with it (they wrote it).
[18:13] <saltlake> dpb1: thanks for that tip
[18:13] <malikeye> meh... when I add the br-ext, I lose my gateway, even though I'm forcing the eth0 gateway to route correctly
[18:15] <saltlake> malikeye : I think I faced the same problem. I worked around that one by creating the network first on the MAAS controller and then adding that network interface to the Maas VM instance.. its weird
[18:32] <nashville> just wondering does this look correct to you guys
[18:33] <nashville>     500 10000 30720 ext4                            \                   $primary{ } $bootable{ }                \                   method{ format } format{ }              \                   use_filesystem{ } filesystem{ ext4 }    \                   mountpoint{ / }
[18:33] <nashville> well formatting sucks but you get the idea?
[18:35] <nashville> i am basically wanting to write all the parts to a certain size and leave the last one as /foo and have it consume the rest of the space
[19:17] <saltlake> malikeye: I am going to use your link now.. the single machine install with openstack-install is over 2 hrs and not proceeding..
[19:17] <stokachu> saltlake: takes awhile to complete, can you pastebin your ~/.cloud-install/commands.log?
[19:18] <stokachu> saltlake: also jump on #ubuntu-solutions so we don't pollute this channel
[19:34] <saltlake> stokachu: Sure I moved.
[22:04] <xipasduarte> Hello, can anyone help me out? I would like to know how does one update Maas to a newer version (same version of ubuntu) and if this is wise. I am using ubuntu 14.04 with maas 1.5
[22:23] <newell> xipasduarte, you can do an upgrade
[22:23] <newell> sudo apt-get update && sudo apt-get upgrade
[22:23] <newell> that should pull the new version of MAAS for you
[22:23] <xipasduarte> I did and the version stayed the same
[22:23] <xipasduarte> which I found a bit strange
[22:24] <newell> did you see the new version being installed?
[22:25] <xipasduarte> no, there never was an indication that the maas packages would be upgraded
[22:25] <newell> what does apt-cache policy maas give you?
[22:25] <xipasduarte> Installed: 1.5.4+bzr2294-0ubuntu1.3
[22:26] <newell> ppa:maas-maintainers/stable
[22:26] <newell> try adding htat
[22:26] <newell> that will give you the new 1.7.1 release
[22:26] <xipasduarte> I used the create Maas option on the ubuntu install process, might it be that the repositories were not added?
[22:26] <xipasduarte> yes, that did it
[22:27] <xipasduarte> thank you newell
[22:34] <newell> np xipasduarte