dubcanada | Can you deploy more then one thing per a server? | 00:27 |
---|---|---|
sarnold | dubcanada: yes; you can either use subordinate charms if the things are logically related somehow or you can use lxc containers if they're not | 00:40 |
dubcanada | How do you use lxc containers? | 00:40 |
sarnold | dubcanada: that'd be something --to foo:1 or --to bar:2 | 00:40 |
dubcanada | Does the GUI support that stuff? | 00:41 |
dubcanada | Or is that only cl? | 00:41 |
sarnold | dubcanada: https://juju.ubuntu.com/docs/charms-deploying.html#deploying-to-specific-machines-and-containers | 00:41 |
sarnold | dubcanada: ah, no idea there, sorry | 00:41 |
sarnold | dubcanada: ah, looks like I had the syntax all wrong, too :) | 00:41 |
=== CyberJacob|Away is now known as CyberJacob | ||
=== CyberJacob is now known as CyberJacob|Away | ||
=== uru_ is now known as urulama | ||
sante | Hi, I'm trying to bootstrap an openstack environment but I'm stuck at this error http://pastebin.com/ER9i8Qt4 . I did setup the new tools-metadata-url and image-metadata-url but the bootstrap process seems to ignore them. Can someone help me understandig thie issue? | 08:27 |
=== Guest30538 is now known as wallyworld | ||
diegows | hi | 12:14 |
schegi | hey guys a little problem with my new maas setup. I configured my maas master with 4 different networks all managed dhcp and dns. but if i now bootstrap a juju environement, the maas master is no longer able to connect to the bootstrapped node cause it chooses to use the wrong network.. | 12:28 |
schegi | if i reduce my networks to only the one which is brought up during installation on nodes everything works fine but not if i have all networks on and managed | 12:29 |
schegi | bootstrapping starts with Attempting to connect to controller.wcloud.uni-koblenz.de:22 Attempting to connect to 192.168.25.14:22 Attempting to connect to 10.10.2.13:22 Attempting to connect to 10.10.2.12:22 | 12:30 |
schegi | which is correct but later it fails with ERROR waited for 33m20s without being able to connect: ssh: connect to host 10.10.2.12 port 22: No route to host, because the host will only bring up the 192.168.25.0 network during installtion. how can i force maas to use one particular network?? | 12:31 |
=== jcw4 is now known as jcw4|on-the-road | ||
schegi__ | can someone helpt with virsh power settings for maas?? already asked in the maas channel noone able toi help there | 16:37 |
roadmr | schegi__: I think #maas would be the right place, if they were unable to help maybe you can post in askubuntu.com? | 16:44 |
=== Ursinha is now known as Ursinha-afk | ||
=== Ursinha-afk is now known as Ursinha | ||
=== CyberJacob|Away is now known as CyberJacob | ||
=== Ursinha is now known as Ursinha-afk | ||
=== Ursinha-afk is now known as Ursinha | ||
lukestuts | hello jujuers | 20:26 |
lukestuts | i have just started jujuing | 20:27 |
lukestuts | i am confused by the relationship between the ubuntu charm store and the charms on github | 20:28 |
lukestuts | how do the github charms differ from the charm store charms? | 20:28 |
ctlaugh | I'm trying to deploy nova-compute using juju to an ARM64 machine running trusty and am trying to figure out how the following line gets added the /etc/apt/sources.list.d/cloud-archive.list: deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/icehouse main | 20:41 |
lukestuts | hello ctlaugh | 20:56 |
ctlaugh | lukestuts: hi | 20:56 |
lukestuts | what do you mean by "how it gets added"? | 20:57 |
ctlaugh | Somehow, in the process of adding the machine using "juju add-machine ssh:ip-address", or when I deployed nova-compute, that file got created. | 20:58 |
ctlaugh | I am 87% sure it was not there before that | 20:58 |
ctlaugh | I was curious if anyone knew if that was part of the juju bootstrapping process, or part of the charm's installation steps | 20:59 |
lukestuts | it's not on my openstack vm | 20:59 |
lukestuts | i'm playing with rails on trusty | 20:59 |
ctlaugh | hmm | 21:00 |
lukestuts | which charm were you using? | 21:00 |
lukestuts | gtg | 21:01 |
ctlaugh | nova-compute from trusty-icehouse | 21:02 |
cl3044 | to shut down juju / juju-gui nodes and reboot it, i thought it was necessary just to hit "stop node" and then "start node", but I'm having the issue of MAAS wiping out the node, PXE booting, and reinstalling a blank node. | 22:58 |
cl3044 | i must be doing something totally wrong. | 22:58 |
sarnold | cl3044: you might just want to juju ssh to issue shutdown commands instead | 22:59 |
jose | or do destroy-environment or destroy-service with terminate-machine | 22:59 |
cl3044 | ok, that's definitely helpful | 23:00 |
cl3044 | no powering down maas nodes then? | 23:00 |
cl3044 | (at least directly) | 23:01 |
sarnold | cl3044: good point. there may be some interface in MAAS for rebooting instead... | 23:01 |
cl3044 | if i deploy openstack with juju and tear it down with destroy-environment/terminate-, etc.... how do i start it back up, then? seems like it would not be persisent. | 23:13 |
mwhudson | if i do juju add-machine lxc:0 is there any easy way to identify the lxc that i just added? | 23:39 |
mwhudson | i guess i can do before/after on juju status but... | 23:39 |
=== CyberJacob is now known as CyberJacob|Away |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!