Use HTTPS where appropriate

The main purpose is to use HTTPS when downloading cloud images in the
"OpenStack on LXD" guide.

Change-Id: Ibbaeb64f51e7c17d7b01f978584347d598840931
This commit is contained in:
Nobuto Murata 2018-02-01 06:54:06 +09:00
parent bee703a23c
commit bbac758c76
15 changed files with 47 additions and 47 deletions

View File

@ -2,8 +2,8 @@
Team and repository tags
========================
.. image:: http://governance.openstack.org/badges/charm-guide.svg
:target: http://governance.openstack.org/reference/tags/index.html
.. image:: https://governance.openstack.org/badges/charm-guide.svg
:target: https://governance.openstack.org/reference/tags/index.html
.. Change things from this point on

View File

@ -61,7 +61,7 @@ OpenStack Newton support on 16.04 and 16.10
The charms provide full support for OpenStack Newton. For further details and
documentation on Openstack Newton, please check out
http://releases.openstack.org/newton
https://releases.openstack.org/newton
To deploy OpenStack Newton on Ubuntu 16.04, use the 'openstack-origin'
configuration option, for example:

View File

@ -53,7 +53,7 @@ OpenStack Ocata support on 16.04
The charms provide full support for OpenStack Ocata. For further details and
documentation on Openstack Ocata please check out
http://releases.openstack.org/ocata
https://releases.openstack.org/ocata
To deploy OpenStack Ocata on Ubuntu 16.04, use the 'openstack-origin'
configuration option, for example:

View File

@ -54,7 +54,7 @@ OpenStack Pike support on 16.04
The charms provide full support for OpenStack Pike. For further details and
documentation on Openstack Pike please check out
http://releases.openstack.org/pike
https://releases.openstack.org/pike
To deploy OpenStack Pike on Ubuntu 16.04, use the 'openstack-origin'
configuration option, for example:

View File

@ -81,7 +81,7 @@ The implementation for the *interface* is typical. If you look at the
``..available`` state/flags are *continuous* from the moment the conditions for
them are met.
.. _`interfaces.juju.solutions`: http://interfaces.juju.solutions/
.. _`interfaces.juju.solutions`: https://interfaces.juju.solutions/
.. _`interface-etcd`: https://github.com/juju-solutions/interface-etcd
By now you will have probably seen the issue; once the ``<name>.connected``

View File

@ -117,7 +117,7 @@ OpenStack Interfaces
--------------------
Interfaces define the data exchange between each of the charms. A list of all
available interfaces is available `here <http://interfaces.juju.solutions>`__.
available interfaces is available `here <https://interfaces.juju.solutions>`__.
A list of OpenStack specific interfaces can be found `here <https://github.com/openstack?query=charm-interface>`__
The interfaces a charm needs are defines in the `layers.yaml`_. Below is a list

View File

@ -16,7 +16,7 @@ the syntax ensures that it roughly always looks the same.
As OpenStack charms are for OpenStack its a good idea to adhere to the
OpenStack Python coding standard. So first things first:
* Read the `OpenStack Coding standard <http://docs.openstack.org/developer/hacking/>`__.
* Read the `OpenStack Coding standard <https://docs.openstack.org/developer/hacking/>`__.
* Read PEP8 (again).
Topics

View File

@ -5,7 +5,7 @@ Talk to us
==========
* Talk to us on IRC channel ``#openstack-charms`` on Freenode.
* Join the conversation on our `Mailing list <http://docs.openstack.org/developer/charm-guide/mailing-list.html>`_.
* Join the conversation on our `Mailing list <https://docs.openstack.org/developer/charm-guide/mailing-list.html>`_.
* Participate to our `Online Meetings <meetings.html>`_.

View File

@ -12,11 +12,11 @@ Getting started
* For bare-metal deployment, Juju uses MAAS_ to provision and configure
physical servers, so that's a good next step.
* Once you have MAAS setup, you can try out the
`OpenStack Base bundle <http://jujucharms.com/openstack-base>`__ from
`OpenStack Base bundle <https://jujucharms.com/openstack-base>`__ from
the Juju charm store.
.. _Juju: https://jujucharms.com/docs/devel/getting-started
.. _MAAS: http://maas.io/get-started
.. _MAAS: https://maas.io/get-started
.. toctree::
:maxdepth: 1

View File

@ -6,7 +6,7 @@ The OpenStack charms are part of the OpenStack project, and follow the
same development process as other projects.
For details on how to submit changes to an OpenStack project please refer
to the OpenStack `development documentation <http://docs.openstack.org/infra/manual/developers.html>`__.
to the OpenStack `development documentation <https://docs.openstack.org/infra/manual/developers.html>`__.
and then take a read through the rest of this section on how to contribute
to the OpenStack Charms.

View File

@ -19,7 +19,7 @@ Broadly the work flow for making a change to a charm is:
.. code:: bash
git clone http://github.com/openstack/charm-cinder
git clone https://github.com/openstack/charm-cinder
cd charm-cinder
git checkout -b bug/XXXXXX master
@ -61,7 +61,7 @@ Finally, submit your change for review (if they pass pep8 and unit tests!):
git review
This will push your proposed changes to Gerrit and provide you with a URL for the
review board on http://review.openstack.org/.
review board on https://review.openstack.org/.
To make amendments to your proposed change, update your local branch and then:

View File

@ -21,7 +21,7 @@ Next meeting
- Every two weeks (on even weeks) on Monday @ 1700 UTC on ``#openstack-meeting-4`` on freenode
- Every two weeks (on odd weeks) on Monday @ 1000 UTC on ``#openstack-meeting-4`` on freenode
`Week Numbers <http://www.epochconverter.com/weeknumbers>`_
`Week Numbers <https://www.epochconverter.com/weeknumbers>`_
Agenda
======

View File

@ -6,34 +6,34 @@ Charms
OpenStack Charms
~~~~~~~~~~~~~~~~
* `ceilometer <http://git.openstack.org/cgit/openstack/charm-ceilometer/>`_
* `ceilometer-agent <http://git.openstack.org/cgit/openstack/charm-ceilometer-agent/>`_
* `cinder <http://git.openstack.org/cgit/openstack/charm-cinder/>`_
* `cinder-backup <http://git.openstack.org/cgit/openstack/charm-cinder-backup/>`_
* `cinder-ceph <http://git.openstack.org/cgit/openstack/charm-cinder-ceph/>`_
* `glance <http://git.openstack.org/cgit/openstack/charm-glance/>`_
* `heat <http://git.openstack.org/cgit/openstack/charm-heat/>`_
* `keystone <http://git.openstack.org/cgit/openstack/charm-keystone/>`_
* `neutron-api <http://git.openstack.org/cgit/openstack/charm-neutron-api/>`_
* `neutron-api-odl <http://git.openstack.org/cgit/openstack/charm-neutron-api-odl/>`_
* `neutron-gateway <http://git.openstack.org/cgit/openstack/charm-neutron-gateway/>`_
* `neutron-openvswitch <http://git.openstack.org/cgit/openstack/charm-neutron-openvswitch/>`_
* `nova-cloud-controller <http://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/>`_
* `nova-compute <http://git.openstack.org/cgit/openstack/charm-nova-compute/>`_
* `openstack-dashboard <http://git.openstack.org/cgit/openstack/charm-openstack-dashboard/>`_
* `openvswitch-odl <http://git.openstack.org/cgit/openstack/charm-openvswitch-odl/>`_
* `swift-proxy <http://git.openstack.org/cgit/openstack/charm-swift-proxy/>`_
* `swift-storage <http://git.openstack.org/cgit/openstack/charm-swift-storage/>`_
* `ceilometer <https://git.openstack.org/cgit/openstack/charm-ceilometer/>`_
* `ceilometer-agent <https://git.openstack.org/cgit/openstack/charm-ceilometer-agent/>`_
* `cinder <https://git.openstack.org/cgit/openstack/charm-cinder/>`_
* `cinder-backup <https://git.openstack.org/cgit/openstack/charm-cinder-backup/>`_
* `cinder-ceph <https://git.openstack.org/cgit/openstack/charm-cinder-ceph/>`_
* `glance <https://git.openstack.org/cgit/openstack/charm-glance/>`_
* `heat <https://git.openstack.org/cgit/openstack/charm-heat/>`_
* `keystone <https://git.openstack.org/cgit/openstack/charm-keystone/>`_
* `neutron-api <https://git.openstack.org/cgit/openstack/charm-neutron-api/>`_
* `neutron-api-odl <https://git.openstack.org/cgit/openstack/charm-neutron-api-odl/>`_
* `neutron-gateway <https://git.openstack.org/cgit/openstack/charm-neutron-gateway/>`_
* `neutron-openvswitch <https://git.openstack.org/cgit/openstack/charm-neutron-openvswitch/>`_
* `nova-cloud-controller <https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/>`_
* `nova-compute <https://git.openstack.org/cgit/openstack/charm-nova-compute/>`_
* `openstack-dashboard <https://git.openstack.org/cgit/openstack/charm-openstack-dashboard/>`_
* `openvswitch-odl <https://git.openstack.org/cgit/openstack/charm-openvswitch-odl/>`_
* `swift-proxy <https://git.openstack.org/cgit/openstack/charm-swift-proxy/>`_
* `swift-storage <https://git.openstack.org/cgit/openstack/charm-swift-storage/>`_
Other Supporting Charms
~~~~~~~~~~~~~~~~~~~~~~~
* `percona-cluster <http://git.openstack.org/cgit/openstack/charm-percona-cluster/>`_
* `rabbitmq-server <http://git.openstack.org/cgit/openstack/charm-rabbitmq-server/>`_
* `odl-controller <http://git.openstack.org/cgit/openstack/charm-odl-controller/>`_
* `lxd <http://git.openstack.org/cgit/openstack/charm-lxd/>`_
* `ceph <http://git.openstack.org/cgit/openstack/charm-ceph/>`_
* `ceph-osd <http://git.openstack.org/cgit/openstack/charm-ceph-osd/>`_
* `ceph-mon <http://git.openstack.org/cgit/openstack/charm-ceph-mon/>`_
* `ceph-radosgw <http://git.openstack.org/cgit/openstack/charm-ceph-radosgw/>`_
* `hacluster <http://git.openstack.org/cgit/openstack/charm-hacluster/>`_
* `percona-cluster <https://git.openstack.org/cgit/openstack/charm-percona-cluster/>`_
* `rabbitmq-server <https://git.openstack.org/cgit/openstack/charm-rabbitmq-server/>`_
* `odl-controller <https://git.openstack.org/cgit/openstack/charm-odl-controller/>`_
* `lxd <https://git.openstack.org/cgit/openstack/charm-lxd/>`_
* `ceph <https://git.openstack.org/cgit/openstack/charm-ceph/>`_
* `ceph-osd <https://git.openstack.org/cgit/openstack/charm-ceph-osd/>`_
* `ceph-mon <https://git.openstack.org/cgit/openstack/charm-ceph-mon/>`_
* `ceph-radosgw <https://git.openstack.org/cgit/openstack/charm-ceph-radosgw/>`_
* `hacluster <https://git.openstack.org/cgit/openstack/charm-hacluster/>`_

View File

@ -220,28 +220,28 @@ For amd64:
.. code:: bash
curl http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img | \
curl https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img | \
openstack image create --public --container-format=bare --disk-format=qcow2 xenial
For arm64:
.. code:: bash
curl http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-arm64-uefi1.img | \
curl https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-arm64-uefi1.img | \
openstack image create --public --container-format=bare --disk-format=qcow2 --property hw_firmware_type=uefi xenial
For s390x:
.. code:: bash
curl http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-s390x-disk1.img | \
curl https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-s390x-disk1.img | \
openstack image create --public --container-format=bare --disk-format=qcow2 xenial
For ppc64el:
.. code:: bash
curl http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-ppc64el-disk1.img | \
curl https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-ppc64el-disk1.img | \
openstack image create --public --container-format=bare --disk-format=qcow2 xenial

View File

@ -5,7 +5,7 @@ description-file =
README.rst
author = OpenStack
author-email = openstack@lists.openstack.org
home-page = http://docs.openstack.org/developer/charm-guide/
home-page = https://docs.openstack.org/developer/charm-guide/
classifier =
Intended Audience :: Developers
License :: OSI Approved :: Apache Software License