Tuesday, 2016-01-19

*** annegentle has quit IRC00:06
*** annegentle has joined #openstack-opw00:32
*** jengeb1 has quit IRC02:19
*** annegentle has quit IRC04:45
*** annegentle has joined #openstack-opw06:46
*** annegentle has quit IRC06:50
*** GB21 has joined #openstack-opw06:55
*** GB21 has quit IRC07:09
*** GB21 has joined #openstack-opw07:26
*** GB21 has quit IRC07:37
*** GB21 has joined #openstack-opw07:40
*** GB21 has quit IRC07:56
*** rossella_s has quit IRC08:08
*** arushi has joined #openstack-opw09:55
*** arushi has left #openstack-opw09:57
*** neiljerram has joined #openstack-opw10:01
*** njirap has joined #openstack-opw10:48
*** neiljerram has quit IRC11:01
*** aysyd has joined #openstack-opw11:06
*** rossella_s has joined #openstack-opw11:07
*** jengeb has joined #openstack-opw11:34
*** neiljerram has joined #openstack-opw11:55
*** enthurohini has joined #openstack-opw11:55
*** julim has joined #openstack-opw12:19
*** njirap has quit IRC13:31
*** njirap_ has joined #openstack-opw13:31
*** njirap_ has quit IRC14:07
*** njirap has joined #openstack-opw14:07
*** enthurohini has quit IRC14:08
*** annegentle has joined #openstack-opw14:09
*** lblanchard has joined #openstack-opw14:14
*** annegentle has quit IRC14:27
*** rossella_s has quit IRC14:30
*** rossella_s has joined #openstack-opw14:31
*** neiljerram has quit IRC14:40
*** neiljerram has joined #openstack-opw14:49
*** annegentle has joined #openstack-opw15:04
*** annegent_ has joined #openstack-opw15:04
*** annegentle has quit IRC15:08
*** annegent_ is now known as annegentle15:16
psargentneiljerram: are you there?15:19
*** enthurohini has joined #openstack-opw15:20
neiljerrampsargent, hi there!15:21
neiljerramhow are you?15:21
psargenthello! doing well. and you?15:21
psargentI started looking into how the nova controller assign instances to the compute node.15:22
psargentI looked in the n-sch logs15:23
neiljerramOK, interesting.  That's an area I don't know myself.15:24
psargentyes..I was thinking there may be some changes around that area...so wanted to understand15:26
*** annegentle has quit IRC15:26
*** annegentle has joined #openstack-opw15:26
neiljerramI just read your email too - sorry that I haven't already replied to that.15:27
psargentI see a call where the nova.scheduler.host_manger updated host state with instances..looking for how it assigns the IP15:28
neiljerramOK, it seems like we're getting to the heart of the work now.15:29
psargentgreat..i just wanted to make sure I am on the right track!15:29
neiljerramI'm not sure the elements are all clear in my mind - so let's talk through them a bit.15:29
neiljerramYes I believe you are.15:29
neiljerramSo we want to design and write a new pluggable IPAM driver, that gets an IP allocation request that includes the compute host, and can choose an IP address according to that compute host.15:30
neiljerramBut at a higher level there's the question of what order things happen in.15:31
psargentyes....15:32
neiljerramSpecifically, does Nova choose the compute host before Neutron/IPAM decides the IP, or after?15:32
neiljerramYou might already know that, from the timestamps on the Nova and Neutron logs...15:33
psargentyes....I haven't compared the timestamps yet !! But will..I was tracing the calls to gain an understaning of what is happening15:34
neiljerramThat sounds very useful.15:34
*** jengeb1 has joined #openstack-opw15:35
psargentok....I think I am almost there...just wanted to get a high level view15:36
psargentof what's going on with the Nova and the compute host15:36
neiljerramMy guess is that, in the most common way of creating a VM, the IP allocation happens first.  But I think that there may be a sequence of command line calls that we can use to make the IP allocation happen later15:38
*** jengeb has quit IRC15:38
psargentNova uses a filter scheduler which supports filtering and weighting to make informed decision on where a new instance should be created....http://docs.openstack.org/developer/nova/filter_scheduler.html15:39
psargentok....so IP allocation happens first but can change the sequence15:40
neiljerramI'm aware of the filter scheduler, but I don't think we need to involve that yet.15:41
psargentok15:41
neiljerramIn the overall picture of why someone would want host-dependent IP allocation, the filter scheduler would certainly be relevant - but there's a very useful first step that we can take without it.15:42
neiljerramTo explain further... the idea is that we want different IP prefixes in different areas of the data center - for example we might want a particular IP prefix for VMs on all the compute hosts that belong to a particular rack in the data center.15:43
neiljerramThen there might be a situation where a particular IP prefix was completely used up, and hence the next VM should not be placed on a one of the compute hosts that would use that IP prefix.15:44
psargentOk...I get it15:45
neiljerramSo that would be a case for using the filter scheduler.15:45
psargentok15:46
neiljerramBut to begin with, we can just address the problem of: "once Nova has selected so-and-so compute host, what is the right IP prefix that we should use for a VM on that host"15:46
psargentok...i got it...just thinking about it15:48
neiljerramSo, I _hope_ that there is a way of booting a VM such that the IP allocation can happen after the compute host has been chosen, as follows.15:49
neiljerram1. Create a Neutron port with no IP address (neutron port-create ...)15:49
neiljerram2. Create a VM using that port, including deciding which compute host, but don't actually boot it yet.  (nova boot or some other nova command?)15:51
neiljerram3. Now add an IP address to the Neutron port (neutron port-update ...)15:53
neiljerram4. Now tell the VM to boot.15:53
psargentok....got it...15:55
neiljerramIf that sequence would work, we can then work on an IPAM module that would do what we want in step 3.15:55
psargentok...15:57
neiljerramDo you feel like experimenting with that kind of sequence?15:58
neiljerramAlternatively, you could ask other developers by writing either to the mailing list or on IRC.15:59
psargentOk I'll check the timestamps to see which comes first IP allocation or selecting the compute node15:59
psargentyes...I can check it out15:59
neiljerramYes, definitely good idea to check that first.16:00
psargentand then see if the CLI commands will allow this sequence16:01
psargentok..i'll go ahead a get started...thanks !!!16:04
neiljerramHave you used CLI commands at all yet in your DevStack system?16:04
psargentI tried to use the CLI commands but I ran into an error...I researched the error a bit but couldn't get to work...I've been using horizon16:05
neiljerramYou'll need to get past that then.16:06
neiljerramNormal procedure is that DevStack creates a file named 'openrc' in the same place where you run stack.sh.  This file contains credentials that you need for running CLI commands.16:07
neiljerramSo, once stack.sh has finished, you then do: ". openrc admin admin"16:07
neiljerramThat puts the credentials into environment variables into the current shell.16:08
psargentok....i'll take a look...from what I remember ...the error was something to do with username...16:08
neiljerramAnd then you can run "nova ..." and "neutron ..." commands.16:08
psargentok16:08
neiljerramThat sounds like a credentials problem, and should be fixed by using openrc as just described.16:08
neiljerramOK, cool.  Please do feel free to ping me straightaway if you hit any problems.16:09
psargentokk...would I  need to unstack and run stack.sh ?16:09
neiljerramNo, if you've already done stack.sh, the system should already be fine16:10
psargentok16:10
psargenti'll check the credentials and then ".openrc admin admin" Thanks!16:11
neiljerramShould be a space after "."16:12
psargentok16:12
neiljerramCool, good luck!16:12
psargentThank you !!!!16:12
*** joyce__ has joined #openstack-opw16:17
*** arushi has joined #openstack-opw16:28
arushiHi people.. If anyone can help me get started... I know python.. Can anyone suggest me a bug to start with? And  tell me if there is any other thing that I need to setup before I  start contributing to openstack? It will be a great help!16:42
*** annegentle has quit IRC16:46
enthurohiniarushi, first thing, you will need to setup devstack (development version of openstack). link that can help you is http://blog.sayalilunkad.com/posts/Devstack/16:47
enthurohiniparallerly, explore openstack components, nd find your interest, to which you want to contribute.16:49
*** annegentle has joined #openstack-opw16:50
enthurohiniAfter this you can search bug for your interested component on launchpad. simple bugs have tag "low-hanging-fruits". you can start with that.16:51
*** annegentle has quit IRC16:55
*** arushi has quit IRC16:55
*** khushbu has joined #openstack-opw17:17
*** khushbu has quit IRC17:22
*** njirap has quit IRC17:50
*** enthurohini has quit IRC18:21
*** jengeb1 has quit IRC18:26
*** rossella_s has quit IRC18:30
*** rossella_s has joined #openstack-opw18:31
*** neiljerram has quit IRC18:36
*** annegentle has joined #openstack-opw18:38
*** jengeb has joined #openstack-opw19:48
*** aysyd has quit IRC19:59
*** joyce__ has quit IRC20:17
*** annegentle has quit IRC21:00
*** lblanchard has quit IRC22:16
*** rossella_s has quit IRC22:31
*** rossella_s has joined #openstack-opw22:31
*** annegentle has joined #openstack-opw23:10

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