diff --git a/HACKING.rst b/HACKING.rst index 03d00ea..fd0f445 100644 --- a/HACKING.rst +++ b/HACKING.rst @@ -1,4 +1,4 @@ gluon Style Commandments =============================================== -Read the OpenStack Style Commandments http://docs.openstack.org/developer/hacking/ +Read the OpenStack Style Commandments https://docs.openstack.org/hacking/latest/ diff --git a/doc/source/devref/database_migration.rst b/doc/source/devref/database_migration.rst index 91ce3d2..095c81e 100644 --- a/doc/source/devref/database_migration.rst +++ b/doc/source/devref/database_migration.rst @@ -10,7 +10,7 @@ job will vote against the change until a migration file for this change is also uploaded. Similar to Neutron migration strategy a script for auto generation is used: -`Neutron Script Auto-generation `_ +`Neutron Script Auto-generation `_ The big difference is that Proton will have a YAML model. So a new auto generate script is needed. @@ -26,7 +26,7 @@ to update the database. The migration process is done in the exact same way as the Neutron database migration. See details in the devref: -`Neutron Database Migration `_ +`Neutron Database Migration `_ Testing diff --git a/doc/source/devref/gluon-auth.rst b/doc/source/devref/gluon-auth.rst index a2587ed..976eba9 100644 --- a/doc/source/devref/gluon-auth.rst +++ b/doc/source/devref/gluon-auth.rst @@ -179,7 +179,7 @@ Action to API Mapping ~~~~~~~~~~~~~~~~~~~~~ Gluon service has to map actions to respective API calls. The OpenStack keystonemiddleware -and oslo.policy(http://docs.openstack.org/developer/oslo.policy/) modules will be integrated +and oslo.policy(https://docs.openstack.org/oslo.policy/latest/) modules will be integrated with Gluon to add keystone authentication and enforce RBAC policies defined in the JSON.policy file. The pecan-wsgi service in the Neutron will be used as a reference code for Gluon implementation