2
Copyright 2010 United States Government as represented by the
3
Administrator of the National Aeronautics and Space Administration.
6
Licensed under the Apache License, Version 2.0 (the "License"); you may
7
not use this file except in compliance with the License. You may obtain
8
a copy of the License at
10
http://www.apache.org/licenses/LICENSE-2.0
12
Unless required by applicable law or agreed to in writing, software
13
distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
14
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
15
License for the specific language governing permissions and limitations
21
Cloudpipe -- Per Project Vpns
22
=============================
24
Cloudpipe is a method for connecting end users to their project insnances in vlan mode.
30
The support code for cloudpipe implements admin commands (via nova-manage) to automatically create a vm for a project that allows users to vpn into the private network of their project. Access to this vpn is provided through a public port on the network host for the project. This allows users to have free access to the virtual machines in their project without exposing those machines to the public internet.
36
The cloudpipe image is basically just a linux instance with openvpn installed. It needs a simple script to grab user data from the metadata server, b64 decode it into a zip file, and run the autorun.sh script from inside the zip. The autorun script will configure and run openvpn to run using the data from nova.
38
It is also useful to have a cron script that will periodically redownload the metadata and copy the new crl. This will keep revoked users from connecting and will disconnect any users that are connected with revoked certificates when their connection is renegotiated (every hour).
44
When you use nova-manage to launch a cloudpipe for a user, it goes through the following process:
46
#. creates a keypair called <project_id>-vpn and saves it in the keys directory
47
#. creates a security group <project_id>-vpn and opens up 1194 and icmp
48
#. creates a cert and private key for the vpn instance and saves it in the CA/projects/<project_id>/ directory
49
#. zips up the info and puts it b64 encoded as user data
50
#. launches an m1.tiny instance with the above settings using the flag-specified vpn image
56
In vlan networking mode, the second ip in each private network is reserved for the cloudpipe instance. This gives a consistent ip to the instance so that nova-network can create forwarding rules for access from the outside world. The network for each project is given a specific high-numbered port on the public ip of the network host. This port is automatically forwarded to 1194 on the vpn instance.
58
If specific high numbered ports do not work for your users, you can always allocate and associate a public ip to the instance, and then change the vpn_public_ip and vpn_public_port in the database. This will be turned into a nova-manage command or a flag soon.
61
Certificates and Revocation
62
---------------------------
64
If the use_project_ca flag is set (required to for cloudpipes to work securely), then each project has its own ca. This ca is used to sign the certificate for the vpn, and is also passed to the user for bundling images. When a certificate is revoked using nova-manage, a new Certificate Revocation List (crl) is generated. As long as cloudpipe has an updated crl, it will block revoked users from connecting to the vpn.
67
The :mod:`nova.cloudpipe.pipelib` Module
68
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
70
.. automodule:: nova.cloudpipe.pipelib
77
The :mod:`nova.api.cloudpipe` Module
78
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
80
.. automodule:: nova.api.cloudpipe
87
The :mod:`nova.crypto` Module
88
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
90
.. automodule:: nova.crypto
added
removed
doc/source/devref/cloudpipe.rst
