Difference between revisions of "Agile testbed/Cloud"
m (add link) |
(update aftert node changes) |
||
| Line 1: | Line 1: | ||
| − | There is an effort to add a cloud to the [[Agile testbed]]. It is based on [http://opennebula.org/ OpenNebula] and currently runs on | + | There is an effort to add a cloud to the [[Agile testbed]]. It is based on [http://opennebula.org/ OpenNebula] and currently runs on autana.nikhef.nl as master and arauca.nikhef.nl as a slave. It is currently in development. |
==Networking== | ==Networking== | ||
| Line 10: | Line 10: | ||
** Public: public IP addresses, bridged (domain <tt>.nikhef.nl</tt>) | ** Public: public IP addresses, bridged (domain <tt>.nikhef.nl</tt>) | ||
| − | + | These networks are all connected via <tt>eth1</tt>, so that the networks across different physical hosts can reach each other safely. Autana then masquerades the internal range for internet connectivity. Autana also runs a nameserver on 10.198.x.1 that serves the dynamic DNS in addition to being a DNS cache. | |
[http://www.semicomplete.com/articles/dynamic-dns-with-dhcp/ Dynamic DNS] [http://www.cameratim.com/computing/linux/using-bind-as-a-local-dns-server DDNS on Fedora] | [http://www.semicomplete.com/articles/dynamic-dns-with-dhcp/ Dynamic DNS] [http://www.cameratim.com/computing/linux/using-bind-as-a-local-dns-server DDNS on Fedora] | ||
==Image repository== | ==Image repository== | ||
| − | There will be an image repository at <tt>/ | + | There will be an image repository at <tt>/var/cloud/images</tt> containing base images for various operating systems. These will be updated daily by a cronjob. |
==Contextualisation== | ==Contextualisation== | ||
| Line 22: | Line 22: | ||
==Future directions== | ==Future directions== | ||
When the cloud is properly setup, future directions can be explored like: | When the cloud is properly setup, future directions can be explored like: | ||
| − | * Secure networking: ebtables | + | * Secure networking: ebtables hooks to only allow allocated mac from node |
* Using virtual machines from within Hudson | * Using virtual machines from within Hudson | ||
** for on-demand build slaves (multiple platforms) | ** for on-demand build slaves (multiple platforms) | ||
** for tests running on virtual machines | ** for tests running on virtual machines | ||
* Moving other parts of the testbed to the cloud, if it turns out to be an improvement. | * Moving other parts of the testbed to the cloud, if it turns out to be an improvement. | ||
Revision as of 11:32, 10 February 2010
There is an effort to add a cloud to the Agile testbed. It is based on OpenNebula and currently runs on autana.nikhef.nl as master and arauca.nikhef.nl as a slave. It is currently in development.
Networking
- Plug'n'play networking
- MAC and IP addresses handed out by OpenNebula
- An OpenNebula hook will be added to register the machine's name with DNS dynamically
- There will be three networks, initially:
- Closed: no internet connection (10.198.5.0/24, domain .closed)
- Private: internet access, masqueraded to the outside world (10.198.6.0/24, .private)
- Public: public IP addresses, bridged (domain .nikhef.nl)
These networks are all connected via eth1, so that the networks across different physical hosts can reach each other safely. Autana then masquerades the internal range for internet connectivity. Autana also runs a nameserver on 10.198.x.1 that serves the dynamic DNS in addition to being a DNS cache.
Image repository
There will be an image repository at /var/cloud/images containing base images for various operating systems. These will be updated daily by a cronjob.
Contextualisation
When a cloud machine is instantiated from a base image from the repository, the machine should still be configured for the specific instance. This is done by an init script that is present in all base images, which sets up the network and runs any machine-specific initialisation. The OpenNebula contextualisation features will be used for this.
Future directions
When the cloud is properly setup, future directions can be explored like:
- Secure networking: ebtables hooks to only allow allocated mac from node
- Using virtual machines from within Hudson
- for on-demand build slaves (multiple platforms)
- for tests running on virtual machines
- Moving other parts of the testbed to the cloud, if it turns out to be an improvement.
