[10:33]  * al-maisan -> office
[12:41] <kiranm> 'ensemble status' always shows me connection timeout for me. Pasted the output here: http://paste.ubuntu.com/625813/
[13:47] <niemeyer> Good morning everyone
[13:53] <kim0> o/
[14:34] <al-maisan> Good morning niemeyer :)
[14:38] <niemeyer> al-maisan, kim0: Hey there!
[15:01] <_mup_> ensemble/trunk r252 committed by gustavo@niemeyer.net
[15:01] <_mup_> Merge add-python-yaml branch by Clint [r=niemeyer] [trivial]
[15:01] <_mup_> This adds the missing python-yaml package dependency.
[16:48] <SpamapS> Hey guys. How would you all feel about moving everything except 'ensemble' out of /usr/bin ?
[16:49] <SpamapS> Otherwise... W: ensemble: binary-without-manpage usr/bin/open-port
[16:53] <niemeyer> SpamapS: Hmm
[16:53] <niemeyer> SpamapS: I think we should provide these man pages eventually
[16:53] <niemeyer> SpamapS: /usr/bin feels to me like the write place for these tools
[16:53] <SpamapS> are any of those ever useful outside of hooks though?
[16:53] <niemeyer> SpamapS: But then, I don't claim to understand the FS organization fantastically
[16:53] <SpamapS> If no, then they're really more suitable in /usr/lib
[16:54] <niemeyer> SpamapS: Today, they're not, but I hope all of these tools are runnable out-of-band in the future
[16:54] <niemeyer> SpamapS: So we can do actions based on events not initiated by Ensemble itself
[16:55] <SpamapS> Ahh, thats enough to make me think they need man pages then.
[16:56] <SpamapS> Though it might be better to have one command which tells the local agent to do things.
[16:57] <niemeyer> SpamapS: That may be a good idea.. that said, I still like how e.g. "relation-get foo" is concise
[16:58] <SpamapS> Yeah, my thinking is that we're just going to dump all over the global /usr/bin namespace.
[17:02] <niemeyer> Ugh.. past lunch time.. biab
[17:34] <SpamapS> hmm.. should -e / --environment be changed to a global option, instead of one for the commands?
[19:27] <SpamapS> Whats the exact policy on trivial changes to the trunk? The online help for remove-relation says that it adds a relation.
[19:34] <niemeyer> SpamapS: If it's truly trivial and you're sure that's what should be in place, you can "cowboy" the change in
[19:34] <niemeyer> SpamapS: Marking it as [trivial] in the commit line
[19:35] <niemeyer> SpamapS: Many times these will also be preceded by an "on-the-fly" review request
[19:35] <niemeyer> SpamapS: E..g just post the diff somewhere and invite a review
[19:35] <niemeyer> (here)
[19:35] <niemeyer> SpamapS: Your example sounds good for a trivial, FWIW
[19:43] <jimbaker> bcsaller, hazmat, niemeyer - standup?
[19:43] <niemeyer> jimbaker: I'd rather see some _action_ happening!
[19:44] <jimbaker> niemeyer, ok
[19:45] <koolhead17> hi all
[19:46] <niemeyer> koolhead17: Hey there
[19:47] <niemeyer> koolhead17: Noticed you picked a formula to work on.. that's pretty cool, thanks!
[19:47] <niemeyer> koolhead17: How're things going there so far/
[19:47] <niemeyer> ?
[19:47] <koolhead17> niemeyer: :)
[19:47] <koolhead17> hoping to get it done by tonight!!
[19:47] <koolhead17> kim0: ping
[19:48] <_mup_> ensemble/set-transitions r239 committed by bcsaller@gmail.com
[19:48] <_mup_> fixed issue with merge of watch establishment in unit agent
[20:01] <SpamapS> koolhead17: You chose the phpmyadmin formula right?
[20:01] <koolhead17> SpamapS: yes
[20:02] <SpamapS> koolhead17: cool, its going to need some help from the mysql formula, but I already started on it.
[20:02] <koolhead17> SpamapS: yes. we need apache2/php5 as well :P
[20:02] <SpamapS> koolhead17: no, thats all in your formula in the install hook
[20:03] <SpamapS> koolhead17: what you need is an admin user that can read/write to/from all dbs.
[20:03] <koolhead17> SpamapS: hmm. am installing phpmyadmin along with depandency to come up with list of depandent pkgs which will go as depandant hook
[20:04] <koolhead17> on one of natty running vm on virtualboc
[20:04] <koolhead17> x
[20:04] <SpamapS> koolhead17: right, but you want to administer a mysql database for some other app, right? like, you want to admin the database for wordpress.
[20:04] <SpamapS> koolhead17: otherwise its just phpmyadmin with its own database
[20:05] <koolhead17> SpamapS: i thought this is a formula 4 a standalone phpmyadmin configuration. please correct me if am wrong 
[20:05] <SpamapS> koolhead17: Its a good start. However, people can do that without ensemble.
[20:05] <koolhead17> now to create DB for a cms say drupal/joomla do we need a web-interface?
[20:06] <SpamapS> koolhead17: ensemble is interesting because it can relate these services together. :)
[20:06] <koolhead17> :D
[20:06] <koolhead17> we can do that via appropriate hooks while writing formula for jooma/drupal/wordpress
[20:06] <koolhead17> isnt it
[20:06] <koolhead17> :P
[20:07] <koolhead17> there we can have mysql formula as depandency
[20:07] <SpamapS> koolhead17: so you'll be able to say 'ensemble add-relation phpmyadmin:db wiki-db:db-admin .. and that will give you access to all the databases on wiki-db.
[20:08] <koolhead17> SpamapS: but i thought phpmyadmin has more to do with checking web-interface based mysql db :)
[20:08] <koolhead17> would we really need a formula like that as you suggsted!! :D
[20:09] <SpamapS> koolhead17: usually phpmyadmin is used to do queries on a database from some other application.
[20:09] <SpamapS> koolhead17: I don't see it being all that useful with just an empty database.
[20:10] <koolhead17> SpamapS: hmm!! your right
[20:10] <koolhead17> SpamapS: let me come up with the basic formula with hooks to install phpmyadin and then in 2nd level/round i can work on this
[20:10] <SpamapS> koolhead17: thats a great way to do it.
[20:10] <koolhead17> it will be easier 4 me to pick up ensemble in that case :P
[20:10] <SpamapS> koolhead17: install hook is usually first, then you add the relations. :)
[20:11] <koolhead17> SpamapS: yes. writing down all the pkgs saperately while testing a install in virtualbox :)
[20:12] <SpamapS> koolhead17: you shouldn't need to do much more than 'apt-get install phpmyadmin'
[20:12] <SpamapS> koolhead17: you will probably want to say '--no-install-recommends'
[20:12] <koolhead17> SpamapS: hmm 
[20:14] <SpamapS> actually no
[20:14] <SpamapS> it only suggests mysql-server
[20:14]  * koolhead17 is running the command
[20:14] <SpamapS> so you can just do 'apt-get -y install phpmyadmin' .. it will automatically pull in php, apache, mysql client, etc. etc.
[20:15] <koolhead17> hmm
[20:15] <koolhead17> including apache2 and all
[20:16] <koolhead17> SpamapS: it also asks two options during install
[20:16] <koolhead17>  Web server to reconfigure automatically: <-- apache2
[20:16] <koolhead17>  
[20:16] <koolhead17>  Configure database for phpmyadmin with dbconfig-common?  
[20:18] <koolhead17> also we need to add "Include /etc/phpmyadmin/apache.conf" in   /etc/apache2/apache2.conf to get it to work :D
[20:18] <SpamapS> koolhead17: during an install hook, it will skip those
[20:18] <SpamapS> koolhead17: thats what you do during the install hook.
[20:18] <koolhead17> SpamapS: hmm
[20:19] <SpamapS> koolhead17: read the wordpress and mysql examples, they handle it
[20:20] <koolhead17> SpamapS: http://fewbar.com/2011/06/so-what-is-ensemble-anyway/
[20:20] <koolhead17> this one
[20:26] <SpamapS> koolhead17: thats my post, not an example. ;) I mean in /usr/share/doc/ensemble/examples
[20:27] <koolhead17> SpamapS: :P
[20:27] <koolhead17> k
[20:27] <koolhead17> SpamapS: phpmyadmin is not dependant on mysql-server
[20:28] <SpamapS> koolhead17: right, it only 'suggests' mysql-server
[20:28] <koolhead17> we need to install mysql-server too for a new installation in order to  get phpmyadmin working :D
[20:29] <SpamapS> No!!
[20:30] <SpamapS> The mysql server can live on another machine.
[20:30] <koolhead17> SpamapS: hmm.
[20:30] <koolhead17> also is there an option in apt-get which results in skipping the question part, like skipping option for username/passwd
[20:31] <koolhead17> and all
[20:31] <SpamapS> -q
[20:31] <SpamapS> -yq actually
[20:32] <koolhead17> SpamapS: thanks. 
[20:32] <SpamapS> koolhead17: if you read that post you linked to, it deploys mysql as its own host.. it then relates mediawiki to it. Your phpmyadmin formula must relate to the database server using hooks.
[20:32] <koolhead17> hmm
[20:33] <SpamapS> koolhead17: have you looked at the example mysql and wordpress formulas yet?
[20:33] <koolhead17> SpamapS: yes
[20:34] <koolhead17> i also have drupal formula here
[20:34] <koolhead17> it will be similar
[20:36] <SpamapS> koolhead17: there are already 2 other drupal formulas in progress...
[20:36] <koolhead17> okey
[20:36] <SpamapS> koolhead17: ok I'm not sure if you understand the examples if you are confused by my statements. Only one formula ever needs to install mysql-server.
[20:41] <SpamapS> DOH.. I just now noticed my last 'ensemble shutdown' a week ago didn't work right and left 11 m1.smalls running for a week
[20:41] <SpamapS> DOH DOH DOH
[20:42] <robbiew> lol
[20:42]  * SpamapS decides tonight he will hack out an LXC provider.. 
[20:42]  * robbiew makes sure to review the next expense report from SpamapS
[20:42] <SpamapS> robbiew: its 1 *meeeeelion* dollars
[20:44] <SpamapS> ok it was actually 7 m1.smalls and 4 t1.micros
[20:44] <SpamapS> that should only be like, $75
[20:48] <koolhead17> hello robbiew
[20:48] <koolhead17> SpamapS: db-relation-changed what is this hook for
[20:48] <robbiew> hey koolhead17
[20:49] <koolhead17> in the wordpress example? assigning DB?
[20:49] <SpamapS> koolhead17: When you relate the wordpress service to the mysql service, that is the hook that gets run
[20:50] <koolhead17> SpamapS: cool
[20:51] <SpamapS> koolhead17: if you haven't read this yet, you really should: https://ensemble.ubuntu.com/docs/write-formula.html
[20:52] <koolhead17> SpamapS: i have that page open, drupal example one. i think kim0 wrote it :)
[20:57] <m_3> SpamapS: you totally just gave me one of those 'oh crap' moments... but everything's safe and shutdown
[20:58] <SpamapS> m_3: I am 99% sure I just typed it fast before slamming the laptop shut.. it probably never completed
[20:59] <niemeyer> m_3!
[20:59] <niemeyer> m_3: Welcome!
[20:59] <m_3> Hi Ensemble team
[20:59] <hazmat> SpamapS, ouch!
[20:59] <m_3> nice to meet everyone
[21:00] <m_3> niemeyer: thanks!
[21:03]  * koolhead17 is scared, the cats are making scary noise outside
[21:06] <SpamapS> hazmat: Hey, I've had debug-log disconnect on me twice now
[21:07] <hazmat> SpamapS, disconnect? what's it say on the terminal when that happens?
[21:08] <SpamapS> http://paste.ubuntu.com/626112/
[21:08] <SpamapS> hazmat: ^^
[21:08] <SpamapS> sweet..
[21:09]  * SpamapS just added a db-admin interface to mysql so services can be related with 'all privileges' ..
[21:10] <hazmat> SpamapS, ah.. yeah.. this is the session event stuff, i've got a branch of txzookeeper which will resolve (https://code.launchpad.net/~hazmat/txzookeeper/session-event-handling), but its pending some additional testing work for setting up zk test clusters
[21:10] <SpamapS> ahh ok
[21:11] <SpamapS> same thing that killed my munin nodes?
[21:11] <hazmat> SpamapS, yup, once that's merged that should resolve this class of issues
[21:11] <hazmat> its basically zk client letting the app know about transient network connect/disconnects
[21:20] <koolhead17> SpamapS: -yq  option doesn`t seem to work :(
[21:24] <hazmat> bcsaller, jimbaker if you one you have time, could you please check out niemeyer's debug-hooks-fixes? its pretty critical to having that feature work well, and needs an additional review
[21:24] <bcsaller> sure
[21:29] <niemeyer> Danke!
[21:33] <_mup_> ensemble/set-transitions r240 committed by bcsaller@gmail.com
[21:33] <_mup_> better error message when passed non-key/value pair on cli
[21:34] <pindonga> hi everyone! I have been playing around a little with ensemble 
[21:34] <pindonga> I'm trying to create a provider for lxc :)
[21:34] <pindonga> I got as far as breaking everything, and slowly starting to put the pieces back in place :p
[21:34] <hazmat> pindonga, cool :-)
[21:35] <pindonga> so I can now create a lxc container, start it, and am stuck when ensemble tries to ssh into it
[21:35] <pindonga> because it didn't yet install the zookeeper stuff into the container
[21:35] <pindonga> can you guys point me to the code that installs the necessary packages into the bootstrap instance?
[21:35] <hazmat> pindonga, ah.. you mean the ssh succeeds but the client can't connect to via the tunnel because zk isn't running
[21:36] <pindonga> hazmat, ensemble tries to connect via ssh to port 281xx 
[21:36] <pindonga> but it fails
[21:36] <hazmat> pindonga, its using cloud-init.. see ensemble/providers/ec2/launch.py for the existing stuff
[21:36] <hazmat> pindonga, you can seed  cloud-init by dropping a file on disk as well instead of the ec2 metadata service
[21:36] <pindonga> I believe ensemble should do something like apt-get or dpkg to install zookeeper into the bootstrap instance, right?
[21:38] <niemeyer> Coffee!
[21:38] <hazmat> pindonga, it should but at the moment its relying on the image to provide it.. installing it at runtime was overly time consuming (ie. java stack from scratch).... so it got yanked from the cloud-init install instructions to part of image building.. we're planning  on yanking that though and going back to cloud-init based installation of zk
[21:39] <hazmat> pindonga, its a pretty small change to reenable it.. effectively just adding a apt-get install zookeeper to the cloud init commands list
[21:39] <pindonga> hazmat, k, will look for it
[21:39] <pindonga> so right now ensemble cannot bootstrap from base install, as I understand?
[21:41] <hazmat> pindonga, it can, its just not configured that way atm.. actually let me double check something
[21:41]  * hazmat waits for ec2 bootup
[21:46] <hazmat> pindonga, so it can bootstrap a regular image.. we just pre-install for speed
[21:47] <hazmat> pindonga, so ensemble/providers/common.py has the standard packages and repos we use as constants, ensemble/providers/ec2/utils.py has format_cloud_ini (which should get refactored into the previous common.py since its now generic).. and then ensemble/providers/ec2/launch.py will setup additional things for installation based on bootstrap node vs. machine node.
[21:48] <hazmat> in terms of getting cloud-init setup with with an lxc-provider, the cloud-init needs to be preseeded on disk before starting up the instance, as an example with (assuming natty) http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/seed/README
[21:49] <pindonga> thanks, will look into it
[21:56] <hazmat> pindonga, cool, you might want to talk to SpamapS if you want to collab as he mentioned some interest in working on an lxc-provider as well
[21:57] <hazmat> and keep the questions coming ;-)
[21:57] <pindonga> hazmat, right now I'm just doing the minimum to get it up and running 
[21:57] <pindonga> no intention to get production code until I understand how this works :)
[22:03] <hazmat> bcsaller, re the branch config-set.. was there a merge conflict with this branch, i'm seeing some oddities in a diff against trunk?
[22:04] <bcsaller> hazmat: the config-set that was merged? or the later branch I emailed you about?
[22:04] <hazmat> bcsaller, the emailed branch
[22:05] <bcsaller> hazmat: I had a divergent branch issue between this and my other laptop from when this one was being repaired. That said its a few revisions back and I thought dealt with 
[22:05] <hazmat> bcsaller, as an example there's a test_hook_knows_service that looks like it got yanked in the branch.. some of other oddities are just relocating code chunks
[22:05] <bcsaller> hmm
[22:07] <bcsaller> hazmat: ahh, I think I know what happened there, That was code that was deprecated after a review but by the time it was ready for merge jim's branch was already depending on some of that code 
[22:08] <bcsaller> so I added those parts back in  (though my branch already contained the diff to remove them from the previous review)
[22:08] <hazmat> bcsaller, ah.. ic.. okay.. i'm having a look at it now
[22:08] <bcsaller> appreciate it 
[22:19] <hazmat> bcsaller, could you pastebin errors from a test run?
[22:19] <bcsaller> hazmat: sure, are you not getting errors?
[22:20] <hazmat> i get a pretty constant set of 4 error
[22:20] <hazmat> over 3 full test runs
[22:20] <bcsaller> and if you run those alone do you still see them?
[22:21] <hazmat> bcsaller, haven't tried yet.. i just want to make sure we have the same error set to verify them and ensure we have sane local setup deltas
[22:21] <hazmat> bcsaller, is that number inline with your seeing?
[22:22] <bcsaller> that time I only got ensemble.agents.tests.test_unit.UnitAgentResolvedTest.test_hook_error_on_resolved_retry_remains_in_error_state
[22:22] <bcsaller> but it might change if I run it again (which I am)
[22:26] <hazmat> bcsaller, yeah.. one of these tests is definitely bleeding into the others
[22:26] <bcsaller> hazmat: yeah, that time it was a different one
[22:32] <hazmat> bcsaller, one review comment on the change.. it would be better to just reconstruct the service state as needed rather than passing it as a new construct arg to scheduler, relhookcontext, etc
[22:33] <hazmat> ie. the rel hook context has a client and can reconstruct the state on demand
[22:33] <bcsaller> hazmat: doesn't the service name then need to be parsed from the unit_name
[22:36] <hazmat> bcsaller, it does, but that's a pretty trivial
[22:37] <bcsaller> I can make those changes 
[22:37] <hazmat> i think the service-state-manager could grow a utility method for it as well
[22:37] <hazmat> return the service state given a unit name
[22:41] <bcsaller> makes sense,  yes
[22:43] <daker> yo
[22:43] <niemeyer> daker: Yo
[22:43] <niemeyer> daker: So,
[22:44] <niemeyer> daker: "--password=" < that's not going to work if you split the arguments 
[22:44] <niemeyer> daker: You can drop the "=" sign there
[22:44] <niemeyer> daker: Then they can be in separate arguments
[22:44] <niemeyer> daker: This won't do what you want as well:
[22:44] <niemeyer> "< %(ensemble_sql)s" % config)
[22:44] <daker> should be splited ?
[22:45] <niemeyer> daker: It's a bit trickier in this case
[22:45] <niemeyer> daker: When you provide something like that to the shell, what's happening is that the file descriptor for stdin is being replaced to that of the open file with the given name.
[22:45] <niemeyer> daker: Have you considered using bash for your script?
[22:46] <niemeyer> daker: In case that's what you're most comfortable with?
[22:46] <daker> i am comfortable with python, bash was suggested by kim0
[22:47] <niemeyer> daker: Aha, ok
[22:49] <daker> niemeyer, i have an idea
[22:49] <niemeyer> daker: You may want to use -e
[22:49] <niemeyer> daker: Rather than stdin
[22:50] <daker> i'll just use MySQLdb
[22:50] <niemeyer> daker: Otherwise you'll have to open a file and extend your do() function to replace stdin
[22:50] <niemeyer> daker: Ah, that works too! :)
[23:34] <SpamapS> niemeyer: so the idea of using relation id is actually good
[23:34] <SpamapS> niemeyer: thinking through it, using service name for database names is actually VERY limiting.
[23:34] <niemeyer> SpamapS: I'm not entirely sure yet, to be honest
[23:35] <SpamapS> niemeyer: otherwise we can't have two services use the same database.
[23:35] <niemeyer> SpamapS: Agreed, for that kind of use case a relation id would be great
[23:35] <niemeyer> SpamapS: The question is more around the lines of reestablishment
[23:35] <SpamapS> niemeyer: so I think we need to have the consuming services provide us with a clear hint. It may usually be service name.
[23:36] <niemeyer> SpamapS: It isn't clear that what we want to happen when one removes and readds a relation
[23:36] <niemeyer> s/that what/what/
[23:36] <SpamapS> niemeyer: IMO, thats up to the formula to document.
[23:36] <niemeyer> SpamapS: I think we need to guide people here
[23:37] <niemeyer> SpamapS: So that formulas implement it somewhat consistently, and follow a principle of least surprise
[23:37] <SpamapS> niemeyer: I was thinking of mapping relation-id to the requested context like "demo-wiki" .. then if something else asks for demo-wiki, give them access.
[23:38] <niemeyer> SpamapS: I don't get that last idea
[23:38] <SpamapS> niemeyer: can add an optional setting of 'maxrelations' for each database context too.. so you can say 'maxrelations=1' if you want to have exclusive databases.
[23:39] <SpamapS> niemeyer: so the relation-id is just a uuid, so there'd be a table..   relation-id: 11004-33-55-5-666, data-name: 'wiki'
[23:39] <SpamapS> niemeyer: when we break the relation, we remove that row. When somebody asks for 'data-name=wiki' we give them access to the 'wiki' database.
[23:39] <SpamapS> err
[23:39] <SpamapS> meh I'm all out of order.
[23:40] <SpamapS> niemeyer: basically use the relation-id to map to the data we care about
[23:41] <niemeyer> SpamapS: I don't understand how that's better than what we have now?
[23:41] <SpamapS> niemeyer: the only change is that the consuming formulas specify the database name, rather than the consuming service's name..
[23:42] <SpamapS> niemeyer: so that you can say, have a backend hadoop job querying the same database as the frontend webservers.
[23:42] <SpamapS> right now you can't do that
[23:42] <niemeyer> SpamapS: We already have that.. that's essential what relations do
[23:43] <niemeyer> SpamapS: They have a name, for precisely that reason
[23:43] <niemeyer> SpamapS: and that's already possible today (sharing the db between multiple services)
[23:43] <SpamapS> right now, if I spawn two mediawiki services.. and relate them both to a mysql service, they will get independent databases...
[23:44] <SpamapS> I may want them to share a db
[23:44] <SpamapS> yeah, thats a formula problem. :)
[23:46] <SpamapS> niemeyer: yes I guess I'm saying we should do that sooner rather than later... the relation-id is a separate issue.
[23:46] <niemeyer> SpamapS: Do what sooner?
[23:48] <SpamapS> niemeyer: change the mysql formula to accept the database name rather than assume it.
[23:48] <SpamapS> niemeyer: and as far as the relation-id, we can use that to know which relation maps to which database name.
[23:48] <niemeyer> SpamapS: I'd like to see a use case we can work on, first
[23:48] <SpamapS> as long as its available in all hooks
[23:49] <SpamapS> niemeyer: the mysql use case isn't good enough?
[23:49] <SpamapS> during broken, I have no idea what resources to clean up
[23:49] <niemeyer> SpamapS: Sorry, I may have missed it.. what's the use case again?
[23:50] <SpamapS> it was in the bug you duped IIRC
[23:50] <niemeyer> SpamapS: Ah, ok.. that's about being able to identify relation ids, so that re-adding a relation to the same set of formulas can reuse resources.
[23:51] <niemeyer> SpamapS: That's not the same as manually specifying database names
[23:51] <SpamapS> Its actually more than that. Iduring broken, right now, there is no way to tell which relation was broken other than a hack where you run 'relation-list'
[23:51] <niemeyer> SpamapS: Why do you want to tell which relation has been broken?
[23:52] <niemeyer> SpamapS: I mean.. why do you want an identifier in that location?
[23:52] <SpamapS> Because I want to revoke the user privileges, delete temp tables, etc. etc. The documented reasons for the broken relation are to clean up.
[23:52] <niemeyer> SpamapS: Hmmm..
[23:53] <niemeyer> SpamapS: Removing tables is not a good idea in general, but I see your point otherwise
[23:53] <SpamapS> notice I said *temp*. :)
[23:53] <niemeyer> Cool, ok :-)
[23:53] <SpamapS> I happen to agree that purging should be primarily manual. :)
[23:53] <niemeyer> SpamapS: Yeah, I think for _that_ the relation id in that ticket should handle it
[23:53] <SpamapS> Or at least married with a backup service.
[23:54] <niemeyer> SpamapS: THe issue is what do you expect when you re-add a relation to the same couple of services?
[23:57] <SpamapS> Right, for that, we definitely need to set an example.
[23:57] <SpamapS> I like the way the mysql formula handles that. If somebody requests an existing database, go ahead and give them access.
[23:57] <niemeyer> SpamapS: I'm starting to think the mysql formula should create a database after the remote service name, as it is doing right now
[23:58] <niemeyer> SpamapS: and we need a relation id
[23:58] <SpamapS> and never allow shared access to a single db?
[23:59] <niemeyer> SpamapS: That's a different use case.. let's handle it separately please
[23:59] <niemeyer> SpamapS: We already handle shared access
[23:59] <niemeyer> SpamapS: All the service units from the same service will access the same database
[23:59] <SpamapS> But I want two services to be able to share data through mysql.