On 10/09/2013, Tim Penhey <tim.pen...@canonical.com> wrote: > > 1. MAAS Tag support > > This seems to be a key need for a number of engagements we have, and > also a reason why some MAAS/Juju demos are still using pyJuju. We have > talked about this a lot, but I haven't seen any other movement or > progress on it. > > What is the current state of play with the provider or cloud specific > constraints? Does anyone see real blockers to having MAAS tag > deployment constraints done in the next three weeks? Who is going to be > the lead on this? William?
Once there's some framework for provider-specific constraints, maas-tags isn't too involved. Basically it's just a pass-through of a value, the main catch being that juju can't easily test it's validity before trying to obtain a machine, and that tags that are valid now may not continue to be valid for all time. > 2. Container Pain > > Right now we don't have a way to restrict the users creating containers > that they cannot address. I propose that we add a method to the > environment interface that is SupportsContainers() bool. This can then > be used to stop people at least creating containers that they can't use. > > This I think we need to do in the next three weeks, and make sure the > add-machine and deployment commands respect whether containers are > supported or not. Currently the only provider that actually supports > containers is MAAS. > > Next I think we should have SupportedContainers() on a machine. > Different machines can support different containers. However I'm not > sure we should do this in the next three weeks, so will be the focus of > a different email. Do we want to support creating just one container, or block container creation full stop in most environments? > 6. Container addressability for EC2 / Openstack > > I don't know where this is at right now. Can Martin please fill us in. Doing EC2 requires some work on goamz, but is all pretty straightforward, with a few unknowns around how they permit VPC with older accounts. I'm still not clear what the solution for Openstack deployments without neutron is. You mentioned previously that was a requirement and something IS knew how to do, but I'm none the wiser as to what needs implementing there. Martin -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
