/srv/irclogs.ubuntu.com/2014/06/26/#cloud-init.txt

=== praneshp_ is now known as praneshp
=== harlowja is now known as harlowja_away
=== evilissimo|afk is now known as evilissimo
CatKillerHi there, I'm having some issues with cloud-init, I've built a Ubuntu desktop image with cloud-init and OpenStack as the source, but cloud-init fails to retrieve the metadata from the server as the network isn't configured yet. Any ideas how to get cloud-init to configure the network so that the server can be contacted? Running it after the OS has finished booting (and subsequently once the network is up) works fine.10:00
robjoJust noticed that the Azure data source tries to start "walinuxagent". This appears inconsistent to me as the upstream source provides "waagent"12:37
robjoshouldn't cloud-init stick to upstream provided names?12:38
robjoAlso the code is setup to always use the "service" command. While distros switching to systemd have service rewired to do the "right" thing it would be nice to use systemctl where appropriate12:41
smoserCatKiller, hi13:22
smosercloud-init runs its network metadata search when all configured 'auto' interfaces are set up in /etc/network/interfaces.13:22
smoseri suspect you just need to put 'auto eth0' and config it for dhcp there.13:23
smoserrobjo, i'm not opposed to that, but service is a functional work around.13:23
smoserie, usage of it was by design. 13:24
smoserwrt walinuxagent or waagent, i'm not sure. i'm fine for patches to go looking for the right name.13:24
robjosmoser: so conditional code for name and command would be OK?13:25
smosersure. i dont really care. 13:25
smoseronce we got azure functional, i have not looked back at it. and have been happier :)13:25
robjoyup, I usually look at this stuff only as long as I have to as well, will work on a patch13:26
smoserthe worst hack in azure is bouncing the network interface in order to "publish" the hostname.13:26
smoseri'm guessing what i have there wont work on suse13:27
robjoOK, thanks for the heads up, will take a look at that as well13:27
smoserfwiw, the agent start command is configurable13:28
smoservia the datasource config13:28
smoser(and so is bounce command)13:29
robjoYes I saw the "merge" call but I cannot put all the parts together just yet on how the configuration and everything else connects13:30
CatKillersmoser: Oh my god you're right, I know what's happening13:31
CatKillerSilly Ubuntu desktop comes with Network Managr13:31
CatKiller*Manager13:31
CatKillerOr nightmare manager as I like to call it13:32
CatKillerSo cloud-init must be waiting from the network to be up from upstart which is probably not really happening with Network Manager13:32
CatKillerI'm going to remove it completely (unless there's a better option)13:32
smoserCatKiller, if it were me, i might go the route of grabbing a cloud image and apt-get install ubuntu-desktop13:37
smoserrather than building your own13:37
CatKillersmoser: I thought about this13:37
CatKillersmoser: I thought it would be bad13:38
smoserCatKiller, its not waiting for anything from network manager13:38
CatKillerbut I just learned the hard way!13:38
smosercloud-init's job only waits on "static networking"13:38
CatKillerI'm actually probably do what you suggested13:38
smoserwhich means "stuff configured 'auto' in /etc/network/interfaces"13:38
CatKillerIt does make a lot of sense13:38
CatKillerFew distros use NetworkManager and no server ones would (which is usually what people start in the cloud)13:39
CatKillersmoser: I think I'll go the way you suggested with getting ubuntu-desktop in a cloud image13:39
CatKillerBut thanks a lot for helping me understand what was going wrong13:39
smoserCatKiller, i might do something like:13:39
smoser get-cloud-iamge13:39
CatKillerit's good to know why something didn't work13:39
smoser mount-image-callback my.image -- chroot _MOUNTPOINT_ apt-get intsall ubuntu-desktop13:40
smoserthat wont' "just work", but it will be pretty close13:40
smosera couple gotchas:13:40
smosera.) you'll have to resize the image to larger than 2G (maybe)13:40
smoser  er... 1.4G13:40
CatKillerTrue, didn't think of that13:40
smoserb.) you'll have to disable services . i have that code somewhere, let me find it.13:40
CatKillersmoser: Thanks, that's great13:41
smoser(disable services so they dont start when you 'apt-get install' stuff)13:41
smoserCatKiller, https://code.launchpad.net/~smoser/maas/maas-ephemerals-v213:42
smoserthe bin/maas-cloduimg2ephemeral is what we do to make the cloud images into "ephemeral" images.13:43
smoserthe process is much the same13:43
smoserbut we dont have to grow the disk.13:43
CatKillersmoser: Nice!13:43
CatKillerSo I don't even have to boot the cloud image in KVM to configure it then?13:43
smoserCatKiller, well, i do the build process inside a kvm. 13:44
smoserbut thats neither here nor there.13:44
smoserwe just do that for safety13:44
CatKillerok but you don't need to actually boot the cloud-image to install packages etc13:44
smoseri'd be very open to patches to mount-image-callback for '--grow-first=4G' or something like that.13:45
smoserright. we dont boot it.13:45
CatKiller(which I had been doing to configure my existing cloud image, I booted it and configured it)13:45
smoserwe chroot in and 'apt-get install'13:45
CatKillersmoser: If I can figure out a way to streamline the growing13:45
CatKillerI'll submit a patch13:45
CatKillerSo your package is similar to "vmbuilder" right?13:46
CatKillerexcept it relies on Ubuntu's preconfigured cloud images instead of building one from scratch from what I can gathr13:47
CatKiller*gather13:47
CatKillerbbl13:48
smoserCatKiller, i really would never suggest to anyone that they build a cloud iamge from scratch13:55
smoserthere are tools that do that, and i thik that they are silly13:55
smosersimilarly i'd never suggest to anyone that they build their own linux kernel, python, glibc or php13:56
smoserpeople do that for you, use their work.13:56
robjosmoser: tried the config route for Azure and starting the agent14:07
robjothen "rm -rf /var/lib/cloud/*"14:08
robjoafter running cloud-init -d {init, init --local, modules --mode=config} in that order on the command line there is no evidence of an attempt to start the agent?14:09
robjoIs this testable live or do I have to run a re-build upload etc. cycle?14:10
robjoThe config entry looks as follows:14:10
robjodatasource:14:11
robjo  Azure:14:11
robjo    agent_command: ['service', 'waagent', 'start']14:11
=== zz_gondoi is now known as gondoi
smoserrobjo, it should be testable14:21
smoserpastbin /var/log/cloud-init.log ?14:21
smoserrobjo, 14:22
smoserinit --local 14:22
smoserneeds to run first14:22
smoser(it clears the state)14:23
smoserthen init14:23
smoserand init should have ran and found the azure datasource14:23
robjoOK, let me try again14:23
smoseryou can configure off the other datasources to reduce cruft.14:24
CatKillersmoser: Makes total sense, I'll use the cloud image first14:29
robjosmoser: http://pastie.org/932684214:31
smoserrobjo, /var/log/cloud-init.log should be much more verbose than that.14:34
smoseroh. and i see. seed=/var/lib/waagent14:35
smoserheres another fun bit of azure, robjo 14:35
smoseryou get that CDrom that has important data14:35
smoserbut at some point in a reboot they just yank it from you14:35
robjo/var/log/cloud-init.log is empty, I pasted /var/log/cloud-init-output.log14:35
smoserrobjo, you rpboably need to restart syslog14:35
smosermaybe remove that file and resart syslog.14:36
smoseror maybe on suse thats not hooked up right. but thtats a bug .14:36
smoserif its not.14:36
smoserhm..14:36
smoserhm.. sorry for being dense.14:36
smoserthere is defintiely more verbose output going somewhere.14:37
robjosmoser: http://pastie.org/932691114:41
robjohttp://pastie.org/932691414:41
robjohttp://pastie.org/932691714:42
robjohttp://pastie.org/932692014:42
robjoOutput in the terminal from each command, was too large for 1 paste14:42
smoserrobjo, suse needs 'pastebinit'14:43
smoserits amazingly convenient.14:43
smoserpastebinit <file>14:43
smoseror14:43
smosersome-command | pastebinit14:43
robjo/var/log/cloud-init.log is still empty even after restarting syslog14:43
smoser2014-06-26 14:39:34,259 - stages.py[DEBUG]: Restored from cache, datasource: DataSourceAzureNet [seed=/var/lib/waagent]14:44
smoserit found that, so its not going to go through its earch14:45
smosernot really sure why it found it as init --local should have removed that link14:45
robjoso where is that cache? so I can get rid off it ;)14:45
smoserwell its /var/lib/cloud/instance that is a link. 14:46
smoseryou can purge all of /var/lib/cloud14:46
robjoI did, before I ran the commands.....grmbl14:46
robjorm -rf /var/lib/cloud/*14:46
smoserare you able to just let me in to poke really quick ?14:49
robjoyes, send me your public key14:51
robjorjschwei@suse.com14:51
smoserrobjo, https://launchpad.net/%7Esmoser/+sshkeys14:53
smoseranother tool you need is 'ssh-import-id' :)14:53
robjosmoser: OK, try this: ssh azuser@sp3-ibs-try4.cloudapp.net14:55
smoserrobjo, k. i'm in14:56
smoserrobjo, for logging, cloud-init sends its log to /dev/log14:58
smoserwhich in ubuntu gets sent to /var/log/cloud-init.log because of 14:59
smoser http://paste.ubuntu.com/7706306/14:59
smoserso yours is just goign to /var/log/messages15:00
smoseras its not being captured specifically somewhere15:00
=== gondoi is now known as zz_gondoi
robjoOK, can certainly setup the rule, thanks15:00
smoserif you ust remove the 15:00
smoser [ *log_base, *log_syslog ]15:00
smoserline in /etc/cloud.d/cloud.cfg.d/05_loging15:01
smoserthen it will go straight to the file15:01
smoserso i made that change15:02
smoserand now ran15:02
smosercloud-init init --local15:02
smoserand15:02
smoser cloud-init init15:02
smoserand see the log15:02
smoseryou can see your 15:03
smoser 'service', 'waagent', 'start'15:03
smoserthe reason for the logging being as it is, is that generally, i wanted to use syslog15:03
smoserbut early in boot syslog isnt necessarily available15:03
smoserso cloud-init tries to write to /dev/log15:03
smoserand if htat fails it writes to /var/log/cloud-init.log directly15:04
smoserthen, the next time it comes up (cloud-init init) it probably has /dev//log15:04
smoserand it works.15:04
smosernote, the file above in that pastebin is a rsyslog format file. i dont knwo about your syslog (syslog-ng)15:06
robjoOK, makes sense. I'll fix the logging ni my image builds. And will just configure the datasource in the config file, then there is no need to have a bunch of ugly serach code in the azure datasource code15:06
robjowe have syslog-ng in sles 11, rsyslog in openSUSE and rsyslog will be in SLE 12, it's a mess, bute getting better :)15:07
robjoThanks, one problem down :)15:08
smoserso just one other gotcha there.15:08
smoseron our walinuxagent15:08
smoserwe do not start it by default15:08
smoserand we basically configure off all of its function15:09
smoseras it overlaps with cloud-init. so we have cloud-init start it only on azure. and neuter it heavily. 15:09
robjoI am setting "Provisioning.Enabled=n" in the waagent.conf, that's the info I got from M$15:10
robjoso should I or should I not enable the agent to start at boot?15:11
smoseri'm trying to remember15:13
CatKillersmoser: Does cloud-init (using configuration found on the Ubuntu cloud-image) run unattended security upgrades on boot, or is it something that needs to be defined at the metadataserver level?15:17
smoserCatKiller, by default it does not do that.15:19
smoseryou'd enable that via user-data or some other way15:19
smoseryou could patch that on when you re-build your images15:19
CatKillersmoser: ok, no problem. I'll patch that while rebuilding15:20
CatKillerAnother thing, what are the "cloud_config_modules" defined in the cloud.cfg config file?15:20
CatKillerAre they programs that will run during the config stage15:20
CatKillerFor instance I wanted to know what "package-update-upgrade-install" was doing but couldn't really tell15:20
smoserCatKiller, i'm sorry that documentation for such things sucks.15:21
smoserthat ends up involking the 'cc_package_update_upgrade_install.py' file15:21
smoserwhich handles 'apt_update' and 'apt_upgrade'15:21
smoserbut this is not anywhere well documented.15:21
CatKillersmoser: OK, I'll look in that file. Just a quick question though15:23
CatKillerall of the modules defined in the cloud.cfg will run, or does that just mean they're available?15:23
CatKillerand the metadata will tell which one needs to run15:23
smoserthey run15:24
smoserthe user-data can configure which ones run15:24
smoseryes.15:24
smoserby re-defining that list15:24
CatKillersmoser: But if it's not defined in the user-data (we use OpenStack here and the user data is *very* scarce) it'll run15:25
smoserwhat do you mean the user data is very scarse15:25
smosermodules generally do the right thing.15:26
smoserif you give htem config, they may act and have sane defaults 15:26
CatKillersmoser: Well the metadata only provides hostname, authorized SSH keys but not much more15:26
smoseruser-data15:26
smosernot meta-data15:26
CatKillerah ok sorry my bad I confused the two15:27
smoseruser provides user-data when they launch an instance15:27
smosernova boot --user-data=your.user-data.file.txt15:27
CatKillerAh ok I see. We don't provide any specific user data here as far as I know15:27
smoserright. so you get the default behavior. which should be perfectly fine.15:28
CatKillerOK, sounsd good15:28
=== evilissimo is now known as evilissimo|afk
CatKillerAnother thing I'm not entirely sure about. In the config there is a "package-update-upgrade-install" module, and in "cc_package_update_upgrade_install.py" the handle function looks for "package_update" and "apt_upgrade" from the configuration15:29
CatKillerthese are unrelated right?15:29
smoserthey're synonyms15:30
smoserdistro-generic and distro-specific.15:30
CatKillerSo "apt-get update" and "apt-get upgrade" will run on boot (or is that only on *first* boot) with the default cloud-init config?15:31
smoserdefault is off15:31
smoseryou can turn it on and it will run on first boot15:32
smoserthat module only runs 'per-instance'. by default.15:32
smosermeaning once per instance-id15:32
CatKillerBut it's in the config file though, so the user-data defines the behavior here?15:32
smoseryou can change it to run per-always15:32
smoseryou can put it in config also15:32
smoserand the user-data can still override15:32
CatKillerah ok, so here it's in the config but user-data probably overrides.15:33
CatKillerWhere can I find the user data in the system actually?15:33
CatKiller(the default ones)15:33
smoserthere is no real location for defaults. 15:34
smosermost of stuff is described 15:34
smoser http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/cloud-config.txt15:34
smoserand other files in http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/files/head:/doc/examples/15:34
CatKillerthanks for those files15:35
CatKillerbut in the specific of cloud.cfg's "package-update-upgrade-install" module, where can I figure out what will happen there?15:36
CatKillerI'm not really sure what this clause does15:36
CatKilleror where it is configured15:36
CatKillerI guess I'm having trouble linking those modules with what will actually happen when they run (their config files etc)15:37
smoserCatKiller, by default basically nothing happens there.15:41
smoserbut it responds to some settings in15:42
smoser http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/cloud-config.txt15:42
smoser(package_upgrade=true)15:42
CatKillersmoser: Ah ok, makes sense15:47
CatKillersmoser: And just a quick question so that I can understand this config file better15:47
CatKillerwhere are all these clause defined then in the code?15:47
CatKillerI grepped for "package-update-upgrade-install" without success15:48
CatKillerin the cloudinit Python code15:48
CatKiller(I wanted to figure out what config clause did what by looking at the source)15:48
smosercloud_config_modules, cloud_init_modules and cloud_final_modules16:33
smoserare lists16:33
smoserthey reference "config modules"16:33
smoserconfig_modules are loaded . they'r ein the source tree at cloudinit/config/cc_<name-in-list>.py16:34
smoserwhere 'name-in-list' has '-' replaced with '_'16:34
CatKillersmoser: Ahhh ok I get it. Sorry you were trying to tell me this earlier and I had completely missed it. I thought the "cc_" file you told me to lookup handled all of the "config modules"16:44
CatKillersmoser: It's much much clearer now, thank you very much16:44
smosercool16:44
CatKillersmoser: There's one thing that I'm not quite sure about yet16:44
CatKillersmoser: Let's imagine I don't want to pass custom "user-data" to the instance, where can I configure a "default" user-data within the image?16:45
smoseryou cant explicitly provide default user-data.16:46
smoseruser-data an be cloud-config syntax or other syntaxes.16:46
smoserbut you can provide any config in /etc/cloud/cloud.cfg.d/<your-file>.cfg16:46
CatKillersmoser: Ah great, so I could add a file  /etc/cloud/cloud.cfg.d/my-config.cfg that would contain:16:47
CatKiller#cloud-config\npackage_upgrade: true16:47
CatKillerfor instance16:47
CatKillerIn that case, that config would be interpreted as a "cloud-config" file and the package_update should run on first boot16:47
CatKillerDoes that sound right?16:47
smoseryes.16:53
smoserfiles in that dir do not need to start with #cloud-config16:53
smoserthey can only be cloud-config16:53
CatKillersmoser: Good to know16:53
CatKillersmoser: In the absolute, it seems that I could add the package_upgrade: true clause at the top level of the /etc/cloud/cloud.cfg config file as well no?16:53
CatKillerlooking at the cc_package.... script it seems that it'll get the flag from the config(s) files (presumably cloud.cfg included)16:54
smoseryeah.16:56
smoserconfig modules know no difference between "builtin" config and user-data16:57
smoserits all just config that they act on16:57
=== harlowja_away is now known as harlowja
harlowjasmoser hey, do u have any medium size ideas for cloud-init that i can do, need a diversion from the other projects :-P17:32
smoseris that medium sized in human terms17:33
smoseror in super-human  harlowja terms17:33
harlowjalol17:33
harlowjaharlowja terms i guess :-P17:33
smoserthe stuff i have listed here is at: 17:34
smoser https://blueprints.launchpad.net/ubuntu/+spec/servercloud-u-cloud-init17:34
harlowjaUtopic ?17:34
harlowjawhats that17:34
smoser14.10 Utopic Unicorn17:35
harlowjaah17:35
smoserwent looking for mark's post on utopic17:35
smoserand saw:17:35
smoser http://www.markshuttleworth.com/archives/134217:35
harlowjanice17:35
smoserhttp://www.markshuttleworth.com/archives/136317:36
smoserthat one is utopic17:36
harlowjai should forward that on here, 17:36
smoseranywah...17:36
smoserfor things..17:36
smoserthe 2 things you might be interested in:17:36
smoser a.) python317:36
harlowjaack, that one again, lol17:36
harlowjapython3 hasn't gone away yet, lol17:37
smoser b.) more work on ci-tool17:37
smoser http://bazaar.launchpad.net/~smoser/cloud-init/ci-tool/view/head:/ci-tool17:37
smoseri'm not sure how i feel about ci-tool17:37
smoseroh. the other one... the query stuff.17:37
smoseryou revved that at some point. 17:37
smoserit'd be nice to have 2 json files in /run17:38
harlowjasmoser ya, good-ole-query stuff17:38
smoseri think thats the way i'd go now.17:38
smoserjust 2 json files17:38
smoserone with non-sensitive data17:38
smoserand one with sensitive data17:38
harlowjaright17:38
smoserand try to have a sane format for things common to most clouds17:38
harlowja:)17:39
smoserand allow the datasource to shove other stuff in its own place in the json17:39
harlowjaright17:39
harlowjaci-tool; would that be needed with a more extensive query tool (or maybe they merge?)17:39
harlowjainto super-ci-query-tool17:39
smoserci-tool 'seed' is the real function of ci-tool17:40
smoser'seed', 'reset', 'set-ds'17:40
harlowjaoh man, marks page is now showing me 'Error establishing a database connection'17:40
smoser:)17:40
harlowjasmoser sure, ya, the seed stuff is nice to have17:41
smoseroh.17:41
smoserthe other bug... 17:41
harlowja?17:41
smoserthe network interfaces stuff sucks17:41
harlowja:)17:41
harlowjayaaaa17:41
harlowjado u want to try to see how the netcf stuff works?17:42
harlowjai can try messing around there17:42
harlowjamaybe its 'ready' for primetime17:42
harlowja*although we'd probably need both, if netcf isn't avaiable on given distro17:43
harlowjaomg, what is my password doin in http://bazaar.launchpad.net/~smoser/cloud-init/ci-tool/view/head:/ci-tool#L5117:44
harlowjahaha17:44
smoserthats your password to? wow. coincidence.17:44
smosertoo17:44
harlowja:)17:45
harlowjasmoser in 14.10 unicorny no more 2.x python?17:45
smoseryeah, the netcf stuff. ive' come to needing that elsewhere too.17:45
smoserwe really need to get openstack networking sorted17:45
harlowja:-/17:45
smoserto the way that amazon does it.17:45
smoserso that you can hotplug a NIC into the system17:46
harlowjai believe with neutron u can do that17:46
smoserand then the system can hit the metadata service and get the interface config for that.17:46
harlowjaya17:46
smoserand that itnerface config needs to be in some format17:46
smoserand thus... i was asking you again about netcf17:46
harlowja:)17:47
harlowjaya, let me see if i can get mark mcclain in here to chat about the openstack neutron networking thing17:47
smosermaybe after running xml2json on it17:47
harlowjahow we can get from here to there17:47
harlowjasmoser ya, xml == evil17:47
harlowjalol17:47
smoserit really just isnt suitable for that reason17:48
harlowjasmoser exactly17:48
markmcclain1harlowja: here17:48
smoserhi markmcclain1 17:48
harlowjamarkmcclain1 hey, so we were just wondering a little bit about the future of hot-plugging, metadata in openstack, and how cloud-init will help out here17:48
harlowjathought u might have some knowledge (that i don't have)17:48
harlowja*hotplugging nics17:48
smoseryou can plug the nics in17:49
smoseri have done that.17:49
smoserand they do show up17:49
smoserall that works.17:49
harlowjai know what yahoo is doing here (with config drive, which won't work obviously here)17:49
smoserand then atually.... in the metadata servie i noticed one of them actually in a /etc/network/interfaces file after hotplugging.17:49
smoserconfig drive will die17:49
smoserand that will be ok17:49
harlowja:)17:49
harlowjaya, i'll have to fight the people here on that one to make it die (if possible)17:50
smoseri'm not too hung up on it.17:50
smosermostly people hated the metadata service because it didn't work.17:50
smoseror the networking never worked to get the instance to it.17:50
smoserbut now i think that those problems are less comon17:50
smoserbut anyway..17:50
smoseri hotplugged a nic17:50
harlowjak17:50
markmcclain1yeah so with hotplugging dhcp should work on that interface17:50
smoserand then an entry in /etcnetwork/interfaces styel file was in the interfaces location in the metadata service17:50
smoserbut it was out of order :)17:51
smoserie, the new nic was eth0 and the orig was eht117:51
smoserso its just silly.17:51
smoserthus need for some beter format for describing17:51
harlowjaand then enter xml netcf format :-P17:51
harlowja*xml (cough)17:52
smoseryeah, i most certaily would make major mistakes if i invented my own language.17:52
smoserbut really would not be interested in putting xml into a stack where it doesn't otherwise exist. 17:52
harlowja:)17:53
harlowjaxml is da best17:53
harlowjamarkmcclain1 has there been any thought on moving to a more agnostic format in the community for this17:54
harlowjanot saying it has to be https://fedorahosted.org/netcf/ (but something similar in json or other would be nice)17:54
markmcclain1I haven't heard too much yet about how to fix these issue17:54
harlowjak17:54
harlowjasmoser so the mission, if u choose to accept it, is to fix this issue, this message will self-destruct in 5 seconds17:55
harlowjaboom17:55
smoseryeah. i'd like to do it. it generally needs doing i think17:55
harlowjaagreed17:56
harlowjasmoser would this be a cloud-init thing at that point, or something else?17:57
harlowjasomething else that listens for hotplugs and then does stuff17:57
harlowjanetwork-cloud-init (or something)17:57
smoseri think i'd keep it in cloud-init. but try to make it separatable17:57
harlowjak17:57
smoserbasically, its udev hooks, code to get the data, and then code to act on it.17:58
harlowjaya17:58
harlowjaany idea how that works for freebsd ?17:58
harlowjaharmw activate, lol17:58
smoserand cloud-init would get the original datasource, and then the udev hooks would say "ok, i just got an interface, what cloud should i get data from!"17:58
smoserand cloud-init would have configured that.17:58
harlowjaright, makes sense17:59
harlowjasmoser do u want to do a joint writeup to the openstack-dev ML, i can draft somethign18:00
harlowjaand we can start this discussion there18:00
harlowjaand then see about how to make this really happen18:01
harlowjafix the brokeness that exists for this in to many places (nova has parts of this code, neturon seems like it has others)18:01
harlowjasmoser sound ok with u boss18:02
harlowjait just requires like cleanup in lots of places, which would be nice to just do18:05
harlowjalike nova has a metadata part, so does neutron, so this would have to be made in both of them?18:05
harlowjaand config-drive basically doesn't get this, idk18:05
harlowjaor does nova rewrite the config-drive when a hotplug occurs18:06
smoserharlowja, well, it could re-pouplate it for reboot i guess.18:30
smoserbut theres really no other way for the guest to "free" it.18:30
=== praneshp_ is now known as praneshp
=== harlowja is now known as harlowja_away
harmwharlowja_away: sup19:46
=== harlowja_away is now known as harlowja
harlowjaharmw nadda was just discussing how more dynamic network configuration can be done20:23
harmwyou know fbsd is still ancient in many ways, right :p20:24
harlowja:)20:27

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