[14:32] <morty> any way to deploy browbeat with juju?
[14:52] <rick_h> morty: hmm, I don't see any charm for that. Might be worth an email to the juju list and see if anyone's working on one that they've not made public yet.
[14:55] <morty> alright, thanks rick_h :)
[15:25] <TheAbsentOne> What is actually the best way to create a file with the reactive framework? Is there an example somewhere that shows what the cleanist approach is?
[15:34] <stokachu> TheAbsentOne, like a charm that uses reactive?
[15:37] <TheAbsentOne> stokachu: yes! I want to create (what should be) a very simple charm. Let's say it runs apache or nginx, installs php and I want to create a phpfile with only phpinfo() function. What would be the best approach inside the python charm code?
[15:39] <TheAbsentOne> And the same for copying pre-existing files (no templates, just files ready to be copied)
[17:41] <stokachu> TheAbsentOne, i think resources is what you want for the files to be copied
[17:55] <stokachu> TheAbsentOne, https://github.com/battlemidget/juju-charm-ghost thats my example one
[17:55] <stokachu> uses resources and reactive
[18:22] <TheAbsentOne> aha nice thanks for the help stokachu
[18:28] <fallenour> hey everyone. Im having issues with my browser consoles loading in openstack. I looked into: juju config openstack-dashboard, but I dont see a setting for SPICE. I think I need to change a setting in there from AUTO to SPICE in order to fix the problem as per this: https://ask.openstack.org/en/question/26123/horizon-sends-wrong-rest-request-when-spice-is-enabled/ but im not sure. I think the issue may be my console is trying to load 
[18:28] <fallenour> instead of the DNS name as well. I did notice that the browser keeps trying to load a 10.X address instead of the DNS name. Your thoughts?
[18:29] <fallenour> address bar: 10.0.0.16:6082/spice_auto.html?token=d5ff7eaa-d411-4595-b315-e8eba399fdf6&title=test2(73f3e8f3-b5f6-4f8c-93ac-9bc78bfa35a8)
[18:37] <fallenour> Ok so I think I have a better handle on the question, my problem is the direct opposite of this: https://ask.openstack.org/en/question/58938/dashboard-problem-with-url-of-vnc-console/ My client is Spice
[19:14] <kwmonroe> admcleod_ or beisner, got any suggestions for fallenour ^^  i dunno what config the openstack dashboard supports
[19:16] <fallenour> kwmonroe: from what I can tell, based on juju config openstack-dashboard, quite a lot. Do you think it might be easier to convert everything to a DNS based process isntead of an IP based one. Even if I did, would it stop the placement of IP addresses for the console URL?
[19:17] <beisner> hi fallenour kwmonroe - the vnc/spice console settings are a nova config, set on the nova-cloud-controller charm.  ref: https://github.com/openstack/charm-nova-cloud-controller/blob/master/config.yaml
[19:28] <fallenour> beisner: So i checked at console access protocol, and it shows spice, so spice is configured correctly in that regard, what would make it change from a DNS name to an internal IP address? and how would I change that?
[19:29] <fallenour> also, for reference: juju config nova-cloud-controller console-access-protocol is the command, with the respective setting for those who dont know
[19:32] <beisner> fallenour: are you able to access the ip address from your local machine?  mine generally gives an ip address in the url.
[19:32] <beisner> it is the unit ip address of nova-cloud-controller that terminates the console addresses
[19:36] <fallenour> beisner: No, the initial address is a wan routable DNS address. It then converts from a DNS address to the IP internal, which screws the pooch. Anythoughts?
[19:38] <beisner> fallenour: what ip does the initial dns address resolve to?  i think the assumption for console access is that you can also reach the nova-cloud-controller address.
[19:39] <beisner> (when using the default console proxy == local)
[19:40] <fallenour> horizon.eduarmor.com/horizon -> http://horizon.eduarmor.com/horizon/project/instances/73f3e8f3-b5f6-4f8c-93ac-9bc78bfa35a8/ -> http://10.0.0.16:6082/spice_auto.html?token=578c2277-0899-46a6-b077-eab257d39bee&title=test2(73f3e8f3-b5f6-4f8c-93ac-9bc78bfa35a8)
[19:40] <fallenour> The nova cloud controller IP is: 10.0.0.16
[19:40] <fallenour> so its using the nova-cloud-controller to connect to the session.
[19:46] <fallenour> oops. beisner sorry*
[19:47] <fallenour> beisner: meant to @ you earlier with the previous. So yea, what are your thoughts? Do I need to change here? Im not sure exactly how to fix this issue whiel also keepign access wan routable
[19:47] <beisner> fallenour: Yes, exactly.  You have to be able to reach that address, whether resolved via DNS, or directly called by IP, when using 'local' for the console proxy.
[19:48] <fallenour> beisner: what is the easiest way to eliminate this issue? Without making major changes more sepcifically/hopefully?
[19:48] <beisner> fallenour: I take it that address isn't accessible/routable from the machine you're trying to use for a console client?
[19:49] <fallenour> beisner: I can make it WAN accessible via a loadbalancer if necessary. I guess my question with that is what setting(s) would I need to change to implement that?
[19:49] <fallenour> I take it I would need to: HAproxy -> Nova-Cloud-Controller
[19:50] <fallenour> Id need to set a route any rule for HAproxy because I dont knwo what port itll send to, and id need to give the nova-cloud-controller a DNS name
[19:51] <fallenour> beisner: that should get the traffic into the network, but my question is, what, if anything, will that break on openstack? Also, just because I pass the traffic, does that stop it from trying to route to the IP via console? how do I fix that issue?
[19:52] <fallenour> beisner: how do I make it go from 10.0.0.16:xxxx to novacloudcontroller001:xxxx via juju config nova-cloud-controller / juju config openstack-dashboard ?
[19:52] <beisner> i'm not aware of a config to achieve that, fallenour
[19:53] <fallenour> beisner: so theres no way to have it try to terminate at the novacloud controller via its dns name instead of its IP address?
[19:54] <beisner> fallenour: all of the use cases i've been in, and all of the docs for vanilla openstack upstream reference nova_ip:port as the method of reference.
[19:54] <fallenour> beisner: I did find this: https://ask.openstack.org/en/question/58938/dashboard-problem-with-url-of-vnc-console/ which is the complete opposite of what we are trying to do
[19:55] <fallenour> beisner: so then how do people normally access the consoles?
[19:56] <fallenour> beisner: sorry, via WAN. Becuase unless you were on the network, it wouldnt be possible to route to an internal addresss. If nothing else, you dhave to give a nova-cloud-controller a wan ip address to make it work?
[19:56] <beisner> https://docs.openstack.org/nova/latest/admin/remote-console-access.html#spice-console
[19:57] <beisner> specifically: "Replace IP_ADDRESS with the management interface IP address of the controller or the VIP."  translate:  the ip address of the nova-cloud-controller unit.
[19:57] <beisner> (or if HA, the VIP of nova-cloud-controller)
[19:58] <fallenour> beisner: yea, I saw that. Hmm...do you think if we just "put" a dns name there, that itd work?
[19:58] <beisner> fallenour: if you want to access this from the outside of the next hop on your network, that would likely be configuration of routers outside openstack.  ie. port forwarding, nat mapping, etc., on whatever is separating the networks.
[19:58] <fallenour> beisner: I mean, I knwo the documents SAY it requires an IP, but has anyone actually tried via a DNS name?
[19:58] <beisner> no, i think if you can't get to the IP address directly from the client machine right now, no DNS tricks on the planet will solve that.
[19:59] <beisner> ie. if the L3 address is not routable, it's not routable, and you'd have to address that.
[19:59] <fallenour> beisner: what about the second idea? make it WAN routable
[19:59] <beisner> i doubt you want your nova-cloud-controller ip address on a wan
[20:00] <fallenour> beisner: yea that was my thought to. i see that ending...badly
[20:00] <beisner> haha right!?
[20:00] <fallenour> beisner: it was make one hell of a news story though XD
[20:00] <beisner> apologies, have to step away for an appt
[20:00] <fallenour> beisner: its alright. Ill see if I can figure out a way to make an internal IP internally routable without know what port itll be on
[20:00] <beisner> no pressure ;-)