Hey guys, I have demoed MAAS for my team more times this last year then I care to count, been sowing these seeds for long enough now, the rest of the team is finally starting to get the picture and have made a group decision for everyone to become familiar with MAAS, and have devised a plan to fold everything in the datacenter into MAAS over the next few weeks/months.
Of course the first operation a team member wants to preform is to check one of the Hadoop stacks into MAAS and redeploy it on Centos. We quickly found the limitations of storage and networking only being supported on Ubuntu. I've never deployed Centos with MAAS before so I wasn't keen to this prior to seeing the message in the UI. Centos vs Ubuntu support aside, I seem to be hitting a slew of different issues ... too many to file bugs for single handedly or create workarounds for on my own. Right now, I have to battle people proving the errors that I'm hitting, fight terminology skew, and spend my time on these things (filing bugs all day and night trying to get MAAS to function correctly) - I'm so over this. I know there is a good chance that more of my issues then not may have to do with operator error, but if so, it would be nice to know so I don't waste everyones time on filing a string of issues. I'm wondering if I can hop on a call with a few of you, and have you guys observe my workflow and document and file the bugs you see as I'm hitting them? Either way, hoping we can find a better way to get to the bottom of some of these issues. Thanks, James
-- Maas-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/maas-devel
