)]}'
{"releasenotes/notes/alembic-migrations-902b31edae7a5d7d.yaml":[{"author":{"_account_id":21722,"name":"Dharini Chandrasekar","email":"dharini.chandrasekar@intel.com","username":"dharinic"},"change_message_id":"8293d0e20e2cbc910e60a25b08323ee810559b02","unresolved":false,"context_lines":[{"line_number":2,"context_line":"upgrade:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The database migration engine used by Glance for database upgrades has been"},{"line_number":5,"context_line":"    changed from SQLAlchemy Migrate to Alembic in this release."},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"    * This has necessitated a change in the location and naming convention"},{"line_number":8,"context_line":"      for migration scripts.  Please consult the `Database Management`_"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3a461143_591022a9","line":5,"range":{"start_line":5,"start_character":17,"end_line":5,"end_character":35},"updated":"2017-02-02 02:04:15.000000000","message":"How about highlighting this?","commit_id":"ce5388f67acb36d86085da88599a1ac8fd2fdc12"},{"author":{"_account_id":21722,"name":"Dharini Chandrasekar","email":"dharini.chandrasekar@intel.com","username":"dharinic"},"change_message_id":"8293d0e20e2cbc910e60a25b08323ee810559b02","unresolved":false,"context_lines":[{"line_number":2,"context_line":"upgrade:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The database migration engine used by Glance for database upgrades has been"},{"line_number":5,"context_line":"    changed from SQLAlchemy Migrate to Alembic in this release."},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"    * This has necessitated a change in the location and naming convention"},{"line_number":8,"context_line":"      for migration scripts.  Please consult the `Database Management`_"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3a461143_7925de08","line":5,"range":{"start_line":5,"start_character":39,"end_line":5,"end_character":46},"updated":"2017-02-02 02:04:15.000000000","message":"and this.","commit_id":"ce5388f67acb36d86085da88599a1ac8fd2fdc12"},{"author":{"_account_id":8158,"name":"Hemanth Makkapati","email":"makstacker+osgerrit@gmail.com","username":"hemanth.makkapati"},"change_message_id":"fc9144c8afd3b9cba96ec6edc3fb776a5b6955aa","unresolved":false,"context_lines":[{"line_number":4,"context_line":"    The database migration engine used by Glance for database upgrades has been"},{"line_number":5,"context_line":"    changed from SQLAlchemy Migrate to Alembic in this release."},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"    * This has necessitated a change in the location and naming convention"},{"line_number":8,"context_line":"      for migration scripts.  Please consult the `Database Management`_"},{"line_number":9,"context_line":"      section of the Glance documentation for details."},{"line_number":10,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3a461143_b9f10698","line":7,"range":{"start_line":7,"start_character":44,"end_line":7,"end_character":74},"updated":"2017-02-02 01:38:17.000000000","message":"And testing?","commit_id":"ce5388f67acb36d86085da88599a1ac8fd2fdc12"},{"author":{"_account_id":12807,"name":"Steve Lewis (stevelle)","email":"stevelle@gmail.com","username":"stevelle"},"change_message_id":"45807d10fac285dd47bf1ac274b4be90bf90b720","unresolved":false,"context_lines":[{"line_number":4,"context_line":"    The database migration engine used by Glance for database upgrades has been"},{"line_number":5,"context_line":"    changed from SQLAlchemy Migrate to Alembic in this release."},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"    * This has necessitated a change in the location and naming convention"},{"line_number":8,"context_line":"      for migration scripts.  Please consult the `Database Management`_"},{"line_number":9,"context_line":"      section of the Glance documentation for details."},{"line_number":10,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3a461143_f9ec6e94","line":7,"range":{"start_line":7,"start_character":44,"end_line":7,"end_character":74},"in_reply_to":"3a461143_b9f10698","updated":"2017-02-02 01:48:19.000000000","message":"Is that an operator-facing concern? I might be missing something.","commit_id":"ce5388f67acb36d86085da88599a1ac8fd2fdc12"},{"author":{"_account_id":8158,"name":"Hemanth Makkapati","email":"makstacker+osgerrit@gmail.com","username":"hemanth.makkapati"},"change_message_id":"429a310dbc1d10f12ccbe9b5658f3ccbdc845bd0","unresolved":false,"context_lines":[{"line_number":4,"context_line":"    The database migration engine used by Glance for database upgrades has been"},{"line_number":5,"context_line":"    changed from SQLAlchemy Migrate to Alembic in this release."},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"    * This has necessitated a change in the location and naming convention"},{"line_number":8,"context_line":"      for migration scripts.  Please consult the `Database Management`_"},{"line_number":9,"context_line":"      section of the Glance documentation for details."},{"line_number":10,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3a461143_b980268d","line":7,"range":{"start_line":7,"start_character":44,"end_line":7,"end_character":74},"in_reply_to":"3a461143_f9ec6e94","updated":"2017-02-02 01:54:38.000000000","message":"You\u0027re right, it doesn\u0027t require a mention here. Ignore my comment.","commit_id":"ce5388f67acb36d86085da88599a1ac8fd2fdc12"},{"author":{"_account_id":21722,"name":"Dharini Chandrasekar","email":"dharini.chandrasekar@intel.com","username":"dharinic"},"change_message_id":"8293d0e20e2cbc910e60a25b08323ee810559b02","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"    * This has necessitated a change in the location and naming convention"},{"line_number":8,"context_line":"      for migration scripts.  Please consult the `Database Management`_"},{"line_number":9,"context_line":"      section of the Glance documentation for details."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"    * The change in migration engine has been undertaken in order to enable"},{"line_number":12,"context_line":"      zero-downtime database upgrades for Glance rolling upgrades in the Pike"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3a461143_b433cbf5","line":9,"updated":"2017-02-02 02:04:15.000000000","message":"Maybe just say a line about the new commands available for the database migrations?","commit_id":"ce5388f67acb36d86085da88599a1ac8fd2fdc12"},{"author":{"_account_id":8158,"name":"Hemanth Makkapati","email":"makstacker+osgerrit@gmail.com","username":"hemanth.makkapati"},"change_message_id":"fc9144c8afd3b9cba96ec6edc3fb776a5b6955aa","unresolved":false,"context_lines":[{"line_number":8,"context_line":"      for migration scripts.  Please consult the `Database Management`_"},{"line_number":9,"context_line":"      section of the Glance documentation for details."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"    * The change in migration engine has been undertaken in order to enable"},{"line_number":12,"context_line":"      zero-downtime database upgrades for Glance rolling upgrades in the Pike"},{"line_number":13,"context_line":"      release.  An **experimental** preview of zero-downtime database upgrades"},{"line_number":14,"context_line":"      is available in this release, but keep in mind that it is experimental"},{"line_number":15,"context_line":"      and hence not suitable for production systems.  Please consult the"},{"line_number":16,"context_line":"      `Database Management`_ section of the Glance documentation for details."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"    .. _`Database Management`: http://docs.openstack.org/developer/glance/db.html"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3a461143_b94826ce","line":16,"range":{"start_line":11,"start_character":6,"end_line":16,"end_character":77},"updated":"2017-02-02 01:38:17.000000000","message":"I don\u0027t know if this should go here or not but this work alone doesn\u0027t achieve rolling upgrades. It just addresses the database migration aspect of rolling upgrades. Also, should we mention that the database migration here is CI?","commit_id":"ce5388f67acb36d86085da88599a1ac8fd2fdc12"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"0c6ad7854ff092cf4cde268de342df26aedd8744","unresolved":false,"context_lines":[{"line_number":8,"context_line":"      for migration scripts.  Please consult the `Database Management`_"},{"line_number":9,"context_line":"      section of the Glance documentation for details."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"    * The change in migration engine has been undertaken in order to enable"},{"line_number":12,"context_line":"      zero-downtime database upgrades for Glance rolling upgrades in the Pike"},{"line_number":13,"context_line":"      release.  An **experimental** preview of zero-downtime database upgrades"},{"line_number":14,"context_line":"      is available in this release, but keep in mind that it is experimental"},{"line_number":15,"context_line":"      and hence not suitable for production systems.  Please consult the"},{"line_number":16,"context_line":"      `Database Management`_ section of the Glance documentation for details."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"    .. _`Database Management`: http://docs.openstack.org/developer/glance/db.html"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3a461143_191cda76","line":16,"range":{"start_line":11,"start_character":6,"end_line":16,"end_character":77},"in_reply_to":"3a461143_b94826ce","updated":"2017-02-02 01:58:43.000000000","message":"I\u0027ll rewrite to make it more clear that this is one aspect of rolling upgrades, not the whole thing.  The visibility changes patch already describes the CI migration, so I think it\u0027s ok to be vague here.","commit_id":"ce5388f67acb36d86085da88599a1ac8fd2fdc12"},{"author":{"_account_id":8158,"name":"Hemanth Makkapati","email":"makstacker+osgerrit@gmail.com","username":"hemanth.makkapati"},"change_message_id":"389403d73937cf7ef2bee55b97343beb51e8d074","unresolved":false,"context_lines":[{"line_number":37,"context_line":"          conversant in SQLAlchemy Migrate and are interested in comparing"},{"line_number":38,"context_line":"          it with a \"new-style\" Alembic migration script.  The Alembic"},{"line_number":39,"context_line":"          script, which is the one actually used to do the migration,"},{"line_number":40,"context_line":"          is ``ocata01_add_visibility_remove_is_public.py``.  (It is located"},{"line_number":41,"context_line":"          in the ``glance/db/sqlalchemy/alembic_migrations/versions``"},{"line_number":42,"context_line":"          directory.)"},{"line_number":43,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":5,"id":"3a461143_b6fd7a70","line":40,"range":{"start_line":40,"start_character":62,"end_line":40,"end_character":63},"updated":"2017-02-02 15:38:25.000000000","message":"Nit: why parenthesis?","commit_id":"27c43dd4c27123f368b743512b66de8a06aa3b42"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"55e047971cf5a532bddba3e9a78243bc34f1e686","unresolved":false,"context_lines":[{"line_number":37,"context_line":"          conversant in SQLAlchemy Migrate and are interested in comparing"},{"line_number":38,"context_line":"          it with a \"new-style\" Alembic migration script.  The Alembic"},{"line_number":39,"context_line":"          script, which is the one actually used to do the migration,"},{"line_number":40,"context_line":"          is ``ocata01_add_visibility_remove_is_public.py``.  (It is located"},{"line_number":41,"context_line":"          in the ``glance/db/sqlalchemy/alembic_migrations/versions``"},{"line_number":42,"context_line":"          directory.)"},{"line_number":43,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":5,"id":"3a461143_7125dcac","line":40,"range":{"start_line":40,"start_character":62,"end_line":40,"end_character":63},"in_reply_to":"3a461143_b6fd7a70","updated":"2017-02-02 15:47:07.000000000","message":"My thought was that the info is already present (first bullet point), so the parentheses indicate that this is a reminder.  But I\u0027m definitely over-thinking things! I\u0027ll remove them, and then it won\u0027t look so weird.","commit_id":"27c43dd4c27123f368b743512b66de8a06aa3b42"},{"author":{"_account_id":2537,"name":"Nikhil Komawar","email":"nik.komawar@gmail.com","username":"nikhil-komawar"},"change_message_id":"813c85f145bb1ede9ee61e2ed19ead1e2720a2ce","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"upgrade:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The database migration engine used by Glance for database upgrades has been"}],"source_content_type":"text/x-yaml","patch_set":6,"id":"3a461143_9f0b2e7d","line":1,"updated":"2017-02-02 17:48:14.000000000","message":"oh we need a note in the prelude for experimental rolling upgrades","commit_id":"5e58dd91dc8dd20f6ed533c5495cce6c9b06243f"},{"author":{"_account_id":2537,"name":"Nikhil Komawar","email":"nik.komawar@gmail.com","username":"nikhil-komawar"},"change_message_id":"813c85f145bb1ede9ee61e2ed19ead1e2720a2ce","unresolved":false,"context_lines":[{"line_number":5,"context_line":"    changed from *SQLAlchemy Migrate* to *Alembic* in this release."},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"    * This has necessitated a change in the location and naming convention"},{"line_number":8,"context_line":"      for migration scripts.  Please consult the `Database Management`_"},{"line_number":9,"context_line":"      section of the Glance documentation for full details.  Here\u0027s a brief"},{"line_number":10,"context_line":"      summary of the changes:"},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"      - A new directory, ``alembic_migrations``, has been introduced under"},{"line_number":13,"context_line":"        ``glance/db/sqlalchemy``. This directory is the home for all glance"}],"source_content_type":"text/x-yaml","patch_set":6,"id":"3a461143_e26739e8","line":10,"range":{"start_line":8,"start_character":30,"end_line":10,"end_character":29},"updated":"2017-02-02 17:48:14.000000000","message":"So, my note below has a suggestion for an alternate statement.","commit_id":"5e58dd91dc8dd20f6ed533c5495cce6c9b06243f"},{"author":{"_account_id":21722,"name":"Dharini Chandrasekar","email":"dharini.chandrasekar@intel.com","username":"dharinic"},"change_message_id":"85f10f1cafdf2abf39d540193084237d922c1202","unresolved":false,"context_lines":[{"line_number":9,"context_line":"      section of the Glance documentation for full details.  Here\u0027s a brief"},{"line_number":10,"context_line":"      summary of the changes:"},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"      - A new directory, ``alembic_migrations``, has been introduced under"},{"line_number":13,"context_line":"        ``glance/db/sqlalchemy``. This directory is the home for all glance"},{"line_number":14,"context_line":"        migrations from Ocata onward."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"      - Migration scripts reside in the ``versions`` subdirectory of the"},{"line_number":17,"context_line":"        ``alembic_migrations`` directory mentioned above."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"      - All database migrations up through the Liberty release are consolidated"},{"line_number":20,"context_line":"        into one Alembic migration script named ``liberty_initial``."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"      - Mitaka migrations are retained, but have been rewritten for Alembic"},{"line_number":23,"context_line":"        and named using the new naming convention.  (This is explained in the"},{"line_number":24,"context_line":"        `Database Management`_ section of the Glance documentation.)"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"      - All the glance manage db commands are changed appropriately. They now"},{"line_number":27,"context_line":"        use Alembic to perform operations such as ``version``, ``upgrade``,"}],"source_content_type":"text/x-yaml","patch_set":6,"id":"3a461143_fc5d2349","line":24,"range":{"start_line":12,"start_character":8,"end_line":24,"end_character":68},"updated":"2017-02-02 16:19:05.000000000","message":"Should we be talking about scripts to the operators? The location etc?","commit_id":"5e58dd91dc8dd20f6ed533c5495cce6c9b06243f"},{"author":{"_account_id":2537,"name":"Nikhil Komawar","email":"nik.komawar@gmail.com","username":"nikhil-komawar"},"change_message_id":"813c85f145bb1ede9ee61e2ed19ead1e2720a2ce","unresolved":false,"context_lines":[{"line_number":9,"context_line":"      section of the Glance documentation for full details.  Here\u0027s a brief"},{"line_number":10,"context_line":"      summary of the changes:"},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"      - A new directory, ``alembic_migrations``, has been introduced under"},{"line_number":13,"context_line":"        ``glance/db/sqlalchemy``. This directory is the home for all glance"},{"line_number":14,"context_line":"        migrations from Ocata onward."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"      - Migration scripts reside in the ``versions`` subdirectory of the"},{"line_number":17,"context_line":"        ``alembic_migrations`` directory mentioned above."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"      - All database migrations up through the Liberty release are consolidated"},{"line_number":20,"context_line":"        into one Alembic migration script named ``liberty_initial``."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"      - Mitaka migrations are retained, but have been rewritten for Alembic"},{"line_number":23,"context_line":"        and named using the new naming convention.  (This is explained in the"},{"line_number":24,"context_line":"        `Database Management`_ section of the Glance documentation.)"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"      - All the glance manage db commands are changed appropriately. They now"},{"line_number":27,"context_line":"        use Alembic to perform operations such as ``version``, ``upgrade``,"}],"source_content_type":"text/x-yaml","patch_set":6,"id":"3a461143_3f2cfaaa","line":24,"range":{"start_line":12,"start_character":8,"end_line":24,"end_character":68},"in_reply_to":"3a461143_fc5d2349","updated":"2017-02-02 17:48:14.000000000","message":"Yeah, I think we should skip this information here and be more explicit/detailed about the info in the dev docs.\n\nA note here can say that\n\n\"Developers and DevOps are strongly encouraged to read through the `Database Management`_ page for updates introduced in *Ocata*\"\n\nIn that page, we should be particular about Ocata updates and term them experimental until the release that declares them otherwise.","commit_id":"5e58dd91dc8dd20f6ed533c5495cce6c9b06243f"},{"author":{"_account_id":2537,"name":"Nikhil Komawar","email":"nik.komawar@gmail.com","username":"nikhil-komawar"},"change_message_id":"813c85f145bb1ede9ee61e2ed19ead1e2720a2ce","unresolved":false,"context_lines":[{"line_number":28,"context_line":"        ``sync`` and ``version_control``.  Hence, the \"old-style\" migration"},{"line_number":29,"context_line":"        scripts will no longer work with the Ocata glance manage db commands."},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"      - The \"old-style\" migration scripts have been retained in their current"},{"line_number":32,"context_line":"        directory, ``glance/db/sqlalchemy/migrate_repo/versions``, so that"},{"line_number":33,"context_line":"        interested operators can correlate them with the new migrations."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"        * In particular, the \"old-style\" script for the Ocata migration,"},{"line_number":36,"context_line":"          ``045_add_visibility.py`` is retained for operators who are"},{"line_number":37,"context_line":"          conversant in SQLAlchemy Migrate and are interested in comparing"},{"line_number":38,"context_line":"          it with a \"new-style\" Alembic migration script.  The Alembic"},{"line_number":39,"context_line":"          script, which is the one actually used to do the migration,"},{"line_number":40,"context_line":"          is ``ocata01_add_visibility_remove_is_public.py``.  It is located"},{"line_number":41,"context_line":"          in the ``glance/db/sqlalchemy/alembic_migrations/versions``"},{"line_number":42,"context_line":"          directory."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"      - Database versions are no longer numerical.  Instead, they are the"},{"line_number":45,"context_line":"        *revision ID* of the last migration applied on the database."}],"source_content_type":"text/x-yaml","patch_set":6,"id":"3a461143_42b64d3e","line":42,"range":{"start_line":31,"start_character":7,"end_line":42,"end_character":20},"updated":"2017-02-02 17:48:14.000000000","message":"This will go in the dev docs too.","commit_id":"5e58dd91dc8dd20f6ed533c5495cce6c9b06243f"},{"author":{"_account_id":12000,"name":"Ian Cordasco","email":"sigmavirus24@gmail.com","username":"sigmavirus24"},"change_message_id":"e029583d3aba7a64e6fc5963561a03f6dfa1201c","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"prelude: \u003e"},{"line_number":3,"context_line":"  - An **experimental** means to do zero-downtime database upgrades using an"},{"line_number":4,"context_line":"    expand-migrate-contract series of operations is available."},{"line_number":5,"context_line":"upgrade:"},{"line_number":6,"context_line":"  - |"}],"source_content_type":"text/x-yaml","patch_set":7,"id":"3a461143_b30d8139","line":3,"range":{"start_line":3,"start_character":4,"end_line":3,"end_character":65},"updated":"2017-02-02 18:38:28.000000000","message":"I would reword this to:\n\n    **Experimental** zero-downtime database upgrades ...\n\nRight now it\u0027s too wordy and confusing","commit_id":"d9d6521e7e7c8f649cab39b987f54617fb888ffa"},{"author":{"_account_id":2537,"name":"Nikhil Komawar","email":"nik.komawar@gmail.com","username":"nikhil-komawar"},"change_message_id":"0e47277db05faab0fda1cb66650f3ebf9af33a0a","unresolved":false,"context_lines":[{"line_number":10,"context_line":"    * This has necessitated a change in the location and naming convention for"},{"line_number":11,"context_line":"      migration scripts.  Developers, operators, and DevOps are strongly"},{"line_number":12,"context_line":"      encouraged to read through the `Database Management`_ section of the"},{"line_number":13,"context_line":"      Glance documentation for details of the changes introduced in the Ocata"},{"line_number":14,"context_line":"      release.  Here\u0027s a brief summary of the changes:"},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"      - All the ``glance manage db`` commands are changed appropriately to use"}],"source_content_type":"text/x-yaml","patch_set":7,"id":"3a461143_333191ed","line":13,"range":{"start_line":13,"start_character":72,"end_line":13,"end_character":77},"updated":"2017-02-02 18:40:53.000000000","message":"Bold font: **Ocata**","commit_id":"d9d6521e7e7c8f649cab39b987f54617fb888ffa"},{"author":{"_account_id":2537,"name":"Nikhil Komawar","email":"nik.komawar@gmail.com","username":"nikhil-komawar"},"change_message_id":"0e47277db05faab0fda1cb66650f3ebf9af33a0a","unresolved":false,"context_lines":[{"line_number":11,"context_line":"      migration scripts.  Developers, operators, and DevOps are strongly"},{"line_number":12,"context_line":"      encouraged to read through the `Database Management`_ section of the"},{"line_number":13,"context_line":"      Glance documentation for details of the changes introduced in the Ocata"},{"line_number":14,"context_line":"      release.  Here\u0027s a brief summary of the changes:"},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"      - All the ``glance manage db`` commands are changed appropriately to use"},{"line_number":17,"context_line":"        Alembic to perform operations such as ``version``, ``upgrade``,"}],"source_content_type":"text/x-yaml","patch_set":7,"id":"3a461143_732a3980","line":14,"range":{"start_line":14,"start_character":14,"end_line":14,"end_character":16},"updated":"2017-02-02 18:40:53.000000000","message":"femto nit, extra ws","commit_id":"d9d6521e7e7c8f649cab39b987f54617fb888ffa"},{"author":{"_account_id":2537,"name":"Nikhil Komawar","email":"nik.komawar@gmail.com","username":"nikhil-komawar"},"change_message_id":"0e47277db05faab0fda1cb66650f3ebf9af33a0a","unresolved":false,"context_lines":[{"line_number":15,"context_line":""},{"line_number":16,"context_line":"      - All the ``glance manage db`` commands are changed appropriately to use"},{"line_number":17,"context_line":"        Alembic to perform operations such as ``version``, ``upgrade``,"},{"line_number":18,"context_line":"        ``sync`` and ``version_control``.  Hence, the \"old-style\" migration"},{"line_number":19,"context_line":"        scripts will no longer work with the Ocata glance manage db commands."},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"      - Database versions are no longer numerical.  Instead, they are the"}],"source_content_type":"text/x-yaml","patch_set":7,"id":"3a461143_d3404d38","line":18,"range":{"start_line":18,"start_character":41,"end_line":18,"end_character":43},"updated":"2017-02-02 18:40:53.000000000","message":"extra ws","commit_id":"d9d6521e7e7c8f649cab39b987f54617fb888ffa"},{"author":{"_account_id":2537,"name":"Nikhil Komawar","email":"nik.komawar@gmail.com","username":"nikhil-komawar"},"change_message_id":"0e47277db05faab0fda1cb66650f3ebf9af33a0a","unresolved":false,"context_lines":[{"line_number":18,"context_line":"        ``sync`` and ``version_control``.  Hence, the \"old-style\" migration"},{"line_number":19,"context_line":"        scripts will no longer work with the Ocata glance manage db commands."},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"      - Database versions are no longer numerical.  Instead, they are the"},{"line_number":22,"context_line":"        *revision ID* of the last migration applied on the database."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"        * For example, the Liberty migration, which was version ``42`` under"}],"source_content_type":"text/x-yaml","patch_set":7,"id":"3a461143_73787990","line":21,"range":{"start_line":21,"start_character":50,"end_line":21,"end_character":52},"updated":"2017-02-02 18:40:53.000000000","message":"extra ws","commit_id":"d9d6521e7e7c8f649cab39b987f54617fb888ffa"},{"author":{"_account_id":2537,"name":"Nikhil Komawar","email":"nik.komawar@gmail.com","username":"nikhil-komawar"},"change_message_id":"0e47277db05faab0fda1cb66650f3ebf9af33a0a","unresolved":false,"context_lines":[{"line_number":22,"context_line":"        *revision ID* of the last migration applied on the database."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"        * For example, the Liberty migration, which was version ``42`` under"},{"line_number":25,"context_line":"          the old system, will now appear as ``liberty``.  The Mitaka"},{"line_number":26,"context_line":"          migrations ``43`` and ``44`` appear as ``mitaka01`` and ``mitaka02``,"},{"line_number":27,"context_line":"          respectively."},{"line_number":28,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":7,"id":"3a461143_335fd10f","line":25,"range":{"start_line":25,"start_character":57,"end_line":25,"end_character":59},"updated":"2017-02-02 18:40:53.000000000","message":"extra ws","commit_id":"d9d6521e7e7c8f649cab39b987f54617fb888ffa"},{"author":{"_account_id":2537,"name":"Nikhil Komawar","email":"nik.komawar@gmail.com","username":"nikhil-komawar"},"change_message_id":"0e47277db05faab0fda1cb66650f3ebf9af33a0a","unresolved":false,"context_lines":[{"line_number":27,"context_line":"          respectively."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"    * The change in migration engine has been undertaken in order to enable"},{"line_number":30,"context_line":"      zero-downtime database upgrades, which are part of the effort to"},{"line_number":31,"context_line":"      implement rolling upgrades for Glance (scheduled for the Pike release)."},{"line_number":32,"context_line":"      An **experimental** preview of zero-downtime database upgrades is"},{"line_number":33,"context_line":"      available in this release, but keep in mind that it is experimental and"}],"source_content_type":"text/x-yaml","patch_set":7,"id":"3a461143_d395ad88","line":30,"range":{"start_line":30,"start_character":45,"end_line":30,"end_character":48},"updated":"2017-02-02 18:40:53.000000000","message":"s/are/is","commit_id":"d9d6521e7e7c8f649cab39b987f54617fb888ffa"},{"author":{"_account_id":2537,"name":"Nikhil Komawar","email":"nik.komawar@gmail.com","username":"nikhil-komawar"},"change_message_id":"0e47277db05faab0fda1cb66650f3ebf9af33a0a","unresolved":false,"context_lines":[{"line_number":28,"context_line":""},{"line_number":29,"context_line":"    * The change in migration engine has been undertaken in order to enable"},{"line_number":30,"context_line":"      zero-downtime database upgrades, which are part of the effort to"},{"line_number":31,"context_line":"      implement rolling upgrades for Glance (scheduled for the Pike release)."},{"line_number":32,"context_line":"      An **experimental** preview of zero-downtime database upgrades is"},{"line_number":33,"context_line":"      available in this release, but keep in mind that it is experimental and"},{"line_number":34,"context_line":"      hence not suitable for production systems.  Please consult the `Database"}],"source_content_type":"text/x-yaml","patch_set":7,"id":"3a461143_739f99b4","line":31,"range":{"start_line":31,"start_character":63,"end_line":31,"end_character":67},"updated":"2017-02-02 18:40:53.000000000","message":"Bold font: **Pike**","commit_id":"d9d6521e7e7c8f649cab39b987f54617fb888ffa"},{"author":{"_account_id":12000,"name":"Ian Cordasco","email":"sigmavirus24@gmail.com","username":"sigmavirus24"},"change_message_id":"e029583d3aba7a64e6fc5963561a03f6dfa1201c","unresolved":false,"context_lines":[{"line_number":29,"context_line":"    * The change in migration engine has been undertaken in order to enable"},{"line_number":30,"context_line":"      zero-downtime database upgrades, which are part of the effort to"},{"line_number":31,"context_line":"      implement rolling upgrades for Glance (scheduled for the Pike release)."},{"line_number":32,"context_line":"      An **experimental** preview of zero-downtime database upgrades is"},{"line_number":33,"context_line":"      available in this release, but keep in mind that it is experimental and"},{"line_number":34,"context_line":"      hence not suitable for production systems.  Please consult the `Database"},{"line_number":35,"context_line":"      Management`_ section of the Glance documentation for details."}],"source_content_type":"text/x-yaml","patch_set":7,"id":"3a461143_f33d49bc","line":32,"range":{"start_line":32,"start_character":10,"end_line":32,"end_character":25},"updated":"2017-02-02 18:38:28.000000000","message":"this sentence is very experimental. Maybe remove this first one and emphasize the second one something like\n\n    A preview of zero-downtime ..., but it is **experimental** and **not supported for production systems**.","commit_id":"d9d6521e7e7c8f649cab39b987f54617fb888ffa"},{"author":{"_account_id":2537,"name":"Nikhil Komawar","email":"nik.komawar@gmail.com","username":"nikhil-komawar"},"change_message_id":"0e47277db05faab0fda1cb66650f3ebf9af33a0a","unresolved":false,"context_lines":[{"line_number":31,"context_line":"      implement rolling upgrades for Glance (scheduled for the Pike release)."},{"line_number":32,"context_line":"      An **experimental** preview of zero-downtime database upgrades is"},{"line_number":33,"context_line":"      available in this release, but keep in mind that it is experimental and"},{"line_number":34,"context_line":"      hence not suitable for production systems.  Please consult the `Database"},{"line_number":35,"context_line":"      Management`_ section of the Glance documentation for details."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"    .. _`Database Management`: http://docs.openstack.org/developer/glance/db.html"}],"source_content_type":"text/x-yaml","patch_set":7,"id":"3a461143_f3ab89d4","line":34,"range":{"start_line":34,"start_character":48,"end_line":34,"end_character":50},"updated":"2017-02-02 18:40:53.000000000","message":"extra ws","commit_id":"d9d6521e7e7c8f649cab39b987f54617fb888ffa"},{"author":{"_account_id":2537,"name":"Nikhil Komawar","email":"nik.komawar@gmail.com","username":"nikhil-komawar"},"change_message_id":"84714f431ae6ad321d0a068fc632d8861a84a3d8","unresolved":false,"context_lines":[{"line_number":30,"context_line":"      zero-downtime database upgrades, which are part of the effort to"},{"line_number":31,"context_line":"      implement rolling upgrades for Glance (scheduled for the Pike release)."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"        * A preview of zero-downtime database upgrades is available in this"},{"line_number":34,"context_line":"          release, but it is **experimental** and **not supported for for"},{"line_number":35,"context_line":"          production systems**.  Please consult the `Database Management`_"},{"line_number":36,"context_line":"          section of the Glance documentation for details."}],"source_content_type":"text/x-yaml","patch_set":8,"id":"3a461143_939ec505","line":33,"range":{"start_line":33,"start_character":5,"end_line":33,"end_character":8},"updated":"2017-02-02 18:54:09.000000000","message":"you have indentation error here, irrespective of where you want to place it","commit_id":"1c615391dd0941d2c020abc36dcbb9c34aab11a0"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"a7555b76f20f359e4a7f37315e710ed5eb0855b3","unresolved":false,"context_lines":[{"line_number":30,"context_line":"      zero-downtime database upgrades, which are part of the effort to"},{"line_number":31,"context_line":"      implement rolling upgrades for Glance (scheduled for the Pike release)."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"        * A preview of zero-downtime database upgrades is available in this"},{"line_number":34,"context_line":"          release, but it is **experimental** and **not supported for for"},{"line_number":35,"context_line":"          production systems**.  Please consult the `Database Management`_"},{"line_number":36,"context_line":"          section of the Glance documentation for details."}],"source_content_type":"text/x-yaml","patch_set":8,"id":"3a461143_5317fd53","line":33,"range":{"start_line":33,"start_character":5,"end_line":33,"end_character":8},"in_reply_to":"3a461143_939ec505","updated":"2017-02-02 18:56:35.000000000","message":"yep, thanks for catching that.","commit_id":"1c615391dd0941d2c020abc36dcbb9c34aab11a0"},{"author":{"_account_id":8158,"name":"Hemanth Makkapati","email":"makstacker+osgerrit@gmail.com","username":"hemanth.makkapati"},"change_message_id":"b24b60763a6280adb8b73c4eee424c2b9545c529","unresolved":false,"context_lines":[{"line_number":31,"context_line":"      implement rolling upgrades for Glance (scheduled for the Pike release)."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"        * A preview of zero-downtime database upgrades is available in this"},{"line_number":34,"context_line":"          release, but it is **experimental** and **not supported for for"},{"line_number":35,"context_line":"          production systems**.  Please consult the `Database Management`_"},{"line_number":36,"context_line":"          section of the Glance documentation for details."},{"line_number":37,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":9,"id":"3a461143_3355111d","line":34,"range":{"start_line":34,"start_character":70,"end_line":34,"end_character":73},"updated":"2017-02-02 18:57:07.000000000","message":"\u0027for\u0027 appears twice.","commit_id":"1d356415487e4b5ae08f746828e8389876626d1e"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"74c7276f8e238d77e58ef11f191ccf5a27e29ba5","unresolved":false,"context_lines":[{"line_number":31,"context_line":"      implement rolling upgrades for Glance (scheduled for the Pike release)."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"        * A preview of zero-downtime database upgrades is available in this"},{"line_number":34,"context_line":"          release, but it is **experimental** and **not supported for for"},{"line_number":35,"context_line":"          production systems**.  Please consult the `Database Management`_"},{"line_number":36,"context_line":"          section of the Glance documentation for details."},{"line_number":37,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":9,"id":"3a461143_ae80ba47","line":34,"range":{"start_line":34,"start_character":70,"end_line":34,"end_character":73},"in_reply_to":"3a461143_3355111d","updated":"2017-02-02 18:59:51.000000000","message":"Good catch, will get this.","commit_id":"1d356415487e4b5ae08f746828e8389876626d1e"},{"author":{"_account_id":12000,"name":"Ian Cordasco","email":"sigmavirus24@gmail.com","username":"sigmavirus24"},"change_message_id":"f703197eeab3aeba72f30638ba48fcfd8f9cf2bd","unresolved":false,"context_lines":[{"line_number":7,"context_line":"    The database migration engine used by Glance for database upgrades has been"},{"line_number":8,"context_line":"    changed from *SQLAlchemy Migrate* to *Alembic* in this release."},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"    * This has necessitated a change in the location and naming convention for"},{"line_number":11,"context_line":"      migration scripts.  Developers, operators, and DevOps are strongly"},{"line_number":12,"context_line":"      encouraged to read through the `Database Management`_ section of the"},{"line_number":13,"context_line":"      Glance documentation for details of the changes introduced in the Ocata"}],"source_content_type":"text/x-yaml","patch_set":10,"id":"3a461143_846cbe9d","line":10,"range":{"start_line":10,"start_character":11,"end_line":10,"end_character":14},"updated":"2017-02-02 19:24:32.000000000","message":"extra word","commit_id":"fb851b9ead8f177aa82c8b8188500411f27e00a9"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"051fd3a1ac211ee3b9b24ae6f749d2c3bf142e38","unresolved":false,"context_lines":[{"line_number":7,"context_line":"    The database migration engine used by Glance for database upgrades has been"},{"line_number":8,"context_line":"    changed from *SQLAlchemy Migrate* to *Alembic* in this release."},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"    * This has necessitated a change in the location and naming convention for"},{"line_number":11,"context_line":"      migration scripts.  Developers, operators, and DevOps are strongly"},{"line_number":12,"context_line":"      encouraged to read through the `Database Management`_ section of the"},{"line_number":13,"context_line":"      Glance documentation for details of the changes introduced in the Ocata"}],"source_content_type":"text/x-yaml","patch_set":10,"id":"3a461143_c47886fb","line":10,"range":{"start_line":10,"start_character":11,"end_line":10,"end_character":14},"in_reply_to":"3a461143_846cbe9d","updated":"2017-02-02 19:31:00.000000000","message":"No, this is the present perfect simple tense, indicating an action that is still going on, i.e., the change we\u0027ve made not only affects these scripts, but all scripts going forward.","commit_id":"fb851b9ead8f177aa82c8b8188500411f27e00a9"},{"author":{"_account_id":12000,"name":"Ian Cordasco","email":"sigmavirus24@gmail.com","username":"sigmavirus24"},"change_message_id":"f703197eeab3aeba72f30638ba48fcfd8f9cf2bd","unresolved":false,"context_lines":[{"line_number":13,"context_line":"      Glance documentation for details of the changes introduced in the Ocata"},{"line_number":14,"context_line":"      release.  Here\u0027s a brief summary of the changes:"},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"      - All the ``glance manage db`` commands are changed appropriately to use"},{"line_number":17,"context_line":"        Alembic to perform operations such as ``version``, ``upgrade``,"},{"line_number":18,"context_line":"        ``sync`` and ``version_control``.  Hence, the \"old-style\" migration"},{"line_number":19,"context_line":"        scripts will no longer work with the Ocata glance manage db commands."}],"source_content_type":"text/x-yaml","patch_set":10,"id":"3a461143_a467fab5","line":16,"range":{"start_line":16,"start_character":46,"end_line":16,"end_character":49},"updated":"2017-02-02 19:24:32.000000000","message":"were","commit_id":"fb851b9ead8f177aa82c8b8188500411f27e00a9"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"051fd3a1ac211ee3b9b24ae6f749d2c3bf142e38","unresolved":false,"context_lines":[{"line_number":13,"context_line":"      Glance documentation for details of the changes introduced in the Ocata"},{"line_number":14,"context_line":"      release.  Here\u0027s a brief summary of the changes:"},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"      - All the ``glance manage db`` commands are changed appropriately to use"},{"line_number":17,"context_line":"        Alembic to perform operations such as ``version``, ``upgrade``,"},{"line_number":18,"context_line":"        ``sync`` and ``version_control``.  Hence, the \"old-style\" migration"},{"line_number":19,"context_line":"        scripts will no longer work with the Ocata glance manage db commands."}],"source_content_type":"text/x-yaml","patch_set":10,"id":"3a461143_6459925b","line":16,"range":{"start_line":16,"start_character":46,"end_line":16,"end_character":49},"in_reply_to":"3a461143_a467fab5","updated":"2017-02-02 19:31:00.000000000","message":"Using present tense to be consistent with the other descriptions, plus, we\u0027re talking about what\u0027s happening *now* at the time of release.","commit_id":"fb851b9ead8f177aa82c8b8188500411f27e00a9"},{"author":{"_account_id":12000,"name":"Ian Cordasco","email":"sigmavirus24@gmail.com","username":"sigmavirus24"},"change_message_id":"f703197eeab3aeba72f30638ba48fcfd8f9cf2bd","unresolved":false,"context_lines":[{"line_number":16,"context_line":"      - All the ``glance manage db`` commands are changed appropriately to use"},{"line_number":17,"context_line":"        Alembic to perform operations such as ``version``, ``upgrade``,"},{"line_number":18,"context_line":"        ``sync`` and ``version_control``.  Hence, the \"old-style\" migration"},{"line_number":19,"context_line":"        scripts will no longer work with the Ocata glance manage db commands."},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"      - Database versions are no longer numerical.  Instead, they are the"},{"line_number":22,"context_line":"        *revision ID* of the last migration applied on the database."}],"source_content_type":"text/x-yaml","patch_set":10,"id":"3a461143_040feee1","line":19,"range":{"start_line":19,"start_character":16,"end_line":19,"end_character":30},"updated":"2017-02-02 19:24:32.000000000","message":"do not","commit_id":"fb851b9ead8f177aa82c8b8188500411f27e00a9"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"051fd3a1ac211ee3b9b24ae6f749d2c3bf142e38","unresolved":false,"context_lines":[{"line_number":16,"context_line":"      - All the ``glance manage db`` commands are changed appropriately to use"},{"line_number":17,"context_line":"        Alembic to perform operations such as ``version``, ``upgrade``,"},{"line_number":18,"context_line":"        ``sync`` and ``version_control``.  Hence, the \"old-style\" migration"},{"line_number":19,"context_line":"        scripts will no longer work with the Ocata glance manage db commands."},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"      - Database versions are no longer numerical.  Instead, they are the"},{"line_number":22,"context_line":"        *revision ID* of the last migration applied on the database."}],"source_content_type":"text/x-yaml","patch_set":10,"id":"3a461143_445e5646","line":19,"range":{"start_line":19,"start_character":16,"end_line":19,"end_character":30},"in_reply_to":"3a461143_040feee1","updated":"2017-02-02 19:31:00.000000000","message":"ok, you got me on this one.","commit_id":"fb851b9ead8f177aa82c8b8188500411f27e00a9"},{"author":{"_account_id":12000,"name":"Ian Cordasco","email":"sigmavirus24@gmail.com","username":"sigmavirus24"},"change_message_id":"f703197eeab3aeba72f30638ba48fcfd8f9cf2bd","unresolved":false,"context_lines":[{"line_number":26,"context_line":"          migrations ``43`` and ``44`` appear as ``mitaka01`` and ``mitaka02``,"},{"line_number":27,"context_line":"          respectively."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"    * The change in migration engine has been undertaken in order to enable"},{"line_number":30,"context_line":"      zero-downtime database upgrades, which are part of the effort to"},{"line_number":31,"context_line":"      implement rolling upgrades for Glance (scheduled for the Pike release)."},{"line_number":32,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":10,"id":"3a461143_c42b2632","line":29,"range":{"start_line":29,"start_character":37,"end_line":29,"end_character":45},"updated":"2017-02-02 19:24:32.000000000","message":"was","commit_id":"fb851b9ead8f177aa82c8b8188500411f27e00a9"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"051fd3a1ac211ee3b9b24ae6f749d2c3bf142e38","unresolved":false,"context_lines":[{"line_number":26,"context_line":"          migrations ``43`` and ``44`` appear as ``mitaka01`` and ``mitaka02``,"},{"line_number":27,"context_line":"          respectively."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"    * The change in migration engine has been undertaken in order to enable"},{"line_number":30,"context_line":"      zero-downtime database upgrades, which are part of the effort to"},{"line_number":31,"context_line":"      implement rolling upgrades for Glance (scheduled for the Pike release)."},{"line_number":32,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":10,"id":"3a461143_a4a53a48","line":29,"range":{"start_line":29,"start_character":37,"end_line":29,"end_character":45},"in_reply_to":"3a461143_c42b2632","updated":"2017-02-02 19:31:00.000000000","message":"present perfect simple again","commit_id":"fb851b9ead8f177aa82c8b8188500411f27e00a9"}]}