| === arosales_ is now known as arosales | ||
| === kadams54 is now known as kadams54-away | ||
| === kadams54-away is now known as kadams54 | ||
| === kadams54 is now known as kadams54-away | ||
| === kadams54-away is now known as kadams54 | ||
| === kadams54 is now known as kadams54-away | ||
| === urulama_ is now known as urulama_otp | ||
| === kadams54 is now known as kadams54-away | ||
| === kadams54-away is now known as kadams54 | ||
| lazyPower | Greetings gui team o/ quick ? - just sounding out some ideas out loud and need to confirm some assumptions. | 14:02 |
|---|---|---|
| lazyPower | when the gui has staged a charm, as in "commit" but leave it unassigned - the charm code is still pulled and placed on teh stateserver for deployment when youd ecide to commit a node to it yes? or is this just a placeholder that the gui is offering until you decide to commit to adding the first unit? | 14:02 |
| rick_h_ | lazyPower: so if you commit without placing it, the charm is pulled so that the service is added I believe? a service with 0 units? | 14:04 |
| * rick_h_ is trying to recall | 14:05 | |
| lazyPower | rick_h_: correct | 14:05 |
| lazyPower | like if you hit up the gui demo over on jujucharms.com and deploy something, it defaults to being in a transient state | 14:05 |
| rick_h_ | right | 14:05 |
| rick_h_ | I mean if you can juju status the cli and match it up should tell you tbh | 14:05 |
| lazyPower | which leads me to beleive, there's a way for me to reproduce that scenario with the CLI - having an unplaced charm that i can then say "yo dawg, add-unit --to #" later. | 14:06 |
| rick_h_ | yep, unit=0 or something? | 14:06 |
| lazyPower | ah i haven't tried that, i was going to lead into "can i do this in the CLI or is this something you gave me being the super awesome gui ppl" | 14:06 |
| rick_h_ | num_units=0 | 14:06 |
| rick_h_ | whatever the field is | 14:06 |
| lazyPower | hah, awesome | 14:06 |
| lazyPower | allright, ballin. I'm going to derp around with this and come up with something neat | 14:06 |
| * lazyPower rolls the dice | 14:06 | |
| jrwren | ^^ always scary when lazyPower says this. | 14:09 |
| lazyPower | i'm just scary in general jrwren. this much is obvious ;) | 14:10 |
| jrwren | ha! | 14:10 |
| lazyPower | blame the fact i just spent the last 2 weeks in juju deploy windows land | 14:10 |
| lazyPower | I'm itching to get back to posix land | 14:10 |
| jrwren | that sounds glorious! I'm so jealous. | 14:10 |
| jrwren | if only every version of windows shipped with its posix layer enabled by default. | 14:11 |
| lazyPower | wat | 14:11 |
| lazyPower | what is this "posix layer enablement" you speak of | 14:11 |
| jrwren | lazyPower: windows is a fully posix compliant OS, if you enable it. | 14:11 |
| lazyPower | #TIL | 14:12 |
| jrwren | https://en.wikipedia.org/wiki/Windows_Services_for_UNIX#Subsystem_for_UNIX-based_Applications_.28SUA.29_and_separate_NFS | 14:12 |
| jrwren | oh, my bad, removed from 2012 R2. | 14:12 |
| jrwren | *grumble* wrong direction MSFT | 14:12 |
| lazyPower | http://i.imgur.com/nKXFnZN.jpg <-- pretty much how i feel about that | 14:13 |
| jrwren | i ain't trolling. | 14:13 |
| jrwren | TIL - its removed from 2012R2. | 14:13 |
| lazyPower | i meant about ms removing it | 14:14 |
| jrwren | Its like they do it just to make me angry :) | 14:16 |
| === arosales_ is now known as arosales | ||
| hatch | uiteam lf two reviews and a qa on this code removal branch https://github.com/juju/juju-gui/pull/705 | 17:00 |
| === kadams54 is now known as kadams54-away | ||
| === kadams54-away is now known as kadams54 | ||
| hatch | uiteam anyone able to give this branch a review so I can get it landed? https://github.com/juju/juju-gui/pull/705 | 19:39 |
| === kadams54 is now known as kadams54-away | ||
| === kadams54-away is now known as kadams54 | ||
| === kadams54 is now known as kadams54-away | ||
| === kadams54-away is now known as kadams54 | ||
| === kadams54 is now known as kadams54-away | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!
