/srv/irclogs.ubuntu.com/2013/09/11/#juju.txt

wallyworldthen you copy the generated files up the the public bucket00:00
wallyworldhatch: i just tried juju --version and it works for me, what version of juju do you think you have installed?00:00
lamonterror: flag provided but not defined: --version00:00
lamont1.12.0-0ubuntu1~ubuntu12.04.1~juju100:00
hatchwallyworld: I JUST did it this morning, following the 'install guide'00:00
lamontanyway, afk for a couple of hours00:00
hatchtrying to see what the typical user would see00:00
hatchlamont: thanks for confirming :)00:01
wallyworldlamont: ok, ping us in #juju-dev if you want any more input00:01
wallyworldhatch: i'm running from source, but "juju --version" worked  for me00:01
sarnoldhatch: the python version and the go version have different --version vs version behavior. that's almost a decent way to tell which one you have already.... :)00:02
sarnoldwallyworld: (oh, has that been fixed?)00:02
wallyworldi didn't realise there was a difference00:02
wallyworldi've only ever run go juju00:02
hatchoh that's odd :)00:02
sarnoldah :))00:02
wallyworldian@wallyworld:~$ juju --version00:03
wallyworld1.15.0-raring-amd6400:03
hatchsarnold: thanks for clearing that up00:03
sarnoldwallyworld: neat! yay :)00:03
hatch1.12.0-precise-amd6400:03
hatchhere00:03
hatchon stable00:03
wallyworldah ok. there's been lots of fixes post 1.12 i think00:03
wallyworldwe are looking to release 1.14 next week00:03
hatchwell then....someone should update stable :P00:04
wallyworldfor now, there's a 1.13.300:04
* hatch stokes fire00:04
wallyworldhatch: agree, i think that will happen00:04
wallyworldeach even number release is considered stable00:04
hatchbut really though thanks - it looks like the go version doesn't handle the -- on 1.12.000:04
wallyworldappears so, sorry00:04
hatchbut if it works fine on your version then I won't file a bug00:04
wallyworldok00:05
hatchthis happened when running through the Local Configuration setup docs00:06
hatchit says `juju generate-config --show` which failed00:06
hatchjust fyi00:06
wallyworldhmmm. seems the docs may need some love then00:07
hatchI'm guessing that it was just done with a more recent version00:08
hatchunless even yours doesn't do --show :)00:08
marcoceppi_lamont: still having issues with private cloud?00:45
wallyworldmarcoceppi_: i think he's afk for a bit, but i got his public bucket url sorted, now he needs to generate image metadata01:14
marcoceppi_wallyworld: cool01:15
AskUbuntuJuju e MAAS get error in apt | http://askubuntu.com/q/34406401:41
=== medberry is now known as med_
=== freeflying is now known as freeflying_away
=== freeflying_away is now known as freeflying
=== CyberJacob|Away is now known as CyberJacob
kennQuestion about the bridge node. Due to budget constraints I can only run a single instance in the cloud. Are there any reasons why I wouldn't want to deploy my services to that first machine 0, or anything I should be aware of when doing that? I've done it locally so it's possible to do.06:39
=== rogpeppe1 is now known as rogpeppe
AskUbuntuCan I deploy juju on Eucalyptus | http://askubuntu.com/q/34413707:37
fwereade_jcastro, marcoceppi_: if either of you are around, I'd appreciate advice re resolving doc conflicts caused (at least partly) by header/footer changes08:08
fwereade_jcastro, marcoceppi_: eg "take your tree, copy in $files from trunk, run tools/build.py, commit, merge trunk in"08:09
=== defunctzombie is now known as defunctzombie_zz
=== freeflying is now known as freeflying_away
=== freeflying_away is now known as freeflying
AskUbuntuhelp: bootstrap error | http://askubuntu.com/q/34416809:35
=== freeflying is now known as freeflying_away
=== freeflying_away is now known as freeflying
=== kentb-out is now known as kentb
jcastrofwereade_: evilnickveitch is your guy there13:17
jcastrofwereade_: I am pretty sure he strips all that out and regens the footer/header anyway13:18
fwereade_jcastro, thanks, I chatted to him13:18
jcastromarcoceppi_: also ... review queu!14:09
marcoceppi_jcastro: yup :\14:09
=== freeflying is now known as freeflying_away
evilnickveitchjcastro, fwereade_ I just posted to the list about the new, super-easy way of creating pages I just sorted out this morning...15:02
jcastrok15:03
fwereade_evilnickveitch, cool, thanks15:13
bloodearnestheya all - am having some problems with juju-deployer (0.2.3) hanging after deploying all services, but before adding relations15:20
bloodearnestCtrl-C'ing gives me a tb: https://pastebin.canonical.com/97357/15:21
bloodearnestsame tb every time15:21
bloodearnesthad this happen on 2 different raring machines, on both lxc and openstack (canonistack) envs15:23
bloodearnestany pointers to fix?15:23
jcastrohttp://pad.ubuntu.com/7mf2jvKXNa15:31
jcastroT minus 30 minutes until the Charm Call!15:31
jcastro10 minutes until the juju charm call!15:51
=== BradCrittenden is now known as bac
mattywjcastro, is there a link to just watch the hangout?16:09
marcoceppi_mattyw: ubuntu-on-air.com16:10
marcoceppi_mattyw: http://ubuntuonair.com/16:10
mattywmarcoceppi_, of course, thanks16:11
=== marcoceppi_ is now known as marcoceppi
Chorhi there16:48
kurt_Can you guys tell me if its correct that a deployment fails when there is an existing configuration file for a charm?  I'm seeing this when having destroyed keystone, then trying to redeploy it.  Maybe an adjunct questions is when a service such as keystone is destroyed, should it clean up it's configuration files cleanly?17:15
marcoceppikurt_: if you destroy a service, then try to deploy it again, I believe you get an error about service already deployed17:24
marcoceppikurt_: is that the error you're getting?17:24
kurt_marcoceppi: no, the problem, specifically with keystone was that the /etc/keystone/keystone.conf is left behind17:25
kentbdoes anyone have a *fairly current* and recommended set of steps for deploying openstack charms with maas & juju, especially with quantum-gateway.  For whatever reason, with quantum-gateway in the mix, keystone authentication with quantum gets hosed. every. freaking. time.17:26
marcoceppikurt_: that's a different issue17:26
sarnoldearly charms might expect the unit to be destroyed when the service is unconfigured / terminated / etc. I'm not surprised it didn't do a great job of cleaning up17:26
kurt_kentb: I've been working on this for some time.  I hope to have something out in the near future17:27
kurt_there are several guides out there, but you have to be patient and figure it out17:28
kentbkurt_: yeah, that's the part that's about burned up (patience).  I'll also take whatever you have in the meantime. The quantum-gateway piece is the one that I just can't seem to crack.17:29
kurt_marcoceppi: this appears to be some conflict in removing 2013.1.2-0ubuntu2~cloud0 and it's need for /etc/keystone/keystone.conf17:30
kurt_kentb: yes, I've ran in to this too.  you have to plan your deployment topology very carefully17:30
kurt_kentb: have you seen jamespage's excellent guide? https://wiki.ubuntu.com/ServerTeam/OpenStackHA17:31
=== CyberJacob is now known as CyberJacob|Away
kentbkurt_: yep. I've worked off of that many times.  I don't have enough nodes for the HA part, so, I've tried to make do with 6 physical machines, each with at least two nics.17:33
kurt_kentb: I'm doing mine completely on VMs17:34
kurt_kentb: and you are running in to one of the challenges I am facing as well.  I'm consolidating a lot of services to fewer nodes.17:35
kentbkurt_: yeah, I'm wondering if putting too much on one machine might be hurting me17:35
kentb(with juju-core)17:36
kurt_these guys test with a small amount of nodes, so they have managed to figure it out17:36
kurt_if there was one thing I wish were out there (hint hint jcastro)17:36
kurt_it would be a minimal install blueprint17:36
kurt_I hope to figure that out on my own with what knowledge I have17:37
kentbme too!17:37
kurt_and eventually I am going to create a guide with all of this info - but I'm out in the wild right now17:37
kentbjoin the club :)  I feel like I'm really close.17:38
kurt_keep checking in to this channel.  Since we are on the same track, we should share ideas17:38
kentbwill do!17:39
kentband I agree17:39
kurt_these guys do appreciate the bugs you find, so keep the info flowing17:39
kentbdefinitely!17:39
jcastrokurt_: you mean for openstack?17:40
kurt_yes sir17:40
jcastroyeah17:40
kentbyep17:40
jcastroadam_g: I'm supposed to talk to you about an openstack bundle actually17:40
kentbquantum-gateway is kicking my butt17:40
kurt_that is my numero uno goal right now17:40
kurt_to get a working openstack deployment on VMs with the minimum install17:41
kurt_but not the "virtual" method17:41
kurt_I would love to have a "scalable" blueprint working with maas, juju, juju-gui and openstack17:42
marcoceppikurt_: There are a few deployer configs out there for that17:42
kurt_marcoceppi: yup, but I've not been successful yet in making one work17:43
kurt_I've gotten close, but no cigar17:43
kentbsame here17:43
=== CyberJacob|Away is now known as CyberJacob
jcastroyeah, so arosales told me this morning that adam_g's been working on a working bundle17:43
marcoceppikurt_: kentb thanks for sticking with it. We're working on making this a very strong story in the near future17:43
kurt_marcoceppi: I know you guys are.  I believe you feel this is an important and compelling user case and story17:44
kurt_that's why I've been working hard on this17:44
kentbmarcoceppi: my pleasure. I'm learning a *ton*  I'm also working with a big OEM on a whitepaper on how to do this on their hardware.17:44
kentband I drew the openstack straw :)17:45
kurt_marcoceppi: can you share those deployer configs you spoke of to see if there is anything I don't know about?17:47
marcoceppiadam_g:  where's be most recent version of the openstack deployers? they still in the deployer repo?17:48
* marcoceppi knows you're working with jcastro on this as well17:48
jcastroI only found out today17:48
jcastrobut I am keen on getting my hands on whatever he has, heh17:48
* marcoceppi thinks we all are ;)17:48
adam_gmarcoceppi, in lp:openstack-ubuntu-testing, juju-deployer   -c etc/deployer/deployments.cfg  -l17:48
kurt_are these similar to devstack type things?17:49
adam_gthose are all sort of specific to our lab, using custom charm branches and some lab-specific config17:49
adam_ggimme a minute and ill put together a vanilla one for a simple deployment17:49
kurt_adam_g: nice one, thanks mate17:49
kentbwoohoo17:50
marcoceppikurt_: so juju-deployer, if you're not aware, is a means to standup complicated juju environments17:50
jcastroadam_g: hey so, I am thinking make a simple one, post it on the list, and ask for feedback17:50
marcoceppiit's just a yaml file that can be used with juju-deployer to deploy, configure, and relate services17:50
adam_gjcastro, yeah, i need to put up a wiki that documents this. i have a WI for it and hope to get to it soon.17:50
kurt_marcoceppi: I saw that information for the first time at the bottom of jamespage's manifesto17:50
kurt_marcoceppi: is the juju-deployer discussed at length anywhere?17:52
jcastrohazmat: maybe it's time to post on the list about deployer as well17:54
kurt_I would love to read about what it does and how it does it17:54
adam_gjcastro, http://paste.ubuntu.com/6093510/17:54
adam_gjcastro, this is a vanilla openstack + ceph. ceph node is single node (with no redundnacy), swift is single storage node as well17:55
jcastrois this that deployments.cfg or is this a new thing?17:55
kurt_adam_g: how many nodes is this?  is it single-node?17:56
adam_gkurt_, every service in its own machine17:56
jcastrook so you could add-unit to this?17:56
kurt_how about the quantum-networking - is there a local.yaml or something it is referencing?17:57
jcastro2013-09-11 13:57:55 Deployment name must be specified. available: openstack-services', 'precise-grizzly', 'raring-grizzly')17:58
jcastrowhich one do I use?17:58
kurt_I think both kentb and myself have managed to get pretty far, but have not been able to get a complete working set up because of the networking17:58
kentbyeah, that backfires almost every time...there's something screwy with keystone in the end product that I'm not sure what broke17:58
jcastroadam_g: where do you want the wiki page to be? I can start documenting this17:59
kurt_kentb: I don't think keystone is the problem17:59
kurt_at least in my set ups it wasn't17:59
kurt_it was the ability to assign an IP and spin up vm's from horizon18:00
kentbkurt_: really?  What were you hitting?  For me, I was always getting a 401 error if I tried to do anything with quantum.18:00
kurt_which was probably due to my networking being incorrect18:00
adam_gjcastro, im not sure. somewhere near the current openstack HA wiki page? dont have URL handy18:00
jcastrojujuclient.EnvError: <Env Error - Details:18:01
jcastro {   u'Error': u'invalid entity name or password',18:01
jcastro    u'ErrorCode': u'unauthorized access',18:01
adam_gjcastro, https://help.ubuntu.com/community/UbuntuCloudInfrastructure18:01
jcastroI get this kind of stuff when I try to run deployer on that pastebin'ed bundle18:01
jcastrohttps://help.ubuntu.com/community/UbuntuCloudInfrastructure/JujuBundle for now18:02
jcastroadam_g: ok, so now, next step is what to do wrt. openstack-service, precise-grizzly, or raring-grizzly18:04
jcastroI have an environment up and running18:05
jcastrojuju-deployer -c openstack.cfg  -elocal precise-grizzly18:06
jcastrothis seems right? Looks like it's working18:06
kurt_jcastro: are you able to access horizon and spin up VMs?18:06
jcastroit's firing up right now18:06
jcastrogimme like 5 minutes18:06
kurt_kk18:06
jcastrojuju-deployer -v -c openstack.cfg  -elocal precise-grizzly18:07
adam_gjcastro, good luck using local provider :)18:07
jcastroadam_g: I just wanted to get the syntax for the command down, etc.18:08
adam_gah, right18:08
adam_gjcastro, openstack-services is the base deployment, precise-grizzly just inherits and sets series and the config to install grizzly18:08
jcastroadam_g: can you add some info here? https://help.ubuntu.com/community/UbuntuCloudInfrastructure/JujuBundle18:11
adam_gjcastro,  on a call atm. i will, cant promise its going to happen this week tho18:11
jcastrok18:11
jcastrodo you think this will fire up on like hpcloud or something?18:11
jcastroI'd like to see it work at least once!18:12
adam_gnot sure18:12
jcastrobut it works on MAAS?18:13
kurt_adam_g: if you could include some info around how the networking is handled (i.e. IP/CIDRs, interfaces, public ranges, etc) , I would be grateful18:13
kurt_jcastro: did VM spin up?18:17
jcastroa bunch of containers spun up18:17
jcastrofails on swift-storage-z118:17
kurt_anything interesting in debug-log that's an easy fix?18:18
jcastrohttp://imgur.com/Bh114KN18:19
jcastrothis is the 2nd time I'm trying it, I'll check debug log18:19
jcastrofailing on the install hook18:19
kurt_it looks like most of them are stuck deploying18:21
jcastroyeah, a bunch of them are turning green now18:21
kurt_nice18:21
kurt_can you pastebin your install hook error for swift?18:22
jcastrook so deployer showed an error18:22
jcastrobut the unit came up just fine18:23
jcastroand I think I found a bug in nova-compute though18:23
jcastroadam_g: on the nova-compute charm: http://pastebin.ubuntu.com/6093626/18:23
jcastroshould I report that as a bug?18:24
kentbah! that might be what's killing me too...my nova-compute instance was DOA and libvirt was all messed up as one of the symptoms18:24
adam_gjcastro, full log?  i believe thats one of the many issues you'll hit doing this in containers18:24
jcastrohttp://paste.ubuntu.com/6093637/18:26
kurt_adam_g: wasn't log filling issue fixed in 1.13?18:35
kurt_(juju 1.13)18:35
kentbkurt_: yep...hasn't come back for me since updating18:35
kentbbug killed my bootstrap node within a few hours18:36
kurt_yes, mine too in 1.1218:36
=== defunctzombie_zz is now known as defunctzombie
kentbok. so if an instance is stuck in 'dying' state is there a good way to nuke it?  I can't terminate the machine b/c we're indefinitely stuck there. Please tell me I don't have to destroy-environment and start over (using juju-core 1.13.3-1-1737).20:06
kentbthe agent-state is 'error' with a hook-failure during config-changed20:06
kentbnm I ran juju resolved ceph and then that allowed me to kill it20:13
thumperjcastro: ping20:25
jcastroyo!20:26
thumperjcastro: got a few minutes for a hangout?20:26
jcastroyeah let me finish something20:27
jcastro~10 min?20:27
thumpersure20:27
kurt_kentb: juju resolved <service>20:44
kurt_kentb:  juju resolved <service>20:45
kurt_I just went over this with marcoceppi yesterday20:45
marcoceppikurt_: yes, we need to update the documentation for this20:46
kurt_Can anyone tell me if there is default username/password for console only access for nodes?  I don't have ssh access20:46
marcoceppikurt_: everything is done via ssh20:47
kurt_I'm hosed them20:47
marcoceppikurt_: you can try ubuntu with the password ubuntu20:47
kurt_then20:47
kurt_that doesn't work20:47
marcoceppithen I don't think so20:47
marcoceppiWe try to avoid default passwords and users, because that's a vulnerability20:48
kurt_macroceppi: if I am trying to add an interface after the fact to node?  I keep messing up my routing when I do it20:48
kurt_sorry, that wasn't clear20:48
kurt_is there an easy way to add an interface to a node once it's been deployed?20:48
kurt_I appear to keep screwing up my routing20:49
kurt_this is on maas btw20:49
kurt_not that that matters20:49
kentbkurt_: yep, that unclogged it. thanks!20:52
kurt_kentb: good stuff20:53
jcastrohey thumper20:55
marcoceppikurt_: no, you can't add interfaces after the fact unless you use upgrade-charm20:56
kurt_upgrade-charm?20:56
marcoceppikurt_: yes. So if you're developing a charm locally, and you deploy using --repository and local:, and you later ADD a relation/interface to the metadata.yaml, you can run `juju upgrade-charm --repository ... <service>` to upgrade the charm and register the new relation/interface20:57
marcoceppikurt_: chaning interfaces/relations or removing them can be quite dangerous if you don't first remove all relations20:58
* marcoceppi is working on the upgrade-charm docs atm20:59
kurt_so, do I have to entertain the idea of completely statically assigning my maas installation to make openstack work as in jamepage's doc?20:59
kurt_I am sure I could avoid using the vip parameter, but does that only apply to HA situations?  Or is it a real virtual IP that can be assigned on top of juju's administrative IP?21:02
kurt_Looks like this is going to be a problem too:  https://bugs.launchpad.net/juju/+bug/118812621:11
_mup_Bug #1188126: Juju unable to interact consistently with an openstack deployment where tenant has multiple networks configured <canonistack> <openstack> <serverstack> <juju:New> <juju-core:Triaged> <https://launchpad.net/bugs/1188126>21:11
=== CyberJacob is now known as CyberJacob|Away
=== CyberJacob|Away is now known as CyberJacob
=== kentb is now known as kentb-out
=== freeflying_away is now known as freeflying
=== CyberJacob is now known as CyberJacob|Away
=== defunctzombie is now known as defunctzombie_zz
=== defunctzombie_zz is now known as defunctzombie
=== defunctzombie is now known as defunctzombie_zz
freeflyinghow many constraints from juju python has been implemented in juju-core?23:34

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