Jujulabs: optional message

Maarten Ectors maarten.ectors at canonical.com
Wed Jul 31 16:48:43 UTC 2013


Hi all,

*Somebody added the following additional questions to their survey
responses. I think they are good suggestions and wanted to respond but also
get your feedback if you think these are important features.*

"It would be super-cool to have pre-built high performance production-ready
charms combining different application library stacks.

For example: we are about to launch a product (private beta) that's built
mainly in two parts
Admin: CakePHP, PHP, Apache2, MySQL, AngularJS
Frontend: AngularJS, Node.js, MySQL

Of course, for production there are a set of requirements for achieving
high-performance and availability like:
CDN & Edge static files distribution
Shared FileSystem (NFS +NGINX, S3 buckets, any other) to deliver files to
CDN
The ability to replicate to several Availability Zones (AWS)
Memcache or Redis for in-memory cache
Apache2 event-mpm

Additionally, we use Amazon SNS as a near-real-time push-push messaging
service to orchestrate our event-driven application logic; so I don't know
if there'll be only "self-hosted" products available or are you planning to
add some cloud-vendor specific charms.

What I think would be an important issue for us, and we are working on an
in-house solution, is the ability to do staged-rollouts (from customers
that approve to have our "labs features" to use them as a massive
beta-testing force for new features).

We look forward to hear about this inquiries, maybe we can also place some
effort on developing some solutions for this problems as a collaboration to
the Juju project."

*Response: Creating different application library stacks would be a quick
win and probably a step zero before adding continuous integration. So
definitely something we will look into. You are already able to create your
own Charms if you feel that you can't wait. When you are in the GUI you can
do shift-D. It will download a yaml file. This is a complete bundle of
everything you defined. If you install the optional tool "juju-deployer"
then you are able to install those bundles instantly. We will be working on
making this a fully integrated solution pretty soon.*
*
*
*We have already some Charms around AWS functionality in beta, like ELB,
route53, etc. more info: *
http://manage.jujucharms.com/search?search_text=aws

*You are able to deploy memcached, redis, nginx, etc. already. Multi-AZ
hopefully can be added but at the moment the workaround is to startup the
machines (juju add-machine), kill it if it is not in the required AZ and
afterwards add the service to the machine in the specific AZ.*
*
*
*As you can see from the AWS ELB example, not all products need to be
self-hosted. You can have "proxy" charms that use an external service and
"subordinate" charms that extend a main charm, e.g. NRPE for Nagios.*
*
*
*Internally we are using A-B testing tools like Genetify that help you
create different alternative versions of a feature and find the one that
has more success automatically. If there is a similar framework that could
be used for enabling "labs features" we would definitely be interested in
adding it if people think it is important to them.*

Thanks,
Maarten Ectors
Senior Cloud Strategist
Changing the Future of Cloud
Ubuntu <http://ubuntu.com> / Canonical <http://canonical.com> UK LTD
maarten.ectors at canonical.com
Fixed: +44 (0) 207 630 2435
Mobile: +44 (0) 791 860 814
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/jujulabs/attachments/20130731/17654406/attachment-0001.html>


More information about the JujuLabs mailing list