=== kadams54-away is now known as kadams54 [00:11] rick_h_: crazy how hard it is to successfully post something on linkedin :) === kadams54 is now known as kadams54-away [00:28] jw4: :) === kadams54 is now known as kadams54-away [05:26] Hello All.. I am writing a charm for my product and trying to set/unset a config.yaml parameter from within a charm.Can anyone please tell me, how it can be done ?? [05:27] basically I want to set/unset the option from within a hook [05:29] I am using bash shell scripts for writing the charm/hook === urulama is now known as urulama__ === rogpeppe3 is now known as rogpeppe === urulama__ is now known as urulama === scuttlemonkey is now known as scuttle|afk [13:27] nevermam: you can't [13:27] nevermam: you can only get values, you can't set them [13:28] nevermam: you can get a value with `config-get ` inside a hook [14:09] * Zetas waves to lazyPower [14:25] Mornin Zetas [14:25] morning === kadams54 is now known as kadams54-away === l6unchpad is now known as sky-shiny === kadams54 is now known as kadams54-away [16:16] hi .. if i tried to run openstack using juju on aws, how can i link it to landscape ? [16:23] cory_fu: tvansteenburgh: quick question for you re: charmhelpers. I can use the config() object to store machine state as well correct? Eg: i have a slew of incoming relation data I need out of relation context, and i can just stuff those in the config object and have it persist thanks to the data-backend in config now right? [16:24] lazyPower: yes [16:24] ejat: I dont think OpenStack would run properly on AWS - as nova-compute would be running in a hypervisor. hypervisor in a hypervisor... [16:24] ejat: but in teh spirit of answering your question - so long as the units you register w/ landcape-client can reach your landscape-server, no crazy config / concerns need apply. [16:25] lazyPower: You should use charmhelpers.core.unitdata.kv().set / get instead [16:25] ok so unitdata is a different config store that wont bleed into config-get versioning? [16:25] > "versioned, transactional operation" - exactly what i was looking for [16:26] They are different implementations, and my opinion is that we should move entirely to unitdata [16:26] * lazyPower hattips @ cory_fu [16:26] I think the config tracking should be refactored to use unitdata as well [16:30] i managed to up the horizon [16:30] but connection timed out to login [16:33] lazyPower: i just want to test the openstack charms [16:33] testing purposes === kadams54-away is now known as kadams54 [16:42] anyone can help me ? === kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 === natefinch is now known as natefinch-afk [17:28] ejat: have you tried using devstack or are you tied to using aws? [17:28] devstack works pretty well for simple openstack charm testing [17:29] [Tue May 19 17:23:08.034535 2015] [:error] [pid 19918:tid 140668694456064] Login failed for user "Admin". [17:29] plus unless you make modifications to the charms deploying the openstack bundle to AWS will spin up a dozen fairly expensive users [17:29] s/users/servers [17:29] $ keystone role-list [17:29] +----------------------------------+----------+ [17:29] | id | name | [17:29] +----------------------------------+----------+ [17:29] | 150a57a6033d41978068798b25b99631 | Admin | [17:29] | 26b0725903ea49fbb1530d336a587e86 | Member | [17:29] | 9fe2ff9ee4384b1894a90878d3e92bab | _member_ | [17:29] +----------------------------------+----------+ [17:30] tried to update password [17:30] No user with a name or ID of 'Admin' exists. [17:33] hmm, im very new to openstack so im not sure what the issue would be. [17:33] you are able to login to the dashboard though right? [17:33] set the password with juju set keystone admin-password="mypass" ? [17:52] i manage to change the password... case sensitivity ... but i still cant login horizon dashboard ;( [17:52] still getting the same error ; [Tue May 19 17:50:54.594643 2015] [:error] [pid 19919:tid 140668694456064] Login failed for user "admin". === kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 [18:02] ejat: when you login to the juju-gui is the openstack-dashboard charm green and have all green relations? [18:02] (you did setup the relations right) [18:02] yups [18:02] all green [18:03] ive check the horizon setting [18:03] #OPENSTACK_KEYSTONE_URL = "http://%s:5000/v2.0" % OPENSTACK_HOST [18:03] is it correct ? or i need to put the full URL [18:03] hmm, thats strange [18:03] of the keystone [18:04] run this command: juju status openstack-dashboard [18:04] get the public IP and in your browser go to https://ipaddress/horizon [18:07] for me its https://10.0.3.44/horizon [18:08] http://paste.ubuntu.com/11229418/ [18:09] yea i just hit your dashboard heh [18:09] https://54.238.21.206/horizon [18:09] works great [18:10] might want to add a constraint to the AWS security group to only allow connections to 443/80 from your home IP [18:10] if this is gonna be something you want private [18:11] this is for testing purpose [18:11] horizon up [18:11] but i cant login the admin [18:11] what did you enter in the set password line? [18:12] default .. ive tried to changed a few time [18:12] including manually change in console just now [18:12] apache log still shows login failed [18:13] hmm, well from your main juju box you should be able to use the command juju set keystone admin-password="mypass" and then login with admin/mypass [18:16] is it because of the security group ? [18:17] If you deployed the bundle to aws without changing anything it should be fine. If you can access the horizon dashboard it wouldn't miraculously stop you from logging in [18:17] if there was a security group stopping communication between keystone and the dashboard that might happen but then your relation would be red probably [18:21] thats kinda the whole point of the relation thing, if it's green it should be fine. I haven't had your issue before so im not sure how to fix it [18:21] also i've not deployed openstack to aws fully [18:21] once i saw it spinning up a dozen servers i killed it lol [18:24] have you changed any of the default config values? [18:31] nopes [18:33] have you watched the debug log while logging in? It might have some helpful info [18:36] i'll brb [18:45] lazyPower: ping [18:46] wwitzel3: pong [18:46] lazyPower: got time for a quick hangout? [18:48] wwitzel3: In the middle of something - can you give me some time to wrap up what i'm working on? [18:48] lazyPower: absolutely [18:48] if its emergent i can bounce in [18:48] ack, thanks - i'll ping when i'm at a stopping point [19:26] back [19:26] any luck ej [19:26] oh he left [19:27] hope he figured it out === kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 === urulama is now known as urulama__ [20:32] openstack-charmers, charmers: Does there exist anyone who has successfully implemented vlan networking using a juju charm deployment> [20:32] ?? [20:33] openstack-charmers, charmers: Any chance at all?? [20:34] bdx: you mean like using openvswitch? [20:34] marcoceppi: totally [20:35] marcoceppi: [20:35] marcoceppi: It seems the charms support vlan networking to some degree......I haven't been able to figure it out.... [20:35] I have spent weeks trying to get it working with charm based deployment [20:35] bdx: the openstack-charmers would be able to answer this the best, but they're all at ODS this week [20:36] bdx: sorry to hear that! I'd recommend mailing the juju mailing list (juju@lists.ubuntu.com) if you haven't already about what you've tried and the issue you're seeing [20:37] marcoceppi: I feel like the charms support this use case, but it is treated like a corner case in the sense that there seems to be little to no support for vlan networking [20:37] marcoceppi: thanks man. will do [20:38] bdx: we are beefing up support for that, that much I know, but if there are any special measures the openstack-charmers can help. As I mentioned earlier they're all here in Vancouver at ODS so the email is the best way to start that conversation [20:43] marcoceppi: Thanks, I'll get started on an email to your guys list concerning this......what im getting at though is that vlan networking shouldn't be considered a special measure right? === kadams54 is now known as kadams54-away [20:50] bdx: no, and it won't in the future, I think it's just an issue with getting the charms updated which I'm sure we'll be doing over the next few months [20:54] marcoceppi: I see. Thanks for the insight on this [20:58] marcoceppi: should vlan functionallity be removed from the charms seeing as they don't support it.....this is very misleading and can be very frustrating from an opperators point of view. [20:58] bdx: well vlan does work from what I recall [20:58] *sp: operator === kadams54-away is now known as kadams54 [21:02] marcoceppi: Yea.... [21:02] lol [21:02] marcoceppi: vlans work when I handroll a stack [21:05] marcoceppi: I have preformed introspection and post deploy configuration on a juju deployed stack and am just hitting my head on how this is expected to work using juju.....some documentation on networking configs using juju would be a huge plus++ tahts all [21:06] marcoceppi: thanks for your insight none the less [21:06] bdx: I get your frustration, sorry it's not quite there yet. I'll make sure someone from the OpenStack Charmers team follows up with your email soon! [21:07] marcoceppi: Thanks again === kadams54 is now known as kadams54-away === noodles775 is now known as michaeln === michaeln is now known as mnelson === mnelson is now known as noodles775 [23:16] lazyPower, marcoceppi: are either of you willing to help me on my Friday afternoon to look at imporoving the python-django charm? === noodles775 is now known as miken