On 29/11/16 04:37, Jonas Wagner wrote:
> I'd like to ask a question about how MAAS uses iSCSI. Apparently, the
> MAAS region controller exposes iSCSI targets for supported Ubuntu
> images. These are flagged as vulnerable by the Nessus scanner running
> at our university.
>
> I've described this in
To be more step-by-step descriptive:
* use a commissioning script to configure any hardware RAID volumes
- or do it manually with a rescue mode boot
* recommission to discover the final volumes
* design the filesystem structure you want (i.e. which is the boot/root)
* install as per usual
Imagine you have a data center with quite a large Internet DMZ. That
will be a set of subnets, if your DMZ is too big to fit on one subnet.
Also, your DMZ probably needs to be highly available, so you might have
several subnets on different VLANs, on two or three different switches.
In the langua
This is why we put a more semantic structure into snap channels. In snap
channels the sequence of fallback (from edge to beta to candidate to
stable) is predictable. We also are gaining proper series for snaps, so
people won't get major version jump unless they want the latest bits
explicitly.
I
If this sequence does work, can we have MAAS do that directly itself
when disk space comes under pressure, and use notifications to warn /
inform the admin if disk space is getting low despite that gardening?
Mark
--
Maas-devel mailing list
Maas-devel@lists.ubuntu.com
Modify settings or unsubs
I think everything you care about is in the postgres database and /etc/maas/
Mark
On 01/02/17 17:48, Sandor Zeestraten wrote:
> Hi,
>
> Where can I find procedures for backing up and restoring a region
> controller?
> If there isn't any, what would be the current best approach to do so?
>
> --
Right, it sounds like the generalisation of this is state-transition web
hooks for integration purposes, which sounds really useful, thank you
for the idea.
Mark
--
Maas-devel mailing list
Maas-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/
Let's make "backup and restore" a key piece of functionality and let it
work through the CLI and GUI. That way, as the product evolves, the
documentation can stay simple and constant.
Mark
--
Maas-devel mailing list
Maas-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.u
On 09/02/17 17:41, Lloyd Parkes wrote:
> The name "vlan-5005" is just an internal name that MAAS made up for
> your subnet.
Whoa, that's unexpected. If we're making stuff up we should make it look
more made-up than that :)
Perhaps 'segment-f4s3t3' would be a better-looking made-up name for a
sli
On 10/02/17 06:38, Mike Pontillo wrote:
>
> It's actually a meaningful name; the '5005' in that example correlates
> directly with the VLAN ID, which should make it relatively easy to
> find its context via the MAAS API if necessary (or the UI, if you feel
> like browsing to a subnet and then manua
On 10/02/17 08:17, Mike Pontillo wrote:
> Yes and no; this >5000 value is used as the resource URI, to ensure
> that it remains constant even if the VID is changed. So its exposure,
> although unfortunate, is there. But for usability, we support a
> Fabric/VID style URI... because typically an admi
On 11/02/17 04:07, Mike Pontillo wrote:
> Yes; well, that's what the ISC DHCP server calls it, so MAAS doesn't
> really have a say in the debate. (Correction: the configuration item
> is "shared-network"; I didn't recall correctly.) There was no forcing
> function for the auto-creation; it just so
On 13/02/17 16:06, Mark Wenning wrote:
> R630 is definitely a supported server.
> Look like it autodetected OK, if you have those settings in the GUI.
> One quick thing you might want to check is in the iDRAC -> Network
> Settings, scroll near the bottom and make sure that "IPMI Over LAN" is
>
On 13/02/17 22:13, Sandor Zeestraten wrote:
> Enabling IPMI over LAN (and anything else iDRAC related) is pretty
> straightforward if you use racadm. Check out the link below.
>
> http://www.dell.com/support/manuals/no/no/nobsdt1/dell-idrac-service-module-2.0/idrac8_ug_pub-v1/Configuring-IPMI-Over-
Further on this thread, devices (like machines) will often have multiple
mac addresses and interfaces, I haven't seen a way to associate multiple
discovered addresses with a single device.
Mark
--
Maas-devel mailing list
Maas-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://li
On 20/02/17 09:56, Jonas Wagner wrote:
> We've had similar issues when trying to use HTTPS.
>
> One step was to change maas_url in regiond.conf (and also rackd.conf ?).
> The second step is to ensure that there is as valid certificate set up
> in /etc/apache2/conf-enabled/maas-http.conf ->
> /usr/s
On 20/02/17 22:13, Lloyd Parkes wrote:
> Thanks for that. It's perfectly logical in a twisted and perverse kind
> of way. I can see the UI getting updated at some point in the future
> so that it calls the reserved range two different names depending on
> whether or not the subnet is managed by MAA
This is super-useful Mike, thank you.
I wonder if we shouldn't make this a standard part of the MAAS CLI?
Mark
On 02/03/17 05:49, Mike Pontillo wrote:
> FYI,
>
>I recently found myself in need of an easy way to dump all the
> relevant information about a machine to be used with MAAS, such a
The way this has been handled in LXD is by enabling alias names for
images, and having Juju look for a particular alias
('juju/ubuntu/series') in preference to vanilla ubuntu/series.
Mark
On 27/02/17 16:57, Blake Rouse wrote:
> Matt,
>
> At the moment Juju does not support deploying a charm with
On 02/03/17 21:44, Akash Chandrashekar wrote:
> What if we made them available to paying UA customers only?
>
> Just curious
*boggle*.
Mark
--
Maas-devel mailing list
Maas-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/maas-devel
Rather than standardise VLANs, which would be brittle to share, we can
standardise the names of common 'spaces' in Juju / MAAS networking
terminology.
Having, for example, a list like:
* dmz - a space that includes machines which can also bind directly to
internet routable addresses
* pcidss
Seems to me that it would make sense to be able to add the node as a
device, in which case MAAS should avoid PXE responses altogether.
Alternatively, add the ability to tell MAAS that this node should always
just boot from its disk if it PXEs.
Mark
On 25/04/17 14:08, Mike Pontillo wrote:
> Hi Es
Hi Mac
I'll connect you privately to folks who work with Thunder processors. It
would be interesting to know if 16.04 behaves differently!
Mark
On 02/05/17 01:02, Mac Lin wrote:
> Hi there,
>
> I'm running opencord CiaB to deploy Thunder ARM64 compute node by
> MAAS, and I have had no problem wi
On 24/07/17 20:51, Ernest Martinez wrote:
> I've gotten past my initial issues with MAAS. I'm not sure if this is
> still the forum for Autopilot and Juju. If this is not the right place
> for those questions could someone please point me in the right direction.
>
Ernest - I'll be glad to connect
On 10/30/2017 10:51 PM, Michael Iatrou wrote:
> On Mon, Oct 30, 2017 at 9:16 AM, Андрей Башлаков
> mailto:a.bashla...@corp.vk.com>> wrote:
>
> Hi, all!
>
>
> Hello Andrei!
>
>
> We have several questions about MaaS roadmap:
> 1) Is there any plans to make role-based user management? C
On 10/31/2017 09:26 PM, James Beedy wrote:
> It seems my nodes get dns for a subnet which I do not care about
> having dns on (I want MAAS to manage dns on the interface/subnet that
> I have configured for DHCP, not auto-assign). Is there a method by
> which I can choose which subnet or node interf
This is super interesting. It seems to me that MAAS commissioning should
establish a unique way to identify each disk (unique MBR serial or GUID
or label) and then we should use those on boot to be very precise.
I really don't like the arbitrary behaviour of GPT-when-over-2TB but I
think that was
s -- except I am not a developer and
> anything I write would look like something MacGyver would create
> rather than professional code.
>
>
>
> Thanks,
>
>
> Daniel
>
>
> On Wed, Dec 6, 2017 at 7:30 AM, Mark Shuttleworth <mailto:m...@ubuntu.com>
28 matches
Mail list logo
