Hi Rick, Thank you for mentioning JAAS. It does indeed solve many of my problems. It would be great if you could let me know a bit about pricing. I understand that it's in Beta at the moment. But when it launches will the pricing be based on number of models/number or deployments or some other criteria. Some sort of an idea around pricing would be very helpful.
Overall it looks like JAAS already does what I'm trying to do. And if the pricing is on a similar level as compared to what it would be when I'd deploy juju on my own then it becomes a no brainier. Also I was watching the Getting started with Juju <https://www.youtube.com/watch?v=OBseJVHuVXI&list=PLW1vKndgh8gJS4upPNaXiYYHnCmFdWk03> video on youtube and I learnt about conjure-up. I'm assuming that JAAS will be compatible with all of conjure up commands? Or is conjure-up a slightly different workflow as compared to juju? Best, Akshat On Wed, Aug 30, 2017 at 10:44 PM, Rick Harding <rick.hard...@canonical.com> wrote: > Just to toss, out. JAAS [1] is built to be Juju as a Service across clouds > doing some of the extra work to enable users to have a single dashboard > across a wide array of clouds and regions. Give it a try and I'd love to > chat about any feedback on where JAAS does or doesn't fit for the needs > you're having. > > 1: https://jujucharms.com > > On Wed, Aug 30, 2017 at 10:59 AM fengxia <fx...@lenovo.com> wrote: > >> Akshat, >> >> Just to chip in some of my thoughts on this since we (disclosure, I'm a >> researcher at Lenovo) have had extensive discussions on a similar use case >> and consequently come down to the same challenge as you are currently >> looking at. >> >> 1. Juju CLI allows user to select controller, which essentially leads to >> a particular cloud/provider (these two are 1-1 mapping). Therefore, in >> practice it already supports multi-cloud scenario (last time I counted 12 >> clouds out of box including local LXD and manual). The catch is, of course, >> the manual step of selecting the proper controller. >> >> 2. There are two schools of thought -- whether to have Juju being more >> intelligent so to handle multiple clouds `automatically` (for example, in >> bundle YAML specify which cloud a charm should be deployed to, which is one >> step further than OS series), or using Juju as-is and utilize something >> else as a wrapper to facilitate such mixed-cloud automation. The former >> option minimize tech stack so there is one set of technology to learn and >> manage; the latter gives flexibility, mitigate vendor lock in... I think >> the theme is not new, so it's really a matter of design preference >> >> Juju team has done 90% of the heavy liftings. The former will require >> more in-depth of Juju knowledge, the latter requires less. I think the >> requirements, however, is clear, that there is a higher level of >> abstraction required above the current Juju existence so to drive this. >> >> >> >> On 08/30/2017 04:27 AM, Akshat Jiwan Sharma wrote: >> >> Thank you Feng, >> >> As I understand for now there is no way to use multiple providers with >> juju either with a GUI or command line. >> >> My goal is to be able to allow users to deploy charms (mostly >> wordpress/drupal/ghost) on a cloud of their choice. Anything that allows me >> to do this is acceptable. The only requirement is maximum cloud coverage. >> So for a multi cloud setup what options do I have? >> >> - Should I go for one controller per cloud setup? >> - Can juju api <https://godoc.org/github.com/juju/juju/api> help me >> write some custom code that'll allow me to do what I want? If so what >> should I be looking for in the documentation? >> - Since juju runs in an lxc would it be a good idea to create clone >> containers that can switch the cloud environment on demand? Or would this >> cause more problems that it'll solve? >> >> Thank you once more for being patient with the questions and for all the >> answers! Much appreciated >> >> Best, >> Akshat >> >> On Wed, Aug 30, 2017 at 7:56 AM, fengxia <fx...@lenovo.com> wrote: >> >>> Hi Akshat, >>> >>> Juju controller does not support multiple cloud/provider. It's like a >>> switch board, juju can only talk to one controller at a time. >>> However, I do think there are use case of supporting multiple clouds >>> with one orchestrator. I'm not sure whether juju team has sth like that on >>> its roadmap, or maybe using some other tools for the purpose? >>> On 08/29/2017 09:59 AM, Akshat Jiwan Sharma wrote: >>> >>> Is there a way I can configure multiple providers using the Juju-GUI? >>> Also is there a way I can configure cloud providers based on user access >>> roles? For example a user with access to a particular model can deploy only >>> to a specific cloud provider. >>> >>> If one controller can manage multiple clouds and one controller can have >>> many users then what is the mapping of the relationship between the users >>> and the clouds? >>> >>> Thanks, >>> Akshat >>> >>> >>> >>> -- >>> Feng xia >>> Engineer >>> Lenovo USA >>> >>> Phone: 5088011794 <(508)%20801-1794>fx...@lenovo.com >>> >>> Lenovo.com >>> Twitter | Facebook | Instagram | Blogs | Forums >>> >>> >>> -- >>> Juju mailing list >>> Juju@lists.ubuntu.com >>> Modify settings or unsubscribe at: https://lists.ubuntu.com/ >>> mailman/listinfo/juju >>> >>> >> >> -- >> Feng xia >> Engineer >> Lenovo USA >> >> Phone: 5088011794 <(508)%20801-1794>fx...@lenovo.com >> >> Lenovo.com >> Twitter | Facebook | Instagram | Blogs | Forums >> >> -- >> Juju mailing list >> Juju@lists.ubuntu.com >> Modify settings or unsubscribe at: https://lists.ubuntu.com/ >> mailman/listinfo/juju >> >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
