=== menn0 is now known as menn0-afk | ||
=== frankban|afk is now known as frankban | ||
rock__ | roaksoax: Hi. I have MAAS 1.9.4 0n trusty. And 4 physical servers commissioned. Now I want to test our Openstack bundle on MAAS. On MAAS node I installed juju 2.0. And then I followed https://jujucharms.com/docs/2.0/clouds-maas. MAAS cloud juju model bootstrapping failed. Issue details : http://paste.openstack.org/show/581940/. Can anyone help me in this. | 12:31 |
---|---|---|
rock__ | roaksoax: Please help if you have any idea on this MAAS cloud bootstrapping. | 12:32 |
rock__ | roaksoax: from MAAS UI: Events Info: http://paste.openstack.org/show/582228/ | 12:33 |
rock__ | roaksoax: Console of the server https://imagebin.ca/v/2vj11ogqr5ud. | 12:33 |
rock__ | roaksoax: That deploying server released . MAAS UI Events info: MAAS UI: Events Info: http://paste.openstack.org/show/582231/. That server released. | 12:40 |
baldpope | rock__, not sure - but sounds identical to what I'm working on this week | 12:52 |
baldpope | kiko had pointed me to a different article, 1sec | 12:53 |
baldpope | https://insights.ubuntu.com/2015/11/08/deploying-openstack-on-maas-1-9-with-juju/ | 12:53 |
baldpope | also, these are probably of decent value - https://insights.ubuntu.com/?s=maas+1.9 | 12:54 |
rock__ | baldpope: Thank you. But my issue is different right. Once juju bootstrap done. Next directly we deploy the OpenStack base bundle here. You have successful [MAAS+openstack base] bundle setup?. | 13:05 |
baldpope | no, keep getting interrupted by other work/prod issues | 13:07 |
baldpope | but the 'plan' was to setup maas (done, bm server) and then be able to deploy/bootstrap openstack through maas | 13:07 |
baldpope | the original doc I was following I was told is not correct, by kiko | 13:08 |
baldpope | he pointed me to some of the articles I posted a moment ago | 13:08 |
baldpope | there's a at least 1 other person on the same path as you and I | 13:08 |
baldpope | and kiko and some of the other channel participants have been helpful | 13:09 |
baldpope | if you have questions, post and stay idle - someone will be along who can answer | 13:09 |
baldpope | are you attempting to deploy openstack through the juju charm? | 13:11 |
baldpope | side note - curious how you have your networking configured for the openstack servers | 13:12 |
baldpope | i have 5 boxes with a total of 7 nics, 1 ilom/ipmi , 2 on board, 4 via secondary nic | 13:13 |
baldpope | i had planned to put the 2 onboard into a lag, and use that as the networking for traffic, and then the 4 in a lag for disk sharing | 13:13 |
roaksoax | rock__: it seems you aborted the deployment | 13:14 |
roaksoax | or something aborted the deployment | 13:14 |
rock__ | roaksoax: Yesterday, It worked fine. But today due some other issue I reconfigured everything. Then I tried 5 times to bootstrap the maas cloud. But it was giving the same issue. I reconfigured MAAS again. But facing the same issue. How can I resolve this. Do you have any idea? please help me. | 13:17 |
rock__ | roaksoax: MAAS able to commission successfuly everytime. But curtin installation is aborting. | 13:19 |
roaksoax | rock__: what I see in the logs is the machine moves from Ready -> Deploying to Deploying -> Releasing -> Ready | 13:20 |
roaksoax | rock__: if it went through "Releasing" that means someone told MAAS to release the machine | 13:20 |
roaksoax | rock__: and that /may/ be juju | 13:20 |
rock__ | baldpope: Yes. I am thinkng that might be a juju bootstrap timeout. I am not sure. But Yesterday when I was doing the same thing curtin installation moving fastly without taking much time. Nearly it was taking 30 min. But today curtin installation has taken 30 min. But not bootstrapped. | 13:23 |
rock__ | roaksoax: sorry. previous message pointing you. | 13:23 |
rock__ | roaksoax: So in this situation, any idea from your side? | 13:25 |
rock__ | baldpope: I have taken 5 servers with 2 nics each. All are having IPMI connection. | 13:27 |
rock__ | baldpope: On one server I installed VBox. On top of that I created one VM. In that VM I installed MAAS. In that server for, first nic I provided public network. Second nic I created as router. I done with port forwarding and masqurading. | 13:30 |
kenytux | hello everyone | 13:39 |
kenytux | I really want to ask a question! | 13:40 |
kiko | good morning | 13:40 |
baldpope | rock__, sounds nearly identical - only difference is I re-purposed an old dell 2950 to act as the maas head | 13:40 |
baldpope | kenytux, ask away - sup kiko | 13:40 |
kiko | kenytux, it's your lucky day, questions are allowed on tuesdays | 13:40 |
kenytux | you make happy | 13:40 |
kiko | we try | 13:40 |
baldpope | 0_q | 13:40 |
kenytux | thank you | 13:40 |
baldpope | kiko make happy make baldpope cry ;) | 13:41 |
kenytux | how can I deploy a debian distribution with MAAS 2.0 please? | 13:41 |
kenytux | There's a way? | 13:41 |
baldpope | kenytux, guessing you'd need to import a debian image? | 13:41 |
kenytux | yes | 13:42 |
baldpope | kenytux, found this after quick search -http://www.travnewmatic.com/2015/02/ubuntu-maas-maas-image-builder-centos-6.html | 13:43 |
roaksoax | kenytux: /win 4 | 13:44 |
roaksoax | err | 13:44 |
roaksoax | kenytux: debain is not supported by defailt | 13:44 |
mup | Bug #1625636 opened: [2.1] bridge_all on allocate needs to bridge all unconfigured interfaces too <juju> <MAAS:Confirmed> <https://launchpad.net/bugs/1625636> | 13:44 |
kenytux | i've tried with image builder "maas-image-builder" on ubuntu 16.04/MAAS 2.0 failed at make step because of python version | 13:45 |
kenytux | is there clear steps should I do on iso file? | 13:47 |
kiko | kenytux, no clear steps unfortunately. we can help you with paid consulting, but the docs right now /are/ the source code for curtin | 13:57 |
kiko | I wish I had a better answer honestly and we are getting there | 13:57 |
kenytux | thank you very much!!!! ;) | 14:03 |
=== Guest14517 is now known as med_ | ||
rock__ | roaksoax: HI. I am trying to entire thing on MAAS 2.0. The node which is commissioning in MAAS 1.9 is not able to commission in MAAS 2.0. I mean not doing PXE boot to selected NIC. ERROR: PXE-E51 , No DHCP (or) Proxy DHCP offers were received. | 14:31 |
rock__ | roaksoax: Please help me in this. This is a network problem? | 14:32 |
kiko | rock__, maybe. the node is unable to get a DHCP response. | 14:35 |
kiko | rock__, have you enabled DHCP on the VLAN | 14:35 |
rock__ | Kiko: How to enable in MAAS 2.0.? I gave DHCP and Static Ip ranges. | 14:38 |
rock__ | Kiko: Yes. From MAAS2.0 UI, I observed dhcpd, dhcpd6 not enabled. and rackd — Missing connections to 1 region controller(s). | 14:43 |
mup | Bug #1625663 opened: [2.1] CLI usage differs from actual command <ssh-import> <MAAS:Triaged> <https://launchpad.net/bugs/1625663> | 14:44 |
rock__ | kiko: https://imagebin.ca/v/2vjhM0dTBu8E | 14:47 |
rock__ | Kiko: please tell me how to enable DHCP in MAAS 2.0. | 14:49 |
mup | Bug #1625668 opened: [2.1] When trying to add SSH keys for a GH user that doesn't exist, there's no feedback <ssh-import> <MAAS:Triaged> <https://launchpad.net/bugs/1625668> | 14:53 |
nirlevy | Hi all, can someone exlain to me the DNS configuration in MAAS to be use by landscape install | 14:56 |
nirlevy | I believe I do not configure the private network correctly, once landscape is spawned it looks for DNS in the MAAS node, which should be somewhat configured/ | 14:58 |
mup | Bug #1625668 changed: [2.1] When trying to add SSH keys for a GH user that doesn't exist, there's no feedback <ssh-import> <MAAS:Triaged> <https://launchpad.net/bugs/1625668> | 14:59 |
rock__ | nirlevy: You are using MAAS 1.9 (or) MAAS 2.0? | 15:01 |
mup | Bug #1625668 opened: [2.1] When trying to add SSH keys for a GH user that doesn't exist, there's no feedback <ssh-import> <MAAS:Triaged> <https://launchpad.net/bugs/1625668> | 15:08 |
rock__ | Kiko: From UI I enabled DHCP now. Thank you. Previouly I worked on MAAS 1.9.4. Present first time I am doing on MAAS 2.0 | 15:09 |
nirlevy | kiko: MAAS 1.9 | 15:10 |
nirlevy | MAAS Version 1.9.4+bzr4592-0ubuntu1 (trusty1) to be exact. | 15:10 |
nirlevy | which is the default for apt-get install maas over ubuntu 14.04.5 | 15:12 |
rock__ | nirlevy: You got MAAS UI right? | 15:14 |
rock__ | From MAAS UI, go to cluster there you will configure network interface. then modify "unmanaged" to "DHCP and DNS". Then mention static and dynamic ranges there. | 15:15 |
nirlevy | kiko, I have set clusters wrong previously, now I have public and private interfaces where private should be DHCP and DNS and public should be unmanaged. | 15:23 |
mup | Bug # changed: 1403257, 1452557, 1507724, 1512187, 1596522, 1597541, 1603590, 1607403, 1607980, 1609194, 1613701, 1613702, 1613704, 1615618, 1615686, 1616772, | 15:23 |
mup | 1616773, 1616962, 1617195, 1617591, 1617596, 1619202, 1620514, 1620903, 1621981, 1622770, 1623752, 1623753, 1624035, 1624154, 1624380, 1624516 | 15:23 |
mup | Bug #1625671 opened: [2.1] Need better error message when trying to add SSH keys for LP/GH user that doesn't exist <ssh-import> <MAAS:Triaged> <https://launchpad.net/bugs/1625671> | 15:23 |
mup | Bug #1625674 opened: [2.1] No feedback when there are no keys to import from LP/GH <ssh-import> <MAAS:Triaged> <https://launchpad.net/bugs/1625674> | 15:23 |
mup | Bug #1625676 opened: [2.0, 2.1, UI] MAAS webui allows boot disk to be changed on an already deployed node <sts> <ui> <MAAS:Confirmed> <MAAS 2.0:New> <MAAS trunk:Confirmed> <https://launchpad.net/bugs/1625676> | 15:23 |
nirlevy | I do not get the DNS zone though | 15:24 |
mup | Bug #1625689 opened: default gateway cannot be set to fe80::/64 via web ui <MAAS:New> <https://launchpad.net/bugs/1625689> | 15:36 |
mup | Bug #1625707 opened: NTP servers on regions and racks do not run in orphan mode <ntp> <MAAS:Triaged> <https://launchpad.net/bugs/1625707> | 15:57 |
mup | Bug #1625709 opened: Rack controllers only sync NTP from region controllers, not externally <ntp> <MAAS:Triaged> <https://launchpad.net/bugs/1625709> | 16:15 |
mup | Bug #1625711 opened: Peer selection for NTP servers on region controllers is broken <ntp> <MAAS:Triaged> <https://launchpad.net/bugs/1625711> | 16:15 |
mup | Bug #1625714 opened: DHCP services on rack controllers only publishes NTP servers on rack controllers <ntp> <MAAS:Triaged> <https://launchpad.net/bugs/1625714> | 16:15 |
=== saibarspeis is now known as saibarAuei | ||
=== frankban is now known as frankban|afk | ||
=== beisner is now known as beisner-food | ||
=== beisner-food is now known as beisner | ||
kkkkk | is there any requirements for conjure-up on 16.04? | 20:45 |
kkkkk | do i need unbuntu-desktop ? | 20:46 |
kiko | kkkkk, just apt-get install and go | 20:48 |
kkkkk | it's not working kiko | 20:49 |
kiko | kkkkk, that's not surprising, but without more information there's not much I can say! :) | 20:57 |
mup | Bug #1625809 opened: MAAS needs to detect and manage BMCs that are IPv6-only <maas-ipv6> <MAAS:New> <https://launchpad.net/bugs/1625809> | 21:00 |
mup | Bug #1625812 opened: [2.1] Error message is not user friendly <ssh-import> <MAAS:Triaged> <https://launchpad.net/bugs/1625812> | 21:00 |
kkkkk | kilo | 21:57 |
kkkkk | yaml.reader.ReaderError: unacceptable character #x0080: special characters are not allowed | 21:58 |
kkkkk | in "<unicode string>", position 1971 | 21:58 |
kkkkk | i keep getting that error with conjure-up 2 | 21:58 |
kiko | kkkkk, what are you deploying? | 21:59 |
kkkkk | i am trying to deploy openstack with maas 2 | 22:00 |
kiko | mmcc, stokachu: any clue what this is? | 22:01 |
kiko | kkkkk, reads like a bug to me, though, maybe report it to launchpad? | 22:01 |
* kiko waves out for the night | 22:03 | |
kkkkk | https://bugs.launchpad.net/ubuntu/+source/conjure-up/+bug/1625839 | 22:15 |
mup | Bug #1625847 opened: IPv6 commissioning needs to aggregate /128 networks <maas-ipv6> <MAAS:New for lamont> <https://launchpad.net/bugs/1625847> | 23:12 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!