Activity log for bug #806241

Date Who What changed Old value New value Message
2011-07-05 23:00:50 Adam Gandelman bug added bug
2011-07-06 02:13:37 Kapil Thangavelu ensemble: status New Confirmed
2011-07-06 02:15:50 Kapil Thangavelu summary It should be possible to collocate service units It should be possible to deploy multiple units to a machine
2011-07-06 02:15:55 Kapil Thangavelu ensemble: importance Undecided High
2011-07-06 02:15:58 Kapil Thangavelu ensemble: milestone dublin
2011-07-07 19:29:03 Dave Walker bug added subscriber Dave Walker
2011-07-08 09:09:52 Nick Barcet bug added subscriber Nick Barcet
2011-07-09 06:07:28 Launchpad Janitor branch linked lp:~clint-fewbar/ensemble/reuse-machines
2011-07-19 15:26:05 Kapil Thangavelu ensemble: assignee Clint Byrum (clint-fewbar)
2011-08-11 03:07:51 Clint Byrum ensemble: assignee Clint Byrum (clint-fewbar)
2011-08-11 16:33:14 Clint Byrum ensemble: importance High Medium
2011-08-17 01:19:05 Kapil Thangavelu ensemble: milestone dublin
2011-09-04 00:05:07 Mark Russell bug added subscriber Mark Russell
2011-09-28 14:37:54 Nick Barcet bug added subscriber Juan L. Negron
2011-09-28 14:58:47 Dustin Kirkland  bug added subscriber Dustin Kirkland
2011-09-28 15:26:40 Robbie Williamson juju: importance Medium High
2011-09-28 15:58:31 Clint Byrum tags production
2011-09-28 17:39:38 James Troup bug added subscriber The Canonical Sysadmins
2011-09-30 01:05:57 Dustin Kirkland  summary It should be possible to deploy multiple units to a machine It should be possible to deploy multiple units to a machine (service colocation)
2011-10-01 00:51:41 Boris Devouge bug added subscriber Boris Devouge
2011-10-14 10:34:03 Kapil Thangavelu juju: milestone florence
2011-10-25 03:22:57 Kapil Thangavelu summary It should be possible to deploy multiple units to a machine (service colocation) It should be possible to deploy multiple units to a machine (unit placement)
2011-10-27 17:39:30 Jim Baker juju: assignee Jim Baker (jimbaker)
2011-10-31 20:51:41 Jim Baker juju: assignee Jim Baker (jimbaker)
2011-12-07 12:10:33 Mathias Leppich bug added subscriber Mathias Leppich
2011-12-13 10:30:00 Greg Franklin bug added subscriber Greg Franklin
2011-12-28 06:16:52 Kiall Mac Innes bug added subscriber Kiall Mac Innes
2012-02-03 11:19:06 Vincent Ladeuil bug added subscriber Vincent Ladeuil
2012-03-05 10:14:50 Robin Battey bug added subscriber Robin Battey
2012-03-16 23:24:05 Kapil Thangavelu juju: milestone florence galapagos
2012-04-29 01:19:21 Kapil Thangavelu juju: milestone galapagos honolulu
2012-06-10 20:16:10 Cody Krieger bug added subscriber Cody Krieger
2012-06-19 14:59:09 Luis Arias bug added subscriber Luis Arias
2012-07-04 04:14:36 René Schultz Madsen bug added subscriber René Schultz Madsen
2012-08-06 09:41:01 Dave Russell bug added subscriber Dave Russell
2012-08-24 05:21:19 Pablo Gonzalez bug added subscriber Pablo Gonzalez
2012-09-10 17:36:23 Clint Byrum juju: milestone 0.6 0.7
2012-09-10 17:36:28 Clint Byrum juju: milestone 0.7
2012-10-25 09:43:35 Clint Byrum bug task added juju-core
2012-10-25 09:43:42 Clint Byrum juju-core: status New Confirmed
2012-10-25 09:43:45 Clint Byrum juju-core: importance Undecided High
2012-12-05 03:32:45 Dave Cheney juju-core: milestone 2.0
2012-12-05 03:58:54 Cody Krieger removed subscriber Cody Krieger
2013-02-26 10:42:20 Marius B. Kotsbak bug added subscriber Marius B. Kotsbak
2013-03-05 10:48:10 Marius B. Kotsbak description If this is being tracked on another bug, I apologize in advance... It should be possible to collocate services on the same machine and optionally relate them to one another. This has a very valid use case with regards to openstack. Smaller deployments of only a handful of machines will likely have several (or potentially all) services running on the same machine, while larger deployments will typically isolate services to their own servers and relate them to other services like load balancers, caches, etc. Currently, the alternative is to develop formulas that deal with a specific set of services as one large service unit and take care of everything within hooks scripts. This is obviously not ideal and makes it difficult to scale. For example, I'm working on openstack formulas that currently require a minimum of 5 machines: - nova-compute - nova-cloud-controller - glance - rabbitmq - mysql It would be ideal if I could combine rabbitmq and mysql on the same machine as separate services. nova-cloud-controller is a work-around to this problem as it installs and configures nova-api, nova-schedule, nova-network and nova-objectstore. These should all be handled by separate formulas that relate to one another but currently that would require another 3 machines. glance is similar in that it sets up the glance-api and glance-registry servers as one unit. If this is being tracked on another bug, I apologize in advance... It should be possible to collocate services on the same machine and optionally relate them to one another. This has a very valid use case with regards to openstack. Smaller deployments of only a handful of machines will likely have several (or potentially all) services running on the same machine, while larger deployments will typically isolate services to their own servers and relate them to other services like load balancers, caches, etc. Currently, the alternative is to develop formulas that deal with a specific set of services as one large service unit and take care of everything within hooks scripts. This is obviously not ideal and makes it difficult to scale. For example, I'm working on openstack formulas that currently require a minimum of 5 machines: - nova-compute - nova-cloud-controller - glance - rabbitmq - mysql It would be ideal if I could combine rabbitmq and mysql on the same machine as separate services. nova-cloud-controller is a work-around to this problem as it installs and configures nova-api, nova-schedule, nova-network and nova-objectstore. These should all be handled by separate formulas that relate to one another but currently that would require another 3 machines. glance is similar in that it sets up the glance-api and glance-registry servers as one unit. WORKAROUND: use "jitsu deploy-to" and specify manually the machine to deploy to. Probably requires that charms are not incompatible and that they do not try to use the same ports (e.g. port 80).
2013-03-12 13:25:27 Kapil Thangavelu juju: milestone 0.8
2013-04-21 16:22:39 Marcus bug added subscriber Marcus
2013-06-07 13:57:27 Данило Шеган juju-core: status Confirmed Triaged
2013-07-02 16:18:35 Chris bug added subscriber Chris
2013-07-12 17:38:37 Logan McNaughton bug added subscriber Logan McNaughton
2013-09-11 21:46:51 Tim Penhey juju-core: status Triaged Fix Released
2013-09-11 21:47:06 Tim Penhey juju-core: milestone 2.0
2013-10-01 06:11:45 Mathias Leppich removed subscriber Mathias Leppich
2013-10-12 03:41:36 Curtis Hovey juju: status Confirmed Triaged
2013-10-25 19:52:40 Manoj Pattanaik juju: status Triaged Fix Released