)]}'
{"playbooks/roles/bifrost-configdrives-dynamic/README.md":[{"author":{"_account_id":13997,"name":"SHIGEMATSU Mitsuhiro","email":"shigematsu.mitsuhiro@lab.ntt.co.jp","username":"pshige"},"change_message_id":"b12bb238e73fdbc70cdad4116df86c98bc1ba985","unresolved":false,"context_lines":[{"line_number":16,"context_line":"Additional key variables are:"},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"addressing_mode: If defined and set to a value of \"dhcp\", this role sets the primary interface to utilize DHCP."},{"line_number":19,"context_line":"ipv4_subnet_mask:  This is the subnet mask(e.g. 255.255.255.0 or similar) that matches the static addressing which desires to be imprinted into the configuraiton drive."},{"line_number":20,"context_line":"ipv4_gateway: This is the IPv4 defaut router address with-in the IPv4 subnet being utilized for IP addresses for the nodes being deployed."},{"line_number":21,"context_line":"node_default_network_interface: This is the default network interface with-in the nodes to be deployed which the new IP configuration will be applied to.  Note: This is likely to be deprecated and removed in the future as Bifrost will likely change methods utilized to include networking configuration into the configuration drive sufficiently that this should no longer be required."},{"line_number":22,"context_line":"ipv4_nameserver: Defines the IPv4 Nameserver to configure the node with initially in order to support name resolution."}],"source_content_type":"text/x-gfm","patch_set":3,"id":"3afb71cf_86d8ed54","line":19,"updated":"2015-06-07 07:22:14.000000000","message":"s/configuraiton/configuration/","commit_id":"37d8e9b2f177632ba958396bc16e17b309ad8d92"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"408558127a37311dee9c7bf8272eb0a5b444eef4","unresolved":false,"context_lines":[{"line_number":16,"context_line":"Additional key variables are:"},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"addressing_mode: If defined and set to a value of \"dhcp\", this role sets the primary interface to utilize DHCP."},{"line_number":19,"context_line":"ipv4_subnet_mask:  This is the subnet mask(e.g. 255.255.255.0 or similar) that matches the static addressing which desires to be imprinted into the configuraiton drive."},{"line_number":20,"context_line":"ipv4_gateway: This is the IPv4 defaut router address with-in the IPv4 subnet being utilized for IP addresses for the nodes being deployed."},{"line_number":21,"context_line":"node_default_network_interface: This is the default network interface with-in the nodes to be deployed which the new IP configuration will be applied to.  Note: This is likely to be deprecated and removed in the future as Bifrost will likely change methods utilized to include networking configuration into the configuration drive sufficiently that this should no longer be required."},{"line_number":22,"context_line":"ipv4_nameserver: Defines the IPv4 Nameserver to configure the node with initially in order to support name resolution."}],"source_content_type":"text/x-gfm","patch_set":3,"id":"3afb71cf_a1049049","line":19,"in_reply_to":"3afb71cf_86d8ed54","updated":"2015-06-09 19:16:20.000000000","message":"Good catch, Thank you!  I kind of wonder what planet my brain was on when I was typing it since I consistently misspelled it.","commit_id":"37d8e9b2f177632ba958396bc16e17b309ad8d92"},{"author":{"_account_id":13997,"name":"SHIGEMATSU Mitsuhiro","email":"shigematsu.mitsuhiro@lab.ntt.co.jp","username":"pshige"},"change_message_id":"b12bb238e73fdbc70cdad4116df86c98bc1ba985","unresolved":false,"context_lines":[{"line_number":17,"context_line":""},{"line_number":18,"context_line":"addressing_mode: If defined and set to a value of \"dhcp\", this role sets the primary interface to utilize DHCP."},{"line_number":19,"context_line":"ipv4_subnet_mask:  This is the subnet mask(e.g. 255.255.255.0 or similar) that matches the static addressing which desires to be imprinted into the configuraiton drive."},{"line_number":20,"context_line":"ipv4_gateway: This is the IPv4 defaut router address with-in the IPv4 subnet being utilized for IP addresses for the nodes being deployed."},{"line_number":21,"context_line":"node_default_network_interface: This is the default network interface with-in the nodes to be deployed which the new IP configuration will be applied to.  Note: This is likely to be deprecated and removed in the future as Bifrost will likely change methods utilized to include networking configuration into the configuration drive sufficiently that this should no longer be required."},{"line_number":22,"context_line":"ipv4_nameserver: Defines the IPv4 Nameserver to configure the node with initially in order to support name resolution."},{"line_number":23,"context_line":"ipv4_address: The IPv4 address of the node to be deployed, if applicable."}],"source_content_type":"text/x-gfm","patch_set":3,"id":"3afb71cf_46e2f504","line":20,"updated":"2015-06-07 07:22:14.000000000","message":"s/defaut/default/","commit_id":"37d8e9b2f177632ba958396bc16e17b309ad8d92"},{"author":{"_account_id":12459,"name":"Stephanie Miller","email":"stephane@alum.mit.edu","username":"cinerama"},"change_message_id":"7a70b6cf8e0a804419605e8416ffdbb609bbb98d","unresolved":false,"context_lines":[{"line_number":17,"context_line":""},{"line_number":18,"context_line":"addressing_mode: If defined and set to a value of \"dhcp\", this role sets the primary interface to utilize DHCP."},{"line_number":19,"context_line":"ipv4_subnet_mask:  This is the subnet mask(e.g. 255.255.255.0 or similar) that matches the static addressing which desires to be imprinted into the configuraiton drive."},{"line_number":20,"context_line":"ipv4_gateway: This is the IPv4 defaut router address with-in the IPv4 subnet being utilized for IP addresses for the nodes being deployed."},{"line_number":21,"context_line":"node_default_network_interface: This is the default network interface with-in the nodes to be deployed which the new IP configuration will be applied to.  Note: This is likely to be deprecated and removed in the future as Bifrost will likely change methods utilized to include networking configuration into the configuration drive sufficiently that this should no longer be required."},{"line_number":22,"context_line":"ipv4_nameserver: Defines the IPv4 Nameserver to configure the node with initially in order to support name resolution."},{"line_number":23,"context_line":"ipv4_address: The IPv4 address of the node to be deployed, if applicable."}],"source_content_type":"text/x-gfm","patch_set":3,"id":"3afb71cf_a875c598","line":20,"updated":"2015-06-08 23:05:03.000000000","message":"within rather than with-in here \u0026 in line 21","commit_id":"37d8e9b2f177632ba958396bc16e17b309ad8d92"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"408558127a37311dee9c7bf8272eb0a5b444eef4","unresolved":false,"context_lines":[{"line_number":17,"context_line":""},{"line_number":18,"context_line":"addressing_mode: If defined and set to a value of \"dhcp\", this role sets the primary interface to utilize DHCP."},{"line_number":19,"context_line":"ipv4_subnet_mask:  This is the subnet mask(e.g. 255.255.255.0 or similar) that matches the static addressing which desires to be imprinted into the configuraiton drive."},{"line_number":20,"context_line":"ipv4_gateway: This is the IPv4 defaut router address with-in the IPv4 subnet being utilized for IP addresses for the nodes being deployed."},{"line_number":21,"context_line":"node_default_network_interface: This is the default network interface with-in the nodes to be deployed which the new IP configuration will be applied to.  Note: This is likely to be deprecated and removed in the future as Bifrost will likely change methods utilized to include networking configuration into the configuration drive sufficiently that this should no longer be required."},{"line_number":22,"context_line":"ipv4_nameserver: Defines the IPv4 Nameserver to configure the node with initially in order to support name resolution."},{"line_number":23,"context_line":"ipv4_address: The IPv4 address of the node to be deployed, if applicable."}],"source_content_type":"text/x-gfm","patch_set":3,"id":"3afb71cf_c1a1cc47","line":20,"in_reply_to":"3afb71cf_46e2f504","updated":"2015-06-09 19:16:20.000000000","message":"Done","commit_id":"37d8e9b2f177632ba958396bc16e17b309ad8d92"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"408558127a37311dee9c7bf8272eb0a5b444eef4","unresolved":false,"context_lines":[{"line_number":17,"context_line":""},{"line_number":18,"context_line":"addressing_mode: If defined and set to a value of \"dhcp\", this role sets the primary interface to utilize DHCP."},{"line_number":19,"context_line":"ipv4_subnet_mask:  This is the subnet mask(e.g. 255.255.255.0 or similar) that matches the static addressing which desires to be imprinted into the configuraiton drive."},{"line_number":20,"context_line":"ipv4_gateway: This is the IPv4 defaut router address with-in the IPv4 subnet being utilized for IP addresses for the nodes being deployed."},{"line_number":21,"context_line":"node_default_network_interface: This is the default network interface with-in the nodes to be deployed which the new IP configuration will be applied to.  Note: This is likely to be deprecated and removed in the future as Bifrost will likely change methods utilized to include networking configuration into the configuration drive sufficiently that this should no longer be required."},{"line_number":22,"context_line":"ipv4_nameserver: Defines the IPv4 Nameserver to configure the node with initially in order to support name resolution."},{"line_number":23,"context_line":"ipv4_address: The IPv4 address of the node to be deployed, if applicable."}],"source_content_type":"text/x-gfm","patch_set":3,"id":"3afb71cf_418efcd0","line":20,"in_reply_to":"3afb71cf_a875c598","updated":"2015-06-09 19:16:20.000000000","message":"Done","commit_id":"37d8e9b2f177632ba958396bc16e17b309ad8d92"},{"author":{"_account_id":13997,"name":"SHIGEMATSU Mitsuhiro","email":"shigematsu.mitsuhiro@lab.ntt.co.jp","username":"pshige"},"change_message_id":"b12bb238e73fdbc70cdad4116df86c98bc1ba985","unresolved":false,"context_lines":[{"line_number":29,"context_line":"Customizing"},{"line_number":30,"context_line":"-----------"},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"The attempt with this playbook is to create a very simple and easilly modifable configuraiton drive to be loaded to the remote machine.  This is done for each host that the role is run against..  If one wishes to insert additional files, this can be done by editing the tasks/main.yml file.  As the drives are generated in a stepwise fashion, it is important to make note of and use the \"{{ uuid }}\" variable as that is utilized to deliniate the file destinations between different configuration drives that may be in the process of being created."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"Additional detail on the format of configuraiton drives can be found at http://docs.openstack.org/user-guide/content/enable_config_drive.html."},{"line_number":35,"context_line":""}],"source_content_type":"text/x-gfm","patch_set":3,"id":"3afb71cf_e6f1e1ce","line":32,"updated":"2015-06-07 07:22:14.000000000","message":"s/easilly/easily/ s/modifable/modifiable/ s/configuraiton/configuration/ s/deliniate/delineate/","commit_id":"37d8e9b2f177632ba958396bc16e17b309ad8d92"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"408558127a37311dee9c7bf8272eb0a5b444eef4","unresolved":false,"context_lines":[{"line_number":29,"context_line":"Customizing"},{"line_number":30,"context_line":"-----------"},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"The attempt with this playbook is to create a very simple and easilly modifable configuraiton drive to be loaded to the remote machine.  This is done for each host that the role is run against..  If one wishes to insert additional files, this can be done by editing the tasks/main.yml file.  As the drives are generated in a stepwise fashion, it is important to make note of and use the \"{{ uuid }}\" variable as that is utilized to deliniate the file destinations between different configuration drives that may be in the process of being created."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"Additional detail on the format of configuraiton drives can be found at http://docs.openstack.org/user-guide/content/enable_config_drive.html."},{"line_number":35,"context_line":""}],"source_content_type":"text/x-gfm","patch_set":3,"id":"3afb71cf_eca27ffb","line":32,"in_reply_to":"3afb71cf_e6f1e1ce","updated":"2015-06-09 19:16:20.000000000","message":"Done","commit_id":"37d8e9b2f177632ba958396bc16e17b309ad8d92"},{"author":{"_account_id":13997,"name":"SHIGEMATSU Mitsuhiro","email":"shigematsu.mitsuhiro@lab.ntt.co.jp","username":"pshige"},"change_message_id":"b12bb238e73fdbc70cdad4116df86c98bc1ba985","unresolved":false,"context_lines":[{"line_number":31,"context_line":""},{"line_number":32,"context_line":"The attempt with this playbook is to create a very simple and easilly modifable configuraiton drive to be loaded to the remote machine.  This is done for each host that the role is run against..  If one wishes to insert additional files, this can be done by editing the tasks/main.yml file.  As the drives are generated in a stepwise fashion, it is important to make note of and use the \"{{ uuid }}\" variable as that is utilized to deliniate the file destinations between different configuration drives that may be in the process of being created."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"Additional detail on the format of configuraiton drives can be found at http://docs.openstack.org/user-guide/content/enable_config_drive.html."},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"If one wishes to manually modify a configuration drive after the fact, the files are base64 encoded, gzip compressed, ISO9660 filesystems.  Ironic will fail the deployment of the configuration drive if the file is not first found to be base64 encoded, and then gzip compressed.  Alternatively, the configuration drive can be a vfat filesystem, although this carries with it some risks if the filesystem is always treated as a source of truth upon system boot."},{"line_number":37,"context_line":""}],"source_content_type":"text/x-gfm","patch_set":3,"id":"3afb71cf_c6eee5eb","line":34,"updated":"2015-06-07 07:22:14.000000000","message":"s/configuraiton/configuration/","commit_id":"37d8e9b2f177632ba958396bc16e17b309ad8d92"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"408558127a37311dee9c7bf8272eb0a5b444eef4","unresolved":false,"context_lines":[{"line_number":31,"context_line":""},{"line_number":32,"context_line":"The attempt with this playbook is to create a very simple and easilly modifable configuraiton drive to be loaded to the remote machine.  This is done for each host that the role is run against..  If one wishes to insert additional files, this can be done by editing the tasks/main.yml file.  As the drives are generated in a stepwise fashion, it is important to make note of and use the \"{{ uuid }}\" variable as that is utilized to deliniate the file destinations between different configuration drives that may be in the process of being created."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"Additional detail on the format of configuraiton drives can be found at http://docs.openstack.org/user-guide/content/enable_config_drive.html."},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"If one wishes to manually modify a configuration drive after the fact, the files are base64 encoded, gzip compressed, ISO9660 filesystems.  Ironic will fail the deployment of the configuration drive if the file is not first found to be base64 encoded, and then gzip compressed.  Alternatively, the configuration drive can be a vfat filesystem, although this carries with it some risks if the filesystem is always treated as a source of truth upon system boot."},{"line_number":37,"context_line":""}],"source_content_type":"text/x-gfm","patch_set":3,"id":"3afb71cf_01c364ee","line":34,"in_reply_to":"3afb71cf_c6eee5eb","updated":"2015-06-09 19:16:20.000000000","message":"Done","commit_id":"37d8e9b2f177632ba958396bc16e17b309ad8d92"},{"author":{"_account_id":13997,"name":"SHIGEMATSU Mitsuhiro","email":"shigematsu.mitsuhiro@lab.ntt.co.jp","username":"pshige"},"change_message_id":"b12bb238e73fdbc70cdad4116df86c98bc1ba985","unresolved":false,"context_lines":[{"line_number":64,"context_line":""},{"line_number":65,"context_line":"Unless required by applicable law or agreed to in writing, software"},{"line_number":66,"context_line":"distributed under the License is distributed on an \"AS IS\" BASIS,"},{"line_number":67,"context_line":"WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express orimplied."},{"line_number":68,"context_line":"See the License for the specific language governing permissions and"},{"line_number":69,"context_line":"limitations under the License."},{"line_number":70,"context_line":""}],"source_content_type":"text/x-gfm","patch_set":3,"id":"3afb71cf_06ccfd87","line":67,"updated":"2015-06-07 07:22:14.000000000","message":"s/orimplied/or implied/","commit_id":"37d8e9b2f177632ba958396bc16e17b309ad8d92"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"408558127a37311dee9c7bf8272eb0a5b444eef4","unresolved":false,"context_lines":[{"line_number":64,"context_line":""},{"line_number":65,"context_line":"Unless required by applicable law or agreed to in writing, software"},{"line_number":66,"context_line":"distributed under the License is distributed on an \"AS IS\" BASIS,"},{"line_number":67,"context_line":"WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express orimplied."},{"line_number":68,"context_line":"See the License for the specific language governing permissions and"},{"line_number":69,"context_line":"limitations under the License."},{"line_number":70,"context_line":""}],"source_content_type":"text/x-gfm","patch_set":3,"id":"3afb71cf_acb12749","line":67,"in_reply_to":"3afb71cf_06ccfd87","updated":"2015-06-09 19:16:20.000000000","message":"Done","commit_id":"37d8e9b2f177632ba958396bc16e17b309ad8d92"}],"playbooks/roles/bifrost-configdrives-dynamic/tasks/main.yml":[{"author":{"_account_id":12459,"name":"Stephanie Miller","email":"stephane@alum.mit.edu","username":"cinerama"},"change_message_id":"7a70b6cf8e0a804419605e8416ffdbb609bbb98d","unresolved":false,"context_lines":[{"line_number":18,"context_line":"- name: \"Name Make Temporary folder to build configdrive\""},{"line_number":19,"context_line":"  local_action: command mktemp -d"},{"line_number":20,"context_line":"  register: variable_configdrive_location"},{"line_number":21,"context_line":"- name: \"Make Metadata folder - /openstack/2012-08-10\""},{"line_number":22,"context_line":"  local_action: file state\u003ddirectory name\u003d{{ variable_configdrive_location.stdout }}/{{ uuid }}/openstack/2012-08-10/"},{"line_number":23,"context_line":"- name: \"Make Metadata folder - /openstack/latest\""},{"line_number":24,"context_line":"  local_action: file state\u003ddirectory name\u003d{{ variable_configdrive_location.stdout }}/{{ uuid }}/openstack/latest/"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"3afb71cf_767d6ae6","line":21,"updated":"2015-06-08 23:05:03.000000000","message":"Might be good to put the version in a variable in case we would like to use a later one at some point.","commit_id":"37d8e9b2f177632ba958396bc16e17b309ad8d92"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"408558127a37311dee9c7bf8272eb0a5b444eef4","unresolved":false,"context_lines":[{"line_number":18,"context_line":"- name: \"Name Make Temporary folder to build configdrive\""},{"line_number":19,"context_line":"  local_action: command mktemp -d"},{"line_number":20,"context_line":"  register: variable_configdrive_location"},{"line_number":21,"context_line":"- name: \"Make Metadata folder - /openstack/2012-08-10\""},{"line_number":22,"context_line":"  local_action: file state\u003ddirectory name\u003d{{ variable_configdrive_location.stdout }}/{{ uuid }}/openstack/2012-08-10/"},{"line_number":23,"context_line":"- name: \"Make Metadata folder - /openstack/latest\""},{"line_number":24,"context_line":"  local_action: file state\u003ddirectory name\u003d{{ variable_configdrive_location.stdout }}/{{ uuid }}/openstack/latest/"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"3afb71cf_611e98bc","line":21,"in_reply_to":"3afb71cf_767d6ae6","updated":"2015-06-09 19:16:20.000000000","message":"Done","commit_id":"37d8e9b2f177632ba958396bc16e17b309ad8d92"}]}