Wednesday, 2015-07-29

NobodyCamg'night jroll00:00
NobodyCam:)00:00
NobodyCamnon-worky: this kinda thing just upsets me :( http://www.bbc.com/news/world-us-canada-3369587200:02
openstackgerritJosh Gachnang proposed openstack/ironic-python-agent: Add node param to base erase_block_device  https://review.openstack.org/20676600:02
JoshNang^ related to the hardware manager API breakage00:03
*** davideagnello has quit IRC00:05
NobodyCamJoshNang: voted ahead of test so I hope it passes  :-p00:05
JoshNangNobodyCam: :P thanks00:06
*** ijw has quit IRC00:12
*** achanda has quit IRC00:15
*** david-lyle has quit IRC00:24
*** puranamr has joined #openstack-ironic00:31
*** mtanino has quit IRC00:34
*** naohirot has joined #openstack-ironic00:37
*** puranamr has quit IRC00:43
*** zhenguo has joined #openstack-ironic00:57
*** meghal has quit IRC01:14
*** r-daneel has quit IRC01:19
*** rloo has quit IRC01:24
openstackgerritTan Lin proposed openstack/ironic: Migrate IronicObjectSerializer to subclass from oslo  https://review.openstack.org/20103801:26
*** chenglch has joined #openstack-ironic01:27
*** Pradip has quit IRC01:31
*** pal has joined #openstack-ironic02:02
*** david-lyle has joined #openstack-ironic02:19
*** david-lyle has quit IRC02:23
openstackgerritMerged openstack/ironic-python-agent: Add node param to base erase_block_device  https://review.openstack.org/20676602:28
*** Qiming has joined #openstack-ironic02:28
*** pal has quit IRC02:35
*** achanda has joined #openstack-ironic02:37
*** boris-42 has quit IRC02:40
*** hakimo has joined #openstack-ironic02:51
*** ukalifon has joined #openstack-ironic02:52
*** hakimo_ has quit IRC02:53
*** bizarrochristy has joined #openstack-ironic02:55
*** bizarrochristy has quit IRC02:58
*** bizarrochristy has joined #openstack-ironic02:58
*** bizarrochristy has quit IRC03:12
openstackgerritShivanand Tendulker proposed openstack/ironic: grub2 bootloader support for uefi boot mode  https://review.openstack.org/16619203:18
*** ukalifon has quit IRC03:21
*** coolsvap|away is now known as coolsvap03:26
*** ramineni has joined #openstack-ironic03:28
*** david-lyle has joined #openstack-ironic03:34
*** pal has joined #openstack-ironic03:40
*** sinval_ has quit IRC03:45
openstackgerritOpenStack Proposal Bot proposed openstack/ironic: Updated from global requirements  https://review.openstack.org/20681503:46
openstackgerritOpenStack Proposal Bot proposed openstack/ironic-lib: Updated from global requirements  https://review.openstack.org/20681603:46
openstackgerritOpenStack Proposal Bot proposed openstack/ironic-python-agent: Updated from global requirements  https://review.openstack.org/20681703:46
*** ishant has joined #openstack-ironic03:48
*** achanda has quit IRC03:55
*** amotoki has joined #openstack-ironic03:56
*** vishwanathj has joined #openstack-ironic04:10
*** rameshg87 has joined #openstack-ironic04:32
*** chenke has quit IRC04:33
*** chenke has joined #openstack-ironic04:33
*** puranamr has joined #openstack-ironic04:38
*** davideagnello has joined #openstack-ironic04:51
*** ukalifon has joined #openstack-ironic05:02
*** ukalifon has quit IRC05:04
*** ramineni1 has joined #openstack-ironic05:07
*** ramineni has quit IRC05:09
*** davideagnello has quit IRC05:12
*** achanda has joined #openstack-ironic05:26
rameshg87ramineni1: hi05:42
ramineni1rameshg87, hi , morning :)05:43
*** saripurigopi has joined #openstack-ironic05:43
ramineni1rameshg87, have just seen your comment05:46
ramineni1rameshg87, but the endpoint is already there, we are just adding a pointer to it05:46
saripurigopimorning Ironic05:46
*** puranamr has quit IRC05:51
rameshg87ramineni1: yeah, but sometimes adding a new attribute requires micro-version bump-up too05:55
rameshg87ramineni1: just like https://review.openstack.org/#/c/193439/ , which starts accepting a node attribute as input05:55
rameshg87ramineni1: but I too don't know. in my opinion it's not required.  it's a general rule followed now, that every change (breaking or non-breaking) in the api requires a micro version change.05:56
rameshg87ramineni1: wdyt ?05:56
ramineni1rameshg87, just wondering , this is not a new functionality as such like the ablove review, so not sure, if its actually required05:59
ramineni1rameshg87, may be we can wait for one more opinion on this :)05:59
rameshg87ramineni1: yeah06:00
rameshg87ramineni1: let's wait ..06:00
ramineni1rameshg87, :)06:00
SpamapSTheJulia: sh: 1: debootstrap: not found ...06:06
SpamapScinerama: ^06:06
SpamapSNeed to add that to the env setup.06:07
openstackgerritRamakrishnan G proposed openstack/ironic: Add RAIDInterface for RAID configuration  https://review.openstack.org/19600306:11
*** chenke has quit IRC06:15
openstackgerritRamakrishnan G proposed openstack/ironic: Add RPCAPIs for RAID configuration  https://review.openstack.org/19600606:25
*** Nisha has joined #openstack-ironic06:27
*** zhenguo has quit IRC06:32
*** Marga_ has quit IRC06:36
*** zhenguo has joined #openstack-ironic06:40
*** Marga_ has joined #openstack-ironic06:40
openstackgerritOpenStack Proposal Bot proposed openstack/ironic: Imported Translations from Transifex  https://review.openstack.org/20690306:40
openstackgerritRamakrishnan G proposed openstack/ironic: Add APIs for RAID configuration  https://review.openstack.org/19600706:43
openstackgerritGopi Krishna S proposed openstack/ironic: UCS: node-get-boot-device is failing for Cisco servers  https://review.openstack.org/20652806:49
*** Haomeng has joined #openstack-ironic06:51
*** Haomeng|2 has quit IRC06:54
*** achanda has quit IRC06:54
*** karimb has joined #openstack-ironic06:57
*** athomas has joined #openstack-ironic06:57
*** achanda has joined #openstack-ironic06:57
*** uggla_ has joined #openstack-ironic07:00
*** davideagnello has joined #openstack-ironic07:13
*** uggla_ has quit IRC07:14
*** adam_g has quit IRC07:14
*** davideagnello has quit IRC07:17
*** karimb has quit IRC07:22
*** karimb has joined #openstack-ironic07:23
*** achanda has quit IRC07:27
*** romainh has joined #openstack-ironic07:36
*** dtantsur|afk is now known as dtantsur07:37
dtantsurMorning Ironic07:37
Nishadtantsur, o/07:42
mrdaMorning dtantsur07:44
Nishadtantsur, i was trying inspector ramdisk manually. it reports disk size 1 less than the actual07:45
Nishadtantsur, i used the returned value as the root device hint and the deploy failed07:46
Nishadtantsur, i read the comments as "07:46
Nisha# NOTE(dtantsur): -1 is required to give Ironic some spacing for partitioning and may be removed later07:46
Nisha"07:46
Nishadtantsur, i think this is misleading from inspection results07:47
*** yog__ has joined #openstack-ironic07:47
dtantsurNisha, if you don't do it, deploy will fail07:51
dtantsurso yeah, it's not good, but without it we'll need to do this -1 manually07:51
Nishadeploy in which scenario07:51
dtantsurNisha, any07:51
dtantsurwell, at least iscsi07:52
dtantsurlast time I checked our partitioner failed when local_gb was strictly equal to the disk size07:52
* dtantsur should probably mention it in some "known issues" section...07:52
Nishai used the size returned by inspector ramdisk as root device hint, and deploy failed07:52
Nishabut when i used exact integer size i.e. floating value dropped off, it works fine07:53
dtantsuras root device hints - yes, probably. I'm not sure what to do about it...07:53
Nishadtantsur, means? the returned value would/could be used as root device hint07:54
dtantsuryep, but you have to +1gib until we know how to solve problem with partitioner07:55
Nishahmmm07:55
*** ukalifon1 has joined #openstack-ironic07:55
dtantsurNisha, for your reference: https://github.com/openstack-dev/devstack/blob/master/tools/ironic/scripts/create-node#L15-L1707:56
dtantsurwe do it in devstack as well...07:56
*** pal has quit IRC07:59
*** yog__ has quit IRC07:59
*** natorious is now known as zz_natorious07:59
Nishadtantsur, got it08:02
Nishai had set the local_gb to some arbitrary value for solving one issue, so was not using actual disk size in local_gb08:02
Nishabut in ilo drivers we dont do this ...and using the inspection result works....08:04
Nishaam just wondering if its specific to some drivers...or applies to all08:05
Nishaneed to recheck08:05
*** jistr has joined #openstack-ironic08:08
*** ndipanov has quit IRC08:14
*** ndipanov has joined #openstack-ironic08:14
openstackgerritRamakrishnan G proposed openstack/ironic: Add support for inband raid configuration agent ramdisk  https://review.openstack.org/19823808:16
openstackgerritRamakrishnan G proposed openstack/ironic: Refactor agent driver with pxe boot interface  https://review.openstack.org/16652108:16
rameshg87dtantsur: hi08:16
*** yog__ has joined #openstack-ironic08:16
rameshg87dtantsur: https://review.openstack.org/#/c/206487/1/specs/liberty/ironic-ml2-integration.rst L87, I didn't get the comment #208:17
*** lucasagomes has joined #openstack-ironic08:17
*** karimb has quit IRC08:17
dtantsurrameshg87, 1. "out of band BMC" seems self-repeating, 2. virtual media boot is not a netboot IMO08:18
*** ifarkas has joined #openstack-ironic08:18
rameshg87dtantsur: I got the first one.08:19
rameshg87dtantsur: but virtual media is a sort of "netboot", right ?08:19
dtantsurhmmm, no?08:19
rameshg87dtantsur: we  make the machine boot from an external source in your network08:19
dtantsurdoes it use PXE?08:19
rameshg87dtantsur: ah, pxe == netboot, seems too much restrictive to me08:20
rameshg87dtantsur: it's our term08:20
rameshg87dtantsur: but still in virtual media we boot the machine from an external source in the network08:20
dtantsurI mean, yeah, in some sense it is netboot, but for many people netboot is related to the machine fetching something from network on start up, not out-of-band08:20
rameshg87dtantsur: eh "fetching something from network on start up" is applicable and true here as well08:21
dtantsurrameshg87, so it would be cool if you avoid calling it netboot, just stating that it's still possible to use virtual media boot with some drivers08:21
dtantsurI just don't want people to read it as "some drivers allow PXE to work" :)08:21
rameshg87dtantsur: okay, got it. but in general, all over ironic, notion of "netboot" applies to pxe and virtual media booting08:22
rameshg87dtantsur: for example if someone requests "netboot" as "true" in flavor in nova, you get a node that boots from virtual media08:22
dtantsurinteresting. then fine, you can call it "netboot", but it's worth adding something like "because virtual media boot does not need an instance to access conductor on boot"08:24
dtantsuror something08:24
rameshg87dtantsur: ack, thanks08:30
rameshg87will add it08:30
*** ramineni1 has quit IRC08:32
lucasagomesrameshg87, hi there08:33
rameshg87lucasagomes: hi08:34
lucasagomesrameshg87, re lazy delete instance08:34
lucasagomesrameshg87, what you suggest to remove the periodic task?08:34
openstackgerritRamakrishnan G proposed openstack/ironic-specs: Update neutron integration spec  https://review.openstack.org/20648708:34
lucasagomeswithout having a racy code08:34
*** romcheg has joined #openstack-ironic08:34
rameshg87lucasagomes: I don't know if what I proposed was a good one08:35
rameshg87lucasagomes: if we are a non-stable state, someone is actually holding a lock on the system08:35
lucasagomesrameshg87, oh at the process_event()?08:35
lucasagomesbut that's racy08:35
lucasagomesbecause between the check of the flag08:36
lucasagomesand the actual change of state there's a window there08:36
rameshg87hmm..yeah08:36
rameshg87but first in any case, if we are having a new field in the db, we will need to update it without a lock08:37
rameshg87but advantage with periodic task is if it missed first time, it can do it second time, right ?08:37
*** ukalifon1 has quit IRC08:37
lucasagomesexactly08:37
lucasagomeswe guarantee that it's going to be deleted eventually08:37
lucasagomesand we won't end up with a orhpan node that was suppose to be deleted but wasn't because the code is racy08:38
*** ramineni1 has joined #openstack-ironic08:38
rameshg87lucasagomes: ack, I agree. I will just rethink, please ignore my comment till then08:39
lucasagomesrameshg87, it's ok... let's think08:39
lucasagomesrameshg87, I think it would be useful to have a generic thing08:39
lucasagomesbut there are some differences08:39
rameshg87lucasagomes: yeah, I thought we might have something similar for other things as well08:39
rameshg87lucasagomes: when we have interactive clients (other than nova), talking to ironic08:40
rameshg87lucasagomes: particularly when we have stuffs like ui coming up08:40
*** e0ne has joined #openstack-ironic08:40
rameshg87the same thing might be applicable to all other *ING states as well08:40
lucasagomesrameshg87, right08:41
lucasagomesI replied to the comment08:41
lucasagomesrameshg87, as you suggest we may want to call that field somewhat more generic, what about "abort_operation"?08:41
lucasagomesbut even then there're some differneces, a node in DEPLOY* are expect to transition to AVAILABLE after abort08:42
lucasagomesstates like CLEANING they need to stay at CLEANFAIL and not restart cleaning again08:42
*** athomas has quit IRC08:42
lucasagomesthere are different behaviors when aborting states08:43
*** e0ne has quit IRC08:43
lucasagomesthat's why I decided to minimize the scope for that spec and fix the interaction with nova firtst08:43
lucasagomesfirst*08:43
lucasagomesalso other states will need a new API verb for it, "deleted" can't be used for cleaning, inspecting or zapping because deleting an isntance at those states makes no sense08:44
lucasagomesit's expected to the instance to be deleted already08:44
rameshg87lucasagomes: yeah, but making it even abort_operation is tougher there, right ?08:46
rameshg87lucasagomes: because the periodic task (or whatever) which checks this flag has to decide what to do with the node08:46
rameshg87lucasagomes: if node in states.X, do A; if node in states.Y do B; etc, right ?08:47
rameshg87lucasagomes: yeah, avoiding race condition seems tougher without a periodic task :(08:48
lucasagomesrameshg87, exactly08:48
lucasagomesit's hard that's why I limited the scope08:48
lucasagomescurrently the nova interaction is biting me. We use heat that talks to nova that talks to Ironic08:49
lucasagomeswhen the heat stack fails it tries to delete the instances in nova to rollback08:49
lucasagomeswhich makes nova calls Ironic when nodes are still being deployed08:49
lucasagomesand things goes mad there08:49
lucasagomesso I limited the scope of that patch to fix it08:49
lucasagomesrameshg87, I believe the generic 'abort' will be something else, as I mentioned it needs more than that. A new API call etc08:50
lucasagomesso it may have it's own mechanism08:50
rameshg87lucasagomes: okay08:52
* rameshg87 needs to look at abort spec 08:52
lucasagomesrameshg87, right so should I rename the field to abort_operation? and then in another spec we can reuse it for other tasks?08:53
lucasagomesI think it's ok08:53
rameshg87lucasagomes: but abort_operation turns out to be "delete" for DEPLOYING and "abort" for other *ING, right ?08:55
lucasagomesrameshg87, yeah that's what sucks :-(08:55
lucasagomesok let's keep delete_instance cause it's specific08:55
*** pelix has joined #openstack-ironic08:55
rameshg87lucasagomes: yeah, even I don't have a better opinion on that. let's keep it delete_instance until we all agree we have something better.08:55
lucasagomesrameshg87, ++08:56
lucasagomesfair enuff... rameshg87 thanks for the discussion!08:56
rameshg87lucasagomes: thanks :)08:56
*** pal has joined #openstack-ironic08:57
*** coolsvap is now known as coolsvap|away09:04
*** amotoki has quit IRC09:05
*** dtantsur is now known as dtantsur|brb09:12
*** coolsvap|away is now known as coolsvap09:12
*** ftersin has joined #openstack-ironic09:14
*** athomas has joined #openstack-ironic09:16
openstackgerritShivanand Tendulker proposed openstack/ironic: Secure boot support for pxe_ilo driver  https://review.openstack.org/15480809:18
*** ftersin has left #openstack-ironic09:22
*** alexpilotti has joined #openstack-ironic09:25
*** romcheg has quit IRC09:27
-openstackstatus- NOTICE: Currently our CI system is broken, jobs are not getting processed at all.09:28
*** ChanServ changes topic to "Currently our CI system is broken, jobs are not getting processed at all."09:28
*** MattMan has quit IRC09:31
*** romcheg has joined #openstack-ironic09:31
*** MattMan has joined #openstack-ironic09:32
*** romainh has left #openstack-ironic09:37
*** yuikotakada has joined #openstack-ironic09:38
*** romainh has joined #openstack-ironic09:39
openstackgerritNaohiro Tamura proposed openstack/ironic: Add hardware inspection module for iRMC driver  https://review.openstack.org/19648009:42
*** chenglch has quit IRC09:43
*** mdbooth has quit IRC09:46
*** mdbooth has joined #openstack-ironic09:47
*** alex_xu has quit IRC09:48
*** alex_xu has joined #openstack-ironic09:49
*** coolsvap is now known as coolsvap|away09:50
ramineni1dtantsur|brb, lucasagomes , any comments on this https://review.openstack.org/#/c/203921/09:53
ramineni1dtantsur|brb, lucasagomes , do we need a micro version bump on this?09:53
lucasagomesrameshg87, hi there... we according to what we are following right now yes09:55
lucasagomeseverytime we change the syntax of the API (adding new thing, removing etc...) we should bump the version09:55
*** naohirot has quit IRC09:56
*** Qiming has quit IRC09:56
*** e0ne has joined #openstack-ironic09:57
*** coolsvap|away is now known as coolsvap09:58
rameshg87lucasagomes: yeah, that's what I thought09:59
rameshg87lucasagomes: so I think in ramineni1's case we should do it10:00
lucasagomesrameshg87, but I don't get much that change, why it's adding it only to properties?10:00
lucasagomesI mean other controllers like Node has plenty of endpoints like that10:00
*** ifarkas has quit IRC10:00
*** thiagop has quit IRC10:00
*** mjturek1 has quit IRC10:00
*** yuriyz has quit IRC10:00
*** mitz has quit IRC10:00
*** yuanying has quit IRC10:00
*** dguerri` has quit IRC10:00
*** mitz has joined #openstack-ironic10:00
*** yuriyz has joined #openstack-ironic10:00
*** thiagop has joined #openstack-ironic10:00
*** ifarkas has joined #openstack-ironic10:01
*** yuanying has joined #openstack-ironic10:01
*** dguerri` has joined #openstack-ironic10:01
*** dguerri` is now known as dguerri10:01
*** dguerri has joined #openstack-ironic10:01
rameshg87lucasagomes: hmm..that's true10:01
*** mjturek1 has joined #openstack-ironic10:01
lucasagomesnodes/<uuid>/states,  nodes/<uuid>/validate10:01
lucasagomesand more nested ones10:01
lucasagomeslike nodes/<uuid>/states/power10:01
lucasagomesetc...10:01
rameshg87lucasagomes: but is there some recommendation on what all to provide links ?10:02
*** e0ne_ has joined #openstack-ironic10:02
rameshg87lucasagomes: I understand we gave for ports as it's another type of resources that a node composes10:02
lucasagomesyeah we link the resource itself and the subresources10:02
lucasagomesthe endpoints are documented10:03
lucasagomeswe should have a schema on the API etc10:04
*** pelix1 has joined #openstack-ironic10:04
*** pelix has quit IRC10:04
*** pelix1 is now known as pelix10:04
rameshg87lucasagomes: I don't have an idea someone will be using these links, when they can basically code it to find it10:04
*** pelix has quit IRC10:04
*** pelix has joined #openstack-ironic10:04
rameshg87lucasagomes: links like /v1/drivers/foo/properties10:04
rameshg87when someone knows it is documented in the API, they will make 2 REST calls to first GET on /v1/drivers/foo and then find link and then go there10:05
*** e0ne has quit IRC10:05
*** athomas has quit IRC10:05
*** e0ne_ is now known as e0ne10:06
*** athomas has joined #openstack-ironic10:06
rameshg87lucasagomes: but for nested endpoints, links can be further provided within, right ?10:07
rameshg87lucasagomes: you might wanna take a look at this too - https://review.openstack.org/#/c/205895/10:07
lucasagomesrameshg87, yeah I think what we want to make it all discoverable programatically like that is having a json schema10:07
lucasagomesnot exposes links10:07
*** Nisha has quit IRC10:08
*** Pradeep has joined #openstack-ironic10:12
*** Pradeep has quit IRC10:12
*** PradeepV has joined #openstack-ironic10:12
*** zhenguo has quit IRC10:13
PradeepVHi All,10:14
PradeepVmy ironic node provision state is in cleaning state and i am not able to delete it,  getting error as "InvalidState: Can not delete node "b56c24cd-f19c-4da2-a123-b6b0b52162f3" while it is in provision state "cleaning"."10:14
PradeepVhow to delete the ironic node10:15
rcarrillocruzPradeepV: you will have to change its state on the mysql DB10:16
rcarrillocruzto available10:16
rcarrillocruzprior to being able to delete10:16
rcarrillocruzrun something like:10:16
lucasagomesPradeepV, yeah currently nodes can get stuck on those transitioning states, which is pretty bad10:16
lucasagomeswe are trying to sort it out by introducing things like CLEANWAIT (already merged)10:16
rcarrillocruzsudo mysql ironic -e "update nodes set provision_state='available' where  uuid='your_server_uuid'"10:17
rcarrillocruzthen you'll be able to do ironic node-delete uuid10:17
lucasagomesbut yeah right now you will need to clean the db unfortunately10:17
*** degorenko has quit IRC10:17
PradeepVThank you Carrill it worked...10:19
PradeepVlucasagomes..why is it getting stuck in that state10:20
*** romainh has quit IRC10:20
lucasagomesPradeepV, because the conductor doesn't know how to resume if something fails10:20
lucasagomesand we don't offer any API so you can get out of that state10:21
lucasagomeslike aborting that operation for e.g10:21
PradeepVok lucasagomes, thank you10:21
*** dtantsur|brb is now known as dtantsur10:30
dtantsuroh, gate is broken again....10:36
sambettsdtantsur: yup10:36
sambettsdtantsur: its not doing very well at the moment at being stable10:36
dtantsursigh... I guess openstack upstream has grown too large10:37
lucasagomesdtantsur, https://github.com/openstack/ironic/blob/master/ironic/conductor/manager.py#L804-L81710:39
lucasagomesdtantsur, unless one changes the database it won't be possible to the instance_info to not be cleaned there10:39
dtantsurlucasagomes, ok, nevermind me then. I'll review properly a bit later.10:40
lucasagomesack10:40
dtantsurtbh I spent so much time thinking about versioning, so I can hardly think about anything10:40
lucasagomesheh fair enuff10:40
dtantsurand now this enroll discussion... I regret I even bothered with this enroll change10:41
lucasagomesdtantsur, well do not. Cause I think we agreed the problem is not the enroll10:42
lucasagomesbut how we version stuff10:42
lucasagomesenroll just made it more apparently because now we have to deal with it10:42
dtantsurI'm not sure deva agrees with it10:42
lucasagomesenroll is part of the spec as the entry point for the state machine since it started10:43
lucasagomesand was approved like that10:43
*** Qiming has joined #openstack-ironic10:43
dtantsuryep. several times.10:43
dtantsurand we really need it. *at least* because we need verification step.10:43
sambettsand I want to use Enroll too10:44
*** Qiming has left #openstack-ironic10:44
sambettsthe think I've noticed is all these discussions revolve around existing users, and seem to ignore that new users just want the full feature set as it is without having to "opt-in"10:45
dtantsurthese discussions didn't get users involved at all :-/10:46
dtantsurwe just *assume* we know what users want10:46
sambettsironic is a weird one anyway because the users of ironic aren't the same as the users in the OpenStack sense10:47
dtantsur(I don't state that our assumption is wrong obviously, just pointing out)10:47
sambetts:-P yes10:47
*** thrash|g0ne is now known as thrash10:48
sambettsimo (ignore the standalone case) users talk to ironic through something like nova, and ops talk directly to ironic10:48
dtantsurfor example about versioning: I didn't receive an answer to my question "how should inspector deal with ironic API versioning"10:48
dtantsurI'm an API user, and I still don't know10:48
dtantsuror rather I don't understand. all cases look pretty bad to me.10:49
dtantsurwith enroll it's a bit easier: I don't want give another opportunity to mess enrolling a node, some people do it often enough10:49
sambettsyeah :/ while I was reading the thread this morning, I relised how much I hate calling the client the client10:49
dtantsurok, I'm repeating myself :)10:50
sambettsI don't think we should think of it as a client, but as a python API hook and as an api command line interface (which is what CLI means...) which means the version your using should be dictated by the server your talking to10:52
dtantsursambetts, I think you should add your opinion to the ML thread, so that it's not get lost here10:52
sambettsI wanted to bounce it off you first ;)10:53
dtantsurwell, I kind of agree that our stuff should be a thin layer on the way to the server10:53
*** coolsvap is now known as coolsvap|away10:55
lucasagomesdtantsur, perhaps inspector should use a specific version of the API? and require it?10:57
lucasagomesor support X versions of the API10:57
dtantsurlucasagomes, we don't have notion of supporting "X versions"10:58
lucasagomesX = in the plural I mean10:58
dtantsurwe can request one version, and fail if it's not available10:58
lucasagomesdtantsur, yeah say, right now to inspect a node you need the version 1.10 of the API10:58
lucasagomesso all calls that inspector does to Ironic should use that version10:58
dtantsuryeah, maybe...10:59
lucasagomesdtantsur, right that's like inspector being the client of our API10:59
lucasagomesit's the same as we say "client should mandatory indicate the version"10:59
lucasagomesinspection could have a set of supported versions that it has been tested with10:59
dtantsurlucasagomes, but when Juno was supported by discoverd, it was a bit bigger problem10:59
lucasagomesand user can chose between those10:59
lucasagomesdtantsur, right yeah because there was no versioning at that time11:00
dtantsurI can't have a set of supported versions. the only version supported is version I gate tests against11:00
lucasagomesdtantsur, fair enuff... Inspector can require a specific version of the API to work with11:01
lucasagomesor at least a fallback to the very minimal version11:01
lucasagomes1.111:01
lucasagomesthat was is good because you make inspector to always work independent of how the Ironic API grows11:01
lucasagomesidk it seems analogous to say, this software requires lib version X... you can say inspector requires Ironic API version X too11:02
lucasagomes(just an idea)11:02
dtantsurif I hardcode 1.2 (we need to know about AVAILABLE), then I afraid it will break sambetts' plugin that requires ENROLL11:04
dtantsur(not sure if this plugin already exists)11:04
sambettsdtantsur: not yet, but its on my to do list11:04
dtantsurI see11:04
dtantsurlucasagomes, btw we don't hide current node state even if it's not supported by the API, do we?11:05
* dtantsur writes docs on API versioning11:06
lucasagomesdtantsur, yeah as requiremets grow you can require new versions of the API or disable that feature when the API is not newer enough11:06
lucasagomesdtantsur, I think it gets translated yes11:06
dtantsurlucasagomes, all states? like MANAGEABLE, INSPECTING, etc?11:07
lucasagomesat least AVAILABLE -> NOSTATE11:07
*** Haomeng|2 has joined #openstack-ironic11:07
dtantsurI hope it's the only one actually11:07
lucasagomesoh yeah I think that's the only one11:07
*** athomas has quit IRC11:08
lucasagomesyeah I'm not advocating on feature hiding here... but just that you can get some stability by making inspector to explicitly support a version (or some versions) of the Ironic API11:08
lucasagomesat least for the basic functionality11:09
dtantsuryeah, I think so11:09
*** Haomeng has quit IRC11:10
lucasagomesthat would also allow you to have a clear path for upgrades... 1. upgrade ironic 2. upgrade inspector11:10
lucasagomesat all times11:10
lucasagomeswith the guaarantee that an older version of inspector will continue to work while ironic is being updated across the cluster11:11
lucasagomes(and mixed versions of Ironic may be present at one time)11:11
lucasagomesanyway... food for thought11:12
*** romainh has joined #openstack-ironic11:14
PradeepVI am able to boot up an instance using pxe boot, but the ssame setup is failing when booting an instance using agent driver , getting error as "2015-07-29 16:12:36.310 ^[[01;31mERROR nova.openstack.common.loopingcall [^[[00;36m-^[[01;31m] ^[[01;35m^[[01;31min fixed duration looping call"11:17
* rameshg87 goes home11:18
*** rameshg87 has quit IRC11:18
*** e0ne has quit IRC11:25
TheJuliaSpamapS: Wow you were up late...11:25
TheJuliaGood morning everyone11:26
*** romcheg has quit IRC11:28
dtantsurTheJulia, morning11:29
sambettsmorning TheJulia11:31
lucasagomesTheJulia, good morning11:32
*** ramineni1 has quit IRC11:32
lucasagomesPradeepV, the message is not very helpful11:32
lucasagomesI will grab a quick sandwich and I can try helping out once I'm back11:33
*** lucasagomes is now known as lucas-hungry11:33
*** e0ne has joined #openstack-ironic11:35
openstackgerritDmitry Tantsur proposed openstack/ironic: Document API versioning  https://review.openstack.org/20699911:36
dtantsurlucas-hungry, jroll, devananda and others: please review ^^ I tried to capture the current state of things11:37
PradeepVI will lucasagomes,11:37
*** pal has quit IRC11:37
TheJuliaPradeepV: Realistically we would need logs and insight into the different node configurations that is present with each driver loaded11:38
* TheJulia sips more coffee11:38
*** saripurigopi has quit IRC11:38
sambettsTheJulia: I'm just going through it with him on IM, its weird as hell :-P11:41
*** Haomeng has joined #openstack-ironic11:42
TheJuliasambetts: Joy :)11:42
*** Haomeng|2 has quit IRC11:45
* sambetts thinks coffee might be a good idea 11:49
*** coolsvap|away is now known as coolsvap11:51
TheJuliaYes, coffee is a very good idea11:52
*** athomas has joined #openstack-ironic11:56
*** e0ne has quit IRC11:59
*** pal has joined #openstack-ironic12:03
*** ukalifon has joined #openstack-ironic12:06
openstackgerritSinval Vieira Mendes Neto proposed openstack/ironic: Add more info level log to deploy_utils.work_on_disk() method  https://review.openstack.org/20538712:07
*** pal has quit IRC12:07
dtantsurlucas-hungry, one thing that prevents me from requiring ironic API version 1.2 (or many other) is that it is not (and was not ever) gate tested12:08
*** sinval_ has joined #openstack-ironic12:09
*** jjohnson2 has joined #openstack-ironic12:17
*** coolsvap is now known as coolsvap|away12:17
*** romcheg has joined #openstack-ironic12:19
openstackgerritDmitry Tantsur proposed openstack/ironic-inspector: Require ironic API version 1.6  https://review.openstack.org/20701812:24
dtantsurlucas-hungry, also ^^12:24
*** e0ne has joined #openstack-ironic12:25
*** vikas has joined #openstack-ironic12:30
*** mjturek1 has quit IRC12:31
NobodyCamgood morning Ironicers, from the man making kofi12:33
*** ishant has quit IRC12:36
sambettso/ NobodyCam12:37
*** kkoski has joined #openstack-ironic12:38
*** lucas-hungry is now known as lucasagomes12:38
lucasagomesdtantsur, cool! Yeah, tempest have no notion of microversioning AFAICT right now12:39
lucasagomesthat should change12:39
dtantsurlucasagomes, https://review.openstack.org/#/c/166386 :)12:39
lucasagomesNobodyCam, morning12:39
dtantsurNobodyCam, morning!12:39
lucasagomesyup! o/12:40
vikasHi Guys..I have  installed all-in-one ironic enabled devstack .When I am trying to launch a image on virtual baremetal node,I can see on vnccosole that rernel and ramdisk images are downloaded successfully but it doesnt go further after that and server state on dashboard get stuck at "spawning".Please suggest me something where could be the problem and how can i debug this?12:40
vikasHelp please12:40
NobodyCammornig lucasagomes dtantsur TheJulia sambetts12:41
lucasagomesvikas, the console is redirected to a file at /opt/stack/ironic-bm-logs/baremetalbrbm_0_console.log12:41
lucasagomesyou can do a tail -f there and see it booting12:42
lucasagomesor see a more specific error12:42
NobodyCamvikas: what state is the node in "wait for call back"?12:42
* NobodyCam gets coffee12:43
vikasyes in ir-cond logs , after a long time it changes state from "wait-for-call-back" to "fail"12:43
vikasusing vnc console i can see node fetching images from tftp server12:43
lucasagomesvikas, yeah check the file where the console is being redirect to see what's going on there12:44
vikasafter fetching ramdisk it says "ready"12:44
vikasand thats it12:44
vikasok..12:44
vikaswill get back12:45
lucasagomesor you can disbale the redirection by removing the "console=ttyS0" kernel option from the "pxe_append_params" configuration option at /etc/ironic/ironic.conf12:45
lucasagomesthen restart the conductor12:45
lucasagomesand restart the deployment12:45
vikasok.. will try this also12:45
vikasThanks.. :)12:46
lucasagomescool12:46
openstackgerritDmitry Tantsur proposed openstack/ironic: Only take exclusive lock in sync_power_state if node is updated  https://review.openstack.org/20256212:46
*** mjturek1 has joined #openstack-ironic12:46
lucasagomesfolks if you guys have a time https://review.openstack.org/#/c/205142/ (deprecate bash ramdisk)12:46
*** afaranha has quit IRC12:47
*** coolsvap|away is now known as coolsvap12:48
*** ChanServ changes topic to "Bare Metal Provisioning | Status: http://bit.ly/ironic-whiteboard | Docs: http://docs.openstack.org/developer/ironic/ | Bugs: https://bugs.launchpad.net/ironic"12:50
-openstackstatus- NOTICE: zuul's disks were at capacity. Space has been freed up and jobs are being re-queued.12:50
*** pal has joined #openstack-ironic12:54
openstackgerritLucas Alvares Gomes proposed openstack/ironic-specs: Lazy delete instances  https://review.openstack.org/20416212:55
NobodyCamlucasagomes: do you know if the DIB IPA element still requires over three gig of ram?12:55
lucasagomesfolks if you guys have a time ^ as well12:55
lucasagomesNobodyCam, hi there, hmm I don't know the current state of it exactly12:55
lucasagomestrown, ^ you have been testing it right?12:56
NobodyCammy fear (maybe unfounded) is that we may lose support for unber powered test nodes.. ie if they only have 1 gig of ram12:57
lucasagomesNobodyCam, the coreos version of IPA works with 1GB ram12:57
lucasagomesthat's what we use in gate to test12:57
dtantsur++12:57
NobodyCam++12:58
sambettsSigh... outlook and openstack mailers don't play nice together... its butchered my reply to the versioning thread...12:58
TheJulialucasagomes: coreos deploying via iscsi? or downloading the image12:59
TheJulia?12:59
lucasagomessambetts, heh do not use outlook :-) (jk, you can use whatever u want)12:59
lucasagomesTheJulia, both12:59
lucasagomesTheJulia, IPA (the service) supports both12:59
sambettslucasagomes: its only my work mail that goes through it ;)12:59
lucasagomesand both are tested on gate12:59
dtantsurwell, image download has its restrictions12:59
lucasagomesTheJulia, gate-tempest-dsvm-ironic-pxe_ipa - Tests IPA with ISCSI13:00
*** vikas_ has joined #openstack-ironic13:00
lucasagomesTheJulia, gate-tempest-dsvm-ironic-agent_ssh - Tests IPA with agent13:00
lucasagomesI know the names are horrible...13:00
trownNobodyCam: lucasagomes, checking how much memory my test VMs have13:00
dtantsurour usual default is 4GiB IIRC13:01
trownwell they have 4GB each, since I have been testing in the context of tripleo13:01
TheJuliaI know, thats what I thought, that it had to be iscsi since downloading a 300mb image requires tons of ram to get pushed out to disk13:01
lucasagomesvikas, so if you tftp is running on a different server13:02
lucasagomesvikas, you have to configure the "tftp_server" configuration option at /etc/ironic/ironic.conf to point to it13:02
vikas_my tftp server is 10.0.0.413:02
vikas_yes its this ip only13:02
vikas_10.0.0.4 in ironic.conf13:03
lucasagomesthere are two options related to tftp in Ironic "tftp_server" and "tftp_root"13:03
vikas_and bm node downloading pxelinux.0 from 10.0.0.4 on;y13:03
lucasagomesthe root is the root directory of the tftp, this should be accesible to the ironic-conductor13:03
lucasagomesvikas, oh right so the tftp doesn't seem to be a problem here13:04
lucasagomesvikas, I see  "curl: (7) Failed to connect to 127.0.0.1 port 6385: Connection refused"13:04
lucasagomesthis seems to be the agent trying to access the Ironic API13:04
vikas_ok13:04
lucasagomescan you check if you have any firewall rules blocking a tcp connection to the port 6385 ?13:04
lucasagomesTheJulia, yeah the agent_ssh uses the cirros image13:05
lucasagomeswhich is ~30MB I think13:05
vikas_but how can this bm node which is a vm reach 127.0.0.1 of underlying host13:05
lucasagomesso it's grand... TheJulia but in the future IPA should stream the image and not 1. download then 2.write to the disk13:06
vikas_my internal network is 50.0.0.0/2413:06
lucasagomesvikas, it should be fine, your testing with nested VMs?13:06
lucasagomesthe VM being deployed is running at the same server as the Ironic services, right?13:07
TheJulialucasagomes: agreed, a lthough I suspect that is going to require some fun support to be added :)13:07
vikas_not nested VMs13:07
lucasagomesTheJulia, yeah... well... we can pipe stuff13:07
vikas_only bm node is vm13:07
lucasagomesthere's also some conversion that should happen on the fly there as well13:07
lucasagomesvikas, oh ok... I though you said "all-in-one"... So the services are in one VM and the Baremetal node is in another right?13:08
lucasagomesand you have a bridge network between both VMs?13:08
vikas_yes through neutron router13:08
vikas_and services are in physical ubuntu machgine13:09
TheJulialucasagomes: Yes, I'm not sure qemu-img will support piped input though, but its been a while since I dug through the code13:09
* TheJulia needs more coffee13:09
NobodyCamso does /me13:09
lucasagomesvikas, right, can you boot something on the machine u want to deploy and see if that can reach the Ironic API/13:09
lucasagomes?*13:09
lucasagomesI think there's something going on there13:10
*** rloo has joined #openstack-ironic13:10
vikas_ironic api is running on 10.0.04 (same as tftp server,on physical ubuntu)13:10
vikas_from where i can change this 127.0.0.1 to 10.0.0.413:11
vikas_so that this curl command will not fail13:11
vikas_bm_node can reach services through neutron router only in my setup13:12
vikas_bm_node is in 50. network and services on 10.13:12
*** coolsvap is now known as coolsvap|away13:14
*** degorenko has joined #openstack-ironic13:14
lucasagomesvikas, /etc/ironic/ironic.conf under [api] you have an option called "host_ip"13:16
lucasagomesyou can change it there13:16
vikas_cool13:17
openstackgerritDmitry Tantsur proposed openstack/ironic-inspector: Use retries provided by ironicclient instead of ad-hoc ones  https://review.openstack.org/20703713:19
dtantsurwe should do this ^^^ with nova too, but we need https://review.openstack.org/#/c/206041/13:24
-openstackstatus- NOTICE: zuul jobs after about 07:00 UTC may need a 'recheck' to enter the queue. Look if your change is in http://status.openstack.org/zuul/ and recheck if not.13:26
*** caiobo has joined #openstack-ironic13:27
*** albertoffb has joined #openstack-ironic13:27
openstackgerritMerged openstack/ironic-lib: Updated from global requirements  https://review.openstack.org/20681613:28
*** [1]cdearborn has joined #openstack-ironic13:29
lucasagomesTheJulia, you guys run ironic-api under apache wsgi right?13:34
jrollmorning lucasagomes dtantsur TheJulia vikas_ sambetts and trown :)13:35
lucasagomesjroll, hey13:35
trownmorning jroll13:35
dtantsurjroll, o/13:35
NobodyCammornign jroll13:35
jrolldtantsur: re versioning with inspector... why not let the user set the version? (and plugins like sam's can require 1.11 or whatever)13:35
jrolloh and NobodyCam!13:35
jrollmorning :)13:35
lucasagomesjroll, I know you need coffee still, but if you have a time mind taking a peek at https://review.openstack.org/#/c/204162/ ?13:35
NobodyCam:-p13:36
jrolllucasagomes: dmitry wrote version docs, he gets first dibs on review :P13:36
dtantsur+1 :)13:36
jrollI'll try to get to that today though13:36
dtantsurjroll, I think as we define it, API version is something defined by the client code, not by its user. I can't be sure my code will work with API v1.0 just because a user sets it13:38
jrolldtantsur: I mean, in theory you could test all versions :)13:39
jrolldtantsur: more realistically, you can say "1.2 is tested and fully supported, use others at your own risk" or whatever13:39
dtantsurwell, all past versions :) I can't test future versions (I wish I could)13:39
jrollheh13:39
*** vikas has quit IRC13:40
lucasagomesjroll, heh fair enuff13:41
*** romainh has left #openstack-ironic13:44
*** PradeepV has quit IRC13:45
TheJulialucasagomes: no, we run standalone without apache13:45
lucasagomesTheJulia, I see13:47
jrolldtantsur: I has comments for you13:48
jrolllucasagomes: so are you trying to figure out how to run it in apache?13:48
lucasagomesjroll, yes, I believe it's just copying the etc/apache2/ironic under the apache vhost folder13:48
lucasagomesenable the site and restart apache ?13:49
lucasagomesjroll, something I'm missing?13:49
*** kkoski has quit IRC13:49
jrolllucasagomes: seems like it should mostly work, assuming ironic is at /opt/stack/ironic :)13:49
jrolland apache user/group may need to change13:49
lucasagomesjroll, oh ++13:50
jrollbut yeah, seems sane otherwise... I think yuriyz may also have experience with this if you get stuck13:50
lucasagomeswe should dociment it13:50
lucasagomesdocument*13:50
jrollyeah, totally13:50
lucasagomesI will try to do it and document as we go13:50
jrollI've been meaning to set it up forever and haven't gotten to it13:50
rloohi everyone, dtantsur, jroll, TheJulia, lucasagomes13:50
lucasagomesrloo, hello good morning13:50
NobodyCammornign rloo :)13:50
jrollmorning rloo :)13:50
lucasagomesjroll, cool I will try it here, if I get it working I will document it upstream13:51
jrollrloo: this seems relevant to your interests https://review.openstack.org/#/c/206999/13:51
jrollnice, thanks lucasagomes13:51
rloolucasagomes: quick question, wrt that new CLEANWAIT state. i am looking at https://review.openstack.org/#/c/204995/4/nova/virt/ironic/driver.py.13:51
lucasagomesrloo, shoot!13:51
rloolucasagomes: in _wait_for_provision_state(), don't we want to check for CLEANWAIT too?13:51
rloomorning NobodyCam!13:51
lucasagomesrloo, yeah now that it exists in the Ironic we should indeed13:52
rloolucasagomes: the quesition has nothing to do with that particular patch, just the code i saw while reviewing it :)13:52
lucasagomesrloo, tho i wanna get rid of this loop with the lazy instnace13:52
jrolldtantsur: so on https://review.openstack.org/#/c/206752/ the tl;dr is with that option enabled, nova will do `select * from instances where host='ironic-compute-host'`, which is insane when you can have thousands of instances on one compute host :)13:52
TheJuliagoodmorning rloo13:52
lucasagomesrloo, yeah we could submit a patch to include the CLEANWAIT there ++13:52
rloolucasagomes: but it'll break now won't it?13:52
jrolldtantsur: and I think it actually does it n/10 times, where n is number of ironic nodes13:53
rloolucasagomes: well, not break, just take longer13:53
lucasagomesrloo, yeah right now it will just take longer cause CLEANWAIT doesn't make ironic break the loop13:53
jrolldtantsur: https://github.com/openstack/nova/blob/master/nova/scheduler/host_manager.py#L388-41813:53
rloolucasagomes: whereas before, it was CLEANING so it would have exit'd the loop faster. when do you think you might get the lazy instance delete implemented? the spec hasn't been approved yet...13:54
*** albertoffb has quit IRC13:55
lucasagomesrloo, yeah :-( we could just submit a small patch for now adding CLEANWAIT there13:56
lucasagomesso we break the loop faster13:56
lucasagomesrloo, I already have the code for the lazy stuff almost ready... need the spec tho13:57
rloolucasagomes: ok. would you like me to do it?13:57
lucasagomesrloo, if you have it handy there13:57
rloolucasagomes: no, nothing handy :)13:58
lucasagomeslol13:58
lucasagomesrloo, I added to my todo, if I see nothing is submitted I will do today later on13:58
rloolucasagomes: ok sounds good.13:58
dtantsurjroll, oh I see14:01
dtantsurrloo, morning!14:01
jrolldtantsur: it OOM'd our nova-scheduler running by itself on a 4gb machine :)14:01
dtantsurwow14:01
jrolland ate enough cpu that rabbit handshakes couldn't even get packets out14:02
jrollquite amazing14:02
NobodyCamoh wow14:02
NobodyCamtime.sleep(0)14:03
lucasagomesyuriyz, around?14:04
yuriyzhi lucasagomes14:04
lucasagomesyuriyz, I'm trying to configure the ironic-api with apache wsgi, you've done it right?14:05
yuriyzyes14:05
lucasagomesyuriyz, so here's what I did... I copied etc/ironic/ironic to /etc/apache2/sites-enabled/ironic.conf14:05
lucasagomesI edit it changed the user and group from "stack" to "ironic"14:05
lucasagomesenabled the site and reloaded apache14:05
NobodyCamTheJulia: did cinerama put up a patch to address "sh: 1: debootstrap: not found"14:05
*** EmilienM has quit IRC14:05
lucasagomesthen I started ironic-api14:05
lucasagomesyuriyz, but when I check the ironic_access.log it's empty14:06
lucasagomesyuriyz, am I missing something?14:06
yuriyzdo you edit path to api?14:06
yuriyzdefault is /opt/stack/ironic/ironic/api/app.wsgi14:07
TheJuliaNobodyCam: I thought she was going to, but I don't see anything14:07
lucasagomesyuriyz, yeah that file exists (I'm testing with devstack)14:07
lucasagomesstack@virtual-machine:~/devstack$ ls -la /opt/stack/ironic/ironic/api/app.wsgi14:08
lucasagomes-rw-r--r-- 1 stack stack 858 Jul 21 13:59 /opt/stack/ironic/ironic/api/app.wsgi14:08
TheJuliaNobodyCam: /win 4314:09
TheJuliadoh14:09
yuriyzplease look at /var/log/apache2/ironic_error.log14:09
*** EmilienM has joined #openstack-ironic14:09
jrollNobodyCam: time.sleep(0) is an eventlet-ism to yield to other threads and not hog the cpu, we have some in ironic too14:10
NobodyCamjroll: ya, I saw the comment ... was just thinking that (1) may have prevented the hammering of your system :-p14:11
yuriyz"native" ironic-api process should be stopped before apache restarts14:11
lucasagomesyuriyz, oh right I see some errors there14:12
lucasagomesyuriyz, gotcha14:12
lucasagomeslemme try it a bit more thanks for the tip14:12
jrollNobodyCam: nope, it locked up on the first iteration of the loop :)14:13
lucasagomesyuriyz, worked! Gotta fix the wsgi mode upstream14:13
lucasagomesit's important oslo worngly14:13
* lucasagomes makes a patch14:13
openstackgerritNaohiro Tamura proposed openstack/ironic: Add raises docstring tag into object.Ports methods  https://review.openstack.org/20706414:15
NobodyCamlol: this is kinda Ironic: http://www.pme-legend.com/campaigns/bare-metal-jeans14:16
openstackgerritLucas Alvares Gomes proposed openstack/ironic: Fix apache wsgi import  https://review.openstack.org/20706814:21
lucasagomesyuriyz, ^14:21
jrollnice catch14:22
lucasagomesjroll, I will document it now14:23
*** absubram has joined #openstack-ironic14:25
rloolucasagomes: i +1'd but have some comments for https://review.openstack.org/#/c/204995/. not sure how nova folks vote14:25
*** mtanino has joined #openstack-ironic14:25
*** r-daneel has joined #openstack-ironic14:26
dtantsurNobodyCam, lol14:27
NobodyCam:-p14:27
lucasagomesrloo, thanks!14:28
lucasagomesNobodyCam, looks like a normal jeans14:28
NobodyCamyep.. just the name :-p14:28
*** kkoski has joined #openstack-ironic14:28
lucasagomesthey should add some metal to it14:29
*** uggla__ has joined #openstack-ironic14:29
NobodyCamor a pixie logo :-p14:29
lucasagomesheh ++14:29
lucasagomeson the butt14:29
NobodyCamLOL14:30
*** uggla__ has quit IRC14:30
*** uggla___ has joined #openstack-ironic14:30
*** sinval_ has quit IRC14:33
jrolllucasagomes: I also left a comment there, idk if worth a -1 but I did it anyway14:34
jroll(nova patch)14:34
NobodyCamI hit it late lastnight... should I retest.. I have not yet done that14:35
NobodyCamww14:35
lucasagomesjroll, thanks will fix! left a comment as well14:36
rloojroll: now I feel like I was being too nice. I had the same thought as you, but the other tests (wrt the destroy) use the FAKE_CLIENT node thingy so I figured lucasagomes was being consistent with that.14:36
lucasagomesI can test _unprovision() directly instead of going through destroy() wdyt?14:36
rloolucasagomes: yes, testing _unprovision() would be better.14:36
lucasagomesrloo, yeah I copied it over and then modified it14:36
lucasagomesc&p lazyness :-( sorry14:37
lucasagomeswill do14:37
jrollyeah +114:37
*** coolsvap|away is now known as coolsvap14:37
rloolucasagomes: the only problem with testing _unprovision() is that then I'd wonder about testing all of it :-(14:37
jroll(I now see why you did that, thuogh)14:37
lucasagomesrloo, yeah, well I add the rest of the tests if needed14:37
lucasagomesthe nova driver needs some love14:38
rloolucasagomes: I'm fine with whatever you do I think, given that it needs more love anyway :)14:38
lucasagomes(-:14:38
lucasagomesI will add the tests for _unprovision()14:38
rloolucasagomes: eg if you add _unprovision() tests, my guess is that some of the existing tests might need to be changed to directly test _unprovision()14:39
lucasagomeshmm14:40
lucasagomesI will take a look after documenting the wsgi thing14:40
*** pal has quit IRC14:45
*** pal has joined #openstack-ironic14:46
thiagopgood morning Ironicers14:49
*** athomas has quit IRC14:49
NobodyCamgood mornign thiagop14:50
*** pal has quit IRC14:50
*** athomas has joined #openstack-ironic14:55
thiagopHey NobodyCam14:55
*** absubram has quit IRC14:55
NobodyCam:)14:56
* NobodyCam joins a call :-)14:58
*** absubram has joined #openstack-ironic14:59
*** caiobo has quit IRC15:00
*** jistr has quit IRC15:00
*** yuikotak_ has joined #openstack-ironic15:01
*** e0ne has quit IRC15:02
*** mestery has joined #openstack-ironic15:02
*** jistr has joined #openstack-ironic15:02
*** yuikotakada has quit IRC15:03
*** e0ne has joined #openstack-ironic15:04
rloohey dtantsur, I think 'their' use of 'service' is in reference to this other file (in this patch: https://review.openstack.org/#/c/201670/)15:06
dtantsurrloo, ah I see. so subproject are just not considered, nice...15:07
rloodtantsur: but yeah, a project could provide more than one "service". they don't address the individual components.15:07
rloodtantsur: i find it ironic that in their reference/projects.yaml file, the project names have the first letter uppercased, even though they want them lowercased :)15:07
dtantsurlol15:08
rloodtantsur: i added a comment; will see if anyone bites15:08
*** [1]cdearborn has quit IRC15:09
*** cdearborn has joined #openstack-ironic15:09
*** cdearborn has quit IRC15:10
*** cdearborn has joined #openstack-ironic15:11
*** davideagnello has joined #openstack-ironic15:16
openstackgerritLucas Alvares Gomes proposed openstack/ironic: Document configuring ironic-api behind mod_wsgi  https://review.openstack.org/20709115:20
*** davideagnello has quit IRC15:20
*** vikas_ has quit IRC15:25
*** ijw has joined #openstack-ironic15:29
*** alexpilotti has quit IRC15:34
*** gabriel-bezerra has quit IRC15:39
*** vishwanathj has quit IRC15:41
*** Sukhdev_ has joined #openstack-ironic15:47
*** romcheg has quit IRC15:48
*** ijw has quit IRC15:50
*** trown is now known as trown|lunch15:50
*** ifarkas has quit IRC15:50
openstackgerritStephanie Miller proposed openstack/bifrost: Correct reference to deploy_image variable in install playbook  https://review.openstack.org/20674515:52
*** karimb has joined #openstack-ironic15:54
TheJuliacinerama: danke15:54
*** uggla___ has quit IRC15:57
*** uggla___ has joined #openstack-ironic15:58
*** uggla___ has quit IRC15:59
*** gabriel-bezerra has joined #openstack-ironic16:01
*** lucasagomes is now known as lucas-afk16:03
openstackgerritDmitry Tantsur proposed openstack/ironic-python-agent: [WIP] Add support for inspection using ironic-inspector  https://review.openstack.org/20558716:04
dtantsursee you tomorrow!16:04
*** dtantsur is now known as dtantsur|afk16:04
NobodyCamnight dtantsur|afk16:06
NobodyCamanyone have a free cycle to look at a vagrant file patch: https://review.openstack.org/#/c/191110 </ShameLessPlug>16:07
*** jistr has quit IRC16:08
*** romcheg has joined #openstack-ironic16:11
*** meghal has joined #openstack-ironic16:11
*** romcheg has quit IRC16:12
*** coolsvap is now known as coolsvap|away16:12
*** puranamr has joined #openstack-ironic16:13
*** romcheg has joined #openstack-ironic16:14
*** [1]cdearborn has joined #openstack-ironic16:15
*** david-lyle has quit IRC16:18
*** lsmola has quit IRC16:20
cineramafeels good when you go to look at a patch someone wants a review on and you already reviewed :)16:21
openstackgerritMerged openstack/bifrost: Remove un-necessary role  https://review.openstack.org/20666716:21
NobodyCam:)16:22
*** Marga_ has quit IRC16:26
*** Marga_ has joined #openstack-ironic16:28
*** cdearborn has quit IRC16:30
meghalhello all…I was going through the following raid spec- http://specs.openstack.org/openstack/ironic-specs/specs/liberty/ironic-generic-raid-interface.html which says that a raid interface is being added for operators to specify a raid config while enrolling hardware, which can be used for zapping or cleaning16:33
meghalso, I was wondering if there are any plans to allow end user to customize raid config ?16:33
meghalwhile booting an instance ?16:33
*** coolsvap|away is now known as coolsvap16:39
*** david-lyle has joined #openstack-ironic16:42
devanandameghal: generally no. changing the physical characteristics of the hardware is not logically part of the deploy process, but a precondition to it, so it is done while the node is in the MANAGEABLE state16:45
*** ukalifon has quit IRC16:45
*** alexpilotti has joined #openstack-ironic16:47
*** Marga_ has quit IRC16:47
sambettsdevananda: I still think that should be selectable by flavor :/16:47
sambettsbut thats likely something for the future16:48
meghaldevananda:  thanks for your reply. So, what if there is a ironic node with hw raid configured and has multiple disks, how will a user be able to specify if he wants raid0 or raid10 ?16:48
devanandasambetts: the point is for it to be selectable by flavor :)16:49
*** zz_natorious is now known as natorious16:49
devanandasambetts: iow, if I have a pool of servers and I know some users will want raid5 and some will want raid10, I create two flavors, and prepare some servers in each way, then the scheduler matches flavor <-> raid topology16:50
devanandain that way, the user isn't waiting for the raid to be built after they ask Nova for an instance16:50
sambettsdevananda: in my use case 1 node would be able to support both raids16:50
meghalsambetts:  devananda - so ironic node has raid capabilities and there will be a flavor which exposes those capabilities, so user will know that he is booting a raid node, but I still believe that user will want to configure raid setup16:50
devanandacause, well, building raids isn't necessarily fast ....16:50
meghalbecause if we preconfigure raid, aren't we restricting hw capability to allow customization of raid config16:51
jrollsambetts: devananda: I think just-in-time raid config is something we should do eventually, but baby steps and all16:51
devanandameghal: "user" is a cloud consumer in this case, not a traditional sysadmin16:51
sambettsjroll: Yes baby steps :D16:51
devanandameghal: yes16:51
devanandajroll: yeh ... I know that some hardware will support things like that, but in that case, it can be automated16:52
jrolldevananda: automated?16:52
meghaldevananda:  right…user is cloud admin who configures ironic node with specific raid, but why should we restrict node with hw raid to specific configuration, when we can add support to ipa to customize it based on end user input16:53
devanandathough I think the interface for specifying raid config right now is complex enough that we'll need automation around it anyway16:53
meghaldevananda:  is it because we want predictable reimaging time ?16:53
devanandameghal: that's part of it16:53
jrollmeghal: I think we'll get to that point someday (I certianly want to), but one thing at a time...16:53
devanandameghal: when the cloud user is the same as the cloud operator, then yea, some things are different. but in that case, the "user" can still do this16:54
meghaljroll:  sure…I do not have a question about timing, I was just wondering if that is the direction ironic is thinking16:54
devanandathey just need to perform the RAID config through the manageable state16:54
devanandameghal: primary reason is to support the case where the cloud user != cloud operator16:55
jrollmeghal: cool, yes, that's something I (we?) want to do16:55
meghaldevananda:  now I am confused…I see cloud operator as an admin managing ironic cluster…and cloud user as an end user using nova to boot ironic nodes16:56
devanandajroll: how long does it take your hardware to convert a 12 disk RAID10 into a RAID5?16:56
devanandameghal: exactly16:56
devanandameghal: inthat case, does the user who issues "nova boot" want to wait a very long time for RAID to be rebuilt?16:56
devanandameghal: also, how do they specify ** to Nova ** the RAID config they want?16:56
devanandathey pick a pre-existing flavor16:57
meghaldevananda:  sure in certain cases, he would want to…because he has set that expectation by specifying a particular raid config16:57
devanandawhich "he" ?16:57
meghaldevananda:  yes specifying raid config to nova is the tricky question16:57
meghaldevananda:  I meant cloud user16:57
*** coolsvap is now known as coolsvap|away16:58
devanandameghal: so, it's not a tricky question. it is done by selecting a flavor that the cloud operator has already created16:58
jrolldevananda: I'm not trying to pretend it's possible on all hardware, it's just something I want to be able to do (and maybe some nova users are ok with waiting)16:58
*** coolsvap|away is now known as coolsvap16:58
jrolldevananda: remember mdraid etc is a thing16:58
devanandaNova's API doesn't support anything beyond that16:58
sambettsI see there being 4/5 near indentical flavors with the only difference being the type of raid16:58
devanandajroll: .....16:58
meghaldevananda:  at Yahoo we have been playing around with this question as well, for certain disk customization which can happen after OS comes up, we can use chef16:58
jrolldevananda: yes?16:59
devanandajroll: software raid?16:59
*** kkoski has quit IRC16:59
jrolldevananda: yes?16:59
meghaldevananda:  but for certain customizations which ipa or any OS installer needs to do, either nova needs to support it, or we piggy back on cloud-init user data or so16:59
devananda<sigh>16:59
meghaldevananda:  we have not been able to decide though…this was just a thought16:59
devanandameghal: can you give some specific examples?17:00
meghalbut there should be some support from nova api17:00
*** davideagnello has joined #openstack-ironic17:00
jrolldevananda: people do use software raid, believe it or not17:00
meghaldevananda:  lets say user specifies user-data which is cloud-init and specify a raid config in yaml format17:00
meghaldevananda:  ironic driver receives the user data in instance info17:00
devanandajroll: sure. it exists. but i dont think ironic needs to solve for every situation17:01
meghaldevananda:  ironic conductor parses the user data and provides input to IPA which can take appropriate action17:01
devanandameghal: I mean, can you give an example of the requirement? not the flow you think will meet it17:01
*** pal has joined #openstack-ironic17:02
jrolldevananda: I mean, if I want a compute with the boot disk on software raid, I shouldn't be able to use ironic to do that? that's... sad at best17:02
devanandasambetts: in theory, yea, i could see there being a lot of "hardware-X-config-A", "hardware-X-config-B", and so on17:02
*** kkoski has joined #openstack-ironic17:02
meghaldevananda:  so we have lot of hardware with hw raid and cloud users while booting instances like to specify raid0 or raid10 and expect the hw to come up with that configuration17:02
meghaldevananda:  that is the use case17:02
devanandameghal: ok. could you create two pools of hardware, some preconfigured with raid0 and some preconfigured with raid10?17:03
*** e0ne has quit IRC17:03
devanandato note - the "available storage" of each of those pools will also be different17:04
Madasiseems like a workable intermediate solution, but has lots if inefficiencies long term at scale17:04
meghaldevananda:  then we will be restricting usage of that pool when cloud users needing raid support are not booting instances17:04
devanandaeven if they have the same # of HDD17:04
sambettsdevananda: I don't see a problem with that sort of flavor list, the problem with having pools of preconfigured hardware is that what happens if you run out of one type17:04
*** kkoski has quit IRC17:04
jrollyeah, I think JIT hw raid config should be an acceptable thing, if a deployer chooses to make their user wait hours to get a server17:04
Madasiyou'd end up with a crazy backend system that looks at usage, reconfigures raid, and moves nodes from one pool to another17:05
Madasiseems like a better solution in raid configuration on demand as an end goal17:05
devanandaMadasi: except that by not predefining the set of allowable configurations (and this applies to more than just RAID), we push the complexity out through the API and on to users17:05
devanandaimagine as a user the interface here17:06
jrollwait17:06
Madasiit's predifined to a set of allowed options17:06
jrollthere's a couple of things here17:06
jroll1) raid-x flavors with preconfigured raid17:06
*** Pradip has joined #openstack-ironic17:06
jroll2) raid-x flavors with JIT raid17:07
jroll3) --i-want-raid-x in nova api17:07
jroll3 is horrible17:07
Madasi^17:07
jrolllet's never do that17:07
MadasiI was thinking of #217:07
sambettsI'm after 217:07
jroll2 is great but slow17:07
devanandanova boot --image ... --flavor baremetal --hwspec "{'raid': { ... lots of details ...}, 'network': { ... more details about bonding ... }, 'firmware': { ... specific firmware versions ... }, and so on}"17:07
jroll1 is bad but fast17:07
meghaljroll:  why is it horrible ? because of longer time ?17:07
meghaland user interface ?17:07
Madasijroll: is it really that slow to configure striping across a bunch of completely empty disks?17:07
Madasibeen a long time since I setup hardware raid, so honest question here17:08
jrollI think we can combine 1 and 2 to have raid-x flavors that prefer preconfigured raid, and do it JIT if it isn't there17:08
devanandajroll: 1 is what I think gives the best user eperience. 2 is acceptable as well, but it's clearly a trade off. 3 is terrible IMO17:08
*** Marga_ has joined #openstack-ironic17:08
jrollMadasi: I honestly don't have enough experience to say, I'm trusting others here17:08
*** natorious is now known as zz_natorious17:08
jrolldevananda: yeah, I like 2 with "if something is preconfigured use that"17:08
meghaljroll:  by JIT do you mean sw raid ?17:09
jrolldevananda: and operators that want the best user experience will preconfigure things17:09
jrollmeghal: I mean raid configured Just In Time (at deploy time)17:09
devanandajroll: so remember the discussion we had on Friday in Paris?17:09
MadasiI thought wiping the disks was a significant portion of raid setup time, but maybe it is actually laying down the striping and other setup tasks17:09
jrolldevananda: that was 9 months ago, no17:10
devanandaMadasi: i believe it varies significantly by hardware17:10
jrolldevananda: you mean the whole zapping thing?17:10
Madasinoly user experience difference between #1 and #2 should be boot time, right?17:10
devanandajroll: for the sake of a better UX, I believe we agreed that all the potentially-slow, potentially-destructive, probably-change-the-hardware-properties steps should get lumped together17:10
meghaljroll:  so by (2) you mean raid config is specified in flavor extra spec and hw is configured at deploy time. Yes, that is def better than restricting a hw pool17:10
devanandaand put behind the management API17:10
devanandathe thing about changing RAID config -- it actually changes the node.properties17:11
*** mjturek1 has quit IRC17:11
devanandaso doing that in a deploy will mess with quota usages in Nova too17:11
devanandabecaues it changes the total amount of disk consumed17:11
jrolldevananda: here's my take on this: clearly (1) is the best option here. the question is what to do in the "nothing is preconfigured" case. our options are a) just fail. the user has to ask support what happened. support has to go to ops and ask them to configure a thing. hopefully the user gets it before someone else does. b) configure raid on the fly, user still has to wait but doesn't need to17:11
jrollcontact support.17:11
devanandajust one example -- perhaps not the best one, because who really sets a quota around disk usage?17:11
devananda(oh, wait, folks do bill on that)17:12
devanandajroll: "nothing is preconfigured" should be "cloud operator starts preconfiguring things"17:12
Madasidevananda: that is a valid point, different raid configs are different flavor definitions in nova. One more example of where nova's model of reality doesn't map properly for us17:13
openstackgerritJulia Kreger proposed openstack/bifrost: Cleanup use of extra_dib_elements  https://review.openstack.org/20666417:13
devanandato be clear -- I think it would be quite nice for some use cases to do JIT HW RAID configuration17:13
jrolldevananda: I mean... hopefully. if they're around. and notified. and not busy with something else. etc. etc.17:13
devanandabut I think it significantly complicates /other/ interactions between Ironic and OpenStack that are, well, not great17:13
jrolldevananda: which is going to end with software being written to watch pools of hw and different raid configs and preconfigure int he background and so on17:13
devanandaMadasi: exactly17:13
devanandajroll: yep. and I fully expect that to be written17:14
jrolldevananda: that's... meh. hopefully whoever writes it is a fan of contributing to open source17:14
*** alexpilotti has quit IRC17:14
Madasidevananda: question though. customer builds raid 10, so you are billing them for half the potential capacity of the disk space on the box. Do you have them locked out of the raid config, or can the change that to raid 5 or even raid 0 and get extra space for the price of an os reinstall by hand?17:15
sambettsFor my use case, I know this doesn't fit a lot of other peoples, but we have a data center full of identical hardware, all specs out far beyond what most users might want, I actually want fuzzy fitting of flavors e.g. scedule a flavor onto a node that provides more than the flavor's asking for but limit it using the OOB management17:15
devanandasambetts: oh, interesting17:16
Madasiseems to me like we advertise to nova total potential capacity and don't worry about how it's actually being used17:16
sambettsthat goes for disk, RAM, CPU etc etc etc, we can limit all those things in management and only give the user what they've asked for17:16
devanandaMadasi: fair point. and that's possible, too17:16
jrollright, billing for ram/disk usage doesn't make sense for ironic. bill on instances.17:16
devanandaright17:17
devanandajust poiting out how all this breaks Nova's models17:17
sambettsdon't most people bill based on flavor?17:17
meghalMadasi jroll - yes bill on instances seems right way to go…that's why we also want quota per flavor in nova17:17
devanandaanyway, i need to run. E_TOOMANYMEETINGS17:17
sambettsdevananda: have fun :-P17:17
devanandathanks :p17:17
meghaland quota per flavor could directly track instances17:18
meghalthanks devananda for your inputs17:18
sambettsyeah this conversation is really interesting17:18
*** karimb has quit IRC17:19
Madasisambetts: i would expect so, devananda's point earlier was that from nova's point of view JIT ram config changes a node from one type to another since it tracks nodes by ram/disk capacity17:19
Madasibilling wouldn't care since it is by flavor/instance17:20
Madasibut nova would17:20
meghalwe have this use case here - we order multiple type of hardware and expose it via flavors to cloud users, also hw is installed in specific location in datacenter, and users do want a particular hw in particular location, so we end up assigning quota per flavor and az and any quota assignment that goes beyond params like cores,ram,disk etc needs to be tracked by instances17:21
meghalalso, cloud users want to configure raid config while booting instances17:22
meghalbecause in ironic entire hw comes as a whole and not like vms where it can be split up17:22
sambettsmeghal: is the type of RAID config you want, more than just picking a type of RAID ?17:22
meghalsambetts:  it also relates to customizing disk config, mirroring root partition on RAID17:23
*** alexpilotti has joined #openstack-ironic17:23
meghalfor certain disk config which does not involve raid and can be done after OS comes up, we are asking users to do it via chef, and that we will provide with fixed size root partition17:24
sambettsmeghal: thats software RAID yes?17:24
meghalbut  for sw raid as well,root partition also needs to be mirrored as users want to take that advantage17:25
meghaland so it needs to be done by some OS installer - IPA17:25
sambettsmy use case is for out of band hardware RAID setup specficly17:25
meghalI believe there needs to be an interface which provides input params for setting up RAID, does disk config and is directly understood by IPA to take appropriate action17:26
meghalnow whether we do it via flavor or end-user api17:27
sambettscouldn't you bake the software RAID into the image?17:27
sambettsthen its just done based on image selection17:27
*** achanda has joined #openstack-ironic17:27
meghalthats a great suggestion, I will ask the OS guy in our team17:27
Madasiwouldn't you need an image per raid config per flavor then?17:28
Madasithat's a lot of images17:28
Madasiassuming drive differences between your flavors17:29
*** mjturek1 has joined #openstack-ironic17:29
meghalMadasi: yes…thats true…we would need different configs per different flavors and hence different images17:29
meghalargh17:29
meghalyes that will be lot of images17:29
sambettsI guess it depends on if the software your using to RAID can adapt to different amounts of disk17:29
sambettse.g. done by percentage or something :/ I don't know, I've not played with much sw RAID past like LVM stuff17:30
Madasisambetts: to achieve that i think you'd need to lay down raid at a certain size, then figure out a way to have something like cloud-init trigger a resize of the raid to include any extra space17:31
Madasinot sure if that is possible with raid in the same way it is with partitions, but if so it could work with multiple disk sizes17:31
meghalonce we push it to cloud-init, root partition is already created17:31
*** Marga_ has quit IRC17:32
sambettsmeghal: it might be created but if its a logical volume its easily changed17:32
*** Marga_ has joined #openstack-ironic17:32
sambettsalthough it'll be mounted... shoot...17:32
Madasijust use zfs :P17:32
sambettsor btfs ;)17:33
meghalsambetts:  yeah…so pushing it to image level will also not help17:33
meghalaction needs to happen at IPA level17:33
sambettsmy issue with software level RAID is that it feels like its user level task to complete not a deploy one17:35
sambettse.g. a user could change it after the fact inside his instance but with OOB RAID they can't17:35
sambettshow would nova/ironic deal with a user rearraging something inside the instance? questions like that come up17:36
meghalthats where cleaning comes in…right ?17:36
sambettsmeghal: I mean while the instance is running17:36
meghalsambetts:  while an instance is running why would nova/ironic have to deal with what user does inside the instance ?17:37
sambettsit shouldn't, and for the same reason I don't think it should be setting anything up inside the instance either17:38
meghalsambetts:  question is if user wants things to be configured in a certain way, he can only provide input to the cloud17:39
meghaland cloud needs to take action accordingly…user has no other option17:39
sambettsmeghal: he can create his own image and upload it?17:39
Madasithat's a lot trickier with ironic than it is with nova, due to hardware drivers and the like17:40
meghalsambetts:  as Madasi brought up, it will also have to be tied with the flavor17:40
sambettsif the user is making it themselves, then you don't need so many precreated images, the user knows the flavor he/she targeting it for17:40
*** pelix has quit IRC17:41
*** kkoski has joined #openstack-ironic17:42
meghalsambetts: could work….but there are other questions as well…whether we want users to upload images because of security concerns17:42
*** r-daneel has quit IRC17:44
openstackgerritMerged openstack/ironic: Fix apache wsgi import  https://review.openstack.org/20706817:45
*** Sukhdev_ has quit IRC17:47
sambettsmeghal: thats a good question, what if you provided an image builder that accepted the RAID information and could pre-configure it? and had some kind of checksum that made sure it came from your builder? tbh I don't see a problem with having many prebuilt images, depends how many differnt flavors you have I guess, but you could tag the image with the flavor ID to make it easily searchable17:47
sambettsremembering that the kernal and initrd would be the same for most of them so you wouldn't need duplicates of those uploaded17:49
lucas-afkrloo, replied to https://review.openstack.org/#/c/205033/ , lemme know if that's fine17:51
*** Marga_ has quit IRC17:51
*** Marga_ has joined #openstack-ironic17:52
*** puranamr has quit IRC17:52
rloolucas-afk: yeah, i think that's fine. i haven't thought the stuff through. just that i thought there was some code you added wrt cleaning/cleanwait to be backwards compatible with cleaning, so i figured there might be some timing thing wrt upgrading ironic while a node was being cleaned.17:54
*** puranamr has joined #openstack-ironic17:54
lucas-afkrloo, yeah, I know, it's pretty tricky the whole state of things right now17:55
lucas-afk:-(17:55
*** lucas-afk is now known as lucasagomes17:55
rloolucasagomes: I'm fine approving it then unless you want to update the docstrings.17:55
lucasagomesrloo, I will update the docstrings... but no worries it depends on the patch on nova first17:56
rloolucasagomes: oh right.17:56
lucasagomeswithout been merged on nova this won't merge (Depends-On the commit message)17:56
lucasagomesso we have time17:56
lucasagomesrloo, I'm adding the tests for the _unprovision right now17:56
rloothx lucasagomes17:56
*** e0ne has joined #openstack-ironic17:56
lucasagomesrloo, thanks you for the review17:56
*** [1]cdearborn has quit IRC17:56
*** trown|lunch is now known as trown17:56
rloolucasagomes: yw17:56
*** cdearborn has joined #openstack-ironic17:57
rloolucasagomes: sorry, i had another question in that patch.18:02
lucasagomesrloo, cool will take a look soonish18:02
meghalsambetts:  sorry…was afk…yes verifying checksum is a good idea…let me talk to the OS expert in my team and see how can this be possible and whether we can push this configuration to image level or whether it needs to be done at IPA level18:05
rloolucasagomes: no hurries. (just couldn't change my vote yet.)18:05
*** e0ne has quit IRC18:06
*** adam_g has joined #openstack-ironic18:07
*** adam_g has quit IRC18:07
*** adam_g has joined #openstack-ironic18:07
*** e0ne has joined #openstack-ironic18:09
*** sinval_ has joined #openstack-ironic18:12
*** [1]cdearborn has joined #openstack-ironic18:17
*** coolsvap is now known as coolsvap|brb18:18
meghalhave one more question on availability zones, right now availability zone in nova is tracked by nova-compute hosts rather than hypervisor18:19
meghalso ironic nodes exposed as hypervisors under one nova-compute cannot be exposed to users as avail. zones18:20
meghalhave we tried to talk to nova team about the same ?18:20
meghalor is anybody using a different solution ?18:20
*** zer0c00l has quit IRC18:26
*** pal has quit IRC18:26
lucasagomesrloo, jroll https://review.openstack.org/204995 added the missing unittests, I think it's good now18:27
lucasagomesand folks I will call t a day, it's late here18:27
lucasagomesI will catch up with the rest tomorrow! Have a great night everyone18:27
rloothx lucasagomes!18:28
lucasagomesrloo, see you have a nice afternoon. I will take a look at the instance_uuid patch tomorrow morning18:28
*** lucasagomes is now known as lucas-dinner18:28
sambettsI'm off too, man its been a long day :-P G,night all o/18:29
*** zer0c00l has joined #openstack-ironic18:31
*** openstackgerrit has quit IRC18:31
*** cdearborn has quit IRC18:31
*** openstackgerrit has joined #openstack-ironic18:32
meghalthanks sambetts for your inputes18:40
meghalinputs*18:40
NobodyCamnight sambetts18:42
NobodyCamnight lucas-dinner18:42
*** vishwanathj has joined #openstack-ironic18:42
*** vishwanathj has quit IRC18:46
openstackgerritTom Cocozzello proposed openstack/bifrost: Activate pep8 check that _ is imported  https://review.openstack.org/20717318:53
*** kkoski has quit IRC18:55
*** kkoski has joined #openstack-ironic18:55
*** Sukhdev_ has joined #openstack-ironic18:55
*** zer0c00l has quit IRC18:56
*** kkoski_ has joined #openstack-ironic18:57
*** pal has joined #openstack-ironic18:57
*** kkoski has quit IRC18:58
openstackgerritJulia Kreger proposed openstack/bifrost: Make simple-init element perform source-based install  https://review.openstack.org/20717719:04
openstackgerritJulia Kreger proposed openstack/bifrost: Change default OS and support dib_packages  https://review.openstack.org/20717819:04
TheJuliarcarrillocruz: You'll be interested in the above revision19:04
*** krtaylor has quit IRC19:04
*** sinval_ has quit IRC19:06
openstackgerritJulia Kreger proposed openstack/bifrost: Move set +e to ensure VM creation causes failure  https://review.openstack.org/20718219:10
*** coolsvap|brb is now known as coolsvap|away19:10
openstackgerritJulia Kreger proposed openstack/bifrost: WIP: Test script to drive image testing  https://review.openstack.org/20718419:12
*** zer0c00l has joined #openstack-ironic19:15
*** meghal has quit IRC19:16
*** kkoski_ has quit IRC19:16
*** kkoski has joined #openstack-ironic19:16
*** krtaylor has joined #openstack-ironic19:17
openstackgerritThiago Paiva Brito proposed openstack/ironic: OneView Driver for Ironic  https://review.openstack.org/19182219:26
*** davideagnello has quit IRC19:27
*** ionutbalutoiu has joined #openstack-ironic19:28
alexpilottijroll: me and ionutbalutoiu are playing around with Windows images on Ironic19:29
jrollalexpilotti: cool!19:30
alexpilottiwith GPT, after a reboot PXE boot chain complains that we have not MBR :-)19:30
alexpilottiso one option is to build images with MBR partitioning, we’re trying this now19:31
jrollheh19:31
jrollyou can do UEFI too19:31
alexpilottithe other is that by using UEFI, we cannot use whole disk images19:31
jrolloh.19:31
*** jjohnson2 has quit IRC19:31
TheJuliaI thought > windows8 required gpt19:31
alexpilottihere you go :-)19:31
alexpilottiI basically have two questions19:32
alexpilotti1) can we do UEFI with whole disk images19:32
alexpilotti2) can we get GPT to work :-)19:32
TheJuliawhat drier?19:33
TheJuliadriver19:33
jrollso19:33
* TheJulia knows what jroll is going to say :)19:33
alexpilotticurrently we used PXE, planning to go iPXE19:33
jrollthis should work with agent + whole disk images19:33
jrolland probably whole disk images in general19:33
jrollor maybe not, I think pxe driver chain loads pxe to disk or something ridiculous19:34
alexpilottijroll: yep, that’s how it works19:34
*** vishwanathj has joined #openstack-ironic19:35
TheJuliajroll: I agree, although the agent is going to need to learn to repair gpt tables after the image has been written out19:35
NobodyCamyou could deploy a non gpt whole-disk image then run gdisk to upgrade: One of the best features of gdisk (and sgdisk and cgdisk too) is its ability to convert MBR and BSD disklabels to GPT without data loss.19:36
alexpilottiwas wondering if we can set the target server to boot from local disk and having IPMI to ask to boot from PXE19:36
jrollTheJulia: yeah, and also how to do configdrive on gpt19:36
TheJuliajroll: yup19:36
TheJulia(this is one of those things floating around in the back of her brain at the moment)19:36
jrollalexpilotti: I have no clue why the pxe driver does a pxe chainload thing instead of setting boot from disk, but I assume there was a reason for it...19:37
NobodyCamso tentent instances can not boot with out a control plane19:37
alexpilottiNobodyCam TheJulia: nice idea! this is something requiring changes in the agent or there’s a way to instruct it to do so?19:37
TheJuliait would require changes in the agent19:38
alexpilottiand the node definition should have a property stating the partitioning model I guess19:38
TheJuliait would be easy for the agent to look back at the disk and identify if its mbr or gpt, and act accordingly19:39
TheJuliawell, relatively easy19:39
alexpilottiTheJulia: but this assumes that we have a mandatory partitioning model?19:40
jrollNobodyCam: that sounds like a bug, not a feature19:40
TheJuliaalexpilotti: your image should have it's basic partitioning in it19:40
TheJuliaalexpilotti: Think about it as we're putting a small image on a larger disk :)19:40
NobodyCam:/19:41
TheJuliajroll: Some people I've spoken to actually prefer it that way19:41
TheJuliasomething about having central control over kernels and ramdisks19:42
jrollTheJulia: yeah, they're insane :)19:42
jrollwell, that's a non-argument with whole disk images19:42
TheJuliayup19:42
jrollso I don't get it at all19:42
TheJuliawell, agree that its a non-argument, I didn't administer sanity tests at all19:42
alexpilottiTheJulia: sure, was just about the necessity of a GPT to MBR on the fly conversion, as at that point we can just convert it before storeing it in Glance19:43
alexpilottito recap, you guys say that we can do whole disk + UEFI?19:44
jrollI have no clue about UEFI19:44
TheJuliaalexpilotti: I say give it a shot, and we classify any issues you encounter trying to use a whole disk image as bugs19:45
jroll+119:46
*** pal has quit IRC19:46
*** achanda has quit IRC19:46
TheJuliaPersonally, I've not tried it and cannot say it will work, your bound to encounter an issue or two, but that is why we're here :)19:46
*** krtaylor has quit IRC19:46
NobodyCam++19:46
*** athomas has quit IRC19:47
alexpilottiTheJulia: thanks, we tried with the PXE and it failed, trying again to see what exact errors we got19:47
alexpilottiTheJulia jroll: unrelated, following up to a coversation a few weeks ago: we’re adding ironic configdrive support in Cloudbase-Init this week19:48
NobodyCamalexpilotti: I can say that the iLo driver do support UEFI19:48
*** HenryG has quit IRC19:49
*** pal has joined #openstack-ironic19:49
alexpilottion VMs configdrives are disks, in Ironic partitions, so we just have to look for those as well19:49
*** jjohnson2 has joined #openstack-ironic19:49
TheJuliaalexpilotti: awesome!19:49
jrollalexpilotti: woot19:49
*** e0ne has quit IRC19:51
*** HenryG has joined #openstack-ironic19:52
*** meghal has joined #openstack-ironic19:55
*** e0ne has joined #openstack-ironic19:55
*** vishwanathj has quit IRC19:57
*** krtaylor has joined #openstack-ironic19:59
*** meghal has quit IRC19:59
*** meghal has joined #openstack-ironic20:00
*** meghal has quit IRC20:01
*** meghal has joined #openstack-ironic20:01
alexpilottiso, looks like by setting the BIOS to boot from disk as first option and PXE as second we are good, still testing20:02
*** puranamr has quit IRC20:02
*** e0ne has quit IRC20:03
*** puranamr has joined #openstack-ironic20:03
*** kkoski has quit IRC20:06
*** kkoski has joined #openstack-ironic20:07
TheJuliaWell, ultimately you would still want to do whole disk images via the agent :)20:07
*** vishwanathj has joined #openstack-ironic20:10
*** e0ne has joined #openstack-ironic20:11
*** kkoski has quit IRC20:11
*** meghal has quit IRC20:16
*** openstackgerrit has quit IRC20:16
*** meghal has joined #openstack-ironic20:16
NobodyCamw00t: https://review.openstack.org/#/c/198771 approved20:17
*** openstackgerrit has joined #openstack-ironic20:17
*** jaypipes has joined #openstack-ironic20:18
jaypipesdtantsur|afk: so, does ironic-inspector publish a RESTful API? if it does, then sure, of course it should have a service type and appear in the Keystone service catalog. If it doesn't there's no need to have one.20:18
NobodyCamhey jaypipes welocme to Ironic-landa20:19
NobodyCamwelcome even20:19
jaypipesNobodyCam: holla.20:19
jrollohai20:20
*** vishwanathj has quit IRC20:20
openstackgerritStephanie Miller proposed openstack/bifrost: Clarify variable names & cleanup docs  https://review.openstack.org/20720620:23
*** achanda has joined #openstack-ironic20:25
*** meghal has quit IRC20:27
*** achanda has quit IRC20:34
*** achanda has joined #openstack-ironic20:35
*** jjohnson2 has quit IRC20:35
*** jjohnson2 has joined #openstack-ironic20:36
*** achanda has quit IRC20:41
*** davideagnello has joined #openstack-ironic20:41
openstackgerritOpenStack Proposal Bot proposed openstack/ironic: Updated from global requirements  https://review.openstack.org/20681520:42
*** puranamr has quit IRC20:48
*** puranamr has joined #openstack-ironic20:53
*** pal has quit IRC20:54
*** Sukhdev_ has quit IRC20:55
*** meghal has joined #openstack-ironic20:58
*** meghal has quit IRC20:58
*** trown is now known as trown|outttypeww21:03
*** sinval_ has joined #openstack-ironic21:03
*** absubram has quit IRC21:04
*** kkoski has joined #openstack-ironic21:11
*** ekarlso has quit IRC21:16
*** meghal has joined #openstack-ironic21:18
*** kkoski has quit IRC21:20
*** kkoski has joined #openstack-ironic21:20
*** jjohnson2 has quit IRC21:20
*** sinval_ has quit IRC21:23
*** e0ne has quit IRC21:24
*** kkoski has quit IRC21:25
*** achanda has joined #openstack-ironic21:34
*** kkoski has joined #openstack-ironic21:35
*** achanda has quit IRC21:39
*** ekarlso has joined #openstack-ironic21:44
*** thiagop has quit IRC21:58
*** Haomeng|2 has joined #openstack-ironic22:00
*** meghal has quit IRC22:00
*** meghal has joined #openstack-ironic22:01
*** avladu has joined #openstack-ironic22:01
*** meghal has quit IRC22:01
*** meghal has joined #openstack-ironic22:02
*** Haomeng has quit IRC22:02
*** meghal has quit IRC22:04
rloohey lucas-dinner, I ended up submitting a nova patch for CLEANWAIT: https://review.openstack.org/#/c/207236/22:07
*** romcheg has quit IRC22:09
*** ionutbalutoiu has quit IRC22:09
*** achanda has joined #openstack-ironic22:11
*** [1]cdearborn has quit IRC22:14
*** lucas-dinner has quit IRC22:15
*** Sukhdev_ has joined #openstack-ironic22:19
*** mjturek1 has quit IRC22:23
*** zz_natorious is now known as natorious22:29
*** natorious has quit IRC22:34
*** natorious has joined #openstack-ironic22:34
*** jaypipes has quit IRC22:43
*** sinval_ has joined #openstack-ironic22:46
*** Haomeng has joined #openstack-ironic22:46
*** Haomeng|2 has quit IRC22:49
*** sinval has quit IRC22:50
*** vishwanathj has joined #openstack-ironic22:53
*** penick has joined #openstack-ironic22:56
*** alexpilotti has quit IRC23:05
*** avladu has quit IRC23:06
*** sinval_ has quit IRC23:13
*** puranamr has quit IRC23:18
*** vishwanathj has quit IRC23:20
*** Vikas has joined #openstack-ironic23:22
VikasHi folks, I am trying to boot an instance using pxe.ramdisk and kernel images are being deployed successfully , but at kernel initialization time its getting stuck.In console logs I can see that tgtd daemon is failing.23:27
Vikasstart iSCSI target on /dev/vda^M waiting for tgtd socket...not found^M Jul 29 23:17:17 (none) daemon.info tgtd: semkey 0x610230d1^M Jul 29 23:17:18 (none) daemon.warn tgtd: tgtd daemon started, pid:217^M Jul 29 23:17:18 (none) daemon.warn tgtd: tgtd logger started, pid:219 debug:0^M waiting for tgtd socket...found^M Jul 29 23:17:19 (none) daemon.err tgtd: iser_ib_init(3351) Failed to initialize RDMA; load kernel modules?^23:28
VikasCan anybody give me some pointers please?23:28
*** zhenguo has joined #openstack-ironic23:31
*** meghal has joined #openstack-ironic23:34
*** jamielennox is now known as jamielennox|away23:39
*** penick has quit IRC23:39
*** Vikas_ has joined #openstack-ironic23:58

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