)]}'
{"specs/kilo/containers-service.rst":[{"author":{"_account_id":7385,"name":"Thomas Herve","email":"therve@redhat.com","username":"therve"},"change_message_id":"49b69b4f0e94514e83d95976e3de309598749f2c","unresolved":false,"context_lines":[{"line_number":113,"context_line":"1. Create a container on a specified instance by using its guid."},{"line_number":114,"context_line":"2. Auto-create instances."},{"line_number":115,"context_line":"   2.1. Fill them sequentially until full."},{"line_number":116,"context_line":"   2.2. Remove them automatically when they become empty."},{"line_number":117,"context_line":""},{"line_number":118,"context_line":"The diagram below offers an overview of the system architecture. The OSC box"},{"line_number":119,"context_line":"indicates an OpenStack client, which will communicate with the Containers"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7ac7a964_981675a6","line":116,"updated":"2014-08-15 08:42:07.000000000","message":"This sounds a lot like orchestration. Should the container service use Heat instead of talking to Nova directly? The overall architecture is very similar to say, Trove, so the same arguments would apply IMHO.\n\nIf it\u0027s not the case, a section should be added to explain why it\u0027s not using Heat.","commit_id":"7ef90fb67c1bef6514e07d60e4961f486a24a2e9"},{"author":{"_account_id":668,"name":"Adrian Otto","email":"aotto@aotto.com","username":"aotto"},"change_message_id":"56b5af4a3f45a5d09c3fa5f7e751c9bbabbc6ce2","unresolved":false,"context_lines":[{"line_number":113,"context_line":"1. Create a container on a specified instance by using its guid."},{"line_number":114,"context_line":"2. Auto-create instances."},{"line_number":115,"context_line":"   2.1. Fill them sequentially until full."},{"line_number":116,"context_line":"   2.2. Remove them automatically when they become empty."},{"line_number":117,"context_line":""},{"line_number":118,"context_line":"The diagram below offers an overview of the system architecture. The OSC box"},{"line_number":119,"context_line":"indicates an OpenStack client, which will communicate with the Containers"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7ac7a964_c5c5483d","line":116,"in_reply_to":"7ac7a964_981675a6","updated":"2014-08-15 21:38:56.000000000","message":"Good catch. Yes, we will implement this using Heat. I can add some detail to make that clear.","commit_id":"7ef90fb67c1bef6514e07d60e4961f486a24a2e9"},{"author":{"_account_id":7385,"name":"Thomas Herve","email":"therve@redhat.com","username":"therve"},"change_message_id":"6189edd56deb0d0a862bed5f9aa61104819919c9","unresolved":false,"context_lines":[{"line_number":113,"context_line":"1. Create a container on a specified instance by using its guid."},{"line_number":114,"context_line":"2. Auto-create instances."},{"line_number":115,"context_line":"   2.1. Fill them sequentially until full."},{"line_number":116,"context_line":"   2.2. Remove them automatically when they become empty."},{"line_number":117,"context_line":""},{"line_number":118,"context_line":"The diagram below offers an overview of the system architecture. The OSC box"},{"line_number":119,"context_line":"indicates an OpenStack client, which will communicate with the Containers"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1abeadc6_2d06f7ce","line":116,"in_reply_to":"7ac7a964_c5c5483d","updated":"2014-08-19 13:29:44.000000000","message":"Cool thanks. That asks the question whether that spec should be in nova-specs though :).","commit_id":"7ef90fb67c1bef6514e07d60e4961f486a24a2e9"},{"author":{"_account_id":7385,"name":"Thomas Herve","email":"therve@redhat.com","username":"therve"},"change_message_id":"49b69b4f0e94514e83d95976e3de309598749f2c","unresolved":false,"context_lines":[{"line_number":209,"context_line":"The `Docker API:"},{"line_number":210,"context_line":"\u003chttps://docs.docker.com/reference/api/docker_remote_api_v1.13/\u003e`_"},{"line_number":211,"context_line":"will be used for the initial implementation, with these additions:"},{"line_number":212,"context_line":""},{"line_number":213,"context_line":"1. Support for the X-Auth-Project-Id HTTP request header to allow for"},{"line_number":214,"context_line":"   multi-tenant use."},{"line_number":215,"context_line":"2. Support for the X-Auth-Token HTTP request header to allow for authentication"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7ac7a964_389481e1","line":212,"updated":"2014-08-15 08:42:07.000000000","message":"It feels a bit weird to choose the Docker API, considering the service is talking about OpenVZ and LXC in the future. Is it close enough to OpenStack standards that we can directly use it? Is it good enough to actually be the v1 that we\u0027ll support for a while?","commit_id":"7ef90fb67c1bef6514e07d60e4961f486a24a2e9"},{"author":{"_account_id":5387,"name":"Andrew Melton","email":"andrew.melton@rackspace.com","username":"andrew-melton"},"change_message_id":"b2f8bdbc4403fb95b36ddf9b18f1581eddc9551f","unresolved":false,"context_lines":[{"line_number":209,"context_line":"The `Docker API:"},{"line_number":210,"context_line":"\u003chttps://docs.docker.com/reference/api/docker_remote_api_v1.13/\u003e`_"},{"line_number":211,"context_line":"will be used for the initial implementation, with these additions:"},{"line_number":212,"context_line":""},{"line_number":213,"context_line":"1. Support for the X-Auth-Project-Id HTTP request header to allow for"},{"line_number":214,"context_line":"   multi-tenant use."},{"line_number":215,"context_line":"2. Support for the X-Auth-Token HTTP request header to allow for authentication"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1abeadc6_2c68b086","line":212,"in_reply_to":"1abeadc6_2dbb57e6","updated":"2014-08-19 16:14:55.000000000","message":"This also concerns me. I don\u0027t think tying ourselves to an external API is a good idea. There is a ton of cruft in the Docker remote api: empty hashes, data type mismatches between rest endpoints for the same basic data (network ports), etc. Their REST endpoints may be a good start, but I think tying ourselves to their API and their data types is a bad idea.","commit_id":"7ef90fb67c1bef6514e07d60e4961f486a24a2e9"},{"author":{"_account_id":668,"name":"Adrian Otto","email":"aotto@aotto.com","username":"aotto"},"change_message_id":"56b5af4a3f45a5d09c3fa5f7e751c9bbabbc6ce2","unresolved":false,"context_lines":[{"line_number":209,"context_line":"The `Docker API:"},{"line_number":210,"context_line":"\u003chttps://docs.docker.com/reference/api/docker_remote_api_v1.13/\u003e`_"},{"line_number":211,"context_line":"will be used for the initial implementation, with these additions:"},{"line_number":212,"context_line":""},{"line_number":213,"context_line":"1. Support for the X-Auth-Project-Id HTTP request header to allow for"},{"line_number":214,"context_line":"   multi-tenant use."},{"line_number":215,"context_line":"2. Support for the X-Auth-Token HTTP request header to allow for authentication"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7ac7a964_c5e628b4","line":212,"in_reply_to":"7ac7a964_389481e1","updated":"2014-08-15 21:38:56.000000000","message":"Good question.\n\nIntegration with the backends (Docker, LXC, OpenVZ) can happen as back-end plug-ins to the Container Service, just like Docker and libswarm have pluggable backends today. In practice those are already served today using the current Docker API, so that may be sufficient as a consensus interface to use as our starting point.\n\nAre you aware of specific gaps that would justify having a few alternates? If so, we can address that by having a common base API, and make a few more narrow API\u0027s like the Docker one to address compatibility with tooling built to use one of the alternates.\n\nMy understanding is that neither OpenVZ or LXC have invested in a REST API yet, so it might make sense to just use the Docker one as a starting point, and see where we may need to adapt it.\n\nThe could operator should be given the option to use the container technology of their choice on the backend. That\u0027s why LXC and OpenVZ compatibility are each called out explicitly in the above list of use cases.","commit_id":"7ef90fb67c1bef6514e07d60e4961f486a24a2e9"},{"author":{"_account_id":7385,"name":"Thomas Herve","email":"therve@redhat.com","username":"therve"},"change_message_id":"6189edd56deb0d0a862bed5f9aa61104819919c9","unresolved":false,"context_lines":[{"line_number":209,"context_line":"The `Docker API:"},{"line_number":210,"context_line":"\u003chttps://docs.docker.com/reference/api/docker_remote_api_v1.13/\u003e`_"},{"line_number":211,"context_line":"will be used for the initial implementation, with these additions:"},{"line_number":212,"context_line":""},{"line_number":213,"context_line":"1. Support for the X-Auth-Project-Id HTTP request header to allow for"},{"line_number":214,"context_line":"   multi-tenant use."},{"line_number":215,"context_line":"2. Support for the X-Auth-Token HTTP request header to allow for authentication"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1abeadc6_2dbb57e6","line":212,"in_reply_to":"7ac7a964_c5e628b4","updated":"2014-08-19 13:29:44.000000000","message":"The main API I\u0027m wondering about is the image API. I don\u0027t know if we want to have that in the container service, or if we should delegate to glance.","commit_id":"7ef90fb67c1bef6514e07d60e4961f486a24a2e9"},{"author":{"_account_id":5387,"name":"Andrew Melton","email":"andrew.melton@rackspace.com","username":"andrew-melton"},"change_message_id":"b2f8bdbc4403fb95b36ddf9b18f1581eddc9551f","unresolved":false,"context_lines":[{"line_number":260,"context_line":"Contemplated features (in subsequent release cycles):"},{"line_number":261,"context_line":""},{"line_number":262,"context_line":"* Notify the user each time a Nova instance is created or deleted by the"},{"line_number":263,"context_line":"  Containers service."},{"line_number":264,"context_line":""},{"line_number":265,"context_line":""},{"line_number":266,"context_line":"Other end user impact"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1abeadc6_ec3cf8c1","line":263,"updated":"2014-08-19 16:14:55.000000000","message":"I think these may also be very useful notifications.\n\n* Notify the user each on CRUD of containers containing start and end notifications. (compute.container.create/delete/etc)\n* Notify user periodically of existence of container service managed containers (ex compute.container.exists","commit_id":"7ef90fb67c1bef6514e07d60e4961f486a24a2e9"},{"author":{"_account_id":7368,"name":"Thomas Maddox","email":"me@thomasem.net","username":"thomasm"},"change_message_id":"d984f063c3cee9727d96b297f4e1e409cbc0e19b","unresolved":false,"context_lines":[{"line_number":113,"context_line":"1. Create a container on a specified instance by using its guid."},{"line_number":114,"context_line":"2. Auto-create instances."},{"line_number":115,"context_line":"   2.1. Fill them sequentially until full."},{"line_number":116,"context_line":"   2.2. Remove them automatically when they become empty."},{"line_number":117,"context_line":""},{"line_number":118,"context_line":"The above orchestration will be implemented using Heat."},{"line_number":119,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"fa98f980_17b04cf3","line":116,"updated":"2014-09-02 16:15:09.000000000","message":"Do we want to reference any future plans, like specific things we want in Gantt here? Should we open blueprints/specs against Gantt for things like:\n- I want these guests to be next to each other or,\n- I want these guests away from each other (HA)\n\nJust curious. :)","commit_id":"bb7c920464341891b998785df9963d15981458ca"},{"author":{"_account_id":6434,"name":"keith-bray","email":"kebray@gmail.com","username":"keith-bray"},"change_message_id":"d7d0af908bcd4ff8377a0c92a903f6cc239c6b1f","unresolved":false,"context_lines":[{"line_number":115,"context_line":"   2.1. Fill them sequentially until full."},{"line_number":116,"context_line":"   2.2. Remove them automatically when they become empty."},{"line_number":117,"context_line":""},{"line_number":118,"context_line":"The above orchestration will be implemented using Heat."},{"line_number":119,"context_line":""},{"line_number":120,"context_line":"The diagram below offers an overview of the system architecture. The OSC box"},{"line_number":121,"context_line":"indicates an OpenStack client, which will communicate with the Containers"}],"source_content_type":"text/x-rst","patch_set":4,"id":"fa98f980_32e6fe15","line":118,"updated":"2014-09-04 02:52:25.000000000","message":"Just want to check:  Are you suggesting that in the absence of having Gantt that Heat should orchestrate 2.1. and 2.2 above?  I\u0027d suggest having a modified Nova scheduler performe 2.1. and 2.2.  Since the container service is a separate API, with separate scheduling needs, it seems sufficient to suggest that until scheduling consolidates to Gantt that an operator could/should run not only a separate Containers API from the Nova API, but also a separate Nova Control Plane w/modified scheduler.","commit_id":"bb7c920464341891b998785df9963d15981458ca"},{"author":{"_account_id":6434,"name":"keith-bray","email":"kebray@gmail.com","username":"keith-bray"},"change_message_id":"d7d0af908bcd4ff8377a0c92a903f6cc239c6b1f","unresolved":false,"context_lines":[{"line_number":200,"context_line":""},{"line_number":201,"context_line":"Data model impact"},{"line_number":202,"context_line":"-----------------"},{"line_number":203,"context_line":"For Nova, None. All new data planned will be in the Containers Service."},{"line_number":204,"context_line":""},{"line_number":205,"context_line":""},{"line_number":206,"context_line":"REST API impact"}],"source_content_type":"text/x-rst","patch_set":4,"id":"fa98f980_52ab8274","line":203,"updated":"2014-09-04 02:52:25.000000000","message":"Is there a good solution to accomplish this before Gantt is realized?  I\u0027m still learning about Gantt?  In the mean time, it seems modification directly to Nova scheduler may be the only way.  Data for scheduler (e.g. the map) could be stored in separate tables/DB to allow for clear separate from Nova code.  I\u0027m trying to assess if anyone has an idea how one could start work on this blueprint and provide a working prototype in absence of Gantt, or whether one would need to go help bring Gantt to fruition prior to realizing the implementation of this spec.","commit_id":"bb7c920464341891b998785df9963d15981458ca"},{"author":{"_account_id":6434,"name":"keith-bray","email":"kebray@gmail.com","username":"keith-bray"},"change_message_id":"d7d0af908bcd4ff8377a0c92a903f6cc239c6b1f","unresolved":false,"context_lines":[{"line_number":241,"context_line":""},{"line_number":242,"context_line":"* Need to authenticate against keystone using python-keystoneclient."},{"line_number":243,"context_line":"* A trust token from Nova will be needed in order for the Containers Service"},{"line_number":244,"context_line":"  to call the Nova API on behalf of a user."},{"line_number":245,"context_line":"* Limits must be implemented to control resource consumption in accordance with"},{"line_number":246,"context_line":"  quotas."},{"line_number":247,"context_line":"* Providing STDIO access may generate a considerable amount of network chatter"}],"source_content_type":"text/x-rst","patch_set":4,"id":"fa98f980_52f0e290","line":244,"updated":"2014-09-04 02:52:25.000000000","message":"I think if an operator runs a separate Nova control plane w/the Container API, then need for trust token goes away, acknowledging the downside of the operator having to run a second fleet of infrastructure.  However, this may be a more suitable incremental approach given some operators have yet to move to full Keystone v3 support.  We want everyone to move to and use Keystone v3, but I\u0027m thinking there is an incremental approach that will help further adoption of Container service by large public cloud operators.","commit_id":"bb7c920464341891b998785df9963d15981458ca"},{"author":{"_account_id":7232,"name":"Subbu Allamaraju","email":"subbu@subbu.org"},"change_message_id":"5d4efec8fee006b13823285a5ce155b106c1bdec","unresolved":false,"context_lines":[{"line_number":5,"context_line":" http://creativecommons.org/licenses/by/3.0/legalcode"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":8,"context_line":"Containers Service"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Launchpad blueprint:"}],"source_content_type":"text/x-rst","patch_set":5,"id":"7a8c0949_bf775f39","line":8,"updated":"2014-11-06 10:34:03.000000000","message":"Does this project actually make sense? We can accomplish some of these outcomes with, e.g. the Marathon framework, which has the added benefit of rescheduling containers as needed.","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":668,"name":"Adrian Otto","email":"aotto@aotto.com","username":"aotto"},"change_message_id":"6e7a1092749fd9ed34adf31c3a05c1cb8734c487","unresolved":false,"context_lines":[{"line_number":5,"context_line":" http://creativecommons.org/licenses/by/3.0/legalcode"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":8,"context_line":"Containers Service"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Launchpad blueprint:"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_2b9b3aca","line":8,"in_reply_to":"7a8c0949_bf775f39","updated":"2014-11-20 19:30:33.000000000","message":"I would like to lean more about this. Please include a reference to Marathon.","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"c93079db00f74f7a4bd5b180d030160e603ffc80","unresolved":false,"context_lines":[{"line_number":28,"context_line":"Problem description"},{"line_number":29,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":30,"context_line":"Container technology is rapidly gaining popularity as a way to bundle and"},{"line_number":31,"context_line":"deploy applications. By recognizing and adapting to this trend will position"},{"line_number":32,"context_line":"OpenStack to be useful not only to clouds that employ bare metal and virtual"},{"line_number":33,"context_line":"machine instances, but can remain competitive in offering container services"},{"line_number":34,"context_line":"as well."}],"source_content_type":"text/x-rst","patch_set":5,"id":"9aa7fdbe_fa959040","line":31,"updated":"2014-10-21 21:00:59.000000000","message":"s/By recognizing/Recognizing/","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":668,"name":"Adrian Otto","email":"aotto@aotto.com","username":"aotto"},"change_message_id":"6e7a1092749fd9ed34adf31c3a05c1cb8734c487","unresolved":false,"context_lines":[{"line_number":28,"context_line":"Problem description"},{"line_number":29,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":30,"context_line":"Container technology is rapidly gaining popularity as a way to bundle and"},{"line_number":31,"context_line":"deploy applications. By recognizing and adapting to this trend will position"},{"line_number":32,"context_line":"OpenStack to be useful not only to clouds that employ bare metal and virtual"},{"line_number":33,"context_line":"machine instances, but can remain competitive in offering container services"},{"line_number":34,"context_line":"as well."}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_0b467e4f","line":31,"in_reply_to":"9aa7fdbe_fa959040","updated":"2014-11-20 19:30:33.000000000","message":"Done","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"c93079db00f74f7a4bd5b180d030160e603ffc80","unresolved":false,"context_lines":[{"line_number":49,"context_line":"   Other environments may include local servers, dedicated servers, private"},{"line_number":50,"context_line":"   clouds, and public clouds. Switching environments requires passing database"},{"line_number":51,"context_line":"   connection strings by environment variables at the time a container starts"},{"line_number":52,"context_line":"   to allow the application to use the services available in each environement"},{"line_number":53,"context_line":"   without changing the container image."},{"line_number":54,"context_line":"3. Docker Compatibility. End-user has a Dockerfile used to build an application"},{"line_number":55,"context_line":"   with and its runtime environment and dependencies in a Docker container"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9aa7fdbe_1a917452","line":52,"updated":"2014-10-21 21:00:59.000000000","message":"s/environement/environment/","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":668,"name":"Adrian Otto","email":"aotto@aotto.com","username":"aotto"},"change_message_id":"6e7a1092749fd9ed34adf31c3a05c1cb8734c487","unresolved":false,"context_lines":[{"line_number":49,"context_line":"   Other environments may include local servers, dedicated servers, private"},{"line_number":50,"context_line":"   clouds, and public clouds. Switching environments requires passing database"},{"line_number":51,"context_line":"   connection strings by environment variables at the time a container starts"},{"line_number":52,"context_line":"   to allow the application to use the services available in each environement"},{"line_number":53,"context_line":"   without changing the container image."},{"line_number":54,"context_line":"3. Docker Compatibility. End-user has a Dockerfile used to build an application"},{"line_number":55,"context_line":"   with and its runtime environment and dependencies in a Docker container"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_8b5a6e28","line":52,"in_reply_to":"9aa7fdbe_1a917452","updated":"2014-11-20 19:30:33.000000000","message":"Done","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"c93079db00f74f7a4bd5b180d030160e603ffc80","unresolved":false,"context_lines":[{"line_number":52,"context_line":"   to allow the application to use the services available in each environement"},{"line_number":53,"context_line":"   without changing the container image."},{"line_number":54,"context_line":"3. Docker Compatibility. End-user has a Dockerfile used to build an application"},{"line_number":55,"context_line":"   with and its runtime environment and dependencies in a Docker container"},{"line_number":56,"context_line":"   image. They want an easy way to run the Docker resulting image on an"},{"line_number":57,"context_line":"   OpenStack cloud."},{"line_number":58,"context_line":"4. LXC Compatibility. End-user wants an easy way to remotely create multiple"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9aa7fdbe_3aa0f89e","line":55,"updated":"2014-10-21 21:00:59.000000000","message":"s/with and/and/g","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":668,"name":"Adrian Otto","email":"aotto@aotto.com","username":"aotto"},"change_message_id":"6e7a1092749fd9ed34adf31c3a05c1cb8734c487","unresolved":false,"context_lines":[{"line_number":52,"context_line":"   to allow the application to use the services available in each environement"},{"line_number":53,"context_line":"   without changing the container image."},{"line_number":54,"context_line":"3. Docker Compatibility. End-user has a Dockerfile used to build an application"},{"line_number":55,"context_line":"   with and its runtime environment and dependencies in a Docker container"},{"line_number":56,"context_line":"   image. They want an easy way to run the Docker resulting image on an"},{"line_number":57,"context_line":"   OpenStack cloud."},{"line_number":58,"context_line":"4. LXC Compatibility. End-user wants an easy way to remotely create multiple"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_6b570203","line":55,"in_reply_to":"9aa7fdbe_3aa0f89e","updated":"2014-11-20 19:30:33.000000000","message":"Done","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"c93079db00f74f7a4bd5b180d030160e603ffc80","unresolved":false,"context_lines":[{"line_number":110,"context_line":"projects. Until Gantt is ready for use by the Containers Service, we will"},{"line_number":111,"context_line":"implement only two provisioning schemes for containers:"},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"1. Create a container on a specified instance by using its guid."},{"line_number":114,"context_line":"2. Auto-create instances."},{"line_number":115,"context_line":"   2.1. Fill them sequentially until full."},{"line_number":116,"context_line":"   2.2. Remove them automatically when they become empty."}],"source_content_type":"text/x-rst","patch_set":5,"id":"9aa7fdbe_5a9bfc71","line":113,"updated":"2014-10-21 21:00:59.000000000","message":"By using what\u0027s GUID? The instance\u0027s UUID? In other words, the scheduler will just have a pool of instances that are allocated to place containers in?","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":668,"name":"Adrian Otto","email":"aotto@aotto.com","username":"aotto"},"change_message_id":"6e7a1092749fd9ed34adf31c3a05c1cb8734c487","unresolved":false,"context_lines":[{"line_number":110,"context_line":"projects. Until Gantt is ready for use by the Containers Service, we will"},{"line_number":111,"context_line":"implement only two provisioning schemes for containers:"},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"1. Create a container on a specified instance by using its guid."},{"line_number":114,"context_line":"2. Auto-create instances."},{"line_number":115,"context_line":"   2.1. Fill them sequentially until full."},{"line_number":116,"context_line":"   2.2. Remove them automatically when they become empty."}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_2b4dfa72","line":113,"in_reply_to":"9aa7fdbe_5a9bfc71","updated":"2014-11-20 19:30:33.000000000","message":"Done","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":7232,"name":"Subbu Allamaraju","email":"subbu@subbu.org"},"change_message_id":"5d4efec8fee006b13823285a5ce155b106c1bdec","unresolved":false,"context_lines":[{"line_number":113,"context_line":"1. Create a container on a specified instance by using its guid."},{"line_number":114,"context_line":"2. Auto-create instances."},{"line_number":115,"context_line":"   2.1. Fill them sequentially until full."},{"line_number":116,"context_line":"   2.2. Remove them automatically when they become empty."},{"line_number":117,"context_line":""},{"line_number":118,"context_line":"The above orchestration will be implemented using Heat."},{"line_number":119,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"7a8c0949_9ff543cd","line":116,"updated":"2014-11-06 10:34:03.000000000","message":"Why \"sequentially until full\"? Why not delegate it to a scheduler service?","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":668,"name":"Adrian Otto","email":"aotto@aotto.com","username":"aotto"},"change_message_id":"6e7a1092749fd9ed34adf31c3a05c1cb8734c487","unresolved":false,"context_lines":[{"line_number":113,"context_line":"1. Create a container on a specified instance by using its guid."},{"line_number":114,"context_line":"2. Auto-create instances."},{"line_number":115,"context_line":"   2.1. Fill them sequentially until full."},{"line_number":116,"context_line":"   2.2. Remove them automatically when they become empty."},{"line_number":117,"context_line":""},{"line_number":118,"context_line":"The above orchestration will be implemented using Heat."},{"line_number":119,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_eb33f2f3","line":116,"in_reply_to":"7a8c0949_9ff543cd","updated":"2014-11-20 19:30:33.000000000","message":"Done","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":7232,"name":"Subbu Allamaraju","email":"subbu@subbu.org"},"change_message_id":"5d4efec8fee006b13823285a5ce155b106c1bdec","unresolved":false,"context_lines":[{"line_number":115,"context_line":"   2.1. Fill them sequentially until full."},{"line_number":116,"context_line":"   2.2. Remove them automatically when they become empty."},{"line_number":117,"context_line":""},{"line_number":118,"context_line":"The above orchestration will be implemented using Heat."},{"line_number":119,"context_line":""},{"line_number":120,"context_line":"The diagram below offers an overview of the system architecture. The OSC box"},{"line_number":121,"context_line":"indicates an OpenStack client, which will communicate with the Containers"}],"source_content_type":"text/x-rst","patch_set":5,"id":"7a8c0949_7fcfb77f","line":118,"updated":"2014-11-06 10:34:03.000000000","message":"This requires some kind of hypervisor painting (such as host aggregates) for security reasons.","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":668,"name":"Adrian Otto","email":"aotto@aotto.com","username":"aotto"},"change_message_id":"6e7a1092749fd9ed34adf31c3a05c1cb8734c487","unresolved":false,"context_lines":[{"line_number":115,"context_line":"   2.1. Fill them sequentially until full."},{"line_number":116,"context_line":"   2.2. Remove them automatically when they become empty."},{"line_number":117,"context_line":""},{"line_number":118,"context_line":"The above orchestration will be implemented using Heat."},{"line_number":119,"context_line":""},{"line_number":120,"context_line":"The diagram below offers an overview of the system architecture. The OSC box"},{"line_number":121,"context_line":"indicates an OpenStack client, which will communicate with the Containers"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_cb3476e1","line":118,"in_reply_to":"7a8c0949_7fcfb77f","updated":"2014-11-20 19:30:33.000000000","message":"Done","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"c93079db00f74f7a4bd5b180d030160e603ffc80","unresolved":false,"context_lines":[{"line_number":123,"context_line":"instances if one with enough capacity to host the requested container is not"},{"line_number":124,"context_line":"already known to the Containers service. The containers service will maintain"},{"line_number":125,"context_line":"a database \"Map\" of containers, and what Nova instance each belongs to. Nova"},{"line_number":126,"context_line":"creates instances. Instances belong only to Nova, and contaienrs belong only"},{"line_number":127,"context_line":"to the Containers Service, and a related to a Nova instance. If the instance"},{"line_number":128,"context_line":"includes the agent software \"A\", then it may be included in the inventory of"},{"line_number":129,"context_line":"the Containers service. Instances that do not contain an agent may not interact"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9aa7fdbe_7a89a025","line":126,"updated":"2014-10-21 21:00:59.000000000","message":"s/contaienrs/containers/\n\nAlso, I kind of disagree that instances belong only to Nova. The instances technically belong to the project that launched the instance -- which, in the case of the containers service would be the Containers Service \"service user\".","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":668,"name":"Adrian Otto","email":"aotto@aotto.com","username":"aotto"},"change_message_id":"6e7a1092749fd9ed34adf31c3a05c1cb8734c487","unresolved":false,"context_lines":[{"line_number":123,"context_line":"instances if one with enough capacity to host the requested container is not"},{"line_number":124,"context_line":"already known to the Containers service. The containers service will maintain"},{"line_number":125,"context_line":"a database \"Map\" of containers, and what Nova instance each belongs to. Nova"},{"line_number":126,"context_line":"creates instances. Instances belong only to Nova, and contaienrs belong only"},{"line_number":127,"context_line":"to the Containers Service, and a related to a Nova instance. If the instance"},{"line_number":128,"context_line":"includes the agent software \"A\", then it may be included in the inventory of"},{"line_number":129,"context_line":"the Containers service. Instances that do not contain an agent may not interact"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_cb0d5637","line":126,"in_reply_to":"9aa7fdbe_7a89a025","updated":"2014-11-20 19:30:33.000000000","message":"Done","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"c93079db00f74f7a4bd5b180d030160e603ffc80","unresolved":false,"context_lines":[{"line_number":124,"context_line":"already known to the Containers service. The containers service will maintain"},{"line_number":125,"context_line":"a database \"Map\" of containers, and what Nova instance each belongs to. Nova"},{"line_number":126,"context_line":"creates instances. Instances belong only to Nova, and contaienrs belong only"},{"line_number":127,"context_line":"to the Containers Service, and a related to a Nova instance. If the instance"},{"line_number":128,"context_line":"includes the agent software \"A\", then it may be included in the inventory of"},{"line_number":129,"context_line":"the Containers service. Instances that do not contain an agent may not interact"},{"line_number":130,"context_line":"with the Containers Service, and can be controlled only by a Nova virt driver."}],"source_content_type":"text/x-rst","patch_set":5,"id":"9aa7fdbe_9a8c8437","line":127,"updated":"2014-10-21 21:00:59.000000000","message":"s/a related to a Nova instance/run within a Nova instance/","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":668,"name":"Adrian Otto","email":"aotto@aotto.com","username":"aotto"},"change_message_id":"6e7a1092749fd9ed34adf31c3a05c1cb8734c487","unresolved":false,"context_lines":[{"line_number":124,"context_line":"already known to the Containers service. The containers service will maintain"},{"line_number":125,"context_line":"a database \"Map\" of containers, and what Nova instance each belongs to. Nova"},{"line_number":126,"context_line":"creates instances. Instances belong only to Nova, and contaienrs belong only"},{"line_number":127,"context_line":"to the Containers Service, and a related to a Nova instance. If the instance"},{"line_number":128,"context_line":"includes the agent software \"A\", then it may be included in the inventory of"},{"line_number":129,"context_line":"the Containers service. Instances that do not contain an agent may not interact"},{"line_number":130,"context_line":"with the Containers Service, and can be controlled only by a Nova virt driver."}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_ab12ca55","line":127,"in_reply_to":"9aa7fdbe_9a8c8437","updated":"2014-11-20 19:30:33.000000000","message":"Done","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"c93079db00f74f7a4bd5b180d030160e603ffc80","unresolved":false,"context_lines":[{"line_number":182,"context_line":"Design Principles"},{"line_number":183,"context_line":"-----------------"},{"line_number":184,"context_line":"1. Leverage existing OpenStack projects for what they are good at. Do not"},{"line_number":185,"context_line":"   duplicate funcitonality, or copy code that can be otherwise accessed through"},{"line_number":186,"context_line":"   API calls."},{"line_number":187,"context_line":"2. Keep modifications to Nova to a minimum."},{"line_number":188,"context_line":"3. Make the user experince for end users simple and familiar."}],"source_content_type":"text/x-rst","patch_set":5,"id":"9aa7fdbe_ba830803","line":185,"updated":"2014-10-21 21:00:59.000000000","message":"s/funcitonality/functionality/","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":668,"name":"Adrian Otto","email":"aotto@aotto.com","username":"aotto"},"change_message_id":"6e7a1092749fd9ed34adf31c3a05c1cb8734c487","unresolved":false,"context_lines":[{"line_number":182,"context_line":"Design Principles"},{"line_number":183,"context_line":"-----------------"},{"line_number":184,"context_line":"1. Leverage existing OpenStack projects for what they are good at. Do not"},{"line_number":185,"context_line":"   duplicate funcitonality, or copy code that can be otherwise accessed through"},{"line_number":186,"context_line":"   API calls."},{"line_number":187,"context_line":"2. Keep modifications to Nova to a minimum."},{"line_number":188,"context_line":"3. Make the user experince for end users simple and familiar."}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_2b825a52","line":185,"in_reply_to":"9aa7fdbe_ba830803","updated":"2014-11-20 19:30:33.000000000","message":"Done","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"c93079db00f74f7a4bd5b180d030160e603ffc80","unresolved":false,"context_lines":[{"line_number":185,"context_line":"   duplicate funcitonality, or copy code that can be otherwise accessed through"},{"line_number":186,"context_line":"   API calls."},{"line_number":187,"context_line":"2. Keep modifications to Nova to a minimum."},{"line_number":188,"context_line":"3. Make the user experince for end users simple and familiar."},{"line_number":189,"context_line":"4. Allow for implementation of all features containers are intended to offer."},{"line_number":190,"context_line":""},{"line_number":191,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"9aa7fdbe_da860c13","line":188,"updated":"2014-10-21 21:00:59.000000000","message":"s/experince/experience/","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":668,"name":"Adrian Otto","email":"aotto@aotto.com","username":"aotto"},"change_message_id":"6e7a1092749fd9ed34adf31c3a05c1cb8734c487","unresolved":false,"context_lines":[{"line_number":185,"context_line":"   duplicate funcitonality, or copy code that can be otherwise accessed through"},{"line_number":186,"context_line":"   API calls."},{"line_number":187,"context_line":"2. Keep modifications to Nova to a minimum."},{"line_number":188,"context_line":"3. Make the user experince for end users simple and familiar."},{"line_number":189,"context_line":"4. Allow for implementation of all features containers are intended to offer."},{"line_number":190,"context_line":""},{"line_number":191,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_ab956a89","line":188,"in_reply_to":"9aa7fdbe_da860c13","updated":"2014-11-20 19:30:33.000000000","message":"Done","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"c93079db00f74f7a4bd5b180d030160e603ffc80","unresolved":false,"context_lines":[{"line_number":186,"context_line":"   API calls."},{"line_number":187,"context_line":"2. Keep modifications to Nova to a minimum."},{"line_number":188,"context_line":"3. Make the user experince for end users simple and familiar."},{"line_number":189,"context_line":"4. Allow for implementation of all features containers are intended to offer."},{"line_number":190,"context_line":""},{"line_number":191,"context_line":""},{"line_number":192,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9aa7fdbe_fa7cb022","line":189,"updated":"2014-10-21 21:00:59.000000000","message":"++ on all four above design principles.","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"c93079db00f74f7a4bd5b180d030160e603ffc80","unresolved":false,"context_lines":[{"line_number":231,"context_line":"The scope of the full API will cause this spec to be too long to review, so"},{"line_number":232,"context_line":"the intent is to deal with the specific API design as a series of Gerrit"},{"line_number":233,"context_line":"reviews that submit API code as Not Implemented stubs with docstrings that"},{"line_number":234,"context_line":"clearly document the design, so allow for approval, and further implementation."},{"line_number":235,"context_line":""},{"line_number":236,"context_line":"Security impact"},{"line_number":237,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9aa7fdbe_1a78942a","line":234,"updated":"2014-10-21 21:00:59.000000000","message":"Fair enough.","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"c93079db00f74f7a4bd5b180d030160e603ffc80","unresolved":false,"context_lines":[{"line_number":236,"context_line":"Security impact"},{"line_number":237,"context_line":"---------------"},{"line_number":238,"context_line":"Because Nova will not be changed, there should be no security impacts to Nova."},{"line_number":239,"context_line":"The Containers Serivce implementation, will have the following security related"},{"line_number":240,"context_line":"issues:"},{"line_number":241,"context_line":""},{"line_number":242,"context_line":"* Need to authenticate against keystone using python-keystoneclient."}],"source_content_type":"text/x-rst","patch_set":5,"id":"9aa7fdbe_3a77183c","line":239,"updated":"2014-10-21 21:00:59.000000000","message":"s/Serivce/Service/","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":668,"name":"Adrian Otto","email":"aotto@aotto.com","username":"aotto"},"change_message_id":"6e7a1092749fd9ed34adf31c3a05c1cb8734c487","unresolved":false,"context_lines":[{"line_number":236,"context_line":"Security impact"},{"line_number":237,"context_line":"---------------"},{"line_number":238,"context_line":"Because Nova will not be changed, there should be no security impacts to Nova."},{"line_number":239,"context_line":"The Containers Serivce implementation, will have the following security related"},{"line_number":240,"context_line":"issues:"},{"line_number":241,"context_line":""},{"line_number":242,"context_line":"* Need to authenticate against keystone using python-keystoneclient."}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_4bec062a","line":239,"in_reply_to":"9aa7fdbe_3a77183c","updated":"2014-11-20 19:30:33.000000000","message":"Done","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"c93079db00f74f7a4bd5b180d030160e603ffc80","unresolved":false,"context_lines":[{"line_number":246,"context_line":"  quotas."},{"line_number":247,"context_line":"* Providing STDIO access may generate a considerable amount of network chatter"},{"line_number":248,"context_line":"  between containers and clients through the relay. This could lead to"},{"line_number":249,"context_line":"  bandwidth congestion at the relyays, or API nodes. An approach similar to"},{"line_number":250,"context_line":"  how we handle serial console access today will need to be considered to"},{"line_number":251,"context_line":"  mitigate this concern."},{"line_number":252,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"9aa7fdbe_5a721c4a","line":249,"updated":"2014-10-21 21:00:59.000000000","message":"s/relyays/relays/","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":668,"name":"Adrian Otto","email":"aotto@aotto.com","username":"aotto"},"change_message_id":"6e7a1092749fd9ed34adf31c3a05c1cb8734c487","unresolved":false,"context_lines":[{"line_number":246,"context_line":"  quotas."},{"line_number":247,"context_line":"* Providing STDIO access may generate a considerable amount of network chatter"},{"line_number":248,"context_line":"  between containers and clients through the relay. This could lead to"},{"line_number":249,"context_line":"  bandwidth congestion at the relyays, or API nodes. An approach similar to"},{"line_number":250,"context_line":"  how we handle serial console access today will need to be considered to"},{"line_number":251,"context_line":"  mitigate this concern."},{"line_number":252,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_ebe69243","line":249,"in_reply_to":"9aa7fdbe_5a721c4a","updated":"2014-11-20 19:30:33.000000000","message":"Done","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"c93079db00f74f7a4bd5b180d030160e603ffc80","unresolved":false,"context_lines":[{"line_number":258,"context_line":"  escape the constraints of the container and potentially access other"},{"line_number":259,"context_line":"  resources on the host, including contents of other containers."},{"line_number":260,"context_line":"* Output of processes may be persisted by the containers service in order to"},{"line_number":261,"context_line":"  allow asynchronous sollection of exit status, and terminal output. Such"},{"line_number":262,"context_line":"  content may include sensitive information. Features may be added to mitgate"},{"line_number":263,"context_line":"  the risk of this data being replicated in log messages, including errors."},{"line_number":264,"context_line":"* Creating containers usually requires root access. This means that the Agent"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9aa7fdbe_7a90c043","line":261,"updated":"2014-10-21 21:00:59.000000000","message":"s/sollection/collection/","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"c93079db00f74f7a4bd5b180d030160e603ffc80","unresolved":false,"context_lines":[{"line_number":274,"context_line":"Contemplated features (in subsequent release cycles):"},{"line_number":275,"context_line":""},{"line_number":276,"context_line":"* Notify the user each time a Nova instance is created or deleted by the"},{"line_number":277,"context_line":"  Containers service."},{"line_number":278,"context_line":"* Notify the user each on CRUD of containers containing start and end"},{"line_number":279,"context_line":"  notifications. (compute.container.create/delete/etc)"},{"line_number":280,"context_line":"* Notify user periodically of existence of container service managed"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9aa7fdbe_9a93a44e","line":277,"updated":"2014-10-21 21:00:59.000000000","message":"Notify which user? The cloud operator that is running the container service?","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":668,"name":"Adrian Otto","email":"aotto@aotto.com","username":"aotto"},"change_message_id":"6e7a1092749fd9ed34adf31c3a05c1cb8734c487","unresolved":false,"context_lines":[{"line_number":274,"context_line":"Contemplated features (in subsequent release cycles):"},{"line_number":275,"context_line":""},{"line_number":276,"context_line":"* Notify the user each time a Nova instance is created or deleted by the"},{"line_number":277,"context_line":"  Containers service."},{"line_number":278,"context_line":"* Notify the user each on CRUD of containers containing start and end"},{"line_number":279,"context_line":"  notifications. (compute.container.create/delete/etc)"},{"line_number":280,"context_line":"* Notify user periodically of existence of container service managed"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_8b5b4ef5","line":277,"in_reply_to":"9aa7fdbe_9a93a44e","updated":"2014-11-20 19:30:33.000000000","message":"Done","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"c93079db00f74f7a4bd5b180d030160e603ffc80","unresolved":false,"context_lines":[{"line_number":339,"context_line":"1. Agent"},{"line_number":340,"context_line":"2. Relay"},{"line_number":341,"context_line":"3. API Service"},{"line_number":342,"context_line":"4. IO Relays"},{"line_number":343,"context_line":""},{"line_number":344,"context_line":""},{"line_number":345,"context_line":"Dependencies"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9aa7fdbe_ba9a2861","line":342,"updated":"2014-10-21 21:00:59.000000000","message":"To be completely honest, I think each of the above would likely deserve their own nova-specs specification that would include some details about the proposed implementation. I know this spec is more about the idea of a containers service, though, so I\u0027m going to try not to get hung up on that :)","commit_id":"810c655291e4956fc1ecd958ab3ce1977f522cb0"}]}
