what's wrong with this picture
- consul/0: 52.11.163.126 (started) 53/tcp, 8302/tcp, 8400/tcp, 8500/tcp - consul/1: 52.11.216.46 (started) 53/tcp, 8302/tcp, 8400/tcp, 8500/tcp - consul/2: 52.26.15.3 (started) 53/tcp, 8302/tcp, 8400/tcp, 8500/tcp - docker/0: 52.27.4.236 (started) 3000/tcp, 49154/tcp - heka-agent/1: 52.27.4.236 (started) - registrator/1: 52.27.4.236 (started) - docker/1: 52.24.16.120 (started) - heka-agent/0: 52.24.16.120 (started) - reg/0: 52.24.16.120 (started) - reggie/0: 52.24.16.120 (started) - es/0: 52.26.67.111 (started) 9200/tcp - heka-hub/0: 52.11.55.89 (started) 5565/tcp - juju-gui/0: 52.11.199.84 (started) 80/tcp, 443/tcp - nginx/0: 52.27.4.236 (started) -w -- --- D. Whit Morriss Developer, Juju Ecosystem Canonical USA -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
[Review Queue]
I spent some time reviewing some refactoring and updates to the python-django charm[0]. In general looks good, though still a work in progress. [0] https://code.launchpad.net/~thumper/charms/trusty/python-django/support-1.7/+merge/260389 -w -- --- D. Whit Morriss Developer, Juju Ecosystem Canonical USA -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
[Review Queue]
- bip (irc proxy): new trusty charm +1 [0] - haproxy: merge services [0] https://bugs.launchpad.net/charms/+bug/1401774 [1] https://code.launchpad.net/~danilo/charms/trusty/haproxy/merge-services-fix/+merge/259233 -w -- --- D. Whit Morriss Developer, Juju Ecosystem Canonical USA -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
[Review Queue]
1. minor extending of ubuntu charm: +1. Note it's up to debate whether this is perhaps more appropriate as feature in a personally namespaced charm or a new charm altogether. The ubuntu charm has no clear single owner afaict to make this sort of decision. 2. kibana nginx port configuration: this still lacked a test, so I added one + a fix for not opening the port (still needs code to clean up old port). [1] https://code.launchpad.net/~jjo/charms/trusty/ubuntu/add-execd-and-charmhelpers-syncing/+merge/256136 [2] https://code.launchpad.net/~evarlast/charms/trusty/kibana/add-port-path-config https://code.launchpad.net/~whitmo/charms/trusty/kibana/port-configure-test/+merge/258678 -w -- --- D. Whit Morriss Developer, Juju Ecosystem Canonical USA -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
[Review Queue]
squeezed in a quick review: - ghost update for precise that replaces vendored asset blob with a configurable download. - ntp bug fix both approved [0] https://code.launchpad.net/~hatch/charms/precise/ghost/trunk/+merge/255168 [1] https://code.launchpad.net/~paulgear/charms/trusty/ntp/fix-divide-by-zero/+merge/255660 -w -- --- D. Whit Morriss Developer, Juju Ecosystem Canonical USA -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
[Review Queue]
- ntp auto-peering: https://code.launchpad.net/~brad-marshall/charms/trusty/ntp/add-auto-peers/+merge/253132 nacked for a small test fix, but should be good to go otherwise kibana phat charm option: https://code.launchpad.net/~canonical-ci-engineering/charms/trusty/kibana/local-tarball/+merge/254638 +1 -w -- --- D. Whit Morriss Developer, Juju Ecosystem Canonical USA -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: presenting a poster on juju at PyCon 2015
so glad someone is going to pycon! tell the pyramid crew hello for me! Trying to explain juju can be tricky, doing it on a poster is even trickier. You've got lots of great info on your current one, but I would guess most folks at Pycon won't have any accurate idea of what juju can do or does. Thismay be a "less is more" situation due to lack of exposure. The dry erase idea is really good! Along those lines, a few thoughts on things pycon attendees might click on: - alot of folks at pycon will likely be standing up their infra w/ salt or ansible. Our support of charming w/ those might warrant a mention on the poster. - Key things folks might not know about juju * machine provisioning (w/ cpc images) across N clouds, kvm, containers *and* metal * Peer to peer service discovery and coordination * there is a portfolio of services to deploy and coordinate (charm ecosystem) * higher level tools for centralized system orchestration (esp. in python) - python juju client - juju deployer - Our testing tools are almost exclusively python (amulet, bundletester, etc) and our CI infra for charms and core is a pretty interesting project in itself. - a flow diagram for hook exec helps alot in understanding the the distributed state & execution machine that is deploying and coordinating w/ Juju The big question you will get is "Why juju vs. ". In my experience, usually the ??? will be something that juju can drive (CM, etc) and the answer is that juju gives you tools and a language (group of abstractions) to deal to reason about and manage your infrastructure from a service oriented perspective rather than from a machine oriented perspective. Compared to reasoning about configuration management, juju provides a way to create reference implementations of complex systems that can be discussed in a fairly natural way (environment, service, relationships, and now actions). IMO encapsulation is perhaps the most interesting property of modelling and deploying systems w/ juju. On your poster, I might replace "devops distilled" (loaded, jargony) w/ something like "service deployment and coordination encapsulated". Canonical's work around OpenStack and juju is a great example about how charms and juju can decompose a big problem to great effect for improved quality, and flexibility (plus it's a giant python project charmed in python). The idea of charming up one's fledgling startup or sideproject may not feel quite right (yet) to the average passerby, but folks dealing with slightly larger problems around distributing systems among co-workers and clients are likely to recognize the possible value here. anyway have a blast! can't wait to hear what all the pythonistas reflect back :) -w On Sun, Mar 29, 2015 at 1:08 AM, Eric Snow wrote: > Hey all, > > At the poster session (12 April) at PyCon 2015, I'll be presenting on > Juju. [1] I'm excited to be sharing juju with folks in the Python > community, particularly with the role that Python plays in dev ops as > well as in Juju. The first draft of my poster (big: 120cm x 120cm) is > pretty much done and I'd like to get some feedback. > > Please let me know what you think, what you like, and what I should > fix. Keep in mind that I haven't worked too closely with the charm > side of juju core and I've only written one simple charm myself. So > it's likely I have missed something important and also have a few > mistakes in there. I've attached a PDF and the ODG file is online. > [2] > > As well note that the presentation format is highly interactive and > amounts to me and one or more people standing around the poster > talking about it. Different conference-goers will stop by over the > course of 3-ish hours. I plan on laminating the poster so I can draw > on it with dry-erase markers (hence the relative sparseness). > > Thanks! > > -eric > > [1] https://us.pycon.org/2015/schedule/presentation/446/ > [2] https://drive.google.com/file/d/0B0aWHgOTQ1hNOTE4ei1tUldib1U > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > > -- --- D. Whit Morriss Developer, Juju Ecosystem Canonical USA -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
[Review Queue]
Testing additions for logstash-agent and squid-reverseproxy https://code.launchpad.net/~nicopace/charms/trusty/squid-reverseproxy/all-tests/+merge/251999 https://code.launchpad.net/~nicopace/charms/trusty/logstash-agent/all-tests/+merge/251311d Both nacked due to errors in testing. I took the time to investigate the errors and failures and attempted to fix the errors with logstash-agent and contacted the maintainers wrt dependency skew issues wrt squid-reverseproxy. I would like to state while adding tests to illuminate issues is good, adding tests to charms who's existing tests have errors makes for more and I believe pointless work for reviewers. I believe if you find a bug and want to commit a test, commit them to a personal namespace branch, not the charmstore. For basic stuff we can generate tests for based on charm metadata, we should automate tests and provide them (much like we provide charm proof), rather than adding additional burden to the review process in LOC added to charms. -w -- --- D. Whit Morriss Developer, Juju Ecosystem Canonical USA -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: People Need to Decide between Juju and Docker or how newbies need to thing ?
On Tue, Mar 3, 2015 at 4:38 PM, Vahric Muhtaryan wrote: > Hello All , > > I'm quite new Juju but like it and preparing to introduce it to our > customers for they can use it as a PaaS solution with our cloud offerings > Not understand or learn full functionality of Docker but like juju it can > deploy applications and manage the underlying OS level virtualisation layer > Both product looks like smiler , I would like to learn what juju users and > devs , charmers thinking about Docker and future of all > > Juju is not a replacement for docker or docker is not a replacement for juju. Both help you deliver software, and the similarities end about there. Docker has a very narrow focus, Juju a much wider one. Docker give you the following: - a way to package software - a way to run across a spectrum of linux platforms - an image based workflow for delivering software, - a way to launch software on a single machine. Juju gives you the following: - a distributed execution model for delivering, launching and scaling systems across many machines (virtual or metal) - a way to relate services to each and launch behavior when connecting and coordinating services - the ability to deploy software across a ever increasing number of IAAS providers and metal - a way to logically encapsulate the deployment of complex multi machine systems into a package like artifact. - a service oriented approach to managing infrastructure (vs. a machine orient paradign offered by CM systems) Juju is an excellent tool for delivering docker package solutions and orchestrating docker based workflows. My team has been working on a docker charm to encapsulate best practices with docker workflows and we would love input: https://github.com/chuckbutler/docker-charm http://chuckbutler.github.io/docker-charm/user/getting-started.html We also have been working a system for delivering and orchestrating kubernetes which provides some cluster management smarts atop docker: http://whitmo.github.io/bundle-kubernetes/ https://github.com/whitmo/kubernetes/blob/juju-getting-started/docs/getting-started-guides/juju.md I feel we are a little late to the party w/ docker and just starting to scratch the surface of what juju and docker can do together. As it turns out, they are very complementary. We'd love to get more folks trying this docker based system out and participating in their development. Please kick tire and tell us what you find! -w > o > > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > > -- --- D. Whit Morriss Developer, Juju Ecosystem Canonical USA -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
[Review Queue]
Reviewed the docker reference bundle.[1] This bundle sets up a 2 node docker cluster with flannel networking. Currently deploys great onto AWS, but is having some minor testing issues. I issued a pull request [2] to extend the documentation to have a more complete example of how dockering w/ juju works (add container, extract port and ip, open-port, curl service). Also discussed w/ Chuck a fuller example that shows how flannel facilitates inter-node container networking by deploy a 2 node cluster of tiny rss in docker containers that links to postgres in a docker container. One of the ttrss node would be talking to pg on a different unit. Anyway, fun to play with. I fired up the juju client inside of a container to do some juju in my juju. [3] I know Chuck and Bruzer would love more feedback so give it a whirl. -w [1] https://bugs.launchpad.net/charms/+bug/1413779 [2] https://github.com/mbruzek/docker-bundle/pull/4 [3] https://github.com/whitmo/jujubox -- --- D. Whit Morriss Developer, Juju Ecosystem Canonical USA -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
[Review Queue]
Reviewed the python rewrite of the jenkins charm. Generally looks good but needs some minor fixes for testing and an intermittent race condition. https://code.launchpad.net/~hopem/charms/trusty/jenkins/python-redux/+merge/245769 -w -- --- D. Whit Morriss Developer, Juju Ecosystem Canonical USA -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
[Review Queue]
- logstash forwarder (go-based agent): https://bugs.launchpad.net/charms/+bug/1375685 - mysql https://code.launchpad.net/~niedbalski/charms/precise/mysql/precise-syncup/+merge/244436 -w -- --- D. Whit Morriss Developer, Juju Ecosystem Canonical USA -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
[Review Queue]
* conn-check -1 needs ansible installed for running tests, otherwise looks good https://bugs.launchpad.net/charms/+bug/1392740 * etherpad-lite +1 https://bugs.launchpad.net/charms/+bug/1396643 * python-django +1 https://bugs.launchpad.net/charms/+bug/1387465 -w -- --- D. Whit Morriss Developer, Juju Ecosystem Canonical USA -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
[Review Queue]
Spent my rq time reviewing TVS's mongodb test refactors. https://code.launchpad.net/~tvansteenburgh/charms/trusty/mongodb/test-refactor/+merge/240740 Gave changes a +1. Couple notes: - old versions of amulet hanging around will ruin your morning. You want 1.8.1 or better. - tests run fine on 1.21beta2 -w -- --- D. Whit Morriss Developer, Juju Ecosystem Canonical USA -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
[Review Queue] Tez and Shoutcast
Today I reviewed a bundle and a charm, both from our esteemed Chuck Butler. The tez bundle sets up a framework for doing realtime high volume data processing using Yarn and hadoop: https://bugs.launchpad.net/charms/+bug/1383903. Shoutcast is the venerable internet radio server: https://bugs.launchpad.net/charms/+bug/1374085 Both worked great and got +1s from me. I did run into a couple juju related bumps working on ec2. First was forgetting to set my instance-type constraint and getting dinged for limited capacity on m1.smalls: agent-state-info: 'cannot run instances: We currently do not have sufficient m1.small capacity in the Availability Zone you requested (us-east-1d). Our system will be working on provisioning additional capacity. You can currently get m1.small capacity by not specifying an Availability Zone in your request or choosing us-east-1c, us-east-1a. (InsufficientInstanceCapacity)' The second was an error that popped up several times. These machine hung around in status, but blocked deploy until destroyed. Destroying service and machine cleared up the issue and allowed deployment. agent-state-info: 'cannot run instances: No default subnet for availability zone: ''us-east-1e''. (InvalidInput)' -w -- --- D. Whit Morriss Developer, Juju Ecosystem Canonical USA -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
[RQ]
Today: -1 ubuntu repository cache: https://bugs.launchpad.net/charms/+bug/1366834 This charm is a great example of python charming and bundles up a nice bit of support architecture for creating scalable repository mirrors. More work requested on tests and the autogenerated tests are broken. Looking forward to seeing this completed, has flagbearer potential. -1 pubphoto: https://code.launchpad.net/~jose/charms/precise/pubphoto/trunk Nacked for lack of tests (new charms regardless of series now must have tests) +1 elasticsearch metadata fix: https://code.launchpad.net/~jorge/charms/trusty/elasticsearch/remove-sets-metadata/+merge/234358 elasticsearch's tests do not run with bundletester, but I could deploy and confirm the change was good. Also issued a pr to improve the overview page on the rq itself. https://github.com/marcoceppi/review-queue/pull/8 -- --- D. Whit Morriss Developer, Juju Ecosystem Canonical USA -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
[Review Queue] Postgresql WAL-E, ES Bundle
Last week: *WAL-E*: I reviewed Stuart Bishop's WAL-E merge proposal which adds experimental support via the wal-e utility for shipping logs to a variety of blobs stores (Swift, s3, and azure's WABs). In general, the addition looks good, a fine addition to a fine charm. I requested some additions to the documentation. This week Stuart removed the charm from the queue citing that the charm was going in a possibly incompatible direction. This week: *Elasticsearch Bundle*: Jorge Castro has compile a fine bundle for elasticsearch and friends: logstash, kibana, and a demo of paramedic and bigdesk, ES dashboards. This bundle comes with a script to load up the dashboard plugins and the works of shakespeare so a user can play with querying es via kibana. The bundle is well documented and functions as advertised. gave it a +1. [0] *jujubackup*: (Vincenzo Di Somma <https://launchpad.net/%7Evds>*)* This charm installs as a subordinate to back up files to s3 or ubuntu one via duplicity. I rejected it based on needing an icon, copyright and tests. [1] *WildFly Bundle* (from Jorge Castro): Wildfly is a java web application runtime. The bundle sets up an haproxy, a wildfly container and a mysql db. A simple bundle, works as advertised, gave it a +1. [2] *Hortonworks Zookeeper* (from Amir Sanjar): The hortonwork package of apache zookeeper. Did not finish this review today, but passed back some requests based on charm proofing. [3] -w [0] https://code.launchpad.net/~jorge/charms/bundles/elasticsearch/bundle [1] https://bugs.launchpad.net/charms/+bug/1292492 [2] https://bugs.launchpad.net/charms/+bug/1292597 [3] https://bugs.launchpad.net/charms/+bug/1353197 -- ------- D. Whit Morriss Developer, Juju Ecosystem Canonical USA -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
