Tuesday, 2014-11-11

*** naohirot has joined #openstack-ironic00:02
*** marcoemorais1 has joined #openstack-ironic00:02
*** marcoemorais1 has quit IRC00:02
*** marcoemorais1 has joined #openstack-ironic00:03
*** marcoemorais has quit IRC00:05
*** igordcard has joined #openstack-ironic00:09
*** zyluo_ has joined #openstack-ironic00:14
*** marcoemorais1 has quit IRC00:15
*** marcoemorais has joined #openstack-ironic00:15
*** igordcard has quit IRC00:17
*** penick has quit IRC00:18
*** achanda has joined #openstack-ironic00:20
*** achanda has quit IRC00:34
*** marcoemorais has quit IRC00:35
*** marcoemorais has joined #openstack-ironic00:36
*** marcoemorais has quit IRC00:36
*** marcoemorais has joined #openstack-ironic00:36
*** marcoemorais has quit IRC00:37
*** marcoemorais has joined #openstack-ironic00:37
*** zyluo_ has quit IRC00:39
*** achanda has joined #openstack-ironic00:47
yjiang5JayF: hi, what's the username/passwd for the IPA deploy kernel/ramdisk provided in the devstack?00:49
*** marcoemorais has quit IRC00:50
*** marcoemorais has joined #openstack-ironic00:50
*** anderbubble has joined #openstack-ironic00:57
*** anderbubble has quit IRC00:59
*** ryanpetrello has joined #openstack-ironic00:59
*** achanda has quit IRC01:08
*** nosnos has joined #openstack-ironic01:09
*** achanda has joined #openstack-ironic01:18
*** killer_prince has joined #openstack-ironic01:29
*** killer_prince is now known as lazy_prince01:29
*** chenglch has joined #openstack-ironic01:40
*** achanda has quit IRC01:41
*** achanda has joined #openstack-ironic01:42
*** achanda has quit IRC01:46
*** chenglch has quit IRC01:49
*** ryanpetrello has quit IRC01:50
*** victor_lowther__ has quit IRC01:56
*** victor_lowther__ has joined #openstack-ironic01:56
*** vdrok has quit IRC01:57
*** vdrok has joined #openstack-ironic01:57
*** dlaube has quit IRC02:01
openstackgerritZhongyue Luo proposed a change to openstack/ironic-specs: Dnsmasq DHCP service provider  https://review.openstack.org/13274402:08
*** mitz_ has joined #openstack-ironic02:14
JayFyjiang5: if you append "coreos.autologin" to the kernel command line, it should automatically login. Alternatively, bake an ssh key into the image.02:20
*** Viswanath has joined #openstack-ironic02:23
*** marcoemorais has quit IRC02:26
*** Viswanath has quit IRC02:26
*** cppforlife has joined #openstack-ironic02:42
*** subscope has quit IRC02:58
*** spandhe has quit IRC03:16
*** nosnos has quit IRC03:20
*** penick has joined #openstack-ironic03:53
naohirotHello Ironic team, I recently joined the community.04:03
naohirotIt took for a couple of weeks to realize that past logs are available at http://eavesdrop.openstack.org/irclogs/%23openstack-ironic.04:03
naohirotNow I'm reading them :-).04:04
*** shakamunyi has joined #openstack-ironic04:04
*** achanda has joined #openstack-ironic04:11
*** nosnos has joined #openstack-ironic04:12
*** penick has quit IRC04:13
*** subscope has joined #openstack-ironic04:24
*** pensu has joined #openstack-ironic04:25
*** achanda_ has joined #openstack-ironic04:34
*** achanda has quit IRC04:36
*** shakamun_ has joined #openstack-ironic04:45
*** shakamunyi has quit IRC04:49
*** rushiagr_away is now known as rushiagr04:51
*** pensu has quit IRC04:56
*** pensu has joined #openstack-ironic04:59
*** pcrews has quit IRC05:10
*** pensu has quit IRC05:15
*** chenglch has joined #openstack-ironic05:17
*** spandhe has joined #openstack-ironic05:25
*** spandhe_ has joined #openstack-ironic05:28
*** spandhe has quit IRC05:30
*** spandhe_ is now known as spandhe05:30
*** chenglch has quit IRC05:32
*** marcoemorais has joined #openstack-ironic05:36
*** marcoemorais1 has joined #openstack-ironic05:38
*** rakesh_hs has joined #openstack-ironic05:38
*** k4n0 has joined #openstack-ironic05:39
*** subscope has quit IRC05:40
*** marcoemorais has quit IRC05:41
*** chenglch|2 has joined #openstack-ironic05:44
*** pensu has joined #openstack-ironic05:48
*** foexle has joined #openstack-ironic06:26
*** achanda_ has quit IRC06:27
*** achanda has joined #openstack-ironic06:29
openstackgerritHarshada Mangesh Kakad proposed a change to openstack/ironic: Add serial console feature to seamicro driver  https://review.openstack.org/13262806:36
*** dlpartain has joined #openstack-ironic06:44
*** spandhe has quit IRC06:51
*** datajerk has quit IRC06:58
*** rushiagr is now known as rushiagr_away07:11
*** dlpartain has quit IRC07:20
*** dlpartain has joined #openstack-ironic07:20
*** achanda has quit IRC07:20
*** rameshg87 has joined #openstack-ironic07:22
*** yuanying has quit IRC07:32
*** adam_g` has joined #openstack-ironic07:33
*** jerryz has joined #openstack-ironic07:35
*** adam_g has quit IRC07:38
*** yuanying has joined #openstack-ironic07:44
*** rushiagr_away has quit IRC07:49
*** yuanying has quit IRC07:49
*** foexle has quit IRC07:53
*** jerryz has quit IRC07:56
*** yuanying has joined #openstack-ironic07:58
*** yuanying has quit IRC08:05
*** yuanying has joined #openstack-ironic08:07
*** yuanying has quit IRC08:09
*** yuanying has joined #openstack-ironic08:14
*** foexle has joined #openstack-ironic08:15
*** dlpartain has quit IRC08:15
*** yuanying has quit IRC08:19
*** achanda has joined #openstack-ironic08:21
*** ndipanov_gone is now known as ndipanov08:21
GheRiveromorning @ironic08:22
*** rushiagr has joined #openstack-ironic08:25
*** achanda has quit IRC08:26
*** Nisha has joined #openstack-ironic08:28
*** yuanying has joined #openstack-ironic08:34
*** yuanying has quit IRC08:38
*** ifarkas has joined #openstack-ironic08:44
*** yuanying has joined #openstack-ironic08:44
*** yuanying has quit IRC08:50
*** yuanying has joined #openstack-ironic08:50
*** chenglch|2 has quit IRC08:53
*** chenglch|2 has joined #openstack-ironic08:54
*** jistr has joined #openstack-ironic08:59
*** yuanying has quit IRC09:00
*** derekh has joined #openstack-ironic09:01
*** rameshg87 has quit IRC09:03
*** Marga_ has joined #openstack-ironic09:05
*** Marga_ has quit IRC09:05
*** Marga_ has joined #openstack-ironic09:05
*** yuanying has joined #openstack-ironic09:06
*** yuanying has quit IRC09:08
*** chenglch|2 has quit IRC09:08
*** jiangfei has joined #openstack-ironic09:10
*** dlpartain has joined #openstack-ironic09:13
*** yuanying has joined #openstack-ironic09:15
*** yuanying has quit IRC09:17
*** rameshg87 has joined #openstack-ironic09:18
*** lucasagomes has joined #openstack-ironic09:19
*** zhangyang_ has joined #openstack-ironic09:22
*** lazy_prince has quit IRC09:22
NishaHi lucasagomes09:30
*** yuanying has joined #openstack-ironic09:31
*** athomas has joined #openstack-ironic09:33
*** yuanying has quit IRC09:33
*** yuanying has joined #openstack-ironic09:36
*** MattMan has quit IRC09:37
*** yuanying has quit IRC09:37
*** MattMan has joined #openstack-ironic09:38
*** Marga_ has quit IRC09:43
*** yuanying has joined #openstack-ironic09:43
lucasagomesNisha, good morning/afternoon09:45
*** igordcard has joined #openstack-ironic09:46
*** mkerrin has quit IRC09:47
Nishalucasagomes: hi09:54
Nishalucasagomes: saw Dmitry's suggestion for properties discovery as discussed in summit.09:55
Nishalucasagomes: however i had some queries09:55
Nishalucasagomes: 1. When we say discover shall be a new state, then it shall be implemented as we have power/deploy today?09:56
Nishalucasagomes: secondly, is it necessary to do properties discovery async always? means a driver may want to do synchronously09:57
openstackgerritHarshada Mangesh Kakad proposed a change to openstack/ironic: Add serial console feature to seamicro driver  https://review.openstack.org/13262809:58
lucasagomesNisha, yeah there's still some talking need because the session we had (IMO) went a bit out of hands09:58
lucasagomesfor 1. yup, lemme show u the draft of the state machine09:58
*** leopoldj has joined #openstack-ironic09:58
Nishalucasagomes: ok09:58
lucasagomes2. (Assuming ur talking about out of band discovery) I believe that people will push hard to us to have it async, there's a strong opnion in the Ironic community that everything that touches the BMC should be done async09:59
Nishayes,09:59
Nishalucasagomes: hmmm but it can be left to driver/user also10:00
Nishalucasagomes: either way, the conductor will be able to honor it\10:00
*** romcheg has joined #openstack-ironic10:01
Nishalucasagomes: i am talking about generic node-properties spec10:01
lucasagomesNisha, https://plus.google.com/photos/+LucasAlvaresGomes/albums/6079343647897766897/6079343648628836562?pid=6079343648628836562&oid=11147261881738481610510:01
Nishalucasagomes: this is from summit ? :)10:02
*** pelix has joined #openstack-ironic10:02
lucasagomesNisha, yup10:02
Nishalucasagomes: :)10:03
lucasagomesNisha, right yeah, one good thing about the generic one is that we don't need to care about in-band anymore10:03
lucasagomesin-band will be a separated service10:03
*** sambetts has joined #openstack-ironic10:03
lucasagomesso we can focus on making it generic, cross-vendor, for the out-of-band10:03
Nishaok10:03
lucasagomesNisha, about left the driver choose in-band or out-of-band hmm it's possible, but wouldn't be nicer to be kinda standard one or another10:04
lucasagomesI see sync being easier, but for DRAC at least (AFAIK) we need to issue a couple of requests to the BMC10:04
lucasagomesso it has to be async10:04
lucasagomesit's not only 1 :(10:04
Nishalucasagomes: driver choosing in-band? i didnt get.... do u mean sync and async by this?10:05
lucasagomesNisha, no in-band is out of ironic codebase10:05
lucasagomesif people is willing to do in-band discovery they will need a third-party service to10:05
Nishayes , i was saying about this statement "<lucasagomes> Nisha, about left the driver choose in-band or out-of-band hmm it's possible"10:05
*** romcheg has quit IRC10:06
lucasagomesohhh10:06
lucasagomessync and async10:06
lucasagomesmy bad10:06
Nisha:)10:06
lucasagomeshaha early morning10:06
Nisha:)10:06
lucasagomesmixing words in my head here10:06
Nishaso i was just thinking to propose discovery rpcapi to be sync and async similar to what u have proposed for vendor_passthru10:07
Nisha;)10:07
Nishacopy-paste ;)10:07
Nishadoes it sounds ok?10:07
*** jiangfei has quit IRC10:08
lucasagomesNisha, I think so, but as an alert I think that it's going to get some push-backs, for iLO it may not be a problem but I believe that the overall understanding of BMCs is that it kinda sucks and can get jammed and the request would timed out10:09
lucasagomesso things like that should be async10:09
*** dlpartain has left #openstack-ironic10:10
lucasagomesbut no problems in proposing it10:10
lucasagomesI may be wrong10:10
*** ndipanov has quit IRC10:10
*** romcheg has joined #openstack-ironic10:12
*** ndipanov has joined #openstack-ironic10:12
*** yuanying has quit IRC10:14
*** jiangfei has joined #openstack-ironic10:19
*** yuanying has joined #openstack-ironic10:20
sambettsMorning lucasagomes10:21
lucasagomessambetts, yo morning10:21
*** achanda has joined #openstack-ironic10:23
naohirotGood morning lucasagomes,10:27
lucasagomesnaohirot, good morning there10:28
naohirotI have question regarding DRAC10:28
naohirothi10:28
*** achanda has quit IRC10:28
*** jiangfei_ has joined #openstack-ironic10:28
naohirotdo you have a document such us the iLO driver?10:28
naohirotI'll paste the URL10:29
naohirothttps://wiki.openstack.org/wiki/Ironic/Drivers/iLODrivers10:29
lucasagomesno :( I have to come up with some documentation for it. The only work I did on the DRAC was the management interface10:29
Nishalucasagomes: thanks, i will propose it and then lets see if it goes through10:29
lucasagomeswe will work more on the driver this cycle to support shiny new features like iLO does now10:30
Nishalucasagomes: thanks :)10:30
lucasagomesNisha, awesome! thanks10:30
naohirotI see.10:30
naohirotso I have very basic question.10:30
Nishalucasagomes: i said thanks for following : "we will work more on the driver this cycle to support shiny new features like iLO does now"10:30
Nisha:)10:31
lucasagomes:)10:31
naohirotIf user use pxe_drac driver10:31
*** dtantsur|afk is now known as dtantsur10:31
*** jiangfei has quit IRC10:31
dtantsurMorning Ironic10:31
sambettsMorning dtantsur10:31
* dtantsur is trying to wake up...10:31
Nishadtantsur: : morning10:31
naohirotwhat kind of benefit does user have?10:32
dtantsursambetts, Nisha, hi!10:32
Nishadtantsur: i left a ques for you in discovery spec ...10:32
dtantsurlemme see10:32
Nishai will catch it up in my night time10:32
Nishai have to leave office now10:32
naohirotiLO driver seems to provides some security benefit.10:33
lucasagomesnaohirot, right now, I don't think you have any benefits of using drac_pxe or ipmitool_pxe... But that said, we have specs up for DRAC to do auto discovery of the properties and RAID configuration10:33
Nishajust let me know your comments, i will then update spec and post it10:33
dtantsurNisha, ack10:33
lucasagomesnaohirot, we want to add support for virtual media deployment too10:33
lucasagomesnaohirot, indeed it does10:33
lucasagomesnaohirot, the HP guys are doing great supporting their hardware, the main person that was working on the DRAC from red hat last cycle had to step out a bit10:34
naohirotI see, so far auto discovery and RAID configuration are the target?10:34
lucasagomesbut he's back this cycle so we will try to catch up10:34
lucasagomesnaohirot, yup, and I believe virtual media10:34
naohirotOkay10:35
naohirotAnother basic question10:35
naohirotWhy doesn't Ironic mention anything about SMASH CLP?10:35
naohirotIPMI is enough for standard?10:36
naohirotstandard -> standard I/F.10:36
*** Nisha has quit IRC10:37
lucasagomeswell nobody proposed using it yet... and I believe most of the use cases for Ironic right now are happy with IPMI10:37
lucasagomesI mean not happy but that's the only thing they have10:37
lucasagomesthe biggest deployment of ironic AFAIK uses open compute so they only have vanilla IPMI to manage their machines10:38
naohirotOkay10:38
lucasagomesand we just graduated, the last cycle the focus were most targeting graduation10:38
lucasagomesso we did ton of works on the nova driver (that was the biggest hurdles) and tests (granade, tempest, migration)10:38
*** yuanying has quit IRC10:39
*** yuanying has joined #openstack-ironic10:39
naohirotYes, I understand. Ironic is still young. I have further basic question.10:39
naohirotI still didn't understand the difference between pxe_ipmitool and agent_ipmitool.10:40
lucasagomesyeah the names are a bit misleading there10:41
lucasagomesbut the difference is the way it's deployed10:41
naohirotI believe that both are PXE boots.10:41
lucasagomesnaohirot, yes, we def need to naming things better... lemem try to explain10:41
lucasagomesso for the "pxe_" namespace it mostly means PXE + ISCSI10:42
naohirotAgent install physical OS into local disk, on the other hand PXE didn't install anything into local disk.10:42
naohirotAm I correct?10:42
lucasagomeswhere a ramdisk will be booted, it will then expose the disk via ISCSI and the ironic conductor will copy the image (via dd) onto that disk10:42
*** marcoemorais1 has quit IRC10:42
lucasagomesthe "agent_" uses a more smart ramdisk that will boot on the machine and will fetch the image directly from glance/swift and copy it to the disk there10:43
lucasagomesnaohirot, both installs things on the local disk10:43
lucasagomesthe incosistency here is that "pxe_" always assume that the image is a partition image10:43
lucasagomesso even after deployed it will PXE boot the kernel+ramdisk to boot the machine10:44
naohirotOkay, both installs physical OS into local disk.10:44
lucasagomeswhere "agent_" assumed it's a full disk image, with a bootloader10:44
lucasagomesyes10:44
lucasagomeswe had a session in Paris about making it consistent10:44
lucasagomesthis is a bug right now, because both drivers behave difently and it's not exposed by the user10:45
lucasagomesnaohirot, https://etherpad.openstack.org/p/kilo-ironic-exposing-different-capabilities10:45
lucasagomesthis is the etherpad from the summit10:45
naohirotOkay, in case of pxe_, user have to make partition by hands.10:45
lucasagomesnaohirot, not really, the Ironic conductor will partition the disk10:45
lucasagomesover ISCSI10:46
naohirotbut in case of agent_, agent takes care of partition.10:46
*** yuanying has quit IRC10:46
naohirotOkay, in case of pxe_, physical server must support iSCSI?10:46
lucasagomesboth of them will take care of the partition, but the "pxe_" always do network boot because the image does not contain a bootloader (it's a partition image) nor the ironic conductor installs a boot loader10:47
lucasagomesnaohirot, yeah, the ramdisk built will include all the iscsi modules/clients10:47
naohirotAha, I see.10:47
* lucasagomes realizes how much we need to make it consistent asap10:48
naohirotRight now, physical server has to have local disks. If there is no local disk, what happens?10:49
*** Haomeng has joined #openstack-ironic10:49
lucasagomesnaohirot, yup right now we assume they do10:50
lucasagomesnaohirot, deploy fails :)10:50
*** Haomeng|2 has quit IRC10:50
lucasagomesnaohirot, jroll was looking into having diskless deployments10:50
lucasagomessomeone have raised it in the conference too10:50
naohirotI see, how about if physical server had HBA card and SAN.10:51
naohirotIs it recognized as local disk?10:51
*** ndipanov has quit IRC10:52
naohirotI see, it seems there are a lot of interesting discussion. I wanted to be there :-)10:54
lucasagomesyeah I haven't tried that... If the disk is exposed as a local disk perhaps that may work10:55
lucasagomesyeah it was pretty interesting indeed10:56
naohirotI see, I'll try later the case of SAN.10:57
lucasagomesthere are many use cases, it's good that our drivers interface are flexible to support that (and we should work on some consistency mechanism)10:57
lucasagomesbut we need people to code10:57
lucasagomesand review stuff10:57
lucasagomesnaohirot, awesome10:57
naohirotyes, I'll report the result if we tried.10:58
lucasagomesta much10:59
naohirotoh, another question. drac and ilo have separate python package of SOAP/XML part.10:59
naohirotIs it decision based on some policy?11:00
naohirotIn case of iRMC, do I have to separate SOAP/XML as external library?11:01
openstackgerritA change was merged to openstack/ironic: Remove redundant FunctionalTest usage in API tests  https://review.openstack.org/13349011:02
lucasagomeshmm I'm not sure cause I haven't started any of those drivers, DRAC uses python-wsman and iLO proliantutils11:02
lucasagomesrameshg87, ^11:02
*** yuanying has joined #openstack-ironic11:03
lucasagomesif iRMC supports the same wsman or the other I don't see why not use it11:03
lucasagomesI mean one less cross-driver dependency11:03
naohirotIt seems that iRMC http/https I/F is not pure SOAP.11:04
naohirotSo wsman would not work, I believe.11:05
*** yuriyz has quit IRC11:05
lucasagomesright11:05
*** ndipanov has joined #openstack-ironic11:05
lucasagomesas a note, all those third-party libraries are not dependencies for Ironic itself11:05
lucasagomesoperators should install those on their images depending on the driver they choose to use11:06
naohirotIn case of iRMC, there is no way to get boot device and set boot device, and get list of boot devices.11:06
naohirotvia SOAP.11:06
naohirotvia http/https SOAP alike.11:07
dtantsurlucasagomes, hi, sorry to interrupt, but who and when is going to work on the state machine reform? do you have an idea? this thing kinda blocks everything :)11:07
lucasagomesnaohirot, can it be done via ipmi? if so you may want to take a look at pyghmi as a lib for that11:07
naohirotYes.11:08
lucasagomesdtantsur, I've no idea to be honest11:08
lucasagomesdtantsur, yup, it should be done soon, but I don't know if someone actually proposed to work on that11:08
dtantsurah ok. I suppose it's devananda himself, but I maybe completely wrong :)11:08
*** yuanying has quit IRC11:08
*** romcheg1 has joined #openstack-ironic11:08
lucasagomesdtantsur, I think that it's open in the air for someone willing to do it11:08
lucasagomesI was assuming it would be kinda a plumbing for the decom work11:09
*** romcheg has quit IRC11:09
dtantsurwell mostly, but it also blocks discovery11:09
lucasagomesindeed11:09
dtantsurlucasagomes, also, could you have a quick a look at https://review.openstack.org/#/c/100951/ to see if my comments there make any sense?11:10
lucasagomes+1 it's on my todo list11:10
lucasagomesjust finishing something quicker here and I will take a look at it11:10
*** yuanying has joined #openstack-ironic11:12
dtantsurack11:12
naohirotlucasagomes: In case of iRMC, I'm thinking to use SM CLP to get/set boot device form the management I/F. Do you think it's appropriate?11:12
*** romcheg has joined #openstack-ironic11:13
naohirots/form/for11:13
*** romcheg1 has quit IRC11:13
lucasagomesnaohirot, I don't see why not, specially if by using SM CLP enables you to have more advanced management control11:14
*** yuanying has quit IRC11:15
naohirotI see. The reason I asked is that SM CLP is a standard. so I just wandered.11:15
lucasagomesand also we will have some smash code :) maybe other drivers may be interested in using it in the future too11:15
lucasagomessure11:16
naohirotI see.11:16
naohirotThank you for sparing your time, lucasagomes!11:17
naohirotI'll read the references you kindly gave me.11:17
lucasagomesnaohirot, no problem, ure very welcome11:17
naohirotMaybe I'll ask other questions tomorrow :-)11:18
lucasagomes+1 :D11:18
naohirotsee you!11:18
lucasagomessee ya11:18
*** sambetts_ has joined #openstack-ironic11:40
openstackgerritLucas Alvares Gomes proposed a change to openstack/ironic: Add sync and async support for passthru methods  https://review.openstack.org/12966211:42
openstackgerritLucas Alvares Gomes proposed a change to openstack/ironic: Make vendor methods discoverable via the Ironic API  https://review.openstack.org/13353311:42
openstackgerritLucas Alvares Gomes proposed a change to openstack/ironic: Vendor endpoints to support different HTTP methods  https://review.openstack.org/12994211:42
openstackgerritLucas Alvares Gomes proposed a change to openstack/ironic: Add a mechanism to route vendor methods  https://review.openstack.org/12926111:42
*** sambetts has quit IRC11:42
rameshg87lucasagomes, just reading back11:46
*** yuriyz has joined #openstack-ironic11:46
lucasagomesrameshg87, morning/afternoon... no worries11:49
rameshg87lucasagomes, morning :)11:50
rameshg87lucasagomes, was away from my desk :)11:50
lucasagomesrameshg87, I see :D11:51
*** naohirot has quit IRC11:51
rameshg87naohirot, we have proliantutils module that talks to the iLO using a protocol called RIBCL over HTTPS. basically sends in XML to iLO and gets back XML from iLO. we have made it as a python module: https://github.com/hpproliant/proliantutils/11:52
rameshg87oh i guess you quit right before i sent you the message11:52
rameshg87lucasagomes, i am thinking we can do some testing on gate with virtual media with kvm/virtual box.11:53
rameshg87lucasagomes, if we refactor virtual media out and make it implementation independent11:53
rameshg87lucasagomes, basically it requires just a virtual media floppy and virtual media cdrom that kvm/virtual box already provides11:54
rameshg87lucasagomes, what do you think ?11:54
lucasagomesrameshg87, you mean adding it to the SSH driver?11:54
rameshg87lucasagomes, yes .. virtual media driver with ssh :)11:54
lucasagomesrameshg87, I think it's good, but I don't know exactly what are the benefits since we are not testing anything there11:55
lucasagomesI would love to have a IPMI listener service11:55
rameshg87lucasagomes, is there one ?11:55
lucasagomesthat would convert the IPMI commands to KVM/VBOX11:55
*** andreykurilin has joined #openstack-ironic11:55
lucasagomesbecause then at least we can test the contract with the IPMI commands see if they are correct etc11:55
lucasagomesrameshg87, not really :( not that I know at least11:56
lucasagomesbut once we do that we can test the ipmi* drivers on gate too, and finally delete the ssh one11:56
lucasagomescause it's just a work around really :/11:56
rameshg87lucasagomes, my thought we could test entire solution without actual hardware then - building the images, building the configs, uploading to swift, etc ..11:56
lucasagomesrameshg87, NobodyCam started working on something along tthat lines11:56
rameshg87lucasagomes, all these don't play with real hardware11:56
lucasagomesrameshg87, oh, yeah indeed that would be important to test the generation of the ISO11:57
rameshg87lucasagomes, yes11:57
lucasagomesyeah I see the benefit11:57
lucasagomesI wouldn't mind in having it in gate11:57
rameshg87lucasagomes, yeah let me just think more about it and come up with a proposal11:57
lucasagomes+111:57
rameshg87lucasagomes, are you working on boot-deploy interface separation ?11:58
lucasagomesrameshg87, not currently, I started looking into it and put some patches up11:58
rameshg87lucasagomes, are they on gerrit ?11:58
lucasagomesbut haven't finished the work11:58
lucasagomesrameshg87, inputs are welcome11:58
lucasagomesrameshg87, yup they are11:58
rameshg87lucasagomes, would like to have a look :)11:58
lucasagomesrameshg87, https://review.openstack.org/#/c/127212/11:59
lucasagomesstarts there11:59
rameshg87lucasagomes, got it11:59
lucasagomesbut they are proof of concept11:59
rameshg87lucasagomes, i have one question12:00
rameshg87lucasagomes, do we need to make this mandatory that every driver should have boot and deploy separately ?12:00
rameshg87lucasagomes, couldn't it be one way of making a deploy driver ?12:00
rameshg87lucasagomes, what i meant was someone could still write a deploy driver with the before interfaces12:01
lucasagomesrameshg87, I believe that at the beggining we can't make it mandatory because drivers out of tree will break if we make it mandatory12:01
rameshg87lucasagomes, yes12:01
rameshg87lucasagomes, so boot interface is not mandatory for driver according to you ?12:01
lucasagomesbut in the future, if we separate I think it makes sense to implement a boot interface and deploy interface separated12:02
lucasagomesrameshg87, well I haven't thought much about it to be honest12:02
rameshg87lucasagomes, okay12:02
lucasagomesI understand that as a start point it can't be mandatory, but idk in the future it kinda makes sense to make people to divide the logic12:02
lucasagomesotherwise we lose the benefits of separating it12:03
rameshg87lucasagomes, hmm ..okay .. i still wanted to discuss more on that ..12:03
lucasagomes+112:03
rameshg87lucasagomes, but time to leave office :)12:03
rameshg87lucasagomes, will join you later ..12:03
lucasagomesrameshg87, have a nice evening :)12:03
rameshg87lucasagomes, have a good day :)12:04
*** rameshg87 has quit IRC12:04
*** Marga_ has joined #openstack-ironic12:05
*** Guest9136 has joined #openstack-ironic12:09
*** Guest9136 is now known as annegentle12:10
*** nosnos has quit IRC12:13
*** nosnos has joined #openstack-ironic12:14
*** jiangfei_ has quit IRC12:15
*** nosnos has quit IRC12:18
*** jistr is now known as jistr|english12:23
sorenIs there a documented way to perform kernel updates for nodes managed by Ironic?12:24
*** naohirot has joined #openstack-ironic12:29
*** pensu has quit IRC12:38
sorenSomehow I need to get the kernel and ramdisk refs updated in Nova's db... Then I need to get Ironic to reread that data and repopulate the tftpboot dir.12:44
sorenSurely someone must have needed to update their kernels before?12:44
*** andreykurilin has quit IRC12:56
*** andreykurilin has joined #openstack-ironic12:56
lucasagomessoren, hi that's a good point. I don't think we have a mechanism for it12:58
lucasagomesI'm wondering whether rebuild would be the right way to do that12:58
lucasagomesmaybe that's a bit overkill too12:58
lucasagomessoren, I don't understand the Nova's db part12:59
sorenlucasagomes: Well, I tell nova which kernel/ramdisk I want to use.13:02
sorenlucasagomes: ....and Nova passes that info on to Ironic somehow.13:02
lucasagomessoren, that's in the glance image right?13:02
lucasagomesin glance, the image has metadata about what is the kernel and ramdisk13:02
sorenThat's the typical approach, yes.13:02
lucasagomesin nova nova you say that you want to use that image, so Ironic looks at the glance image metadata and fetch the ramdisk/kernel13:02
sorenYou can specify them manually, but usually it's taken from the metadata of the fs image.13:02
*** romcheg has quit IRC13:03
lucasagomesright...13:03
sorenRebuild would destroy the local state, right?13:04
lucasagomesyeah it would since it reimage the node13:05
lucasagomesnot ideal :/13:05
sorenNot useful, no.13:05
lucasagomesgotta think how it would work, you would upload a new kernel/ramdisk to glance and notify Ironic?13:05
sorenNova would be involved somehow, too.13:06
sorenNova keeps track of which kernel/ramdisk a given instance is running.13:06
lucasagomesright, I gotta take a better look into how nova manages it13:07
lucasagomesI wasn't aware of it13:08
lucasagomesI thought that all the references lived in glance13:08
*** Marga_ has quit IRC13:09
*** Marga_ has joined #openstack-ironic13:09
sorenWow, so I really have to do all of this manually?13:09
* soren is baffled he's the first one to want to upgrade kernels on nodes managed by Ironic13:10
sambetts_lucasagomes: do you think that JayF might have some ideas on this?13:11
lucasagomessambetts_, he might yeah13:12
lucasagomessambetts_, tho IPA uses full disk images, so I bet that the kernel and ramdisk is a simple package update for that case13:13
lucasagomessoren, ^ yeah :/13:13
sorenYeah, that's an entirely different story.13:13
*** dlpartain has joined #openstack-ironic13:13
*** ryanpetrello has joined #openstack-ironic13:15
lucasagomessoren, one thing I can say tho by looking at the Ironic code is that we always grab the kernel & ramdisk from the image metadata13:16
lucasagomesindependent from what is on Nova's db13:16
lucasagomeshttps://github.com/openstack/ironic/blob/master/ironic/drivers/modules/pxe.py#L232-L24013:17
soren*headdesk*13:17
* lucasagomes brb a sec, lunch13:17
lucasagomessoren, yeah :/13:17
lucasagomessoren, sorry for that... many of that logic came from nova bm too so I suspect even nova bm13:18
sorenUh, no?13:18
soreni_info is the instance info.13:18
lucasagomesmight not be looking at the nova db either13:18
lucasagomesyup instance info13:18
sorenIf it *doesn't* have kernel and ramdisk already set, it grabs it from glance.13:18
sorenSo instance data takes precedence. As it should.13:18
lucasagomesyeah13:19
lucasagomesbut nova doesn't populate that kernel ramdisk in instance_info afaict13:19
lucasagomeshttps://github.com/openstack/nova/blob/master/nova/virt/ironic/patcher.py13:19
lucasagomesit does for the deploy_ramdisk and deploy_kernel13:19
lucasagomesso, should be a easy fix in nova to look at the db and populate it correctly when the node is being deployed13:20
* lucasagomes brb13:21
*** lucasagomes is now known as lucas-hungry13:21
*** bearhands is now known as comstud13:22
*** pensu has joined #openstack-ironic13:26
*** achanda has joined #openstack-ironic13:26
*** anderbubble has joined #openstack-ironic13:27
*** anderbubble has quit IRC13:30
*** anderbubble has joined #openstack-ironic13:30
*** romcheg has joined #openstack-ironic13:31
*** achanda has quit IRC13:31
*** romcheg has quit IRC13:33
*** romcheg has joined #openstack-ironic13:34
*** dlpartain has quit IRC13:37
naohirotrameshg87: I really really missed precious opportunity to talk to you.13:39
*** romcheg1 has joined #openstack-ironic13:39
naohirotI just left to have dinner.13:39
*** jjohnson2 has joined #openstack-ironic13:41
naohirotI join to this channel everyday from today on.13:41
*** romcheg2 has joined #openstack-ironic13:42
*** jjohnson2 has quit IRC13:42
*** romcheg has quit IRC13:43
*** jjohnson2 has joined #openstack-ironic13:43
*** igordcard has quit IRC13:43
*** romcheg1 has quit IRC13:43
naohirotI can stay in this channel UTC 00:00-UTC14:00.13:44
*** igordcard has joined #openstack-ironic13:44
*** romcheg has joined #openstack-ironic13:47
*** romcheg2 has quit IRC13:47
naohirotrameshg87: I'm not familiar with IRC. Is there any way to show my status such Microsoft Lync?13:51
naohirots/such/such as/13:52
*** lucas-hungry is now known as lucasagomes13:53
lucasagomesnaohirot, you can set ur away status13:53
lucasagomeslike: /away <msg>13:54
*** pensu has quit IRC13:54
lucasagomesand /away with no message means ur no longer away :)13:54
naohirotHi lucasagomes, again :-)13:54
naohirotOkay.13:54
lucasagomesor just change the nickname, people usually do like <nick>|<status>... like naohirot|sleeping13:55
lucasagomes:D13:55
naohirotAha13:55
naohirotthat's the reason some people change his/her name.13:55
naohirotlucasagomes: are you in Europe?13:56
lucasagomesnaohirot, yup13:56
naohirotI see, PRIMERGY is productized in Germany.13:57
naohirotCan I ask basic question again?13:57
naohirotFrom user's point of view,13:58
lucasagomessure13:58
* lucasagomes googles primergy13:58
Shrewslucasagomes: you want to address dtantsur's comments in https://review.openstack.org/129261 before I +A, or after?13:58
lucasagomesoh fujitsu :)13:58
Shrewslucasagomes: or at all?  :)13:58
lucasagomesShrews, morning Shrews13:58
Shrewsmorning13:59
naohirotGM, shrews13:59
Shrewshi naohirot13:59
lucasagomesShrews, oh I can submit a new one if you think it worth fixing on that patch13:59
naohirotIs "nova boot" the only I/F user can see?13:59
Shrewslucasagomes: not necessary, i think. i'll +A and leave it up to you14:00
lucasagomesShrews, ack! ta much!14:00
lucasagomesnaohirot, the client has a ironic node-set-provision-state that can be used to start a deployment14:01
lucasagomestho, we still want to make it simpler for the users to use Ironic without going through nova14:01
naohirotlucasagomes: I meant user as "end user", not "administrator".14:02
lucasagomesright now we have things used in the deployment like instance_uuid, which is nova-related only14:02
lucasagomesnaohirot, oh gotcha14:02
lucasagomesyeah so nova is the only way14:02
*** jistr|english is now known as jistr14:02
naohirotIsn't it "ironic" for admin, right?14:02
lucasagomesits admin only nowadays14:02
lucasagomessome people wants to add policies but we haven't got any patches as far as I can tell14:03
naohirotlucasagomes: okay, in kilo cycle, is horizon team going to implement Web GUI for Ironic?14:03
lucasagomesJoshNang, was working on that since Juno14:03
lucasagomesbut ofc in Juno it couldn't be merged cause Ironic wasn't even graduated14:04
*** rushiagr is now known as rushiagr_away14:04
lucasagomesbut yeah, there are people working on that right now14:04
naohirotI see.14:04
naohirotAnd let me make suer if I understood the difference between pxe_ and agent_.14:05
naohirotIn case of agent_, only the first boot is PXE, but the second boot and later are iSCSI.14:06
naohirotIn case of pxe_, every time pxe boot, even though physical OS has been installed, because no ipl.14:07
lucasagomesnop14:07
naohirotreally?14:07
lucasagomesagent_ deploys a full disk image, so first boot is PXE to actually boot the deploy ramdisk14:07
lucasagomesthe rest is local boot14:07
lucasagomesin the pxe_ case, yes we pxe boot everytime14:08
lucasagomesthe ISCSI is used by the pxe_ to be able to copy the image onto the disk14:08
lucasagomesso the pxe_ deploy ramdisk boots in the node, it exposes the disk via iscsi and pass it to the ironic conductor, the conductor them partition the iscsi disk and copy the partition image onto it14:09
naohirotOkay, now I think I fully understood the difference.14:09
*** victor_lowther__ has quit IRC14:09
*** victor_lowther__ has joined #openstack-ironic14:09
lucasagomesapart from documenting better and exposing those capabilities/differences via our API14:09
*** victor_lowther__ has quit IRC14:09
lucasagomeswe also want to have only 1 deploy ramdisk14:10
lucasagomesinstead one for pxe_ and one of agent_14:10
*** victor_lowther has joined #openstack-ironic14:10
lucasagomeswe may in a soon future merge everything into the agent ramdisk14:10
naohirotSo I think that HBA and SAN storage works or not depends on the ramdisk.14:10
lucasagomesyeah14:10
lucasagomesthe agent_ ramdisk actually has a service running on it14:10
lucasagomesso it's much more flexible and extensible14:10
naohirotIn oder to create the ramdisk,14:11
naohirotthe ways for agent_ and pxe_ are different, right? I believe.14:12
naohirotsorry14:12
lucasagomesyeah, and thats what need to be fixed before we merge both of them14:13
lucasagomesagent_ works with coreos where pxe_ with disk-image-builder14:13
lucasagomesthere's a disk-image-builder patch upstream that NobodyCam is working on14:13
lucasagomesto be able to build the agent_ ramdisk14:13
victor_lowtherhm... is there a spec out yet for the state machine changes we hashed out at the summit?14:13
lucasagomesand the agent_ ramdisk has some problems being tested on gate, memory constraint, we have to work with infra14:14
lucasagomesto solve that too (should be easy)14:14
lucasagomesvictor_lowther, haven't seem one yet... but +1 to iron that out asap14:14
lucasagomesvictor_lowther, mind putting one up?14:15
victor_lowtherMaybe after I find the "how to write a spec" document. :)14:15
*** datajerk has joined #openstack-ironic14:16
*** rloo has joined #openstack-ironic14:17
lucasagomesvictor_lowther, https://wiki.openstack.org/wiki/Ironic/Specs_Process :)14:17
naohirotlucasagomes: disk-image-builder creates ramdisk for pxe_, and IPA contains ramdisk for agent_. Am I right?14:17
lucasagomesI think that for the state machine we already agreed with the changes14:17
lucasagomesso we can fullfil a full spec14:18
* Shrews interested in reading this spec14:18
lucasagomesnaohirot, IPA is the python service that runs in the agent ramdisk14:18
lucasagomesthey use coreos tools to build their image14:18
naohirotdoes coreos tool have name?14:19
lucasagomeshttps://github.com/openstack/ironic-python-agent/tree/master/imagebuild/coreos14:19
naohirotAha, now I'm getting better understanding :-)14:22
*** rakesh_hs has quit IRC14:23
naohirotlucasagomes: thaks a lot14:23
naohirotthanks a lot.14:23
lucasagomesnaohirot, no problem at all :)14:24
naohirotSo I had a really good progress today by having conversation with you rather than just reading several materials14:26
naohirotNow time to go to bed in Japan.14:27
naohirotsee you tomorrow!14:27
*** naohirot has quit IRC14:28
lucasagomesvictor_lowther, http://paste.openstack.org/show/131911/ in case u need a ASCII art of the state machine14:35
lucasagomesignoring error states ofc14:35
victor_lowtherlucasagomes: https://blueprints.launchpad.net/ironic/+spec/new-ironic-state-machine14:35
*** romcheg has quit IRC14:35
lucasagomesw00t!14:36
*** andreykurilin has quit IRC14:36
* dtantsur is looking forward to this spec too14:36
victor_lowtherNow to write lots of probably-markdown-incompatible ascii art and confuse everyone who was not at the summit. :)14:36
lucasagomeslol14:37
victor_lowtherI am following the process @ https://wiki.openstack.org/wiki/Blueprints, that more or less correct?14:38
lucasagomesyeah that's fine afaik, it's basically14:39
victor_lowthernm, I should read the backscroll.14:39
lucasagomescreates a bp in launchpad, and then fill out the spec template14:39
* victor_lowther hunts down a rst major mode for emacs14:41
lucasagomesvictor_lowther, also for the spec, I think that everyone that was in the summit can contribute writing it14:41
victor_lowtherya14:41
*** romcheg has joined #openstack-ironic14:41
lucasagomesjust need the initial kick :)14:41
victor_lowtherThat is the idea.14:42
lucasagomesnice :)14:42
lucasagomesI don't have anything fancy to write rst, but I do use a online viewer sometimes to test things out14:42
lucasagomeshttp://rst.ninjs.org/14:42
*** romcheg1 has joined #openstack-ironic14:43
lucasagomesyou can also check the syntax, with doc814:43
lucasagomeshttps://launchpad.net/doc814:43
*** romcheg has quit IRC14:46
*** rushiagr_away is now known as rushiagr14:51
*** rushiagr is now known as rushiagr_away14:52
*** jjohnson2 has quit IRC14:53
*** jjohnson2_ has joined #openstack-ironic14:53
*** openstackgerrit has quit IRC14:55
*** rushiagr_away is now known as rushiagr15:05
*** pensu has joined #openstack-ironic15:07
*** romcheg1 has quit IRC15:10
lucasagomesdtantsur, the only thing about the validate on the driver_vendor_passthru is that validate expects a task parameter15:12
dtantsurhmmm hmmm15:12
lucasagomesI don't have it on driver_vendor_passthru, I probabaly have to change th validate to accept a task or context15:12
dtantsurwell yeah, as you don't have a node...15:12
lucasagomesthat's why (assuming here) validate wasn't called for driver_vendor_passthru begore15:12
lucasagomesbefore*15:12
lucasagomesyeah15:12
dtantsurI don't know. let's talk after the call15:13
lucasagomesok15:13
*** foexle has quit IRC15:13
*** marcoemorais has joined #openstack-ironic15:19
*** marcoemorais1 has joined #openstack-ironic15:23
*** marcoemorais has quit IRC15:26
*** k4n0 has quit IRC15:27
ShrewsJayF: JoshNang: Just watched the recording of your decom talk. Great stuff.15:28
pensuHi everyone, any idea where does devstack ironic store images? Need to delete some of those to free space on my VM!15:30
*** foexle has joined #openstack-ironic15:32
Shrewspensu: /opt/stack/data/ironic maybe?15:35
lucasagomespensu, /opt/stack/devstack/files/15:36
lucasagomesthere's a images dir there15:37
dtantsur /opt/stack/data/ironic IIRC15:37
pensuokay, got it.....it's /opt/stack/devstack/files.....thanks lucasagomes!15:39
pensudtantsur: Shrews: I don't have an /opt/stack/data/ironic folder....15:39
dtantsurthey must've changed something then...15:40
lucasagomesonce you do a ./unstack.sh the /opt/stack/data/ironic goes away15:41
*** pcrews has joined #openstack-ironic15:46
*** ryanpetrello has quit IRC15:48
*** achanda has joined #openstack-ironic15:59
*** ChuckC has quit IRC16:00
*** achanda has quit IRC16:07
*** ndipanov is now known as ndipanov_gone16:20
lucasagomesdtantsur, alright so validate()16:29
dtantsuryeah16:29
dtantsurcan we have something like driver_validate()? Or it doesn't make any sense?16:29
* victor_lowther forsees lots of comment wars in the new state machine spec.16:30
lucasagomesdtantsur, I don't know what would be best, 1- leave it as a known problem (TODO in the code), 2- modify the validate() to accept a task or context as the first parameter, 3- have a diff validate() endipoint for drivers16:30
dtantsurvictor_lowther, oh be sure ;)16:30
lucasagomesdtantsur, yeah that would be 3-16:30
JayFsambetts_: lucasagomes: We use static DHCP (dhcp_provider None) with static agent images being served up, so I don't think I have much insight for you there :(16:30
JayFShrews: ty16:30
*** Marga_ has quit IRC16:31
lucasagomesJayF, I'm a bit out of context...16:31
dtantsurlucasagomes, I'm inclined to go with 1- and unblock this work16:31
victor_lowtherActually writing it down is exposing lots of ambiguity.16:31
JayFlucasagomes: this is in response to something well, well overnight :)16:31
*** Marga_ has joined #openstack-ironic16:31
dtantsurvictor_lowther, as it usually happens :)16:31
JayFlucasagomes: just catching up on scrollback :)16:31
victor_lowtherIndeed.16:31
JayFlucasagomes: probably well past hte issue now16:31
lucasagomesJayF, ohh I remember now yeah it's about the full disk images16:31
lucasagomesgotcha16:31
lucasagomesdtantsur, right... yeah it didn't call validate() before too, so I will add a TODO16:32
dtantsurlucasagomes, so if you just leave a NOTE there, I'm ok with +2ing it16:32
lucasagomesI mean FIXME actually I can open a bug about it too16:32
dtantsurack16:32
lucasagomesdtantsur, ack... yeah, even because that can be fixed in parallel16:32
* lucasagomes doing it now16:32
*** marcoemorais1 has quit IRC16:34
lucasagomesJayF, q about IPA... I think I know the answer but just confirming16:34
*** ChuckC has joined #openstack-ironic16:34
lucasagomesJayF, you guys don't install a bootloader right? The image already contains one16:34
lucasagomesis that correct?16:34
JayFYes16:34
lucasagomesok, is it grub or syslinux or ... ?16:34
JayFright now we just write a converted-to-raw image to the disk, and the image already has partitions/bootloaders/etc16:34
JayFdepends on the image :)16:35
*** ChuckC has quit IRC16:35
JayFour CoreOS image uses syslinux, other images use grub16:35
JayFit's all up to the distribution16:35
*** ChuckC has joined #openstack-ironic16:35
lucasagomesright, just wondering because in case we want to add local boot support for the iSCSI methodology16:35
lucasagomeswe may want to pick a bootloader16:35
*** Marga_ has quit IRC16:35
JayFIn fact we rely on the image to have a reasonable partition table as well, and allow it to provide a configdrive partition for us to image into16:35
JayFif properly labelled16:35
lucasagomesand I know grub has some problems on being installed outside the machine that it's going to run16:36
lucasagomesso I think syslinux maybe the right choice16:36
JayFI mean, I don't think that holds true so much anymore16:36
JayFJust like with anything if you build an full disk image in one place (ours are built inside a VM iirc) you have to know things about your target to make it work16:37
JayFbecause things like the fstab, etc has to align16:37
JayFeven beyond the bootloader16:37
lucasagomesindeed16:37
dtantsurgoing a bit earlier today, see you tomorrow16:39
*** dtantsur is now known as dtantsur|afk16:39
lucasagomesdtantsur|afk, see ya thanks16:40
*** ChuckC has quit IRC16:50
lucasagomesJayF, another quick q... for the gate problem with IPA16:52
lucasagomesare u guys looking into it? anything I can help with?16:52
JayFWe've been playing whackamole with the various failures16:52
JayFlast time it was an iptables rule blocking agent->swift16:53
*** Viswanath has joined #openstack-ironic16:53
JayFthat was fixed just before the summit and none of us have looked since16:53
JayFafaik16:53
lucasagomesgotcha16:53
lucasagomesthe memory thing has been sorted?16:53
JayFYeah, basically IPA tests are forced to run with 1G in serial16:53
JayFuntil we can get IPA working in less memory (which requires DIB image and possibly image streaming support)16:54
lucasagomesgotcha16:54
*** jistr has quit IRC16:55
JayFOptimizing for low ram / slow connectivity was something far from our minds when designing this against hardware (back when it was teeth-agent before we integrated with Ironic) that had 32GB+ ram :)16:55
JayFheh16:55
Shrewsall the things should be able to run in 256K16:56
lucasagomesheh yeah I don't think that it's a problem for the real world scenario indeed16:56
*** Viswanath has quit IRC16:56
JayFShrews: I learned how to sysadmin about a decade ago fitting a whole lamp stack in one of those 32MB VPS boxes :)16:57
JayFShrews: and here I thought my days of limited ram were behind me... :P16:57
lucasagomes:D16:58
ShrewsJayF: welcome to the cloud of the 90's!  :)16:59
*** ChuckC has joined #openstack-ironic16:59
*** leopoldj has quit IRC17:03
lucasagomes+1 /me hates the term cloud17:04
*** marcoemorais has joined #openstack-ironic17:13
*** dlaube has joined #openstack-ironic17:20
*** athomas has quit IRC17:20
*** andreykurilin has joined #openstack-ironic17:22
*** rameshg87 has joined #openstack-ironic17:24
*** Marga_ has joined #openstack-ironic17:25
* sambetts_ agrees with lucasagomes 17:31
*** ifarkas has quit IRC17:33
*** penick has joined #openstack-ironic17:34
*** ifarkas has joined #openstack-ironic17:39
*** Marga_ has quit IRC17:42
yjiang5lucasagomes: I noticed your statement "in-band will be a separated service". Do you have any etherpad for the discussion?17:44
*** derekh has quit IRC17:44
*** openstackgerrit has joined #openstack-ironic17:49
*** pelix has quit IRC17:53
*** foexle has quit IRC17:56
openstackgerritA change was merged to openstack/ironic: Fix documentation on Standard driver interfaces  https://review.openstack.org/13374417:58
*** anderbubble has joined #openstack-ironic17:59
JoshNangShrews: thanks :D17:59
*** ChuckC has quit IRC18:00
openstackgerritRuby Loo proposed a change to openstack/ironic-specs: Updates to 'maintenance reason' spec  https://review.openstack.org/13377618:03
rloohi ironickers18:03
Shrewshi rloo. welcome back18:04
rloolucasagomes, jroll: I updated the maintenance reason spec ^^ 133776 to have an APIImpact flag in the commit, so I had to change something ;) You might want to check that I got it right.18:04
rloohi Shrews, we missed you!18:05
lucasagomesrloo, morning will check18:05
lucasagomesrloo, btw I also have to talk to u about the vendor spec18:05
rloolucasagomes: ok. am still catching up on stuff. is there something you want me to look at first, wrt vendor spec?18:05
lucasagomesrloo, remember we talked about doing a GET on the vendor_passthru root endpoint to get the avaialble methods?18:05
lucasagomesrloo, well not really, just telling you18:06
rloolucasagomes: yes wrt the GET18:06
lucasagomesrloo, yup, so that doesn't work18:06
rloohmm, too bad.18:06
lucasagomescause the methods for the vendor passthru is an argument18:06
lucasagomeslike {'method': blah} .../vendor_passthru OR ../vendor_passthru/blah18:06
rloolucasagomes: but aren't the methods mapped in the dict?18:06
lucasagomesso we already use GET for the root18:06
lucasagomesyou can do both18:07
rloooh.18:07
lucasagomesit's just a syntax thing, in my patch I will have to add a new endpoint18:07
lucasagomeslike .../vendor_passthru/methods or so18:07
rloothat's fine, adding a new endpoint.18:07
lucasagomescool, yeah just to say because it will differ from the spec a bit :/18:07
rlooI think we might want to update specs after they are approved, if we find that they need updating. I think it was mentioned (maybe in nova?) that they do this.18:08
rlooor maybe it was a question as to whether they should be updated after they are approved. I don't recall, but I'm changing it in my reality to yes, we should. ha ha. what do people think?18:08
lucasagomes+2 ur patch, looks good more clear18:09
lucasagomesI think it's OK to update the specs after approved18:09
lucasagomesI don't want someone to know everything when writing the spec18:10
lucasagomesmany things we forget and ended up remembering/learning as we code18:10
lucasagomesso I think it's complete fine to update a merged spec18:10
rloolucasagomes: great, glad you agree too.18:10
openstackgerritLucas Alvares Gomes proposed a change to openstack/python-ironicclient: Sane parameters for node and driver vendor_passthru()  https://review.openstack.org/13378018:13
rloolucasagomes: so, ahh, would you mind updating the 'Extend Vendor Passthru' to mention the new endpoint? It needs some patch that has an APIImpact flag and I was going to find something to patch, but since you're going to change it. Or have you decided what to use, 'methods'? I can update it for you.18:13
lucasagomesrloo, +1 I will probably do it tomorrow cause it's a bit late here18:13
lucasagomesbut yeah I will update it18:14
lucasagomesyeah on my patch I added a "methods" endpoint18:14
lucasagomescouldn't think of a better name18:14
rloolucasagomes: no worries. I'm not in a hurry, just want to make sure any approved specs that should have had APIImpact, has it ;). thx.18:14
lucasagomesGET vendor_passthru/methods18:14
rloolucasagomes: I think 'methods' is fine, since that's what we're calling them, right?18:14
lucasagomeswould return all the methods supported by the driver/node18:14
*** athomas has joined #openstack-ironic18:14
lucasagomesyeah18:14
lucasagomesrloo, aight! adding to the TODO list for tomorrow then18:15
rloothx lucasagomes18:15
*** achanda has joined #openstack-ironic18:17
*** mjturek has left #openstack-ironic18:17
rameshg87JayF, hi18:18
lucasagomesalright I will call it a day18:18
lucasagomeshave a good night everyone!18:18
rameshg87goodnight lucasagomes :)18:18
sambetts_same here, good night ironic18:19
lucasagomessambetts_, night18:19
lucasagomesrameshg87, thanks you too :)18:19
sambetts_lucasagomes: night!18:19
*** lucasagomes is now known as lucas-zZz18:19
*** sambetts_ has quit IRC18:19
*** spandhe has joined #openstack-ironic18:20
JayFrameshg87: hey18:21
rameshg87JayF, hello18:21
rameshg87JayF, ifarkas and myself were looking for you18:22
rameshg87JayF, we were thinking of coming up with a common approach of doing raid configuration for dell and hp servers18:22
*** anderbubble has quit IRC18:22
JayFrameshg87: for the out of band stuff I don't have much experience or really a dog in the fight at all :)18:23
rameshg87JayF, are you planning to expand this spec: https://review.openstack.org/#/c/131272/1/specs/kilo/hardware-capabilities.rst ?18:23
rameshg87JayF, yeah that's fine, hp is targetting inband :)18:23
JayFrameshg87: I'd love for someone to take over that spec and reflect all the work done in the design summit session18:23
rameshg87JayF, i could give a try then18:24
JayFplease do18:24
rameshg87JayF, i might need to work with dtantsur|afk so that we come up with a common approach of putting together driver capabilities and hardware capabilities18:24
JayFI think that's the right path18:24
rameshg87JayF, i don't see a reason why those two should be separate18:24
rameshg87JayF, for hp, we are giving a try putting the hp raid configuration tool from the ipa image18:25
JayFThere's a different angle of capabilities that you probably aren't thinking about18:25
JayFi.e. as a user I have no way of knowing that pxe driver doesn't do whole disk images and ipa does18:25
rameshg87JayF, what's that ?18:25
JayFI think driver capabilities is more targetting documenting those differences18:25
JayFthan driving configuration like the node/hw capabilities stuff is18:25
rameshg87JayF, but we decided disk vs partition images thing will be fixed18:26
rameshg87JayF, is there any other use-case for driver capability ?18:26
JayF"will be" is how long from now?18:27
*** Marga_ has joined #openstack-ironic18:27
JayFand are you sure all deploy drivers will always support the same set of things?18:27
JayFI'm not convinced that's a technical possibility18:27
rameshg87JayF, then it's merely not just documentation. driver capability is an actual functionality which can affect scheduling18:28
JayFthat's true; but it should also be separately discoverable via the api18:28
rameshg87JayF, and published to the nova scheduler18:28
rameshg87JayF, or rather all set(hardware capabilities, driver capabilities) can be just termed as "capabilities" for the node18:29
JayFYes, but the driver caps need to be separately discoverable imo18:29
rameshg87JayF, why is that ? for bettering user understanding ?18:29
JayFYes18:30
rameshg87JayF, okay18:30
rameshg87JayF, just one more question18:30
JayFuser/operators have *no way whatsoever* to divine that knowledge today18:30
JayFunless they go diving into python18:30
*** lucas-zZz has quit IRC18:30
rameshg87JayF, during the summit i heard something like certain things cant be done in ipa because ipa runs in docker container18:31
*** Marga_ has quit IRC18:31
rameshg87JayF, things dealing with devices, is that true ?18:31
*** jlk has quit IRC18:31
JayFThat's very not true18:32
JayFwe run IPA inside a systemd-nspawn container with the --share-system flag18:32
JayFso it acts more like a chroot than a container18:32
JayFand IPA has full hardware access18:32
*** krtaylor has quit IRC18:32
rameshg87JayF, okay and all device files in /dev18:33
*** foexle has joined #openstack-ironic18:33
JayFyeah18:33
JayFeverything should work exactly the same as you'd expect18:33
JayFany differences would be because CoreOS runs a newer kernel or are a bug against the image18:33
rameshg87JayF, okay :).. that's all .. let me try to polish the hardware capabilities spec ..18:34
*** anderbubble has joined #openstack-ironic18:37
*** rameshg87 has quit IRC18:41
*** ChuckC has joined #openstack-ironic18:42
*** rushiagr is now known as rushiagr_away18:43
yjiang5Can anyone have a look on https://review.openstack.org/#/c/132936/ ?It's waiting some input from ironic guys.18:44
*** ChuckC has quit IRC18:47
spandheHi everyone.. observed something with Icehouse version of Ironic and wanted to confirm if thats expected behavior18:52
spandheI have setup a tftp server, and it serves from a particular directory18:52
spandheso all the paths that the target uses, e.g. pxelinux.0 or pxelinux.cfg/ etc, are related to that path18:53
spandherelative to*18:53
spandhebut when Ironic creates the pxe config file, it puts absolute paths for kernel and ramdisk images18:54
spandheso pxe fails to find those files..18:54
spandheis this expected?18:55
spandheI mean, Its not expected to fail, but are the paths in the pxe config file supposed to be absolute?18:55
spandheI am serving those images through tftp also..18:55
*** igordcard has quit IRC18:55
*** krtaylor has joined #openstack-ironic18:56
*** marcoemorais has quit IRC18:58
*** marcoemorais has joined #openstack-ironic18:58
*** marcoemorais has quit IRC18:59
*** marcoemorais has joined #openstack-ironic18:59
*** achanda has quit IRC19:00
yjiang5JayF: Hi, thanks for reviewing https://review.openstack.org/#/c/132936/3/lib/ironic . You mean I should not adding the agent_ipmitool to the IRONIC_ENABLED_DRIVERS (as in https://review.openstack.org/#/c/132936/3/lib/ironic L58 ), or the whole patch?19:02
JoshNangyjiang5: JayF i think we should add it. It's an in-tree driver, we should do what we can to make it a first class, fully tested citizen in Kilo19:06
JayFI honestly want devananda to weigh in19:07
JayFbecause I was under the impression only the default drivers were enabled by default in devstack19:07
JayFi.e. a breaking change to agent driver shouldn't break nova's (or anyone elses' gate, except Ironic) gate19:08
spandherloo: hey.. do u know if thats a bug?19:10
yjiang5JayF: so you mean we should not add this patch to devstack, right?19:12
rloospandhe: hi, sorry, you mean your question about tftp dir? (wasn't paying attention)19:12
spandherloo: yes.. about tftp directory19:12
JayFyjiang5: I'm saying I don't think the default devstack configuration should contain non-default Ironic drivers.19:12
*** pensu has quit IRC19:13
yjiang5JayF: but we have agent_ssh driver in it alrleady.19:13
rloospandhe: not sure. I'm not familiar with that code. but based on your description, it is a bug cuz it doesn't work for you?19:13
devanandaJayF: you rang?19:13
rloospandhe: did you try looking at the reported bugs and/or what was fixed/addressed in juno?19:14
JayFdevananda: There's a review up for devstack that yjiang5 made that would enable agent_ipmitool in default ironic devstack config19:14
JayFdevananda: iirc at the mid-cycle in Oregon we said that shouldn't happen unless/until it was default driver?19:14
devanandaJayF: i also recall that being the thing we said19:15
devanandadefaults in devstack != recommendations for production19:15
JayFdevananda: wanted to make sure I wasn't misremembering :) this is the merge req in question --> https://review.openstack.org/#/c/132936/19:15
*** Marga_ has joined #openstack-ironic19:15
devanandaour config option should resemble something production-sane19:16
devanandadevstack's defaults should resemble something useful in a devstack environment ...19:16
devanandathat's jus tmy 2c, though19:16
spandherloo: it doesnt work for me, yes.. but now I am wondering if it assumes that some http service is supposed to serve the file instead of tftp.. or whether I am doing something wrong thats causing absolute paths to show up there19:16
yjiang5JayF: devananda, sorry guys, what do you mean the default driver?19:16
spandheif more people have observed this issue, its probably a bug..19:16
JayFyjiang5: default deploy driver for ironic right now is "pxe" not "agent"19:16
rloospandhe: it would be easier if you were using juno19:17
rloospandhe: 'easier' == a lot was changed19:17
devanandaJayF: devstack currently enables agent_ssh, pxe_ssh, and pxe_ipmitool19:17
spandherloo:  :) hopefully soon :)19:17
devanandathis is closing a gap in that coverage matrix19:17
yjiang5JayF:  devananda So you mean agent_ssh in not default driver although it's supported in devstack, right? I'm a bit lost.19:17
openstackgerritNisha Agarwal proposed a change to openstack/ironic-specs: Discover node properties using new CLI node-discover-properties  https://review.openstack.org/10095119:17
JayFdevananda: ooooooh. So the big difference here is enabling ipmitool19:18
devanandaright19:18
devanandaipmitool + agent is missing from the *default* list of enabled drivers in devstack19:18
*** achanda has joined #openstack-ironic19:18
devanandait's totally possible to enable it by overriding IRONIC_ENABLED_DRIVERS in your localrc, of course19:18
devanandaif we're not exercisign it in the gate, https://review.openstack.org/#/c/132936/3/lib/ironic L58 isn't helpful19:19
devanandahowever ... the other changes iin that file should land regardless19:19
Shrewsagent_ssh is for the IPA tests, iirc. i see no need to add the ipmitool one "just because"19:19
devanandathere's a bug right now in devstack's handling, it seems. using agent_[!ssh] is not possible without modifying this file19:19
devanandalook at the change on line 49719:20
devanandathat definitely should land19:20
devanandaditto L 29419:20
yjiang5devananda: Sure, I will remove that line. that's my question to JayF :)19:20
JayFif you drop your addition of agent_ipmitool to the IRONIC_ENABLED_DRIVERS I'll take my -1 off :)19:21
devanandathough.... [[ ]] shouldn't be used. we can do better pattern matching than =~ agent_[a-z] with no quotes19:21
JayFassuming that's the general consensus of the channel as well19:21
rloospandhe: I looked quickly at git log and I see a few changes related to tftp. It is possible that there was a bug in icehouse that is now fixed. w/o looking through the code though, I don't know definitively.19:21
yjiang5Shrews: I'm not sure. In fact, I'm using devstack for my mini-cloud and that's the reason I added the pxe_ipmitool (https://review.openstack.org/#/c/127658/6 )  and agent_ipmitool (this patch) :)19:21
* devananda adds comments19:21
*** marcoemorais has quit IRC19:21
spandherloo: thanks.. Ill check Juno code..19:21
*** marcoemorais has joined #openstack-ironic19:22
Shrewsyjiang5: like devananda said, those can be enabled in local.conf19:22
devanandaalso, I'll be around on weird schedules for this week19:22
yjiang5devananda: sorry, what do you mean of "we can do better pattern matching than =~ agent_[a-z] with no quotes".19:22
* Shrews wonders why pxe_ipmitool is enabled by default19:23
yjiang5Shrews: yes, I hesitated to that changes also when submitting the patch, because agent_ssh is not there, just didn't remove it. :)19:23
Shrewsi wonder if d-g overrides this value...19:23
* Shrews looks19:23
devanandaShrews: I wonder that too...19:23
yjiang5Shrews: possibly because pxe_ipmitool is in the default driver already.19:23
Shrewsdevananda: https://github.com/openstack-infra/devstack-gate/blob/master/devstack-vm-gate.sh#L139-L16219:25
Shrewsonly for the agent tests19:26
devanandaShrews: yup. so there's no need for it to be in the defaults right now. but also no need to remove it19:27
devanandai mean, we could clean that up a bit19:27
Shrewsdevananda: right19:27
Shrewsbut definitely no need to add something else  :)19:28
yjiang5devananda: for "better pattern matching than =~ agent_[a-z] ", do you have any suggestion of better method? Sorry not well on bash .19:30
devanandayjiang5: if [ -z "${IRONIC_DEPLOY_DRIVER%%agent*}" ]; then19:34
devanandatests if the variable begins with the word "agent"19:34
yjiang5devananda: thanks, I will try that way.19:34
yjiang5devananda:  I will update the previous patch also, which add pxe_ipmitool support.19:35
sorendevananda: Uh, no. That checks if it contains the word "agent".19:36
devanandasoren: -z makes it check if it starts with it19:36
sorenfoo=baragentbaz; echo ${foo%%agent*} gives "bar".19:36
devanandasoren: correct. with -z, checks for the string to be empty19:37
sorendevananda: Yes...19:37
sorenAnd it's not.19:37
sorenUh...19:37
sorenSheesh.19:37
sorenI'm an idiot.19:37
devanandaI am too19:37
devanandabut this time, I tested it :)19:37
sorenYou're right. It checks if the string begins with "agent" or is the empty string.19:38
*** igordcard has joined #openstack-ironic19:38
soren...but the latter case is probably irrelevant.19:38
sorenI always get confused by negations. I'm clearly not in the line of business.19:38
yjiang5soren, thanks for double check and confirmation.19:39
sorenIn the /right/ line of business.19:39
devanandayjiang5: comments posted. other than the nits, the patch LGTM19:39
soren(See? I can't even type properly)19:39
yjiang5devananda: thanks.19:39
* devananda wonders how late his plane is going to be19:39
devanandaoh hey, anyone using reveal.js notes-server functionality?19:40
sorenNow that there are more folks here... Does anyone have a secret trick for upgrading kernels on nodes managed by Ironic? (pxe/ipmi driver)19:40
*** anderbubble has quit IRC19:41
yjiang5soren: switch to IPA, that's what I'm doing now :)19:42
devanandaoh great. my flight to dallas is delayed enough that i'm likely to miss my connection now. /me goes afk to find an agent to fix this19:42
*** anderbubble has joined #openstack-ironic19:42
devanandasoren: change the kernel/ramdisk ref in node.properties and reboot?19:42
devanandaah. no. that SHOULD work but doesn't19:42
sorendevananda: "node.properties" ?19:42
sorenMind you, my Ironic install is a bit long in the tooth.19:43
sorenLike, ice house release or something.19:43
yjiang5soren: oooook :)19:43
devanandasoren: right. the same thing should (not work) there because i dont think that code has changed much19:43
yjiang5soren: You can simiply replace the the file in the local cache?19:43
devanandabut I don't think the pxe_ipmitool driver will rebuild the PXE env, even if you change the right property19:44
devanandasoren: I'd call that a bug -- mind filing one? you *should* be able to update the instance's kernel & ramdisk and trigger a reboot19:44
sorendevananda: Yeah, as far as I can tell, the .prepare method only gets called in response to a new deploy.19:44
devanandathat is possible today with a "rebuild"19:44
devanandabut that'll erase any data on the instance (unless you had an ephemeral volume and did "rebuild --preserve-ephemeral" ... don't ask ...)19:44
sorendevananda: Yeah, I had that chat with Spamaps last week. :)19:45
devanandasoren: or a rebuild, or a hash repartitioning event (in Juno)19:45
devanandaanyhow, i need to sort out this flight prob lem19:45
devanandabbiab (or not)19:45
sorendevananda: Enjoy19:45
yjiang5Does anyone know if the key_name parameter is working for ironic? A quick checking of the code seems no.19:45
*** igordcard has quit IRC19:52
*** penick has quit IRC19:52
*** shakamun_ has quit IRC19:52
*** marcoemorais has quit IRC19:53
*** marcoemorais has joined #openstack-ironic19:53
*** shakamunyi has joined #openstack-ironic19:57
*** Marga_ has quit IRC20:06
*** foexle has quit IRC20:06
*** anderbubble has quit IRC20:09
*** killer_prince has joined #openstack-ironic20:09
*** killer_prince is now known as lazy_prince20:09
*** ChuckC___ has joined #openstack-ironic20:18
*** ChuckC___ has quit IRC20:25
*** jrist has quit IRC20:28
*** penick has joined #openstack-ironic20:34
openstackgerritVictor Lowther proposed a change to openstack/ironic-specs: New Ironic provisioner state machine.  https://review.openstack.org/13382820:34
victor_lowtherLet the reviewinating begin!20:36
* Shrews eagerly notes the spec needing reviewification20:46
*** achanda has quit IRC20:46
JoshNangvictor_lowther: thanks for doing that spec. i thought i was going to have to :)20:54
*** ifarkas has quit IRC20:55
Shrewshrm, wonder if we really need individual fail states, or can just glom on to a single one20:56
JayFThe individual states are WONDERFUL20:57
*** krtaylor has quit IRC20:57
JayFWe key on them all the time for internal dashboards and scripts20:58
ShrewsJayF: you say "them", but we currently only have a single fail state20:59
JoshNangyou really want to treat ZAPFAIL different than DEPLOYFAIL or ERROR21:00
JayFError + Deploy Failed upstream atm afik, right?21:00
JayFWe added Decom Failed downstream21:00
ShrewsJoshNang: of course, but the logic handling the error should know if it was a ZAP or DEPLOY that failed21:02
JayFthe logic that happens once it hits that state is explicitly "operator intervention"21:02
JayFmy operational tools should be able to know at a glance what state things are in21:02
JayFand a generic ERROR state that doesn't indicate what step it failed in or how it failed isn't that useful, especially considering how wildly different our error messages are21:03
Shrewsfail is fail. perhaps you want to know from the state WHAT caused the failure though21:03
Shrewsso, i could see *that*21:03
JayFfail is not fail21:03
JayFwhy and what was happening when fail happened matters a lot21:03
ShrewsJayF: please tell that to my high  school teachers21:04
JayFespecially at scale when you're trying to automatically recover machines from bad states21:04
JayFthis is all about wrapping Ironic in automation to recover the failed states21:04
*** penick has quit IRC21:04
JayFand the state being as specific as possible as to what and when it failed is extra input to that goal21:04
mrdaMorning Ironic!21:05
ShrewsJayF: i shall rephrase: if you're saying an *external* entity needs to know what failed, then i can see individual states being useful21:05
JayFShrews: absolutely21:05
JayFShrews: my bucket full of scripts that fix boxes in decom failed /deploy failed / etc21:05
Shrewsi was considering from internal within ironic, at first21:06
JayFShrews: plus we have a dashboard that interrogates the API for things like that :) This is absolutely an external integratino helper21:06
JayFsince inherently the *FAIL states are "operator intervention required"21:06
ShrewsJayF: ok ok. i'm convinced  :-P21:07
JoshNangmrda: g'morning!21:07
Shrewsmrda: morning21:07
JayFShrews: never argue with someone who can type faster than you ;)21:07
ShrewsJayF: maybe i need a dvorak keyboard to keep up21:09
*** Viswanath has joined #openstack-ironic21:09
JayFShrews: I'm just kidding of course :P21:10
mrda\o21:10
Shrewspersonally, i can't wait for robot-monkey helpers to type for me21:10
*** Marga_ has joined #openstack-ironic21:11
mrdabe careful, they will be robot monkey overlords21:11
ShrewsI, for one, welcome our poo-flinging robotic overlords21:12
*** Viswanath has quit IRC21:12
*** achanda has joined #openstack-ironic21:14
victor_lowtherindividual fail states are doubleplusgood.21:14
*** penick has joined #openstack-ironic21:16
victor_lowtherthe recovery steps you probably want to take for DELETEFAIL (mostly automated, probably ignorable) are not the same ones you want for ZAPFAIL (OMG firmware flash hang! Call Support!)21:16
Shrewsvictor_lowther: please see the above scrollback wherein I yielded to JayF's superior intellect21:17
Shrews:)21:17
victor_lowtherdamn you scrollback!21:18
JayFvictor_lowther: in most of my downstream experience, DECOMFAIL ("ZAPFAIL") correllates strongly to hardware issues, whereas DEPLOYFAIL (which downstream is both deploy filed and delete failed) usually indicates some kind of epehemeral brokenness (like an API that's flaky, or issues downloading the image, etc)21:18
*** shakamunyi has quit IRC21:18
victor_lowtherya21:18
victor_lowtherI seperated DEPLOYFAIL and DELETEFAIL because consistency21:19
victor_lowtherand DEPLOYFAIL can mean "Why did the BIOS not switch boot modes and/or flip the VT bit"?21:19
victor_lowtherwhich probably also require manual intervention beyond a simple retry.21:20
JayFI guess so... I feel like DEPLOYING is overloaded a little bit21:20
*** anderbubble has joined #openstack-ironic21:20
JayFbut right now it's very, very overloaded so this is still better21:20
victor_lowtherthat is why I had srt on the board at the summit21:20
victor_lowtherbut the majority of the room was fine with doing that stuff in deploying.21:21
JayFWe just need to do a good job following up after this of standardizing error messages21:21
JayFbecause it should be easy to tell the difference between deployfail (prep step) and deployfail (imaging/primary deploy stuff failed)21:22
ShrewsJayF: are you talking about parsing error messages for that differentiation?21:25
JayFShrews: we absolutely parse error messages downstream today in our scripts21:26
Shrewsick21:26
JayFShrews: which is why I'd love for one day for us to standardize on sets of error messages21:26
ShrewsJayF: perhaps adding something like a "reason code" field would be better21:26
JoshNangick is right, but it works pretty well21:26
JayFShrews: imagine it this way: we classify servers as having given "moods" based on combinations of info given back from the API, including state, last_error, etc21:26
JayFShrews: once you determine the ~5 most common ways things fail, matching on the error isn't so bad21:27
Shrewsi see. but it's horrible to imagine that changing an error string upstream might break someone downstream. a numeric code would help with that21:28
Shrewsbut... hindsight and all21:28
*** Marga__ has joined #openstack-ironic21:33
JayFShrews: I wouldn't consider that "breaking" me downstream fwiw, I'd just see new unknown statuses in my dashboard and fix my classification :)21:33
*** shakamunyi has joined #openstack-ironic21:34
*** Marga_ has quit IRC21:35
*** ryanpetrello has joined #openstack-ironic21:36
*** Marga__ has quit IRC21:38
*** Marga_ has joined #openstack-ironic21:39
*** shakamunyi has quit IRC21:39
*** krtaylor has joined #openstack-ironic21:43
*** penick has quit IRC21:44
*** marcoemorais has quit IRC21:52
*** marcoemorais has joined #openstack-ironic21:53
*** ChuckC_ has joined #openstack-ironic21:54
*** ChuckC_ is now known as ChuckC21:54
*** penick has joined #openstack-ironic21:56
*** Marga_ has quit IRC22:04
*** marzif has joined #openstack-ironic22:05
*** ChuckC has quit IRC22:07
*** ChuckC has joined #openstack-ironic22:07
*** ryanpetrello has quit IRC22:07
*** jjohnson2_ has quit IRC22:11
openstackgerritA change was merged to openstack/ironic: Support ipxe with Dnsmasq  https://review.openstack.org/13049222:12
*** yjiang5 is now known as yjiang5_away22:13
*** anderbubble has quit IRC22:33
*** ChuckC has quit IRC22:39
*** ChuckC has joined #openstack-ironic22:44
*** marzif has quit IRC22:46
*** anderbubble has joined #openstack-ironic22:46
*** rushiagr_away is now known as rushiagr22:48
*** jrist has joined #openstack-ironic22:51
*** shakamunyi has joined #openstack-ironic22:59
*** jrist has quit IRC22:59
*** jrist has joined #openstack-ironic23:00
*** shakamun_ has joined #openstack-ironic23:00
*** shakamunyi has quit IRC23:04
*** athomas has quit IRC23:05
*** yuanying has joined #openstack-ironic23:07
*** shakamunyi has joined #openstack-ironic23:07
*** shakamun_ has quit IRC23:11
*** jrist has quit IRC23:14
*** andreykurilin has quit IRC23:18
*** yuanying has quit IRC23:20
*** yuanying has joined #openstack-ironic23:20
*** yuanying has quit IRC23:25
*** achanda has quit IRC23:27
*** achanda has joined #openstack-ironic23:27
*** achanda has quit IRC23:28
*** anderbubble has quit IRC23:32
*** penick has quit IRC23:35
*** yuanying has joined #openstack-ironic23:47
*** yuanying has quit IRC23:48
*** achanda has joined #openstack-ironic23:51
*** shakamunyi has quit IRC23:53

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!