maas 1.2+bzr1373+dfsg-0ubuntu1~12.04.2 source package in Ubuntu
Changelog
maas (1.2+bzr1373+dfsg-0ubuntu1~12.04.2) precise-proposed; urgency=low * MAAS Stable Release Update, debian/patches: - 99_filestorage_empty_files_lp1204507.patch: Fix to allow the storage of empty files when using Juju Go, otherwise machines will fail to bootstrap. (LP: #1204507) - 99_fix_highbank_localboot_lp1172966.patch: Fix to PXE LOCALBOOT on highbank servers by removing a PXE message. Otherwise highbank will fail to pxe boot. (LP: #1172966) - 99_no_ipmi_detection_kvm_lp1064527.patch: Fix to ensure that IPMI detection does not happen on KVM VM's, otherwise enlistment and commissioning process will take too long. (LP: #1064527) - 99_update_cluster_info_cli_lp1172193.patch: Fix to allow admins to update cluster information from the API/CLI and not only restrict it to the WebUI. (LP: #1172193) - 99_fix_ipmi_power_command_lp1171418: Fix to ensure that ipmi commands are always executed regardless of the state of the machine. (LP: #1171418) - 99_default_timezone_utc_lp1211447.patch: Default to UTC for the deployed nodes. (LP: #1211447) -- Andres Rodriguez <email address hidden> Mon, 12 Aug 2013 12:18:34 -0400
Upload details
- Uploaded by:
- Andres Rodriguez
- Uploaded to:
- Precise
- Original maintainer:
- Ubuntu Developers
- Architectures:
- all
- Section:
- net
- Urgency:
- Low Urgency
See full publishing history Publishing
Series | Published | Component | Section |
---|
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
maas_1.2+bzr1373+dfsg.orig.tar.gz | 1.8 MiB | 33bd1a093f4c2d419169df822d03854a26608adba807e9e045353ed5e1c78259 |
maas_1.2+bzr1373+dfsg-0ubuntu1~12.04.2.debian.tar.gz | 2.9 MiB | f6e50d6a6493d6adaae795e91967619dbeb5e35a2d16b12069726cfc294113d3 |
maas_1.2+bzr1373+dfsg-0ubuntu1~12.04.2.dsc | 2.3 KiB | 558ebc3a8372991f2868625dac23a3c39acb0a4f066cffdbc3a9e6650f7ce160 |
Available diffs
Binary packages built by this source
- maas: Ubuntu MAAS Server
Ubuntu MAAS Server is the successor to Orchestra. It offers a
nice UI to provision your Ubuntu servers. Each physical server
(“node”) will be commissioned automatically on first boot.
During the commissioning process administrators are able to
configure hardware settings manually before an automated smoke
test and burn-in test are done. Once commissioned, a node can
be deployed on demand by name, or allocated to a queue for
dynamic allocation to services being deployed on this MAAS.
.
This package is a metapackage which installs a complete MAAS
service on a single machine.
- maas-cli: Ubuntu MAAS Client Tool
Ubuntu MAAS Server is the successor to Orchestra. It offers a
nice UI to provision your Ubuntu servers. Each physical server
(“node”) will be commissioned automatically on first boot.
During the commissioning process administrators are able to
configure hardware settings manually before an automated smoke
test and burn-in test are done. Once commissioned, a node can
be deployed on demand by name, or allocated to a queue for
dynamic allocation to services being deployed on this MAAS.
.
This package contains the client command line tool.
- maas-cluster-controller: Ubuntu MAAS Cluster Controller
Ubuntu MAAS Server is the successor to Orchestra. It offers a
nice UI to provision your Ubuntu servers. Each physical server
(“node”) will be commissioned automatically on first boot.
During the commissioning process administrators are able to
configure hardware settings manually before an automated smoke
test and burn-in test are done. Once commissioned, a node can
be deployed on demand by name, or allocated to a queue for
dynamic allocation to services being deployed on this MAAS.
.
This package contains the cluster controller, which is
responsible for controlling remote DHCP/TFTP instances on their
own subnets.
- maas-common: Ubuntu MAAS Server
Ubuntu MAAS Server is the successor to Orchestra. It offers a
nice UI to provision your Ubuntu servers. Each physical server
(“node”) will be commissioned automatically on first boot.
During the commissioning process administrators are able to
configure hardware settings manually before an automated smoke
test and burn-in test are done. Once commissioned, a node can
be deployed on demand by name, or allocated to a queue for
dynamic allocation to services being deployed on this MAAS.
.
This package contains common files
- maas-dhcp: Ubuntu MAAS Server - DHCP Configuration (meta-package)
Ubuntu MAAS Server is the successor to Orchestra. It offers a
nice UI to provision your Ubuntu servers. Each physical server
(“node”) will be commissioned automatically on first boot.
During the commissioning process administrators are able to
configure hardware settings manually before an automated smoke
test and burn-in test are done. Once commissioned, a node can
be deployed on demand by name, or allocated to a queue for
dynamic allocation to services being deployed on this MAAS.
.
This package configures a DHCP that can be used with MAAS.
- maas-dns: Ubuntu MAAS Server - DNS configuration (metapackage)
Ubuntu MAAS Server is the successor to Orchestra. It offers a
nice UI to provision your Ubuntu servers. Each physical server
(“node”) will be commissioned automatically on first boot.
During the commissioning process administrators are able to
configure hardware settings manually before an automated smoke
test and burn-in test are done. Once commissioned, a node can
be deployed on demand by name, or allocated to a queue for
dynamic allocation to services being deployed on this MAAS.
.
This package configures a DNS that can be used with MAAS.
- maas-region-controller: Ubuntu MAAS Server
Ubuntu MAAS Server is the successor to Orchestra. It offers a
nice UI to provision your Ubuntu servers. Each physical server
(“node”) will be commissioned automatically on first boot.
During the commissioning process administrators are able to
configure hardware settings manually before an automated smoke
test and burn-in test are done. Once commissioned, a node can
be deployed on demand by name, or allocated to a queue for
dynamic allocation to services being deployed on this MAAS.
.
This package installs the region controller services: the web
UI and the database.
- python-django-maas: Ubuntu MAAS Server - (django files)
Ubuntu MAAS Server is the successor to Orchestra. It offers a
nice UI to provision your Ubuntu servers. Each physical server
(“node”) will be commissioned automatically on first boot.
During the commissioning process administrators are able to
configure hardware settings manually before an automated smoke
test and burn-in test are done. Once commissioned, a node can
be deployed on demand by name, or allocated to a queue for
dynamic allocation to services being deployed on this MAAS.
.
This package contains the Django files.
- python-maas-client: Ubuntu MAAS API Client - (python files)
Ubuntu MAAS Server is the successor to Orchestra. It offers a
nice UI to provision your Ubuntu servers. Each physical server
(“node”) will be commissioned automatically on first boot.
During the commissioning process administrators are able to
configure hardware settings manually before an automated smoke
test and burn-in test are done. Once commissioned, a node can
be deployed on demand by name, or allocated to a queue for
dynamic allocation to services being deployed on this MAAS.
.
This package contains the client API Python modules.
- python-maas-provisioningserver: Ubuntu MAAS Server
Ubuntu MAAS Server is the successor to Orchestra. It offers a
nice UI to provision your Ubuntu servers. Each physical server
(“node”) will be commissioned automatically on first boot.
During the commissioning process administrators are able to
configure hardware settings manually before an automated smoke
test and burn-in test are done. Once commissioned, a node can
be deployed on demand by name, or allocated to a queue for
dynamic allocation to services being deployed on this MAAS.
.
This package contains the provisioning server libraries.