Wednesday, 2012-05-16

*** littleidea has quit IRC00:07
*** utlemming has quit IRC00:07
*** rbasak has quit IRC00:08
*** flaviamissi has joined #openstack-dev00:09
*** mnewby has quit IRC00:10
*** anotherjesse is now known as anotherjesse_zz00:11
*** andrewsben_zz is now known as andrewsben00:17
*** utlemming has joined #openstack-dev00:19
*** vladimir3p has quit IRC00:22
*** roge has quit IRC00:25
*** jgriffith has quit IRC00:27
*** jgriffith has joined #openstack-dev00:27
*** jakedahn is now known as jakedahn_zz00:30
*** maplebed has quit IRC00:30
*** edygarcia has joined #openstack-dev00:38
*** s0mik has quit IRC00:44
*** rods has quit IRC00:46
*** flaviamissi_ has joined #openstack-dev00:46
*** flaviamissi has quit IRC00:47
*** flaviamissi_ is now known as flaviamissi00:47
*** vipul has quit IRC00:49
*** issackelly has quit IRC00:50
*** mdomsch has quit IRC00:52
*** aa has quit IRC00:55
*** pixelbeat has quit IRC00:58
*** reed has quit IRC01:02
*** ayoung has joined #openstack-dev01:03
*** maoy has joined #openstack-dev01:14
*** thingee has quit IRC01:16
*** longhudou has quit IRC01:18
*** sdake has joined #openstack-dev01:18
*** jdurgin has quit IRC01:19
*** thingee has joined #openstack-dev01:19
*** ijw has quit IRC01:19
*** heyho has quit IRC01:19
*** thingee has quit IRC01:19
*** dweimer has quit IRC01:20
*** zaitcev has quit IRC01:30
*** andrewsben is now known as andrewsben_zz01:36
*** zaitcev has joined #openstack-dev01:37
*** dweimer has joined #openstack-dev01:40
*** anotherjesse_zz is now known as anotherjesse01:43
*** adalbas has quit IRC01:46
*** wiliam has quit IRC01:50
*** adjohn has quit IRC01:54
*** anotherjesse is now known as anotherjesse_zz01:58
*** lorin1 has joined #openstack-dev02:00
*** danwent has quit IRC02:00
lorin1Is the "[no]foo" boolean flag format still kosher with ini format? Or is it just "foo=false" these days?02:00
*** jeblair has quit IRC02:01
*** wiliam has joined #openstack-dev02:04
*** andrewsben_zz is now known as andrewsben02:05
*** reed has joined #openstack-dev02:09
*** epim has joined #openstack-dev02:14
*** andrewsben is now known as andrewsben_zz02:16
*** timello_ has quit IRC02:26
*** timello has joined #openstack-dev02:37
*** jeblair has joined #openstack-dev02:40
*** bhuvan_ has quit IRC02:48
*** s0mik has joined #openstack-dev02:49
*** gabrielhurley has quit IRC02:50
*** sandywalsh_ has quit IRC02:52
*** littleidea has joined #openstack-dev02:54
*** somik has joined #openstack-dev02:54
*** jgriffith has quit IRC02:54
*** s0mik has quit IRC02:57
*** somik is now known as s0mik02:57
*** timello has quit IRC03:01
*** jakedahn_zz is now known as jakedahn03:06
*** edygarcia has quit IRC03:14
*** jakedahn is now known as jakedahn_zz03:15
*** jakedahn_zz is now known as jakedahn03:16
*** johnpostlethwait has joined #openstack-dev03:16
*** edygarcia has joined #openstack-dev03:17
*** lorin1 has quit IRC03:21
*** koolhead17 has quit IRC03:25
*** ywu has quit IRC03:32
*** Ryan_Lane has quit IRC03:36
*** edygarcia has quit IRC03:37
*** jgriffith has joined #openstack-dev03:40
*** johnpostlethwait has quit IRC03:41
*** s0mik has quit IRC03:50
*** issackel_ has joined #openstack-dev03:55
*** issackel_ has quit IRC03:56
*** s0mik has joined #openstack-dev04:02
*** wiliam has quit IRC04:11
*** s0mik has quit IRC04:15
*** danwent has joined #openstack-dev04:15
*** anderstj has joined #openstack-dev04:20
*** anotherjesse_zz is now known as anotherjesse04:29
*** harlowja has quit IRC04:29
*** anotherjesse is now known as anotherjesse_zz04:30
*** anotherjesse_zz is now known as anotherjesse04:30
*** jgriffith has quit IRC04:31
*** sleepsonzzz is now known as sleepsonthefloor04:31
*** danwent has quit IRC04:47
vishylorin1: foo=false04:49
*** vipul has joined #openstack-dev05:05
*** anderstj has quit IRC05:05
*** sleepsonthefloor is now known as sleepsonzzz05:10
*** maoy has quit IRC05:10
*** s0mik has joined #openstack-dev05:13
*** reed has quit IRC05:33
*** utlemming has quit IRC05:35
*** Ryan_Lane has joined #openstack-dev05:38
*** Ryan_Lane has joined #openstack-dev05:38
*** zaitcev has quit IRC05:39
*** sleepsonzzz is now known as sleepsonthefloor05:43
zykes-vishy: I've done it05:44
zykes-but it still starts with qemu05:45
vishyzykes-: I don't believe you :)05:45
vishydoes nova-compute mention libvirt_type=kvm when it lists flags on startup?05:45
zykes-nope05:46
vishythen you haven't set the fag properly05:47
vishy:)05:47
vishy* flag05:47
zykes-I'm sorry I mean it does05:47
zykes-libvirt_type : kvm from < nova-compute -d05:48
zykes-why does ubuntu use nova-compute.conf and nova.conf ?05:49
davidhaAnyone still awake?05:49
vishyzykes-: sigh no se05:50
davidha:) Does swift return HTTP headers indicating how long an objct can be cached?05:50
vishyzykes-: but if you launch a new instance it still doesn't start with kvm?05:50
vishyzykes-: does the libvirt.xml still specify qemu?05:50
zykes-need to get to work before I can try again vishy :)05:51
vishyzykes-: my guess is that you missed something :)05:51
zykes-maybe :)05:51
*** anotherjesse is now known as anotherjesse_zz05:54
*** anderstj has joined #openstack-dev05:57
*** danwent has joined #openstack-dev06:01
*** hattwick has quit IRC06:01
*** dubsquared has quit IRC06:03
*** anderstj has quit IRC06:10
*** dachary has joined #openstack-dev06:11
*** mindpixel has joined #openstack-dev06:13
*** dachary has quit IRC06:16
*** s0mik has quit IRC06:23
*** rgoodwin has quit IRC06:24
*** jakedahn is now known as jakedahn_zz06:24
*** vincentricci has quit IRC06:25
*** jakedahn_zz is now known as jakedahn06:27
*** rgoodwin has joined #openstack-dev06:33
zykes-vishy: do you know why ubuntu has 2 nova compute files ?06:40
zykes-as in /etc/nova/nova-compute.conf and nova.conf06:40
*** mrunge has joined #openstack-dev06:44
zykes-so it was all the nova-compute.conf that made issues06:44
*** pmezard has joined #openstack-dev06:45
*** vipul has quit IRC06:46
*** garyk has quit IRC06:46
*** davidha has quit IRC06:49
*** vipul has joined #openstack-dev06:52
*** sleepsonthefloor is now known as sleepsonzzz07:01
*** journeeman has joined #openstack-dev07:07
*** reidrac has joined #openstack-dev07:07
*** dachary has joined #openstack-dev07:17
*** garyk has joined #openstack-dev07:21
zykes-jk0: here for some help on openstack-bosh-cpi07:26
*** Stackops-Jorge has joined #openstack-dev07:26
*** Stackops-Jorge has quit IRC07:31
*** davidha has joined #openstack-dev07:31
*** Stackops-Jorge has joined #openstack-dev07:33
*** vipul has quit IRC07:38
*** dtheodor has joined #openstack-dev07:57
*** Adri2000_ has joined #openstack-dev07:58
*** Adri2000_ has quit IRC07:58
*** Adri2000_ has joined #openstack-dev07:58
*** hattwick has joined #openstack-dev07:58
*** apevec has joined #openstack-dev07:58
*** derekh has joined #openstack-dev07:59
*** Adri2000 has quit IRC08:03
*** littleidea has quit IRC08:19
*** darraghb has joined #openstack-dev08:21
*** dingdeng has quit IRC08:22
*** dingdeng has joined #openstack-dev08:22
*** pmezard has quit IRC08:32
*** pmezard has joined #openstack-dev08:35
*** pixelbeat has joined #openstack-dev08:36
*** gael has joined #openstack-dev08:37
*** zigo has joined #openstack-dev08:45
*** zigo-_- has joined #openstack-dev08:50
*** zigo has quit IRC08:50
*** danpb has joined #openstack-dev09:02
*** mcclurmc_ has quit IRC09:16
ttxkoolhead17 almost scored the millionth bug in LP:09:30
ttxbug 99999909:30
uvirtbotLaunchpad bug 999999 in keystone "keystone does not support postgres database" [Undecided,New] https://launchpad.net/bugs/99999909:30
Davieyso close... but yet, no dice.09:31
*** davidha_who_took has joined #openstack-dev09:44
*** davidha has quit IRC09:44
*** littleidea has joined #openstack-dev09:55
*** lts has joined #openstack-dev10:10
*** mancdaz has joined #openstack-dev10:12
*** heyho has joined #openstack-dev10:22
*** pvo-away is now known as pvo10:25
*** littleidea has quit IRC10:25
*** ijw has joined #openstack-dev10:30
*** davidha has joined #openstack-dev10:37
*** davidha_who_took has quit IRC10:38
zykes-jk0: could you provide a sample .yml file for micro bosh ?10:43
*** eglynn has joined #openstack-dev10:58
*** eglynn__ has quit IRC11:00
*** epim_ has joined #openstack-dev11:02
*** epim has quit IRC11:06
*** epim_ is now known as epim11:06
*** flaviamissi has quit IRC11:14
*** rkukura has quit IRC11:17
*** wiliam has joined #openstack-dev11:29
*** markvoelker has joined #openstack-dev11:34
*** Adri2000_ is now known as Adri200011:35
*** Mkenneth has joined #openstack-dev11:37
*** dhellmann has quit IRC11:44
*** troytoman-away is now known as troytoman11:45
*** salgado has joined #openstack-dev11:46
*** salgado has joined #openstack-dev11:46
LarsErikPif i want to file a bug on the documentation.. where do i put that?11:54
*** mcclurmc_ has joined #openstack-dev11:55
LarsErikPnvm.. found it11:59
*** ayoung has quit IRC12:03
*** bsza has joined #openstack-dev12:07
*** adalbas has joined #openstack-dev12:12
*** dprince has joined #openstack-dev12:17
*** cdub has joined #openstack-dev12:25
*** rbasak has joined #openstack-dev12:25
*** rbasak has joined #openstack-dev12:25
*** roge has joined #openstack-dev12:25
*** mrunge has quit IRC12:25
*** maoy has joined #openstack-dev12:28
*** mikal has quit IRC12:35
*** cdub has quit IRC12:37
*** mikal has joined #openstack-dev12:37
*** tryggvil has joined #openstack-dev12:40
*** alaski has joined #openstack-dev12:41
*** openstackjenkins has quit IRC12:42
*** openstackjenkins has joined #openstack-dev12:43
*** tryggvil has quit IRC12:45
*** sandywalsh has joined #openstack-dev12:45
*** flaviamissi has joined #openstack-dev12:45
*** mancdaz has quit IRC12:52
*** mancdaz has joined #openstack-dev12:53
*** openstackjenkins has quit IRC12:55
*** openstackjenkins has joined #openstack-dev12:55
*** mestery has quit IRC12:56
*** stuntmachine has joined #openstack-dev12:56
*** mestery has joined #openstack-dev12:57
*** openstackjenkins has quit IRC12:59
zykes-notmyname: ping pong12:59
zykes-does swift support regional replication now ?13:00
*** openstackjenkins has joined #openstack-dev13:00
*** openstackjenkins has quit IRC13:01
*** openstackjenkins has joined #openstack-dev13:02
*** lorin1 has joined #openstack-dev13:02
*** lorin1 has left #openstack-dev13:03
*** dolphm_ has joined #openstack-dev13:03
*** openstackjenkins has quit IRC13:03
*** openstackjenkins has joined #openstack-dev13:03
notmynamezykes-: no change in status for that feature. (status == probably work to some degree, but untested and there are probably problems that need to be solved)13:03
*** openstackjenkins has joined #openstack-dev13:04
*** openstackjenkins has quit IRC13:10
*** openstackjenkins has joined #openstack-dev13:10
*** wiliam has quit IRC13:11
*** Mkenneth has quit IRC13:12
*** alaski has quit IRC13:12
*** alaski has joined #openstack-dev13:13
*** sandywalsh_ has joined #openstack-dev13:22
*** sandywalsh has quit IRC13:22
*** zaitcev has joined #openstack-dev13:24
*** wiliam has joined #openstack-dev13:24
*** ayoung has joined #openstack-dev13:27
*** mancdaz has quit IRC13:28
*** mancdaz has joined #openstack-dev13:29
dolphm_ayoung: pki question when you have some time :)13:31
ayoungdolphm_, sure13:31
dolphm_ayoung: so, i was thinking this morning about the backwards compatibility of adding pki -- is that something you've thought about?13:32
ayoungyes13:32
dolphm_ayoung: are your thoughts documented somewhere?13:32
ayoungdolphm_, yes,  just still editing them prior to public posting13:32
ayoungbut the short is13:32
openstackgerritVerification of a change to openstack/nova failed: Sync with latest version of openstack.common.cfg  https://review.openstack.org/748313:32
ayoungit should be OK13:33
ayoungmodulo the token ID being in the URL13:33
ayoungbut that is problematic for other reasons13:33
dolphm_ayoung: length?13:33
ayoungdolphm_, I'll show you13:33
*** adalbas has quit IRC13:34
ayoungdolphm_,   this is a Base64 encoded signed document http://fpaste.org/T7qg/13:34
ayoungso while that will fit into -X-Auth_header13:34
ayoungdoing http://keystonehost/v2.0/tokens/<that thing}  is prohibitive13:34
dolphm_ayoung: yeah, that's starting to get risky13:35
ayoungdolphm_, the thing is,  there is already an understanding that putting the token into the  URL is bad security13:36
dolphm_ayoung: are you familiar with the X-Subject-Token approach from ~e3?13:36
ayoungdolphm_, no13:36
dolphm_ayoung: it was a solution to the token-in-url issue that didn't make it into the keystone rewrite13:36
ayoungdolphm_, link?13:36
*** Mkenneth has joined #openstack-dev13:37
*** timello has joined #openstack-dev13:37
dolphm_ayoung: i'll try and find one13:37
dolphm_https://blueprints.launchpad.net/keystone/+spec/stop-ids-in-uris13:37
ayoungdolphm_, so...assuming that there is an alternative to the token-in-Url scheme (which I assume there will be) then the PKI poken scheme is just a really long token13:37
ayoungdolphm_, ah,  yes, I've seen that13:38
dolphm_ayoung: the idea is that auth still occurs via X-Auth-Token, and instead of passing a token ID in the URL, you'd pass in the "subject" of your request as an X-Subject-Token header13:38
dolphm_ayoung: i was never really happy with the resulting resources (they're not very restful)13:38
*** markmcclain has joined #openstack-dev13:39
dolphm_ayoung: i liked the idea of splitting a "token" into two values: an ID (which is insecure and safe to use in the URL) and a value, which is what needs to be protected, and passed exclusively in headers13:39
ayoungdolphm_, we can still do that.13:40
ayoungthe Base64 text would be the value.13:40
dolphm_so, for a service to validate a token, they'd do the regular GET /tokens/{token_id} (token_id being the insecure identifier) along with an X-Subject-Token or X-Token-Value header or something with the actual token value to be validated13:41
ayoungSo what ever is done in base Keystone for tokens will be done for PKI tokens.  Thus,  I feel pretty confident about backwards compat13:41
dolphm_plus the service's own X-Auth-Token13:41
dolphm_ayoung: could a pki token be handled blindly by the API as unencrypted?13:41
ayoungdolphm_, yep13:41
*** openstackjenkins has quit IRC13:41
dolphm_ayoung: awesome, that's what i was hoping for13:41
ayoungits is just a longer token13:42
*** openstackjenkins has joined #openstack-dev13:42
*** dhellmann has joined #openstack-dev13:42
* dolphm_ keeps getting more and more excited for pki!13:42
ayoungI'll have proof of concept code posted soonish13:42
ayoungI can show what needs to be done from the command line using the NSS utils13:43
ayoungI'm just trying to make is legible13:43
*** rkukura has joined #openstack-dev13:44
*** maoy has quit IRC13:45
*** openstackjenkins has quit IRC13:47
*** openstackjenkins has joined #openstack-dev13:48
*** apevec has quit IRC13:49
*** openstackjenkins has quit IRC13:49
*** lorin1 has joined #openstack-dev13:50
*** openstackjenkins has joined #openstack-dev13:50
*** lorin1 has left #openstack-dev13:50
*** joesavak has joined #openstack-dev13:51
*** PotHix has joined #openstack-dev13:53
*** edygarcia has joined #openstack-dev13:55
*** adalbas has joined #openstack-dev13:58
*** crobinso has joined #openstack-dev14:04
*** salgado has quit IRC14:04
ayoungdolphm_, I'm splitting the article into two parts for clarity.  Here;s the first part. http://adam.younglogic.com/2012/05/signing-certutil/14:06
*** salgado has joined #openstack-dev14:07
*** salgado has joined #openstack-dev14:07
dolphm_ayoung: thanks, i'll read it this morning14:07
zykes-jk0: ping14:09
*** danwent has quit IRC14:12
*** journeeman has quit IRC14:12
*** b1rkh0ff has joined #openstack-dev14:13
*** dtroyer is now known as dtroyer_zzz14:13
*** b1rkh0ff has quit IRC14:14
*** b1rkh0ff has joined #openstack-dev14:15
*** b1rkh0ff has quit IRC14:15
*** b1rkh0ff has joined #openstack-dev14:15
*** sleepsonzzz is now known as sleepsonthefloor14:17
*** jsavak has joined #openstack-dev14:20
*** andrewsben_zz is now known as andrewsben14:21
*** joesavak has quit IRC14:23
*** GheRivero has joined #openstack-dev14:24
*** openstackjenkins has quit IRC14:26
davidhanotmyname, hi14:26
notmynamedavidha: good morning14:26
*** openstackjenkins has joined #openstack-dev14:26
*** dtroyer_zzz is now known as dtroyer14:27
davidhanotmyname, gm, is there any support to controlling the HTTP headers indicating how long an object may be cached?14:27
davidhanotmyname:  I mean when a client does get-object   - will the http headers indicating how long this object can be cached be set?14:29
notmynamedavidha: I think the answer is "yes", but the question doesn't really make sense to me. this is for caching in an external system14:29
notmyname?14:29
davidhayes - for external cache14:29
davidha(one object may be cacheable while a second non cacheable)14:30
notmynamedavidha:ok, that makes sense. I was a little worried you were thinking about some sort of cache inside of swift (which doesn't exist)14:30
davidhanotmyname: S3 seem to have this feature - hence my Q :)14:30
notmynamedavidha: for cloudfront?14:30
notmynamedavidha: you can add any piece of arbitrary metadata to any object. either use the "x-object-meta-key: value" form or add your own header to the allowed_headers config variable in the object server config and then set that14:32
davidhanotmyname: Well I do not know if it part of cloudFront or not.14:35
notmynamedavidha: you have a caching layer in front of swift and want to store the TTL with the object, right?14:35
davidhaBut you answer is that swift is extendiable to incldue any header per object14:35
davidhanotmyname: yes - as an example14:36
davidhayou=your14:36
notmynamedavidha: ya, so add whatever you want the header to be named to the object server config and then start setting it on your objects14:37
notmyname(or let your customers start setting it)14:37
davidhanotmyname: I get it.14:37
*** tserong has quit IRC14:39
ayoungdolphm_, posted the full proof of concept now, too: http://adam.younglogic.com/2012/05/signing-certutil/14:39
*** danwent has joined #openstack-dev14:39
davidhacreiht: gm.14:39
*** sdake has quit IRC14:39
creihtmorning14:40
*** sdake has joined #openstack-dev14:40
davidhaThanks for your comments yesterday. I do not think it all boils down to concurency - concurency can be bad  - depending on what limits the request processor.14:41
creihtwell I was more talking about the limitations of python in general in terms of concurrency14:42
*** sleepsonthefloor is now known as sleepsonzzz14:43
*** maoy has joined #openstack-dev14:44
*** renier has quit IRC14:45
*** rnirmal has joined #openstack-dev14:48
*** openstackjenkins has quit IRC14:48
davidhaok, at the long run, I would like to see the wsgi web front end as an option for getting a server running using a minimalistic web front end while actual deployments can choose their best server (i.e. not necesserily fastest server, but best overall).14:48
*** openstackjenkins has joined #openstack-dev14:48
davidhacreiht: (the eventlet wsgi, being one option they can choose from)14:49
*** blamar has joined #openstack-dev14:49
*** anderstj has joined #openstack-dev14:52
*** anderstj has quit IRC14:55
*** matwood_ has joined #openstack-dev14:56
*** mindpixel has quit IRC14:59
*** matwood has quit IRC14:59
*** openstackjenkins has quit IRC15:00
*** matwood_ has quit IRC15:00
*** openstackjenkins has joined #openstack-dev15:00
creihtdavidha: as long as that can be done simply/generically I would be fine with that15:00
davidhacreiht: great - I think it can be quiet simple for Swift  - no idea about other servers15:02
davidhaI will cont working to get it working.15:02
notmynamedavidha: to echo what creiht said, I like your idea in general. unfortunately, it's hard to say if it's better or not until you actually have it working. but it's certainly stuff I'd consider including in swift15:03
davidhaquiet=quite15:03
*** maoy has quit IRC15:05
*** maoy has joined #openstack-dev15:05
davidhanotmyname - sounds good. If it will be better depends on what you measure with. Its likely that it would be better for some in the community while others be better off with the existing solution. It will make swift more open for sure.  Lets play this and see where it goes.15:09
*** troytoman is now known as troytoman-away15:12
*** garyk has quit IRC15:16
*** garyk has joined #openstack-dev15:16
*** blamar has quit IRC15:17
*** utlemming has joined #openstack-dev15:18
*** Ryan_Lane has quit IRC15:18
*** vladimir3p has joined #openstack-dev15:19
*** openstackjenkins has quit IRC15:22
*** openstackjenkins has joined #openstack-dev15:23
*** matwood has joined #openstack-dev15:24
*** matwood has quit IRC15:24
*** dtheodor has quit IRC15:25
s1rpvishy: dprince: i pushed up a new version of https://review.openstack.org/#/c/7458/ ; included a docstring explaining why per-table utf8 is needed for now15:26
*** openstackjenkins has quit IRC15:27
*** kbringard has joined #openstack-dev15:27
*** jgriffith has joined #openstack-dev15:27
*** openstackjenkins has joined #openstack-dev15:27
*** matwood has joined #openstack-dev15:28
*** cdub has joined #openstack-dev15:29
*** mancdaz has quit IRC15:36
*** mancdaz has joined #openstack-dev15:38
*** reidrac has quit IRC15:40
*** lloydde has joined #openstack-dev15:41
*** devananda has quit IRC15:42
*** devananda has joined #openstack-dev15:43
*** vladimir3p has quit IRC15:44
*** jgriffith has quit IRC15:46
*** jgriffith has joined #openstack-dev15:47
*** rnirmal_ has joined #openstack-dev15:47
*** rnirmal has quit IRC15:48
*** rnirmal_ is now known as rnirmal15:48
*** rnirmal has quit IRC15:50
*** rnirmal has joined #openstack-dev15:51
*** matwood has quit IRC15:51
*** matwood has joined #openstack-dev15:51
*** simo has joined #openstack-dev15:56
*** clayg has quit IRC15:56
*** clayg_ is now known as clayg15:56
openstackgerritVerification of a change to openstack/nova failed: Add version to compute rpc API.  https://review.openstack.org/739115:57
*** clayg_ has joined #openstack-dev15:57
ayoungsimo, no I still don't think revocations are necessary15:58
ayoungjust that if we have them,  they could be pushed out from Keystone on a queue15:58
andrewbogott_dhellmann:  I'm adding some commands to openstackclient, and one of them is producing "ERROR    cliff.app PrettyTable instance has no attribute 'align' "15:59
ayoungTTL in the queue based on the expiriy of the tokens they are revoking15:59
andrewbogott_dhellmann:  My questions are 1) Any guess what's causing that?  and 2) Would it be possible for things like that to be exceptions rather than log messages so that we get a stack trace?15:59
simoayoung: tehy are not absolutely necessary, but they make administration easier, as you can revoke a token when you change roles for a user15:59
dhellmannandrewbogott_, the version of PrettyTable used by the other client apps is older and has a slightly different API than what cliff wants15:59
dhellmannuse the --debug option to get a stack trace16:00
dhellmannopenstackclient --debug your command here16:00
andrewbogott_Oh, nice!16:00
ayoungsimo, right now,  the CLI gets tokens before evey call, it does not even cache them.  To say that we need to expire tokens would be a major increase in the lifespan of a token16:00
simoayoung: will you allow any service to ask a token-cert ? Or do you want to require proof of auth before giving out a token ?16:00
andrewbogott_dhellmann:  OK, so I need to update PrettyTable?  Or will that break all the other clients?16:00
dhellmannwe should probably do something to trap openstack exceptions but let the others through by default16:00
ayoungproof-of-auth16:00
simoayoung: proof-of-auth means services cannot ask for a token if they are close to expiration time16:01
dhellmannI updated via "sudo pip install -U PrettyTable" and both "nova list" and "openstack list server" work on the same system, but that was surprising (I expected the nova command to break)16:01
simoayoung: how do you handle potential failures due to expired tokens ?16:01
ayoungsimo, lets call them signed-tokens.  As they will not be certificates in any X509 meaning of the term when we get to the final impl16:01
dhellmannyou might want to install openstackclient into a virtualenv?16:01
simoor do you need at all ?16:01
ayoungsimo, resubmit16:01
simoayoung: authz-token then16:01
simoayoung: resubmit means the job is killed and the admin needs to resubmit it ?16:02
ayoungsimo, no, signed tokens, to distinguish them from the current impl,  which I would call cookies16:02
ayoungsimo, yes, as all of this is authenticated upon jub submission16:02
simosigned-authz-token (just teasing)16:02
simoayoung: ok but a job may take long time and then try to do an action16:03
simoif the job always take > expiration time then it will always fail on the final action16:03
simomaking the job impossible to complete16:03
simoayoung: is there any case like that ?16:03
simoI am thinking something like provisiona  machine then do an action and provisioning turns out to take 1 full hour16:04
andrewbogott_dhellmann:  Worked!  thanks.16:04
dhellmannmy guess is nova does not try to align columns16:05
dtroyerdhellmann, andrewbogott_:  the other clients all handle pretty table 0.6 correctly now.  devstack is still pinned to 0.5, I think that can be removed now16:05
dhellmannah, cool16:05
ayoungsimo, when I submit a job, say through nova,  the token tells nova that I am authed to submit it.  Then nova does a bunch of stuff on my behalf,  and probably using the data from the token.  But Nova has its own long lived auth via an admin token.  Now,  admin tokens I could see an argument for revocation.16:05
ayoungBut your argument could be extended to HPC type jobs that take months.  THere is always the possibility of a process that will outlast its auth token.16:07
simoayoung: wait you mean user auth-tokens are not carried on to authorize all steps ?16:07
simoayoung: yes there is always the possibility in kerberos we have ways to solve the problem, I am just saying you may need those ways too16:07
simoayoung: for example allowing the release of a new token, bound to a service. by presenting evidence of a non-expired token16:08
ayoungeglynn, when nova talks to glance on behalf of a user,  which token is used to authorize the action?  THe users token, or the admin token?16:08
*** troytoman-away is now known as troytoman16:09
eglynnayoung: I'd expect the user's token is propogated to glance by nova16:09
eglynnayoung: (otherwise every user effectively becomes an admin, right?)16:10
ayoungeglynn, depends.  Admin API can say "do this on behalf of user X"16:11
ayoungBut I don't know glance well enough to say whether that would make sense.16:11
ayoungsimo, OK,  so currently tokens are just cookies.  Which means that their lifespan is effectively controlled by Keystone.  To time out a cookie-token,  the server just responds unauthorized16:12
eglynnayoung: I don't know if the simple x-auth-token header style of creds propogation supports OBO-style operation16:12
*** mancdaz_ has joined #openstack-dev16:13
eglynnayoung: or even, if it could be done within the current scheme, whether it would really bring anything to the table16:13
ayoungeglynn, so you would expect nova to pass on the token it was presented.  Thus,  those tokens have to live long enough to perform the whole operation.16:13
eglynnayoung: yep (default token expiry is 24hrs IIRC)16:14
*** Gordonz has joined #openstack-dev16:14
*** Lumiere has quit IRC16:15
*** smoser has joined #openstack-dev16:15
eglynnayoung: 24hrs unless of course the token is revoked in the meantime (derekh recently proposed a revocation mechanism for cases where a passwd was compromised)16:15
*** Gordonz has quit IRC16:15
ayoungsimo, edygarcia so now roles are checked on line, which means that if I revoke a role at the 12 hour mark,  future operations can use that same token,  and will just fail if the user  no longer has the  role required16:15
*** edygarcia has quit IRC16:16
*** Gordonz has joined #openstack-dev16:16
ayoungeglynn, ^^ was for you, of course16:16
*** mancdaz has quit IRC16:16
*** mancdaz_ is now known as mancdaz16:16
*** anotherjesse_zz is now known as anotherjesse16:16
*** Lumiere has joined #openstack-dev16:17
smoserok. so i'm clearly reading something wrong. but doesn't _mounted_processing in nova/virt/xenapi/vm_utils.py invoke inject_data_into_fs from nova.virt.disk incorrectly ?16:17
simoeglynn: how is revocation performed ?16:17
smoserit looks to me like its passing a varible named 'metadata' into a variable named 'admin_passwd' while passing in 'None' for 'metadata'16:17
eglynnayoung: one sec ...16:18
jgriffithanotherjesse: ping16:18
ayoungderekh, is your "Revocation" proposal written up anywhere>16:18
*** sleepsonzzz is now known as sleepsonthefloor16:18
ayoungsleepsonthefloor, https://bugzilla.redhat.com/show_bug.cgi?id=822182 and https://bugzilla.redhat.com/show_bug.cgi?id=82218716:19
uvirtbotbugzilla.redhat.com bug 822182 in Package Review "Review Request: python-websockify - Python proxy for the websockets protocol" [Medium,New]16:19
anotherjessejgriffith pong - sending a direct message16:19
eglynnayoung see https://review.openstack.org/7276 & https://review.openstack.org/734416:20
*** Mkenneth has quit IRC16:20
*** Mkenneth1 has joined #openstack-dev16:20
eglynnayoung: ^^^ wrt token revocation16:20
sleepsonthefloorayoung: looking16:21
ayoungeglynn, OK.  Thanks.  simo I concede the point,  and will write up the revocation scheme.  I'll include both the HTTP and AMQP based options16:21
*** salgado has quit IRC16:22
*** maplebed has joined #openstack-dev16:24
*** edygarcia has joined #openstack-dev16:24
*** salgado has joined #openstack-dev16:25
*** salgado has joined #openstack-dev16:25
*** reed has joined #openstack-dev16:27
simoayoung: cool16:27
derekhayoung: https://review.openstack.org/#/c/7276/16:27
*** s0mik has joined #openstack-dev16:28
ayoungderekh, thanks16:28
derekhayoung: and there is another for when a user is disabled https://review.openstack.org/#/c/7344/16:28
ayoungderekh, thanks...I see that one is already merged16:32
derekhayoung: yup one to invalidate tokens when a users password changes merged the other is still waiting16:33
ayoungderekh, what about if a user is removed from a tenancy?  I guess it is OK to leave the token around, and just return "No roles" when they online check is made?16:34
derekhayoung: good question, I havn't looked into that case16:35
*** littleidea has joined #openstack-dev16:36
*** gael has quit IRC16:37
ayoungderekh, I'm trying to address the needs for revocation WRT to the PKI  approach to token validation that I wrote up here  http://adam.younglogic.com/2012/05/signed-authz-authn/16:37
*** vipul has joined #openstack-dev16:38
*** danwent has quit IRC16:38
*** issackel_ has joined #openstack-dev16:39
*** zigo-_- has quit IRC16:40
*** zigo has joined #openstack-dev16:40
*** garyk has quit IRC16:41
*** andrewsben is now known as andrewsben_zz16:41
*** sdake has quit IRC16:42
derekhayoung: I'll take a look through it now16:42
ayoungderekh, thanks16:42
*** AlanClark has joined #openstack-dev16:44
bhuvancan someone review (and approve) https://review.openstack.org/7149 and https://review.openstack.org/7175?16:47
bcwaldonVek: ping16:47
bhuvanfwiw, 7149 is for python-keystoneclient and 7175 is for keystone16:48
*** danwent has joined #openstack-dev16:49
*** rgoodwin is now known as rgoodwin_away16:49
openstackgerritVerification of a change to openstack/keystone failed: Changed arguments in keystone CLI for consistency.  https://review.openstack.org/725316:51
*** adjohn has joined #openstack-dev16:52
*** mnewby has joined #openstack-dev16:53
*** vipul has quit IRC17:01
*** andresambrois has joined #openstack-dev17:02
*** zigo has quit IRC17:03
*** zigo has joined #openstack-dev17:03
*** mcclurmc_ has quit IRC17:08
derekhayoung: I had a look through your post at first glance to me the idea makes sense, I gotta run but I'll try out your examples later17:09
ayoungderekh, thanks for the check...I would say sanity check,  but I would not want to make unsubstantiated claims about myself17:10
derekhayoung: :-)17:10
*** derekh has quit IRC17:11
*** maoy has quit IRC17:15
*** danpb has quit IRC17:15
*** _adjohn has joined #openstack-dev17:16
*** Blah1 has joined #openstack-dev17:17
*** rgoodwin_away is now known as rgoodwin17:19
*** adjohn has quit IRC17:19
*** _adjohn is now known as adjohn17:19
*** Blah1 has quit IRC17:20
*** harlowja has joined #openstack-dev17:20
*** Stackops-Jorge has quit IRC17:25
*** vincentricci has joined #openstack-dev17:27
*** Blah1 has joined #openstack-dev17:28
*** Ryan_Lane has joined #openstack-dev17:28
*** Ryan_Lane has joined #openstack-dev17:28
*** GheRivero has quit IRC17:32
comstudrussellb: left an idea on your rpc versioning review.. ping me if you want to talk here or brainstorm some more.17:34
*** davidha has quit IRC17:36
*** anderstj has joined #openstack-dev17:38
mtaylordanwent, mnewby: https://review.openstack.org/#/c/7494/ - should fix tarball jobs17:41
mtaylorbcwaldon, jk0: https://review.openstack.org/#/c/7490/ should fix tarball jobs17:41
zykes-jk0: ping17:41
*** matwood has quit IRC17:42
danwentmtaylor: what testing (if any) is needed on this by reviews?17:43
*** anderstj_ has joined #openstack-dev17:43
mtaylordanwent: shouldn't need to be any ... it should pass the gate  - but I did run it locally to make sure17:43
mtaylordanwent: it shouldn't change normal behavior17:43
*** anderstj has quit IRC17:43
danwentmtaylor: ok, i figured, but just confirming17:43
russellbcomstud: cool, looking over it now.  I actually didn't use RpcDispatcher as a mix-in on the simpler conversions.  When I got to scheduler and compute, I did, because it was easier ... I like not using it as a mix-in better, though.17:46
comstudahh..i only really reviewed the compute versioning review17:47
comstudand so it there17:47
comstudso far17:47
comstudso it there/saw it there17:47
* russellb nods17:47
russellbyour patch may make it easier to not use it as a mix-in17:48
russellbwhich would rock17:48
*** _0x44 has quit IRC17:49
comstudyeah, it makes your versioning changes easier, actually17:49
comstudbecause it'll default all managers to 1.017:49
comstudsince I modified the base class17:49
comstudand you won't have to mix it in manually17:49
comstudthough I didn't go back and double check your changes to the managers to make sure that statement is truly accurate17:49
comstudhehe17:49
*** _0x44 has joined #openstack-dev17:50
*** jdurgin has joined #openstack-dev17:50
comstudbut essentially.. I'd like a more generic way to be able to create a dispatcher17:50
russellbso if a manager wanted to have more than one api version served up, would it just override create_rpc_dispatcher() ?17:50
comstudand i don't necessarily like having to set the .managers attribute manually...17:50
russellb(in your patch)17:51
comstudniceer to be able to be to pass them to __init__17:51
comstudcorrect17:51
russellbyeah, that is nicer indeed17:51
comstudyou could switch part of it back to using API_VERSION..17:51
comstudi'm not really opposed to that17:51
*** mrunge has joined #openstack-dev17:51
*** andrewsben_zz is now known as andrewsben17:52
comstudI had it as API_VERSION = '1.0' in the base manager class at first17:52
russellbinstead of the tuple?17:52
comstudyea17:52
russellbk17:52
comstudi don't necessarily like the tuple... but.. i don't necessarily like the API_VERSION getattr magic, either.  haha17:52
comstudbut it's less important to me17:52
russellbi kind of like having it there ... in your face right by the code17:52
comstudthan being able to pass a list of managers or callbacks to RpcDispatcher17:53
russellbimportant thing is not forgetting to update it when it should be updated17:53
*** littleidea has quit IRC17:53
comstudnod17:53
russellbcool, thanks much for the feedback17:53
comstudsure.. this also simplifies the rpc code and makes it always use the dispatcher now17:53
russellbi shold be able to incorporate all this stuff this afternoon17:53
russellbyeah, i like that17:53
*** johnpostlethwait has joined #openstack-dev17:54
comstudsorry it took me a while to get to reviewing17:54
comstuddef would love to see this get in asap17:54
russellbit didn't take that long17:54
*** Ryan_Lane has quit IRC17:54
comstudwell, i thought you'd put this up last week or something17:54
comstud:)17:54
russellbyeah, these patches love to go into conflict17:54
russellbnah, Monday I think17:54
comstudahh ok17:54
comstudbeen heads down lately on some internal stuff @ rax17:55
russellbi had it on github before that, you may have seen me mention that on the ML17:55
*** darraghb has quit IRC17:55
* russellb nods17:55
comstudahh that might be it17:55
russellbpayin' billz17:55
comstudya :)17:55
comstudfinally updated my cells branch17:55
comstudneed to get the BP created17:56
russellbnice17:56
russellband document it a bit?  :-p17:56
comstudhaha17:56
comstudthat's the idea17:56
russellbmaybe you  have, i dunno, haven't looked17:56
russellbthough i'm defnitely interested in that work17:56
mtaylorbcwaldon: oops. I forgot a git add. thanks.17:57
comstudif you incorporate my changes, I'll be able to make the code make a little more sense17:57
comstudcuz I will separate out some of the worker methods into different classes17:57
russellbcool17:57
comstudkinda nasty right now17:57
russellbgotta start somewhere17:58
russellbthat's a big (complex) problem to solve17:58
russellbso i have another blueprint that got assigned to me ... formalized-message-structures17:59
russellbi was thinking that by roping all rpc usage into nova/*/rpcapi.py modules, that sort of accomplishes the goal17:59
russellbthat make sense, or do you think there is more that should be done?18:00
comstudI like the rpcapi modules18:01
mtaylormnewby: fixed that patch ... thanks for pointing out that I forgot to remove stuff from setup.cf18:01
mtaylorcfg18:01
comstudi like centralizing the creation of the messages18:01
comstudinstead of forming the rpc messages all over the places18:02
russellbcool, glad you like it ... it was time consuming :-p18:02
mnewbymtaylor: np18:02
comstudYeah18:02
*** jog0 has joined #openstack-dev18:02
comstudI'm not familiar with that blueprint, but sounds like it should address at least part of it18:02
russellbDocumenting the messages passed through the rpc layer to improve modularity and scalability.18:02
russellbthat's the whole description, heh18:02
comstudahhh18:03
comstudthen yeah, blueprint done.18:03
russellbscore18:03
openstackgerritVerification of a change to openstack/keystone failed: Bug 890411: service roles and ID filtering  https://review.openstack.org/701018:03
comstudJust link docs to rpcapi.pys ;)18:03
uvirtbotLaunchpad bug 890411 in keystone "Tenant role conflicts/overlaps can be a security issue" [Medium,In progress] https://launchpad.net/bugs/89041118:03
*** somik has joined #openstack-dev18:03
russellbcomstud: thanks again for the feedback.  i'm off to incorporate your changes18:03
comstudno prob18:04
*** adjohn has quit IRC18:05
*** s0mik has quit IRC18:06
*** somik is now known as s0mik18:06
*** epim_ has joined #openstack-dev18:11
anotherjessejgriffith: building a dependency tree for cinder transition here: https://blueprints.launchpad.net/nova/+spec/remove-nova-volumes18:13
anotherjessejust getting started18:13
russellbcomstud: oh, hrm, you want more than one API class for the same API version.  That will require another tweak to the dispatch() method but I think that's ok18:14
russellbcomstud: that's what you meant by breaking up your cells code?18:14
*** zigo has quit IRC18:14
*** epim has quit IRC18:14
*** epim_ is now known as epim18:14
comstudrussellb: They don't have to be versioned the same18:15
comstudrussellb: In fact, I think they shouldn't be..18:15
comstudthat's why I have the tuples18:15
comstudbut18:15
comstudwhat you had before by using manager.API_VERSION would also still work18:15
russellbright now it stops on the first is_compatible()18:16
comstudnot sure if I understood your version correctly18:16
*** jog0 has left #openstack-dev18:16
comstudI think that's fine..18:16
comstudone shouldn't define the same method in multiple classes..18:16
comstudmaybe18:17
comstud:)18:17
russellbunless it's 2 API versions18:17
russellbthis example you put on gerrit ...         return rpc_dispatcher.RpcDispatcher([(RpcCallSetX(), '1.0'), (RpcCallSetY(), '1.0')])18:17
comstudyeah... maybe then you pick the closest version18:17
comstudhowever, i wasn't thinking about that case18:17
russellbright now it would never call anything on RpcCallSetY()18:17
comstudmy goal was just to split up functionality18:17
*** mnewby has quit IRC18:17
comstuda set of rpc methods for cell scheduler18:17
comstuda set of rpc methods for cell routing18:17
comstuddifferent method names tho18:18
russellbk, so i just need to make it ... if is_compatible() and hasattr():18:18
comstudjust makes up the huge manager class18:18
russellbright18:18
comstudinto some smaller classes18:18
comstudoooh18:18
comstudyeah18:18
comstudI missed that18:18
comstudwhat was the goal with allowing multiple managers in the first place?18:18
russellbeasy change, just making sure that's what we want18:18
comstudjust curious18:18
russellbsupporting a 1.0 and 2.0 at the same time18:19
russellb(eventually)18:19
russellbif we're like, this API sucks, i want to rewrite it (but support messages from the old version for upgrades)18:19
*** asisin has quit IRC18:19
comstudooh right18:19
comstudduh18:20
*** davidha has joined #openstack-dev18:20
russellbnormally we'd just be doing little changes, and bumping it to 1.1, 1.2, etc18:20
russellbmeaning it's compatible with 1.X where X <= the current version18:21
russellbor so was my thinking18:21
*** gyee has joined #openstack-dev18:25
*** alaski has quit IRC18:26
*** davidha has quit IRC18:27
*** novas0x2a|laptop has joined #openstack-dev18:27
*** davidha has joined #openstack-dev18:27
*** alaski has joined #openstack-dev18:28
*** maoy has joined #openstack-dev18:30
*** heyho has quit IRC18:30
maoyvishy: ping18:30
*** jakedahn is now known as jakedahn_zz18:30
*** mnewby has joined #openstack-dev18:31
*** mnewby has joined #openstack-dev18:32
*** dolphm_ has quit IRC18:32
*** smoser has quit IRC18:32
*** wting has quit IRC18:33
*** smoser has joined #openstack-dev18:33
*** bourke has quit IRC18:33
*** wting has joined #openstack-dev18:34
*** rkukura has quit IRC18:34
maoycomstud: ping18:35
cp16netjgriffith: hey i added the notifications :) https://review.openstack.org/751718:35
*** bourke has joined #openstack-dev18:35
jgriffithcp16net: Awesome!!!  I'll go have a look18:36
comstudrussellb: makes sense!18:38
comstudmaoy: pong18:38
maoycomstud: https://docs.google.com/document/d/1nlKmYld3xxpTv6Xx0Iky6L46smbEqg7-SWPu_o6VJws/edit18:39
maoycomstud: i'm trying to see if there is a way to better describe the nova state machine and simplify it18:39
*** adjohn has joined #openstack-dev18:40
maoycomstud: i'd like to get some early feedback before i send to the ML18:40
*** adjohn has quit IRC18:41
*** adjohn has joined #openstack-dev18:41
comstudthere's a larger problem I think I'd like considered along with this...18:41
maoycomstud: listening18:41
maoycomstud: it's part of a larger problem i'm working on too. :)18:41
comstudin that the API should keep track of its own view of the state18:42
*** alaski has quit IRC18:42
comstudand updates should be pushed to it when needed..18:42
*** alaski has joined #openstack-dev18:42
comstudso..18:42
comstudwhat API needs and what compute worker needs might be completely different18:43
comstudit's almost like task_state is what the worker cares about18:43
comstudand vm_state is more what the API cares about18:43
comstudalthough we do have an extension to expose task_state as well via API18:43
comstudbut anyway.. :)18:43
maoycomstud: API should care task_state too to avoid running concurrent conflicting tasks18:43
*** jsavak has quit IRC18:44
comstudas best as it can, anyway18:44
comstudthe problem is that API should always treat the information as at least slightly stale.18:44
*** garyk has joined #openstack-dev18:44
comstudthis is important for a highly distributed setup18:45
comstudesp w/ cells18:45
comstudbecause w/ cells, API has its own completely separate table18:45
comstudyou can have a cell in AU with compute workers updating state..18:46
maoyi haven't looked at the cell stuff at all.18:46
comstudbut say you have an API server somewhere that currently can't talk to it18:46
comstudcertainly they're not using the same DB..18:46
comstudso updates from that cell are pushed via queues18:46
*** dachary has quit IRC18:47
comstudAPI will update its state based off that18:47
comstudbut it's always slightly stale18:47
comstudeven today in non-cells.. it's slightly stale18:47
comstudor can be18:47
maoystale meaning?18:47
comstudi mean18:47
comstudwell18:47
comstudas soon as you return from an API call, the state is no longer valid18:47
comstudbut also...18:47
comstudthere's no transactions18:47
maoyvm_state or task_state?18:47
comstudgetting the state18:47
comstudand setting the state are not atomic18:48
comstudboth18:48
*** Ryan_Lane has joined #openstack-dev18:48
*** Ryan_Lane has joined #openstack-dev18:48
maoyit depends on how you look at this.18:48
maoysay you creating a VM, when the task finishes on the worker, the task is done in the physical world18:49
comstudyou're proposal here is a big API change18:49
maoybut not from the db's perspective18:49
comstudtasks finishing and not being marked as finished immediately isn't so much of a problem18:50
*** sdake has joined #openstack-dev18:50
maoyi actually think that only the state machine transition related part is affected18:50
maoythey are a bit broken anyway18:50
comstudanyway...18:50
maoythe other change is how you translate vm_state + task_state to the ec2 state18:51
comstudI think what you have here makes sense18:51
comstudas far as the DB is concerned18:52
comstudmapping them back to what the API returns is something else18:52
comstudlike you just said w/ ec218:52
comstudhehe18:52
maoyok.18:53
comstudnot sure about 'INITIALIZED', but18:53
comstudthis is probably good for discussion18:53
maoysure18:53
comstudbut it sounds like you're talking about now adding a subtask_state too18:53
comstudso that'll make 4!18:53
comstudhehe18:53
maoystate machine should ignore subtask_state18:54
maoythat's for something else18:54
comstudyeah18:54
comstudi'm not disagreeing with it18:54
comstudI think they all have valuable meaning18:54
maoyi'm don't completely understand soft-delete and resize18:55
maoyso the state there might be wrong18:55
*** joesavak has joined #openstack-dev18:56
*** joesavak has left #openstack-dev18:56
*** joesavak has quit IRC18:57
*** sdake has quit IRC18:57
maoybtw, what's the preferred way to present stuff like this, google doc vs etherpad vs wiki vs email?18:57
*** sdake has joined #openstack-dev18:57
*** rnirmal_ has joined #openstack-dev19:02
*** rnirmal has quit IRC19:03
*** rnirmal_ is now known as rnirmal19:03
comstudmaoy: nod.. sorry, gotta run for now19:03
comstudmaoy: I think a lot of us tend to use etherpad more than anything else..19:04
comstudthat's certainly my preference, anyway19:04
comstud:)19:04
comstudif ther'es brainstorming going on, anyway19:04
comstudwiki for links from blueprints, though19:04
comstudi'll bbs19:04
*** fc__ has quit IRC19:05
*** torgomatic has joined #openstack-dev19:06
*** novas0x2a|laptop has quit IRC19:06
*** termie has quit IRC19:07
*** adjohn has quit IRC19:07
sdagueI'm trying to add a brand new unit test (new .py file) into nova, but when I do "./run_tests.sh test_virt_driver_loader" I'm getting a AttributeError: 'module' object has no attribute 'test_virt_driver_loader'19:07
sdagueis there some other place I need to add this?19:07
*** adjohn has joined #openstack-dev19:08
*** novas0x2a|laptop has joined #openstack-dev19:08
openstackgerritVerification of a change to openstack/glance failed: Add min_ram and min_disk to bin/glance help.  https://review.openstack.org/751619:15
*** torgomatic has quit IRC19:15
*** davidha has quit IRC19:15
*** davidha has joined #openstack-dev19:16
*** dolphm has joined #openstack-dev19:16
*** torgomatic has joined #openstack-dev19:16
*** galstrom has joined #openstack-dev19:16
Blah1sdague: u shouldn't need to add it anyplace else19:18
Blah1sdague: what's the name of the file and where'd u put it19:18
sdaguenova/tests/test_virt_driver_loader.py19:19
russellbcomstud: got a moment for a sanity check?  trying to figure out how this exception could be caused by these changes ... http://paste.openstack.org/show/17837/19:19
Blah1sdague: that looks good to me19:20
Blah1can u pastebin it somewhere?19:20
*** dachary has joined #openstack-dev19:21
sdagueBlah1: yes, one minute, I just blew away my venv, once it rebuilds I can19:21
Blah1sdague : this is what i have in my test file 'nova/tests/test_blah.py':19:22
Blah1from nova import test19:22
Blah1class BlahTestCase(test.TestCase):19:22
Blah1    def test_blah(self):19:22
Blah1        self.assertTrue(1)19:22
Blah1and that seemed to work for me.19:22
Blah1./run_tests.sh test_blah19:23
*** matwood has joined #openstack-dev19:26
*** torgomatic has quit IRC19:26
*** matwood has quit IRC19:26
*** torgomatic has joined #openstack-dev19:27
*** vincentricci has quit IRC19:27
Blah1dprince : is there a way to submit smoke tests to run on a draft branch prior to having it submitted for review?19:28
*** sandywalsh_ has quit IRC19:29
*** anotherjesse is now known as anotherjesse_zz19:29
*** anotherjesse_zz is now known as anotherjesse19:30
maoycomstud: thanks.19:30
comstudrussellb: gimme a few19:30
comstudrusselb: it's a None version in dispatcher19:31
russellbk np .. i'm trying to figure it out before you have to tell me, heh19:31
comstudrussellb: I ran into that too19:31
comstudoh19:31
comstudit's the scheduler19:31
comstudbecause it has a __getattr__19:31
dprinceBlah1: Yes. There is a way but it involves manually logging into SmokeStack, putting in your branches, and then firing the job.19:32
russellboh, hasattr for the API_VERSIOn19:32
comstudyeah19:32
russellband then boom19:32
russellbawesome, thanks19:32
comstudi'd like to ditch that thing in the scheduler19:32
comstud:)19:32
comstudjust haven't gotten there yet19:33
comstudit tries to be too magic-y19:33
Blah1dprince:  oh.  what's the best way to just make sure my branch passes smoketest prior to submit for review - would running the local one in the 'smoketest' dir be the same result as the one you're running?19:33
russellbit has bitten me more than one on this patchset19:33
comstudyup19:33
*** dachary has quit IRC19:34
russellbbut to quote the source, "# NOTE(vish) magic is fun!"19:34
Blah1dprince:  i ask because i can't get my local smoketests to get anywhere near passing19:34
dprinceBlah1: You could go that route. Yes. But the Smoke tests aren't the easiest thing to get running.19:34
vishyrussellb comstud : it is fun!19:34
Blah1i would've thoguht devstack would get that all up and running but apparently not19:34
dprinceBlah1: Most devs like to dev test things on devstack.19:34
Blah1i am using devstack19:35
russellbvishy: agreed :)19:35
Blah1it's still pretty challenging.  a lot of stuff are broken even when it says it stack.sh installed successfully19:35
vishyBlah1: the smoketsts are fairly old, exercise.sh has a similar set of tests19:35
vishyBlah1: which should run out of the box on devstack.19:35
Blah1vishy: ah yes, exercise.sh appeared to run through well.  good to know19:35
vishyBlah1: you have to create a special image and run the tests specifying that image to get smoketests to work19:36
vishy(Blah1 after getting euca credentials and sourcing them)19:36
Blah1but now that i have your attention vishy, with devstack i can upload images via glance image-create just fine but using ec2ools such as cloud-publish-image decryption fails.  is that a known issue or just my lucky dev env?19:36
vishyBlah1: perhaps we should have an exercise script that runs the smoketest19:37
Blah1and also i notice the eucarc in devstack is broken i have to unset SERVICE_TOKEN && SERVICE_PASSWORD to get it to source19:37
vishyBlah1: if you ran exercises and they all passed, then bundling works through euca2ools.  There is an exercise for it.19:37
Blah1oh.  interesting19:37
Blah1i'll have to go back and check that.19:38
vishyBlah1: check how the script does it, you need to get the right keys19:38
vishyexercises/bundle.sh19:38
Blah1ya you're right.  how'd i miss that!  thx again19:38
maoyvishy: i'd also get some your early input on the nova state machine simplification proposal before i broadcast it to the public if you have time19:38
maoyvishy: https://docs.google.com/document/d/1nlKmYld3xxpTv6Xx0Iky6L46smbEqg7-SWPu_o6VJws/edit?pli=119:38
vishymaoy: ok19:38
sdagueBlah1: hmmm... yep, your example works fine, ok, something else isn't right, I'll bang on it a bit19:39
Blah1Blah1: cool19:40
vishymaoy: looks good so far19:40
Blah1whoops i meant sdague cool19:40
vishymaoy: I think you should consider keeping lock free in the following way19:40
vishysome of these fields should only be set from the top down (i.e. user requests)19:40
vishyother fields set only from the bottom up (i.e. reports from compute)19:41
vishythat way you don't have timing conflicts19:41
maoyvishy: power_state is bottom up, task_state is top down19:41
vishythe state reported by the api on show should be due to some logic that resolves all the fields into one view19:42
vishybut what about vm_state?19:42
vishyI would say vm_state should only be top down as well19:42
maoyvm_state is also top down19:42
maoyvm_state and task_state can only be changed via compute api call19:42
vishyso is vm_state really the last task that completed?19:43
vishyshould it be last_state?19:43
maoyno.19:43
vishymaoy: how would you change the current state of the vm top down?19:43
maoyvm_state is the real state. task_state is more like a "lock" to describe the on-going task19:44
maoyyou can only change the vm_state by make API calls.19:44
vishybut it doesn't change from the call19:44
vishyi.e. to get to rescued19:44
vishyit has to finish rescuing19:44
vishyright?19:44
maoyit does. it's updated at the end of the rescue task,19:45
vishyso it looks like the completion of the task updates the vm_state19:45
*** dolphm has quit IRC19:45
maoyat the same time when you set task_state to None19:45
maoyexactly19:45
vishymaoy: so who is responsible for tracking that state?19:45
vishythe others are simple because it is api request or compute report19:46
vishyit is the vm_state that is tricky19:46
maoywhoever is running the task is responsible to update the vm_state at the end of the task.19:46
maoyright now it's the compute worker.19:46
maoyit will be a different guy when we remove db from compute19:46
maoyif the task fails or stuck, the vm state won't change19:47
maoybut the task_state wont change either19:47
sdagueBlah1: ok, figured it out, I had bad import way up the chain, and it was just an unhelpful error message19:47
Blah1sdague: nice!19:47
vishymaoy: so i guess here is my problem.  What is the point of vm_state?19:47
maoywithout vm_state, when there is no task running, task_state is None. you don't know what's the status of the vm should be19:48
vishybut why do you care?19:48
vishywe know the power state19:48
vishywe know there are no tasks running19:48
vishyso why is this arbitrary state field important?19:48
maoythe power state is the physical world - what's going on, not what the customer want it to be19:49
vishymaoy: so I think you are saying that the purpose of vm_state is to have something to display to the customer19:49
maoythey can be different and when they are, different policies can be used to address that19:49
mnaserfrom my experience having two states will cause confusion, all that the customer cares is the real power_state (but forgive me, walking into a discussion here)19:49
*** legkodymov has joined #openstack-dev19:50
vishymaoy: I'm just trying to clarify, if we are only using it to display something reasonable to the customer, then we shouldn't ever key code decisions off of it19:50
openstackgerritVerification of a change to openstack/nova failed: Finish quota refactor.  https://review.openstack.org/704819:51
vishymaoy: if it is more than just for the customer than I think we are conflating too many things into one field.19:51
legkodymovHas anyone tried to do container syncing with keystone?19:51
maoyvishy: yup. i know it's hard to explain. that's why we need this discussion.19:52
maoyvishy: the vm_state + task_state together is what's running in the customer's head. power state is reality. both have values.19:53
*** Stackops-Jorge has joined #openstack-dev19:53
maoyvishy: i'm making up an example:19:54
vishymaoy: does the state machine use vm_state as an input to decide what is allowed?19:54
maoyvishy: yes.19:54
maoyvishy: e.g. you can't call unrescue if the vm_state is active19:55
maoyit must be unrescue19:55
vishymaoy: in that case i would prefer we simplify it to only include that information19:55
vishymaoy: maybe you have removed all the other ones already19:55
maoyvishy: i'm afraid they all have to be there.19:56
maoyvishy: yeah i did removed some19:56
vishymaoy: ok i don't see any superfluous ones right now19:56
vishymaoy: i think we potentially need a separate field/timestamp for destroyed19:57
maoyvishy: i thought we had that in the db..19:57
vishymaoy: we have deleted for when the db record is deleted19:57
vishymaoy: i'm thinking for when the user requests a terminate19:57
maoyvishy: ok. sure.19:58
*** anotherjesse is now known as anotherjesse_zz19:58
vishymaoy: assuming that it may take a while for such a thing to happen, it seems like we should have special case for deprovisioning.19:58
vishymaoy: otherwise I think everything looks pretty good19:58
vishymaoy: we may have to have special logic to get the user-displayed states to match the spec though19:58
maoyvishy: i deleted SHUTOFF from vm_state. that one is probably also the one you have doubt about to be included19:58
vishymaoy: aye SHUTOFF / STOPPED seem the same19:59
*** anotherjesse_zz is now known as anotherjesse19:59
maoyvishy: yes. mapping (vm_state, task_state) to ec2 state is trivial20:00
maoyi'm not very faimilar with OS api20:00
vishymaoy: yes it may be a little less trivial, but should be doable regardless20:00
*** galstrom has quit IRC20:00
maoydelete/destroy/terminate, whatever the name is, should have a higher priority so that it can preeempt other running tasks20:01
maoywhich needs a kill task support from compute workers.20:01
maoyvishy: oh. and i'm not clear about the soft-delete semantics.. you can recover the soft-deleted vms if you change your mind?20:02
vishys1rp: ^^ can you explain soft-delete ?20:02
maoyvishy: is it based on timeout or what?20:03
vishyhonestly I think all deletes should be soft by default :|20:03
vishymaoy: or at least providers should be able to keep the instance data around for a while and have it cleaned up later20:03
kbringardthis is a super good idea20:03
maoyvishy: so after a soft-delete, it's only a shutdown but no cleanup? there is a periodic_task somewhere to clean up later?20:05
vishymaoy: i think so20:05
s1rpvishy: sure, soft-delete just shutdown the VM and puts it in a `soft-delete` state so that it's in accessible to the customer. a periodic_task (in nova/compute/manager) periodically hard-deletes any soft-deleted instances that have expired20:05
s1rpthere is also a python-novaclient extension that allows you to force delete or undelete soft-deleted instances20:06
maoys1rp: thanks. gotta update the state machine to reflect that..20:07
maoys1rp: so when i call terminate in ec2 api, is it softdelete or hard? doesn't it count against my quota?20:07
s1rpmaoy: right now soft-delete is only available via the Openstack API, though I don't think there is a reason why we couldn't include it in ec2 as well20:09
maoys1rp: i c. what about the quota question? that has nothing to do with state machine though. :)20:09
s1rpmaoy: i seem to recall it counting against your quota (which seems like a bug)20:10
*** renier has joined #openstack-dev20:10
s1rpmaoy: the quota stuff is being completely reworked so i wonder if thats still the case, if it is, we should file a bug against that20:11
maoys1rp: got it.20:11
*** anotherjesse is now known as anotherjesse_zz20:12
*** anotherjesse_zz is now known as anotherjesse20:12
*** legkodymov has quit IRC20:12
*** jakedahn_zz is now known as jakedahn20:13
maoyvishy: the resize/migration part is the last puzzle to me..20:15
maoyvishy: are user allow to manually confirm resize via api if task_state is in RESIZE_VERIFY?20:15
comstudyes20:16
comstudmaoy: yes20:16
comstudmaoy: or optionally, they can revert it20:16
maoycomstud: but a periodic task running in the background is also trying to confirm that automatically?20:17
*** cdub has quit IRC20:17
comstudyes, it'll auto-confirm it for the user after a period of time20:17
comstudif they do not20:17
maoyis either VM, src/dst, running during resizing?20:19
maoyis live_migration a special case of resizing or separate magic?20:20
*** wiliam has quit IRC20:21
maoycomstud, vishy: ^^20:23
comstudthe src is shut down to resize20:23
comstuddest won't start until the resize is done20:23
vishymaoy: live-migration and block-migration are special magic20:23
vishy(and they only work on kvm right now)20:23
comstudxenapi coming!20:24
comstudsupposedly20:24
*** adalbas has quit IRC20:24
maoycomstud: ok. now the state machine is clearer. but how does the user know when to confirm resize? or whether to confirm?20:24
comstudbecause they're return a state of resize_verify20:25
comstudor something similar20:25
comstudbut also...20:25
comstudthey had to have kicked off the resize themselves20:25
comstudso they should know they'd need to confirm it20:25
maoyi c.20:25
maoyhave to familiarize myself with those don't exist in ec2..20:26
maoywhat should ec2 api interpret a resize_verify state?20:27
maoyor we assume it doesn't happen. since the user had to use OS api to resize in the first place?20:27
*** thingee has joined #openstack-dev20:28
comstudi try to ignore the ec2 api, honestly.20:28
comstudwhich is probably bad of me20:28
maoylol20:28
comstud:)20:28
comstudSo I cannot answer your question20:28
maoyfair enough20:28
comstudvishy is a lot more familiar with it than I am20:30
*** mcclurmc_ has joined #openstack-dev20:34
vishymaoy: i think we can safely ignore it in ec2 (just display it as active)20:38
vishy(or running I guess it is in ec2land20:38
*** Ruetobas has quit IRC20:40
*** rkukura has joined #openstack-dev20:42
*** Stackops-Jorge has quit IRC20:43
*** vincentricci has joined #openstack-dev20:43
*** johnpostlethwait has quit IRC20:44
*** Stackops-Jorge has joined #openstack-dev20:45
*** davidha has quit IRC20:45
*** mcclurmc_ has quit IRC20:45
*** davidha has joined #openstack-dev20:46
*** lorin1 has joined #openstack-dev20:46
maoyvishy: how is the ERROR state used in vm_state now? is it safe to say any exception in any task would set it to ERROR?20:47
*** johnpostlethwait has joined #openstack-dev20:48
vishymaoy: not necessarily, for example, an error in a live migrate just rollbacks20:48
*** johnpostlethwa-1 has joined #openstack-dev20:48
*** Ruetobas has joined #openstack-dev20:48
maoyvishy: what can a user do if vm_state is in error besides delete?20:49
vishymaoy: right now nothing.  Pretty bad user experience20:50
maoymaoy: i'm proposing to remove ERROR state. the vm_state won't change if the task raises an exception20:51
*** devananda has quit IRC20:51
maoyvishy: ^^20:51
maoyvishy: this is compatible with migration behavior.20:51
maoyvishy: but i wonder how would the user know if something went wrong. not that hard in general. and we always allow delete no matter what.20:52
*** johnpostlethwait has quit IRC20:52
*** littleidea has joined #openstack-dev20:57
vishymaoy: yeah i don't think you can do that without an api change20:57
vishymaoy: I guess we could just show error to the user if there are faults in the instance_faults table20:57
*** stuntmachine has quit IRC20:59
*** andrewsben is now known as andrewsben_zz20:59
maoyvishy: ok.20:59
maoyvishy: didn't know we had that table. hoho.21:01
vishymaoy: the problem is there are times when things have gone wrong but the instance is still usable (like if a resize fails and is rolled back)21:01
maoyvishy: exactly.21:02
vishymaoy: so it sucks to show the state as ERROR in that case21:02
maoyvishy: if there is a rollback for a task call, and the rollback works, vm_state shouldn't be touched21:02
*** galstrom has joined #openstack-dev21:02
maoyvishy: can we silently add it to instance_fault table?21:03
*** troytoman is now known as troytoman-away21:03
vishymaoy: but the spec says instance_faults only show up in ERROR State21:03
vishy:(21:03
maoyvishy: oops.21:03
maoyvishy: the OS API spec?21:04
maoyvishy: guess we already violate that with livemigration rollback?21:05
*** lts has quit IRC21:05
maoyvishy: anyway, probably a good idea to still keep error state for now..21:06
*** Mkenneth1 has quit IRC21:09
*** renier has quit IRC21:09
*** AlanClark has quit IRC21:09
*** markvoelker has quit IRC21:10
russellbcomstud: updated rpc version patches with your input from earlier ..21:10
*** AlanClark has joined #openstack-dev21:11
*** danwent has quit IRC21:12
*** alaski has quit IRC21:15
*** rnirmal has quit IRC21:17
*** lorin1 has quit IRC21:19
comstudrussellb: cool, will take a look shortly21:20
*** cmagina has joined #openstack-dev21:22
*** cmagina_ has quit IRC21:23
*** flaviamissi has quit IRC21:24
*** cmagina has quit IRC21:24
*** cmagina has joined #openstack-dev21:25
*** flaviamissi has joined #openstack-dev21:26
*** mcclurmc_ has joined #openstack-dev21:26
*** b1rkh0ff has quit IRC21:27
*** b1rkh0ff has joined #openstack-dev21:30
*** flaviamissi_ has joined #openstack-dev21:32
*** flaviamissi has quit IRC21:32
*** flaviamissi_ is now known as flaviamissi21:32
*** galstrom has quit IRC21:33
*** pixelbeat has quit IRC21:36
*** Mkenneth has joined #openstack-dev21:37
*** renier has joined #openstack-dev21:40
*** ywu has joined #openstack-dev21:41
*** maoy has quit IRC21:44
*** ayoung has quit IRC21:45
*** gyee has quit IRC21:45
*** torgomatic has quit IRC21:58
*** Stackops-Jorge has quit IRC21:59
*** mcclurmc_ has quit IRC22:00
*** sdake has quit IRC22:04
*** Gordonz has quit IRC22:05
*** torgomatic has joined #openstack-dev22:05
*** flaviamissi has quit IRC22:06
*** Mkenneth has quit IRC22:06
*** kbringard has quit IRC22:08
zykes-jk0: ping22:08
*** byeager has quit IRC22:09
openstackgerritVerification of a change to openstack/glance failed: Implement image visibility in v2 API  https://review.openstack.org/743022:15
*** Ryan_Lane has quit IRC22:15
*** torgomatic has quit IRC22:16
*** torgomatic has joined #openstack-dev22:17
*** mrunge has quit IRC22:18
*** ecarlin has joined #openstack-dev22:18
*** Mkenneth has joined #openstack-dev22:20
*** salgado has quit IRC22:23
*** PotHix has quit IRC22:24
*** byeager has joined #openstack-dev22:25
*** dachary has joined #openstack-dev22:26
*** ecarlin has quit IRC22:29
*** anderstj_ has quit IRC22:33
*** bhuvan_ has joined #openstack-dev22:34
*** byeager has quit IRC22:42
*** danwent has joined #openstack-dev22:44
*** devananda has joined #openstack-dev22:47
*** jkyle has joined #openstack-dev22:50
*** b1rkh0ff has quit IRC22:51
*** devananda has quit IRC22:54
*** devananda has joined #openstack-dev22:55
*** pmezard has quit IRC22:55
*** dtroyer is now known as dtroyer_zzz22:57
*** littleidea has quit IRC23:00
*** edygarcia has quit IRC23:03
*** gporras has joined #openstack-dev23:14
*** littleidea has joined #openstack-dev23:15
gporrashey guys, I'm trying to run the keystone tests ( ./run_tests.sh ) but why do I need to have keystoneclient and swift ? is there a way to turn this off and only test whatever I need to test for keystone?23:15
*** lloydde has quit IRC23:20
*** mnaser has quit IRC23:32
*** jakedahn is now known as jakedahn_zz23:32
*** mnaser has joined #openstack-dev23:35
*** lloydde has joined #openstack-dev23:36
*** roge has quit IRC23:37
*** flaviamissi has joined #openstack-dev23:37
*** byeager has joined #openstack-dev23:39
gporrasnot a usefull channel23:40
*** mnaser has quit IRC23:40
*** gporras has left #openstack-dev23:40
*** thingee has quit IRC23:46
*** AlanClark has quit IRC23:46
*** ywu has quit IRC23:47
*** lloydde_ has joined #openstack-dev23:51
*** lloydde has quit IRC23:53
*** mnaser has joined #openstack-dev23:54
*** lloydde_ has quit IRC23:57

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