mup | Bug #1630123 opened: OpenStack base 45 not being deployed with Juju GUI <MAAS:New> <https://launchpad.net/bugs/1630123> | 06:37 |
---|---|---|
=== frankban|afk is now known as frankban | ||
PCdude | Hi all | 08:49 |
PCdude | I have some questions about openstack on ubuntu | 08:49 |
PCdude | I have put it in an askubuntu question | 08:49 |
PCdude | http://askubuntu.com/questions/832736/openstack-with-autopilot-some-networking-clear-up | 08:49 |
PCdude | Some about them are MAAS related | 08:49 |
Sujeet_ | Hi Kiko, Hi Roaksoax | 11:26 |
mup | Bug #1630123 changed: OpenStack base 45 not being deployed with Juju GUI <juju-core:New> <juju-gui:New> <https://launchpad.net/bugs/1630123> | 11:50 |
baldpope | good morning kiko roaksoax | 12:49 |
baldpope | fyi - ran through the conjure at about 4pm yesterday, 13hrs or so and it's just sitting idle, no progress | 12:50 |
baldpope | i'll dig into it more this morning | 12:50 |
stokachu | baldpope: what do you mean sitting idle? | 12:53 |
stokachu | at what point? | 12:53 |
baldpope | finished inputting in maas server ip, and the api key | 12:53 |
stokachu | baldpope: are you seeing machines being deployed in maas? | 12:54 |
baldpope | then the next screen shows which modules will be selected, i presumed the default would be sufficient, so left untouched | 12:54 |
baldpope | of the 5 nodes, 1 is deployed (previously in the ready state) the other 4 are sitting in the idle state | 12:55 |
baldpope | the deployed host is online, and ssh is on, but I cannot ssh into it - the ssh key I added is not accepted when I attempt to connect as ubuntu | 12:55 |
baldpope | ssh key I added to the webui | 12:55 |
stokachu | it's probably using the ssh key generated by juju | 12:56 |
stokachu | you can do juju switch controller;juju ssh 0 | 12:56 |
baldpope | from the maas host? | 12:56 |
stokachu | yea | 12:57 |
stokachu | well wherver you ran conjure-up | 12:57 |
baldpope | right | 12:57 |
baldpope | sysadmin@ubuntu-ap-brk:~/.local/share/juju/ssh$ juju switch controller | 12:57 |
baldpope | finch:admin@local/conjure-up -> finch:admin@local/controller | 12:57 |
baldpope | sysadmin@ubuntu-ap-brk:~/.local/share/juju/ssh$ juju ssh 0 | 12:57 |
baldpope | ERROR no API addresses | 12:57 |
stokachu | your bootstrap failed then | 12:57 |
stokachu | what does juju models show | 12:57 |
baldpope | cannot list models - no api addresses | 12:58 |
stokachu | yea your bootstrap failed | 12:58 |
stokachu | are you able to deploy a node via maas ui? | 12:58 |
baldpope | i believe so, | 13:00 |
baldpope | 1sec | 13:00 |
baldpope | yea, was able to deploy a new bloade with ubuntu 16.04 lts | 13:07 |
baldpope | and i can login with the ssh key assigned in webui | 13:08 |
stokachu | can you access the internet from that node? | 13:08 |
stokachu | also what version of juju are you running | 13:08 |
baldpope | 2.0-rc2-xenial-amd64 | 13:09 |
baldpope | apt install worked (presumably through maas controller) but running lynx www.google.com fails | 13:10 |
stokachu | and can you access the internet from that node? or run a `sudo apt update` | 13:10 |
stokachu | yea | 13:10 |
stokachu | your network isn't configured properly | 13:10 |
baldpope | apt update worked | 13:10 |
stokachu | thats from the maas proxy | 13:10 |
stokachu | do you have IP forwarding enabled on the maas server? | 13:11 |
baldpope | am I mistaken, but I thought maas also acted as squid proxy ? | 13:11 |
baldpope | stokachu, shit .. i'll bet not | 13:11 |
stokachu | yea assuming you setup the network config on the maas server properly :) | 13:11 |
stokachu | you also want to NAT that traffic | 13:11 |
stokachu | so you'll need to add that rule in iptables | 13:11 |
baldpope | i have a forward rule, but I don't have any nat rules | 13:12 |
baldpope | sigh .. did I miss a step somewhere, thought I followed closely | 13:12 |
stokachu | /docs/en/users/#customize-headless-mode | 13:12 |
stokachu | err | 13:12 |
stokachu | http://paste.ubuntu.com/23275006/ | 13:12 |
stokachu | baldpope: thats what i use for my private network | 13:12 |
stokachu | just change that to whatever network you're using | 13:13 |
baldpope | that's in /etc/iptables/rules.save or something? | 13:13 |
stokachu | http://paste.ubuntu.com/23275007/ | 13:13 |
stokachu | see the pre-up line | 13:13 |
stokachu | you can add it there | 13:13 |
stokachu | or save it | 13:13 |
stokachu | do all of your nodes have 2 nics? | 13:15 |
baldpope | yea | 13:15 |
stokachu | all eth0/eth1? | 13:15 |
baldpope | well, 6 | 13:15 |
baldpope | enp9s0f0 and enp9s0f1 | 13:15 |
stokachu | ok so when you get to the application list make sure to configure your neutron br-ext to be enp9s0f1 | 13:16 |
stokachu | it defaults to eth1 | 13:16 |
baldpope | the other 4 not currently plugged in | 13:16 |
stokachu | i would plug those in because you can't select the machine you want to use for neutron | 13:17 |
baldpope | the nics, you mean? | 13:18 |
stokachu | yea | 13:18 |
stokachu | well the machine that is housing neutron | 13:18 |
stokachu | you can't specifically select that machine, juju will grab one at random | 13:19 |
baldpope | stokachu, (or anyone else) if I've got the masq rule in place, do I also need to be running squid, or will it just forward the traffic? | 13:37 |
baldpope | wait.. | 13:39 |
baldpope | ok, i may not have setup networking correctly, the 'internal' network I created is routable through firewall - is not required to go through maas controller | 13:40 |
baldpope | and in this case, the individual nodes do not have access through firewall out - | 13:40 |
baldpope | so the question I have now is - should the nodes be required to go through the maas controller, or is it ok for them to have direct access out? | 13:40 |
stokachu | the easiest solution is to route everything through your maas server | 13:41 |
baldpope | hm | 13:41 |
baldpope | that's interesting | 13:41 |
baldpope | i would think I would want to use maas for dpeloyment, but not necessarily to act as the end-all routing uplink.. | 13:41 |
stokachu | it doesn't have to be | 13:42 |
stokachu | thats just the easiest solution | 13:42 |
baldpope | if that's the case, more care should be taken on the maas controller to use a bridge interface with sub interfaces for redundancy | 13:42 |
baldpope | so eth0 and eth1 in bridge with br0.1 as the wan and br0.2 as lan? | 13:43 |
baldpope | along with any other sub interfaces as required | 13:43 |
stokachu | yea that will work too | 13:43 |
baldpope | hm | 13:44 |
baldpope | ok, not going to mess with that just yet | 13:44 |
baldpope | I can update the firewall to allow my private segment out | 13:44 |
baldpope | but I'm not sure how that resolves the juju deploy? | 13:44 |
stokachu | because juju needs to resolve things like streams.canonical.com:443 | 13:46 |
baldpope | ah | 13:46 |
baldpope | i thought that was being done from the maas controller | 13:47 |
baldpope | my mistake | 13:47 |
baldpope | in my 5 node environment, after the juju controller has already been deployed, am I limited to using the remaining 4 for compute, so the 1 head is lost? | 13:55 |
stokachu | yea unfortunately | 13:59 |
baldpope | hm | 13:59 |
stokachu | juju 2 requires a node for the controller | 13:59 |
baldpope | well, that by itself isn't terrible | 13:59 |
baldpope | if you plan ahead, you can pick a host that would suffice for juju, but might not be the ideal compute/storage node | 14:00 |
baldpope | that's what I thought I was deploying on the maas box (an older dell poweredge) | 14:00 |
stokachu | so you can select which machine to perform the bootstrap on | 14:00 |
baldpope | well - not exactly | 14:00 |
stokachu | JUJU_BOOTSTRAP_TO=host.maas conjure-up -d openstack | 14:00 |
stokachu | ? | 14:00 |
baldpope | ah | 14:01 |
baldpope | sorry - thought you were asking me a question | 14:01 |
stokachu | this only works for maas and i haven't documented it yet | 14:01 |
baldpope | stokachu, that would work perfectly, if I had a spare host to deploy to | 14:01 |
stokachu | most people usually create a VM to house the controller | 14:01 |
baldpope | not complaining - just trying to understand the environmen | 14:01 |
stokachu | and just register that in the maas | 14:01 |
baldpope | yea, that makes sense | 14:02 |
baldpope | stokachu, not sure if it's progressing or not | 14:05 |
baldpope | http://imgur.com/LalU5zS | 14:05 |
stokachu | did it get passed fetching juju agent yet? | 14:06 |
baldpope | no, been sitting here for the last couple of minutes | 14:06 |
stokachu | yea it still can't get out to streams.canonical.com | 14:06 |
baldpope | and both the node and maas controller have unfiltered access out | 14:06 |
baldpope | hm | 14:06 |
baldpope | looking at firewall, no blocked traffic | 14:08 |
stokachu | deploy another node via maas and just see if you can wget from streams.canonical.com | 14:10 |
stokachu | like wget http://streams.canonical.com/juju/tools/agent/2.0-rc2/juju-2.0-rc2-xenial-amd64.tgz | 14:11 |
baldpope | testing - need a minute to deploy again | 14:14 |
baldpope | thanks for taking a few minutes stokachu | 14:15 |
stokachu | np | 14:15 |
baldpope | i've got pages of notes on my side where I've made mistakes, thinkgs I've forgotten after cleaning/reinstalling/deploying | 14:15 |
baldpope | will be happy to share any relevant bits once I get it cleaned up and repeatable | 14:16 |
stokachu | yea im sure roaksoax and the docs team would want to look at that | 14:16 |
shubjero | How does one configure a large amount of servers in maas with a specific disk layout? | 14:46 |
shubjero | I'd like to have 36 machines configured with the same partition layout | 14:47 |
shubjero | I'd rather not have to go through 36 times and do it all | 14:47 |
baldpope | stokachu, ok, a bit lost now... i've deployed a new node - i can perform nslookup on www.google.com, with the reply coming from maas controller, but attempting wget fails, though traffic is not blocked | 14:54 |
baldpope | i can ssh directly into the node using the key provided through webui | 14:55 |
baldpope | default route is out through firewall | 14:55 |
baldpope | stokachu, i appear to have a routing issue - have to work on this and report back - but will have to be later... | 15:30 |
stokachu | baldpope: ok | 15:31 |
mup | Bug # changed: 1392763, 1394792, 1459888, 1481285, 1508975, 1589640, 1593388, 1623110, 1623634, 1623878, 1625711, 1625714, 1627019, 1627038, 1627039, 1627363, 1628052, 1628213, 1628298, 1629004, 1629008, 1629011, 1629019, 1629022, 1629045, 1629142, 1629402, 1629491, 1629868, 1629896 | 16:40 |
=== frankban is now known as frankban|afk | ||
mup | Bug #1630343 opened: [2.1] upgrade from 2.0 to 2.1 broken <MAAS:New> <https://launchpad.net/bugs/1630343> | 18:16 |
mup | Bug #1629026 changed: [2.1] Images have been imported, but can't add a chassis <MAAS:Invalid> <https://launchpad.net/bugs/1629026> | 20:07 |
mup | Bug #1630361 opened: [2.1 ipv6] MAAS should refuse to deploy a host with bad address-family config <maas-ipv6> <MAAS:New> <https://launchpad.net/bugs/1630361> | 20:07 |
mup | Bug #1616232 changed: [2.1, 2.0] Installs should use GPT by default if volume is larger than 2TB <MAAS:Fix Released by blake-rouse> <MAAS 2.0:Triaged> <MAAS trunk:Fix Released by blake-rouse> <https://launchpad.net/bugs/1616232> | 21:19 |
mup | Bug #1630343 changed: [2.1] upgrade from 2.0 to 2.1 broken <MAAS:Fix Released by blake-rouse> <https://launchpad.net/bugs/1630343> | 21:19 |
mup | Bug #1616232 opened: [2.1, 2.0] Installs should use GPT by default if volume is larger than 2TB <MAAS:Fix Released by blake-rouse> <MAAS 2.0:Triaged> <MAAS trunk:Fix Released by blake-rouse> <https://launchpad.net/bugs/1616232> | 21:28 |
mup | Bug #1630343 opened: [2.1] upgrade from 2.0 to 2.1 broken <MAAS:Fix Released by blake-rouse> <https://launchpad.net/bugs/1630343> | 21:28 |
mup | Bug #1616232 changed: [2.1, 2.0] Installs should use GPT by default if volume is larger than 2TB <MAAS:Fix Released by blake-rouse> <MAAS 2.0:Triaged> <MAAS trunk:Fix Released by blake-rouse> <https://launchpad.net/bugs/1616232> | 21:34 |
mup | Bug #1630343 changed: [2.1] upgrade from 2.0 to 2.1 broken <MAAS:Fix Released by blake-rouse> <https://launchpad.net/bugs/1630343> | 21:34 |
mup | Bug #1630394 opened: [2.1] Bootloaders not downloaded on initial import <MAAS:Confirmed for ltrager> <https://launchpad.net/bugs/1630394> | 22:19 |
mup | Bug #1630398 opened: [2.0] EFI system fails to PXE boot: PXE-E23, Maas server returns TFTP error for bootx64.efi <oil> <MAAS:New> <https://launchpad.net/bugs/1630398> | 23:11 |
wililupy | MAAS 2.0 is not seeing all my interfaces on my server. How can I manually add them? | 23:13 |
wililupy | clarification, my rack controller can't see all of its interfaces. | 23:13 |
=== cyberjacob is now known as zz_cyberjacob | ||
=== zz_cyberjacob is now known as CyberJacob | ||
mup | Bug #1630398 changed: [2.0] EFI system fails to PXE boot: PXE-E23, Maas server returns TFTP error for bootx64.efi <oil> <MAAS:New> <https://launchpad.net/bugs/1630398> | 23:56 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!