Wednesday, 2014-11-12

*** shakamunyi has joined #openstack-ironic00:02
*** naohirot has joined #openstack-ironic00:02
*** ryanpetrello has joined #openstack-ironic00:08
*** shakamunyi has quit IRC00:09
*** penick has joined #openstack-ironic00:09
*** shakamunyi has joined #openstack-ironic00:10
*** shakamunyi has quit IRC00:15
*** ryanpetrello has quit IRC00:23
*** Viswanath has joined #openstack-ironic00:25
*** achanda has quit IRC00:27
*** achanda has joined #openstack-ironic00:27
*** Viswanath has quit IRC00:29
*** zyluo has joined #openstack-ironic00:29
*** shakamunyi has joined #openstack-ironic00:31
*** rushiagr is now known as rushiagr_away00:44
*** zhangyang_ has quit IRC00:47
*** penick has quit IRC00:49
*** ryanpetrello has joined #openstack-ironic00:56
*** rloo has quit IRC01:16
*** achanda has quit IRC01:19
*** achanda has joined #openstack-ironic01:20
*** achanda has quit IRC01:25
naohirotGM ironic team01:28
*** Haomeng has quit IRC01:39
*** ryanpetrello has quit IRC01:39
*** Haomeng has joined #openstack-ironic01:42
*** Haomeng has quit IRC01:47
*** Viswanath has joined #openstack-ironic01:47
*** Viswanath has quit IRC01:51
*** anderbubble has joined #openstack-ironic01:55
*** nosnos has joined #openstack-ironic02:06
*** dlaube has quit IRC02:16
*** spandhe has quit IRC02:16
*** ChuckC has quit IRC02:17
*** marcoemorais has quit IRC02:21
*** openstackgerrit has quit IRC02:34
*** anderbubble has quit IRC02:46
*** anderbubble has joined #openstack-ironic02:50
*** jrist has joined #openstack-ironic03:01
*** Haomeng has joined #openstack-ironic03:17
*** yuanying has joined #openstack-ironic03:18
*** Viswanath has joined #openstack-ironic03:22
*** Viswanath has quit IRC03:25
*** achanda has joined #openstack-ironic03:27
*** shakamunyi has quit IRC03:32
*** teju has joined #openstack-ironic03:33
*** __mohit__ has joined #openstack-ironic03:41
*** __mohit__ has quit IRC03:41
*** yuanying has quit IRC03:46
*** yuanying has joined #openstack-ironic03:46
*** zyluo has quit IRC03:50
*** rameshg87 has joined #openstack-ironic03:53
naohirotrameshg87: Hello04:14
naohirotsorry for not being able to reply to you04:15
naohirotyesterday04:15
*** pensu has joined #openstack-ironic04:15
naohirotI certainly looked at the URL  https://github.com/hpproliant/proliantutils/04:16
rameshg87naohirot, hello04:16
naohirotHi04:17
rameshg87naohirot, did i answer your question yesterday ? :)04:17
naohirotYes, you did :-) thanks!04:17
rameshg87naohirot, great :)04:17
*** Nisha has joined #openstack-ironic04:18
naohirotThe page https://wiki.openstack.org/wiki/Ironic/Drivers/iLODrivers04:18
naohirotis excellent.04:18
naohirotit's very helpful to understand what is iLO driver.04:19
naohirotI'm still in the stage to understand overall picture.04:20
naohirotI submitted 4 blue prints, and right now I'm in the process of witting the spec of the first one, pxe_irmc driver.04:22
*** pensu has quit IRC04:23
naohirotdo you think that I should write similar spec as04:23
naohirothttps://github.com/openstack/ironic-specs/blob/master/specs/juno/drac-management-driver.rst04:24
naohirotand04:24
naohirothttps://github.com/openstack/ironic-specs/blob/master/specs/kilo/ilo-management-interface.rst04:24
naohirot?04:24
*** pcrews has quit IRC04:33
*** subscope has joined #openstack-ironic04:36
rameshg87naohirot, sorry, i just saw your messages now04:47
rameshg87naohirot, may be you can add my name to the messages if it was to me so that i will get a notification04:47
naohirotthat's ok, no problem.:-)04:47
naohirotOkay, I'll do that.04:48
rameshg87naohirot, are you planning to have a management interface for your hardware ? if so, you should write a similar spec04:51
naohirotrameshg87: yes, pxe_irmc implements like pxe_ilo and pxe_drac.04:54
naohirotrameshg87: I believe that pxe part is common. the different part are get/set boot device, and power on/off.04:56
*** jrist has joined #openstack-ironic04:57
rameshg87naohirot, yes04:57
naohirotrameshg87: So maybe I need to write similar spec with https://github.com/openstack/ironic-specs/blob/master/specs/juno/drac-power-driver.rst too.04:57
rameshg87naohirot, so you may submit two different specs - one for irmc power interface and one for irmc management interface04:57
rameshg87naohirot, yes04:58
naohirotrameshg87: I see. that make sense to me. thanks!04:58
*** pensu has joined #openstack-ironic05:18
*** loki184 has joined #openstack-ironic05:21
*** rakesh_hs has joined #openstack-ironic05:44
*** lazy_prince has quit IRC05:57
*** lazy_prince has joined #openstack-ironic05:57
*** rushiagr_away is now known as rushiagr06:14
*** pradipta_away is now known as pradipta06:28
*** k4n0 has joined #openstack-ironic06:37
*** subscope has quit IRC06:55
*** achanda has quit IRC06:57
*** achanda has joined #openstack-ironic07:01
*** achanda has quit IRC07:10
*** anderbubble has quit IRC07:14
*** erwan_taf has joined #openstack-ironic07:35
*** chenglch has joined #openstack-ironic07:46
*** dlpartain has joined #openstack-ironic07:50
*** dtantsur|afk is now known as dtantsur07:52
dtantsurMorning Ironic07:52
naohirotdtantsur: good morning07:53
*** erwan_taf has quit IRC08:01
naohirotdtantsur: isn't there a bug which can be fixed easily?08:02
dtantsurlemme see08:02
naohirotdtantsur: If there were, I'd like to try it to learn the process of the ironic development.08:03
*** jistr has joined #openstack-ironic08:08
Haomengnaohirot: welcome, you can take this as reference - http://docs.openstack.org/developer/ironic/dev/dev-quickstart.html08:13
naohirotHaomeng: Hi Haomeng08:14
naohirotHaomeng: I went through the page.08:14
naohirotHaomeng: pxe_ssh driver worked ok, but agent_ssh always became error due to timeout.08:15
Haomengnaohirot: ok08:15
Haomengnaohirot: have to check agent side log08:15
Haomengnaohirot: so far we have no take agent log back to conductor side, so it it diffcult to debug, have to check physical machine console output08:16
Haomengnaohirot: to see the hang point08:16
naohirotHaomeng: I checked the log, and I found three error in screen conductor's log.08:16
*** erwan_taf has joined #openstack-ironic08:16
Haomengnaohirot: can you paste the error message via http://paste.openstack.org/08:16
naohirotHaomeng: Ok, just moment.08:17
Haomengnaohirot: no rush:)08:17
dtantsurnaohirot, that's what we use to search for easy bugs: https://bugs.launchpad.net/ironic/+bugs?field.tag=low-hanging-fruit08:17
dtantsurnaohirot, have a look at e.g. https://bugs.launchpad.net/ironic/+bug/127728208:18
dtantsuror https://bugs.launchpad.net/ironic/+bug/132626908:18
naohirotHaomeng: I pasted my log.08:19
Haomengnaohirot: ok08:19
naohirotdtantsur: thanks, I read the bug/1326269.08:24
naohirotdtantsur: Drivers page (doc/source/dev/drivers.rst) should be updated. Do you think how many lines of explanation is expected?08:26
dtantsuroh I don't know :) imagine you just came to Ironic and read this new explanation. what will be sufficient for you?08:26
*** jcoufal has joined #openstack-ironic08:28
naohirotdtantsur: I see. When I went through the quick start page, I also found some places which more explanation should be added.08:29
dtantsurnaohirot, feel free to propose changes, that's always very good to have feedback from fresh point of view :)08:30
naohirotdtantsur: So I can submit similar improvement suggestion as a bug, and fix it by myself.08:30
dtantsurnaohirot, for small improvements you don't need a bug IMO08:31
naohirotdtanstsur: Okay, I'll try, please assign bug/1326269 to me.08:32
dtantsurnaohirot, you can assign bugs to yourself (especially since I don't know your ID)08:33
naohirotdtantsur: really?08:34
dtantsurnaohirot, yeah, press edit button next to " Unassigned" in "Assigned to" column08:35
naohirot dtantsur: In case of "TRIAGED", who triaged?08:35
dtantsurnaohirot, didn't quite get your question. Assignee is who is working on the bug. Triager is one of us that sets priority and confirms bugs08:36
Haomengnaohirot: yes, just click 'edit' icon in 'assigned to' colume and click 'assing me', done:)08:37
naohirotdtantsur: I see, "TRIAGED" is one of state of a bug toward "FIX COMMITTED".08:38
*** Nisha has quit IRC08:38
dtantsurnaohirot, triaged means "we understand how to fix it", while "confirmed" is "we understand it's a bug, but still not sure how to fix it"08:39
dtantsurdoes it make things clearer? :)08:39
naohirotdtantsur: Haomeng: Yes, very clear. I understood. Thanks! :-)08:40
*** ifarkas has joined #openstack-ironic08:41
Haomengnaohirot: welcome08:41
Haomengnaohirot: feel free to ask question here, all of us can help you, good luck08:42
naohirotHaomeng: Thank you for saying that. Here is easier than mailing list to ask such basic question :-)08:44
*** rakesh_hs has quit IRC08:44
*** rakesh_hs has joined #openstack-ironic08:46
*** Nisha has joined #openstack-ironic08:46
Haomengnaohirot: yes, we are all same way from basic... :)08:46
Nishadtantsur: hi08:47
*** pradipta is now known as pradipta_away08:48
Haomengnaohirot: based on your log message - FailedToUpdateDHCPOptOnPort: No VIFs found for node ca91bacc-e943-4e35-896a-47c9a275b976 when attempting to update DHCP BOOT options.08:49
Haomengnaohirot: it should be neutron issue08:49
Haomengnaohirot: can you check neutron logs08:49
Haomengnaohirot: looks like the nif is not ready during bm provisioning08:49
naohirotHaomeng: Okay, you got the log.08:50
Haomengnaohirot: have to run neutron command to check the dhcp port information by instance id08:50
dtantsurNisha, hi08:50
Haomengnaohirot: yes, i got your log08:51
Nishadtantsur: i was seeing ur comments on discovery spec08:51
Nishai made management interface to create ports08:51
Nishaas per the spec08:51
Nishadtantsur: do you expect anything else for in-band?08:51
*** romcheg has joined #openstack-ironic08:52
Nishadtantsur: yesterday, lucasgomes told that its decided that in-band will not be done via generic, while it will be third party driver08:53
Nishadtantsur: please give comments in the spec where all you see the changes will be required for in-band08:53
naohirotHaomeng: do you think that there is some relation between first two JSONDecodeError errors and the last VIFs error?08:53
naohirotHaomeng: I put the url here too. http://paste.openstack.org/show/132230/08:55
Nishadtantsur: excerpt from yesterday's discussion: "2014-11-11T10:05:33  <lucasagomes> Nisha, no in-band is out of ironic codebase 2014-11-11T10:05:51  <lucasagomes> if people is willing to do in-band discovery they will need a third-party service to"08:55
Haomengnaohirot: dont think so,ok will check your new log08:55
naohirotHaomeng: the url I put here is the same log, not new log.08:56
Haomengnaohirot: yes, same one08:58
Haomengnaohirot: can you try with pxe_ipmitool driver?08:58
Haomengnaohirot: it is easy one then IPA08:59
dtantsurNisha, that does not contradict, we'll still need discoverd for in-band. But the common API should invoke it.08:59
Nishadtantsur: the management interface is the one i remeber was your comment for that09:00
Haomengnaohirot: how did you run ironic, with devstack?09:00
naohirotHaomeng: Yes I can try pxe_ipmitool driver. I confirmed that pxe_ssh in my environment.09:00
Haomengnaohirot: yes, pxe_ssh is easy for dev/debug09:01
*** rushiagr has quit IRC09:01
Haomengnaohirot: pxe_ipmitool is used for real physical node I think if you have hardware server09:01
*** rushiagr has joined #openstack-ironic09:02
naohirotHaomeng: I followed the exactly same steps as the page http://docs.openstack.org/developer/ironic/dev/dev-quickstart.html#deploying-ironic-with-devstack.09:02
Haomengnaohirot: yes, that is good09:02
Nishadtantsur: it will be better if you could provide the comment in spec where and how you feel the interface shall be modified to support in-band. i have less hands on in-band :(09:03
Haomengthe default driver is "IRONIC_DEPLOY_DRIVER" with this document09:03
naohirotHaomeng: Yes, I have a physical server.09:03
Haomengnaohirot: so if you want to run with pxe_ssh driver, have to change the ironic.conf file to enable it09:03
Haomengnaohirot: cool09:03
dtantsurNisha, readding comments now09:03
Haomengnaohirot: can you check from neutron side09:04
Haomengnaohirot: neutron port-list09:04
Haomengnaohirot: to check if the dhcp port is created already09:04
Haomengnaohirot: will be back after a while, good luck:)09:05
naohirotHaomeng: Okay, I'll try it, and see the dhcp port.09:05
*** jistr has quit IRC09:06
naohirotHaomeng: Thanks a lot.09:06
dtantsurNisha, done09:07
*** foexle has joined #openstack-ironic09:08
dtantsurNisha, tl;dr the only difference between OOB and IB is that IB is _essentially_ async, so you can't rely on it returning values right away09:09
dtantsurNisha, that may potentially by the case for some OOB too09:09
Nishadtantsur: ok. So i have proposed discovery APIs and management interface to be both synchronous and asynchronous as per driver choice.09:10
*** derekh has joined #openstack-ironic09:10
dtantsurNisha, lucas meant that we won't _implement_ IB discovery as part of Ironic (and that's true)09:10
Nishadtantsur: :)09:10
Nishaok i will just address the comments in the spec09:11
dtantsurNisha, they are always async, but the problem is that you expect driver discover_hardware_properties to return something, which may not be possible09:11
dtantsurNisha, yes please :)09:11
Nishadtantsur: :) i didnt realize that it requires change09:12
Nishadtantsur: thanks for the comments.09:12
dtantsurNisha, see http://kilodesignsummit.sched.org/event/6be748864a8d14ee914d292bd0e8c816#.VGMkfH-LL5s : it's stated as " requires a solution which accommodates both in- and out-of-band methods within a common API. "09:13
dtantsurthat's why I'm thinking that your API will need to _potentially_ support both09:13
dtantsurno problem, you're welcome :)09:13
Nishadtantsur: yes thanks09:13
*** igordcard has joined #openstack-ironic09:19
*** athomas has joined #openstack-ironic09:20
*** dlpartain has quit IRC09:23
*** andreykurilin has joined #openstack-ironic09:25
*** jistr has joined #openstack-ironic09:26
*** lucasagomes has joined #openstack-ironic09:26
*** ndipanov_gone is now known as ndipanov09:29
*** rakesh_hs has quit IRC09:31
pensuHi dtantsur09:32
dtantsurpensu, hi09:33
pensudtantsur: I have a question regarding this: http://docs.openstack.org/developer/ironic/deploy/install-guide.html#configure-neutron-to-communicate-with-the-bare-metal-server09:33
pensudtantsur: what is 'physnet1' here supposed to be?09:33
pensudtantsur: the same physical interface which is connected to bare metal node?09:33
dtantsurI don't really know neutron, sorry :(09:34
dtantsurHaomeng, any ideas ^^^09:34
*** rakesh_hs has joined #openstack-ironic09:35
*** MattMan has quit IRC09:39
*** MattMan has joined #openstack-ironic09:40
pensudtantsur: np..:) lucasagomes: jroll: ^^09:51
dtantsurbrb09:51
Haomengdtantsur: I am back10:00
Haomengdtantsur: our team has neutron expert, so I learn with her:)10:01
*** sambetts has joined #openstack-ironic10:01
Haomengpensu: for physnet1, that is defined with neutron to connect to physical and define the vlan tag numbers10:01
Haomengpensu: "bridge_mappings = physnet1:br-eth2" means that the br-eth2 will take as physical network connection with eth2, and eth2 will be connected with switch on the vlan trunk/access port with fix vlan tag defined by switch10:03
*** andreykurilin has quit IRC10:05
Haomengpensu: so, for the example in document, we will take eth2 physical as the external physical network connection with our neutron10:05
*** achanda has joined #openstack-ironic10:11
Nishadtantsur: i posted the patch with comments addressed and some questions in comments for previous patch.10:15
*** achanda has quit IRC10:15
*** krtaylor has quit IRC10:16
Nishapensu: the eth2 is the nic/mac address of the cloud controller which connects to the baremetal10:19
*** chenglch has quit IRC10:22
*** Nisha has quit IRC10:23
*** krtaylor has joined #openstack-ironic10:24
pensuHaomeng: Nisha: got it, guys, thanks! :)10:32
Haomengpensu: wel, any time10:33
*** dprince has joined #openstack-ironic10:39
*** nosnos has quit IRC10:39
*** ndipanov has quit IRC10:56
*** ndipanov has joined #openstack-ironic10:58
*** romcheg1 has joined #openstack-ironic11:00
*** romcheg has quit IRC11:00
*** nosnos has joined #openstack-ironic11:02
*** romcheg1 has quit IRC11:03
*** romcheg has joined #openstack-ironic11:03
*** loki184 has quit IRC11:08
*** ndipanov has quit IRC11:14
*** rakesh_hs2 has joined #openstack-ironic11:20
*** rakesh_hs has quit IRC11:23
*** ndipanov has joined #openstack-ironic11:27
rameshg87ifarkas, hi11:28
ifarkasrameshg87, hi11:28
rameshg87ifarkas, got some time to discuss regarding raid configuration ?11:29
*** erwan_taf has quit IRC11:29
ifarkasrameshg87, yeah, I have11:29
ifarkasrameshg87, did you see the drac spec?11:29
rameshg87ifarkas, yeah i saw that11:30
rameshg87ifarkas, it talks about vendor passthru right ? are you still planning for a vendor passthru for raid configuration ?11:31
ifarkasrameshg87, I am planning to update it based on our discussion to propose a raid interface11:31
rameshg87ifarkas, yes11:31
rameshg87ifarkas, we could go for adding raid support in long-term running tasks (that happens before the node reaches available state)11:32
ifarkasrameshg87, did you have a chance to discuss it with the rackspace folks?11:33
rameshg87ifarkas, i talked to JayF, he wants us to pursue the hardware capabilities spec https://review.openstack.org/#/c/131272/11:34
ifarkasrameshg87, I meant if you had a chance to discuss with them whether it should go to zapping or prepare11:35
rameshg87ifarkas, ah no :(11:35
*** pensu has quit IRC11:35
rameshg87ifarkas, http://eavesdrop.openstack.org/irclogs/%23openstack-ironic/%23openstack-ironic.2014-11-11.log (search for "2014-11-11T18:21:38")11:36
ifarkasrameshg87, ok, no worries11:36
rameshg87ifarkas, will check with them today11:36
rameshg87ifarkas, for us, we are targetting the inband stuff, so would like to put it in zapping11:36
rameshg87ifarkas, we are planning to do raid configuration through inband utility within ipa11:37
ifarkasrameshg87, oh, so you no longer prefer prepare?11:37
rameshg87ifarkas, kind of not :)11:37
rameshg87ifarkas, the reason is our out-of-band approach isn't fully capable of doing raid configuration, there are some challenges11:37
*** rakesh_hs2 has quit IRC11:37
ifarkasrameshg87, ok, then I will propose the spec this way and then everyone can comment on it11:37
rameshg87ifarkas, so you want to continue with vendor passthru ?11:38
ifarkasrameshg87, no, I will try to propose a raid interface11:38
rameshg87ifarkas, okay ..11:38
rameshg87ifarkas, and do them as part of zapping or prepare ?11:38
ifarkasrameshg87, zapping is fine for me as well11:39
rameshg87ifarkas, great11:39
*** rakesh_hs has joined #openstack-ironic11:39
rameshg87ifarkas, so we could have the same interface to the operator atleast11:39
ifarkasrameshg87, yeah, that would be great11:39
rameshg87ifarkas, i am thinking about this11:39
rameshg87ifarkas, the operator would say on what raid he wants the node to be configured11:40
rameshg87ifarkas, the node would create the maximum possible disk of that raid configuration and then return the disk information back to the properties11:40
rameshg87ifarkas, i am not sure if we can accept the size of the logical drive to be created11:41
ifarkasrameshg87, I think it should be configurable11:41
rameshg87ifarkas, because different raid configurations have different space utilizations11:41
ifarkasrameshg87, eg. for storage node, you want to have an array for the os and then another one for the actual storage device11:42
rameshg87ifarkas, hmm.. yeah i agree11:42
rameshg87ifarkas, but what worries me is this11:42
rameshg87ifarkas, if i have 10x50G disks on the RAID controller11:43
rameshg87ifarkas, if operator says RAID0, i can create logical disks update 500G11:43
rameshg87ifarkas, if operator says RAID1, i can create only upto 250G11:44
rameshg87ifarkas, so we will have to do the math after checking the physical drive information.11:44
rameshg87ifarkas, if not sufficient disks, we might need to error out11:44
ifarkasrameshg87, hmm. don't we want to leave the calculation for the operator?11:45
rameshg87ifarkas, so we would assume that the input is correct (RAID level and logical disk sizes) and go ahead with the configuration ?11:46
ifarkasifarkas, yes11:46
ifarkasrameshg87, if it fails, the operator will eventually find that out11:46
rameshg87ifarkas, hmm yeah that's fine11:47
rameshg87ifarkas, so we had talked about zapping would happen to move the node from init -> available, right ?11:48
ifarkasrameshg87, cool. and if later we think that would be a useful feature, we can add it later11:48
ifarkasrameshg87, yeah11:48
rameshg87ifarkas, yeah makes sense .. may be later11:48
rameshg87ifarkas, when the node is in init, the operator will have to put this information into the node. RAID level and the size of logical disks. probably in driver_info ?11:49
ifarkasrameshg87, yeah, that's a good place for that11:50
rameshg87ifarkas, okay. so once the zapping task for raid configuration is done, it would update the capabilities11:51
rameshg87ifarkas, and properties for the disk size11:51
rameshg87ifarkas, and that information would go to the nova scheduler to allow user to choose a node11:51
ifarkasrameshg87, yeah, devananda also added this comment to my spec11:52
rameshg87ifarkas, in flavor we could set disk=50 and in flavor's extra spec will have raid_level=111:52
rameshg87ifarkas, if user never cared about raids, it wouldn't become a scheduling criteria and the node can still be allocated to the user11:53
ifarkasrameshg87, and if it is specified then nova would be able to pick a correct one11:53
rameshg87ifarkas, yeah ..11:54
rameshg87ifarkas, there we go .. we have the solution :)11:54
ifarkasrameshg87, excellent ;-)11:54
rameshg87ifarkas, i can still make use of the raid interface that you would be using11:55
ifarkasrameshg87, what do you mean?11:55
rameshg87ifarkas, if node is already booted to ipa ramdisk, i can use the interface to talk to ipa and get it done11:56
rameshg87ifarkas, for example create_virtual_disk() call, i could talk to ipa to get it done11:56
ifarkasrameshg87, yeah , right11:57
rameshg87ifarkas, will you doing the creation/deletion synchronously in oob drac approach ?11:59
*** dlpartain has joined #openstack-ironic11:59
rameshg87ifarkas, but there wouldn't be a chance of call-back in oob approach, right. that was a stupid question i think :)12:00
ifarkasrameshg87, right, and synchronous is not possible with the drac12:00
rameshg87ifarkas, as part of zapping, so would you trigger a job in drac controller, and keep polling the status of the job ?12:01
ifarkasrameshg87, yes12:01
rameshg87ifarkas, okay12:01
rameshg87ifarkas, i could trigger the job in ipa, and ipa could notify it back once it is done12:02
ifarkasrameshg87, cool12:03
rameshg87ifarkas, i was just thinking what all should be part of the raid interface12:03
rameshg87ifarkas, should it be just logical disk size and raid level ?12:03
rameshg87ifarkas, the driver could select the raid controller and the physical disks to use for creating the logical disk12:04
ifarkasrameshg87, oh, right. What if there are multiple raid controllers?12:04
rameshg87ifarkas, yeah, there could be multiple raid controllers12:05
ifarkasrameshg87, according to my original proposal the workflow would be for the operator to first list the physical disks and raid controllers and then create the virtual disk12:05
rameshg87ifarkas, yeah but that would be too much for the operator to do when there are 100 nodes12:05
ifarkasrameshg87, true12:06
rameshg87ifarkas, i guess we could just take raid level and logical disk sizes as input from operator for raid configuration12:06
ifarkasrameshg87, the input should also contain the controller, shouldn't it?12:07
rameshg87ifarkas, but wouldn't that vary across different nodes ?12:07
rameshg87ifarkas, does the operator really care which controller it is configured in ?12:08
ifarkasrameshg87, hmm, not sure12:08
ifarkasrameshg87, ok, so we can pick the first one if there are multiple controllers12:08
rameshg87ifarkas, yeah12:08
rameshg87ifarkas, and we could allow them to specify optional inputs like stripe size (which you have mentioned in your spec)12:09
ifarkasrameshg87, yeah12:10
rameshg87ifarkas, and then there would be a delete_disk which again takes the logical disk size (and optional raid level ??) to delete the disk12:11
ifarkasrameshg87, delete_disk should just have the disk id as an input, not?12:11
ifarkasrameshg87, why does it care about disk size?12:12
rameshg87ifarkas, but where is this disk id ?12:12
rameshg87ifarkas, from raid controller ? is it applicable to all logical disks created ?12:12
*** dprince has quit IRC12:13
*** dlpartain1 has joined #openstack-ironic12:13
ifarkasrameshg87, how about adding the id to capabilities?12:14
rameshg87ifarkas, yeah that makes sense12:14
ifarkasrameshg87, the problem is what ironic will do if there's to logical disk with the same size12:14
rameshg87ifarkas, but thinking about cloud use-case, i don't know if we will ever delete a single logical disk12:14
ifarkass/to/two12:14
rameshg87ifarkas, just imagining the use-cases12:15
*** dlpartain has quit IRC12:15
*** teju has left #openstack-ironic12:15
rameshg87ifarkas, when node is enrolled, operator says i need two logical disks of 100G each with RAID1 on this node12:15
rameshg87ifarkas, and we create it as part of zapping12:15
rameshg87ifarkas, the node gets scheduled to someone, then at some point later is teared down, and disks are erased as part of decommissioning12:16
ifarkasrameshg87, right, so you would prefer something like clear_raid_config?12:16
rameshg87ifarkas, exactly12:16
rameshg87ifarkas, :)12:16
ifarkasrameshg87, ok12:16
*** lucasagomes is now known as lucas-hungry12:17
rameshg87ifarkas, unless operator wants to change the raid configuration12:17
rameshg87ifarkas, i don't see why they would delete a single disk12:17
ifarkasrameshg87, I agree that's not a very likely usecase12:17
rameshg87ifarkas, okay12:17
rameshg87ifarkas, so we would have 2 method for raid interface - create_raid_configuration and delete_raid_configuration12:18
rameshg87ifarkas, ??12:18
ifarkasrameshg87, yes12:18
rameshg87ifarkas, create_raid_configuration accepts a list of logical disk information [ {disk_size:50, raid_level:1}, {disk_size:100, raid_level:5}, .. ]12:19
rameshg87ifarkas, does the above make sense ?12:19
ifarkasrameshg87, absolutely ;-)12:19
rameshg87ifarkas, and clear_raid_configuration wouldn't anyway accept anything :)12:19
ifarkasrameshg87, yeah, basically none of them has input because they are using the driver_info field, right?12:20
rameshg87ifarkas, yeah ..12:21
rameshg87ifarkas, would we overload driver_info with raid configuration data ?12:21
ifarkasrameshg87, otherwise how would ironic do it during zapping?12:22
rameshg87ifarkas, or may be extra ?12:22
ifarkasrameshg87, yeah, that would also work12:22
rameshg87ifarkas, yeah, may be we can start with extra and see what others think. what do you say ?12:23
ifarkasrameshg87, not sure which one is prefer for this type of data12:23
ifarkasrameshg87, ack12:23
rameshg87ifarkas, just one question12:24
rameshg87ifarkas, isn't swapping and decommissioning one and the same ?12:25
ifarkasrameshg87, I guess you meant zapping12:26
rameshg87ifarkas, oh i meant zapping12:26
rameshg87ifarkas, yeah :)12:26
ifarkasrameshg87, decommissioning is supposed to be part of zapping12:26
rameshg87ifarkas, got it12:26
ifarkasso yes ;-)12:26
rameshg87ifarkas, and we missed one part12:26
rameshg87ifarkas, get_current_raid_configuration should also be part of the interface12:27
*** pensu has joined #openstack-ironic12:27
rameshg87ifarkas, everytime the node is returned back, we could make sure that the node is still configured the same raid configuration that the operator wishes12:27
rameshg87ifarkas, if it is not, we could just delete_raid_configuration and then do create_raid_configuration again12:28
rameshg87ifarkas, so that we don't have to do this again and again until it really changes12:28
rameshg87ifarkas, what do you say ?12:28
ifarkasrameshg87, ok, how about naming it as check_current_raid_config because it must be async and get presumes synchronicity?12:29
*** rushiagr is now known as rushiagr_away12:31
rameshg87ifarkas, and how would it stay async ?12:32
*** romcheg has quit IRC12:32
*** romcheg has joined #openstack-ironic12:33
rameshg87ifarkas, i am really sorry, i would need to leave now :(12:33
ifarkasrameshg87, okay, we can discuss it later, or tomorrow12:34
rameshg87ifarkas, i will catch you later, may be one round of discussion more, we should have something12:34
ifarkasrameshg87, I need to think about your q12:34
ifarkasrameshg87, definietly12:34
rameshg87ifarkas, see you then .. bye :)12:34
ifarkasrameshg87, bye ;-)12:34
*** rameshg87 has quit IRC12:34
*** ryanpetrello has joined #openstack-ironic12:38
*** erwan_taf has joined #openstack-ironic12:40
*** Haomeng|2 has joined #openstack-ironic12:46
*** Haomeng has quit IRC12:47
*** naohirot has quit IRC13:00
*** pelix has joined #openstack-ironic13:01
*** krtaylor has quit IRC13:01
*** dprince has joined #openstack-ironic13:01
*** nosnos has quit IRC13:10
*** krtaylor has joined #openstack-ironic13:15
*** lucas-hungry is now known as lucasagomes13:18
*** dlpartain1 has quit IRC13:35
*** k4n0 has quit IRC13:46
*** lucasagomes_ has joined #openstack-ironic13:50
*** lucasagomes has quit IRC13:54
*** sambetts has quit IRC13:55
*** sambetts has joined #openstack-ironic13:56
NobodyCammorning Ironic13:59
vdrokhi everyone!14:10
romchegMorning Ironic!14:10
vdrokmorning NobodyCam14:10
romchegHi vdrok!14:10
vdrokafternoon romcheg !14:10
NobodyCammornig vdrok romcheg14:11
* NobodyCam just got back home lastnight14:11
vdroklucasagomes_, hi14:11
dtantsurmorning folks :)14:12
vdrokhi dtantsur14:12
*** rakesh_hs has quit IRC14:17
*** lucasagomes_ is now known as lucasagomes14:17
lucasagomesNobodyCam, morning14:17
lucasagomesvdrok, hi there14:18
vdroklucasagomes, yuriyz told that there is some agreement on this one https://review.openstack.org/#/c/130228/ ?14:18
lucasagomesvdrok, yeah I brought it up on the "making ironic easier to use" session14:19
lucasagomesoverall I think people agree it's a good idea14:19
lucasagomesit was just a mention, I'm looking fwd to see the comments from others on that review14:20
NobodyCammorning lucasagomes14:20
NobodyCammornig dtantsur14:20
vdroklucasagomes, aha, ok, thanks14:21
lucasagomesvdrok, np, I think there's an etherpad on that session with what was proposed/discussed for reference14:23
lucasagomeshttps://wiki.openstack.org/wiki/Summit/Kilo/Etherpads#Ironic14:23
vdrokoh, thanks, will read14:23
*** anderbubble has joined #openstack-ironic14:25
*** anderbubble has quit IRC14:27
*** shakamunyi has joined #openstack-ironic14:31
*** rloo has joined #openstack-ironic14:31
*** krtaylor has quit IRC14:33
lucasagomes[offtopic14:35
*** pensu has quit IRC14:35
* lucasagomes hits enter too quick14:36
lucasagomes[offtopic] someone here uses google play music?14:36
*** adam_g` is now known as adam_g14:37
dtantsurtried14:37
dtantsurdidn't work for me14:37
*** adam_g has quit IRC14:37
*** adam_g has joined #openstack-ironic14:37
*** athomas has quit IRC14:38
lucasagomesdtantsur, oh, I mean the paid service14:38
lucasagomes(full access I think that's how the call it)14:38
dtantsurlucasagomes, I was subscribed for a couple of months14:39
dtantsurit sucks14:39
lucasagomesgotcha14:39
lucasagomesright I will stick to spotify then :)14:39
lucasagomesthanks14:39
*** openstackgerrit has joined #openstack-ironic14:40
*** krtaylor has joined #openstack-ironic14:42
*** athomas has joined #openstack-ironic14:42
openstackgerritAdam Gandelman proposed openstack/ironic: Testing forward grenade migration (Do not merge)  https://review.openstack.org/12447414:43
adam_gJayF, http://logs.openstack.org/21/133921/1/check/check-tempest-dsvm-ironic-agent_ssh-nv/afb2c10/ passing now14:44
lucasagomeswoah14:46
*** vdrok has quit IRC14:52
*** vdrok has joined #openstack-ironic14:52
*** krtaylor has quit IRC14:58
dtantsurfolks are already planning their midcycles. should we?15:03
NobodyCamI just got home. Thou we did chat about it at the summit15:03
rloodtantsur: take a look at the etherpad - deva put some notes there about midcycle.15:04
NobodyCamI vote for palm springs CA, usa :-p15:04
NobodyCammorning rloo15:04
rloodtantsur: bottom of https://etherpad.openstack.org/p/IronicWhiteBoard15:04
dtantsuryeah, I've seen it, I'm interesting in the follow-up :)15:04
rloohiya NobodyCam! How was your trip/site-seeing?15:05
rloodtantsur: I'm not interested. ha ha. I see that the etherpad doesn't mention possible dates, although that was discussed.15:05
NobodyCamit was Great I got to meet *most* all of johns family )15:06
rloodtantsur: maybe ping devananda about it. or Put it on the agenda for our meeting? or should it be an email?15:06
rlooNobodyCam: are they like John? :-)15:06
NobodyCam:)15:06
*** anderbubble has joined #openstack-ironic15:07
NobodyCamthey are a really nice group of folks, lol, they sent us home with like 25 lbs of different english candy15:08
rlooNobodyCam: ha ha. Better make a dentist appointment!15:10
NobodyCamlol ...yup :-P15:10
*** romcheg has quit IRC15:11
*** romcheg has joined #openstack-ironic15:12
*** romcheg has quit IRC15:12
*** ChuckC has joined #openstack-ironic15:12
openstackgerritDmitry Tantsur proposed openstack/ironic: Make some periodic tasks run in parallel  https://review.openstack.org/13397615:13
*** romcheg has joined #openstack-ironic15:16
*** romcheg has left #openstack-ironic15:16
*** romcheg has joined #openstack-ironic15:17
*** anderbubble has quit IRC15:17
*** romcheg has left #openstack-ironic15:18
*** dprince has quit IRC15:18
*** romcheg has joined #openstack-ironic15:19
*** ryanpetrello has quit IRC15:19
*** pensu has joined #openstack-ironic15:20
lucasagomesdtantsur, NobodyCam rloo about the mid-cycle, tho I love it I think that us as a open source project should also discuss a bit15:23
lucasagomeshow much of the face to face thing is required for an open source project15:24
openstackgerritVictor Lowther proposed openstack/ironic-specs: New Ironic provisioner state machine.  https://review.openstack.org/13382815:24
dtantsurlucasagomes, seems like a lot :-/15:24
*** ryanpetrello has joined #openstack-ironic15:25
lucasagomesdtantsur, yeah, that's the line I'm looking here, cause seems there's something broken in our development process if that's the case15:25
rloolucasagomes: yeah. There was a discussion on the list awhile ago. I personally think 4 times/year is a lot (not that I don't like seeing you but...) However, others have said the midcycles are more useful than the summits (or something like that)15:25
lucasagomesrloo, I think midcycle are more productives in terms of coding15:25
lucasagomesit's like a hackaton15:26
lucasagomesbut yeah I feel that 4x year, for an opensource project is a bit too much. I also worry about excluding folks that can't attend for whatever reason (visa, budget etc)15:26
rloolucasagomes: is it possible to do a hackathon via eg google-whatever? Cuz not everyone at the midcycle are hacking on the same thing?15:26
lucasagomesrloo, yeah it would be possible I believe15:27
lucasagomesthis midcycle we may try the tele-conference thing for those who can't attend15:27
lucasagomesI hope that work out well15:27
*** penick has joined #openstack-ironic15:27
rloowe'll see. I think that as long as these meet ups work for people and as long as people want to go, then fine. Just don't make it mandatory for others.15:28
rlooi like the idea of the meetup being in Europe this time (if there has to be a meetup) because that makes it easier for Europeans to attend.15:29
lucasagomesyeah sounds reasonable, but I'd like to have us to talk to see what we can improve in the development in a distributed way15:29
rloolucasagomes: agreed.15:29
devanandasomething seems odd with my cell ph here ...15:30
lucasagomesdevananda, morning there15:30
dtantsurdevananda, o/15:30
devanandalucasagomes: afternoon, actually15:30
rlooIt's Wednesday, devananda, do you know where you are? :-)15:31
lucasagomesdevananda, oh yeah indeed, is it 13:00ish now?15:31
rloodtantsur: I have a question for you wrt the Ironic Inbox. Is there any (easy) way to list patches to Nova's ironic driver?15:32
dtantsurrloo, I doubt it honestly15:33
devanandathere are patches up for the nova driver?15:33
rloodevananda: I have no idea. That's why it'd be good to have some way to know.15:33
devanandarloo: in principle, you can set a file-based watch in gerrit15:33
ChuckChi ironic15:34
rloodevananda: hmm. thx. I'll keep that in mind. If I decide to look into it.15:35
rloohi ChuckC15:35
ChuckCrloo: hi15:35
ChuckCrloo: I have a network boot question15:36
ChuckCrloo: do you know who I should bug?15:36
lucasagomesChuckC, ask it here in the channel someone may know and answer that15:36
rlooChuckC: best not to bug anyone, but if you want to, I think you can just ask and hopefully someone will jump in.15:36
lucasagomesand it also benefit other people reading the channel logs15:36
ChuckCrloo: lucasagomes: sure :)15:37
rlooChuckC: don't worry about 'bugging'.15:37
devanandaChuckC: can you be more precise w.r.t. network boot?15:38
ChuckCif neutron were to support using dhcp client id, would that be helpful in allowing ironic to boot from any of a set of nics?15:38
devanandaoh. that's _totally_ not what I thought you meant. glad I asked :)15:39
ChuckCrloo: I don't really worry about bugging folks ;)15:39
ChuckCboot a server, that is15:39
ChuckCWhat I don't know is whether the boot protocols can use dhcp client id15:39
NobodyCammorning devananda15:40
devanandaChuckC: ironic/dhcp/neutron.py L160 -- looks like Ironic will attempt to update the dhcp options for every port belongong to a node15:41
devanandait aborts the deploy if all attempts fail; continues if at least one port update completed15:41
devanandaNobodyCam: g;morning15:41
NobodyCam:) off to go pickup the kids15:42
devanandaChuckC: i'm not immediately seeing how DHCP Client ID would change things. can you explain what you're thinking?15:42
ChuckCdevananda: well, DHCP client id can be used instead of mac address to vend and IP, so multiple nics with the same dhcp client id could get the same IP address15:45
ChuckCdevananda: which would be handy in case a nic fails, an alternate nic could be used15:45
ChuckCdevananda: but I have no idea about boot protocols, so I don't know if the client side can be set up to use dhcp client id15:46
devanandaChuckC: ah, related to port bonding?15:46
ChuckCdevananda: ya, similar concept15:46
devanandaI'm similarly unsure about the client side -- what ever is called by cloud-init, in this case15:47
ChuckCdevananda: that's kind of why I was hoping there was a network boot guru in your ranks15:48
ChuckCdevananda: seems like very specific knowledge/experience is needed15:49
devanandayep. lifeless has dug into that stuff in the past. not sure if he wants to any more :)15:49
*** lazy_prince is now known as killer_prince15:50
devanandaChuckC: if it's a matter of Ironic informing Neutron that "this and that VIF belong to teh same host" -- I don't see, offhand, how the current API would support that15:50
devanandabut IANANE15:51
devananda(i am not a neutron expert)15:51
ChuckCdevananda: the proposal is to add dhcp_client_id to the port resource15:51
ChuckCdevananda: right the current API does not15:52
*** penick has quit IRC15:52
devanandaChuckC: here is where Nova gets the MACs from Ironic, passes them to Neutron: http://git.openstack.org/cgit/openstack/nova/tree/nova/compute/manager.py#n140815:53
*** erwan_taf has quit IRC15:53
JayFadam_g: quick, make it vote :)15:55
*** rushiagr_away is now known as rushiagr15:56
ChuckCdevananda: ok, maybe I'll poke around a bit15:57
ChuckCdevananda: do you think an ML thread might be helpful?15:57
*** pcrews has joined #openstack-ironic15:58
devanandaChuckC: there's a second path whereby ironic also updates those options here -- http://git.openstack.org/cgit/openstack/ironic/tree/ironic/dhcp/neutron.py#n13715:59
devanandaChuckC: yep, definitely15:59
ChuckCdevananda: ok, thanks!15:59
*** david-lyle has joined #openstack-ironic16:03
*** erwan_taf has joined #openstack-ironic16:12
*** krtaylor has joined #openstack-ironic16:17
*** anderbubble has joined #openstack-ironic16:27
*** Haomeng|2 has quit IRC16:28
*** Haomeng|2 has joined #openstack-ironic16:29
*** mjturek has joined #openstack-ironic16:30
*** Viswanath has joined #openstack-ironic16:36
*** achanda has joined #openstack-ironic16:37
*** Viswanath has quit IRC16:39
*** dtantsur is now known as dtantsur|afk16:43
openstackgerritMerged openstack/ironic: Use wsme.Unset as default value for API objects  https://review.openstack.org/13113916:47
*** shakamunyi has quit IRC16:53
*** rloo has quit IRC16:54
*** ifarkas has quit IRC16:54
*** achanda has quit IRC17:00
*** lucasagomes is now known as lucas-brb17:01
*** romcheg has quit IRC17:06
*** marcoemorais has joined #openstack-ironic17:14
openstackgerritVladyslav Drok proposed openstack/ironic: Add put method to API to create or update a node  https://review.openstack.org/13022817:16
*** igordcard has quit IRC17:28
*** igordcard has joined #openstack-ironic17:33
*** igordcard has quit IRC17:36
*** jistr has quit IRC17:38
*** athomas has quit IRC17:39
*** Nisha has joined #openstack-ironic17:47
*** spandhe has joined #openstack-ironic17:51
*** anderbubble has quit IRC17:52
*** shakamunyi has joined #openstack-ironic17:56
*** shakamunyi has quit IRC17:56
*** dprince has joined #openstack-ironic17:57
*** ndipanov is now known as ndipanov_gone17:58
*** derekh has quit IRC17:58
*** shakamunyi has joined #openstack-ironic18:01
*** rloo has joined #openstack-ironic18:03
*** sambetts has quit IRC18:05
openstackgerritNisha Agarwal proposed openstack/ironic-specs: Discover node properties using new CLI node-discover-properties  https://review.openstack.org/10095118:09
*** penick has joined #openstack-ironic18:10
*** andreykurilin_ has joined #openstack-ironic18:13
openstackgerritNisha Agarwal proposed openstack/ironic-specs: Automate UEFI-BIOS Iso Creation  https://review.openstack.org/13402218:15
openstackgerritNisha Agarwal proposed openstack/ironic-specs: Discover node properties using new CLI node-discover-properties  https://review.openstack.org/10095118:27
Shrewslucas-brb: ping18:27
*** pensu has quit IRC18:30
*** subscope has joined #openstack-ironic18:36
*** achanda has joined #openstack-ironic18:47
*** rloo has quit IRC19:03
*** rloo has joined #openstack-ironic19:03
*** pelix has quit IRC19:04
spandheIs there a known issue in Ironic where Ironic never finds out that the node was rebooted?19:06
lucas-brbShrews, pong, sorry the delay19:11
*** lucas-brb is now known as lucasagomes19:11
*** shakamunyi has quit IRC19:12
*** shakamunyi has joined #openstack-ironic19:13
Shrewslucasagomes: no worries. i hadn't considered your TZ either. :)  i left a comment in one of your reviews19:16
lucasagomesShrews, ah ta much for the reviews I will take a look19:17
Shrewslucasagomes: i was wondering about dmitry's comment in your client change19:17
lucasagomesShrews, oh yeah, I will reply there... cause that args_array_to_dict() functions is quite weird19:18
lucasagomesit needs a dict as input19:18
Shrewsyeah. that is a weird func19:18
lucasagomesyou're correct on the comment I'm not passing that fileds dict to the vendor_passthru() method I'm using it because it's required by that method19:18
*** Marga_ has joined #openstack-ironic19:20
*** achanda has quit IRC19:30
*** achanda has joined #openstack-ironic19:31
*** achanda has quit IRC19:34
*** achanda has joined #openstack-ironic19:35
*** zhidong_ has joined #openstack-ironic19:36
*** dlaube has joined #openstack-ironic19:36
*** zhidong has quit IRC19:38
*** lucasagomes is now known as lucas-dinner19:38
*** marcoemorais has quit IRC19:44
*** marcoemorais has joined #openstack-ironic19:44
*** Marga_ has quit IRC19:53
*** igordcard has joined #openstack-ironic19:54
*** achanda has quit IRC19:56
*** foexle has quit IRC19:59
*** subscope has quit IRC20:01
*** rushiagr is now known as rushiagr_away20:01
*** tatyana has joined #openstack-ironic20:02
*** ChuckC has quit IRC20:11
*** jcoufal has quit IRC20:15
*** andreykurilin__ has joined #openstack-ironic20:17
*** andreykurilin_ has quit IRC20:17
rloodevananda, NobodyCam, Shrews, JayF and anyone else: I did a first stab at release notes for Juno. Please contribute, etc. I'm not quite sure what one puts in release notes.20:18
rloooh yeah: https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Juno20:18
Shrewsrloo: LOL at the upgrade notes20:19
*** mjturek has quit IRC20:20
rlooShrews: you noticed! ;)20:20
rlooShrews: makes me wonder if we should have an etherpad to note down upgrade stuff and deprecated stuff. Or is the DocImpact flag supposed to capture all that.20:21
Shrewsrloo: the specs template has a section for that20:24
Shrewsthough i guess that won't cover a bug fix that may impact upgrading20:25
rlooShrews: right, but is someone going to go through all the specs, or bugs? ie, I didn't even want to look at the bugs/specs for Juno.20:25
Shrewsrloo: an operator won't, surely20:25
rlooShrews: so I suspect I won't want to go through the specs/bugs for Kilo. Maybe someone will volunteer ;)20:26
*** andreykurilin_ has joined #openstack-ironic20:26
*** andreykurilin__ has quit IRC20:26
*** krtaylor has quit IRC20:31
*** Marga_ has joined #openstack-ironic20:34
*** Marga_ has quit IRC20:37
*** Marga_ has joined #openstack-ironic20:37
*** ChuckC has joined #openstack-ironic20:38
*** anderbubble has joined #openstack-ironic20:38
*** achanda has joined #openstack-ironic20:39
*** achanda has quit IRC20:39
*** krtaylor has joined #openstack-ironic20:43
mrdaMorning Ironic20:43
*** achanda has joined #openstack-ironic20:43
rloomorning mrda!20:44
ShrewsMorning mrda20:44
mrda\o20:49
openstackgerritNisha Agarwal proposed openstack/ironic-specs: Discover node properties for iLO drivers  https://review.openstack.org/10300720:50
*** tatyana has quit IRC20:51
*** tatyana has joined #openstack-ironic20:51
*** Marga_ has quit IRC20:53
*** Nisha has quit IRC20:53
*** mjturek has joined #openstack-ironic20:55
*** dprince has quit IRC20:56
*** mjturek has quit IRC20:56
openstackgerritJosh Gachnang proposed openstack/ironic-specs: Support Decommissioning of Nodes  https://review.openstack.org/10268520:57
openstackgerritJosh Gachnang proposed openstack/ironic-specs: Support Zapping of Nodes  https://review.openstack.org/10268520:57
JoshNangwhoops, forgot to update the commit message20:57
JoshNang<3 "zapping"20:58
*** Marga_ has joined #openstack-ironic21:10
*** shakamun_ has joined #openstack-ironic21:10
*** shakamunyi has quit IRC21:10
*** killer_prince has quit IRC21:14
*** eglute has joined #openstack-ironic21:16
*** shakamun_ has quit IRC21:26
*** killer_prince has joined #openstack-ironic21:28
*** killer_prince is now known as lazy_prince21:28
*** shakamunyi has joined #openstack-ironic21:30
openstackgerritJosh Gachnang proposed openstack/ironic-specs: Support Zapping of Nodes  https://review.openstack.org/10268521:30
*** achanda has quit IRC21:32
*** Viswanath has joined #openstack-ironic21:36
*** Viswanath has quit IRC21:40
*** Viswanath has joined #openstack-ironic21:41
*** Viswanath has quit IRC21:44
*** anderbubble has quit IRC21:57
*** achanda has joined #openstack-ironic22:00
*** anderbubble has joined #openstack-ironic22:02
*** achanda has quit IRC22:06
*** achanda has joined #openstack-ironic22:14
*** tatyana has quit IRC22:27
openstackgerritLucas Alvares Gomes proposed openstack/ironic: Add sync and async support for passthru methods  https://review.openstack.org/12966222:29
openstackgerritLucas Alvares Gomes proposed openstack/ironic: Make vendor methods discoverable via the Ironic API  https://review.openstack.org/13353322:29
openstackgerritLucas Alvares Gomes proposed openstack/ironic: Vendor endpoints to support different HTTP methods  https://review.openstack.org/12994222:29
*** andreykurilin_ has quit IRC22:34
*** Marga_ has quit IRC22:38
openstackgerritLucas Alvares Gomes proposed openstack/ironic-specs: Adjust the extended-vendor-passthru spec  https://review.openstack.org/13406622:38
openstackgerritLucas Alvares Gomes proposed openstack/ironic-specs: Adjust the extended-vendor-passthru spec  https://review.openstack.org/13406622:40
*** Marga_ has joined #openstack-ironic22:58
*** enterprisedc has joined #openstack-ironic22:59
*** marcoemorais1 has joined #openstack-ironic23:05
*** lucas-dinner has quit IRC23:06
*** marcoemorais has quit IRC23:09
*** david-lyle is now known as david-lyle_afk23:12
*** ChuckC has quit IRC23:16
*** igordcard has quit IRC23:23
*** marcoemorais1 has quit IRC23:30
*** marcoemorais has joined #openstack-ironic23:31
*** anderbubble has quit IRC23:32
*** ryanpetrello has quit IRC23:39
*** ChuckC has joined #openstack-ironic23:40
*** shakamunyi has quit IRC23:58
*** shakamunyi has joined #openstack-ironic23:58

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