Merge lp:~andreserl/maas/update_package_descriptions into lp:~maas-maintainers/maas/packaging

Proposed by Andres Rodriguez
Status: Merged
Approved by: Andres Rodriguez
Approved revision: 466
Merged at revision: 466
Proposed branch: lp:~andreserl/maas/update_package_descriptions
Merge into: lp:~maas-maintainers/maas/packaging
Diff against target: 134 lines (+60/-23)
2 files modified
debian/changelog (+4/-2)
debian/control (+56/-21)
To merge this branch: bzr merge lp:~andreserl/maas/update_package_descriptions
Reviewer Review Type Date Requested Status
Andres Rodriguez (community) Approve
Review via email:

This proposal supersedes a proposal from 2016-03-25.

Commit message

Update package descriptions!

To post a comment you must log in.
Revision history for this message
Andres Rodriguez (andreserl) wrote :


review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'debian/changelog'
2--- debian/changelog 2016-03-25 14:09:59 +0000
3+++ debian/changelog 2016-03-25 17:45:47 +0000
4@@ -1,7 +1,9 @@
5-maas (2.0.0~alpha4+bzr4834-0ubuntu1) UNRELEASED; urgency=medium
6+maas (2.0.0~alpha4+bzr4837-0ubuntu1) UNRELEASED; urgency=medium
8- * New upstream release, 2.0.0 alpha 4 bzr4834 (Standing FFe LP: #1553261)
9+ * New upstream release, 2.0.0 alpha 4 bzr4837 (Standing FFe LP: #1553261)
10 * Ensure /etc/maas/templates/power gets removed on upgrade
11+ * debian/control: Update homepage and package descriptions.
12+ (LP: #1562036, LP: #1562034, LP: #1562062)
14 -- Andres Rodriguez <> Wed, 23 Mar 2016 12:27:27 -0400
17=== modified file 'debian/control'
18--- debian/control 2016-03-18 15:04:24 +0000
19+++ debian/control 2016-03-25 17:45:47 +0000
20@@ -13,7 +13,7 @@
21 python3-twisted
22 Standards-Version: 3.9.6
23 X-Python3-Version: >= 3.5
27 Package: maas
28 Architecture: all
29@@ -21,18 +21,31 @@
30 maas-region-controller (= ${binary:Version}),
31 python3-django-maas (= ${binary:Version}),
32 ${misc:Depends}
33-Description: MAAS server all-in-one metapackage
34- MAAS is "Metal As A Service", a system for dynamic provisioning of physical
35- servers that has many of the same characteristics as a cloud. You register
36- servers with MAAS by telling MAAS about their IPMI or other control system.
37- MAAS can then do hardware inventory, and provision that system on demand
38- with whatever OS and software you like. MAAS is standalone software that
39- works with any configuration system, but for best results combine MAAS with
40- Juju.
41+Description: "Metal as a Service" is a physical cloud and IPAM
42+ MAAS runs a software-defined data centre - it turns a collection of physical
43+ servers into an on-demand bare metal cloud with full open source IP address
44+ management (IPAM).
45+ .
46+ MAAS controls the servers through IPMI or another BMC or converged chassis
47+ controller such as Cisco UCS. It provides a full inventory of components,
48+ and can install Ubuntu, CentOS or Windows very fast on any server under
49+ its control.
50+ .
51+ MAAS handles VLANs and fabrics that span many trunked switches, as well as
52+ the routing-centric infrastructure typically used for large-scale OpenStack
53+ or other scale-out deployments. MAAS can track IP addresses and provides
54+ APIs for address assignment and release. MAAS can also assign IP addresses
55+ for containers on machines, and release them when the machine is repurposed.
56+ MAAS provides PXE, DHCP, DNS and other low-level services to ensure the
57+ cluster works smoothly.
58+ .
59+ MAAS works with any configuration system, and is recommended by the teams
60+ behind both Chef and Juju as a physical provisioning system.
61 .
62 MAAS provides:
63 * Hardware inventory of servers
64- * Dynamic provisioning based on name or attributes such as disk, RAM cores, sockets
65+ * Dynamic provisioning based on name or attributes such as disk, RAM, cores,
66+ nic's, networking
67 * DNS and DHCP as needed
68 * PXE boot services
69 .
70@@ -82,9 +95,18 @@
71 postgresql (>= 9.1),
72 ${misc:Depends},
73 Recommends: openssh-server
74-Description: MAAS server complete region controller
75- This package installs and configures the complete MAAS region controller,
76- including the minimum setup, plus the database server and messaging queue.
77+Description: Region Controller for MAAS
78+ The MAAS region controller is the REST API server for all MAAS clients,
79+ and the postgres database that maintains machine state for the entire
80+ data centre (or “region”). The region controller can be scaled-out and
81+ highly available given the appropriate postgres setup and additional
82+ API servers.
83+ .
84+ This package installs the postgres database and the API server, so it
85+ is appropriate for the initial installation of a new MAAS region. To
86+ scale out the controller or make it highly available, install
87+ maas-region-controller-api on additional servers and ensure the
88+ postgres database is HA too.
90 Package: python3-maas-provisioningserver
91 Section: python
92@@ -131,10 +153,11 @@
93 ${python3:Depends}
94 Conflicts: maas-region-controller-min (<= 1.5+bzr1909-0ubuntu1)
95 Replaces: maas-region-controller-min (<= 1.5+bzr1909-0ubuntu1)
96-Description: MAAS command line API tool
97- This package contains the MAAS client command line API tool.
98- This tool enables automation of tasks in MAAS, remotely, through
99- its API.
100+Description: MAAS client and command-line interface
101+ This package contains the 'maas' command-line interface, which
102+ talks to the MAAS region controller REST API. Use the maas command
103+ to login to MAAS and drive the data centre entirely from the
104+ command-line.
106 Package: python3-maas-client
107 Section: python
108@@ -179,10 +202,22 @@
109 maas-cluster-controller
110 Replaces: python-maas-provisioningserver,
111 maas-cluster-controller
112-Description: MAAS server cluster controller
113- This package contains the MAAS cluster controller, which is responsible
114- for enabling and controlling remote DHCP/TFTP instances on their own
115- subnets.
116+Description: Rack Controller for MAAS
117+ The MAAS rack controller provides highly available, fast and local
118+ broadcast services to the machines provisioned by MAAS. There should
119+ be a MAAS rack controller attached to each fabric (which is a set of
120+ trunked switches). You can arrange for multiple rack controllers
121+ that are attached to these physical networks, and MAAS will then be
122+ highly available, with secondary rack controllers automatically
123+ stepping to provide these services to a rack if the primary rack
124+ controller fails.
125+ .
126+ A common configuration is to have a rack controller in each rack,
127+ with secondary network interfaces on one or two other racks for high
128+ availability redundancy.
129+ .
130+ This package also installs all the necessary components to provide
131+ iSCSI, DHCP, TFTP and power management.
133 Package: python3-django-maas
134 Section: python


People subscribed via source and target branches

to all changes: