[09:35] <bcsaller> niemeyer: https://bugs.launchpad.net/ensemble/+bug/771348
[09:35] <_mup_> Bug #771348: status barfs when checking newly deployed service units (no state) <Ensemble:New> < https://launchpad.net/bugs/771348 >
[09:37] <niemeyer> bcsaller: Cheers
[09:40] <jimbaker> hazmat, dublin is fun + productive
[09:40] <kim0> A new screencast springs into existence → http://www.youtube.com/user/ubuntucloud#p/a/u/0/AMHcy63wRL0
[09:40] <kim0> "Ensemble deploy and scale cloud apps with ease"
[09:41] <jimbaker> kim0, sounds great! need to get my headphones out
[09:41] <kim0> if you spot a horrible mistake .. let me know .. can still fix it
[11:50] <_mup_> ensemble/expose-status r263 committed by jim.baker@canonical.com
[11:50] <_mup_> Tests to verify that open-ports is not set in status unless service is exposed
[11:51] <_mup_> ensemble/expose-status r264 committed by jim.baker@canonical.com
[11:51] <_mup_> Do not set open-ports unless service is exposed
[12:23] <_mup_> Bug #802931 was filed: Modify provisioning agent so that the machine opens/closes ports <Ensemble:New> < https://launchpad.net/bugs/802931 >
[12:57] <kim0> Does anyone agree "ensemble shutdown" should have a -y option ?
[13:35] <ivoks> can ensemble formula be interactive?
[13:36] <ivoks> meaning, can it ask for some user input before for information required when packages are installed
[14:10] <kim0> ivoks: afaik not really .. but we'll get that soon with config-set (passing variables to formulas)
[14:11] <kim0> devs correct me if I'm wrong
[14:11] <ivoks> ok, that's good enough
[14:12] <ivoks> how does expose/unexpose work?
[14:13] <ivoks> even if i don't expose, all the services from my formula are available from outside
[14:13] <kim0> ivoks: I believe expose is for opening up ports using ec2 security groups (current provider)
[14:13] <kim0> but today .. I believe all ports are open by default
[14:13] <ivoks> ok
[14:14] <ivoks> i'm working on mail-stack formula
[14:14] <ivoks> i got it working fine, with exception of not being able to define relayhost :)
[14:15] <kim0> Ben is working hard to add passing params
[14:15] <kim0> should hopefully land soon
[14:15] <ivoks> what i'd like to do more is to separate postfix to one instance and dovecot to the other
[14:16] <kim0> ivoks: btw https://ensemble.ubuntu.com/docs/ has more info on exposing :)
[14:16] <ivoks> yeah, i know
[14:16] <ivoks> :)
[14:20] <hazmat> ivoks, atm things are open, but in future, when the ports stuff land it will be closed to public by default but open to internal traffic (till we adjust the ports work to take into account relations)
[14:21] <ivoks> ok
[14:21] <hazmat> ivoks, re how ports work.. the formula hooks can designate which hooks they want to open and close via an ensemble cli api (open-port, close-port).. the ensemble user/admin will need to expose the service for these hook defined settings to take effect
[14:22] <ivoks> ok
[14:24] <hazmat> underneath the hood their using ec2 security groups as kim0 pointed out
[14:24] <hazmat> kim0, are you in dublin this week?
[14:25] <kim0> Yes 
[14:25] <kim0> you are not right
[14:25] <hazmat> kim0, nope.. just wondering where the dev team is hanging out at
[14:26] <hazmat> kim0, i did a mongodb conference yesterday.. and did a quick demo of the mongodb formula i've been working on
[14:26] <hazmat> but it also needs config-set for the sharding configuration
[14:26] <kim0> woohoo
[14:26] <kim0> hazmat: share that formula man :)
[14:27]  * hazmat looks up the how to share with principia docs
[14:27] <hazmat> niemeyer, hallo!
[14:29] <ivoks> destroy-service doesn't really do anything yet?
[14:29] <hazmat> ivoks, it does.. it removes relations, destroys units, it should wipe the service from the environment
[14:29] <ivoks> hm
[14:29] <ivoks> everything is still running on my instance :)
[14:30] <hazmat> hmm.. 
[14:30] <hazmat> ivoks, have you implemented the stop hook?
[14:30] <ivoks> there are no relations, but dovecot, postfix and amavis are still running
[14:31] <ivoks> yes; it might be wrong
[14:31] <ivoks> service dovecot stop
[14:31] <ivoks> same for postfix and amavis
[14:31]  * hazmat checks the implementation
[14:32] <hazmat> SpamapS, how's the reception of lxc-provider at the rally?
[14:39] <hazmat> ivoks, so it doesn't appear that destroying a service will actually inform the unit it should suicide, it just tells the machine agent to kill the unit agent
[14:39] <hazmat> ivoks, so in the destroy-service case with the service processes still running, do you see any unit agent processes in the process listing?
[14:40] <hazmat> so the relation-broken hooks are invoked, but not afaics the stop hook
[14:40] <ivoks> i see unit agent
[14:40] <ivoks> /usr/bin/python -m ensemble.agents.unit -n --pidfile /var/lib/ensem....
[14:41] <hazmat> hmm
[14:41] <ivoks> it's not listed in ensemble status
[14:42] <ivoks> ah, don't worry about it
[14:42] <ivoks> i have other things to solve first
[14:42] <niemeyer> hazmat: Hey man!
[14:42] <niemeyer> hazmat: Missing you here
[14:42] <hazmat> ivoks, i'll keep digging into it
[14:42] <ivoks> like 'restart service after 'install''
[14:42] <hazmat> niemeyer, how's it going so far
[14:42] <niemeyer> hazmat: Fantastic
[14:42] <hazmat> niemeyer, awesome.. any highlights so far? or just a good productive vibe going around?
[14:42] <ivoks> niemeyer: i bet it's raining all the time :)
[14:43] <niemeyer> ivoks: :-)
[14:43] <niemeyer> hazmat: Quite a few.. still have to digest
[14:43] <niemeyer> hazmat: What are you working on right now?
[14:43] <hazmat> i think its rained every day at wimbledon but like two.. out of 10
[14:43] <niemeyer> hazmat: and how much time would it take for you to get rid of our pre-baked images?
[14:43] <hazmat> niemeyer, atm digging into destroy-service
[14:43] <hazmat> niemeyer, maybe 2.5 hrs
[14:43] <niemeyer> hazmat: Awesome!
[14:43] <niemeyer> hazmat: Can you push that?
[14:44] <hazmat> niemeyer, sounds good, i'll put an issue to have a look at destroy-service later
[14:44] <niemeyer> hazmat: Yeah, destroy-service actually looks important, but I wonder if it should be postponed and solve LXC first
[14:45] <niemeyer> hazmat: destroy-service will likely have a different story in that light
[14:45] <bcsaller> hazmat: also there is some hinting at more review on my branch which would be helpful
[14:47] <hazmat> niemeyer, not sure that its significantly different, in light of lxc.. perhaps.. the machine agent does a destroy on the unit deployment, and the relations are broken first.. i guess it depends on how we structure the agents for the container, if a machine agent lives in each container in the provider case, or if we just have a singleton machine agent on the physical machine creating containers (which would translate well to pushing the work to ec2)
[14:47] <hazmat> bcsaller, indeed i do need to follow up on that
[14:47] <niemeyer> hazmat: Yeah, maybe it's not that different indeed
[14:48] <niemeyer> hazmat: What about the security stuff?
[14:48] <niemeyer> hazmat: Would be good to get some action happening on that front sooner rather than later
[14:49] <_mup_> Bug #802995 was filed: Destroy service should invoke unit's stop hook, verify/investigate this is true <Ensemble:New> < https://launchpad.net/bugs/802995 >
[14:50] <hazmat> niemeyer, i've got some comments on the review, i'll try to kick that back out today..  so reviews and image work on my plate for today
[14:50] <niemeyer> hazmat: Cool.. I'm just concerned we're not getting any action for a while
[14:51] <niemeyer> hazmat: We can continue evolving the spec and the overall design, but would be good to define what are the first few steps and get these going
[14:52] <ivoks> hazmat: note that this was reproduced on my custom formula (maybe the formula is broken)
[14:53] <hazmat> niemeyer, the mongodb conference yesterday was fun.. their roadmap has some cool features.. the aggregation stuff (map/reduce replacement) is really nice
[14:54] <niemeyer> hazmat: It's awesome indeed.. really looking forward to it
[14:58] <hazmat> off to dog-walk, back in a few
[14:58] <niemeyer> hazmat: Have fun
[16:55] <SpamapS> hazmat: re the lxc provider, its a bit rough getting going, but m_3 was able to get it going
[16:55] <hazmat>  SpamapS nice, you doubled the user population ;-)
[16:55] <_mup_> ensemble/expose-provision-machines r264 committed by jim.baker@canonical.com
[16:55] <_mup_> Initial commit
[16:56] <SpamapS> hazmat: I really want to get all of the agents running under upstart, that would be cool.
[16:58] <hazmat> SpamapS, i had a look after we discussed last month, it looked pretty straightforward
[16:58] <hazmat> i'll see if i can get in this week if no else gets to it
[17:03] <_mup_> Bug #803042 was filed: The "bootstrap node" needs high availability <Ensemble:New> < https://launchpad.net/bugs/803042 >
[17:09] <ivoks> i could help with that :)
[17:11] <niemeyer> Yos
[17:11] <niemeyer> ivoks: Why aren't you here? :)
[17:11] <ivoks> don't know :)
[17:24] <_mup_> ensemble/sans-ami r264 committed by kapil.thangavelu@canonical.com
[17:24] <_mup_> use standard ubuntu amis
[17:24] <_mup_> ensemble/sans-ami r265 committed by kapil.thangavelu@canonical.com
[17:24] <_mup_> add missing natty release image data for tests
[17:56] <_mup_> ensemble/expose-provision-machines r265 committed by jim.baker@canonical.com
[17:56] <_mup_> Now loops
[18:00] <_mup_> ensemble/expose-provision-machines r266 committed by jim.baker@canonical.com
[18:00] <_mup_> Removed debugging sleeps from new test
[19:01] <_mup_> ensemble/sans-ami r266 committed by kapil.thangavelu@canonical.com
[19:01] <_mup_> allow image specifications to select an ami, these specs are not passed to user data.
[20:07] <_mup_> ensemble/sans-ami r267 committed by kapil.thangavelu@canonical.com
[20:07] <_mup_> use the ensemble ppa for software installation by default, but also support branch installations.
[20:48] <_mup_> ensemble/sans-ami r268 committed by kapil.thangavelu@canonical.com
[20:48] <_mup_> tweak install commands to include state and log dir creation
[21:13] <_mup_> ensemble/sans-ami r269 committed by kapil.thangavelu@canonical.com
[21:13] <_mup_> correct name for txzookeeper, and normalize checkout dirname
[22:39]  * niemeyer breaths and heads to some reviewing..
[22:40] <niemeyer> A bit sleepy.. may not last long. :)