Thursday, 2014-06-19

rlooShrews: out of curiosity, what do the logs show you? Are we logging enough that you can figure out why it is locked?00:00
lifelessShrews: on bare metal?00:00
lifelessShrews: its the background power assert thread.00:00
Shrewsrloo: i see nothing in the logs that is relevant00:00
lifelessShrews: if you have a bad ilo that thread can lock a node for an extended time period00:00
Shrewslifeless: this is with the fake_ipmitool driver00:01
rlooShrews: that isn't good. means it'll be hard for people to troubleshoot.00:01
lifelessShrews: oh, huh.00:01
rlooShrews: can you change the config setting to 'turn off' the periodic task. if you get NodeLocked, I might start to worry ;)00:01
Shrewsrloo: good idea00:02
Shrewsrloo: recall which setting it is?00:02
rloosync_power_state_interval I think. set to 1 minute now.00:02
rlooset it to 100000 or something like that. I assume you're faster than that ;)00:02
Shrewsoh, lookie there...00:04
Shrewsoutput when I ctrl-C the conductor...00:05
Shrews2014-06-18 20:02:19.054 3592 WARNING ironic.drivers.modules.ipmitool [-] IPMI power status failed for node 62474f5b-c07a-4bb1-84f5-dd3be095b799 with error: Unexpected error while running command.00:05
ShrewsCommand: ipmitool -I lanplus -H 1.2.3.4 -L ADMINISTRATOR -U admin -R 12 -N 5 -f /tmp/tmp6vemNu power status00:05
ShrewsExit code: 25500:05
ShrewsStdout: '\nSIGN INT: Close Interface IPMI v2.0 RMCP+ LAN Interface\n'00:05
ShrewsStderr: 'Error: Unable to establish IPMI v2 / RMCP+ session\n'.00:05
Shrewsoh, it's there on startup. scrolled by too quickly00:06
Shrewswhy is that being run with fake_ipmitool??00:07
Shrewsrloo: what is the output of 'git rev-parse HEAD' for you?00:08
rlooShrews: ccf0950043775da941bb1bc0fd87e5106cd7b1ef00:09
rlooShrews: looks like you found a bug!00:10
Shrewsrloo: ??? that's o nthe master branch?00:10
Shrewsi don't see that commit hash00:10
rlooShrews: yeah. I did a pull recently.00:11
rlooShrews: sorry wrong window. that was the client code.00:11
rlooShrews: de8e5e1621ba0cead4bdb6edf97d75462d8b52d500:12
Shrewsok, me too. what the fudge is going on00:12
rlooShrews: I can look (start a new dev env) tomorrow and try it out. I don't like looking into things like this in the evening cuz I don't want to work all night.00:13
Shrewsrloo: ++00:14
ShrewsI'm the same way, though I know it's probably going to bug the heck out of me and keep me awake until I resolve it.00:14
* Shrews is a bit OCD'ish sometimes00:14
rlooShrews: ha ha. Well, start a new dev environment then. FWIW, I'm running in RHEL and I don't expect the node I added to ironic, to do anything.00:16
*** matsuhashi has joined #openstack-ironic00:20
*** Chandra has quit IRC00:23
*** hemna is now known as hemna_00:25
*** meylor has joined #openstack-ironic00:37
*** meylor has left #openstack-ironic00:37
*** nosnos has joined #openstack-ironic00:43
*** ellenh has quit IRC01:03
openstackgerritOpenStack Proposal Bot proposed a change to openstack/ironic: Updated from global requirements  https://review.openstack.org/9622801:07
openstackgerritOpenStack Proposal Bot proposed a change to openstack/ironic-python-agent: Updated from global requirements  https://review.openstack.org/8872201:07
*** Haomeng has quit IRC01:13
*** eguz has joined #openstack-ironic01:25
*** eghobo has quit IRC01:29
*** dwalleck has joined #openstack-ironic01:39
*** eguz has quit IRC01:42
*** foexle_ has joined #openstack-ironic01:46
*** foexle has quit IRC01:49
*** matsuhashi has quit IRC02:07
*** matsuhashi has joined #openstack-ironic02:08
*** matsuhashi has quit IRC02:08
*** matsuhashi has joined #openstack-ironic02:08
openstackgerritA change was merged to openstack/ironic: Destroy instance to clear node state on failure  https://review.openstack.org/9951902:12
*** rloo has quit IRC02:17
*** yfujioka has quit IRC02:50
*** ramineni has joined #openstack-ironic02:58
*** vinbs has joined #openstack-ironic03:05
*** rwsu has quit IRC03:27
*** blamar has joined #openstack-ironic03:38
*** blamar has quit IRC03:38
*** matsuhashi has quit IRC03:38
*** matsuhashi has joined #openstack-ironic03:39
*** matsuhashi has quit IRC03:45
*** matsuhashi has joined #openstack-ironic03:45
*** matsuhashi has quit IRC03:46
*** dwalleck has quit IRC03:46
*** radsy has quit IRC03:48
*** sabah has joined #openstack-ironic03:52
*** nosnos has quit IRC04:02
*** matsuhashi has joined #openstack-ironic04:37
*** nosnos has joined #openstack-ironic04:43
*** Nisha has joined #openstack-ironic04:46
*** rameshg87 has joined #openstack-ironic04:52
*** matsuhashi has quit IRC04:56
*** matsuhashi has joined #openstack-ironic04:57
*** k4n0 has joined #openstack-ironic05:08
*** rakesh_hs2 has joined #openstack-ironic05:35
*** bmahalakshmi has joined #openstack-ironic05:37
*** pcrews has quit IRC05:45
*** harlowja is now known as harlowja_away05:54
*** lazy_prince has joined #openstack-ironic06:00
openstackgerritOpenStack Proposal Bot proposed a change to openstack/ironic: Imported Translations from Transifex  https://review.openstack.org/9606306:02
Nishak4n0: are you working on seamicro?06:06
k4n0Nisha, used to work on that06:10
k4n0Nisha, why?06:10
Nishak4n0: I have raised a design spec review https://review.openstack.org/#/c/100951/06:13
Nishak4n0: Deva's opinion is that Seamicro and IPA guys shall also have a look at it06:14
k4n0Nisha, does this discovery happen after node registration?06:15
Nishaand give their opinion on it06:15
*** rakesh_hs2 has quit IRC06:15
*** rakesh_hs2 has joined #openstack-ironic06:16
k4n0Nisha, does this discovery happen after manual node registration?06:16
Nishak4n0: Yes and No.  Yes because after node id is created and node is registered, the properties are discovered. No, because the node is not returned until the discovery is completed and properties fields are populated.06:16
k4n0Nisha, ok, i will take a deeper look and get back to you, btw i am no longer associated with SeaMicro.06:17
k4n0Nisha, you should talk to michael patridge at SeaMicro06:17
Nishak4n0: It will be good if you could review and let me know the opinion. Do you know who is currently working on seamicro?06:18
*** Poornima|mtg has joined #openstack-ironic06:19
*** Mikhail_D_ltp has joined #openstack-ironic06:19
*** pcrews has joined #openstack-ironic06:20
NishaJayF: Are you working on IPA?06:20
k4n0Nisha, Michael Patridge from AMD06:23
k4n0Nisha, dunno if he is on this chan06:23
Nishak4n0: Thanks06:25
dtantsur|afkMorning Ironic!06:50
mrdahi dtantsur|afk06:52
*** dtantsur|afk is now known as dtantsur06:53
*** jcoufal has joined #openstack-ironic07:10
*** sysexit has joined #openstack-ironic07:15
*** ajc_ has joined #openstack-ironic07:17
*** athomas has joined #openstack-ironic07:21
openstackgerritShivanand Tendulker proposed a change to openstack/ironic-specs: Design spec for firmware settings feature.  https://review.openstack.org/10112207:25
*** Madasi has quit IRC07:27
*** Madasi has joined #openstack-ironic07:29
openstackgerritShivanand Tendulker proposed a change to openstack/ironic-specs: Design spec for firmware settings feature.  https://review.openstack.org/10112207:31
*** vinbs has quit IRC07:33
*** vinbs has joined #openstack-ironic07:34
*** pcrews has quit IRC07:37
openstackgerritA change was merged to openstack/ironic: Add 'context' parameter to get_console_output()  https://review.openstack.org/10076807:48
*** sabah has quit IRC08:05
*** sysexit has quit IRC08:06
*** sysexit has joined #openstack-ironic08:07
raminenidtantsur , Hi08:20
dtantsurramineni, hi08:20
raminenidtantsur, regarding the comment in the ilo power spec ,08:21
raminenidtantsur, by ilo specification , u meant some API documentation about functions?08:22
dtantsurramineni, any kind, that people may read to know what iLO is :) it's more-or-less formal request from me, so that spec is complete08:22
raminenidtantsur , ok userguide kind of?08:24
dtantsurramineni, should be enough, I guess08:24
raminenidtantsur , thanks ..will udpate that :)08:25
*** pelix has joined #openstack-ironic08:35
*** igordcard has joined #openstack-ironic08:36
*** romcheg has joined #openstack-ironic08:39
*** mrda is now known as mrda-away08:43
*** nosnos has quit IRC08:44
*** lucasagomes has joined #openstack-ironic08:45
*** nosnos has joined #openstack-ironic08:46
*** igordcard has quit IRC08:48
openstackgerritImre Farkas proposed a change to openstack/ironic-specs: DRAC power driver  https://review.openstack.org/9935208:49
*** igordcard has joined #openstack-ironic08:52
*** rakesh_hs2 has quit IRC08:54
*** rakesh_hs2 has joined #openstack-ironic08:58
*** saripurigopi has joined #openstack-ironic08:59
*** sabah has joined #openstack-ironic09:10
saripurigopiI'm testing the vendor_passthru using curl+POST., i'm testing a simplet method that returns firmware information. but i'm not seeing any response.09:10
saripurigopiIn the logs I can see the info printed.09:10
saripurigopiany idea why it is returning null in the response.09:13
*** openstackgerrit has quit IRC09:14
rameshg87saripurigopi, i don't vendor passthru returns anything in http body back09:15
rameshg87saripurigopi,  is your vendor passthru getting called ? (checking api and conductor logs ??)09:15
saripurigopirameshg87, Yes, In the conductor log I can see the return values printed.09:16
saripurigopi2014-06-19 15:50:12.500 29936 DEBUG ironic.drivers.modules.cisco [-] UCS server firmware version: {'Dn': 'sys/chassis-1/blade-5/fw-status', 'OperState': 'ready', 'PackageVersion': '2.1(1a)B'} _get_firmware_info /opt/stack/ironic/ironic/drivers/modules/cisco.py:52509:17
*** martyntaylor has joined #openstack-ironic09:17
saripurigopi@rameshg87, At the moment vendor_passthru is used only for set operations ?09:19
rameshg87saripurigopi, yes i think it is09:20
rameshg87saripurigopi, https://github.com/openstack/ironic/blob/master/ironic/conductor/manager.py#L257-L29009:20
rameshg87saripurigopi, the conductor thread processing vendorpassthru rpc message, triggers the vendor passthru in the background and comes out immediately. so it doesn't return anything09:21
saripurigopirameshg87, are there any plans to support GET?09:21
rameshg87saripurigopi, i guess there has been no requirement for GET till now, so only POST has been implemented https://github.com/openstack/ironic/blob/master/ironic/api/controllers/v1/node.py#L450-L47709:22
rameshg87saripurigopi, you may add support for making a GET call on the nodes/vendor_passthru09:23
rameshg87saripurigopi, :-)09:23
lucasagomesjroll, instance_info patches were updated again after rloo review09:24
saripurigopi@rameshg87, I'm not very familier with the framework, I'm willing to add the support with some help on understanding the framework.09:25
rameshg87saripurigopi, sure :-)09:26
rameshg87saripurigopi, if you wanted to add GET interface for vendorpassthru, the existing code should help. changes required for that would be similar09:27
rameshg87saripurigopi, you may refer an existing thing nodes/console which supports both GET and PUT  https://github.com/openstack/ironic/blob/master/ironic/api/controllers/v1/node.py#L75-L11009:27
saripurigopi@rameshg87, ok.09:28
saripurigopi@rameshg87, will gothrough the links and try this out.09:29
raminenisaripurigopi , if you are looking for getting firmware information , I have proposed a standard API for that09:30
raminenisaripurigopi, u can have a look at that , https://review.openstack.org/#/c/100842/309:30
raminenisaripurigopi, still in design spec review though :)09:31
saripurigopi@rameshg87, there are various other get methods I'm trying to verify.09:32
saripurigopiok09:32
*** nosnos has quit IRC09:40
*** matsuhashi has quit IRC09:44
*** matsuhashi has joined #openstack-ironic09:44
*** matsuhashi has quit IRC09:46
*** matsuhashi has joined #openstack-ironic09:47
lucasagomesa-ha... * openstackgerrit has quit (Ping timeout: 240 seconds)09:51
*** coolsvap|afk is now known as coolsvap09:55
rameshg87lucasagomes, :-) , how do we get it back in ?09:58
lucasagomesrameshg87, hah no idea09:58
dtantsuropenstackgerrit is on PTO :D10:00
lucasagomeslol10:01
*** Nisha has quit IRC10:12
*** coolsvap is now known as coolsvap|afk10:15
*** max_lobur has joined #openstack-ironic10:16
*** Manishanker has joined #openstack-ironic10:20
*** Manishanker has quit IRC10:24
*** viktors has joined #openstack-ironic10:24
*** coolsvap|afk is now known as coolsvap10:32
*** romcheg has quit IRC10:34
lucasagomeslifeless, ping re #86092, left a comment there, I believe that patches are safe to land each patch in a standalone fashion10:35
*** takadayuiko has joined #openstack-ironic10:36
lucasagomeslifeless, there's an abstraction layer that checks whether that driver supports the management interface and use it if so, or it falls back to the normal vendor_passthru (just as before)10:36
*** coolsvap is now known as coolsvap|afk10:57
*** matsuhashi has quit IRC11:00
*** matsuhashi has joined #openstack-ironic11:01
*** ramineni has left #openstack-ironic11:03
*** matsuhashi has quit IRC11:05
*** dtantsur is now known as dtantsur|lunch11:11
*** Mikhail_D_ltp has quit IRC11:14
*** Mikhail_D_wk has quit IRC11:14
*** Mikhail_D_ltp has joined #openstack-ironic11:15
*** Mikhail_D_wk has joined #openstack-ironic11:15
*** matsuhashi has joined #openstack-ironic11:16
*** romcheg has joined #openstack-ironic11:20
*** rameshg87 has left #openstack-ironic11:23
*** pradipta_away is now known as pradipta11:30
*** sabah has quit IRC11:34
*** saripurigopi has quit IRC11:35
*** ajc_ has quit IRC11:50
*** ajc_ has joined #openstack-ironic11:50
*** bmahalakshmi has quit IRC11:54
*** ajc_ has quit IRC11:55
*** shausy has joined #openstack-ironic11:55
Shrewslucasagomes: mrda-away: commit messages can be edited directly in gerrit. new feature since the upgrade12:00
lucasagomesoh that's true12:02
*** sysexit has quit IRC12:03
*** koolks has joined #openstack-ironic12:03
*** Poornima|mtg has quit IRC12:07
*** pradipta is now known as pradipta_away12:11
*** matsuhashi has quit IRC12:13
*** matsuhashi has joined #openstack-ironic12:14
*** matsuhas_ has joined #openstack-ironic12:18
*** matsuhashi has quit IRC12:18
vinbsHi lucasagomes :)12:19
vinbslucasagomes, pxe boot on ironic baremetal passes but the eventual os deploy fails12:21
romchegMorning Ironic!12:21
vinbslucasagomes, I think it's an issue with the partitioning12:22
lucasagomesvinbs, hey right... do you have the conductor log handy?12:23
vinbslucasagomes, yes let me share it with you12:23
*** sysexit has joined #openstack-ironic12:24
vinbslucasagomes, here's the conductor log http://paste.openstack.org/show/84494/12:30
vinbslucasagomes, I'm using the icehouse version of ironic12:31
lucasagomesvinbs, oh right yeah I can see the sfdisk there12:32
lucasagomesvinbs, the partitioning seems to be fine, the image was copied to the disk as well "3431565312 bytes (3.4 GB) copied, 79.6272 s, 43.1 MB/s"12:32
lucasagomesvinbs, which error you get when booting the instance?12:32
vinbslucasagomes, I dont see an error on the openstack side12:33
vinbslucasagomes, but after copying the image, the server reboots for the actual os deploy12:33
lucasagomesvinbs, right, something on the console?12:33
lucasagomesvinbs, ohh12:33
lucasagomesvinbs, the instance in nova-list is marked as active?12:34
vinbslucasagomes, and it again goes into pxe bott12:34
vinbslucasagomes, yes12:34
lucasagomesvinbs, and u sure ur not using the same deploy ramdisk and deploy kernel in the image metadata?12:34
lucasagomesvinbs, right, one thing is, local boot is not actually implemented in Ironic12:35
lucasagomesso, it will PXE boot to boot the final image12:35
lucasagomesvinbs, it's done because we want to guarantee the order that the machines are booted (hosts first and then guests) so having guests to always PXE boot we can ensure that ordem12:35
*** k4n0 has quit IRC12:36
vinbslucasagomes, I'm confused about the different images I need to use12:36
lucasagomesvinbs, right... so you have 2 pairs of ramdisks and kernels12:37
lucasagomesyou have the deploy kernel and ramdisk, which are set in the flavor12:37
vinbslucasagomes, ahh that is where I'm making a mistake!12:37
lucasagomesthis is a special ramdisk that actually does the deployment of the node (expose the iscsi etc)12:37
lucasagomesand you have the real image ramdisk and kernel set as metadata in glance12:37
lucasagomesvinbs, right12:37
*** coolsvap|afk is now known as coolsvap12:38
vinbslucasagomes, and both these pairs of images need to be imported into glance?12:38
lucasagomesso the metadata in glance should point to the real ramdisk and kernel of the image u want to deploy12:38
lucasagomesvinbs, yes12:38
vinbslucasagomes, so in glance I would be having two pairs of ramdisk and kernel images and one actual image of the deploy OS?12:39
lucasagomesvinbs, yes12:39
vinbslucasagomes, one pair I would have associated with the flavor and the other pair with the actual deploy OS by using glance image-update12:39
vinbslucasagomes, is that right?12:39
lucasagomesvinbs, that's correct... the deploy one in flavor12:40
*** takadayuiko has quit IRC12:40
lucasagomesvinbs, you can use some tripleO scripts to extract the kernel/ramdisk from the image and upload it to glance12:40
lucasagomesor at least look at how it's done... lemme grab the link12:40
lucasagomesvinbs, https://github.com/openstack/tripleo-incubator/blob/master/scripts/load-image12:41
vinbslucasagomes, yes I did use diskimage builder to extract kernel and ramdisk from my deploy image12:41
lucasagomes(we def need to document such things better, and I'm looking fwd to have local boot as an option)12:41
lucasagomesvinbs, right, so you upload those to glance12:41
lucasagomesand then set their ID's on the image metadata12:41
vinbslucasagomes, so I associate the id of these extracted images with my actual deploy image12:42
lucasagomesvinbs, yes12:42
vinbslucasagomes, I can't use the same kernel and ramdisk images to associate with the flavor?12:42
lucasagomesvinbs, no because the flavor one points to the deploy ramdisk12:43
lucasagomesvinbs, which is a special ramdisk... this deploy ramdisk has a customized init script12:43
lucasagomesvinbs, which takes the disk expose it via iscsi, try to talk back to the Ironic api etc...12:43
vinbslucasagomes, where do I get the images which I need to associate with the flavor?12:44
lucasagomesvinbs, you can build a deploy ramdisk using the diskimage-builder12:44
lucasagomesvinbs, https://github.com/openstack/diskimage-builder/tree/master/elements/deploy-ironic/12:44
vinbslucasagomes, these special ramdisk images are extracted from a cloud image which diskimage builder gets over the internet12:47
vinbslucasagomes, is that right?12:47
*** rloo has joined #openstack-ironic12:47
lucasagomesvinbs, afaiui, yes, it uses a base image (ubuntu by default I think) to build it12:48
vinbslucasagomes, cool.. that was a very informative conversation12:49
vinbslucasagomes, it cleared many doubts for me12:50
lucasagomesvinbs, :)12:50
vinbslucasagomes, thanks! :)12:50
lucasagomesvinbs, cool, glad to help12:50
lucasagomesyw12:50
*** rloo has quit IRC12:51
*** rloo has joined #openstack-ironic12:51
*** rloo_ has joined #openstack-ironic12:55
*** lucasagomes is now known as lucas-hungry12:55
*** rloo has quit IRC12:56
*** jcoufal has quit IRC12:56
*** rloo has joined #openstack-ironic12:58
*** rloo_ has quit IRC13:00
*** rloo has quit IRC13:02
*** rloo has joined #openstack-ironic13:02
*** dtantsur|lunch is now known as dtantsur13:12
*** shausy has quit IRC13:13
*** jcoufal has joined #openstack-ironic13:23
*** linggao has joined #openstack-ironic13:31
*** lucas-hungry is now known as lucasagomes13:33
NobodyCamgood morning Ironic13:38
linggaomorning NobodyCam13:39
dtantsurmorning, NobodyCam, lucasagomes, romcheg, vinbs :)13:39
romchegMornint guys!13:39
dtantsur... and linggao!13:39
lucasagomesmorning linggao romcheg NobodyCam dtantsur13:39
vinbsmorning dtantsur!13:39
linggaomorning dtantsur lucasagomes romcheg vinbs13:39
NobodyCammorning linggao dtantsur romcheg lucasagomes and vinbs :)13:40
dtantsurOur greeting lists are becoming longer :) I guess it's a good sign :)13:40
romcheg++13:40
NobodyCamlucasagomes: your buying e-novance .. or so i've heard13:41
dtantsurwow, lucasagomes is buying a company :D13:41
NobodyCamlol welll red hat really13:41
NobodyCam:-p13:41
lucasagomeslol13:42
lucasagomesNobodyCam, yup that's correct: http://www.redhat.com/about/news/press-archive/2014/6/red-hat-to-acquire-enovance13:42
NobodyCam:) wow :)13:43
NobodyCamvery nice, just in time to fill up the paris summit :) oh there is going to be so many red hats runninng around :-p13:44
*** vinbs has quit IRC13:44
lucasagomesyeah, there's a mid-cycle there as well13:45
*** sysexit has quit IRC13:45
lucasagomesNobodyCam, https://wiki.openstack.org/wiki/Sprints/ParisJuno201413:45
lucasagomesbtw devananda ^13:45
dtantsurlucasagomes, btw I'll be in Paris for my PTO, so maybe will drop by for OpenStack party :)13:45
dtantsur(depending on what mrs. Tantsur will say))13:45
linggaodtantsur, lol13:46
NobodyCamcongratz lucasagomes: Ironic13:46
NobodyCamLucas Alvares Gomes13:46
lucasagomesdtantsur, haha ack, yeah sure that would be cool13:46
rloohello ironicees13:46
dtantsurhi rloo!13:46
NobodyCammorning ironic13:46
lucasagomesNobodyCam, :)13:46
NobodyCamgah13:46
lucasagomesrloo, yo morning13:46
NobodyCammorning rloo13:46
NobodyCam:-p13:46
linggaohi rloo13:47
rloolooks like Paris is the place to be in 2014!13:47
rloolucasagomes: wrt https://review.openstack.org/#/c/94855/. Had more comments. Let me know if I don't make sense.13:48
lucasagomesrloo, sorry i think I missed ur comment for the  states13:49
rloolucasagomes: no worries. I know I had a lot.13:49
NobodyCamwe need to add set-provision-state to None that doesn't call verify :-p (to clear stuck nodes)13:50
*** sysexit has joined #openstack-ironic13:50
*** davidlenwell has quit IRC13:51
*** anteaya has quit IRC13:51
*** anteaya has joined #openstack-ironic13:52
*** davidlenwell has joined #openstack-ironic13:53
*** rloo has quit IRC13:56
*** rloo has joined #openstack-ironic13:56
*** rloo has quit IRC13:57
*** rloo has joined #openstack-ironic13:57
*** dguerri has joined #openstack-ironic13:57
*** rloo has quit IRC14:01
*** hemna has joined #openstack-ironic14:02
*** rloo has joined #openstack-ironic14:02
NobodyCamlucasagomes: Ironic14:08
NobodyCamLucas Alvares Gomes14:08
NobodyCamgrrr14:08
NobodyCamlucasagomes: http://paste.openstack.org/show/Sec5sjsKOVprN8BLQXNA/14:08
NobodyCamahh worked that time14:08
lucasagomes:( NobodyCam to tear down the machine after the deploy failed?14:09
lucasagomesNobodyCam, what caused the deploy to fail?14:09
NobodyCamyea, tftp issues14:10
jrollmorning y'all!14:10
NobodyCammorning jroll14:11
romchegMorning jroll!14:11
jrollNobodyCam: +1 on and endpoint for fixing stuck nodes :)14:11
NobodyCamI kinda think we should have somehting in the cli that would allow operators to do that14:12
NobodyCamsome thing like set-provision-state=None or --force option14:12
jrollyep14:13
jrollthe current solution is a mysql shell :(14:13
*** matsuhas_ has quit IRC14:17
*** foexle has joined #openstack-ironic14:18
*** dguerri is now known as _dguerri14:19
*** foexle_ has quit IRC14:19
lucasagomes:( yeha14:21
lucasagomesrloo, the states looks alright i think... it's talking about setting/validating the power state of the node14:23
lucasagomesnot the provision state14:23
*** matsuhashi has joined #openstack-ironic14:23
lucasagomesrloo, tho, maybe that needs a general update (or removal)14:23
lucasagomesidk if makes much sense to have that doc there14:23
*** _dguerri is now known as dguerri14:24
rloolucasagomes: ok. I wondered ;)14:24
lucasagomesrloo, so for power state it doesn't need to touch the instance_info14:24
lucasagomesrloo, ack, cheers for the other two comments there14:24
romchegGuys, I just ran stack.sh and noticed that node validation says "Can not validate PXE bootloader. The following parameters were not passed to ironic: ['pxe_root_gb', 'pxe_image_source']"14:29
romchegLooks like devstack has to be updated14:29
lucasagomesromcheg, weird lastest version of devstack and ironic?14:31
romchegFresh install14:31
romchegNew VM, fresh sources, etc14:32
lucasagomesic14:32
romchegI'll take a look14:32
*** jdob has joined #openstack-ironic14:33
*** athomas_ has joined #openstack-ironic14:33
*** rakesh_hs2 has quit IRC14:33
*** matsuhashi has quit IRC14:33
*** matsuhashi has joined #openstack-ironic14:33
*** rwsu has joined #openstack-ironic14:34
* Shrews notes to NOT upgrade devstack14:34
*** theDavidAiken has joined #openstack-ironic14:35
*** athomas_ has quit IRC14:36
romchegAnd the node's stuck in "wait call-back" :(14:37
lucasagomesew, wondering how tests are passing14:37
*** jbjohnso has joined #openstack-ironic14:37
*** hemna has quit IRC14:37
*** matsuhashi has quit IRC14:38
* romcheg is going to debug that14:38
*** matsuhashi has joined #openstack-ironic14:40
*** dguerri is now known as _dguerri14:41
*** _dguerri is now known as dguerri14:41
lucasagomesNobodyCam, https://review.openstack.org/#/c/101148/ easy one14:45
NobodyCamdoh hahaha good catch14:48
rloolucasagomes: wrt 101148 (am just looking at it). not all the tests call sleep, is the idea to just put sleep in all the tests, just in case?14:49
lucasagomesrloo, well I though it would be easier to put at the class level so that we make sure that no tests would waste time sleeping14:49
lucasagomes(we don't access the BMC on tests so no reason to sleep between ipmi commands there)14:50
NobodyCamrloo I just landed it14:51
lucasagomesrloo, if you think it's better I could add the sleep only on the tests that actually are using it14:51
NobodyCamor +a14:51
NobodyCam'd14:51
lucasagomesoh14:51
lucasagomesheh ok a bit late :)14:51
rloolucasagomes: I should probably read up more on mocks. If it is at the class level, is it used for all tests in that class, or only for tests that have it in their list of parameters?14:51
lucasagomesrloo, it affects all the methods on the class AFAIUI14:52
lucasagomesI mean, the class will pass that mock to all the methods14:52
lucasagomesthat mock will be passed to all the methods in that class*14:53
rloolucasagomes: so even if mock_sleep isn't in a method's args, that mock will still be invoked in that method?14:53
rloolucasagomes: eg test__power_status_exception(self, mock_exec, mock_sleep). Did you need to put mock_sleep there?14:54
lucasagomesrloo, yeah, it that mock affects all tests, and the mock will be passed to all methods in that class14:55
lucasagomespassed as a parameter*14:55
*** romcheg1 has joined #openstack-ironic14:55
*** romcheg has quit IRC14:58
rloolucasagomes: ok, got it. So it *has* to be passed in as a parameter, cannot NOT pass it in. Thx.15:01
lucasagomesrloo, yup15:02
lucasagomesrloo, there a way to mock something at the class level but it won't be passed as parameter to any method15:02
lucasagomesrloo, @mock.patch.object(time, 'sleep', lambda _: None)15:03
lucasagomesbut it seems to be something like, or u always pass the mock to all methods, or u never pass it to any method15:03
* lucasagomes needs to read more about mock15:04
rloolucasagomes: cool. If you used the mock.patch.object, can you access it from w/i a test? If so, that seems 'cleaner'.15:04
lucasagomesrloo, both cases uses mock.patch.object, but that lambda prevents it from being passed as a parameter... And if it's not passed as a parameter I don't know how to access that mock15:05
* lucasagomes will investigate15:06
NobodyCamhumm, should we have a node-set-maintenance in the client?15:06
lucasagomesNobodyCam, node-update?15:06
*** matsuhashi has quit IRC15:07
NobodyCamya but we have set-Provision and power as a option15:07
*** matsuhashi has joined #openstack-ironic15:07
NobodyCamwhy is maintenance different15:08
NobodyCamjust looking at the node-list fields15:08
NobodyCamvs the info dict fields15:08
lucasagomesNobodyCam, afaiui because to set the power or provision in the rest api you have a special resource to validate the request (instead of only setting it on the db)15:09
lucasagomeswhere maintanance you don't need any special validation to set, if the node resource can be updated (I think we prevent updates mid-provisioning operation) you can set maintenance just like any other field15:10
dtantsurlucasagomes, rloo, I guess instead of lambda you can pass return_value=None and you'll get both return_value and mock object as a parameter15:10
dtantsur(did not follow context, just saw the latest discussion)15:10
lucasagomesdtantsur, ah good to know15:11
jbjohnsofyi, I've pushed the web widget code for confluent if anone has interest15:11
dtantsurneeds to be checked but I remember I did it once :)15:11
Shrewsadam_g: devananda: changed https://review.openstack.org/94439 to add a new BaremetalFeaturesGroup config group so we can selectively turn off the rebuild() test (or others)15:11
jbjohnsoI also have started doing service processor and node autodetection groundwork there15:11
rloodtantsur: thx. I think you're the resident mock expert :-)15:11
*** matsuhashi has quit IRC15:11
dtantsurrloo, you're overestimating me :) just did some research some time ago15:12
rloodtantsur: more research than I did! :D15:12
*** blamar has joined #openstack-ironic15:12
*** romcheg1 has left #openstack-ironic15:15
*** mdorman has joined #openstack-ironic15:15
*** athomas_ has joined #openstack-ironic15:18
*** athomas_ has quit IRC15:18
*** athomas has quit IRC15:19
*** jcoufal has quit IRC15:21
*** dwalleck has joined #openstack-ironic15:25
*** hemna has joined #openstack-ironic15:25
*** coolsvap is now known as coolsvap|afk15:27
*** athomas has joined #openstack-ironic15:28
jbjohnsoout of band inventory..... so I can offer some generally applicable stuff if interested and a scheme where in knowing which mac is which (or even needing to know the mac addresses at all) is not required15:30
jbjohnsoif anyone is interested in talking15:30
jbjohnsocpu and memory are possible to describe reasonably within the standard, mac and disk are not, but uuid is15:31
*** jgrimm has quit IRC15:34
linggaojbjohnso, devananda is not here. but I am very interested in knowing how to tell which mac is install mac without booting the node.15:34
jbjohnsothat's not possible, but you can know another PXE idenetfier reliably that does not vary with NIC, the UUID15:35
linggaomeaning, which mac is facing the conductor.15:35
jbjohnsothen you can shift to focus on UUID to do boot configuration15:35
jbjohnsoand then the OS will pick up the correct nic to ifup by way of BOOTIF=15:35
jbjohnsoIP configuration could be done outside the scope of DHCP with a generic identity instead to tide things over to static identity assignment15:36
jbjohnsoor DHCP could do DDNS update from client to assign a reliable name to a pool allocated address... so many options15:36
lucasagomesrloo, have u read lifeless comments at #99426 ? I just added another one, what do u think?15:44
* rloo looks15:44
rloolucasagomes: oh boy.15:47
lucasagomesrloo, lol I hear yah15:47
rloolucasagomes: maybe a discussion with lifeless would help. It seems to me that you're doing his first suggestiong, make everything MB to get consistency.15:48
lucasagomesrloo, that was the initial idea15:48
lucasagomesrloo, back in february... anyway yeah...15:49
rlooso, just to be clear. the issue was the inconsistency, right? swap was in MB, but root and ephemeral was in GB.15:49
lucasagomesrloo, yup15:49
rloolucasagomes: wait a minute. sorry. we want to use GB, not MB. and lifeless suggested going MB.15:51
lucasagomesrloo, yeah... but the initial idea was to use MB and (I forgot exactly) then after some discussion we decided to use GB15:52
*** eghobo has joined #openstack-ironic15:52
*** eghobo has quit IRC15:52
lucasagomesI forgot exactly why we changed our minds*15:53
rloolucasagomes: maybe it needs a BP? (just joking). I think there may be two issues here but not sure.15:53
*** eghobo has joined #openstack-ironic15:53
rloolucasagomes: 1. want consistency in units, either MB or GB.15:53
*** eghobo has quit IRC15:53
rloolucasagomes: 2. want to make sure we keep the same 'intention' as currently, so if GB, and swap was in MB, we don't want 1 MB swap -> 1 GB swap.15:54
*** eghobo has joined #openstack-ironic15:54
lucasagomesrloo, aye, sounds correct15:54
rloolucasagomes: 3. Is lifeless disagreeing with allowing root/ephemeral to be in units smaller than a GB?15:54
rloolucasagomes: wrt 3. I am wondering if he is OK with swap_GB being in fractions, but not root/ephemeral.15:55
lucasagomesrloo, I don't think so cause he suggested to use MB on that comment15:55
lucasagomesrloo, let's wait for lifeless to comment again15:56
lucasagomesrloo, cause having only swap_GB to accept fractions sounds even more incosistent15:56
rloolucasagomes: yeah. So if MB is the smallest unit we're dealing with, it seems to me that we should use MB. but maybe the argument was that people think in GB these days.15:57
lucasagomesrloo, yeah I agree... seems that going back to the original idea of MB is the best choice... 1) it's consistent 2) don't add the complexity of having fractions15:58
lucasagomesdevananda, ^ thoughts?15:58
*** lazy_prince has quit IRC16:00
lucasagomesrloo, thank u16:02
rloolucasagomes: yw. hope I helped ;)16:03
lucasagomesrloo, it did, a lot16:05
lucasagomestho I'm not coding anything until I make sure we all have an agreement on that16:05
*** jcoufal has joined #openstack-ironic16:06
ShrewsNobodyCam: ping16:07
*** vinbs has joined #openstack-ironic16:10
NobodyCamreply with "pong"16:10
ShrewsNobodyCam: why does FakeIPMIToolDriver not use a fake power driver? If there nothing real deployed, those calls won't work.16:12
*** vinbs_ has joined #openstack-ironic16:12
Shrewsi'm failing to understand the purpose of these16:12
*** cdent has joined #openstack-ironic16:13
NobodyCamhumm,16:13
Shrews"these" being fake drivers16:13
*** vinbs has quit IRC16:14
*** vinbs_ is now known as vinbs16:15
NobodyCamShrews: say I have a laptop that I want to use as a test node, I could hit the power button at the correct time and the deploy would work?16:15
*** Nisha has joined #openstack-ironic16:17
ShrewsNobodyCam: so all of the Fake* drivers (except for FakeDriver), are expected to have real h/w for nodes?16:17
*** blamar has quit IRC16:18
NobodyCamor used to check that the rest of the bits did their thing, I.e setup the tftp dir correctly, pulled images16:18
NobodyCametc,16:18
NobodyCamoh bbt brb16:19
*** martyntaylor has left #openstack-ironic16:23
*** ellenh has joined #openstack-ironic16:23
*** foexle has quit IRC16:28
Nishalinggao: Hi16:29
Nishalinggao: saw the comment on https://review.openstack.org/#/c/100951/5 "Discover node properties at node-create/node-update"16:31
*** coolsvap|afk is now known as coolsvap16:31
*** cdent_ has joined #openstack-ironic16:31
*** cdent has quit IRC16:32
*** cdent_ is now known as cdent16:32
*** jcoufal has quit IRC16:41
*** jcoufal has joined #openstack-ironic16:42
*** koolks has quit IRC16:53
*** ellenh_ has joined #openstack-ironic16:55
*** ellenh has quit IRC16:55
*** ellenh_ is now known as ellenh16:55
NishaHi linggao16:57
dtantsurinstance_info patch https://review.openstack.org/#/c/94855/ got 2x +2 and is waiting for final approval16:59
dtantsurNobodyCam, devananda wanna have a look ^^^ ?16:59
JayFhttp://www.rackspace.com/cloud/servers/onmetal/ just got announced today. https://gist.github.com/jnoller/248a9d7f9b008f5d0aee17:02
JayFWe'll be posting a blog very shortly about how our production environment works. TL;DR: Ironic master + Agent patches, everything provisioned with the agent.17:02
rloodtantsur: why don't you want to approve?17:02
JayFThanks to everyone here for helping us get up to speed, learn about how things work, and providing a foundation for us to build something awesome on.17:03
NishaJayF: Hi17:03
dtantsurrloo, give folks chances to have last look. Will approve, if noone else appears for review after some time :)17:03
lucasagomeso/17:04
JayFNisha: hey, I saw your message overnight but you weren't in here when I got in.17:04
rloodtantsur: ok.17:04
jrolloh Nisha, you're here now! I put "review Nisha's spec" on my todo list :) (I also work on IPA)17:04
rlooJayF: you scared me. I thought you were thanking us cuz you were leaving!17:04
comstudhahaha17:04
JayFrloo: no absolutely not! This is the start of a long journey17:04
comstudSEE YA GUYS... HAVE FUN!17:04
NishaJayF: jroll: Thanks17:04
rlooha ha ha17:04
jrolllol comstud17:05
*** pcrews has joined #openstack-ironic17:05
NishaPlease could you review https://review.openstack.org/#/c/100951/5 and let me know the comments on the same17:05
*** harlowja_away is now known as harlowja17:05
dtantsurJayF, wow cool!17:05
NishaJayF: jroll: If any doubts we can discuss here also17:05
jrollNisha: sure. Jay and I are at a conference today, and have a hack day tomorrow. we'll take a look next week at the latest :)17:06
NishaOk17:06
JayFdtantsur: thanks!17:07
lucasagomesaight, it's late here and I came to the office so gotta take the train back home17:09
lucasagomeshave a good night everybody17:09
JayFlucasagomes: thanks, goodnight17:09
*** lucasagomes has quit IRC17:09
*** blamar has joined #openstack-ironic17:15
*** dguerri has quit IRC17:19
*** athomas has quit IRC17:22
*** Mikhail_D_ltp has quit IRC17:33
*** eghobo has quit IRC17:37
*** eguz has joined #openstack-ironic17:37
*** Shrews has quit IRC17:37
*** jcoufal has quit IRC17:38
*** pelix has quit IRC17:41
*** eguz has quit IRC17:49
*** eghobo has joined #openstack-ironic17:50
anteayaNobodyCam: is deva around today?17:50
*** Shrews has joined #openstack-ironic17:50
devanandamorning, all17:53
devanandaanteaya: hi!17:53
anteayadevananda: hello17:53
anteayajeblair pinged you in infra linking you to https://news.ycombinator.com/item?id=791709817:54
anteayajust wanted to ensure you were going to be around today17:54
anteayanothing like accurate information17:54
jrollmorning devananda :)17:55
NobodyCamanteaya: he is working on securing a new home for him self17:55
NobodyCamoh didn't see ya there devananda :)17:55
anteayaNobodyCam: ah cool17:56
anteayayes having a place to live is very important17:56
anteayaor you can just take it with you everywhere you go17:56
NobodyCamI have to run to the store real quick17:56
anteayalike a turtle or NobodyCam17:56
NobodyCamlol17:56
anteaya:D17:57
devanandayea - i'll be offline again in a few min17:57
anteayakk17:57
devanandadoing the paperwork dance for a new apartment17:57
jrollanteaya: "nothing like accurate information" - what do you mean?17:57
anteayaI hope it goes well17:57
*** blamar has quit IRC17:57
devanandaanteaya: I was about to ask what jroll just asked17:57
BadCubOooh.. How fun17:57
anteayaI mean that a trail of comments is all spectulation17:57
anteayaso hearing from people who have actual real information is sometimes helpful17:58
jrollanteaya: hm, those comments17:58
anteayayeah17:58
devanandaanteaya: taht seems more in line with something a representative of rackspace should cover, no?17:58
anteayaso joining in on the thread might be a chance to share some real information about what ironic does and doenst' do17:58
anteayasure17:58
anteayaif they know it is on hacker news17:59
jrollI have no idea wtf a micro-vm17:59
jrollis17:59
anteayaright17:59
anteayaneither do folks in the comments17:59
devanandajroll: oh, so the announcement covered BOTH OnMetal and CoreOS / Docker17:59
anteayahere comes the spin17:59
jrollI think I got it17:59
devanandajroll: so i blame your marketing peopel for any confusion that ensues17:59
jrolldevananda: I mean, kind of17:59
jrollnobody knows where that article came from17:59
jrollit also dropped *before* the announcement17:59
jrollso like, idk17:59
devanandahah17:59
devanandathat's fun18:00
devanandajroll: not much before ... maybe minutes, or less18:00
JayFdevananda: we blame our marketing people for any confusion that ensues :)18:00
anteayaso contributing might be a chance to get accurate info out there18:00
anteayaor whether the storm when inaccurate info about ironic hits people in the subconcsious18:01
anteayaweather18:01
devanandagotta run ... bbiah18:01
JayFjroll has a blog post written describing how this stuff is running in our environment18:01
jrollanteaya: commented on that18:01
JayFbut pretty much anytime in the last 2 months when we've said 'this works in our lab' or 'this works in our environment'... we pretty much mean that18:01
JayFlol18:01
jroll^ said blog post is having delays going up, but will be soon18:02
anteayaso folks are already thinking that rackspace build ironic18:02
anteayabuilt18:02
jrollanteaya: sigh18:02
anteayayup18:02
jrolldue to that article?18:02
anteayafollow or get trampled18:02
anteayahttps://news.ycombinator.com/item?id=791720318:03
JayFPeople think lots of crazy things :)18:03
anteayasorry, lead or get trampled18:03
anteayaKudos to Rackspace for building this.18:03
JayFanteaya: FWIW, none of us feel that way18:03
anteayaoh I know that18:03
*** hemna has quit IRC18:03
jrollhrm18:03
*** ryanpetrello has quit IRC18:03
anteayabut trying changing public perception _after_ it has formed18:04
jrollggreer used to work in our office, I'd be shocked if he thought we built ironic18:04
jrollbut will comment18:04
* anteaya returns to doing battle in the third party space18:04
anteayaclarity is good18:04
jroll+118:04
JayFanteaya: I commented18:07
* NobodyCam is back18:07
JayFanteaya: my annoyance with it is actually more that so many people are overlooking that these are OpenCompute machines!18:07
*** vinbs has quit IRC18:08
*** rloo has quit IRC18:08
*** viktors has quit IRC18:08
*** dshulyak has quit IRC18:08
*** slamont has quit IRC18:08
*** Madasi has quit IRC18:08
*** mkerrin has quit IRC18:08
*** rushiagr has quit IRC18:08
*** russell_h has quit IRC18:08
*** eghobo has quit IRC18:08
*** wendar has quit IRC18:08
*** harlowja has quit IRC18:08
*** mgagne has quit IRC18:08
*** agordeev has quit IRC18:08
*** yjiang5 has quit IRC18:08
*** adam_g has quit IRC18:08
*** rainya has quit IRC18:08
*** stevebaker has quit IRC18:08
*** pquerna has quit IRC18:08
*** zigo has quit IRC18:08
*** morgabra has quit IRC18:08
*** mrda-away has quit IRC18:08
*** antonym has quit IRC18:08
*** cdent has quit IRC18:08
*** eghobo has joined #openstack-ironic18:10
*** vinbs has joined #openstack-ironic18:10
*** rloo has joined #openstack-ironic18:10
*** viktors has joined #openstack-ironic18:10
*** Madasi has joined #openstack-ironic18:10
*** dshulyak has joined #openstack-ironic18:10
*** mkerrin has joined #openstack-ironic18:10
*** wendar has joined #openstack-ironic18:10
*** slamont has joined #openstack-ironic18:10
*** harlowja has joined #openstack-ironic18:10
*** yjiang5 has joined #openstack-ironic18:10
*** mgagne has joined #openstack-ironic18:10
*** agordeev has joined #openstack-ironic18:10
*** rushiagr has joined #openstack-ironic18:10
*** adam_g has joined #openstack-ironic18:10
*** rainya has joined #openstack-ironic18:10
*** russell_h has joined #openstack-ironic18:10
*** antonym has joined #openstack-ironic18:10
*** mrda-away has joined #openstack-ironic18:10
*** morgabra has joined #openstack-ironic18:10
*** zigo has joined #openstack-ironic18:10
*** pquerna has joined #openstack-ironic18:10
*** stevebaker has joined #openstack-ironic18:10
*** dguerri has joined #openstack-ironic18:10
linggaoHi Nisha18:12
NishaHi linggao18:13
*** Mikhail_D_ltp has joined #openstack-ironic18:13
NishaI posted the resolution comments on the comments you gave on Discover node properties design spec18:14
linggaoNisha, let me take a look....18:14
*** vinbs has quit IRC18:14
*** rloo has quit IRC18:14
*** viktors has quit IRC18:14
*** dshulyak has quit IRC18:14
*** slamont has quit IRC18:14
*** Madasi has quit IRC18:14
*** mkerrin has quit IRC18:14
*** rushiagr has quit IRC18:14
*** russell_h has quit IRC18:14
*** eghobo has quit IRC18:14
*** wendar has quit IRC18:14
*** harlowja has quit IRC18:14
*** mgagne has quit IRC18:14
*** agordeev has quit IRC18:14
*** yjiang5 has quit IRC18:14
*** adam_g has quit IRC18:14
*** rainya has quit IRC18:14
*** stevebaker has quit IRC18:14
*** pquerna has quit IRC18:14
*** zigo has quit IRC18:14
*** morgabra has quit IRC18:14
*** mrda-away has quit IRC18:14
*** antonym has quit IRC18:14
Nishalinggao: Thanks18:15
*** eghobo has joined #openstack-ironic18:16
*** vinbs has joined #openstack-ironic18:16
*** rloo has joined #openstack-ironic18:16
*** viktors has joined #openstack-ironic18:16
*** Madasi has joined #openstack-ironic18:16
*** dshulyak has joined #openstack-ironic18:16
*** mkerrin has joined #openstack-ironic18:16
*** wendar has joined #openstack-ironic18:16
*** slamont has joined #openstack-ironic18:16
*** harlowja has joined #openstack-ironic18:16
*** yjiang5 has joined #openstack-ironic18:16
*** mgagne has joined #openstack-ironic18:16
*** agordeev has joined #openstack-ironic18:16
*** rushiagr has joined #openstack-ironic18:16
*** adam_g has joined #openstack-ironic18:16
*** rainya has joined #openstack-ironic18:16
*** russell_h has joined #openstack-ironic18:16
*** antonym has joined #openstack-ironic18:16
*** mrda-away has joined #openstack-ironic18:16
*** morgabra has joined #openstack-ironic18:16
*** zigo has joined #openstack-ironic18:16
*** pquerna has joined #openstack-ironic18:16
*** stevebaker has joined #openstack-ironic18:16
*** bmahalakshmi has joined #openstack-ironic18:18
*** mdorman has quit IRC18:18
*** mdorman has joined #openstack-ironic18:19
jrolloh, right, for any of you that happen to be in SF today, this is the party I mentioned on monday: http://www.eventbrite.com/e/rackspace-special-announcement-party-onmetal-tickets-11943323803?aff=estw18:20
Nishalinggao, there?18:21
*** ryanpetrello has joined #openstack-ironic18:21
linggaoNisha, the mac address in the port table is for deployment use, manly for dhcp.18:22
linggaoSo it does not make sense to put all the mac addresses in the port table.18:22
linggaothe cpu, meomory, disk properties are for scheduling purpose.18:23
NishaYes, i know that MAC address is for deploy use.18:23
NishaBut when we say we will discover hw properties all those also form part of the hw properties18:23
linggaothen how do you tell which mac is for deployment?18:24
Nishaeach NIC/MAC have some prop at firmware level18:24
Nishathe states i have seen are disabled, PXE, iSCSI18:25
Nishai think PXE state MAC address can be chosen for deploy18:25
Nishaand BTW nothing stops an admin to set other MAC addresses to PXE or iSCSI state18:25
Nishaby default i have seen only one having PXE state and others in disabled state, and generally we will pick up that MAC address for deploy18:26
Nishadoes it make sense?18:26
linggaois this for iLO or IPMI?18:27
Nishalinggao: The MAC address state can be get18:27
linggaojbjohnso, are you there?18:28
NishaThe feature proposal isgeneric, it can be acheived thru iLO and ipmi both18:28
Nishaatleast we can use ipmi commands to get the state of MAC, thats for sure18:28
Nishalinggao: we plan to implement it thru iLO but it shall be possible via IPMI too18:29
linggaolet me ask jbjohnso, he knows more about firmware than I.18:29
Nishaok18:29
Nisha:)18:29
Nishalinggao: meanwhile can we discuss about your comment for disk inventory18:31
jbjohnsohello18:31
jbjohnsolinggao, I'm awake18:32
linggaojbjohnso, that's good. :)18:32
Nishajbjohnso, Hi18:32
jbjohnsoNisha, hello18:32
jbjohnsoso for memory and cpu, at least those can be described via strict ipmi specification to pretty specific stuff18:32
linggaoNisha and I are dicussing how to identify the install mac through IPMI. Nisha said there is a state associated with each mac18:33
jbjohnsowell, state is an interesting question18:33
Nishajbjohnso, are u aware of it?18:34
jbjohnsoso whatever data about a nic won't be in standard ipmi as far as I can think, but at least we do it using OEM vocabulary18:34
NishaYes we need to use raw command18:34
jbjohnsonow for state, how much do yu see?  We could distingush things like linuk state, but that doesn't seem adequate18:34
jbjohnsowhat I was planning to do to facilitate more arbitrary less context sensitive stuff was to enable tooling to do boot configuration keyed more into the UUID than the mac addresses18:35
rloodtantsur: I had another comment for 9462018:35
jbjohnsosince I could forsee a lot of cases where indequate context can be retrieved (e.g. which vlan is where and also what about off the shelf pci adapters)18:35
Nishajbjohnso, i didnt get your statement18:36
Nishathe second last one18:36
jbjohnsoNisha, so a PXE discover and such all comes with two servicable identifiers (well, one in DHCPv6, 2 in ipv418:36
dtantsurrloo, always thought that int(float) behaves exactly as int(round(float)) lemme check18:36
jbjohnsoUUID and mac address18:36
jbjohnsothe former is unique per node, the latter unique per iface18:36
Nishaok.18:37
linggaojbjohnso, let's not go to the UUID yet. Nisha said there are states like: pxe, iscsi, and disable. he/she can pick the the mac with pxe state as install nic.18:37
dtantsurrloo, int(floor(float)) actually18:37
NishaYes lingago is correct18:37
Nishalinggao*18:37
rloodtantsur: that will take the floor. did you want the floor or round?18:37
Nishasorry misspelled the name18:37
rloodtantsur: eg for 1.6, do you want 1 or 2?18:38
linggaoNisha, np, I just learned that you can use the tab key to auto fill the name.18:38
Nisha linggao: I am she18:38
*** bandicot has joined #openstack-ironic18:38
dtantsurrloo, that's a fair question and I don't see a correct answer :) I preferred floor because it's more predictable18:38
linggaoNisha, same here.18:38
Nishagr818:39
jbjohnsoNisha, so you are basically reying upon someone exlicitly configuring the roles in firmware?18:39
Nishajbjohnso18:39
NishaNo18:39
rloodtantsur: I'm fine with that (see what happens if that function is actually being used). but you need to document it then. it says 'round' ;)18:39
Nishaby default, say a BM has 10 ports18:39
dtantsurrloo, I mean, both variants are bad if we have 1.6 MiB, but we can't with current disk partitioner :)18:39
jbjohnsook.18:39
Nishajbjohnso, then one is enabled as PXE state and others are in disabled state18:39
jbjohnsoNisha, right, but who enabled one?18:40
rloodtantsur: yeah, i know that in practise it won't happen, just want to make sure the code is accurate/does what it says.18:40
Nishai think that comes factory shipped18:40
jbjohnsoNisha, so for us, we have PXE attempts go through all available ports18:40
Nishaor we can add a step to enable one of the port to PXE and create a port for it18:40
NishaI am not very sure if PXE state shall work for all deploys, but i think so18:41
dtantsurrloo, round, ceil and floor all are called "rounding" actually: http://en.wikipedia.org/wiki/Rounding18:41
dtantsurif you do insist, I will change, but please provide me with the correct variant :)18:42
jbjohnsoNisha, we have analagous capability, but it just seems like the system has to have a fair amount of accurate config as a prereq and would not be able to cover use of off the shelf adapters without particular UEFI drivers..18:42
jbjohnsoNisha, well, about the disk side...18:43
Nishai didnt get ur statement18:43
jbjohnsoNisha, well, like put a solarflare adapter into the server18:43
jbjohnsonow what will the inventory do....18:43
jbjohnsoor perhaps more challenging, a Chelsio...18:43
linggaoNisha, jbjohnso, in our case, pxe go through all the macs, but only one (hopefully) responded from the server side. that is the one we need to put in the port table for the node.18:44
rloodtantsur: yes, but using 'round' isn't specific enough. round up, round down, round... if you want to leave it as you have it then18:44
jbjohnsolinggao, if we must be as boring as that, true.  However we also don't need to do just one...18:44
rloodtantsur: based on http://en.wikipedia.org/wiki/Rounding#Rounding_to_integer, it is round towards zero I think.18:44
jbjohnsothat was one mistake I made in our implementation18:44
*** notarealperson has quit IRC18:44
jbjohnsoyou can have multiple fixed-address entries mapping to the same value18:44
Nishajbjohnso: i didnt get :)18:45
jbjohnsothat would mean you didn't have to pick the right one, any that appeared in inventory would work18:45
*** wanyen has joined #openstack-ironic18:45
dtantsurrloo, it seems to me we try to do to much to a single comment :)18:45
jbjohnsoof course, the inventory may likely not cover add-in cards that are not options from the server vendor...18:45
Nishawanyen, i am talking to jbjohnso and linggao18:45
jbjohnsoUUID would however cover all if we so enabled ;018:45
linggaojbjohnso, let's not get there :). I know you love UUID.18:46
wanyenwhat is the subject for discussion?18:46
jbjohnsoon the disk piece, I've not had much use for out of band assessment.. mainly because I get interested in vpd page 80 as a way to corrrelate SAN hosted volumens to deployment view..18:46
rloodtantsur: maybe I've worked on too much s/w where the kind of rounding made a difference :-(18:46
Nishawanyen, discussion gng on for automatic port create18:46
dtantsurheh, that's possible :)18:47
devanandaback. but on really slow connection, it seems18:47
Nishajbjohnso, linggao, so is it fine to do auto-creation of ports based on state18:47
Nisha?18:47
dtantsuranyway, my brain refuses to work and I already nearly written "code looks code" in one review :) so see you tomorrow18:47
dtantsurdevananda, hello and good buy :)18:47
linggaoNisha, no, because it is not reliable.18:47
jbjohnsofyi, Iconfess to not be tracking the ironic data model closely18:48
Nishalinggao, why do you think its not reliable18:48
wanyenwhat are the concerns of doing port create?18:48
rloonight dtantsur!18:48
jbjohnsois it arbitrarily many ports or one port per server?18:48
*** dtantsur is now known as dtantsur|afk18:48
jbjohnsoguess the question is whether we are talking about a not as awesome as it could be, but better than nothing for now..18:49
linggaojbjohnso, to register a bm node, Ironic needs to know the bmc ip/username/password for BMC access, cpu, memory and disk size for scheduling, mac for deployment.18:49
jbjohnsodepending on the overall architecture...18:49
jbjohnsoit needs to know the disk size in advance?18:49
Nishadisk size can be retrieved18:49
linggaoNisha proposed a design spec to get cpu, memory and disk size and mac out-of-band18:49
jbjohnsowhat if you have a mix of direct attached and san volumes, or in general a plurality?18:49
linggaoyes, for scheduling purpose.18:50
jbjohnsolinggao, when you say 'mac for deplayment, must it be singular?18:50
linggaoIt can be multiple, I think.18:51
jbjohnsohmm, would it be so bad if multiple macs were crammed in to cover an 'any of the above scenario'18:51
Nishayes , a node can have multiple ports today also18:51
jbjohnsoa common scenario there would be pxe boot over what is intended to be a redundant bond..18:51
jbjohnsoeither nic as a singular item can function good enough to pxe without minding the bond nature18:52
*** vinbs has quit IRC18:52
linggaoNisha, I think we can put multiple all of them have connection to the conductor node?18:52
jbjohnsoI'm still not convinced that any mac inventory scheme will be robust and comprehensive in the face of arbitrary server and/or adapter vendor, but it would be better than nothing18:53
linggaolet's ping devananda18:53
Nishai meant for BM node, we can have multiple ports today too18:53
wanyenI know that Nova virtual instance alow multiple ports18:54
jbjohnsoNisha, and tehy can have a many to one mapping and nothing consideres an error if some of those never come to fruition?18:54
Nishayes, true18:54
Nishawanyen, i have tried on ironic node also18:54
*** [1]Sam_S has joined #openstack-ironic18:55
jbjohnsohmm, so as a 'best effort', cram as many candidates as can be flagged so that if any of them crop up in the right place at right time, golden18:55
Nishaironic node can be associated with multiple ports today also18:55
jbjohnsothough if you are bootstrapping the boot from a fake usb stick, that wouldn't fly18:55
jbjohnsothe mechanism in that case would specifically have to know 'the one' without much chance to discover18:55
*** dwalleck has quit IRC18:56
devanandalinggao: hi!18:56
jbjohnsoof course, if something is trying to apply distinct configuration to each port and this data is shared with such a facility, that scheme wouldn't be too happy either18:56
Nishaif the "extra" field in the port object is populated with the state of the MAC, then it can be helpful for deploy to chose the MAC18:56
linggaodevananda, Nisha jbjohnso and wanyen are discussing the auto discovery of the node properties.18:56
devanandagreat!18:57
*** Sam_S has quit IRC18:57
*** [1]Sam_S is now known as Sam_S18:57
*** max_lobur has quit IRC18:57
linggaodevananda, one question is that node in Ironic can asscociate with many ports (macs)18:57
wanyenwhat kind of MAC state?18:57
linggaowhy is that?18:57
jbjohnsowanyen, I think a better word is mac 'role'18:57
wanyenI see.18:58
devanandabecause a physcal machine may have more than one NIC18:58
Nishawanyen, each NIC on the BM has state associated (disabled/PXE/iSCSI).18:58
jbjohnsoIf the data is only to facilitate deployment in a manner that won't step on other stuff18:58
devanandaNisha: i don't know what these states are that you refer to18:58
linggaodevananda, should we put all the macs in the port talbe  for the node?18:58
devanandalinggao: yes18:58
jbjohnsothen you could just say 'whatever mac you see, go for it, here's all the possibilities'18:59
devanandalinggao: ironic (will) inform neutron of the MACs for the node when it is placed on a network18:59
linggaodevananda, I thought the ports in the port talbe is for install nic only.18:59
jbjohnsoI need to add the memory inventory to pyghmi... well all the inventory...18:59
devanandalinggao: so ironic must know all data-plane MAC addresses for that node in order for it to be properly connected to tenant network18:59
Nishadevananda: when we get firmware settings of the NICs, we get these details too18:59
Nishaby default, i have seen only one nIC having PXE state and rest as disabled19:00
linggaodevananda, even if the port is disabled from the firmware?19:00
devanandalinggao: ironic also informs neutron of the MAC address(es) to which DHCP should be honored,  and which are expected to PXE boot19:00
*** ekarlso has quit IRC19:01
jbjohnsoNisha, devananda though I think the 'role' information is at some significant risk for being inadequate, and to some extent mac inventory at all even amongst the most careful non-bladed designs..19:01
klindgrenHello - I am working on getting the anvil project to build packages for ironic.  I have a working example - but am hoping for some input on the spec file: https://review.openstack.org/#/c/100693/2/conf/templates/packaging/specs/openstack-ironic.spec19:01
devanandalinggao: if the NIC does not need to be placed on a network, and will not be handling traffic, ironic does not need to know about it19:01
devanandalinggao: however, that gets potentially awkward. what if the tenant turns that NIC on in firmware?19:01
jbjohnsobladed designs can guarantee by virtue of having proprietary only io adapters..19:01
linggaodevananda, how does Ironic know which MAC address to use when informing Neutron about dhcp.19:01
devanandaklindgren: hi! can you give us a link / some background on what Anvil is?19:02
jbjohnsodevananda, fyi, I think this might be an interesting place to consider the role of MAC in a mandatory prereq for deployment as a stop-gap19:02
devanandalinggao: right now it's naive -- it just says "all of them"19:02
devanandajbjohnso: i *think* it is. I think a node with no macs can not be deployed to19:02
jbjohnsodevananda, as fixed target identity without foreknowledge of mac is quite feasible19:02
devanandajbjohnso: though i'm not sure we're enforcing that in the right places19:02
jbjohnsodevananda, well, that's because the tooling isn't cool enough then19:02
devanandajbjohnso: no. we just haven'maybe t aded a check for that inthe right spot. the data's al lthere to do it19:03
jbjohnsodevananda, incidentally, my scheme here is why I did RFC 6355 and got it into UEFI and WHQL specs19:03
jrolldevananda: (and friends): http://developer.rackspace.com/blog/how-we-run-ironic-and-you-can-too.html19:03
jbjohnsodevananda, so that I don't ever need to care about mac addresses, but that scheme can map to ipv4 as well19:03
devanandajroll: awesome, thanks! /me reaeds19:04
jbjohnsoat least to bootstrap deployment for the 'deployment' nic19:04
devanandaklindgren: hello?19:04
*** ekarlso has joined #openstack-ironic19:04
linggaoNisha, in that case, we can put all the mac addresses in the ports table.19:04
wanyenthat's great!19:05
NishaOk, with the states associated?19:05
linggaoNisha, that's your choice.19:05
Nishastates will go in port object extra field if required19:05
wanyenI think we just ut all the ports19:05
Nishaok19:05
Nishalingago can we now discuss disk inventory comemnt too19:05
jbjohnsowanyen, I think I agree with that unless there is fear of trampling some non-deployment config hook19:05
linggaoNisha, for disk size, I saw two comments.19:05
linggaoone from jbjohnso19:06
klindgrendevananda, sorry - was getting some lunch19:06
linggaoone from dguerri in the blueprint I pointed to you19:06
klindgrenAnvil is a project headed up by yahoo to help package openstack from source into rpm's currently but in the future debian packages as well19:06
jbjohnsoin the plurality case, I wasn't sure what you decide....  for that matter I am curious how the target selection scheme works (passing NAA or something like it or something else)19:06
linggaojbjohnso, are you saying that we cannot get accurate disk size from ipmi?19:06
klindgrenit also lets you specific the code code base to use and lets you do any custom patches on top19:07
Nishayes i saw them, but the example xml i pasted shows disk info19:07
jbjohnsolinggao, well, you can do *anything* over ipmi messages, but using OEM commands...19:07
jbjohnsolinggao, there are more usefully specific standard things (like inventory of all dimms by offering up the raw SPD)19:07
klindgrendevananda, http://anvil.readthedocs.org/en/latest/ for some docs19:08
jbjohnsolinggao, I'm unaware of a specific structure that can be related to disk attributes like say NAA or WWNN+LUN or what have you)19:08
*** theDavidAiken has quit IRC19:08
jbjohnsoso such inventory to my knowledge exists as vendor-specific vocabulary19:09
linggaoNisha, my point in the comment is that since we cannot or hard to  get correct info, I prefer we just display the inventory (properties), do not auto update the node.19:09
jbjohnsoto the extent that vendor specific vocabulary can possibly be avoided, I get happier...  for disk if it must be know whithout ever booting an in-band assessment agent, there isn't a rosy picture to be had19:09
linggaoNisha, as jbjohnso mentioned, there is no standard languange to pass for disk.19:10
jbjohnsoin-band assessment can be very well informed through nicely neutral udevadm friends19:10
*** hemna has joined #openstack-ironic19:10
linggaojbjohnso, there will be a in-band discovery in IPA.19:11
Nishalinggao, jbjohnso, but same can be retrieved thru iLO19:11
wanyenhowever, if a vednor BMC has the capability to report total disk size , we should allow vendors to make use of that data19:11
jbjohnsoof course even memory is not without it's faults.  Inventory won't be accurate after manipulating the dimm contents but before firmware boot19:11
jbjohnsoNisha, the same what can be retrieved?19:11
jbjohnsonice thing about in band assessment is that it will never be cached data at time of retrieval19:12
Nishathe storage details19:12
Nishathe example xml i have pasted in the design spec resolution comments19:13
Nisha                    <PHYSICAL_DRIVE>                          <LABEL VALUE = "Port 5I Box 1 Bay 1"/>                          <STATUS VALUE = "OK"/>                          <SERIAL_NUMBER VALUE = "6SL7H2DP0000B41800T9"/>                          <MODEL VALUE = "EF0600FARNA"/>                          <CAPACITY VALUE = "558 GB"/>                          <LOCATION VALUE = "Port 5I Box 1 Bay 1"/>                          <DRIV19:13
jbjohnsoNisha, don't see wwnn+lun or naa in there ;)19:14
Nishawhat is naa?19:14
jbjohnsowell, it matters more with virtual luns19:14
jbjohnsowell, vrtual is a bad word19:14
Nishalogical drive?19:14
jbjohnsobut if you have a san controller and you create a lun19:15
Nishayes u can19:15
jbjohnsothen you can get a viable naa to identify it19:15
Nisha          <CONTROLLER>                <LABEL VALUE = "Controller in Slot 1"/>                <STATUS VALUE = "OK"/>                <CONTROLLER_STATUS VALUE = "OK"/>                <SERIAL_NUMBER VALUE = "PDVTF0BRH5L0EA"/>                <MODEL VALUE = "HP Smart Array P822 Controller"/>                <FW_VERSION VALUE = "4.68"/>                <CACHE_MODULE_STATUS VALUE = "OK"/>                <CACHE_MODULE_SERIAL_NUM VALUE =19:15
jbjohnsobut not so much a viable serial number19:15
jbjohnsoso that's the controller19:15
jbjohnsowell, specifically, a direct attach controller19:15
Nishai cant paste the complete xml here, too big :)19:15
jbjohnsoas opposed to a SAN controller (e.g. netapp or emc)19:16
jbjohnsoin any event, 'do not let the enemy be the perfect of the good' and all19:16
linggaoNisha, wait19:16
*** ellenh has quit IRC19:16
jbjohnsobut I guess people should be mindful that there will be circumstances beyond the reach of out-of-band inventory, even sticking with a server vendor that tries to do a pretty thorough job of it19:17
linggaoNisha, you can use http://paste.openstack.org/ to paste.19:17
jbjohnsoput in some SAN or pcie adapters and things can go all over the place quickly19:17
linggaoand put the link here.19:17
Nishaok.19:17
jbjohnsoand state can be stale and context impractical or inaccurate19:17
jbjohnsoof course, being at a vendor that also does it's best to assure that inventory is accurate I probably should not be so discouraging...19:18
Nisha:)19:19
jbjohnsothough we are doing some reduced cost offerings that eschew the expensive restrictions required...19:19
jbjohnsoto get the inventory 95% of the way there...19:19
jbjohnsoI just hate things where we can really only get 95% of the way there..19:20
Nishajbjohnso, linggao, anyway i have proposed as of now only the disk size as the property to be discovered19:21
Nishathat anyway is needed for scheduling properties19:21
jbjohnsoNisha, what do you do about plurality of volumes?19:21
jbjohnsooh, so memory isn't a scheduling property?19:22
jbjohnsooh, we are talking about disk volumes...19:22
Nishayes it is also19:22
linggaojbjohnso, memory and cpu are.19:22
jbjohnsook, but the comment was just talking about the only storage property of interest at the moment19:22
linggaoare you saying that memory is not accurate neither?19:22
jbjohnsolinggao, well, it's unlikely, but it can be inaccurate19:22
jbjohnsolinggao, an off system won't update dimm contents if a dimmi s added or removed19:23
jbjohnsobut that's probably enough of a corner case to not sweat too bad19:23
Nishathe storage property can be rediscovered for a node if storage is updated19:23
jbjohnsostorage fabrics can make the storage inventory a bit more sloppy19:23
Nishameans all the properties can be rediscovered19:23
jbjohnsoNisha, well, with the server off it will ramp up the memory controller enough to take stock?19:24
Nishajbjohnso, could u explain "plurality of volumes"?19:24
jbjohnsoNisha, you have 2 disks, which disk do you care about?19:24
devanandaklindgren: ok, got it. so - what are you lokoing for from us?19:24
devanandaklindgren: there are alraedy folks packaging ironic for deb/rh19:24
jbjohnsoyou have 2 local disks, they are to be raided but not raided yet, and you also have visibility let's say to 3 san volumes...19:24
klindgrendevananda, I didn't see anything from redhat.... but I did see stuff from suse19:25
jbjohnsoor no local disks but 3 san volumes with an intent to boot one particular one (and the 3 are spread across two discrete storage subsystems...19:25
Nishahow do we do manually today for ironic19:25
klindgrenthe spec is largely based upon suse's spec file.  More that the service names and packages seem correct19:25
*** hemna has quit IRC19:25
jbjohnsook, so just a 'helpful best guess'19:26
Nishahow does the admin choose them today when he configures manually19:26
jbjohnsonot intended to be perfect perfect19:26
jbjohnsoNisha, well, so one thing is whether it is manually configured or not19:26
jbjohnsoNisha, e.g. in the san case, we've done situations where software is auto-creating a lun with intent clear19:26
jbjohnsoNisha, and it relays that intent by flagging the NAA to the deployment tool19:26
jbjohnsoso the os deployment says 'hey, I should touch this one and only this volume'19:27
*** bandicot has quit IRC19:27
Nishaok19:27
devanandaklindgren: i'm not teh best person to ask about packaging -- GheRivero would probably be more help19:27
jbjohnsobut again, that's a scenario with very end to endautomation19:27
jbjohnsoso other environments may benefit from a best guess19:27
wanyenIronic does not support boot from SANyet.  Si, I think it should be covered by cinder and ironic discussion.19:28
Nishajbjohnso, i emant we can consider scenarios how disk size is manually provided today19:28
devanandaklindgren: i'm a little confused by this. why is it installed as "openstack-ironic-api" instead of "ironic-api" ?19:28
jbjohnsowanyen, does it support 'don't screw up visible san volumes?' ;)19:28
devanandaklindgren: oh - that's just the init script. nvm :)19:29
jbjohnsowanyen, e.g. an os deployment facility that is ruthless would ideally pick the local single hard drive over then 500TB san volume..19:29
klindgrendevananda, all of the openstack init script just have openstack-<project>-<service>19:29
devanandayep yep19:29
devanandai misraed and thougt that was the bin/* name19:29
klindgrenah yea - that wouldn't be good19:30
klindgren:-)19:30
devanandaklindgren: this doesn't seem to contain any of the non-python deps19:30
devanandaklindgren: eg, tftpd, tgtadm, etc. should it?19:30
devanandaklindgren: or is that being left to the deployer to know what to install to get the conductor working in their config19:30
devanandaas some of those are optional // have multiple packages which could satisfy the requirement19:31
wanyenso how does in-band discovery solve all disk size problems?19:31
devanandanisha, wanyen, jbjohnso - one problem with reporting disk size(s) is modelling the entire disk topology. available storage is variable if there is a hardware RAID controller19:31
jbjohnsowanyen, it probably more helps a scenario which I suspect is not covered, automated end to end configuration and the ability of external components to relay identifiers and be correlated19:32
linggaoNisha, again. Since there is no standard language in IPMI to parse disk. I think let's not get too aggressive here to auto-update-node. We just display the the hardware inventory as a MangementInterface function.19:32
jbjohnsolinggao, and the lack of a standard vocablary, though that can be mapped..19:32
klindgrendevananda, actually - thats a good catch - it should spell out all the requirements that are needed for boot -outside of python19:32
jbjohnsoeach vendor would have to provide their own layer and ideally a user need not fret about manually selecting the layer19:32
anteayaJayF: good that you got your voice out there19:32
linggaojbjohnso, and accuracy as you mentioned is another problem.19:33
anteayabefore the thundering herds ignore it19:33
devanandaklindgren: happy to help19:33
*** vinbs has joined #openstack-ironic19:33
JayFanteaya: I am a buffalo19:33
JayFanteaya: and I herd that19:33
jbjohnsolifeless, yes, though it might be a 'better than nothing' approach for less ambitious circumstances... (to be devil's advocate since I really don't live and breath the openstack infrastructure yet)19:33
*** sacharya has joined #openstack-ironic19:34
jbjohnsolinggao, I meant you...19:34
harlowjadevananda a quick summary of anvil, anvil sucks down all the various openstack components, analyzes there requirements files and finds the master list of requirements that works across all the downloaded compoents, then  can build (using these spec files) a unified set of rpms (in the future debian?) that are built from the downloaded components (and the unified requirements master list), and then u can put those rpms in yum19:34
harlowja repo somewhere and later install from that19:34
jbjohnsoI should really start typing more than two chars before tab..19:34
wanyenLinggao- I  think auto update the node or not could be a driver choice.19:34
harlowjadevananda yahoo uses it and godaddy (and others?) for building openstack components from git into packages19:35
harlowja*in an automated way*19:35
klindgrendevananda, is their a list of those external requirements somewhere that I could look at? (tftpd, tgtadm)?19:35
*** bmahalakshmi has quit IRC19:35
harlowja*it also has capabilities to install those rpms locally and such for developers (if they want to go this way)19:35
linggaojbjohnso, :)19:35
linggaojbjohnso, thanks for all the info you have given us.19:36
*** sysexit has quit IRC19:36
devanandaklindgren: take a look in devstack .... :(19:36
harlowjahttp://anvil.readthedocs.org/en/latest/topics/summary.html (is a good summary)19:37
devanandaharlowja: thanks for the summary!19:37
Nishalinggao, jbjohnso, as wanyen said it can be driver choice to auto update the node for disk size19:37
harlowjadevananda np :)19:37
Nishais that fine?19:37
*** vinbs has quit IRC19:38
linggaoNisha, can we split it into two parts. First, make display working.  Then propose auto-create and auto-update. For auto discovery, discovering and configuring BMCs may be very important too.19:39
Nishamake display working means?19:39
jbjohnsoon that subject, if, hypothetically, something cropped up that could provide that service as a long-running component19:39
jbjohnsowould that be of interest?  to show autodetected pxe and service processors?19:40
linggaoNisha and wanyen, expecially there will be auto discovery of the node properties in-band in IPA soon.19:40
jrollheh19:40
jroll"soon"19:40
linggaojroll, I made a promise for you, lol. Do not sweat.19:41
wanyenThe out-of-band discovery is an alternative to IPA in-band discovery.19:41
jbjohnsofyi that is my current project to extend confluent to be able to detect various management and pxe things (and to control the latter)19:41
jrolllinggao: :)19:41
linggaowanyen, I understand, if it can get accurate information.19:41
jbjohnsowell, I guess control both...19:41
wanyenit is useful for drivers that uses out-of-band operatins19:41
wanyenI like to undersatdn how in-band discovery solves all the different storage configuration, e.g., SAN, RAID, ..etc19:43
jbjohnsowanyen, well, two pieces19:43
jbjohnsowanyen, for one, it eliminates a great deal of vendor to vendor code branching19:43
jbjohnsothree pieces19:44
jbjohnsofor another, the in band scheme is very much what you see is what you get at the moment of collection with a pretty strong guarantee, since storage inventory tends to be a push from storage adapter to service processor..19:44
jbjohnsoand finally, the inventory doesn't have every attribute that might be relevant for safe deployment anyhow in an orchestrated environment19:45
linggaoI think that's all handled by OS right?19:46
jbjohnsoout-of-band is proprietary agreements between HCA and controller vendors and service processor vendors, whereas in-band is highly standard SCSI and FCP thingamajigs.19:46
wanyenHow would in-band discovery know which SAN voluem to use?19:46
linggaobrb19:46
jbjohnsowanyen, in a wider orchestration sense, the lun proviosioning software talking to netapp or emc has a chance to pass a recognizable unique id to the deployment facility19:47
wanyenYes.  out-of-band discovery is meant for vendor-specific drivers19:47
jbjohnsowanyen, I haven't seen a host service processor ever provide a very viable inventory of SAN volumes19:48
wanyenWe want to support SAN volume through Cinder so Cinder wil choose a vloume.19:48
* linggao back19:49
wanyenThat's teh reason I think SAN will be a subject that needs to get Cinder involves19:51
jbjohnsoSo in short, there's a data model that can either be blank or have some driver driven guesses that can then be fixed manually19:53
jbjohnsoI suppose that's better than being unhelpful19:53
Nishajbjohnso: linggao so you are ok with the given proposal for disk inventory?19:54
Nishalinggao: if yes, we move to next comment. that is to standardize the CLI along with node-create/node-update19:55
jbjohnsoI only describe my thoughts, I make no judgement calls ;)19:56
Nishalinggao: there?19:57
jbjohnsoI have more ambitious desires, but that does not preclude me being accepting of other solutions if I think they wouldn't interefere with a better way down the road19:57
linggaoNisha, from ipmi stand point, I do not feel parsing the text that are not standalized. I am in favor of just displaying the hard inventory for Juno release. But I can be flexible on auto update if you think iLO can give you accurate info.  Let's see what other folks say.20:00
*** sysexit has joined #openstack-ironic20:00
Nishaipmi and ilo will get sam information from a baremetal20:00
Nishasame*20:01
Nishalinggao: i think even ipmi has documented health information publicly available.20:02
jbjohnsoI need to create vendor extensibility and add IBM extensions as an example to pyghmi20:02
jbjohnsohealth or inventory?20:02
Nishathis information is retrieved from health information only20:03
jbjohnsoNisha, the disk size is health?20:03
jbjohnsoI would have probably considered 'get sensor reading' as directed by the SDR as health-y stuff20:03
Nisha:) i didnt mean that20:03
linggaoNisha, these are different categories.20:04
NishaOk i think probably ilo and ipmi differs there20:04
jbjohnsoand get fru as the mechansim to get fru data with oem content (though we do have oem commands for some health and inventory stuff)20:04
Nishayes i know OEM comamnds are there20:04
jbjohnsobut I was going to model under 'get_sensors' (and by extention 'get_health') a lookup table based on vendor (which would also be fed product id if it matters to said vendor)20:05
Nishawhich get health information, since i dont understand the raw imput/output much for ipmi i am not sure if it has disk information or not20:05
jbjohnsofor any 'health' type data whatever thatmeans20:05
JayFThere's kinda an interesting dependency being talked about in some of this -- how do you intend the BMCs themselves to get IPs in this kind of discovery context?20:05
jbjohnsofor inventory, same deal, an oem hook to go (with raw sdr and fru available in both cases)20:05
Nishaok20:06
jbjohnsoJayF, if we are talking about utterly automagic, the way we have done it is one of two ways20:06
jbjohnsoJayF, the vendor agnostic way is 'pxe first', where the service processor has no or not viable or just don't care config20:06
lifelessMy plan for BMC ip management is to register the BMC's with neutron directly20:06
lifelessDC ops get BMC MAC, API call to neutron to create a port on the BMC network. Done.20:07
jbjohnsothe other is to scan and/or sense the presence of entities on network segments20:07
JayFjbjohnso: Yeah my main problem with discerning that is how you tie BMC IP <> Hardware in the case20:07
JayFjbjohnso: like if you PXE boot the hardware we're running, there's no way to determine BMC IP from a running OS20:07
jbjohnsoJayF, in the pxe first case, by using ipmitool commands to configure the service processor the way you know it should be20:07
JayFjbjohnso: assuming your BMC is truly isolated, that doesn't work20:07
jbjohnsoJayF, determining is lame, focing the correct configuration is good20:07
jbjohnsoJayF, when you say 'truly' isolated20:08
jbjohnsoJayF, I presume you mean no KCS or BT relation?20:08
jrollseparate physical BMC network.20:08
jrollas you should20:08
jrollbecause every BMC can be presumed to be insecure20:09
jbjohnsojroll, right, but that says nothing about whether ipmitool on the node can work over KCS or BT20:09
jrollidk what KCS or BT are20:09
lifelessMe neither20:09
lifelessI was just about to ask20:09
jbjohnso/dev/ipmi020:09
jbjohnsomodprobe ipmi_devintf20:09
lifelessoh, local mode?20:09
jbjohnsoand maybe ipmi_si (though that is likely compiled in)20:09
jbjohnsoright20:09
jbjohnsoso you pxe boot node20:09
devanandarussell_h: nice dash board integration! also, I didn't know ya'll had remote usage monitoring going on yet.20:09
lifelessSo more recent hardware is locking access to the BMC locally down20:09
JayFjbjohnso: that's blocked via firmware in the devices we're using20:09
lifeless(e.g. moonshot)20:09
jbjohnsothen node knows what the BMC is supposed to be configured20:09
jbjohnsoin a case where KCS/BT is forbidden from working, then you must rely upon service processor first20:10
jrolldevananda: before this project, russell was a manager for our cloud monitoring product :P20:10
jbjohnsoservice processor first is something that is far lest standardized20:11
jbjohnsobut for example, you scan for service processors as they are accurately configured20:11
jrolldevananda: it's just a little agent that you install: http://www.rackspace.com/cloud/monitoring/20:11
jbjohnsoand then for the candidates, you allow for manual or automatic relationship20:11
jbjohnsoe.g. we identify the attached switch port and based intended service processor based on that in xCAT20:12
devanandajroll: ah, nice20:12
JayFdevananda: a large number of us on the project were former Cloud Monitoring (me, russell, paul)20:12
jbjohnsothen we connect out of band to said piece and inventory gives us hint for correlation (e.g. UUID as it appears in DMI table)20:12
JayFdevananda: honestly, running that system made me wish I had real hardware available via API... so here we are :)20:12
jbjohnsoso that's the service processor first scheme20:12
JayFjbjohnso: that would work, like using a serial in the fru data to map in-band to out-of-band20:13
jbjohnsoJayF, well, the best one is 'get system uuid'20:13
jbjohnsoJayF, since that readily appears in a PXE discover packet, you can make the bind without ever entering a kernel20:13
*** hemna has joined #openstack-ironic20:13
jbjohnsoin fact, that sort of discovery (where the binding appers after the pxe discover is sent just in time for the offer) is one of the things I'm gunning for in my toy20:15
jbjohnsoI clearly should have played with more conventional toys in my childhood...20:15
jbjohnsoJayF, there will be of course be two distinct cases driving the need for node first and service processor first20:16
NishaThanks for the discussion guys , but are we OK with the given proposal or you see modification required for disk size?20:16
jbjohnsoJayF, node first for cases where the service processor might not bereachable by default until configured in band20:16
jbjohnsoJayF, and service processor first for less open ended out of band state (and in fact mandated by architectures that refuse in-band)20:17
jbjohnsoservice processor first does require something to understand some proprietary behavior and vocabulary at the moment20:17
jbjohnsowell, except for manually configured targets20:18
jbjohnsoe.g. in the IBM case, understanding how it behaves with respect to SLP and what attributes are used and what default credentials are to be employed and what protocols are enabled/disabled by default20:18
jbjohnsodefault credentials can have an static, algorithmic, or user by user customized situation20:19
jbjohnsoanyway, I'm manifesting uncategorized detected elements in my toy under a '/detected/' collection20:19
jbjohnsowhen something enters the collection, it is to be vetted against enclosure and network identifier maps to see if it matches something20:20
jbjohnsoif match, automagic happens and you have your node ready to go one way or the other20:20
Nishaok, but we can under properties even20:20
jbjohnsoJayF, I have spent an unhealthy amount of time living in the world of cardboard box to manageable for thousands of systems...20:21
*** sysexit has quit IRC20:22
linggaoNisha, I am thinking of how end user is uisng this function.20:22
*** dwalleck has joined #openstack-ironic20:23
linggaoNisha, user run  ironic node-update, then you have to tell them that the disk size is just the best guess.20:23
linggaoNisha, then tell them to run IPA node discovery to get it updated.20:23
Nishahmmm if u want a manual step here by an admin then we can have all the disks details in a sub-dictionary in properties20:24
linggaomy question is why bother have the first step?20:24
Nishathen admin can select from the sub-dictionary and manually assign disk size as he does today20:25
*** ellenh has joined #openstack-ironic20:26
jrollI'm of the opinion that if you're running IPA, you won't be doing any OOB discovery20:26
Nishathe disk properties can be rediscovered if required during deploy (thats what i understand you meant by having "run IPA node discovery to get it updated")20:27
jrollregister a node, Ironic PXE boots IPA, IPA sends back hardware info20:27
JayFjroll: there will have to be some interaction with OOB though20:27
jrollIronic optionally shuts the node back down20:27
jrollfor why20:27
jbjohnsojroll, I think that's the most robust strategy at least20:27
JayFjroll: to map OOB interface information (what is your BMC IP?) to IN-Band information20:27
JayFjroll: ironic can't 'shut the node back down' if it knows nothing of the bmcs20:27
wanyen<Jroll> exactly.  If a user eitehr choose IPA or OOB driver20:27
jrollJayF: you register BMC IP when registering the node20:27
jbjohnsoJayF, though that can be done in the pre-boot phase20:27
JayFjroll: then it's not discovery20:27
JayFjroll: it's only slightly less manual at that point than what we've already done20:28
devanandaregarding using "ironic node-update" to initiate discovery -- this doesn't make sense to me20:28
jrollJayF: everyone else is talking about "when you register a node, it discovers hardware"20:28
JayFoh. that's less exciting.20:28
devanandacould someone explain how that is being proposed to work?20:28
*** blamar has joined #openstack-ironic20:28
jrollJayF: I'd rather have "when you plug in a new node, it self-registers"20:28
JayFjroll: +120:28
jrollJayF: but that's harder20:28
jrollJayF: because auth20:28
jbjohnsojrist, JayF well, we have that model operational in xCAT....20:28
devanandajroll: so, auth. "autodiscover new hardware" is what everyone wants20:29
jbjohnsojroll, I could chat all day about that20:29
devanandababy steps20:29
devanandalet's go first for "enroll minimal info, let irnic *interrogate* the hardware"20:29
JayFI think the agent is incredibly well suited for that20:29
jrolldevananda: of course :) I'm saying we should start with "give ironic a BMC IP, let it figure everything else out"20:29
devanandato discover any additional properties20:29
jbjohnsoI favor formulaic datacenter description for large systems and automagically filling in the gaps20:29
devanandajroll: yes20:29
wanyen<deva> ironic node-update can be used to re-discover if hw changes20:29
JayFI just don't think we'd be as likely to gain benefit from it. But we're only one use case :)20:29
jrist:)20:29
devanandawanyen: how and why20:29
jrollJayF: our bootstrap script would be much smaller :P20:30
devanandawanyen: node-updaet is a means for the user to *update* the node. not request that smoe action be performed20:30
devanandawell. today it is20:30
devanandataht could change :)20:30
wanyen<deva>  if adding NICs or replace hardwae components20:30
devanandabut let me reword that20:30
* jroll hates the thought that hardware will be changed while registered in ironic20:30
devanandanode-update is a way for the user to pass known-information to Ironic20:30
jbjohnsoso if there was a service which gave a structure of detected elements (pxe and/or service processors, chassis managers, etc), who all might want to discuss that design?20:30
jbjohnsosince I'm in process of building such a capability now..20:31
jrolljbjohnso: so, regarding structure...20:31
* jroll finds something20:31
devanandawanyen: so if a NIC were replaced, I would use "irnoic port-update" to supply the new MAC address20:31
wanyennode-update does not do automatic discovery.  It only does that if "--discover" is specified20:32
devanandawanyen: if I need Ironic to interrogate the hardware because I do not know the new MAC address, I wold not use ndoe-update20:32
devanandaah, i see20:32
jbjohnsojroll, something?20:32
devanandawanyen: so i'm thinking of the REST API -- and the CLI as an extension of that. how does "--discover" look to the REST API ?20:32
linggaodevananda, Nisha proposed a design sepc that you wanted to take a look. In there it will use "ironic node-create" or "ironic node-update" command to put cpu/memory/disk/mac info for the node by querrying BMC under the cover.20:33
Nishadevananda : it will be like : ironic node-update <node_uuid> --discover <true/false>20:34
devanandathat's the CLI20:34
NishaYes20:34
wanyen <deva> NIC update is just an example,  Ther could be more hardware changes than just NIC.  So we thought provding "--discover" option is a convinent way to re-discover and update node properties.20:34
jrolljbjohnso: I can't find it :(20:34
devanandawhat is the proposed  REST API for this functin?20:34
linggaoThe issue with that is that you cannot get accurate disk size from out-of-band. jbjohnso has a long explaination to it.20:34
jrolljbjohnso: but with this review, we've been working on a giant json blob describing hardware: https://review.openstack.org/#/c/9284720:34
jrolljbjohnso: but I can't find what the output looks like at the moment20:34
NishaThe existing REST API patch and post will be modified for it20:35
adam_gShrews, ping20:35
devanandaNisha: modified how?20:35
NishaExample prototype looks like :20:35
linggaodevananda, besides, IPMI output does not have standard text for disks because of different vendors uses different text.20:35
Nisha1. node.create()20:36
Nisha2. call ManagementInterface() function20:36
Nishawhich updates the properties filed of the node object20:36
Nisha3. if create_ports option provided on command line, create ports for the mac addresses returned20:37
devanandaNisha: that's not the REST API either -- taht's the ConductorManager20:37
Shrewsadam_g: sup?20:37
devanandaNisha: how does this change -- http://docs.openstack.org/developer/ironic/webapi/v1.html#nodes20:37
NishaWhy, NodesController Class is under REST APIS, correct?20:38
devanandaNisha: do support a PATCH /v1/nodes/NNNN which will perform this function20:38
adam_gShrews, re: that tempest rebuild flag.. is it expected that rebuild is going to be supported across all ironic drivers?20:38
devanandaNisha: without breakign backwards compatibility20:38
Shrewsadam_g: no, which is why i added it20:38
Shrewsadam_g: oh, wait.... drivers....20:38
Nishadevananda: Thanks, i will add that to design spec20:39
devanandajroll: will IPA support rebuild --preserve-ephemeral?20:39
Shrewsadam_g: i don't see why not20:39
devanandajroll: eventually20:39
devanandaNisha: thanks :)20:39
jrolldevananda: I guessssssss20:39
lifelesstripleo depends on it20:39
jrolldevananda: I don't believe in --preserve-ephemeral, ideologically20:39
lifelessif you want to move to IPA being default...20:39
jrolldevananda: but we will support it20:39
Nishalinggao: devananda last comment on the design spec is to have standard CLI for it20:40
jrolllifeless: we will support everything pxe driver supports, no worries (even if I don't like it)20:40
NishaDo we really want to have one even when node-create and node-update are being modified to do so20:40
JayFand we /really/ don't like --preserve-ephemeral :(20:40
jrollJayF: that's just like, your opinion, man20:41
devanandaNisha: the CLI is an implementation of a python client which speaks to the RESTful API20:41
* Shrews loves that "ephemeral" is used for partitions that don't have to be ephemeral20:41
NishaYes20:41
JayFShrews: very yes20:41
JayFalso the entire concept of 'replace my OS, leave the data' is scary to me from an operational standpoint20:41
JayFif that's the model you want, put your data on cinder, and spin up a *new* node and attach your volume to it20:42
lifelessJayF: ever hear of cinder?20:42
Nishadevananda: But as per proposal we are modifying the node-create and node-update CLI with the options for discovery feature20:42
JayFbut it doesn't matter, as I said the other day I joined openstack much too late to have this argument20:42
lifelessJayF: this is the equivalent for LCD hardware20:42
lifeless bn;/.B9~'20:42
devanandaNisha: but your proposal does not describe how that is implemented on the REST API20:42
lifelessbah, sorry.20:42
JayFso I'm sure we'll take our medicine and implement that :(20:42
JayFlifeless: lcd hardware?20:42
lifelesslowest common denominator20:42
devanandaNisha: it says only "Modify existing PATCH /v1/nodes/patch to call new rpcapi function and the port-create functions."20:42
lifelesscommodity20:43
lifelessvs required a hardware SAN20:43
*** theDavidAiken has joined #openstack-ironic20:43
Nishadevananda: for my prototype i modified the "post" and "patch" methods20:43
devanandaNisha: please describve those changes in the spec :)20:43
NishaOk, will add that :)20:43
devanandaNisha: not just "call the rpc method" -- the spec need to describe what different API endpoints or functions are exposed20:44
devanandathanks!20:44
lifelessJayF: what rebuild --preserve-ephemeral does is the closest approximation we know of to cinder + attach.20:44
Nishaso a seperate CLI si not needed for this, correct?20:44
jrolllifeless: it's fine, we'll be implementing it. JayF is just extra opinionated today :)20:44
*** rch has joined #openstack-ironic20:44
devanandaNisha: changes to the python-ironicclient project (our CLI) will be required, yes20:44
Nishadevananda: sure will do that20:45
JayFlifeless: I disagree, but it doesn't matter, because the decision was made well before I was an Openstack contributer, so like I said I'm sure we'll end up implementing it whether we like it or not.20:45
* devananda needs to run and move car before gettign a ticket20:45
devanandabbiab!20:45
NishaThanks devananda jbjohnso linggao wanyen for the discussion20:45
linggaobye devananda.20:45
Nishavery late now, need to get some sleep20:45
lifelessJayF: I'd love to hear your suggestions for an alternative. Really - if we can do something better, lets.20:45
linggaothank you Nisha20:45
linggaogood night Nisha20:45
NishaThanks linggao20:45
Nishabye gn20:46
linggao:)20:46
lifelessJayF: but saying 'I hate X and waah waah it happened before I joined' is not constructive20:46
jbjohnsojroll, fyi, I was thinking a skeleton set of idenetfier data until fleshed out20:46
lifelessJayF: and its not inclusive20:46
JayFlifeless: Arguing about it when my opinion has no alternative other than 'we shouldn't do this at all' isn't constructive either :x20:46
jbjohnsojroll, an 'unknown' node may enumerate mac addresses, uuid, but wouldn't do an exhaustive inventory until categorized20:46
JayFlifeless: not trying to troll or being not constructive20:47
lifelessok20:47
lifelessso - we're still in the status quo - we don't have a better alternative20:47
JayFlifeless: so like I said, we'll end up implementing it. Other people need it, and it's important to us to support upstream even if our use cases don't always align.20:48
Shrewsadam_g: hrm, you raise an interesting point (rebuild is part of nova, not ironic), but it's the ironic driver that actually implements the rebuild (and thus a feature of ironic). I can't make up my mind if that should be a tempest config option of compute or baremetal ...20:48
adam_gShrews, is there any reason to skip it currently?20:50
Shrewsadam_g: but we DO need the flag so we can skip it when we test older stable releases (which we arent' doing yet)20:51
Shrewsso, stable/icehouse20:51
*** Nisha has quit IRC20:52
Shrewsadam_g: this was something devananda brought up yesterday, and mentioned here: https://review.openstack.org/#/c/97834/3/README.rst20:52
adam_gShrews, ah!20:52
Shrewsadam_g: i'm just flip-flopping on where it should reside now  :/20:53
Shrewsi can't think of a solid reason to not put it under compute now20:54
*** linggao has quit IRC20:56
adam_gShrews, you may want to get other opinions from the -qa folk.20:56
adam_gsomeone brought a loud pomeranian to this coffee shop. i need to relocate back home.20:57
*** jdob has quit IRC20:58
lifelessShrews: FWIW I want to add --preserve-ephemeral support to libvirt too20:59
jbjohnsoJayF, I'm largely thinking that it can be ignored and scrapped when better comes along and that as an alternative to completely empty values, it might not be shabby20:59
lifelessShrews: there was support for that in the original proposal, its just been ETIME since20:59
lifelessShrews: dunno if that helps20:59
jbjohnsoJayF, in other words, I'm not a fan either, but if I can ignore it, great (e.g. my attitude toward OpenLMI implementation)20:59
jbjohnsoanyway, if I had some auto-detection stuff I'll maybe mention ithere, but I'll stop nagging people here with the minutia unless they want to in #confluent21:00
*** coolsvap is now known as coolsvap|afk21:09
*** Mikhail_D_ltp has quit IRC21:11
*** dwalleck has quit IRC21:12
*** dwalleck has joined #openstack-ironic21:12
*** dwalleck has quit IRC21:16
*** jbjohnso has quit IRC21:17
devanandaadam_g, Shrews: so there's another wrinkle in the where-to-put-tempest-preserve-ephemeral-config-option discussion: taht ironic is an admin-only API *and* the test exercizing this is conencting to Nova, not ironic21:21
devanandaShrews: so ya, explaining this to QA folks and getting their opinion is def the right way to go21:22
*** sysexit has joined #openstack-ironic21:24
devanandaJayF: fwiw, if you don't like something, work to change it in the minds of people. the code will follow.21:26
JayFdevananda: I agree and understand, but maybe not so good at making the "Openstack shouldn't do this at all, userspace tools should" argument :)21:27
JayFdevananda: BTW, thank you very much for being welcoming to us, it's a big day for those of us who've worked on this, and we've appreciated how welcoming the Ironic community has been21:28
JayFMy only curiosity is if we immediately win the 'largest deployment of Ironic' award ;)21:28
*** mrda-away is now known as mrda21:32
mrdaMorning Ironic!21:32
devanandaJayF: depends. how large is your deployment? :)21:32
devanandamrda: g'morning21:32
JayFdevananda: lets say it's hundreds of servers at the moment21:33
devanandalifeless: that actually might be a better question for you at this point ^ ?21:33
JayFjroll: do you think we can say the actual server count? seems relevant for proving a scaling model21:33
JayFjroll: and you're at least 90% less scaredy cat than I am about such things :)21:34
*** openstackgerrit has joined #openstack-ironic21:34
JayFdevananda: our existing environment is managing 170 servers, with two conductors, two apis, all control plane running on vms21:36
*** dwalleck has joined #openstack-ironic21:43
*** dwalleck has quit IRC21:44
lifelessJayF: I can't really say :P - but I can say that our commercial edition is targeting multiple K's of servers.21:46
lifelessJayF: I can't really say because other teams are doing lots of scale testing etc21:47
lifelessJayF: and I'm not directly involved there - but I am with the overall arch21:47
JayFlifeless: that's fair. I think our intention is to get to multiple k's of servers too :)21:47
*** sacharya has quit IRC21:58
*** sysexit has quit IRC22:02
*** hemna has quit IRC22:08
*** hemna has joined #openstack-ironic22:10
*** davidlenwell is now known as davidlenwell_22:14
*** davidlenwell_ is now known as davidlenwell22:14
*** hemna has quit IRC22:25
*** ellenh_ has joined #openstack-ironic22:32
*** ellenh has quit IRC22:33
*** ellenh_ is now known as ellenh22:33
*** blamar has quit IRC22:34
*** openstackgerrit has quit IRC22:34
*** 20WAAHXAJ has joined #openstack-ironic22:36
*** radsy has joined #openstack-ironic22:36
*** sacharya has joined #openstack-ironic22:37
*** sacharya has left #openstack-ironic22:37
*** wanyen has quit IRC22:39
*** openstack has joined #openstack-ironic22:51
*** ellenh has quit IRC22:59
*** ellenh has joined #openstack-ironic23:05
*** ellenh has quit IRC23:11
*** ellenh has joined #openstack-ironic23:14
*** ellenh has quit IRC23:16
*** 20WAAHXAJ has quit IRC23:29
*** openstackgerrit has joined #openstack-ironic23:31
*** dwalleck has joined #openstack-ironic23:33
*** Abhishek has joined #openstack-ironic23:44
*** ellenh has joined #openstack-ironic23:44
*** dwalleck has quit IRC23:49
*** mdorman has quit IRC23:51
*** dwalleck has joined #openstack-ironic23:51
*** hemna has joined #openstack-ironic23:52
*** dwalleck has quit IRC23:56

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