HI Curtis, I had a similar thought, but wasn't able to validate that as I was able to deploy mysql into a t1.micro (640mb of ram).
Cheers Dave On Fri, Dec 20, 2013 at 4:42 AM, Curtis Hovey-Canonical < [email protected]> wrote: > I think I have sussed the HP mysql errors that have plagues the 1.17.0 > development cycle. > > I and the CI use machines with 2G memory. This is about as small as > anyone will use mysql for. Juju's memory usage has changed quite a > bit. We have seen the mysql state errors change from rare or very > common. > > So I think https://bugs.launchpad.net/juju-core/+bug/1255242 > (upgrade-juju and bootstrap on HP cloud broken in devel) is really > about mysql + juju. > > For now, I have changed CI to use more RAM. If the next few CI runs > don't see the error, I will consider this issue a mysql problem. > However we might have a user problem because "juju deploy mysql" is > less likely to "just work" on HP cloud. > > -- > Curtis Hovey > Canonical Cloud Development and Operations > http://launchpad.net/~sinzui > > -- > Juju-dev mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev >
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
