=== dooferlad_ is now known as dooferlad
=== mpontillo_ is now known as mpontillo
=== Tribaal_ is now known as Tribaal
=== X-Istence is now known as x58
=== jefferai_ is now known as jefferai
=== frankban_ is now known as frankban
=== Guest26208 is now known as CyberJacob
[10:45] <rock_> Hi. I want to know  What "Curtin" script will do exactly ?  And Can I edit "curtin" Script?
[12:18] <rock_> roaksoax/kiko:  Can you please tell me about what "Curtin script " will do exactly?
[13:06] <roaksoax_> rock_: that cna be anything you want it to do
[13:06] <roaksoax_> maas uses curtin to the isntallation
[13:06] <roaksoax_> you can add extra scripts
[13:09] <rock_> roaksoax: Thank you. For enlisting, commissioning and deploying maas will use separate scripts right? I mean the scripts present under /etc/maas/preceeds
[13:10] <roaksoax_> rock_: different preseeds yes
[13:11] <rock_> roaksoax: So for example, If I write a script for deployment. So how I can I tell maas use my script instead of default one.
[13:12] <roaksoax_> rock_: you can't override MAAS' preseed completely
[13:12] <roaksoax_> rock_: you can do additional stuff, either before installation or after installation
[13:15] <rock_> roaksoax: So I understand like this. For Existing preseed scripts[whether commission script (or) deployment scripet(or) enlist script)  I can just  add stuff  right.
[13:17] <rock_> roaksoax: How MAAS will check the provided machines are ubuntu certified? MAAS will check or not?
[13:25] <rock_> roaksoax: So I have to give a demo to my collegues on MAAS. So I want to get clarification on my questions.
[13:31] <rock_> roaksoax/kiko: I am using dell servers.  In that i used SATA and SAS disks. So when MAAS discovered the dell nodes automatically, then I commissioned them . But MAAS not able to list nodes hard disks. But when I manually added nodes to MAAS and then did the commission then MAAS listing hard disks successfully. This was the problem with MAAS? I tried with both MAAS 1.9 and MAAS 2.0
[13:36] <rock_> roaksoax/kiko: In MAAS 1.9.4 cluster controller present in MAAS 2.0 rack controller replaced cluster controller. I saw fuctionality wise both are OK. MAAS UI is differed from MAAS 1.9 to MAAS 2.0. Apart from these MAAS rack controller has any specific feature?
=== jgr is now known as jgrassler
[14:12] <roaksoax_> rock_: In teh seetings page, try using Trusty with hwe-x as kernel for commissioning to discover your disks
=== lutostag_ is now known as lutostag
[14:24] <rock_> roaksoax: OK. thank you.  I will try that.
[15:02] <baldpope> anyone who has access to insights.ubuntu.com - verify database connection error?
[15:03] <roaksoax_> baldpope: some services are down atm
[15:03] <baldpope> ok, just making sure someone knew
[15:03] <baldpope> thanks roaksoax_
[15:03] <roaksoax_> baldpope: thank you!
[15:07] <baldpope> appears up roaksoax_
=== roaksoax_ is now known as roaksoax
[15:21] <samba35> i have installed local harddisk to maas client ,but in maas server gui when i try to depoly it give me message /error
[15:21] <samba35>  The deploy action for 1 node failed with error: {"storage": ["Specify a storage device to be able to deploy this node.", "Mount the root '/' filesystem to be able to deploy this node."]}
[15:21] <samba35> machine /client status is ready
[15:23] <samba35> this is my 1st maas client /server setup ,have no idea how to start from ,it could be procedure mistake  ?
[15:23] <samba35> when i click on machine on storage do i suppose to see hardisk ? or i have to create harddisk ?
[15:24] <samba35> Storage >>
[15:24] <samba35>     No storage information. Commissioning this node will gather the storage information.
[15:24] <samba35>     Specify a storage device to be able to deploy this node.
[15:24] <samba35>     Mount the root '/' filesystem to be able to deploy this node.
[15:25] <samba35> machine has 2 gb ram
=== daniel3 is now known as Odd_Bloke
=== frankban is now known as frankban|afk
=== Guest68174 is now known as med_
[19:00] <spaok> in MAAS / Juju 2.0, where does juju get DNS from? the machine I'm running juju commands on looks at the MAAS server for DNS, but the juju status shows the DNS as the IP's of the machines, MAAS 1.9.3 didn't have this issue and shows FQDN
[19:01] <spaok> the juju add-machine command used the MAAS names for the nodes with no issues
[20:42] <mup> Bug # changed: 1573528, 1623994, 1624522, 1625663, 1625668, 1625671, 1625674, 1625689, 1625812, 1626669, 1626722, 1626727, 1626748
[22:03] <mup> Bug #1623760 changed: [2.1] If Region and Rack controller are in the same machine, NTP service tracker is listed under rack <MAAS:Invalid> <https://launchpad.net/bugs/1623760>
[22:30] <mup> Bug #1627873 opened: [2.1 UI] Clicking on 'admin' in the first-user journey loops back to the first-user journey <MAAS:Confirmed> <https://launchpad.net/bugs/1627873>
[22:33] <roaksoax> ~/win 2
[23:00] <mup> Bug #1627884 opened: regiond PID should appear in regiond.log <MAAS:New> <https://launchpad.net/bugs/1627884>