Thursday, 2014-11-27

*** alexpilotti has quit IRC00:04
*** alexpilotti has joined #openstack-ironic00:04
*** Masahiro has joined #openstack-ironic00:07
*** Masahiro has quit IRC00:12
NobodyCamanyone know if tripleo elements are aware of devest env vars if they happen to be running in that env00:13
*** spandhe has quit IRC00:15
NobodyCamthe answer is Yes they are :) (Found devtest agent var)00:23
*** zhenzanz has joined #openstack-ironic00:25
HaomengNobodyCam: morning:) yes, devtest will run with these tripleo env vars:)00:29
NobodyCammorning Haomeng :)00:30
HaomengNobodyCam: I have one question also00:30
NobodyCamya I just ran a quick test00:30
NobodyCamsure00:30
HaomengNobodyCam: can we reuse the seed image which built by tripleo?00:30
NobodyCamHaomeng: I do that every day00:30
HaomengNobodyCam: to deploy a seed cloud with vms00:30
HaomengNobodyCam: I think so, but not sure:)00:30
NobodyCamno thats what I do00:31
HaomengNobodyCam: any addition steps to be done, such as to config the ip or control plne00:31
NobodyCamI hack devtest to not deploy a under or overcloud00:31
NobodyCamthen do all my work on the seed00:31
HaomengNobodyCam: so my questions is ,can we run seed.qcwo2 image with another non-tripleo env to run our deploy seed node00:32
HaomengNobodyCam: cloudinit, right?00:32
HaomengNobodyCam: ok, let me have try with seed image00:32
NobodyCamHaomeng: seed is all hardcoded values00:32
HaomengNobodyCam: but not sure why rdo did not release such seed image00:33
HaomengNobodyCam: yes00:33
NobodyCamHaomeng: look at https://github.com/openstack/tripleo-incubator/blob/master/scripts/boot-seed-vm00:33
HaomengNobodyCam: so should we change these hardcoded values for non-tripleo env00:34
HaomengNobodyCam: ok, thanks00:34
HaomengNobodyCam: ok, let me run boot_vm scripts to try, thanks00:34
HaomengNobodyCam: :)00:34
NobodyCamfor values look at https://github.com/openstack/tripleo-image-elements/tree/master/elements/seed-stack-config00:34
HaomengNobodyCam: ok00:35
HaomengNobodyCam: thank you very much:)00:35
NobodyCamHaomeng: I abuse the devtest scripts quite a lot. :)00:36
HaomengNobodyCam: :) cool:)00:36
NobodyCamand I'm loving jq00:37
jroll^^00:40
*** naohirot has joined #openstack-ironic00:42
naohirotgood morning ironic00:42
NobodyCammorning naohirot00:43
naohirotNobodyCam: hi00:43
NobodyCamits T-day for you naohirot no?00:43
naohirotNobodyCam: no, these day, hallowin (is spell correct?) is popular here00:44
Haomengnaohirot: good morning:)00:45
naohirotHaomeng: good morning00:45
NobodyCam:)00:45
*** alexpilotti_ has joined #openstack-ironic00:46
naohirotNobodyCam: Halloween :-)00:46
*** alexpilotti has quit IRC00:47
*** alexpilotti_ is now known as alexpilotti00:47
Haomengnaohirot: :)00:50
* naohirot in meeting00:54
*** Masahiro has joined #openstack-ironic01:02
*** ekarlso- has quit IRC01:12
*** ekarlso- has joined #openstack-ironic01:13
*** davideagnello has quit IRC01:22
*** ryanpetrello has joined #openstack-ironic01:33
*** r-daneel has quit IRC01:47
zer0c00lhttp://paste.fedoraproject.org/154504/17053265/ devstack seem to errorout on01:54
zer0c00lsudo ovs-vsctl add-br brb01:54
zer0c00land list-br01:55
zer0c00lany idea how to fix this?01:55
*** Masahiro has quit IRC01:56
*** achanda has joined #openstack-ironic02:04
*** Masahiro has joined #openstack-ironic02:10
*** nosnos has joined #openstack-ironic02:11
*** ryanpetrello has quit IRC02:12
Haomengzer0c00l: hi02:21
zer0c00lHaomeng:  hi02:22
Haomengdid you see "sudo: no tty present and no askpass program specified"02:24
*** achanda has quit IRC02:28
*** achanda has joined #openstack-ironic02:31
Haomengzer0c00l: how do you launch devstack.sh, by ssh? hope this can help - http://askubuntu.com/questions/461283/no-tty-present-and-no-askpass-program-specified-with-ssh-a02:32
zer0c00lHaomeng:  Solved that by editing sudoers file02:32
zer0c00lThanks02:32
Haomengzer0c00l: welcome02:33
zer0c00lHaomeng: Now i am running into something else02:33
zer0c00lhttp://paste.fedoraproject.org/154518/41705559/02:33
zer0c00lironic port-create fails missing chassis_uuid02:33
Haomengzer0c00l: yes, got your log, but not sure if you are runing with latest code, and if your env is clean02:37
Haomengzer0c00l: chassis_uuid is got via - https://github.com/openstack-dev/devstack/blob/ca7aa301b2825da8e67cf1294ae939676b7d7504/lib/ironic#L50402:38
Haomengzer0c00l: can you try to run - ironic chassis-create -d "ironic test chassis" | grep " uuid " | get_field 2 -  again02:39
*** achanda has quit IRC02:41
*** achanda has joined #openstack-ironic02:43
zer0c00lsure02:45
zer0c00llet me check02:45
*** chenglch has joined #openstack-ironic02:45
Haomengzer0c00l: I think it does not return chassis_uuid02:47
*** ramineni has joined #openstack-ironic02:48
zer0c00lHaomeng: HTTPResponse instance has no attribute 'text'02:52
zer0c00lI get this on my terminal02:52
Haomengzer0c00l: should be your keystone issue02:53
Haomengzer0c00l: can you check if keystone works, and if needed, have to clean and run devstack again02:53
Haomengzer0c00l: good luck02:53
zer0c00lironic chassis-create -d 'ironic test chassis'02:59
zer0c00lresults in 40302:59
Haomengzer0c00l: sometimes, 403 is keystone issue03:00
Haomengzer0c00l: suggest to run unstack.sh, and reboot, and run stack.sh again03:00
zer0c00lokay03:02
*** Masahiro has quit IRC03:06
*** achanda has quit IRC03:11
*** achanda has joined #openstack-ironic03:14
*** achanda has quit IRC03:16
zer0c00lGot it working :D03:16
zer0c00lThanks03:16
*** harlowja_ is now known as harlowja_away03:18
*** rushiagr_away is now known as rushiagr03:28
*** pensu has joined #openstack-ironic03:34
*** naohirot has quit IRC03:35
*** Masahiro has joined #openstack-ironic03:54
*** alexpilotti has quit IRC03:56
*** pcrews has quit IRC04:00
*** naohirot has joined #openstack-ironic04:00
*** nosnos has quit IRC04:00
*** datajerk has quit IRC04:02
*** dlaube has quit IRC04:09
*** rushiagr is now known as rushiagr_away04:15
*** Masahiro has quit IRC04:41
*** Masahiro has joined #openstack-ironic04:45
*** nosnos has joined #openstack-ironic04:49
*** yuanying has joined #openstack-ironic04:59
*** yuanying has quit IRC05:02
*** yuanying_ has quit IRC05:02
*** rushiagr_away is now known as rushiagr05:06
*** yuanying has joined #openstack-ironic05:06
*** dlaube has joined #openstack-ironic05:07
*** dlaube has quit IRC05:09
*** Marga_ has quit IRC05:14
*** Masahiro has quit IRC05:22
*** killer_prince is now known as lazy_prince05:28
*** pradipta_away is now known as pradipta05:30
*** Masahiro has joined #openstack-ironic05:32
*** ryanpetrello has joined #openstack-ironic05:45
*** smoriya has joined #openstack-ironic05:51
*** vipul has quit IRC06:02
*** Masahiro has quit IRC06:04
*** vipul has joined #openstack-ironic06:04
*** Masahiro has joined #openstack-ironic06:08
*** ryanpetrello has quit IRC06:11
openstackgerritTan Lin proposed openstack/ironic: Add task_manager lock to Drac power driver  https://review.openstack.org/13752606:16
*** rakesh_hs has joined #openstack-ironic06:24
*** k4n0 has joined #openstack-ironic06:26
openstackgerritNaohiro Tamura proposed openstack/ironic-specs: iRMC Power Driver for Ironic  https://review.openstack.org/13448706:32
*** Nisha has joined #openstack-ironic06:38
*** ekarlso- has quit IRC06:54
*** ekarlso- has joined #openstack-ironic06:54
*** amitpp has joined #openstack-ironic07:02
*** rakesh_hs2 has joined #openstack-ironic07:02
*** rakesh_hs has quit IRC07:02
GheRiveromorning all07:15
*** Masahiro has quit IRC07:16
*** Masahiro has joined #openstack-ironic07:19
*** vinbs has joined #openstack-ironic07:30
openstackgerritHarshada Mangesh Kakad proposed openstack/ironic: Add documentation for SeaMicro driver  https://review.openstack.org/13632407:32
*** mrda is now known as mrda-away07:44
*** athomas has joined #openstack-ironic08:02
*** lucasagomes has joined #openstack-ironic08:03
*** lucasagomes has quit IRC08:03
*** lucasagomes has joined #openstack-ironic08:04
*** ifarkas_ has joined #openstack-ironic08:04
*** dtantsur|afk is now known as dtantsur08:06
dtantsurMorning08:06
openstackgerritDmitry Tantsur proposed openstack/ironic-specs: Introduce driver capabilities  https://review.openstack.org/12892708:08
*** yuriyz has quit IRC08:12
*** dlpartain has joined #openstack-ironic08:16
*** yuriyz has joined #openstack-ironic08:19
*** erwan_taf has joined #openstack-ironic08:23
*** amitpp has quit IRC08:29
*** Masahiro has quit IRC08:30
openstackgerritTan Lin proposed openstack/ironic: Add decorator that requires a lock for Drac power driver  https://review.openstack.org/13752608:30
*** romcheg has joined #openstack-ironic08:31
openstackgerritGhe Rivero proposed openstack/ironic: Use olso.config generator  https://review.openstack.org/13744708:31
*** aswadr has joined #openstack-ironic08:32
*** Masahiro has joined #openstack-ironic08:33
*** romcheg has quit IRC08:35
openstackgerritDmitry Tantsur proposed openstack/ironic-specs: Introduce driver capabilities  https://review.openstack.org/12892708:35
*** viktors|afk has quit IRC08:40
*** andreykurilin_ has joined #openstack-ironic08:47
openstackgerritMerged openstack/ironic-specs: Support for non-Glance image references  https://review.openstack.org/13527608:48
*** viktors has joined #openstack-ironic08:48
*** nosnos has quit IRC08:49
openstackgerritHarshada Mangesh Kakad proposed openstack/ironic: Add documentation for SeaMicro driver  https://review.openstack.org/13632408:50
*** pradipta is now known as pradipta_away08:50
openstackgerritHarshada Mangesh Kakad proposed openstack/ironic: Add documentation for SeaMicro driver  https://review.openstack.org/13632408:53
*** romcheg has joined #openstack-ironic08:55
*** zhenzanz has quit IRC08:58
*** jcoufal has joined #openstack-ironic09:00
openstackgerritjiangfei proposed openstack/ironic: modify for ipa conf variables  https://review.openstack.org/13755009:01
*** andreykurilin_ has quit IRC09:02
*** andreykurilin__ has joined #openstack-ironic09:02
*** foexle has joined #openstack-ironic09:07
*** smoriya has quit IRC09:07
*** jistr has joined #openstack-ironic09:10
*** Masahiro has quit IRC09:16
*** lintan has joined #openstack-ironic09:16
lintanNaohiro Tamura?09:19
naohirotlintan: Hi09:21
*** Masahiro has joined #openstack-ironic09:21
naohirotlintan: have you join to IRC some time ago?09:22
naohirotlintan: I was just waiting for you.09:22
lintannaohirot: it's my first time to join Ironic IRC09:23
naohirotlintan: I also started to use IRC after I joined to the community :-)09:24
lintannaohirot: sorry for wait09:24
naohirotlintan: no problem :-)09:24
naohirotlintan: so what kind of settings does AMT have in the config file?09:26
lintannaohirot:  port and http09:27
lintannaohirot: http always use port 16992 and https always use port 1699309:27
naohirotlintan: Okay09:28
lintannaohirot: I am not sure should I put these two into driver_info09:28
lintannaohirot:what do you think in your case?09:29
naohirotlintan: "Servers in one cloud should be consistent, right? I am thinking to have the same auth_method and even same port? The only different is the address and password. I am not admin, just some thought."09:29
naohirotlintan: here is your comment in the gerrit.09:29
lintannaohirot:yes09:30
naohirotlintan: In case of ATM, can deployer choose authentication method?09:30
*** teju has joined #openstack-ironic09:31
naohirotlintan: what I didn't fully understand is that "consistency" between what? between drivers?09:32
naohirotlintan: I think making consist is good, I have no objection.09:33
lintannaohirot:consistent means if you try to your AMT Nodes, you should use http for all or use https for all09:33
*** BertieFulton has joined #openstack-ironic09:34
lintannaohirot:AMT support Digest and Kerberos authentication09:34
naohirotlintan: Okay,09:34
dtantsurrestating what I already said on the review, I'm also not convinced we should have per-node authentication method09:34
naohirotlintan: let's say, there are 4 nodes, ATM node, HP node, DELL node, Fujitsu node.09:35
naohirotlintan: are you saying that all four kind of nodes should share the same authentication method?09:36
lintannaohirot:NO,no,no I mean in the same types nodes09:37
naohirotlintan: same types, could you give some example?09:37
lintannaohirot:We can set specific config for each driver09:37
dtantsurnaohirot, you could _optionally_ allow node-specific auth method (though I don't see the reason), but there should be a common one in a configuration09:37
naohirotdtantsur: hi09:38
dtantsurnaohirot, g'afternoon :)09:38
*** nosnos has joined #openstack-ironic09:39
lintannaohirot:you can check /etc/ironic/ironic.conf, there is section for ilo driver09:39
lintannaohirot:all ilo ports will use 443 as client_port09:39
naohirotlintan: I still didn't understand what are the same type, could you give me example which shows different type?09:39
lintannaohirot: and we can have sections for Fujitsu node and ATM node as well09:40
* naohirot just moment09:40
naohirotlintan: I'm looking at root/ironic/etc/ironic/ironic.conf.sample09:41
lintannaohirot: it's the same09:42
naohirotlintan: Yes, I'm looking at [ilo] section09:43
* naohirot thinking09:44
*** andreykurilin__ has quit IRC09:45
*** derekh has joined #openstack-ironic09:46
naohirotlintan: let me check if I could understand the point.09:46
naohirotlintan: we should "auth_method" in default section, then each driver overwrite the default if necessary.09:47
naohirotlintan: Am I correct?09:47
naohirotlintan: Regarding "the same types nodes", is that a case, for example, there are 4 DELL nodes.09:50
lintannaohirot: Yes, this what I mean09:51
naohirotlintan: among the 4 DELL nodes, the settings have to be the same. We shouldn't allow deployer to set different settings to each individual Dell Node.09:52
lintannaohirot: exactly, if you really want to set different setting to each node, you can add the option in the driver_info09:54
naohirotlintan: Okay, node_info and node are one-to-one relation.09:54
naohirotlintan: But [amt] section in config file and nodes are one to many.09:54
*** chenglch has quit IRC09:55
naohirotlintan: Now I got. I'll move the auth_method into the config file.09:55
lintannaohirot: yes09:55
lintannaohirot: that's my point09:56
naohirotlintan: s/node_info/driver_info/09:56
naohirotlintan: thank you very much :-)09:56
lintannaohirot: :)09:56
naohirotlintan: my network disconnect soon, and leave for dinner, see you later!09:57
lintannaohirot: see you09:58
openstackgerritYuriy Zveryanskyy proposed openstack/ironic: Change some exceptions from invalid to missing  https://review.openstack.org/13712409:59
openstackgerritRamakrishnan G proposed openstack/ironic-specs: iLO virtual media drivers to deploy without DHCP  https://review.openstack.org/13756710:03
Nishadtantsur: hi10:08
*** rameshg87 has joined #openstack-ironic10:13
*** Masahiro has quit IRC10:13
erwan_tafyo10:13
*** yuanying_ has joined #openstack-ironic10:14
rameshg87ifarkas_, hi10:15
*** yuanying has quit IRC10:16
*** Masahiro_ has joined #openstack-ironic10:20
*** Masahiro_ has quit IRC10:22
*** naohirot has quit IRC10:24
*** sambetts has joined #openstack-ironic10:29
*** Masahiro has joined #openstack-ironic10:32
*** dlpartain has quit IRC10:34
*** Masahiro has quit IRC10:34
*** Masahiro has joined #openstack-ironic10:37
ifarkas_rameshg87, hi10:38
ifarkas_rameshg87, have you checked the raid spec?10:38
rameshg87ifarkas_, i just checked now10:38
rameshg87ifarkas_, i had some questions10:39
rameshg87ifarkas_, first regarding the physical disks information in 'target_raid_configuration'10:40
*** Nisha has quit IRC10:40
rameshg87ifarkas_, do we need to provide physical disks information ? can't the driver find this by itself ?10:40
rameshg87ifarkas_, the operator has to goto each machine to find out the physical disks10:41
ifarkas_rameshg87, the operator need to decide which physical disk goes to which raid array. eg you have a raid array of ssds and a raid array of hdds10:41
ifarkas_rameshg87, the operator can use node introspection10:42
ifarkas_rameshg87, the introspection will stash the information on node.properties or something and it can be used to define the raid arrays10:42
rameshg87ifarkas_, yeah then can't the input be just the type of disks to be used for raid configuration10:42
*** pelix has joined #openstack-ironic10:43
rameshg87ifarkas_, the problem with giving actual disk is the operator has to go and work on each bare metal node. it becomes a problem when there are many bare metal nodes10:43
openstackgerritGhe Rivero proposed openstack/ironic: Use olso.config generator  https://review.openstack.org/13744710:45
rameshg87ifarkas_, i would like to avoid providing "machine-specific" things in target_raid_configuration field10:45
ifarkas_rameshg87, I don't think you can avoid it, think about the scenario I gave before10:46
rameshg87ifarkas_, so can we make it optional then ?10:49
rameshg87ifarkas_, if the operator doesn't provide that info, then its upto driver to figure out which raid controller and which disks to use depending on the information available10:51
rameshg87ifarkas_, my use case is like this - if i am an operator who has a uniform type of 30 machines, i just want to specify the number of disks and raid levels that i want10:51
ifarkas_rameshg87, that might work. what would the driver do if it find a bunch of disks?10:52
rameshg87ifarkas_, what do you mean my bunch of disks ?10:52
ifarkas_rameshg87, like 2 hdds and 6 ssds10:53
rameshg87ifarkas_, can we ever mix hdds and ssds into a single logical driver ?10:53
rameshg87ifarkas_, i think that's not possible10:53
rameshg87ifarkas_, s/logical driver/logical drive10:54
rameshg87ifarkas_, if we mention a preferred disk_type we could select that10:55
ifarkas_rameshg87, yeah, I don't think that's possible. My question is what would the driver do with these machines if the operator is not required to define that they want eg 3 separate raid arrays?10:55
rameshg87ifarkas_, i guess i still didn't your question :)10:55
rameshg87ifarkas_, is your question like "what would driver do if operator just says only this much - 'i want a logical disk of 50gb and raid 1'" ? is that the question ?10:56
ifarkas_rameshg87, ahh, so you require at least to define the size and raid level, right?10:58
*** Masahiro has quit IRC10:58
rameshg87ifarkas_, yes10:58
dtantsurlucasagomes, https://blueprints.launchpad.net/ironic-discoverd/+spec/plugin-architecture10:58
ifarkas_rameshg87, then how the driver would select which physical disks would be used out of the 8?10:58
rameshg87ifarkas_, if the input is only "i want a logical disk of 50gb and raid 1" - driver would examine the raid controllers and the disks, select a raid controller which has physical disks whose storage space adds upto 50gb, then select physical disks  until 50gb is available and then create a logical disk11:00
*** MattMan has quit IRC11:00
*** Haomeng|2 has joined #openstack-ironic11:00
*** MattMan has joined #openstack-ironic11:01
*** Haomeng has quit IRC11:02
ifarkas_rameshg87, the problem with this approach is that there is chance that the raid arrays will be built by hdds instead of ssds. or maybe the driver will mix the type which will cause failure11:02
rameshg87ifarkas_, couldn't we programatically make sure that driver picks up the same type of disks ?11:03
ifarkas_rameshg87, yeah but how the driver will decide if the operator want to build a raid array ouf of hdds or ssds?11:03
rameshg87ifarkas_, and if the operator has a preference in type of disk, we could even add "disk_type=ssd" to the logical disk input which will cause the driver to pick only ssd11:04
dtantsurifarkas_, could you review https://review.openstack.org/137595 ? It's pretty urgent, I think I screwed the sqlite patch :(11:04
ifarkas_dtantsur, sure11:04
rameshg87ifarkas_, if it can't find enough ssds, it could throw an error11:04
*** ramineni has quit IRC11:05
ifarkas_rameshg87, what happens if there isn't any ssd, just hdds?11:05
ifarkas_rameshg87, my problem is that I don't see how the driver should select the physical disks11:05
ifarkas_rameshg87, there's a lot of questions there11:06
rameshg87ifarkas_, let me put it this way11:06
*** igordcard has joined #openstack-ironic11:06
rameshg87ifarkas_, operator says "i want 2 logical disks of (50gb, raid1), (100gb, raid5) on all my 30 machines"11:07
rameshg87ifarkas_, no preference in disk types11:07
rameshg87ifarkas_, during zapping of each bare metal node, driver could examine raid controllers and disks within them on each bare metal11:08
rameshg87ifarkas_, it checks if it can make 50gb in a raid controller with a same disk type11:08
rameshg87ifarkas_, i mean it checks if it can make a 50gb logical disk with all disks of same type11:09
rameshg87ifarkas_, assuming we can programmatically determine the type of disks within a raid controller11:10
rameshg87ifarkas_, does it sound good till now ?11:10
ifarkas_rameshg87, ok11:10
rameshg87ifarkas_, next scenario11:10
ifarkas_rameshg87, could you add a paragraph to the spec to gather feedback on that?11:10
rameshg87ifarkas_, okay11:10
rameshg87ifarkas_, operator says "i want 2 logical disks of (50gb, raid1, ssd), (100gb, raid5, hdd) on all my 30 machines"11:11
rameshg87ifarkas_, it checks if it can make 50gb in a raid controller with ssds11:12
rameshg87ifarkas_, if it can't it throws an error and puts node in maintanence11:12
rameshg87ifarkas_, similarly for hdds11:12
ifarkas_rameshg87, yeah11:12
ifarkas_rameshg87, okay, it makes sense to me this way11:12
rameshg87ifarkas_, okay. just wanted to make sure both use cases are covered.11:13
ifarkas_rameshg87, right11:13
rameshg87ifarkas_, both for operators who have uniform hardware and don't want to go in each machine11:13
rameshg87ifarkas_, and for operators who are choosy and want to provide configuration themselves11:13
ifarkas_rameshg87, the operator don't have to go to every machine, since it can be automated, but I see your point11:15
rameshg87ifarkas_, okay.11:15
rameshg87ifarkas_, so how you want to proceed ?11:15
rameshg87ifarkas_, shall i post a new patch on the review with the things discussed so far ?11:15
ifarkas_rameshg87, could you add a paragraph to the spec describing it?11:15
ifarkas_rameshg87, yeah11:15
rameshg87ifarkas_, okay will do it today itself11:16
ifarkas_rameshg87, I mean just a new revision11:16
rameshg87ifarkas_, yeah, a new patch set :)11:16
ifarkas_rameshg87, right ;-)11:16
rameshg87ifarkas_, great. will discuss after posting the patch.11:17
rameshg87ifarkas_, thanks11:17
ifarkas_rameshg87, thank you11:17
*** rameshg87 has quit IRC11:17
*** erwan_taf has quit IRC11:30
*** pensu has quit IRC11:34
*** vinbs has quit IRC11:36
*** teju has left #openstack-ironic11:46
*** naohirot has joined #openstack-ironic11:46
openstackgerritGhe Rivero proposed openstack/ironic: Use olso.config generator  https://review.openstack.org/13744711:50
*** ryanpetrello has joined #openstack-ironic11:54
*** pensu has joined #openstack-ironic11:59
*** alexpilotti has joined #openstack-ironic12:01
*** ryanpetrello has quit IRC12:06
naohirotdtantsur: Hi, I read your comment. can I clarify little bit?12:08
naohirotdtantsur: Is it okay that some parameter appears in both device_info and config?12:10
*** aswadr has quit IRC12:10
naohirotdtantsur: for example port number.12:11
*** Masahiro has joined #openstack-ironic12:12
naohirotdtantsur: anyway I follows the way iLO does.12:13
*** Masahiro has quit IRC12:15
*** Masahiro has joined #openstack-ironic12:16
naohirotdtantsur: it seems iLO doesn't allow to change port number for each individual node according to root/ironic/ironic/drivers/modules/ilo/deploy.py12:18
*** Masahiro has quit IRC12:18
naohirotdtantsur: no I'm not right, iLO allow to change port number for individual node according to root/ironic/ironic/drivers/modules/ilo/common.py.12:23
*** erwan_taf has joined #openstack-ironic12:24
naohirotdtantsur: so I change my spec so as to be the same as iLO.12:25
*** Masahiro has joined #openstack-ironic12:25
*** k4n0 has quit IRC12:26
dtantsurnaohirot, it's completely ok to have the default value in the configuration and (optional) overriding value in node12:27
*** rameshg87 has joined #openstack-ironic12:28
*** Masahiro has quit IRC12:29
naohirotdtantsur: Okay, so I revive the "client_timeout" in driver_info, and add irmc_port and auth_method into config file.12:31
dtantsurnaohirot, I see no point in bringing client_timeout in driver_info, why would you do it?12:32
naohirotdtantsur: in case of iLO, it allows to overwrite client timeout for individual node.12:33
dtantsurnaohirot, I see no point in it as well :)12:33
* naohirot I'm going to paste URL here12:33
*** pelix has quit IRC12:34
*** pelix has joined #openstack-ironic12:35
naohirotdtantsur: https://github.com/openstack/ironic/blob/master/ironic/drivers/modules/ilo/common.py12:35
naohirotdtantsur: Line 15312:35
dtantsurnaohirot, I believe you. But the fact that ilo did it does not automatically justify any more use cases. rameshg87 any idea why it was done ^^?12:36
naohirotdtantsur: you are right, iLO does not always implement correctly :-)12:38
rameshg87dtantsur naohirot, yes there is actually no point in timeout.12:39
rameshg87dtantsur, naohirot, mainly because i now see proliantutils module doesn't seem to use it https://github.com/hpproliant/proliantutils/blob/master/proliantutils/ilo/ribcl.py :(12:39
naohirotrameshg87: Hi, Okay I exclude client time out from driver_info.12:39
rameshg87dtantsur, naohirot, the point i remember was to make it work with slow iLO's if i remember correctly12:40
naohirotrameshg87: dtantsur: thanks, now everything became clear to me.12:42
dtantsuryou're welcome :)12:42
rameshg87dtantsur, i had a question for you12:43
dtantsursure12:43
rameshg87dtantsur, in in-band discovery12:43
dtantsurouch :)12:43
rameshg87dtantsur, https://review.openstack.org/#/c/122151/5 - will we have a separate ramdisk for discovery ?12:44
rameshg87dtantsur, built *only* for discovery ?12:44
dtantsurrameshg87, for now - yes. I hope to base all ramdisks on IPA in the near future12:44
rameshg87dtantsur, yeah, exactly my question was the same12:44
rameshg87dtantsur, why don't we move this to ipa now itself ? :)12:45
rameshg87dtantsur, to avoid operator to deal with multiple ramdisks12:45
dtantsurrameshg87, it needs DIB support and we have to make sure it can be built on RHEL12:45
rameshg87dtantsur, diskimage-builder has ironic-agent element which can be made to be built over rhe12:46
rameshg87dtantsur, currently it has been tested with fedora it seems https://github.com/openstack/diskimage-builder/tree/master/elements/ironic-agent12:46
rameshg87dtantsur, i don't think it will be much of an effort to make ironic-agent to built over rhel :)12:46
dtantsuroh it's merged!12:46
dtantsurI didn't know :)12:47
rameshg87dtantsur, yeah :)12:47
dtantsurok, I will start investigating it ASAP, thanks for update12:47
rameshg87dtantsur, great :)12:47
rameshg87dtantsur, ultimately only 1 ramdisk = relief for operator :)12:47
dtantsuryeah, that's where we're going12:48
*** rakesh_hs2 has quit IRC12:50
*** zhenzanz has joined #openstack-ironic12:51
*** nosnos has quit IRC13:01
openstackgerritNaohiro Tamura proposed openstack/ironic-specs: iRMC Power Driver for Ironic  https://review.openstack.org/13448713:08
*** bradjones has quit IRC13:10
*** bradjones has joined #openstack-ironic13:10
*** bradjones has quit IRC13:10
*** bradjones has joined #openstack-ironic13:10
rameshg87lucasagomes, hi13:13
*** leopoldj has joined #openstack-ironic13:20
*** pensu has quit IRC13:24
openstackgerritRamakrishnan G proposed openstack/ironic-specs: New driver interface for RAID configuration  https://review.openstack.org/13589914:05
*** rloo has joined #openstack-ironic14:06
rameshg87ifarkas_, ^^^14:06
ifarkas_rameshg87, thanks!14:06
*** Masahiro has joined #openstack-ironic14:06
*** Masahiro has quit IRC14:11
ifarkas_rameshg87, wow, I just saw you changed a bunch of stuff, not just added a paragraph14:17
ifarkas_rameshg87, was there any issue with the api endpoint urls that required you to change it?14:18
rameshg87ifarkas_, sorry, i wanted to discuss that .. but thought of putting it anyway and checking14:21
rameshg87ifarkas_, /nodes/<uuid>/raid/configuration/apply => /nodes/<uuid>/raid/apply_configuration14:21
rameshg87ifarkas_, i was wondering why would we need 'configuration' as an intermediate resource14:22
rameshg87ifarkas_, is there any reason for that ? is there something else we can do with raid other 'configuration' ? :)14:22
ifarkas_rameshg87, not yet, but maybe in the future we will support more features14:23
dtantsurrameshg87, I also think you don't need `apply` :) PUT already assumes apply for example14:24
dtantsurrameshg87, so it should be PUT /nodes/<uuid>/raid/configuration IMO14:24
rameshg87dtantsur, so you are suggesting only one endpoint ?14:25
dtantsur(i.e. in RESTful and RESTish API interfaces URL parts should be nouns, not verbs)14:25
dtantsurlemme have one more look14:25
ifarkas_rameshg87, I have also seen you changed node.properties to node.extras14:25
ifarkas_rameshg87, could we please discuss the changes to spec before overwriting it?14:26
rameshg87ifarkas_, yeah so shall we take it one by one ..14:26
dtantsurrameshg87, POST /nodes/<uuid>/raid/configuration, DELETE /nodes/<uuid>/raid/configuration, POST /nodes/<uuid>/raid/configuration/verify, smth like this14:26
dtantsur(verify is a verb, but here it can't be helped as far as I see)14:27
rameshg87dtantsur, yeah seems better to me actually14:27
rameshg87ifarkas_, what do you think ? ^^14:27
ifarkas_rameshg87, ack14:27
rameshg87dtantsur, ifarkas_, so can't we just avoid verify and let POST /nodes/<uuid>/raid/configuration do it14:28
rameshg87dtantsur, ifarkas_, POST /nodes/<uuid>/raid/configuration can verify if configuration is intact and could re-create if it isn't14:28
rameshg87dtantsur, ifarkas_, what do you think ?14:29
dtantsurrameshg87, oh btw s/node.extra.target_raid_configuration/node.properties.target_raid_configuration/14:29
dtantsurrameshg87, extra is not for Ironic internal use14:30
rameshg87dtantsur, oh14:30
rameshg87dtantsur, yeah but shall we take that next after freezing on endpoint stuff :)14:30
dtantsurrameshg87, well  POST /nodes/<uuid>/raid/configuration (or even PUT if this an idempotent operation) works for me14:30
rameshg87ifarkas_, what's your opinion on that - only 2 endpoints as of now - POST /nodes/<uuid>/raid/configuration and DELETE /nodes/<uuid>/raid/configuration ?14:31
ifarkas_rameshg87, yeah, good idea14:32
rameshg87ifarkas_, okay i will change this14:32
rameshg87ifarkas_, dtantsur, next was properties => extra14:32
rameshg87ifarkas_, dtantsur, the reason i was not preferring properties as 'properties' seemed scheduling information14:33
rameshg87ifarkas_, dtantsur, and target_raid_configuration as it is, IS NOT scheduling information14:33
dtantsurrameshg87, then driver_info, I guess. extra is not for Ironic to touch :)14:33
rameshg87ifarkas_, dtantsur, nova will never be interested in full information in  target_raid_configuration14:34
ifarkas_rameshg87, btw, the spec can't be built, tox fails14:34
rameshg87dtantsur, yeah driver_info works for me too14:34
rameshg87ifarkas_, what's your thought ?14:34
rameshg87ifarkas_, oh may be i screwed it up. will fix the issue.14:35
*** rushiagr has quit IRC14:35
ifarkas_rameshg87, I don't think this belongs to driver_info but maybe we can try14:41
rameshg87ifarkas_, where do you feel it belongs ?14:41
ifarkas_rameshg87, properties :-)14:41
rameshg87ifarkas_, :)14:42
rameshg87ifarkas_, what i felt was ironic could update the properties after raid configuration is done with what is relevant14:42
ifarkas_rameshg87, yeah, it's capabilities field14:43
rameshg87ifarkas_, target_raid_configuration was actually an input to Ironic, not a *property* of the bare metal :)14:43
rameshg87ifarkas_, or we could propose something for storing information of zapping tasks. i am sure there will be more such information to be stored :)14:45
rameshg87ifarkas_, zap_info :)14:46
ifarkas_rameshg87, yeah, me neither. I would suggest to wait for more feedback14:46
rameshg87ifarkas_, okay, i will just revert it back to properties for now14:46
rameshg87ifarkas_, let's wait until we have a better one14:47
rameshg87ifarkas_, the other change is moved a sentense from problem description to proposed change (which i felt was actually a change that is proposed)14:47
rameshg87ifarkas_, then i added whatever we discussed. since target_raid_configuration itself was a bigger thing in the context, i moved it to a separate bullet item, and just put both our use-cases14:48
rameshg87ifarkas_, do you feel okay with both the above ?14:49
rameshg87ifarkas_, oh and a slight change in your proposed use-case to push 'controller' information inside virtual_disks to be compatible with mine14:50
rameshg87ifarkas_, okay, i will be back in some-time14:56
rameshg87ifarkas_, feel free to comment in the spec or post a new spec with what-ever-we-discussed + your-thoughts14:56
rameshg87ifarkas_, we will discuss again14:56
*** rameshg87 is now known as rameshg87-away14:57
*** zhenzanz has quit IRC15:03
*** foexle has quit IRC15:03
*** rushiagr_away has joined #openstack-ironic15:04
ifarkas_rameshg87-away, yeah, I actually wanted to change the controller thing as well15:05
ifarkas_rameshg87-away, maybe we no longer need the hash, the list of raid arrays should be enough15:06
*** zhenzanz has joined #openstack-ironic15:07
*** r-daneel has joined #openstack-ironic15:10
*** rushiagr_away is now known as rushiagr15:11
*** naohirot has quit IRC15:16
*** BertieFulton has quit IRC15:18
*** rameshg87-away is now known as rameshg8715:18
rameshg87ifarkas_, okay. anything more to discuss on the current spec then ?15:19
rameshg87ifarkas_, if not, i will make the changes as we discussed and post a new patch15:19
ifarkas_rameshg87, I have nothing more on my mind15:19
rameshg87ifarkas_, okay. let me make the changes then15:20
*** achanda has joined #openstack-ironic15:22
*** lazy_prince is now known as killer_prince15:27
*** achanda has quit IRC15:27
rameshg87ifarkas_, just one more thing if you have some time15:27
rameshg87ifarkas_, just came to my mind15:28
ifarkas_rameshg87, sure15:32
rameshg87ifarkas_, we have 2 methods of doing raid configuration15:32
rameshg87ifarkas_, as part of zapping OR as part of a manual REST API call15:33
rameshg87ifarkas_, shouldn't the manual REST API call recieve the raid configuration information from the REST call itself15:33
rameshg87ifarkas_, i mean as part of data in http POST15:33
ifarkas_rameshg87, in that case, how the user would run verify?15:36
rameshg87ifarkas_, the POST call (which inturn will do the verify first) would have raid configuration information data15:37
rameshg87ifarkas_, just instead of the current way of picking up information from node.properties, it would pick up from http data15:37
rameshg87ifarkas_, but it might be worth storing for reference15:38
rameshg87ifarkas_, hmm, i will keep it as we discussed for now15:38
ifarkas_rameshg87, yeah, I agree. Mostly because previously discussed there will be only POST and DELETE15:39
rameshg87ifarkas_, yeah15:39
dtantsurjroll, seen https://review.openstack.org/#/c/137550/ ?15:41
NobodyCamhappy t-day you all!15:42
openstackgerritRamakrishnan G proposed openstack/ironic-specs: New driver interface for RAID configuration  https://review.openstack.org/13589915:45
rameshg87ifarkas_, ^^15:46
*** ParsectiX has joined #openstack-ironic15:49
*** Masahiro has joined #openstack-ironic15:55
*** ndipanov has quit IRC15:58
rameshg87all, i have a general question15:59
rameshg87is there a way of safely restarting an ironic conductor - i mean making sure that restart after conductor is completely idle15:59
*** davideagnello has joined #openstack-ironic16:00
rameshg87usecase is - i have done a config change, i need to restart ironic conductor. but i don't want to disturb any currently running activities16:00
*** Masahiro has quit IRC16:00
*** ndipanov has joined #openstack-ironic16:01
*** dlaube has joined #openstack-ironic16:04
dtantsurNobodyCam, hi! :)16:05
NobodyCammorning dtantsur :)16:07
NobodyCamrameshg87: background task are always running on the conductors16:08
NobodyCamso the idle is questionable16:09
rameshg87NobodyCam, but just now i accidently stopped the node when it was deleting16:12
rameshg87NobodyCam, and i had to go and update the db16:12
rameshg87NobodyCam, because i couldn't change the provision_state otherwise16:12
rameshg87NobodyCam, is there anyway to avoid this ?16:13
rameshg87NobodyCam, a safer way of scheduling conductor restarts :)16:13
*** davideagnello has quit IRC16:20
NobodyCamhumm16:21
NobodyCamother then checking the state before restarting16:21
*** erwan_taf has quit IRC16:24
*** romcheg has quit IRC16:38
*** romcheg has joined #openstack-ironic16:38
*** romcheg has quit IRC16:38
*** ndipanov has quit IRC16:41
openstackgerritMerged openstack/ironic: Add decorator that requires a lock for Drac power driver  https://review.openstack.org/13752616:41
openstackgerritHarshada Mangesh Kakad proposed openstack/ironic: Add documentation for SeaMicro driver  https://review.openstack.org/13632416:52
*** jcoufal has quit IRC16:52
*** ndipanov has joined #openstack-ironic16:53
*** ParsectiX has quit IRC16:55
*** viktors is now known as viktors|afk16:55
*** ParsectiX has joined #openstack-ironic16:56
*** romcheg has joined #openstack-ironic16:56
*** rameshg87 has quit IRC16:58
*** sambetts has quit IRC16:59
*** athomas has quit IRC17:05
*** dtantsur is now known as dtantsur|afk17:06
*** zhenzanz has quit IRC17:07
*** lucasagomes has quit IRC17:09
*** rushiagr is now known as rushiagr_away17:11
*** ifarkas_ has quit IRC17:11
*** ParsectiX has quit IRC17:12
*** ParsectiX has joined #openstack-ironic17:12
*** pensu has joined #openstack-ironic17:13
*** Nisha has joined #openstack-ironic17:22
*** derekh has quit IRC17:24
*** ndipanov is now known as ndipanov_gone17:29
*** Masahiro has joined #openstack-ironic17:44
*** Masahiro has quit IRC17:48
*** jistr has quit IRC17:50
*** rushiagr_away is now known as rushiagr18:02
*** achanda has joined #openstack-ironic18:04
*** davideagnello has joined #openstack-ironic18:08
*** foexle has joined #openstack-ironic18:11
*** davideagnello has quit IRC18:13
*** pcrews has joined #openstack-ironic18:17
*** romcheg has quit IRC18:19
*** achanda has quit IRC18:28
*** MattMan has quit IRC18:32
*** romcheg has joined #openstack-ironic18:35
*** leopoldj has quit IRC18:39
*** pensu has quit IRC18:41
*** foexle has quit IRC18:46
*** rushiagr is now known as rushiagr_away18:48
*** pcrews has quit IRC18:49
*** rushiagr_away is now known as rushiagr18:56
*** Parsecti_ has joined #openstack-ironic18:56
*** ParsectiX has quit IRC18:57
*** pelix has quit IRC19:06
*** pcrews has joined #openstack-ironic19:11
*** Parsecti_ has quit IRC19:25
*** pcrews has quit IRC19:27
*** pcrews has joined #openstack-ironic19:31
*** romcheg1 has joined #openstack-ironic19:31
*** Masahiro has joined #openstack-ironic19:33
*** Masahiro has quit IRC19:37
*** achanda has joined #openstack-ironic19:38
*** achanda has quit IRC19:43
*** dlaube has quit IRC20:05
*** igordcard has quit IRC20:12
*** romcheg1 has quit IRC20:13
*** mrda-away is now known as mrda20:39
mrdaMorning Ironic20:39
*** igordcard has joined #openstack-ironic21:00
*** andreykurilin_ has joined #openstack-ironic21:03
*** davideagnello has joined #openstack-ironic21:12
*** igordcard has quit IRC21:20
*** Masahiro has joined #openstack-ironic21:21
*** Marga_ has joined #openstack-ironic21:22
*** davideagnello has quit IRC21:23
*** Masahiro has quit IRC21:26
*** igordcard has joined #openstack-ironic21:34
openstackgerritOpenStack Proposal Bot proposed openstack/ironic-python-agent: Updated from global requirements  https://review.openstack.org/13596421:42
*** Marga_ has quit IRC21:44
*** Marga_ has joined #openstack-ironic21:44
*** Marga_ has quit IRC21:51
*** davideagnello has joined #openstack-ironic22:28
*** davideagnello has quit IRC22:40
*** davideagnello has joined #openstack-ironic22:40
*** Nisha has quit IRC22:49
*** romcheg1 has joined #openstack-ironic22:52
*** andreykurilin_ has quit IRC23:04
*** Masahiro has joined #openstack-ironic23:10
*** Masahiro has quit IRC23:15
*** pcrews has quit IRC23:16
*** Haomeng has joined #openstack-ironic23:36
*** Haomeng|2 has quit IRC23:37
*** romcheg has quit IRC23:42
*** romcheg has joined #openstack-ironic23:42
*** romcheg has quit IRC23:43
*** Marga_ has joined #openstack-ironic23:44
*** derekh has joined #openstack-ironic23:47
*** Marga_ has quit IRC23:51
*** romcheg1 has quit IRC23:55

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