Thank you. I prefer the cloud-init option. But I couldn't find the thread you mentioned. If anyone can provide some guidance on this approach I'd really appreciate it. My thoughts are to inject my node customization into MAAS's node user-data, for the machine's cloud-init to pick it up when deployed by juju. From what I can gather there's no MAAS command to do this, so may be direct API interaction is needed (with RESTful POST may be). I was browsing the Juju source code to try and find out how juju builds its user-data and how and where it inserts it in MAAS. Thought that will give me some hints. But I got lost (my python skills are next to none) :-)
Thanks,Sameer From: Mark Shuttleworth <m...@ubuntu.com> To: Sameer Zeidat <same...@yahoo.com>; juju@lists.ubuntu.com Sent: Monday, November 17, 2014 3:30 AM Subject: Re: Machine customization for MAAS Hi Sameer No problem, this is the right place to ask. There was a thread on this topic on this list a month or two back, so look there for more detail, but in short: * get cloud-init to run scripts on your behalf on install, or * use a subordinate charm if the work can be done after the main service is setup In future we'll have a mechanism to let you place a charm on the machine to do this before other charms are deployed. Mark On 15/11/14 17:15, Sameer Zeidat wrote: Hi, Sorry for asking here. Got a need to do a simple change in deployed machines on maas (alter the network/ interfaces file). I didn't want to add that to one of my charm hooks as it doesn's seem the appropriate place for it. Anyone done it before and can give me some hints. I use the curtain installer and tried all sorts of things with the curtain preseed files without luck. Thanks, Sameer
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
