Friday, 2014-08-01

*** Haomeng|2 has joined #openstack-ironic00:03
*** Haomeng has quit IRC00:03
devanandaon the not-a-cmdb topic, what can we do to better facilitate integration with _existing_ CMDBs?00:04
devanandathat might help make the line clearer, too00:05
devanandajroll: that totally might be related to ironic. or it totally might be something else.00:06
jrollyeah :P00:06
jrollit just doesn't call it out00:06
devanandajroll: I suspect it's mroe of a "look at our cool thing which shows all your physical and virtual assets in one screen!"00:07
*** ellenh has quit IRC00:07
jrolldevananda: indeed00:08
* jroll has to run00:08
*** igordcard has quit IRC00:08
*** openstackgerrit has quit IRC00:16
*** openstackgerrit has joined #openstack-ironic00:17
*** killer_prince has joined #openstack-ironic00:20
*** killer_prince is now known as lazy_prince00:20
devanandahttps://www.openstack.org/vote-paris/Presentation/trusted-bare-metal-what-s-that00:22
*** ellenh has joined #openstack-ironic00:25
*** rameshg87 has joined #openstack-ironic00:49
*** chuckC has quit IRC00:51
rameshg87lifeless, hi00:51
*** rameshg87 has quit IRC00:56
*** rameshg87 has joined #openstack-ironic00:57
*** ellenh has quit IRC01:05
*** rameshg87 has quit IRC01:11
openstackgerritGhe Rivero proposed a change to openstack/ironic: WIP: '_periodic_last_run' missing (simple test)  https://review.openstack.org/11112601:14
openstackgerritYongli He proposed a change to openstack/ironic: Rewrite ironic policy to use the new changes of common policy  https://review.openstack.org/9773101:30
*** mitz_ has joined #openstack-ironic01:34
*** mitz has quit IRC01:36
*** lazy_prince has quit IRC01:44
*** nosnos has joined #openstack-ironic01:51
*** dkehn_ has joined #openstack-ironic01:55
*** dkehnx has quit IRC01:59
*** jgrimm has joined #openstack-ironic02:07
*** killer_prince has joined #openstack-ironic02:16
*** killer_prince is now known as lazy_prince02:16
*** eghobo has quit IRC02:17
*** rainya has quit IRC02:20
*** zz_nkubota is now known as nkubota02:21
*** aswadr has joined #openstack-ironic02:31
*** hemna has quit IRC02:33
openstackgerritGhe Rivero proposed a change to openstack/ironic: Update strutils from oslo-incubator  https://review.openstack.org/11114402:34
openstackgerritGhe Rivero proposed a change to openstack/ironic: Fix not attribute '_periodic_last_run'  https://review.openstack.org/11112602:40
*** chuckC has joined #openstack-ironic02:40
*** lazy_prince has quit IRC02:45
*** Haomeng|2 has quit IRC02:46
*** nkubota is now known as zz_nkubota02:51
*** killer_prince has joined #openstack-ironic02:55
*** rwsu has quit IRC02:55
*** killer_prince is now known as lazy_prince02:55
*** Zerpex has quit IRC02:58
*** Zerpex has joined #openstack-ironic02:58
*** jgrimm has quit IRC03:00
*** jgrimm has joined #openstack-ironic03:01
*** Haomeng|2 has joined #openstack-ironic03:10
*** nosnos has quit IRC03:13
*** nosnos has joined #openstack-ironic03:14
*** rainya has joined #openstack-ironic03:17
*** nosnos has quit IRC03:18
*** scubacuda has quit IRC03:25
*** nosnos has joined #openstack-ironic03:44
*** Haomeng|2 has quit IRC03:53
*** Haomeng|2 has joined #openstack-ironic03:55
*** eghobo has joined #openstack-ironic04:09
*** nosnos has quit IRC04:11
*** nosnos has joined #openstack-ironic04:20
*** Poornima has joined #openstack-ironic04:22
openstackgerritYongli He proposed a change to openstack/ironic: Rewrite ironic policy to use the new changes of common policy  https://review.openstack.org/9773104:23
*** pcrews has quit IRC04:52
*** ramineni has joined #openstack-ironic04:54
*** bmahalakshmi has joined #openstack-ironic04:58
*** lazy_prince is now known as killer_prince05:02
openstackgerritA change was merged to openstack/ironic: Updated from global requirements  https://review.openstack.org/10656905:06
*** zz_nkubota is now known as naotok05:09
*** jcoufal has joined #openstack-ironic05:16
*** bmahalakshmi has quit IRC05:27
*** k4n0 has joined #openstack-ironic05:28
*** rainya has quit IRC05:29
*** rainya has joined #openstack-ironic05:30
*** killer_prince has quit IRC05:31
*** rakesh_hs has joined #openstack-ironic05:35
*** nikunj2513 has joined #openstack-ironic05:37
*** bvivek has joined #openstack-ironic05:37
*** killer_prince has joined #openstack-ironic05:41
*** killer_prince is now known as lazy_prince05:41
*** rainya has quit IRC05:59
*** lynxman has quit IRC06:03
GheRiveromorning all!06:04
*** lynxman has joined #openstack-ironic06:05
GheRiveroCan I get some love for https://review.openstack.org/#/c/111126/ ?06:07
openstackgerritOpenStack Proposal Bot proposed a change to openstack/ironic: Imported Translations from Transifex  https://review.openstack.org/11086006:10
*** eghobo has quit IRC06:32
openstackgerritDavid J Hu proposed a change to openstack/python-ironicclient: Add keystone v3 CLI support  https://review.openstack.org/11117506:34
Haomeng|2GheRivero: morning06:36
Haomeng|2GheRivero: sure, let me help to review06:37
Haomeng|2GheRivero: :)06:37
Haomeng|2GheRivero: Thanks for the patch, code lgtm, and left some nits with the commit message.06:41
GheRiveroHaomeng|2: yeah, the commit message, it was like 4am for me so I doubt the message make any sense at all :)06:51
Haomeng|2GheRivero: :)06:52
Haomeng|2GheRivero: ok, that is fine with me06:52
*** radsy has quit IRC06:52
ZerpexMorning people - I'm trying to deploy a server using ironic - but every time I get:06:53
Zerpex2014-08-01 08:25:51.368 5421 INFO nova.filters [req-4a372c33-4219-45ed-a96b-371860f26ba3 e37d75eaf5dd4b7084ab9ef75087502d 5e4448cf9b524d16a7b89af6c6669311] Filter ComputeFilter returned 0 hosts06:53
Haomeng|2Zerpex: morning06:53
Zerpexhi again Haomeng|2 :D06:53
Haomeng|2Zerpex: :)06:53
Haomeng|2Zerpex: can you show your node and flavor and  properties06:53
GheRiveroand  nova hypervisor-stats06:54
Zerpexhttp://snaps.lucasrolff.com/ie1s47tw1706v1t.png is the node and flavor06:55
Haomeng|2yes, should be some not maching06:55
*** jgrimm has quit IRC06:56
Zerpexhttp://snaps.lucasrolff.com/g2o0q37pssyobwi.png is the hypervisor stats.. but seems like that is the current machine I'm on (controller1) and not the actual 10.1.30.105 node06:57
Haomeng|2Zerpex: did you set ironic scheduler in nova.conf?06:57
ZerpexYep06:57
Zerpexscheduler_host_manager=ironic.nova.scheduler.ironic_host_manager.IronicHostManager06:57
Haomeng|2Zerpex: looks like there is no 'arch' with your node attributes06:58
Zerpexshould be under "properties" or instance_info ?06:58
Haomeng|2Zerpex: let me check the devstack scripts, my env is down, can not check my node attributes07:00
Haomeng|2https://github.com/openstack-dev/devstack/blob/master/lib/ironic#L35707:01
Haomeng|2Zerpex: ironic should have cpu_arch=x86_64 attribute I think to match flavor's ext data07:02
Zerpexcool - will try adding the info as in that line!07:02
Haomeng|2Zerpex: ok, try again, and good luck07:03
Haomeng|2Zerpex: I think that should be default flavor filter enabled to select the nodes07:08
Haomeng|2Zerpex: if it is working now?07:10
ZerpexCurrently testing - need to delete the old node07:10
Haomeng|2Zerpex: ok07:12
Haomeng|2Zerpex: you can run "ironic node-update" to add/update the node attributes07:13
Zerpexstill not working, bah07:17
*** bvivek has quit IRC07:19
Haomeng|2Zerpex: not the node has cpu_arch attribute, right?07:19
Zerpexhttp://snaps.lucasrolff.com/ntsder4fmg231so.png07:19
Zerpexyap07:19
*** viktors|afk is now known as viktors07:20
Haomeng|2Zerpex: yes, the properties looks fine07:21
Haomeng|2Zerpex: for this - http://snaps.lucasrolff.com/g2o0q37pssyobwi.png, strnage, why runing-vms=2?07:23
Haomeng|2Zerpex: you have launched 2 vms already?07:23
ZerpexHaomeng|2: back in time when I wasn't using ironic - yes - i launched two VMs on the controller node.. not on the 10.1.30.105 node - which also surprises me, because I would assume the hypervisor-stats would show my ironic node07:24
Haomeng|2Zerpex: did you have multi compute nodes?07:25
Haomeng|2Zerpex: I understand you have multi hypervisors including ironic and others07:25
ZerpexI used to have a compute node, which I removed (also wondering why it shows two vms when I deleted them :D)07:26
Haomeng|2so have to check ironic hyper-visior status07:26
Zerpexand now I just have the controller server, and 1 ironic thing07:26
*** dtantsur|afk is now known as dtantsur07:26
Haomeng|2Zerpex: maybe nova database is wrong07:26
dtantsurMorning everyone!07:26
Haomeng|2dtantsur: morning:)07:26
ZerpexHaomeng|2: need to find a way to clean that then07:28
Haomeng|2Zerpex: I understand you have old nova.conf, and modified it to enable ironic, right?07:29
Zerpexyeap07:30
dtantsurHaomeng|2, great job with Ceilometer patch!07:30
Haomeng|2dtantsur: thanks for you kindly review and valuable comments again:)07:32
dtantsurnp :)07:32
Haomeng|2dtantsur: :)07:32
openstackgerritYongli He proposed a change to openstack/ironic: Rewrite ironic policy to use the new changes of common policy  https://review.openstack.org/9773107:32
Haomeng|2dtantsur: one question about our ironic scheduler filter07:32
Haomeng|2dtantsur: I understand the logic is we use default nova flavor filter to checkout the baremetals from ironic nodes which has cpu_arch value matches the flavor ext cpu_arch data, right?07:33
dtantsurHaomeng|2, I'm not really strong here, but yes, should be07:34
Haomeng|2dtantsur: Zerpex encoutered the issue which ironic scheduler does not work, can not check out the ironic nodes07:34
Haomeng|2dtantsur: :)07:34
* dtantsur reading scrollback07:34
ZerpexEven when I do a "nova hypervisor-list" I don't see the machine either :/07:35
Haomeng|2Zerpex: you mean the output is empty with "nova hypervisor-list" command call?07:36
Haomeng|2Zerpex: should be a hypervisor which is ironic compute07:37
Zerpexnope - it shows the controller server07:37
dtantsurZerpex, I see several problems with http://snaps.lucasrolff.com/ie1s47tw1706v1t.png07:37
dtantsur1. Node.properties does not contain memory_mb, cpu_arch, cpus07:38
dtantsur2. local_gb = 60, in flavor disk = 4007:39
Haomeng|2dtantsur: yes, we add cpu_arch already, and should add others07:39
Haomeng|2yes, should be matched with flavor07:39
Zerpex| properties             | {u'memory_mb': u'4096', u'cpu_arch': u'x86_64', u'local_gb': u'60', u'cpus': u'2'}07:39
dtantsurlooks good07:39
Haomeng|2is this now attributes?07:39
dtantsurdid you fix the flavor?07:40
ZerpexHaomeng|2: yes - and I'll fix the flavor now07:40
Haomeng|2it is better we make sure flavor's attribute matchs ironic node properties07:41
Haomeng|2Zerpex: if still not working,have to check ironic hypervisor status and properties07:41
ZerpexCan I actually update the disk for a flavor07:41
Haomeng|2looks like there is no such flavor-update command07:42
Haomeng|2Zerpex: so can you take devstack scripts as reference and recreate the flavor - https://github.com/openstack-dev/devstack/blob/master/lib/ironic#L36807:43
*** ifarkas has joined #openstack-ironic07:44
ZerpexRecreated it - now let's see if it will work :D07:45
Haomeng|2Zerpex: good luck:)07:46
Haomeng|2Zerpex: if still not working,have to check nova side07:46
Zerpexokay, so still not working - ComputeFilter always return 0 :(07:47
Haomeng|2nova-manage service list07:47
Haomeng|2Zerpex: to see if our ironic compute driver is normal status07:47
Zerpexhttp://snaps.lucasrolff.com/926ff5eenzbw9ss.png bah07:47
*** jistr has joined #openstack-ironic07:48
Haomeng|2status is not :)07:48
Zerpexhttp://snaps.lucasrolff.com/bbc25j5h99y2wpb.png07:48
Haomeng|2nova-compute line07:48
Zerpexbut is running :D07:48
Haomeng|2you can paste the text with http://paste.openstack.org/ also:)07:49
Haomeng|2should be ironic driver side issue07:49
Haomeng|2can you check nova compute log?07:49
Haomeng|2Zerpex: maybe our ironic nova driver is not started with exceptions07:49
Haomeng|2and help to paste the nova compute log via http://paste.openstack.org/ , thanks07:50
*** Mikhail_D_ltp has joined #openstack-ironic07:50
Zerpexhttp://paste.openstack.org/show/89543/07:51
Zerpexwat - it did cut my paste07:51
Haomeng|2Zerpex: ok07:52
Haomeng|2Zerpex: maybe the last lines contain some exception that will cause nova compute wrong status07:53
Haomeng|2Zerpex: one finding -  scheduler_manager              = nova.scheduler.manager.SchedulerManager07:53
Haomeng|2Zerpex: should be "ironic.nova.scheduler.ironic_host_manager.IronicHostManager" I think07:54
dtantsurbrb07:54
Haomeng|2Zerpex: in the compute log line 27807:54
*** dtantsur is now known as dtantsur|brb07:55
Zerpexnova-compute     controller1                          nova             enabled    :-)   2014-08-01 07:32:1207:56
Zerpexnow is ok07:56
Haomeng|2Zerpex: did you set scheduler_manager=ironic.nova.scheduler.ironic_host_manager.IronicHostManager ?07:56
Haomeng|2Zerpex: how did you fix?07:57
Zerpexhttp://snaps.lucasrolff.com/sqss2atppjja3ms.png07:57
Zerpexyes :D07:57
Zerpexso now it returns the correct thing as well07:57
Haomeng|2Zerpex: looks fine07:57
Haomeng|2Zerpex: have interested with your actions -how did you fix?07:57
*** romcheg1 has joined #openstack-ironic07:58
Zerpexrebooted the server and changed the scheduler_manager :')07:58
Haomeng|2Zerpex: cool:)07:58
Haomeng|2Zerpex: try again, and good luck:)07:58
Zerpexhttp://snaps.lucasrolff.com/f13r7tmc9pgafrm.png07:59
Zerpexbut now I get that07:59
openstackgerritGhe Rivero proposed a change to openstack/ironic: Fix not attribute '_periodic_last_run'  https://review.openstack.org/11112607:59
Zerpexbrb 4 mins08:00
Haomeng|2Zerpex: :)08:00
*** romcheg_ltp has quit IRC08:00
*** naotok is now known as zz_naotok08:01
Zerpexhmm - wondering where that comes from :308:01
Haomeng|2Zerpex: can you check the nova.conf carefuly?08:02
ZerpexI'll do08:02
Haomeng|2Zerpex: and not sure if your nova code is so old which does not match the new ironic code?08:03
ZerpexI did use the RDO installer - so would assume is somewhat new :D08:04
Zerpexand was deployed like 1 week ago08:04
Haomeng|2Zerpex: looks the code is trying to access the unknow attribute self.host08:04
Zerpexhttp://snaps.lucasrolff.com/kxnuy19vum65wwk.png should be there08:04
Haomeng|2Zerpex: or self is none08:05
Haomeng|2strange08:05
Haomeng|2any more information from log?08:05
Zerpexlet me see08:05
Haomeng|2Zerpex: manager_class has no such host argument, I think, based on the error message08:06
Haomeng|2let me check our ironic scheduler manager code08:07
*** romcheg1 has quit IRC08:09
Haomeng|2base class is nova.scheduler.host_manager.HostManager08:09
*** bvivek has joined #openstack-ironic08:12
*** ndipanov has joined #openstack-ironic08:18
*** foexle has joined #openstack-ironic08:18
*** nikunj2513 is now known as nikunj251208:19
*** derekh_ has joined #openstack-ironic08:19
*** derekh_ is now known as derekh__08:22
*** derekh__ is now known as derekh_08:22
*** MattMan has quit IRC08:32
*** MattMan has joined #openstack-ironic08:32
*** bmahalakshmi has joined #openstack-ironic08:50
*** romcheg1 has joined #openstack-ironic08:55
*** lazy_prince has quit IRC09:16
*** athomas has joined #openstack-ironic09:18
*** rameshg87 has joined #openstack-ironic09:21
openstackgerritVladyslav Drok proposed a change to openstack/ironic: Remove gettextutils _ injection  https://review.openstack.org/11063409:26
*** killer_prince has joined #openstack-ironic09:38
*** killer_prince is now known as lazy_prince09:38
*** rameshg87_ has joined #openstack-ironic10:03
*** ndipanov_ has joined #openstack-ironic10:05
*** rameshg87 has quit IRC10:11
*** ndipanov has quit IRC10:11
*** Mikhail_D_ltp has quit IRC10:11
*** foexle has quit IRC10:11
*** foexle has joined #openstack-ironic10:14
*** Mikhail_D_ltp has joined #openstack-ironic10:16
*** ndipanov_ has quit IRC10:19
*** ndipanov has joined #openstack-ironic10:19
openstackgerritRamakrishnan G proposed a change to openstack/ironic: Take iSCSI deploy out of pxe driver  https://review.openstack.org/11123210:21
*** romcheg1 has left #openstack-ironic10:37
*** romcheg1 has joined #openstack-ironic10:37
mariosanyone tried devtest with ironic lately? my undercloud heat stack create timed out - trying again10:38
Haomeng|2marios: hi10:52
Haomeng|2marios: if the root cause is timeout, you can modify the default timeout value in devstack scripts10:52
*** romcheg1 has quit IRC10:52
Haomeng|2marios:   stack.sh:SERVICE_TIMEOUT=${SERVICE_TIMEOUT:-60}10:53
Haomeng|2marios: you mean tripleo's devtest?10:53
Haomeng|2marios: not devstack?10:54
Haomeng|2marios: and you can raise the question to tripleo10:54
Haomeng|2marios: irc  #tripleo10:54
mariosHaomeng|2: thanks, seems to be metadata (Aug 01 10:49:20 localhost nova-api[3384]: 2014-08-01 10:49:20.798 3788 ERROR nova.api.metadata.handler [-] Failed to get metadata for...92.0.2.310:56
Haomeng|2marios: so have to check nova-api-metadata service process and log10:57
Haomeng|2marios: welcome10:57
*** dtantsur|brb is now known as dtantsur10:59
*** ramineni has quit IRC11:01
*** Alexei_9871 has joined #openstack-ironic11:03
dtantsurFolks, anyone wanting to have a look at Ceilometer integration https://review.openstack.org/#/c/72538/ before it's approved?11:04
openstackgerritRamakrishnan G proposed a change to openstack/ironic: Take iSCSI deploy out of pxe driver  https://review.openstack.org/11123211:30
*** bmahalakshmi has quit IRC11:37
rameshg87_dtantsur, just have a quick question11:40
dtantsurrameshg87_, yep11:41
rameshg87_dtantsur, https://review.openstack.org/#/c/111232/1/ironic/drivers/modules/deploy_utils.py L35211:41
rameshg87_dtantsur, comment on "redundant"11:41
dtantsuryes11:41
dtantsuryou don't need a return value in case of exception11:41
dtantsur(that's why it wasn't there from the beginning)11:41
rameshg87_dtantsur, ah okay, because we are rethrowing the exception ?11:42
dtantsurrameshg87_, exactly11:42
rameshg87_dtantsur, ah okay .. i missed that part ..11:43
rameshg87_dtantsur, i will revise it, thanks11:43
dtantsuryeah, I'm also often confused at this point11:43
dtantsurnp :)11:43
rameshg87_dtantsur, i just posted a new patch excatly at the same minute you posted comment11:43
rameshg87_dtantsur, i will address in next patch :-)11:43
dtantsuryeah, I've seen it :)11:43
openstackgerritImre Farkas proposed a change to openstack/ironic: Add DracDriver and its DracPower module  https://review.openstack.org/10485011:58
*** nikunj2512 has quit IRC12:02
*** Shrews has joined #openstack-ironic12:02
*** rameshg87_ has quit IRC12:04
*** Shrews has quit IRC12:06
*** Shrews has joined #openstack-ironic12:06
openstackgerritDmitry Tantsur proposed a change to openstack/ironic: EXPERIMENTAL Implement hardware discovery in PXE driver  https://review.openstack.org/11003112:06
openstackgerritDmitry Tantsur proposed a change to openstack/ironic: Add newly_discovered column to Node object  https://review.openstack.org/10738912:06
openstackgerritDmitry Tantsur proposed a change to openstack/ironic: EXPERIMENTAL Add Conductor.discovery_driver field  https://review.openstack.org/10930412:06
openstackgerritDmitry Tantsur proposed a change to openstack/ironic: EXPERIMENTAL Implement conductor part of hardware discovery  https://review.openstack.org/10931212:06
*** jasondotstar has quit IRC12:10
openstackgerritImre Farkas proposed a change to openstack/ironic: Add DracDriver and its DracPower module  https://review.openstack.org/10485012:18
openstackgerritA change was merged to openstack/ironic: Implements send-data-to-ceilometer  https://review.openstack.org/7253812:29
*** lazy_prince has quit IRC12:41
*** killer_prince has joined #openstack-ironic12:56
*** mkerrin has quit IRC12:56
*** killer_prince is now known as lazy_prince12:56
*** mkerrin has joined #openstack-ironic12:57
openstackgerritA change was merged to openstack/ironic: Fix not attribute '_periodic_last_run'  https://review.openstack.org/11112613:05
*** jistr has quit IRC13:12
*** jistr has joined #openstack-ironic13:14
*** jasondotstar has joined #openstack-ironic13:19
*** k4n0 has quit IRC13:26
*** stendulker has joined #openstack-ironic13:28
*** jasondotstar has quit IRC13:40
*** jasondotstar has joined #openstack-ironic13:41
NobodyCamGood morning Ironic TGIF!!!13:44
dtantsurNobodyCam, morning, TGIF :)13:46
NobodyCammorning dtantsur :)13:46
*** mkerrin has quit IRC13:48
*** mkerrin has joined #openstack-ironic13:48
NobodyCambrb...13:49
*** jistr has quit IRC13:52
*** jistr has joined #openstack-ironic13:53
*** Poornima has quit IRC13:56
*** dkehn_ is now known as dkehnx14:02
*** pcrews has joined #openstack-ironic14:06
*** rainya has joined #openstack-ironic14:06
stendulkerJayF: Hello, are you  there?14:07
NobodyCammuch too cold outside for summer :-p14:08
*** rainya has quit IRC14:09
stendulkerNobodyCam: Hello14:10
*** rainya has joined #openstack-ironic14:10
NobodyCamgood morning stendulker :)14:10
stendulkerNobodyCam: good morning :)14:10
stendulkerNobodyCam: Wanted to discuss regarding firmware settings spec https://review.openstack.org/#/c/101122/14:11
*** lazy_prince is now known as killer_prince14:11
jrollmorning y'all14:12
stendulkerNobodyCam: It seems this spec got discussed during mid-cycle meetup and it was felt this spec is kind of outside Ironic scope. JayF have left me comment summarizing it.14:12
openstackgerritJim Rollenhagen proposed a change to openstack/ironic: Remove dbapi calls from agent driver  https://review.openstack.org/11129214:12
NobodyCammorning jroll14:13
*** igordcard has joined #openstack-ironic14:13
dtantsurjroll, morning!14:13
jrollgah I forgot a bug for that14:13
*** killer_prince is now known as lazy_prince14:13
NobodyCamstendulker: let me review the comments14:14
stendulkerNobodyCam: Ok.14:14
openstackgerritJim Rollenhagen proposed a change to openstack/ironic: Remove dbapi calls from agent driver  https://review.openstack.org/11129214:15
jrollmuch better14:15
jrollfairly easy review there, I think14:15
*** zul has joined #openstack-ironic14:17
*** rakesh_hs has quit IRC14:27
*** nosnos has quit IRC14:31
openstackgerritA change was merged to openstack/ironic-python-agent: Updated from global requirements  https://review.openstack.org/8872214:32
*** comstud is now known as bearhands14:36
NobodyCamstendulker: we did discuss the firmware and inventory aspects at the meetup.14:37
*** jgrimm has joined #openstack-ironic14:40
*** nosnos has joined #openstack-ironic14:41
NobodyCamstendulker: I really what to find out what will come out of this : https://www.openstack.org/vote-paris/Presentation/cmdb-for-openstack-public-cloud-based-assets14:42
stendulkerNobodyCam: Ok, I had posted the comment justifying the need for the individual tuning as well as 'Capability' attribute proposed in the comment which would be part of the flavor14:42
*** Mikhail_D_ltp has quit IRC14:42
stendulkerNobodyCam: I was not fully convinced that 'Capability' attribute in flavor would be able to tune the BM node in a desired fashion for the user.14:43
*** nosnos has quit IRC14:44
NobodyCamstendulker: In your example are saying expert users would what to fine tune systems after they have been provisioned?14:50
*** lazy_prince is now known as killer_prince14:57
*** rainya has quit IRC14:59
stendulkernobodyCam: Not after. Before provisioning would want to tune the system for his workload which would be run after deploy.15:02
stendulkerNobodyCam: Most of the firmware settings would need a reboot, so best time to perform tuning would be before deploy15:03
jrollstendulker: if the desired settings are known before provisioning, a capability could be created to handle that. right?15:03
*** rainya has joined #openstack-ironic15:03
stendulkerjroll: The 'Capability' being a single property, it may not be handle multiple tuning that may be required to achieve the end result.15:05
jrollstendulker: I think the idea is that a capability could handle multiple firmware settings15:05
stendulkerCpability would be broad level setting which would be interpreted by the driver as a pre-defined set of firmware settings and not individual ones. This would prevent the custom tuning by the user.15:06
jrollwhy couldn't the user make his or her own new capability?15:06
jrollwith all the right settings?15:06
devanandamorning, all15:08
stendulkerjroll: How do the driver interpret user defined capability. Can you please give  me a possible example15:08
jrollstendulker: the same way. any user of ironic is an admin user, and so could create a capability15:08
jrollmorning devananda15:08
stendulkerjroll : Will the capability have set of name/value pairs?15:08
jrollstendulker: I don't think people have decided how a capability will be defined15:09
stendulkerjroll: Say the user wants to deploy a node to use UEFI boot with power tuned to optimum value and few more processor related settings15:09
jrollin terms of firmware things15:09
jrollyes, that will be possible, it appears15:10
*** dkehn_ has joined #openstack-ironic15:10
jrollstendulker: we want to enable your use case, just in a (seemingly) better way15:10
jrolldevananda: found some dbapi calls in the driver after all :P https://review.openstack.org/11129215:10
stendulkerjroll: Will capability be used by nova scheduler for node selection or it is something that would be used by driver to prepare the node for deploy post selection15:11
jrollstendulker: sounds like both15:12
jrollif needed, the driver could prepare the node15:12
devanandajroll: good stuff15:13
stendulkerjroll: Wanted to understand the capability better as firmware settings are mostly vendor specific and flavor is something which is generic in nature15:13
*** dkehnx has quit IRC15:14
jrollstendulker: right, I have to run in a moment, but hopefully someone else can explain :)15:15
jrollstendulker: but, short version is that we can support your needs, I think15:15
JayFstendulker: exactly why I said what I did15:16
stendulkerjroll: ok. Thanks. If I could get more details, it would help me understand if the usecase gets covered.15:16
JayFstendulker: firmware settings *are* vendor dpecific15:16
JayF*specific15:16
JayFstendulker: and Ironic has to abstract that to present a reasonable api15:16
stendulkerJayF: Good morning :)15:16
JayFstendulker: the point you crossover into configuring a single machine in a highly specific way, you've moved out of the realm of cloud and treating servers at cattle into the realm of managing snowflakes, which isn't really in the scope of openstack generally15:17
JayFstendulker: good morning :)15:17
stendulkerJayF: The proposed API were accepting key/value pairs for the firmware settings so that drivers could handle it based on the individual vendor15:18
JayFstendulker: I think that'll be somewhat preserved, but in the form of 'capabilities' that then a driver could implement however15:18
JayFtheoretically, you could make a driver that exposed a large number of bios settings as different capabilities15:18
JayFand require them all on the nova flavor definition15:18
JayFthat's absolutely not the way I'd use it, but I think enabling custom capabilities is important; but it has to be made better for the generic case15:19
stendulkerJayF: so is a capability be defined as a set of generic firmware settings to be done by driver before provisioning?15:20
*** dtantsur is now known as dtantsur|brb15:21
JayFWell, we have to write a spec to define exactly what it would be :), but the idea talked about at the meetup is like this:15:21
JayFcapabilities are ternary: true/false/configure15:21
JayFin the case of BIOS settings, you're almost always going to expose them as a configurable option15:21
JayFwe would have a small generic set (think: HPC, virtualization, etc) which we would want all drivers to support, so an operator could configure a 'virutalization' flavor which would schedule to a server with the proper config; including VT bit set, turbo mode disabled, etc15:22
stendulkerJayF: So, I suppose the capabilities would be pre-defined key names having one of the ternary values15:23
JayFand then also drivers could expose their own capabilities15:23
JayFlike for instance, for IPA, the agent could query loaded hardware managers to capabilities15:23
JayFor for iLo/DRAC, it could query those and determine additional capabilities15:23
JayFstendulker: yeah, exactly.15:23
JayFstendulker: and for ones that are 'configure', you'd have a new call, just before deploy, that does that configuration15:24
devanandaJayF: It sounds like you want to write the spec for Kilo :)15:25
stendulkerJayF: So this will not cover any vendor spefic tunings or custom tuning required by the user15:25
JayFdevananda: I wouldn't have had such well-formed ideas if I knew they came with responsiblity :P15:25
devanandaJayF: ideas always come with responsibility ;)15:25
JayFstendulker: explicitly not; the only real customization you can expose to the user is via nova flavors15:25
JayFstendulker: or from an ironic api standpoint directly; capabilities15:26
JayFstendulker: if you have a cool vendor specific set of tunings; you /could/ expose it as capabilities, you just have to do it from within a driver -- like via a custom IPA hardware manager15:28
stendulkerJayF: But doesn't this constrain the user to pre-defined capabilities and take away the flexibility to fine tune ?15:28
JayFstendulker: so lets step back for a second, I'm assuming your use case is using Ironic behind Nova, correct?15:28
JayFstendulker: with a Nova driver?15:28
stendulkeryes ironic behind nova15:29
JayFOK, so assuming it would be OK scope wise and abstraction wise to set specific BIOS settings, how would those users pass those requests through to Ironic via Nova API?15:30
stendulkerany capability defined would not be able to cater all tuning needs of the user.15:30
NobodyCamstendulker: do you have an example of a setting that a user would fine tune?15:32
*** foexle has quit IRC15:32
* Shrews hopes everyone had a better week than he did15:32
JayFI'm also still curious about how you'd feed that information through nova to ironic. I don't think there's a mechanism/interface for it now either :) Remember that adding something to Ironic API still means only an admin could do it15:32
NobodyCamShrews: :(15:33
NobodyCamShrews: and good morning :)15:33
ShrewsNobodyCam: morning  :)15:33
stendulkerNobodyCam: Say user wants to tune the power NIC  and processor settings15:33
stendulkerthere are multiple tunables names within power, NIC and processor and users would want to use different combinations15:34
stendulkerso the different combinations could become individual capabilities?15:35
JayFYes, absolutely15:36
JayFOr as separate, so say for power, you could have a 'power-saving power-medium power-performance' capability set15:37
JayFor something better named :)15:37
stendulkerJayF: Can a single flavor have multiple capabilities?15:37
JayFI think we'd want to do it that way, yes15:38
*** killer_prince is now known as lazy_prince15:38
JayFbut given we're talking about somethign that hasn't even been codified to a spec, anything is possible as long as it fits within the scope and abstractions of Ironic :P15:38
stendulkerJayF: I understand, trying to understand the idea :)15:39
JayFThe big issue is just that the idea of what a 'setting' is has to be abstracted so it could work for a set of devices, not just one15:39
JayFand that Ironic-itself would directly list a small number of them, and drivers could expose more as needed15:40
*** Hefeweizen has quit IRC15:41
JayFpower-saving vs power-performance are even capabilities I could see making a whole lot of sense on the global scale :)15:41
stendulkerJayF: may be better  to delegate that responsibility to the driver which is closest to the node and they can handle for individual vendors15:42
JayFthe only difference between global vs driver-specific would be that all drivers would be (forced || strongly encouraged) to implement global ones15:43
JayFso you would still have the driver close to the node deciding what that means, in a specific sense15:43
stendulkerJayF: That is possible by making certain settings as mandatory ones.15:44
NobodyCamJayF: as a host would a setting like power saving/performance be something you would bill differently for, or even something you want run from specific raq's15:45
JayFstendulker: exactly15:46
stendulkerJayF: So necessarily, capabilities could be individual or group of settings that are part of the flavor and are completed before actual deploy operation begins. Is this understanding correct?15:46
JayFNobodyCam: I would think more like, setting the bios settings to aggressively power save15:46
JayFstendulker: capabilities would become a part of the ironic api that would be exposed via nova flavors and completed as part of provisioning -- so yes, that's what I'm thinking15:47
JayFstendulker: the key thing there being that it's part of provisioning. If it's not part of or related to provisioning, it's arguably not in Ironic's scope15:47
stendulkerJayF: What would happen to deploy if the capability tuning fail? Or any of the capability itself needs a reboot to get into effect?15:48
JayFstendulker: I was actually talking to jroll ^ about that exact possibility. I'd think you'd just do that as neccessary at deploy time15:49
*** ifarkas has quit IRC15:49
JayFstendulker: although, also, most bios settings would be fine to just take effect as you reboot into the instance15:50
stendulkerJayF: I did not get you fully.15:50
JayFstendulker: meaning you could either just do a reboot during the provision to make it take effect if that's required15:51
*** BadCub has quit IRC15:51
stendulkerJayF: yes, but if any tuning itself needs a recycle. though I do not have any example for that.15:51
JayFstendulker: or just utilize the reboot that already happens when you're about to reboot into a customer image15:51
*** BadCub has joined #openstack-ironic15:52
JayFstendulker: i.e., write image to disk, change bios settings, reboot into customer image15:52
*** viktors is now known as viktors|afk15:52
JayFstendulker: or something like apply settings, reboot, write image, reboot into customer image15:52
*** lazy_prince is now known as killer_prince15:52
stendulkerJayF: it should be possible to have multiple reboots within provisoning.15:53
JayFI agree, actually :)15:53
JayFSo this sounds like it'd be an interesting spec for Kilo -- does it seem like it matches up with your use case?15:54
*** rainya has quit IRC15:55
stendulkerJayF: Will capabilities be defined by Ironic? Or user would define it based on published list of global key/values? Can vendor publish its own key/value pairs?15:55
JayFstendulker: I'm not 100% sure, but it would probably be done at the driver level -- which would be super easy to customize if using IPA (custom HardwareManager), but IDK how it'd work if you wanted to configure things using out of band methods (like ilo)15:56
jbjohnsofyi, it may be pertinent to some interest around here (a place employing pyghmi and a possible contender to serve in place of complex neutron interaction)15:57
jbjohnsohttps://sourceforge.net/p/xcat/wiki/Confluent/15:57
JayFstendulker: I'd see where and how those are defined as something that likely needing the most additional thought :)15:57
jbjohnsoIt might have a bit more stuff than ironic would want to use, but my goal is to have a pretty tunable experience15:57
jbjohnsoso one could just tell it 'boot this kernel without messing with dhcp'15:58
jbjohnsoand/or 'give me a token to delegate console access to a client'15:58
NobodyCamoh jbjohnso morning: I wanted to point out we landed this: https://github.com/openstack/ironic-specs/blob/master/specs/juno/enabling-ipmi-double-bridge-support.rst15:59
stendulkerIf driver could publish possible tunables then user should be able to define its own set of capabilities using the combination of global and vendor specific tunables15:59
NobodyCamdoes pyghmi expose dbl bridging?16:00
jbjohnsoNobodyCam, someone at intel submitted something I accepted it16:00
jbjohnsoNobodyCam, but I have no idea what testing it would be like16:00
JayFstendulker: yeah, I'm not 100% sure about that, but we should get a spec up when K opens and chat about it there. Sounds like there's a happy middle ground that fits in Ironic's model and covers most, if not all, of your use case16:00
jbjohnsoNobodyCam, at the time, intel guy said it was mostly about getting at the ME in a system with ME and vendor-specific bmc mostly16:01
stendulkerJayF: yes, I think we will surely need to discuss more on this.16:01
jbjohnsobut I have no architectures that opted to use ipmi bridging for bmc sharing.. can't say more than that16:02
stendulkerJayF, NobodyCam, jroll: Thank you for your patience and helping me understand this.16:02
jbjohnsoI can't recall specifics, but there seems to be quite a few hiccups in some concepts in a bridged management situation16:04
jbjohnsoI want to say I thought SOL payload was an example where a distinct model than bridging is indicated...16:04
*** rainya has joined #openstack-ironic16:04
*** rainya has quit IRC16:05
jbjohnsobut haven't honestly discussed it much in depth with the platform guys16:05
bearhandsdevananda: any reason you did not +A: https://review.openstack.org/#/c/111292 ?16:05
*** rainya has joined #openstack-ironic16:05
JayFstendulker: no problem, I wasn't sure about which way to go either which is why I brought it up last week :) nice chat :) have a good day16:07
*** Haomeng has joined #openstack-ironic16:08
*** ndipanov is now known as ndipanoff16:08
NobodyCambrb16:08
JayFdevananda: very curious as to your thoughts on https://review.openstack.org/#/c/97744/10/specs/juno/ironic-ilo-virtualmedia-deploy.rst line 14716:08
stendulkerJayF: On side note, would the capability obsolete the boot device related management APIs whcih are already defined?16:09
*** Haomeng|2 has quit IRC16:09
JayFstendulker: not at all, I don't think16:10
*** dkehn__ has joined #openstack-ironic16:10
*** mdorman has joined #openstack-ironic16:10
stendulkerJayF: Isnt that boot device could get covered in Capabilities?16:11
JayFI'm not sure it's something we want to be user configurable16:11
JayFit's mostly an attribute of the image used (and by extension, currently in ironic, the deploy driver used)16:11
*** dkehn_ has quit IRC16:13
stendulkerJayF: Isnt these APIs could be used by user to configure teh same?16:14
JayFI'm honestly not sure :(16:15
JayFI have a meeting in a few minutes I have to prep for so can't stick around in IRC, but lets keep pondering on this, and get a spec up first thing for kilo16:15
JayFonce it opens16:15
devanandabearhands: yep. it hadn't passed jenkins yet16:16
bearhandsdevananda: jenkins will not do anything more if it failed :)16:17
bearhandsi don't see the point in waiting16:17
stendulkerJayF: Ok. Thank you for a nice discussion.16:17
*** ellenh has joined #openstack-ironic16:17
devanandabearhands: i know. but I wanted to see it16:17
*** dkehn__ is now known as dkehnx16:18
bearhandshaa16:18
bearhandsi still don't get it, but okay :)16:18
bearhandsseems like a waste of time.. this could have been hitting the gate already :)16:18
*** matty_dubs is now known as matty_dubs|lunch16:25
*** dkehnx has quit IRC16:28
*** dkehn has joined #openstack-ironic16:30
*** Hefeweizen has joined #openstack-ironic16:31
*** Mikhail_D_ltp has joined #openstack-ironic16:40
*** aswadr has quit IRC16:42
jrolldevananda: you don't trust me to run tox? :)16:43
JayFI don't trust our tests at all until we have tempest working against ipa :x16:45
*** eghobo has joined #openstack-ironic16:45
jrollthat's a completely different thing :P16:46
*** derekh_ has quit IRC16:46
* jroll runs off to hack devstack16:46
*** stendulker has quit IRC16:46
JayFjroll: oh yeah, I had the second stack.sh running in a vm, I should finish that up and boot an agent :D16:47
JayFjroll: 2014-08-01 01:04:45.395 | [ERROR] /opt/stack/devstack/lib/ironic:324 pxelinux.0 (from SYSLINUX) not found.16:47
JayFjroll: wonder if that's a missing dep for ironic or a missing dep for ipa? probably just ironic?16:47
jrollO.o16:47
jrollironic16:47
jrollbut like... I've never seen that16:48
jrollwith a fresh cloud server, even16:48
jrollare you following the ironic devstack guide?16:48
JayFI cloned devstack, ran stack.sh. Did your steps including replacing my existing localrc (excepting creds) and reran stack.sh16:48
jroll"excepting creds"?16:49
JayFmeaning I had already set passwords for some things16:49
JayFso I kept my passwords instead of using yours16:49
*** Mikhail_D_ltp has quit IRC16:49
jrolloh, lame16:49
jrollpassword is the best password16:49
jrollJayF: you on 12.04 or 14.04?16:50
jrollor... something else?16:50
JayF14.04, using p1-8gb w/pvhvm16:51
JayFafter apt-get install syslinux it appears to be continuing16:51
jrollweird16:51
*** MattMan has left #openstack-ironic16:51
* jroll shrugs16:51
openstackgerritA change was merged to openstack/ironic: Remove dbapi calls from agent driver  https://review.openstack.org/11129216:56
*** bvivek has quit IRC16:56
NobodyCamhttps://wiki.openstack.org/wiki/Blazar16:57
*** Nisha has joined #openstack-ironic16:57
NobodyCamwtf https://www.openstack.org/vote-paris/Presentation/astrologer17:04
jrollNobodyCam: blazar looks.... interesting17:06
*** ndipanoff has quit IRC17:06
jrollastrologer looks LOL17:06
NobodyCamjroll: ya...17:07
NobodyCam:/17:07
jrollaaand googling his name (not clicking links) logged me out in os x D:17:09
jrollwtf17:09
jrollprobably unrelated but wtf17:09
*** penick has joined #openstack-ironic17:11
*** mdorman has quit IRC17:12
*** scubacuda has joined #openstack-ironic17:12
*** mdorman has joined #openstack-ironic17:16
NobodyCamjroll: its written in the stars17:18
jrolllol17:19
*** mdorman has quit IRC17:21
matty_dubs|lunchOh man, this would be an awesome session17:21
JayFWe could ask them to put together our roadmap for kilo17:22
JayFsince they'd already know what we'd get done17:22
matty_dubs|lunchLOL17:22
jrollhahaha17:22
*** Alexei_9871 has quit IRC17:24
*** dkehn is now known as dkehnx17:28
matty_dubs|lunchI seriously think it would be awesome if this guy had a booth17:29
matty_dubs|lunchThough I'd hate to reward spammers17:29
*** mdorman has joined #openstack-ironic17:29
*** matty_dubs|lunch is now known as matty_dubs17:30
NobodyCam:)17:30
Shrewsi love that he offers a 101% guarantee17:31
Shrewsthat extra 1%, man....17:31
*** mmitchell has quit IRC17:31
jrollmatty_dubs: I'd bet he's not the only spammer submitting talks :P17:32
adam_gjroll,  re, 'pxelinux.0 (from SYSLINUX) not found.' and other things that require stuff from packages, make sure to delete devstack/.prereqs before re-running devstack. i was hitting the same issue yesterday.17:32
adam_ger JayF ^17:32
jrollhuh, I didn't know that existed17:32
*** mdorman has quit IRC17:33
adam_gme either. :) it leaves some time stamp there and only installs package dependencies on re-run if some amount of time has passed17:33
*** mdorman has joined #openstack-ironic17:33
JayFadam_g: nice, thanks17:34
NobodyCamadam_g: jroll: have you seen : https://bugs.launchpad.net/tripleo/+bug/135101017:34
adam_gNobodyCam, no i haven't. where did syslinux get bumped to v6? debian?17:34
jrollNobodyCam: oh goody17:35
NobodyCamnot sure it has been ... I just saw that lastnight17:35
*** mdorman_ has joined #openstack-ironic17:36
*** mmitchell has joined #openstack-ironic17:38
*** mdorman has quit IRC17:38
*** mdorman_ is now known as mdorman17:38
*** mdorman has quit IRC17:40
*** mdorman has joined #openstack-ironic17:40
devanandaNobodyCam: http://packages.ubuntu.com/trusty/utils/syslinux-common IIUC this says it is still syslinux 517:42
devananda417:42
*** Shrews has quit IRC17:43
adam_gdebian's bumped to 3:6.03~pre18+dfsg-117:45
*** rameshg87 has joined #openstack-ironic17:46
devanandaurgh17:49
*** Shrews has joined #openstack-ironic17:49
rameshg87JayF, devananda, hi17:50
devanandaadam_g: wheezy is still 4. jessie is 6. yes?17:51
devanandaah, and so is sid17:51
devanandaok. taggign ironic on this17:51
adam_gdevananda, yup17:52
NobodyCamjroll: the dib ipa ramdisk has no /usr at all17:59
rameshg87devananda, request your thoughts on comment on https://review.openstack.org/#/c/97744/10/specs/juno/ironic-ilo-virtualmedia-deploy.rst (L79)18:03
NobodyCamjroll: I think I  may need to fiddle around here, to fix that18:04
NobodyCamhttps://github.com/openstack/diskimage-builder/blob/master/lib/ramdisk-functions#L4918:04
rameshg87devananda, JayF & lifeless suggests we build an image from kernel/ramdisk at run time and then attach it to the baremetal node (which you were probably against at the time of patch set 2)18:05
JayFNobodyCam: so where are the python packages pip installed to?18:08
*** athomas has quit IRC18:10
openstackgerritRamakrishnan G proposed a change to openstack/ironic-specs: iLO-IPA Deploy Driver  https://review.openstack.org/10844518:11
NobodyCamJayF: I am assuming that the /usr is just not linked in the final ramdisk. I am checking on that now18:12
JayFah, okay18:13
NobodyCamhumm : No distributions matching the version for oslo.config>=1.4.0.0a3 (from ironic-python-agent==50b8f25)18:14
JayFNobodyCam: you need a newer version of pip18:15
JayFNobodyCam: this is why we had to bump the agent container to trusty18:15
JayFNobodyCam: so we could land the global reqs change which forces that version of oslo.config, which is apparently only packaged as a wheel file18:15
*** amitpp has joined #openstack-ironic18:17
NobodyCamJayF: will "sudo pip install pip --upgrade" work for saucy18:20
* NobodyCam wants to not reformat'18:21
JayFNobodyCam: in the container, that moved my pip binary from /usr/bin/pip to /usr/local/bin/pip and 'broke' just running "pip" without a path, so I didn't do that for the container18:21
JayFNobodyCam: I can tell you that the trusty one Just Works(tm)18:21
*** amitpp has quit IRC18:23
NobodyCamJayF: what version of pip do I need. the upgrade line seem to not ave broken my pip but I still get error about oslo.config18:25
NobodyCammy pip is now 1.5.6 was 1.5.218:25
JayFlet me see what the last agent container built with18:25
JayFroot@e432ea033395:/# pip --version18:27
JayFpip 1.5.4 from /usr/lib/python2.7/dist-packages (python 2.7)18:27
JayFNobodyCam: so obviously something is a little different18:28
NobodyCamyep let me see if I can build trusty18:28
rameshg87JayF, just a question18:28
JayFNobodyCam: I actually have to leave very shortly, but you can see the exact things running in my container in the dockerfile18:28
rameshg87JayF, regarding https://review.openstack.org/#/c/97744/10/specs/juno/ironic-ilo-virtualmedia-deploy.rst18:28
JayFNobodyCam: and that starts from a really barebones trusty container18:29
JayFrameshg87: if it's quick I have a minute18:30
rameshg87JayF, don't think it will be over in a minute, then i will leave you rather :-(18:30
rameshg87JayF, do you have plans to login later today ?18:30
*** Nisha has quit IRC18:30
NobodyCambrb18:30
JayFrameshg87: if you put the comments/discussion in the spec I'll absolutely check in on it over the weekend18:31
rameshg87JayF, okay here is a quick one ..18:31
JayFrameshg87: I try to keep low-latency reviewing on stuff that I know people (aka you) are looking at quickly :)18:31
rameshg87JayF, there were two concerns in the end if i get it right18:31
rameshg87JayF, 1 - the boot image not persistent across reboots,   2 - building the boot image dynamically inorder to be same as pxe deployement18:32
rameshg87JayF, for #2 we will check with devananda to get his thoughts18:33
JayF#1 I feel pretty strongly we should set the state of the machine to continue to boot whatever iso is configured until ironic reconfigures it18:33
rameshg87JayF, for #1 i would leave a comment, but i can make it persistent by use BOOT_ALWAYS option and generating swift temp url long enough18:33
rameshg87JayF, swift temp url long reasonbly long enough so that it can stay until the user releases the machine18:34
JayFoooh. I didn't think about the possibility of swift temp url expiration.18:34
rameshg87JayF, the swift temp url will expire after the given time ...18:35
JayFYeah, I hadn't thought about that at all. Does the iLO not cache the image?18:35
rameshg87JayF, no it doesn't18:35
JayFI think some amount of this depends on the behavior of the iLO, which I'm sadly not as up on18:35
rameshg87JayF, the ilo just uses the http location given by swift temp url and uses it as virtual cdrom18:36
jbjohnsoI don't know about iLO, but if the image is sufficently small it can be uploaded to IMM18:36
rameshg87JayF, what is IMM ?18:36
jbjohnsorameshg87, it's IBM's x86 service processor18:36
jbjohnsowe upload a ~700 kilobyte ipxe payload18:36
jbjohnsowhich has things like a CA cert to trust and private node credentials18:37
rameshg87JayF, jbjohnso, so you mean to cache the image somewhere ?18:37
jbjohnsorameshg87, the IMM has 50 MB of space that can be uploaded to via an http api18:37
JayFrameshg87: Do floppy images work the same way?18:37
JayFrameshg87: like can floppy images be cached?18:37
rameshg87JayF, yes, it works the same way ..18:38
JayFrameshg87: that really introduces a huge limitation18:38
jbjohnsoI suggest that a small ISO scheme18:38
jbjohnsowith the mount semantics dealt with separately18:38
jbjohnsowould enable best available18:38
rameshg87JayF, there might be some caching, but it is not predictable i guess. the http url needs to be accessible.18:38
*** romcheg1 has joined #openstack-ironic18:38
JayFrameshg87: if you provision a customer node, and that customer reboots after the swift temp url for the boot iso expires, the customer machine becomes unusable18:39
NobodyCamJayF: trusty built18:39
*** tatyana has joined #openstack-ironic18:39
JayFNobodyCam: \o/18:39
rameshg87JayF, if the reboot method in ironic takes care of that, then is it a real concern ?18:39
jbjohnsosurprised iLO can't do the same trick18:39
JayFrameshg87: a *customer* in-band can restart an image18:39
JayFrameshg87: aka a 'reboot' from the command line on a provisioned machine18:40
*** romcheg1 has quit IRC18:40
JayFrameshg87: and if the boot [floppy || iso] is gone, it won't boot18:40
*** romcheg1 has joined #openstack-ironic18:40
rameshg87JayF, i agree..18:40
JayFrameshg87: which means that URL has to be forever-persistent... which shouldn't be a problem for an image with a kernel and initrd, but we should call that out18:40
JayFrameshg87: you can't make a swift temp url that never expires, but you can make one that will effectively last for longer than the machine18:41
rameshg87JayF, then can't we keep the swift-temp-url long enough ?18:41
jbjohnsoso I was thinking of extending pyghmi to automate upload of .iso images and the like to endpoints...18:41
rameshg87jbjohnso, i think ilo needs the url to be always accessible18:41
jbjohnsobut I could only do the IBM/Lenovo backend...18:42
JayFrameshg87: I think you can't make it *unlimited*, but you can make it long enough to not matter so much18:42
jbjohnsorameshg87, I don't care about iLO ;)18:42
*** lsmola has quit IRC18:42
jbjohnsorameshg87, if HP wants to implement the backend though...18:42
rameshg87jbjohnso, :-)18:42
JayFrameshg87: I'd suggest you add to the spec that the temp-url for the kernel ramdisk be defaulted to a long time18:42
JayFrameshg87: and that the deploy disk be setup with a temp-url of something like an hour, and persisted18:42
rameshg87JayF, yes, that can be done ..18:43
*** romcheg2 has joined #openstack-ironic18:43
*** romcheg1 has quit IRC18:43
JayFrameshg87: then I think that would resolve my issue with #1, and for #2, we'll have to see what devananda says...18:43
NobodyCambrb18:44
devananda#2?18:44
JayFdevananda: https://review.openstack.org/#/c/97744/10/specs/juno/ironic-ilo-virtualmedia-deploy.rst18:44
rameshg87devananda, we were discussing about comment on L147 ^^18:44
jbjohnsohow small is your boot.iso?18:46
devanandaJayF: so right now, each "boot driver" (yes, i'm using a new term here) requires a different image18:46
rameshg87jbjohnso, usually 6-7 MiB18:46
JayFdevananda: I'm OK with it requiring a separate image; just I thought the suggestion was a good one given ironic would hve to generate floppy images anyway18:47
jbjohnsorameshg87, that's surprising, bigger than I'd expect one way, smaller than I'd expect the other18:47
devanandaPXE driver requires kernel & initrd made by dib/elements/ironic-deploy-ramdisk18:47
jbjohnso674K is one of mine for rhels6 deploy18:47
jbjohnsobut if I did it with kernel and initrd onboard it would be bigger..18:48
JayFdevananda: I would propose that this driver pull those initrd/kernel down, embed them in a floppy boot image, and mount that via ilo18:48
JayFdevananda: rather than having a new set of DIB elements to package them into an iso || floppy image18:49
devanandaJayF: not via floppy. via cd-rom.18:49
JayFdevananda: we would change to via floppy as well if we did that18:49
JayFdevananda: so ironic would only have to build floppy images, which is already in scope of that spec18:49
JayFand per rameshg87, iLO does not impose size restriction on virtual floppies18:49
devanandaJayF: except it's building a floppy image right now just for a specific vector -- load keys over a secure channel18:50
devanandaJayF: this conflates that mechanism to deliver non-secure payloads18:50
rameshg87JayF, sorry i am yet to confirm that it can put kernel/ramdisk into floppy image, but looks possible to me ..18:50
JayFdevananda: if that distinction crosses a scope line, I'm OK with it being done the existing proposed way18:51
JayFdevananda: this was originally lifeless's suggestion, I just picked it up becuase I thought it was worthwhile :) if it's an issue we can do it as written currently18:51
JayFand generate the image (using DIB) beforehand18:51
rameshg87JayF, the initial plan was to make dib capable of giving out boot iso18:52
jbjohnsoI'd say that an .iso format would look less... bizarre....18:52
devanandaJayF: I don't see any particular benefit to doing it the way lifeless/you are proposing, and I see some operator confusion and additional overhead.18:52
JayFok then :)18:53
devanandawhat I'd really like to see in Kilo is the iLO attach-virtual-floppy mechanism become a separate interface18:53
rameshg87JayF, additional concern was the kernel/initrd will be duplicated for each instance18:53
rameshg87JayF, if we dynamically generate image for each instance18:53
devanandasomething like PassSecureMedia (or some better name than that)18:53
jbjohnsorameshg87, which is a good reason to contemplate the concept I describe18:53
JayFthat's fine :) I'm totally sold on going back to building the iso with the image now :) no need to keep convincing me, lol18:53
rameshg87JayF, :-)18:54
jbjohnsorameshg87, which basically keeps the flow for things identical to pxe except without dhcp, proxydhcp, or tftp18:54
rameshg87JayF, just was saying my point again :-)18:54
jbjohnsorameshg87, a ~1MB unique payload per target or so...18:54
rameshg87jbjohnso, okay18:55
jbjohnsomade a touch easier if Michael Brown's recent endeavor pans out...18:55
jbjohnsobut only for UEFI style boots18:55
jbjohnsoBIOS style is a pretty hopeless cause with the way entry vector to entry would work18:56
jbjohnsowell, not hopeless, you could build ipxe with drivers instead of duing undi, but it'd get bigger18:56
rameshg87devananda, just one more thing if you have time. probably this is something we discussed long back.18:56
rameshg87devananda, regarding comment on https://review.openstack.org/#/c/97744/10/specs/juno/ironic-ilo-virtualmedia-deploy.rst (L79)18:57
devanandaoh,the boot-once or always-boot-from18:58
rameshg87devananda, yes18:58
devanandaso in a broader context, i think we need to be able to determine that programatically, regardless of the driver18:58
rameshg87devananda, yes we can ..18:59
rameshg87devananda, but JayF concern was if the user does an in-band reboot on baremetal node, the machine wouldn't boot18:59
devanandaAIUI, PXE driver always boots from PXE, IPA driver will boot from PXE only when required to (user image is not going to be net booted, ever)18:59
devanandarameshg87: so that depends on the BIOS settings. Will the local drives be *removed* from the boot options?19:00
JayFbut fwiw, IPA does always set persistent=true when calling the force-pxe option19:00
JayFbecause it will be an explicit post-deploy ironic call to flip it back to disk19:00
rameshg87devananda, no the local drives are not removed from boot options19:00
devanandaJayF: right. when deploy is done, you set boot optionsback to disk19:00
devanandaJayF: whereas the PXE driver does not (today)19:01
jbjohnsobtw, how much of this is UEFI style versus BIOS boot?19:01
rameshg87devananda, if a user deploys an fs-image, the bm node will need to be booted from virtual media everytime for ilo driver19:01
JayFYes :) my concern in that spec for rameshg87 was about if the node reboots due to non-ironic reasons (power cycle in rack, in-band reboot via IPA, etc) it should boot back into the state it was before19:01
devanandaso it sounds like the proposal for the iLO driver is: if it uses PXE, it's going to break when the user reboots locally. if it uses IPA, it will boot locally just fine.19:01
jbjohnsoI ask because efibootmgr with UEFI boot services means you can rejigger things in an utterly agnostic fashion at the iend19:01
jbjohnsoUEFI runtime service I mean19:01
devanandajbjohnso: all BIOS today19:01
jbjohnsodevananda, that's sad...19:02
rameshg87devananda, exactly...s/PXE/virtual media boot/19:02
devanandajbjohnso: so come help add UEFI support. there's a proposal from HP, but we haven't had time to review it19:02
devanandajbjohnso: or more clearly, come help review specs and code for the project. there's not enough of us reviewing to keep up with demand as it is.19:03
*** dkehn__ has joined #openstack-ironic19:03
jbjohnsowell, just keep it in the back of your mind that efibootmgr in-band when possible works in interestingly awesome ways19:03
rameshg87jbjohnso, https://review.openstack.org/99850 uefi review  :-)19:03
JayFI have to leave for the day, thanks for the good chat on ilo spec, I am eager for it to land and will check on it this weekend :)19:04
devanandarameshg87: er, right. I meant, if it uses iSCSI as the deploy mechanism, it'll need to boot from iLO every time19:04
devanandarameshg87: and if it uses IPA as the deploy mechanism, it'll be able to boot from local disk19:04
rameshg87devananda, an alternative to that suggested was to make a swift-temp-url looong enough and keep it attached to the ilo everytime19:04
rameshg87JayF, thanks ...19:04
rameshg87devananda, exactly ..19:04
devanandarameshg87: until the iSCSI deploy method gets support added for local boot loaders19:05
rameshg87devananda, yes, but is there a plan to do so ?19:05
devanandarameshg87: "I wish that it would happen." -- does that count as a plan? :)19:05
*** dkehnx has quit IRC19:06
rameshg87devananda, yes it does, but not for juno i guess :-)19:06
rameshg87devananda, we can try to get in a spec early for K19:06
devanandarameshg87: sounds good19:06
jbjohnsodevananda, I commented some19:07
jbjohnsodevananda, in short, that could be done in a very auto-sensing way and require less configuration by operator19:07
rameshg87devananda, but for now for the ilo driver does this look fine ? - "make a swift-temp-url looong enough and keep it attached to the ilo everytime"19:07
devanandarameshg87: it's hackish and prone to edge failures19:11
devanandarameshg87: curious, does that even need to be a swift tempurl?19:12
devanandarameshg87: if the boot.iso is shared across machines (eg, no private data on it) then why not use the glance URL to it?19:12
rameshg87devananda, the images are expected to be backed by glance, so swift gives away http access easily through temp-url19:13
rameshg87devananda, s/backed by glance/backed by swift/19:13
rameshg87devananda, the boot.iso is shared across machines19:14
devanandarameshg87: right. so why does it need a temp url?19:14
rameshg87devananda, but the url scheme needs to be http for ilo to access it19:14
rameshg87devananda, glance will require authentication in normal mode, right ?19:14
rameshg87devananda, swift anyway provides the feature of temp url which guarantees http access for the images for the specified duration19:15
*** tatyana has quit IRC19:15
rameshg87devananda, so is there a advantage for glance over swift-temp-url ?19:16
devanandarameshg87: swift temp-url encodes the access in the URL, rather than requiring a separate X-Auth-Token header, which iLO does not support sending19:16
rameshg87devananda, yes ..19:16
devanandarameshg87: does a public glance image require an X-Auth-Token header to access it directly? What about a swift  object that is made public?19:17
devanandarameshg87: what I'm getting at is the boot.iso does not need to be private19:17
devanandarameshg87: Setting a long expiration time is a work-around, but it's going to lead to edge cases where it fails19:18
devanandarameshg87: eg, if someone rotates the signing key used to create temp-url's, it will invalidaet previously generated ones19:18
*** Mikhail_D_ltp has joined #openstack-ironic19:18
devanandarameshg87: for a short-duration object, like the vfat image, that's fine. for long-running instances, this would cause them to be unrebootable19:18
rameshg87devananda, yes i agree ..19:19
rameshg87devananda, but i guess for glance/swift, we will still need some specific configuration to directly access the image data from either glance/swift from its APIs19:20
rameshg87devananda, --is-public says "Makes an image accessible for all the tenants"19:22
rameshg87devananda, can't we just offer to boot from virtual media everytime with "reboot from ironic" attaching the boot iso on demand19:25
devanandarameshg87: sure. except we can't control when the user issues a local reboot19:26
*** tatyana has joined #openstack-ironic19:26
rameshg87devananda, yes, the user can still trigger a reboot, but may be trigger a "vendor passthru" before rebooting inband which attaches boot iso ?19:27
devanandarameshg87: in any case, I don't want to hold up driver over this, but it definitely needs to be addressed at some point19:27
devanandarameshg87: please add it as a known limitation right now19:28
rameshg87devananda, if they forget to do so, they always have a second chance to boot it from ironic again19:28
devanandarameshg87: that could be a note on the spec. and it should be(come) a bug in launchpad19:28
devanandarameshg87: right. there is an easy work-around -- just ask ironic to reboot it19:28
*** tatyana has quit IRC19:28
rameshg87devananda, yes ..19:28
rameshg87devananda, okay ..19:28
devanandarameshg87: if this code were already in production, I would classify it as a Medium bug19:28
devanandaaffects-some-users, has-workaround19:28
rameshg87devananda, okay ..19:29
devanandaso as long as that's documented, I'm OK to proceed19:29
rameshg87devananda, "a "vendor passthru" before rebooting inband which attaches boot iso" - does it make sense to have it right now ?19:29
devanandarameshg87: no19:29
devanandarameshg87: if the user is going to issue an API call to reboot, they should just use the existing reboot mechanism19:30
devanandarameshg87: no need to issue an API call to vendor passthru, and _then_ reboot inband19:30
rameshg87devananda, okay, i was just wondering if there was some software update that was going to trigger reboot automatically on the bm node19:30
rameshg87devananda, some inband reboots that are not in user's control19:30
rameshg87devananda, and ironic doesn't support soft reboot right now - it doesn't reboot in the "nice" way19:31
devanandarameshg87: so, on that last comment, actually it looks like iLO does not support "hard" reboot19:31
devanandaon the hardware in the tripleo CI cloud, they observe that an "ipmi chassis power off" command actually issuse an ACPI soft-off19:32
*** dkehn__ is now known as dkehnx19:32
rameshg87devananda, oh okay ..19:32
devanandathat seems like a bug to me, but i haven't dug into it more19:33
devanandaanyway, I need to go AFK for a few hours19:33
rameshg87devananda, okay, then for now i will file a bug for now19:33
rameshg87devananda, and refer it as a limitation with a workaround and repost the spec ..19:33
devanandarameshg87: thanks!19:34
rameshg87devananda, thanks a lot :-)19:34
*** rwsu has joined #openstack-ironic19:37
*** pcrews has quit IRC19:39
*** Mikhail_D_ltp has quit IRC19:45
ShrewsBug 1351026 - 483 fails in 24hrs19:46
Shrewsyowzers19:46
Shrewslol. the fix is to skip the test  :)19:47
NobodyCamlol, Shrews no no the correct fix is to edit the test so it passes LOL....19:50
NobodyCam:-p19:50
Shrews:)19:51
*** jcoufal has quit IRC19:56
*** jcoufal has joined #openstack-ironic19:56
openstackgerritRamakrishnan G proposed a change to openstack/ironic-specs: iLO Virtual Media iSCSI Deploy Driver  https://review.openstack.org/9774420:07
openstackgerritA change was merged to openstack/python-ironicclient: Add {set,get}_boot_device and get_supported_boot_devices  https://review.openstack.org/10964020:08
openstackgerritRamakrishnan G proposed a change to openstack/ironic-specs: iLO-IPA Deploy Driver  https://review.openstack.org/10844520:08
*** rameshg87 has quit IRC20:09
*** f13o_ has joined #openstack-ironic20:12
*** romcheg2 has quit IRC20:18
*** funid has joined #openstack-ironic20:32
*** pcrews has joined #openstack-ironic20:39
*** derekh_ has joined #openstack-ironic20:40
*** jcoufal has quit IRC20:43
*** jgrimm has quit IRC20:45
*** ellenh has quit IRC20:46
*** penick has quit IRC20:50
*** marzif_ has joined #openstack-ironic21:02
*** funid has left #openstack-ironic21:24
*** matty_dubs is now known as matty_dubs|gone21:26
*** jasondotstar has quit IRC21:34
*** romcheg1 has joined #openstack-ironic21:34
*** igordcard has quit IRC21:36
*** pcrews has quit IRC21:41
*** igordcard has joined #openstack-ironic21:50
openstackgerritRoman Prykhodchenko proposed a change to openstack/ironic: Add charset and engine settings to every table  https://review.openstack.org/11140222:06
*** romcheg1 has quit IRC22:39
*** jistr has quit IRC22:50
*** scubacuda has quit IRC23:08
*** mdorman has quit IRC23:19
*** pcrews has joined #openstack-ironic23:23

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